Description
Secure User Plane for Location (SUPL) is a protocol suite standardized by 3GPP and Open Mobile Alliance (OMA) that provides location services (LCS) by leveraging the user plane (IP-based data channels) rather than the control plane signaling channels. Introduced in 3GPP Release 7, SUPL enables efficient and scalable determination of a mobile device's position by transporting positioning-related messages between the SUPL Enabled Terminal (SET), which is the mobile device, and the SUPL Location Platform (SLP), which is the network-based location server. The SLP consists of two main components: the SUPL Location Center (SLC), which handles session management and privacy, and the SUPL Positioning Center (SPC), which performs position calculation.
SUPL operates by establishing a secure IP connection (using TLS/DTLS) between the SET and SLP. The protocol supports multiple positioning methods, including Assisted Global Navigation Satellite System (A-GNSS), Observed Time Difference of Arrival (OTDOA), Enhanced Cell ID (E-CID), and others. In a typical SUPL session, the SLP initiates or the SET initiates a location request. They exchange messages (using OMA-defined protocols like ULPS or LPP) to transfer assistance data (e.g., satellite ephemeris for A-GNSS) from SLP to SET and measurement data (e.g., pseudoranges or timing measurements) from SET to SLP. The SPC then computes the position, which can be returned to the SET or to an external LCS client (e.g., a navigation app or emergency service).
Key architectural elements include the SET's SUPL agent (the application requesting location), the SLP's interfaces with core network elements (like GMLC in control plane LCS), and support for roaming scenarios where the home SLP and visited SLP may collaborate. SUPL is designed to reduce signaling load on the control plane, offer faster positioning, and support continuous tracking services. It is widely deployed for commercial location-based services (e.g., maps, friend finders) and mandated for emergency services like E911 in some regions. Specifications span 3GPP (e.g., 23.271 for architecture) and OMA (e.g., OMA-AD-SUPL for protocol details), ensuring interoperability across devices and networks.
Purpose & Motivation
SUPL was developed to address limitations of control plane location solutions in 2G/3G networks, which relied on signaling system no. 7 (SS7) and circuit-switched connections. Control plane LCS was complex, slow, and not scalable for mass-market location-based services due to heavy signaling overhead and dependency on network vendor implementations. As demand for location services grew with the rise of smartphones and apps, a more efficient, IP-based approach was needed.
The primary motivation for SUPL was to leverage the user plane (packet-switched data) for location positioning, enabling faster session setup, reduced network congestion, and easier integration with Internet-based applications. By using standard IP security (TLS), SUPL also provided inherent security and privacy protections, which were less robust in control plane methods. This allowed operators to offer commercial LCS (like navigation and advertising) without impacting core network stability.
Furthermore, SUPL supported a wider range of positioning technologies (e.g., A-GNSS, Wi-Fi positioning) and allowed continuous location tracking for services like fleet management or child monitoring. Its introduction in Release 7 coincided with the growth of 3G data services, providing a future-proof framework that evolved through LTE and 5G. SUPL also facilitated regulatory compliance for emergency services (e.g., E112 in Europe) by offering a standardized, reliable method for location determination, complementing control plane solutions. Thus, SUPL solved the problems of scalability, speed, and flexibility, enabling the location-aware ecosystem we see today.
What changed in its specifications
The latest release-to-release comparison of specifications that define SUPL. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-18 adds signal level Enhanced Network Selection, covering emergency-session and eCall-over-IMS behaviour for UEs in limited service state, tied to the ims-EmergencySupport broadcast bit. The overview lists only this one feature, so no further items can be named from the provided material.
Full comparison in TS 23.167 →Technology family
Location services architecture · Services
- R98 BSSAP-LE, BSSLAP, GMLC, LMU, RRLP, SMLC
- Rel-5 PCAP, SAS
- Rel-6 PPR, R-GMLC
- Rel-7 LRF, SUPL
- Rel-9 E-SMLC, LCS-AP, LPP, LPPa
- Rel-15 LMF, NRPPa
- Rel-18 LCS-UPP, RSPP, SLPP
Also in this family (introduction release not pinned to a single defining specification): H-GMLC, LMC, MLP, V-GMLC
- SUPL used together with LPP
“LPP further supports the OMA user plane location solution SUPL 2.0, as defined in the OMA SUPL 2.0 standards ([17], [18]), and is intended to be compatible with the successor protocols of SUPL 2.0 as well.” TS 36.305
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 5 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.
Rel-7 specifies use of OMA SUPL procedures for positioning WLAN UEs via the GMLC/SLP, and allows SUPL for IMS emergency location retrieval by the LRF.
- “shall use the OMA SUPL mechanism specified by OMA (OMA AD SUPL [38], OMA TS ULP [39]) to transport location related assistance data” TS 23.271 v7.10.0
- “This shall use SUPL procedures based on OMA SUPL (OMA AD SUPL [38], OMA TS ULP [39]).” TS 23.271 v7.10.0
- “may be used if supported by the terminal and if it is possible to establish a user plane connection between the UE and the SUPL server” TS 23.167 v7.13.0
TS 36305 first specifies how E-UTRAN positioning (LPP) supports OMA SUPL 2.0, including SET/SLP roles and an informative annex on using LPP with SUPL.
- “LPP further supports the OMA user plane location solution SUPL 2.0, as defined in the OMA SUPL 2.0 standards” TS 36.305 v9.10.0
- “For SUPL 2.0 support, the SUPL Enabled Terminal (SET) is the target device and the SUPL Location Platform (SLP) is the server.” TS 36.305 v9.10.0
- “For SUPL, SUPL Initiation Function using UDP/IP (OMA AD SUPL [15]) shall be supported by the SET.” TS 23.167 v9.14.0
Rel-14 extends SUPL use in IMS emergency location: SUPL may locate a UE with WLAN access, and the LRF assigns a target-side E-SLP after handover.
- Enable use of SUPL to locate a UE with WLAN Access TS 23.167CR0312
- “If SUPL is used on the target side, the LRF assigns a target side E-SLP” TS 23.271 v14.4.0
The new NG-RAN positioning specification TS 38.305 defines SUPL 2.0 support, including LPP use with SUPL, SET/SLP roles, LMF-SLP interaction and SUPL positioning method support.
- “The design goal of LPP is to enable it to be used in user plane location solutions such as OMA SUPL” TS 38.305 v15.10.0
- “An LMF may have a proprietary signalling connection to an SLP. The SLP is the SUPL entity responsible for positioning over the user plane.” TS 38.305 v15.10.0
- “For SUPL 2.0 support, the SUPL Enabled Terminal (SET) is the target device and the SUPL Location Platform (SLP) is the server.” TS 38.305 v15.10.0
SUPL user-plane positioning support was corrected, so E-CID/NR E-CID methods can now be supported in SUPL via LPP tunnelling, and the SUPL support notes in the positioning method tables were updated.
- “E-CID/NR E-CID positioning methods defined within LPP proper can be supported in SUPL, via tunnelling LPP as shown in this annex” TS 38.305 v16.10.0
- Correction to SUPL support for NR positioning methods TS 38.305CR0028
- Correction on user-plane positioning support by SUPL TS 38.305CR0078
Defining Specifications
3GPP specifications that define or reference SUPL, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 22.814 va00 | LCS Support for Non-3GPP Access | Rel-10 read |
| TS 23.167 vk10 | IMS Emergency Services | Rel-20 read |
| TS 23.271 vj00 | LCS Stage 2 Specification | Rel-19 read |
| TS 23.273 vj70 | 5G Location Services Architecture Stage 2 | Rel-19 read |
| TS 23.303 vj00 | Proximity Services (ProSe) Stage 2 | Rel-19 read |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |
| TR 23.730 ve00 | Study on extended CIoT architecture | Rel-14 read |
| TS 23.868 v900 | Study on IMS Emergency Calls | Rel-9 read |
| TS 24.526 vk00 | 5GS UE Policies | Rel-20 read |
| TS 24.572 vk00 | 5G LCS User Plane Protocol | Rel-20 read |
| TS 29.171 vj10 | LCS-AP between MME and E-SMLC (SLs) | Rel-19 read |
| TS 29.212 vk00 | Diameter-Based PCC Reference Points | Rel-20 read |
| TS 29.512 vk10 | Session Management Policy Control Service Stage 3 | Rel-20 read |
| TS 36.305 vj00 | UE Positioning in E-UTRAN Stage 2 | Rel-19 read |
| TS 36.355 vj00 | LTE Positioning Protocol (LPP) | Rel-19 read |
| TS 36.809 vc00 | Study on RF Pattern Matching for LTE Positioning | Rel-12 read |
| TS 37.355 vj30 | LTE Positioning Protocol (LPP) | Rel-19 read |
| TS 37.857 vd10 | Indoor Positioning Enhancements for UTRA and LTE | Rel-13 read |
| TS 38.305 vj30 | NG-RAN UE Positioning Stage 2 | Rel-19 read |