Tech-invite3GPPspaceIETF RFCsSIP

Content for  TR 33.854  Word version:  17.1.0

Top   Top   None   None   Next
1…   5…   6…   6.1…   6.2…   6.3…   6.4…   6.5…   6.6…   6.7…   6.8…   6.9…   6.10…   6.11…   6.12…   6.13…   6.14…   6.15…   6.16…   7…


1  Scopep. 8

The present document contains a study on the security aspects of Uncrewed Aerial Systems (UASs). TS 22.125 contains the service requirements for UAS while TR 23.754 is studying aspects like the UAS connectivity, identification and tracking and TR 23.755 studies UAV services and application layer features. The security study of the present document provides key issue including security threat and potential requirements related to the work in these other specifications and develops and analyses solutions to these key issues. Finally the study provides some conclusions for potential normative work.

2  Referencesp. 8

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.
TR 21.905: "Vocabulary for 3GPP Specifications".
TS 22.125: "Unmanned Aerial System (UAS) support in 3GPP".
TR 23.754: "Study on supporting Unmanned Aerial Systems (UAS) connectivity, Identification and tracking".
TR 23.755: "Study on application layer support for Unmanned Aerial Systems (UAS)".
TS 23.273: "5G System (5GS) Location Services (LCS)".
ASTM F3411 19: "Standard Specification for Remote ID and Tracking",

3  Definitions of terms, symbols and abbreviationsp. 8

3.1  Termsp. 8

For the purposes of the present document, the terms 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.
The following definitions are adopted from TS 22.125 with Unmanned change into Uncrewed:
Uncrewed Aerial System (UAS)
UAV controller (UAV-C)
The following definitions are adopted from TR 23.754 with Unmanned change into Uncrewed:
Third Party Authorized Entity (TPAE)
Command and Control (C2) Communication
CAA (Civil Aviation Administration)-level UAV Identity
Networked Remote ID
Broadcast Remote ID
The following definitions are adopted from TR 23.755 with Unmanned change into Uncrewed:
UAS Service Supplier (USS)
UAS Traffic Management (UTM)
Uncrewed Aerial Vehicle (UAV)

3.2  Symbolsp. 9


3.3  Abbreviationsp. 9

For the purposes of the present document, the abbreviations given in TR 21.905 apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
Third Party Authorized Entity
Uncrewed Aerial Vehicle
UAV Controller
Uncrewed Aerial System
UAS Service Supplier
UAS Traffic Management

4  Overview of uncrewed Aerial Systems (UAS)p. 9

The main objective of 3GPP systems is to facilitate non-3GPP entities UAS Service Supplier (USS) and/or UAS Traffic Management (UTM), which supply services to Civil Aviation Authority (CAA), and provide UAS Remote Identification (Remote ID) services. UAS Remote ID refers to a UAS in flight provides identification and tracking information that can be received by regulatory agencies.
An Uncrewed Aerial System (UAS) is composed of an Uncrewed Aerial Vehicle (UAV) and a UAV controller (UAVC).
TPAE is the Third Party Authorized Entity which can monitor UAVs, access and track UAV data, and make controls to UAVs.
A UAV can be controlled by either a UAVC, TPAE, or UTM.
Clause 4 of TS 23.754 provides some architectural assumptions and requirements and an overall reference architecture for the supporting UAS.

Up   Top   ToC