About Subscriber Profile Repositories

A Subscriber Profile Repository (SPR) is a system for storing and managing subscriber-specific policy control data as defined under the 3GPP standard.

An SPR can be deployed in environments where the MPE device needs access to a separate repository for subscriber data. The SPR acts as a centralized repository for this data so that multiple MPE devices can access and share the data. This data can include profile data (pre-provisioned information that describes the capabilities of each subscriber), quota data (information that represents the subscriber's use of managed resources), or other subscriber-specific data.

The following SPR systems can be used in the CMP system:

The Oracle Communications Subscriber Database Management (SDM) product includes interfaces for provisioning subscriber information, as well as managing, changing, and accessing this information. These interfaces include an application programming interface for XML provisioning of subscriber profile data, as well as an interactive user interface through the Configuration Management Platform system using a proprietary RESTful API interface.
The SDM system is built upon an existing software base and technology. It not only manages static provisioned subscriber data, but also dynamic intra- and inter-session data from MPE devices—for example, when it is critical to store inter-session quota data centrally so that it can be retrieved upon the next subscriber attachment, wherever that attachment occurs within the network. Intra-session data such as mappings from IP addresses to MSISDNs becomes important as well, especially when managing enforcement points such as DPI devices and optimization gateways where MSISDN/IMSI data is not available. With this the Subscriber Database Management system provides both a storage and notification platform for policy operations, as well as a platform for provisioning.

For detailed information on the Subscriber Database Management system, see the Subscriber Data Management documentation.
The Oracle Communications User Data Repository (UDR) is a highly-scalable, consolidated database back end for subscriber and profile data. User Data Repository utilizes multiple application front ends with the database. UDR supports the Oracle Communications Enhanced Subscriber Profile Repository (ESPR) application, a function used for the storage and management of subscriber policy control and pool data. XML-REST and XML-SOAP interfaces are used by Enhanced Subscriber Profile Repository for creating, retrieving, modifying, and deleting subscriber and pool data.

For detailed information on the UDR, see the User Data Repository documentation.
A customer-specified SPR.
See the Subscriber Profile Repository documentation for more information.

To use an SPR with the CMP system, you must perform the following actions:

You can also modify an SPR connection. See Modifying the SPR Connection for details.