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

Glossary term · Radio Access Network

NG-RAN node

Next Generation Radio Access Network node

Radio Access Network →

NG-RAN node is a gNB or ng-eNB in the 5G radio access network that provides NR and LTE radio access to UEs and connects to the 5G Core via the NG interface.

Introduced
Rel-15
Where
Radio Access Network › NG-RAN (5G)
Specifications
11 specs
NG-RAN node Description Purpose What changed Neighbours Detected Changes Specifications

Description

An NG-RAN node is defined in 3GPP specifications as either a gNB or an ng-eNB, as specified in TS 38.300. It is the fundamental building block of the Next Generation Radio Access Network (NG-RAN), which is the radio access network component of the 5G System. The NG-RAN connects User Equipment (UE) to the 5G Core Network (5GC) through the NG interface, and NG-RAN nodes interconnect with each other through the Xn interface. The term is used extensively across specifications including TS 33.501 (security), TS 38.300 (NR overall description), TS 38.401 (NG-RAN architecture), and the Xn interface specification series (TS 38.410, 38.413, 38.414, 38.420, 38.422, 38.423, 38.424, 38.455).

The gNB is the NR base station that provides New Radio access to UEs. It may be deployed in a split architecture with a gNB-CU and one or more gNB-DUs connected via the F1 interface, or as a monolithic node. The ng-eNB is the LTE base station variant that provides E-UTRA access but connects to the 5G Core rather than the EPC. Like the gNB, the ng-eNB may be split into an ng-eNB-CU and ng-eNB-DUs. Both node types terminate the NG interface toward the 5GC, supporting both control plane (NG-C, using NGAP) and user plane (NG-U, using GTP-U) connectivity.

NG-RAN nodes are responsible for a wide range of functions: radio resource management, radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources in both uplink and downlink, IP header compression, encryption and integrity protection of user and signalling data, and selection of the AMF at UE attachment. They also handle scheduling, paging, broadcast of system information, and measurement configuration and reporting. In dual connectivity scenarios, an NG-RAN node may act as a master node or a secondary node, coordinating with another NG-RAN node over the Xn interface.

The Xn interface enables inter-node coordination for mobility (handover), dual connectivity, and other functions. Xn-C uses the XnAP protocol (TS 38.423) for control plane signalling, while Xn-U uses GTP-U for user plane data forwarding. The NG interface uses NGAP (TS 38.413) for control plane and GTP-U for user plane. These standardized interfaces allow multi-vendor deployment and interoperability between NG-RAN nodes from different manufacturers.

Security for NG-RAN nodes is addressed in TS 33.501, which defines the 5G security architecture including authentication, key management, and protection of signalling and user data. NG-RAN nodes participate in the security procedures by enforcing AS (Access Stratum) security, handling key derivation, and supporting integrity and ciphering algorithms. The NG-RAN node is also a key element in network slicing, supporting slice-aware resource management and slice-specific configuration.

Purpose & Motivation

The concept of the NG-RAN node was created to provide a unified, technology-neutral term for the base stations of the 5G radio access network. In 4G, the term eNB referred specifically to LTE base stations connected to the EPC. With 5G, 3GPP needed to support both New Radio (NR) access via gNBs and LTE access via ng-eNBs within the same radio access network connected to the 5G Core. Rather than defining separate architectures, 3GPP introduced the umbrella term NG-RAN node to encompass both.

This abstraction solves several problems. First, it allows the NG and Xn interfaces to be defined generically for both node types, simplifying the architecture and enabling interoperability. Second, it supports migration scenarios where operators deploy NR gradually while continuing to rely on LTE coverage — ng-eNBs provide LTE access to the 5GC alongside gNBs. Third, it enables dual connectivity between LTE and NR nodes (EN-DC, NGEN-DC, NE-DC) by treating both as NG-RAN nodes that can coordinate over Xn.

The NG-RAN node concept also supports the split CU/DU architecture, allowing both gNBs and ng-eNBs to be deployed flexibly with centralized and distributed functions. This unified model reduces specification complexity and gives operators a consistent framework for managing multi-radio-technology networks under a single 5G core.

What changed in its specifications

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

TS 33.501Rel-18 → Rel-19

Rel-19 TS 33.501 adds roaming and inter-PLMN indirect communication authorization, fast re-authentication for non-3GPP mobility, and AI/ML security clauses for positioning and federated learning. It also adds NPN security, NRF access token key retrieval, LTM security, and monitoring-of-signalling-traffic protection.

Full comparison in TS 33.501 →
TS 38.300Rel-18 → Rel-19

Rel-19 adds multi-hop L2 UE-to-Network relay for NR sidelink as the largest item. It also adds low-power wake-up signal and receiver (LP-WUS/WUR) text, on-demand SSB and SIB1 for network energy savings, and sub-band full duplex for TDD carriers.

Full comparison in TS 38.300 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (9 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 1 change
  • When NG-RAN node fails to set up a QoS flow for IMS voice TS 38.413CR0048
Rel-16 3 changes
  • Propagation of Roaming and Access Restriction information in NG-RAN in non-homogenous NG-RAN node deployments TS 38.300CR0207
  • Global Cell Identities and Global NG-RAN Node Identities when NR access is shared TS 38.300CR0246
  • Propagation of Roaming and Access Restriction information in NG-RAN in non-homogenous NG-RAN node deployments TS 38.423CR0327
Rel-17 2 changes
  • Introduction of Local NG-RAN Node IDs for RRC_INACTIVE [RRCInactive] TS 38.300CR0426
  • Correction on the local NG-RAN Node Identifier on Xn [RRCInactive] TS 38.423CR1072
Rel-18 2 changes
  • Correction of a wrong description of the S-NG-RAN node Counter Check procedure TS 38.423CR1396
  • Correction of Served Cell Specific Info Request in NG-RAN node configuration update procedure TS 38.423CR1336
Rel-19 1 change
  • Correction on NG-RAN node UE XnAP ID transfer in LTM CONFIGURATION UPDATE TS 38.423CR1670

Defining Specifications

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

SpecificationTitleRelease
TS 33.501 vk30 5G Security Architecture Rel-20 read
TS 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read
TS 38.401 vj30 NG-RAN Architecture Description Rel-19 read
TS 38.410 vj20 NG-RAN; NG General Aspects and Principles Rel-19 read
TS 38.413 vj40 NG Application Protocol (NGAP) Specification Rel-19 read
TS 38.414 vj00 NG Interface User Plane Protocol Rel-19 read
TS 38.420 vj10 Introduction to Xn interface specifications Rel-19 read
TS 38.422 vj00 Xn Signalling Transport Specification Rel-19 read
TS 38.423 vj40 NG-RAN Xn Application Protocol Rel-19 read
TS 38.424 vj00 Xn Interface User Plane Transport Protocol Rel-19 read
TS 38.455 vj30 NR Positioning Protocol A Rel-19 read