Privacy Class

Description

Privacy Class is a 3GPP-defined concept within the Location Services (LCS) framework that specifies a list of LCS Clients—entities authorized to request location information—to which permission may be granted to locate a target User Equipment (UE). The permission can be granted either on activation by the target UE or permanently for a contractual period of time agreed between the target UE and the service provider. This concept is essential for balancing the need for location-based services with the user's right to privacy, ensuring that location information is only disclosed to authorized clients under defined conditions.

In the 3GPP architecture, Privacy Class is part of the privacy exception list, which is a broader list consisting of various types of privacy classes (e.g., operator-related, personal). Each privacy class defines a set of LCS Clients and the conditions under which they may locate the target UE. The privacy exception list is managed by the LCS Client and the target UE's home network, and it is enforced by the Privacy Check Function (PCF) or equivalent entity in the core network. When an LCS Client requests location information for a target UE, the network performs a privacy check to determine whether the request is allowed based on the target UE's privacy profile and the applicable privacy classes.

The Privacy Class concept was introduced in 3GPP Release 99 (R99) and has been maintained across all subsequent releases up to Rel-19. The definition has evolved slightly over time, primarily in terminology: in R99 through Rel-5, the target was referred to as the "target MS" (Mobile Station), while from Rel-6 onward, the term "target UE" (User Equipment) was adopted to reflect the broader range of devices and access technologies. The core meaning of Privacy Class—a list of LCS Clients within a privacy exception class to which permission may be granted to locate the target—has remained consistent.

Key components of Privacy Class include the LCS Clients, the privacy exception class, and the permission mechanism. LCS Clients are external or internal entities that request location information, such as emergency services, law enforcement, commercial location-based services, or the user's own applications. The privacy exception class is a category of privacy settings that defines which LCS Clients are allowed to locate the UE and under what conditions. The permission mechanism allows the target UE to grant or revoke permission dynamically, or to establish a permanent permission as part of a contractual agreement with the service provider.

Privacy Class is closely related to other privacy and security concepts in 3GPP, such as the Privacy Exception List, the Privacy Check Function, and the LCS privacy requirements defined in TS 22.071, TS 22.935, TS 23.171, and TS 23.271. It is a critical enabler for location-based services, ensuring that user privacy is protected while allowing authorized clients to access location information when necessary. The concept is also relevant to regulatory requirements, such as emergency call location and lawful interception, where location information must be provided to authorized entities.

In summary, Privacy Class is a fundamental building block of the 3GPP location services privacy framework. It provides a structured way to define which LCS Clients can locate a target UE, under what conditions, and with what level of user control. Its consistent presence across releases underscores its importance in balancing location-based service innovation with privacy protection.

Purpose & Motivation

Privacy Class was created to address the privacy concerns associated with location-based services in mobile networks. As LCS became more prevalent, users needed a way to control which entities could access their location information. Without such controls, any LCS Client could potentially locate a user, leading to privacy violations and potential misuse of location data. Privacy Class provides a mechanism for users to grant permission to specific LCS Clients, either on a per-request basis or through a contractual agreement, thereby giving users control over their location privacy.

The concept also supports regulatory and legal requirements, such as emergency services and lawful interception, by allowing authorized entities to obtain location information even when the user has not explicitly granted permission. This is achieved through privacy exception classes that define special conditions under which location information may be disclosed. The Privacy Class concept thus balances the need for location-based services with the user's right to privacy, providing a flexible and enforceable framework.

Over time, the Privacy Class definition has evolved to use more inclusive terminology (target UE instead of target MS) and to align with the broader 3GPP privacy framework. Its continued presence in 3GPP specifications from R99 to Rel-19 demonstrates its enduring relevance and adaptability.