Some of the following examples are based upon previous requests. The order of the requests can be important.
This example creates three new NAI routing entities and sets their destination values to the specified values. This example assumes that the host and destination values already exist.
<updateSubscriberNai ent=”subscriberRouting” ns=”dsr” id=”101”> <host>oracle.com</host> <user>John.Smith</user> <user>Jane.Doe</user> <user>Mike.Jones</user> <imshss>IMS_HSS_1</imshss> <ltehss>LTE_HSS_1</ltehss> <aaa>AAA_Texas</aaa> </updateSubscriberNai>
<updateSubscriberNaiResp id=”101”> <res error=”0” affected=”3”/> </updateSubscriberNaiResp>
The result of this request is that the specified NAI routing entities are updated with specified values.
<updateSubscriberNai ent=”subscriberRouting” ns=”dsr” id=”102”> <host>oracle.com</host> <user>Jane.Doe</user> <user>Mike.Jones</user> <ltehss>LTE_HSS_4</ltehss> <pcrf>PCRF_Ohio</pcrf> </updateSubscriberNai>
<updateSubscriberNaiResp id=”102”> <res error=”0” affected=”2”/> </updateSubscriberNaiResp>
This example fails to update existing NAI routing entities with new destination values because the destination does not exist.
No changes are made to the database because the request failed.
<updateSubscriberNai ent=”subscriberRouting” ns=”dsr” id=”103”> <host>oracle.com</host> <user>Jane.Doe</user> <ltehss>junk</ltehss> </updateSubscriberNai>
<updateSubscriberNaiResp id=”102”> <res error=”2006” affected=”0” description="destination not found”/> </updateSubscriberNaiResp>