UMTS Signaling

4.6.2 Inter-3G-2G_MSC Handover Call Flow

First a complete end-to-end call flow diagram of the procedure is introduced (Figure 4.43 and following) and then important messages and parameters as monitored on E interface will be presented as detailed as possible.

Figure 4 43 - Inter-3G-2G_MSC Handover/Relocation Call Flow 1/4 The trigger to start an Inter-RAT Handover procedure is defined when RRC measurement is set up as described in part 2 of this book. The appropriate trigger event is identified by ID "e3a" = "The estimated quality of the currently used UTRAN frequency is below a certain threshold and the estimated quality of the other system is above a certain threshold". Including full parameterization (hysteresis, time-to-trigger value etc.) the setup procedure of this event trigger is done by sending RRC Measurement Control message from SRNC to UE. Anytime during an active call the UE moves into a position where the trigger conditions are fulfilled. This is when UE sends RRC Measurement Report with event-ID = "e3a". Now the SRNC starts the handover procedure with sending RANAP Initiating Message with procedure code = "Relocation Resource Allocation" (in 3GPP 25.413 this combination is named RANAP Relocation Preparation message) including a source ID and a target ID to its serving MSC. The relocation type = "UE involved" indicates that UE will perform handover and relocation simultaneously. The cause value = "Time critical relocation" shall set a higher priority in comparision to intra-3G relocation/handover procedures. The source ID is encoded using the UMTS service area identifier (SAI). The target ID uses the cell group identifier (CGI) to identify the target radio network subsystem. Since CGI is typical for Base Station Subsystems (BSS) it already emerges at this point of the call that the handover target will be a GSM cell. It is task of the serving MSC to take the important parameters from the RANAP message and construct a BSSMAP Handover Request message. To highlight this point: it is the 3G MSC that constructs a BSSMAP message, which is actually used for communication between 2G MSC and BSC on GSM A interface. In TCAP transaction portion the application context name version 3 is used in first step. However, as it will happen often in early days of 3G networks and inter-system handovers the target 2G MSC is not able to "understand" this version 3. Hence, it sends TCAP Abort message and requests a repetition of the dialog using application context name version 2. After successful reception of MAP Prepare Handover operation on 2G MSC side a SCCP class 2 connection is set up between 2G MSC and target BSC. It starts with a SCCP Connection Request (CR) message that carries the BSSMAP Handover Request as constructed by 3G MSC before. The BSC that receives the BSSMAP Handover Request proceeds as in case of normal intra-2G handover: it creates a RSL (Radio Signaling Link protocol) Channel Activation message (CHNAV) that is sent to the GSM base transceiver station (BTS). In the Channel Activation message the time slot number for the call after handover to GSM and the handover reference number value (HO Ref) are found. It should be noticed that especially the channel activation messages of the RSL protocol often contain proprietary parameters and/or sequences so that is mostly depends on the equipment manufacturer how these messages look in detail.

Copyright Tektronix Berlin GmbH & Co KG. Company confidential.

UMTS Signaling

Figure 4 44 - Inter-3G-2G_MSC Handover/Relocation Call Flow 2/4 In next step the BTS confirms the channel activation for time slot 4 with a RSL Channel Activation Acknowledge message (CHNAK). The setup of SCCP connection on A interface is confirmed with a SCCP Call Confirm (CC) sent by BSC. This CC message includes a BSSMAP Handover Request Accept as information to the MSC that requested the handover (the 3G MSC!) that radio resources have been allocated successfully. The BSSMAP message contains a DTAP Handover Command (HCOM), which is to order the UE to enter the GSM cell and use time slot 4 of this cell to continue the call. The absolute radio frequency code number (ARFCN) is used to distinguish this cell from its neighbor GSM cells on radio interface. It indicates the unique frequency of this cell's broadcast channel, because in GSM each neighbor cell has its own unique BCH frequency. So the function of the ARFCN as identifier in GSM can be compared with the identification function of primary scrambling code in UTRAN. The DTAP Handover Command also contains the handover reference number that will be used later by BSC to detect the successful handover. With MAP Prepare Handover acknowledge the 3G MSC receives the handover number (HO No.) for routing of ISUP IAM related to this call. Now the traffic channel on E interface is set up using the well-known ISUP procedure while the embedded DTAP Handover Complete is forwarded on IuCS interface to SRNC using RANAP Successful Outcome message for Relocation Resource Allocation. Now the SRNC sends a RRC Handover from UTRAN Command-GSM to the UE. This RRC message contains information about the new radio access technology (frequency band = dcs1800) as well as information how the radio access bearer shall be defined in the new cell. In addition the message transports the DTAP Handover Command coming from target BSC to the UE.

Copyright Tektronix Berlin GmbH & Co KG. Company confidential.

UMTS Signaling

Figure 4 45 - Inter-3G-2G_MSC Handover/Relocation Call Flow 3/4 After the UE switched into the new cell the UE sends a handover access burst on radio interface containing the same handover reference no (HO Ref) that has been assigned with RSL channel activation procedure to the BTS. When the handover access burst is received and the HO Ref value is the same as expected (which is the normal case) a RSL Handover Detect (HODET) message is sent by BTS to BSC. The time slot number (TS=4) links this message to the channel activation procedure. So the BSC is enabled to send a BSSMAP Handover Detect (HODET) message to the 3G MSC using the active SCCP class 2 connection. This BSSMAP HODET contains the HO Ref assigned to the procedure before. To forward the BSSMAP HODET to the 3G MSC 2G MSC needs to send this message enclosed in a MAP Process Access Signaling operation. Simultaneously 2G MSC activates the forwarded voice traffic channel on E interface by sending ISUP Answer message (ANM) for the defined CIC. Meanwhile radio link establishment on Abis interface is complete by RSL Establish Indication (ESTIN) and a Data Indication (DATIN) is used to transport the first layer 3 DTAP message from UE to the BSC using GSM radio channels. This message is DTAP Handover Complete (HCOMP) with cause value = "normal event". So it is a regular and successful handover. BSSMAP sends Handover Complete to anchor MSC of the call (3G MSC) embedded in MAP Send End Signal, which means that handover procedure from point of view of MAP is finished. Reception of BSSMAP Handover Complete triggers release of the RANAP and SCCP connection on IuCS interface by 3G MSC. With this procedure also the radio access bearer will be released as described in MOC/MTC scenarios in part 2 of this book. The further messages in the UTRAN are used to release the assigned UMTS radio resources (RNTI[s], scrambling codes, spreading codes etc.) with NBAP Radio Link Deletion. Also the AAL2 SVC established for transport of dedicated traffic channels and dedicated control channels are released on both, Iub and IuCs interface.

Copyright Tektronix Berlin GmbH & Co KG. Company confidential.

UMTS Signaling

Figure 4 46 - Inter-3G-2G_MSC Handover/Relocation Call Flow 4/4

4.6.3 Inter-3G-2G_MSC Handover Messages on E Interface

Now the focus is on the messages of the previously described handover procedure that can be monitored on E interface between 3G MSC and 2G MSC. Addressing aspects and parameter description shall be highlighted.

Figure 4 47- Inter-3G-2G_MSC Handover/Relocation on E-Interface Call Flow 1/3 The end-to-end addressing between both MSCs is a task of SCCP. Since the application part is MAP SCCP UDT messages will be exchanged between MSCs and each UDT contains a called party address as well as a calling

Copyright Tektronix Berlin GmbH & Co KG. Company confidential.