Description
IAB topology is a fundamental concept in 3GPP Integrated Access and Backhaul (IAB) networks, introduced in Release 17. It defines the logical grouping of IAB-nodes and IAB-donor-DUs that are connected to and managed by a single IAB-donor-CU (Central Unit). In an IAB network, the IAB-donor is a base station that has a wired connection to the core network and provides backhaul to other IAB-nodes. The IAB-donor consists of a Central Unit (CU) and one or more Distributed Units (DUs). The IAB-donor-CU is responsible for the control plane (RRC) and user plane (PDCP) functions, while the DUs handle lower layers. The IAB topology encompasses all IAB-nodes and IAB-donor-DUs that have their F1 interface (between CU and DU) and/or RRC connections terminated at the same IAB-donor-CU.
The topology is established through the IAB-node's initial access and backhaul link establishment procedures. When an IAB-node powers on, it performs cell search and selects a parent IAB-node or IAB-donor to connect to. It then establishes an RRC connection with the IAB-donor-CU and sets up F1 connections. The IAB-donor-CU maintains a topology table that tracks all connected nodes and their relationships. This topology information is used for routing and mobility management. The topology can be multi-hop, where an IAB-node connects to another IAB-node, forming a tree or mesh structure. The IAB-donor-CU is the root of the topology and manages the entire tree.
The IAB topology is defined in 3GPP specifications such as TS 38.300 (NR and NG-RAN Overall Description) and TS 38.401 (NG-RAN Architecture Description). These specifications describe the architecture, interfaces, and procedures for establishing and maintaining the topology. The topology is dynamic and can change due to node mobility, link failures, or new node additions. The IAB-donor-CU is responsible for topology adaptation, including path switching and route updates, to ensure continuous connectivity.
The concept of IAB topology is crucial for network planning and operation. It allows the network to manage resources efficiently, balance load, and provide seamless mobility. For example, if an IAB-node moves, the topology may need to be updated to reflect the new parent-child relationships. The IAB-donor-CU can use topology information to make handover decisions and to allocate resources. The topology also affects interference management, as nodes in the same topology may coordinate transmissions to avoid cross-link interference.
In terms of evolution, the definition of IAB topology was introduced in Release 17 and has remained unchanged in Releases 18 and 19. This stability indicates that the core concept has been well-defined and is expected to persist as IAB technology matures. Future releases may introduce enhancements such as support for mobile IAB-nodes and more complex topologies, but the fundamental definition is likely to remain.
Purpose & Motivation
The IAB topology concept was created to provide a clear framework for managing the complex relationships in an IAB network. In traditional cellular networks, base stations are connected via fixed backhaul, and the topology is static. With IAB, backhaul links are wireless and can change dynamically, creating a need for a logical grouping that simplifies management. The IAB topology defines the scope of control for an IAB-donor-CU, enabling it to manage all nodes under its domain as a single entity. This solves the problem of distributed control and ensures consistent resource allocation, mobility management, and interference coordination. It also facilitates network planning by allowing operators to design IAB deployments as clusters rooted at a donor. The concept addresses the limitations of previous ad-hoc relay approaches, where each relay was managed independently, leading to inefficiencies. By defining a topology, 3GPP enables scalable and efficient IAB deployments for 5G and beyond.
What changed in its specifications
The latest release-to-release comparison of specifications that define IAB topology. Each summary describes the whole specification, not only this term.
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 →Rel-19 adds Wireless Access Backhaul (WAB) architecture and node procedures to TS 38.401. It also adds multi-hop Layer-2 sidelink UE-to-Network relay with First, Intermediate and Last U2N Relay UE roles. Ambient IoT support is added, including A-IoT session contexts and AMF connectivity.
Full comparison in TS 38.401 →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.
Defining Specifications
3GPP specifications that define or reference IAB topology, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 38.300 vj40 | NR and NG-RAN Overall Description | Rel-19 read |
| TS 38.401 vj30 | NG-RAN Architecture Description | Rel-19 read |