hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 5
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
1 Scope
|
The present document provides the protocol details for enhancements to IMS multimedia telephony communication services enabled by supporting the IMS data channel and for AR communication which is one of the applications based on IMS data channel capability, based on stage 1 requirements in 3GPP TS 22.261 [2] and stage 2 requirements in 3GPP TS 23.228 [3].
The present document is applicable to User Equipment (UE), Application Servers (AS)and IP Multimedia (IM) Core Network (CN) subsystem which are intended to support IMS multimedia telephony communication services supporting the IMS data channel and AR communication which is one of the applications based on IMS data channel capability.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.261: "Service requirements for the 5G system; Stage 1".
[3] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[4] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction".
[5] IETF RFC 5688: "A Session Initiation Protocol (SIP) Media Feature Tag for MIME Application Subtype".
[6] IETF RFC 6809: "Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)".
[7] IETF RFC 3264: "An Offer/Answer Model with the Session Description Protocol (SDP)".
[8] 3GPP TS 22.173: "IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1".
[9] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[10] 3GPP TS 24.173: "IMS Multimedia telephony communication service and supplementary services; Stage 3".
[11] 3GPP TS 24.275: "Management Object (MO) for Basic Communication Part (BCP) of IMS Multimedia Telephony (MMTEL) communication service".
[12] 3GPP TS 24.629: "Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[13] 3GPP TR 22.873: "Study on evolution of the IP Multimedia Subsystem (IMS) multimedia telephony service".
[14] IETF RFC 8864: "Negotiation Data Channels Using the Session Description Protocol (SDP)".
[15] 3GPP TS 24.147: "Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem".
[16] 3GPP TS 24.604: "Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[17] 3GPP TS 24.615: "Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[18] 3GPP TS 29.175: "IP Multimedia Subsystem; IP Multimedia Subsystem (IMS) Application Server (AS) Services; Stage 3".
[19] 3GPP TS 29.176: "IP Multimedia Subsystems (IMS); Media Function (MF) Services; Stage 3".
[20] 3GPP TS 32.260: "Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging".
[21] 3GPP TS 32.255: "Telecommunication management; Charging management; 5G data connectivity domain charging; stage 2".
[22] 3GPP TS 24.647: "Advice Of Charge (AOC) using IP Multimedia (IM) Core Network (CN) subsystem".
[23] 3GPP TS 24.239: "Flexible Alerting (FA) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[24] 3GPP TS 24.174: "Support of multi-device and multi-identity in the IP Multimedia Subsystem (IMS); Stage3.
[25] 3GPP TS 24.642: " Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[26] 3GPP TS 24.183: "IP Multimedia Subsystem (IMS) Customized Ringing Signal (CRS); Protocol specification".
[27] 3GPP TS 24.182: "IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT); Protocol specification".
[28] 3GPP TS 24.628: "Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[29] 3GPP TS 26.264: "IMS-based AR Real-Time Communication".
[30] 3GPP TS 31.103: "Characteristics of the IP multimedia services identity module (ISIM) application".
[31] 3GPP TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM) application".
[32] 3GPP TS 24.610:" Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[33] 3GPP TS 22.011: "Service accessibility".
[34] 3GPP TS 22.156: "Mobile Metaverse Services; Stage 1".
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
3 Definitions of terms, symbols and abbreviations
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
3.1 Terms
|
For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
IMS data channel application: An IMS data channel application is an application using IMS data channel capability to provide IMS services.
AR anchor: AR anchor is meant to identify a point in the user space to be used to anchoring a visual object. It is kind of metadata allowing accurate overlaying/rendering of text, graphics or video contents.
For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.228 [3] apply:
Bootstrap data channel
Application data channel
IMS communication service
IMS Communication Service Identifier (ICSI)
Standalone IMS Data Channel Session
The following terms and definitions given in 3GPP TS 26.264 [29] apply:
AR media
Split rendering
The following terms and definitions given in 3GPP TS 24.229 [9] apply:
3GPP PS data off status
The following terms and definitions given in 3GPP TS 22.011 [33] apply:
3GPP PS data off
3GPP PS data off exempt services
The following terms and definitions given in 3GPP TS 22.156 [34] apply:
Avatar
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
ADC Application Data Channel
AR Augmented Reality
AOC Advice Of Charge
AS Application Server
BDC Bootstrap Data Channel
CAT Customized Alerting Tones
CB Communication Barring
CCBS Completion of Communications to Busy Subscriber
CCNL Completion of Communications on Not Logged-in
CCNR Completion of Communications by No Reply
CD Communication Deflection
CDIV Communication DIVersion
CFB Communication Forwarding Busy
CFNL Communication Forwarding on Not Logged-in
CFNR Communication Forwarding No Reply
CFNRc Communication Forwarding on subscriber Not Reachable
CFU Communication Forwarding Unconditional
CN Core Network
CONF Conference
CRS Customized Ringing Signal
CW Communication Waiting
DC Data Channel
DCSF Data Channel Signalling Function
CUG Closed User Group
eCNAM Enhanced Calling Name
ECT Explicit Communication Transfer
FA Flexible Alerting
HOLD Communication Hold
ICSI IMS Communication Service Identifier
IM IP Multimedia
IMS IP Multimedia Core Network Subsystem
ISIM IM Subscriber Identity Module
MF Media Function
MiD Multi-iDentity
MMTel Multimedia Telephony
MuD Multi-Device
MWI Message Waiting Indication
OIP Originating Identification Presentation
OIR Originating Identification Restriction
OMA-DM Open Mobile Alliance Device Management
P2A Person to Application
P2A2P Person to Application and Application to Person
P2P Person to Person
SBI Service Based Interface
PSI Public Service Identifier
TIP Terminating Identification Presentation
TIR Terminating Identification Restriction
UE User Equipment
UICC Universal Integrated Circuit Card
URN Uniform Resource Name
USIM Universal Subscriber Identity Module
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
3.3 Symbols
|
For the purposes of the present document the following symbols apply:
DC1 Reference Point between an SBI capable IMS AS and DCSF.
DC2 Reference Point between an SBI capable IMS AS and MF.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
4 General
|
According to 3GPP TS 23.228 [3], IMS multimedia telephony service supporting IMS data channel includes IMS data channel capability negotiation and IMS data channel setup. AR communication which is application based on IMS data channel capability, provisioned to the UE as an IMS data channel application, includes respective application domain specific media capability negotiation and media processing (e.g. AR communication).
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
5 Functional entities
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
5.1 General
|
This clause specifies the functionalities of the functional entities for IMS data channel.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
5.2 UE
|
An UE supporting IMS data channel has the following functionalities:
- support IMS data channel capability negotiation;
- support bootstrap data channel and application data channel establishment and management;
- may support IMS data channel multiplexing and its capability negotiation.
Additionally, the UE supporting the IMS data channel capability and provisioned with AR communication, which is an application having IMS data channel capability, supports the following functionalities:
- support application's domain specific media capability exchange; and
- support application's domain specific media processing.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
5.3 IMS AS
|
The IMS AS interacts with the DCSF and the MF.
For functionalities of the IMS AS supporting IMS data channel refer to 3GPP TS 23.228 [3] clause AC.2.2.4.
For the IMS AS interaction with the Media Function (MF) refer to 3GPP TS 29.176 [19].
For the IMS AS interaction with the Data Channel Signalling Function (DCSF), NEF and Trusted AF refer to 3GPP TS 29.175 [18].
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
6 Operational requirements
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
6.1 Provision/withdrawal
|
IMS Multimedia Telephony communication service enhanced to support IMS data channel is provided after prior arrangement with the service provider.
IMS Multimedia Telephony communication service enhanced to support IMS data channel is withdrawn at the user's request or for administrative reasons.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
7 Basic communication
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
7.1 IMS Session Control
|
The IMS multimedia telephony communication enhanced to support the IMS data channel applications shall support data channel media specified in clause 6.2.10 of 3GPP TS 26.114 [4] in addition to MMTel media types listed in 3GPP TS 22.173 [8]. The session control procedures for the different media types shall be in accordance with 3GPP TS 24.229 [9], 3GPP TS 24.173 [10] and clause 9.
The usage of IMS data channel media streams in MMTel session is negotiated using the SDP offer/answer procedures defined in IETF RFC 3264 [7]. If the received SDP offer contains IMS data channel media description(s) and if the receiving entity determines not to accept the requested IMS data channels, the receiving entity shall reject the offered data channel media description(s) by setting the port number of the rejected data channel media description(s) to zero in created SDP answer.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
7.2 IMS communication service identifier (ICSI)
|
The MMTel service enhanced to support IMS Data Channel shall use the ICSI value defined in 3GPP TS 24.173 [10] clause 5.1. The UE and IMS AS shall handle the ICSI value as specified in 3GPP TS 24.229 [9].
NOTE: Based on the operator policy, the subclass identifier ".imsdc" can be used within the MMTel ICSI URN.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
8 IMS data channel applications
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
8.1 Procedures at the UE
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
8.1.1 General
|
Once an MMTel session with the bootstrap data channels have been established, if the IMS data channel applications are available, based on the IMS data channel applications list received via the established bootstrap data channel, the UE shall download through the established bootstrap data channel the IMS data channel applications. The UE shall follow the procedures in clause 9.3.2.1.3.2 to set up an application data channel and include in the re-INVITE request the updated SDP offer with negotiated bootstrap data channel media description, the requested application data channel media description as well as the associated data channel application binding information (provided within the "a=3gpp-req-app" SDP attribute), according to 3GPP TS 23.228 [3] and 3GPP TS 26.114 [4]. The UE receiving the re-INVITE request shall identify the requested application data channel and the corresponding IMS data channel application, select an established bootstrap data channel to download through if it is not available on the UE, based on the associated data channel application binding information.
Upon receipt of a re-INVITE request initiated by the IMS AS to update an existing MMTel session with established bootstrap data channels for adding an application data channel requested by a DC AS, the UE accepting the requested application data channel shall identify the corresponding IMS data channel application and select an established bootstrap data channel to download through if it is not available on the UE, based on the associated data channel application binding information.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
8.1.2 Support of Standalone IMS Data Channel Session
|
If the originating UE has downloaded the data channel application, application data channel can be established together with bootstrap data channel during standalone IMS data channel session establishment.
If the terminating UE received the INVITE request to set up the bootstrap and application data channel simultaneously, the UE shall identify the data channel application in the application binding information (provided within the "a=3gpp-req-app" SDP attribute) is available or not, and:
1) if not available, it shall accept the bootstrap data channel and reject the application data channel to indicate that the data channel application is desired to be downloaded and download the application data channel through the established bootstrap data channel; or
2) if available, it shall follow the procedure in clause 9.3.3.1.6.3 to establish the requested bootstrap data channel and application data channel.
If the UE did not download the data channel application, the UE shall establish an IMS session with only the bootstrap data channel towards a PSI, download the application through the established bootstrap data channel, and then establish an standalone IMS session with the associated application data channel and required bootstrap data channels towards peer UE; or initiate an IMS session with only the bootstrap data channel towards peer UE, and download the application through the established bootstrap data channel then add the associated application data channel during standalone IMS data channel session establishment.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
8.2 Procedures at the IMS AS
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
8.2.1 General
|
After an MMTel session with the bootstrap data channels have been established, if the IMS AS received a re-INVITE request with an SDP offer containing application data channels media descriptions (identified by "dcmap" attribute lines containing "stream-id" parameter set to values starting at 1000 and associated "a=3gpp-req-app" attribute lines as specified in 3GPP TS 26.114 [4]), the IMS AS shall notify the DCSF, may trigger the reservation or update of corresponding application data channel media resources upon the instruction from the DCSF and shall send re-INVITE request with the SDP offer containing the requested application data channel and related bootstrap data channel media descriptions according to the specific data channel application use case (e.g. P2P/P2A/P2A2P), following the procedures in 3GPP TS 23.228 [3] and clauses 9.3.2.2.2.2 and 9.3.3.2.2.2.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
8.2.2 Support of Standalone IMS Data Channel session
|
The application data channel can be established along with the bootstrap data channel. If the IMS AS receives the INVITE to establish the bootstrap data channel and the application data channel, it shall check whether the user is authorized to use standalone data channel. If the user is authorized to use standalone data channel, the IMS AS shall notify the DCSF and reserve the data channel media as specified in clause 9.3.2.1.6.4 and 9.3.3.1.6.3.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9 Signalling Procedures
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.1 General
|
This clause provides the following signalling procedures for IMS data channel:
- IMS data channel capability negotiation during IMS initial registration and re-registration;
- IMS data channel capability indication during session establishment and modification;
- IMS data channel establishment which includes both bootstrap data channel and application data channel establishment during session establishment and modification;
- IMS data channel shutdown which includes both bootstrap data channel and application data channel; and
- abnormal cases.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.2 IMS data channel capability negotiation
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.2.1 IMS data channel capability negotiation during IMS initial registration
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.2.1.1 Procedure at the UE
|
The policy related to the UE supporting the IMS data channel can be provided by the network to the UE using e.g. OMA-DM with the management objects specified in 3GPP TS 24.275 [11], ISIM with EFIMSDCI file specified in 3GPP TS 31.103 [30] or USIM with EFIMSDCI file specified in 3GPP TS 31.102 [31]. When the UE is configured as specified in 3GPP TS 24.275 [11], 3GPP TS 31.103 [30] or 3GPP TS 31.102 [31] with configuration for IMS data channel allowed then the UE determines support for IMS data channel according to the configuration. If the UE is configured with both IMS_DC_configuration node and EFIMSDCI file, then the EFIMSDCI file shall take precedence.
If the UE is configured with IMS_DC_configuration node specified in 3GPP TS 24.275 [11] or EFIMSDCI file specified in 3GPP TS 31.103 [30] or 3GPP TS 31.102 [31], and the DC_allowed leaf of the IMS_DC_configuration node or IMS DC Establishment Indication of the EFIMSDCI file indicates that IMS data channel is allowed, then a UE supporting IMS data channel on sending an unprotected REGISTER request shall include the media feature tag defined in IETF RFC 5688 [5] for supported streaming media type. For the IMS data channel capability indication, the UE shall use +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4].
NOTE: Precedence for EFIMSDCI file configured on both the USIM and ISIM is defined in 3GPP TS 31.102 [31].
On receiving the 200 (OK) response to the REGISTER request, if the 200 (OK) response includes a Feature-Caps header field containing feature-capability indicator "g.3gpp.datachannel", the UE shall determine that the home network supports the IMS data channel capability as specified in 3GPP TS 23.228 [3].
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.2.1.2 Procedure at the IMS AS
|
Upon receipt of a third-party REGISTER request, if the Contact header field of the REGISTER request in the body including a media feature tag for supported streaming media type containing +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4], the IMS AS shall store this IMS data channel capability indication and determine the UE supports the IMS data channel capability.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.2.2 IMS data channel capability negotiation during IMS re-registration
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.2.2.1 Procedure at the UE
|
If the UE is allowed to use IMS data channel, on sending of re-REGISTER request, for user-initiated reregistration, the UE supporting IMS data channel shall include the media feature tag defined in IETF RFC 5688 [5] for supported streaming media type. For the IMS data channel capability indication, the UE shall use +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4].
NOTE: The policy related to the IMS data channel allowed at the UE, can be provided by the network to the UE using e.g., OMA-DM with the management objects specified in 3GPP TS 24.275 [11] or UICC configuration, as specified in clause 9.2.1.1.
On receiving the 200 (OK) response to the re-REGISTER request, if the 200 (OK) response includes a Feature-Caps header field containing feature-capability indicator "g.3gpp.datachannel", the UE shall determine that the home network supports the IMS data channel capability as specified in 3GPP TS 23.228 [3].
The UE shall continue to indicate its IMS data channel capability as specified in the above procedure when the UE has successfully done the IMS data channel capability negotiation during IMS initial registration or re-registration.
On receiving the 200 (OK) response to the REGISTER request, if the 200 (OK) response does not include a Feature-Caps header field containing feature-capability indicator "g.3gpp.datachannel", the UE shall keep established data channel media of the UE's existing IMS session.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.2.2.2 Procedure at the IMS AS
|
Upon receipt of a third-party REGISTER request, if the Contact header field of the REGISTER request in the body including a media feature tag for supported streaming media type containing +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4], the IMS AS shall store this IMS data channel capability indication and determine the UE supports the IMS data channel capability.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.2.3 IMS data channel capability indication during IMS session establishment and modification
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.2.3.1 Procedure at the UE
|
Upon generating an initial INVITE request or a re-INVITE request, if the UE supporting IMS data channel is configured with IMS data channel is allowed option and if the UE determined its home network supports the IMS data channel capability, the UE shall include the +sip.app-subtype media feature tag defined in IETF RFC 5688 [5] for supported streaming media type in the Contact header field set to the value="webrtc-datachannel" as specified in 3GPP TS 26.114 [4], regardless of IMS data channel media description being part of the SDP offer or not. The UE may include in the initial INVITE request an Accept-Contact header field containing the "sip.app-subtype" media feature tag defined in IETF RFC 5688 [5] with a value of "webrtc-datachannel" as specified in 3GPP TS 24.173 [10].
Upon receiving an initial INVITE request or a re-INVITE request, if the UE supporting IMS data channel is configured with IMS data channel is allowed option, the UE shall include +sip.app-subtype media feature tag defined in IETF RFC 5688 [5] set to the value ="webrtc-datachannel" as specified in 3GPP TS 26.114 [4] in the Contact header field in the SIP response, regardless of IMS data channel media description being part of the SDP offer or not.
9.2A IMS data channel multiplexing capability negotiation
9.2A.1 IMS data channel multiplexing capability negotiation during IMS registration
9.2A.1.1 Procedure at the UE
If a UE supporting IMS data channel multiplexing capability is allowed to use IMS data channel, on sending of an unprotected REGISTER request or re-REGISTER request for user-initiated re-registration, the UE shall include the "g.3gpp.dc-mux" media feature tag defined in 3GPP TS 26.114 [4] in the Contact header field.
On receiving the 200 (OK) response to the REGISTER request or re-REGISTER request, if the 200 (OK) response includes a Feature-Caps header field containing feature-capability indicator "g.3gpp.dc-mux", the UE shall determine that the home network supports the IMS data channel multiplexing capability as specified in 3GPP TS 23.228 [3].
The UE shall continue to indicate its IMS data channel multiplexing capability as specified in any subsequent re-registration procedure when the UE has successfully done the IMS data channel capability negotiation during IMS initial registration or re-registration.
9.2A.1.2 Procedure at the IMS AS
Upon receipt of a third-party REGISTER request, if the Contact header field of the REGISTER request in the body including a "g.3gpp.dc-mux" media feature tag defined in 3GPP TS 26.114 [4], the IMS AS shall store this IMS data channel multiplexing capability indication and determine the UE supports the IMS data channel multiplexing capability.
9.2A.2 IMS data channel multiplexing capability indication during IMS session establishment and modification
9.2A.2.1 Procedure at the UE
If supporting IMS data channel multiplexing capability, being allowed to use IMS data channel and having determined the home network supports the IMS data channel multiplexing capability, upon generating an initial INVITE request or a re-INVITE request including a SDP offer that contains data channel media descriptions using IMS data channel multiplexing, the UE shall include the "g.3gpp.dc-mux" media feature tag defined in 3GPP TS 26.114 [4] in the Contact header field.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3 MMTel session procedures
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.1 General
|
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 3GPP TS 24.173 [10] with the additions defined in the present document.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2 Originating side
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.1 Procedures at the UE
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.1.1 General
|
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 3GPP TS 24.275 [11] 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 3GPP TS 24.275 [11] and:
a) 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
b) 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;
NOTE 1: If the bootstrap data channel was not established during the MMTel session establishment, the UE can try to setup the bootstrap data channel as described in clause 9.3.2.1.3.1.
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 3GPP TS 31.103 [30] or 3GPP TS 31.102 [31] and:
a) 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;
b) 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;
NOTE 2: If the bootstrap data channel was not established during the MMTel session establishment, the UE can try to setup the bootstrap data channel as described in clause 9.3.2.1.3.1.
c) 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
d) 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.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.1.2 IMS bootstrap data channel setup in conjunction with MMTel session setup
|
If the UE initiates an MMTel session with IMS data channels, the UE:
1) shall generate an initial INVITE request in accordance with 3GPP TS 24.229 [9] and 3GPP TS 24.173 [10];
2) shall include the media feature tag defined in IETF RFC 5688 [5] for supported streaming media type with +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4] in the Contact header field;
3) may include an Accept-Contact header field containing the "sip.app-subtype" media feature tag defined in IETF RFC 5688 [5] with a value of "webrtc-datachannel" as specified in 3GPP TS 26.114 [4]; 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 3GPP TS 24.173 [10] and data channel media descriptions for both the local and remote bootstrap data channels in accordance with 3GPP TS 26.114 [4].
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.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.1.3 IMS data channel setup in conjunction with MMTel session modification
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.1.3.1 IMS bootstrap data channel establishment
|
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 3GPP TS 24.229 [9] and 3GPP TS 24.173 [10];
2) include the media feature tag defined in IETF RFC 5688 [5] for supported streaming media type with +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4] 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 3GPP TS 26.114 [4].
Upon receiving a re-INVITE request to establish a bootstrap data channel, the procedure defined in clause 9.3.3.1.3.1 applies.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.1.3.2 IMS application data channel establishment
|
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 3GPP TS 24.229 [9] and 3GPP TS 24.173 [10];
2) shall include the media feature tag defined in IETF RFC 5688 [5] for supported streaming media type with +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4] 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 3GPP TS 26.114 [4].
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.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.1.4 Closing IMS application data channel in conjunction with MMTel session modification
|
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 IETF RFC 8864 [14] clause 6.6.1 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 IETF RFC 8864 [14].
The UE shall not close the bootstrap data channel during MMTel session modification procedure.
NOTE: The application data channel termination during the session modification does not impact the ongoing audio, video or other data channels within the MMTel session.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.1.5 Closing IMS data channel in conjunction with MMTel session release
|
When the UE releases an MMTel session that has associated bootstrap and application data channels, the UE shall apply procedures defined in 3GPP TS 24.229 [9] clause 5.1.5 and shall close bootstrap and application data channels.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.1.6 Support of standalone data channel
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.1.6.1 General
|
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 3GPP TS 24.275 [11] and DC_allowed leaf indicates that IMS data channel is not allowed, the UE shall not establish an standalone IMS data channel session.
NOTE 1: The DC_setup_option of the IMS_DC_configuration leaf that is specified in 3GPP TS 24.275 [11] is not applicable to the standalone IMS data channel session establishment.
If the UE is configured with EFIMSDCI file specified in 3GPP TS 31.103 [30] or 3GPP TS 31.102 [31] and IMS DC Establishment Indication indicates that IMS data channel is not allowed, the UE shall not establish an standalone IMS data channel session.
NOTE 2: The coding '01' and '02' for the IMS Data Channel Establishment Indication in the EFIMSDCI file specified in 3GPP TS 31.103 [30] or 3GPP TS 31.102 [31] are not applicable to the standalone IMS data channel session establishment.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.1.6.2 Standalone bootstrap data channel establishment
|
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.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.1.6.3 Void
|
9.3.2.1.6.3A Adding application data channel during standalone IMS data channel session establishment
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.
NOTE: The UE initiates a standalone data channel session towards the terminating UE with only bootstrap data channel if the user selected data channel application is not available.
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 3GPP TS 26.114 [4].
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.1.6.4 Combined standalone bootstrap data channel and application data channel establishment
|
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.
NOTE: The UE initiates a standalone data channel session towards the terminating UE with both bootstrap data channel and application data channel if the user selected data channel application is available at UE.
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 3GPP TS 23.228 [3] clause AC.10.2.3 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 3GPP TS 26.114 [4].
NOTE: If the terminating UE accepted the bootstrap data channel and rejected the application data channel received in the SDP answer of 183 (Session Progress) response to the initial INVITE request with both bootstrap and application data channel media description, it means that the terminating UE desires to download the data channel application.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.1.6.5 Adding video/audio media to IMS session with standalone data channel
|
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.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.1.6.6 Removing video/audio media from IMS data channel session
|
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.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.1.7 Enforcement of 3GPP SIP-Based 3GPP PS Data Off Exempt Services
|
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 3GPP TS 24.275 [11] or in 3GPP TS 31.102 [31] indicates that the services over IMS Data Channel is not a 3GPP PS data off exempt service, in addition to following 3GPP TS 24.229 [9], 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 3GPP TS 24.229 [9] clause 5.1.5; 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:
a) if the initial SDP offer contained only IMS data channel media description(s), send a CANCEL request; or
b) 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.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.1.8 Support of data channel multiplexing
|
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 3GPP TS 26.114 [4] in the Contact header field; and
3) include in the SDP offer the multiplexed data channel media description(s) according to 3GPP TS 26.114 [4], using:
a) a single m line for both the local and remote bootstrap data channels; and
b) 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 3GPP TS 26.114 [4] 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.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.2 Procedure at the IMS AS
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.2.1 IMS bootstrap data channel establishment in conjunction with MMTel session setup
|
Based on served user service specific data which is enhanced with IMS data channel specific service details, if the IMS AS received an initial INVITE request with an SDP offer containing media description for IMS data channels, the IMS AS shall determine whether the served user is authorized to use IMS data channel.
If the served user is not authorized to use IMS data channel, then based on the operator policy the IMS AS shall determine whether to remove from the SDP offer media lines related to the IMS data channels:
- If the operator policy indicates removal of media lines related to the IMS data channels, the IMS AS shall remove media lines describing the bootstrap data channel(s) i.e. "dcmap" attribute lines containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0, 10, 100 and 110, and associated with 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". If there are no other "dcmap" attribute lines that contain a subprotocol parameter set to value other than "http", the IMS AS shall remove any other SDP media attribute lines associated with that m line e.g., "sctp-port", "max-message-size", "tls-id", "a=setup", "a=3gpp-qos-hint" SDP attribute lines from the received SDP offer, and send the initial INVITE request with the modified SDP offer to the S-CSCF.
- If the operator policy does not indicate removal of media lines related to the IMS data channels, the IMS AS may forward media description describing the bootstrap data channel with "dcmap" attribute lines containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110, and send the initial INVITE request to the S-CSCF.
Otherwise, if the served user is authorized to use IMS data channel and the DCSF is not selected, the IMS AS shall select a DCSF and notify the DCSF about the session establishment request event, with a calling identity set to the value of the P-Asserted-Identity header field and a called identity set to the value of Request URI of the received initial INVITE request, and shall not send the initial INVITE request to the S-CSCF until receiving an acknowledgement to the corresponding notification from the DCSF.
Based on the received Media instruction set from the DCSF, the IMS AS shall select a MF and request the MF to allocate required data channel media resources. Based on the response of the reserved media resource from the MF, the IMS AS shall:
1) delete the bootstrap data channel media description terminated locally, i.e. local bootstrap data channel for the originating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10);
2) replace the IP address represented in the attribute lines "c=" line, the UDP port number in the "m=application" line, as well as the DC endpoint information represented as the attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" within the remote bootstrap data channel media description for the originating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110), i.e. the remote bootstrap data channel between the originating UE and terminating network, received in the SDP offer with the media resource information for the termination towards the remote network allocated on the MF if the media is anchored on the originating MF, and add "a=3gpp-bdc-used-by:" attribute line containing "bdc-used-by" parameter set to value "sender" if not present; and
3) generate and add the remote bootstrap data channel media description for the terminating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110 and "a=3gpp-bdc-used-by:" attribute with "bdc-used-by" parameter set to value "receiver"), i.e. remote bootstrap data channel between the originating network and the terminating UE.
Upon the reception of the successful acknowledgement to the corresponding notification from the DCSF, the IMS AS shall send the initial INVITE request with audio, video and modified data channel SDP offer to the S-CSCF towards the terminating network.
Upon receipt the 18x or 2xx response on the initial INVITE request including the SDP answer which includes the data channel media description, the IMS AS shall notify the DCSF about corresponding session event (session establishment progress (i.e. receiving the 183 (Session Progress) response ), session establishment alerting (i.e. receiving the 180 (Ringing) response) or session establishment success (i.e. receiving 200 (OK) response) event) and shall request the MF to update the media resource. Based on the media resource update response from the MF, the IMS AS shall:
1) delete the remote bootstrap data channel media description for the terminating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110 and "a=3gpp-bdc-used-by" attribute with "bdc-used-by" parameter set to value "receiver"), i.e. the remote bootstrap data channel between terminating UE and originating network from the SDP answer;
2) replace the IP address represented in the "c=" line, the UDP port number in the "m=application" line, as well as the DC endpoint information represented as the attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" within the remote bootstrap data channel media description for originating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and110 and "a=3gpp-bdc-used-by" attribute with "bdc-used-by" parameter set to value "sender") in the SDP answer if the media is anchored on the MF, i.e. the remote data channel for the originating UE between originating UE and terminating network, with the media resource information for the termination towards the originating UE to the terminating network allocated by the MF; and
3) generate and add the local bootstrap data channel media description for the originating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and10), i.e. the local bootstrap data channel between originating UE and originating network in the SDP answer.
Upon the reception of an acknowledgement from the DCSF to the corresponding notification, the IMS AS shall include the modified SDP answer for data channel in the 18x or 2xx response and send 18x or 2xx response to S-CSCF towards the originating UE.
If the IMS AS received from the terminating network the UPDATE request with the SDP offer containing data channel media description for the bootstrap data channel establishment, the procedure of the IMS AS defined in clause 9.3.3.2.2.1 applies.
Upon receipt of a CANCEL request to the initial INVITE request, the IMS AS shall notify the DCSF about the session establishment cancellation, request the MF to release the corresponding data channel media resources, and forward the CANCEL request to the S-CSCF towards the terminating network.
Upon receipt of a 4xx, 5xx or 6xx response on the initial INVITE request from the terminating network, the IMS AS shall notify the DCSF about session establishment failure, and request the MF to release the data channel media resources.
9.3.2.2.1A Network-initiated IMS standalone data channel session setup
Upon receipt a request to setup an IMS standalone data channel session as specified in 3GPP TS 23.228 [3] AG.2.2, the IMS AS shall determine whether the served user is authorized to use IMS data channel as specified in clause 9.3.2.2.1. If the served user is authorized to use data channel, the IMS AS shall select a DCSF and notify the DCSF about the external session create event. Based on the instruction from the DCSF, the IMS AS shall request the MF to allocate data channel media resources, generate the media description for the data channel as specified in clause 9.3.2.2.2.4, generate and send initial INVITE request with
- SDP offer for the originating and terminating UEs as specified in 3GPP TS 24.229 [9] clause 5.7.3;
- the DC-Info header field as specified in 3GPP TS 24.229 [9] 7.2.x to indicate the data channel is initiated by the DC AS.
Upon receipt of the 18x or 2xx response including SDP answer to the initial INVITE request, the IMS AS shall notify the DCSF about corresponding session event (session establishment progress (i.e. receiving the 183 (Session Progress) response ), session establishment alerting (i.e. receiving the 180 (Ringing) response) or session establishment success (i.e. receiving 200 (OK) response) event) and request the MF to update the media resource.
Upon receipt of a 4xx, 5xx or 6xx response to the initial INVITE request, the IMS AS shall notify the DCSF about session establishment failure, and request the MF to release the data channel media resources.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.2.2 MMTel session modification
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.2.2.1 IMS bootstrap data channel establishment
|
If the IMS AS received from the originating UE a re-INVITE request with the SDP offer containing data channel media description for the bootstrap data channel establishment, the IMS AS shall determine whether the served user is authorized to use IMS data channel or not as specified in clause 9.3.2.2.1.
- if the served user is not authorized to use IMS data channel, the procedure defined in clause 9.3.2.2.1 applies; and
- if the served user is authorized to use IMS data channel, the IMS AS shall select a DCSF and notify the DCSF about the media change request event, with a calling identity set to the value of the P-Asserted-Identity header field and a called identity set to the value of Request URI of the initial INVITE request received during MMTel session establishment, if the media instruction from DCSF is:
a) to reject all the data channel medias in this request, the IMS AS shall send a 488 (Not Acceptable Here) to the originating UE if other medias are not updated; and
b) in other cases, the IMS AS shall request the MF to reserve the media resources and modify the data channel media description in the SDP offer and send the re-INVITE request as per clause 9.3.2.2.1. Upon receipt of the 183 (Session Progress) or 200 (OK) response to the re-INVITE request, the IMS AS shall send notify the DCSF about the media change success if the data channel media is accepted or media change failure if the data channel media is rejected and modify the data channel media description in the SDP answer and send the 183 (Session Progress) or 200(OK) response to S-CSCF as per clause 9.3.2.2.1. Upon receipt of a CANCEL request to the re-INVITE request, the IMS AS shall notify the DCSF about the media change cancellation, request the MF to release the corresponding data channel media resources, and forward the CANCEL request as per clause 9.3.2.2.1. Upon receipt of a 4xx, 5xx or 6xx response on the re-INVITE request, the IMS AS shall notify the DCSF about the media change failure and forward the response to the originating UE.
If the IMS AS received from the terminating network a re-INVITE request with the SDP offer containing data channel media description for the bootstrap data channel establishment, the procedure of the IMS AS in the terminating network on receipt of a re-INVITE request from the originating network defined in clause 9.3.3.2.2.1 applies.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.2.2.2 IMS application data channel establishment
|
After the DCSF is selected, upon receipt of the re-INVITE request with an SDP offer which contains new application data channel media descriptions (the media lines with the "dcmap" attribute containing "stream-id" parameter set to values starting at 1000) along with the video, audio, and bootstrap data channel media descriptions, the IMS AS shall notify to DCSF about a media change request event. If the media instruction from the DCSF is
- to reject all the data channel medias in this request, the IMS AS shall send a 488 (Not Acceptable Here) to the originating UE if other medias are not updated; and
- in other cases, the IMS AS shall request the MF to allocate media resources for the application data channels based on the instruction from the DCSF if the media is anchored on the MF, and shall not send a re-INVITE request to the S-CSCF until receiving an acknowledgement to the corresponding notification from the DCSF;
- based on the response on the data channel media resource update from the MF as specified in 3GPP TS 29.176 [19] and media instruction from the DCSF as specified in 3GPP TS 29.175 [18], the IMS AS shall:
1) delete the data channel media description (media line with the "dcmap" attribute containing "stream-id" parameter set to values starting at 1000 and "a=3gpp-req-app " attribute with "endpoint" parameter set to value "server") if the media instruction from the DCSF is to terminate that media;
2) delete the data channel media description if the media instruction from the DCSF is to reject the media and there are other medias to be established;
3) replace the IP address represented in the "c=" line, the UDP port number in the "m=application"in the data channel media description in the SDP offer with the media resource information for the termination towards the terminating network which is allocated by the MF if the media instruction from the DCSF is to terminate and originate the media; and also replace the DC endpoint information represented as the attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" when the media proxy configuration is HTTP proxy; and
4) generate and add a data channel media description (media line with the "dcmap" attribute containing "stream-id" parameter set to values starting at 1000 and "a=3gpp-req-app " attribute with "endpoint" parameter set to value "server") by using the DC stream information provided by the DCSF in the attribute lines "a=dcmap" and "a=3gpp-req-app", DC endpoint information of the DC AS in the attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup", IP address and UDP port number allocated on the termination towards to the terminating network on the MF in the "c=" line and "m=application" line when the media proxy configuration is UDP proxy, or using the DC stream information provided by the DCSF in the attribute lines "a=dcmap" and "a=3gpp-req-app", IP address, UDP port number and DC endpoint information (e.g. tlsId, sctp-port) allocated on the termination towards to the terminating network on the MF in other attribute lines above when the media proxy configuration is HTTP proxy, if the media instruction from the DCSF is to originate a new media; and
- an existing application data channel media description in which a new "a=dcmap" line containing the "stream-id" parameter set to values starting at 1000 is added, the IMS AS shall notify the DCSF about media change request event, and request MF to update the media resource when receiving the media instruction from DCSF is to update the media.
Upon the reception of an acknowledgement from the DCSF to the media change request event notification, the IMS AS shall send the re-INVITE request with the modified SDP offer with the modified application data channel media description or the original application data channel media description if no media instruction received from DCSF, as well as the media description of established video, audio and bootstrap data channels.
Upon receipt of the 183 (Session Progress) or 200 (OK) response on the re-INVITE request with the SDP answer which contains media description of the requested application data channel from the terminating network:
- if the application data channel is accepted, the IMS AS shall notify the DCSF about the media change success and request the MF to update the media resources. Based on the response of the MF, the IMS AS shall:
a) generate and add a data channel media description in the SDP answer by using the DC endpoint information of the DC AS provided by the DCSF in the attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" and IP address and UDP port number allocated on the termination towards to the originating UE on the MF in the "c=" and "m=application" line when the media proxy configuration is UDP proxy, or using IP address, UDP port number and DC endpoint information (e.g. tlsId, sctp-port) allocated on the termination towards to the originating UE on the MF in the attribute lines when the media proxy configuration is HTTP proxy, if the instruction from the DCSF is to terminate the media;
b) add the rejected media description and set the port number to 0 in the "m=application" line if the instruction from the DCSF is to reject the media and there are other medias to be established;
c) replace the IP address represented in the "c=" line, the UDP port number in the "m=application" in the media description in the SDP answer with the media resource information on the termination towards to the originating UE allocated by the MF, if the instruction from the DCSF is to terminate and originate the media; and also replace the DC endpoint information as attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" when the media proxy configuration is HTTP proxy; and
d) delete the media description in the SDP answer if the instruction from the DCSF is to originate a new media;
and send the 183 (Session Progress) or 200 (OK) response with the modified SDP answer on the re-INVITE request to the S-CSCF towards to the originating UE after the receipt of an acknowledgement from the DCSF to the corresponding notification; or
if the application data channel is rejected, the IMS AS shall notify the DCSF about the media change failure event and request the MF to release the media resources. Then, the IMS AS shall send 183 (Session Progress) or 200 (OK) response to S-CSCF after the receipt of an acknowledgement from the DCSF to the corresponding notification.
Upon receipt of a CANCEL request to the re-INVITE request, the IMS AS shall notify the DCSF about the media change cancellation, request the MF to release the corresponding data channel media resources, and forward the CANCEL request as per clause 9.3.2.2.1.
Upon receipt of a 4xx, 5xx or 6xx response on the re-INVITE request from the terminating network, the IMS AS shall notify the DCSF about media change failure, request the MF to release the corresponding data channel media resources and forward the response to the originating UE.
Upon receiving the re-INVITE request from the terminating network to setup data channels and the corresponding response from the originating UE, the procedure in clause 9.3.3.2.2 applies.
9.3.2.2.2.2A Support of data channel interworking between an DC capable originatiing UE and a non-DC capable terminating UE
When the IMS AS receives an initial INVITE or the re-INVITE request with an SDP offer that contains the media description for the bootstrap data channel, the procedure in clause 9.3.2.2.1 and clause 9.3.2.2.2.1 applies. If the IMS AS receives the SIP response to the initial INVITE or the re-INVITE request in which the SDP answer indicates the remote bootstrap data channel to the terminating UE is rejected, the IMS AS may check the Contact header field of the received response. If the media feature tag "sip.video" is contained in the received Contact header field, the IMS AS may report to the DCSF about that the terminating UE supports video media. On receipt of a re-INVITE request with an SDP offer that contains media description for application data channel in which the "endpoint" parameter is set to "UE" in attribute "a=3gpp-app-req" line, the IMS AS shall follow the procedure from clause 9.3.2.2.2.2 with the following additions.
If the IMS AS, after reporting the media change request event to the DCSF as per clause 9.3.2.2.2.2, received from the:
- an instruction to transform the application data channel media to video media, the IMS AS shall:
a) request the MF to allocate the video media resources as well as the data channel media resources (as specified in 3GPP TS 29.176 [19]) and generate and add the SDP offer the media description for video media based on the reserved video media resource information by the MF; and
b) delete media description for the corresponding application data channel in SDP offer, or
- an instruction to terminate the data channel and indicates the interworking, the IMS AS shall delete the media description for the application data channel; request the MF to allocate media resources for a P2A application data channel and notify the NEF the DC interworking required event as specified in 3GPP TS 29.175 [18].
The IMS AS shall send the re-INVITE request with the updated SDP offer to the S-CSCF towards the terminating network.
Upon receiving the 200 (OK) response with the SDP answer on the re-INVITE request, the IMS AS shall report the media change success event to the DCSF. If the instruction from the DCSF when reporting the media change request event to DCSF was:
- to transform the application data channel media to video media, the IMS AS shall:
a)- request the MF to associate the data channel application to the video streams as per 3GPP TS 29.176 [19];
b)- delete the media description of the video media from the SDP answer; and
c) generate and add the corresponding application data channel media description in the SDP answer by using the DC endpoint information allocated on the termination towards to the originating UE on the MF with the "endpoint" parameter set to "UE" in attribute "a=3gpp-app-req" line; or
- to terminate the application data channel and indicates the interworking, the IMS AS shall:
a) generate and add the corresponding application data channel media description in the SDP answer as per clause 9.3.2.2.2.2 with the "endpoint" parameter set to "server" in attribute "a=3gpp-app-req" line.
9.3.2.2.2.3 Closing application data channel
Upon receipt of the re-INVITE request with an SDP offer which contains an existing application data channel media description in which an existing "a=dcmap" is removed, the IMS AS shall notify the DCSF about media change request event, and request MF to update the media resource when receiving the media instruction from DCSF is to update the media.
Upon receipt of the re-INVITE request with an SDP offer which contains an existing application data channel media description in which the UDP port number is set to 0, the IMS AS shall notify the DCSF about media change request event, and request the MF to release the corresponding media resource when receiving the media instruction from the DCSF is to delete the media.
Upon receipt of the 200 (OK) response on the re-INVITE message with the SDP answer, the procedure in clause 9.3.2.2.2.2 applies.
Upon receiving the re-INVITE request from the terminating network to close data channels and the corresponding 200 (OK) response from the originating UE, the procedure in clause 9.3.3.2.2.3 applies.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.2.2.4 Network-initiated data channel establishment and update
|
If the IMS AS received a request from the NEF or trusted AF to update an existing IMS session to add a P2A application data channel and/or bootstrap data channel as specified in 3GPP TS 29.175 [18] towards a served UE, the IMS AS shall:
a) determine whether the served user is authorized to use IMS data channel as specified in clause 9.3.2.2.1.
b) determine the request application data channel is already established based on the comparison of the application binding information included in the request from the NEF or trusted AF with the "a=3gpp-req-app" attribute line within the application data channel media descriptions included in the latest stored SDP offer/answer for this IMS session;
c) determine the request bootstrap data data channel is already established based on the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10 within the data channel media descriptions included in the latest stored SDP offer/answer for this IMS session; or
d) determine the request bootstrap data data channel and/or application data channel is already established based on the comparison of the stored media correlation IDs with the one included in the request from the NEF.
If the served user is authorized to use data channel and the requested application data channel and/or bootstrap data channel is not established, the IMS AS shall select a DCSF and notify the DCSF about the external session update event. Based on the instruction of the DCSF, the IMS AS shall request the MF to allocate data channel media resources and
- generate the media description for:
a) the bootstrap data channel containing "a=dcmap" attribute line with the subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10; or
b) the P2A application data channel containing "dcmap" attribute in which "stream-id" parameter set to values starting at 1000, "a=3gpp-req-app" attribute line with "endpoint" parameter set to value "server", "c=" line and "m=application" line with the IP address and UDP port number information of termination on the MF towards to the UE, and "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" attribute lines with the information of the termination on the MF towards the UE if the media proxy configuration is HTTP, or the information of the DC AS if the media proxy configuration is UDP; and
- include the DC-Info header field as specified in 3GPP TS 24.229 [9] 7.2.x to indicate the data channel is initiated by the DC AS;
and generate and send a re-INVITE request to the served UE with an updated SDP offer in which the generated media description of data channel above is added.
Upon reception of the 200 (OK) response to the re-INVITE request in which:
- the data channel media is accepted, the IMS AS shall notify the DCSF about the media change success event; or
- the data channel media is rejected, the IMS AS shall notify the DCSF about the media change failure event.
If the IMS AS receives a request from the NEF or trusted AF to establish a P2A2P application data channel between two UEs in an existing IMS session in which the video/audio media is established, the IMS AS shall
- follow the procedure above to determine the served user is authorized to use data channel and the requested application data channel is not established; and
- include the DC-Info header field as specified in 3GPP TS 24.229 [9] 7.2.x to indicate the data channel is initiated by the DC AS;
and generate the application data channel media descriptions and generate and send re-INVITE requests for the served UE and the remote UE.
Upon reception of the 200(OK) responses to the re-INVITE request:
- if both the two UEs accept the data channel media, the IMS AS shall notify the DCSF about the media change success event;
- if both the two UEs reject the data channel media, the IMS AS shall notify the DCSF about the media change failure event;
- if one UE accepts the data channel media, and the other UE rejects the data channel media, the IMS AS shall send a re-INVITE request to the UE who accepts the data channel media to close the established data channel, and notify the DCSF about the media change failure.
If the IMS AS received a request from the NEF or trusted AF to update an existing IMS session to add a P2P application data channel as specified in 3GPP TS 29.175 [18], the IMS AS shall determine the served user is authorized to use data channel and the requested application data channel is not established, notify the DCSF about the external session update event. If the DCSF instructs to anchor the added application data channel on the MF of the originating network, the IMS AS shall request the MF to allocate the data channel media resource on the termination towards the served originating UE. Based on the data channel media information from the MF, the IMS AS generates an application data channel media description containing "dcmap" attribute in which "stream-id" parameter set to values starting at 1000, "a=3gpp-req-app" attribute line with "endpoint" parameter set to value "UE", "c=" line and "m=application" line with the IP address and UDP port number information and "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" attribute lines with the information of the termination on the MF towards the originating UE; and generate and send the re-INVITE request to originating UE.
Upon receiving the 200 (OK) response to the re-INVITE request including the SDP answer for the application data channel from the originating UE, the IMS AS shall request the MF to update the data channel media resources of the termination towards the originating UE and create the data channel media resources of the termination towards the terminating UE. Based on the media resources created by the MF, the IMS AS shall create an application data channel media description containing "dcmap" attribute in which "stream-id" parameter set to values starting at 1000, "a=3gpp-req-app" attribute line with "endpoint" parameter set to value "UE", "c=" line and "m=application" line with the IP address and UDP port number information and "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" attribute lines with the information of the termination on the MF towards the terminating network and generate and send the re-INVITE request to terminating network.
Upon receiving the 200 (OK) response to the re-INVITE request from the terminating network, the IMS AS shall update the media resources of the termination towards the terminating network. And then, the IMS AS shall send ACK to both terminating network and originating UE and notify about the media change success event.
If the served user is authorized to use data channel and the requested application data channel and/or bootstrap data channel is established, the IMS AS shall follow the requirement as specified in 3GPP TS 29.175 [18].
If the IMS AS received a request from the NEF or trusted AF to update an existing IMS session to update an application data channel and/or bootstrap data channel as specified in 3GPP TS 29.175 [18] towards a served UE, the IMS AS shall:
a) determine the request application data channel based on the comparison of the application binding information included in the request from the NEF or trusted AF with the "a=3gpp-req-app" attribute line within the application data channel media descriptions included in the latest stored SDP offer/answer for this IMS session;
b) determine the request bootstrap data data channel based on the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10 within the data channel media descriptions included in the latest stored SDP offer/answer for this IMS session; or
c) determine the request bootstrap data data channel and/or application data channel based on the comparison of the stored media correlation IDs with the one included in the request from the NEF; and
d) select a DCSF and notify the DCSF about the external session update event.
Based on the instruction of the DCSF, the IMS AS shall request the MF to update data channel media resources and update the media descriptions for the requested application data channel and/or bootstrap data channel and generate and send re-INVITE request for the served UE and also the remote UE when P2P or P2A2P application data channel is to be updated. In the re-INVITE request, the IMS AS shall include the DC-Info header field as specified in 3GPP TS 24.229 [9] 7.2.x to indicate the data channel is updated by the DC AS.
If the requested application data channel and/or bootstrap data channel to update is not existed, the IMS AS shall follow the requirement as specified in 3GPP TS 29.175 [18].
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.2.2.5 Network-determined closing of bootstrap and application data channel
|
If the IMS AS determines to terminate the established bootstrap data channels and application data channels to the terminating UE during the session modification, the procedure defined in clause 9.3.3.2.2.4 applies.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.2.2.6 Network-initiated data channel termination
|
If the IMS AS received a request from the NEF or trusted AF to update an existing IMS session to terminate an application data channel and/or bootstrap data channel towards the originating or the terminating UE as specified in 3GPP TS 23.228 [3] clause AG.2.1, the IMS AS shall:
a) determine the request application data channel based on the comparison of the application binding information included in the request from the NEF or trusted AF with the "a=3gpp-req-app" attribute line within the application data channel media descriptions included in the latest stored SDP offer/answer for this IMS session;
b) determine the request bootstrap data data channel based on the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10 within the data channel media descriptions included in the latest stored SDP offer/answer for this IMS session; or
c) determine the request bootstrap data data channel and/or application data channel based on the comparison of the stored media correlation IDs with the one included in the request from the NEF; and
notify the DCSF about external session update event as specified in 3GPP TS 29.175 [18], request MF to release or update the corresponding data channel media resource and send a re-INVITE request towards the UE with the subsequent SDP offer based on the media information of the data channel required by the NEF or the trusted AF. In the SDP offer, the IMS AS shall:
- set the UDP port number of the corresponding data channel media description to zero, if the required application data channel and/or bootstrap data channel is not multiplexed; or
- remove the "a=dcmap" attribute line associated with the required bootstrap data channel or application data channel and also the "a=3gpp-req-app" attribute if all the related application data channels for that application are to be terminated from the corresponding multiplexed data channel media description.
In the re-INVITE request, the IMS AS shall include the DC-Info header field as specified in 3GPP TS 24.229 [9] 7.2.x to indicate the data channel is terminated by the DC AS.
Upon reception of the 200 (OK) response to the re-INVITE request, the IMS AS shall notify the DCSF about the media change success event.
If the requested application data channel and/or bootstrap data channel to terminate does not existed, the IMS AS shall follow the requirement as specified in 3GPP TS 29.175 [18].
If a request is to terminate the only bootstrap data channel in an exising IMS session containing application data channels, the IMS AS shall reject the request and follow the requirement as specified in 3GPP TS 29.175 [18].
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.2.3 MMTel session release
|
Upon initiation or receipt of a BYE request matching an existing MMTel session with IMS data channel, the IMS AS shall notify session termination event to the DCSF and follow the call release procedure as per 3GPP TS 24.229 [9].
IMS AS shall send media resource management request to MF to release the allocated data channel media resources for this MMTel session.
Upon receipt of a request from the NEF or trusted AF to terminate an IMS standalone data channel session as specified in 3GPP TS 23.228 [3] clause AG.2.3, the IMS AS shall request MF to release the allocated data channel media resources for this IMS standalone data channel session, send a BYE request to both the served UE and the remote network and notify session termination event to the DCSF.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.2.4 Support of IMS standalone data channel session
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.2.4.1 General
|
If the IMS AS received from:
- the originating UE an initial INVITE request with the SDP offer containing only data channel media description; or
- the originating UE a re-INVITE request with the SDP offer in which the audio and video media is removed (i.e. the port number of the audio/video media set to 0);
the IMS AS shall determine whether the served user is authorized to use a standalone IMS data channel or not by the local configuration or the subscription data. If the user is not authorized to use IMS standalone data channel, the IMS AS shall send 401 (Unauthorized) to the originating UE to reject the session or to reject the media change request.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.2.4.2 Standalone bootstrap data channel establishment
|
Upon receipt of an initial INVITE request in which:
1) the SDP offer only includes IMS data channel media description for the local bootstrap data channel; and
2) the specific "request-uri" indicating standalone data channel contained in the Request-URI,
and the IMS AS determines that the user is authorized to use standalone data channel, the IMS AS shall:
a) notify the DCSF about session establishment request event;
b) request the MF to allocate the data channel media resources as per clause 9.3.2.2.1;
c) return a 200 (OK) response to the initial INVITE request with the SDP answer generated as per 3GPP TS 26.114 [4] and IETF RFC 8864 [14] to the S-CSCF towards the originating UE; and
d) notify the DCSF about the session establishment success event.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.2.4.3 Void
|
9.3.2.2.4.3A Subsequent standalone bootstrap data channel and application data channel establishment
Upon receipt of the initial INVITE request towards a terminating UE with the SDP offer which only includes media descriptions for bootstrap data channels and the 183 (Session Progress) response to the initial INVITE request from the terminating network, the IMS AS shall follow the procedure in clause 9.3.2.2.1 to handle the bootstrap data channel media.
Upon receipt the UPDATE request with an updated SDP offer that contains a data channel media description for 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) and the 200 (OK) response to the UPDATE request, the IMS AS shall follow the procedures upon receipt of the re-INVITE request and the response to the re-INVITE request in clause 9.3.2.2.2.2 to handle the application data channel media.
Upon receipt the 200 (OK) response to the initial INVITE request from the terminating network, the IMS AS shall notify the DCSF about the session establishment success event and forward the 200 (OK) response to the originating UE.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.2.4.4 Combined standalone bootstrap data channel and application data channel establishment
|
Upon receipt the initial INVITE request towards a terminating UE with the SDP offer which includes the media description for both bootstrap data channel and application data channel and the 183 (Session Progress) response to the initial INVITE request from the terminating network, the IMS AS shall follow the procedure in clause 9.3.2.2.1 to handle the bootstrap data channel media and clause 9.3.2.2.2.2 to handle the application data channel media.
Upon receipt the UPDATE request with an updated SDP offer that contains a data channel media description for 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) and the 200 (OK) response to the UPDATE request, the IMS AS shall follow the procedure in clause 9.3.2.2.2.2 to handle the application data channel media.
Upon receipt the 200 (OK) response to the initial INVITE request from the terminating network, the IMS AS shall notify the DCSF about the session establishment success event and forward the 200 (OK) response to the originating UE.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.2.5 Enforcement of 3GPP PS data off
|
If "Services over IMS Data Channel" is not in the list of 3GPP PS data off exempt services, upon receipt of a third-party REGISTER request containing a "+g.3gpp.ps-data-off" Contact header field parameter indicating the 3GPP PS data off status of the UE, in addition to the procedure in 3GPP TS 24.229 [9] clause 5.7.1.26, the IMS AS serving the UE:
1) may notify the DCSF about the 3GPP PS data off status of the UE by session establishment request event and PS data off status change event as specified in 3GPP TS 29.175 [18] and 3GPP TS 23.228 [3] clause X.3.2;
2) if the 3GPP PS data off status of the UE is changed from "inactive" to "active" and no SIP message removing all the IMS data channels in the ongoing MMTel session is received within an operator defined time, shall:
- generate 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, send to the served UE and remote network, notify the DCSF about media change request event due to the activation of the 3GPP PS data off and "Services over IMS Data Channel" is not in the list of 3GPP PS data off exempt services, and request MF to release the media resource for IMS data channels; and
- terminate the ongoing standalone IMS data channel session by applying procedures defined in 9.3.2.2.3; and
3) if the 3GPP PS data off status of the UE is changed from "inactive" to "active", no SIP message removing all the IMS data channels in the ongoing establishment of the MMTel session is received within an operator defined time, the IMS AS serving the UE received an initial INVITE request with IMS data channel media description(s) in the SDP offer and a final response to that initial INVITE request is not yet sent towards the served UE:
a) if the initial SDP offer contained only IMS data channel media description(s):
- shall send a 403 (Forbidden) response towards the served UE;
- if the initial INVITE request has been sent towards the terminating network, shall send a CANCEL request towards the terminating network;
- shall notify the DCSF about a session termination event due to the activation of the 3GPP PS data off and "Services over IMS Data Channel" is not in the list of 3GPP PS data off exempt services; and
- if the MF already allocated IMS data channel media resources, shall request the MF to release the allocated data channel media resource; or
b) if the initial SDP offer also contained other media description(s):
- if the IMS AS serving the UE did not yet receive the SDP answer, shall wait for reception of a SIP message with the SDP answer. Upon reception of the SDP answer, if at least one of the offered IMS data channel media descriptions is accepted (e.g., local or remote bootstrap data channel), the IMS AS serving the UE shall:
A) modify the SDP answer by setting the UDP port number of each accepted IMS data channel media description to zero and forward the received SIP message with the modified SDP answer to the served UE; and
B) 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 the UPDATE (or PRACK) request towards the terminating network;
- if the IMS AS serving the UE forwarded the SDP answer with accepted IMS data channel media descriptions to the served UE and there is no ongoing SDP offer/answer exchange, shall create a new SDP offer in which the UDP port number of each IMS data channel media description is set to zero and send the SDP offer within the UPDATE request towards the served UE and terminating network;
- notify the DCSF about media change request event due to the activation of the 3GPP PS data off and "Services over IMS Data Channel" is not in the list of 3GPP PS data off exempt services; and
- if the MF already allocated IMS data channel media resources, request the MF to release the allocated data channel media resource.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.2.6 Support of data channel interworking between a non-DC capable originating UE and a DC capable terminating UE
|
Upon receipt of an initial INVITE request with an SDP offer containing the audio and video media description from the originating UE, if the interworking required event subscribed and the IMS AS determines that the originating UE is a non-DC capable UE as specified in clause 9.2.1.2 and clause 9.2.2.2, the IMS AS shall notify the NEF or the trusted AF about the interworking required event based on the subscription from them as specified in 3GPP TS 23.228 [3] clause AC.7.9.4 and 3GPP TS 29.175 [18].
After the final response of the initial INVITE request received, the IMS AS shall notify the NEF or the trusted AF about the IMS session establishment event based on the subscription as specified in 3GPP TS 23.228 [3] clause AC.7.9.4 and 3GPP TS 29.175 [18].
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.2.7 Handling of data channel multiplexing
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.2.7.1 General
|
When the IMS AS receives from the originating UE an initial INVITE with the SDP offer containing only the multiplexed data channel media description(s), if the data channel multiplexing is not supported or not allowed, the IMS AS shall return 488 (Not Acceptable Here) response containing an SDP message body.
Upon receipt of a 488 response to the initial INVITE request with the SDP offer containing only the multiplexed data channel media description(s), the IMS AS shall notify the DCSF about session establishment failure and request the MF to modify the data channel media resources of multiplexed data channels towards the terminating network based on the media instruction from the DCSF. After the successful response from the MF, the IMS AS shall modify the SDP offer with de-multiplexed data channel media descriptions and resend the initial INVITE request towards the terminating network.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.2.7.2 Bootstrap data channel multiplexing
|
When the IMS AS receives from the originating UE an initial INVITE, a re-INVITE or an UPDATE request with an SDP offer that contains a multiplexed bootstrap media description, if the data channel multiplexing is supported and allowed, the IMS AS shall select and notify the DCSF as specified in clause 9.3.2.2.1, clause 9.3.2.2.2, and clause 9.3.2.2.4.
Based on the instruction of the DCSF, the IMS AS shall select an MF supporting data channel multiplexing and request the MF to allocate data channel media resources for the multiplexed data channels. Based on the response from the MF, the IMS AS shall modify the SDP offer:
- delete the local bootstrap data channel related attributes ( the "dcmap" attribute line containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10) from the received multiplexed bootstrap data channel media description and add the "a=3gpp-bdc-used-by:" attribute line containing "bdc-used-by" parameter set to value "sender" if the "dcmap" attribute line containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110 presents, if the DCSF indicates the media is to be de-multiplexed and the media instruction from the DCSF is to terminate and originate the media;
- generate and add the remote bootstrap data channel media description for the terminating UE (media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110 and "a=3gpp-bdc-used-by:" attribute with "bdc-used-by" parameter set to value "receiver"), i.e. remote bootstrap data channel between the originating network and the terminating UE, if the media instruction from the DCSF is to originate the media;
Upon the reception of an acknowledgement from the DCSF to the event notification, the IMS AS shall send the received SIP request with the modified SDP offer towards the terminating network.
Upon receipt of the 18x or 2xx response including SDP answer to the initial INVITE, re-INVITE or UPDATE request, the IMS AS shall notify the DCSF about corresponding session event or media change event and request the MF to update the media resource as specified in clause 9.3.2.2.1, clause 9.3.2.2.2, and clause 9.3.2.2.4. Based on the response from the MF, the IMS AS shall modify the SDP answer:
- delete the remote bootstrap data channel media description for the terminating UE (media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110 and "a=3gpp-bdc-used-by" attribute with "bdc-used-by" parameter set to value "receiver"), i.e. the remote bootstrap data channel between the originating network and terminating UE;
- add the local bootstrap data channel related attributes ( the "dcmap" attribute line containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10), and replace the IP address as well as the DC endpoint information with the media resource information allocated by the MF towards the originating UE, if the original media is multiplexed bootstrap data channel media description and the media instruction from the DCSF is to terminate and originate the media;
and send the response with the modified SDP answer towards to the originating UE.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.2.2.7.3 Application data channel multiplexing
|
When the IMS AS receives from the originating UE an initial INVITE, re-INVITE or UPDATE request with an SDP offer that contains a multiplexed application data channel media description, if the data channel multiplexing is supported and allowed, the IMS AS shall notify the DCSF as specified in clause 9.3.2.2.2.
Based on the instruction from the DCSF, the IMS AS shall request the MF to allocate data channel media resources as specified 3GPP TS 29.176 [19].
If DCSF determines not to demultiplex the multiplexed media as specified in 3GPP TS 29.175, the IMS AS shall follow the procedure of clause 9.3.2.2.2.2 to handle the application data channel media description and send the INVITE, re-INVITE or UPDATE request with the multiplexed application data channel media description in the SDP offer to the terminating network.
If the DCSF determines to demultiplex the multiplexed media, for the multiplexed media description, the IMS AS shall:
1) remove the parameters "adc-info" with the "adc-stream-id-endpoint" is set to "Server" in attribute "a=3gpp-req-app" line and the corresponding "a=dcmap" lines with the same "stream-id" in the multiplexed data channel media description;
2) if media instruction from DCSF is to originate a new media and include one existing media Id as the associated media Id in the instruction (i.e. the media identified by associated media Id is demultiplexed), generate and add a new media description for the new de-multiplexed data channel in the SDP offer; and
3) remove the "a=dcmap" lines and the related "a=3gpp-req-app" lines that are using separate media descriptions in bullet 2) in the original multiplexed media description.
Upon receipt of the 488 (Not Acceptable Here) response or 18x or 200 (OK) response to the INVITE, re-INVITE or UPDATE request and the multiplexed application data channel media is accepted, the IMS AS shall determine that the terminating network supports data channel multiplexing.
Upon receipt of the 488 (Not Acceptable Here) response or the 18x or 200 (OK) response in which the multiplexed application data channel media is rejected, the IMS AS shall:
1) notify the DCSF as specified in 3GPP TS 29.175 [x]; and
2) de-multiplex the application data channel media description as specified in the bullet 2) and 3) above and send the INVITE, re-INVITE or UPDATE request to the terminating network again.
Upon receipt of the 18x or 200 (OK) response from the terminating network to the INVITE, re-INVITE or UPDATE request with the demultiplexed data channel media in the SDP answer, the IMS AS shall multiplex the data channel media descriptions in the SDP answer using the original multiplexed media id in the SDP offer and send the 18x or 200 (OK) response to the originating UE.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3 Terminating side
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.1 Procedures at the UE
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.1.1 General
|
The terminating UE can also setup or terminate data channels during the session modification.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.1.2 IMS bootstrap data channel setup in conjunction with MMTel session setup
|
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 IETF RFC 5688 [5] for supported streaming media type with +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4] 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 3GPP TS 24.275 [11] and EFIMSDCI file specified in 3GPP TS 31.103 [30] or 3GPP TS 31.102 [31], and the terminating UE:
a) accepts the offered bootstrap data channel(s), it shall generate the SDP answer based on the 3GPP TS 26.114 [4] and IETF RFC 8864 [14]; or
b) 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 3GPP TS 24.275 [11] and the DC_allowed leaf indicates that IMS data channel:
a) is allowed and if the terminating UE accepts the offered bootstrap data channel(s), it shall generate the SDP answer based on the 3GPP TS 26.114 [4] and IETF RFC 8864 [14]; or
b) 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 3GPP TS 31.103 [30] or 3GPP TS 31.102 [31] and the IMS DC Establishment Indication indicates that IMS data channel:
a) is allowed and if the terminating UE accepts the offered bootstrap data channel(s), it shall generate the SDP answer based on the 3GPP TS 26.114 [4] and IETF RFC 8864 [14]; or
b) 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.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.1.3 IMS data channel setup in conjunction with MMTel session modification
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.1.3.1 IMS bootstrap data channel establishment
|
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.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.1.3.2 IMS application data channel establishment
|
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 3GPP TS 26.114 [4] and IETF RFC 8864 [14].
If the terminating UE wants to setup an application data channel, the procedure defined in clause 9.3.2.1.3.2 applies.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.1.4 Closing IMS application data channel in conjunction with MMTel session modification
|
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 IETF RFC 8864 [14].
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.
NOTE: The application data channel termination during the session modification does not impact the ongoing audio, video or other data channels within the MMTel session.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.1.5 Closing IMS data channel in conjunction with MMTel session release
|
When the UE releases an MMTel session that has associated bootstrap and application data channels, the UE shall apply procedures defined in 3GPP TS 24.229 [9] clause 5.1.5 and shall close bootstrap and application data channels.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.1.6 Support of IMS standalone data channel session
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.1.6.1 Void
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.1.6.2 Void
|
9.3.3.1.6.2A Adding application data channel during standalone IMS data channel session establishment
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 3GPP TS 26.114 [4] and IETF RFC 8864 [1].
NOTE 1: When receiving the incoming INVITE request, the UE can alert the user that there is a standalone data channel establishing based on the UE's implementation for user consent.
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 3GPP TS 26.114 [4] 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:
a) 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 3GPP TS 26.114 [4] and IETF RFC 8864 [1] and return the 200(OK) response to the UPDATE request; and
4) return 200 (OK) response to the INVITE request; or
b) 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 3GPP TS 26.114 [4] and IETF RFC 8864 [1] and return the 200(OK) response to the UPDATE request; and
3) return 200 (OK) response to the INVITE request.
NOTE 2: Based on the UE's implementation for user consent, the UE can alert the user that data channel is downloaded.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.1.6.3 Combined standalone bootstrap data channel and application data channel establishment
|
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:
a) has not been downloaded, the UE:
1) shall generate SDP answer for the data channel as per 3GPP TS 26.114 [4] and IETF RFC 8864 [1] 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 3GPP TS 23.228 [3] clause AC.10.2.3 and return a 183 (Session Progress) response with the generated SDP answer to the initial INVITE request;
NOTE 1: When receiving the incoming INVITE request, the UE can alert the user that there is a standalone data channel establishing based on the UE's implementation for user consent.
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 3GPP TS 26.114 [4] and IETF RFC 8864 [1] and return the 200(OK) response to the UPDATE request;
- return 200 (OK) to the INVITE request; or
b) has been downloaded, the UE shall:
1) generate the SDP answer that contains both the bootstrap data channel and application data channel as per 3GPP TS 26.114 [4] and IETF RFC 8864 [1] 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.
NOTE 2: Based on the UE's implementation for user consent, the UE can alert the user that data channel is downloaded.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.1.6.4 Adding video/audio media to standalone IMS data channel session
|
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 3GPP TS 26.114 [4].
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.1.6.5 Removing video/audio media from IMS data channel session
|
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 3GPP TS 26.114 [4].
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.1.7 Enforcement of 3GPP SIP-Based 3GPP PS Data Off Exempt Services
|
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:
a) if the initial SDP offer contained only IMS data channel media description(s), the UE shall send a 403 (Forbidden) response; or
b) 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
2) otherwise, the procedure defined in clause 9.3.2.1.7 applies.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.1.8 Support of the data channel multiplexing
|
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 3GPP TS 26.114 [4] 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 3GPP TS 26.114 [4] and IETF RFC 8864 [14];
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 3GPP TS 26.114 [4] and IETF RFC 8864 [14].
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.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.2 Procedures at the serving IMS AS for the terminating UE
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.2.1 IMS bootstrap data channel establishment in conjunction with MMTel session setup
|
Upon receipt of a SIP initial INVITE request with the SDP offer including IMS data channel media descriptions from the originating network, if the IMS AS determined that the terminating registered UE:
1) supports IMS data channel capabilities and is authorized to use IMS data channel, the IMS AS shall notify the DCSF about a session establishment request event, with a calling identity set to the value of the P-Asserted-Identity header field and a called identity set to the value of Request URI of the received initial INVITE request, and shall not send a INVITE request to the S-CSCF until receiving an acknowledgement from the DCSF. Based on the received Media instruction set from the DCSF, the IMS AS shall select the MF and request the MF to allocate required data channel media resources. Based on the response of the reserved media resource from the MF, the IMS AS shall:
- delete the remote bootstrap data channel media description for the originating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110 and "a=3gpp-bdc-used-by" attribute with "bdc-used-by" parameter set to value "sender"), i.e. the remote bootstrap data channel between originating UE and terminating network in the SDP offer;
- replace the IP address represented in the "c=" line, the UDP port number in the "m=application" line as well as the DC endpoint information represented as the attribute lines including the "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" line in the remote bootstrap data channel media description for the terminating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110 and "a=3gpp-bdc-used-by" attribute with "bdc-used-by" parameter set to value "receiver"), i.e. the remote bootstrap data channel between terminating UE and originating network, with the media resource information for the termination towards the terminating UE if the media in anchored on the MF; and
- generate and add the local bootstrap data channel media description for the terminating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10), i.e. the local bootstrap data channel between the terminating network and terminating UE to the SDP offer.
upon the reception of a successful acknowledgement from the DCSF to the session establishment request event notification, the IMS AS shall send the initial INVITE request with the modified SDP offer via the S-CSCF towards the terminating registered UE of the served user, which support the IMS data channel capabilities; or
2) does not support IMS data channel capabilities or is not authorized to use IMS data channel, then based on the operator policy the IMS AS shall determine whether to remove from the SDP offer media lines related to the IMS data channels:
a) if the operator policy indicates removal of media lines related to the IMS data channels, the IMS AS shall not trigger the DC media resource reservation and the IMS AS shall remove from the received SDP offer media lines describing the bootstrap data channel(s) i.e.:
- "dcmap" attribute lines containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0, 10, 100 and 110; and
- if present, "a=3gpp-bdc-used-by:" attribute lines,
associated with 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". If there are no other "dcmap" attribute lines that contain a subprotocol parameter set to value other than "http", the IMS AS shall remove any other SDP media attribute lines associated with that m line e.g., "sctp-port", "max-message-size", "tls-id", "a=setup", "a=3gpp-qos-hint" SDP attribute lines. The IMS AS shall send the SIP initial INVITE request with the modified SDP offer to the S-CSCF towards the terminating registered UE of the served user.
Upon receipt of a SIP initial INVITE request with the SDP offer not including IMS data channel media descriptions from the originating network, if the IMS AS determined that the terminating registered UE supports IMS data channel capabilities and is authorized to use IMS data channel, the IMS AS shall notify the DCSF of a session establishment request event and shall not send a INVITE request to the S-CSCF until receiving an acknowledgement from the DCSF. Based on the received media instruction set from the DCSF, the IMS AS shall select an MF and request the MF to allocate required data channel media resources.
Based on the response of the reserved media resource from the MF, the IMS AS shall generate and add the local bootstrap data channel media description for the terminating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10), i.e. the local bootstrap data channel between the terminating network and terminating UE to the SDP offer. Upon the reception of a successful acknowledgement from the DCSF to the session establishment request event notification, the IMS AS shall send the initial INVITE request with the modified SDP offer via the S-CSCF towards the terminating registered UE of the served user, which support the IMS data channel capabilities. If no media instruction received from the DCSF or no acknowledgement from the DCSF received, the IMS AS shall forward the initial INVITE request from the originating network (i.e. without IMS data channel media descriptions in the SDP offer) to the S-CSCF.
Upon receipt of the 18x or 2xx response on the initial INVITE message including the SDP answer which includes the data channel media description, the IMS AS shall notify the DCSF about corresponding session event (session establishment progress (i.e. receiving the 183 (Session Progress) response ), session establishment alerting (i.e. receiving the 180 (Ringing) response) or session establishment success (i.e. receiving the 200 (OK) response on the INVITE request) event) and shall request the MF to update the media resources. Based on the response from the MF, the IMS AS shall:
- generate and add the remote bootstrap data channel media description for the originating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110 and "a=3gpp-bdc-used-by" attribute with "bdc-used-by" parameter set to value "sender") in the SDP answer, i.e. the remote bootstrap data channel between originating UE and terminating network;
- replace the IP address represented in the "c=" line, the UDP port number in the "m=application" line as well as the DC endpoint information represented as the attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" line within the remote bootstrap data channel media description for the terminating UE (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110 and "a=3gpp-bdc-used-by" attribute with "bdc-used-by" parameter set to value "receiver"), i.e. the remote data channel between terminating UE and originating network, with the DC endpoint information for the termination towards the originating network allocated by the MF; and
- delete the bootstrap data channel media description (the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10) in the SDP answer, i.e. the bootstrap data channel between terminating UE and terminating network.
Upon receipt of the 18x or 2xx response including the SDP answer which only contains the data channel media description for the bootstrap data channel between terminating UE and terminating network, the IMS AS shall notify the DCSF, request the MF to update the media resources as above and delete this bootstrap data channel media description (i.e. the media line with the "dcmap" attribute containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10) in the SDP answer.
Upon the reception of an acknowledgement from the DCSF to the corresponding notification, the IMS AS shall include the modified SDP answer for data channel to originating network and send the 18x or 2xx response on the initial INVITE request to the S-CSCF.
Upon receipt of a CANCEL request the initial INVITE request, the IMS AS shall notify the DCSF about the session establishment cancellation, request the MF to release the corresponding data channel media resources, and forward the CANCEL request to the S-CSCF towards the terminating UE.
Upon receipt of a 4xx, 5xx or 6xx response on the initial INVITE request from the terminating UE, the IMS AS shall notify the DCSF about session establishment failure, and request MF to release the data channel media resources.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.2.2 MMTel session modification
| |
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.2.2.1 IMS bootstrap data channel establishment
|
If the IMS AS received from the originating network a re-INVITE request with the SDP offer containing data channel media description for the bootstrap data channel establishment, if the IMS AS determined that the terminating registered UE:
- supports IMS data channel capabilities and is authorized to use IMS data channel, the IMS AS shall notify the DCSF about the media change request, with a calling identity set to the value of the P-Asserted-Identity header field and a called identity set to the value of Request URI of the initial INVITE request received during MMTel session establishment. If the media instruction from the DCSF is:
a) to reject the bootstrap data channel, the IMS AS shall send a 488 (Not Acceptable Here) to the originating network;
b) in other cases, based on the instruction from DCSF, the IMS AS shall request the MF to reserve the media resources and modify the data channel media description in the SDP offer and send the re-INVITE request as per clause 9.3.3.2.1. Upon receipt of the 183 (Session Progress) or 200 (OK) response to the re-INVITE request, the IMS AS shall send notify the DCSF about the media change success if the data channel media is accepted or media change failure if the data channel media is rejected and modify the data channel media description in the SDP answer and send the 183 (Session Progress) or 200 (OK) response to S-CSCF as per clause 9.3.2.2.1. Upon receipt of a CANCEL request to the re-INVITE request, the IMS AS shall notify the DCSF about the media change cancellation, request the MF to release the corresponding data channel media resources, and forward the CANCEL request as per clause 9.3.2.2.1. Upon receipt of a 4xx, 5xx or 6xx response on the re-INVITE request, the IMS AS shall notify the DCSF about the media change failure and forward the response to the originating network; and
- does not support IMS data channel capabilities or is not authorized to use IMS data channel, the procedure defined in clause 9.3.3.2.1 applies.
If the IMS AS received from the served user a re-INVITE request with the SDP offer containing data channel media description for the bootstrap data channel establishment, the procedure of the IMS AS in the originating network on receipt of a re-INVITE request from the originating UE defined in clause 9.3.2.2.2.1 applies.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.2.2.2 IMS application data channel establishment
|
Upon receipt of a re-INVITE request with the SDP offer including new application data channel media descriptions (the media lines with the "dcmap" attribute containing "stream-id" parameter set to values starting at 1000) along with the video, audio, and bootstrap data channel media descriptions from the originating network, the IMS AS shall notify the DCSF about the media change request. If the media instruction from the DCSF is
- to reject all the data channel medias in this request, the IMS AS shall send a 488 (Not Acceptable Here) response to the originating network and other medias are not updated; and
- in other cases, the IMS AS shall request MF to update the media resources. Based on the response on the data channel media resource update from the MF as specified in 3GPP TS 29.176 [19] and media instruction from DCSF as specified in 3GPP TS 29.175 [18], the IMS AS shall:
1) delete the data channel media description (media line with the "dcmap" attribute containing "stream-id" parameter set to the values starting at 1000 and "a=3gpp-req-app " attribute with "endpoint" parameter set to value "server") if the media instruction from DCSF is to terminate the media;
2) delete the data channel media description if the media instruction from DCSF is to reject the media as specified in 3GPP TS 29.175 [18] and there are other medias to be established;
3) replace the IP address represented in the "c=" line, the UDP port number in the "m=application" line in the data channel media description in the SDP offer with the media resource information for the termination towards the terminating UE allocated by the MF if the media instruction from DCSF is to terminate and originate the media, and also replace the DC endpoint information represented as the attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" when the media proxy configuration is HTTP proxy; and
4) generate and add a data channel media description (media line with the "dcmap" attribute containing "stream-id" parameter set to values starting at 1000 and "a=3gpp-req-app " attribute with "endpoint" parameter set to value "server") by using the DC stream information provided by the DCSF in the attribute lines "a=dcmap" and "a=3gpp-req-app", DC endpoint information of the DC AS provided by the DCSF in the attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup", IP address and UDP port number allocated on the termination towards to the terminating UE on the MF in the "c=" line and "m=application" when the media proxy configuration is UDP proxy, or using the DC stream information provided by the DCSF in the attribute lines "a=dcmap" and "a=3gpp-req-app" and the IP address, UDP port number and DC endpoint information (e.g. tlsId, sctp-port) allocated on the termination towards to the terminating UE on the MF in the other attribute lines above when the media proxy configuration is HTTP proxy, if the media instruction from DCSF is to originate a new media as specified in 3GPP TS 29.175 [18].
- an existing application data channel media description in which the new "a=dcmap" line containing the "stream-id" parameter value set to values starting at 1000 is added, the IMS AS shall notify the DCSF about media change request, and request MF to update the media resource if the media instruction from DCSF is to update the media.
The IMS AS shall send the re-INVITE request to the S-CSCF with the modified SDP offer including the modified application data channel media description or the original application data channel media description if no media instruction received from DCSF as well as the media descriptions of established video, audio and bootstrap data channels, to the terminating UE.
Upon receipt of the 183 (Session Progress) or 200 (OK) response on the re-INVITE request with the SDP answer which contains media description of the requested application data channel from the terminating UE,
- if the application data channel is accepted, the IMS AS shall notify DCSF about the media change success and request the MF to update the media resources. Based on the response of the MF, the IMS AS shall:
a) generate and add a data channel media description in the SDP answer by using DC endpoint information of the DC AS provided by the DCSF in the attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" and the IP address and the UDP port number allocated on the termination towards to the originating network on MF in the lines "c=" and "m=application", or using the IP address, the UDP port number and the DC endpoint information (e.g. tlsId, sctp-port) allocated on the termination towards to the originating network on the MF in the attribute lines above when the media proxy configuration is HTTP proxy, if the instruction from the DCSF is to terminate the media;
b) add the rejected media description and set the port number to 0 in the "m=application" line if the instruction from the DCSF is to reject the media and there are other medias to be established;
c) replace the IP address represented in the "c=" line, the UDP port number in the "m=application" line in the media description in the SDP answer with the media resource information on the termination towards to the originating network allocated by the MF if the instruction from the DCSF is to terminate and originate the media and also replace the DC endpoint information as attribute lines "a=tlsId", "a=sctp-port", "a=fingerprint" and "a=setup" when the media proxy configuration is HTTP proxy; and
d) delete the media description in the SDP answer if the instruction from the DCSF is to originate a new media;
and send the 183 (Session Progress) or 200 (OK) response with the modified SDP answer on the re-INVITE request to the S-CSCF towards to the originating network after the receipt of an acknowledgement from the DCSF to the corresponding notification; or
- if the application data channel is rejected, the IMS AS shall notify the DCSF about media change failure and request the MF to release the media resources. The IMS AS shall send the 183 (Session Progress) or 200 (OK) response to S-CSCF with the modified SDP answer for the requested application data channel as well as the media descriptions of established video, audio, and bootstrap data channels after the receipt of an acknowledgement from the DCSF to the corresponding notification.
Upon receipt of a CANCEL request to the re-INVITE request, the IMS AS shall notify the DCSF about the media change cancellation, request the MF to release the corresponding data channel media resources and forward the CANCEL request to the S-CSCF towards the terminating UE.
Upon receipt of a 4xx, 5xx or 6xx response on the re-INVITE request from the terminating UE, the IMS AS shall notify the DCSF about media change failure, request the MF to release the corresponding data channel media resources and forward the response to the originating network.
Upon receiving the re-INVITE request from the terminating UE to setup an application data channels and the corresponding response form the originating network, the procedure in clause 9.3.2.2.2.2 applies.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.2.2.3 Closing application data channel
|
Upon receipt of the re-INVITE request with an SDP offer which contains an existing application data channel media description in which the UDP port number is set to 0, the IMS AS shall notify the DCSF about media change request, and request the MF to release the corresponding media resource if the media instruction from DCSF is to delete the media.
Upon receipt of the re-INVITE request with an SDP offer which contains an existing application data channel media description in which an existing "a=dcmap" line is removed, the IMS AS shall notify the DCSF about media change request, and request MF to update the media resource if the media instruction from DCSF is to update the media.
Upon receipt of the 200 (OK) response on the re-INVITE message with the SDP answer, the procedure in clause 9.3.3.2.2.2 applies.
Upon receiving the re-INVITE request from the terminating UE to close an application data channels and the corresponding 200 (OK) response form the originating network, the procedure in clause 9.3.2.2.2.3 applies.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.2.2.4 Network-determined closing of bootstrap and application data channel
|
If the IMS AS determines to terminate the established bootstrap data channels and application data channels to the originating UE during the session modification (e.g. due to supplementary service procedures as specified in clause 10.19.2), the IMS AS shall send a re-INVITE request to the originating network with the subsequent SDP offer and set the UDP port number of the data channel media descriptions to zero.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.2.3 MMTel session release
|
Upon initiation or receipt of a BYE request matching an existing MMTel session with IMS data channel, the procedure defined in clause 9.3.2.2.3 applies.
|
065ca81b6362758a2aaa311cba0fc48d
|
24.186
|
9.3.3.2.4 Support of IMS standalone data channel session
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.