Description
E1AP is the Application Layer protocol defined by 3GPP for the E1 interface, a key internal interface within the Next Generation Radio Access Network (NG-RAN) introduced in the 5G system. The E1 interface connects the Central Unit (CU) and the Distributed Unit (DU) in a disaggregated gNB (5G base station) or ng-eNB (upgraded LTE base station for 5G core). This functional split, specifically the CU-DU split, is a fundamental architectural shift in 5G RAN, allowing the separation of time-critical lower layer functions (DU) from less time-sensitive higher layer functions (CU). The E1AP protocol operates on top of a transport network layer (using SCTP/IP) and is responsible for all control plane signaling between these two logical nodes.
The protocol defines a set of Elementary Procedures (EPs) that govern the interaction between the CU and DU. These procedures are categorized as Class 1 (requiring a response) and Class 2 (not requiring a response). Key functions managed by E1AP include Bearer Context Management (setup, modification, release), DU and CU configuration updates, mobility management for connected mode UEs, and the transfer of RRC messages between the CU-CP (Control Plane part of the CU) and the UE via the DU. When a UE connects, the CU-CP uses E1AP to establish a bearer context in the DU, configuring the necessary radio resources. The DU handles the real-time scheduling and physical layer processing, while the CU manages radio resource control, security, and connectivity to the core network.
From a procedural perspective, E1AP messages are carried in E1AP PDUs (Protocol Data Units). The interface supports both F1-C and F1-U reference points termination at the DU, meaning the DU communicates with the CU-CP via E1 and with the CU-UP (User Plane part of the CU) via another interface. E1AP is designed to be future-proof and flexible, supporting different functional split options (though Split Option 2, as defined in 3GPP, is the most common for E1). It enables centralized coordination of multiple DUs by a single CU, facilitating advanced features like coordinated multipoint (CoMP), load balancing, and efficient resource pooling. This separation is crucial for enabling cloud-native RAN deployments, network slicing, and flexible scaling of capacity and coverage independently.
Purpose & Motivation
E1AP and the E1 interface were created to address the need for a more flexible, scalable, and efficient RAN architecture for 5G, moving beyond the monolithic base station design of 4G LTE. The traditional eNB integrated all radio protocol layers, which limited deployment flexibility and made it difficult to centralize intelligence for features like advanced coordination or to leverage cloud computing resources. The purpose of the CU-DU split, facilitated by E1AP, is to disaggregate the base station, allowing network functions to be placed optimally in the network based on their latency and processing requirements.
This disaggregation solves several key problems. It enables Centralized RAN (C-RAN) deployments where the CU can be located in a regional data center, serving many remote DUs. This centralization allows for more efficient resource pooling, reduced site footprint and costs at cell towers, and simplified implementation of multi-cell coordination techniques. Furthermore, it aligns with the broader 5G design principles of network softwarization and cloud-native design, allowing the CU to be implemented as virtualized network functions (VNFs) or cloud-native functions (CNFs) on commercial off-the-shelf hardware. E1AP provides the standardized control protocol to make this split operational and interoperable between different vendors' CU and DU equipment.
Historically, prior to 3GPP standardization, proprietary splits and interfaces were used in some pre-5G C-RAN implementations, leading to vendor lock-in. The standardization of E1AP in Release 15 was motivated by the industry's desire for multi-vendor interoperability and a clear, open interface. It allows operators to mix and match CUs from one vendor with DUs from another, fostering competition and innovation. The E1 interface, with E1AP as its brain, is thus a cornerstone of the Open RAN (O-RAN) movement and is essential for realizing the full economic and performance benefits of a virtualized, disaggregated 5G RAN.
Technology family
RAN interfaces · Radio Access Network
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.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 4 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.
E1AP is specified for the first time in Rel-15 as the signalling protocol between gNB-CU-CP and gNB-CU-UP over the E1 interface, with its services, procedures and transfer syntax.
- “The E1 Application Protocol (E1AP) supports the functions of E1 interface by signalling procedures defined in the present document.” TS 38.463 v15.13.0
- “E1AP provides the signalling service between the gNB-CU-CP and the gNB-CU-UP” TS 38.463 v15.13.0
- “E1AP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax” TS 38.463 v15.13.0
In Rel-16 E1AP gained trace function support, alternative QoS profiles, and handling for unmapped DL QoS flows, plus corrections for IPsec setup, duplication and IAB QoS mapping.
In Rel-17 the E1AP specification moved from TS 38.463 to TS 37.483, extended to eNB-CP/eNB-UP and ng-eNB nodes, and gained MBS-associated signalling and services.
- “between the gNB-CU-CP and the gNB-CU-UP, or between the eNB-CP and the eNB-UP, or between the ng-eNB-CU-CP and the ng-eNB-CU-UP” TS 37.483 v17.11.0
- “The MBS-associated logical E1-connection uses the identities GNB-CU-CP MBS E1AP ID and GNB-CU-UP MBS E1AP ID” TS 37.483 v17.11.0
- E1AP specification transfer to TS 37.483 TS 38.463CR0665
E1AP was corrected in Rel-19: message-level criticality of procedures, AI/ML for NG-RAN support, and UE performance metrics were fixed, and Error Indication handling for MBS-associated signalling was specified.
- Correction of message level criticality of E1AP procedures TS 37.483CR0144
- Correction to E1AP for UE performance metrics TS 37.483CR0185
- “In case the Error Indication procedure is triggered by utilising MBS associated signalling the gNB-CU-CP MBS E1AP ID IE and gNB-CU-UP MBS E1AP ID IE shall be included” TS 37.483 v19.4.0
Defining Specifications
3GPP specifications that define or reference E1AP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 37.480 vj10 | E1 Interface General Aspects and Principles | Rel-19 read |
| TS 38.460 vj00 | E1 Interface General Aspects and Principles | Rel-19 read |