Description
The en-gNB is a logical radio access network node introduced in 3GPP Release 15 to enable the first phase of 5G deployment, known as Non-Standalone (NSA) architecture option 3/3a/3x. In this architecture, the en-gNB provides New Radio (NR) user plane and control plane protocol terminations towards the User Equipment (UE) while acting as a Secondary Node (SN) within an E-UTRA-NR Dual Connectivity (EN-DC) configuration. The master node in this arrangement is an eNB (LTE base station), which anchors the control plane connection to the core network (EPC) and manages the overall radio resource control (RRC) connection. The en-gNB connects to the EPC via the S1-U interface for user plane traffic and to the eNB via the X2 interface for inter-node coordination, including the X2-C control plane and X2-U user plane.
Architecturally, the en-gNB is defined across multiple 3GPP specifications. TS 37.340 provides the overarching multi-connectivity framework, defining how the en-gNB interacts with the master eNB through procedures such as Secondary Node Addition, Modification, and Release. TS 38.401 describes the overall NG-RAN architecture, while TS 38.473 specifies the F1AP protocol used when the en-gNB is split into a Central Unit (CU) and Distributed Unit (DU). TS 38.471 defines the E1AP protocol for the CU control plane and user plane separation. TS 36.420 covers the X2 interface between the eNB and en-gNB, and TS 28.540 addresses management aspects. TS 23.401 and 23.501 provide the core network architecture context for EPC and 5GC respectively.
The en-gNB supports NR radio interface capabilities including higher bandwidths (up to 100 MHz per carrier in FR1), massive MIMO antenna arrays, beamforming, and higher-order modulation schemes. It can operate in both Frequency Range 1 (FR1, sub-7 GHz) and Frequency Range 2 (FR2, mmWave). The en-gNB handles NR Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH) transmissions, along with associated control channels such as PDCCH and PUCCH. It maintains its own NR cell configurations, including SSB (Synchronization Signal Block) transmissions for cell detection and measurement.
In the EN-DC bearer architecture, the en-gNB can host Secondary Cell Group (SCG) bearers, where user plane data is split at the master node and routed through the en-gNB, or it can host Split Bearers where data is split at the PDCP layer. The en-gNB supports both MCG (Master Cell Group) and SCG bearer types, with the SCG split bearer being the most common configuration for maximizing throughput. The en-gNB reports radio measurements to the master eNB, which makes handover and secondary node change decisions.
From a deployment perspective, the en-gNB was critical for early 5G launches because it allowed operators to leverage existing LTE core networks (EPC) and control plane infrastructure while adding NR capacity through the secondary node. This avoided the need for immediate 5G core (5GC) deployment. Over time, as Standalone (SA) architecture became available, the role of the en-gNB evolved, but it remains a fundamental component for NSA deployments and dual connectivity scenarios throughout Releases 15 through 20.
Purpose & Motivation
The en-gNB was created to solve a critical deployment challenge: how to introduce 5G NR technology rapidly without requiring a complete overhaul of existing LTE core network infrastructure. When 3GPP began standardizing 5G in Release 15, operators faced a dilemma — building a fully standalone 5G network with a new core (5GC) would take years and enormous capital investment, but delaying 5G deployment meant falling behind in the race for enhanced mobile broadband capacity. The en-gNB concept, embedded in the EN-DC architecture, provided an elegant solution by allowing NR base stations to operate as secondary nodes anchored to existing LTE infrastructure.
Before the en-gNB, there was no standardized mechanism for LTE and NR to interoperate at the radio access level. Previous dual connectivity solutions, such as those defined in Release 12 for LTE-LTE dual connectivity, only addressed homogeneous LTE deployments. The introduction of NR required a new framework that could handle the significant differences between LTE and NR radio interfaces, including different numerologies, frame structures, and beam management procedures. The en-gNB specification in TS 37.340 addressed these challenges by defining new X2 signaling procedures, measurement configurations, and bearer architectures specifically designed for EN-DC.
The en-gNB also solved the problem of control plane anchoring. By keeping the RRC connection anchored at the LTE master eNB, the en-gNB avoided the complexity of dual RRC termination and ensured that mobility management remained stable during the transition period. This design choice meant that UEs could benefit from NR's higher throughput for user plane data while maintaining the proven reliability of LTE control plane procedures. This approach significantly reduced the risk of connection failures during the early deployment phase when NR coverage was still being built out.
What changed in its specifications
The latest release-to-release comparison of specifications that define en-gNB. Each summary describes the whole specification, not only this term.
Rel-19 adds Disaster Roaming in EPS, which covers disaster-roaming procedures and attach, tracking area update and mobility signalling. It also adds Time Reference Information Distribution Indication to subscription data and the MME-to-eNB path, along with Store and Forward Satellite operation text.
Full comparison in TS 23.401 →Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.
Full comparison in TS 23.501 →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
- en-gNB builds on gNB
“The purpose of the EN-DC X2 Setup procedure is to exchange application level data needed for an eNB and an en-gNB to interoperate correctly over the X2 interface in EN-DC case.” TS 36.300
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 5 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 en-gNB is introduced in Rel-15 as the NR Secondary Node in EN-DC, with its X2 procedures (EN-DC X2 setup/removal, configuration update) specified and the en-gNB term introduced in TS 37.340.
- “introduction of the en-gNB term” TS 37.340 v15.16.0
- “in which a UE is connected to one eNB that acts as a MN and one en-gNB that acts as a SN” TS 37.340 v15.16.0
- “An eNB initiates the procedure by sending the EN-DC X2 SETUP REQUEST message to a candidate en-gNB.” TS 36.423 v15.14.0
The en-gNB's EN-DC X2 setup and configuration update behaviour was extended (partial served-cell lists, IPSEC TNL address, CSI-RS and TDD configuration handling) and inter-system handover with a shared en-gNB/gNB was added.
- “The initiating en-gNB shall transfer the complete list of its served cells or if supported, a partial list of its served cells together with the Partial List Indicator IE” TS 36.423 v16.13.0
- “the receiving en-gNB shall, if supported, take this into account for IPSEC tunnel establishment.” TS 36.423 v16.13.0
- “If a gNB and an en-gNB are involved in direct data forwarding and realised within the same network entity” TS 37.340 v16.13.0
The en-gNB's X2AP behaviour in EN-DC gained new requirements: CPC data forwarding handling, CSI-RS and timing configuration handling, user plane integrity protection, SCG activation, and UE history collection.
- “If the SCG Activation Request IE in the SGNB ADDITION REQUEST message is set to "Activate SCG", the en-gNB shall, if supported, activate the SCG resources” TS 36.423 v17.7.0
- “if the Integrity Protection Indication IE is set to "required", the en-gNB shall, if supported, perform user plane integrity protection for the concerned E-RAB” TS 36.423 v17.7.0
- “Upon reception of the SGNB ADDITION REQUEST message, the en-gNB shall, if supported, start collecting the SCG information” TS 36.423 v17.7.0
Rel-18 adds en-gNB behaviour in X2AP: a RACH INDICATION procedure to the MeNB reporting random access, and ACCESS AND MOBILITY INDICATION handling extended to en-gNBs.
- “The en-gNB initiates the procedure by sending the RACH INDICATION message to MeNB.” TS 36.423 v18.4.0
- “This message is sent by the en-gNB to the MeNB to inform of one or more performed random access procedures at the en-gNB” TS 36.423 v18.4.0
- “This message is sent by the eNB to the eNB/en-gNB to transfer access and mobility related information.” TS 36.423 v18.4.0
A new SCG Failure Information Report procedure lets the MeNB report PSCell change failure to the en-gNB, which stores the information and uses it for SCG failure optimisation.
- “The MeNB initiates the procedure by sending the SCG FAILURE INFORMATION REPORT message to the en-gNB.” TS 36.423 v19.1.0
- “If received, the en-gNB uses the above information for SCG failure reason detection and optimisation.” TS 36.423 v19.1.0
- “The en-gNB initiates the procedure by sending the SCG FAILURE TRANSFER message to the MeNB.” TS 36.423 v19.1.0
Defining Specifications
3GPP specifications that define or reference en-gNB, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.401 vk10 | Evolved Packet System Architecture | Rel-20 read |
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 28.540 vk40 | 5G Network Resource Model (NRM) Stage 1 | Rel-20 read |
| TS 36.420 vj00 | X2 Interface Introduction for E-UTRAN | Rel-19 read |
| TS 37.340 vj30 | Overview of Multi-Connectivity Operation using E-UTRA and NR | Rel-19 read |
| TS 38.471 vj00 | F1 Interface Layer 1 Specification | Rel-19 read |
| TS 38.473 vj40 | F1 Application Protocol (F1AP) | Rel-19 read |