1. Provisioning Interface
  2. XML Message Definitions
  3. Message Flow Example Sessions
  4. Single Command Transaction

Single Command Transaction

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, MSISDN, and External Identifier routing entities.

Table 5-34 Single Command Transaction (XML)

Message Description
CPS—>SDS 
<updateSubscriber ent="subscriberRouting" ns="dsr" resonly="n">
  <imsi>310910421000106</imsi>
  <imsi>310910421000307</imsi>
  <imsi>310910421000309</imsi>
  <msisdn>15634210106</msisdn>
  <msisdn>15634210107</msisdn>
  <ltehss>LTE_HSS_2</ltehss>
  <aaa>AAA_4</aaa>
</updateSubscriber>

Request to create 5 standalone 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 subscriber routing entities - success. Affected rows = 5 (as 5 new entries created for 3 IMSIs and 2 MSISDNs).

Note: As requested, the original XML request is included in the response.

CPS<—SDS 
<updateSubscriberResp>
  <updateSubscriber ent="subscriberRouting" ns="dsr" resonly="n">
    <imsi>310910421000106</imsi>
    <imsi>310910421000307</imsi>
    <imsi>310910421000309</imsi>
    <msisdn>15634210106</msisdn>
    <msisdn>15634210107</msisdn>
    <ltehss>LTE_HSS_2</ltehss>
    <aaa>AAA_4</aaa>
  </updateSubscriber>
  <res error="0" affected="5">
</updateSubscriberResp>
CPS—>SDS 
<updateSubscriber ent="subscriberRouting" ns="dsr" resonly="n">
  <imsi>310910421000106</imsi>
  <imsi>310910421000307</imsi>
  <imsi>310910421000309</imsi>
  <msisdn>15634210106</msisdn>
  <msisdn>15634210107</msisdn>       
<externalId>test1@oracle.com</externalId>
<externalId>test2@oracle.com</externalId>
  <ltehss>LTE_HSS_2</ltehss>
  <mtchss>MTC_HSS_4</mtchss>
</updateSubscriber>

Request to create seven standalone routing entities - 3 IMSIs, 2 MSISDNs, and 2 External Identifiers with LTE HSS and MTC HSS server destinations.

Note: Request is made to include the original request in the response.

Response to create standalone routing entities - success. Affected rows = 7 (as 7 new entries created for 3 IMSIs, 2 MSISDNs, and 2 External Identifiers).

Note: As requested, the original XML request is included in the response.

CPS<—SDS 
<updateSubscriberResp>
  <updateSubscriber ent="subscriberRouting" ns="dsr" resonly="n">
    <imsi>310910421000106</imsi>
    <imsi>310910421000307</imsi>
    <imsi>310910421000309</imsi>
    <msisdn>15634210106</msisdn>
    <msisdn>15634210107</msisdn>
<externalId>test1@oracle.com</externalId>
<externalId>test2@oracle.com</externalId>
    <ltehss>LTE_HSS_2</ltehss>
    <aaa>MTC_HSS_4</aaa>
  </updateSubscriber>
  <res error="0" affected="7">
</updateSubscriberResp>
CPS—>SDS 
<updateSubscriber ent="subscriberRouting" ns="dsr">
  <imsi>310910421000106</imsi>
  <msisdn>15634210106</msisdn>
  <ltehss>LTE_HSS_5</ltehss>
</updateSubscriber>

Request to update existing IMSI and MSISDN standalone routing entities with a new LTE HSS value.

Response to update subscriber routing entities - success. Affected rows = 2 (as 2 entries for an IMSI and MSISDN were updated with new LTE HSS value).

CPS<—SDS 
<updateSubscriberResp>
  <res error="0" affected="2"/>
</updateSubscriberResp>
CPS—>SDS 
<updateSubscriber ent="subscriberRouting" ns="dsr">
  <imsi>310910421000106</imsi>
  <msisdn>15634210106</msisdn>
<externalId>test1@oracle.com</externalId>
<externalId>test2@oracle.com</externalId>
  <mtchss>MTC_HSS_5</mtchss>
</updateSubscriber>

Request to update existing IMSI, MSISDN, and External Identifier standalone routing entities with a new MTC HSS value.

Response to update standalone routing entities - success. Affected rows = 4 (as 4 entries for an IMSI, MSISDN, and External Identifier were updated with new MTC HSS value).

CPS<—SDS 
<updateSubscriberResp>
  <res error="0" affected="4"/>
</updateSubscriberResp>
CPS—>SDS 
<updateSubscriber ent="subscriberRouting" ns="dsr">
  <imsi>310910421000102</imsi>
  <ltehss>BAD_VALUE</ltehss>
</updateSubscriber>

Request to create a subscriber routing entity with an invalid LTE HSS destination value.

Request fails, as the destination does not exist.

CPS<—SDS 
<updateSubscriberResp>
  <res description=”destination not found” error="2006" affected="0"/>
</updateSubscriberResp>