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:  17.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.3.6 Conferencing  7.6.1.2.3.7 Communication Waiting  7.6.1.2.4 When use of Gm or I1 reference point is not possible due to VPLMN limitations  7.6.1.2.4.1 When attached to an MSC Server enhanced with ICS  7.6.1.2.4.2 When attached to an MSC Server not enhanced with ICS  7.6.1.3 User configuration of Supplementary Services 
...

 

7.6.1.2.3.6  Conferencing  p. 78
IMS procedures as defined in TS 24.173 apply The SCC AS combines the description of the CS bearer with the service control signalling communicated over the I1 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.3.6-1 describes how ICS UE executes the IMS conferencing when using I1 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.3.6-1: ICS UE executes the IMS Conferencing via I1
Figure 7.6.1.2.3.6-1: ICS UE executes the IMS Conferencing via I1
(⇒ copy of original 3GPP image)
Up
Step 1.
The ICS UE A initiates a session with the conference AS by sending a conference invitation message to SCC AS via I1 interface.
Step 2.
The SCC AS continues session establishment towards the conference AS and the conference connection is created as specified in clause 7.6.1.2.2.6, steps 3 to 7.
Step 3.
On receipt of an OK message from the Conference AS, the SCC AS sends an OK message to the ICS UE via the I1 interface.
Step 4.
The SCC AS sends a backward message to the MGCF to update the MGW port for connecting with the conference AS.
Step 5.
The ICS UE A initiates a message to the SCC AS via I1 interface indicating UE B transferring the current session to the conference AS.
Step 6.
UE B is referred to the conference AS as specified in clause 7.6.1.2.2.6.
Step 7.
On receipt of a Notify message from UE B indicating transfer complete, the SCC AS sends a transfer completed message to ICS UE A via I1 interface.
Step 8.
The session between the ICS UE A and UE B is released.
Step 9.
Steps 5-8 is repeated for UE C.
Up
7.6.1.2.3.7  Communication Waiting  p. 79
IMS procedures as defined in TS 24.173 apply The SCC AS combines the description of the CS bearer with the service control signalling communicated over the I1 reference point, as specified in clause 7.1.
7.6.1.2.4  When use of Gm or I1 reference point is not possible due to VPLMN limitations  p. 80
7.6.1.2.4.1  When attached to an MSC Server enhanced with ICS  p. 80
Procedures specified in clause 7.6.2 Service Consistency for non ICS UE apply.
7.6.1.2.4.2  When attached to an MSC Server not enhanced with ICS  p. 80
Procedures specified in clause 7.6.3 apply.

7.6.1.3  User configuration of Supplementary Services  p. 80

An ICS UE supporting multimedia telephony shall manage the IMS multimedia telephony communication service settings data as specified in TS 24.173. I1 does not support configuration of supplementary services.

Up   Top   ToC