Below are examples of how to use the <updateSubscriber> request and likely response. Some of these examples are based upon previous requests; hence, the order of the requests could be important.
This example creates new stand-alone IMSI and MSISDN routing entities and sets their destination values to the specified values.
<updateSubscriber ent=”subscriberRouting” ns=”dsr” resonly=”n” id=”101”> <imsi>111111111100001</imsi> <imsi>111111111100002</imsi> <imsi>111111111100003</imsi> <msisdn>8004605500</msisdn> <msisdn>8004605503</msisdn> <ltehss>LTE_HSS_1</ltehss> </updateSubscriber>
<updateSubscriberResp id=”101”> <updateSubscriber ent=”subscriberRouting” ns=”dsr” resonly=”n” id=”101”> <imsi>111111111100001</imsi> <imsi>111111111100002</imsi> <imsi>111111111100003</imsi> <msisdn>8004605500</msisdn> <msisdn>8004605503</msisdn> <ltehss>LTE_HSS_1</ltehss> </updateSubscriber> <res error=”0” affected=”5”> </updateSubscriberResp>
The result of this request is that the IMSI and MSISDN routing entities are updated with specified values.
<updateSubscriber ent=”subscriberRouting” ns=”dsr” id=”102”> <imsi>111111111100001</imsi> <imsi>111111111100002</imsi> <imsi>111111111100003</imsi> <msisdn>8004605500</msisdn> <ltehss>LTE_HSS_4</ltehss> <aaa>AAA_4</aaa> </updateSubscriber>
<updateSubscriberResp id=”102”> <res error=”0” affected=”4”/> </updateSubscriberResp>
This example creates a subscriber using existing routing entities that all have the same destination values.
After this request is completed, a new subscriber is created and all of the routing entities are assigned to that subscriber.
<updateSubscriber ent=”subscriberRouting” ns=”dsr” id=”103” group=”y”> <imsi>111111111100001</imsi> <imsi>111111111100002</imsi> <msisdn>8004605500</msisdn> </updateSubscriber>
<updateSubscriberResp id=”103”> <res error=”0” affected=”1”/> </updateSubscriberResp>
This example fails when creating a subscriber using existing routing entities because the existing routing entities have different destination values.
No changes are made to the database because the request failed.
<updateSubscriber ent=”subscriberRouting” ns=”dsr” id=”104” group=”y”> <imsi>111111111100003</imsi> <msisdn>8004605503</msisdn> </updateSubscriber>
<updateSubscriberResp id=”104”> <res error=”2029” affected=”0” description= ”all routes must have the same destination values”/> </updateSubscriberResp>
This example adds an Account ID to an existing subscriber. Any of the subscriber's IMSI or MSISDN values can be used. For this example, the MSISDN value is used.
The result of this request is that the subscriber will have an Account ID value.
<updateSubscriber ent=”subscriberRouting” ns=”dsr” id=”105” group=”y”> <accountId>80044400001234567890111112</accountId> <msisdn>8004605500</msisdn> </updateSubscriber>
<updateSubscriberResp id=”105”> <res error=”0” affected=”1”> </updateSubscriberResp>
The result of this request is that all of the subscriber's IMSI and MSISDN routing entities will have a new destination value
<updateSubscriber ent=”subscriberRouting” ns=”dsr” id=”106”> <imsi>111111111100002</imsi> <ltehss>LTE_HSS_99</ltehss> </updateSubscriber>
<updateSubscriberResp id=”106”> <res error=”0” affected=”3”/> </updateSubscriberResp>
This example replaces an MSISDN value for an existing subscriber. The new MSISDN routing entity inherits the destination values from an old IMSI or MSISDN routing entity. (It doesn't matter which of the Subscriber's routing entities is used because they all have the same destination values.)
<updateSubscriber ent=”subscriberRouting” ns=”dsr” id=”107” group=”y”> <deleteMsisdn>8004605500</deleteMsisdn> <msisdn>8884605500</msisdn> </updateSubscriber>
<updateSubscriberResp id=”107”> <res error=”0” affected=”1”/> </updateSubscriberResp>
This example replaces several identification (Account ID, IMSI and MSISDN) values for an existing subscriber. The new IMSI and MSISDN routing entities inherit the destination values from the old IMSI and MSISDN routing entities. It does not matter which of the Subscriber's routing entities is used because they all have the same destination values.
<updateSubscriber ent=”subscriberRouting” ns=”dsr” id=”108” group=”y”> <deleteAccountId>80044400001234567890111112</deleteAccountId> <deleteImsi>111111111100001</deleteImsi> <deleteImsi>111111111100002</deleteImsi>> <deleteMsisdn>8884605500</deleteMsisdn> <imsi>888888888800001</imsi> <imsi>888888888800002</imsi> <msisdn>8884605555</msisdn> </updateSubscriber>
<updateSubscriberResp id=”108”> <res error=”0” affected=”1”/> </updateSubscriberResp>
This example creates a subscriber using new routing entities with specified destinations.
<updateSubscriber ent=”subscriberRouting” ns=”dsr” id=”109” group=”y”> <accountId>11111222223333344444555556</accountId> <imsi>333333333300001</imsi> <imsi>333333333300002</imsi> <msisdn>9198675309</msisdn> <ltehss>LTE_HSS_3</ltehss> <aaa>AAA_3</aaa> </updateSubscriber>
<updateSubscriberResp id=”109”> <res error=”0” affected=”1”/> </updateSubscriberResp>
This example fails when creating a subscriber using new routing entities because no destinations were specified.
No changes are made to the database because the request failed.
<updateSubscriber ent=”subscriberRouting” ns=”dsr” id=”110” group=”y”> <accountId>1111122222</accountId> <imsi>333333333300003</imsi> <imsi>333333333300004</imsi> <msisdn>9198675309</msisdn> </updateSubscriber>
<updateSubscriberResp id=”110”> <res error=”2013” affected=”0” description= ”at least one destination must be specified”/> </updateSubscriberResp>