Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.284  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   4…   4.2…   4.3…   5   6…   6.3…   6.3.2   6.3.3   6.3.4   6.3.5   7…   7.2.4…   7.2.4.2   7.2.4.3   7.2.4.4   7.2.4.5   7.2.4.6   7.3…   7.3.4…   7.3.4.2   7.3.4.3   7.3.4.4   8…   8.2.3   8.3…   8.3.2   8.4…   8.4.1.1.7…   8.4.1.2…   8.4.2…   8.4.2.2…   8.4.5…   8.4.5.6   8.4.5.7   8.4.5.8…   9…   13…   13.4…   13.4.3…   13.4.4…   13.5…   13.6…   13.7…   14…   16…   A…   A.2… 
7.2.4.5 Intermediate Node/GMSC Server Initiated 
...

 

7.2.4.5  Intermediate Node/GMSC Server Initiated  p. 55

Figure 7.2.4.5.1 shows the message sequence example for the network initiated LCLS Break.
Copy of original 3GPP image for 3GPP TS 23.284, Fig. 7.2.4.5.1: Intermediate Node / GMSC Server initiated LCLS break
Figure 7.2.4.5.1: Intermediate Node / GMSC Server initiated LCLS break
(⇒ copy of original 3GPP image)
Up
Step 1.
The iMSC server determines that local switching should be disconnected.
Step 2a, b.
The iMSC server send the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" to the preceding node and to the succeeding node.
Step 3.
-
  1. The oMSC server sends to the oBSS the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "Release LCLS".
  2. The tMSC server sends to the tBSS the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "Release LCLS".
Step 4.
-
  1. The oBSS confirms the reception of the LCLS release request but does not change the LCLS-BSS status since LCLS release request is not yet received for the associated call leg.
  2. The tBSS reports the LCLS disconnection by sending the LCLS-Connect-Control Acknowledge message with the LCLS-BSS-Status IE set to "the call is no longer locally switched" to the tMSC server.
  3. The oBSS reports the LCLS disconnection by sending the LCLS-Notification message with the LCLS-BSS-Status IE set to "the call is no longer locally switched" to the oMSC server.
Step 5.
-
  1. On the receipt of the LCLS-Connect-Control Acknowledge message with the LCLS-BSS status still indicating local switching the oMSC server sends to the succeeding node the LCLS Status Change Request Acknowledge message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" and the Result code IE set to LCLS Status Change Request accepted.
  2. On the receipt of the LCLS-Connect-Control Acknowledge message the tMSC server sends to the preceding node the LCLS Status Change Request Acknowledge message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" and the Result code IE set to LCLS Status Change Request accepted.
Step 6.
-
  1. At reception of the LCLS-Connect-Control Acknowledge message indicating LCLS disconnection the tMSC server sends the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected" to the preceding node.
  2. On the receipt of the LCLS-Notification message the oMSC server sends the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected" to the succeeding node.
Up

Up   Top   ToC