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 MMTel session procedures  9.3.1 General  9.3.2 Originating side  9.3.2.1 Procedures at the UE  9.3.2.1.1 General  9.3.2.1.2 IMS bootstrap data channel setup in conjunction with MMTel session setup  9.3.2.1.3 IMS data channel setup in conjunction with MMTel session modification  9.3.2.1.4 Closing IMS application data channel in conjunction with MMTel session modification  9.3.2.1.5 Closing IMS data channel in conjunction with MMTel session release  9.3.2.1.6 Support of standalone data channel  9.3.2.1.7 Enforcement of 3GPP SIP-Based 3GPP PS Data Off Exempt Services  9.3.2.1.8 Support of data channel multiplexing 
...

 

9.3  MMTel session procedures  p. 16

9.3.1  General  p. 16

The support of the IMS data channel is optional.
The session control procedures for IMS multimedia telephony communication service with IMS data channel shall be in accordance with TS 24.173 with the additions defined in the present document.

9.3.2  Originating side  p. 16

9.3.2.1  Procedures at the UE  p. 16

9.3.2.1.1  General  p. 16
The UE shall only initiate an MMTel session with an IMS data channel if the UE has determined that the UE and the home network supports the IMS data channel capability.
The policy related to the UE supporting the IMS data channel can be provided by the home network to the UE using e.g. OMA-DM with the management objects specified in TS 24.275 or UICC configuration, as specified in clause 9.2.1.1. When the UE is configured by home network with configuration for IMS data channel, then the UE may setup the IMS data channel.
If the UE is configured with IMS_DC_configuration node specified in TS 24.275 and:
  1. if DC_allowed leaf indicates that IMS data channel is not allowed, the UE shall not include data channel capability indication and data channel related media description in SDP offer; or
  2. if DC_allowed leaf indicates that IMS data channel is allowed, and:
    1. if DC_Setup_Option leaf is configured and indicates the IMS data channel is allowed to be setup simultaneously while establishing an MMTel session, the UE:
      • shall include the bootstrap data channel related media description in SDP offer within the initial INVITE request as described in clause 9.3.2.1.2 to setup the bootstrap data channel;
    2. if DC_Setup_Option leaf is configured and indicates the IMS data channel is not allowed to be setup simultaneously while establishing an MMTel session, the UE shall generate a re-INVITE request for the bootstrap data channel setup and include the bootstrap data channel related media description in SDP offer as described in clause 9.3.2.1.3.1 to setup the bootstrap data channel; and
    3. if the UE receives an initial INVITE or a re-INVITE request including the bootstrap data channel related media description in SDP offer, the UE shall generate an SDP answer as described in clauses 9.3.3.1.2 and 9.3.3.1.3.1.
If the UE is configured with EFIMSDCI file specified in TS 31.103 or TS 31.102 and:
  1. if IMS DC Establishment Indication indicates that IMS data channel is not allowed, the UE shall not include data channel capability indication and data channel related media description in SDP offer;
  2. if IMS DC Establishment Indication indicates that IMS data channel is allowed and allowed to be setup simultaneously while establishing an MMTel session, the UE shall include the bootstrap data channel related media description in SDP offer within the initial INVITE request as described in clause 9.3.2.1.2 to setup the bootstrap data channel;
  3. if IMS DC Establishment Indication indicates that IMS data channel is allowed but not allowed to be setup simultaneously while establishing an MMTel session, the UE shall generate a re-INVITE request for the bootstrap data channel setup and include the bootstrap data channel related media description in SDP offer as described in clause 9.3.2.1.3.1 to setup IMS data channel; and
  4. if IMS DC Establishment Indication indicates that IMS data channel is allowed, if the UE receives an initial INVITE or a re-INVITE request including the bootstrap data channel related media description in SDP offer, the UE shall generate an SDP answer as described in clauses 9.3.3.1.2 and 9.3.3.1.3.1.
Up
9.3.2.1.2  IMS bootstrap data channel setup in conjunction with MMTel session setup  p. 17
If the UE initiates an MMTel session with IMS data channels, the UE:
  1. shall generate an initial INVITE request in accordance with TS 24.229 and TS 24.173;
  2. shall include the media feature tag 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;
  3. may include an Accept-Contact header field containing the "sip.app-subtype" media feature tag defined in RFC 5688 with a value of "webrtc-datachannel" as specified in TS 26.114; and
  4. if the configuration described in clause 9.3.2.1.1, allows the establishment of bootstrap data channels simultaneously with the setup of the MMTel session, shall include an SDP offer containing the media descriptions for the MMTel media according TS 24.173 and data channel media descriptions for both the local and remote bootstrap data channels in accordance with TS 26.114.
