Content for TS 24.186 Word version: 19.0.0
10 Interaction with supplementary services
10.1 Originating Identification Presentation (OIP)
10.2 Terminating Identification Presentation (TIP)
10.3 Originating Identification Restriction (OIR)
10.4 Terminating Identification Restriction (TIR)
10.5 Message Waiting Indication (MWI)
10.6 Conferencing (CONF)
10.6.1 Procedure at UE
10.6.2 Procedure at IMS AS serving the user
10.7 Communication Diversion (CDIV)
10.7.1 Communication Forwarding Unconditional (CFU)
10.7.2 Communication Forwarding on Busy user (CFB)
10.7.3 Communication Deflection (CD)
10.7.4 Communication Forwarding on No Reply (CFNR)
10.7.5 Communication Forwarding on Not Reachable (CFNRc)
10.7.6 Communication Forwarding on Not Logged-in (CFNL)
10.8 Communication Waiting (CW)
10.8.1 Actions at AS of user B
10.8.2 Actions at UE of user B
10.9 Advice Of Charge (AOC)
10.10 Flexible Alerting (FA)
10.10.1 Actions at the AS serving the pilot identity
...
...
10 Interaction with supplementary services p. 26
10.1 Originating Identification Presentation (OIP) p. 26
No interaction with IMS data channel.
10.2 Terminating Identification Presentation (TIP) p. 26
No interaction with IMS data channel.
10.3 Originating Identification Restriction (OIR) p. 26
No interaction with IMS data channel.
10.4 Terminating Identification Restriction (TIR) p. 26
No interaction with IMS data channel.
10.5 Message Waiting Indication (MWI) p. 26
No interaction with IMS data channel.
10.6 Conferencing (CONF) p. 27
10.6.1 Procedure at UE p. 27
When a user is participating in two or more SIP sessions, established SIP session's data channel media streams are specific to each SIP session. The user is handling multiple SIP sessions, but only one SIP session shall be active at a time.
The user (conference creator) creates SIP session with the conference focus by sending an INVITE request as described in clause 5.3.1.3 of TS 24.147, and a new SIP session is established between the user (conference creator) and the conference focus.
The user (conference creator) decides and perform the procedures as described in clause 5.3.1.4 of TS 24.147 for inviting a user (conference participant) to a conference by sending an REFER request for each of the active sessions that are requested to be joined to the three-way session, and new SIP sessions are established between the users (conference participants) and the conference focus.
At the establishment of the SIP session with the conference focus, the conference creator and conference participants, shall terminate the existing call session including data channel media streams as per TS 24.147, and clause 9.3.
If the user (conference creator or conference participant) wants to use IMS data channel in the SIP session established with the conference focus, the user shall follow procedure specified in clause 9.3.2.1.
10.6.2 Procedure at IMS AS serving the user p. 27
On reception of the SIP INVITE request in conjunction with IMS data channel setup as per clause 9.3.2.1.2 and request URI set to the conference factory URI in accordance with clause 5.3.1.3 of TS 24.147, the IMS AS serving the user shall follow procedure specified in clause 9.3.2.2.1.
10.7 Communication Diversion (CDIV) p. 27
10.7.1 Communication Forwarding Unconditional (CFU) p. 27
10.7.1.1 Actions at the AS of the diverting User p. 27
On reception of incoming session setup INVITE request in the IMS AS of the diverting user with the media feature tag +sip.app-subtype="webrtc-datachannel" as specified in TS 26.114 in the Contact header field and SDP offer containing the media descriptions for the MMTel media according TS 24.173 and a data channel media description for the bootstrap data channel in accordance with TS 26.114, if a CFU service condition is satisfied based on the diverting user subscription data, the IMS AS of the diverting user shall not send session event notification to the DCSF. The IMS AS of the diverting user shall route the incoming session setup INVITE request towards a diverted-to user as defined in TS 24.604.
There will be no media negotiation between the originating user and the diverting user, including data channel media negotiation. The data channel media session setup shall be performed between originating user and the diverted-to user together with audio, video media negotiation as per procedures defined in clause 9.3.
10.7.2 Communication Forwarding on Busy user (CFB) p. 28
10.7.2.1 Actions at the AS of the diverting User p. 28
On reception of incoming session setup INVITE request in the IMS AS of the diverting user with the media feature tag +sip.app-subtype="webrtc-datachannel" as specified in TS 26.114 in the Contact header field and SDP offer containing the media descriptions for the MMTel media according TS 24.173 and a data channel media description for the bootstrap data channel in accordance with TS 26.114, diverting user's network functions shall reserve the data channel media resources before routing the session setup request to the diverting user.
On reception of SIP response 486 (User Busy) from the diverting user, if CFB has been triggered as defined in TS 24.604, the diverting user's network functions shall release the reserved data channel media as per procedures defined in clause 9.3 and route the incoming session setup INVITE request towards a diverted-to user as defined in TS 24.604. The data channel media session setup shall be performed between originating user and the diverted-to user together with audio, video media negotiation as per procedures defined in clause 9.3.
In case of failure of data channel media resources reservations at serving network functions of diverting user, the IMS AS of diverting user shall proceed with setup of the MMTel session without performing data channel bootstrapping, by deleting data channel media description (m lines) from SDP offer of incoming INVITE request and route the updated INVITE request to the diverted-to user.
For the CFB under Network Determined User Busy as defined in TS 24.604, the CFB behaviour will be same with CFU as specified in clause 10.7.1.
10.7.3 Communication Deflection (CD) p. 28
10.7.3.1 Actions at the AS of the diverting User p. 28
The CD service can only be triggered before the 200 OK SIP response reception from the diverting user as defined in TS 24.604.
On reception of 302(Moved Temporarily) SIP response at IMS AS, the IMS AS:
- shall trigger the close of the established data channel media on early dialog of the MMTel session between the originating and the diverting user's network by interacting with the DCSF and the MF of the user-B as per procedures defined in clause 4.5.2.6.3 of TS 24.604 and in clause 9.3; and
- shall route the incoming session setup INVITE request towards a diverted-to user as defined in TS 24.604. The data channel media negotiation shall be performed between the originating user and the diverted-to user together with audio, video media negotiation as per procedures defined in clause 9.3.
10.7.4 Communication Forwarding on No Reply (CFNR) p. 28
10.7.4.1 Actions at the AS of the diverting User p. 28
The CFNR service no-reply timer at IMS AS shall be started at the reception of 180 (Ringing) SIP response reception. On no-reply timer expiry, the IMS AS:
- shall trigger the close of the established data channel media on early dialog of the MMTel session between the originating and the diverting user's network by interacting with the DCSF and the MF of the user-B as per procedures defined in clause 4.5.2.6.3 of TS 24.604 and in clause 9.3; and:
- shall route the incoming session setup INVITE request towards a diverted-to user as defined in TS 24.604. The data channel media negotiation shall be performed between originating user and the diverted-to user together with audio, video media negotiation as per procedures defined in clause 9.3.
10.7.5 Communication Forwarding on Not Reachable (CFNRc) p. 28
10.7.5.1 Actions at the AS of the diverting User p. 28
There's no data channel media session setup between the originating and the diverting user's network, hence the CFNRc behavior shall be same as CFU service in clause 10.7.1.
10.7.6 Communication Forwarding on Not Logged-in (CFNL) p. 29
10.7.6.1 Actions at the AS of the diverting User p. 29
When the AS of the diverting user receives an incoming session setup INVITE request for an unregistered served user with the media feature tag +sip.app-subtype="webrtc-datachannel" as specified in TS 26.114 in the Contact header field and SDP offer containing the media descriptions for the MMTel media according TS 24.173 and a data channel media description for the bootstrap data channel in accordance with TS 26.114, and a CFNL condition is determined at the IMS AS, there's no data channel media negotiation between the originating user and the diverting user, hence the CFNL service behavior shall be same as CFU service in clause 10.7.1.
In case of a late CFNL detection by the network (e.g., the terminating S-CSCF of a diverting user), the network shall send 480 (Temporarily Unavailable) response to the IMS AS, for the incoming INVITE request to the diverting user. On reception of a 480 (Temporarily Unavailable) response, the IMS AS of the diverting user shall trigger the release of reserved DC media resources and route the incoming INVITE request towards the diverted-to user. Hence for this use case, CFNL service behavior shall be same as CFB service in clause 10.7.2
10.8 Communication Waiting (CW) p. 29
10.8.1 Actions at AS of user B p. 29
If a network-based CW ("approaching NDUB") or terminal based CW condition is determined, after a CW service execution, the serving IMS AS will interact with the serving DCSF and the MF of the user B, to reserve the DC media resources for waiting communication, based on the served user B subscription data. The serving IMS AS shall forward or send the INVITE request to the user B, as per TS 24.615.
The user B may proceed with below actions when a communication waiting indication is to be given to the user B:
-
the user B may accept the waiting communication and holds the active communication or releases the active communication (per procedures in TS 24.615):
- on reception of a Re-INVITE request, which is meant for holding the active communication, the IMS AS interaction with DCSF and MF for DC media handling is not required; or
- on reception of a BYE request for the active communication, the serving IMS AS of the user B, will trigger the release of reserved DC Media resources of active communication by interacting with the serving DCSF and the MF of the user B. The serving IMS AS of the user B, shall follow the session release procedure as specified in TS 24.229.
-
the user B may reject the waiting communication:
- on reception of an unsuccessful response for waiting communication from the user B, the serving IMS AS of the user B will trigger the release the reserved DC Media resources of waiting communication by interacting with the DCSF and the MF of the user B and shall reject the communication by sending unsuccessful response to the user C.
10.8.2 Actions at UE of user B p. 29
If the user B accepts the waiting communication and holds the active communication (as per procedures in TS 24.615), the hold invoking UE of the user B shall perform the hold procedure.
10.9 Advice Of Charge (AOC) p. 29
The Advice Of Charge (AOC) service specified in TS 24.647 shall allow the served user to be informed of IP Multimedia session related charging information even if the session is accompanying with data channel media.
According to TS 32.260 and TS 32.255, duration-based charging and volume-based charging are used for IMS data channel, which does not introduce specific requirements on charging information element specified in Annex C of TS 24.647. So, AOC service has no interaction with IMS data channel.
10.10 Flexible Alerting (FA) p. 30
10.10.1 Actions at the AS serving the pilot identity p. 30
The flexible alerting telecommunication service with IMS data channel, procedures for the IMS AS serving user B identified by the FA pilot identity, shall be in accordance with TS 24.239 with the additions defined in the present document.
Upon reception of an incoming SIP INVITE request with DC media destined to the FA pilot identity of the user B, served by the IMS AS, the IMS AS:
- shall not trigger the IMS data channel resource reservation; and
- shall execute the FA procedures and route the incoming SIP INVITE request with DC media along with other MMTel media towards the FA group member identities, by sending the SIP INVITE request to S-CSCF in accordance with clause 4.5.5.2 of TS 24.239.
