4.7 Network Controlled Notifications

29.198-04-33GPPOpen Service Access (OSA) Application Programming Interface (API)Part 4: Call controlRelease 9Subpart 3: Multi-party call control Service Capability Feature (SCF)TS

The following sequence diagram shows how an application can receive notifications that have not been created by the application, but are provisioned from within the network.

1: The application is started. The application creates a new IpAppMultiPartyCallControlManager to handle callbacks.

2: The enableNotifications method is invoked on the IpMultiPartyCallControlManager interface to indicate that the application is ready to receive notifications that are created in the network. For illustrative purposes we assume notifications of type "B" are created in the network.

3: When a network created trigger occurs the application is notified on the callback interface.

4: The event is forwarded to the application.

5: When a network created trigger occurs the application is notified on the callback interface.

6: The event is forwarded to the application.

7: When the application does not want to receive notifications created in the network anymore, it invokes disableNotifications on the IpMultiPartyCallConrolManager interface. From now on the gateway will not send any notifications to the application that are created in the network.