Description
Node B is the fundamental radio access network element of the UMTS Terrestrial Radio Access Network (UTRAN). It is a logical node within the Radio Network Subsystem (RNS) that performs the physical layer processing and radio transmission/reception functions for one or more cells towards the User Equipment (UE). Architecturally, Node B sits between the UE over the Uu air interface and the Radio Network Controller (RNC) over the Iub interface, which it terminates. This separation of radio functions (Node B) from radio resource control and mobility management (RNC) is a defining characteristic of the UMTS architecture and distinguishes it from the flatter LTE architecture where the eNodeB combines both roles.
Functionally, Node B performs channel coding, interleaving, rate matching, spreading, modulation, and RF transmission on the downlink, and the corresponding reverse operations on the uplink. It handles the physical channels of the WCDMA air interface, including the Primary Common Control Physical Channel (P-CCPCH), Primary Common Pilot Channel (P-CPICH), and dedicated physical channels (DPCH). With the introduction of High Speed Downlink Packet Access (HSDPA) in Release 5, Node B gained additional responsibilities including fast scheduling, Hybrid ARQ (HARQ), and Adaptive Modulation and Coding (AMC) through the High Speed Downlink Shared Channel (HS-DSCH). Release 6 added High Speed Uplink Packet Access (HSUPA) with the Enhanced Dedicated Channel (E-DCH), further increasing Node B's role in uplink scheduling and HARQ processing.
The Iub interface between Node B and RNC carries both control plane signalling (Node B Application Part, NBAP) and user plane data (Frame Protocol). NBAP is used for cell configuration, common channel setup, dedicated channel management, and measurement reporting. The Frame Protocol transports user data and associated control information such as timing adjustment and power control. Node B also performs measurements on the air interface, including received signal code power (RSCP), received total wideband power (RTWP), and transmit power, which are reported to the RNC for radio resource management decisions such as admission control, congestion control, and handover.
Node B supports several operational modes including Frequency Division Duplex (FDD) and Time Division Duplex (TDD), corresponding to the two modes of UTRA. In FDD mode, uplink and downlink use separate frequency carriers, while TDD mode uses the same carrier with time-separated uplink and downlink slots. Node B also supports transmit diversity, beamforming, and, in later releases, MIMO and higher-order modulation (64QAM) for HSDPA. The logical node concept allows a single physical Node B to serve multiple cells, typically three sectors with directional antennas, each cell being an independent radio coverage area.
In the broader evolution of 3GPP networks, Node B represents the second generation of base station architecture, following the GSM Base Transceiver Station (BTS) and preceding the LTE eNodeB and 5G gNodeB. While the term remains in use throughout all UMTS releases up to Rel-19, the functional scope of Node B has expanded significantly with each release, particularly through HSPA enhancements. The term is also used in the context of Home Node B (HNB), also known as femtocell, which is a consumer-deployed Node B for improved indoor coverage.
Purpose & Motivation
Node B was created to provide the radio access functionality for UMTS, separating the physical layer radio processing from the higher-layer radio resource control and mobility management functions performed by the RNC. This architectural split was motivated by the need to centralize radio resource management in the RNC for efficient coordination across multiple Node Bs, enabling soft handover and centralized interference management, while keeping the Node B relatively simple and cost-effective to deploy in large numbers.
The separation also allowed network operators to deploy Node Bs flexibly in different environments, from dense urban macrocells to rural coverage, while maintaining centralized control. The Iub interface was standardized to ensure multi-vendor interoperability, allowing operators to mix Node Bs and RNCs from different vendors. Over time, as HSPA introduced fast scheduling and HARQ, Node B gained more intelligence, moving closer to the distributed architecture later adopted in LTE, where the eNodeB combines the functions of Node B and RNC.
What changed in its specifications
The latest release-to-release comparison of specifications that define Node B. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Added relative time stamp accuracy for RRC connection failure logging, revised TDD UE demodulation tests for multi-cell scenarios, and added band 27 to E-UTRAN FDD RSRP/RSRQ parameters.
Full comparison in TS 25.123 →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
- Node B counterpart in another generation: BTS
“Type B LMU: accessed over the base station to controller interface (Abis in GSM and Iub in UMTS).” TS 23.002
- Node B counterpart in another generation: eNB
“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
- Node B extended by HNB
“The Home NodeB Subsystem (HNS) consists of a Home NodeB (HNB), a Home NodeB Gateway (HNB-GW) and optionally a Local GW (L-GW).” TS 23.002
- Node B used together with RNC
“The RNS consists of one Radio Network Controller (RNC) and one or more Node B.” TS 23.002
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.
Node B is defined for the first time as the logical node responsible for radio transmission/reception in cells, terminating the Iub interface towards the RNC and supporting FDD, TDD or dual mode.
- “logical node in the RNS responsible for radio transmission / reception in one or more cells to/from the UE” TS 25.401 v3.10.0
- “Iub: Interface between the RNC and the Node B” TS 25.401 v3.10.0
- “A Node B can support FDD mode, TDD mode or dual-mode operation.” TS 25.401 v3.10.0
Node B behaviour was extended for TDD: it may support one or both chip-rate options, and uplink inner-loop power control and synchronisation roles were specified per FDD, 1.28 Mcps TDD and 3.84 Mcps TDD.
- “A Node B which supports TDD cells can support one chip-rate option only, or both options.” TS 25.401 v4.6.0
- “UL Inner Loop Power Control which is located in Node B for FDD and 1.28 Mcps TDD and is located in the UE for 3.84 Mcps TDD” TS 25.401 v4.6.0
- “At the detection of uplink burst, the Node B will evaluate the received power level and timing” TS 25.401 v4.6.0
Node B functionality was extended for Rel-5: MAC-hs and HS-DSCH scheduling now reside in the Node B, with HS-DSCH frame protocol interworking over Iub, and a Node B management IOC was added.
- “The High Speed MAC (MAC-hs) entity in the Node B transfers MAC-hs PDU to the peer MAC-hs entity in the UE over the Uu interface.” TS 25.401 v5.10.0
- “A Relaying Function in the Node B relays the HS-DSCH frame received by HS-DSCH FP entity to the MAC-hs entity.” TS 25.401 v5.10.0
- “This IOC represents Node B functionality.” TS 32.642 v5.6.0
Node B gained E-DCH responsibilities in Rel-6: MAC-e entity with E-DCH scheduling, an interworking function to E-DCH FP, and Iuant/RET antenna control via its element manager.
- “An Interworking Function (IWF) in the Node B interworks the E-DCH frame received by the MAC-e entity into the E-DCH Frame Protocol” TS 25.401 v6.9.0
- “E-DCH scheduling is performed by MAC-e in the Node B and reordering is performed by MAC-es in the RNC.” TS 25.401 v6.9.0
Rel-7 extends Node B behaviour in TS 25.401: it hosts the Enhanced High Speed MAC (MAC-ehs) with HS-DSCH scheduling, supports 7.68 Mcps TDD, and supports more than two chip-rate options.
- “HS-DSCH scheduling is performed by MAC-hs (or MAC-ehs) in the Node B.” TS 25.401 v7.6.0
- “A Node B which supports TDD cells can support one chip-rate option only, or more than one option.” TS 25.401 v7.6.0
- “The Enhanced High Speed MAC (MAC-ehs) entity in the Node B transfers MAC-ehs PDU to the peer MAC-ehs entity in the UE” TS 25.401 v7.6.0
The Rel-8 text extends the HS-DSCH Cell_DCH and Cell_FACH/PCH/URA_PCH protocol models to 1.28 Mcps TDD, and the E-DCH entities now include MAC-i/MAC-is.
- “[FDD and 1.28 Mcps TDD – The protocol model in Figure 25 is applied for HS-DSCH configured for UEs in Cell_DCH.]” TS 25.401 v8.2.0
- “E-DCH scheduling is performed by MAC-e/MAC-i in the Node B and reordering is performed by MAC-es/MAC-is in the RNC.” TS 25.401 v8.2.0
Defining Specifications
3GPP specifications that define or reference Node B, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 25.123 vj00 | Radio Resource Management for TDD | Rel-19 read |
| TS 25.133 vj00 | UTRAN RRM Requirements for FDD | Rel-19 read |
| TS 25.171 vj00 | A-GPS Minimum Performance Requirements for UTRA FDD UE | Rel-19 read |
| TS 25.401 vj00 | UTRAN Overall Architecture | Rel-19 read |
| TS 28.652 vj00 | UTRAN Network Resource Model (NRM) IRP Information Service | Rel-19 read |
| TS 28.702 vj00 | Core Network NRM IRP Information Service | Rel-19 read |
| TS 32.602 vj00 | Basic Configuration Management IRP Information Service | Rel-19 read |
| TS 32.622 vb10 | Generic Network Resources NRM | Rel-11 read |
| TS 32.632 vb00 | Core Network Resources NRM | Rel-11 read |
| TS 32.642 vb50 | UTRAN Network Resource Model | Rel-11 read |
| TS 32.662 vj00 | Configuration Management (CM); Kernel CM IRP | Rel-19 read |
| TS 32.712 vb10 | Transport Network NRM Information Service | Rel-11 read |