| Oracle® Communications UDR Feature Configuration Guide Release 12.4 E93556-01 |
|
 Previous |
 Next |
| Oracle® Communications UDR Feature Configuration Guide Release 12.4 E93556-01 |
|
|
Previous |
Next |
The Ud Client allows the UDR to function as a User Data Convergence Front-End element, which allows UDR to access, retrieve, and update subscriber records in a third-party UDR network other than UDR. The subscriber profile retrieved from the third-party UDR network other than Oracle Communications User Data Repository is stored in a format that is transparent to Policy Management (PM), thus providing transparent support for all existing quota management capabilities.
UDR interfaces with an embedded third-party subscriber database and provides support for all quota management use cases. UDR also preserves all existing quota management capabilities.
Ud client facilitates UDR to access subscriber records in a separate off-board subscriber database. Whenever a subscriber record is not available in the UDR, then UDR uses this interface to retrieve the record from an off-board subscriber database. After retrieving, the record is cached locally in the UDR until it is for the application. UDR also subscribe for notifications from the separate subscriber database to receive notifications in the event that the subscriber record is modified in the other database.
UDR leverages LDAP to retrieve and update subscriber profiles. For more information, refer to the 3GPP TS 29.335, User Data Repository Access Protocol over the Ud Interface, Release 12. This occurs when PM performs the first attempt to access a particular profile for a subscriber via Sh. Upon retrieving the subscriber profile via LDAP search, UDR converts the profile data from the format provided by the off-board database to the internal format that is cached in the UDR. This involves mapping database fields to the subscriber profile, based on configuration data in the SEC. The subscriber data is cached in UDR and made available to any other application that chooses to access the data from UDR that includes PM, and other third-party applications that are integrated to UDR.
You can refresh the profile for a subscriber based on a configured refresh interval. When enabled, the profile for a subscriber is refreshed if the specified refresh interval duration has elapsed since the last refresh time. This refresh is triggered by the first Sh request associated with the subscriber after the refresh interval has elapsed.
Each time the subscriber profile is refreshed, the subscriber profile in the UDR is updated to align with the current information provided by the off-board database. The UDR generates a Push-Notification-Request (PNR) in scenarios where a change has occurred in the subscriber profile and the subscriber has an active subscription for notifications. A PNR is not be generated if the refresh does not result in changes to the subscriber profile.
UDR leverages SOAP to subscribe for notifications for any updates that occur to the specified profile for the subscriber in the off-board database. For more information, refer to the 3GPP TS 29.335, User Data Repository Access Protocol over the Ud Interface, Release 12. Whenever UDR retrieves a profile for the subscriber from the off-board database, it subscribes to notifications for any updates that occur for that subscriber. UDR supports a configurable expiry limit for SOAP subscriptions, which is negotiated with the off-board subscriber database in response to subscription. UDR monitors the expiration of active subscriptions, and initiates a re-subscription before the current subscription expires.
Profiles remain in the UDR database until one of the following events occur. When any of these events occur, the UDR notifies the PM via Sh PNR if there is an active subscription for notifications associated with the subscriber:
