Content for TS 23.237 Word version: 18.0.0

0… 4… 5… 5.4… 6… 6.2… 6.2.2… 6.3… 6.3.2… 6.3.2.1.3… 6.3.2.1.7… 6.3.2.1.9… 6.3.2.2… 6.3.2.3… 6.3.2.3.6… 6.3.3… 6.4… 6a… 6a.3… 6a.4… 6a.4.3… 6a.4.5… 6a.4.7… 6a.4a… 6a.5… 6a.6… 6a.7… 6a.8… 6a.9… 6a.10… 6a.11… 6c… 7… A… B… C…

6.2.2 Termination 6.2.2.1 Termination Procedures 6.2.2.2 Terminating sessions that use CS media 6.2.2.3 Terminating sessions that use only PS media flow(s) 6.2.2.3a Terminating sessions that use only PS media flow(s) - fallback to CS domain in pre-alerting phase 6.2.2.4 Terminating sessions over Gm where speech media is not accepted by the UE 6.2.2.5 Terminating sessions for (v)SRVCC that use ATCF enhancements 6.2.2.6 Terminating sessions for CS to PS - Single Radio
...

6.2.2 Termination p. 40

6.2.2.1 Termination Procedures p. 40

IMS multimedia sessions towards SC subscribers in the PS or in the CS domain are anchored at the SCC AS to enable IMS Service Continuity. The execution of terminating iFC results in routing of the sessions to the SCC AS in the home IMS network, where the SCC AS uses 3rd party call control as per TS 23.228 to terminate the session to the SC subscriber. The sessions may be delivered to the UE via the PS or CS access.

The SCC AS shall be the last Application Server of any Application Servers that need to remain in the path of the call after Session Termination.

6.2.2.2 Terminating sessions that use CS media p. 40

The procedures specified in clause 7.4.2 of TS 23.292 Terminating sessions that use CS media shall be followed to terminate sessions that use CS media to the SC subscriber.

Reproduction of 3GPP TS 23.237, Fig. 6.2.2.2-1: Terminating session that uses CS media

Figure 6.2.2.2-1: Terminating session that uses CS media

Step 1.

A request is received at S-CSCF serving UE-1 following standard IMS session set up procedures.

Step 2 ~ 3.

The service logic with iFC causes the request to be forwarded to the SCC AS so that the session is anchored for enabling Session Transfer.

Step 4.

The SCC AS anchors the incoming session. A dynamic STI is assigned for the anchored session.

Step 5.

The SCC AS forwards the request to UE-1 based on the procedures specified in TS 23.292 for setting up CS bearer and splitting the media flow(s) if necessary. The dynamic STI is communicated between the SCC AS and the UE if possible. If the SCC AS decided to split the non-speech media and speech media for a certain UE, the T-ADS in the SCC AS delivers the split session only to this particular UE. The SCC AS uses the C-MSISDN for correlation.

The session is set up with CS media. The session may also include PS media flow(s).

6.2.2.3 Terminating sessions that use only PS media flow(s) p. 41

Existing Mobile Termination procedures described in TS 23.228 are used to establish a session towards a SC subscriber.

Reproduction of 3GPP TS 23.237, Fig. 6.2.2.3-1: Terminating session that uses only PS media

Figure 6.2.2.3-1: Terminating session that uses only PS media

Step 1.

The request is received at S-CSCF following normal IMS session set up procedures.

Step 2 ~ 3.

The service logic with iFC causes the request to be forwarded to the SCC AS so that the session can be anchored for potential session transfer.

Step 4.

The SCC AS anchors the session. An STI is assigned for the anchored session.

Step 5.

The SCC AS determines that the session is terminated to UE-1 with PS media flow(s) only and routes the request to UE-1. For Dual Radio scenario, the SCC AS may provide an update STN to the UE as part of the INVITE sent to the UE.

6.2.2.3a Terminating sessions that use only PS media flow(s) - fallback to CS domain in pre-alerting phase |R14| p. 42

The procedure is to be used if SRVCC in alerting phase for terminating sessions is not supported.

