Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.292  Word version:  18.0.0

Top   Top   Up   Prev   Next
1…   4…   5…   7…   7.2…   7.3…   7.3.2.2…   7.3.2.2.4…   7.4…   7.4.2.2…   7.4.2.2.3…   7.4.2.2.7…   7.5…   7.6…   7.6.1.2.2.6…   7.6.1.2.3…   7.6.1.2.3.5…   7.6.1.2.3.6…   7.6.2…   7.6.2.7   7.6.2.8…   7.6.2.11…   7.6.3…   7.7…   7.7.2…   7.9…   7.9.2…   7.9.2.4   7.9.2.5   8…   A…   G…   H…   H.5…   H.5.3… 
7.6.1.2.2.6 Conferencing  7.6.1.2.2.7 Communication Waiting  7.6.1.2.2.8 Customized Alerting Tone (CAT) 
...

 

7.6.1.2.2.6  Conferencing  p. 67
IMS procedures as defined in TS 24.173 apply with the SCC AS combining the description of the CS bearer with the service control signalling communicated over the Gm reference point as specified in clause 7.1.
Additionally, the SCC AS may employ an MRF for control of media as needed for execution of the Conferencing.
Figure 7.6.1.2.2.6-1 describes how ICS UE executes the IMS conferencing when using Gm interface. The ICS UE A has a held call with UE B and a held call with UE C before it initiates a conference.
Copy of original 3GPP image for 3GPP TS 23.292, Fig. 7.6.1.2.2.6-1: ICS UE executes the IMS Conferencing via Gm
Figure 7.6.1.2.2.6-1: ICS UE executes the IMS Conferencing via Gm
(⇒ copy of original 3GPP image)
Up
Step 1.
The ICS UE A initiates a session with the conference AS by sending an INVITE to S-CSCF.
Step 2.
The S-CSCF sends the INVITE to the SCC AS as it was inserted at session establishment.
Step 3.
The SCC AS sends the INVITE to the S-CSCF.
Step 4.
The INVITE is sent to the conference AS.
Step 5.
A conference connection is created as specified in TS 24.173.
Step 6.-9.
Conference AS sends an OK response containing the conference URI to the ICS UE A via S-CSCF and SCC AS.
Step 10.
SCC AS sends a backward message to MGCF to update the MGW port for connecting with the conference AS.
Step 11.
The ICS UE A initiates a REFER message indicating UE B transferring the current session to the conference AS using Gm interface as specified in TS 24.173.
Step 12.
The S-CSCF sends the REFER to the SCC AS as it was inserted at session establishment.
Step 13.
The SCC AS sends the REFER to the S-CSCF.
Step 14.
The S-CSCF sends the REFER to UE B.
Step 15.
A session is established between the conference AS and UE B as specified in TS 24.173.
Step 16.-19.
UE B sends a NOTIFY indicating the transfer completed back to ICS UE A via S-CSCF and SCC AS.
Step 20.
The media between the ICS UE A and UE B is released.
Step 21.
Step 11-20 are repeated for UE C.
Up
7.6.1.2.2.7  Communication Waiting  p. 69
Figure 7.6.1.2.2.7-1 provides the ICS communication waiting flow over Gm reference point for the ICS UE.
Copy of original 3GPP image for 3GPP TS 23.292, Fig. 7.6.1.2.2.7-1: ICS UE Communication Waiting over Gm Reference Point
Figure 7.6.1.2.2.7-1: ICS UE Communication Waiting over Gm Reference Point
(⇒ copy of original 3GPP image)
Up
Step 1.
An incoming INVITE message is received at the S-CSCF of the ICS UE A.
Step 2.
The S-CSCF executes terminating initial filter criteria and forwards the INVITE message to the SCC AS.
Step 3.
The SCC AS performs terminating access domain selection and chooses the CS access network for the setup of the media.
Step 4.
The SCC AS sends the INVITE message to the S-CSCF.
Step 5.
The S-CSCF sends the INVITE message to UE A.
Step 6.
The ICS UE A sends to the S-CSCF an indication that the call is waiting.
Step 7.
The S-CSCF sends the indication of call waiting to the SCC AS.
Step 8.
The SCC AS sends the indication of call waiting to the S-CSCF.
Step 9.
The S-CSCF forwards the indication of call waiting to UE C.
Step 10.
The ICS UE A sends a Hold message to the S-CSCF as specified in TS 23.228.
Step 11.
The session between UE A and UE B is put on hold as described in clause 7.6.1.2.2.2 Communication Hold/Resume.
Step 12.
Completion of the session establishment between UE A and UE C. The existing CS bearer can be reused.
Up
7.6.1.2.2.8  Customized Alerting Tone (CAT)  p. 70
IMS procedures as defined in TS 24.182 apply with the SCC AS combining the description of the CS bearer with the service control signalling communicated over the Gm reference point as specified in clause 7.1.
The CS bearer is used for the media of the customized alerting tone, as well as the media of the regular session. And the CS bearer shall be reused if already established using the Gm reference point as specified in clause 7.3.2.2.1.
If the ICS UE originates an ICS session reusing the existing CS bearer as specified in clause 7.3.2.2.1, the SCC AS shall send the early session media info to the MSC Server/MGCF in the form of regular session media info (i.e. a SDP without early media indication). Then the SCC AS sends the regular session media info of the remote party to the MSC Server/MGCF for the session communication when receiving the 200 OK (acceptance of the session) from the remote party, if the early session or forking model is used for the CAT service.
Up

Up   Top   ToC