LTE Handover Call Flow
LTE Handover Call Flow
Overview CONTENTS
With the fast-changing mobile landscape and convergence in all aspects of Objectives of Handover Procedures pg. 2
telecommunications, “seamless handover” is important for any technology
Intra-LTE (Intra-MME/SGW) Handover
to succeed. Operators and consumers both benefit from seamless handover Using the X2 Interface pg. 2
in terms of cost effectiveness, enhanced features, location independence
and ease of use, not only within a Long Term Evolution (LTE) network but Intra-LTE (Intra-MME/SGW) Handover
also between networks including UMTS, GSM and CDMA. Using the S1 Interface pg. 4
Conclusions pg. 11
References pg. 11
Interoperable UE Handovers in LTE | Radisys White Paper 2
2. Handover shall not drain the UE battery power. • Inter-RAT: Handover between different radio
technology networks, for example GSM/UMTS
3. Service continuity shall be maintained and UMTS
(i.e., minimal handover latency).
4. Seamless handoff to 3G / 2G / CDMA technology. We’ll look at Intra-LTE handovers with X2AP signaling
and S1AP signaling first, then Inter-RAT handovers
There are two ways a handoff can be decided: in LTE (i.e., handover between LTE and UMTS).
• Network Evaluated: the network makes the
handover decision Intra-LTE (Intra-MME/SGW)
• Mobile Evaluated: the UE makes the handoff decision Handover Using the X2
and informs the network about it. In this instance, Interface
the final decision will be made by the network based This procedure is used to handover a UE from a source
upon on the Radio Resource Management. eNodeB (S-eNB) to a target eNodeB (T-eNB) using
In 3G and LTE networks, a hybrid approach is used to the X2 interface when the Mobility Management Entity
decide on the handover. In this case, the UE will assist (MME) and Serving Gateway (SGW) are unchanged.
in the handoff decision by measuring the neighboring It is possible only if direct connectivity exists between
cells and reporting the measurements to the network, the source and target eNodeB’s with the X2 interface.
which in turn decides upon the handoff timing and the The X2 handover procedure is performed without
target cell/node. The parameters to measure and the Evolved Packet Core (EPC) involvement, i.e. preparation
thresholds for reporting are decided by the network. messages are directly exchanged between the S-eNB
and T-eNB. The release of the resources at the source 7. The S-eNB generates the RRC message to perform the
side during the handover completion phase is triggered handover, i.e, RRCCONNECTION RECONFIGURATION
by the T-eNB. The message flow is shown in Figure 1 message including the mobilityControlInformation.
followed by the description. The S-eNB performs the necessary integrity protection
1. A data call is established between the UE, S-eNB and ciphering of the message and sends it to the UE.
and the network elements. Data packets are 8. T
he S-eNB sends the eNB STATUS TRANSFER
transferred to/from the UE to/from the network message to the T-eNB to convey the PDCP and
in both directions (DL as well as UL). HFN status of the E-RABs.
2. The network sends the MEASUREMENT CONTROL 9. T
he S-eNB starts forwarding the downlink data
REQ message to the UE to set the parameters to packets to the T-eNB for all the data bearers
measure and set thresholds for those parameters. Its (which are being established in the T-eNB during
purpose is to instruct the UE to send a measurement the HANDOVER REQ message processing).
report to the network as soon as it detects the 10. In the meantime, the UE tries to access the T-eNB
thresholds. cell using the non-contention-based Random
3. The UE sends the MEASUREMENT REPORT to the Access Procedure. If it succeeds in accessing
S-eNB after it meets the measurement report criteria the target cell, it sends the RRC CONNECTION
communicated previously. The S-eNB makes the RECONFIGURATION COMPLETE to the T-eNB.
decision to hand off the UE to a T-eNB using the 11. T
he T-eNB sends a PATH SWITCH REQUEST
handover algorithm; each network operator could message to the MME to inform it that the UE
have its own handover algorithm. has changed cells, including the TAI+ECGI of
4. The S-eNB issues the RESOURCE STATUS REQUEST the target. The MME determines that the SGW
message to determine the load on T-eNB (this is can continue to serve the UE.
optional). Based on the received RESOURCE STATUS 12. T
he MME sends a MODIFY BEARER REQUEST
RESPONSE, the S-eNB can make the decision to (eNodeB address and TEIDs for downlink user
proceed further in continuing the handover procedure plane for the accepted EPS bearers) message
using the X2 interface. to the SGW. If the PDN GW requested the UE’s
5. The S-eNB issues a HANDOVER REQUEST message location info, the MME also includes the User
to the T-eNB passing necessary information to Location Information IE in this message.
prepare the handover at the target side (e.g., UE 13. The SGW sends the downlink packets to the target
Context which includes the Security Context and eNB using the newly received addresses and TEIDs
RB Context (including E-RAB to RB Mapping) and (path switched in the downlink data path to T-eNB)
the Target cell info). and the MODIFY BEARER RESPONSE to the MME.
6. The T-eNB checks for resource availability and, if 14. T
he SGW sends one or more “end marker” packets
available, reserves the resources and sends back on the old path to the S-eNB and then can release
the HANDOVER REQUEST ACKNOWLEDGE message any user plane / TNL resources toward the S-eNB.
including a transparent container to be sent to the
UE as an RRC message to perform the handover. The 15. T
he MME responds to the T-eNB with a PATH
container includes a new C-RNTI, T-eNB security SWITCH REQ ACK message to notify the completion
algorithm identifiers for the selected security of the handover.
algorithms, and may include a dedicated RACH 16. T
he T-eNB now requests the S-eNB to release
preamble and possibly some other parameters the resources using the X2 UE CONTEXT RELEASE
(i.e., access parameters, SIBs, etc.). message. With this, the handover procedure is
complete.
Interoperable UE Handovers in LTE | Radisys White Paper 4
Inter-MME Handover 2. T
he S-MME uses GTP signaling to communicate
the handover signaling to the T-MME and vice versa.
Using the S1 Interface The FORWARD RELOCATION procedure in GTP-C is
(Without Changing S-GW) being used here.
In an inter-MME handover, two MMEs are involved in 3. A
fter receiving the S1 HANDOVER REQUIRED, the
the handover, the source MME (S-MME) and target S-MME detects that the target cell requested for
MME (T-MME). The S-MME controls the S-eNB and the handover belongs to another MME and initiates
T-MME controls the T-eNB; both MMEs are connected the GTP FORWARD RELOCATION REQ message
to the same SGW. This handover is triggered when the to the T-MME.
UE moves from one MME area to another MME area. 4. The T-MME creates the S1 logical connection toward
the T-eNB and sends the S1 HANDOVER REQ on it.
1. As mentioned in the previous section (Intra-MME/
SGW handover), based on the MEASUREMENT 5. The T-eNB prepares the requested resources and
REPORT from the UE, the S-eNB decides to handover responds with a HANDOVER REQ ACK to the T-MME.
the UE to another eNodeB (T-eNB). The handover 6. T
he T-MME sends a GTP FORWARD RELOCATION
procedure in this section is very similar to that in the RESP to the S-MME, to notify the resource
previous section except for the involvement of two reservation at the T-eNB. From this point onwards,
MMEs coordinating the handover signaling between the interaction between the S-MME and S-eNB
the source and target eNodeBs. is very similar to the S1-based Intra-MME/SGW
handover described in the previous section.
Interoperable UE Handovers in LTE | Radisys White Paper 6
5. Once the T-RNC detects the UE in its area, it phase, resources are reserved in the target network,
notifies the T-SGSN about the completion of the while in the execution phase the UE is handed over
handover by sending a RANAP: RELOCATION to the target network from the source network. The
COMPLETE message. Preparation phase message flow is given in Figure 7,
6. The T-SGSN notifies the completion of handover followed by the description.
to the S-MME by sending a GTP: FORWARD 1. O
nce the inter-RAT handover is decided at
RELOCATION COMPLETE NOTIFICATION ACK the S-RNC based on the measurement report
message. The S-MME acknowledges this message procedure, it prepares and sends a RANAP
and proceeds with release of the resources RELOCATION REQUIRED message to the S-SGSN.
associated with this UE at the S-SGW and S-eNB. 2. The S-SGSN detects that it is an Inter-RAT handover
7. The T-SGSN modifies the E-RAB resources at from the message contents and retrieves the T-MME
the T-SGW by initiating the GTP MODIFY BEARER details from the database based on the information
procedure. in the message. It now prepares and sends a GTP-C:
8. The T-SGW notifies the bearer parameters with FORAWRD RELOCATION REQUEST to the T-MME.
the PGW by initiating the GTP MODIFY BEARER 3. T
he T-MME detects the change of SGW and creates
procedure. the bearer resources in the T-SGW by initiating the
GTP: CREATE SESSION procedure.
Inter-RAT Handover: 4. O
nce the resources are reserved at the T-SGW,
UTRAN to E-UTRAN it responds to the T-MME with a GTP: CREATE
SESSION RESPONSE message.
Preparation Phase
5. T
he T-MME now reserves the resources at the
In the UMTS-to-LTE Inter-RAT handover, the S-RNC
T-eNB by sending aS1AP: HANDOVER REQUEST
connects to the S-SGSN and S-SGW, the T-eNB
message to it.
connects to the T-MME and T-SGW, and both the
source and target SGWs connect to the same PGW. 6. T
he T-eNB reserves the radio resources and
As above, this procedure is divided into two parts for responds to the T-MME with a S1AP: HANDOVER
clarity, Preparation and Execution. In the Preparation REQUEST ACK message.
Interoperable UE Handovers in LTE | Radisys White Paper 10
Corporate Headquarters
5435 NE Dawson Creek Drive
Hillsboro, OR 97124 USA
503-615-1100 | Fax 503-615-1121
Toll-Free: 800-950-0044
www.radisys.com | info@radisys.com