Block Transaction Rolled Back

This example issues several requests within a block transaction. One of the requests fails; therefore, the transaction is automatically rolled back.

Block Transaction Rolled Back Message Flow Example
Message	Description
CPS—>SDS	<tx resonly=”n”> <updateSubscriber ent="subscriberRouting" ns="dsr"> <imsi>310910421000111</imsi> <ltehss>LTE_HSS_2</ltehss> </updateSubscriber> <updateSubscriber ent="subscriberRouting" ns="dsr"> <msisdn>156342101011</msisdn> <ltehss>LTE_HSS_2</ltehss> </updateSubscriber> <updateSubscriber ent="subscriberRouting" ns="dsr"> <imsi>310910421000112</imsi> <ltehss>LTE_HSS_99</ltehss> </updateSubscriber> <updateSubscriber ent="subscriberRouting" ns="dsr"> <msisdn>15634210112</msisdn> <ltehss>LTE_HSS_6</ltehss> </updateSubscriber> </tx>	A single request is sent containing 4 different updateSubscriber requests for existing stand-alone IMSI or MSISDN routing entities. The request is made to include each request in the response for the entire transaction (indicated by the resonly="n" attribute). Response to create subscriber routing entities - success. Affected rows = 1 (as 1 NAI entry was updated). The first two requests that were successful, indicate no error and the correct number of affected rows. The third request that fails gives the correct error and no affected rows. The fourth request that has not been executed has an error code indicating NOT_PROCESSED. All requests are rolled back.
CPS<—SDS	<txResp nbreq="4"> <updateSubscriberResp> <updateSubscriber ent="subscriberRouting" ns="dsr"> <imsi>310910421000111</imsi> <ltehss>LTE_HSS_2</ltehss> </updateSubscriber> <res error="0" affected="1"/> </updateSubscriberResp> <updateSubscriberResp> <updateSubscriber ent="subscriberRouting" ns="dsr"> <msisdn>156342101011</msisdn> <ltehss>LTE_HSS_2</ltehss> </updateSubscriber> <res error="0" affected="1"/> </updateSubscriberResp> <updateSubscriberResp> <updateSubscriber ent="subscriberRouting" ns="dsr"> <imsi>310910421000112</imsi> <ltehss>LTE_HSS_99</ltehss> </updateSubscriber> <res description= ”destination not found” error="2006" affected="0"/> </updateSubscriberResp> <updateSubscriberResp> <updateSubscriber ent="subscriberRouting" ns="dsr"> <msisdn>15634210112</msisdn> <ltehss>LTE_HSS_6</ltehss> </updateSubscriber> <res error="1" affected="0"/> </updateSubscriberResp> </txResp>

Block Transaction Rolled Back Message Flow Example

Message

Description

CPS—>SDS

<tx resonly=”n”>
<updateSubscriber ent="subscriberRouting" ns="dsr">
<imsi>310910421000111</imsi>
<ltehss>LTE_HSS_2</ltehss>
</updateSubscriber>
<updateSubscriber ent="subscriberRouting" ns="dsr">
<msisdn>156342101011</msisdn>
<ltehss>LTE_HSS_2</ltehss>
</updateSubscriber>
<updateSubscriber ent="subscriberRouting" ns="dsr">
<imsi>310910421000112</imsi>
<ltehss>LTE_HSS_99</ltehss>
</updateSubscriber>
<updateSubscriber ent="subscriberRouting" ns="dsr">
<msisdn>15634210112</msisdn>
<ltehss>LTE_HSS_6</ltehss>
</updateSubscriber>
</tx>

A single request is sent containing 4 different updateSubscriber requests for existing stand-alone IMSI or MSISDN routing entities. The request is made to include each request in the response for the entire transaction (indicated by the resonly="n" attribute).

Response to create subscriber routing entities - success. Affected rows = 1 (as 1 NAI entry was updated).

The first two requests that were successful, indicate no error and the correct number of affected rows. The third request that fails gives the correct error and no affected rows. The fourth request that has not been executed has an error code indicating NOT_PROCESSED. All requests are rolled back.

CPS<—SDS

<txResp nbreq="4">
<updateSubscriberResp>
<updateSubscriber ent="subscriberRouting" ns="dsr">
<imsi>310910421000111</imsi>
<ltehss>LTE_HSS_2</ltehss>
</updateSubscriber>
<res error="0" affected="1"/>
</updateSubscriberResp>
<updateSubscriberResp>
<updateSubscriber ent="subscriberRouting" ns="dsr">
<msisdn>156342101011</msisdn>
<ltehss>LTE_HSS_2</ltehss>
</updateSubscriber>
<res error="0" affected="1"/>
</updateSubscriberResp>
<updateSubscriberResp>
<updateSubscriber ent="subscriberRouting" ns="dsr">
<imsi>310910421000112</imsi>
<ltehss>LTE_HSS_99</ltehss>
</updateSubscriber>
<res description= ”destination not found” error="2006" 
affected="0"/>
</updateSubscriberResp>
<updateSubscriberResp>
<updateSubscriber ent="subscriberRouting" ns="dsr">
<msisdn>15634210112</msisdn>
<ltehss>LTE_HSS_6</ltehss>
</updateSubscriber>
<res error="1" affected="0"/>
</updateSubscriberResp>
</txResp>