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 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.2.2 Terminal based CW flows  A.1.2.2.1 Successful communication establishment  A.1.2.2.2 AS CW Timer expires  A.1.2.2.3 UE CW timer expires 
...

 

A.1.2.2  Terminal based CW flows  p. 39

A.1.2.2.1  Successful communication establishment  p. 39
Figure A.1.2.2.1-1 shows an example of terminal-based communication waiting signalling flow at the terminating side and successful communication establishment. Waiting communication request contains DC media session along with other MMTel media sessions.
Copy of original 3GPP image for 3GPP TS 24.186, Fig. A.1.2.2.1-1: Terminal based CW: Successful communication establishment
Figure A.1.2.2.1-1: Terminal based CW: Successful communication establishment
(⇒ copy of original 3GPP image)
Up
The description of the steps mentioned in the Figure A.1.2.2.1-1 is in accordance with the TS 24.615 with the additions defined in the present document:
  1. in step 1) initial INVITE request with data channel media is received for the user B(UA-B) in accordance with clause A.1.1.1 step 1);
  2. in step 2) the IMS AS serving the user B(UA-B) receives SIP INVITE request with data channel media;
  3. in step 2a) to step 2c) the IMS AS of user B(UA-B) determines and executes terminal-based CW procedures. Depending on the user B IMS data channel subscription, the IMS AS of the user B(UA-B) triggers the reservation of resources for data channel setup for waiting communication in accordance with clause 9.3.3.2.1 and clause AC.7.1 of TS 23.228;
  4. in step 3) the IMS AS of the user B(UA-B) sends SIP INVITE request with data channel media for waiting communication, towards the user B(UA-B);
  5. in step 8a), step 13a) on reception of 18x responses with call waiting indication from user B(UA-B) for waiting communication, the IMS AS of the user B(UA-B) sends session progress event notification to the DCSF serving the user B(UA-B);
  6. in step 18) the IMS AS of the user B(UA-B) receives 200 OK response with data channel media from user B(UA-B) for the waiting communication; and
  7. in step 18b) the IMS AS of the user B(UA-B) sends successful session establishment event notification for waiting communication, to the DCSF serving the user B(UA-B).
Up
A.1.2.2.2  AS CW Timer expires  p. 41
Figure A.1.2.2.2-1 shows an example of terminal-based communication waiting signalling flow at the terminating side and CW timer expires at IMS AS. Waiting communication request contains DC media session along with other MMTel media sessions.
Copy of original 3GPP image for 3GPP TS 24.186, Fig. A.1.2.2.2-1: Terminal based CW: CW timer expires at AS
Figure A.1.2.2.2-1: Terminal based CW: CW timer expires at AS
(⇒ copy of original 3GPP image)
Up
The description of the steps mentioned in the Figure A.1.2.2.2-1 is in accordance with the TS 24.615 with the additions defined in the present document:
  1. in step 1) initial INVITE request with data channel media is received for the user B(UA-B) in accordance with clause A.1.1.1 step 1);
  2. in step 2) the IMS AS serving the user B(UA-B) receives SIP INVITE request with data channel media;
  3. in step 2a) to step 2c) the IMS AS of user B(UA-B) determines and executes terminal-based CW procedures. Depending on the user B(UA-B) IMS data channel subscription, the IMS AS of the user B(UA-B) triggers the reservation of resources for data channel setup for waiting communication in accordance with clause 9.3.3.2.1 and clause AC.7.1 of TS 23.228;
  4. in step 3) the IMS AS of the user B(UA-B) sends SIP INVITE request with data channel media for waiting communication, towards the user B(UA-B);
  5. in step 8a), 13a) on reception of 18x responses with call waiting indication from user B(UA-B) for waiting communication, the IMS AS of the user B(UA-B) sends session progress event notification to the DCSF serving the user B(UA-B); and
  6. in step 14c) to step 14d) upon CW timer expiry for waiting communication, the IMS AS of the user B(UA-B) notifies session failure event to the DCSF of the user B(UA-B) and as per media instruction request from the DCSF, the IMS AS sends media resource management request to the MF to release the allocated data channel media resources for this waiting communication SIP session. The IMS AS notifies the DCSF about the DC media release as part of the media instruction response.
Up
A.1.2.2.3  UE CW timer expires  p. 43
Figure A.1.2.2.3-1 shows an example of terminal-based communication waiting signalling flow at the terminating side and CW timer expires at UE-B. Waiting communication request contains DC media session along with other MMTel media sessions.
Copy of original 3GPP image for 3GPP TS 24.186, Fig. A.1.2.2.3-1: Terminal based CW: CW timer expires at UE-B
Figure A.1.2.2.3-1: Terminal based CW: CW timer expires at UE-B
(⇒ copy of original 3GPP image)
Up
The description of the steps mentioned in the Figure A.1.2.2.3-1 is in accordance with the TS 24.615 with the additions defined in the present document:
  1. in step 1) initial INVITE request with data channel media is received for the user B(UA-B) in accordance with clause A.1.1.1 step 1);
  2. in step 2) the IMS AS serving the user B(UA-B) receives SIP INVITE request with data channel media;
  3. in step 2a) to step 2c) the IMS AS of user B(UA-B) determines and executes terminal-based CW procedures. Depending on the user B(UA-B) IMS data channel subscription, the IMS AS of the user B(UA-B) triggers the reservation of resources for data channel setup for waiting communication in accordance with clause 9.3.3.2.1 and clause AC.7.1 of TS 23.228;
  4. in step 8a, step 13a) on reception of 18x responses with call waiting indication from user B(UA-B) for waiting communication, the IMS AS of the user B(UA-B) sends session progress event notification to the DCSF serving the user B(UA-B); and
  5. in step 18a) to step 18b) upon reception of 480 (Temporarily Unavailable) SIP response for waiting communication, the IMS AS of the user B(UA-B) notifies session failure event to the DCSF of the user B(UA-B) and as per media instruction request from the DCSF, the IMS AS sends media resource management request to the MF to release the allocated data channel media resources for this waiting communication SIP session. The IMS AS notifies the DCSF about the DC media release as part of the media instruction response.
Up

Up   Top   ToC