Content for TS 23.284 Word version: 17.0.0
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.6 MSC server Initiated when Access Side Termination is isolated in MGW p. 57
Figure 7.2.4.6.1 shows the message sequence example for the MSC server initiated LCLS Break for the case when the LCLS negotiation through the Core Network enabled the MSC server to use the option to isolate access side termination from the network side termination.
In this example the oMSC server moves the originating UE (access side termination T1) back to the context oC with network side termination T2 and requests the oMGW to be bothway through-connected after the oMSC server determined that local switching should be disconnected and sent to the succeeding node the LCLS Status Change Request message indicating LCLS disconnection preparation.
Figure 7.2.4.6.1: MSC initiated LCLS break, access side termination isolated in MGW
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
Step 1.
The oMSC server determines that local switching should be disconnected.
Step 2.
The oMSC server sends to:
Step 3.
- the succeeding node the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation";
- the oMGW request to move the access side termination T1 to context oC with the network side termination T2;
The further steps are performed as defined in clause 7.2.4.2, steps 3 - 12.
