Description
Low-Earth Orbiting (LEO) satellites refer to artificial satellites that orbit the Earth at altitudes typically ranging from 500 to 2,000 kilometers. Within the 3GPP framework, starting from Release 14 study items and concretely in Release 15 onwards, LEO satellites are a primary focus for Non-Terrestrial Networks (NTN). They are integrated as aerial access nodes or relay nodes to provide seamless 5G (and beyond) service continuity and global coverage. Unlike Geostationary Earth Orbit (GEO) satellites, LEO satellites move rapidly relative to the Earth's surface, resulting in shorter orbital periods (approximately 90-120 minutes) and smaller coverage areas (cells) on the ground that are in constant motion.
From a network architecture perspective, a LEO satellite in a 3GPP NTN can act as a radio access node (effectively a cell tower in space), a transparent payload (bent-pipe relay), or a regenerative payload (with onboard base station functions). When acting as a transparent payload, the satellite simply amplifies and converts the frequency of the signal between the ground-based gateway (Next Generation NodeB - gNB) and the User Equipment (UE). The gateway connects to the 5G core network. In a regenerative architecture, the satellite contains a full gNB, processing the signal in orbit and connecting directly to the core network via an inter-satellite link or a dedicated ground gateway. The key technical challenge is managing the high Doppler shift due to the satellite's high velocity, large propagation delays (though significantly lower than GEO), and the continuous handovers required as beams move across the Earth.
The integration involves significant enhancements to the 5G New Radio (NR) and core network protocols. The physical layer (covered in specs like 38.101 and 38.108) is adapted to handle larger timing advance values, specific reference signals for tracking, and compensation for Doppler frequency shift. The Radio Resource Control (RRC) layer and mobility management procedures are enhanced to support predictable satellite movement, long cell dwell times, and efficient handover between moving beams or between satellite and terrestrial networks. The core network supports service continuity for UEs moving in and out of satellite coverage. The ultimate role of LEO satellites in 3GPP is to extend the reach of 5G services to airplanes, ships, and remote land areas, creating a truly global network fabric.
Purpose & Motivation
The integration of LEO satellites into 3GPP standards is driven by the imperative to provide ubiquitous, seamless connectivity beyond the reach of traditional terrestrial networks. Terrestrial cellular coverage is economically and geographically limited, leaving vast oceanic, aerial, and remote rural areas without service. Previous satellite communication systems operated in proprietary silos, with high latency (especially GEO systems) and no integration with mainstream consumer mobile devices or core networks. This created a coverage gap for critical services like maritime communications, in-flight connectivity, and disaster response.
3GPP's work on NTN, with LEO as a cornerstone, aims to solve this by making satellite access a native component of the 5G system. This allows a standard 5G smartphone, with some enhancements, to potentially connect directly to a LEO satellite network without specialized hardware, enabling global roaming and service continuity. The motivation includes supporting United Nations sustainable development goals for connectivity, enabling Internet of Things (IoT) services in agriculture and logistics across remote regions, and providing resilient back-up for terrestrial networks during failures or disasters.
Technically, LEO satellites were chosen over GEO because their lower altitude (500-2000 km vs 36,000 km) results in much lower propagation latency (20-40 ms vs 500+ ms), making them suitable for latency-sensitive 5G services. The proliferation of mega-constellations (like SpaceX's Starlink) demonstrated the commercial viability of dense LEO networks, prompting 3GPP to standardize interfaces and procedures to leverage this new infrastructure. The standardization ensures interoperability between different satellite operators and terrestrial network operators, fostering a competitive ecosystem and preventing vendor lock-in.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-14, normative work from Rel-18.
In Release 18, specific support for Low-Earth Orbiting (LEO) satellite access was formalized, including a defined end-to-end latency requirement of up to 31 ms for LEO-based services. The release also clarified the operational distinctions and usage between LEO and other Non-Geostationary Satellite Orbit (NGSO) types like MEO, particularly for scenarios involving UE switching between satellites with different orbital characteristics. Furthermore, it introduced the capability for the system to collect distinct charging information for user traffic traversing different satellite orbit types, including LEO.
Explore further
Broader topics and technologies where LEO plays a role.
Defining Specifications
3GPP specifications that define or reference LEO, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.261 vk30 | 5G System Service Requirements | Rel-20 |
| TS 22.822 vg00 | Satellite Access in 5G Study | Rel-16 |
| TS 22.887 vk00 | Study on satellite access - Phase 4 | Rel-20 |
| TS 23.008 vj00 | Organization of Subscriber Data | Rel-19 |
| TS 23.501 vk00 | 5G System Architecture Stage 2 | Rel-20 |
| TS 23.700 vk00 | XR Services Application Enablement Layer | Rel-20 |
| TR 23.737 vh20 | Satellite Access in 5G Architecture Study | Rel-17 |
| TR 23.799 ve00 | Study on Next Generation System Architecture | Rel-14 |
| TS 24.229 vj50 | IMS call control protocol based on SIP and SDP | Rel-19 |
| TS 24.301 vj60 | NAS protocol for Evolved Packet System | Rel-19 |
| TS 24.501 vj50 | 5G NAS Protocols Specification | Rel-19 |
| TR 28.808 vh00 | 5G satellite integration management study | Rel-17 |
| TR 28.841 vi01 | Technical Report on IoT NTN Enhancements | Rel-18 |
| TS 28.874 vj10 | Study on Management Aspects of NTN Phase 2 | Rel-19 |
| TS 29.212 vj00 | Gx/Gxx/Sd/St Diameter Protocol | Rel-19 |
| TS 29.512 vj40 | 5G Session Management Policy Control Service | Rel-19 |
| TS 29.514 vj40 | 5G System; Policy Authorization Service; Stage 3 | Rel-19 |
| TS 29.523 vj20 | 5G Policy Control Event Exposure Service | Rel-19 |
| TS 29.571 vj50 | Common Data Types for 5G Service Based Interfaces | Rel-19 |
| TS 33.700 | 3GPP TR 33.700 | Rel-14 |
| TS 36.102 vj10 | E-UTRA UE Satellite Access RF Requirements | Rel-19 |
| TS 36.108 vj10 | Satellite Access Node RF Requirements | Rel-19 |
| TS 36.181 vj30 | E-UTRA RF Test Methods for Satellite Access Node | Rel-19 |
| TS 36.300 vj00 | E-UTRAN Radio Interface Protocol Architecture Overview | Rel-19 |
| TS 36.521 vj00 | E-UTRA UE Conformance ICS Proforma | Rel-19 |
| TR 36.763 vh00 | NB-IoT/eMTC Support for Non-Terrestrial Networks | Rel-17 |
| TS 38.101 vj31 | NR User Equipment Radio Transmissions | Rel-19 |
| TS 38.108 vj20 | NTN NR Satellite Access Node RF Requirements | Rel-19 |
| TS 38.181 vj10 | NR Satellite Access Node RF Testing | Rel-19 |
| TS 38.300 vj00 | NG-RAN Overall Description | Rel-19 |
| TS 38.331 vj00 | NR Radio Resource Control (RRC) Protocol Specification | Rel-19 |
| TS 38.521 vj20 | NR Physical Layer UE Conformance Testing | Rel-19 |
| TS 38.741 vj00 | NTN L-/S-band for NR Technical Specification | Rel-19 |
| TS 38.811 vf40 | Study on NR Support for Non-Terrestrial Networks | Rel-15 |
| TS 38.821 vg20 | NR Support for Non-Terrestrial Networks | Rel-16 |
| TS 38.863 vj10 | NR NTN RF and Co-existence Spec | Rel-19 |
| TR 38.913 vj00 | Next Gen Access Tech Scenarios & Requirements | Rel-19 |