Description
The X2 interface is a fundamental component of the LTE and NR RAN architecture, enabling decentralized coordination between neighboring base stations (eNodeBs in LTE, gNBs in NR). It is defined as a logical interface, typically implemented over IP transport networks. The interface comprises two main parts: the X2-Control Plane (X2-C) and the X2-User Plane (X2-U). The X2-C uses the X2 Application Protocol (X2AP), defined in TS 36.423 for LTE and TS 38.423 for NR, which runs over SCTP/IP for reliable signaling transport. The X2-U uses the GTP-U protocol (TS 29.281) over UDP/IP for forwarding user data packets during handovers.
Key procedures executed over X2AP include Handover Preparation, where the source base station requests resources from and forwards context to the target base station; Load Indication, for exchanging resource status and traffic load information to assist in load balancing; and Inter-Cell Interference Coordination (ICIC), where eNodeBs exchange overload indicators and high-interference indicators to coordinate scheduling and reduce interference at cell edges. In NR, the Xn interface (the 5G equivalent of X2) supports these and additional functions like dual connectivity setup.
During an X2-based handover, the source node sends a HANDOVER REQUEST message over X2-C. The target node reserves resources and responds. Once the UE connects to the target, the source forwards in-flight user data packets to the target via the X2-U tunnels to prevent data loss. This direct forwarding path is faster than routing data back through the core (S1 interface). The establishment of X2 connections can be automated via the Automatic Neighbor Relation (ANR) function, where a base station discovers neighbors and sets up the X2 interface configuration.
Purpose & Motivation
The X2 interface was introduced in LTE Rel-8 to address limitations of previous 3G UMTS architecture, where NodeBs communicated only through the Radio Network Controller (RNC) via the Iur interface. This centralized coordination could introduce latency and create a single point of failure. The flat LTE architecture eliminated the RNC, distributing its functions to the eNodeBs. The X2 interface was created to restore fast, direct coordination between these distributed nodes.
Its primary purpose is to enable seamless, low-latency handovers (HO). By allowing eNodeBs to communicate directly, handover preparation and execution can occur without involving the core network's MME and S-GW for the control part, significantly reducing handover interruption time. This is critical for supporting mobility and real-time services. Furthermore, X2 facilitates advanced radio resource management techniques like ICIC and enhanced ICIC (eICIC), which are essential for improving spectral efficiency and cell-edge user performance in dense, interference-limited deployments. These capabilities were foundational for LTE's performance claims and are carried forward into 5G NR via the Xn interface.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (20 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-8, normative work from Rel-15.
In Release 15, the X2 interface was enhanced to support EN-DC (E-UTRA-NR Dual Connectivity) operations, including the introduction of an X2 partial reset procedure specific to EN-DC. Furthermore, the specification clarified the list of served cells for X2 connections between an eNB and an en-gNB and provided corrections to the overall list of functions supported on the X2 interface.
- X2 partial reset for EN-DC TS 36.300CR1152
- List of served cells for X2 connection between eNB and en-gNB TS 36.300CR1153
- Correction on list of functions on the X2 interface TS 36.420CR0019
- Setting of DSCP value for priority services on a GTPv2-C Interface TS 29.274CR1837
- Extending the scope of the specification to cover the N26 interface TS 29.274CR1852
- GTP-C tunnel per UE over the N26 interface TS 29.274CR1853
+ 11 more changes
In Release 16, a key update for the X2 interface function was the removal of the requirement for exchanging the complete cell list over X2, as indicated by the Change Request title. This modification streamlined the X2 interface setup and management procedures between eNodeBs. The specific technical implementation details for this change, however, are not described within the provided grounding context.
- TS36.300 Removal of Requirement for Exchanging Complete Cell List over X2 TS 36.300CR1257
In Release 17, the X2 interface function was enhanced to support the transfer of Inter-system SON Configuration over the N26 interface, as indicated in the Change Request titles. The technical grounding confirms GTPv2-C is used on the N26 interface, where there shall be only one pair of TEID-Cs per UE, and it specifies procedures like the Forward Relocation Request message over this interface. Furthermore, a new Interface Type, N19mb, was introduced for the F-TEID to facilitate these new capabilities.
Explore further
Broader topics and technologies where X2 plays a role.
Defining Specifications
3GPP specifications that define or reference X2, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 29.274 vj50 | GTPv2-C Control Plane Protocol Specification | Rel-19 |
| TS 36.300 vj00 | E-UTRAN Radio Interface Protocol Architecture Overview | Rel-19 |
| TS 36.420 vj00 | X2 Interface Introduction for E-UTRAN | Rel-19 |
| TS 36.425 vj00 | X2 User Plane Protocol for Dual Connectivity | Rel-19 |