Subscriber Data Schema

You can query for subscriber profile in the Ud client interface provided by UDR. This feature expects that the structure of the subscriber data in the off-board database aligns with the hierarchal structure outlined by 3GPP TS 32.181, User Data Convergence (UDC) Framework for Model Handling and Management, Release 12 and 3GPP TS 132.182, User Data Convergence (UDC) Common baseline Information Model, Release 9. Whenever UDR retrieves a subscriber record from the off-board database, it internally translates it into the internal XML format that it uses to store subscriber data in customer production networks.

UDR applies the internal structure which involves having a base profile and extended with entity data used to categorize data for different applications and functions. This structure emulates a hierarchy as the subscriber data is mapped to an LDAP interface. The base level of the hierarchy is associated with the subscriber profile. A single level request maps to the set of requested entities that are associated with the subscriber profile. Whenever the Ud client retrieves a subscriber profile from the off-board database, it leverages this configuration data to determine how the data schema provided by the off-board database maps to the UDR subscriber profile.

An example of a Subscriber Search request is outlined in the following figure. It illustrates how the GUI configuration facilitates mapping between the various fields from the LDAP response to fields within the subscriber profile.

In this example, the following mappings are configured:

• UDR Tier maps to LDAP Field serviceName
• UDR Entitlement maps to LDAP Field svcs1[0:3] {that is, 3 char from svcs is udr Entitlement}
• UDR IMSI maps to LDAP Field imsi
• UDR MSISDN maps to LDAP uid
• UDR Custom1 maps to LDAP Field service
• UDR Custom2 maps to LDAP Field expiry
• UDR Custom5 maps to LDAP Field epc-profile
• UDR Custom10 maps to LDAP Field activationDate
• UDR Custom13 maps to LDAP Field activationStatus