hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
162c3f0c36a54745dc509a8130708d2d | 22.104 | 9.2 Requirements | Subject to regulatory requirements and operator policy, the 5G system shall support a mechanism by which an MNO can identify the ability of the MNO's infrastructure to continue operation despite a lack of electrical supply service, specifying which physical regions would be affected in terms of physical topology and th... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 ... |
b3bbdb8d26c45089a67aa06bf888a05c | 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.
-... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 3 Definitions of terms, symbols and abbreviations
| |
b3bbdb8d26c45089a67aa06bf888a05c | 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... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 ... |
b3bbdb8d26c45089a67aa06bf888a05c | 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.
|
b3bbdb8d26c45089a67aa06bf888a05c | 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 respec... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 5 Functional entities
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 5.1 General
| This clause specifies the functionalities of the functional entities for IMS data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 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 suppor... |
b3bbdb8d26c45089a67aa06bf888a05c | 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), ... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 6 Operational requirements
| |
b3bbdb8d26c45089a67aa06bf888a05c | 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.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 7 Basic communication
| |
b3bbdb8d26c45089a67aa06bf888a05c | 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 accor... |
b3bbdb8d26c45089a67aa06bf888a05c | 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.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 8 IMS data channel applications
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 8.1 Procedures at the UE
| |
b3bbdb8d26c45089a67aa06bf888a05c | 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... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 originating UE did not download the data channel application, the UE shall establish an IMS session with o... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 8.2 Procedures at the IMS AS
| |
b3bbdb8d26c45089a67aa06bf888a05c | 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=3gp... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 request 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 standa... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9 Signalling Procedures
| |
b3bbdb8d26c45089a67aa06bf888a05c | 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 bo... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.2 IMS data channel capability negotiation
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.2.1 IMS data channel capability negotiation during IMS initial registration
| |
b3bbdb8d26c45089a67aa06bf888a05c | 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 con... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 in... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.2.2 IMS data channel capability negotiation during IMS re-registration
| |
b3bbdb8d26c45089a67aa06bf888a05c | 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 +si... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 in... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.2.3 IMS data channel capability indication during IMS session establishment and modification
| |
b3bbdb8d26c45089a67aa06bf888a05c | 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 RF... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3 MMTel session procedures
| |
b3bbdb8d26c45089a67aa06bf888a05c | 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.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2 Originating side
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.1 Procedures at the UE
| |
b3bbdb8d26c45089a67aa06bf888a05c | 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 objec... |
b3bbdb8d26c45089a67aa06bf888a05c | 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-datachan... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.1.3 IMS data channel setup in conjunction with MMTel session modification
| |
b3bbdb8d26c45089a67aa06bf888a05c | 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 ... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 th... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 o... |
b3bbdb8d26c45089a67aa06bf888a05c | 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.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.1.6 Support of standalone data channel
| |
b3bbdb8d26c45089a67aa06bf888a05c | 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 c... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 boots... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 b... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 SD... |
b3bbdb8d26c45089a67aa06bf888a05c | 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.
|
b3bbdb8d26c45089a67aa06bf888a05c | 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.
|
b3bbdb8d26c45089a67aa06bf888a05c | 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 ... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 ... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2 Procedure at the IMS AS
| |
b3bbdb8d26c45089a67aa06bf888a05c | 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.
I... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.2 MMTel session modification
| |
b3bbdb8d26c45089a67aa06bf888a05c | 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... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 de... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 spec... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 (e.g., due to supplementary service procedures as specified in clause 10.19.2) during the session modification, the procedure defined in clause 9.3.3.2.2.4 applies.
NOTE: This clause define... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.2.6 Network-initiated data channel termination based on the request from the trusted AF
| 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 requested application d... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 ch... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.4 Support of standalone IMS data channel session
| |
b3bbdb8d26c45089a67aa06bf888a05c | 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 I... |
b3bbdb8d26c45089a67aa06bf888a05c | 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... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 re... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.4.4 Combined 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 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 procedu... |
b3bbdb8d26c45089a67aa06bf888a05c | 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.2... |
b3bbdb8d26c45089a67aa06bf888a05c | 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... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.2.2.7 Handling of data channel multiplexing
| |
b3bbdb8d26c45089a67aa06bf888a05c | 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 rece... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 ... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 o... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3 Terminating side
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.1 Procedures at the UE
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.1.1 General
| The terminating UE can also setup or terminate data channels during the session modification.
|
b3bbdb8d26c45089a67aa06bf888a05c | 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 3... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.1.3 IMS data channel setup in conjunction with MMTel session modification
| |
b3bbdb8d26c45089a67aa06bf888a05c | 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 t... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 d... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 applicati... |
b3bbdb8d26c45089a67aa06bf888a05c | 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.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.1.6 Support of standalone IMS data channel session
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.1.6.1 Void
| |
b3bbdb8d26c45089a67aa06bf888a05c | 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 bootstrap data channel, the UE shall return a 183 (Session Progress) ... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 n... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 standalone IMS 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]... |
b3bbdb8d26c45089a67aa06bf888a05c | 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].
|
b3bbdb8d26c45089a67aa06bf888a05c | 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 res... |
b3bbdb8d26c45089a67aa06bf888a05c | 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-... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2 Procedures at the serving IMS AS for the terminating UE
| |
b3bbdb8d26c45089a67aa06bf888a05c | 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 ... |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.2 MMTel session modification
| |
b3bbdb8d26c45089a67aa06bf888a05c | 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 chan... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 ne... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 fro... |
b3bbdb8d26c45089a67aa06bf888a05c | 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 s... |
b3bbdb8d26c45089a67aa06bf888a05c | 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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.