This example issues several requests within one transaction which is then committed successfully.
| Message | Description | |
|---|---|---|
| CPS—>SDS | <startTransactionRequest>0</startTransactionRequest> |
Request to start a transaction immediately. Response to start transaction - success. |
| CPS<—SDS | <ns2:sdsResult affected="0" error="0"> </ns2:sdsResult> |
|
| CPS—>SDS | <updateSubscriberRequest <addressList> <imsi>310910421000444</imsi> <msisdn>15634210444</msisdn> </addressList> <destinationList> <ltehss>LTE_HSS_1</ltehss> </destinationList> </updateSubscriberRequest> |
Request to add new stand-alone IMSI and MSISDN - success. |
| CPS<—SDS | <ns2:sdsResult affected="2" error="0"/> </ns2:sdsResult> |
|
| CPS—>SDS | <updateSubscriberRequest> <addressList> <imsi>310910421000555</imsi> <msisdn>15634210555</msisdn> </addressList> <destinationList> <ltehss>LTE_HSS_2</ltehss> </destinationList> </updateSubscriberRequest> |
Request to update existing stand-alone IMSI and MSISDN - success. |
| CPS<—SDS | <ns2:sdsResult affected="2" error="0"/> </ns2:sdsResult> |
|
| CPS—>SDS | <updateSubscriberNaiRequest> <naiList> <host>operator.com</host> <user>roger.brown</user> </naiList> <destinationList> <ltehss>LTE_HSS_1</ltehss> </destinationList> </updateSubscriberNaiRequest> |
Request to update an NAI - success. |
| CPS<—SDS | <ns2:sdsResult affected="1" error="0"> </ns2:sdsResult> |
|
| CPS—>SDS | <commitRequest> </commitRequest> |
Request to commit the transaction. Response to commit transaction - success. All updates were successfully performed. |
| CPS<—SDS | <ns2:sdsResult affected="0" error="0"> </ns2:sdsResult> |
|