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.4.0

Top   Top   Up   Prev   Next
1…   4…   9…   9.3…   9.3.2.2…   9.3.3…   9.3.3.2…   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… 
9.3.3 Terminating side  9.3.3.1 Procedures at the UE  9.3.3.1.1 General  9.3.3.1.2 IMS bootstrap data channel setup in conjunction with MMTel session setup  9.3.3.1.3 IMS data channel setup in conjunction with MMTel session modification  9.3.3.1.4 Closing IMS application data channel in conjunction with MMTel session modification  9.3.3.1.5 Closing IMS data channel in conjunction with MMTel session release  9.3.3.1.6 Support of IMS standalone data channel session  9.3.3.1.7 Enforcement of 3GPP SIP-Based 3GPP PS Data Off Exempt Services  9.3.3.1.8 Support of the data channel multiplexing 
...

 

9.3.3  Terminating side  p. 32

9.3.3.1  Procedures at the UE  p. 32

9.3.3.1.1  General  p. 32
The terminating UE can also setup or terminate data channels during the session modification.
9.3.3.1.2  IMS bootstrap data channel setup in conjunction with MMTel session setup  p. 33
If the terminating UE determines that the UE and the network supports the IMS data channel, on the reception of SIP initial INVITE request, the terminating UE shall include the media feature tags defined in RFC 5688 for supported streaming media type with +sip.app-subtype="webrtc-datachannel" as specified in TS 26.114 in the Contact header field of SIP 18x and 2xx responses to the SIP INVITE request.
If the terminating UE receives the initial INVITE request with an SDP offer which includes the data channel media descriptions, i.e. the "m=" line containing the media set to "application", the UDP port number, the proto value set to "UDP/DTLS/SCTP" and the fmt value set to "webrtc-datachannel" and with associated "dcmap" attribute lines containing a subprotocol parameter set to "http" and any "stream-id" parameter set to values 0, 10, 100 or 110, and the terminating UE:
  1. is not configured with IMS_DC_configuration node as specified in TS 24.275 and EFIMSDCI file specified in TS 31.103 or TS 31.102, and the terminating UE:
    1. accepts the offered bootstrap data channel(s), it shall generate the SDP answer based on the TS 26.114 and RFC 8864; or
    2. does not accept the offered bootstrap data channel(s), it shall set the port number(s) of the rejected data channel media stream(s) to zero in the generated SDP answer; or
  2. is configured with IMS_DC_configuration node as specified in TS 24.275 and the DC_allowed leaf indicates that IMS data channel:
    1. is allowed and if the terminating UE accepts the offered bootstrap data channel(s), it shall generate the SDP answer based on the TS 26.114 and RFC 8864; or
    2. is not allowed, it shall reject the offered bootstrap data channel media stream(s) by setting the port number of the rejected data channel media stream(s) to zero in the generated SDP answer,
  3. is configured with EFIMSDCI file specified in TS 31.103 or TS 31.102 and the IMS DC Establishment Indication indicates that IMS data channel:
    1. is allowed and if the terminating UE accepts the offered bootstrap data channel(s), it shall generate the SDP answer based on the TS 26.114 and RFC 8864; or
    2. is not allowed, it shall reject the offered bootstrap data channel media stream(s) by setting the port number of the rejected data channel media stream(s) to zero in the generated SDP answer,
