Target eNodeB Interfaces (S1 Handover)

LTE Mobile eNodeB Core Network EventStudio System Designer 6

Network
UE Target eNodeB MME SGW 17-Feb-14 17:24 (Page 1)
This sequence diagram was generated with EventStudio Sytem Designer - http://www.EventHelix.com/EventStudio/

UE is handed over using an S1 handover if the X2 interface is not available between the source and target eNodeB.

Handover preparation
S1AP Handover Request The MME sends Handover Request message to the target
s1ap s1ap eNodeB. This message creates the UE context in the target
eNodeB, including information about the bearers, and the
EPS Bearers to security context. For each EPS Bearer, the "Bearers to Setup"
Setup,
AMBR, includes Serving GW address and uplink TEID for user plane,
S1A P Cause, and EPS Bearer QoS. If the direct forwarding flag indicates
Source to Target unavailability of direct forwarding and the MME knows that
transparent there is no indirect data forwarding connectivity between source
container,
Handove r and target, the Bearers to Setup shall include "Data forwarding
Restriction List, not possible" indication for each EPS bearer. Handover
RAN assistance Restriction List is sent if available in the MME.
data

Generate AS keys from KeNB

(KeNB = KeNB*)

Perform admission control the Check if resources are available at the target eNodeB to accept
E-RABs in the message this session.
Create DRB ID (Uplink / Assign Dedicated Radio Bearer ids for Uplink and Downlink.
Downlink)

RRC: Reserve downlink and The Target eNodeB allocates radio resources for the UE that
uplink radio resources for the will be handed in.
session

Allocate RACH Preamble The Target eNodeB allocates a RACH preamble to the UE. The
UE will use this preamble to send a contention free RACH.
Allocate C-RNTI A new C-RNTI is assigned to the UE.
RRC: Prepare the Handover This message includes the RACH preamble that needs to be
Command message (RRC sent to the terminal. This message includes information about
Connection Reconfiguration the assigned radio resources.
Request)

S1AP Handover Request Acknowledge The Target eNodeB responds back to the MME with a
s1ap s1ap Handover Request Acknowledge message. This message
carries the Handover Command message (RRC Connection
EPS Bearer Setup Reconfiguration Request) in a transparent container. The "EPS
list,
EPS Bearers failed Bearer Setup list" includes a list of addresses and TEIDs
to setup list, allocated at the target eNodeB for downlink traffic on S1 U
Transparent reference point (one TEID per bearer) and addresses and
container = TEIDs for receiving forwarded data if necessary.
Handover
Command

Buffering downlink data At this point, the target eNodeB is ready to buffer downlink data
that will be received during the handover.

Handover execution

Copying data from source eNodeB to target eNodeB

Downlink Data The downlink data is transported from the Source eNodeB to
gtp gtp the Target eNodeB via the just established indirect tunnel.

Buffer data received from the The data cannot be sent to the target until the RRC
Source eNodeB reconfiguration is completed.
RRC reconfiguration
 Target eNodeB Interfaces (S1 Handover)
LTE Mobile eNodeB Core Network EventStudio System Designer 6
Network
UE Target eNodeB MME SGW 17-Feb-14 17:24 (Page 2)
Synchronizing with target cell
RACH Preamble UE uses the preamble assigned in the handover command to
rrc rrc send a RACH to the target eNodeB.

Random Access Response The target eNodeB accepts the request and responds back with
rrc rrc a timing adjustment and an uplink resource grant.
Timing Advance,
Target C-RNTI,
Uplink grant

RRC Connection Reconfiguration Complete The UE uses the assigned resources to transmit the Handover
rrc rrc Confirm message (RRC Connection Reconfiguration
Complete).
Target C-RNTI

AS layer security procedure

RRC-Connected The UE is not connected to the Target eNodeB. Thus it

transitions to the RRC-Connected state.

RRC Handover Confirm After the UE has successfully synchronized to the target cell, it
rrc rrc sends a Handover Confirm message to the target eNodeB.
Downlink packets forwarded from the source eNodeB can be
sent to the UE. Also, uplink packets can be sent from the UE,
which are forwarded to the target Serving GW and on to the
PDN GW.
Target eNodeB Forwarding
buffered downlink data to the UE
Downlink Data The buffered downlink data is sent to the terminal.
rlc rlc

Uplink data is now being received at the target eNodeB

Uplink Data Uplink data is now being received from the terminal.
rlc rlc

Uplink Data The uplink data is now flowing directly from the Target eNodeB
gtp gtp to the SGW.

S1AP Handover Notify The target eNodeB sends a Handover Notify message to the
s1ap s1ap target MME.
TAI+ECGI,
Local Home
Network ID

Downlink data flows directly to the target eNodeB

Downlink data SGW has switched the path to the Target eNodeB, so the
gtp gtp downlink data is directly delivered to the target eNodeB.

Downlink data
rlc rlc
Target eNodeB Interfaces (S1 Handover)
LTE Mobile eNodeB Core Network EventStudio System Designer 6
Network
UE Target eNodeB MME SGW 17-Feb-14 17:24 (Page 3)

Release resources on Source eNodeB

Tracking Area Update (Click to Tracking Area Update Sequence Diagram) The UE may perform a tracing area update due to cell change.

This sequence diagram was generated with EventStudio Sytem Designer - http://www.EventHelix.com/EventStudio/

Learn more about LTE at: http://www.eventhelix.com/lte/