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.
What changed in its specifications
The latest release-to-release comparison of specifications that define IAB-MT. Each summary describes the whole specification, not only this term.
Rel-19 adds NTN-for-IoT Phase 3 and inter-RAT mobility from E-UTRAN to NR NTN, plus LTE-based 5G Broadcast Phase 2 changes. It also adds IMS disaster-roaming access barring, NTN-for-NR Phase 3 fields, and NR RRM Phase 5 items.
Full comparison in TS 36.331 →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 →Technology family
Base stations and RAN nodes · Radio Access Network
- Phase 1 BSC, BSS, BTS
- R99 Node B, RNC, RNS
- Rel-8 eNB, HeNB, HNB, HNB-GW
- Rel-10 DeNB, HeNB-GW, RN
- Rel-15 en-gNB, gNB, gNB-CU, gNB-CU-CP, gNB-CU-UP, gNB-DU, ng-eNB
- Rel-16 IAB-donor, IAB-DU, IAB-MT, IAB-node
- Rel-18 Mobile IAB-node
- IAB-MT part of IAB-node
“In addition to the gNB-DU functionality, the IAB-node also supports a subset of the UE functionality referred to as IAB-MT” TS 38.300
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 4 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
IAB-MT is specified for the first time in Rel-16: the IAB-node connects upstream via a UE-like IAB-MT function, with RRM, RF and conformance requirements defined for it.
- “The IAB-node connects to an upstream IAB-node or an IAB-donor-DU via a subset of the UE functionalities of the NR Uu interface (named IAB-MT function of IAB-node).” TS 38.401 v16.12.0
- “In RRC_CONNECTED state the IAB-MT shall be capable of sending RRCReestablishmentRequest message within Tre-establish_delay seconds” TS 38.174 v16.13.0
- “Phase 1: IAB-MT setup. In this phase, the IAB-MT of the new IAB-node” TS 38.401 v16.12.0
Rel-17 adds IAB-MT requirements for simultaneous operation with IAB-DU, including Case-6 timing error limits, IAB-MT transmit timing control and timing error test requirements.
- “the timing error between transmission timing of IAB-DU and IAB-MT shall not exceed 3µs.” TS 38.174 v17.10.0
- “IAB-DU and IAB-MT can be configured as IAB Simultaneous Operation based on declaration.” TS 38.174 v17.10.0
- Correction on CQI derivation accounting for provided DL Tx power adjustment for IAB-MT TS 38.214CR0308
Rel-18 extends IAB-MT with mobile IAB-MT (mIAB-MT) types, RRM, RF and performance requirements and mobile IAB-MT migration procedures, plus corrections to IAB-MT test requirements.
- “Mobile IAB-MT: IAB-MT function on the mobile IAB-node as defined in TS 38.300” TS 38.174 v18.8.0
- “All the RRM requirements specified for IAB-MT in the clauses listed below shall apply to mIAB-MT:” TS 38.174 v18.8.0
- “The mobile IAB-MT can be migrated from a source RRC-terminating IAB-donor-CU to a target RRC-terminating IAB-donor-CU using the Xn handover procedure.” TS 38.401 v18.7.0
Rel-19 revises IAB-MT/IAB-DU radio requirements in TS 38.174: spurious emission co-existence and co-location tables are reworded and per-band exclusion notes removed, with PMI requirements referencing IAB-MT reports.
- “where requirements for co-existence with the system type listed in the first column apply for IAB-MT and IAB-DU” TS 38.174 v19.2.0
- “The basic limits are in table 6.6.5.2.3-1 for an IAB-DU and IAB-MT.” TS 38.174 v19.2.0
- “This requirement does not apply to IAB-DU and IAB-MT operating in band n77 or n78.” TS 38.174 v19.2.0
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 vj40 | E-UTRA Radio Resource Control (RRC) Protocol | Rel-19 read |
| 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.211 vj50 | NR Physical Channels and Signals | Rel-19 read |
| TS 38.214 vj50 | NR Physical Layer Data Channel Procedures | Rel-19 read |
| TS 38.306 vj40 | NR UE Radio Access Capability Parameters | Rel-19 read |
| TS 38.331 vj40 | NR Radio Resource Control (RRC) | Rel-19 read |
| TS 38.420 vj10 | Introduction to Xn interface specifications | Rel-19 read |
| TS 38.809 vg60 | IAB Radio Transmission & Reception Background | Rel-16 read |