Description
The IAB-MT (Integrated Access and Backhaul Mobile Termination) is a fundamental component of the 3GPP-defined IAB architecture introduced in Release 16. It represents the 'user equipment' side of an IAB node. Functionally, the IAB-MT is the logical entity that establishes and maintains a wireless connection to a parent node, which can be another IAB node or a donor gNB (gNB-DU). This connection forms the wireless backhaul link, carrying both control plane signaling and user plane data for the IAB node itself and for any downstream nodes or UEs it serves. The IAB-MT operates according to the standard NR Uu interface specifications, meaning it uses the same physical layer (as defined in 38.211), layer 2 protocols, and RRC procedures (as in 38.331) as a conventional 5G UE. This design choice maximizes reuse of existing UE functionality and ensures reliable, standardized connectivity for the backhaul.
Architecturally, an IAB node comprises two main functional parts: the IAB-MT and the IAB-DU (Distributed Unit). The IAB-MT is responsible for the wireless backhaul uplink, while the IAB-DU provides the access network functionality to serve end-user UEs or child IAB nodes via the NR Uu interface. The IAB-MT and IAB-DU within the same node are coordinated by an IAB-specific adaptation layer and are managed by a central IAB-donor CU (Centralized Unit). This split architecture allows for efficient resource allocation and topology management. The IAB-MT's operation is tightly integrated with the IAB-DU's scheduling to manage time-division multiplexing (TDM) or spatial-division multiplexing between backhaul and access links, preventing self-interference and optimizing spectral efficiency.
The role of the IAB-MT is critical for enabling self-backhauling networks. It allows an operator to deploy a network node where fiber is unavailable or too costly, by having the node 'wire itself in' to the network. The IAB-MT supports carrier aggregation, dual connectivity, and operation in FR1 and FR2 frequency ranges, as specified in the relevant RF performance specs (38.174, 38.176). Its performance directly impacts the capacity and latency of the multi-hop backhaul chain. Key procedures involving the IAB-MT include initial access and connection setup to a parent node, RRC reconfiguration for mobility (e.g., parent cell change), and the handling of backhaul adaptation layer (BAP) routing identifiers to correctly steer packets through the IAB topology.
Purpose & Motivation
IAB-MT was created to address the challenge of deploying dense 5G networks, especially in millimeter-wave (mmWave) bands where signal propagation is limited and fiber installation is prohibitively expensive for every cell site. Traditional networks require a fiber connection to each base station for backhaul, which is a major bottleneck for rapid and cost-effective deployment. The purpose of the IAB-MT is to turn a network node into a relay, allowing it to connect to the core network wirelessly through a multi-hop mesh of similar nodes. This enables operators to extend coverage and capacity into new areas—like urban canyons, indoor venues, or temporary event sites—by building upon an initial fiber-connected anchor point (the donor).
Historically, similar concepts existed in LTE (Relay Nodes), but they were not fully integrated into the RAN architecture. The 5G IAB architecture, with the IAB-MT as a core component, is a native, more flexible, and scalable solution. It solves the problem of network densification by decoupling the need for fiber from the need for radio coverage. The IAB-MT specifically solves the problem of how a relay node integrates into the network as a peer. By behaving as a standard UE for its upstream connection, it leverages all the existing mobility, security, and radio resource management mechanisms of 5G NR, ensuring robust and manageable backhaul links. This design was motivated by the industry's push towards more agile and deployable networks for 5G and beyond.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (50 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the IAB-MT function was newly introduced with the capability to transfer F1-C related information between an IAB-DU and an IAB-donor-CU. This is performed using the DLInformationTransfer and ULInformationTransfer RRC procedures over SRB2, specifically when the IAB-MT is in RRC_CONNECTED. The release also addressed security and procedural aspects for termination point changes, particularly for RLC UM bearers.
In Release 16, the IAB-MT function was introduced to enable the transfer of F1-C related information between an IAB-DU and an IAB-donor-CU via new dedicated ULInformationTransfer and DLInformationTransfer procedures. This required the IAB-MT to operate on SRB2 to tunnel this F1-C signaling, distinguishing its role from a standard UE. Furthermore, specific capabilities and configurations for the IAB-MT were defined and updated, covering aspects like TDD resource configuration, transmission suspension upon backhaul link failure, and security risk mitigation during termination point changes.
- 36.331 CR on Integrated Access and Backhaul TS 36.331CR4233
- Big CR on IAB-MT demodulation in TS 38.174 TS 38.174CR0016
- Big CR: IAB-MT RRM test cases in 38.174 TS 38.174CR0018
- Introduction of integrated access and backhaul for NR TS 38.211CR0025
- Introduction of integrated access and backhaul for NR TS 38.214CR0052
- 38.331 CR on Integrated Access and Backhaul for NR TS 38.331CR1471
+ 12 more changes
In Release 17, enhancements for IAB-MT included clarifying its role in transferring F1-C related information between the IAB-DU and IAB-donor-CU via dedicated SRB2 signaling, using the DLInformationTransfer and ULInformationTransfer procedures. Specific corrections were made to the IAB-MT's timing reference point, CQI derivation accounting for DL Tx power adjustments, and its handling of cell barring procedures to follow standard UE behavior. Furthermore, measurement procedures for over-the-air timing errors between the IAB-DU and IAB-MT were refined.
- Introducing Enhancements to Integrated Access and Backhaul for NR TS 38.331CR2811
- Correction to IAB-MT timing reference point in TS 38.174 TS 38.174CR0042
- CR to TS 38.176-2 with bracket removal for measurement uncertainties for OTA timing error between IAB-DU and IAB-MT TS 38.176CR0017
- Correction on CQI derivation accounting for provided DL Tx power adjustment for IAB-MT TS 38.214CR0308
- Corrections in TS 36.331 on IFRI handling by IAB-MT for eIAB TS 36.331CR4910
- Clarification that IAB-MT follows the UE behaviour for cell barring procedure as defined in TS 38.304 TS 38.331CR3935
In Release 18, the IAB-MT function was enhanced with the formal introduction and support of Mobile IAB, requiring new RF, RRM, and demodulation core requirements. Key technical additions included the definition of procedures for transferring F1-C related information between the IAB-DU and IAB-donor-CU via the IAB-MT using dedicated SRBs. Furthermore, the release introduced specific corrections and performance requirements for the IAB-MT, covering areas such as output power dynamics, timing advance adjustment accuracy, and scaling factors for conformance testing.
- Big CR to TS 38.174 on RF core requirements for NR Mobile IAB TS 38.174CR0077
- Big CR to TS 38.174 on RRM core requirements for NR Mobile IAB TS 38.174CR0095
- BigCR for 38.174 addition of mobile IAB demodulation requirements TS 38.174CR0108
- Big CR on RRM performance requirements for NR Mobile IAB TS 38.174CR0114
- BigCR to TS 38.176-2 on RF conformance requirements for NR Mobile IAB TS 38.176CR0057
- Introduction of mobile IAB TS 38.331CR4457
+ 17 more changes
Explore further
Broader topics and technologies where IAB-MT plays a role.
Defining Specifications
3GPP specifications that define or reference IAB-MT, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 36.331 vj00 | LTE RRC Protocol Specification | Rel-19 |
| TS 37.340 vj00 | Multi-Connectivity Operation Overview | Rel-19 |
| TS 38.174 vj10 | NR Integrated Access and Backhaul Radio Spec | Rel-19 |
| TS 38.176 vj20 | IAB Conformance Testing Specification | Rel-19 |
| TS 38.211 vj10 | NR Physical Channels and Modulation | Rel-19 |
| TS 38.214 vj10 | NR Physical Layer Procedures for Data | Rel-19 |
| TS 38.306 vj00 | NR UE Radio Access Capability Parameters | Rel-19 |
| TS 38.331 vj00 | NR Radio Resource Control (RRC) Protocol Specification | Rel-19 |
| TS 38.420 vj10 | Introduction to Xn interface specifications | Rel-19 |
| TS 38.809 vg60 | IAB Radio Transmission & Reception Background | Rel-16 |