Request

Semantic Rules (all requests)

• At least one routing entity (IMSI or MSISDN) must be specified.
• No more than 10 routing entities (IMSI, MSISDN, or combinations of the two) can be specified.
• A destination name must already exist in the database.
• Each destination name type can only be specified once.
• All specified routing entities will be provisioned with the same destination value(s).
• Any existing destination(s) for a routing entity will not be changed/removed if not specified in the request.
• Specifying a destination name of “none” removes the association of that destination from the specified routing entity(s).

Semantic Rules (requests that do not specify the group attribute or specify group="n")

• The accountId, deleteAccountId, deleteImsi, and deleteMsisdn parameters cannot be specified.
• All specified IMSI and MSISDN values must be for stand-alone routing entities or they all must be assigned to one subscriber. There cannot be a mixture of stand-alone routing entities and routing entities that are part of a subscriber.
• At least one routing entity (IMSI or MSISDN) must be specified.
• A maximum of 10 routing entities (IMSI, MSISDN, or combinations of the two) can be specified.
• At least one destination must be specified.
• All specified routing entities will be provisioned with the same destination value(s).

Semantic (requests that specify attribute group="y")

• The accountId, deleteAccountId, deleteImsi, and deleteMsisdn parameters can be specified.
• All specified Account ID, IMSI, or MSISDN values must be assigned to one subscriber or must exist in stand-alone routing entities. After the command successfully completes, all specified values will be assigned to one subscriber.
• All specified deleteAccountId, deleteImsi, or deleteMsisdn values that exist in the database must be assigned to the same subscriber. All Account ID, IMSI or MSISDN values must be assigned to the same subscriber or not assigned to any subscriber.
• At least one IMSI, MSISDN, or Account ID value must be specified.
• The deleteAccountId, deleteImsi, deleteMsisdn values and all destination tags and values are optional. This allows a user to just add an Account ID or MSISDN and/or IMSI values to a subscriber.
• A maximum of one accountId, one deleteAccountId, siximsi, six deleteImsi, six msisdn, and/or six deleteMsisdn values can be specified. If any of these limits are exceeded, the request fails.
• All specified accountId, imsi, and msisdn values that are not currently associated with a subscriber will be assigned to the same subscriber. They are added to an existing subscriber or new subscriber.
• If a new subscriber is being created with all new routing entities, all specified routing entities will be provisioned with the specified destination values.
• If a new subscriber is being created with at least one existing stand-alone routing entity, all destination values from existing stand-alone routing entities must be the same prior to applying any specified destination changes. All new routing entities will inherit their destinations values from an existing stand-alone routing entity with the applied destination changes.
• If existing stand-alone routing entities are being added to an existing subscriber, the destination values in each stand-alone routing entity must match the destination values for the subscriber (extracted from any of the subscriber's routing entities) prior to applying any specified destination changes.
• If new routing entities are being added to an existing subscriber, the new routing entities will inherit the destination values for the subscriber (extracted from any of the subscriber's routing entities).
• If a new routing entity is being created, at least 1 of its destination values must not be equal to none.
• The updated subscriber must have at least 1 IMSI or MSISDN routing entity.
• The updated subscriber can have 0 or 1 Account ID values, 0-6 IMSI values and 0-6 MSISDN values, as long as there is at least one IMSI or MSISDN value. If the result of the update (deleting and then adding new Account ID, IMSI, and/or MSISDN values) would cause too many Account ID, IMSI or MSISDN values, the request will fail.
• The subscriber's Account ID value can be updated only if it is currently null or deleted within the request (as specified by the deleteAccountId parameter).
• If any of the values specified in the deleteAccountId, deleteImsi, or deleteMsisdn parameters do not exist in the database, they will be ignored. If nothing else changes for the subscriber, the NO_UPDATES is returned.
• If any of the values specified in the deleteAccountId, deleteImsi, or deleteMsisdn parameters exist in the database, they must be assigned to the subscriber being updated or the command will fail.
• If any of the values specified in the deleteImsi or deleteMsisdn parameters exist, the routing entity will be deleted unless it is the last IMSI or MSISDN routing entity for the subscriber, in which case the command will fail.

Request Format

<updateSubscriber ent="subscriberRouting" ns="dsr" [resonly="resonly"]
                  [id="id"] [timeout="timeout"] [group="group"]>
[   <deleteAccountId>deleteAccountId</deleteAccountId> ]
[
    <deleteImsi>deleteImsi</deleteImsi>
    …
    <deleteImsi>deleteImsi</deleteImsi>
]
[
    <deleteMsisdn>deleteMsisdn</deleteMsisdn>
    …
    <deleteMsisdn>deleteMsisdn</deleteMsisdn>
]
[   <accountId>accountId</accountId> ]
[
    <imsi>imsi</imsi>
    …
    <imsi>imsi</imsi>
]
[
    <msisdn>msisdn</msisdn>
    …
    <msisdn>msisdn</msisdn>
]
[   <imshss>imshss</imshss>       ]
[   <ltehss>ltehss</ltehss>       ]
[   <pcrf>pcrf</pcrf>             ]
[   <ocs>ocs</ocs>                ]
[   <ofcs>ofcs</ofcs>             ]
[   <aaa>aaa</aaa>                ]
[   <userdef1>userdef1</userdef1> ]
[   <userdef2>userdef2</userdef2> ]
</updateSubscriber>

Request Parameters