Description
The LCS Client Subscription Profile is a fundamental concept in 3GPP Location Services (LCS), representing the contractual agreement between an LCS client and the service provider regarding the use of location information. It is a collection of subscription attributes that specify the LCS-related parameters, such as the allowed quality of service (QoS), privacy constraints, and authorization rules. This profile is essential for managing access to location data and ensuring that location services are provided in accordance with regulatory and commercial requirements.
In the 3GPP architecture, the LCS Client Subscription Profile is stored in the LCS client's home environment, typically in a database such as the Gateway Mobile Location Center (GMLC) or a dedicated subscription repository. When an LCS client requests location information for a target UE, the network retrieves the subscription profile to verify that the request is authorized and to determine the parameters for the location service. The profile includes attributes such as the LCS client ID, the list of target UEs or groups that the client is allowed to locate, the permitted QoS (e.g., accuracy, response time), and privacy settings (e.g., whether user consent is required).
The profile is defined in several 3GPP specifications, including TS 22.071 (Location Services requirements), TS 22.935 (Location Services feasibility study), TS 23.171 (Functional stage 2 description of LCS in UMTS), and TS 23.271 (Functional stage 2 description of LCS in EPC and 5G). These specifications outline the structure and management of the subscription profile, ensuring interoperability across different network generations. The profile can be static or dynamic, with the possibility of updates based on changes in the contractual agreement or user preferences.
One of the key roles of the LCS Client Subscription Profile is to enforce privacy and security. It ensures that location information is only provided to authorized clients and that the target user's privacy preferences are respected. For example, the profile may specify that the client can only obtain location information during certain hours or that the user must be notified. This is crucial for compliance with privacy regulations such as GDPR in Europe.
With the evolution of networks from 2G to 5G, the LCS Client Subscription Profile has adapted to new requirements, such as support for IoT devices, network slicing, and enhanced privacy mechanisms. In 5G, location services are integrated with the Service Based Architecture (SBA), and the subscription profile may be managed by the Unified Data Management (UDM) or other network functions. The profile continues to be a cornerstone for delivering location-based services in a secure and controlled manner.
Purpose & Motivation
The LCS Client Subscription Profile exists to formalize the agreement between LCS clients and service providers, ensuring that location services are delivered according to predefined terms. It solves the problem of unauthorized access to location data and provides a framework for privacy and QoS management. Without such a profile, location services could be misused, leading to privacy breaches and regulatory non-compliance.
Historically, as location-based services emerged in the late 1990s and early 2000s, there was a need to standardize how location information is accessed and controlled. 3GPP introduced the LCS Client Subscription Profile in Release 99 (R99) as part of the initial LCS specifications. This allowed operators to offer location services with clear contractual terms, facilitating commercial deployment and regulatory acceptance.
Over time, the profile has evolved to address new challenges such as emergency services, lawful interception, and IoT location tracking. It remains a critical element in the 3GPP location services framework, balancing the need for location information with privacy and security.
What changed in its specifications
The latest release-to-release comparison of specifications that define LCS Client Subscription Profile. Each summary describes the whole specification, not only this term.
Rel-19 brings only minor changes to TS 22.071: 1 clause changed, with no change attributed to a release feature.
Full comparison in TS 22.071 →Rel-19 brings only minor changes to TS 23.271: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 23.271 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference LCS Client Subscription Profile, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 22.071 vj00 | Location Services (LCS) Stage 1 | Rel-19 read |
| TR 22.935 vd00 | LCS Feasibility Study for 3GPP-WLAN Interworking | Rel-13 read |
| TS 23.171 v390 | LCS Stage 2 for UMTS | R99 read |
| TS 23.271 vj00 | LCS Stage 2 Specification | Rel-19 read |