and the terminating UE shall return a 18x or 2xx response to the INVITE request with the above generated the SDP answer.
Up
9.3.3.1.3  IMS data channel setup in conjunction with MMTel session modification  p. 33
9.3.3.1.3.1  IMS bootstrap data channel establishment  p. 33
If the terminating UE determines that the UE and the network supports the IMS data channel, when the UE receives the re-INVITE request with an SDP offer, which includes the bootstrap data channel media descriptions, i.e. the "m=" line containing the media set to "application", the UDP port number, the proto value set to "UDP/DTLS/SCTP" and the fmt value set to "webrtc-datachannel" and with associated "dcmap" attribute lines containing a subprotocol parameter set to "http" and any "stream-id" parameter set to values 0, 10, 100 or 110, the procedure defined in clause 9.3.3.1.2 applies.
If the terminating UE wants to setup a bootstrap data channel during the session modification by sending SIP re-INVITE request, the procedure defined in clause 9.3.2.1.3.1 applies.
Up
9.3.3.1.3.2  IMS application data channel establishment  p. 33
If the terminating UE has an established bootstrap data channel associated with the MMTel session available and if the UE receives the re-INVITE request with an SDP offer which includes data channel media descriptions for the bootstrap data channel, as well as the requested application data channel and the associated data channel application binding information (provided within the "a=3gpp-req-app" SDP attribute), and the terminating UE accepts the offered application data channel, it shall return a 183 (Session Progress) or 200 (OK) response to the re-INVITE request with the generated the SDP answer based on the TS 26.114 and RFC 8864.
If the terminating UE wants to setup an application data channel, the procedure defined in clause 9.3.2.1.3.2 applies.
Up
9.3.3.1.4  Closing IMS application data channel in conjunction with MMTel session modification  p. 34
If the terminating UE receives a re-INVITE request including an SDP offer in which the UDP port number of the data channel media description was set to zero or the "a=dcmap" line associated with an application data channel was removed from the data channel media description, and the terminating UE accepts the application data channel termination, it shall return a 200 (OK) response to the re-INVITE request with the generated SDP answer based on the RFC 8864.
If the terminating UE wants to close an established application data channel during the session modification by sending re-INVITE request, the procedure defined in clause 9.3.2.1.4 applies.
Up
9.3.3.1.5  Closing IMS data channel in conjunction with MMTel session release  p. 34
When the UE releases an MMTel session that has associated bootstrap and application data channels, the UE shall apply procedures defined in clause 5.1.5 of TS 24.229 and shall close bootstrap and application data channels.
9.3.3.1.6  Support of IMS standalone data channel session |R19|  p. 34
9.3.3.1.6.1  Void
9.3.3.1.6.2  Void
9.3.3.1.6.2A  Adding application data channel during standalone IMS data channel session establishment  p. 34
Upon receipt of the initial INVITE request with the SDP offer with only the media description for the bootstrap data channel and the UE accepts the the bootstrap data channel, the UE shall return a 183 (Session Progress) response to the initial INVITE request with the SDP answer generated as per TS 26.114 and RFC 8864.
Upon receipt of the UPDATE request with the updated SDP offer containing the established bootstrap data channel and a requested application data channel with the associated DC application binding information (provided within the "a=3gpp-req-app" SDP attribute) according to TS 26.114 to establish an application data channel, the UE shall determine whether the data channel application has been downloaded or not. If the data channel application:
  1. has not been downloaded, the UE shall not:
    1. download the application data channel application;
    2. alert the user and return the 180 (Ringing) once the data channel application is downloaded;
    3. generate the SDP answer that contains the media description for the application data channel as per TS 26.114 and RFC 8864 and return the 200(OK) response to the UPDATE request; and
    4. return 200 (OK) response to the INVITE request; or
  2. has been downloaded, the UE shall:
    1. alert the user and return the 180 (Ringing);
    2. generate the SDP answer that contains media descriptions for both the bootstrap data channel and application data channel as per TS 26.114 and RFC 8864 and return the 200(OK) response to the UPDATE request; and
    3. return 200 (OK) response to the INVITE request.
Up
9.3.3.1.6.3  Combined standalone bootstrap data channel and application data channel establishment  p. 35
Upon receipt of the initial INVITE request with the SDP offer with the media description for both the bootstrap data channel and the application data channel associated with the application binding information in "a=3gpp-req-app" line, the UE shall determine whether the data channel application has been downloaded or not. If the data channel application:
  1. has not been downloaded, the UE:
    1. shall generate SDP answer for the data channel as per TS 26.114 and RFC 8864 accepting the bootstrap data channel and rejecting the application data channel by setting the port number of m=line of application data channel to zero, indicate the data channel application is desired to be downloaded according to clause AC.10.2.3 of TS 23.228 and return a 183 (Session Progress) response with the generated SDP answer to the initial INVITE request;
    2. download the application data channel application;
    3. upon receipt of the UPDATE request with the updated SDP offer to establish the corresponding application data channel,
      • alert the user and return the 180 (Ringing) once the data channel application is downloaded;
      • generate the SDP answer as per TS 26.114 and RFC 8864 and return the 200(OK) response to the UPDATE request;
      • return 200 (OK) to the INVITE request; or
  2. has been downloaded, the UE shall:
    1. generate the SDP answer that contains both the bootstrap data channel and application data channel as per TS 26.114 and RFC 8864 and retrun the 183 (Session Process) response to the network;
    2. alert the user and return the 180 (Ring) response; and
    3. return the 200(OK) response to the INVITE request.