Reproduction of 3GPP TS 23.237, Fig. 6.2.2.3a-1: Terminating session that uses only PS media - fallback to 2/3G in pre-alerting phase

Figure 6.2.2.3a-1: Terminating session that uses only PS media - fallback to 2/3G in pre-alerting phase

Step 1~ 5.

The request is received from UE-2 following normal IMS session set up procedures and UE-1 sends a 183 response.

Step 6.

The multimedia PS bearer setup fails.

Step 7~8.

The P-CSCF sends a response to S-CSCF indicating the failure of the delivery of the terminating call on the PS domain.

Step 9~13.

The S-CSCF forwards the response to SCC AS that attempts to deliver the terminating call on the CS domain if possible, according to clause 7.4.3 in TS 23.292 (steps 8 through 12).

6.2.2.4 Terminating sessions over Gm where speech media is not accepted by the UE p. 43

If the SCC AS includes only bi-directional speech media, the procedures specified in clause 7.4.3 of TS 23.292 shall be followed.

If the SCC AS includes non-speech media in the request, in addition to bi-directional speech or CS media and if the UE decides to only accept the non-speech media, the UE returns a response to IMS that only bi-directional speech or CS media is rejected. The SCC AS, upon reception of the response, splits the non speech media from the bi-directional speech or CS media for this UE. The T-ADS in the SCC AS re-attempts the terminating call setup directly towards the same UE over CS domain if possible. The SCC AS uses the C-MSISDN for correlation.

6.2.2.5 Terminating sessions for (v)SRVCC that use ATCF enhancements |R10| p. 44

Figure 6.2.2.5-1 shows a terminating session when the ATCF has previously been included in the signalling path (see clause 6.1.2). If the ATCF was not included in the signalling path then existing Mobile Termination procedures described in previous clauses and TS 23.228 are used.

Reproduction of 3GPP TS 23.237, Fig. 6.2.2.5-1: Terminating session that uses only PS media (ATCF in signalling path)

Figure 6.2.2.5-1: Terminating session that uses only PS media (ATCF in signalling path)

Step 1-2.

A Terminating session is sent towards UE-1 from UE-2. The initial SIP INVITE request is routed via the I/S-CSCF to the SCC AS.

Step 3.

The SCC AS performs necessary T-ADS procedures according to clause 5.3.1, and routes the request towards the UE-1.

Step 4.

The INVITE is routed towards the ATCF. When receiving the INVITE, the ATCF may decide whether to anchor the media for the session and allocate ATGW resources for it if needed.

Step 5.

The SIP INVITE is forwarded to UE-1 (P-CSCF not shown in flow).

Step 6.

Session setup is completed. As part of this step, if not already done, the ATCF may decide, based on information not available earlier in the procedure, to anchor the session and allocate ATGW resources for voice media or voice and video media and anchor the voice media or voice and video media in the ATGW. The ATCF will in such case update the remote end with the media information of the ATGW in another offer/answer exchange (this may be done as part of other required session update).

6.2.2.6 Terminating sessions for CS to PS - Single Radio |R11| p. 44

The CS termination is done according to clause 7.4 of TS 23.292, with the addition that the call is routed through the ATCF.

Once the session is established, the ATCF will act as the access transfer function in the call.

Reproduction of 3GPP TS 23.237, Fig. 6.2.2.6-1: Terminating call setup over CS through ATCF

Figure 6.2.2.6-1: Terminating call setup over CS through ATCF

Step 1-2.

UE-2 sends an INVITE towards UE-1. The call is routed towards MSC Server using procedure according to clause 7.4 of TS 23.292.

Step 3.

The MSC Server routes the INVITE via ATCF using the ATCF management URI that it has received from SCC AS (see clause 6.1.3.2). The INVITE shall include the C-MSISDN to the ATCF for further correlation purposes.

Step 4.

The ATCF may decide whether to anchor the media session and allocate if needed ATGW resources to it. Media anchoring criteria used for ATCF enhancements apply.

Step 5-6.

The call setup proceeds and is routed toward UE-1.

Step 7.

The call setup is completed.