Description
A-GNSS is a hybrid positioning method standardized by 3GPP that combines Global Navigation Satellite Systems (GNSS) such as GPS, GLONASS, Galileo, or BeiDou with cellular network assistance. The core principle involves the network delivering pre-processed satellite data to the User Equipment (UE), enabling the device to compute its position more rapidly and with lower power consumption than standalone GNSS. The architecture typically involves a Location Server (e.g., Secure User Plane Location (SUPL) Enabled Location Server - SLP or Control Plane entities like E-SMLC), which collects assistance data from GNSS reference receivers and disseminates it to UEs via control plane or user plane protocols. The UE uses this data, which can include precise satellite orbits (ephemeris), clock corrections, ionospheric models, and approximate time and location, to accelerate satellite signal acquisition and position calculation.
Operationally, the process begins when a location request is triggered, either by the network (e.g., for emergency services) or the UE (e.g., for a navigation app). The UE establishes a connection with the Location Server, which then provides assistance data tailored to the UE's approximate location and capabilities. This data allows the UE's GNSS receiver to predict which satellites are visible and their expected signal parameters, drastically reducing the search space for satellite signals. Consequently, the Time to First Fix (TTFF) is reduced from tens of seconds (in standalone mode) to a few seconds, and sensitivity is improved, enabling fixes in weaker signal conditions such as indoors or under dense foliage.
Key components include the UE with an A-GNSS-capable receiver, the cellular network's Radio Access Network (RAN) and Core Network (CN), and the Location Server. The Location Server interfaces with GNSS reference networks to obtain real-time satellite data. Protocols like Radio Resource Location Protocol (RRLP) for GSM, Radio Resource Control (RRC) for UMTS/LTE, or LTE Positioning Protocol (LPP) for LTE/NR are used over the control plane, while Secure User Plane Location (SUPL) utilizes IP-based transport over the user plane. A-GNSS supports various modes: UE-assisted, where the UE measures satellite signals and sends raw measurements to the network for position calculation; and UE-based, where the UE calculates its own position using assistance data. This technology is integral to 3GPP's positioning framework, often combined with other methods like Observed Time Difference of Arrival (OTDOA) or Enhanced Cell ID for hybrid positioning solutions.
Purpose & Motivation
A-GNSS was introduced to address the limitations of standalone GNSS receivers in mobile devices, particularly slow Time to First Fix (TTFF), high power consumption, and poor performance in challenging signal environments. Standalone GNSS requires the receiver to download satellite ephemeris and almanac data directly from satellites, which can take 30 seconds or more due to low data rates (50 bps for GPS), and fails in weak signal areas. For emergency services like E911 in the US or E112 in Europe, rapid and reliable location determination is legally mandated, making standalone GNSS insufficient. A-GNSS solves these problems by leveraging the cellular network's bandwidth to deliver assistance data quickly, enabling faster fixes and extending operational range to indoor and urban canyon scenarios.
Historically, A-GNSS emerged in 3GPP Release 7 as part of the broader Location Services (LCS) framework, driven by regulatory requirements for emergency caller location and the growing demand for commercial location-based services (e.g., navigation, geotagging). Prior approaches relied on network-based methods like Cell ID or timing advances, which offered limited accuracy (hundreds of meters to kilometers), or required dedicated GPS hardware with long acquisition times. A-GNSS provided a cost-effective, standardized way to enhance existing GNSS capabilities without major hardware changes, facilitating widespread adoption in smartphones and IoT devices. It also reduces UE battery drain by shortening active GNSS processing time and allowing the receiver to enter low-power states more frequently.
The technology continues to evolve to support new GNSS constellations, improve accuracy with real-time kinematic (RTK) or precise point positioning (PPP) assistance, and integrate with 5G NR positioning. It addresses the need for high-accuracy positioning in applications like autonomous vehicles, drone navigation, and industrial IoT, where sub-meter precision is required. By offloading complex calculations and data acquisition to the network, A-GNSS enables thinner, more power-efficient UE designs while maintaining robust performance across diverse environments.
What changed in its specifications
The latest release-to-release comparison of specifications that define A-GNSS. Each summary describes the whole specification, not only this term.
Rel-19 brings only minor changes to TS 23.271: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.271 →Rel-12 added support for BeiDou Navigation Satellite System (BDS) for UTRA and LTE, including a network-assisted positioning method, a normative reference to BDS ICD, and a definition for BDS.
Full comparison in TS 25.305 →Technology family
Positioning methods · Radio Access Network › Multi-RAT
- R98 E-OTD
- R99 A-GPS, OTDOA-IPDL
- Rel-9 A-GNSS, E-CID, OTDOA
- Rel-16 DL-AoD, DL-TDOA, Multi-RTT, NR E-CID, UL-AoA, UL-TDOA
Also in this family (introduction release not pinned to a single defining specification): U-TDOA
- A-GNSS coexists with E-OTD
“Five positioning mechanisms are supported for LCS: Timing Advance (TA), Enhanced Observed Time Difference (E-OTD), Global Navigation Satellite System (GNSS) based positioning (A-GNSS), Uplink Time Difference Of Arrival (U-TDOA), and Multilateration based positioning.” TS 43.059
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 9 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
TS 36.171 first specifies minimum performance requirements for UE-based and UE-assisted A-GNSS (including A-GPS) terminals in FDD and TDD E-UTRA, with measurement parameters and test cases.
- “The present document establishes the minimum performance requirements for A-GNSS (including A-GPS) for FDD or TDD mode of E-UTRA for the User Equipment (UE).” TS 36.171 v9.3.0
- “The present document defines the minimum performance requirements for both UE based and UE assisted FDD or TDD A-GNSS (including A‑GPS) terminals.” TS 36.171 v9.3.0
A-GNSS was extended to support the BeiDou Navigation Satellite System (BDS) as an additional GNSS alongside GPS, Galileo, SBAS, QZSS and GLONASS.
- “Quasi Zenith Satellite System (QZSS), GLONASS and BDS. The assistance data shall enable combined usage of satellite signals belonging to different GNSS” TS 43.059 v12.1.0
- “CR to TS 36.171 on introduction BDS to A-GNSS of E-UTRA” TS 36.171 v12.1.0
Rel-13 clarifies that A-GNSS minimum performance requirements for UE category M1 and M2 apply only to UEs supporting VoLTE.
- “A-GNSS minimum performance requirements in Section 5 and 6 are applicable only to UEs supporting VoLTE.” TS 36.171 v13.1.0
- “Clarification on applicability of A-GNSS requirements on Cat-M UEs (Rel-13)” TS 36.171 v13.1.0
TS 38.171 first specifies minimum A-GNSS performance requirements for UE-based and UE-assisted terminals with NG-RAN access in 5GS, using LPP between UE and LMF.
- “The present document establishes the minimum requirements for both UE based and UE assisted FDD or TDD A-GNSS terminals” TS 38.171 v15.4.0
- “The minimum A-GNSS performance requirements are specified in clauses 5 and 6 for RRC_CONNECTED state.” TS 38.171 v15.4.0
- “The measurement parameters in case of UE-assisted A-GNSS are the UE GNSS code phase measurements” TS 38.171 v15.4.0
A-GNSS was extended in Rel-16 with BDS B1C signal support, updated B1I ICD version, and revised A-GNSS sensitivity test requirements and frequency bands.
- “Introduction of B1C signal in BDS system in A-GNSS” TS 37.355 v16.14.0
- “Update B1I signal ICD file to v3.0 in BDS system in A-GNSS” TS 37.355 v16.14.0
- “Frequency bands for testing of A-GNSS sensitivity requirements” TS 36.171 v16.6.0
Requirements for A-GNSS support were extended to cover NavIC L5 in TS 38.171, with related CRs correcting A-GNSS support requirements in TS 36.171 and 38.171.
- “Requirements for NavIC L5 A-GNSS support” TS 38.171 v17.4.0
- CR on TS 38.171 requirements for support of A-GNSS TS 38.171CR0018
Rel-19 extends A-GNSS with new satellite signals: NavIC L1 SPS support in LPP and stage 2 specs, and BDS B2b signal support, including the A-GNSS requirements in TS 36.171 and 38.171.
- “Introduction of NavIC L1 SPS A-GNSS in LPP” TS 37.355 v19.3.0
- “Introduction of B2b signal in BDS system in A-GNSS” TS 37.355 v19.3.0
- “CR for TS 38.171 to introduce BDS B2b signal in A-GNSS” TS 38.171 v19.1.0
Defining Specifications
3GPP specifications that define or reference A-GNSS, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.271 vj00 | LCS Stage 2 Specification | Rel-19 read |
| TS 25.305 vj00 | UTRAN UE Positioning Stage 2 | Rel-19 read |
| TS 34.171 v940 | Measurement Procedures for FDD Mode of UTRA UE with A-GPS | Rel-9 read |
| TS 36.171 vj10 | A-GNSS Minimum Performance Requirements for UE | Rel-19 read |
| TS 37.571 vj00 | UE Conformance for Positioning | Rel-19 read |
| TS 37.857 vd10 | Indoor Positioning Enhancements for UTRA and LTE | Rel-13 read |
| TS 38.171 vj10 | 5G A-GNSS UE Positioning Requirements | Rel-19 read |
| TS 43.059 vj00 | GERAN LCS Stage 2 Specification | Rel-19 read |
| TS 45.005 vj00 | GSM RF Requirements for MS and BSS | Rel-19 read |
| TS 51.010 vj00 | SIM Application Toolkit Conformance Testing | Rel-19 read |