Description
Slant Total Electron Content (STEC) is a geophysical parameter representing the integral of the free electron density along a specific line-of-sight path between a Global Navigation Satellite System (GNSS) satellite and a receiver on or near the Earth's surface. It is measured in Total Electron Content Units (TECU), where 1 TECU = 10^16 electrons per square meter. In the context of 3GPP standards, STEC is a key data element used for advanced positioning techniques, particularly for correcting ionospheric-induced errors in GNSS measurements. The ionosphere, a layer of the atmosphere ionized by solar radiation, slows down and bends radio signals, introducing a variable delay that is a major source of error in satellite-based positioning.
Architecturally, STEC data is utilized within the Location Management Function (LMF) in the 5G core network or the Enhanced Serving Mobile Location Centre (E-SMLC) in LTE. The network can assist UEs in their positioning calculations by providing STEC information or correction data. The process involves several components: GNSS reference networks (e.g., Continuously Operating Reference Stations - CORS), which continuously track satellite signals and calculate STEC; these values are then processed to create ionospheric models or correction streams. These corrections can be delivered to the UE via control plane (e.g., LTE Positioning Protocol - LPP, NR Positioning Protocol - NRPPa) or user plane methods.
How it works technically: The raw GNSS observables (pseudorange and carrier phase) measured by a receiver are affected by the ionosphere. The delay is frequency-dependent (dispersive). By using dual-frequency GNSS receivers (e.g., receiving L1 and L5 signals from GPS), the STEC along the satellite-receiver path can be directly estimated because the difference in the measured pseudoranges at the two frequencies is proportional to the STEC. The formula involves the difference between the pseudoranges (or carrier phases) divided by a known constant related to the frequencies. Once STEC is estimated for a reference station, it can be interpolated or modeled to provide corrections for nearby UEs. The 3GPP specifications define how this STEC information or derived Vertical TEC (VTEC) models can be packaged and transmitted to the UE to improve its position solution.
Key components in the 3GPP ecosystem include the GNSS assistance data elements defined in LPP, which can contain ionospheric delay corrections modeled from STEC data. The specifications (e.g., 37.355 for LPP, 38.305 for NR positioning architecture) detail the formats and procedures. The role of STEC is to transition GNSS positioning from meter-level accuracy to decimeter or even centimeter-level accuracy when used with Real-Time Kinematic (RTK) or Precise Point Positioning (PPP) techniques. It is especially crucial for demanding applications like autonomous driving, drone navigation, and precision agriculture, where sub-meter accuracy is mandatory.
Purpose & Motivation
The integration of STEC data into 3GPP standards was motivated by the escalating demand for high-precision positioning across numerous industries. Traditional standalone GNSS, even with standard assistance data, is limited to several meters of accuracy due to errors from satellite clocks, orbits, and most variably, the ionosphere. The ionospheric delay can introduce errors from a few meters to over 20 meters depending on solar activity, time of day, and geographical location. Prior approaches relied on single-frequency receivers using generic ionospheric models (like the Klobuchar model), which only correct about 50-70% of the error. This was insufficient for emerging use cases in Release 16 and beyond, such as V2X, industrial IoT, and augmented reality.
STEC-based corrections address this fundamental limitation by providing much more accurate, localized, and real-time information about the ionospheric conditions. The problem it solves is the single largest variable error source in satellite positioning. By incorporating STEC data into network-assisted and network-based positioning protocols, 3GPP enables mass-market devices to achieve precision previously reserved for expensive survey-grade equipment with dedicated correction services. This was a key enabler for positioning as a 5G service.
Historically, high-precision GNSS corrections were delivered via satellite-based augmentation systems (SBAS) or private terrestrial networks (e.g., RTK networks). The 3GPP initiative, particularly in Release 16 with the 5G positioning enhancements, aimed to leverage the ubiquitous cellular network as a reliable, low-latency delivery channel for these corrections. This convergence of telecommunications and geopositioning creates a scalable and standardized platform. The creation of STEC as a defined parameter within 3GPP specs (like 37.355) allows for interoperability between different GNSS correction service providers and device manufacturers, fostering an ecosystem for precise positioning as an integral part of the cellular service offering.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (29 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 16, the STEC (Slant Total Electron Content) function was not explicitly introduced or detailed in the provided grounding context. The specified changes for Release 16 primarily involved updates to A-GNSS assistance data, including the introduction of the B1C signal for the BeiDou (BDS) system, updates to the B1I signal ICD file, and the introduction of support for GNSS Integer Ambiguity Level Indications. The core technical descriptions of network-assisted GNSS methods, state space representations, and assistance data types like ionospheric models remained consistent with pre-Release 16 capabilities as outlined in the grounding text.
- Introduction of B1C signal in BDS system in A-GNSS TS 36.305CR0083
- Introduction of B1C signal in BDS system in A-GNSS TS 37.355CR0248
- Introducing support for GNSS Integer Ambiguity Level Indications TS 37.355CR0252
- Introduction of B1C signal in BDS system in A-GNSS TS 38.305CR0013
- Update B1I signal ICD file to v3.0 in BDS system in A-GNSS TS 36.305CR0088
- Update B1I signal ICD file to v3.0 in BDS system in A-GNSS TS 37.355CR0259
+ 3 more changes
In Release 17, the STEC (Slant Total Electron Content) function was enhanced through updates to GNSS integrity and correction data. Specifically, this included corrections and clarifications to the GNSS Orbit and Clock Integrity Bounds and the GNSS Tropospheric Delay Correction field description to improve the accuracy of state space representation (SSR) corrections. These refinements help provide more precise ionospheric and error modeling data to the UE for high-accuracy positioning.
- Introduction of B2a and B3I signal in BDS system and GNSS Positioning Integrity TS 36.305CR0107
- 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
- GNSS SSR BDS orbit emphemeris reference clarification to align with RTCM TS 37.355CR0461
- Field description correction for HA-GNSS metrics TS 37.355CR0474
- Correcting field description and definition of GNSS-SSR-URA TS 37.355CR0400
+ 2 more changes
In Release 18, the STEC (Slant Total Electron Content) function was not explicitly mentioned in the provided CR titles or grounding context. The documented changes for GNSS positioning in this release focused on corrections and enhancements to existing assistance data, including refinements to GNSS LOS/NLOS assistance information, miscellaneous RIL corrections, and specific corrections to almanac and timing model support for systems like NavIC. These updates aimed to improve the accuracy and reliability of network-assisted GNSS methods by refining the underlying assistance data parameters provided to the UE.
- GNSS LOS/NLOS assistance information [GNSS LOS/NLOS] TS 37.355CR0446
- Miscellaneous RIL corrections for GNSS LOS/NLOS [GNSS LOS/NLOS] TS 37.355CR0495
- 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 STEC function was enhanced through the introduction of support for new GNSS signals, specifically the NavIC L1 SPS and BDS B2b signals, within the A-GNSS framework across LTE and NR specifications. This expansion was detailed in updates to the LPP and stage 2 specifications, enabling more precise ionospheric correction data for positioning. The release also included corrections and miscellaneous updates to LPP procedures related to GNSS line-of-sight conditions.
- Introduction of NavIC L1 SPS A-GNSS in LTE Stage 2 specification TS 36.305CR0120
- Introduction of BDS B2b in A-GNSS TS 36.305CR0121
- Introduction of NavIC L1 SPS A-GNSS in LPP TS 37.355CR0532
- Introduction of B2b signal in BDS system in A-GNSS TS 37.355CR0545
- UE request for equalIntegerAmbiguityLevel assistance data [GNSS-EqualIntegerAmbiguity] TS 37.355CR0557
- Introduction of NavIC L1 SPS A-GNSS in NR Stage 2 specification TS 38.305CR0179
+ 2 more changes
Explore further
Broader topics and technologies where STEC plays a role.
Defining Specifications
3GPP specifications that define or reference STEC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 36.305 vj00 | UE Positioning in E-UTRAN Stage 2 | Rel-19 |
| TS 37.355 vj20 | LTE Positioning Protocol (LPP) | Rel-19 |
| TS 38.305 vj00 | NG-RAN UE Positioning Stage 2 | Rel-19 |