The present document specifies architecture enhancements for supporting Uncrewed Aerial Systems (UAS) connectivity, identification, and tracking, according to the use cases and service requirements defined in TS 22.125.
The following functions are specified:
UAV Identification, authentication and authorization.
UAV tracking in the 3GPP system:
this includes how the 3GPP system can provide support for UAV to ground identification (e.g. to authorized third parties such as police devices).
handling of unauthorized UAVs and revocation of authorization.
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.
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 or TS 23.501.
3GPP UAV ID:
Identifier assigned by the 3GPP system and used by external AF (e.g. USS) to identify the UAV. GPSI is used as the 3GPP UAV ID.
Broadcast Remote ID:
The capability of providing Remote Identification and Tracking over broadcast radio links.
a UAV identity assigned by USS/UTM, and uniquely identifies a UAV at least within the scope of a USS.
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 or to report telemetry data from a UAV to its UAV controller or a UTM.
C2 Aviation Payload:
Contains application layer information sent by the UAS to the USS containing UAV pairing information and/or flight authorization information that is transparent to the 3GPP System.
C2 Authorization Payload:
Contains application layer information sent by the USS to the UAV containing e.g. C2 pairing information and/or C2 security information that is transparent to the 3GPP System.
C2 Pairing Information:
Contains UAV-C Addressing Information which may e.g. include the UAV-C IP Address.
Networked UAV Controller:
a UAV Controller connected to the 3GPP network and connected to the UAV via a 3GPP network.
Non-Networked UAV Controller:
a UAV Controller not connected to the 3GPP network and connected to UAV via a transport outside the scope of 3GPP, e.g. internet connectivity or direct wireless communication over a technology outside the scope of 3GPP.
Networked Remote ID:
The capability of providing Remote Identification and Tracking to a USS over 3GPP network.
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. The Remote ID information payload may include Serial Number or Session ID assigned to the UAV, location of the ground-station controller, emergency status indication, etc.
Third Party Authorized Entity:
is either a privileged Networked UAV Controller, or a privileged Non-Networked UAV Controller, or another entity which gets information on sets of UAV controllers and UAVs from the 3GPP network, and may be connected to the UAV via the Internet; it may be authorized by the UTM to interface with sets of UAV(s).
a 3GPP UAS Network Function for support of aerial functionality related to UAV identification, authentication/authorization and tracking, and to support Remote Identification.
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). In the scope of this specification, the term USS refers to both USS and USS/UTM.
UAS Traffic Management (UTM):
a system that can safely and efficiently integrate the flying UAV along with other airspace users. It provides 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).
The UAV controller of a UAS enables a drone pilot to control an UAV.
the entity owning and operating a UAV.
A transparent container to the 3GPP system that includes UUAA Aviation/Authorization Payload and/or C2 Aviation/Authorization Payload.
refers to establishment of connectivity for a UAS for communication with USS, for C2, for remote identification, and for UAV location and tracking.
A communication between a UAV and a USS other than C2 communication, by means of user plane data transmission for some UAS Services.
UUAA Authorization Payload:
Contains application layer information optionally including UUAA result for UAV consumption provided by the USS to the UAS which is transparent to the 3GPP System.
UUAA Aviation Payload:
Contains application layer information provided by the UAS to USS and is transparent to the 3GPP System
Uncrewed Aerial System (UAS):
Composed of Uncrewed 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.
A list of the UAVs to be identified in the target area and served by the PLMN as the result of the UAV tracking requested by USS/UTM.
UAV USS authentication and authorization procedure of the UAV to ensure that the UAV has successfully registered with a USS and has therefore been authorized for operations by the USS. An UAV is authenticated and authorized by USS via a UUAA procedure with the support of the 3GPP system before connectivity for UAS services is enabled.
the UUAA procedure optionally performed during registration to a 5GS.
the UUAA procedure performed during the establishment of a PDU session, and performed during the establishment of a PDN connection.
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.