Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Security

PPR

Privacy Profile Register

Security →

PPR is a network function that stores and manages a user's privacy settings to control the sharing of their location and personal data, enforcing policies on what information is disclosed and to whom.

Introduced
Rel-6
Where
Services › IMS
Specifications
5 specs
PPR Description Purpose What changed Family Neighbours Detected Changes Specifications

Description

The Privacy Profile Register (PPR) is a logical network entity defined within the 3GPP architecture for managing user privacy, primarily in the context of Location Services (LCS). It functions as a database and policy enforcement point that holds the subscriber's privacy preferences, often referred to as the 'Privacy Profile.' This profile contains rules that dictate the conditions under which the subscriber's location information can be requested, calculated, and disclosed to various entities, known as LCS Clients.

The PPR interacts with several core network elements to enforce these rules. When a Location Service request is initiated by an LCS Client (e.g., a navigation app, an emergency service, or a value-added service), the request is routed through the Gateway Mobile Location Centre (GMLC). The GMLC queries the Home Subscriber Server (HSS) to determine the serving node and to fetch the subscriber's LCS subscription data. Crucially, the HSS may also indicate the address of the PPR associated with the user. The GMLC then contacts the PPR to verify the request against the stored privacy profile. The profile contains rules based on factors such as the identity of the requesting client (client type, identity), the type of location request (e.g., immediate, deferred, periodic), the required accuracy, and the time of day.

Based on the evaluation, the PPR returns a verdict to the GMLC: allowed, barred, or allowed with notifications. If allowed, the location procedure proceeds via the Mobile Switching Centre (MSC) or Mobility Management Entity (MME)/Access and Mobility Management Function (AMF) to the UE. If the profile mandates notification, the network may send an alert to the user's device seeking consent before disclosing location. If barred, the request is rejected. The PPR may be a standalone node or its functionality can be integrated into the HSS or another network repository. Its architecture centralizes privacy control, providing a consistent policy point regardless of the user's location or the type of access network (2G, 3G, 4G, 5G) they are using.

Purpose & Motivation

The PPR was created to address growing privacy concerns and regulatory requirements (e.g., GDPR in Europe, various national laws) surrounding the tracking and disclosure of a mobile subscriber's geographical location. Early location services lacked granular user control; once a user subscribed to an LCS, their location could potentially be provided to any authorized service without further consent. This raised significant privacy issues, as users demanded the ability to control who could locate them and when.

Its development was motivated by the need to standardize a flexible, user-centric privacy management framework within the telecom network. Before the PPR concept, privacy was often handled in an ad-hoc manner by applications or was a simple binary subscription flag in the HLR/HSS. The PR introduces a sophisticated rule-based system that empowers the subscriber. It solves the problem of dynamic privacy management, allowing users to set different rules for different requesters (e.g., always allow emergency services, allow my family only during evenings, bar all commercial requests). This gives users transparency and control, which is essential for the ethical and legal deployment of location-based services, fostering user trust and enabling the growth of the LCS ecosystem.

What changed in its specifications

The latest release-to-release comparison of specifications that define PPR. Each summary describes the whole specification, not only this term.

TS 23.271Rel-18 → Rel-19

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 →
TS 29.173Rel-13 → Rel-14

Rel-14 updated routing rules, protocol references, command-code handling, and AVP treatment in the Diameter base specification.

Full comparison in TS 29.173 →

Technology family

Location services architecture · Services

  1. R98 BSSAP-LE, BSSLAP, GMLC, LMU, RRLP, SMLC
  2. Rel-5 PCAP, SAS
  3. Rel-6 PPR, R-GMLC
  4. Rel-7 LRF, SUPL
  5. Rel-9 E-SMLC, LCS-AP, LPP, LPPa
  6. Rel-15 LMF, NRPPa
  7. Rel-18 LCS-UPP, RSPP, SLPP

Also in this family (introduction release not pinned to a single defining specification): H-GMLC, LMC, MLP, V-GMLC

Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.

Release Timeline

Detected Changes Across Releases

verified against 3GPP sources

Documented changes in 4 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.

Rel-6 introduced

The Privacy Profile Register is defined for the first time as an entity that stores target UE privacy profiles, performs privacy checks and returns results to the H-GMLC over the Lpp interface.

  • “The PPR stores privacy information of the target mobile. The PPR also executes privacy checks and sends the privacy check results to other network elements using the Lpp interface.” TS 23.271 v6.13.0
  • “The PPR is accessible from the H-GMLC via the Lpp interface.” TS 23.271 v6.13.0
  • “PPR performs the privacy check based on the target UE's privacy profile.” TS 23.271 v6.13.0
Rel-7 specification text

The PPR's role in privacy checks was extended: H-GMLC/PPR selects privacy-check indicators for serving nodes supporting LCS capability set 4 or later, and the PPR handles notification and verification based on current location.

  • “When the client type indicates value added service and the serving node supports LCS capability set 4 or later, H-GMLC/PPR shall select indicators” TS 23.271 v7.10.0
  • “send a notification if the result of the privacy check requires the notification and verification based on current location” TS 23.271 v7.10.0
Rel-9 specification text

For EPS location requests, the privacy profile must be stored in H-GMLC/PPR and privacy checking is done there; the HSS also returns the PPR address, now carried over Diameter in the new TS 29.173.

  • “The privacy profile of the UE subscriber (SLPP) shall for EPS be stored in H-GMLC/PPR.” TS 23.271 v9.8.0
  • “This is also applied to EPS location request, i.e. privacy checking is done at H-GMLC/PPR of the target UE.” TS 23.271 v9.8.0
  • “The PPR-Address AVP is of type Address and contains the IPv4 or IPv6 address of the Privacy Profile Register for the targeted user.” TS 29.173 v9.4.0
Rel-10 specification text

NEW adds that the numbers assigned to service types are defined in an annex, which OLD does not state.

Defining Specifications

3GPP specifications that define or reference PPR, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.271 vj00 LCS Stage 2 Specification Rel-19 read
TS 23.871 v500 Enhanced User Privacy for Location Services Rel-5 read
TS 29.173 vj00 Diameter-based SLh Interface for LCS Rel-19 read
TS 32.271 vj20 3GPP LCS Charging Management Spec Rel-19 read
TS 32.272 vj00 Charging for Push-to-Talk over Cellular (PoC) Rel-19 read