Description
The parent node is a fundamental concept in 3GPP's Integrated Access and Backhaul (IAB) architecture, introduced in Release 16. IAB allows a radio access network to be built using wireless backhaul links instead of, or in addition to, fibre, which is attractive for dense deployments and for extending coverage cheaply. In IAB, an IAB-node contains two logical functions: an IAB-MT (Mobile Termination), which behaves like a UE towards its upstream neighbour, and an IAB-DU (Distributed Unit), which serves downstream UEs and child IAB-nodes. The parent node is the node that the IAB-MT connects to on its upstream side — that is, the next hop towards the IAB-donor.
A parent node can be either another IAB-node (in a multi-hop chain or tree) or an IAB-donor-DU, which is the DU part of the IAB-donor that terminates the backhaul at the core-network side. The relationship is directional: from the perspective of a given IAB-node, its parent is upstream; the nodes it serves are its child nodes. The IAB-donor (comprising a CU and one or more DUs) sits at the root of the topology. The parent node provides the backhaul link — the radio connection over which the IAB-MT's traffic is carried — and is responsible for scheduling and radio resource management on that link.
Operationally, the parent node plays a key role in IAB integration and topology management. When an IAB-node powers on or moves, it performs cell selection and attaches its IAB-MT to a suitable parent, similar to how a UE selects a cell. The parent then becomes the anchor for the IAB-node's backhaul. The IAB-donor-CU is informed of the topology and configures routes and bearers across the multi-hop path. Because IAB-nodes can be fixed or mobile (mobile IAB was added in Release 18), the parent relationship can change over time through handover or topology adaptation, and the network must manage these changes without disrupting service.
The parent node concept also underpins routing and bearer mapping. F1-AP and related interfaces carry configuration between the IAB-donor-CU and the IAB-DUs, while the backhaul adaptation protocol (BAP) routes packets hop-by-hop across parent-child links. Each hop, including the one to the parent, has its own radio link with its own scheduling, so the parent node is responsible for allocating resources on the backhaul link and for handling the corresponding HARQ and link adaptation. The parent node is therefore both a topological concept and an operational one: it determines where an IAB-node's traffic goes and who schedules it.
The specifications covering the parent node include 38.300 (NR overall architecture), 37.340 (multi-connectivity and IAB architecture), and 38.174/38.176 (IAB radio protocols and relay aspects). The term was refined in Release 18 to explicitly include mobile IAB-MTs, reflecting the introduction of mobile IAB nodes such as those mounted on vehicles or drones. In Release 20 the wording was revised again, notably referring to an 'IAB-donor' rather than 'IAB-donor-DU' in the quoted definition, reflecting ongoing editorial alignment of the architecture descriptions.
Purpose & Motivation
The parent node concept exists because IAB networks are multi-hop trees rather than flat star topologies. To route traffic from an IAB-node to the core network, every node needs an unambiguous upstream neighbour, and the network needs a term to describe that relationship for configuration, routing, and mobility. Before IAB, small cells required dedicated fibre or microwave backhaul, which is expensive and slow to deploy in dense urban or hard-to-reach areas. IAB replaces that with wireless backhaul, but wireless multi-hop topologies need explicit parent-child relationships so that the donor can build routes, manage resources hop-by-hop, and adapt the topology when links change. The parent node term provides that anchor: it identifies the next hop towards the donor, enables the BAP routing and F1-AP configuration to work across hops, and supports topology adaptation and, from Release 18, mobility of IAB-nodes. It is the IAB equivalent of the 'serving cell' concept for UEs, adapted to a network of relays.
What changed in its specifications
The latest release-to-release comparison of specifications that define Parent node. Each summary describes the whole specification, not only this term.
Rel-19 adds to TS 37.340 data collection for SON/MDT in NR standalone and MR-DC Phase 4. It covers conditional PSCell addition or change (CPAC/S-CPAC) failure detection and root cause analysis in MN and SN nodes.
Full comparison in TS 37.340 →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
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 Parent node, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 37.340 vj30 | Overview of Multi-Connectivity Operation using E-UTRA and NR | 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.300 vj40 | NR and NG-RAN Overall Description | Rel-19 read |