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

Glossary term · Radio Access Network

ng-eNB

Next Generation Evolved NodeB

Radio Access Network →

ng-eNB is an LTE base station that connects via the NG interface to the 5G Core, enabling LTE radio access to interwork with 5G core networks.

Introduced
Rel-15
Where
Radio Access Network › NG-RAN (5G)
Specifications
7 specs
Also in
Management
ng-eNB Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The ng-eNB (Next Generation Evolved NodeB) is a radio access network node defined in 3GPP Release 15 as part of the 5G architecture. It provides E-UTRA (Evolved Universal Terrestrial Radio Access, i.e., LTE) user plane and control plane protocol terminations towards the User Equipment (UE) and connects to the 5G Core Network (5GC) via the NG interface. The ng-eNB is essentially an LTE base station (eNB) that has been upgraded to support the NG interface, allowing it to interwork with the 5G core. This enables operators to leverage their existing LTE infrastructure while migrating to 5G, providing a smooth transition path.

The ng-eNB is a key component of the NG-RAN (Next Generation Radio Access Network), which also includes the gNB (NR base station). Together, ng-eNBs and gNBs can serve UEs and connect to the 5GC. The ng-eNB supports the E-UTRA air interface, which includes LTE features such as carrier aggregation, MIMO, and dual connectivity. It terminates the E-UTRA protocols (RRC, PDCP, RLC, MAC, PHY) towards the UE and the NG Application Protocol (NGAP) towards the 5GC. The NG interface between the ng-eNB and the 5GC consists of the control plane (NG-C) and user plane (NG-U) parts. The control plane uses NGAP over SCTP, while the user plane uses GTP-U over UDP/IP.

Architecturally, the ng-eNB can be connected to the 5GC via the AMF (Access and Mobility Management Function) for control plane and the UPF (User Plane Function) for user plane. It may also support dual connectivity with a gNB, where the ng-eNB acts as a master or secondary node, enabling tight interworking between LTE and NR. This is known as E-UTRA-NR Dual Connectivity (EN-DC) or NG-RAN E-UTRA-NR Dual Connectivity (NGEN-DC). The ng-eNB also supports network slicing, allowing it to connect to different network slices in the 5GC.

The ng-eNB was introduced in Release 15 as part of the initial 5G specifications. Its definition has remained largely unchanged across Releases 15 to 19, emphasizing its role as an LTE node connected to the 5GC. In Release 20, the definition was changed to refer to 3GPP TS 38.300, indicating a consolidation of radio access network terminology. The ng-eNB is essential for operators who wish to deploy 5G core networks while continuing to use LTE radio access, providing a path to 5G services without immediate NR deployment.

In summary, the ng-eNB is a critical element for the coexistence and interworking of LTE and 5G, enabling a smooth evolution to 5G core networks and supporting features like network slicing and dual connectivity.

Purpose & Motivation

The ng-eNB was introduced in Release 15 to enable LTE radio access to connect to the 5G Core Network (5GC). Prior to 5G, LTE base stations (eNBs) connected to the 4G Evolved Packet Core (EPC) via the S1 interface. With the advent of 5G, operators needed a way to leverage their existing LTE infrastructure while migrating to the new 5G core, which offers improved capabilities such as network slicing, service-based architecture, and enhanced QoS. The ng-eNB solves this by providing an upgraded LTE base station that supports the NG interface to the 5GC, allowing LTE UEs to access 5G services.

The motivation for the ng-eNB also stems from the need for a smooth transition path. Deploying a nationwide 5G NR network requires significant investment and time. By allowing LTE base stations to connect to the 5GC, operators can offer 5G services to users with LTE devices and gradually upgrade to NR as needed. This approach, known as Non-Standalone (NSA) or Standalone (SA) with LTE access, ensures that users can benefit from 5G core features like network slicing and lower latency even before NR coverage is ubiquitous.

Furthermore, the ng-eNB supports dual connectivity with gNBs, enabling tight interworking between LTE and NR. This allows for increased throughput and reliability by aggregating LTE and NR carriers. The ng-eNB also plays a role in network slicing by allowing LTE cells to be associated with specific slices in the 5GC. Overall, the ng-eNB is a key enabler for the coexistence and interworking of LTE and 5G, facilitating a cost-effective and gradual migration to 5G networks.