Upon receiving of the UPDATE request with the SDP offer to establish a bootstrap data channel, the procedure defined in clause 9.3.3.1.3.1 applies and the originating UE shall return a SIP response to the UPDATE request with the generated SDP answer.
Up
9.3.2.1.3  IMS data channel setup in conjunction with MMTel session modification  p. 17
9.3.2.1.3.1  IMS bootstrap data channel establishment  p. 17
If the UE wants to establish a bootstrap data channel, the UE shall take into account the data channel configuration as specified in clause 9.3.2.1.1, and if the UE determines that the configuration allows the establishment of IMS data channels after the establishment of the MMTel session, the UE shall:
  1. generate a re-INVITE request in accordance with TS 24.229 and TS 24.173;
  2. include the media feature tag 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; and
  3. include an updated SDP offer that contains data channel media descriptions for both the local and remote bootstrap data channels according to TS 26.114.
Upon receiving a re-INVITE request to establish a bootstrap data channel, the procedure defined in clause 9.3.3.1.3.1 applies.
Up
9.3.2.1.3.2  IMS application data channel establishment  p. 18
If a UE wants to establish an application data channel within an existing MMTel session and if the UE has an established bootstrap data channel associated with the MMTel session available, the UE:
  1. shall generate a re-INVITE request in accordance with TS 24.229 and TS 24.173;
  2. shall include the media feature tag 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; and
  3. shall include an updated SDP offer that contains the data channel media descriptions for the bootstrap data channels, as well as the requested application data channel and the associated DC application binding information (provided within the "a=3gpp-req-app" SDP attribute), according to TS 26.114.
If the 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, the procedure defined in clause 9.3.3.1.3.2 applies.
Up
9.3.2.1.4  Closing IMS application data channel in conjunction with MMTel session modification  p. 18
If the UE wants to close an established application data channel during the session modification by sending re-INVITE request with the subsequent SDP offer, the UE shall remove the "a=dcmap" attribute line associated with the closed application data channel and, if the associated "a=3gpp-req-app" attribute references only the closed application data channel, the "a=3gpp-req-app" attribute line from the data channel media description as defined in Section 6.6.1 of RFC 8864 or set the UDP port number of the data channel media description to zero if no other "a=dcmap" attribute line associated with an application data channel existed in this data channel media description.
If the UE receives a re-INVITE request with 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 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.
The UE shall not close the bootstrap data channel during MMTel session modification procedure.
Up
9.3.2.1.5  Closing IMS data channel in conjunction with MMTel session release  p. 18
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.2.1.6  Support of standalone data channel |R19|  p. 18
9.3.2.1.6.1  General  p. 18
The procedures of standalone data channel include:
  1. establish an IMS session to a PSI or a target UE with only bootstrap data channel;
  2. establish an IMS data session with combined bootstrap data channel and application data channel;
  3. modify an IMS session to add audio/video media to the IMS session that only contains data channel media; and
  4. modify an IMS session to remove audio/video media in the IMS session that includes IMS data channel and audio/video media.
If the UE is configured with IMS_DC_configuration node specified in TS 24.275 and DC_allowed leaf indicates that IMS data channel is not allowed, the UE shall not establish an standalone IMS data channel session.
If the UE is configured with EFIMSDCI file specified in TS 31.103 or TS 31.102 and IMS DC Establishment Indication indicates that IMS data channel is not allowed, the UE shall not establish an standalone IMS data channel session.
Up
9.3.2.1.6.2  Standalone bootstrap data channel establishment  p. 18
If the UE wants to initiate a call to a Public Service Identifier (PSI) with only bootstrap data channel, the UE shall:
  1. populate the Request-URI header field with a specific "request-uri" indicating standalone data channel pre-configured in the UE;
  2. include data channel media description only for the local bootstrap data channel in the SDP offer; and
  3. follow the procedure of clause 9.3.2.1.2 to generate an initial INVITE request.
