Content for TR 22.843 Word version: 19.2.0

1… 5… 5.2… 5.3… 5.4… 5.5… 5.6… 5.7… 5.8… 5.9… 5.10… 6…

6.1 Network support and exposure for UAV usage 6.2 Safety and Security

6 Consolidated potential requirements p. 27

6.1 Network support and exposure for UAV usage p. 27

CPR #	Consolidated Potential Requirement	Original PR #
CPR 6.1-001	Based on operator's policy, the 5G system shall be able to support a method to predict, monitor network conditions and QoS (e.g. bitrate, latency, reliability) and report to 3rd party along a continuous geographic planned flight path of a UAV at specific times of its expected flight duration.	P.R 5.2.6-001 P.R 5.6.6-001
CPR 6.1-002	Based on operator's policy, the 5G system shall be able to provide UTM with the information about geographic areas where UAV service requirements could or could not be met based on predicted network conditions and QoS (e.g. bitrate, latency, reliability).	P.R 5.2.6-002
CPR 6.1-003	Based on a 3rd party request, the 5G system shall be able to assist the UTM with mechanism to provide to the 3rd party alternative UAV flight paths, e.g.,based on required waypoints, QoS, and exclusion zones.	P.R 5.2.6-003
CPR 6.1-004	Based on a 3rd party request and operator's policy, the 5G system shall be able to reconfigure network resources to provide the required QoS along a UAV planned flight path, e.g. at particular geographical area(s) and time(s).	P.R 5.2.6-004
CPR 6.1-005	The 5G system shall be able to support a mechanism to enable a network operator to track an airborne connected UE which does not have an aerial subscription.	P.R 5.7.6-001
CPR 6.1-006	The 5G system shall be able to support service enablement layer exposure mechanisms for the UTM or other authorized 3rd party to provide the UAV application with configuration information to route and switch traffic between one active and one standby PLMN connection, e.g. for C2 communication reliability and redundancy purpose, or to route different traffic across different PLMN connections simultaneously, e.g. C2 traffic via one PLMN and other data via the second PLMN. NOTE 1: The above requirement can be extended to scenarios where one network is a PLMN and one is an NPN. NOTE 2: There is no impact on legacy network selection. NOTE 3: It is assumed that UAV traffic handling, over each PLMN, is subject to NW control mechanisms (e.g. in accordance with MNO routing priorities, available QoS/NW resources, etc.).	P.R 5.8.6-001 P.R 5.9.6-001
CPR 6.1-007	The 5G system shall be able to support mechanisms for the UTM to configure different aerial flight zones where UAV application settings and communication QoS may be different, and provide network and UAV with means to identify those flight zones.	P.R 5.10.6-001
CPR 6.1-008	The 5G system shall be able to support mechanisms for the UTM to provide network and UAV with policy information including UAV application settings and communication QoS to be applied in specific aerial flight zones, e.g. based on flight zone type indicated or available to the UAV in a certain geographical location.	P.R 5.10.6-002
CPR 6.1-009	Based on operator and UTM policy, the 5G system shall be able to provide UTM with an airborne UE's location and 3GPP identity to fulfil the UTM's request. NOTE 6: The 3GPP identity and UE location is expected to be used by the UTM to determine the position of airborne objects containing the UE.	P.R 5.5.6-001
CPR 6.1-010	SSubject to user consent and national or regional regulation, based on operator and UTM policy, and the UTM's request, the 5G system may be able to provide aerial object location(s) derived using 5G Wireless Sensing to the UTM to fulfil the UTM's request. NOTE 4: The airborne object location(s) are expected to be used by the UTM to determine the position of airborne objects.	P.R 5.5.6-002

6.2 Safety and Security p. 29

CPR #	Consolidated Potential Requirement	Original PR #
CPR 6.2-001	The 5G system shall be able to detect that a connected UE is airborne, when the UE doesn't have an aerial subscription.	PR 5.1.6-001
CPR 6.2-002	The 5G system shall support means to determine whether UTM supports regulatory requirements e.g., maximal VLOS distance between the UAV and the UAV controller. NOTE 1: The requirement applies to the case of both UAV and UAV controller connected to the 3GPP network	PR 5.3.6-001
CPR 6.2-003	Based on operator's policy, the 5G system shall be able to support a method to monitor and provide a 3rd party with information about deviations and violations along a UAV flight path and time. NOTE 2: Deviations can be e.g. in location and/or time with respect to the original flight plan. Violations can be e.g. with respect to exclusion zones provided together with the flight plan or known via other means.	P.R 5.6.6-002
CPR 6.2-004	Based on operator's policy, the 5G system shall be able to support a method to provide UTM and UAVs with the information collected or generated by the 5G system (e.g., based on sensing results), including e.g. the location or relative distance between3GPP UAVs and other flying objects (can be drones not using 3GPP connectivity).	P.R 5.4.6-001
CPR 6.2-005	The 5G system shall be able to track the UAV-Controller, regardless of the type of connection.	PR 5.3.6-002
CPR 6.2-006	Based on MNO policies and/or regulatory requirements, the 5G system shall be able to inform the UTM, when the 5G system detects a specific UAV condition or event, in order to enable UTM control of the UAV communication (e.g., when detecting violation of exclusion zones or maximal distance between UAVs).	PR 5.3.6-003

7 Conclusion and recommendations p. 29

The present document contains several use cases and service requirements for enhanced UAV usage and safety.

It is recommended to define normative service requirements based on the consolidated potential requirements identified in clause 6.