Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Physical Layer

Non-contiguous spectrum

Non-contiguous spectrum

Physical Layer →

Non-contiguous spectrum is a spectrum allocation consisting of two or more sub-blocks separated by gaps, used in carrier aggregation to combine fragmented bands for improved data rates and efficiency.

Introduced
Rel-10
Where
Radio Access Network › Multi-RAT
Specifications
15 specs
Non-contiguous spectrum Description Purpose What changed Neighbours Detected Changes Specifications

Description

Non-contiguous spectrum is a fundamental concept in advanced wireless systems, particularly in the context of carrier aggregation (CA) introduced in 3GPP Release 10 for LTE and extended in later releases for NR. It describes a spectrum arrangement where the total available bandwidth is not a single continuous block but is composed of multiple sub-blocks (also called component carriers) that are separated by gaps, known as sub-block gaps. These gaps may be due to spectrum fragmentation, where an operator owns non-adjacent frequency bands, or due to the need to avoid interference with other systems.

In carrier aggregation, non-contiguous spectrum allows the aggregation of multiple component carriers (CCs) that may be in different frequency bands (inter-band CA) or within the same band but non-adjacent (intra-band non-contiguous CA). Each component carrier functions as an independent cell, with its own synchronization, reference signals, and control channels. The UE aggregates these carriers to increase the effective bandwidth and thus the peak data rate. The sub-block gaps between carriers can vary in size, and the UE must be capable of tuning to each carrier independently while managing the gaps.

The implementation of non-contiguous spectrum poses several technical challenges. The UE must support multiple transceivers or a wideband transceiver with sufficient linearity to handle multiple carriers simultaneously. The gaps between sub-blocks may require the UE to filter out unwanted emissions and avoid intermodulation products. In the base station, the transmitter must ensure that the aggregated carriers meet spectrum emission requirements, including limits on out-of-band emissions and spurious emissions. 3GPP specifications such as TS 36.101 (LTE UE radio transmission and reception) and TS 38.101 (NR UE radio transmission and reception) define the requirements for non-contiguous spectrum operation, including allowed sub-block gaps and carrier aggregation configurations.

Non-contiguous spectrum is also relevant in other contexts, such as in the definition of operating bands for NR, where a band may be specified as non-contiguous to accommodate fragmented spectrum holdings. For example, in the 3.5 GHz band (n78), an operator might have two non-adjacent blocks; non-contiguous CA allows them to be used together. The concept is also applied in dual connectivity (DC) and supplementary uplink (SUL) scenarios, where different frequency ranges are combined.

The evolution of non-contiguous spectrum support has been progressive. Release 10 introduced intra-band non-contiguous CA for LTE, with later releases adding more band combinations and higher order CA. In NR, non-contiguous spectrum is supported from Release 15 onwards, with flexible numerology and wider bandwidths. The specifications continue to evolve to support new band combinations and deployment scenarios, including those for private networks and shared spectrum.

Overall, non-contiguous spectrum is a key enabler for operators to maximize the use of their fragmented spectrum assets, delivering higher data rates and better user experience. It requires careful design in both UE and network to handle the gaps and ensure coexistence with other systems.

Purpose & Motivation

Non-contiguous spectrum exists to address the reality that spectrum allocations are often fragmented, and operators may not have access to large contiguous blocks of spectrum. Before carrier aggregation, each operator could only use a single contiguous block of spectrum per carrier, limiting peak data rates. The introduction of carrier aggregation in Release 10 allowed the combination of multiple carriers, including non-contiguous ones, to form a larger effective bandwidth. This was motivated by the need to increase peak data rates to meet the requirements of IMT-Advanced and beyond.

The concept solves the problem of spectrum fragmentation by enabling the aggregation of non-adjacent sub-blocks, thereby allowing operators to utilize their entire spectrum portfolio efficiently. It also provides flexibility in network deployment, as operators can deploy carriers in different bands and aggregate them based on availability and load. This is particularly important in scenarios where spectrum is scarce or when an operator acquires spectrum in multiple auctions.

Furthermore, non-contiguous spectrum supports interference mitigation by allowing gaps to be placed between sub-blocks to avoid interfering with other systems or to meet regulatory requirements. It also facilitates spectrum sharing and refarming, as operators can gradually migrate spectrum to new technologies while maintaining service on legacy carriers. The ongoing evolution of non-contiguous spectrum support in 3GPP ensures that networks can continue to adapt to new spectrum bands and deployment scenarios, such as those in millimeter wave and sub-6 GHz bands.

What changed in its specifications

The latest release-to-release comparison of specifications that define Non-contiguous spectrum. Each summary describes the whole specification, not only this term.

TS 25.104Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 25.104: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 25.104 →
TS 25.141Rel-11 → Rel-12

Rel-12 added L-band for Supplemental Downlink in E-UTRA and UTRA, introducing UTRA band XXXII in 1452–1496 MHz with test and coexistence requirements.

Full comparison in TS 25.141 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-17 1 change
  • CR to 37.145-2: Correction to ACLR limit in non-contiguous spectrum (Rel-17) TS 37.145CR0313

Defining Specifications

3GPP specifications that define or reference Non-contiguous spectrum, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 25.104 vj00 UTRA FDD Base Station RF Characteristics Rel-19 read
TS 25.141 vj00 UTRA FDD Base Station RF Conformance Testing Rel-19 read
TS 36.101 vk10 E-UTRA UE RF Requirements Rel-20 read
TS 36.104 vj20 E-UTRA/NB-IoT Base Station RF Requirements Rel-19 read
TS 36.141 vj10 RF Test Methods for LTE and NB-IoT Base Stations Rel-19 read
TS 36.823 vb01 LTE Carrier Aggregation Enhancements Study Rel-11 read
TS 37.104 vj40 NR, E-UTRA, UTRA, GSM/EDGE and NB-IoT Multi-Standard Radio Rel-19 read
TS 37.105 vj40 AAS Base Station Radio Requirements Rel-19 read
TS 37.141 vj40 RF Test Methods and Conformance for Multi-Standard Radio Base Stations Rel-19 read
TS 37.145 vj40 AAS Base Station Radiated Requirements Rel-19 read
TS 37.802 va10 MSR BS RF Requirements for Non-Contiguous Spectrum Rel-10 read
TS 37.812 vb30 Multi-band Multi-standard Radio BS Requirements Rel-11 read
TS 38.104 vk10 NR Base Station RF Requirements Rel-20 read
TS 38.141 vj40 BS Conformance Testing (TR 38.141) Rel-19 read
TS 38.174 vk00 NR Integrated Access and Backhaul Requirements Rel-20 read