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.
Key Features
- Orbital altitude of 500-2000 km enabling low latency (20-40 ms)
- High velocity relative to Earth requiring advanced Doppler compensation
- Can function as transparent (bent-pipe) or regenerative (onboard gNB) payloads
- Integrated into 5G as a Non-Terrestrial Network (NTN) component
- Provides moving cell coverage on Earth's surface
- Enables direct-to-device or gateway-mediated connectivity
Evolution Across Releases
Initiated study items on using satellite access in 5G systems. Focused on identifying use cases, deployment scenarios, and channel models for NTN, with LEO satellites as a key component. This release laid the conceptual groundwork and requirements for technical standardization in subsequent releases.
Defining Specifications
| Specification | Title |
|---|---|
| TS 22.261 | 3GPP TS 22.261 |
| TS 22.822 | 3GPP TS 22.822 |
| TS 22.887 | 3GPP TS 22.887 |
| TS 23.008 | 3GPP TS 23.008 |
| TS 23.501 | 3GPP TS 23.501 |
| TS 23.700 | 3GPP TS 23.700 |
| TS 23.737 | 3GPP TS 23.737 |
| TS 23.799 | 3GPP TS 23.799 |
| TS 24.229 | 3GPP TS 24.229 |
| TS 24.301 | 3GPP TS 24.301 |
| TS 24.501 | 3GPP TS 24.501 |
| TS 28.808 | 3GPP TS 28.808 |
| TS 28.841 | 3GPP TS 28.841 |
| TS 28.874 | 3GPP TS 28.874 |
| TS 29.212 | 3GPP TS 29.212 |
| TS 29.512 | 3GPP TS 29.512 |
| TS 29.514 | 3GPP TS 29.514 |
| TS 29.523 | 3GPP TS 29.523 |
| TS 29.571 | 3GPP TS 29.571 |
| TS 33.700 | 3GPP TR 33.700 |
| TS 36.102 | 3GPP TR 36.102 |
| TS 36.108 | 3GPP TR 36.108 |
| TS 36.181 | 3GPP TR 36.181 |
| TS 36.300 | 3GPP TR 36.300 |
| TS 36.521 | 3GPP TR 36.521 |
| TS 36.763 | 3GPP TR 36.763 |
| TS 38.101 | 3GPP TR 38.101 |
| TS 38.108 | 3GPP TR 38.108 |
| TS 38.181 | 3GPP TR 38.181 |
| TS 38.300 | 3GPP TR 38.300 |
| TS 38.331 | 3GPP TR 38.331 |
| TS 38.521 | 3GPP TR 38.521 |
| TS 38.741 | 3GPP TR 38.741 |
| TS 38.811 | 3GPP TR 38.811 |
| TS 38.821 | 3GPP TR 38.821 |
| TS 38.863 | 3GPP TR 38.863 |
| TS 38.913 | 3GPP TR 38.913 |