Description
The Multi-functional Satellite Augmentation System (MSAS) is a Satellite-Based Augmentation System (SBAS) standardized within 3GPP to improve the performance of Global Navigation Satellite Systems (GNSS) for cellular user equipment (UE). Operationally, MSAS refers to systems like the Japanese QZSS-based augmentation or similar regional SBAS (e.g., WAAS, EGNOS). It broadcasts correction data (for satellite orbit, clock, and ionospheric delays) and integrity information via geostationary satellites on the L1 frequency (1575.42 MHz). This data is received directly by GNSS-capable UEs or can be delivered to the UE through the 3GPP network as part of Assisted-GNSS (A-GNSS) protocols, significantly enhancing positioning accuracy and reliability.
Architecturally, MSAS integrates with the 3GPP location services (LCS) architecture. Key network elements include the Secure User Plane Location (SUPL) Enabled Terminal (SET), which is the UE, and the SUPL Location Platform (SLP). For control-plane solutions, the Serving Mobile Location Center (SMLC) or Evolved SMLC (E-SMLC) in LTE/NR communicates with the UE. The MSAS augmentation data can be provided to these network elements from reference networks or directly from SBAS service providers. The UE's GNSS receiver uses MSAS corrections to compute a more precise position, reducing errors from atmospheric effects and satellite ephemeris inaccuracies to sub-meter levels in open-sky conditions.
How it works involves the UE acquiring GNSS signals (e.g., GPS) and simultaneously decoding the MSAS augmentation signals from geostationary satellites. The correction parameters are applied in the positioning calculation algorithm. In A-GNSS modes, the network may provide MSAS correction data or integrity data to the UE over LTE or NR radio bearers using protocols like Radio Resource Control (RRC) or LTE Positioning Protocol (LPP). This assists UEs with weak direct satellite reception. MSAS also provides integrity flags, warning the UE if a particular GNSS satellite's signal is unreliable, which is critical for safety-of-life applications. Its role is to enable high-accuracy, high-integrity positioning services mandated for emergency calls (E911/E112), navigation, and emerging services like V2X, which depend on trustworthy location data.
Purpose & Motivation
MSAS was incorporated into 3GPP standards to address the inherent limitations of standalone GNSS in mobile environments, particularly for emergency services and commercial location-based applications. Standalone GPS/GNSS can have accuracy reduced to 10+ meters due to ionospheric delays, satellite clock errors, and ephemeris inaccuracies, and it lacks a certified integrity monitoring mechanism. For emergency call location (e.g., E112 in Europe), regulatory requirements demand improved accuracy and reliability, which augmentation systems like MSAS provide.
The historical motivation stems from aviation safety systems, where SBAS like WAAS and MSAS were developed to enable precision approaches. 3GPP recognized the value of these existing infrastructures for terrestrial mobile users. By integrating MSAS support, the standards enabled mobile networks to meet stricter positioning requirements without solely relying on network-based methods like Observed Time Difference of Arrival (OTDOA), which have deployment limitations. It solved the problem of providing ubiquitous, high-integrity positioning in both urban canyons (via assistance data) and open areas, enhancing services like turn-by-turn navigation, geofencing, and location-aware billing.
Furthermore, MSAS support future-proofed 3GPP systems for emerging applications in IoT and autonomous systems, where precise and reliable positioning is non-negotiable. It represents a convergence of satellite navigation and cellular communication technologies, allowing operators to offer enhanced location services by leveraging publicly available augmentation signals, thus reducing dependency on proprietary assistance data and improving interoperability across global regions with different SBAS providers.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (24 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-8, normative work from Rel-16.
In Release 16, the MSAS function was enhanced with the introduction of support for the B1C signal within the BeiDou (BDS) system for A-GNSS positioning. The specification also updated the BDS B1I signal Interface Control Document (ICD) file to version 3.0 for A-GNSS. Furthermore, Release 16 introduced new GNSS Integer Ambiguity Level Indications to improve positioning accuracy.
- Introduction of B1C signal in BDS system in A-GNSS TS 37.355CR0248
- Introducing support for GNSS Integer Ambiguity Level Indications TS 37.355CR0252
- Update B1I signal ICD file to v3.0 in BDS system in A-GNSS TS 37.355CR0259
- Correction of reference TRP for DL-AoD and Multi-RTT measurement report TS 37.355CR0330
In Release 17, the MSAS function introduced support for including NMEA GGA sentence information within high-accuracy GNSS location estimates and added clarifications for GNSS SSR (State Space Representation) corrections, including orbit and clock integrity bounds and tropospheric delay correction field descriptions. These enhancements aimed to improve the interoperability and accuracy of multi-GNSS positioning, with specific updates for BDS and Galileo signal references to align with external standards like RTCM. The release also included corrections and clarifications for multi-RTT timing error margins and field definitions for high-accuracy metrics and integrity parameters like URA.
- NMEA GGA sentence info in high accuracy GNSS location estimates [HA-GNSS-NMEA] TS 37.355CR0349
- Correction on the GNSS Orbit and Clock Integrity Bounds in TS 37.355 TS 37.355CR0377
- Corrections on applicability of timing error margin of RxTEG in NR-Multi-RTT-SignalMeasurementInformation field descriptions and other Miscellaneous corrections TS 37.355CR0431
- Correction to Multi-RTT TS 37.355CR0455
- GNSS SSR BDS orbit emphemeris reference clarification to align with RTCM TS 37.355CR0461
- Field description correction for HA-GNSS metrics TS 37.355CR0474
+ 4 more changes
In Release 18, the MSAS function introduced new assistance information for GNSS Line-of-Sight and Non-Line-of-Sight (LOS/NLOS) conditions and added support for Satellite Phase Center Variation (PCV) Residuals in State Space Representation (SSR) data. The release also included corrections and enhancements to A-GNSS positioning capabilities, such as updates to almanac support, UTC model support, and specific parameters for systems including NavIC. These refinements improve the accuracy and robustness of satellite-based positioning for location services.
- GNSS LOS/NLOS assistance information [GNSS LOS/NLOS] TS 37.355CR0446
- SSR Satellite PCV Residuals [Rel18PCV] TS 37.355CR0465
- Miscellaneous RIL corrections for GNSS LOS/NLOS [GNSS LOS/NLOS] TS 37.355CR0495
- Correction of NR-DL-TDOA-MeasurementCapability and NR-Multi-RTT-MeasurementCapability TS 37.355CR0528
- Correction on GNSS-AlmanacSupport and GNSS-UTC-ModelSupport in A-GNSS positioning TS 37.355CR0518
- Correction on NavIC almanac set IE, and field descriptions under KlobucharModelParamater and GNSS-SystemTime. TS 37.355CR0534
In Release 19, the MSAS (Multi-functional Satellite Augmentation System) function was enhanced by introducing support for the NavIC L1 SPS and BDS B2b signals within the A-GNSS framework via the LPP protocol. It also added a new UE capability to request equalIntegerAmbiguityLevel assistance data for improved positioning accuracy. Furthermore, the release included miscellaneous corrections to LPP procedures related to GNSS line-of-sight and non-line-of-sight conditions.
Explore further
Broader topics and technologies where MSAS plays a role.
Defining Specifications
3GPP specifications that define or reference MSAS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.071 vj00 | 3GPP TS 22.071: Location Services (LCS) Stage 1 | Rel-19 |
| TS 25.305 vj00 | UTRAN UE Positioning Stage 2 | Rel-19 |
| TS 25.306 vj00 | UE Radio Access Capabilities Specification | Rel-19 |
| TS 25.331 vj00 | UTRAN RRC Protocol Specification | Rel-19 |
| TS 25.423 vj00 | UTRAN RNSAP Specification | Rel-19 |
| TS 25.433 vj00 | Node B Application Part (NBAP) Protocol | Rel-19 |
| TS 25.453 vj00 | PCAP Protocol Specification | Rel-19 |
| TS 36.355 vj00 | LTE Positioning Protocol (LPP) | Rel-19 |
| TS 37.355 vj20 | LTE Positioning Protocol (LPP) | Rel-19 |
| TS 38.455 vj10 | NR Positioning Protocol A (NRPPa) | Rel-19 |
| TS 44.031 vj00 | Radio Resource LCS Protocol (RRLP) | Rel-19 |