WebSphere brand IBM WebSphere IP Multimedia Subsystem Connector, Version 6.2

Sh subscriber profile Web service call flows

Call flows describe how the applications get and update data, as well as how applications subscribe to data change notification, and how notifications about user state are passed between the IMS™ Application Server, Diameter Enabler base, and the Home Subscriber Server (HSS).

Data get (User Data Request) flow:
  1. IMS Application Server invokes one of the Sh data get Web service requests, such as getRepositoryData.
  2. The Sh subscriber profile Web service application validates the parameters received from the Web service interface and then builds a Sh User Data Request message using the parameters. Diameter Enabler base then sends the User Data Request message to the HSS.
  3. The HSS receives the User Data Request message, retrieves the requested data, and then returns the data to the Diameter Enabler base in a User Data Answer message.
  4. The Sh subscriber profile Web service application receives the User Data Answer message from the Diameter Enabler base containing the requested data in XML format. The Sh subscriber profile Web service application parses the XML data received and returns the information to the Web service interface.
Data update (Profile Update Request):
  1. IMS Application Server invokes one of the Sh data update Web service requests, such as updateRepositoryData.
  2. The Sh subscriber profile Web service application validates the parameters received from the Web service interface and then builds a Sh Profile Update Request message using the parameters. Diameter Enabler base then sends the Profile Update Request message to the HSS.
  3. The HSS receives the Profile Update Request message, updates the requested profile information, and returns the result to the Diameter Enabler base in a Profile Update Answer message.
  4. The Sh subscriber profile Web service application receives the Profile Update Answer message from the Diameter Enabler base that contains the result of the profile update operation. The Sh subscriber profile Web service application returns the result to the Web service interface.
Data subscribe (Subscribe Notifications Request):
  1. IMS Application Server invokes one of the Sh data subscription Web service requests, such as subscribeRepositoryData.
  2. The Sh subscriber profile Web service application validates the parameters received from the Web service interface and then builds a Sh Subscription Notifications Request message using the parameters. Diameter Enabler base then sends the Subscription Notifications Request message to the HSS.
  3. The HSS receives the Subscription Notifications Request message, creates a subscription to the requested profile information, and returns the result to the Diameter Enabler base in a Subscription Notifications Answer message.
  4. The Sh subscriber profile Web service application receives the Subscription Notification Answer message from the Diameter Enabler base that contains the result of the Subscribe Notification operation and returns the result to the Web service interface.
Data notify (Notification Request):
  1. To receive notifications the IMS Application Server must first implement the server side Notify WSDL and register the Web service endpoint as the callback URI in all subscriptions.
  2. When data with an associated subscription is updated in the HSS, the HSS sends a Push Notification message including the updates to the Diameter Enabler base.
  3. The Diameter Enabler base sends the message to the Sh subscriber profile Web service application. The Sh subscriber profile Web service application references the subscriptions associated with the notification in the database to retrieve the callback URI.
  4. The Sh subscriber profile Web service application sends the updated data received in the notification request to the appropriate notification Web services.



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.