Description
The IAB-node is a fundamental component of the Integrated Access and Backhaul (IAB) architecture introduced in 3GPP Release 16 for 5G NR. It acts as a relay node that simultaneously serves UEs (access) and connects to the network wirelessly (backhaul), using the same NR radio interface. This eliminates the need for a dedicated fiber backhaul to every base station, significantly reducing deployment costs and time, especially for dense urban or hard-to-reach areas.
Architecturally, an IAB-node comprises two logical functions: a UE function (IAB-UE) and a Distributed Unit (DU) function (IAB-DU). The IAB-UE connects to a parent node (either a donor or another IAB-node) via the NR Uu interface, while the IAB-DU serves child nodes and UEs. The IAB-node is managed by a Central Unit (CU) located at the IAB-donor, which controls the DU via the F1 interface. The CU/DU split allows centralized scheduling and mobility management, while the DU handles real-time functions.
The IAB-node supports both in-band and out-of-band relaying. In-band operation means the access and backhaul links share the same frequency band, requiring careful resource coordination to avoid interference. Out-of-band uses separate frequencies, simplifying interference management. The backhaul link can be established via NR Uu, and the IAB-node can be multi-hop, meaning it can connect through other IAB-nodes to reach the donor. This creates a tree topology rooted at the IAB-donor, which has a wired connection to the core network.
Key procedures for IAB-node operation include initial integration, where the IAB-UE performs cell search and random access to a parent node, followed by backhaul link setup and F1-AP establishment with the CU. The IAB-node also supports mobility (e.g., handover between parent nodes) and topology adaptation to maintain connectivity. Resource allocation for backhaul and access links is managed by the CU through centralized scheduling or distributed coordination, depending on the configuration.
The IAB-node is specified across multiple 3GPP specifications: TS 38.401 defines the overall architecture, TS 38.321 covers MAC procedures, TS 37.340 addresses multi-connectivity, and TS 23.501/23.401 detail core network aspects. The term has remained stable across Releases 16 to 20, with only minor editorial updates (e.g., reference number change in Rel-20). This consistency reflects the maturity of the IAB concept and its continued relevance in 5G-Advanced and beyond.
Purpose & Motivation
The IAB-node was created to address the challenge of providing ubiquitous high-capacity coverage in 5G networks without the prohibitive cost and logistical complexity of deploying fiber backhaul to every small cell or relay site. Traditional backhaul solutions, such as fiber or microwave, are expensive and time-consuming to install, especially in dense urban environments, historical sites, or rural areas. The IAB-node solves this by enabling wireless self-backhauling using the same NR spectrum, allowing rapid and flexible network densification.
Before IAB, relay nodes in LTE (e.g., Rel-10 relays) used separate backhaul links and were limited in flexibility and spectral efficiency. They often required dedicated resources and could not easily adapt to dynamic traffic conditions. The IAB architecture, with its CU/DU split and centralized control, allows for more efficient resource utilization, multi-hop topologies, and seamless integration with the 5G core. It also supports both in-band and out-of-band operation, giving operators deployment flexibility.
The IAB-node is particularly motivated by the need for cost-effective coverage extension in millimeter wave (mmWave) bands, where propagation is challenging and cell sizes are small. By using wireless backhaul, operators can deploy IAB-nodes on street furniture, buildings, or vehicles without trenching fiber. This accelerates 5G rollout and enables new use cases like temporary events, disaster recovery, and industrial IoT. The IAB-node thus represents a key enabler for scalable, high-performance 5G networks.
What changed in its specifications
The latest release-to-release comparison of specifications that define IAB-node. Each summary describes the whole specification, not only this term.
Rel-19 adds Disaster Roaming in EPS, which covers disaster-roaming procedures and attach, tracking area update and mobility signalling. It also adds Time Reference Information Distribution Indication to subscription data and the MME-to-eNB path, along with Store and Forward Satellite operation text.
Full comparison in TS 23.401 →Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.
Full comparison in TS 23.501 →Technology family
Base stations and RAN nodes · Radio Access Network
- Phase 1 BSC, BSS, BTS
- R99 Node B, RNC, RNS
- Rel-8 eNB, HeNB, HNB, HNB-GW
- Rel-10 DeNB, HeNB-GW, RN
- Rel-15 en-gNB, gNB, gNB-CU, gNB-CU-CP, gNB-CU-UP, gNB-DU, ng-eNB
- Rel-16 IAB-donor, IAB-DU, IAB-MT, IAB-node
- Rel-18 Mobile IAB-node
- IAB-node decomposed into IAB-DU
“The gNB-DU functionality on the IAB-node is also referred to as IAB-DU.” TS 38.300
- IAB-node decomposed into IAB-MT
“In addition to the gNB-DU functionality, the IAB-node also supports a subset of the UE functionality referred to as IAB-MT” TS 38.300
- IAB-node extended by Mobile IAB-node
“Mobile IAB supports the same functionality as IAB unless explicitly specified.” TS 38.300
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 5 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.
Rel-16 first specifies the IAB-node as a relay with an IAB-MT (UE) function and an IAB-DU function, providing NR wireless backhaul and access, in TS 38.401 and TS 23.501.
- “The IAB-node provides wireless backhaul to the downstream IAB-nodes and UEs via the network functionalities of the NR Uu interface (named IAB-DU function of IAB-node).” TS 38.401 v16.12.0
- “A relay node that supports wireless in-band and out-of-band relaying of NR access traffic via NR Uu backhaul links.” TS 23.501 v16.20.0
Rel-17 extends IAB-node behaviour with inter-CU topology adaptation, NR-DC with an F1-terminating donor, boundary IAB-nodes, and TNL address migration via MOBIKE and F1AP gNB-DU Configuration Update.
- “Boundary IAB-node: an IAB-node with one RRC interface terminating at a different IAB-donor-CU than the F1 interface.” TS 38.401 v17.10.0
- “the IAB-node may use MOBIKE (IETF RFC 4555 [29]) to migrate the IPsec tunnel to the new IP outer addresses” TS 38.401 v17.10.0
- “If the IAB-node establishes NR-DC before the establishment of F1-C connection, the MN decides whether the MN or the SN becomes the F1-terminating IAB-donor.” TS 38.401 v17.10.0
Rel-18 extends IAB-node to mobile IAB-nodes, adding integration phases, authorization handling, and F1/RRC-terminating donor roles, plus updated IAB-node authorization and de-registration handling.
- “the RRC-terminating IAB-donor-CU receives the authorization status of the mobile IAB-node from the 5GC.” TS 38.401 v18.7.0
- “After the F1 interface is set up, the mobile IAB-node can start serving UEs.” TS 38.401 v18.7.0
- “MBSR (IAB gNB-DU) can use IAB-node integration procedure or inter-IAB-donor gNB mobility procedure to integrate into the serving PLMN to provide service.” TS 23.501 v18.12.0
Rel-19 management specs add requirements, use cases and procedures for IAB-node: location-based configuration via notifications and IP configuration for OAM connectivity when connecting to the management system, including during mobility.
- “REQ_IAB_CM_1: 3GPP management system should have the capability to configure IAB-node configuration based on IAB-node location.” TS 28.531 v19.2.0
- “the MnS producer for IAB-node shall provide location information with IAB-node indication via notifications to 3GPP management system” TS 28.314 v19.2.0
- NRM changes to support IAB-node management TS 28.541CR1598
Management of IAB-node was reworked: mobility text now says IAB-node generally (not only 'Mobile IAB') uses location-based configuration at power-up, with location notifications, and an NCI reconfiguration CR was approved.
- “IAB-node should use configuration based on its location at power up and in mobile scenarios as specified in 3GPP TS 38.401 [18].” TS 28.531 v20.1.0
- Rel-20 CR Update to management of IAB-node for NCI reconfiguration TS 28.540CR0052
- “the MnS producer for IAB-node needs to provide location information with IAB-node indication via notifications to 3GPP management system” TS 28.531 v20.1.0
Defining Specifications
3GPP specifications that define or reference IAB-node, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.401 vk10 | Evolved Packet System Architecture | Rel-20 read |
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 36.423 vj10 | X2 Application Protocol (X2AP) Specification | Rel-19 read |
| TS 37.340 vj30 | Overview of Multi-Connectivity Operation using E-UTRA and NR | Rel-19 read |
| TS 38.321 vj40 | NR MAC Protocol Specification | Rel-19 read |