Tech-invite3GPP-SpecsReleasesFeaturesEntitiesInterfacesSBIsIdentifiersTi+Search in Tech-invite

21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TS 22.125SA1
Unmanned Aerial System (UAS) support in 3GPP

use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced
V17.1.0 (Wzip)2019/12  16 p.
V16.3.0 (Wzip)  2019/09  10 p.

Rapporteur:  Mr. Hall, Edward

Interest in using cellular connectivity to support Unmanned Aerial Systems (UAS) is strong, and the 3GPP ecosystem offers excellent benefits for UAS operation. Ubiquitous coverage, high reliability and QoS, robust security, and seamless mobility are critical factors to supporting UAS command and control functions. In parallel, regulators are investigating safety and performance standards and Registration and licensing programs to develop a well-functioning private and civil UAS ecosystem which can safely coexist with commercial air traffic, public and private infrastructure, and the general population.
The 3GPP system can provide control plane and user plane communication services for UAS. Examples of services which can be offered to the UAS ecosystem includes data services for command and control (C2), telematics, UAS-generated data, remote identification, and authorisation, enforcement, and regulation of UAS operation.
The present document identifies the requirements for operation of Unmanned 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.

full Table of Contents for  TS 22.125  Word version:   17.1.0

Here   Top
1  ScopeWord-p. 5
2  References
[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".
[5] IMT 2020(5G): "Application for UAV in 5G White Paper", September 2018
3  Definitions, symbols and abbreviations
3.1  Definitions
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 deliver messages with information of command and control for UAV operation from a UAV controller or a UTM to a UAV.
Unmanned Aerial System (UAS): Composed of Unmanned Aerial Vehicle (UAV) and related functionality, including command and control (C2) links between the UAV and the control station, the UAV and the network, and for remote identification. An UAS may comprise of a UAV and a UAV controller.
Unmanned 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 Unmanned Aerial Vehicle (UAV).
3.2  SymbolsWord-p. 6
3.3  Abbreviations
4  Overview on UAS
4.1  General
An Unmanned Aerial System (UAS) is the combination of an Unmanned 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.
Unmanned 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.
4.2  C2 Communication [R17]
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 ipossible 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/departuring, 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.
5  Requirements for Remote Identification of UASWord-p. 7
6  Requirements for UAV usages [R17]Word-p. 10
7  Performance requirements [R17]Word-p. 11
A  UAS Reference ModelWord-p. 15
B  Change historyWord-p. 16

Up   Top