Iub Interface (RNC–Node B Interface)

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.