Description
The SAN channel bandwidth is a radio-frequency (RF) parameter defined in the 3GPP RF performance specifications for satellite access (36.108, 36.181, 38.108, 38.181). It represents the RF bandwidth that supports a single E-UTRA (or NR) RF carrier, with the transmission bandwidth configured either in the uplink or in the downlink direction. In essence, it is the spectral envelope allocated to one carrier at the Satellite Access Node (SAN) — the non-terrestrial network node that provides the 5G/E-UTRA air interface to user equipment via a satellite link. The channel bandwidth is expressed in MHz (e.g., 5, 10, 15, 20 MHz and beyond) and is the reference against which the transmission bandwidth configuration (the set of usable resource blocks) is defined.
Architecturally, the SAN channel bandwidth sits between the operating band (the broader regulatory spectrum block) and the transmission bandwidth configuration (the actual resource blocks used). The channel bandwidth includes guard bands on either side of the transmission bandwidth configuration to prevent adjacent-channel interference. The relationship is: operating band ≥ SAN RF bandwidth ≥ SAN channel bandwidth ≥ transmission bandwidth configuration. Each carrier served by the SAN is assigned one channel bandwidth, and the SAN may aggregate multiple carriers within its RF bandwidth to serve more users or deliver higher throughput.
In operation, the SAN channel bandwidth determines the maximum occupied bandwidth of the transmitted signal and therefore constrains the achievable data rate per carrier. The gNB (or eNB) function hosted by the SAN schedules resource blocks only within the transmission bandwidth configuration, which must fit inside the channel bandwidth. RF requirements such as spectrum emission mask, adjacent channel leakage ratio (ACLR), and spurious emissions are all specified relative to the channel bandwidth edges. Because satellite links suffer from large path loss and long propagation delay, the choice of channel bandwidth directly trades off coverage (narrower bandwidth concentrates power) against capacity (wider bandwidth supports more throughput).
The parameter is also central to coexistence and regulatory compliance. Since satellite spectrum is often shared or adjacent to terrestrial mobile and fixed-satellite service allocations, the channel bandwidth defines the boundaries used in coexistence studies and in the RF requirement tables of 36.108/38.108 (conducted performance) and 36.181/38.181 (radiated performance for satellite). These specifications define transmitter and receiver characteristics — output power, EVM, frequency error, blocking, and reference sensitivity — all parameterized by channel bandwidth.
For engineers, the SAN channel bandwidth is the anchor value used when dimensioning a satellite cell, planning carrier placement within the operating band, and verifying that a SAN implementation meets 3GPP RF conformance. It is closely tied to the SAN RF bandwidth (the total bandwidth the node can transmit/receive across multiple carriers) and to the transmission bandwidth configuration (the usable resource blocks). Understanding this term is essential for anyone designing, testing, or deploying NTN (non-terrestrial network) equipment under 3GPP Release 17 and later.
Purpose & Motivation
Before Release 17, 3GPP RF specifications were written for terrestrial base stations (BS) and user equipment (UE), with channel bandwidth defined for a single E-UTRA or NR carrier at a ground-based node. When 3GPP began standardizing Non-Terrestrial Networks (NTN) — satellite-borne or airborne access nodes — it became clear that the RF characteristics of a Satellite Access Node differ substantially from a terrestrial gNB: much larger coverage areas, different power and antenna profiles, and different regulatory spectrum environments. A dedicated definition of channel bandwidth for the SAN was needed so that RF conformance requirements (emission masks, ACLR, receiver blocking, etc.) could be specified against a well-defined spectral reference for the satellite node.
The SAN channel bandwidth concept solves the ambiguity of applying terrestrial channel-bandwidth definitions to a node whose carrier may be configured differently in uplink and downlink and whose transmission bandwidth must be constrained within satellite-specific spectrum allocations. By defining it as the RF bandwidth supporting a single carrier with the transmission bandwidth configured in uplink or downlink, 3GPP allows the SAN to use asymmetric or direction-specific configurations while keeping a single, testable RF envelope.
It also enables coexistence and sharing studies: satellite bands are frequently shared with terrestrial IMT or fixed-satellite service systems, and a precise channel-bandwidth definition is a prerequisite for computing adjacent-channel interference and guard-band requirements. The term thus provides the regulatory and technical foundation for certifying SAN equipment and for planning carrier deployments in NTN.
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.
Initial definition introduced for NTN: the SAN channel bandwidth was defined as the RF bandwidth supporting a single NR RF carrier with the transmission bandwidth configured in the uplink or downlink, establishing the spectral reference for satellite access node RF requirements.
Defining Specifications
3GPP specifications that define or reference SAN channel bandwidth, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 36.108 vk00 | Satellite Access Node RF Requirements | Rel-20 read |
| TS 36.181 vj40 | RF Test Methods and Conformance for Satellite Access Nodes | Rel-19 read |
| TS 38.108 vk00 | NR NTN Satellite Access Node RF Requirements | Rel-20 read |
| TS 38.181 vj40 | NR Satellite Access Node RF Conformance Testing | Rel-19 read |