Lte Handover

Download as pdf or txt
Download as pdf or txt
You are on page 1of 17

Handover in LTE

Mobility Types
 Two types of handover procedure in LTE
for UEs in active mode
 the S1-handover procedure
 no X2 interface between the two eNodeBs
 configured to initiate handover towards a particular
target eNodeB via the S1 interface
 the X2-handover procedure
 normally used for the inter-eNodeB handover
S1-Handover
 Consist of
a preparation phase
 steps 2 to 8
 involving the core network

 the resources are first prepared at the target side

 an execution phase
 steps 8 to 12
a completion phase
 after step 13
S1-Handover ~ Preparation Phase
S1-Handover ~ Execution Phase
S1-Handover ~ Completion Phase
S1-Handover
 the ‘STATUS TRANSFER’ message
 themain difference compared to UMTS
 sent by the source eNodeB
 steps 10 and 11
 added in order to carry some PDCP status
information
 that is needed at the target eNodeB in cases when
PDCP status preservation applies for the S1-
handover
 in alignment with the information which is sent
within the X2 ‘STATUS TRANSFER’ message
S1-Handover
 assumed to be triggered in parallel with the
start of data forwarding
 after the source eNodeB has received the
‘HANDOVER COMMAND’ message from the
source MME
 The ‘HANDOVER NOTIFY’ message
 step 13
 sent later by the target eNodeB
 when the arrival of the UE at the target side is
confirmed
S1-Handover
 forwardedby the MME to trigger the update of
the path switch in the S-GW towards the
target eNodeB the resources at the source
side are
 The ‘RELEASE RESOURCE’ message
 Release the resources at the source side
X2-handover
 Handover via the X2 interface is triggered
by default
 unless there is no X2 interface established
 Unless the source eNodeB is configured to
use the S1-handover instead
X2-handover
X2-handover
 Key features
 The handover is directly performed between
two eNodeBs
 make the preparation phase quick
 Data forwarding may be operated per bearer
in order to minimize data loss
 The MME is only informed at the end of the
handover procedure
 once the handover is successful
 in order to trigger the path switch

 The release of resources at the source side is


directly triggered from the target eNodeB
Seamless Handover
 The source eNodeB selects the seamless
handover mode
 using ‘HANDOVER REQUEST’ message to
establish a GTP tunnel
 operate the downlink data forwarding
 If the target eNodeB accepts ‘HANDOVER
REQUEST’ message
 ‘HANDOVER REQUEST ACK’ message
 Indicating the the tunnel endpoint
 where the forwarded data is expected to be received
 The tunnel endpoint may be different from the one
of the new bearer established over the target S1
Seamless Handover
 Upon
reception of the ‘HANDOVER
REQUEST ACK’ message, the source
eNodeB can
 start forwarding the data freshly arriving over the
source S1 path
 in parallel with sending the handover trigger to the
UE over the radio interface
 forwarded data is thus available at the target eNodeB to
be delivered to the UE as early as possible
 When in-sequence delivery of packets is
required
 the target eNodeB is assumed to deliver first the
packets forwarded over X2
Seamless Handover

 some ‘special GTP packets’ to indicate the


end of the forwarding
 the S-GW has inserted over the source S1 path
just before switching this S1 path
 these are then forwarded by the source eNodeB
over X2 like any other regular packets
Lossless Handover
 The lossless mode for a given bearer
 The source eNodeB will additionally forward
over X2
 user plane downlink packets
 has PDCP processed but are still buffered locally
 have not yet been delivered and acknowledged by
the UE
 together with their assigned PDCP SN included in a GTP
extension header field
 sent over X2 prior to the freshly arriving packets from the
source S1 path
Lossless Handover
 the target eNodeB must ensure that
 all the packets are delivered in sequence at the
target side

You might also like