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

Glossary term · Radio Access Network

IP UTRAN node

Internet Protocol UTRAN Node

Radio Access Network →

IP UTRAN node is a UTRAN node (RNC or NodeB) that supports the IP Transport Option for its lub/lur/Iu interfaces, enabling IP-based backhaul instead of ATM.

Introduced
Rel-8
Where
Radio Access Network › UTRAN (3G)
Specifications
2 specs
IP UTRAN node Description Purpose Neighbours Specifications

Description

An IP UTRAN node is a UTRAN network element—typically a Radio Network Controller (RNC) or a NodeB—that implements the IP Transport Option defined in 3GPP specifications 25.432 and 25.434. In the classic UTRAN architecture, transport between the RNC and NodeB (Iub), between RNCs (Iur), and between the RNC and the core network (Iu) was originally carried over ATM (Asynchronous Transfer Mode). The IP Transport Option allows these same interfaces to be carried over IP-based transport, using IP as the transport layer for user-plane and control-plane data. This is a transport-level change, not a change to the radio interface or to the UTRAN protocol stack above the transport layer.

The concept matters because ATM backhaul was expensive, operationally complex, and increasingly out of step with the IP-centric evolution of core networks and transmission infrastructure. By supporting IP transport, an IP UTRAN node can connect to an IP/MPLS transport network, share infrastructure with other IP services, and benefit from the economies of scale and operational tooling of IP networks. The specifications 25.432 (UTRAN Iub interface: user plane protocols for Common Transport Channel data streams) and 25.434 (UTRAN Iub interface data transport and transport signalling for Common Transport Channel data streams) define how data is carried over IP transport, including the framing, QoS handling, and transport signalling needed for the Iub interface.

Architecturally, the IP Transport Option is negotiated and configured per interface. An IP UTRAN node must support the relevant transport signalling, such as the transport bearer management procedures, and must be able to map UTRAN QoS requirements onto IP transport QoS mechanisms (for example, DiffServ code points or MPLS traffic engineering). The node also needs to handle IP address management, security considerations for IP transport, and interworking with the existing ATM-based parts of the network during migration. In practice, operators often deploy a mix of ATM and IP transport, so an IP UTRAN node may need to interoperate with nodes that still use ATM.

Its definition—"An UTRAN Node supporting the IP Transport Option"—is deliberately simple and stable, because the underlying transport option itself is defined in the referenced specifications rather than in the glossary definition. The stability of the definition across releases reflects that the concept is a transport capability rather than a feature that evolves release by release.

For engineers, the key takeaway is that an IP UTRAN node is about transport convergence: it lets UTRAN infrastructure ride on IP backhaul, aligning radio access transport with the all-IP direction of 3GPP networks. It is a foundational step toward the flat, IP-based architectures that later releases (HSPA evolution, LTE, and beyond) would assume as standard.

Purpose & Motivation

The IP UTRAN node exists to solve the transport problem of early UTRAN deployments. Originally, UTRAN interfaces were designed around ATM, which provided strong QoS but was costly, required specialized expertise, and scaled poorly for data-heavy traffic. As core networks and transmission networks moved toward IP, keeping UTRAN on ATM created a transport island that was expensive to operate and hard to integrate with the rest of the operator's infrastructure.

The IP Transport Option addressed this by allowing UTRAN nodes to use IP-based transport for their interfaces. This reduced capital and operational expenditure, enabled the use of commodity IP/MPLS equipment, and allowed transport capacity to be shared and managed with the same tools used elsewhere in the network. It also positioned UTRAN for the transition to all-IP networks, including the eventual move toward flat architectures and the IP-based core networks of later releases.

Historically, the IP UTRAN node represents the point at which 3GPP formalized IP transport for UTRAN in the Release 8 timeframe, even though IP transport work had been ongoing earlier. The definition remained unchanged through Release 19, underscoring that the concept is a stable transport capability rather than a feature that needed repeated revision.

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-8 Initial

Initial introduction of the term as "An UTRAN Node supporting the IP Transport Option." This release established the concept of UTRAN nodes using IP-based transport for their interfaces, defined in specifications 25.432 and 25.434.

Definition carried over unchanged; the term continued to describe a UTRAN node supporting the IP Transport Option.

Definition carried over unchanged; no revision to the glossary wording.

Definition carried over unchanged; no revision to the glossary wording.

Definition carried over unchanged; no revision to the glossary wording.

Definition carried over unchanged; no revision to the glossary wording.

Definition carried over unchanged; no revision to the glossary wording.

Definition carried over unchanged; no revision to the glossary wording.

Definition carried over unchanged; no revision to the glossary wording.

Definition carried over unchanged; no revision to the glossary wording.

Definition carried over unchanged; no revision to the glossary wording.

Definition carried over unchanged; no revision to the glossary wording.

Defining Specifications

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

SpecificationTitleRelease
TS 25.432 vj00 Iub NBAP Signalling Transport Specification Rel-19 read
TS 25.434 vj00 UTRAN Iub Interface Data Transport and Signalling Rel-19 read