Description
The SL Positioning Client UE is a functional role defined in 3GPP TS 23.586 for the Sidelink Positioning and Ranging (SL-PR) service architecture. It represents a UE that hosts an application needing location or ranging information and requests that service over the PC5 sidelink interface. Crucially, the Client UE is a third party: it is neither the SL Reference UE nor the Target UE, meaning the entity requesting the service is logically distinct from the entities that transmit reference signals or are being located. This separation enables use cases where, for example, a device wants to know the relative position of a peer device without itself participating in the measurement exchange.
Architecturally, the SL Positioning Client UE sits at the top of the SL positioning service flow. When an application on the Client UE requires ranging or positioning, the UE initiates a service request that is handled within the sidelink positioning framework. Depending on the deployment, the request may be served entirely by UEs over PC5 (for example, by an SL Positioning Server UE that performs method determination, distributes assistance data, and computes the location), or it may involve 5G core network elements such as the GMLC and LMF through the network-based positioning path described in TS 23.586. The Client UE therefore acts as the service consumer and interacts with the SL Positioning Server UE and other participating UEs to obtain the result.
The Client UE role is defined by its function rather than by a fixed device type. Any UE that supports the client functionality can take this role, and the role is independent of whether the same device also acts as Target or Reference UE in a given session. This flexibility allows a single physical device to assume multiple roles simultaneously or sequentially, which is important for peer-to-peer and proximity-based applications where roles may change dynamically.
In the overall network, the SL Positioning Client UE is the entry point that triggers the sidelink positioning workflow. Its request determines the quality-of-service requirements, the positioning method preferences, and the target of interest. The 3GPP architecture uses this role to cleanly separate service consumption from service provision, which simplifies charging, authorization, and privacy handling: the Client UE can be authorized and billed for the positioning service independently of the Target UE whose location is being determined.
The term was introduced in Release 18 as part of the initial study and normative work on sidelink positioning and ranging, and it was carried forward unchanged into Release 19. Its definition is documented in TS 23.586 (the stage-2 architecture for sidelink positioning), with supporting material in TR 23.700 and the stage-3 service descriptions in TS 28.845.
Purpose & Motivation
The SL Positioning Client UE role exists to decouple the entity that requests a positioning or ranging service from the entities that provide or are subject to it. Before sidelink positioning was standardized, positioning services were primarily network-centric: a UE requested its own location through the core network, and the network (via LMF and RAN measurements) computed it. This model did not naturally support third-party requests where one device asks for the position of another device in proximity, nor did it support device-to-device ranging without network involvement.
By defining a distinct Client UE role, 3GPP enables applications such as asset tracking, social proximity services, and industrial peer-to-peer coordination, where the requesting device is not the device being located. This separation also supports authorization and privacy frameworks: the network can authorize a Client UE to request positioning of a Target UE, and the Target UE's consent and privacy settings can be enforced independently.
The role further enables flexible deployment models, since the Client UE can obtain the service either through a UE-based SL Positioning Server UE over PC5 or through the 5G core network positioning architecture. This dual-path capability was a key motivation for introducing the role in Release 18 alongside the broader sidelink positioning framework.
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (2 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Defining Specifications
3GPP specifications that define or reference SL Positioning Client UE, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 23.586 vj00 | Ranging & Sidelink Positioning in 5GS | Rel-19 read |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |
| TR 28.845 vi00 | Technical Report on Charging for Ranging and Sidelink Positioning | Rel-18 read |