Subscribers

SDS Subscriber Identity Grouping (Subscribers page) groups a customer-specified account ID, multiple MSISDN routing entities, multiple IMSI routing entities, and multiple external identifiers into one Subscriber. After a Subscriber (a group of related routing entities and an optional Account ID value) is created, you can update destinations for all of the related routing entities, read all data from the subscriber, and delete the subscriber by using any of the subscriber’s addresses (for example, account ID, MSISDN, IMSI, or External Identifier). You can also modify addresses within a subscriber by specifying any of the subscriber’s addresses.

Restrictions:

• This is a provisioning-only feature. For information, see Subscriber Database Server Provisioning Interface.

  Note:

  You can only add a subscriber to a subscriber table, if the Account ID, MSISDN, IMSI, or External Identifier is not already in the table. If the table already contains any of these values, the add function fails and an error condition report is generated that contains the reason for the failure.
• The relationships between routing entities is only available on A-level servers, which are the SDS servers and the Query server.

The following restrictions apply to all Subscribers that contain a group of related MSISDN and IMSI routing entities and an optional Account ID. These rules do not apply to standalone routing entities.

• Every subscriber must have at least 1 routing entity (MSISDN, IMSI, or External Identifier).
• All of the subscriber‘s routing entities must have the same destination values.
• Every subscriber can be accessed by specifying any of its routing entity values or its Account ID value.
• When you create a new subscriber, destinations are optional. If you do not specify a destination, destinations are set based upon the existing routing entities.
• All provisioning commands are for a single subscriber. All specified account ID, MSISDN, IMSI, or External Identifier values must be assigned to one subscriber or they can exist in a standalone routing entity.

From the Subscriber page, you can do the following:

• Retrieve information for a specific Subscriber
• Create a Subscriber
• Modify a previously defined Subscriber
• Delete a selected Subscriber