IAB-MT

Integrated Access and Backhaul Mobile Termination

Radio Access Network →
Introduced in Rel-16

IAB-MT is the Mobile Termination function within an IAB node that enables it to connect wirelessly to a parent node like a user equipment for self-backhauling in 5G networks.

Category
Radio Access Network
Introduced
Rel-16
Where
Radio Access Network › NG-RAN (5G)
Specifications
10 specs
IAB-MT Description Purpose Related Classification Detected Changes Specifications

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

Part ofIAB-DU
Specific typesIAB-DU

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (25 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-16 9 changes

In Release 16, the IAB-MT function was introduced to enable the forwarding of F1-C control plane information between an IAB-DU and an IAB-donor-CU using dedicated RRC procedures. This included defining specific capabilities for the IAB-MT, along with corrections and updates for its TDD resource configuration, backhaul RLC channel management, and transmission suspension mechanisms. Furthermore, the release standardized related RRM test cases and demodulation requirements for the IAB-MT.

  • 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
  • CR on maintenance on sharing factor of RLM and link recovery for IAB-MT TS 38.174CR0015
  • Update to IAB-MT capabilities TS 38.306CR0383
  • Corrections on the IAB-MT TDD resource configuration TS 38.331CR1958
  • Update to IAB-MT capabilities TS 38.331CR1994

+ 3 more changes

Rel-17 5 changes

In Release 17, the IAB-MT function saw clarifications and corrections to its operation, including its role in forwarding F1-C related information between the IAB-DU and IAB-donor-CU via specific RRC procedures. Enhancements included corrections for CQI derivation accounting for downlink transmit power adjustment and clarifications on the IAB-MT following UE behavior for cell barring. Furthermore, specifications were corrected for the IAB-MT's handling of IFRI for evolved IAB (eIAB) and its timing reference point.

  • 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
Rel-18 11 changes

In Release 18, the IAB-MT function saw clarifications and corrections to its performance and conformance testing requirements. These included refinements to its output power dynamics, radiated CSI reporting, and specific scaling factors for its type 1-O implementation. Furthermore, corrections were made to the applicable FR2 frequency ranges for its RRM core and performance requirements, as well as to its timing advance adjustment accuracy.

  • Correction on the mandatory features for IAB-MT and NCR-MT TS 38.306CR1228
  • CR for TS 38.174, Correction on scaling factor for IAB-MT type 1-O TS 38.174CR0059
  • Correction to applicable FR2 range for IAB-MT RRM core requirements TS 38.174CR0069
  • [NR_IAB_enh] Correction to IAB-MT TA adjustment accuracy requirements TS 38.174CR0092
  • [NR_IAB_enh] Correction to applicable FR2 range in IAB-MT RRM performance requirements TS 38.174CR0094
  • (NR_IAB-Core)CR for TS 38.174, Correction on scaling factor for IAB-MT type 1-O TS 38.174CR0101

+ 5 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.

SpecificationTitleRelease
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
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.