Description
A satellite beam is a directional radiation pattern produced by an antenna system on-board a satellite. In 3GPP non-terrestrial network (NTN) terminology, it represents the space-borne equivalent of a terrestrial cell: a defined coverage area on the Earth's surface illuminated by a controlled antenna pattern. Satellite payloads typically generate multiple beams simultaneously, either through fixed multi-beam antennas (e.g., a grid of spot beams) or through phased-array antennas that can steer and shape beams electronically. Each beam is characterised by its footprint size, gain profile, polarisation, frequency reuse plan, and the elevation angle under which it reaches the ground.
Architecturally, satellite beams sit at the boundary between the radio access network and the space segment. In a transparent (bent-pipe) architecture, the satellite payload simply amplifies and frequency-converts the signal between the service link (satellite-to-UE) and the feeder link (satellite-to-gateway), and the beam pattern determines which UEs can be served. In a regenerative architecture, the satellite carries gNB or gNB-DU functionality, and beams map more directly to cells managed by that on-board base station. 3GPP specifications such as 38.821 (solutions for NR to support NTN) and 38.742 (NG-RAN architecture for NTN) describe how beams relate to cells, tracking areas, and mobility procedures, while 36.763 covers NTN for NB-IoT/eMTC.
Beam behaviour is central to NTN mobility. Because LEO satellites move at roughly 7.5 km/s, their beams sweep across the Earth's surface, producing predictable but rapid changes in serving beam. 3GPP distinguishes Earth-fixed beams (where the footprint stays fixed on the ground, typically via steerable antennas or beam steering compensation) from Earth-moving beams (where the footprint moves with the satellite). This distinction drives different mobility mechanisms: Earth-moving beams require frequent cell reselection and handover, while Earth-fixed beams allow quasi-static cell identities and simpler idle-mode procedures. System information can carry satellite ephemeris data and beam-specific timing and Doppler pre-compensation parameters so that UEs can adjust their uplink transmission.
Beam design also governs link budget and capacity. Spot beams concentrate radiated power into a small area, increasing spectral efficiency and enabling frequency reuse across spatially separated beams. The trade-off is that narrower beams require more antenna aperture and more precise pointing, and the resulting footprints may be only tens or hundreds of kilometres across. Beam hopping, where the payload illuminates different beams in a time-multiplexed fashion, is another technique used to match capacity to demand. Inter-beam interference management, beam switching, and beam-level resource allocation are therefore active areas of standardisation and implementation.
For UEs, the beam concept appears in measurement and reporting procedures. A UE may measure multiple beams and report beam-level quality, and the network uses this information for beam management, handover decisions, and timing advance maintenance. In Rel-17 and later work, beam-related enhancements for NTN include support for UE location reporting, timing advance pre-compensation based on known beam geometry, and mobility robustness improvements for fast-moving beams.
Purpose & Motivation
Satellite beams exist because a satellite cannot efficiently serve an entire visible Earth disc with a single broad radiation pattern. Concentrating energy into narrow beams improves link budget, allows frequency reuse, and enables capacity density comparable to terrestrial networks in underserved areas. The concept solves the fundamental problem of delivering broadband or IoT connectivity from space with limited satellite power and antenna aperture.
Historically, early satellite systems used global or regional beams with low gain, requiring large ground terminals. The shift to multi-beam and spot-beam payloads, combined with 3GPP NTN standardisation from Rel-16 onward, made it feasible to serve small, low-power user devices directly. 3GPP needed a precise term to describe the space-borne coverage unit so that mobility, measurement, and resource management procedures could be defined consistently across transparent and regenerative architectures.
The beam concept also addresses the need to reconcile satellite motion with cellular mobility frameworks. By defining beams and their relationship to cells, 3GPP enables networks to predict coverage changes from ephemeris data rather than relying solely on UE measurements, which is essential for reliable service under the very short dwell times typical of LEO constellations.
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 Satellite beam, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 36.763 vh00 | NB-IoT/eMTC Support for Non-Terrestrial Networks | Rel-17 read |
| TS 38.742 vk00 | GNSS Resilient NR-NTN Operation Study | Rel-20 read |
| TS 38.821 vg20 | NR Support for Non-Terrestrial Networks | Rel-16 read |