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

Glossary term · Interface

X2-C

X2-Control Plane

Interface →

X2-C is the control plane interface between two eNodeBs in LTE and 5G NR, enabling direct signaling for functions like handover and load management to reduce latency and core network load.

Introduced
Rel-8
Where
Radio Access Network › E-UTRAN (LTE)
Specifications
5 specs
X2-C Description Purpose What changed Neighbours Specifications

Description

The X2-C interface is a critical component of the LTE and 5G NR Radio Access Network (RAN) architecture, specifically defined for the control plane signaling between two neighboring eNodeBs (in LTE) or gNBs (in 5G NR). It operates over an IP-based transport network, typically using SCTP (Stream Control Transmission Protocol) as its reliable transport layer protocol to ensure ordered and reliable delivery of signaling messages. The interface is a logical, point-to-point link, meaning it is established between specific pairs of base stations that are configured as neighbors, often based on geographical proximity and expected user mobility patterns.

The primary function of X2-C is to facilitate direct communication between base stations without always involving the core network's Mobility Management Entity (MME). This is architecturally significant as it decentralizes certain RAN control functions. Key procedures executed over X2-C include Handover Preparation, where the source eNodeB/gNB communicates with the target to reserve resources and context before instructing the UE to switch; Load Management, involving the exchange of Resource Status Reports (RSR) about radio resource block usage; and Inter-Cell Interference Coordination (ICIC), where eNodeBs exchange overload indicators (OI) and high interference indicators (HII) to coordinate uplink and downlink power and resource allocation at cell edges.

From a protocol perspective, the X2 Application Protocol (X2AP) runs over SCTP. X2AP defines the specific elementary procedures and messages for all the aforementioned functions. The interface setup involves an X2 Setup procedure where neighboring eNodeBs exchange their configuration data, including supported features, cell identities, and tracking area codes. The interface's design is highly scalable; while it is a logical point-to-point link, the mesh of X2 connections in a network is managed by Operations, Administration, and Maintenance (OAM) systems that configure the neighbor relationships. In 5G NR, the Xn-C interface is the direct evolution of X2-C, maintaining similar principles but with enhanced procedures to support new 5G capabilities like network slicing and more advanced dual connectivity scenarios.

Purpose & Motivation

The X2-C interface was created to address key limitations of the earlier 3G UMTS architecture, where the RNC (Radio Network Controller) managed handovers and coordination between NodeBs. In the flat LTE architecture, the eNodeB assumed the RNC's functions, necessitating a direct communication path between them. The primary problem X2-C solves is the reduction of handover latency and signaling load on the core network. Without X2, every inter-eNodeB handover would require signaling to traverse the core network (source eNodeB -> MME -> target eNodeB), introducing significant delay and consuming core network resources.

By enabling a direct control link, X2-C allows for faster, more efficient handovers, which is critical for supporting seamless mobility for high-speed users and real-time services like VoIP. Furthermore, it enables distributed RAN optimization functions. For instance, features like Load Balancing and Interference Coordination require rapid, cell-to-cell exchange of radio conditions, which would be impractical if routed through a central core node. X2-C provides the necessary low-latency, high-reliability signaling channel for these real-time RAN coordination tasks, fundamentally enabling the self-organizing network (SON) concepts that are central to LTE and 5G network automation and optimization.

What changed in its specifications

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

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
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 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-8 Initial

Introduced as the foundational control plane interface for LTE. Defined core procedures for X2 setup, handover preparation and execution, UE context transfer, and error handling. Established SCTP as the transport protocol and defined the basic X2AP protocol structure.

Enhanced mobility robustness with the introduction of Radio Link Failure (RLF) Indication procedures. This allowed a target eNodeB to inform a source eNodeB about a UE's connection failure, improving handover parameter optimization and overall mobility performance.

Extended support for Carrier Aggregation (CA) and enhanced ICIC (eICIC) for heterogeneous networks. Introduced procedures for secondary cell activation/deactivation coordination and the exchange of Almost Blank Subframe (ABS) patterns to protect pico-cell users from macro-cell interference.

Further enhanced CoMP (Coordinated Multi-Point) operations and introduced support for Network Energy Saving (NES). Added procedures for coordinating transmission points and for an eNodeB to signal its intention to enter a power-saving sleep mode to its neighbors.

Introduced enhancements for dual connectivity (DC), defining specific X2-C procedures for bearer split and flow control between a Master eNodeB (MeNB) and a Secondary eNodeB (SeNB). Enhanced small cell mobility and discovery mechanisms.

Further refined dual connectivity and introduced support for License Assisted Access (LAA). Enhanced procedures for SeNB addition, modification, and release, and for coordination in unlicensed spectrum operations.

Enhanced support for further enhanced ICIC (feICIC) and introduced early data transmission for IoT. Continued evolution of features for dense and heterogeneous network deployments.

Marked the transition to 5G NR. While the Xn interface (the 5G equivalent) was fully defined, X2-C procedures were updated to support EN-DC (E-UTRA NR Dual Connectivity), where an LTE eNodeB acts as a master node. Defined detailed X2AP procedures for NR secondary cell group management.

Enhanced support for NR-NR dual connectivity and integrated access and backhaul (IAB). Introduced more sophisticated mobility and resource coordination procedures for advanced 5G deployments, including enhancements for ultra-reliable low-latency communication (URLLC).

Introduced support for non-terrestrial networks (NTN) and enhanced support for sidelink relay. Updated X2 procedures to handle the unique timing and mobility challenges presented by satellite-based access nodes.

Further evolution for advanced network automation, AI/ML-driven RAN optimization, and enhanced support for extended reality (XR) traffic. Continued refinement of dual connectivity and mobility in increasingly complex network topologies.

Ongoing enhancements for network energy efficiency, evolution towards 6G capabilities, and support for novel service requirements. Focus on streamlining inter-RAT and intra-RAT coordination in multi-vendor, cloud-native RAN environments.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TR 25.912 vj00 Evolved UTRA and UTRAN Technical Report Rel-19 read
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 36.302 vj00 E-UTRA Physical Layer Services Rel-19 read
TS 36.420 vj00 X2 Interface Introduction for E-UTRAN Rel-19 read