Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Interface

X2

X2 Interface

Interface →

X2 is the direct logical interface between two neighboring base stations (eNodeBs in LTE or gNBs in NR) that enables critical functions like handover preparation and interference coordination without involving the core network.

Introduced
Rel-8
Where
Radio Access Network › E-UTRAN (LTE)
Specifications
4 specs
X2 Description Purpose What changed Family Neighbours Detected Changes Specifications

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.

What changed in its specifications

The latest release-to-release comparison of specifications that define X2. Each summary describes the whole specification, not only this term.

TS 29.274Rel-18 → Rel-19

Rel-19 adds S-NSSAI text to the Create Session Request and Response procedures for edge computing phase 3. It also clarifies eMLPP priority values and GTP priority handling for MPS messaging and emergency traffic.

Full comparison in TS 29.274 →
TS 36.300Rel-18 → Rel-19

Rel-19 added NTN IoT Phase 3 for LTE, covering regenerative payload S1 removal, Msg3 early data transmission, and ETWS/CMAS for NB-IoT NTN. It also added inter-RAT mobility from E-UTRAN terrestrial network to NR NTN, plus NR NTN feeder link switchover via handover.

Full comparison in TS 36.300 →

Technology family

RAN interfaces · Radio Access Network

  1. Phase 1 A interface, Abis
  2. R99 Iu, Iu-BC, Iu-CS, Iu-PS, Iub, Iur, NBAP, Uu
  3. Rel-5 Iur-g
  4. Rel-8 S1, S1-MME, S1-U, S1AP, X2
  5. Rel-15 E1, E1AP, F1, F1-C, F1-U, F1AP, NG, NG-C, NG-U, NGAP, Xn, Xn-C, Xn-U
  • X2 counterpart in another generation: Xn
    “The interface allowing to interconnect NG-RAN nodes with each other is referred to as the Xn interface.” TS 38.420
  • X2 counterpart in another generation: Iur
    “The interface allowing to interconnect eNBs with each other is referred to as the X2 interface.” TS 36.420

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 1 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-8 introduced

The X2 interface between eNodeBs is specified for the first time in Rel-8, with user plane and control plane protocol structure in TS 36.300 and TS 36.420.

Defining Specifications

3GPP specifications that define or reference X2, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 29.274 vk00 GTPv2-C Control Plane Protocol Rel-20 read
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 36.420 vj00 X2 Interface Introduction for E-UTRAN Rel-19 read
TS 36.425 vj00 X2 User Plane Protocol for Dual Connectivity Rel-19 read