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

Glossary term · Physical Layer

BS transmission bandwidth configuration

Base Station Transmission Bandwidth Configuration

Physical Layer →

BS transmission bandwidth configuration is the set of resource blocks within a BS channel bandwidth that a base station may use for transmission or reception, defining the usable spectrum grid.

Introduced
Rel-15
Where
Radio Access Network › NG-RAN (5G)
Specifications
3 specs
BS transmission bandwidth configuration Description Purpose What changed Neighbours Specifications

Description

The BS transmission bandwidth configuration (often abbreviated N_RB) is a fundamental physical-layer and RF concept in 5G NR. It defines the set of resource blocks (RBs) located within the BS channel bandwidth that the base station may use for transmitting or receiving. Each resource block occupies 12 subcarriers, and the transmission bandwidth configuration specifies how many such blocks fit inside a given channel bandwidth after accounting for guard bands on either edge of the channel. This parameter is central to how NR maps the abstract resource grid onto real RF spectrum.

In the NR physical layer, the channel bandwidth (e.g., 5, 10, 20, 50, 100, 400 MHz) is wider than the actual transmission bandwidth because guard bands are required to prevent adjacent channel interference and to allow for filter roll-off. The transmission bandwidth configuration is therefore the largest RB count that fits within the channel while respecting those guard bands. For example, a 100 MHz channel with 30 kHz subcarrier spacing supports 273 resource blocks in the transmission bandwidth configuration. The exact values are tabulated per subcarrier spacing in TS 38.104, since different numerologies yield different RB sizes and therefore different RB counts for the same channel bandwidth.

TS 38.104 (NR Base Station radio transmission and reception) is the primary normative source. It specifies the transmission bandwidth configuration for each supported channel bandwidth and subcarrier spacing combination, along with the minimum and maximum guard band requirements. These values are used directly in RF conformance testing: test equipment configures the BS to transmit at the edges of the transmission bandwidth configuration to verify spectral emissions, EVM, and adjacent channel leakage ratio (ACLR) compliance. TS 38.194 extends this to the BS conducted test scenarios, and TS 38.877 provides further background on NR RF requirements.

The concept matters because it bridges the gap between the logical resource grid used by schedulers and the physical RF constraints of real hardware. The gNB scheduler operates on resource blocks; the RF front end must respect guard bands and spectral masks. The transmission bandwidth configuration is the agreed boundary that both sides honor. It also determines the maximum number of RBs that can be scheduled in a given carrier, directly affecting peak throughput calculations.

Because NR supports flexible numerology (15, 30, 60, 120 kHz subcarrier spacing), the transmission bandwidth configuration is not a single number per channel bandwidth but a table indexed by both channel bandwidth and subcarrier spacing. This flexibility is a defining feature of NR compared to LTE, where the RB count per channel bandwidth was more rigid. The definition has remained stable across Rel-15 through Rel-20, reflecting its foundational and well-understood nature.

Purpose & Motivation

The BS transmission bandwidth configuration exists to reconcile two competing realities: the logical resource grid used by the NR scheduler and the physical constraints of RF transmission. Real-world spectrum is never perfectly rectangular — filters have roll-off, adjacent channels must be protected, and regulatory spectral masks must be satisfied. Without a defined transmission bandwidth configuration, there would be no standardized agreement on how many resource blocks a base station may actually use within a nominal channel bandwidth, leading to interoperability failures between vendors and non-compliance with spectrum regulations.

Historically, LTE (Rel-8) already defined a transmission bandwidth configuration per channel bandwidth, but NR's introduction of flexible numerology in Rel-15 made the concept more complex. The same 100 MHz channel can host different RB counts depending on whether 30 kHz or 60 kHz subcarrier spacing is used. The transmission bandwidth configuration tables in TS 38.104 were created to give equipment vendors, test labs, and regulators a single authoritative reference. This enables consistent RF conformance testing and ensures that a UE from one vendor can operate with a gNB from another across all supported bandwidths.

The concept also solves a testing problem: conformance test equipment needs to know exactly which RBs to activate to stress the RF chain at its limits. By standardizing the configuration, 3GPP ensures that a BS declared compliant at a given channel bandwidth will behave predictably regardless of which test house evaluates it.

What changed in its specifications

The latest release-to-release comparison of specifications that define BS transmission bandwidth configuration. Each summary describes the whole specification, not only this term.

TS 38.104Rel-18 → Rel-19

Rel-19 adds sub-band full duplex base station requirements to TS 38.104, plus LP-WUS text, ATG PUSCH requirements, and the new n110 band. It also adds sub-5 MHz FR1 channel bandwidth requirements and extends wide-area BS unwanted emission limits to n68, n87, n88 and n110.

Full comparison in TS 38.104 →

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-15 Initial

Initial definition introduced with NR: the set of resource blocks located within the BS channel bandwidth which may be used for transmitting or receiving by the BS. Established the per-numerology RB tables in TS 38.104 that underpin all NR RF conformance testing.

Definition carried over unchanged; the concept remained foundational as NR expanded to new frequency ranges and deployment scenarios.

Definition carried over unchanged; continued to apply as NR extended to new bands and features such as RedCap.

Definition carried over unchanged; the term remained stable through the 5G-Advanced baseline.

Definition carried over unchanged; continued use in RF conformance specifications.

Definition carried over unchanged; the term persists as a stable physical-layer reference.

Defining Specifications

3GPP specifications that define or reference BS transmission bandwidth configuration, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 38.104 vk10 NR Base Station RF Requirements Rel-20 read
TS 38.194 vj40 Ambient IoT RF Requirements Rel-19 read
TR 38.877 vi10 Technical Report Rel-18 read