Up
9.3.2.1.6.3  Void
9.3.2.1.6.3A  Adding application data channel during standalone IMS data channel session establishment  p. 18
This procedure applies when the user selected data channel application is not available on the originating UE.
If the UE determines to initiate a standalone data channel session towards the terminating UE with only bootstrap data channels, it shall generate an initial INVITE request as per clause 9.3.2.1.2, but without the audio and video media in the SDP offer.
Upon receipt of the 183 (Session Progress) response to the initial INVITE request which indicates the bootstrap data channel has been established and the data channel application is downloaded through the established bootstrap data channel, the UE shall generate a SIP UPDATE request with the updated SDP offer containing the established bootstrap data channel, as well as the requested application data channel and the associated DC application binding information (provided within the "a=3gpp-req-app" SDP attribute) according to TS 26.114.
Up
9.3.2.1.6.4  Combined standalone bootstrap data channel and application data channel establishment  p. 18
This procedure applies when the user selected data channel application already exists on the UE.
This procedure applies when the user selected data channel application is available on the originating UE.
If the UE determines to initiate a standalone data channel session towards the terminating UE with both bootstrap data channel and application data channel, it shall generate an initial INVITE request with the SDP offer which includes both the bootstrap data channel media description and application data channel media description.
Upon receipt of the 183 (Session Progress) response to the initial INVITE request in which the bootstrap data channel is accepted but the application data channel is rejected, i.e. the port number of the application data channel media description is set to zero, the UE shall determine that the terminating UE has not downloaded the data channel application according to clause AC.10.2.3 of TS 23.228 and consequently shall generate a SIP UPDATE request with the updated SDP offer containing the established bootstrap data channel, as well as the requested application data channel and the associated DC application binding information (provided within the "a=3gpp-req-app" SDP attribute) according to TS 26.114.
Up
9.3.2.1.6.5  Adding video/audio media to IMS session with standalone data channel  p. 19
If the UE wants to add audio/video media to the IMS session with standalone data channel toward the peer UE, it shall generate a re-INVITE request with the SDP offer which includes the media descriptions for established application data channel, bootstrap data channel and audio/video.
9.3.2.1.6.6  Removing video/audio media from IMS data channel session  p. 19
If the UE is authorized to use standalone data channel, and it wants to remove the audio/video media from the IMS session including both audio/video and data channel media, the UE shall generate a re-INVITE with the SDP offer in which the port number of audio/video media is set to zero.
9.3.2.1.7  Enforcement of 3GPP SIP-Based 3GPP PS Data Off Exempt Services |R19|  p. 20
When 3GPP PS data off is supported and 3GPP PS data off status is changed to "active", if the list of 3GPP PS data off exempt services configured in TS 24.275 or in TS 31.102 indicates that the services over IMS Data Channel is not a 3GPP PS data off exempt service, in addition to following TS 24.229, the UE shall:
  1. prevent IMS data channel setup procedures;
  2. close all the IMS data channels in the ongoing MMTel session with IMS data channel by generating a re-INVITE request including an SDP offer that contains the IMS data channel media descriptions for both bootstrap data channels and application data channels and set the UDP port number of each IMS data channel media description to zero;
  3. terminate the ongoing standalone IMS data channel session by applying procedures defined in clause 5.1.5 of TS 24.229; and
  4. if the UE sent an initial INVITE request with IMS data channel media description(s) in the SDP offer and did not receive a final response to the initial INVITE request:
    1. if the initial SDP offer contained only IMS data channel media description(s), send a CANCEL request; or
    2. if the initial SDP offer also contained other media description(s):
      • if the UE received the SDP answer, at least one of the offered IMS data channel media descriptions is accepted, and there is no ongoing SDP offer/answer exchange, 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 (or PRACK) request; or
      • if the UE did not yet receive the SDP answer, wait for reception of a SIP message with the SDP answer. If the received SDP answer indicates at least one of the offered IMS data channel media descriptions is accepted, 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 (or PRACK) request.
Up
9.3.2.1.8  Support of data channel multiplexing |R19|  p. 20
If a UE determines both the UE and its home IMS network support IMS data channel multiplexing capability, and wants to multiplex IMS data channels during IMS data channel establishment, the UE shall:
  1. follow the procedures of clause 9.3.2.1.2, clause 9.3.2.1.3 and clause 9.3.2.1.6.4 to generate an initial INVITE, a re-INVITE or a UPDATE request;
  2. include the "g.3gpp.dc-mux" media feature tag defined in TS 26.114 in the Contact header field; and
  3. include in the SDP offer the multiplexed data channel media description(s) according to TS 26.114, using:
    1. a single m line for both the local and remote bootstrap data channels; and
    2. a single m line for different application data channels for applications with compatible QoS requirements.
Upon receipt of the 18x or 2xx response including SDP answer to the initial INVITE, re-INVITE or UPDATE request, if the port number(s) of the multiplexed data channel media description(s) is set to zero and the "g.3gpp.dc-mux" header field parameter as specified in TS 26.114 is not included in the Contact header field, the UE may modify the SDP offer with de-multiplexed data channel media description and resend the corresponding request.
Upon receiving a re-INVITE request with an SDP offer, which contains multiplexed data channel media description(s), the procedure defined in clause 9.3.3.1.8 applies.
If a 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.
Up

Up   Top   ToC