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

Glossary term · Core Network

SPR

Subscription Profile Repository

SPR has more than one meaning in 3GPP. Also: Successful PSCell Addition/Change Report.

Core Network →

SPR is a database in the 3GPP Policy and Charging Control architecture that stores permanent subscription data for user services and policies and provides subscriber profile information to the PCRF for dynamic policy and charging rule generation.

Introduced
Rel-7
Where
Core Network › Evolved Packet Core
Specifications
3 specs
SPR Description Purpose What changed Neighbours Specifications

Description

The Subscription Profile Repository (SPR) is a functional entity within the 3GPP Policy and Charging Control (PCC) framework, defined initially for the Evolved Packet Core (EPC) in LTE. It acts as a centralized repository for subscriber-specific data that is relatively static and provisioned by the operator. This data includes information such as the subscriber's allowed services, QoS parameters (e.g., subscribed guaranteed and maximum bit rates), charging characteristics, spending limits, and potentially service-specific policies (like time-of-day restrictions or roaming policies). The SPR does not handle session-specific or dynamic data; its content is tied to the subscription itself.

The SPR interfaces primarily with the Policy and Charging Rules Function (PCRF) via the Sp reference point (specified in TS 29.214). When the PCRF needs to make a policy decision for a subscriber's IP Connectivity Access Network (IP-CAN) session (e.g., a PDN connection), it can query the SPR to retrieve the relevant subscription profile. The PCRF uses this static profile in conjunction with dynamic inputs from the Application Function (AF) and the Access Network itself to derive and install the appropriate Policy and Charging Control (PCC) rules in the Policy and Charging Enforcement Function (PCEF).

Architecturally, the SPR can be a standalone node or its functionality can be integrated with other operator databases, such as the User Data Repository (UDR) in later 3GPP architectures. Its role is critical for enabling personalized, subscription-aware network policies. For example, it allows an operator to offer tiered service plans where a "gold" subscriber receives higher priority QoS than a "bronze" subscriber, based on the information stored in the SPR. The separation of the SPR from the PCRF allows for a modular architecture where subscription data management can be scaled and managed independently from the real-time policy decision logic.

Purpose & Motivation

The SPR was created to address the need for a dedicated, authoritative source of subscription-based policy information within the new, IP-based PCC architecture of LTE. Previous mobile architectures often embedded policy data within the HSS (Home Subscriber Server) or other network elements, which were not designed for the dynamic, service-aware policy decisions required for advanced IP services. The purpose of the SPR is to decouple static subscription information from the dynamic policy decision logic performed by the PCRF.

This separation solves several problems: It allows for more flexible and scalable policy management, as subscription data can be updated independently of the policy engines. It enables the PCRF to make informed, subscriber-specific decisions by providing a standardized interface to retrieve a comprehensive profile. This was essential for the commercialization of LTE, supporting sophisticated service differentiation, tiered pricing models, and fair usage policies based on a user's contract. The SPR's creation was motivated by the shift towards all-IP networks and the requirement for real-time, context-aware policy control that could leverage a user's subscribed services and limits.

What changed in its specifications

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

TS 23.203Rel-16 → Rel-17

NB-IoT/eMTC support for Non-Terrestrial Networks: adds QCI characteristic for satellite access, note on GEO/LEO delays, and PCRF policy control for satellite PDN connections.

Full comparison in TS 23.203 →
TS 29.154Rel-13 → Rel-14

Added Diameter Load Information Conveyance protocol and Load AVP. Updated Diameter Base Protocol notes referencing RFC 6733, keeping Vendor-Specific-Application-Id AVP required.

Full comparison in TS 29.154 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-7 Initial

Introduced as part of the initial Policy and Charging Control (PCC) architecture in 3GPP Release 7. It was defined as a standalone repository for subscription profiles, providing the PCRF with the necessary static data to make dynamic policy decisions for IP-based services, forming a cornerstone for service-aware policy management in the EPC.

Defining Specifications

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

SpecificationTitleRelease
TS 23.203 vk10 Policy and Charging Control Architecture Rel-20 read
TS 29.154 vj00 Nt Reference Point Protocol Rel-19 read
TS 29.201 vj00 RESTful Rx Interface for AF-PC Communication Rel-19 read