Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 29.257  Word version:  18.2.0

Top   Top   None   None   Next
1…   5…

 

1  Scopep. 11

The present document specifies the stage 3 Protocol and data model for the UAS Application Enabler (UAE) Server services, for enabling the support of Uncrewed Aerial System (UAS) applications over 3GPP networks. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the UAE Server.
The stage 2 application layer architecture for Uncrewed Aerial System (UAS), functional requirements, procedures and information flows necessary for enabling Uncrewed Aerial System (UAS) applications over 3GPP networks are specified in TS 23.255.
The common protocol and interface aspects for API definition are specified in clause 5.2 of TS 29.122.
Up

2  Referencesp. 11

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 29.122: "T8 reference point for Northbound Application Programming Interfaces (APIs)".
[3]
TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[4]
OpenAPI: "OpenAPI Specification Version 3.0.0", https://spec.openapis.org/oas/v3.0.0.
[5]
TR 21.900: "Technical Specification Group working methods".
[6]
TS 23.255: "Application layer support for Uncrewed Aerial System (UAS); Functional architecture and information flows".
[7]
TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3".
[8]
TS 29.572: "5G System; Location Management Services; Stage 3".
[9]
TS 23.222: "Common API Framework for 3GPP Northbound APIs; Stage 2".
[10]
TS 29.222: "Common API Framework for 3GPP Northbound APIs; Stage 3".
[11]
TS 33.122: "Security aspects of Common API Framework (CAPIF) for 3GPP northbound APIs".
[12]
RFC 6749:  "The OAuth 2.0 Authorization Framework".
Up

3  Definitions, symbols and abbreviationsp. 11

3.1  Definitionsp. 11

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.
For the purpose of the present document, the terms and definitions given in clause 3 of TS 23.255 also apply, including the ones referencing other specifications.
Up

3.2  Symbolsp. 12

Void.

3.3  Abbreviationsp. 12

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
CAA
Civil Aviation Authorities
DAA
Detect And Avoid
RSRP
Reference Signal Received Power
UAE
UAS Application Enabler
UAS
Uncrewed Arial System
UASS
UAS Application Specific Server
UAV
Uncrewed Aerial Vehicle
UAV-C
Uncrewed Aerial Vehicle - Controller
USS
UAS Service Supplier
UTM
UAS Traffic Management
Up

4  Overviewp. 13

The UAS Application Enabler (UAE) Server forms part of the UAS application enabler layer that aims to ensure the efficient use and deployment of UAS over 3GPP systems. The UAE Server supports for this purpose, among other functionalities defined in TS 23.255, the following functionalities:
  • UAS application layer support functions to a UASS (e.g. USS/UTM) over the Us reference point, i.e.:
    • C2 operation mode configuration management for a UAS (i.e. pair of UAV and UAV-C);
    • C2 communication modes switching control and management for a UAS (i.e. pair of UAV and UAV-C);
    • Real-Time UAV Connection Status Monitoring and Location reporting;
    • USS change management; and
    • DAA management;
      and
    • interaction with other UAE Servers over the UAE-E reference point, in order to support distributed UAE Server deployments.
Figure 4-1 shows the reference model of the UAS Application Layer, with a focus on the UAE Server:
Copy of original 3GPP image for 3GPP TS 29.257, Fig. 4-1: UAS Application Layer functional model
Figure 4-1: UAS Application Layer functional model
(⇒ copy of original 3GPP image)
Up

Up   Top   ToC