Carrier Aggregation Bandwidth Class

Description

A carrier aggregation bandwidth class is defined by 3GPP as a class defined by the aggregated transmission bandwidth configuration and maximum number of component carriers supported by a UE. It provides a standardised way to describe the bandwidth aggregation capability of a UE within a specific operating band or carrier aggregation band. Each class is identified by a letter (A through N, with additional classes in later releases), and each letter corresponds to a specific combination of maximum aggregated bandwidth and maximum number of component carriers.

The bandwidth class concept was introduced to simplify the specification and signalling of UE capabilities for carrier aggregation. Rather than listing every possible combination of component carrier bandwidths and counts, 3GPP defines a finite set of classes. For example, in E-UTRA, Class A supports a single component carrier with a maximum aggregated bandwidth of 20 MHz, Class B supports two component carriers with up to 20 MHz aggregated, Class C supports two component carriers with up to 40 MHz aggregated, and so on. In NR, similar classes are defined with different bandwidth thresholds reflecting NR's wider channel bandwidths.

Each bandwidth class is associated with specific RF requirements. The aggregated transmission bandwidth configuration determines the total occupied bandwidth, which in turn affects requirements such as maximum output power, power spectral density, ACLR, spurious emissions, and reference sensitivity. The maximum number of component carriers affects the complexity of the transceiver architecture, including the number of local oscillators, filters, and power amplifiers required. By defining classes, 3GPP ensures that requirements are specified consistently for all UEs claiming a given capability.

Bandwidth classes are used in UE capability signalling. A UE indicates which bandwidth classes it supports for each carrier aggregation band combination. The network then uses this information to configure carrier aggregation appropriately. For example, if a UE supports Class C in a given band, the network knows it can aggregate up to two component carriers with a total bandwidth of up to 40 MHz. This enables efficient use of spectrum while ensuring that the UE can meet the associated RF requirements.

The bandwidth class concept is also used in base station specifications and in coexistence studies. Base stations must support the bandwidth classes that UEs in their coverage area are expected to use, and coexistence studies must account for the aggregated bandwidth and carrier counts associated with each class. This makes the bandwidth class a key parameter in the end-to-end design and deployment of carrier aggregation systems.

Purpose & Motivation

Carrier aggregation bandwidth classes exist to provide a standardised, compact way to describe and specify UE capabilities for carrier aggregation. Without such a classification, UE capability signalling would need to enumerate every possible combination of component carrier bandwidths and counts, leading to a combinatorial explosion of capability parameters. The bandwidth class reduces this to a manageable set of well-defined categories.

The concept also serves a critical role in RF requirement specification. The aggregated transmission bandwidth and number of component carriers directly affect the RF performance requirements that a UE must meet. By defining classes, 3GPP can specify requirements per class rather than per individual combination, ensuring consistency and reducing the specification effort. This is particularly important as the number of supported band combinations has grown into the hundreds.

Historically, the bandwidth class concept was introduced in Rel-15 for NR, building on the experience gained from E-UTRA carrier aggregation in earlier releases. It reflects the maturation of carrier aggregation from a simple two-carrier concept to a complex, multi-band, multi-carrier feature. The class framework enables device vendors to clearly declare their capabilities, network operators to configure aggregation efficiently, and test houses to verify compliance against well-defined requirements.