Description
gNB (gNodeB) is the base station in 5G New Radio (NR) that serves as the radio access node for User Equipment (UE). It is responsible for radio resource management, scheduling, and providing connectivity to the 5G Core Network (NGC). The gNB is the NR counterpart to the eNB in LTE and supports a wide range of deployment scenarios, including standalone (SA) and non-standalone (NSA) architectures. In SA, the gNB connects directly to the 5G Core via the NG interface; in NSA, it may operate as a secondary node (en-gNB) under an LTE Master Node. The gNB interfaces with other gNBs via the Xn interface for handover and dual connectivity, and with the AMF/UPF via NG-C and NG-U respectively.
Architecturally, a gNB can be implemented in a centralized unit (CU) and distributed unit (DU) split, as defined in 3GPP TS 38.401. The CU handles higher-layer protocols (e.g., RRC, SDAP, PDCP) while the DU handles lower layers (RLC, MAC, PHY). This functional split allows flexible deployment, with the CU located in a central office and DUs at cell sites, connected via F1 interface. The gNB also supports network slicing, enabling multiple logical networks on the same physical infrastructure, and advanced features like beamforming, massive MIMO, and dynamic spectrum sharing. Key specifications include TS 38.401 (NG-RAN architecture), TS 38.413 (NGAP), and TS 38.473 (F1AP).
The gNB performs several critical functions: radio resource management (scheduling, handover, power control), connection management (establishment, maintenance, release), and data forwarding. It also participates in mobility procedures such as handovers and dual connectivity, and supports QoS flows through the SDAP layer. The gNB communicates with the UE via the Uu interface, using OFDM-based waveforms and flexible numerology. In multi-connectivity, the gNB can act as a Master Node (MN) or Secondary Node (SN), coordinating with other nodes (e.g., eNB or other gNBs) for dual connectivity.
gNB is essential for delivering 5G services with high data rates, low latency, and massive connectivity. It enables use cases like eMBB, URLLC, and mMTC by providing the necessary radio capabilities and core network integration. The gNB also plays a key role in network sharing, allowing multiple operators to share the same infrastructure. Its design is highly scalable, supporting dense deployments and diverse spectrum bands (sub-6 GHz and mmWave).
The term gNB was introduced in Release 14 as part of initial 5G study, and its definition was later simplified to reference TS 38.300. This reflects the maturation of 5G specifications, where the gNB is now fully defined in the RAN architecture specs. The gNB continues to evolve with 5G Advanced, incorporating features like AI/ML-based optimization, energy efficiency, and integrated access and backhaul (IAB).
Purpose & Motivation
The gNB was created to provide the radio access for 5G NR, addressing the limitations of LTE eNB in supporting new spectrum, higher bandwidths, and advanced antenna technologies. While LTE eNB could be upgraded to support some 5G features via EN-DC, the true potential of 5G required a new base station designed from the ground up to handle mmWave frequencies, beamforming, and network slicing. The gNB exists to deliver the enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC) services that define 5G.
Previous generations of base stations (e.g., eNB) were not designed for the flexibility and scalability demanded by 5G. They lacked the ability to dynamically allocate resources across diverse services, support massive MIMO with beam management, or integrate with a service-based core network. The gNB solves these problems by adopting a modular architecture with CU/DU split, enabling centralized coordination and distributed processing for low latency. It also supports network slicing, which allows operators to create multiple virtual networks on a single physical infrastructure, each tailored to specific service requirements.
The gNB was motivated by the need to handle the extreme variability of 5G use cases, from high-throughput video streaming to ultra-reliable industrial automation. Its design allows for flexible numerology, wide bandwidth operation, and advanced antenna systems, which were not feasible with LTE. Additionally, the gNB's integration with the 5G Core (NGC) via NG interfaces ensures end-to-end QoS and policy control, enabling new business models and revenue streams for operators. Overall, the gNB is the cornerstone of 5G radio access, enabling the full realization of 5G's potential.
What changed in its specifications
The latest release-to-release comparison of specifications that define gNB. Each summary describes the whole specification, not only this term.
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 →Rel-19 adds Wireless Access Backhaul (WAB) architecture and node procedures to TS 38.401. It also adds multi-hop Layer-2 sidelink UE-to-Network relay with First, Intermediate and Last U2N Relay UE roles. Ambient IoT support is added, including A-IoT session contexts and AMF connectivity.
Full comparison in TS 38.401 →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
- gNB decomposed into gNB-CU
“gNB Central Unit (gNB-CU): a logical node hosting RRC, SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs.” TS 38.401
- gNB decomposed into gNB-DU
“gNB Distributed Unit (gNB-DU): a logical node hosting RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by gNB-CU.” TS 38.401
- gNB extended by en-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
- gNB counterpart in another generation: eNB (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 6 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 first specifies gNB requirements and measurements: security requirements for ciphering and integrity protection in TS 33.501, and gNB performance measurements and KPIs in TS 28.552 and TS 28.554.
- “The gNB shall support ciphering of user data between the UE and the gNB.” TS 33.501 v15.20.0
- “The gNB shall activate ciphering of user data based on the security policy sent by the SMF.” TS 33.501 v15.20.0
- “5.1.1.3.1 Average DL UE throughput in gNB” TS 28.552 v15.7.0
In Rel-16 the gNB gained new behaviour: GTP-U QoS-monitoring delay measurement, PDU session and DRB setup measurements, and updated security requirements and handover procedures.
- “The gNB performs the GTP PDU packet delay measurement for QoS monitoring per the GTP PDU monitoring packets received from UPF” TS 28.552 v16.20.0
- “The gNB sends the HO command to the UE, in which the gNB shall include the 4 LSB of the downlink NAS COUNT” TS 33.501 v16.20.0
- Add PDU Session Resource setup related measurements for gNB TS 28.552CR0004
gNB behaviour changed in Rel-17: UP security activation and policy handling now applies to gNB/ng-eNB, and the NR CGI report and NGAP signalling gained gNB ID length handling.
- Introduction of gNB ID length reporting in the NR CGI report [gNB_ID_Length] TS 36.300CR1363
- Support for handling unknown length of gNB identifier [gNB_ID_Length] TS 38.413CR0571
- “the target ng-eNB/gNB shall initiate intra-cell handover procedure which includes RRC Connection Reconfiguration procedure to reconfigure the DRBs” TS 33.501 v17.16.0
Rel-18 changed gNB behaviour and requirements: new gNB measurements (per-PLMN PDU session counts, network slice throughput at gNB, QoS monitoring delay) and updated SCAS security requirements for the gNB.
- “This measurement provides the number of PDU Sessions by the gNB. This measurement is split into subcounters per S-NSSAI and per PLMN ID.” TS 28.552 v18.12.0
- “This KPI describes the downstream throughput of a network slice instance at gNB/CU-UP end on the NgU interface.” TS 28.554 v18.9.0
- “The gNB activates ciphering of user data based on the security policy sent by the SMF” TS 33.511 v18.3.0
In Rel-19 the gNB gains LTM (L1/L2 Triggered Mobility) roles: it handles L1 measurement reports, issues cell switch commands, and has LTM security key handling and Handover Cancel support.
- “LTM (L1/L2 Triggered Mobility) is a procedure in which a gNB receives L1 measurement report(s) from a UE” TS 28.552 v19.9.0
- “During LTM execution phase, the serving gNB includes the NCC used for the derivation of KNG-RAN* in the Cell Switch Command MAC CE to the UE.” TS 33.501 v19.7.0
- Support for Handover Cancel from the source gNB for LTM TS 38.423CR1690
gNB-related KPIs and measurements were extended: gNB energy consumption now supports per-PLMN-ID granularity, carbon emission KPI covers multiple energy supplies, and new gNB measurements for early TA acquisition and AIoT were added.
- “The KPI optionally supports consumption of an gNB at operator-specific, i.e., at a per PLMN-ID granularity.” TS 28.554 v20.3.0
- Enhance Estimated carbon emission KPI for gNB with multiple energy supplies TS 28.554CR0261
- Add AIoT related measurements for gNB TS 28.552CR0806
Defining Specifications
3GPP specifications that define or reference gNB, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 28.540 vk40 | 5G Network Resource Model (NRM) Stage 1 | Rel-20 read |
| TS 37.483 vj40 | E1 Application Protocol (E1AP) | 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 |
| TS 38.463 vj00 | E1 Application Protocol (E1AP) | 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 |
| TR 38.801 ve00 | Study on new radio access technology: Radio access architecture and interfaces | Rel-14 read |
| TS 38.806 vf00 | E1 Interface for CP/UP Separation in 5G NR | Rel-15 read |