Content for TS 23.284 Word version: 18.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…

8.2.3 Inter-MSC UMTS to GSM Handover
...

8.2.3 Inter-MSC UMTS to GSM Handover p. 69

8.2.3.1 Inter-MSC UMTS to GSM Handover that establishes Local Switching p. 69

8.2.3.1.1 General p. 69

When LCLS is not established for a call and an inter-MSC UMTS to GSM handover occurs that makes the call local, the call can be locally switched in the Target BSS. The following clauses describe the additional requirements for inter-MSC handovers that establish LCLS.

8.2.3.1.2 MSC-1 / MGW-1 p. 69

8.2.3.1.2.1 Relocation Required p. 69

When MSC-1 Server receives the Relocation Required message from the serving RNC and determines that the call shall be handed over to the Target MSC Server, it shall send the GCR of the call, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE to the Target MSC Server in a MAP Prepare-Handover_Request message.

8.2.3.1.2.2 Handover Request Acknowledge p. 69

When MSC-1 Server receives the MAP Prepare_Handover_Response including Handover_Request_Acknowledgement message with a LCLS-BSS-Status IE the Anchor MSC-1 Server configures the bearer terminations in MGW-1 and sends the GCR IE, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE to the target MSC-Server.

8.2.3.1.2.3 Bearer establishment between MGW-1 and Target MGW p. 70

The handling of the bearer establishment between MGW-1 and Target MGW is as described in clause 6.1 for a Basic Mobile Originating Call. The MSC server shall also use the Change Flow Direction procedure to request the MGW-1 to set the Handover Device to the initial state.

8.2.3.1.2.4 MGW Flow Direction Control p. 70

In accordance with the normal handover case the MGW-1 isolates the termination towards the Target MGW (T2) from the termination to the RNC(TS) and configures the Anchor termination (T1) one-way DL towards the Target MGW termination (T2). Termination to the RNC (TS) is both-way connected to Anchor termination (T1) since it is also receiving UL user data from termination to the RNC (TS).

8.2.3.1.2.5 Relocation Command/Handover Detect p. 70

The MSC-1 Server uses the Change Flow Direction procedure to requests the MGW-1 to set the Handover Device to intermediate state.

8.2.3.1.2.6 Handover Complete p. 70

When the MSC-1 Server receives the Handover Complete message, it releases the related Iu-interface connection towards RNC. The MSC-1 Server also requests MGW-1 to set the Handover Device to its final state by removing the bearer termination towards the RNC.

The MSC-1 server shall send to the adjacent call node the LCLS-Status-Update message with the LCLS-Status IE indicating that LCLS is established.

8.2.3.1.3 Target MSC Server / Target MGW p. 70

8.2.3.1.3.1 Prepare Handover Request message and MGW selection p. 70

The Target MSC server selects the Target MGW when it receives MAP Prepare Handover Request message. The Target MSC server sends the Handover Request message to the Target BSS as for the normal case but shall include the GCR IE, the LCLS-Configuration IE and the LCLS-Connection-Status-Control IE set to "Connect".

8.2.3.1.3.2 Handover Request Acknowledge p. 70

If the Target BSS supports the LCLS feature it shall include the LCLS-BSS-Status IE in the Handover Request Acknowledge message in order to inform the Target MSC Server that the BSS supports the LCLS feature. The Target MSC Server sends the same information in the MAP Prepare Handover Response message to the MSC-1 Server.

8.2.3.1.3.3 Bearer establishment towards Target BSS p. 70

When the Target MSC Server has selected the Target MGW it requests the Target MGW to seize a TDM circuit if AoTDM using the Reserve Circuit procedure, or an IP termination if AoIP using the reserve Connection Point procedure as for the normal handover procedure. The Target MSC Server sends the Handover Request message to the Target BSS containing the CIC for AoTDM or the IP addresses and UDP ports received from the target MGW if AoIP.

8.2.3.1.3.4 Bearer establishment between MGW-1 and Target MGW p. 70

The handling of the bearer establishment between MGW-1 and Target MGW is as described for basic mobile terminating call in clause 6.2.

8.2.3.1.3.5 Handover Complete p. 70

When LCLS has been established during the handover procedure, the target BSS informs the target MSC-Server that the call has been locally switched in the Handover Complete message.

8.2.3.1.4 Example of Inter-MSC UMTS to GSM Handover that establishes Local Switching p. 71

8.2.3.1.4.1 Connection Model p. 71

Figure 8.2.3.1.4.1.1 shows the network model for the Basic Inter-MSC UMTS to GSM handover when LCLS is established as a result of the handover. The dashed line in green represents call control signalling and the dashed line in blue represents the user plane connection path via the core network, which should be used if LCLS is not established or after LCLS is broken. The non-dotted lines represent the bearer carrying real user plane data. In MGW-1 the bearer termination TS is used for the bearer towards RNC, bearer termination T1 is used for the bearer towards the succeeding/preceding MGW, that is MGW-2 and bearer termination T2 is used towards the Target MGW. In MGW-2 the bearer termination T4 is used for the bearer towards BSS-2 and bearer termination T3 is used for the bearer towards MGW-1. In Target-MGW the bearer termination TT is used towards the Target-BSS and bearer termination T5 is used towards MGW-1.

In this example scenario the Handover Device is located in MGW-1 selected for the call establishment by the MSC-1 server, which controls the call and mobility management.

Copy of original 3GPP image for 3GPP TS 23.284, Fig. 8.2.3.1.4.1.1: Basic Inter-MSC UMTS to GSM Handover (network model)

