X2 Interface - LTE

4G - X2 Interface
Schwannden Kuo
NCTU CS
schwannden@gmail.com
X2 Protocol Stack
• X2 control plan • X2 data plan

X2 Protocol Stack
• X2 has exactly the same stack as S1,

simplifying data forwarding operation.
X2 Initiation
X2 initiation sets up the connection between two

eNodeB’s via X2 Interface
X2 Initiation
• X2 manages two functions: load or interference related function and handover related information.
• The two functions are independent of each other.
Uu
UE eNodeB
MME HSS
Mobility  Home 
X-2 Management Subscriber 
Entity Server
S1-MME
Uu S1-U
UE eNodeB S-GW P-GW
User Equipment Evolved NodeB Serving Gateway PDN Gateway
E-UTRAN Core Network (EPC)

X2 Initiation
• A full mesh between all eNodeB’s is not mandated in an E-UTRAN network.
Uu
UE eNodeB
MME HSS
Mobility  Home 
Entity Server
S1-MME
Uu S1-U
UE eNodeB S-GW P-GW

X2 Initiation
• Initialization begins with the identification of a suitable neighbor, either by configuration of ANRF
(Automatic Neighbor Relation Function).
• Once it decides to establish an X2 interface, it establishes a TLN (transport Layer Network)
connection by target’s IP (found via configuration or query over S1 interface).
Uu
UE eNodeB
User Equipment MME HSS
Mobility  Home 
Management Subscriber 
X2 setup request Entity Server
X-2 S1-MME
Uu S1-U
UE eNodeB S-GW P-GW

X2 Initiation
• Informations passed during X2 setup request facilitate automatic self-configuration of the Physical
Cell Identities (PCIs) and RACH self-optimization.
Uu
Information passed in X2 setup request UE eNodeB
Mandatory
1. Physical Cell IDs for the cell it manages MME HSS
2. Frequency Band Mobility  Home 
3. Tracking Area Identity and/or the Management Subscriber 
associated PLMN X2 setup request Entity Server
Optional
1. Neighbor Information X-2 S1-MME
2. Number of Antenna Ports
3. PRACH Configuration
4. MBSFN Subframe Info Uu S1-U
5. CSG ID (mandatory if the eNB is CSG
UE eNodeB S-GW P-GW
Cell or Hybrid Cell)
6. MultibandInfoList

X2 Initiation
• Once the X2 setup procedure has been completed by X2 Setup Response, the X2 interface is
operational.
Uu
UE eNodeB
MME HSS
Mobility  Home 
X2 Setup Response Entity Server
X-2 S1-MME
Uu S1-U
UE eNodeB S-GW P-GW
Evolved NodeB Serving Gateway PDN Gateway

X2 Handover
X2 Handover (HO) handover a UE from one
eNodeB (source eNodeB) to the other (target
eNodeB).
X2 Handover
Recall the normal data flow:
Downlink Data
Uplink Data
Uu
UE eNodeB
MME HSS
Mobility  Home 
Entity Server
S1-MME PDN 
Uu S1-U (PSS, IME)
UE eNodeB S-GW P-GW
User Equipment Evolved NodeB Serving Gateway PDN Gateway Packet Data Network 
(packet Switch Stream,
IP Multimedia System)

Decision Request Preparation Path Switch Complete
X2 Handover
• The network sets the measurement thresholds for sending measurement reports.
eNodeB
MME HSS
Mobility  Home 
Entity Server
X-2
RRC
Meas
UE urem
ent C
ontro
S1-MME
l
RRC
Meas
urem
S-GW P-GW
ent R
e p o rt eNodeB S1-U Serving Gateway PDN Gateway
Uu
Evolved NodeB

X2 Handover
• Neighboring cell signal quality is now better than the serving cell.
• The RRC uses the latest measurement to decide if a handover is needed to another cell. The target
cell is selected. The eNodeB for the target cell is identified.
eNodeB
MME HSS
UE Mobility  Home 
R
R
C
Entity Server
R
M
R
ea
C
X-2
su
M
re
ea
m
su
en
re
S1-MME
tC
m
en
on
S-GW P-GW
tR
tro
ep
l
or
eNodeB
t
S1-U Serving Gateway PDN Gateway

Uu
Evolved NodeB

X2 Handover
• The Source eNodeB initiates the handover with the Handover Request message, including
information about active E-RABs. Some UE historical information (UE/Cell RRM related information,
list of visited cells) is passed in Handover Request message.
eNodeB
MME HSS
Entity Server
X2AP Handover Request
S1-MME
S-GW P-GW
Uu eNodeB S1-U Serving Gateway PDN Gateway
Evolved NodeB

X2 Handover
• GTP connect for the uplink side is established between the Target eNodeB and the serving SGW.
eNodeB
Up
link
MME HSS
UE S1
Be
Mobility  Home 
are Management Subscriber 
rE Entity Server
sta
blis
hm
en
S1-MME t
S-GW P-GW
Evolved NodeB

