Below are examples of how to use the <updateSubscriber> request and likely response. Some of these examples are based on previous requests; hence, the order of the requests could be important.
These examples show the SDS provisioning request and response contents that are stored within the <soapenv:Body> or <SOAP-ENV:Body> tags. See the Start Transaction Examples for examples of the entire SOAP request/response text.
This example creates new stand-alone IMSI and MSISDN routing entities and sets their destination values to the specified values.
<updateSubscriberRequest> <addressList> <imsi>111111111100001</imsi> <imsi>111111111100002</imsi> <imsi>111111111100003</imsi> <msisdn>8004605500</msisdn> <msisdn>8004605503</msisdn> </addressList> <destinationList> <ltehss>LTE_HSS_1</ltehss> </destinationList> </updateSubscriberRequest>
<ns2:sdsResult affected="5" error="0" </ns2:sdsResult>
The result of this request is that the IMSI and MSISDN routing entities are updated with specified values.
<updateSubscriberRequest> <addressList> <imsi>111111111100001</imsi> <imsi>111111111100002</imsi> <imsi>111111111100003</imsi> <msisdn>8004605500</msisdn> </addressList> <destinationList> <ltehss>LTE_HSS_4</ltehss> <aaa>AAA_4</aaa> </destinationList> </updateSubscriberRequest>
<ns2:sdsResult affected="4" error="0" </ns2:sdsResult>
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.
<updateSubscriberRequest group=”y”> <addressList> <imsi>111111111100001</imsi> <imsi>111111111100002</imsi> <msisdn>8004605500</msisdn> </addressList> <destinationList> </destinationList> </updateSubscriberRequest>
<ns2:sdsResult affected="1" error="0"> </ns2:sdsResult>
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.
<updateSubscriberRequest group=”y”> <addressList> <imsi>111111111100003</imsi> <msisdn>8004605503</msisdn> </addressList> <destinationList> </destinationList> </updateSubscriberRequest>
<ns2:sdsResult affected="0" error="2029" description= ”all routes must have the same destination values”> </ns2:sdsResult>
This example adds an Account ID to an existing subscriber. Any of the subscriber 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.
<updateSubscriberRequest group=”y”> <addressList> <accountId>80044400001234567890111112</accountId> <msisdn>8004605500</msisdn> </addressList> <destinationList> </destinationList> </updateSubscriberRequest>
<ns2:sdsResult affected="1" error="0"> </ns2:sdsResult>
The result of this request is that all of the subscriber's IMSI and MSISDN routing entities will have a new destination value.
<updateSubscriberRequest> <addressList> <imsi>111111111100002</imsi> </addressList> <destinationList> <ltehss>LTE_HSS_99</ltehss> </destinationList> </updateSubscriberRequest>
<ns2:sdsResult affected="3" error="0" </ns2:sdsResult>
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 does not matter which of the subscriber's routing entities is used. All entities have the same destination values.
<updateSubscriberRequest group=”y”> <addressList> <deleteMsisdn>8004605500</deleteMsisdn> <msisdn>8884605500</msisdn> </addressList> <destinationList> </destinationList> </updateSubscriberRequest>
<ns2:sdsResult affected="1" error="0"> </ns2:sdsResult>
This example replaces several identification 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. All routing entities have the same destination values.
<updateSubscriberRequest> <addressList> <deleteImsi>111111111100001</deleteImsi> <deleteImsi>111111111100002</deleteImsi> <deleteMsisdn>8884605500</deleteMsisdn> <imsi>888888888800001</imsi> <imsi>888888888800002</imsi> <msisdn>8884605555</msisdn> </addressList> <destinationList> </destinationList> </updateSubscriberRequest>
<ns2:sdsResult affected="1" error="0"> </ns2:sdsResult>
This example creates a subscriber using new routing entities with specified destinations.
<updateSubscriberRequest group=”y”> <addressList> <accountId>11111222223333344444555556</accountId> <imsi>333333333300001</imsi> <imsi>333333333300002</imsi> <msisdn>9198675309</msisdn> </addressList> <destinationList> <ltehss>LTE_HSS_3</ltehss> <aaa>AAA_3</aaa> </destinationList> </updateSubscriberRequest>
<ns2:sdsResult affected="1" error="0"> </ns2:sdsResult>
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.
<updateSubscriberRequest group=”y”> <addressList> <accountId>1111122222</accountId> <imsi>333333333300003</imsi> <imsi>333333333300004</imsi> <msisdn>9198675309</msisdn> </addressList> <destinationList> </destinationList> </updateSubscriberRequest>
<ns2:sdsResult affected="0" error="2013" description= ”at least one destination must be specified”> </ns2:sdsResult>