1. Provisioning Interface
  2. XML Message Definitions
  3. Message Flow Example Sessions
  4. Block Transaction Committed

Block Transaction Committed

This example issues several requests within a block transaction. All of the requests succeed; therefore, the transaction is automatically committed.

Table 5-37 Block Transaction Committed Message Flow Example

Message Description
CPS—>SDS 
<tx>
  <updateSubscriber ent="subscriberRouting" ns="dsr">
    <imsi>310910421000109</imsi>
    <ltehss>LTE_HSS_2</ltehss>
  </updateSubscriber>
  <updateSubscriber ent="subscriberRouting" ns="dsr">
    <msisdn>156342101009</msisdn>
    <ltehss>LTE_HSS_2</ltehss>
  </updateSubscriber>
  <updateSubscriber ent="subscriberRouting" ns="dsr">
    <imsi>310910421000110</imsi>
    <msisdn>15634210110</msisdn>
    <ltehss>LTE_HSS_6</ltehss>
  </updateSubscriber>
  <updateSubscriber ent="subscriberRouting" ns="dsr">
    <ltehss>LTE_HSS_6</ltehss>
  </updateSubscriber>
</tx>

A single request is sent contain 3 different <updateSubscriber> requests for existing stand-alone IMSI or MSISDN routing entities.

Response indicates that 3 requests were within the transaction. Each request indicates that 1 row was affected for each, and every request was successful (as error="0" in all response).

CPS<—SDS 
<txResp nbreq="3">
  <updateSubscriberResp>
    <res error="0" affected="1”/>
  </updateSubscriberResp>
  <updateSubscriberResp>
    <res error="0" affected="1”/>
  </updateSubscriberResp>
  <updateSubscriberResp>
    <res error="0" affected="2” description=
    “changed (imsi 310910421000110, 
    dn 15634210110), ltehss LTE_HSS_6“/>
  </updateSubscriberResp>
</txResp>