Description
The IAB Distributed Unit (IAB-DU) is one of the two key functional components of an Integrated Access and Backhaul (IAB) node, the other being the IAB-MT (Mobile Termination). The IAB-DU is responsible for the radio access network functionality towards its 'child' nodes. From the perspective of a User Equipment (UE) or a downstream IAB node's IAB-MT, the IAB-DU appears and operates identically to a standard gNB Distributed Unit in a 5G network. It terminates the radio interface layers up to the Radio Link Control (RLC) layer, handling physical layer processing, Medium Access Control (MAC) scheduling, and radio resource management for its served cell(s).
Architecturally, the IAB-DU is controlled by a Central Unit (CU) located in the IAB donor node. This control relationship is established over the F1 interface, specifically the F1-C (Control plane) and F1-U (User plane). However, unlike a traditional fronthaul link, this F1 connection is not carried over a direct fiber or microwave link. Instead, it is tunneled through the wireless backhaul path established by the IAB-MT component of the same IAB node and potentially other upstream IAB nodes. The F1-AP messages and user plane data are encapsulated and routed over Backhaul RLC channels, using the Backhaul Adaptation Protocol (BAP) for hop-by-hop forwarding.
The IAB-DU's operation is tightly coordinated with the IAB-MT to avoid self-interference and to optimize the overall capacity of the node. The IAB donor CU provides a resource configuration that dictates when the IAB-DU can transmit/receive to its children (access links) and when the IAB-MT must transmit/receive to its parent (backhaul link). This configuration defines a pattern of 'soft' cells, where the IAB-DU's cell is available only during specific time resources if TDM (Time Division Multiplexing) is used. The IAB-DU performs all standard gNB-DU functions like broadcasting system information, random access channel (RACH) handling, scheduling of uplink and downlink data, and HARQ processes, but within the constraints of the resources allocated to it by the donor CU.
Purpose & Motivation
The IAB-DU exists to provide the essential radio access point functionality within a wireless IAB node, enabling the creation of a multi-hop, self-backhauling network without requiring a separate, dedicated access radio unit. Its purpose is to decouple the radio access function from the need for a direct, wired connection to the core network. By integrating a standard-compliant gNB-DU into the IAB node, the network can present a normal 5G radio interface to end-user devices, ensuring full UE compatibility and leveraging all existing NR features for access.
This design solves the problem of how to make a relay node appear as a native part of the 5G RAN to the devices it serves. Previous relay solutions sometimes required specialized UE behavior or created non-transparent links. The IAB-DU, by conforming to the 3GPP-defined gNB-DU specification, ensures transparency and interoperability. The motivation stems from the need for cost-effective network densification; the IAB-DU allows an operator to drop a node that immediately starts serving traffic, using its wireless backhaul (via the co-located IAB-MT) to reach the network core.
Furthermore, separating the DU function from the CU (in the donor) allows for centralized coordination and efficient resource pooling across the entire IAB topology. The donor CU can dynamically adjust resources between the IAB-DU (for access) and the IAB-MT (for backhaul) of multiple nodes based on traffic demand, optimizing the capacity of the entire wireless mesh. The IAB-DU is thus a critical enabler for the flexible, rapid, and cost-efficient deployment of 5G small cells envisioned for urban environments and industrial IoT campuses.
What changed in its specifications
The latest release-to-release comparison of specifications that define IAB-DU. Each summary describes the whole specification, not only this term.
Rel-19 adds NTN-for-IoT Phase 3 and inter-RAT mobility from E-UTRAN to NR NTN, plus LTE-based 5G Broadcast Phase 2 changes. It also adds IMS disaster-roaming access barring, NTN-for-NR Phase 3 fields, and NR RRM Phase 5 items.
Full comparison in TS 36.331 →Rel-19 adds LTM cell-switch and MIMO Phase 5 identifiers to TS 38.331, plus multi-hop sidelink U2N relay clauses and IEs. It also adds OD-SIB1 and adaptive SSB for RRM, SIB27 for NTN, and SBFD identifiers.
Full comparison in TS 38.331 →Technology family
Base stations and RAN nodes · Radio Access Network
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 sourcesDocumented 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.
IAB-DU is specified for the first time in Rel-16, with F1AP procedures for configuring IAB-DU resources and RF conformance requirements for the IAB-DU in 38.174 and 38.176.
- “IAB-DU: as defined in TS 38.300 [6].” TS 38.473 v16.23.0
- “All considerations of gNB-DU in this specification also apply to the IAB-DU and IAB-donor-DU, unless stated otherwise.” TS 38.473 v16.23.0
- “IAB-DU channel bandwidth: RF bandwidth supporting a single IAB-DU RF carrier with the transmission bandwidth configured in the uplink or downlink” TS 38.176-1 v16.11.0
Rel-17 adds IAB-DU requirements for simultaneous operation with IAB-MT, including a 3µs timing error limit, simultaneous-operation conformance testing, and IAB-DU-related F1AP congestion and RRC delivery behaviour.
- “the timing error between transmission timing of IAB-DU and IAB-MT shall not exceed 3µs.” TS 38.174 v17.10.0
- “IAB-DU and IAB-MT can be configured as IAB Simultaneous Operation based on declaration.” TS 38.174 v17.10.0
- “If the gNB-DU is an IAB-DU or an IAB-donor-DU, and if the IAB Congestion Indication IE is present” TS 38.473 v17.16.0
Rel-18 extends IAB-DU to mobile IAB (mIAB-DU): test and performance requirements apply to mIAB-DU, and F1 procedures cover mobile IAB-DU migration and co-location discovery.
- “Unless otherwise stated, the performance requirement tests for IAB-DU shall apply to mIAB-DU (see D.204 in Table 4.6-1).” TS 38.176 v18.10.0
- “Mobile IAB-DU: IAB-DU function on the mobile IAB-node as defined in TS 38.300 [30]” TS 38.176 v18.10.0
- “the gNB-CU shall, if supported, consider the F1 setup outcome of the target logical gNB-DU co-located with the gNB-DU” TS 38.473 v18.11.0
Defining Specifications
3GPP specifications that define or reference IAB-DU, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 36.331 vj40 | E-UTRA Radio Resource Control (RRC) Protocol | Rel-19 read |
| TS 38.174 vk00 | NR Integrated Access and Backhaul Requirements | Rel-20 read |
| TS 38.176 vj40 | IAB Conformance Testing | Rel-19 read |
| TS 38.331 vj40 | NR Radio Resource Control (RRC) | Rel-19 read |
| TS 38.420 vj10 | Introduction to Xn interface specifications | Rel-19 read |
| TS 38.809 vg60 | IAB Radio Transmission & Reception Background | Rel-16 read |