Description
Medium-Earth Orbiting (MEO) satellites are a critical element within 3GPP's Non-Terrestrial Network (NTN) architecture, designed to extend 5G and future cellular services globally. They operate in orbits ranging from approximately 2,000 kilometers to just below the geostationary belt at 35,786 kilometers. This orbital altitude represents a strategic compromise, offering a significantly wider coverage footprint per satellite compared to Low-Earth Orbit (LEO) constellations while providing much lower signal latency and reduced path loss compared to Geostationary Earth Orbit (GEO) satellites. Within the 3GPP system, MEO satellites are integrated as either transparent (bent-pipe) or regenerative (on-board processing) payloads. As transparent payloads, they simply amplify and convert frequencies between the gateway earth station (known as the NTN Gateway) and the User Equipment (UE). Regenerative payloads, which are more complex, can demodulate, decode, switch, and re-encode signals on-board, effectively functioning as base stations in the sky (gNodeBs).
The integration of MEO satellites into the 3GPP radio access network (RAN) requires specific adaptations to handle the unique characteristics of satellite links. Key technical challenges addressed in the specifications include very long propagation delays (ranging from tens to over a hundred milliseconds), high Doppler shifts due to satellite motion relative to the ground, and significant path loss. The 3GPP RAN and Core Network protocols are enhanced to support these conditions. For instance, timing advance procedures are modified, hybrid automatic repeat request (HARQ) processes are adapted or disabled for very long delay scenarios, and scheduling is adjusted. The core network, via the Access and Mobility Management Function (AMF) and Session Management Function (SMF), must also be aware of the serving satellite's characteristics for proper mobility and session management, especially as UEs are handed over between satellite beams or between satellites.
MEO satellites play a pivotal role in achieving true global and seamless connectivity. They are a foundational technology for 5G NTN, enabling service continuity for terrestrial networks and providing direct-to-device or backhaul services. Architecturally, they connect to ground-based NTN Gateways, which then interface with the standard 5G Core Network (5GC). This allows MEO constellations to provide 3GPP-defined services like enhanced Mobile Broadband (eMBB) and massive IoT (mIoT) in regions without terrestrial infrastructure. The specifications covering MEO span service requirements (22-series), system architecture (23-series), protocols (24-, 25-, 36-, 38-series), and management (28-, 32-series), ensuring a comprehensive framework for satellite-integrated cellular networks.
Purpose & Motivation
The standardization of MEO satellites within 3GPP was motivated by the need to extend high-quality mobile broadband and IoT services to unserved and underserved regions globally. Traditional terrestrial networks are economically challenging to deploy in remote areas, over oceans, and in airspace. Prior to 3GPP's formal integration, satellite communication existed as a separate, often proprietary ecosystem with limited interoperability with cellular devices and services. The purpose of defining MEO in 3GPP standards is to bridge this gap, creating a unified network architecture where satellites are a native, integrated component rather than an external add-on.
This integration solves critical problems of coverage, resilience, and service continuity. It addresses the coverage gap problem by providing a scalable solution for global connectivity, which is essential for applications like maritime and aeronautical communications, disaster response, and rural broadband. Furthermore, it enhances network resilience by providing an alternative backhaul or access layer during terrestrial network failures caused by natural disasters. From a service perspective, it enables seamless mobility for users traveling between terrestrial and satellite coverage areas, a concept fundamental to the 3GPP vision of ubiquitous connectivity.
The creation of MEO standards was historically driven by the convergence of the satellite and telecom industries and the launch of new MEO constellations (like O3b and its successors). 3GPP Release 15 began the serious study of Non-Terrestrial Networks, with subsequent releases refining the architecture and protocols. MEO's specific orbital characteristics offered a viable middle-ground for early 5G NTN deployments, balancing the constellation size (number of satellites needed) against latency and ground station complexity, making it a strategically important component of the overall NTN portfolio defined by 3GPP.
Classification
Evolution Across Releases
Initial study and feasibility analysis for satellite access integration into 3GPP systems began. This release laid the groundwork by identifying key scenarios and challenges, such as long delay and high mobility, associated with satellite communications including MEO orbits.
Enhanced studies on architecture enhancements for satellite backhaul and direct access. Work continued on defining use cases and requirements for integrating satellite components, focusing on the network impacts of MEO and other satellite types.
Further refined scenarios and channel models for non-terrestrial networks. The study item on 'New Services and Markets Technology Enablers' included satellite, paving the way for more concrete architecture work in later releases.
Marked the start of formal normative work on 'Non-Terrestrial Networks (NTN)' as part of 5G. While initially focused on feasibility, it established key principles for supporting MEO satellites, including transparent satellite operation models.
Introduced first-phase normative specifications for NTN support in 5G NR. This included specific adaptations for radio protocols to handle MEO satellite characteristics like long delay and Doppler shift for both transparent and regenerative payloads.
Significantly expanded NTN support, including enhancements for IoT (NB-IoT, eMTC) over satellites and improved mobility management. MEO-specific parameters and performance requirements were more concretely defined in RAN and core network specs.
Focused on evolution towards 'NTN-Advanced', including support for regenerative payloads with more advanced on-board processing, improved integration with 5GC, and enhanced positioning for MEO-based services.
Further enhancements for network-controlled repeaters, sidelink over NTN, and mobility optimizations for dynamic MEO constellations. Work continued on improving spectral efficiency and capacity for MEO satellite links.
Ongoing work towards future 6G-era NTN, exploring ultra-dense MEO constellations, AI/ML-based optimization for satellite resource management, and deeper integration with terrestrial network slicing.
Explore further
Broader topics and technologies where MEO plays a role.
Defining Specifications
3GPP specifications that define or reference MEO, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.261 vk70 | 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 vk20 | 5G System Architecture Stage 2 | Rel-20 |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 |
| TR 23.737 vh20 | Satellite Access in 5G Architecture Study | Rel-17 |
| TS 24.229 vk00 | IMS Call Control Protocol based on SIP | Rel-20 |
| TS 24.301 vk00 | 3GPP TS 24301 vk00: NAS Protocols for EPS | Rel-20 |
| TS 24.501 vk00 | 5G System (5GS) Non-Access Stratum (NAS) Protocol | Rel-20 |
| TS 25.172 vj00 | A-GANSS UE Minimum Performance Requirements (FDD) | Rel-19 |
| TS 25.173 vj00 | A-GANSS Performance Requirements (TDD) | Rel-19 |
| TS 28.538 vj50 | Management and orchestration for edge computing | 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 29.212 vj10 | Diameter-based Gx, Gxx, Sd, St Interfaces | Rel-19 |
| TS 29.512 vk00 | Session Management Policy Control Service | Rel-20 |
| TS 29.514 vk00 | 3GPP TS 29514 vk00: Policy Authorization Service | Rel-20 |
| TS 29.523 vk00 | Policy Control Event Exposure Service | Rel-20 |
| TS 29.571 vk00 | Common Data Types for 5G SBI APIs | Rel-20 |
| TS 33.700 | 3GPP TR 33.700 | Rel-12 |
| TS 36.102 vj40 | E-UTRA UE RF Requirements for Satellite Access | Rel-19 |
| TS 36.171 vj10 | A-GNSS Minimum Performance Requirements for UE | Rel-19 |
| TS 36.300 vj20 | E-UTRAN Radio Interface Protocol Architecture | Rel-19 |
| TS 36.521 vj11 | E-UTRA UE Conformance Testing for Satellite Access | Rel-19 |
| TR 36.763 vh00 | NB-IoT/eMTC Support for Non-Terrestrial Networks | Rel-17 |
| TS 38.171 vj10 | 5G A-GNSS UE Positioning Requirements | Rel-19 |
| TS 38.300 vj30 | NR and NG-RAN Overall Description | 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 vj40 | NR NTN RF and Coexistence Specifications | Rel-19 |
| TR 38.913 vj00 | Next Gen Access Tech Scenarios & Requirements | Rel-19 |