Subscriber LCS Privacy Profile

Description

The Subscriber LCS Privacy Profile (SLPP) is a fundamental component within the 3GPP Location Services (LCS) architecture, designed to enforce user privacy preferences for location-related operations. It is stored within the network, typically in the Home Subscriber Server (HSS) or a dedicated privacy profile register, and is accessed by the Gateway Mobile Location Centre (GMLC) and other LCS entities. The profile contains rules that dictate whether a location request from a specific client (e.g., a value-added service, emergency services, or law enforcement) should be allowed, rejected, or require explicit notification and consent from the subscriber. These rules are evaluated based on parameters such as the identity and type of the requesting client, the type of location request (e.g., immediate, deferred, periodic), and the subscriber's current geographical area.

Operationally, when a Location Service Client (LCS client) initiates a location request for a target Mobile Station (MS), the request is routed to the GMLC. The GMLC retrieves the subscriber's SLPP from the HSS. The profile is then processed to determine the applicable privacy check. This check may result in the request being granted without user notification, granted only after notifying the user and obtaining consent (via SMS, USSD, or a data session), or outright denied. The SLPP supports different classes of clients, such as emergency services, value-added services, law enforcement, and the subscriber themselves, each with potentially different authorization levels. This granular control is crucial for regulatory compliance with privacy laws like GDPR and for building user trust in location-based applications.

The SLPP's architecture integrates with core network signaling, primarily using Diameter-based interfaces (e.g., between GMLC and HSS) or MAP (Mobile Application Part) in earlier releases. It is a key enabler for commercial LCS services like friend-finder, fleet management, and location-based advertising, as it provides the legal and technical framework for user consent. Without SLPP, networks would be unable to offer differentiated privacy handling, potentially leading to unauthorized tracking and significant legal liabilities. Its management can be partially exposed to subscribers via self-care portals, allowing users to update their privacy preferences dynamically.

Purpose & Motivation

The SLPP was created to address the critical privacy concerns inherent in cellular network-based location tracking. As mobile networks evolved to provide precise user location (initially for emergency services like E911 in the US), it became apparent that this capability could be misused without proper safeguards. Prior to standardized privacy profiles, there was no uniform mechanism to let subscribers control who could locate them, creating risks of unauthorized surveillance and violating fundamental privacy rights. The SLPP provides a standardized, network-enforced method to obtain and respect user consent.

Its development was motivated by both regulatory pressures and commercial needs. Regulators demanded that telecom operators protect subscriber location data. Commercially, for location-based services (LBS) to thrive, users needed assurance that their privacy would be respected. The SLPP solves this by putting control in the user's hands through configurable profiles, enabling a trusted ecosystem for LBS. It differentiates between various requestors, ensuring that emergency calls can always be located while commercial services require explicit permission, balancing safety, legality, and service innovation.

Key Features

• Defines authorization rules for location requests per client type (e.g., emergency, value-added, law enforcement)
• Supports multiple notification and verification methods (e.g., SMS, USSD, data session) for user consent
• Allows configuration of privacy settings per geographical area or time of day
• Stored in HSS for centralized access and consistency across the network
• Integrates with GMLC for real-time privacy policy enforcement during location procedures
• Enables subscriber management of privacy preferences via self-service interfaces

Evolution Across Releases

Defining Specifications