Content for TS 23.255 Word version: 19.3.0

0… 5… 6… 7… 7.1a… 7.2… 7.3… 7.4… 7.5… 7.6… 7.7… 7.8… 7.9… 7.10… 8… 8.2.5… A B… C…

3.1 Terms 3.2 Abbreviations 4.1 General 4.2 Support for communications between UAVs 4.3 QoS provisioning for C2 communication 4.4 C2 communication mode switching 4.5 Support for monitoring of UAV location deviation 4.6 Support for reporting of UAV events 4.7 Support for multi-USS deployments 4.8 Support of detect and avoid services and applications
...

0 Introduction p. 9

In order to ensure efficient use and deployment of UAS on 3GPP networks an architecture for UAS application layer consisting of UAS application enabler is specified in this document.

The UAE application enabler capabilities takes into consideration the existing stage 1 and stage 2 work within 3GPP related to UAS in TS 22.125 and TS 23.256.

1 Scope p. 10

The present document specifies the functional architecture, procedures and information flows for UAS application enabler layer. This specification includes the capabilities of the application layer support for UAS that are necessary to ensure efficient use and deployment of UAS over 3GPP systems. The UAS application enabler capabilities applies to both EPS and 5GS.

2 References p. 10

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.125: "Unmanned Aerial System (UAS) support in 3GPP; Stage 1".

[3]

TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2".

[4]

TS 23.256: "Support of Uncrewed Aerial Systems (UAS) connectivity, identification, and tracking; Stage 2".

[5]

TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".

[6]

TS 23.501: "System architecture for the 5G System (5GS); Stage 2".

[7]

TS 23.558: "Architecture for enabling Edge Applications"

[8]

TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".

[9]

TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".

[10]

TS 26.348: "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point".

[11]

TS 29.214: "Policy and Charging Control over Rx reference point".

[12]

TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 Reference Point; Stage 3".

[13]

TS 23.502: "Procedures for the 5G System (5GS)".

[14]

TS 23.435: "Procedures for Network Slice Capability Exposure for Application Layer Enablement Service".

3 Definitions of terms and abbreviations p. 11

3.1 Terms p. 11

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.

DAA application policy:

The configuration provided to the UAS application specific client by a UAS application specific server for handling of detect and avoid.

DAA assist capability:

The functionality for the UAE layer to assist the UAV application specific layer with handling of detect and avoid during flight.

LDGS capability:

A UAE client with LDGS capability offers the ground based DAA support for the UAVs in the monitoring range of the LDGS. The Local DAA Ground-Station (LDGS) can be operated by a USS and can serve one or more USSes.

Multi-USS capability:

The functionality for the UAE layer to assist at change of USS during flight.

Multi-USS policy:

The configuration provided by a UAS application specific server to assist at change of USS.

Remote Identification (Remote ID) of UAS:

The ability of a UAS 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.

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.

UAV:

The Uncrewed Aerial Vehicle (also called remotely piloted aircraft or drone) of a UAS.

For the purposes of the present document, the following terms given in TS 22.125 apply

Command and Control (C2) Communication

Uncrewed Aerial System (UAS)

Uncrewed Aerial System Traffic Management (UTM)

UAV controller

For the purposes of the present document, the following terms given in clause 4.2 of TS 22.125 apply

Direct C2 Communication

Network-Assisted C2 communication

UTM-Navigated C2 communication

3.2 Abbreviations p. 11

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

Command and Control

CAPIF

Common API Framework for northbound APIs

DAA

Detect And Avoid

LDGS

Local DAA Ground Station

QoS

Quality of Service

SEAL

Service Enabler Architecture Layer

UAE

UAS Application Enabler

UAS

Uncrewed Aerial System

UAV

Uncrewed Aerial Vehicle

UAV-C

Uncrewed Aerial Vehicle-Controller

USS

UAS Service Supplier

UTM

UAS Traffic Management

4 Architectural requirements p. 13

4.1 General p. 13

[AR-4.1-a]

The UAS application enabler layer shall support one or more UAS applications.

[AR-4.1-b]

The UAE capabilities should be offered as APIs to the UAS applications.

4.2 Support for communications between UAVs p. 13

4.2.1 Description p. 13

This clause specifies the requirements for support for communications between UAVs.

