This example shows three request/response pairs that are exchanged between the CPS and SDS. These requests are processed as single command transactions, which means that each request is immediately committed to the database. This example creates IMSI and MSISDN routing entities.
| Message | Description | |
|---|---|---|
| CPS—>SDS | <updateSubscriberRequest> <addressList> <imsi>310910421000106</imsi> <imsi>310910421000307</imsi> <imsi>310910421000309</imsi> <msisdn>15634210106</msisdn> <msisdn>15634210107</msisdn> </addressList> <destinationList> <ltehss>LTE_HSS_2</ltehss> <aaa>AAA_4</aaa> </destinationList> </updateSubscriberRequest> |
Request to create 5 stand-alone routing entities - 3 IMSIs and 2 MSISDNs with an LTE HSS and AAA server destinations. Note: Request is made to include the original request in the response.
Response to create stand-alone routing entities - success. Affected rows = 5 (as 5 new entries created for 3 IMSIs and 2 MSISDNs). |
| CPS<—SDS | <ns2:sdsResult affected="5" error="0"> </ns2:sdsResult> |
|
| CPS—>SDS |
<updateSubscriberRequest> <addressList> <imsi>310910421000106</imsi> <msisdn>15634210106</msisdn> </addressList> <destinationList> <ltehss>LTE_HSS_5</ltehss> </destinationList> </updateSubscriberRequest> |
Request to update existing IMSI and MSISDN subscriber routing entities with a new LTE HSS value. Response to update subscriber routing entities - success. Affected rows = 2 (2 entries for an IMSI and MSISDN were updated with new LTE HSS value). |
| CPS<—SDS | <ns2:sdsResult affected="2" error="0"> </ns2:sdsResult> |
|
| CPS—>SDS | <updateSubscriberRequest> <addressList> <imsi>310910421000102</imsi> </addressList> <destinationList> <ltehss>BAD_VALUE</ltehss> </destinationList> </updateSubscriberRequest> |
Request to create a stand-alone routing entitiy with an invalid LTE HSS destination value. Request fails, as the destination does not exist. |
| CPS<—SDS | <ns2:sdsResult description=“destination not found” affected="0" error="2006"></ns2:sdsResult> |
|