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

Glossary term · Radio Access Network

Child node

Child Node (IAB)

Radio Access Network →

Child node is an IAB-node that is the next-hop neighbor of an IAB-DU or IAB-donor-DU in the Integrated Access and Backhaul topology, forming the downstream branch of the backhaul tree.

Introduced
Rel-16
Where
Radio Access Network › NG-RAN (5G)
Specifications
2 specs
Child node Description Purpose What changed Neighbours Specifications

Description

In the context of Integrated Access and Backhaul (IAB), a child node is defined as an IAB-node that is the next-hop neighbor of an IAB-DU or an IAB-donor-DU. The term describes the hierarchical relationship between nodes in the IAB topology, where the network forms a tree structure rooted at the IAB-donor. The child node is itself an IAB-node, meaning it provides both access and backhaul functionality. This parent-child relationship is fundamental to how IAB networks route traffic and manage topology.

The IAB architecture consists of an IAB-donor, which is a network node that provides the connection to the core network, and one or more IAB-nodes, which are relay nodes that extend coverage and capacity. Each IAB-node contains a Distributed Unit (DU) and a Mobile Termination (MT). The IAB-DU provides the access link to User Equipment (UE) and the backhaul link to child nodes, while the IAB-MT connects to the parent node's DU. The child node, therefore, is the downstream neighbor that connects to the parent's IAB-DU. The parent node's IAB-DU serves the child node's IAB-MT, establishing the backhaul link. This creates a multi-hop topology where traffic from the child node is relayed through the parent node towards the IAB-donor and the core network.

The child node concept is essential for topology management and routing in IAB networks. The parent node is responsible for allocating resources to the child node, managing the backhaul link, and handling mobility events. The child node, in turn, may have its own child nodes, forming a tree. The network must maintain a clear understanding of these relationships to route packets correctly, manage interference, and perform handovers when the child node moves. The specifications 37.340 and 38.300 define the overall architecture and the IAB-specific aspects, including the parent-child relationships and the procedures for establishing and maintaining the backhaul links.

From an operational perspective, the child node is a key element in the self-backhauling capability of IAB. It allows the network to extend coverage to areas where fiber backhaul is not available, by using wireless backhaul links between nodes. The child node's IAB-MT connects to the parent's IAB-DU, and the child node's IAB-DU serves its own UEs and child nodes. This creates a flexible, scalable network that can be deployed quickly and cost-effectively. The parent-child relationship also enables advanced features such as topology adaptation, where the network can reconfigure the tree structure to optimize performance or recover from failures.

In summary, the child node is a fundamental building block of the IAB topology, representing the downstream neighbor of an IAB-DU or IAB-donor-DU. It enables multi-hop wireless backhaul, extends network coverage, and supports flexible deployment scenarios. The concept is defined in 3GPP specifications 37.340 and 38.300 and has remained stable across releases from Rel-16 to Rel-19, reflecting its maturity and importance in 5G NR networks.

Purpose & Motivation

The child node concept exists to enable the hierarchical, multi-hop topology of Integrated Access and Backhaul networks. IAB was introduced to address the challenge of deploying dense 5G networks without the need for fiber backhaul to every base station. By defining parent-child relationships, the network can extend coverage and capacity using wireless backhaul links, where each child node relays traffic to its parent and ultimately to the IAB-donor. This solves the problem of backhaul scarcity and high deployment costs, particularly in urban environments where fiber is expensive or impractical to install.

Historically, backhaul has been a major bottleneck for cellular network densification. Traditional small cells require dedicated wired backhaul, which limits where they can be deployed and increases operational costs. IAB, introduced in Rel-16, provides a wireless self-backhauling solution that leverages the same spectrum for both access and backhaul. The child node concept is central to this architecture, as it defines the relationships between nodes and enables the network to manage the topology dynamically. Before IAB, relay nodes (introduced in earlier releases) provided some self-backhauling capabilities, but they were limited in scalability and flexibility. IAB with its parent-child hierarchy offers a more robust and scalable solution.

The child node concept also addresses the need for topology management and mobility in multi-hop networks. As child nodes can move or be reconfigured, the network must track these relationships to ensure proper routing and resource allocation. The definition of child node in 3GPP specifications provides a clear, standardized way to describe these relationships, enabling interoperability and consistent implementation across vendors. Its stability from Rel-16 to Rel-19 indicates that the fundamental concept has been well understood and effectively standardized.

What changed in its specifications

The latest release-to-release comparison of specifications that define Child node. Each summary describes the whole specification, not only this term.

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

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-16 Initial

Initial definition of child node as the IAB-DU's and IAB-donor-DU's next-hop neighbor node, where the child node is also an IAB-node, establishing the hierarchical parent-child topology for IAB in NR.

The definition carried over unchanged from Rel-16; no textual revision to the child node concept.

The definition carried over unchanged from Rel-16; the concept remained stable.

The definition carried over unchanged from Rel-16; no change to the child node description.

Defining Specifications

3GPP specifications that define or reference Child node, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 37.340 vj30 Overview of Multi-Connectivity Operation using E-UTRA and NR Rel-19 read
TS 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read