BAIC — Understanding entitlements and custom fields

Subscription Profile Repository (SPR) Release 9.1 Subscriber Provisioning Reference Manual Examples CLI: Modify profile Subscriptions[]:Subscription[SubscriptionID = sub-1]> modify Policy[PublicIdentity=tel:+5149359700] BillingDay = 5; Custom1 = 112 XML: Select profile fields by MSISDN XML-REST: Add profile POST {baseURI}/msr/sub 10404723525 +33123654862 184569547984229 1 DayPass Understanding entitlements and custom fields This section helps clarify the differences between entitlements and custom fields and gives some recommendations about when to use each.

Entitlement Fields — The entitlement field is a multi-valued field where each value represents a boolean flag that represents a capability associated with a subscriber. As an example, let's consider how we would represent whether a subscriber has the ability to use Voicemail. We might create a field for each subscriber, which has a value of either true or false, indicating whether they have that ability. This is a relatively simple representation. However, let's now consider what this means if there are potentially hundreds (or more) of such features that may be associated with a subscriber. It becomes very difficult to manage the subscriber records if there are hundreds of such fields.

Instead of using a field for each feature, if we simply added a value (such as "Voicemail") to the entitlement field for each feature that is enabled for a subscriber then we have captured the same information in a much easier to manage way. 260 910-6701-001 Revision A, June 2013 Attribute Value Range Default Description • If the User Identity follows a NAI based on username format: sip:UserName@example.com, the Subscription ID will be extracted from the NAI format.