Description
Integrated Access and Backhaul (IAB) is a 3GPP Rel-17 feature that allows a gNB to use the same spectrum for both access links to UEs and backhaul links to other IAB nodes, forming a multi-hop relay tree. The IAB-donor is the node at the root of this tree that connects to the core network. In a multi-hop topology, an IAB-node may be served by more than one IAB-donor, or may move between donors. The F1-terminating IAB-donor is the donor that terminates the F1 interface for a given IAB-node, meaning it hosts the CU-CP and CU-UP functions that manage that node's DU.
The F1 interface, defined in TS 38.473, connects a gNB-CU to a gNB-DU. For IAB, the IAB-node contains a DU that is managed by a CU hosted in the IAB-donor. When an IAB-node is at the boundary between two donors, or when it is a mobile IAB-node (e.g., mounted on a vehicle), the F1 termination point must be clearly defined to avoid ambiguity in RRC and F1AP signaling. The F1-terminating IAB-donor is that authoritative donor. It handles UE context management, bearer setup, and mobility procedures for UEs served by the IAB-node.
The concept is specified in TS 38.401 (NG-RAN architecture), TS 38.420 (IAB architecture), TS 38.423 (XnAP), and TS 38.473 (F1AP). It enables topologies where an IAB-node has redundant backhaul paths to multiple donors, supporting resilience and mobility. For mobile IAB-nodes, the F1-terminating donor may change as the node moves, requiring handover of the F1 termination and coordination between donors over the Xn interface.
In Release 17 the term was defined by reference to TS 38.401. From Release 18 onward the definition was rewritten to explicitly state that it refers to the IAB-donor that terminates F1 for the boundary IAB-node or a mobile IAB-node, reflecting the introduction of mobile IAB in that release.
Purpose & Motivation
The F1-terminating IAB-donor concept solves the ambiguity of which donor owns the F1 connection when an IAB-node has links to multiple donors or is mobile. Without a clear termination point, RRC and F1AP procedures could conflict, leading to inconsistent UE context management. By designating a single terminating donor, 3GPP ensures deterministic control-plane behavior, enables donor redundancy for resilience, and supports mobile IAB-nodes that change attachment points. This is essential for deploying IAB in dense urban, indoor, and vehicular scenarios where multi-hop and multi-donor topologies are common.
What changed in its specifications
The latest release-to-release comparison of specifications that define F1-terminating IAB-donor. Each summary describes the whole specification, not only this term.
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 →Rel-19 adds OD-SIB1 configuration provision messages and TA Information Transfer, LTM Cancel and CSI-RS Coordination procedures to TS 38.423. It also adds SON/MDT data collection with CLI Indication and SCG Failure Indication, XR IEs for ECN marking and PDU Set QoS, and RedCap LP-WUS paging IEs.
Full comparison in TS 38.423 →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 F1-terminating IAB-donor, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 38.401 vj30 | NG-RAN Architecture Description | Rel-19 read |
| TS 38.420 vj10 | Introduction to Xn interface specifications | Rel-19 read |
| TS 38.423 vj40 | NG-RAN Xn Application Protocol | Rel-19 read |
| TS 38.473 vj40 | F1 Application Protocol (F1AP) | Rel-19 read |