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

Glossary term · Radio Access Network

IAB-donor-DU

Integrated Access and Backhaul Donor Distributed Unit

Radio Access Network →

IAB-donor-DU is the gNB-DU of an IAB-donor that hosts the IAB BAP sublayer and provides wireless backhaul to IAB-nodes, acting as the root of the IAB backhaul tree.

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

Description

The IAB-donor-DU is the distributed unit (DU) function of an Integrated Access and Backhaul (IAB) donor gNB. In the IAB architecture, the donor node is split into a central unit (IAB-donor-CU) and one or more distributed units (IAB-donor-DU). The IAB-donor-DU hosts the IAB Backhaul Adaptation Protocol (BAP) sublayer, as defined in TS 38.340, and provides wireless backhaul to IAB-nodes. It is the root of the IAB backhaul tree, connecting the IAB topology to the core network via the donor's CU and the NG interface.

Architecturally, the IAB-donor-DU is responsible for the lower layers of the radio protocol stack, including RLC, MAC, and PHY, for both the access and backhaul links. It communicates with the IAB-donor-CU over the F1 interface, and with child IAB-nodes over the NR Uu interface. The IAB-donor-DU's BAP entity handles the routing of backhaul packets, forwarding them between the CU and the child IAB-nodes based on the BAP routing identifiers. It also manages the radio resources for the backhaul links, including scheduling and link adaptation.

The IAB-donor-DU is defined in TS 38.401 (NG-RAN architecture) and TS 38.300 (NR overall description). The BAP protocol is specified in TS 38.340. The F1 interface procedures are in TS 38.470 and TS 38.473. Security aspects are covered in TS 33.501, and management aspects in TS 28.541.

In operation, the IAB-donor-DU performs several key functions. It establishes the backhaul link with child IAB-nodes, including the initial access and the setup of the BAP layer. It routes backhaul packets based on the BAP routing table configured by the IAB-donor-CU, ensuring that packets reach the correct destination IAB-node. It manages the radio resources for the backhaul links, allocating time-frequency resources and handling interference. It also supports the integration of new IAB-nodes by providing the necessary synchronization and broadcast signals.

The IAB-donor-DU is typically co-located with the IAB-donor-CU, but it can also be deployed separately. Its separation from the CU allows for flexible deployment, such as placing the DU at the cell site while the CU is in a centralized location. The IAB-donor-DU is a key enabler of the IAB feature, as it provides the wireless backhaul connection that allows IAB-nodes to connect to the network without a wired backhaul.

Purpose & Motivation

The IAB-donor-DU exists to provide the wireless backhaul anchor point for the IAB topology. In traditional RAN deployments, each base station requires a wired backhaul connection, which is expensive and time-consuming to deploy. IAB addresses this by using wireless backhaul for some nodes, but this requires a donor node that can connect the wireless backhaul to the core network. The IAB-donor-DU serves this role by hosting the BAP layer and providing the radio interface for the backhaul links. It allows IAB-nodes to connect wirelessly to the network, extending coverage and capacity without the need for fiber to every site.

Before IAB, relay nodes 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-DU is the entity that provides the wireless backhaul connection, using the BAP protocol to route packets between the CU and the IAB-nodes. 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-DU manages the root of this tree, ensuring that all backhaul traffic is properly routed.

In summary, the IAB-donor-DU was created to meet the need for a scalable, flexible, and standardized way to provide wireless backhaul in 5G networks. It leverages the CU-DU split and the BAP protocol to provide a wireless anchor point, 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-DU. Each summary describes the whole specification, not only this term.

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

Rel-19 adds multi-hop L2 UE-to-Network relay for NR sidelink as the largest item. It also adds low-power wake-up signal and receiver (LP-WUS/WUR) text, on-demand SSB and SIB1 for network energy savings, and sub-band full duplex for TDD carriers.

Full comparison in TS 38.300 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-16 2 changes
  • Correction on the identification of IAB-donor-DU TS 38.473CR0666
  • Correction on BAP address configuration for IAB-donor-DU TS 38.473CR0722

Defining Specifications

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

SpecificationTitleRelease
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.340 vj00 Backhaul Adaptation Protocol (BAP) Specification 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