X2 Handover
• Meanwhile Target eNodeB allocates resources, assigns RACH preamble and new C-RNTI to UE.
eNodeB
Up
link
MME HSS
UE S1
Be
Mobility  Home 
are Management Subscriber 
rE Entity Server
sta
blis
hm
en
S1-MME t
S-GW P-GW
Evolved NodeB

X2 Handover
• The Target eNodeB responds back to the source eNodeB with a Handover Request Acknowledge
message. This message carries the Handover Command message (RRC Connection
Reconfiguration Request) in a transparent container (including the RACH preamble and C-RNTI
generated previously).
eNodeB
MME HSS
Entity Server
X2AP Handover Request Ack.

S1-MME
S-GW P-GW
Evolved NodeB

X2 Handover
• An X2 GTP connection is established between the Source and the Target eNodeBs. This channel
will carry the user data during the handover.
• UE is ready to buffer downlink data from this point on.
eNodeB
MME HSS
X2 TEID
Entity Server
S1-MME
X2 TEID S-GW P-GW
Evolved NodeB

X2 Handover
• Source eNodeB initiates HO commands to UE in RRC Reconfiguration Request. The messages
contain the new RACH preamble and C-RNTI of UE.
• PDCP Sequence Number (SN) are sent from source eNodeB to target eNodeB.
eNodeB
MME HSS
SN
Tra
Entity Server
ns
RR qu
fer
Re
C es
Re t
Sta
co
tu
n
fig
S-GW P-GW
s
ur
at
eNodeB
io
Uu S1-U Serving Gateway PDN Gateway

n
Evolved NodeB

X2 Handover
Data flow during handover preparation:
Downlink Data
Uplink Data
eNodeB
Downlink data MME HSS
is buffered
Entity Server
S-GW P-GW
eNodeB S1-U Serving Gateway PDN Gateway
Evolved NodeB

X2 Handover
• During SN Transfer Status, source eNodeB freeze its
transmitter/receiver status.
• Mean while UE is switching to target eNodeB.
Detach from source eNodeB eNodeB

MME HSS
SN
UE Uu Mobility  Home 
Tra
Entity Server
ns
fer
Sta
tu
S-GW P-GW
s
UE status eNodeB S1-U Serving Gateway PDN Gateway
RRC IDLE Evolved NodeB

X2 Handover
RACH Preamble eNodeB

MME HSS
SN
Tra
Entity Server
ns
fer
Sta
tu
S-GW P-GW
s

X2 Handover
Random Access Response eNodeB

MME HSS
SN
Tra
Entity Server
ns
fer
Sta
tu
S-GW P-GW
s

X2 Handover
RRC Connection
eNodeB
Reconfiguration Complete
MME HSS
SN
Tra
Entity Server
ns
fer
Sta
tu
S-GW P-GW
s
RRC CONNECTED Evolved NodeB

X2 Handover
Data flow during handover execution (after ho preparation):
Downlink Data
Uplink Data
Buffered downlink
data is delivered Uu eNodeB
MME HSS
Entity Server
S-GW P-GW
Evolved NodeB

X2 Handover
• Path switch
S1AP Path Switch Req.

eNodeB
MME HSS
Entity Server
S-GW P-GW

X2 Handover
• Path switch

eNodeB
MME HSS
Entity Server
Modify Bearer Req . 
(EPS Bearer ID, S1 TEID, ECGI, TAI)
S-GW P-GW

X2 Handover
• Path switch

eNodeB
MME HSS
Entity Server
S-GW P-GW
(EPS Bearer ID, ECGI, TAI)

X2 Handover
• Path switch

eNodeB
MME HSS
Entity Server
S-GW P-GW
RRC CONNECTED Evolved NodeB Modify Bearer Res.

X2 Handover
• Path switch

eNodeB
MME HSS
Entity Server
Modify Bearer Res.
S-GW P-GW
RRC CONNECTED Evolved NodeB Modify Bearer Res.

X2 Handover
• When path switch is complete, downlink data is sent directly from S-GW to target eNodeB. And an
end marker is inserted from S-GW to source eNodeB indicate the last frame from old path.
S1AP Path Switch Res.

eNodeB
MME HSS
Do
UE Uu wn Mobility  Home 
link
End
da
ta Entity Server
Ma
rke
r
Ma r ker S-GW P-GW

End

X2 Handover
Data flow after hand over (after path switch complete):
Downlink Data
Uplink Data
Buffered downlink
data is delivered Uu eNodeB
MME HSS
Entity Server
S-GW P-GW
Evolved NodeB

X2 Handover
• The Source eNodeB initiates the handover with the Handover
Request message, including information about active E-RABs.
X2AP Path Switch Req. Ack.

eNodeB
MME HSS
Entity Server
X1AP UE Context Release

S1-MME
S-GW P-GW
Evolved NodeB

X2 HO modes
1. Seamless HO
2. Lossless HO
3. Selective Retransmission
4. Multiple Preparation
• Mobility Robustness Handling (more in later presentation)
• Mobility towards Home eNodeBs via X2 (more in later

presentation)
X2 Feature on HO
• Seamless or lost less mode are set during X2AP
HO Req., and acknowledged by the corresponding
response. The mode is set on a per EPS bearer
basis.
X2 Feature on HO
• Selective Retransmission: Do not retransmit
1. Downlink packets already received by UE before

