Content for TS 23.333 Word version: 18.1.0

1… 4 5… 5.8… 5.12… 5.14… 5.20… 5.24… 6… 6.1.8… 6.2… 6.2.3… 6.2.4… 6.2.5 6.2.6… 6.2.7… 6.2.8… 6.2.9… 6.2.10… 6.2.10.2.7 6.2.10.3… 6.2.11… 6.2.13… 6.2.13.2.6… 6.2.14… 6.2.15… 6.2.16… 6.2.18… 6.2.19… 6.2.19.3… 6.2.20… 6.2.21… 6.2.22… 6.2.23 6.2.24… 7 8… 8.11… 8.20 8.21 8.22 8.23… 8.30… 8.39… 8.45… 8.56…

6.2 Call Related Procedures p. 83

6.2.1 Play Tone Procedure p. 83

6.2.1.1 General p. 83

The following procedure assumes the IMS session has been established and the bearer is through-connected and the MRFC has received a trigger to play a tone and the MRFP selected for the call has the capabilities to provide tones.

6.2.1.2 Send tone p. 83

After reception of a trigger to play a tone, the MRFC shall initiate the Send tone procedure. The MRFC may request the MRFP to send tone to one, multiple or all terminations in a context simultaneously with the tone identifier. The tone identifier may be a pre-configured identifier.

The MRFC may request the MRFP to send tone continuously until requested to be stopped. Alternatively, duration may be indicated or provisioned in the MRFP. When the duration elapses, the tone shall be stopped.

The MRFC may request the MRFP to detect DTMF digits, and may request the MRFP to stop sending tone when a DTMF digit is detected. For the second case, only the tone completion event is notified.

The MRFC may request the MRFP to detect the tone completion, and notify the completion event and cause to the MRFC. The tone is completed when either of the following has occurred;

the duration has elapsed or:
a DTMF digit is detected by the MRFP or:
the sending tone is not successful.

6.2.1.3 Stop tone p. 83

On receipt of a trigger to stop a tone, the MRFC shall request the MRFP to stop the tone.

6.2.1.4 Tone completed p. 83

When a tone is completed, if the MRFC has requested the MRFP to notify the tone completion, the MRFP shall notify the tone completion event and the cause to the MRFC. The cause that the tone is completed may be that the duration has elapsed, a DTMF digit is detected by the MRFP, or that the tone is not successful. Then the MRFC may indicate to the AS that the tone has been stopped.

6.2.1.5 Message sequence chart p. 84

Figure 6.2.1.1 shows the message sequence chart example for sending tone.

Copy of original 3GPP image for 3GPP TS 23.333, Fig. 6.2.1.1: Sending tone (message sequence chart)

Figure 6.2.1.1: Sending tone (message sequence chart)
(⇒ copy of original 3GPP image)

6.2.2 Play Announcement Procedure p. 84

6.2.2.1 General p. 84

The following procedure assumes the IMS session has been established and the bearer is through-connected, and the MRFC has received a trigger to play announcement, and the MRFP selected for the call has the capabilities to provide announcement.

6.2.2.2 Start announcement p. 84

After reception of a trigger to play the announcement, the MRFC should initiate the Start announcement procedure. The MRFC shall request the MRFP to play announcement to one, multiple or all terminations in a context with the announcement identifier. The announcement identifier may be a pre-configured identifier (such as a number).

If it is a sequence of announcements, the MRFC shall request the MRFP to play all the announcements with one request. The MRFC may request the MRFP to play the announcement in a loop continuously until requested to be stopped or in a loop with a fixed number of times. For the second case, if the fixed number of times is exhausted, the announcement is completed successfully.

If it is a variable announcement, the MRFC may indicate to the MRFP the following variants to the announcements:

Date: A date variant is made up of three components: day, month and year. The MRFC shall indicate the date value and the date format to the MRFP, such as " day-month-year" or "year-month-day".
Time: A time variant is made up of two components: hour and minute, The MRFC shall indicate the time value and the time format to the MRFP, such as "12-hours format" or "24-hours format".
Digits (the announcement may contain a number of digits to be controlled by the MRFC for example a telephone number): a digits variant is made up of a sequence digit.
Money (currency).
Integer (a value within the announcement that is controlled by the MRFC, e.g. "you are caller number 3 in the queue"): an integer variant may be spoken as a cardinal or ordinal value. The MRFC shall indicate to the MRFP the value and type to be spoken.

The MRFC may request the MRFP to detect DTMF digit while playing an announcement, and may request the MRFP to stop playing an announcement when a DTMF digit is detected. For the latter case, only the announcement completion event is notified.

The MRFC may request the MRFP to detect the announcement completion, and notify the completion event and cause to the MRFC. The announcement is completed when either of the following has occurred;

the announcement has been completed successfully or:
a DTMF digit is detected by the MRFP or:
the playing announcement is not successful.

6.2.2.3 Stop announcement p. 85

On receipt of a trigger to stop the announcement, the MRFC shall request the MRFP to stop the announcement.

6.2.2.4 Announcement completed p. 85

When an announcement is completed, if the MRFC has requested the MRFP to notify the announcement completion, the MRFP shall notify the announcement completion event and the cause to the MRFC. The cause that the announcement is completed may be the announcement has been completed successfully, or a DTMF digit is detected by the MRFP, or the playing announcement is not successful. Then the MRFC may indicate to the AS that the announcement has been stopped.

6.2.2.5 Message sequence chart p. 85

Figure 6.2.2.1 shows the message sequence chart example for playing announcement.

Copy of original 3GPP image for 3GPP TS 23.333, Fig. 6.2.2.1: Playing announcement (message sequence chart)

Figure 6.2.2.1: Playing announcement (message sequence chart)
(⇒ copy of original 3GPP image)