Description
The Location Services User Plane Protocol (LCS-UPP) is the specific protocol that realizes the LCS User Plane (LCS-UP) framework. It is an application-layer protocol that rides on top of the standard 5G user plane transport stack (IP, UDP, GTP-U). LCS-UPP defines the structure of Protocol Data Units (PDUs) that carry all positioning-related information exchanged directly over the data channel, enabling efficient, high-volume transfers that would be prohibitive over control plane signaling.
Technically, LCS-UPP PDUs encapsulate payloads from higher-layer positioning protocols. The most significant of these is the LTE Positioning Protocol (LPP), which is repurposed for 5G. In the LCS-UP context, LPP messages (which contain measurement requests, measurement reports, assistance data delivery, and location information) are not sent over NAS but are instead packaged as the payload within an LCS-UPP PDU. The LCS-UPP layer adds its own header, which includes control information such as a PDU Type (e.g., Data, Acknowledge), a Sequence Number for reliable delivery if needed, and identifiers to associate the PDU with a specific positioning session or transaction. This encapsulated LPP-in-LCS-UPP PDU is then sent over the established PDU Session's user plane bearer.
The protocol operates between two primary endpoints: the LCS-UPP layer in the UE and the LCS-UPP layer in the Location Management Function (LMF). The gNB and UPF are transparent to the LCS-UPP content; they merely forward the IP packets containing the GTP-U-encapsulated LCS-UPP PDUs. LCS-UPP supports both connection-oriented and connectionless modes. For a sustained positioning session with frequent data exchange (e.g., continuous tracking), a connection-oriented context can be established, managing sequence numbers and acknowledgments. For one-off assistance data delivery, a simple connectionless datagram can be used. The protocol is designed to be lightweight, minimizing overhead to preserve the low-latency advantage of the user plane. It works in concert with control plane protocols (like LPP over NAS) which are still used for session establishment, capability negotiation, and activation/deactivation of the user plane positioning data transfer.
Purpose & Motivation
LCS-UPP was developed to provide a standardized, efficient encapsulation and delivery mechanism for positioning protocol data over the 5G user plane. Before its introduction, positioning protocols like LPP were solely carried over the control plane (NAS), which was not designed for the data intensity of advanced positioning. The need for a user plane protocol became apparent with 5G-Advanced use cases requiring the transfer of large assistance data files (e.g., real-time kinematic (RTK) corrections, precise point positioning (PPP) data) and high-frequency streams of raw sensor measurements from the UE.
The protocol solves the problem of how to reliably and efficiently transport structured positioning messages within the unstructured flow of user plane IP packets. It provides the necessary session management, message framing, and optional reliability mechanisms at the application layer without relying on TCP, which may introduce unacceptable latency and jitter. By defining LCS-UPP, 3GPP created a purpose-built conduit that allows the rich feature set of LPP (and future positioning protocols) to be leveraged in a high-performance data plane context. This enables network operators and service providers to offer differentiated, high-accuracy positioning-as-a-service with guaranteed QoS, a key enabler for monetizing 5G network capabilities in vertical markets.
What changed in its specifications
The latest release-to-release comparison of specifications that define LCS-UPP. Each summary describes the whole specification, not only this term.
Rel-19 adds satellite NG-RAN access text, LP-WUS/WUR assistance and disabling, ATUC RAT utilization control, and network-controlled slice selection with S-NSSAI time validity to TS 24.501. It also adds ATSSS Phase 4 multi-access and 5G ProSe multi-hop relay support.
Full comparison in TS 24.501 →Rel-19 adds enhanced NR topology support to TS 38.305, including WAB-gNB, updated definitions and gNB-to-LMF information transfer. It also includes two further related items.
Full comparison in TS 38.305 →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
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 2 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 24.572 is first specified in this release, defining the LCS user plane protocol (LCS-UPP) for UE–LMF user plane positioning, with related NAS capability bits and connection handling in other specs.
- “The present document specifies the LCS user plane protocol (LCS-UPP) to support the Location Services in the 5G System (5GS)” TS 24.572 v18.5.0
- “defines the message format, message contents, error handling and system parameters applied by the LCS-UPP and the UPP-CM protocol” TS 24.572 v18.5.0
- “In this release, only one LCS-UPP connection is allowed for an UE.” TS 29.518 v18.15.0
Rel-19 allows a UE with multiple-LCS-UPP-connections capability to hold several LCS-UPP connections, each to a different LMF, replacing the earlier single-connection limit, with matching AMF handling and capability signalling.
- “if the AMF determines that the UE is not supporting multiple LCS-UPP connections capability and LCS-UPP connection already exists between the UE and one LMF” TS 29.518 v19.8.0
- “NOTE 2: In this release, only one LCS-UPP connection is allowed for an UE.” TS 29.518 v19.8.0
- “the UE supports multiple LCS‑UPP connections, each towards a different LMF” TS 29.518 v19.8.0
Defining Specifications
3GPP specifications that define or reference LCS-UPP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 24.501 vk10 | 5GS NAS Protocol Specification | Rel-20 read |
| TS 24.572 vk00 | 5G LCS User Plane Protocol | Rel-20 read |
| TS 38.305 vj30 | NG-RAN UE Positioning Stage 2 | Rel-19 read |