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
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-12, normative work from Rel-18.
In Release 18, the 5G system's capability to support Medium-Earth Orbit satellite access was formally specified, including the requirement to support MEO-based access with an end-to-end latency of up to 203 ms. The system must also support the selection and switching of suitable satellites, including those in MEO, based on characteristics like altitude and orbital dynamics. Furthermore, Release 18 enables the collection of distinct charging information for user traffic traversing satellites of different orbit types, including MEO.
- Clarification of local switch via UPF on GEO satellites TS 23.501CR4422
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 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 |
| 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 |
| 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 vj40 | Edge Computing Management (ECM) | 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 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-12 |
| TS 36.102 vj10 | E-UTRA UE Satellite Access RF Requirements | Rel-19 |
| TS 36.171 vj10 | A-GNSS Minimum Performance Requirements for UE | 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.171 vj10 | 5G A-GNSS UE Positioning Requirements | Rel-19 |
| TS 38.300 vj00 | 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 vj10 | NR NTN RF and Co-existence Spec | Rel-19 |
| TR 38.913 vj00 | Next Gen Access Tech Scenarios & Requirements | Rel-19 |