29.198-053GPPOpen Service Access (OSA) Application Programming Interface (API)Part 5: User interaction Service Capability Feature (SCF)Release 9TS
This sequence shows a Pre-paid application that uses the Advice of Charge feature. The application will send the charging information before the actual call setup and when during the call the charging changes new information is sent in order to update the end-user. Note that the Advice of Charge feature requires an application in the end-user terminal to display the charges for the call, depending on the information received from the application.
1: This message is used by the application to create an object implementing the IpAppCallControlManager interface.
2: This message is sent by the application to enable notifications on new call events. As this sequence diagram depicts a pre-paid service, it is likely that only new call events within a certain address range will be enabled. When a new call, that matches the event criteria, arrives a message (not shown) is directed to the object implementing the IpCallControlManager. Assuming that the criteria for creating an object implementing the IpCall interface (e.g. load control values not exceeded) are met, other messages (not shown) are used to create the call and associated call leg object.
3: The incoming call triggers the Pre-Paid Application (PPA).
4: The message is forwarded to the application.
5: A new object on the application side for the Call object is created
6: The Pre-Paid Application (PPA) sends the AoC information (e.g. the tariff switch time). (it shall be noted the PPA contains ALL the tariff information and knows how to charge the user).
During this call sequence 2 tariff changes take place. The call starts with tariff 1, and at the tariff switch time (e.g. 18:00 hours) switches to tariff 2. The application is not informed about this (but the end-user is!)
7: The Pre-Paid Application (PPA) requests to supervise the call. The application will be informed after the period indicated in the message. This period is related to the credits left on the account of the pre-paid subscriber.
8: The application requests to route the call to the destination address.
9: At the end of each supervision period the application is informed and a new period is started.
10: The message is forwarded to the application.
11: The Pre-Paid Application (PPA) requests to supervise the call for another call duration.
12: At the end of each supervision period the application is informed and a new period is started.
13: The message is forwarded to the application.
14: Before the next tariff switch (e.g. 19:00 hours) the application sends a new AOC with the tariff switch time. Again, at the tariff switch time, the network will send AoC information to the end-user.
15: The Pre-Paid Application (PPA) requests to supervise the call for another call duration. When the timer expires it will indicate that the user is almost out of credit.
16: When the user is almost out of credit the application is informed.
17: The message is forwarded to the application.
18: The application creates a new call back interface for the User interaction messages.
19: A new UI Call object that will handle playing of the announcement needs to be created
20: The Gateway creates a new UI call object that will handle playing of the announcement.
21: With this message the announcement is played to the parties in the call.
22: The user indicates that the call should continue.
23: The message is forwarded to the application.
24: The user does not terminate so the application terminates the call after the next supervision period.
25: The user is out of credit and the application is informed.
26: The message is forwarded to the application.
27: With this message the application requests to release the call.
28: Terminating the call which has still a UICall object associated will result in a userInteractionFaultDetected. The UICall object is terminated in the gateway and no further communication is possible between the UICall and the application.