Up
9.3.3.1.6.4  Adding video/audio media to standalone IMS data channel session  p. 35
Upon receipt of the re-INVITE request with an updated SDP offer in which the audio/video media description is added within the IMS standalone data channel session, the UE shall return a 183 (Session Progress) or 200 (OK) response to the re-INVITE request with the generated the SDP answer based on the TS 26.114.
9.3.3.1.6.5  Removing video/audio media from IMS data channel session  p. 35
Upon receipt of the re-INVITE request with an updated SDP offer in which the port number of audio/video media description is set to zero, the UE shall return a 183 (Session Progress) or 200 (OK) response to the re-INVITE request with the generated the SDP answer based on the TS 26.114.
9.3.3.1.7  Enforcement of 3GPP SIP-Based 3GPP PS Data Off Exempt Services |R19|  p. 35
When 3GPP PS data off is supported and 3GPP PS data off status is changed to "active", if "Services over IMS Data Channel" is not in the list of 3GPP PS data off exempt services:
  1. if the UE received an initial INVITE request with IMS data channel media description(s) in the SDP offer and did not yet send a final response to the initial INVITE request:
  2. if the initial SDP offer contained only IMS data channel media description(s), the UE shall send a 403 (Forbidden) response; or
  3. if the initial SDP offer also contained other media description(s):
    • if the UE did not yet send the SDP answer, the UE shall reject the offered IMS data channel media description(s) by setting the UDP port number of the rejected data channel media description(s) to zero in created SDP answer and shall send a SIP response to the initial INVITE request with the generated SDP answer; or
    • if the UE already sent the SDP answer with the accepted IMS data channel media descriptions and there is no ongoing SDP offer/answer exchange, the UE shall create a new SDP offer in which the UDP port number of each accepted IMS data channel media description is set to zero and send the SDP offer within UPDATE request; and
  4. otherwise, the procedure defined in clause 9.3.2.1.7 applies.
Up
9.3.3.1.8  Support of the data channel multiplexing |R19|  p. 36
Upon receiving an initial INVITE, a re-INVITE or a UPDATE request with an SDP offer, which contains the multiplexed data channel media description(s), the UE shall:
  1. follow the procedures of clause 9.3.3.1.2, clause 9.3.3.1.3, clause 9.3.3.1.4, and clause 9.3.3.1.6.3 to generate a response to the initial INVITE, re-INVITE or UPDATE request;
  2. include the "g.3gpp.dc-mux" media feature tag defined in TS 26.114 in the Contact header field;
  3. if the UE determines both the UE and its home IMS network support IMS data channel multiplexing capability and accepts the requested IMS data channels in the single m line in the SDP offer, generate an SDP answer based on the TS 26.114 and RFC 8864;
  4. if the UE determines both the UE and its home IMS network support IMS data channel multiplexing capability but accepts neither of the offered IMS data channels, or if the UE does not support IMS data channel multiplexing capability, set the port number(s) of the multiplexed data channel media description(s) to zero; and
  5. if the UE determines both the UE and its home IMS network support IMS data channel multiplexing capability and accepts the requested IMS data channels termination in the single m line in the SDP offer, generate an SDP answer based on the TS 26.114 and RFC 8864.
If the terminating UE wants to close an established multiplexed application data channel during the session modification by sending re-INVITE request with the subsequent SDP offer, the procedure defined in clause 9.3.2.1.4 applies.
If the UE wants to multiplex IMS data channels during IMS data channel establishment by sending SIP re-INVITE request, the procedure defined in clause 9.3.2.1.8 applies.
Up

Up   Top   ToC