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

Glossary term · Radio Access Network

Mobile IAB-node

Mobile Integrated Access and Backhaul Node

Radio Access Network →

Mobile IAB-node is a RAN node that supports NR access links to UEs and an NR backhaul link to a parent node, can conduct physical mobility across the RAN area, and corresponds to the MBSR function in 5GC.

Introduced
Rel-18
Where
Radio Access Network › NG-RAN (5G)
Specifications
10 specs
Mobile IAB-node Description Purpose What changed Neighbours Specifications

Description

The Mobile IAB-node is a RAN node introduced in 3GPP Release 18 that extends the concept of Integrated Access and Backhaul (IAB) to mobile scenarios. Like a conventional IAB-node, it provides NR access links to User Equipment (UEs) and uses an NR backhaul link to connect to a parent node (either a donor gNB or another IAB-node). However, unlike a fixed IAB-node, the Mobile IAB-node is capable of physical mobility across the RAN area. This means it can move and change its parent node, enabling flexible deployment in scenarios such as vehicles, drones, or temporary events. The Mobile IAB-node function in 3GPP 38-series specifications corresponds to the Mobile Base Station Relay (MBSR) function defined in TS 23.501, ensuring alignment between RAN and core network specifications.

Architecturally, the Mobile IAB-node consists of a Distributed Unit (DU) and a Mobile Termination (MT). The DU serves UEs via the access link, while the MT communicates with the parent node via the backhaul link. The MT is responsible for establishing and maintaining the wireless backhaul connection, including mobility procedures such as cell selection/reselection and handover. The Mobile IAB-node uses the same procedures and behaviors as a fixed IAB-node, unless explicitly stated otherwise in the specifications. This reuse minimizes complexity and leverages the existing IAB framework. Key procedures include integration with the core network via the donor gNB, which hosts the Central Unit (CU) and provides connectivity to the 5G Core (5GC). The Mobile IAB-node's DU is controlled by the CU through the F1 interface, and the MT is managed by the CU via RRC signaling.

Mobility is a critical aspect of the Mobile IAB-node. The node can move within the RAN area and may change its parent node as it moves. This requires enhanced mobility procedures, such as mobile IAB-specific cell selection and handover mechanisms, to ensure service continuity. The specifications (e.g., TS 38.300, 38.331, 38.340, 38.413, 38.420, 38.423, 38.473) define the necessary signaling and protocols to support this mobility, including updates to RRC, NGAP, XnAP, and F1AP. For example, the Mobile IAB-node may need to perform a handover of its MT to a new parent node, and the network must manage the associated context and bearer updates. The MBSR function in the core network handles the registration and session management for the Mobile IAB-node, treating it as a special type of UE for mobility purposes.

The Mobile IAB-node is particularly useful in scenarios where deploying fixed infrastructure is challenging or cost-prohibitive. For instance, it can be mounted on a bus or train to provide connectivity to passengers, or on a drone to extend coverage in hard-to-reach areas. It can also be used for temporary capacity boosts at events or in disaster recovery situations. By enabling mobility, the Mobile IAB-node brings the benefits of IAB (such as reduced fiber dependency and rapid deployment) to dynamic environments. The node can self-configure and self-optimize, integrating seamlessly with the network.

In Release 20, the definition of Mobile IAB-node was simplified to reference TS 38.300, indicating that the term is now fully integrated into the overall RAN architecture specifications. This reflects the maturity of the concept and its alignment with other RAN nodes. The Mobile IAB-node continues to evolve, with ongoing work on enhancing mobility, power efficiency, and integration with network slicing. Overall, the Mobile IAB-node represents a significant step towards flexible, mobile 5G-Advanced networks, enabling new use cases and business models.

Purpose & Motivation

The Mobile IAB-node was created to address the need for flexible, high-capacity network infrastructure in mobile scenarios. Traditional IAB-nodes are fixed, limiting their deployment to locations where backhaul can be permanently established. However, many use cases require connectivity on the move, such as public transportation, emergency response, and temporary events. The Mobile IAB-node solves this by allowing the IAB node itself to move while maintaining backhaul connectivity through dynamic parent node selection. This extends the benefits of IAB—such as reduced reliance on fiber and rapid deployment—to mobile environments. The introduction in Release 18 was motivated by the growing demand for mobile small cells and relays in 5G networks, particularly in millimeter-wave bands where coverage is challenging. By reusing the existing IAB framework and aligning with the MBSR function in the core network, the Mobile IAB-node ensures interoperability and leverages existing investments. It also enables new business opportunities for operators, such as providing connectivity to moving vehicles or deploying temporary networks.

What changed in its specifications

The latest release-to-release comparison of specifications that define Mobile IAB-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 →
TS 38.331Rel-18 → Rel-19

Rel-19 adds LTM cell-switch and MIMO Phase 5 identifiers to TS 38.331, plus multi-hop sidelink U2N relay clauses and IEs. It also adds OD-SIB1 and adaptive SSB for RRM, SIB27 for NTN, and SBFD identifiers.

Full comparison in TS 38.331 →

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-18 Initial

Introduced as a new RAN node type capable of physical mobility, with detailed definition and alignment to the MBSR function in 5GC. This release established the architecture, procedures, and specification impacts for mobile IAB, enabling mobile backhaul scenarios.

The definition carried over unchanged from Rel-18, maintaining the same capabilities and alignment with MBSR. No modifications to the definition were made in this release.

The definition was revised to a simplified form: 'Mobile IAB-node as defined in TS 38.300 [29]'. This change reflects the integration of the term into the overall RAN architecture specifications, removing redundant details and referencing the primary specification for the complete definition.

Defining Specifications

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

SpecificationTitleRelease
TS 38.174 vk00 NR Integrated Access and Backhaul Requirements Rel-20 read
TS 38.175 vj00 EMC for NR IAB Nodes Rel-19 read
TS 38.176 vj40 IAB Conformance Testing Rel-19 read
TS 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read
TS 38.331 vj40 NR Radio Resource Control (RRC) Rel-19 read
TS 38.340 vj00 Backhaul Adaptation Protocol (BAP) Specification Rel-19 read
TS 38.413 vj40 NG Application Protocol (NGAP) Specification 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