What changed in its specifications

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

TS 28.540Rel-18 → Rel-19

Rel-19 adds management clauses for Ambient IoT, IAB nodes, and regenerative NTN with UE-Satellite-UE communication. It also shifts NTN responsibility from 5GC to 3GPP.

Full comparison in TS 28.540 →
TS 28.657Rel-15 → Rel-16

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

Full comparison in TS 28.657 →

Technology family

Base stations and RAN nodes · Radio Access Network

  1. Phase 1 BSC, BSS, BTS
  2. R99 Node B, RNC, RNS
  3. Rel-8 eNB, HeNB, HNB, HNB-GW
  4. Rel-10 DeNB, HeNB-GW, RN
  5. Rel-15 en-gNB, gNB, gNB-CU, gNB-CU-CP, gNB-CU-UP, gNB-DU, ng-eNB
  6. Rel-16 IAB-donor, IAB-DU, IAB-MT, IAB-node
  7. Rel-18 Mobile IAB-node
  • ng-eNB builds on 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

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 sources

Documented 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.

Rel-15 introduced

Rel-15 first defines the ng-eNB as an E-UTRA node connected via the NG interface to 5GC, with its security procedures, Xn/NG signalling, spectrum-sharing coordination and management support.

  • “node providing E-UTRA user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC.” TS 36.300 v15.14.0
  • “For an ng-eNB which can connect to EPC and 5GC, the ng-eNB shall choose the corresponding security procedures” TS 33.501 v15.20.0
  • “This IE is used to globally identify an ng-eNB (see TS 38.300 [8]).” TS 38.413 v15.13.0
Rel-16 1 CR

Rel-16 extends ng-eNB behaviour: it supports Control Plane and User Plane CIoT 5GS optimisation with suspend/resume and re-establishment procedures, plus new NG-AP procedures that apply only to ng-eNB.

  • “The purpose of this procedure is to allow the ng-eNB to suspend an RRC connection to be resumed by the UE using User Plane CIoT 5GS Optimisation” TS 33.501 v16.20.0
  • “This procedure applies only if the NG-RAN node is an ng-eNB.” TS 38.413 v16.18.0
  • CR to 38.401 on corrections to ng-eNB deployment TS 38.401CR0107
Rel-17 specification text

In Rel-17, ng-eNB gained support for user plane integrity protection with the UE over Uu, and ng-eNB must no longer reject PDU sessions requiring integrity protection; the UE must indicate support.

  • “ng-eNB shall support the use of integrity protection with the UE over the Uu interface.” TS 33.501 v17.16.0
  • “The UE shall indicate its support of integrity protection with the ng-eNB if it supports E-UTRA connected to 5GC.” TS 33.501 v17.16.0
  • “If the NG-RAN node is an ng-eNB, it shall reject all PDU sessions for which the Integrity Protection Indication IE is set to "required".” TS 38.423 v17.14.0
Rel-18 specification text

ng-eNB gained a requirement to handle highPriorityAccess attempts with high priority, rejecting them with RRC Reject only in extreme load, plus Xn-U address indication for data forwarding.

  • “The ng-eNB handles access attempts with establishment or resume cause "highPriorityAccess" with high priority” TS 36.300 v18.8.0
  • “the new ng-eNB may send Xn: Xn-U ADDRESS INDICATION message to the old ng-eNB to provide DL data forwarding address” TS 36.300 v18.8.0

Defining Specifications

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

SpecificationTitleRelease
TS 28.540 vk40 5G Network Resource Model (NRM) Stage 1 Rel-20 read
TS 28.657 vk00 E-UTRAN and ng-eNB NRM Requirements Rel-20 read
TS 28.802 vf00 Management Study for 5G Network Architecture Rel-15 read
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 38.401 vj30 NG-RAN Architecture Description Rel-19 read
TS 38.413 vj40 NG Application Protocol (NGAP) Specification Rel-19 read
TS 38.455 vj30 NR Positioning Protocol A Rel-19 read