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

Glossary term · Radio Access Network

Sub-block gap

Sub-block gap

Radio Access Network →

Sub-block gap is a frequency separation between adjacent sub-blocks within a base station's operating bandwidth to enable uncoordinated coexistence for different operators or services.

Introduced
Rel-10
Where
Radio Access Network › Multi-RAT
Specifications
16 specs
Sub-block gap Description Purpose What changed Neighbours Specifications

Description

In modern cellular networks, a base station's RF bandwidth can be composed of multiple sub-blocks, each potentially serving different operators, frequency layers, or radio access technologies. A sub-block gap is the unused frequency region between two consecutive sub-blocks within the overall base station RF bandwidth. These gaps are not arbitrary; they are defined to ensure that the RF requirements in the gap—such as unwanted emissions, blocking, and intermodulation—are based on co-existence for un-coordinated operation. This means that the network can deploy sub-blocks without requiring precise synchronization or coordination with other systems, simplifying deployment and reducing operational complexity.

The concept was introduced in 3GPP Release 10 as part of the work on multi-standard radio (MSR) base stations, which aimed to support multiple technologies (e.g., GSM, UMTS, LTE) within a single base station. Sub-block gaps enable flexible spectrum usage by allowing operators to deploy non-contiguous spectrum chunks while maintaining acceptable interference levels. The size and placement of sub-block gaps are specified in 3GPP TS 37.104 and 37.141 for MSR, and in 38.104 for NR. They are typically expressed as a minimum frequency separation that must be maintained to meet regulatory and co-existence requirements.

From a technical perspective, the sub-block gap is characterized by its width in Hz (or MHz). Within the gap, the base station must meet certain RF requirements, such as spurious emissions limits, to avoid causing harmful interference to other systems. These requirements are less stringent than those for in-band transmissions but more stringent than for out-of-band emissions. The gap also affects the base station's ability to perform measurements and may influence scheduling if the gap is used for other purposes (e.g., guard bands). The gap is defined at the base station antenna connector and is part of the overall RF bandwidth configuration.

Key parameters associated with sub-block gaps include the maximum number of sub-blocks, the minimum gap size, and the applicable RF requirements. For example, in LTE, a sub-block gap of at least 5 MHz might be required between two sub-blocks of different operators to ensure co-existence. The gap size depends on factors such as the operating band, the sub-block bandwidths, and the coexistence scenario (e.g., co-located base stations). 3GPP specifications provide tables mapping these parameters to specific requirements.

Sub-block gaps are essential for enabling spectrum sharing and flexible deployment. They allow operators to use non-contiguous spectrum, which is common in refarmed bands. They also facilitate the coexistence of different radio access technologies within the same base station, supporting the smooth evolution from 2G/3G to 4G and 5G. Without sub-block gaps, deploying multiple sub-blocks would require tight synchronization and coordination, increasing cost and complexity. As networks move towards 5G NR and beyond, the concept remains relevant for multi-band and multi-operator deployments, including spectrum sharing scenarios like CBRS and shared spectrum in 6 GHz.

Purpose & Motivation

The sub-block gap was introduced to address the challenge of deploying multiple sub-blocks within a single base station's RF bandwidth without requiring tight coordination between them. Before its definition, operators faced difficulties in sharing spectrum or deploying multi-operator base stations because uncoordinated transmissions could cause severe interference. The sub-block gap provides a buffer zone where RF requirements are relaxed but still controlled, enabling coexistence in un-coordinated scenarios. This is particularly important for spectrum refarming, where legacy technologies and new ones must coexist, and for shared spectrum access, where multiple operators use the same band. The gap concept allows flexible spectrum usage and simplifies deployment, reducing the need for complex coordination and synchronization mechanisms.

What changed in its specifications

The latest release-to-release comparison of specifications that define Sub-block gap. 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

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-10 Initial

Initial definition: 'A frequency gap between two consecutive sub-blocks within an RF bandwidth, where the RF requirements in the gap are based on co-existence for un-coordinated operation.' Introduced as part of MSR work to support multi-standard base stations.

Definition refined to: 'frequency gap between two consecutive sub-blocks within an Base Station RF Bandwidth, where the RF requirements in the gap are based on co-existence for un-coordinated operation.' The term 'Base Station' was made explicit, clarifying the scope.

Definition carried over unchanged from Rel-11.

Definition carried over unchanged from Rel-11, but with minor formatting adjustments (line breaks) in the specification text.

Defining Specifications

3GPP specifications that define or reference Sub-block gap, 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
TS 51.021 vj00 RF test methods and conformance requirements for GSM BSS Rel-19 read