Content for TR 23.755 Word version: 17.0.0
1 Scope p. 6
The present document is a technical report which identifies the application architecture aspects to support UAS, and corresponding architectural solutions. The study includes identifying architecture requirements that are necessary to ensure efficient use and deployment of UAS services and applications over 3GPP systems.
The study takes into consideration the existing stage 1 work within 3GPP related to UAS in TS 22.125, TS 22.281 and TS 22.282. The study also takes into consideration the related system architecture developed by SA2 in TR 23.754. The recommendations from the study include architecture solutions that may be considered for normative work.
2 References p. 6
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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 22.071: "Location Services (LCS); Service description; Stage 1".
[3]
TS 22.125: "Unmanned Aerial System (UAS) support in 3GPP; Stage 1".
[4]
TS 22.261: "Service requirements for the 5G system; Stage 1".
[5]
TS 22.281: "Mission Critical Video services over LTE".
[6]
TS 22.282: "Mission Critical Data services over LTE".
[7]
TS 23.222: "Common API Framework for 3GPP Northbound APIs; Stage 2".
[8]
TS 23.271: "Functional stage 2 description of Location Services (LCS)".
[9]
TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2".
[10]
TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[11]
TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
[12]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[13]
TS 23.502: "Procedures for the 5G System; Stage 2".
[14]
TS 23.558: "Architecture for enabling Edge Applications".
[15]
TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications"
[16]
TR 23.754: "Study on supporting Unmanned Aerial Systems (UAS) connectivity, Identification and tracking".
[17]
TS 26.348: "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point".
[18]
TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3".
[19]
TS 36.305: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Stage 2 functional specification of User Equipment (UE) positioning in E-UTRAN".
[20]
TS 38.305: "NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN".
[21]
FAA UTM Concept of Operations v2.0: "Foundational Principles, Roles and Responsibilities, Use Cases and Operational Threads", https://www.faa.gov/uas/research_development/traffic_management/media/UTM_ConOps_v2.pdf .
[22]
FAA website (available on 12th July 2019): "FAA Remote Identification", https://www.faa.gov/uas/research_development/remote_id/ .
[23]
"IETF Drone Remote ID Protocol (DRIP) WG", https://datatracker.ietf.org/wg/drip/about/
[24]
ASTM F3411-19: "ASTM Standard Specification for Remote ID and Tracking", https://www.astm.org/Standards/F3411.htm .
[25]
"ATIS Unmanned Aerial Vehicles (UAVs) report", https://www.atis.org/01_strat_init/uav/ .
[26]
"ANSI Unmanned Aircraft Systems Standardization Collaborative (UASSC)", https://www.ansi.org/news_publications/news_story?menuid=7&articleid=fcf7a65b-23c7-4d87-a5c7-eb879d316898 .
[27]
"ICAO Remotely Piloted Aircraft Systems Panel (RPASP)", https://www.icao.int/safety/UA/Pages/Remotely-Piloted-Aircraft-Systems-Panel-(RPASP).aspx .
[28]
"Radio Technical Commission for Aeronautics (RTCA) UAS standards", https://www.rtca.org/content/standards-guidance-materials .
[29]
"ISO/TC 20/SC 16 Unmanned aircraft systems", https://www.iso.org/committee/5336224.html .
[30]
"EU U-Space", https://www.sesarju.eu/U-space .
3 Definitions, symbols and abbreviations p. 8
3.1 Definitions p. 8
For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
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.
Remote Identification (Remote ID) of UAS:
The ability of a UAS in flight to provide identification and tracking information that can be received by other parties, to facilitate advanced operations for the UAS (such as Beyond Visual Line of Sight operations as well as operations over people), assist regulatory agencies, air traffic management agencies, law enforcement, and security agencies when a UAS appears to be flying in an unsafe manner or where the UAS is not allowed to fly [22].
Unmanned Aerial System (UAS):
Composed of Unmanned Aerial Vehicle (UAV) and related functionality, including command and control (C2) links between the UAV and the UAV controller, the UAV and the network, and for remote identification. A UAS is comprised of a UAV and a UAV controller.
UAS Service Supplier (USS):
An entity that provides services to support the safe and efficient use of airspace by providing services to the operator / pilot of a UAS in meeting UTM operational requirements. A USS can provide any subset of functionality to meet the provider's business objectives (e.g., UTM, Remote Identification) [21].
UAS Traffic Management (UTM):
A set of functions and services for managing a range of autonomous vehicle operations (e.g. authenticating UAV, authorizing UAS services, managing UAS policies, and controlling UAV traffics in the airspace) [21].
UAV:
The Unmanned Aerial Vehicle (also called remotely piloted aircraft or drone) of a UAS.
UAV controller:
The UAV controller of a UAS enables a pilot to control a UAV.
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.
For the purposes of the present document, the following terms given in TS 22.125 apply
Command and Control (C2) Communication
3.2 Abbreviations p. 8
For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply.
An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
BVLOS
Beyond Visual Line of Sight
C2
Command and Control
Remote ID
Remote Identification
UAS
Unmanned Aerial System
UAV
Unmanned Aerial Vehicle
UAV-C
Unmanned Aerial Vehicle Controller
USS
UAS Service Supplier
UTM
UAS Traffic Management
4 Void
