Description
In 3GPP specifications, an operating band is a frequency range designated for E-UTRA (or NR) operation, identified by an integer band number (e.g., Band 1, Band 3, Band 7). The term 'high operating band' is not an absolute designation but a relative one: it refers to an operating band whose downlink frequency is higher than that of another, low, operating band being discussed in the same context. It is defined in 3GPP TS 36.133 (requirements for support of radio resource management) and TS 36.521 (UE conformance specification), where it is used to describe multi-band and carrier aggregation requirements.
The concept is needed because many RF requirements are specified relative to a pair of bands. For example, when a UE supports carrier aggregation across two bands, the specifications must define how the UE behaves when one band is the 'low' band and the other is the 'high' band. The high operating band is the one with the higher downlink frequency. This matters for receiver and transmitter requirements because propagation loss, antenna efficiency, and duplex spacing differ between bands, and inter-band carrier aggregation introduces new interference scenarios (e.g., harmonic and intermodulation products) that depend on the frequency relationship between the bands.
In practice, the term appears in requirements such as reference sensitivity, blocking characteristics, and spurious emission limits for multi-band operation. For instance, when a UE is configured with inter-band carrier aggregation, the specification may define separate requirements for the low band and the high band, and the high operating band is the one whose downlink is higher. The term is also used in the context of dual connectivity and multi-carrier operation, where the network may configure a primary cell in one band and a secondary cell in another.
The definition has remained stable since its introduction in Rel-11, which is notable because it is a purely relational definition: it does not name specific bands or frequencies, so it does not need to be updated when new bands are added. New bands are simply added to the band tables in the specifications, and the relative term continues to apply. This makes the definition robust and long-lived, which is why it appears unchanged in Rel-11 through Rel-14 and again in Rel-17 through Rel-19.
For engineers, the practical implication is that when reading a requirement that refers to a 'high operating band', one must identify the pair of bands under consideration and determine which has the higher downlink frequency. The term is a shorthand that avoids repeating the band numbers in every requirement clause, and it allows the specification to be written generically for any band pair.
Purpose & Motivation
The term 'high operating band' exists to make 3GPP RF requirements generic and reusable across the growing number of operating bands. When multi-band operation (such as inter-band carrier aggregation) was introduced, the specifications needed a way to describe requirements that depend on the relative frequency relationship between two bands without hard-coding specific band numbers. By defining a relative term, the specifications could write a single requirement that applies to any pair of bands, with the 'high' band being the one with the higher downlink frequency.
This approach solved a practical problem: the number of possible band combinations grew rapidly, and writing separate requirements for each combination would have been unwieldy and error-prone. A relative definition allows the requirement to be applied mechanically once the band pair is known, and it remains valid as new bands are introduced. It also reflects the physical reality that many RF impairments (such as harmonic interference and intermodulation) depend on the frequency relationship between bands rather than on the absolute band identity.
The definition was introduced in Rel-11, a period when carrier aggregation was expanding from intra-band to inter-band combinations. Earlier releases had focused on single-band operation and intra-band contiguous aggregation, where the relative term was less necessary. As inter-band aggregation became common, the need for a generic way to describe band-pair requirements became clear, and the term has been carried forward unchanged ever since because it remains fit for purpose.
What changed in its specifications
The latest release-to-release comparison of specifications that define High operating band. Each summary describes the whole specification, not only this term.
Rel-19 adds enhanced NR NTN and IoT NTN requirements and test methods to TS 36.133. It also removes many clauses, mainly SCell delay, RSRP accuracy, NB-IoT and LTE-M measurement and test sections, plus multi-layer gap monitoring and CGI identification clauses.
Full comparison in TS 36.133 →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.
Defining Specifications
3GPP specifications that define or reference High operating band, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 36.133 vj60 | LTE Radio Resource Management Requirements | Rel-19 read |
| TS 36.521 vj11 | E-UTRA UE Conformance Testing for Satellite Access | Rel-19 read |