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

Glossary term · Radio Access Network

IAB-donor-CU

Integrated Access and Backhaul Donor Central Unit

Radio Access Network →

IAB-donor-CU is a gNB-CU of an IAB-donor that terminates the F1 interface towards IAB-nodes and the IAB-donor-DU, anchoring the control and user plane of the IAB topology.

Introduced
Rel-16
Where
Radio Access Network › NG-RAN (5G)
Specifications
6 specs
IAB-donor-CU Description Purpose What changed Neighbours Specifications

Description

The IAB-donor-CU is the central unit (CU) function of an Integrated Access and Backhaul (IAB) donor gNB. In the IAB architecture defined by 3GPP, the donor node is split into a central unit (IAB-donor-CU) and one or more distributed units (IAB-donor-DU). The IAB-donor-CU terminates the F1 interface towards the IAB-nodes and towards the IAB-donor-DU, meaning it hosts the F1-C (control plane) and F1-U (user plane) endpoints for all downstream IAB-DUs. It is responsible for the RRC, SDAP and PDCP layers of the donor gNB, and it manages the IAB topology by configuring the BAP (Backhaul Adaptation Protocol) layer and the F1 connections of the IAB-nodes.

Architecturally, the IAB-donor-CU sits at the top of the IAB tree. It communicates with the IAB-donor-DU over the F1 interface, and with each IAB-node's DU function over the F1 interface as well. The IAB-node's mobile termination (MT) connects to the parent node's DU, while its DU connects to the CU. The IAB-donor-CU thus acts as the common CU for the entire IAB topology, enabling centralized control of radio resource management, mobility, and backhaul routing. It also hosts the BAP entity that handles routing and bearer mapping for the backhaul links.

The IAB-donor-CU is defined in TS 38.401 (NG-RAN architecture) and TS 38.300 (NR overall description). Its F1 interface procedures are specified in TS 38.470 (general aspects) and TS 38.473 (F1AP). Security aspects, including the protection of the F1 interface and the handling of IAB-node credentials, are covered in TS 33.501. The management of the IAB-donor-CU, including its configuration and the configuration of the IAB topology, is described in TS 28.541 (5G NRM).

In operation, the IAB-donor-CU performs several key functions. It establishes and maintains the F1 connections with each IAB-node's DU, using F1AP procedures such as F1 Setup and UE Context Management. It configures the BAP layer of the IAB-nodes via RRC signalling, defining the backhaul routing tables and bearer mappings. It manages the integration of new IAB-nodes into the topology, including the assignment of BAP addresses and the setup of the necessary backhaul bearers. It also handles mobility events, such as the handover of an IAB-node's MT from one parent to another, by coordinating with the involved DUs and updating the F1 connections accordingly.

The IAB-donor-CU is a logical node that can be deployed in a centralized location, such as a regional data center, or co-located with the IAB-donor-DU. Its separation from the DU allows for flexible deployment and centralized control, which is particularly beneficial for dense deployments where many IAB-nodes need to be managed. The CU-DU split also enables the use of different vendors for the CU and DU, as long as the F1 interface is standardized. The IAB-donor-CU is a key enabler of the IAB feature, which allows operators to extend coverage and capacity without the need for a full fiber backhaul to every base station.

Purpose & Motivation

The IAB-donor-CU exists to provide a centralized control point for the IAB topology, enabling efficient management of backhaul resources and mobility. In traditional RAN deployments, each base station requires a dedicated backhaul connection, typically fiber, which is costly and time-consuming to deploy. IAB addresses this by using wireless backhaul for some nodes, but this introduces the need for centralized coordination of the wireless backhaul links to avoid interference and ensure reliable connectivity. The IAB-donor-CU solves this by acting as the common CU for all IAB-nodes, allowing it to manage the BAP routing, allocate resources, and handle mobility events in a coordinated manner.

Before IAB, relay nodes (such as those in LTE) had limited capabilities and often required separate management and backhaul configuration. The IAB architecture, introduced in Release 16, integrates the relay functionality into the NR framework, using the same CU-DU split and F1 interface as regular gNBs. The IAB-donor-CU is the entity that makes this integration possible by terminating the F1 interface towards the IAB-nodes and providing the necessary control functions. It also enables the use of advanced features such as multi-hop backhaul, where an IAB-node can connect to another IAB-node, forming a tree topology. The IAB-donor-CU manages this tree, ensuring that each node has a route to the donor and that the backhaul links are properly configured.

In summary, the IAB-donor-CU was created to meet the need for a scalable, flexible, and standardized way to manage wireless backhaul in 5G networks. It leverages the CU-DU split and the F1 interface to provide centralized control, while allowing distributed deployment of the IAB-nodes. This enables operators to quickly extend coverage in areas without fiber, such as street furniture, lampposts, and buildings, and to improve capacity in hotspots.

What changed in its specifications

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

TS 28.541Rel-18 → Rel-19

Rel-19 adds the A-IoT area, AIOTF and ADM function classes, plus the AIOT2 interface to TS 28.541. It also adds ProSe UE-to-UE relay role attributes for L2/L3, end, intermediate and multihop roles, and the NRECMappingRule IOC for energy efficiency criteria.

Full comparison in TS 28.541 →
TS 33.501Rel-18 → Rel-19

Rel-19 TS 33.501 adds roaming and inter-PLMN indirect communication authorization, fast re-authentication for non-3GPP mobility, and AI/ML security clauses for positioning and federated learning. It also adds NPN security, NRF access token key retrieval, LTM security, and monitoring-of-signalling-traffic protection.

Full comparison in TS 33.501 →

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-16 Initial

Initial definition introduced with the IAB architecture. The IAB-donor-CU is defined as the gNB-CU of an IAB-donor, terminating the F1 interface towards IAB-nodes and IAB-donor-DU. This established the CU as the central control entity for the IAB topology, enabling centralized management of backhaul and access links.

The definition text carried over unchanged from Rel-16. The IAB-donor-CU continued to serve as the F1 termination point for IAB-nodes and the IAB-donor-DU, with no changes to its fundamental role or architecture.

The definition text carried over unchanged from Rel-16. The IAB-donor-CU remained the gNB-CU of an IAB-donor, terminating the F1 interface towards IAB-nodes and IAB-donor-DU, with no modifications to its definition.

The definition text carried over unchanged from Rel-16. The IAB-donor-CU continued to be defined as the gNB-CU of an IAB-donor, terminating the F1 interface towards IAB-nodes and IAB-donor-DU, with no changes to its wording.

The definition was revised to a reference: 'As defined in TS 38.401 [78].' This change replaces the explicit description with a pointer to the NG-RAN architecture specification, likely to avoid duplication and maintain a single source of truth. The technical meaning remains the same, but the definition now relies on TS 38.401 for the detailed description.

Defining Specifications

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

SpecificationTitleRelease
TS 28.541 vk41 5G Network Resource Model Stage 2/3 Rel-20 read
TS 33.501 vk30 5G Security Architecture Rel-20 read
TS 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read
TS 38.401 vj30 NG-RAN Architecture Description Rel-19 read
TS 38.470 vj20 F1 Interface Specification for NG-RAN Rel-19 read
TS 38.473 vj40 F1 Application Protocol (F1AP) Rel-19 read