hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.1 General
| This clause describes the adhoc group call participating MCPTT function procedures using on-demand and pre-established sessions to setup adhoc group calls, release the ongoing adhoc group calls, and modify the ongoing adhoc group calls participants.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.2 Adhoc group call setup
| This clause describes the originating, and terminating call setup participating MCPTT function procedures.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.2.1 Call setup procedures using on-demand session
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.2.1.1 Originating procedures
| In the procedures in this clause:
1) emergency indication in an incoming SIP INVITE request refers to the <adhoc-emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
2) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.2.1.2 Terminating procedures
| In the procedures in this clause:
1) emergency indication in an incoming SIP INVITE request refers to the <adhoc-emergency-ind> element of the application/vnd.3gpp.mcptt-info+xml MIME body; and
2) imminent peril indication in an incoming SIP INVITE request refers to the <imminentperil-ind> element of the application/... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.2.2 Call setup procedures using pre-established session
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.2.2.1 Originating procedures
| Upon receipt of a "SIP REFER request for a pre-established session", with:
1) the Refer-To header field containing a Content-ID ("cid") Uniform Resource Locator (URL) as specified in IETF RFC 2392 [62] that:
a) points to an application/resource-lists+xml MIME body as specified in IETF RFC 5366 [20] containing one or... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.2.2.2 Terminating procedures
| Upon receipt of a "SIP INVITE request for terminating participating MCPTT function", the participating MCPTT function shall follow the procedures as specified in clause 17.3.2.1.2.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.3 Adhoc group call release
| This clause describes the originating, and terminating call release participating MCPTT function procedures.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.3.1 Call release procedures using on-demand session
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.3.1.1 Originating procedures
| Upon receiving from the MCPTT client a SIP BYE request the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.1.6.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.3.1.2 Terminating procedures
| Upon receiving a SIP BYE request from the controlling MCPTT function, the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.2.8.1.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.3.2 Call release procedures using pre-established session
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.3.2.1 Originating procedures
| Upon receiving from the MCPTT client a SIP REFER request when using a pre-established session with the "method" SIP URI parameter set to value "BYE" in the URI in the Refer-To header field the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.1.7.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.3.2.2 Terminating procedures
| Upon receiving a SIP BYE request from the controlling MCPTT function and if the MCPTT session id refers to an MCPTT user that has a pre-established session with the participating MCPTT function, the participating MCPTT function shall follow the procedures as specified in clause 6.3.2.2.8.2.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.4 Adhoc group call rejoin
| This clause describes the originating, and terminating call rejoin participating MCPTT function procedures.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.4.1 Call rejoin procedures using on-demand session
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.4.1.1 Originating procedures
| Upon receipt of a "SIP INVITE request for originating participating MCPTT function" containing an application/vnd.3gpp.mcptt-info+xml MIME body with the <session-type> element set to a value of "adhoc", the participating MCPTT function shall follow the procedures specified in clause 17.3.2.1.1 with the clarification in... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.4.2 Call rejoin procedures using pre-established session
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.4.2.1 Originating procedures
| Upon receipt of a "SIP REFER request for a pre-established session", with the Refer-To header containing an application/vnd.3gpp.mcptt-info+xml MIME type content in an hname "body" parameter in the headers portion of the SIP URI and with the <session-type> element set to "adhoc", the participating MCPTT function shall ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.5 Adhoc group call participants modify
| This clause describes the originating adhoc group call participants modify participating MCPTT function procedures.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.5.1 Call participants modify procedures using on-demand session
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.5.1.1 Originating procedures
| Upon receipt of a SIP re-INVITE request for an MCPTT session identifying an on-demand MCPTT adhoc group session, the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP re-INVITE request with a SIP 500 (Server Internal Error) r... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.5.2 Call participants modify procedures initiated by participating MCPTT function
| This clause describes the procedure to notify the controlling MCPTT function about user meeting or no longer meeting the criteria to be added to or removed from the ongoing adhoc group session.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.5.2.1 Originating procedures
| When the participating MCPTT function determines that new MCPTT users are meeting the specified criteria or the MCPTT users who are meeting the specified criteria are no longer meeting the specified criteria, the participating MCPTT function:
1) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.6 Adhoc group call participants determination
| This clause describes the procedure to provide the user list from the participating MCPTT function serving users based on the criteria for determining the participants to be invited for adhoc group sessions, and handling the notification from the controlling MCPTT function about the release of an adhoc group session to... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.6.1 Call participants determination procedures
| Upon receipt of a "SIP MESSAGE request to get userlist for adhoc group call request for participating MCPTT function", the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Erro... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.6.2 Call participants determination stop procedures
| Upon receipt of a "SIP MESSAGE request to stop determining the participant list for participating MCPTT function", the participating MCPTT function:
1) shall stop determining the MCPTT users meeting and no longer meeting the specified criteria;
2) shall remove all the stored information about the adhoc group ID, the ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.3.7 Notification of ad hoc group call redirection
| When receiving a "SIP MESSAGE request to the terminating participating MCPTT function to send notification of adhoc group call redirection", the terminating participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request wi... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4 Controlling MCPTT function procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.1 General
| This clause describes the adhoc group calls controlling MCPTT function procedures using on-demand and pre-established sessions to setup adhoc group calls, release the ongoing adhoc group calls, and modify (criteria for) the participant list of the ongoing adhoc group calls.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.2 Adhoc group call setup
| This clause describes the originating, and terminating call setup controlling MCPTT function procedures.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.2.1 Originating Procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.2.1.1 INVITE targeted to an MCPTT client
| This clause describes the procedures for inviting an MCPTT user to an MCPTT session. The procedure is initiated by the controlling MCPTT function as the result of an action in clause 17.4.2.2.
The controlling MCPTT function:
1) shall generate a SIP INVITE request as specified in clause 6.3.3.1.2;
2) shall set the Re... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.2.2 Terminating Procedures
| In the procedures in this clause:
1) MCPTT ID in an incoming SIP INVITE request refers to the MCPTT ID of the originating user from the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP INVITE request;
2) adhoc group identity in an incoming SIP INVITE request if ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.3 Adhoc group call release
| This clause describes the originating, and terminating call release controlling MCPTT function procedures.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.3.1 Originating Procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.3.1.1 Adhoc group call release initiated by the controlling MCPTT function
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.3.1.1.1 SIP BYE request for releasing MCPTT session
| When the MCPTT session for group call needs to be released as specified in clause 6.3.8.1, the controlling MCPTT function shall execute the procedures in clause 17.4.6.2 and then follow the procedures in clause 6.3.3.1.5 with the clarifications given below for the clause 6.3.8.1 that:
1) the condition "minimum number ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.3.1.2 Adhoc group call leave initiated by the controlling MCPTT function
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.3.1.2.1 SIP BYE request for releasing MCPTT client from MCPTT session
| When an MCPTT client needs to be removed from the MCPTT session (e.g. user no longer meeting the criteria), the controlling MCPTT function shall follow the procedures in clause 6.3.3.1.5.
After successful in removing the MCPTT client from the MCPTT session, the controlling MCPTT function may generate a notification to... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.3.2 Terminating Procedures
| Upon receiving a SIP BYE request, the controlling MCPTT function:
1) if the adhoc group call is to be released based on the release policies as specified in clause 6.3.8.1, shall follow the procedures as specified in clause 17.4.6.2;
2) if the MCPTT user leaves the ad hoc group call due to migration, may inform the r... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.4 Adhoc group call rejoin
| This clause describes the originating, and terminating call rejoin controlling MCPTT function procedures.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.4.1 Call rejoin procedures using on-demand session
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.4.1.1 Terminating procedures
| Upon receipt of a SIP INVITE request that includes an MCPTT session identity of an ongoing MCPTT session in the Request-URI the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP INVITE request with a SIP 500 (Server Internal Er... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.5 Adhoc group call participants modify
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.5.0 General
| This clause describes the terminating ad hoc group call modification procedures in terms of (criteria for) the participant list.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.5.1 Modification of the participant list or criteria for the participant list procedures using on-demand session
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.5.1.1 Terminating procedures
| In the procedures in this clause:
1) MCPTT ID in an incoming SIP re-INVITE request refers to the MCPTT ID of the originating user from the <mcptt-calling-user-id> element of the application/vnd.3gpp.mcptt-info+xml MIME body of the incoming SIP INVITE request;
2) MCPTT ID or the functional alias in an incoming SIP re-... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.5.2 Call participants modify procedures initiated by participating MCPTT function
| This clause describes the procedure to handle the notification from the participating MCPTT function about user meeting or no longer meeting the criteria to be added to or removed from the ongoing adhoc group session.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.5.2.1 Terminating procedures
| Upon receiving a:
- "SIP MESSAGE request to add user to adhoc group call notification for controlling MCPTT function"; or
- "SIP MESSAGE request to remove user from adhoc group call notification for controlling MCPTT function";
the controlling MCPTT function:
1) if the incoming SIP MESSAGE request does not contain ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.6 Adhoc group call participants determination
| This clause describes the procedure to determine the participants to be invited to the adhoc group session. Based on local policy, the participants to be invited to the adhoc group session may be determined on the controlling MCPTT function or by means of getting the user lists from the participating MCPTT functions se... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.6.1 Call participants determination procedures
| When the controlling MCPTT function needs to determine the MCPTT users meeting the specified criteria, it may determine them, based on local policy on the controlling MCPTT function. Additionally, the controlling MCPTT function may create a list of terminating participating MCPTT functions from which users are to be de... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.4.6.2 Call participants determination stop procedures
| When the controlling MCPTT function needs to stop determining the MCPTT users meeting the specified criteria, then for each terminating participating MCPTT function in the created list, the controlling MCPTT function:
1) shall generate an outgoing SIP MESSAGE request in accordance with 3GPP TS 24.229 [4] and IETF RFC ... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.5 Extension of application/resource-lists +xml MIME type
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.5.1 Introduction
| The present clause describes an extension of the application/resource-lists+xml MIME body specified in IETF RFC 4826 [99].
The functional alias extension is used to indicate per-user functional alias association for the enties in the resource list.
|
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 17.5.2 Schema
| <?xml version="1.0" encoding="UTF-8"?>
<xs:schema
targetNamespace="urn:3gpp:ns:mcpttResLists:1.0"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:mcpttResLists="urn:3gpp:ns:mcpttResLists:1.0"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<!-- MCPTT specific child element of endp... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 18 Remote emergency floor request trigger
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 18.1 General
| Clause X specifies the MCPTT client, participating MCPTT function and controlling MCPTT function procedures for a remote emergency floor request trigger.
In the procedures clause X:
- the term "requesting MCPTT user" is used to refer to the user who sends a trigger for a remote emergency floor request;
- the term "... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 18.1.1 Client procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 18.1.1.1 Client originating procedure
| Upon receiving a request from the requesting MCPTT user to send a remote emergency floor request trigger to the MCPTT user who has initiated an ongoing emergency group call or emergency private call, the MCPTT client:
1) if the <allow-trigger-remote-floor-request> element of the <ruleset> element is not present in the... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 18.1.1.2 Client terminating procedure
| Upon receiving a "SIP MESSAGE request for emergency remote floor request trigger for terminating client", the MCPTT client:
1) shall determine that the targeted communication is a group call if the application/vnd.3gpp.mcptt-info+xml MIME body contained in the received SIP MESSAGE request contains an <mcptt-calling-gr... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 18.1.2 Participating MCPTT function procedures
| |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 18.1.2.1 Originating procedures
| Upon receiving a "SIP MESSAGE request for emergency remote floor request trigger for originating participating MCPTT function", the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Inte... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 18.1.2.2 Terminating procedures
| Upon receiving a "SIP MESSAGE request for emergency remote floor request trigger for terminating participating MCPTT function" the participating MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Inter... |
603c77cd0da93e5e476a024643c0ef1c | 24.379 | 18.1.3 Controlling MCPTT function procedures
| Upon receiving a "SIP MESSAGE request for emergency remote floor request trigger for controlling MCPTT function" the controlling MCPTT function:
1) if unable to process the request due to a lack of resources or a risk of congestion exists, may reject the SIP MESSAGE request with a SIP 500 (Server Internal Error) respo... |
556719e8696c25b4ac3572453768229c | 22.843 | 1 Scope | The present document provides additional use cases of UAV and identifies potential requirements to improve 5G system’s support of UAV applications, UAV operations and management, including:
• Provide additional information to the UAV operator/USS to execute pre-flight preparations and inflight operation (e.g, flight mi... |
556719e8696c25b4ac3572453768229c | 22.843 | 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.
- Fo... |
556719e8696c25b4ac3572453768229c | 22.843 | 3 Definitions of terms, symbols and abbreviations | |
556719e8696c25b4ac3572453768229c | 22.843 | 3.1 Terms | For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
example: text used to clarify abstract rules by applying them literally. |
556719e8696c25b4ac3572453768229c | 22.843 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
AAM Advanced Air Mobility
BRID Broadcast Remote Identification
BV... |
556719e8696c25b4ac3572453768229c | 22.843 | 4 Overview | The present document focuses on improving the 3GPP support for the applications and security for various scenarios using low altitude UAVs. The present document provides potential use cases and defines potential new service level requirements and KPIs for supporting identified use cases by 3GPP system. Use cases cover ... |
556719e8696c25b4ac3572453768229c | 22.843 | 5 Use cases | |
556719e8696c25b4ac3572453768229c | 22.843 | 5.1 Use case on UAV detection | |
556719e8696c25b4ac3572453768229c | 22.843 | 5.1.1 Description | 3GPP aerial features are activated based on "aerial subscription" flag specified in Rel-15. This implies that an operator using these features will provide UAV users with USIMs that are associated to a user profile with the "aerial subscription" flag set.
It is however technically possible for a UAV user to insert a US... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.1.2 Pre-conditions | A UAV user has inserted in a UE on board a UAV, a USIM that is associated to a user profile without the "aerial subscription" flag set. |
556719e8696c25b4ac3572453768229c | 22.843 | 5.1.3 Service Flows | 1. The UE registers in 5GS and starts communicating. The UAV takes off.
2. The network detects that the UE is on board a UAV.
3. The network takes action, e.g. activates aerial features, changes the QoS, populates charging records, alert the UTM and/or let the UTM take over the communication used to control the UAV. |
556719e8696c25b4ac3572453768229c | 22.843 | 5.1.4 Post-conditions | The UTM may take over the communication used to control the UAV and force the UAV to land safely.
Later, the UTM and/or network operator informs or reminds the user that a specific USIM needs to be used for proper operation of a UE on board a UAV. |
556719e8696c25b4ac3572453768229c | 22.843 | 5.1.5 Existing features partly or fully covering the use case functionality | - "aerial subscription" flag in subscription;
- Provision of "CAA-level UAV ID" by the UE;
- detection of UE above altitude thresholds by the eNB / gNB (per TS 36.331 & TS 38.331). |
556719e8696c25b4ac3572453768229c | 22.843 | 5.1.6 Potential New Requirements needed to support the use case | [PR 5.1.6-001] The 5G system shall be able to detect that a connected UE is airborne, while UE’s subscription does not include the "aerial subscription" flag set. |
556719e8696c25b4ac3572453768229c | 22.843 | 5.2 Use case on supporting UAV pre-flight preparation | |
556719e8696c25b4ac3572453768229c | 22.843 | 5.2.1 Description | During the operation of UAVs using the 3GPP network access, the network needs to ensure that the UAVs can access the network smoothly and timely. UAV flight mission need to be ensured for the real-time performance and stability of flight control link to guarantee the continuity of the flight.
5G network can provide wid... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.2.2 Pre-conditions | Pipeline company uses UAV A and logistics company uses UAV B. UAV A and UAV B are both individual terminals that subscribe to the communication service from 5G network.
Operator A provides 5G network coverage and communication services for remote command and control (C2) communication between UAV and UAV control platfo... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.2.3 Service Flows | Figure 5.2.3-1: Supporting UAV pre-flight preparation
1. The pipeline company plans to use UAV A to provide video inspection of pipelines from X to Y and the logistics company uses UAV B to deliver express from X to Z.
2. UAV/UAV-C A and UAV/UAV-C B register in 5G network and can communicate with UTM though 5G network.... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.2.4 Post-conditions | UAV A and UAV B can finish their respective tasks with the support of 5G system. |
556719e8696c25b4ac3572453768229c | 22.843 | 5.2.5 Existing features partly or fully covering the use case functionality | None. |
556719e8696c25b4ac3572453768229c | 22.843 | 5.2.6 Potential New Requirements needed to support the use case | [P.R 5.2.6-001] Based on operator’s policy, the 5G system shall be able to support a method to predict network conditions and QoS (e.g. bitrate, latency, reliability) along a continuous geographic planned flight path of a UAV at specific times of its expected flight duration.
[P.R 5.2.6-002] Based on operator’s policy,... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.3 Use case on Geofencing for Visual Line-of-Sight UAV missions | |
556719e8696c25b4ac3572453768229c | 22.843 | 5.3.1 Description | 3GPP has specified a wide range of aerial features, activated through an "aerial subscription". Three types of C2 communications have been defined for R17, in TS.22.125 [3]:
• Direct C2 communications (when the UAV controller and UAV establish a direct C2 link to communicate with each other);
• Network-Assisted C2 comm... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.3.2 Pre-conditions | The UAV is associated with an aerial UE profile and a “VLoS” option is activated together with its subscription. The UAV is associated with an UAV Controller (UAV-C). The 5G system is informed by the UTM of the maximal distance authorized between the UAV and the UAV-C (VLoS distance threshold, usually around 200 or 300... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.3.3 Service Flows | 1. The UAV registers in 5GS as an aerial UE with the VLoS option activated.
2. The UAV is associated with an UAV-C. The UAV takes off.
3. The network tracks the geolocalization of both the UAV and UAV-C, and deduces the distance between both. If the UAV-C does not belong to the 3GPP system, its geolocalization may be o... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.3.4 Post-conditions | The UTM may take over the communication used to control the UAV and force the UAV to land safely. |
556719e8696c25b4ac3572453768229c | 22.843 | 5.3.5 Existing features partly or fully covering the use case functionality | - "Aerial subscription" option in subscription, as specified in Rel-15;
- UAV / UAV-C association, as in TS 23.256 for example;
- Tracking of the geolocalization of the UAV as in TS 23.256 for example. |
556719e8696c25b4ac3572453768229c | 22.843 | 5.3.6 Potential New Requirements needed to support the use case | [PR 5.3.6-001] The 5G system shall be able to be informed of VLoS regulatory requirements (e.g. maximal distance threshold) and shall be informed if the UTM needs to be supported in meeting such requirements for a given UAS.
[PR 5.3.6-002] The 5G system shall be able to track the UAV-Controller, regardless of the type ... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.4.1 Description | Collection of information for UAV detection and avoidance in order to support tactical deconfliction is one of the key functions to guarantee UAV service safety. Previous studies on 3GPP mostly focused on the aspect that the detection and resolution of collisions is locally performed between UAVs using direct UAV to UA... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.4.2 Pre-conditions | UAV A is 3GPP aerial UE and subscribes the communication service from 5G network.
UAV B is an aerial vehicle not capable of 3GPP communications and could setup communication with USS/UTM directly. |
556719e8696c25b4ac3572453768229c | 22.843 | 5.4.3 Service Flows | Figure 5.4.3-1: Network-assisted UAV DAA
1. UAV A registers in 5G network and can setup communications with UTM though 5G network. UAV B setup communication with UTM directly.
2. The UTM subscribes network-assisted UAV DAA service from Operator M.
3. Operator M could use base station(s) to perform sensing to collect in... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.4.4 Post-conditions | UAV A and B can fly safely under the control of UTM with the support of 5G network. |
556719e8696c25b4ac3572453768229c | 22.843 | 5.4.5 Existing features partly or fully covering the use case functionality | SA1 has performed a study on UAV DAA in previous releases, where related normative stage 1 requirements are introduced in TS 22.125 [3].
TS 22.125 [3] clause 6.2 introduces the network support for UAV detection as below:
[R-5.2.1-001] The 3GPP system shall provide a mechanism for a UTM to provide route data, along with... |
556719e8696c25b4ac3572453768229c | 22.843 | 5.4.6 Potential New Requirements needed to support the use case | [P.R 5.4.6-001] Based on operator’s policy, the 5G system shall be able to provide a method to provide UTM and UAVs with the information collected or generated by the 5G system (e.g., based on sensing results), including e.g. the location or relative distance of 3GPP UAVs and other flying objects (can be drones not usi... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.