Assisted GPS (A-GPS) Explained

The user experience of opening a maps app and seeing your location pin appear within seconds is enabled by Assisted GPS (A-GPS) — one of the most consequential GPS-system improvements since SA was turned off in 2000. This article explains what A-GPS is, how it works, when it doesn't, and what to expect from modern smartphones.

The /learn/how-gps-works pillar covers the standalone GPS architecture; this article goes deeper on the network-assisted layer on top.

What A-GPS solves

Standalone GPS satellites broadcast at 50 bits per second. To compute a position, the receiver needs:

• Almanac — rough information about the entire constellation (which satellites exist, approximately where they are). Broadcast in a 12.5-minute repeating frame.
• Ephemeris — precise orbit for each tracked satellite. Each satellite broadcasts its own ephemeris in a 30-second repeating frame.

A cold-start receiver (no recent data) needs to download both: 12.5 minutes for the almanac (or skip if approximate is good enough), then 30 seconds per satellite for ephemeris. In good conditions, a cold start takes 30–60 seconds total.

The problem: 30–60 seconds is too long for a smartphone user who wants to see their location right now. Users wait impatiently, often closing and reopening the app.

A-GPS solves this by bypassing the slow broadcast download. Instead of receiving the ephemeris from the satellites, the phone fetches it from a server over cellular or Wi-Fi — arriving in milliseconds rather than 30 seconds.

How A-GPS works

The basic flow:

1. The phone determines its approximate location from cell- tower position (or Wi-Fi if no cellular).
2. The phone connects to an A-GPS server (over cellular data or Wi-Fi).
3. The phone reports its approximate location to the server.
4. The server replies with the precise ephemeris for all satellites currently visible at that location.
5. The phone's GPS receiver uses the network-supplied ephemeris to skip directly to ranging.
6. Total time: 1–5 seconds for the first fix.

The position-fix accuracy is unchanged from non-assisted GPS — the receiver still tracks the same satellites and computes the same pseudorange equations. A-GPS shortens the acquisition step only.

Standards and protocols

Two main standards define A-GPS:

3GPP cellular-managed A-GPS (in cellular networks):

• RRLP (Radio Resource Location Protocol) — original 2G/3G variant.
• LPP (LTE Positioning Protocol) — current 4G/5G standard (3GPP TS 36.355).

These run over the cellular control plane, with the network managing the location request. They're used primarily for emergency-call positioning (E911 in the US, eCall in EU) and location-based-service queries from the carrier.

OMA SUPL (Secure User Plane Location):

