Description
Radio Navigation Satellite (RNS) refers to satellite-based systems that transmit signals used for determining position, velocity, and time (PVT) on Earth. In the context of 3GPP specifications, RNS encompasses global navigation satellite systems (GNSS) like GPS (USA), Galileo (EU), GLONASS (Russia), and BeiDou (China), which are integrated into mobile networks to provide location services. These systems operate by deploying constellations of satellites in medium Earth orbit, each broadcasting precise timing and orbital data. User equipment (UE), such as smartphones, receives signals from multiple satellites, calculates the time delay for each signal, and uses trilateration to compute its geographic coordinates with accuracy ranging from meters to centimeters, depending on the technology and assistance data.
The integration of RNS into 3GPP networks involves several architectural components and protocols. The UE includes a GNSS receiver capable of processing satellite signals, while the network provides assistance data through protocols like LTE Positioning Protocol (LPP) or Radio Resource Control (RRC). This assistance data, delivered from entities such as the Enhanced Serving Mobile Location Center (E-SMLC) or Location Management Function (LMF), includes information like satellite ephemeris, almanac, and timing, which accelerates the time-to-first-fix and improves accuracy, especially in challenging environments like urban canyons. 3GPP specs define interfaces and procedures for assisted GNSS (A-GNSS), where the network aids the UE in acquiring and processing satellite signals, reducing power consumption and enhancing performance.
RNS plays a critical role in 3GPP services, particularly for emergency calls (e.g., E911 in the US), where regulatory requirements mandate accurate location reporting. It also supports commercial applications like navigation, geofencing, and location-based advertising. In 5G and beyond, RNS integration extends to use cases such as vehicle-to-everything (V2X) communication, industrial IoT, and network synchronization. Specifications like 23.271 (Location Services) and 25.305 (Stage 2 functional specification of UE positioning in UTRAN) detail the requirements and procedures, ensuring interoperability between satellite systems and mobile networks. The evolution toward hybrid positioning, combining RNS with terrestrial methods like OTDOA or Wi-Fi, further enhances reliability and accuracy in diverse scenarios.
Purpose & Motivation
Radio Navigation Satellite (RNS) systems were incorporated into 3GPP standards to meet growing demands for accurate location-based services in mobile networks. Prior to integration, mobile positioning relied primarily on network-based methods like Cell-ID or timing advance, which offered limited accuracy (hundreds of meters to kilometers). As applications such as emergency services, navigation, and asset tracking required more precise location data, the inclusion of satellite-based positioning addressed these limitations by providing global coverage and meter-level accuracy.
The motivation for RNS integration stemmed from regulatory mandates, such as the FCC's E911 requirements in the United States, which compelled operators to provide precise location information for emergency calls. Additionally, the rise of smartphones and location-aware applications drove commercial need for reliable positioning. 3GPP standards evolved to support assisted GNSS (A-GNSS), where networks deliver satellite assistance data to UEs, reducing the time and power required for position fixes. This approach overcame challenges like slow standalone GNSS acquisition and poor signal reception indoors.
By standardizing RNS interfaces and procedures, 3GPP enabled interoperability across different satellite constellations and mobile technologies, from 2G to 5G. It solved problems related to accuracy, availability, and power efficiency, supporting a wide range of services from public safety to autonomous driving. The evolution continues with advancements like dual-frequency GNSS and integration with 5G NR positioning, enhancing performance for future use cases.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (3 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 18, the new support for 5G satellite charging was introduced for the RNS function within the 3GPP system. This enhancement specifically addresses the evolved radio access network (E-UTRAN) and its interaction with the core network for satellite-based access. The change provides the framework for charging procedures applicable to user equipment utilizing satellite radio links managed by the RNS.
- Introduce the support of 5G Satellite charging TS 32.240CR0486
In Release 19, the RNS function was enhanced to introduce support for store and forward satellite operation and UE-satellite-UE communication. This expanded the capabilities of the 3GPP system's radio access network to include new satellite-based communication modes. Additionally, the release added MVNO charging to provide for satellite service within the evolved packet system.
Explore further
Broader topics and technologies where RNS plays a role.
Defining Specifications
3GPP specifications that define or reference RNS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 23.009 vj00 | Handover Procedures in PLMNs | Rel-19 |
| TS 23.060 vj00 | GPRS Service Description Stage 2 | Rel-19 |
| TS 23.851 v1600 | Network Sharing Architecture for 3G Systems | Rel-6 |
| TR 23.908 v1400 | Pre-paging in GSM/UMTS networks | Rel-5 |
| TR 23.923 v1300 | Mobile IP+ Feasibility Study for UMTS/GPRS | Rel-4 |
| TS 25.301 vj00 | UE-UTRAN Radio Interface Protocol Architecture | Rel-19 |
| TS 25.302 vj00 | UTRA Physical Layer Services | Rel-19 |
| TS 25.321 vj00 | MAC Protocol Specification for UTRAN | Rel-19 |
| TS 25.401 vj00 | UTRAN Overall Architecture | Rel-19 |
| TS 25.402 vj00 | UTRAN Synchronisation Mechanisms | Rel-19 |
| TS 25.413 vj00 | Radio Access Network Application Part (RANAP) | Rel-19 |
| TS 25.420 vj00 | Iur Interface Introduction for UTRAN | Rel-19 |
| TS 25.423 vj00 | UTRAN RNSAP Specification | Rel-19 |
| TS 25.430 vj00 | Introduction to Iub Interface Specifications | Rel-19 |
| TS 25.453 vj00 | PCAP Protocol Specification | Rel-19 |
| TS 25.471 vj00 | RNSAP User Adaptation (RNA) for Iurh | Rel-19 |
| TR 25.931 vj00 | UTRAN Signalling Procedures Examples | Rel-19 |
| TS 32.102 vj00 | Telecom Management Physical Architecture Framework | Rel-19 |
| TS 32.240 vj40 | Charging Management Architecture & Principles | Rel-19 |
| TS 32.272 vj00 | Charging for Push-to-Talk over Cellular (PoC) | Rel-19 |
| TS 33.859 vb10 | UTRAN Key Hierarchy Enhancement Study | Rel-11 |
| TS 38.807 vg10 | NR beyond 52.6 GHz Study | Rel-16 |
| TS 43.129 vj00 | PS Handover in GERAN A/Gb and GAN Modes | Rel-19 |
| TS 43.130 vj00 | Iur-g Interface Overview | Rel-19 |
| TS 44.060 vj00 | GERAN RLC/MAC Protocol Specification | Rel-19 |