4.2.2 Requirements p. 13

[AR-4.2-a]

The UAS application enabler layer shall provide mechanism to support communications between UAVs in a geographical area using unicast Uu.

4.3 QoS provisioning for C2 communication p. 13

4.3.1 Description p. 13

This clause specifies the C2 QoS provisioning related requirements.

4.3.2 Requirements p. 13

[AR-4.3.2-a]

The UAE layer capabilities shall enable C2 application QoS parameter provisioning for network-assisted C2 communications to the 3GPP network system.

[AR-4.3.2-b]

The UAE layer capabilities shall enable QoS differentiation for UAV operations.

[AR-4.3.2-c]

The UAE server shall be capable of obtaining monitoring events related to the C2 QoS fulfilment/unfulfilment from the UAE clients (UAV and/or UAV controller).

[AR-4.3.2-d]

The UAE layer capabilities shall enable QoS parameters modification to support meeting the C2 end-to-end application requirements, for paired-Uu connections between a UAV and UE-based UAV-C.

4.4 C2 communication mode switching p. 13

4.4.1 Description p. 13

This clause specifies the C2 communication mode switching related requirements.

4.4.2 Requirements p. 13

[AR-4.4.2-a]

The UAE Server shall provide a mechanism for configuring the C2 communication modes at the UAE Client (UAV and UAV-C).

[AR-4.4.2-b]

The UAE Client (UAV and UAV-C) and UAV Server shall provide mechanisms for switching between the C2 communication links.

[AR-4.4.2-c]

The UAE Client (UAV and UAV-C) shall provide a mechanism for selecting a primary and a secondary communication link based on C2 communication mode configuration information.

[AR-4.4.2-d]

The UAE Client (UAV or UAV-C) shall provide a mechanism to switch C2 communication link without involving the UAE Server when an immediate change of C2 communication mode is needed.

[AR-4.4.2-e]

The UAE Server shall provide a mechanism for monitoring the availability of ProSe/PC5 link for C2 communications.

[AR-4.4.2-f]

The UAE Client shall be capable of reporting the availability of ProSe/PC5 link for C2 communications.

4.5 Support for monitoring of UAV location deviation p. 14

4.5.1 Description p. 14

This clause specifies the requirements for location reporting capabilities to monitor the UAV location deviation.

4.5.2 Requirements p. 14

[AR-4.5.2-a]

The SEAL layer shall provide mechanism to support the monitoring of UAV location.

4.6 Support for reporting of UAV events p. 14

4.6.1 Description p. 14

This clause specifies the requirements for support for reporting of UAV events to USS/UTM.

4.6.2 Requirements p. 14

[AR-4.6.2-a]

The SEAL layer shall provide mechanism to support the reporting of the 3GPP related UAV events to the USS/UTM.

4.7 Support for multi-USS deployments |R18| p. 14

4.7.1 Description p. 14

This clause specifies the requirements for support of multi-USS deployments.

4.7.2 Requirements p. 14

[AR-4.7.2-a]

The UAE Server shall provide a mechanism for the UAE Client to report its multi-USS capability to the UAE Server.

[AR-4.7.2-b]

The UAE Server shall provide a mechanism for enabling USS for configuring the Multi-USS policies to the UAE Client (UAV).

[AR-4.7.2-c]

The UAV Server shall provide a mechanism to support change of USS during UAS operations.

[AR-4.7.2-d]

The UAE Client (UAV) shall provide a mechanism to support change of USS based on the policies for multi-USS configuration when an immediate change of USS is needed.

4.8 Support of detect and avoid services and applications |R18| p. 15

4.8.1 Description p. 15

This clause specifies the requirements related to support for detect and avoid services and applications.

4.8.2 Requirements p. 15

[AR-4.8.2-a]

The UAE Server shall provide a mechanism for the UAE Client to report its DAA assist capability to the UAE Server.

[AR-4.8.2-b]

The UAE Server shall provide a mechanism for enabling USS for configuring the DAA policies to the UAE Client (UAV).

[AR-4.8.2-c]

The UAE layer shall provide a mechanism for a UAS application specific server to obtain DAA related events for a UAV.

[AR-4.8.2-d]

The UAS application enabler layer shall provide a mechanism for a UAS application specific client to obtain DAA related events for a UAV.