Description
The Location Services User Plane (LCS-UP) is a fundamental architectural component within the 5G system, specifically defined to handle the data transfer required for advanced positioning services. Unlike the control-plane LCS-AP, which manages signaling and session control, the LCS-UP is responsible for the actual conveyance of positioning measurement data, assistance data, and location results over the user plane. This separation allows for higher bandwidth, lower latency data exchange, which is critical for real-time, high-accuracy positioning applications like autonomous driving, augmented reality, and industrial IoT.
Architecturally, the LCS-UP involves several network functions. The key entity is the Location Management Function (LMF) in the 5G Core (5GC), which orchestrates the positioning session. The user plane path typically involves the UE, the gNB (or ng-eNB) in the Radio Access Network (RAN), the User Plane Function (UPF), and the LMF. For UE-assisted or UE-based positioning methods (e.g., Assisted GNSS, OTDOA, sensor-based positioning), the UE generates measurement data (e.g., satellite pseudoranges, observed time differences). This data is packaged into LCS-UP Protocol Data Units (PDUs) and sent via a dedicated Packet Data Unit (PDU) Session or a QoS Flow established for location services. The data travels through the gNB and UPF to the LMF. Conversely, the LMF can send assistance data (like GNSS ephemeris or cell positioning reference signal (PRS) information) to the UE via the same user plane path to aid its position calculation.
The operation of LCS-UP is governed by the LCS User Plane Protocol (LCS-UPP), which defines the format of the PDUs and the procedures for their exchange. A positioning session is first established via control plane signaling (using protocols like LPP over NAS). Once the session is active, the LMF can instruct the UE and/or the RAN to activate a user plane connection for positioning data transfer. This connection uses standard 5G user plane mechanisms (GTP-U tunnels between gNB and UPF, N3/N9 interfaces), ensuring it can benefit from 5G's network slicing and QoS capabilities. The LCS-UP framework supports both unicast (point-to-point between LMF and a single UE) and multicast/broadcast (for delivering common assistance data to multiple UEs) data delivery, making it highly scalable for mass-market services.
Purpose & Motivation
LCS-UP was created to address the limitations of purely control-plane-based positioning in earlier 3GPP releases, which could not efficiently support the massive data volumes and stringent latency requirements of emerging 5G use cases. Control plane signaling, while reliable for session management, is not optimized for streaming large datasets like raw GNSS measurements, dense assistance data, or frequent position updates. The historical approach relied heavily on LPP (LTE Positioning Protocol) carried over NAS, which could become a bottleneck. LCS-UP solves this by offloading the bulk data transfer to the high-performance 5G user plane.
The motivation stems from vertical industry demands for centimeter-level accuracy and real-time kinematic positioning, essential for automotive V2X, drone navigation, and precision agriculture. These applications require the continuous exchange of rich sensor fusion data (from UE and network sensors) which is impractical over the control plane. LCS-UP leverages the inherent strengths of the 5G user plane: high throughput, ultra-low latency, and QoS differentiation. By providing a dedicated, optimized path for positioning data, it enables network-based positioning services to achieve performance on par with or superior to standalone GNSS, especially in challenging environments like urban canyons or indoors. Its introduction in Release 18 represents a strategic evolution of 3GPP's LCS architecture to fully harness the capabilities of 5G-Advanced networks.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (8 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 18, the LCS-UP function was refined with specific corrections and clarifications to the LCS-UP connection binding procedure and its associated binding ID. These enhancements introduced defined failure conditions and abnormal case handling for the binding procedure, and provided corrections for the allocation and association of the LCS-UP binding ID at both the UE and LMF. The changes also specified the minimum and maximum length for the LCS-UP binding ID to ensure robust operation.
- Correction on LCS-UP binding ID handling at UE TS 24.572CR0056
- Minimum and maximum length of the LCS-UP binding ID TS 24.572CR0052
- LCS-UP connection binding failure conditions TS 24.572CR0053
- Correction on LCS-UP binding ID handling at LMF TS 24.572CR0055
- Correction on the association of LCS-UP binding ID and UE ID TS 24.572CR0062
- Correction of LCS-UP connection binding procedure abnormal case TS 24.572CR0045
In Release 19, the LCS-UP function was updated with corrections to the DL LCS-UP TRANSPORT message and clarifications for handling an LCS session initiated prior to the LCS-UP connection establishment. These changes refine the downlink transport procedure and the overall session management to ensure robust operation of the LCS secured user plane connection between the UE and the LMF.
Explore further
Broader topics and technologies where LCS-UP plays a role.
Defining Specifications
3GPP specifications that define or reference LCS-UP, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 24.572 vj50 | 5G LCS User Plane Protocol Specification | Rel-19 |
| TS 38.305 vj00 | NG-RAN UE Positioning Stage 2 | Rel-19 |