handover.
2. Uplink packets already received by source

eNodeB.
X2 Feature on HO
• Multiple Preparation
• Trigger handover preparation to  

multiple eNobeB's concurrently.
• Note the source receive only  

one RELEASE RESOURCE  
from selected   http://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&ved=0CAcQjRw&url=http%3A%2F%2Fwww.understandingrelationships.com%2Fdating-
multiple-women%2F10254&ei=8jkFVfv5DIzc8AXAuIHwAg&bvm=bv.88198703,d.dGc&psig=AFQjCNGPJ7XPg-HlhqlDQho2qLs8iXARsQ&ust=1426492166316130
target eNodeB.  
And is recommended to send cancel procedure to
unselected eNodeB’s.
X2 Management
X2 Load and Interference Management
MME MME
X2 Management
• Interference Management: Frequency domain and
time domain interference.
• Informations are exchanged in the order of tens of

milliseconds to optimize RRM process.
X2 Management
• Load Balancing: X2 facilitates the exchange of load
information.
• In Release 10, partial reporting is allowed per cell

and per measurement. Therefore, if a serving
eNodeB does not support some measurements, it
will still report the other measurements that it does
support.
References
1. LTE: the UMTS long term evolution. New York: John Wiley & Sons, 2009.
2. LTE X2 handover sequence diagram: https://www.eventhelix.com/lte/

handover/x2/lte-x2-handover-sequence-diagram.htm#.VQOlCELfK-I
3. TE X2 Handover Messaging: http://www.eventhelix.com/lte/handover/

LTE-X2-Handover-Messaging.pdf
4. summary of LTE Identifiers: http://www.nmcgroups.com/en/expertise/lte/

identifiers.asp
5. Random Access Procedure in LTE: http://4g-lte-world.blogspot.tw/

2013/04/random-access-procedure-rach-in-lte.html
6. 4G introduction: http://www.slideshare.net/schwannden/4g-intriduction

X2 Interface - LTE

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

X2 Interface - LTE

Загружено:

Авторское право:

Доступные форматы

4G - X2 Interface

• X2 control plan • X2 data plan

• X2 has exactly the same stack as S1,

X2 initiation sets up the connection between two

E-UTRAN Core Network (EPC)

E-UTRAN Core Network (EPC)

E-UTRAN Core Network (EPC)

E-UTRAN Core Network (EPC)

E-UTRAN Core Network (EPC)

E-UTRAN Core Network (EPC)

E-UTRAN Core Network (EPC)

S1-U Serving Gateway PDN Gateway

E-UTRAN Core Network (EPC)

E-UTRAN Core Network (EPC)

E-UTRAN Core Network (EPC)

E-UTRAN Core Network (EPC)

X2AP Handover Request Ack.

E-UTRAN Core Network (EPC)

E-UTRAN Core Network (EPC)

Uu S1-U Serving Gateway PDN Gateway

E-UTRAN Core Network (EPC)

E-UTRAN Core Network (EPC)

Detach from source eNodeB eNodeB

UE status eNodeB S1-U Serving Gateway PDN Gateway

RRC IDLE Evolved NodeB

E-UTRAN Core Network (EPC)

RACH Preamble eNodeB

UE status eNodeB S1-U Serving Gateway PDN Gateway

RRC IDLE Evolved NodeB

E-UTRAN Core Network (EPC)

Random Access Response eNodeB

UE status eNodeB S1-U Serving Gateway PDN Gateway

RRC IDLE Evolved NodeB

E-UTRAN Core Network (EPC)

UE status eNodeB S1-U Serving Gateway PDN Gateway

RRC CONNECTED Evolved NodeB

E-UTRAN Core Network (EPC)

E-UTRAN Core Network (EPC)

S1AP Path Switch Req.

RRC CONNECTED Evolved NodeB

E-UTRAN Core Network (EPC)

S1AP Path Switch Req.

RRC CONNECTED Evolved NodeB

E-UTRAN Core Network (EPC)

S1AP Path Switch Req.

E-UTRAN Core Network (EPC)

S1AP Path Switch Req.

RRC CONNECTED Evolved NodeB Modify Bearer Res.

E-UTRAN Core Network (EPC)

S1AP Path Switch Req.

Modify Bearer Res.

RRC CONNECTED Evolved NodeB Modify Bearer Res.

E-UTRAN Core Network (EPC)

S1AP Path Switch Res.

Ma r ker S-GW P-GW

RRC CONNECTED Evolved NodeB

E-UTRAN Core Network (EPC)

E-UTRAN Core Network (EPC)

X2AP Path Switch Req. Ack.

X1AP UE Context Release

E-UTRAN Core Network (EPC)

• Mobility Robustness Handling (more in later presentation)

• Mobility towards Home eNodeBs via X2 (more in later

1. Downlink packets already received by UE before

• Trigger handover preparation to  

• Note the source receive only  