Description
The Evolved Node B (eNB) is the central network element of the Long-Term Evolution (LTE) Radio Access Network, known as E-UTRAN. It is a sophisticated base station that performs the majority of the radio network controller (RNC) functions that were distributed across separate nodes in previous 3G UMTS networks, leading to a flatter, more efficient architecture. The eNB is responsible for the complete stack of Layer 1 (Physical), Layer 2 (MAC, RLC, PDCP), and Layer 3 (RRC) protocols towards the User Equipment (UE). It manages the radio interface, including modulation, coding, scheduling of uplink and downlink resources, and handover execution.
Architecturally, an eNB serves one or multiple cells. It connects to UEs via the LTE-Uu radio interface and connects to other eNBs via the X2 interface for direct coordination, primarily to enable seamless handovers and to exchange load and interference information. The connection to the Evolved Packet Core (EPC) is established via the S1 interface, split into S1-MME for control plane signaling to the MME and S1-U for user plane data tunneling to the Serving Gateway (S-GW). This separation allows for scalable and flexible network deployment.
Key internal components of the eNB functionality include the Radio Resource Control (RRC) entity for connection establishment, mobility, and security activation; the Packet Data Convergence Protocol (PDCP) for header compression, ciphering, and integrity protection; the Radio Link Control (RLC) for segmentation and ARQ; and the Medium Access Control (MAC) for scheduling, hybrid ARQ, and multiplexing logical channels. The eNB's role is critical in ensuring Quality of Service (QoS) by enforcing QoS policies received from the core network and managing radio bearers accordingly. In 5G Non-Standalone (NSA) deployments, the eNB (often referred to as an ng-eNB when connecting to a 5GC) works in tandem with a 5G NR gNB, with the LTE side providing the anchor for control plane connectivity.
Purpose & Motivation
The eNB was created as part of the 3GPP's LTE standard to address the limitations of the 3G UMTS network architecture, which utilized a separate Radio Network Controller (RNC) node. The distributed RNC-Node B architecture introduced latency in radio resource decisions and created a potential single point of failure and congestion. The primary motivation was to develop a flatter, all-IP architecture that would reduce latency, increase user data rates, and simplify network deployment and management.
By integrating the RNC functions into the base station, the eNB enables faster, localized decision-making for radio resource management and handovers. This architectural shift was essential to meet the key performance targets of LTE, such as sub-10ms user plane latency and peak data rates exceeding 100 Mbps. The eNB's direct interface (S1) to the core network also streamlined the data path, improving efficiency for packet-switched services. Its introduction marked a fundamental evolution from the circuit-switched oriented architecture of 2G/3G towards a packet-optimized system designed for the mobile broadband era.
What changed in its specifications
The latest release-to-release comparison of specifications that define eNB. Each summary describes the whole specification, not only this term.
Rel-19 adds NTN-for-IoT Phase 3 and inter-RAT mobility from E-UTRAN to NR NTN, plus LTE-based 5G Broadcast Phase 2 changes. It also adds IMS disaster-roaming access barring, NTN-for-NR Phase 3 fields, and NR RRM Phase 5 items.
Full comparison in TS 36.331 →Added UE test loop mode F for counting received MBMS packets on SC-MTCH in SC-PTM. Added handling of stored MBS positioning information reset and new positioning technology identifiers.
Full comparison in TS 36.509 →Evolution Lineage
- Evolved from: RNC (3G→4G)
- Network evolution overview →
Technology family
Base stations and RAN nodes · Radio Access Network
- Phase 1 BSC, BSS, BTS
- R99 Node B, RNC, RNS
- Rel-8 eNB, HeNB, HNB, HNB-GW
- Rel-10 DeNB, HeNB-GW, RN
- Rel-15 en-gNB, gNB, gNB-CU, gNB-CU-CP, gNB-CU-UP, gNB-DU, ng-eNB
- Rel-16 IAB-donor, IAB-DU, IAB-MT, IAB-node
- Rel-18 Mobile IAB-node
- eNB counterpart in another generation: Node B
“The Evolved UTRAN (E-UTRAN) consists of eNBs, providing the E-UTRA user plane (PDCP/RLC/MAC/PHY) and control plane (RRC) protocol terminations towards the UE.” TS 23.002
- eNB extended by HeNB
“The Home eNodeB Subsystem (HeNS) consists of a Home eNodeB (HeNB), optionally a Home eNodeB Gateway (HeNB-GW) and optionally a Local GW (L-GW).” TS 23.002
- eNB extended by ng-eNB
“The paging optimisation in clause 23.13 is also applicable, where AMF shall be considered instead of MME and ng-eNB shall be considered instead of eNB.” TS 36.300
- eNB counterpart in another generation: gNB (not stated verbatim in the specifications)
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 13 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.
The eNB's behaviour is specified for the first time in S1AP (E-RAB setup), X2AP (handover preparation) and RRC procedures, together with eNB performance requirements in TS 36.104.
- “For each E-RAB and based on the E-RAB level QoS parameters IE the eNB shall establish a Data Radio Bearer” TS 36.413 v8.10.0
- “The source eNB initiates the procedure by sending the HANDOVER REQUEST message to the target eNB.” TS 36.423 v8.9.0
- eNB performance requirements for UL timing adjustment TS 36.104CR17
The eNB's behaviour was extended in Rel-9, adding full configuration handover for earlier eNB releases, EIA0 handling, CS fallback and registered LAI handling, CSG membership handling, and mobility-target restriction handling.
- “the target eNB should use the full configuration option to reconfigure the UE for Handover and Re-establishment.” TS 36.331 v9.18.0
- “the eNB should initiate actions to ensure that the UE is no longer served by the CSG cell” TS 36.413 v9.10.0
- Introduction of Full Configuration Handover for handling earlier eNB releases TS 36.331CR0383
eNB behaviour changed in Rel-10: it uses the Correlation ID for LIPA with an L-GW, handles MDT and CSG membership checks, and applies ABS interference-coordination information received over X2.
- “If the Correlation ID IE is included in the E-RAB SETUP REQUEST message towards the eNB with L-GW function for LIPA operation” TS 36.413 v10.9.0
- “the eNB shall reject the procedure using the INITIAL CONTEXT SETUP FAILURE message.” TS 36.413 v10.9.0
- “The receiving eNB may take such information into consideration when scheduling UEs.” TS 36.423 v10.7.0
eNB behaviour in S1AP/X2AP procedures was extended, e.g. new UE Radio Capability Match handling, HO Cause Value in UE History Information, and Management Based MDT PLMN List handling.
- “the eNB shall use it to determine the value of the Voice Support Match Indicator IE to be included in the UE RADIO CAPABILITY MATCH RESPONSE message.” TS 36.413 v11.8.0
- “the source eNB shall, if supported, include the HO Cause Value IE in the UE History Information IE of the HANDOVER REQUIRED message.” TS 36.413 v11.8.0
- “The source eNB shall, if supported and available in the UE context, include the Management Based MDT Allowed IE and the Management Based MDT PLMN List IE” TS 36.423 v11.9.0
In Rel-12 the eNB gained new behaviour: SIPTO@LN handling in E-RAB setup and initial context setup, Masked IMEISV and Expected UE Behaviour use, ProSe authorization, and NAICS/CoMP load information handling.
- “the eNB shall use this information for SIPTO@LN operation for the concerned E-RAB.” TS 36.413 v12.7.0
- “the eNB shall, if supported, store this information and may use it to determine the RRC connection time.” TS 36.413 v12.7.0
- “the receiving eNB may use it for the configuration of DL interference mitigation assistance information towards the UE.” TS 36.423 v12.9.0
The eNB gained new S1AP/X2AP behaviour in Rel-13, including UE context suspend/resume procedures, non-IP bearer handling without header compression, and CIoT optimisation support.
- “The eNB initiates the procedure by sending the UE CONTEXT SUSPEND REQUEST message to the MME.” TS 36.413 v13.8.0
- “then the eNB shall not perform header compression for the concerned E-RAB.” TS 36.413 v13.8.0
- “The new eNB initiates the procedure by sending the RETRIEVE UE CONTEXT REQUEST message to the old eNB.” TS 36.423 v13.8.0
In Rel-14 the eNB gained new behaviours: it stores Enhanced Coverage Restricted and CE-Mode-B Restricted information, handles V2X authorization and sidelink AMBR, supports CP relocation, and uses new eNB ID types.
- “the eNB shall, if supported, update its V2X services authorization information for the UE accordingly.” TS 36.413 v14.9.0
- “The eNB initiates the procedure by sending a eNB CP RELOCATION INDICATION message to the MME.” TS 36.413 v14.9.0
- Introduction of New types of eNB ID TS 36.413CR1502
In Rel-15 the eNB gained new S1AP/X2AP behaviour: storing NR UE Security Capabilities and Aerial UE information, reporting EN-DC PSCell information, and EN-DC X2 removal procedures.
- “If the NR UE Security Capabilities IE is included in the INITIAL CONTEXT SETUP REQUEST message, the eNB shall, if supported, store this information” TS 36.413 v15.11.0
- “If the PSCell Information IE is included in the User Location Information IE, it indicates the UE was configured with EN-DC radio resources at the eNB” TS 36.413 v15.11.0
- “An eNB initiates the procedure by sending the EN-DC X2 REMOVAL REQUEST message to a candidate en-gNB.” TS 36.423 v15.14.0
In Rel-16 the eNB gained new behaviour: conditional handover and DAPS handover handling, Ethernet header compression, UE Radio Capability ID use, and NR V2X sidelink authorization handling.
- “the target eNB shall consider that the request concerns a conditional handover and shall include the Conditional Handover Information Acknowledge IE” TS 36.423 v16.13.0
- “the eNB shall, if supported, take this into account to perform header compression appropriately for the concerned E-RAB” TS 36.413 v16.14.0
- “the target eNB shall consider that the request concerns a DAPS handover for that E-RAB” TS 36.423 v16.13.0
Rel-17 added eNB behaviour for EPS user plane integrity protection (required/preferred/not needed), Security Indication and Security Result handling in S1AP and X2AP, plus EN-DC and conditional handover procedures.
- “if the Integrity Protection Indication IE is set to "required", then the eNB shall, if supported by the eNB and the UE, perform user plane integrity protection” TS 36.413 v17.6.0
- “the target eNB shall, if supported, use it as specified in TS 33.401 [15] and include the Security Result IE” TS 36.413 v17.6.0
- Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution TS 36.401CR0090
eNB gained new behaviour in Rel-18: it may use Coarse UE Location from the MME, sends eNB Early Status Transfer for time-based handover, and applies UP integrity protection policy requirements.
- “If the Coarse UE Location IE is included in the INITIAL CONTEXT SETUP REQUEST message, the eNB may use it as specified in TS 36.300 [14].” TS 36.413 v18.4.0
- “the target eNB may use this information to allocate necessary resources for the incoming handover.” TS 36.413 v18.4.0
- “If the eNB receives UP integrity protection policy from the MME, the eNB shall use the received UP integrity protection policy” TS 33.216 v18.1.0
Rel-19 adds eNB behaviour in S1AP: a new S1 Removal procedure between eNB and MME, Time Reference Distribution Information handling, and UE radio capability retrieval, plus attributes for store-and-forward satellite operation.
- “The purpose of the S1 Removal procedure is to remove the interface between the eNB and the MME in a controlled manner.” TS 36.413 v19.2.0
- “the eNB shall, if supported, store this information in the UE context and use it as defined in TS 23.401 [11].” TS 36.413 v19.2.0
- Add attributes to support Store and Forward Satellite operation for eNB TS 28.658CR0068
TS 33.216 (first appearing in this release's evidence) specifies eNB security assurance behaviour, such as the target eNB selecting AS algorithms by priority and including them in the handover command.
- “The target eNB verifies the algorithms and selects AS algorithms which have the highest priority according to the ordered lists.” TS 33.216 v20.0.0
- “EIA0 is enabled at the eNB.” TS 33.216 v20.0.0
- “The source eNB transfers the ciphering and integrity algorithms used in the source cell to the target eNB in the handover request message.” TS 33.216 v20.0.0
Defining Specifications
3GPP specifications that define or reference eNB, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 36.331 vj40 | E-UTRA Radio Resource Control (RRC) Protocol | Rel-19 read |
| TS 36.509 vi00 | UE Conformance Test Loop Functions | Rel-18 read |
| TS 36.523 vj20 | E-UTRA UE Conformance ICS Proforma | Rel-19 read |
| TS 37.571 vj00 | UE Conformance for Positioning | Rel-19 read |