Description
Space Radiocommunication Stations (SRS) are a foundational element in 3GPP's standardization of Non-Terrestrial Networks (NTN). An SRS can be a satellite payload (e.g., a bent-pipe transponder or a regenerative processor) or a ground-based gateway station that communicates with satellites. In the architecture, the SRS forms the space-borne or ground-based radio interface for user equipment (UE) or for network nodes like gNBs. For a transparent payload (bent-pipe), the SRS receives, amplifies, frequency-converts, and retransmits the signal between the UE and a gateway on Earth. For a regenerative payload, the SRS includes onboard processing to demodulate/decode and then re-modulate/re-encode the signal, effectively acting as a base station in space.
The operation of an SRS is defined by stringent radio transmission and reception parameters to cope with the unique challenges of satellite links. These include very long propagation delays (up to hundreds of milliseconds), high Doppler shifts due to satellite motion, and significant path loss. The 3GPP specifications detail the required performance for SRS in terms of maximum output power, frequency stability, spurious emissions, and receiver sensitivity. The SRS must support specific 3GPP-defined waveforms and channel bandwidths, adapting terrestrial NR or LTE air interfaces for space-based propagation.
Key components of an SRS system include the antenna subsystem (often with steerable or multi-beam antennas for coverage area shaping), the radio frequency (RF) front-end for amplification and conversion, and the digital processing unit. For regenerative payloads, this includes baseband processing modules equivalent to a gNB's functions. The SRS's role is to extend the 3GPP radio access network (RAN) into space, providing service continuity, ubiquitous coverage, and backhaul connectivity in remote areas, over oceans, and for aerial vehicles. It is a critical node enabling direct communication between standard 3GPP UEs and satellites, as standardized from Release 15 onwards for 5G NTN.
Purpose & Motivation
The standardization of Space Radiocommunication Stations (SRS) within 3GPP was motivated by the growing need to integrate satellite networks with terrestrial mobile networks seamlessly. Historically, satellite communication operated in proprietary silos, using non-3GPP technologies that prevented interoperability with the billions of existing cellular devices. This created coverage gaps in rural, maritime, and aeronautical scenarios where terrestrial infrastructure is economically unviable. The purpose of defining SRS is to bring satellites into the 3GPP ecosystem as standardized radio nodes, enabling global and seamless service coverage.
By creating technical specifications for SRS, 3GPP addresses the limitations of previous fragmented approaches. It allows mobile network operators to incorporate satellite assets into their networks, using standardized interfaces and protocols. This solves critical problems such as providing disaster resilience when terrestrial networks fail, enabling Internet of Things (IoT) services over vast geographical areas, and supporting connectivity for moving platforms like ships and airplanes. The SRS definitions ensure that satellite networks can meet the same service quality, security, and mobility management expectations as terrestrial 5G networks, facilitating the vision of truly ubiquitous connectivity.
Key Features
- Support for both transparent (bent-pipe) and regenerative (on-board processing) payload architectures
- Adaptation of 3GPP NR and LTE radio interfaces for high-delay, high-Doppler satellite channels
- Definition of rigorous RF performance requirements (e.g., output power, frequency stability, spurious emissions)
- Enablement of global coverage, including polar regions, via satellite beams
- Support for feeder link (gateway-to-satellite) and service link (satellite-to-UE) operations
- Integration with 5G core network for end-to-end service management and mobility
Evolution Across Releases
Initial study item on Non-Terrestrial Networks (NTN). Defined foundational scenarios and identified key challenges for integrating satellites, including propagation delay, Doppler, and mobility management. Laid the groundwork for SRS requirements by analyzing use cases for 5G via satellite.
Enhanced NTN studies with a focus on deployment scenarios and architecture options. Started specifying channel models and performance requirements for satellite radio links, directly informing the technical parameters for future SRS specifications.
First normative specifications for 5G NTN support. Defined detailed RF requirements for SRS in TS 38.101 and TS 38.133. Specified adaptations for the NR physical layer (e.g., timing advance, HARQ) and RRC protocols to operate with SRS, covering both low-earth orbit (LEO) and geostationary (GEO) satellites.
Introduced enhancements for NTN, including support for direct device-to-satellite communication for IoT and handheld devices. Expanded SRS capabilities to better support mobility, network slicing over satellite, and improved integration with the 5G core network for service continuity.
Further evolution focusing on network energy efficiency for SRS operations, enhanced positioning services via satellites, and support for advanced satellite constellations. Worked on co-existence and interference mitigation between multiple SRS systems and terrestrial networks.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 26.522 | 3GPP TS 26.522 |
| TS 26.565 | 3GPP TS 26.565 |
| TS 26.854 | 3GPP TS 26.854 |
| TS 28.552 | 3GPP TS 28.552 |
| TS 36.111 | 3GPP TR 36.111 |
| TS 36.112 | 3GPP TR 36.112 |
| TS 36.141 | 3GPP TR 36.141 |
| TS 36.211 | 3GPP TR 36.211 |
| TS 36.212 | 3GPP TR 36.212 |
| TS 36.213 | 3GPP TR 36.213 |
| TS 36.214 | 3GPP TR 36.214 |
| TS 36.302 | 3GPP TR 36.302 |
| TS 36.321 | 3GPP TR 36.321 |
| TS 36.455 | 3GPP TR 36.455 |
| TS 36.459 | 3GPP TR 36.459 |
| TS 36.855 | 3GPP TR 36.855 |
| TS 37.355 | 3GPP TR 37.355 |
| TS 37.857 | 3GPP TR 37.857 |
| TS 37.910 | 3GPP TR 37.910 |
| TS 38.101 | 3GPP TR 38.101 |
| TS 38.133 | 3GPP TR 38.133 |
| TS 38.174 | 3GPP TR 38.174 |
| TS 38.176 | 3GPP TR 38.176 |
| TS 38.201 | 3GPP TR 38.201 |
| TS 38.202 | 3GPP TR 38.202 |
| TS 38.211 | 3GPP TR 38.211 |
| TS 38.212 | 3GPP TR 38.212 |
| TS 38.213 | 3GPP TR 38.213 |
| TS 38.214 | 3GPP TR 38.214 |
| TS 38.215 | 3GPP TR 38.215 |
| TS 38.300 | 3GPP TR 38.300 |
| TS 38.305 | 3GPP TR 38.305 |
| TS 38.331 | 3GPP TR 38.331 |
| TS 38.455 | 3GPP TR 38.455 |
| TS 38.521 | 3GPP TR 38.521 |
| TS 38.522 | 3GPP TR 38.522 |
| TS 38.523 | 3GPP TR 38.523 |
| TS 38.807 | 3GPP TR 38.807 |
| TS 38.820 | 3GPP TR 38.820 |
| TS 38.843 | 3GPP TR 38.843 |
| TS 38.857 | 3GPP TR 38.857 |
| TS 38.859 | 3GPP TR 38.859 |
| TS 38.863 | 3GPP TR 38.863 |
| TS 38.889 | 3GPP TR 38.889 |
| TS 38.912 | 3GPP TR 38.912 |