Examples

These examples show the SDS provisioning request and response contents that are stored within the <soapenv:Body> or <SOAP-ENV:Body> tags. See Start Transaction Examples for an example of the whole SOAP request/response text.

The format of the response differs depending on whether the group="y" attribute is specified.

If group="y" is not specified, then each routing entity that was found is displayed with its destination values.

If group="y" is specified, then the result response includes an optional Account ID value, all MSISDN and IMSI values for that subscriber, and one set of destination values (all routing entities within a subscriber have the same destination values).

Read Routing Entities (not subscribers)

This example reads IMSI and MSISDN routing entities and displays their destination values. It does not matter if any of the routing entities are assigned to a subscriber because the same result will occur.

Request:

<readSubscriberRequest>
  <addressList>
    <imsi>111111111100001</imsi>
    <imsi>111111111100002</imsi>
    <msisdn>8004605500</msisdn>
  </addressList>
</readSubscriberRequest>

Response:

<ns3:readSubscriberResponse>
  <result affected="3" error="0"></result>
  <resultSet>
    <imsi imsi="111111111100001"> 
      <ltehss>LTE_HSS_4</ltehss>
      <aaa>AAA_4</aaa>
    </imsi>
    <imsi imsi="111111111100002"> 
      <ltehss>LTE_HSS_4</ltehss>
      <aaa>AAA_4</aaa>
    </imsi>
    <msisdn msisdn="8004605500"> 
      <ltehss>LTE_HSS_4</ltehss>
      <aaa>AAA_4</aaa>
    </msisdn>
  </resultSet>
</ns3:readSubscriberResponse>

Read Routing Entities with Not Found MSISDN/IMSI Values

This example reads IMSI and MSISDN routing entities and displays their destination values. In this example, one MSISDN and one IMSI value do not exist, so the response returns the two values that do exist. The same result will occur if any of the routing entities are assigned to a subscriber.

Request:

<readSubscriberRequest>
  <addressList>
    <imsi>777777777777777</imsi>
    <imsi>111111111100002</imsi>
    <msisdn>8004605500</msisdn>
    <msisdn>88888888888888</msisdn>
  </addressList>
</readSubscriberRequest>

Response:

<ns3:readSubscriberResponse>
  <result affected="2" error="0"></result>
  <resultSet>
    <imsi imsi="111111111100002"> 
      <ltehss>LTE_HSS_4</ltehss>
      <aaa>AAA_4</aaa>
    </imsi>
    <msisdn msisdn="8004605500"> 
      <ltehss>LTE_HSS_4</ltehss>
      <aaa>AAA_4</aaa>
    </msisdn>
  </resultSet>
</ns3:readSubscriberResponse>

Read Subscriber (success)

This example reads a subscriber and displays all of the subscriber data. Any of the subscriber Account ID, MSISDN or IMSI values can be specified. In this example, the MSISDN value is specified.

Request:

<readSubscriberRequest group=”y”>
  <addressList>
    <msisdn>8004605500</msisdn>
  </addressList>
</readSubscriberRequest>

Response:

<ns3:readSubscriberResponse>
  <result affected="1" error="0"></result>
  <resultSet>
    <subscriber>
      <accountId>80044400001234567890111112</accountId>
      <imsi>111111111100001</imsi>
      <imsi>111111111100002"</imsi>
      <msisdn>8004605500</msisdn>
      <ltehss>LTE_HSS_4</ltehss>
      <aaa>AAA_4</aaa>
    </subscriber>
  </resultSet>
</ns3:readSubscriberResponse>

Read Subscriber Fails for Stand-alone Routing Entity

This example attempts to read a subscriber. The request fails because the specified MSISDN value is for a stand-alone routing entity.

Request:

<readSubscriberRequest group=”y”>
  <addressList>
    <msisdn>9198675309</msisdn>
  </addressList>
</readSubscriber>

Response:

<ns3:readSubscriberResponse>
  <result description=”subscriber not found” 
   affected="0" error="2022"></result>
</ns3:readSubscriberResponse>