Description
The Aggregated IAB-DU Channel Bandwidth is a radio frequency (RF) requirement concept defined in 3GPP TS 38.174 (IAB RF requirements) and referenced in TS 38.176 (IAB EMC requirements). It describes the total RF bandwidth occupied when an Integrated Access and Backhaul Distributed Unit (IAB-DU) simultaneously transmits and receives multiple contiguously aggregated carriers. The IAB-DU is the part of an IAB node that serves UE traffic over the access link, functioning logically like a gNB distributed unit. When carrier aggregation (CA) is configured on the access side, the IAB-DU may operate several component carriers that are contiguous in the frequency domain, and the aggregated channel bandwidth is the span covering all of them, expressed in MHz.
Architecturally, an IAB node consists of two functional entities: the IAB-DU, which terminates the NR access link toward UEs and child IAB nodes, and the IAB-MT (Mobile Termination), which connects toward the parent node over the backhaul link. The IAB-DU channel bandwidth concept mirrors the conventional BS channel bandwidth definitions in TS 38.104, but is adapted for the IAB context where the node is not a fixed, fully-provisioned base station. The aggregated bandwidth determines the RF filter masks, spectrum emission masks, adjacent channel leakage ratio (ACLR) requirements, and spurious emission limits that the IAB-DU must satisfy. It also constrains the maximum number of aggregated resource blocks that can be scheduled on the access link.
The concept works together with the definition of the aggregated transmission bandwidth configuration: the aggregated channel bandwidth is the RF span in MHz, while the transmission bandwidth configuration counts the resource blocks actually allocated within that span. The relationship between the two is governed by the NR channel raster, the subcarrier spacing numerology, and the guard bands required at the edges of the aggregated span. Because IAB deployments are often dense and use the same spectrum for access and backhaul (in-band operation), tight RF requirements on the aggregated IAB-DU bandwidth are essential to control self-interference and cross-link interference.
In Rel-16, when IAB was first specified, the aggregated IAB-DU channel bandwidth was introduced to allow IAB nodes to exploit carrier aggregation on the access side, improving peak throughput and scheduling flexibility toward UEs. The definition has remained stable across Rel-17 through Rel-20, reflecting that the fundamental RF measurement concept did not need revision even as IAB features such as enhanced duplexing, mobility enhancements, and multi-hop topologies were added. The term therefore serves as a stable anchor in the RF conformance test framework for IAB equipment.
For engineers, the aggregated IAB-DU channel bandwidth matters when designing RF front-ends, planning spectrum, and performing conformance testing. It directly affects the complexity of the power amplifier and filter chain, the thermal design of the IAB node, and the coexistence analysis with adjacent operators or services. It is also a key input to link budget calculations and to the assessment of whether a given IAB node can support the carrier aggregation configurations envisioned by the network operator.
Purpose & Motivation
The Aggregated IAB-DU Channel Bandwidth exists to provide a precise, testable RF definition for IAB nodes that aggregate multiple contiguous carriers on their access link. Before IAB was introduced in Rel-16, base station RF requirements in TS 38.104 assumed a conventional gNB with a fixed set of supported channel bandwidths. IAB nodes, however, are deployed flexibly — on lamp posts, building walls, or rooftops — and must often operate with carrier aggregation to deliver sufficient capacity to UEs while sharing spectrum with the backhaul link. A dedicated definition was needed so that RF conformance tests, spectrum masks, and coexistence rules could be applied consistently to the IAB-DU entity.
The concept solves the problem of ambiguity in measuring and regulating emissions when multiple component carriers are transmitted as one contiguous block. Without an aggregated bandwidth definition, each carrier would be tested in isolation, which does not capture the true spectral footprint and could allow excessive emissions at the edges of the aggregated span. By defining the aggregated IAB-DU channel bandwidth in MHz, 3GPP enables regulators and operators to evaluate the actual occupied spectrum and to set appropriate guard bands.
The IAB-specific version was motivated by the need to support in-band backhaul, where the access and backhaul links share the same spectrum and self-interference must be tightly controlled. The stable definition across Rel-16 to Rel-20 reflects the maturity of the underlying RF framework and the fact that later IAB enhancements focused on protocols, mobility, and duplexing rather than on redefining the basic bandwidth measurement.
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.
Initial introduction of IAB in 3GPP. The aggregated IAB-DU channel bandwidth was defined as the RF bandwidth in which an IAB-DU transmits and receives multiple contiguously aggregated carriers, measured in MHz, establishing the RF conformance framework for IAB access-side carrier aggregation.
Defining Specifications
3GPP specifications that define or reference Aggregated IAB-DU Channel Bandwidth, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 38.174 vk00 | NR Integrated Access and Backhaul Requirements | Rel-20 read |
| TS 38.176 vj40 | IAB Conformance Testing | Rel-19 read |