B.1 Message flows

29.3283GPPIP Multimedia (IM) Subsystem Sh interfaceRelease 18Signalling flows and message contentsTS

The following message flows give examples regarding which Diameter messages shall be sent in scenarios described in 3GPP TS 23.218 [4].

B.1.1 Data Update, Registration, Notification Subscription.

Figure B.1.1: Data Update, Registration, Notification Subscription

1. A user subscribes to a new service. The operator provisions the service in an AS. The AS stores some service data for a user in the HSS, Sh-Update (user identity, updated data) e.g. repository data.

2. HSS confirms the data is updated

3. Some time later, user registers with the network

4. S-CSCF downloads the data from the HSS (during the procedure S-CSCF Registration Notification on Cx interface). Filter criteria specify that the AS wants to be notified that the end user is registered.

5. 200 OK

6. S-CSCF sends third party registration message to the application server to notify that user is registered.

7. 200 OK

8. The AS subscribes to notifications and downloads data needed for providing service from HSS, by means of Sh-Subs-Notif (user identity, requested data, service information and send data indication).

9. HSS confirms the subscription request and sends data to AS

10. At some moment, the AS decides to update user’s service data e.g. repository data in the HSS, by means of Sh-Update (user identity, updated data).

11. The HSS confirms the service data is updated.

12. At some moment, user data is updated in the HSS. As the AS subscribed to notifications (step 8), the HSS sends to the AS the requested updates, by means of Sh-Notif (user identity, updated data).

13. The AS acknowledges the notification.

Annex C (informative):
UML model of the data downloaded over Sh interface

The purpose of this UML model is to define in an abstract level the structure of the data downloaded over the Sh interface and describe the purpose of the different information classes included in it.