Figure 8.2.3.1.4.1.1: Basic Inter-MSC UMTS to GSM Handover (network model)
(⇒ copy of original 3GPP image)

8.2.3.1.4.2 Basic Sequence for Inter-MSC UMTS to GSM Handover that establishes Local Switching p. 72

Figure 8.2.3.1.4.2.1 and Figure 8.2.3.1.4.2.2 show the message sequence example for the Basic Inter-MSC UMTS to GSM Handover shown in the corresponding network model Figure 8.2.3.1.4.1.1. The Handover Device is located in MGW-1 selected for the call establishment by the MSC-1 server, which controls the call and the mobility management. The description is based on TS 23.009, TS 23.205 and TS 23.231.

Copy of original 3GPP image for 3GPP TS 23.284, Fig. 8.2.3.1.4.2.1: Initial phase of Inter-MSC UMTS to GSM Handover establishing Local Switching

Figure 8.2.3.1.4.2.1: Initial phase of Inter-MSC UMTS to GSM Handover establishing Local Switching
(⇒ copy of original 3GPP image)

Step 1.

Iu Relocation Required Request is received from RNC requesting an inter-MSC handover. The call is currently not locally switched.

Step 2.

The MSC-1 server determines that inter-MSC handover is required and sends the MAP Prepare-Handover Request message to target MSC-Server which includes LCLS Negotiation Request IE, the LCLS-Configuration-Preference IE and GCR IE.

Step 3a, b.

The Target-MSC-Server requests the target MGW to reserve circuit or Connection Point towards the Target-BSS

Step 4.

The Target MSC-Server sends Handover Request message to the Target BSS with GCR, the LCLS-Configuration IE and the LCLS-Connection-Status-Control IE indicating "connect" to through-connect the local call.

Step 5.

Target BSS performs call leg correlation with GCR to find if another call leg is active with same GCR. The BSS reports in Handover Request Acknowledge message that the local call was found but LCLS is not yet established.

Step 5a.

The BSS-2 notifies MSC-2 server the LCLS status is changed by sending the LCLS_ Notification message with the LCLS-BSS-Status IE set to "Call not yet locally switched".

Step 5b.

If the call has been answered and MSC-2 server permits LCLS to be connected, then the MSC-2 server sends to the BSS-2 the LCLS_Connect_Control message with the LCLS-Connection-Status-Control IE set to "connect".

Step 5c.

The BSS-2 returns the LCLS_Connect_Control_ACK message with the LCLS-BSS-Status IE set to "Call not yet locally switched".

Step 6a, b.

(These signalling steps are only applicable to AoIP.) When the Target MSC-Server receives the BSSMAP Handover Request-Ack message, it sends the BSC-B IP address and UDP Port number to the MGW-B using the Configure RTP Connection Point procedure.

Step 7.

The Target MSC-Server sends the MAP Prepare Handover Response message to MSC-1 server.

Step 8a, b.

In accordance with normal handover the MSC-1 server requests MGW-1 to isolate the termination towards Target MGW (T2) from the termination to the Serving BSS-1 (TS) and to configure the Anchor termination (T1) one-way DL towards the Target MGW termination (T2).

Step 9.

MSC-Server 1 sends IAM (Initial Address Message) to Target MSC-Server including GCR, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE.

Step 10a, b.

Target MSC-Server reserves bearer connection T5 towards MGW-1.

Step 11.

After Target MGW has replied with the bearer address and the binding reference (Step 10b), the Target MSC-Server returns APM with selected codec, the LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE.

Copy of original 3GPP image for 3GPP TS 23.284, Fig. 8.2.3.1.4.2.2: Completion phase of Inter-MSC UMTS to GSM Handover establishing Local Switching

Figure 8.2.3.1.4.2.2: Completion phase of Inter-MSC UMTS to GSM Handover establishing Local Switching
(⇒ copy of original 3GPP image)

Step 12.

Target MSC-Server sends ACM (Address Complete Message). Target MSC-Server awaits the capturing of the UE-1 on the radio path when the ACM is sent and MSC-1 server initiates the handover execution when receiving ACM.

Step 13 - 18.

When the local switching has been established during the handover procedure, the target BSS shall inform the target MSC-Server that the call has been locally switched in HANDOVER COMPLETE, and the target BSS shall also send a new message LCLS-Notification with LCLS-BSS-Status IE to inform the MSC-2 server that the local switching has been established. In steps 16a and 16b the MSC-1 server configures MGW-1 for the completion of the handover.

Step 19.

A-HO-DETECT/COMPLETE when received, is included in the MAP-Send-End-Signal request and send back to the MSC-1 server.

Step 20.

Target MSC-Server sends ANSWER when A-HO-DETECT/COMPLETE is received.

Step 21a, b.

MSC-1 Server releases the call leg in RNC.

Step 22a, b.

MSC-1 server releases the bearer termination towards RNC.

Step 23.

Target MSC-Server informs the MSC-1 server about the LCLS Status.

Step 24.

MSC-1 server (Anchor MSC-Server) sends LCLS-Status-Update message to the far end MSC-2 server.

Step 25.

Local switching is established in the BSS.

8.2.3.2 Inter-MSC UMTS to GSM Handover that does not establish Local Switching p. 76

Inter-MSC UMTS to GSM Handover that does not establish Local Switching follows the procedures in clause 8.2.3.1. The differences are:

in the step 17, the target BSS informs target MSC that the call is not locally switched in the Handover Complete.
steps 5a, 5b, 5c 18, step 23, step 24 and step 25 are not triggered.