• Open Mobile Alliance standard, used by application-managed positioning (e.g., the phone's OS reports location to an app independent of cellular control).
• Runs over standard IP / TCP / UDP rather than cellular control plane.
• The dominant A-GPS protocol on smartphones today; iPhone and Android both use SUPL for their default location services.

The two protocols cover the same A-GPS functionality but target different deployment models. Modern smartphones use SUPL by default for the user-facing “What's my location?” question; cellular-managed A-GPS is reserved for emergency calling.

Predicted ephemeris

A complementary technique to A-GPS is predicted ephemeris (also called extended ephemeris, or by branded names like Qualcomm's gpsOneXTRA, Apple's assistedGPS prediction).

Standard ephemeris is valid for ~4 hours; beyond that the satellite orbit prediction errors grow and accuracy degrades. Predicted ephemeris extends this to 7+ days by:

1. Downloading a precomputed satellite-orbit model from a server (typically once per day).
2. Using the precomputed model to predict where satellites will be for the next 7 days.
3. Once a day or so, refreshing the model from the network.

A phone with cached predicted ephemeris can do fast cold-start fixes for days without network access. Combined with A-GPS, this gives sub-5-second fixes nearly everywhere.

Apple iOS has included predicted ephemeris since iOS 4.3 (2011). Qualcomm's gpsOneXTRA is widely deployed on Android. The user-facing experience: opening a maps app on a phone that's been off-network for days, getting an instant location fix anyway.

When A-GPS doesn't work

Several scenarios where A-GPS falls back to standalone GPS:

• No cellular signal and no Wi-Fi. A phone in airplane mode with no connectivity can't fetch ephemeris from a server. If predicted-ephemeris cache is valid, fast cold start still works; otherwise, the receiver does a standalone ephemeris download (30+ seconds).
• A-GPS server unreachable. Some smartphones use carrier- specific A-GPS servers that can fail if the carrier's back-end is down. Reasonable fallbacks usually kick in.
• Cold-start in poor signal conditions. Even with A-GPS, the receiver still needs to actually track the satellites to compute a position. In a basement or deep canyon, A-GPS doesn't magically produce a fix.
• Old hardware without A-GPS support. Pre-2008 GPS chipsets and some industrial GPS devices don't implement A-GPS; they always do cold-start standalone acquisition.

For travellers in remote regions, A-GPS can be a liability if the phone aggressively tries to fetch network ephemeris and fails: some implementations time out (waste a few seconds) before falling back to standalone GPS. Modern implementations handle this gracefully but it's worth knowing.

Power and battery implications

Standalone GPS uses 50–100 mW continuously when active. A-GPS adds:

• ~1–10 mW of cellular data transmit/receive (briefly, to fetch ephemeris).
• Negligible processing overhead on the application processor.

The net effect of A-GPS on battery is small (and usually reduces total power because the GPS receiver is active for less time). Modern smartphones aggressively use A-GPS specifically to minimise GPS-active duration.

Practical observations

For typical smartphone users:

• Indoor cold start: With A-GPS, the phone can often get a coarse position from cell-tower triangulation instantly (network-provided as the “rough location” to seed A-GPS), then refine to GPS accuracy when signal is acquired.
• Travel cold start: When you arrive in a new city and open Maps, A-GPS uses cellular position to seed; ephemeris download happens automatically; GPS converges in 5 seconds.
• Airplane mode → off: Modern smartphones cache ephemeris, so the first GPS fix after turning airplane mode off is usually under 5 seconds, not 30+.
• In a parking garage / basement: Cell-tower seed gives a rough position; GPS satellite tracking may not work; the phone falls back to cellular or Wi-Fi position.

The Coordinately /tools/my-location uses the browser's navigator.geolocation API, which internally uses A-GPS, Wi-Fi triangulation, and IP geolocation depending on availability. The reported accuracy reflects whichever method produced the answer.

A-GPS in the smartphone era

The history of A-GPS adoption tracks the consumer-GPS era:

• 2002: 3GPP publishes initial RRLP A-GPS specifications driven by the FCC E911 mandate (US carriers required to locate emergency callers).
• 2005: First widely-deployed A-GPS handsets (BlackBerry 8800, Motorola V3, early Nokia models). Standalone-GPS cold-start delays were a known user complaint; A-GPS shipped as a workaround.
• 2007: Apple iPhone launches with A-GPS as a standard feature. The instant-fix user experience becomes the baseline.
• 2010s: Predicted ephemeris (Qualcomm gpsOneXTRA, Apple assistedGPS prediction) widespread; cold-start time effectively zero when cache is valid.
• 2020s: Dual-frequency L1+L5 + A-GPS + predicted ephemeris combine to give sub-second fixes with sub-metre accuracy on premium hardware.

The user-perceived “GPS just works instantly” on modern smartphones is the cumulative effect of these layered optimisations — not improvements in the GPS satellites themselves.

A-GPS in IoT and tracking devices

Smaller GPS devices (asset trackers, fitness wearables, pet trackers) have a particular A-GPS challenge: limited battery and intermittent connectivity. Common strategies:

• Burst-mode A-GPS: device wakes briefly, fetches A-GPS data, computes a position, transmits the position over cellular or LoRaWAN, then sleeps. Total active time: a few seconds.
• Predicted ephemeris with weekly refresh: device caches a 7-day ephemeris from a server when first powered on; uses it for fast cold starts without ongoing network access.
• Pseudo-A-GPS: device uploads raw GPS satellite measurements to a server; the server computes the position with help from the network's ephemeris. Used in some ultra-low-power tracker designs.

The Coordinately /tools/my-location is a browser-side tool that uses the device's built-in A-GPS via the geolocation API; the API doesn't expose the underlying acquisition mechanism but the speed of the first fix usually reflects whether A-GPS is in play.

Common misconceptions

“A-GPS uses cellular triangulation as the location source.” No — cellular triangulation provides a rough seed position for selecting which satellites to focus on, but the final position comes from real GPS satellite tracking. A-GPS does not replace satellite tracking; it accelerates it.

“A-GPS works without GPS satellite reception.” No. If the receiver can't see the GPS satellites (indoors, in a deep canyon), A-GPS cannot produce a GPS-grade fix. The phone may report a Wi-Fi or cellular position as a fallback, but that's not A-GPS; it's a separate positioning method.

“A-GPS is a privacy concern because the network sees my location.” It can be — the cellular network already knows your approximate location from cell-tower data, independent of A-GPS. SUPL-based A-GPS uses the application layer over a (typically) carrier-agnostic server, so the location request goes through the app provider rather than the carrier directly. Whether that's an improvement depends on the trust model.

“A-GPS only works on 4G / 5G.” No — A-GPS works on 2G, 3G, 4G, 5G, and Wi-Fi. Any IP network connection can serve SUPL data; the early A-GPS implementations ran over 2G GPRS. The cellular generation affects download speed (a few KB of ephemeris takes longer over 2G than 5G), but A-GPS is supported across all of them.

“A-GPS reduces accuracy because it uses network data.” A-GPS doesn't affect accuracy. The network delivers the same satellite ephemeris that the receiver would otherwise download from the satellites themselves. The position fix uses identical math regardless of where the ephemeris came from.

“Disabling A-GPS makes GPS more private.” Disabling A-GPS makes the first fix slower; it doesn't change what data leaves the phone. Location-tracking concerns are addressed by application-layer permissions and OS-level Location Services settings, not by toggling A-GPS.

“A-GPS is a Google / Apple proprietary technology.” A-GPS is standardised by 3GPP (cellular) and OMA (SUPL). Apple and Google use the same standards as every other implementer; the operational A-GPS servers may be operated by specific vendors (Apple operates Apple SUPL; Qualcomm operates gpsOneXTRA; Broadcom and MediaTek have their own), but the protocols are open standards.