hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.4 Support of standalone IMS data channel session
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.4.0 General
| If the IMS AS received from the originating network:
- an initial INVITE request with the SDP offer containing only data channel media description;
- 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 403 (Forbidden) to the originating network to reject the session or to reject the media change request.
If the IMS AS received from the terminating UE:
- an initial INVITE request with the SDP offer containing only data channel media description;
- 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 requirements in clause 9.3.2.2.4.1 applies.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.4.1 Void
| 9.3.3.2.4.1A Subsequent standalone bootstrap data channel and application data channel establishment
Upon receipt of the initial INVITE request from the originating network towards a terminating UE with the SDP offer which only includes bootstrap data channels and the 183 (Session Progress) response to the INVITE request with the SDP answer, from the terminating UE, the IMS AS shall follow the procedure in clause 9.3.3.2.1 to handle the bootstrap data channel media.
Upon receipt of the UPDATE request from the originating network 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 from the terminating UE, 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 of the 200 (OK) response to the initial INVITE request from the terminating UE, the IMS AS shall notify the DCSF about the session establishment success event and forward the 200 (OK) response to the originating network.
Upon receipt of a 4xx, 5xx or 6xx response to the initial INVITE request from the terminating UE, the IMS AS shall notify the DCSF about session establishment failure, request MF to release the data channel media resources and forward the response to the originating network.
Upon receipt of a 4xx, 5xx or 6xx response to the UPDATE 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.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.4.2 Void
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.4.3 Combined standalone bootstrap data channel and application data channel establishment
| Upon receipt of the initial INVITE request from the originating network to a terminating UE with 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 UE, the IMS AS shall follow the procedure in clause 9.3.3.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 of the UPDATE request from the originating network 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 from the terminating UE, the IMS AS shall follow the procedure in clause 9.3.3.2.2.2 to handle the application data channel media.
Upon receipt of the 200 (OK) response to the initial INVITE request from the terminating UE, the IMS AS shall notify the DCSF about the session establishment success event and forward the 200 (OK) response to the originating network.
Upon receipt of a 4xx, 5xx or 6xx response to the initial INVITE request from the terminating UE, the IMS AS shall notify the DCSF about session establishment failure, request the MF to release the data channel media resources and forward the response to the originating network.
Upon receipt of a 4xx, 5xx or 6xx response to the UPDATE 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.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.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":
- when a re-INVITE request to the served UE is received, if the SDP offer from the re-INVITE request contains only the data channel media descriptions, the IMS AS shall:
a) send a 403 response to the originating side;
b) send BYE request towards the originating and terminating side;
c) 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
d) if the MF already allocated IMS data channel media resources, shall request the MF to release the allocated data channel media resource; or
- when an SDP offer from the received re-INVITE request contains other media description(s) in addition to data channel media descriptions, shall remove the data channel media descriptions from the received SDP offer before sending re-INVITE request to the served UE, and set the port number of the "m=" lines for the data channel media description as zero in the SDP answer of the response to the corresponding re-INVITE request towards the originating side.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.6 Handling of data channel multiplexing
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.6.1 General
| When the IMS AS receives from the originating network an initial INVITE with the SDP offer containing only the multiplexed data channel media description(s), if the data channel multiplexing is not supported by the terminating network, the IMS AS shall return 488 (Not Acceptable Here) response containing an SDP message body.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.6.2 Bootstrap data channel multiplexing
| When the IMS AS receives from the originating network an initial INVITE, a re-INVITE or an UPDATE request with an SDP offer that contains a multiplexed bootstrap media description from the originating network, if the data channel multiplexing is supported by the terminating network and the served UE, the IMS AS shall select and notify the DCSF as specified in clause 9.3.3.2.1, clause 9.3.3.2.2, and clause 9.3.3.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 media description which contains the remote bootstrap data channel in which the "dcmap" attribute line containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110 and the "a=3gpp-bdc-used-by:" attribute line containing "bdc-used-by" parameter set to value "sender", if the media instruction from the DCSF is to delete the media;
- generate a multiplexed bootstrap data channel media description by adding the local bootstrap data channel related attributes for the terminating UE (i.e. the bootstrap data channel between the terminating network and terminating UE related attributes (the "dcmap" attribute line containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10) in the media description which contains the remote bootstrap data channel for the terminating UE (the "dcmap" attribute line containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110), if the DCSF indicates the media is to be multiplexed and the media instruction from the DCSF is to terminate and 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 UE.Upon receipt of the 18x or 2xx response including SDP answer to the initial INVITE, re-INVITE or UPDATE request from the served UE, 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.3.2.1, clause 9.3.3.2.2, and clause 9.3.3.2.4. Based on the response from the MF, the IMS AS shall modify the SDP answer:
- 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;
- delete the local bootstrap data channel related attributes for the terminating UE (i.e. the bootstrap data channel between the terminating network and terminating UE related attributes (the "dcmap" attribute line containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 0 and 10) in the received multiplexed bootstrap data channel media description which contains the remote bootstrap data channel for the terminating UE (the "dcmap" attribute line containing a subprotocol parameter set to "http" and "stream-id" parameter set to values 100 and 110), and replace the IP address as well as the DC endpoint information with the media resource information allocated by the MF towards the originating network;
and send the response with the modified SDP answer towards to the originating network.
When the IMS AS receives from the originating network an initial INVITE, a re-INVITE or an UPDATE request with an SDP offer that contains a multiplexed bootstrap media description from the originating network, if the data channel multiplexing is not supported by the served UE, the IMS AS shall follow the procedures as specified in clause 9.3.3.2.1, clause 9.3.3.2.2, and clause 9.3.3.2.4.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.6.3 Application data channel multiplexing
| When the IMS AS receives from the originating network 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 it determines the terminating UE:
- supports the data channel multiplexing, the procedure in clause 9.3.3.2.2 applies; or
- does not support the data channel multiplexing, the IMS AS shall de-multiplex the application data channel media based on the instruction of DCSF, i.e.
1) generate and add new media descriptions for the de-multiplexed data channel not using the same media Id as the original multiplexed media in the SDP offer, and
2) remove the "a=dcmap" lines and the related "a=3gpp-req-app" lines that are described in separate media descriptions as specified in bullet 1) in the original multiplexed media description,
and send the re-INVITE with the de-mulitplexed application data channel media description to the terminating UE.
Upon receipt of the 18x or 200 (OK) response from the terminating UE to the INVITE, re-INVITE or UPDATE request with demultiplexed data channel media description in 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 network.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.3.3.2.7 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 network, if the interworking required event subscribed and the IMS AS determines that the originating UE is a non-DC capable UE as the Contact header field does not 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], 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 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].
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4 Abnormal cases
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.1 General
| Abnormal cases on IMS data channel include the following:
- The IMS AS has sent a data channel resource reservation/update request and does not receive a response to that request.
- The IMS AS has sent a data channel resource reservation/update request, and receives an error response to that request due to no sufficient data channel resource.
- The IMS AS hasn't received QoS parameters when generating SDP offer or answer for the application data channel media.
- The IMS AS has notified a session event to the DCSF and does not receive a response or receives a failure.
- The re-INVITE request collision in the IMS AS during IMS data channel establishment and closing.
The failures during IMS data channel establishment and maintenance shall not impact any other ongoing media which are associated with the same IMS session (e.g. audio, video, etc.).
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.2 No response on DC2 interface
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.2.1 Actions at the IMS AS
| If the IMS AS does not receive a response to a bootstrap data channel resource reservation/update request, the IMS AS shall:
- remove the data channel media description from the SDP offer for the INVITE/re-INVITE request; and
- set the port number of the "m=" lines for data channel as zero in the SDP answer of the response to the INVITE/re-INVITE request.
If the IMS AS does not receive a response to an application data channel resource reservation/update request, the IMS AS shall:
- remove from the SDP offer for the re-INVITE request:
1) the "a=dcmap" line associated to this requested application data channel; or
2) the data channel media description containing this requested application data channel if no other "a=dcmap" attribute line existed in this media description; and
- set the port number of the "m=" lines for the data channel media description containing this requested application data channel as zero in the SDP answer of the response to the re-INVITE request in the case 2).
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.3 Insufficient data channel resource
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.3.1 Actions at the IMS AS
| If the IMS AS receives an error response message to a bootstrap data channel resource reservation/update request, the IMS AS shall:
- remove the data channel media description from the SDP offer for the INVITE/re-INVITE request;
- continue the ongoing session procedure; and
- set the port number of the "m=" lines for data channel as zero in the SDP answer of the response to the INVITE/re-INVITE request.
If the IMS AS receives an error response message to an application data channel resource reservation/update request, the IMS AS shall:
- remove from the SDP offer for the re-INVITE request:
1) the "a=dcmap" line associated to this requested application data channel; or
2) the data channel media description containing this requested application data channel if no other "a=dcmap" attribute line existed in this media description; and
- set the port number of the "m=" lines for the data channel media description containing this requested application data channel as zero in the SDP answer of the response to the re-INVITE request in the case 2).
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.4 No response or failure response on DC1 interface
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.4.1 Actions at the IMS AS
| If the IMS AS does not receive a response to a session event notification or receives a failure response to a session event notification, the IMS AS shall:
- in the case of notifying IMS data channel session establishment request or media change request on bootstrap data channel setup, remove the IMS data channel SDP media description from the SDP offer for the INVITE/re-INVITE request and continue the ongoing session procedure;
- in the case of notifying media change request on application data channel setup:
a) remove from the SDP offer for the re-INVITE request:
1) the "a=dcmap" line associated to this requested application data channel; or
2) the data channel media description containing this requested application data channel if no other "a=dcmap" attribute line existed in this media description; and
b) continue the ongoing session procedure;
- set the port number of the "m=" lines for IMS data channel as zero in the SDP answer of the response to the INVITE/re-INVITE request; and
- in the case of notifying IMS data channel session establishment failure, media change failure, and session termination request, continue the ongoing session procedure.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.5 QoS parameters not received.
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.5.1 Actions at the IMS AS
| If new SDP offer generated by the UE includes the application data channel media description containing "a=3gpp-req-app" attribute with "endpoint" parameter set to "server" and:
- "a=3gpp-qos-hint" attribute but no QoS parameters received in the media instruction from the DCSF, the IMS AS of the served UE shall generate "a=3gpp-qos-hint" attribute with the default values based on the configuration, if available; or
- updated "a=3gpp-qos-hint" attribute but no QoS parameters received in the media instruction from the DCSF, the IMS AS of the served UE shall generate "a=3gpp-qos-hint" attribute with the values previously negotiated within SDP offer and SDP answer;
for the corresponding application data channel media description before forwarding the SDP offer and the associated SDP answer.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.6 Re-INVITE request collision
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 9.4.6.1 Actions at the IMS AS
| The IMS AS shall handle re-INVITE request collisions as specified in 3GPP TS 24.229 [9] with the clarification in this subclause.
When a re-INVITE request including an SDP offer containing IMS data channel media description is received while a re-INVITE is progressing as per 9.3.2.2.2 and 9.3.3.2.2, or while a re-INVITE has already been sent out, the IMS AS shall not notify the DCSF about the media change request including the information of the received re-INVITE request and shall return 491 (Request Pending) response to the received re-INVITE request.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10 Interaction with supplementary services
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.1 Originating Identification Presentation (OIP)
| No interaction with IMS data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.2 Terminating Identification Presentation (TIP)
| No interaction with IMS data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.3 Originating Identification Restriction (OIR)
| No interaction with IMS data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.4 Terminating Identification Restriction (TIR)
| No interaction with IMS data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.5 Message Waiting Indication (MWI)
| No interaction with IMS data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.6 Conferencing (CONF)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.6.1 Procedure at UE
| When a user is participating in two or more SIP sessions, established SIP session's data channel media streams are specific to each SIP session. The user is handling multiple SIP sessions, but only one SIP session shall be active at a time.
The user (conference creator) creates SIP session with the conference focus by sending an INVITE request as described in clause 5.3.1.3 3GPP TS 24.147 [15], and a new SIP session is established between the user (conference creator) and the conference focus.
The user (conference creator) decides and perform the procedures as described in clause 5.3.1.4 3GPP TS 24.147 [15] for inviting a user (conference participant) to a conference by sending an REFER request for each of the active sessions that are requested to be joined to the three-way session, and new SIP sessions are established between the users (conference participants) and the conference focus.
At the establishment of the SIP session with the conference focus, the conference creator and conference participants, shall terminate the existing call session including data channel media streams as per 3GPP TS 24.147 [15] and clause 9.3.
If the user (conference creator or conference participant) wants to use IMS data channel in the SIP session established with the conference focus, the user shall follow procedure specified in clause 9.3.2.1.
NOTE: In this Release of the present document an IMS data channel establishment with the conference focus is not supported.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.6.2 Procedure at IMS AS serving the user
| On reception of the SIP INVITE request in conjunction with IMS data channel setup as per clause 9.3.2.1.2 and request URI set to the conference factory URI in accordance with clause 5.3.1.3 3GPP TS 24.147 [15], the IMS AS serving the user shall follow procedure specified in clause 9.3.2.2.1.
NOTE 1: The served user can be a conference creator or conference participant.
NOTE 2: For each served user which is authorized to use IMS data channel a local bootstrap data channel will be established (i.e., IMS data channels with stream ID 0 or 10 between the user and the DCSF serving the user).
NOTE 3: In this Release of the present document an IMS data channel establishment with the conference focus is not supported, therefore the data channels with the conference focus will not be established. The IMS AS will discover this upon reception of the response to SIP INVITE request with the SDP answer and the port number value of the data channel media stream(s) is zero and 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], is not present in the Contact header field.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7 Communication Diversion (CDIV)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.1 Communication Forwarding Unconditional (CFU)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.1.1 Actions at the AS of the diverting User
| On reception of incoming session setup INVITE request in the IMS AS of the diverting user with the media feature tag +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4] in the Contact header field and SDP offer containing the media descriptions for the MMTel media according 3GPP TS 24.173 [10] and a data channel media description for the bootstrap data channel in accordance with 3GPP TS 26.114 [4], if a CFU service condition is satisfied based on the diverting user subscription data, the IMS AS of the diverting user shall not send session event notification to the DCSF. The IMS AS of the diverting user shall route the incoming session setup INVITE request towards a diverted-to user as defined in 3GPP TS 24.604 [16].
There will be no media negotiation between the originating user and the diverting user, including data channel media negotiation. The data channel media session setup shall be performed between originating user and the diverted-to user together with audio, video media negotiation as per procedures defined in clause 9.3.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.2 Communication Forwarding on Busy user (CFB)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.2.1 Actions at the AS of the diverting User
| On reception of incoming session setup INVITE request in the IMS AS of the diverting user with the media feature tag +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4] in the Contact header field and SDP offer containing the media descriptions for the MMTel media according 3GPP TS 24.173 [10] and a data channel media description for the bootstrap data channel in accordance with 3GPP TS 26.114 [4], diverting user's network functions shall reserve the data channel media resources before routing the session setup request to the diverting user.
On reception of SIP response 486 (User Busy) from the diverting user, if CFB has been triggered as defined in 3GPP TS 24.604 [16], the diverting user’s network functions shall release the reserved data channel media as per procedures defined in clause 9.3 and route the incoming session setup INVITE request towards a diverted-to user as defined in 3GPP TS 24.604 [16]. The data channel media session setup shall be performed between originating user and the diverted-to user together with audio, video media negotiation as per procedures defined in clause 9.3.
In case of failure of data channel media resources reservations at serving network functions of diverting user, the IMS AS of diverting user shall proceed with setup of the MMTel session without performing data channel bootstrapping, by deleting data channel media description (m lines) from SDP offer of incoming INVITE request and route the updated INVITE request to the diverted-to user.
For the CFB under Network Determined User Busy as defined in 3GPP TS 24.604 [16], the CFB behaviour will be same with CFU as specified in clause 10.7.1.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.3 Communication Deflection (CD)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.3.1 Actions at the AS of the diverting User
| The CD service can only be triggered before the 200 OK SIP response reception from the diverting user as defined in 3GPP TS 24.604 [16].
On reception of 302(Moved Temporarily) SIP response at IMS AS, the IMS AS:
- shall notify the establishment failure event and trigger the release of the established data channel media resource on early dialog of the MMTel session between the originating and the diverting user’s network by interacting with the DCSF and the MF of the user-B as per procedures defined in clause 4.5.2.6.3 3GPP TS 24.604 [16] and in clause 9.3; and
- shall route the incoming session setup INVITE request towards a diverted-to user as defined in 3GPP TS 24.604 [16]. The data channel media negotiation shall be performed between the originating user and the diverted-to user together with audio, video media negotiation as per procedures defined in clause 9.3.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.4 Communication Forwarding on No Reply (CFNR)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.4.1 Actions at the AS of the diverting User
| The CFNR service no-reply timer at IMS AS shall be started at the reception of 180 (Ringing) SIP response reception. On no-reply timer expiry, the IMS AS:
- shall notify the establishment failure event and send a CANCEL or BYE request to the diverting UE as per procedures defined in clause 4.5.2.6.3 of 3GPP TS 24.604 [16], notify the DCSF about the session establishment cancellation or session termination and request the MF to release the allocated data channel media resource on early dialog of the MMTel session for the BDC related to diverting user and diverting network (e.g. the BDC between the originating user and the diverting user’s network the BDC between the originating network and the diverting user and the BDC between the diverting user and diverting network) by interacting with the DCSF and the MF of the user-B (diverting user) as per procedures in clause 9.3; and
- shall route the incoming session setup INVITE request towards a diverted-to user as defined in 3GPP TS 24.604 [16]; and
. - shall support the data channel media negotiation between originating user and the diverted-to user:
a) upon receipt of an SDP answer from the network serving the diverted-to user, shall generate an SDP offer based on received SDP answer, for the BDC between the originating UE and the network serving the diverted-to user and the BDC between the originating network and the diverted-to user, include the generated SDP offer in the UPDATE request and send it towards the originating network.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.4.2 Actions at the AS of the originating User
| Upon receiving an SDP offer included in an UPDATE request containing data channel media description to update the BDC between the originating network and the diverted-to user, and the BDC between the originating user and the diverted-to network, the IMS AS shall:
1) notify the DCSF about media change event;
2) request the MF to update the data channel media resource allocated for the BDCs towards the diverted-to network and the diverted-to user, based on the instruction from the DCSF; and
3) send the UPDATE request with the modified SDP offer containing data channel media description for the BDCs (i.e. the BDC between the originating network and the originating user, and the BDC between the originating user and the diverted-to user’s network) towards the originating UE.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.5 Communication Forwarding on Not Reachable (CFNRc)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.5.1 Actions at the AS of the diverting User
| There’s no data channel media session setup between the originating and the diverting user’s network, hence the CFNRc behavior shall be same as CFU service in clause 10.7.1.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.6 Communication Forwarding on Not Logged-in (CFNL)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.7.6.1 Actions at the AS of the diverting User
| When the AS of the diverting user receives an incoming session setup INVITE request for an unregistered served user with the media feature tag +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4] in the Contact header field and SDP offer containing the media descriptions for the MMTel media according 3GPP TS 24.173 [10] and a data channel media description for the bootstrap data channel in accordance with 3GPP TS 26.114 [4], and a CFNL condition is determined at the IMS AS, there’s no data channel media negotiation between the originating user and the diverting user, hence the CFNL service behavior shall be same as CFU service in clause 10.7.1.
In case of a late CFNL detection by the network (e.g., the terminating S-CSCF of a diverting user), the network shall send 480 (Temporarily Unavailable) response to the IMS AS, for the incoming INVITE request to the diverting user. On reception of a 480 (Temporarily Unavailable) response, the IMS AS of the diverting user shall trigger the release of reserved DC media resources and route the incoming INVITE request towards the diverted-to user. Hence for this use case, CFNL service behavior shall be same as CFB service in clause 10.7.2
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.8 Communication Waiting (CW)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.8.1 Actions at AS of user B
| If a network-based CW ("approaching NDUB") or terminal based CW condition is determined, after a CW service execution, the serving IMS AS will interact with the serving DCSF and the MF of the user B, to reserve the DC media resources for waiting communication, based on the served user B subscription data. The serving IMS AS shall forward or send the INVITE request to the user B, as per 3GPP TS 24.615 [17].
NOTE: Bandwidth usage by active session DC media and the requested bandwidth usage in a waiting communication, can be one of the conditions to evaluate "approaching NDUB".
The user B may proceed with below actions when a communication waiting indication is to be given to the user B:
1) the user B may accept the waiting communication and holds the active communication or releases the active communication (per procedures in 3GPP TS 24.615 [17]):
a) on reception of a Re-INVITE request, which is meant for holding the active communication, the IMS AS interaction with DCSF and MF for DC media handling is not required; or
b) on reception of a BYE request for the active communication, the serving IMS AS of the user B, will trigger the release of reserved DC Media resources of active communication by interacting with the serving DCSF and the MF of the user B. The serving IMS AS of the user B, shall follow the session release procedure as specified in 3GPP TS 24.229 [9]; or
2) the user B may reject the waiting communication:
a) on reception of an unsuccessful response for waiting communication from the user B, the serving IMS AS of the user B will trigger the release the reserved DC Media resources of waiting communication by interacting with the DCSF and the MF of the user B and shall reject the communication by sending unsuccessful response to the user C.
Upon expiry of the TAS-CW timer, the serving IMS AS of the user B will trigger the release of the reserved DC Media resources of waiting communication by interacting with the DCSF and the MF of the user B before sending a CANCEL request for waiting communication towards the user B.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.8.2 Actions at UE of user B
| If the user B accepts the waiting communication and holds the active communication (as per procedures in 3GPP TS 24.615 [17]), the hold invoking UE of the user B shall perform the hold procedure.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.9 Advice Of Charge (AOC)
| The Advice Of Charge (AOC) service specified in 3GPP TS 24.647 [22] shall allow the served user to be informed of IP Multimedia session related charging information even if the session is accompanying with data channel media.
According to 3GPP TS 32.260 [20] and 3GPP TS 32.255 [21], duration-based charging and volume-based charging are used for IMS data channel, which does not introduce specific requirements on charging information element specified in Annex C of 3GPP TS 24.647 [22]. So, AOC service has no interaction with IMS data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.10 Flexible Alerting (FA)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.10.1 Actions at the AS serving the pilot identity
| The flexible alerting telecommunication service with IMS data channel, procedures for the IMS AS serving user B identified by the FA pilot identity, shall be in accordance with 3GPP TS 24.239 [23] with the additions defined in the present document.
Upon reception of an incoming SIP INVITE request with DC media destined to the FA pilot identity of the user B, served by the IMS AS, the IMS AS:
- shall not trigger the IMS data channel resource reservation; and
- shall execute the FA procedures and route the incoming SIP INVITE request with DC media along with other MMTel media towards the FA group member identities, by sending the SIP INVITE request to S-CSCF in accordance with clause 4.5.5.2 3GPP TS 24.239 [23].
NOTE: The data channel media negotiation will be performed between the originating user and the FA group member together with audio, video media negotiation as per procedures defined in clause 9.3.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.11 Multi-Device (MuD)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.11.1 Actions at the AS serving user B
| The multi-device service with IMS data channel, procedures for the IMS AS serving the user B having federated UEs, shall be in accordance with 3GPP TS 24.174 [24] with the additions defined in the present document.
On reception of a SIP initial INVITE request with an SDP offer containing IMS data channel media descriptions, the IMS AS of the user B, shall execute multi-device service procedure, which branch the call into several call legs to alert the federated UEs of the user B. The IMS AS shall determine whether the served user B is authorized to use IMS data channel. If the served user is authorized to use IMS data channel, then for each federated UE of the user B the IMS AS shall determine if the federated UE supports IMS data channel capabilities. For each created call leg towards the federated UE:
1) if the served user B is authorized to use IMS data channel and if the federated UE supports IMS data channel capabilities, the IMS AS shall follow procedure specified in clause 9.3.3.2.1, bullet 1); and
2) if the served user B is authorized to use IMS data channel but the federated UE does not support IMS data channel capabilities or if the served user B is not authorized to use IMS data channel, the IMS AS shall follow procedure specified in clause 9.3.3.2.1, bullet 2).
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.11.2 Call pull, actions at the AS serving user A
| On reception of an INVITE request from the UE of the user A who has triggered the call pull request, to establish new partial dialog with the IMS AS of the user A in accordance with 3GPP TS 24.174 [24] clause 4.5.3.2.3:
1) the IMS AS shall update existing partial dialog towards the remote network in accordance with 3GPP TS 24.174 [24] clause 4.5.3.2.3 and 3GPP TS 24.229 [9], containing media descriptions to close established data channels associated with the UE of the user A whose call is getting pulled; and
2) after the successful session acknowledgement between the UE of the user A who has triggered the call pull request and the remote network, the IMS AS shall notify the DCSF about the session release event for the call leg towards the UE of the user A whose call is getting pulled and the established data channels associated with the UE of the user A whose call is getting pulled are closed as part of a partial dialog termination in accordance with clause 9.3.2.1.5.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.11.3 Call push, actions at the AS serving user A
| On reception of a SIP REFER request for call push request from the UE of the user A involved in ongoing call:
1) the IMS AS shall establish new partial dialog with the target UE of the user A in accordance with 3GPP TS 24.174 [24] clause 4.5.3.2.4 and 3GPP TS 24.628 [28] clause 4.4.a;
2) the IMS AS shall update existing partial dialog towards the remote network in accordance with 3GPP TS 24.174 [24] clause 4.5.3.2.4 and 3GPP TS 24.229 [9], containing media descriptions to close established data channels associated with the UE of the user A who has triggered the call push request in accordance with clause 9.3.3.1.4 of this specification; and
3) after a successful session acknowledgement between the target UE of the user A and the remote network, the IMS AS shall notify the DCSF about the session release event for the call leg towards the UE of the user A who has initiated the call push request and the established data channels associated with the UE of the user A who has initiated the call push request are closed as part of a partial dialog termination in accordance with clause 9.3.2.1.5.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.12 Multi-iDentity (MiD)
| No interaction with IMS data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.13 Completion of Communications to Busy Subscriber (CCBS), Completion of Communications by No Reply (CCNR) and Completion of Communications on Not Logged-in (CCNL)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.13.1 General
| The CCBS, CCNR and CCNL services enable a user, encountering a destination that is busy, does not answer or is not logged-in, to have the communication completed at a later point in time without the user having to manually initiate a new communication attempt, which is defined in 3GPP TS 24.642 [25].
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.13.2 Action at the UE
| When the UE initiates the initial IMS session before the CC services activation, the IMS data channel media description can be included in the INVITE along with other MMTel medias. The procedure defined in clause 9.3.2.1.2 applies.
On reception of the 486 (Busy Here) in case of CCBS or the 480 (Temporarily Unavailable) in case of CCNL or on sending the 487 (Request Terminated) in case of CCNR, the UE shall terminate the existing call session as specified in 3GPP TS 24.642 [25] including data channel media.
When the CC call is initiated, the IMS data channel media description can be included in initial INVITE message along with other MMTel medias.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.13.3 Action at the IMS AS serving the originating UE
| Upon reception of the incoming sessions setup INVITE request in the IMS AS serving the originating UE with the media feature tag +sip.app-subtype="webrtc-datachannel" as specified in 3GPP TS 26.114 [4] in the Contact header field and SDP offer containing the media descriptions for the MMTel media according 3GPP TS 24.173 [10] and a data channel media description for the bootstrap data channel in accordance with 3GPP TS 26.114 [4], the AS will trigger the DC media resources reservation according to 3GPP TS 23.228 [3] and route the INVITE message to the S-CSCF towards the terminating UE.
In case of CCBS activation, on reception of SIP response 486 (User Busy) from the terminating network, the IMS AS will release the reserved data channel media offered to the terminating network as per procedures defined in clause 9.3. On sending the SIP response 486 (User Busy) to the originating UE, the AS will release the reserved data channel media terminated from the originating UE as per procedures defined in clause 9.3.
In case of CCNL activation, on reception of SIP response 480 (Temporarily Unavailable) from the terminating network, the IMS AS will release the reserved data channel media offered to the terminating network as per procedures defined in clause 9.3. On sending the SIP response 480 (Temporarily Unavailable) to the originating UE, the IMS AS will release the reserved data channel media terminated from the originating UE as per procedures defined in clause 9.3.
In case of CCNR activation, upon reception a 180 (Ringing) response from the terminating network, the IMS AS will notify to DCSF and update the data channel media resources. Upon reception the SIP response 487 (Request Terminated) from the terminating network, the IMS AS will release the data channel media resources along with the session release.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.14 Enhanced Calling Name (eCNAM)
| No interaction with IMS data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.15 Closed User Group (CUG)
| No interaction with IMS data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.16 Communication Barring (CB)
| No interaction with IMS data channel.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.17 Customized Ringing Signal (CRS)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.17.1 General
| The CRS service is an operator specific service specified in 3GPP TS 24.183 [26], which describes three models of CRS service:
- Download and play model: it has no interaction with IMS data channel.
- Gateway model: it has no impact to IMS data channel.
- Early session model: it has no impact to IMS data channel.
As specified in 3GPP TS 24.183 [26], the CRS media can consist of music, voice, text, video or other customized ringing signals.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.17.2 Actions on the originating UE
| When the originating UE is configured with IMS_DC_configuration node specified in 3GPP TS 24.275 [11] and the DC_Setup_Option leaf indicates that the IMS data channel is to be setup simultaneously while establishing an IMS session, the data channel media can be negotiated in the initial INVITE request and its corresponding response.
In early session model, if the originating UE initiates an MMTel session with an IMS data channel, the UE shall include the data channel media description in the SDP offer of the initial SIP INVITE, as specified in the clause 9.3.2.1.2.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.17.3 Actions on the CRS AS
| Upon receiving the SIP requests and responses containing data channel SDP media descriptions, the CRS AS shall ignore them and just transmit them transparently.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.18 Customized Alerting Tones (CAT)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.18.1 General
| The CAT service is an operator specific service specified in 3GPP TS 24.182 [27], which describes three models of CAT service as follows:
- forking model: it has no impact to IMS data channel.
- gateway model: it has no impact to IMS data channel.
- early session model: it has no impact to IMS data channel.
As specified in 3GPP TS 24.182 [27], the CAT media can consist of favourable songs, multi-media clips or other customized alerting tones.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.18.2 Actions at the originating UE
| When the originating UE is configured with IMS_DC_configuration node specified in 3GPP TS 24.275 [11] and the DC_Setup_Option leaf indicates that the IMS data channel is to be setup simultaneously while establishing an IMS session, the data channel media can be negotiated in the initial INVITE request and its corresponding response.
In early session model, if the originating UE initiates MMTel session with an IMS data channel, the UE shall include the data channel media description in the SDP offer of initial SIP INVITE message, as specified in clause 9.3.2.1.2.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.18.3 Actions at the CAT AS
| Upon receiving the SIP requests and responses containing data channel SDP media descriptions, the CAT AS shall ignore them and just transmit them transparently.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.19 Explicit Communication Transfer (ECT)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.19.1 General
| The explicit communication transfer (ECT) service provides a party involved in a communication to transfer that communication to a third party as defined in 3GPP TS 24.629 [12].
There are three actors active in a transfer, they are acting in the following roles:
transferor: the party that initiates the transfer of the active communication that it has with the transferee;
transferee: the party which stays in the communication which is transferred;
transfer target: the party which the communication is transferred to and which replaces the transferor in the communication.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.19.2 Actions at the AS serving the transferor
| On reception of REFER message, if ECT has been triggered as defined in 3GPP TS 24.629 [12], the IMS AS serving the transferor:
- shall trigger the closing of all the established data channels on the transferor’s network (including the data channel between the transferor’s network and the transferor, the data channel between the transferor’s network and the transferee, the data channel between transferor’s network and the transfer target) as per procedures defined in clause 9.3: and
- route the session setup INVITE request which includes audio, video and data channel media towards a REFER-TO user as defined in 3GPP TS 24.629 [12]. The data channel media set up shall be performed between the transferee and the transfer target together with audio, video media negotiation as per procedures defined in clause 9.3.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.19.3 Actions at the AS serving the transferee
| If the transferee's network has established data channel media with the transferor before the transfer happens, the transferee's network shall release the data channel between transferor and transferee’s network. After establishment of an IMS session towards the transfer target data channels may be established towards the transfer target as per procedures defined in clause 9.3.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.19.4 Actions at the AS serving the transfer target
| In case of blind transfer, if the transfer target's network provides data channel service, on reception of incoming INVITE request from transferor’s network, the transfer target's network shall send the INVITE message to transfer target. On reception of the 18x response or 200 (OK) response on the INVITE message from the transfer target, the transfer target's network shall trigger the reservation of the data channel media resources to establish the data channel for the transfer target and the transferee, together with audio, video media negotiation as per procedures defined in clause 9.3 and then sends the 18x response or 200 (OK) response to transferor’s network.
In case of consultative transfer, if the transfer target's network provides data channel service, on reception of incoming re-INVITE request with the SDP offer of transferee’s network from transferor’s network, the transfer target's network shall update the established data channel between transfer target’s network and transferor to data channel between transfer target’s network and transferee.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.20 Communication Hold (HOLD)
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.20.1 Actions at the invoking UE
| If the UE want to put some media stream on hold, then in addition to the application of procedures according to 3GPP TS 24.610 [32], the following procedures shall be applied at the invoking UE.
The invoking UE shall include in the generated SDP offer as specified in 3GPP TS 26.114 [4]:
1) for each data channel media that was previously active (i.e. the SDP direction attribute "a=sendrecv" was present in the last SDP body or no SDP direction attribute was included), the SDP direction attribute "a=inactive" associated with the corresponding "m=application" line if the invoking UE wants to suspend the data channel media; and
2) for each data channel media that was previously suspended (i.e. the SDP direction attribute "a=inactive" was present in the last SDP body), the SDP direction attribute "a=sendrecv" associated with the corresponding "m=application" line (or to omit the SDP direction attribute) if the invoking UE wants to resume the suspended data channel media;
and as specified in 3GPP TS 24.610 [32], the invoking UE shall send the generated SDP offer in a re-INVITE request to the remote UE.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.20.2 Actions at the AS serving the invoking UE
| |
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.20.2.1 General
| In addition to the application of procedures according to 3GPP TS 24.610 [32], the following procedures shall be applied at the AS serving the invoking UE.
NOTE: The AS serving the invoking UE can be the AS in the originating IMS network and/or the terminating IMS network, depending on by which network the media to be suspended is managed.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.20.2.2 Event report
| On reception of the SIP re-INVITE request with the SDP offer that contains an "a=inactive" SDP direction attribute in data channel media description and data channel media was previously active, the AS shall notify the DCSF that data channel media is to be suspended as specified in 3GPP TS 29.175 [18].
On reception of the SIP re-INVITE request with the SDP offer that contains an "a=sendrecv" SDP direction attribute (or the SDP direction attribute is omitted) in data channel media description and data channel media was previously suspended, the AS shall notify the DCSF that data channel media is to be resumed as specified in 3GPP TS 29.175 [18].
Based on the instruction from the DCSF, the AS serving the invoking UE shall modify the SDP offer where:
1) for each data channel media towards the remote UE that was previously active (i.e. the SDP direction attribute "a=sendrecv" was present in the last SDP body or no SDP direction attribute was included), the SDP direction attribute "a=inactive" associated with the corresponding "m=application" line;
2) for each data channel media towards the remote UE that was previously suspended (i.e. the SDP direction attribute "a=inactive" was present in the last SDP body), the SDP direction attribute "a=sendrecv" associated with the corresponding "m=application" line (or to omit the SDP direction attribute);
and as specified in 3GPP TS 24.610 [32], the IMS AS shall send the modified SDP offer in a re-INVITE request to the remote UE.
|
b3bbdb8d26c45089a67aa06bf888a05c | 24.186 | 10.20.3 Actions at the held UE
| In addition to the application of procedures according to 3GPP TS 24.610 [32], the held UE shall generate an SDP answer for the held data channel media as specified as 3GPP TS 26.114 [4].
Annex A (informative):
Signalling flows
This annex provides the signalling flows related to clause10.
A.1 Interaction with supplementary services
Below sections depict signalling flow diagram for IMS data channel service interaction with existing MMTel supplementary services.
A.1.1 Communication Diversion
A.1.1.1 Communication Forwarding unconditional
Figure A.1.1.1-1 shows an example signalling flow for a successful communication forwarding unconditional based on an AS providing the forwarding and initial communication setup request consist of DC media session setup request along with other MMTel media session setup request.
Figure A.1.1.1-1: Call Forwarding Unconditional
The description of the steps mentioned in the figure A.1.1.1-1 is in accordance with the 3GPP TS 24.604 [16] with the additions defined in the present document:
1. in step 1), user A(UA-A) sends initial INVITE request towards the user B(UA-B), which contains:
• 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;
• optionally the 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
• the SDP offer containing the media descriptions for the MMTel media according 3GPP TS 24.173 [10] and a data channel media description for the bootstrap data channel in accordance with 3GPP TS 26.114 [4];
2. in step 3), the IMS AS serving the user B(UA-B) receives SIP INVITE request with DC media. CFU service condition is satisfied based on the diverting user B(UA-B) subscription data. Depending on the diverting user B (UA-B) IMS data channel subscription, the IMS AS of the diverting user does not send session event notification to the DCSF for data channel setup. Procedures for CFU are executed;
3. in step 5) the IMS AS sends SIP INVITE request with data channel media towards the diverted-to-user C(UA-C);
4. in step 7) the communication is routed towards the diverted-to-user C(UA-C) along with data channel media;
5. in step 9) bootstrap data channel is established for the originating user A(UA-A)/network and the diverted-to-user C(UA-C)/network; and
6. in step 10) application data channel is established along with other MMTel media.
A.1.1.2 Communication Forwarding on Busy
Figures A.1.1.2-1 shows an example signalling flow for a successful communication forwarding on busy based on an AS providing the forwarding and initial communication setup request consist of DC media session setup request along with other MMTel media session setup request.
Figure A.1.1.2-1: Call Forwarding on Busy
The description of the steps mentioned in the figure A.1.1.2-1 is in accordance with the 3GPP TS 24.604 [16] with the additions defined in the present document:
1. in step 1) user A(UA-A) sends initial INVITE request towards the user B(UA-B) in accordance with clause A.1.1.1 step 1);
2. in step 3) to step 12) the IMS AS serving the user B(UA-B) receives SIP INVITE request with DC media. Depending on the user B(UA-B) IMS data channel subscription, the IMS AS of the user B(UA-B) triggers the reservation of resources for data channel setup in accordance with clause 9.3.3.2.1 and clause AC.7.1 3GPP TS 23.228 [3];
3. in step 13) the initial INVITE request is sent to the user B(UA-B) along with data channel media due to normal communication procedures;
4. in step 15) to step 17) on reception of the 486 (Busy Here) response for the initial INVITE request, in the IMS AS, CFB service condition is satisfied based on the diverting user B(UA-B) subscription data. Procedures for CFB are executed. The IMS AS notifies session establishment failure event to the DCSF and sends media resource management request to the MF to release the allocated data channel media resources for this SIP Session.
5. in step 19) the IMS AS sends SIP INVITE request with data channel media towards the diverted-to-user C(UA-C);
6. in step 21) the communication is routed towards the diverted-to-user C(UA-C) along with data channel media;
7. in step 23) bootstrap data channel is established between the originating user A(UA-A)/network and the diverted-to-user C(UA-C)/network; and
8. in step 24) application data channel is established along with other MMTel media.
A.1.2 Communication Waiting (CW)
A.1.2.1 Network based CW flows
Figure A.1.2.1-1 shows an example of network-based communication waiting signalling flow at the terminating side and successful communication establishment. Waiting communication request contains DC media session along with other MMTel media sessions.
Figure A.1.2.1-1: Network based CW flow: Successful communication establishment.
The description of the steps mentioned in the figure A.1.2.1-1 is in accordance with the 3GPP TS 24.615 [17] with the additions defined in the present document:
1. in step 1) initial INVITE request with data channel media is received for the user B(UA-B) in accordance with clause A.1.1.1 step 1);
2. in step 2) the IMS AS serving the user B(UA-B) receives SIP INVITE request with data channel media;
3. in step 2a) to step 2c) the IMS AS of user B(UA-B) executes network-based CW procedures. Depending on the user B(UA-B) IMS data channel subscription, the IMS AS of the user B(UA-B) triggers the reservation of resources for data channel setup for waiting communication in accordance with clause 9.3.3.2.1 and clause AC.7.1 3GPP TS 23.228 [3];
4. in step 3) the IMS AS of the user B(UA-B) sends SIP INVITE request with data channel media and call waiting indication for waiting communication, towards the user B(UA-B);
5. in step 13) the IMS AS of the user B(UA-B) receives 200OK response with data channel media from user B(UA-B) for the waiting communication; and
6. in step 13a) the IMS AS of the user B(UA-B) sends successful session establishment event notification for waiting communication to the DCSF serving the user B(UA-B).
A.1.2.2 Terminal based CW flows
A.1.2.2.1 Successful communication establishment
Figure A.1.2.2.1-1 shows an example of terminal-based communication waiting signalling flow at the terminating side and successful communication establishment. Waiting communication request contains DC media session along with other MMTel media sessions.
Figure A.1.2.2.1-1 Terminal based CW: Successful communication establishment.
The description of the steps mentioned in the figure A.1.2.2.1-1 is in accordance with the 3GPP TS 24.615 [17] with the additions defined in the present document:
1. in step 1) initial INVITE request with data channel media is received for the user B(UA-B) in accordance with clause A.1.1.1 step 1);
2. in step 2) the IMS AS serving the user B(UA-B) receives SIP INVITE request with data channel media;
3. in step 2a) to step 2c) the IMS AS of user B(UA-B) determines and executes terminal-based CW procedures. Depending on the user B IMS data channel subscription, the IMS AS of the user B(UA-B) triggers the reservation of resources for data channel setup for waiting communication in accordance with clause 9.3.3.2.1 and clause AC.7.1 3GPP TS 23.228 [3];
4. in step 3) the IMS AS of the user B(UA-B) sends SIP INVITE request with data channel media for waiting communication, towards the user B(UA-B);
5. in step 8a), step 13a) on reception of 18x responses with call waiting indication from user B(UA-B) for waiting communication, the IMS AS of the user B(UA-B) sends session progress event notification to the DCSF serving the user B(UA-B);
6. in step 18) the IMS AS of the user B(UA-B) receives 200OK response with data channel media from user B(UA-B) for the waiting communication; and
7. in step 18b) the IMS AS of the user B(UA-B) sends successful session establishment event notification for waiting communication, to the DCSF serving the user B(UA-B).
A.1.2.2.2 AS CW Timer expires
Figure A.1.2.2.2-1 shows an example of terminal-based communication waiting signalling flow at the terminating side and CW timer expires at IMS AS. Waiting communication request contains DC media session along with other MMTel media sessions.
Figure A.1.2.2.2-1 Terminal based CW: CW timer expires at AS.
The description of the steps mentioned in the figure A.1.2.2.1-1 is in accordance with the 3GPP TS 24.615 [17] with the additions defined in the present document:
1. in step 1) initial INVITE request with data channel media is received for the user B(UA-B) in accordance with clause A.1.1.1 step 1);
2. in step 2) the IMS AS serving the user B(UA-B) receives SIP INVITE request with data channel media;
3. in step 2a) to step 2c) the IMS AS of user B(UA-B) determines and executes terminal-based CW procedures. Depending on the user B(UA-B) IMS data channel subscription, the IMS AS of the user B(UA-B) triggers the reservation of resources for data channel setup for waiting communication in accordance with clause 9.3.3.2.1 and clause AC.7.1 3GPP TS 23.228 [3];
4. in step 3) the IMS AS of the user B(UA-B) sends SIP INVITE request with data channel media for waiting communication, towards the user B(UA-B);
5. in step 8a), 13a) on reception of 18x responses with call waiting indication from user B(UA-B) for waiting communication, the IMS AS of the user B(UA-B) sends session progress event notification to the DCSF serving the user B(UA-B); and
6. in step 14c) to step 14d) upon CW timer expiry for waiting communication, the IMS AS of the user B(UA-B) notifies session failure event to the DCSF of the user B(UA-B) and as per media instruction request from the DCSF, the IMS AS sends media resource management request to the MF to release the allocated data channel media resources for this waiting communication SIP session. The IMS AS notifies the DCSF about the DC media release as part of the media instruction response.
A.1.2.2.3 UE CW timer expires
Figure A.1.2.2.3-1 shows an example of terminal-based communication waiting signalling flow at the terminating side and CW timer expires at UE-B. Waiting communication request contains DC media session along with other MMTel media sessions.
Figure A.1.2.2.3-1 Terminal based CW: CW timer expires at UE-B.
The description of the steps mentioned in the figure A.1.2.2.3-1 is in accordance with the 3GPP TS 24.615 [17] with the additions defined in the present document:
1. in step 1) initial INVITE request with data channel media is received for the user B(UA-B) in accordance with clause A.1.1.1 step 1);
2. in step 2) the IMS AS serving the user B(UA-B) receives SIP INVITE request with data channel media;
3. in step 2a) to step 2c) the IMS AS of user B(UA-B) determines and executes terminal-based CW procedures. Depending on the user B(UA-B) IMS data channel subscription, the IMS AS of the user B(UA-B) triggers the reservation of resources for data channel setup for waiting communication in accordance with clause 9.3.3.2.1 and clause AC.7.1 3GPP TS 23.228 [3];
4. in step 8a, step 13a) on reception of 18x responses with call waiting indication from user B(UA-B) for waiting communication, the IMS AS of the user B(UA-B) sends session progress event notification to the DCSF serving the user B(UA-B); and
5. in step 18a) to step 18b) upon reception of 480 (Temporarily Unavailable) SIP response for waiting communication, the IMS AS of the user B(UA-B) notifies session failure event to the DCSF of the user B(UA-B) and as per media instruction request from the DCSF, the IMS AS sends media resource management request to the MF to release the allocated data channel media resources for this waiting communication SIP session. The IMS AS notifies the DCSF about the DC media release as part of the media instruction response.
A.1.3 Explicit Communication Transfer
A.1.3.1 IMS serving the transferee provides data channel service
A.1.3.1.1 Blind Transfer
Figure A.1.3.1.1-1: Blind Transfer when IMS serving the transferee provides data channel service
Figure A.1.3.1.1-1 shows a call flow for blind transfer when IMS serving the transferee provides data channel service.
Step1: UE-A calls UE-B, UE-A sends an INVITE request towards the UE-B.
Step2: DC media resource is allocated by IMS-A for UE-A and UE-B.
Step3-6: UE-B answers the call, session connection is established between UE-A and UE-B. IMS-A establishes BDC connection for UE-A and UE-B. And then IMS-A establishes ADC connections between UE-A and UE-B.
Step7: UE-B starts transfer process.
Step8: UE-B sends a REFER message to transfer the call to UE-C.
Step9-10: IMS-B sends 202/NOTIFY to UE-B to accept the transfer request, and then sends BYE message to UE-B. UE-B releases reserved DC media resources of established BDC and ADC between UE-B and IMS-A/UE-A for A-B call.
Step11-12: IMS-B sends an initial INVITE message to UE-C without SDP, UE-C replies SDP offer with audio media in 18X/200 response.
Step13: IMS-B sends re-INVITE message to IMS-A and release the data channels between the IMS-B and UE-A.
Step14-16: IMS AS of IMS-A notifies session modify event to the DCSF and as per media instruction request from the DCSF, the IMS AS sends media resource management request to MF to update the data channel media resources for UE-B. IMS-A releases reserved DC media resources of established BDC and ADC between IMS-A and UE-B for A-B call.
Step17-19: IMS AS of IMS-A sends a re-INVITE message carrying SDP offer with data channel media towards UE-A. In SDP offer of re-INVITE message, the IMS AS of IMS-A adds previously established BDC and ADC between IMS-A and UE-A for A-B call with UDP ports set to zero. Earlier established BDC between UE-A and IMS-A (in step 4-1) can remain as it is or re-established as per operator policy. IMS-A releases the earlier established DC media resources between IMS-A and UE-A. UE-A releases the earlier established DC media resources between UE-A and IMS-A/UE-B and prepare SDP answer with earlier established DC media with UDP port zero. UE-A replies with the SDP answer with data channel media included in the 200 OK response.
Step20-22: IMS AS of IMS-A notifies session modify event to the DCSF and as per media instruction request from the DCSF, the IMS AS sends media resource management request to MF to update the data channel media resources for UE-A.
Step23: IMS AS of IMS-A sends a 200 OK message with updated data channel media to IMS-B.
Step24: IMS-B sends PRACK/ACK message towards UE-C with no DC media in SDP answer.
Step25: The session connection is established between UE-A and UE-C.
A.1.3.1.2 Consultation Transfer
Figure A.1.3.1.2-1: Consultative Transfer when IMS serving the transferee provides data channel service
Figure A.1.3.1.2-1 shows a call flow for consultative transfer when IMS serving the transferee provides data channel service.
Step1: UE-A calls UE-B, UE-A sends an INVITE request towards the UE-B.
Step2: DC media resource is allocated by IMS-A for UE-A and UE-B.
Step3-6: UE-B answers the call, session connection is established between UE-A and UE-B. IMS-A establishes BDC connection for UE-A and UE-B. And then IMS-A establishes ADC connections between UE-A and UE-B.
Step7-8: UE-B holds UE-A, and then calls UE-C.
Step9: When UE-C sends 180 ringing or 200 response, UE-B starts transfer process.
Step10: UE-B sends a REFER message to transfer the call to UE-C.
Step11-12: IMS-B sends 202/NOTIFY to UE-B to accept the transfer request, and then sends BYE message to UE-B.
Step13-15: IMS-B sends a media re-negotiation request to UE-A, UE-A replies SDP offer with data channel media description.
Step16-18: IMS AS of IMS-A notifies session modify event to the DCSF and as per media instruction request from the DCSF, the IMS AS sends media resource management request to MF to update the data channel media resources for UE-A.
Step19: IMS AS sends a 200 OK response for re-INVITE to the IMS-B with updated data channel media.
Step20-21: IMS-B sends a re-INVITE message carrying SDP offer with data channel media towards UE-C, and receives 200 OK response for reINVITE carrying SDP answer with data channel media from UE-C.
Step22: IMS-B sends an ACK message carrying SDP answer with data channel media towards IMS-A.
Step23-25: IMS AS of IMS-A notifies session modify event to the DCSF and as per media instruction request from the DCSF, the IMS AS sends media resource management request to MF to update the data channel media resources for UE-C.
Step26: IMS AS of IMS-A sends an ACK message carrying SDP answer with data channel media towards UE-A.
Step27: The BDC media connection is established between IMS-A and UE-C.
Step28: The ADC media connections are established between UE-A and UE-C.
Step29: The session connection is established between UE-A and UE-C.
A.1.3.2 IMS serving the transferor provides data channel service
A.1.3.2.1 Blind Transfer
Figure A.1.3.2.1-1: Blind Transfer when IMS serving the transferor provides data channel service
Figure A.1.3.2.1-1 shows a call flow for blind transfer when IMS serving the transferor provides data channel service.
Step1: UE-A calls UE-B, UE-A sends an INVITE request towards the UE-B.
Step2: DC media resource is allocated by IMS-B for UE-A and UE-B.
Step3-6: UE-B answers the call, session connection is established between UE-A and UE-B. IMS-B establishes BDC connection for UE-A and UE-B. And then IMS-B establishes ADC connections between UE-A and UE-B.
Step7: UE-B starts transfer process.
Step8: UE-B sends a REFER message to transfer the call to UE-C.
Step9-10: IMS-B sends 202/NOTIFY to UE-B to accept the transfer request, and then sends BYE message to UE-B.
Step11: IMS-B releases all the allocated data channel media resources on MF for UE-A, UE-B.
Step12-17: IMS-B sends an INVITE message to UE-C, the audio along with data channel media connections are established between UE-A and UE-C, the data channel media can be provided either by IMS-A or IMS-C or both.
A.1.3.2.2 Consultation Transfer
Figure A.1.3.2.2-1: Consultative Transfer when IMS serving the transferor provides data channel service
Figure A.1.3.2.2-1 shows a call flow for consultative transfer when IMS serving the transferor provides data channel service.
Step1: UE-A calls UE-B, UE-A sends an INVITE request towards the UE-B.
Step2: DC media resource is allocated by IMS-B for UE-A and UE-B.
Step3-6: UE-B answers the call, session connection is established between UE-A and UE-B. IMS-B establishes BDC connection for UE-A and UE-B. And then IMS-B establishes ADC connections between UE-A and UE-B.
Step7-8: UE-B holds UE-A, and then calls UE-C.
Step9: When UE-C sends 180 ringing or 200 response, UE-B starts transfer process.
Step10: UE-B sends a REFER message to transfer the call to UE-C.
Step11-12: IMS-B sends 202/NOTIFY to UE-B to accept the transfer request, and then sends BYE message to UE-B.
Step13: IMS-B releases all the allocated data channel media resources on MF for UE-A, UE-B and UE-C.
Step14-18: IMS-B sends a media re-negotiation request with to establish the connection between UE-A and UE-C.
Step19: The audio along with data channel media connections are established between UE-A and UE-C, the data channel media can be provided either by IMS-A or IMS-C or both.
A.1.3.3 IMS serving the transfer target provides data channel service
A.1.3.3.1 Blind Transfer
Figure A.1.3.3.1-1: Blind Transfer when IMS serving the transfer target provides data channel service
Figure A.1.3.3.1-1 shows a call flow for consultative transfer when IMS serving the transfer target provides data channel service.
Step1: UE-A calls UE-B, UE-A sends an INVITE request towards the UE-B.
Step2: UE-B answers the call, session connection is established between UE-A and UE-B.
Step3: UE-B starts transfer process. UE-B sends a REFER message to transfer the call to UE-C.
Step4-5: IMS-B sends 202/NOTIFY to UE-B to accept the transfer request, and then sends BYE message to UE-B.
Step6: IMS-B sends an INVITE message towards UE-C.
Step7-9: IMS-C forwards the INVITE message to UE-C. On reception of 18X/200 message with data channel media from UE-C, IMS-C allocates the data channel media resources on MF for UE-A and UE-C.
Step10.: IMS-C sends the 18X/200 message to IMS-B.
Step11-12: IMS-B transfers the 18X/200 message to reINVITE message and sends it towards UE-A, UE-A responses 200 OK with data channel media answer to IMS-B.
Step13-14: IMS-B transfers the 200 OK message to PRACK/ACK message and sends it to IMS-C. IMS-C update data channel media on MF. Then IMS-C sends the PRACK/ACK message to UE-C.
Step16: The BDC media connections are established on MF of IMS-C for both UE-A and UE-C.
Step17: The ADC media connections are established between UE-A and UE-C.
Step18: The session connection is established between UE-A and UE-C.
A.1.3.3.2 Consultation Transfer
Figure A.1.3.3.2-1: Consultative Transfer when IMS serving the transfer target provides data channel service
Figure A.1.3.3.2-1 shows a call flow for consultative transfer when IMS serving the transfer target provides data channel service.
Step1: UE-A calls UE-B, UE-A sends an INVITE request towards the UE-B.
Step2: UE-B answers the call, session connection is established between UE-A and UE-B.
Step3-9: UE-B holds UE-A, and then calls UE-C, session connection is established between UE-B and UE-C. IMS-C establishes BDC connection for UE-B and UE-C. And then IMS-C establishes ADC connections between UE-B and UE-C.
Step10: UE-B starts transfer process. UE-B sends a REFER message to transfer the call to UE-C.
Step11-12: IMS-B sends 202/NOTIFY to UE-B to accept the transfer request, and then sends BYE message to UE-B.
Step13-15: IMS-B sends a re-INVITE request to establish the connection between UE-A and UE-C.
Step16: IMS-C updates the DC media connection for UE-A when receiving the updated data channel media from UE-A.
Step17-19: The media re-negotiation finished between UE-A and UE-C.
Step20: The BDC media connection is established on MF of IMS-C for UE-A.
Step21: The ADC media connections are established between UE-A and UE-C.
Step22: The session connection is established between UE-A and UE-C.
Annex B (normative):
Extensions within the present document
B.1 Feature-capability indicators defined in the present document
This clause describes the feature-capability indicators definitions, according to IETF RFC 6809 [6], that are applicable for the 3GPP IM CN subsystem.
B.1.1 Definition of feature-capability indicator g.3gpp.datachannel
Feature-capability indicator name: g.3gpp.datachannel
Summary of the feature indicated by this feature-capability indicator:
This feature-capability indicator indicates the support of data channel capability in the network, and can be included in a Feature-Caps header field as specified in IETF RFC 6809 [6] in a 200 (OK) response to the REGISTER request.
Feature-capability indicator specification reference:
3GPP TS 24.186, http://www.3gpp.org/ftp/Specs/archive/24_series/24.186/
Values appropriate for use with this feature-capability indicator: Not applicable
Examples of typical use: Indicating the support of data channel capability in the network.
Security Considerations: Security considerations for this feature-capability indicator are discussed in clause 9 of IETF RFC 6809[6].
B.1.2 Definition of feature-capability indicator g.3gpp.dc-mux
Feature-capability indicator name: g.3gpp.dc-mux
Summary of the feature indicated by this feature-capability indicator: This feature-capability indicator indicates the support of IMS data channel multiplexing capability in the network, and can be included in a Feature-Caps header field as specified in IETF RFC 6809 [6] in SIP request and response.
Feature-capability indicator specification reference:
3GPP TS 24.186, http://www.3gpp.org/ftp/Specs/archive/24_series/24.186/
Values appropriate for use with this feature-capability indicator: Not applicable
Examples of typical use: Indicating the support of IMS data channel multiplexing capability in the network.
Security Considerations: Security considerations for this feature-capability indicator are discussed in clause 9 of IETF RFC 6809[6].
Annex C(normative):
Applications based on IMS data channel
C.1 General
The present annex depicts the applications based on the IMS data channel, including the corresponding procedures.
C.2 AR communication
C.2.1 AR Remote Cooperation
C.2.1.1 General Description
According to clause 6.39.2 of 3GPP TS 22.261 [2], the IMS network should support AR media processing. AR Remote Cooperation is a typical AR call service and the detailed user experience of AR Remote Cooperation is described in clause 5.3 of 3GPP TR 22.873 [13].
It’s assumed that the local UE shares the camera to the remote UE for assistance, and the remote UE displays the shared camera and provides assistances. A voice call is established between local UE and remote UE, and then AR Remote Assistance application is triggered by local UE.
The overall solution is based on IMS DC architecture specified in Annex AC of 3GPP TS 23.228 [3] and shown as follows:
- The local UE triggers the media renegotiation for AR Remote Cooperation based on user actions to establish a new video stream to transmit local video content (see A002 in figure C.2.1.1-1) and an application data channel to transmit AR anchors (see A001 in figure C.2.1.1-1).
- After the DCSF recognizes the AR Remote Cooperation service, it anchors the video stream and application data channel to MF. Then the DCSF initiates media renegotiation with remote UE to establish a new video stream to transmit local video content (see B002 in figure C.2.1.1-1) and an application data channel to transmit AR anchors (see B001 in figure C.2.1.1-1).
- The local UE may decide to start AR media split rendering negotiation as specified in 3GPP TS 26.264 [29] and 3GPP TS 23.228 [29].
- The local UE or remote UE extract the original AR anchors input from the user and transmits the anchors to the MF through the application data channel.
- The local UE and remote UE receives the updated AR anchors from the MF, displays it on the video stream.
Figure C.2.1.1-1 illustrates the media connection model of the AR Remote Cooperation.
Figure C.2.1.1-1: Media Connection model of AR Remote Cooperation
Table C.2.1.1-1 lists the media streams for the AR Remote Cooperation.
Table C.2.1.1-1 Media stream list for the AR Remote Cooperation
Media ID
(Example)
Media Resource Type
Direction
Description
A001
DC
bi-directional
Transmit upstream and downstream AR anchors between MF and local UE and the split rendering messages.
A002
Video
unidirectional
Transmit video content from local UE to the MF.
B001
DC
bi-directional
Transmit upstream and downstream AR anchors between the MF and remote UE.
B002
Video
unidirectional
Transmit local UE's video content to remote UE.
C.2.2 Procedures
C.2.2.1 Data Channel Setup
C.2.2.1.1 Procedure at the UE
Once AR remote cooperation application is launched, the local UE sends a SIP re-INVITE request with an SDP offer which includes a video media description with an "a=sendonly" attribute line to establish a video stream (see B001 in Figure C.2.1.1-1) as specified in 3GPP TS 24.229 [9] and 3GPP TS 24.173 [10] and a data channel media description with "a=dcmap" attribute line containing "stream-id" parameter set to the values starting at 1000 and "a=3gpp-req-app " attribute line to establish an application data channel (see A001 in Figure C.2.1.1-1) as specified in clause 9.3. The "a=3gpp-req-app " attribute line indicates that the newly established application data channel is used for AR Remote Cooperation application.
After application data channel and video stream established, the local UE may decide to start split rendering. If the local UE decides to split rendering, the UE shall use the procedure defined in 3GPP TS 26.264 [29].
After split rendering negotiation procedure finished, both the local UE or remote UE extracts the original AR anchors input by the user and transmits it to MF through the established application data channel.
When receiving the updated AR anchors transmitted via application data channel from the MF, both the local UE and the remote UE displays the updated AR anchors based on video stream.
C.2.2.1.2 Procedure at the IMS AS
When receiving the SIP re-INVITE request from local UE, IMS AS shall notify the DCSF about media change request related to local UE requesting to setup an application data channel and a new video.
When receiving media reservation instruction from DCSF, the IMS AS shall convert the media instructions to the corresponding media resource operations and request MF to create or update media resources, and reserve media processing resources for AR Remote Cooperation.
When receiving response from MF on the media resources reservation or update, IMS AS sends media reservation response to DCSF, indicating the URL addresses of each stream involved AR Remote Cooperation service control, which is specified in 3GPP TS 29.175 [18].
C.2.2.2 Closing Data Channel
If the UE wants to close the AR remote cooperation related application data channels, the procedure defined in clause 9.3 applies.
C.3 Avatar communication
C.3.1 General
As specified in clause 5.2.2.2 in 3GPP TS 22.156 [34], the IMS network shall support avatar-based real time communication. The overall solution of avatar communication based on IMS data channel is defined in 3GPP TS 23.228 [3].
C.3.2 Procedures
C.3.2.1 Procedure at the UE
C.3.2.1.1 Avatar ID List Downloading
When the UE downloading the avatar communication application through the established bootstrap data channel as specified in clause 9.3.2.1.2 or clause 9.3.2.1.3.1, the UE may fetch the list of avatar ID as specified in 3GPP TS 23.228 [3] through bootstrap data channel or by pre-configuration.
NOTE 1: The list of avatar ID can be downloaded to the UE through application data channel. This procedure is outside the scope of this specification.
NOTE 2: The Avatar ID associated URL can be included in the Avatar ID list and downloaded to UE. The associated URL enables the UE to download the Avatar representation associated with the Avatar ID.
C.3.2.1.2 Application Data Channel Establishment and Avatar Animation
After the user selects the avatar ID and runs the avatar communication application, the originating UE shall generate an SDP offer to establish an application data channel as per clause 9.3.2.1.3.2.
The originating UE may initiate the avatar animation negotiation with the DC AS and terminating UE via the established application data channel as per 3GPP TS 23.228 [3].
Based on the avatar animation negotiation result:
- if the rendering mode is negotiated to originating UE centric, the originating UE may get the avatar representation identified with the selected avatar ID via the application data channel if needed, and performs avatar animation with the selected avatar representation. In addition, the UE shall send the animated video stream over RTP to the peer UE;
- if the rendering mode is negotiated to terminating UE centric,
1) the originating UE shall request the terminating UE to perform avatar animation, which should include the avatar ID selected by the user of originating UE and sends the avatar metadata to terminating UE through the established application data channel and audio/video through RTP channel; and
2) the terminating UE shall download the avatar representation using the originating UE ID, the avatar ID and associated URL received from originating UE as specified in bullet 1) and the terminating UE ID and performs the avatar animation based on the received avatar metadata; and
- if the rendering mode is negotiated to network centric, the originating UE:
1) may initiate a new P2A2P or P2P application data channel, which are used for avatar rendering-related data transmission between the two UEs and the network, and
2) sends the avatar metadata to through the newly established application data channel and/or audio/video.
If the terminating UE initiates the avatar communication, the procedure for originating UE applies to the terminating UE and the procedure for terminating UE applies to the originating UE.
C.3.2.2 Procedure at the IMS AS
Upon receiving the re-INVITE request to establish application data channel establishment, the procedure in clause 9.3.2.2.2 applies.
Annex <D> (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2023-04
CT1#141
Draft skeleton provided by the rapporteur.
0.0.0
2023-04
CT1#141
Implementing the agreed pCR:
C1-232932, C1-232933, C1-232934
0.1.0
2023-05
CT1#142
Implementing the agreed pCR:
C1-234121, C1-234122, C1-234123, C1-234124
0.2.0
2023-08
CT1#143
Implementing the agreed pCR:
C1-236169, C1-236178, C1-236184, C1-236188,
C1-236189, C1-236191, C1-236544
0.3.0
2023-10
CT1#144
Implementing the agreed pCR:
C1-238296, C1-238298, C1-238299, C1-238303,
C1-238306, C1-238310, C1-238313, C1-238320,
C1-238321, C1-238322, C1-238323
0.4.0
2023-11
CT1#145
Implementing the agreed pCR:
C1-238764, C1-238928, C1-239524, C1-239525,
C1-239526, C1-239527, C1-239528, C1-239530,
C1-239531, C1-239532, C1-239534, C1-239535,
C1-239536, C1-239539, C1-239542, C1-239543,
C1-239544, C1-239545, C1-239546, C1-239555
0.5.0
2023-12
CT#102
Presentation to TSG CT for information
1.0.0
2024-01
CT1#146
Implementing the agreed pCR:
C1-240115, C1-240131, C1-240137, C1-240193,
C1-240195, C1-240281, C1-240283, C1-240343,
C1-240344, C1-240345, C1-240346, C1-240347,
C1-240348, C1-240349, C1-240352, C1-240377,
C1-240378, C1-240379, C1-240380, C1-240383,
C1-240384, C1-240385, C1-240386, C1-240387
1.1.0
2024-03
CT1#147
Implementing the agreed pCR:
C1-240623, C1-240733, C1-241409, C1-241428,
C1-241432, C1-241435, C1-241437, C1-241439,
C1-241450, C1-241452, C1-241454, C1-241455,
C1-241456, C1-241464, C1-241470, C1-241471,
C1-241472, C1-241474, C1-241476, C1-241477,
C1-241478
1.2.0
2024-03
CT#103
CP-240231
Presentation to TSG CT for approval
2.0.0
2024-06
CT#104
CP-241186
0012
-
B
Abnormal case for DC1 interface
18.1.0
2024-06
CT#104
CP-241186
0001
1
B
The requirement of the IMS AS during registration
18.1.0
2024-06
CT#104
CP-241186
0006
1
F
Correction to TS 24.186
18.1.0
2024-06
CT#104
CP-241186
0008
1
F
Clarification on the procedure of IMS AS during session setup and session modification
18.1.0
2024-06
CT#104
CP-241186
0007
1
F
Add the handling of SDP answer in the procedure of IMS AS
18.1.0
2024-06
CT#104
CP-241186
0010
1
F
Support of AR media split rendering negotiation
18.1.0
2024-06
CT#104
CP-241186
0015
1
F
Removal of CONF related EN
18.1.0
2024-06
CT#104
CP-241186
0009
2
F
Clarification on the capability negotiation
18.1.0
2024-06
CT#104
CP-241186
0003
2
F
Update the abnormal case on DC2
18.1.0
2024-06
CT#104
CP-241186
0004
3
C
Solve the EN on UICC configuration
18.1.0
2024-06
CT#104
CP-241186
0005
2
C
Clarification on DC setup policy
18.1.0
2024-06
CT#104
CP-241186
0027
-
F
Update the DC setup policy according to the new definition of DC setup option
18.1.0
2024-06
CT#104
CP-241186
0011
3
B
Interaction with CH supplementary service
18.1.0
2024-06
CT#104
CP-241186
0023
1
F
Correction on the procedure of IMS AS
18.1.0
2024-06
CT#104
CP-241186
0018
1
F
Procedure of originating IMS AS on receiving the BDC establishment request
18.1.0
2024-06
CT#104
CP-241186
0025
1
F
The remote BDC setup requested by the UE
18.1.0
2024-06
CT#104
CP-241186
0026
1
B
Abnormal case for DC QoS negotiation in P2A and P2A2P scenarios
18.1.0
2024-06
CT#104
CP-241186
0017
2
F
Delete MRF from the spec
18.1.0
2024-09
CT#105
CP-242191
0024
3
F
DC resource release due to a CANCEL request
18.2.0
2024-09
CT#105
CP-242191
0031
1
F
DC related re-INVITE request collision
18.2.0
2024-09
CT#105
CP-242191
0032
1
F
Correct the IMS AS procedure on handling IP and port number
18.2.0
2024-09
CT#105
CP-242191
0028
1
F
Correction to error handling
19.0.0
2024-09
CT#105
CP-242191
0033
1
F
Correction on the incomplete SIP request and responses
19.0.0
2024-12
CT#106
CP-243193
0037
1
A
Correction on the SDP handling for ADC setup
19.1.0
2024-12
CT#106
CP-243223
0042
1
B
Support of interworking with MTSI client
19.1.0
2024-12
CT#106
CP-243223
0041
1
B
Support of Standalone DC
19.1.0
2024-12
CT#106
CP-243193
0043
1
F
Miscellaneous corrections
19.1.0
2024-12
CT#106
CP-243193
0035
2
A
Correction on the BDCs and ADCs in a m line
19.1.0
2024-12
CT#106
CP-243223
0039
2
B
Update session control and DC application related requirement to support the standalone DC
19.1.0
2024-12
CT#106
CP-243193
0049
1
F
Correction on the IMS AS behaviour in CDIV
19.1.0
2024-12
CT#106
CP-243223
0050
1
B
UE handling of IMS data channel in PS Data off feature
19.1.0
2024-12
CT#106
CP-243223
0051
1
B
AS handling of IMS data channel in PS Data off feature
19.1.0
2024-12
CT#106
CP-243223
0054
1
B
Procedure of avatar communication
19.1.0
2024-12
CT#106
CP-243193
0045
1
F
Clarify the calling and called identity notified to the DCSF
19.1.0
2024-12
CT#106
CP-243223
0052
2
B
Procedure of Standalone data channel
19.1.0
2024-12
CT#106
CP-243223
0053
2
B
Procedure of network-initiated DC establishment
19.1.0
2025-03
CT#107
CP-250145
0002
6
B
Setup local BDC on terminating side in case INVITE does not contain DC description
19.2.0
2025-03
CT#107
CP-250144
0055
-
F
Correction on the description of SDP handling for ADC
19.2.0
2025-03
CT#107
CP-250150
0056
2
B
Update the IMS AS requirement for the enforcement of PS data off
19.2.0
2025-03
CT#107
CP-250150
0057
1
B
Update the IMS AS requirement for the support of interworking with MTSI client
19.2.0
2025-03
CT#107
CP-250150
0058
3
B
Support of DC multiplexing capability negotiation and indication
19.2.0
2025-03
CT#107
CP-250150
0059
2
B
UE support of DC multiplexing
19.2.0
2025-03
CT#107
CP-250199
0061
2
B
Network initiated standalone IMS DC session setup
19.2.0
2025-03
CT#107
CP-250150
0062
1
B
Procedure of network initiated P2P application data channel establishment
19.2.0
2025-03
CT#107
CP-250150
0064
1
F
Remove a EN of avatar communication
19.2.0
2025-03
CT#107
CP-250150
0065
1
B
Procedure of application data channel interworking via DC AS for originating UE
19.2.0
2025-03
CT#107
CP-250172
0067
1
A
ECT corrections: AS serving the transferee and blind call flow
19.2.0
2025-03
CT#107
CP-250144
0068
-
F
Conferencing procedure at IMS AS
19.2.0
2025-03
CT#107
CP-250150
0069
-
D
Editorial corrections
19.2.0
2025-03
CT#107
CP-250150
0070
1
B
PS Data off support during IMS session establishment
19.2.0
2025-06
CT#108
CP-251151
0072
1
A
Network-determined DC termination after session setup
19.3.0
2025-06
CT#108
CP-251171
0075
1
B
Solve the EN on closing ADC in the case of DC multiplexing
19.3.0
2025-06
CT#108
CP-251171
0076
1
B
Supplementary to interworking procedure
19.3.0
2025-06
CT#108
CP-251171
0077
1
B
DC termination and standalone DC session termination on KI#2
19.3.0
2025-06
CT#108
CP-251151
0082
2
A
Correction on the media reject
19.3.0
2025-06
CT#108
CP-251171
0060
4
B
Network support of DC multiplexing
19.3.0
2025-06
CT#108
CP-251171
0079
2
B
Procedure of ADC multiplexing at IMS AS
19.3.0
2025-06
CT#108
CP-251171
0078
2
B
Update the UE support of standalone DC session procedures
19.3.0
2025-06
CT#108
CP-251171
0080
2
B
Update on the avatar communication
19.3.0
2025-06
CT#108
CP-251151
0074
4
A
Update the interaction of DC with CFNR and support the requirement
19.3.0
2025-06
CT#108
CP-251171
0089
1
B
Additional requirement of the IMS AS in KI#2
19.3.0
2025-06
CT#108
CP-251171
0086
2
B
Update the IMS AS support of standalone DC session procedures
19.3.0
2025-06
CT#108
CP-251171
0085
3
B
DC allowed configuration is applicable for standalone DC session
19.3.0
2025-06
CT#108
CP-251171
0091
2
B
The indication for network initiated data channel setup
19.3.0
2025-06
CT#108
CP-251171
0087
2
B
The requirement of the UE related to DC application in 8.1
19.3.0
2025-09
CT#109
CP-252156
0092
1
B
Alerting in standalone data channel scenario
19.4.0
2025-09
CT#109
CP-252156
0094
1
B
Update on IMS data channel application for standalone data channel
19.4.0
2025-09
CT#109
CP-252156
0095
1
F
Indication in standalone data channel scenario
19.4.0
2025-09
CT#109
CP-252156
0097
1
B
Additional information to indicate DC operation is initiated by the DC AS in KI#2-24.186
19.4.0
2025-09
CT#109
CP-252156
0098
1
C
Solve the EN on NW initiated BDC termination
19.4.0
2025-09
CT#109
CP-252156
0099
1
C
Update the requirement of the IMS AS on how to associate with the requested DC in KI#2
19.4.0
2025-09
CT#109
CP-252156
0093
2
B
General update on the requirement of IMS AS for standalone data channel
19.4.0
2025-09
CT#109
CP-252156
0096
3
B
Handling of application data channel multiplexing
19.4.0
2025-12
CT#110
CP-253106
0101
2
F
IMS AS procedures for Standalone IMS DC sessions
19.5.0
2025-12
CT#110
CP-253106
0102
1
F
Update in UE procedures for Standalone IMS DC sessions
19.5.0
2025-12
CT#110
CP-253106
0103
2
F
Providing editorial changes and correct SIP responses for clarity
19.5.0
2025-12
CT#110
CP-253106
0104
2
F
Update on avatar communication
19.5.0
2025-12
CT#110
CP-253106
0106
1
F
Correction on standalone data channel
19.5.0
2025-12
CT#110
CP-253106
0107
F
Solve the EN in B.1.2
19.5.0
2025-12
CT#110
CP-253106
0108
1
F
Add the DC-Info header field in the BYE request
19.5.0
2025-12
CT#110
CP-253106
0109
1
F
Align the standalone IMS data channel session
19.5.0
2025-12
CT#110
CP-253106
0110
2
F
Update in IMS AS procedures for Standalone IMS DC sessions
19.5.0
2025-12
CT#110
CP-253106
0111
2
F
Correction on the network initiated data channel operation
19.5.0
|
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 1 Scope | The present document identifies the requirements for operation of Uncrewed Aerial Vehicles (UAVs) via the 3GPP system.
This includes requirements for meeting the business, security, and public safety needs for the remote identification and tracking of UAS linked to a 3GPP subscription. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 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] FAA UTM Concept of Operations v1.0, Foundational Principles, Roles and Responsibilities, Use Cases and Operational Threads https://utm.arc.nasa.gov/docs/2018-UTM-ConOps-v1.0.pdf
[3] FAA Remote Identification, https://www.faa.gov/uas/research_development/remote_id/
[4] 3GPP TS 22.261: "Service requirements for the 5G system; Stage 1".
[5] IMT 2020(5G): "Application for UAV in 5G White Paper", September 2018 |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 3 Definitions, symbols and abbreviations | |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 3.1 Definitions | For the purposes of the present document, the terms and definitions 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].
Above ground level (AGL): In the context of a UAV it is the UAV altitude referenced to ground level in the vicinity.
Command and Control (C2) Communication: the user plane link to convey messages with information of command and control for UAV operation between a UAV controller and a UAV.
Uncrewed Aerial System (UAS): Composed of Uncrewed Aerial Vehicle (UAV) and related functionality, including command and control (C2) links between the UAV and the controller, the UAV and the network, and for remote identification. A UAS is comprised of a UAV and a UAV controller.
NOTE: A UAV can be controlled by different UAV controllers, but at any given time, a UAV is under the control of only one UAV controller. The mechanisms to ensure which UAV controller is active and controlling the UAV is out of scope of 3GPP.
Uncrewed Aerial System Traffic Management (UTM): a set of functions and services for managing a range of autonomous vehicle operations.
UAV controller: The UAV controller of a UAS enables a drone pilot to control an UAV.
UxNB: radio access node on-board UAV. It is a radio access node providing connectivity to UEs, which is carried in the air by an Uncrewed Aerial Vehicle (UAV). |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 3.3 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].
BVLOS Beyond Visual Line of Sight
C2 Command and Control
Remote ID Remote Identification [3]
UAS Uncrewed Aerial System
UAV Uncrewed Aerial Vehicle
UTM Uncrewed Aerial System Traffic Management [2] |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 4 Overview on UAS | |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 4.1 General | An Uncrewed Aerial System (UAS) is the combination of an Uncrewed Aerial Vehicle (UAV), sometimes called a drone, and a UAV controller. A UAV is an aircraft without a human pilot onboard – instead, in some cases. the UAV can be controlled from an operator via a UAV controller and will have a range of autonomous flight capabilities. The communication system between the UAV and UAV controller is, within the scope of this specification and in some scenarios, provided by the 3GPP system. The UAS model considers also the scenario where the UAV controller communicates with the UAV via mechanisms outside the scope of 3GPP.
UAVs range in size and weight from small, light aircraft often used for recreational purposes to large, heavy aircraft which are often more suited to commercial applications. Regulatory requirements vary across this range and vary on a regional basis.
The communication requirements for UAS cover both the Command and Control (C2), and uplink and downlink data to/from the UAS components towards both the serving 3GPP network and network servers. The applicable C2 communication modes is depicted in clause 4.2.
Uncrewed Aerial System Traffic Management (UTM) is used to provide a number of services to support UAS and their operations including but not limited to UAS identification and tracking, authorisation, enforcement, regulation of UAS operations, and also to store the data required for UAS(s) to operate. It also allows authorised users (e.g., air traffic control, public safety agencies) to query the identity and metadata of a UAV and its UAV controller. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 4.2 C2 Communication | When using 3GPP network as the transport network for supporting UAS services, the following C2 communication are considered to provision UAS services by guaranteeing QoS for the C2 communication:
Direct C2 communication: the UAV controller and UAV establish a direct C2 link to communicate with each other and both are registered to the 5G network using the radio resource configured and scheduled provided by the 5G network for direct C2 communication.
Network-Assisted C2 communication: the UAV controller and UAV register and establish respective unicast C2 communication links to the 5G network and communicate with each other via 5G network. Also, both the UAV controller and UAV may be registered to the 5G network via different NG-RAN nodes. The 5G network needs to support mechanism to handle the reliable routing of C2 communication.
UTM-Navigated C2 communication: the UAV has been provided a pre-scheduled flight plan, e.g. array of 4D polygons, for autonomous flying, however UTM still maintains a C2 communication link with the UAV in order to regularly monitor the flight status of the UAV, verify the flight status with up-to-date dynamic restrictions, provide route updates, and navigate the UAV whenever necessary.
In general, Direct C2 communication and Network-Assisted C2 communication are used by a human-operator using a UAV controller. UTM-Navigated C2 communication is used by the UTM to provide cleared flying routes and routes updates. In order to ensure the service availability and reliability of the C2 communication for UAS operation, especially when the UAV is flying beyond line of sight (BLOS) of the operator, redundant C2 communication links can be established for any C2 communication links from UAV controller or UTM to a UAV.
For reliability and service availability consideration, it is possible to activate more than one C2 communication with one as a backup link for C2 communication or switch among the applicable links for C2 communication.
- For example, Direct C2 communication can be used at first and then switch to the Network-Assisted C2 communication when the UAV is flying BLOS.
- For example, UTM-navigated C2 communication can be utilized whenever needed, e.g. for air traffic control, the UAV is approaching a No Drone Zone, and detected potential security threats, etc.
There are four control modes considered in the C2 communication for the UAV operation that are with different requirements, e.g. on message intervals, sizes, and end to end latencies, etc., including steer to waypoints, direct stick steering, automatic flight by UTM and approaching autonomous navigation infrastructure.
• Steer to waypoints: the control message contains flight declaration, e.g. waypoints, sent from the UAV controller or UTM to the UAV. The control mode is used in both of direct C2 communication and network-assisted C2 communication.
• Direct stick steering: the control message contains direction instructions sending from the UAV controller to the UAV while optionally video traffic is provided as feedback from the UAV to the UAV controller. The control mode is used in both of direct C2 communication and network-assisted C2 communication.
• Automatic flight by UTM: the control message contains a pre-scheduled flight plan, e.g. array of 4D polygons, sent from the UTM to the UAV, which thereafter flies autonomously with periodic position reporting. The control mode is used in UTM-Navigated C2 communication.
• Approaching autonomous navigation infrastructure: the control message contains direction instructions, e.g. waypoints, altitudes and speeds from the UTM to the UAV. When the UAV is landing/departing, the UTM coordinates more closely with autonomous navigation infrastructure, e.g. vertiport or package distribution center. The control mode is used in UTM-Navigated C2 communication. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 5 Requirements for Remote Identification of UAS | |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 5.1 General | [R-5.1-001] The 3GPP system should enable UTM to associate the UAV and UAV controller, and the UTM to identify them as a UAS.
[R-5.1-002] The 3GPP system shall be able to provide UTM with the identity/identities of a UAS.
[R-5.1-003] The 3GPP system shall enable a UAS to send UTM the UAV data which can contain: unique identity (this may be a 3GPP identity), UE capability of the UAV, make & model, serial number, take-off weight, position, owner identity, owner address, owner contact details, owner certification, take-off location, mission type, route data, operating status.
[R-5.1-004] The 3GPP system shall enable a UAS to send UTM the UAV controller data which can contain: unique identity (this may be a 3GPP identity), UE capability of the UAV controller, position, owner identity, owner address, owner contact details, owner certification, UAV operator identity, UAV operator license, UAV operator certification, UAV pilot identity, UAV pilot license, UAV pilot certification and flight plan.
[R-5.1-005] The 3GPP system shall enable a UAS to send different UAS data to UTM based on the different authentication and authorizations level which are applied to the UAS.
NOTE 0: Subject to the regional regulation, the different authentication and authorization levels can be: the initial network access authentication and authorization, UAS identity authentication, UAV flight plan authorization, additional UTM service authentications, such as flight monitoring, collision avoidance services, so on.
[R-5.1-006] The 3GPP system shall support capability to extend UAS data being sent to UTM with the evolution of UTM and its support applications in future.
[R-5.1-007] Based on regulations and security protection, the 3GPP system shall enable a UAS to send UTM the identifiers which can be: IMEI, MSISDN, or IMSI, or IP address.
[R-5.1-008] Void
[R-5.1-009] The 3GPP system should enable an MNO to augment the data sent to a UTM with the following: network-based positioning information of UAV and UAV controller.
NOTE 1: This augmentation may be trust-based (i.e. the MNO informs the UTM that the UAV position information is trusted) or it may be additional location information based on network information, such as OTDOA, cell coordinates, synchronization source, etc.
NOTE 2: This requirement will not be applied to the case which the UAS and UTM has direct control communication connection without going through MNO, such as OTDOA, cell coordinates, synchronization source, etc.
[R-5.1-010] The 3GPP system shall enable UTM to inform an MNO of the outcome of an authorisation to operate.
[R-5.1-011] The 3GPP system shall enable an MNO to allow a UAS authorisation request only if appropriate subscription information is present.
[R-5.1-012] The 3GPP system shall enable a UAS to update a UTM with the live location information of a UAV and its UAV controller.
[R-5.1-013] The 3GPP network should be able to provide supplement location information of UAV and its controller to a UTM.
NOTE 3: This supplement may be trust-based (i.e. the MNO informs the UTM that the UAV position information is trusted) or it may be additional location information based on network information.
[R-5.1-014] The 3GPP network shall support UAVs and the corresponding UAV controller are connecting to different PLMNs at the same time.
[R-5.1-014a] The 3GPP system shall support UAVs and the corresponding UAV controller are connecting to different PLMNs at the same time.
[R-5.1-015] The 3GPP system shall provide the capability for network to obtain the UAS information regarding its support of 3GPP communication capabilities designed for UAS operation.
[R-5.1-016] The 3GPP system shall support the UAS identification and subscription data which can differentiate the UAS with UAS-capable UE and the UAS with non-UAS-capable UE.
NOTE 4: UAS-capable UE refers to the UE which support interaction capability with UTM and certain 3GPP communication features which 3GPP provides for UAS.
[R-5.1-017] The 3GPP system shall support the UTM in detection of UAV operating without authorization.
NOTE 5: the scenarios covered by the requirement above are FFS.
[R-5.1-018] The 5G system shall be able to detect that a connected UE is airborne, when the UE doesn’t have an aerial subscription.
[R-5.1-019] The 5G system shall be able to support a mechanism to enable a network operator to track an airborne connected UE which doesn’t have an aerial subscription.
[R-5.1-020] Based on operator and UTM policy, the 5G system shall be able to provide UTM with an airborne UE’s location and 3GPP identity to fulfil the UTM’s request.
NOTE 6: The 3GPP identity and UE location is expected to be used by the UTM to determine the position of airborne objects containing the UE. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 5.2 UAS traffic management | |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 5.2.1 General | NOTE: The following requirements are valid for both centralized and decentralized UTM.
[R-5.2.1-001] The 3GPP system shall provide a mechanism for a UTM to provide route data, along with flight clearance, to a UAV.
[R-5.2.1-002] The 3GPP system shall be able to deliver route modification information received from a UTM to a UAS with a latency of less than 500ms.
[R-5.2.1-003] The 3GPP system shall be able to deliver the notifications received from a UTM to a UAV controller with a latency of less than 500ms.
[R-5.2.1-004] Based on MNO policies and/or regulatory requirements, the 3GPP system shall enable the UTM to take over the communication used to control the UAV. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 5.2.2 Decentralized UAS traffic management | [R-5.2.2-001] The 3GPP system shall enable a UAV to broadcast the following data for identifying UAV(s) in a short-range area for collision avoidance: e.g. UAV identities if needed based on different regulation requirements, UAV type, current location and time, flight route information, current speed, operating status.
[R-5.2.2-002] The 3GPP system shall be able to support a UAV to transmit a message via network connection for identifying itself as an UAV to the other UAV(s).
[R-5.2.2-003] The 3GPP system shall enable UAV to preserve the privacy of the owner of the UAV, UAV pilot, and the UAV operator in its broadcast of identity information.
[R-5.2.2-004] The 3GPP system shall enable a UAV to receive local broadcast communication transport service from other UAV in short range.
[R-5.2.2-005] A UAV shall be able to use a direct UAV to UAV local broadcast communication transport service in the coverage or out of coverage of a 3GPP network.
[R-5.2.2-006] A UAV shall be able to use a direct UAV to UAV local broadcast communication transport service when the sending and receiving UAVs are served by the same or different PLMNs.
[R-5.2.2-007] The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service at relative speeds of up to 320 km/h.
[R-5.2.2-008] The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service with variable message payloads of 50-1500 bytes, not including security-related message component(s).
[R-5.2.2-009] The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which supports a range of up to 600m.
[R-5.2.2-010] The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which can transmit messages at a frequency of at least 10 messages per second.
[R-5.2.2-011] The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which can transmit messages with an end-to-end latency of at most 100ms. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 5.3 Void | |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 5.4 Security | [R-5.4-001] The 3GPP system shall protect the transport of data between the UAS and UTM.
[R-5.4-002] The 3GPP system shall protect against spoofing attacks of the UAS identities.
[R-5.4-003] Void.
[R-5.4-004] Void.
[R-5.4-005] The 3GPP system shall support confidentiality protection of identities related to the UAS and personally identifiable information.
[R-5.4-006] The 3GPP system shall support regulatory requirements (e.g. Lawful Intercept) for UAS traffic. |
49d023d828ebe5a050e72f70efeac4a5 | 22.125 | 6 Requirements for UAV usages |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.