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

Glossary term · Interface

Iub

Iub Interface (RNC–Node B Interface)

Interface →

Iub is the standardized 3GPP interface connecting a Radio Network Controller (RNC) to Node B base stations in UMTS, carrying user data and control signaling for UTRAN.

Introduced
R99
Where
Services
Specifications
2 specs
Iub Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Iub interface is the standardized logical interface between the Radio Network Controller (RNC) and a Node B in the UMTS Terrestrial Radio Access Network (UTRAN). It is defined in 3GPP TS 25.401 (UTRAN overall description) and referenced in the vocabulary specification TS 21.905. Architecturally, Iub sits between the Uu air interface (UE to Node B) and the Iu interface (RNC to core network), forming the middle segment of the UTRAN protocol stack. Because the RNC owns radio resource control, admission control, and handover decisions, the Iub interface is the transport over which those centralized decisions are executed at the Node B.

Functionally, Iub carries two broad classes of traffic: user plane data and control plane signalling. The user plane transports dedicated channel (DCH) and, in later releases, High Speed Downlink Packet Access (HSDPA) and High Speed Uplink Packet Access (HSUPA) data frames between the RNC and Node B. The control plane carries Node B Application Part (NBAP) signalling, which is used for cell configuration, common transport channel setup, dedicated channel establishment and release, radio link reconfiguration, and measurement reporting. NBAP messages allow the RNC to command the Node B to add, modify, or delete radio links for a given UE.

The Iub transport architecture is layered. Above the physical transport, ATM was the original bearer in early UMTS deployments, with AAL2 for user plane and AAL5 for control plane. From Rel-5 onwards, IP transport became increasingly common, and the Iub was adapted to run over IP with SCTP for NBAP signalling and UDP/IP for user plane framing. This transport flexibility allowed operators to migrate from ATM to IP backhaul without changing the logical interface definition.

A key architectural feature of Iub is the concept of the lub FP (Frame Protocol) for user data. The Frame Protocol defines data frames, control frames, and timing information that allow the RNC and Node B to synchronize and to manage the radio link. For HSDPA, the Iub carries HS-DSCH data frames and associated control, while for HSUPA it carries E-DCH data frames. These enhancements required new frame formats and flow control mechanisms, which were added in Rel-5 and Rel-6 respectively.

In terms of deployment, Iub is a logical interface and does not mandate a specific physical topology. It may be realized over point-to-point links, star topologies, or shared backhaul, and it may traverse aggregation networks. The RNC can control many Node Bs over Iub, and each Node B may serve multiple cells. This flexibility is essential for radio network planning, because it decouples logical radio control from physical backhaul layout. The Iub interface remained stable across Releases 4 through 19, with the definition text unchanged, reflecting its mature and settled role in the UTRAN architecture.

Purpose & Motivation

The Iub interface exists to provide a standardized, vendor-interoperable connection between the RNC and Node B in UMTS. Before standardization, radio base station control was often proprietary, which limited multi-vendor deployment and made it difficult for operators to mix equipment from different suppliers. By defining Iub in 3GPP specifications, the industry enabled an open interface where the RNC could control Node Bs from multiple vendors, fostering competition and reducing costs.

A second motivation is the centralization of radio resource management. In UMTS, the RNC performs functions such as admission control, handover control, and radio bearer management. These functions require a reliable signalling path to the Node B, which Iub provides. Without a standardized Iub, each vendor would implement its own control protocol, making interworking and feature parity difficult.

Finally, Iub was designed to support the evolution from circuit-switched to packet-switched radio access. As HSDPA and HSUPA were introduced, Iub had to carry new frame types and support higher data rates and tighter scheduling. The interface definition was kept stable while transport options evolved from ATM to IP, allowing operators to upgrade backhaul without redefining the logical interface. This balance of stability and transport flexibility is a key reason Iub remained relevant through Rel-19.

What changed in its specifications

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

TR 21.905Rel-17 → Rel-18

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 →
TS 25.401Rel-18 → Rel-19

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

Full comparison in TS 25.401 →

Technology family

RAN interfaces · Radio Access Network

  1. Phase 1 A interface, Abis
  2. R99 Iu, Iu-BC, Iu-CS, Iu-PS, Iub, Iur, NBAP, Uu
  3. Rel-5 Iur-g
  4. Rel-8 S1, S1-MME, S1-U, S1AP, X2
  5. Rel-15 E1, E1AP, F1, F1-C, F1-U, F1AP, NG, NG-C, NG-U, NGAP, Xn, Xn-C, Xn-U
  • Iub counterpart in another generation: Abis
    “Transmission sharing between the GSM/GPRS Abis interface and the Iub interface shall not be precluded.” TS 25.430
  • Iub used together with NBAP
    “Node B Application Part: Radio Network Signalling over the Iub” TS 25.401
  • Iub counterpart in another generation: F1
    “The F1 interface provides means for interconnecting a gNB-CU and a gNB-DU of a gNB within an NG-RAN” TS 38.470

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

R99 introduced

TS 25.401 first specifies the Iub interface as the interface between the RNC and Node B, covering its transport network layer, signalling and user plane protocol model.

  • “Iub: Interface between the RNC and the Node B” TS 25.401 v3.10.0
  • “A Node B is connected to the RNC through the Iub interface.” TS 25.401 v3.10.0
  • “For each UTRAN interface (Iu, Iur, Iub) the related transport network layer protocol and functionality is specified.” TS 25.401 v3.10.0
Rel-5 specification text

TS 25.401 Rel-5 adds Iub HS-DSCH Frame Protocol between MAC-hs at Node B and the CRNC flow control, and extends the Iub MAC distribution to HS-DSCH.

  • “Iub HS-DSCH Frame Protocol is used to interwork the MAC-hs at the Node B with the Flow Control function at the Controlling RNC.” TS 25.401 v5.10.0
  • “how the MAC layer is distributed over Uu, Iub and Iur for the RACH, FACH, DCH, [TDD – DSCH, USCH] and HS-DSCH.” TS 25.401 v5.10.0
Rel-7 specification text

Adds a protocol model (Figure 25B) for HS-DSCH for UEs in Cell_FACH, Cell_PCH and URA_PCH, where MAC-ehs at the Node B interworks over Iub with flow control in the MAC-c at the CRNC.

  • “Figure 25B shows the protocol model for the HS-DSCH transport channel configured for UE in Cell_FACH, Cell_PCH and URA_PCH” TS 25.401 v7.6.0
  • “Iub HS-DSCH Frame Protocol is used to interwork the MAC-ehs at the Node B with the Flow Control function at the MAC-c” TS 25.401 v7.6.0

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 25.401 vj00 UTRAN Overall Architecture Rel-19 read