Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 24.186  Word version:  19.0.0

Top   Top   Up   Prev   Next
1…   4…   9…   9.3…   9.3.3…   9.4…   10…   10.11…   A…   A.1.2…   A.1.2.2…   A.1.3…   A.1.3.2…   A.1.3.3…   B…   C…

 

A.1.3.3  IMS serving the transfer target provides data channel servicep. 50

A.1.3.3.1  Blind Transferp. 50
Copy of original 3GPP image for 3GPP TS 24.186, Fig. A.1.3.3.1-1: Blind Transfer when IMS serving the transfer target provides data channel service
Up
Figure A.1.3.3.1-1 shows a call flow for consultative transfer when IMS serving the transfer target provides data channel service.
Step 1.
UE-A calls UE-B, UE-A sends an INVITE request towards the UE-B.
Step 2.
UE-B answers the call, session connection is established between UE-A and UE-B.
Step 3.
UE-B starts transfer process. UE-B sends a REFER message to transfer the call to UE-C.
Step 4-5.
IMS-B sends 202/NOTIFY to UE-B to accept the transfer request, and then sends BYE message to UE-B.
Step 6.
IMS-B sends an INVITE message towards UE-C.
Step 7-9.
IMS-C forwards the INVITE message to UE-C. On reception of 18X/200 message with data channel media from UE-C, IMS-C allocates the data channel media resources on MF for UE-A and UE-C.
Step 10..
IMS-C sends the 18X/200 message to IMS-B.
Step 11-12.
IMS-B transfers the 18X/200 message to reINVITE message and sends it towards UE-A, UE-A responses 200 OK with data channel media answer to IMS-B.
Step 13-14.
IMS-B transfers the 200 OK message to PRACK/ACK message and sends it to IMS-C. IMS-C update data channel media on MF. Then IMS-C sends the PRACK/ACK message to UE-C.
Step 16.
The BDC media connections are established on MF of IMS-C for both UE-A and UE-C.
Step 17.
The ADC media connections are established between UE-A and UE-C.
Step 18.
The session connection is established between UE-A and UE-C.
Up
A.1.3.3.2  Consultation Transferp. 51
Copy of original 3GPP image for 3GPP TS 24.186, Fig. A.1.3.3.2-1: Consultative Transfer when IMS serving the transfer target provides data channel service
Up
Figure A.1.3.3.2-1 shows a call flow for consultative transfer when IMS serving the transfer target provides data channel service.
Step 1.
UE-A calls UE-B, UE-A sends an INVITE request towards the UE-B.
Step 2.
UE-B answers the call, session connection is established between UE-A and UE-B.
Step 3-9.
UE-B holds UE-A, and then calls UE-C, session connection is established between UE-B and UE-C. IMS-C establishes BDC connection for UE-B and UE-C. And then IMS-C establishes ADC connections between UE-B and UE-C.
Step 10.
UE-B starts transfer process. UE-B sends a REFER message to transfer the call to UE-C.
Step 11-12.
IMS-B sends 202/NOTIFY to UE-B to accept the transfer request, and then sends BYE message to UE-B.
Step 13-15.
IMS-B sends a re-INVITE request to establish the connection between UE-A and UE-C.
Step 16.
IMS-C updates the DC media connection for UE-A when receiving the updated data channel media from UE-A.
Step 17-19.
The media re-negotiation finished between UE-A and UE-C.
Step 20.
The BDC media connection is established on MF of IMS-C for UE-A.
Step 21.
The ADC media connections are established between UE-A and UE-C.
Step 22.
The session connection is established between UE-A and UE-C.
Up

Up   Top   ToC