4 Architectural requirements

23.2553GPPApplication layer support for Uncrewed Aerial System (UAS)Functional architecture and information flowsRelease 18TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

4.1 General

[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

4.2.1 Description

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

4.2.2 Requirements

[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

4.3.1 Description

This clause specifies the C2 QoS provisioning related requirements.

4.3.2 Requirements

[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

4.4.1 Description

This clause specifies the C2 communication mode switching related requirements.

4.4.2 Requirements

[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.

4.5 Support for monitoring of UAV location deviation

4.5.1 Description

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

4.5.2 Requirements

[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

4.6.1 Description

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

4.6.2 Requirements

[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

4.7.1 Description

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

4.7.2 Requirements

[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 reception of the policies for multi-USS configuration from the USS and further provide the 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.