5 Requirements for Remote Identification of UAS

22.1253GPPTSUnmanned Aerial System (UAS) support in 3GPP

5.1 General

[R-5.1-001] The 3GPP system should enable UTM to associate the UAV and UAV controller, identify them as a UAS.[R-5.1-002] The 3GPP system shall be able to provide UTM with the identity/identities of a UAS.

[R-5.1-003] The 3GPP system shall enable a UAS to send UTM the UAV data which can contain: unique identity (this may be a 3GPP identity), UE capability of the UAV, make & model, serial number, take-off weight, position, owner identity, owner address, owner contact details, owner certification, take-off location, mission type, route data, operating status.

[R-5.1-004] The 3GPP system shall enable a UAS to send UTM the UAV controller data which can contain: unique identity (this may be a 3GPP identity), UE capability of the UAV controller, position, owner identity, owner address, owner contact details, owner certification, UAV operator identity, UAV operator license, UAV operator certification, UAV pilot identity, UAV pilot license, UAV pilot certification and flight plan.

[R-5.1-005] The 3GPP system shall enable a UAS to send different UAS data to UTM based on the different authentication and authorizations level which are applied to the UAS.

NOTE: Subject to the regional regulation, the different authentication and authorization levels can be: the initial network access authentication and authorization, UAS identity authentication, UAV flight plan authorization, additional UTM service authentications, such as flight monitoring, collision avoidance services, so on.

[R-5.1-006] The 3GPP system shall support capability to extend UAS data being sent to UTM with the evolution of UTM and its support applications in future.

[R-5.1-007] Based on regulations and security protection, the 3GPP system shall enable a UAS to send UTM the identifiers which can be: IMEI, MSISDN, or IMSI, or IP address.

[R-5.1-008] The 3GPP system shall enable a UE in a UAS to send the following identifiers to a UTM: IMEI, MSISDN, or IMSI, or IP address

[R-5.1-009] The 3GPP system should enable an MNO to augment the data sent to a UTM with the following: network-based positioning information of UAV and UAV controller.

NOTE 1: This augmentation may be trust-based (i.e. the MNO informs the UTM that the UAV position information is trusted) or it may be additional location information based on network information, such as OTDOA, cell coordinates, synchronization source, etc.

NOTE 2: This requirement will not be applied to the case which the UAS and UTM has direct control communication connection without going through MNO, such as OTDOA, cell coordinates, synchronization source, etc.

[R-5.1-010] The 3GPP system shall enable UTM to inform an MNO of the outcome of an authorisation to operate.

[R-5.1-011] The 3GPP system shall enable an MNO to allow a UAS authorisation request only if appropriate subscription information is present.

[R-5.1-012] The 3GPP system shall enable a UAS to update a UTM with the live location information of a UAV and its UAV controller.

[R-5.1-013] The 3GPP network should be able to provide supplement location information of UAV and its controller to a UTM.

NOTE: This supplement may be trust-based (i.e. the MNO informs the UTM that the UAV position information is trusted) or it may be additional location information based on network information.

[R-5.1-014] The 3GPP network shall support UAVs and the corresponding UAV controller are connecting to different PLMNs at the same time.

[R-5.1-014a] The 3GPP system shall support UAVs and the corresponding UAV controller are connecting to different PLMNs at the same time.

[R-5.1-015] The 3GPP system shall provide the capability for network to obtain the UAS information regarding its support of 3GPP communication capabilities designed for UAS operation.

[R-5.1-016] The 3GPP system shall support the UAS identification and subscription data which can differentiate the UAS with UAS-capable UE and the UAS with non-UAS-capable UE.

NOTE: UAS-capable UE refers to the UE which support interaction capability with UTM and certain 3GPP communication features which 3GPP provides for UAS

[R-5.1-017] The 3GPP system shall support detection, identification and reporting of problematic UAV(s) and the UAV controller to a UTM.

5.2 UAS traffic management

5.2.1 General

NOTE: The following requirements are valid for both centralized and decentralized UTM.

[R-5.2.1-001] The 3GPP system shall provide a mechanism for a UTM to provide route data, along with flight clearance, to a UAV.

[R-5.2.1-002] The 3GPP system shall be able to deliver route modification information received from a UTM to a UAS with a latency of less than 500ms.

[R-5.2.1-003] The 3GPP system shall be able to deliver the notifications received from a UTM to a UAV controller with a latency of less than 500ms.

[R-5.2.1-004] Based on MNO policies and/or regulatory requirements, the 3GPP system shall enable the UTM to take over the communication used to control the UAV.

5.2.2 Decentralized UAS traffic management

[R-5.2.2-001] The 3GPP system shall enable a UAV to broadcast the following data for identifying UAV(s) in a short-range area for collision avoidance: e.g. UAV identities if needed based on different regulation requirements, UAV type, current location and time, flight route information, current speed, operating status.

[R-5.2.2-002] The 3GPP system shall be able to support a UAV to transmit a message via network connection for identifying itself as an UAV to the other UAV(s).

[R-5.2.2-003] The 3GPP system shall enable UAV to preserve the privacy of the owner of the UAV, UAV pilot, and the UAV operator in its broadcast of identity information.

[R-5.2.2-004] The 3GPP system shall enable a UAV to receive local broadcast communication transport service from other UAV in short range.

[R-5.2.2-005] A UAV shall be able to use a direct UAV to UAV local broadcast communication transport service in the coverage or out of coverage of a 3GPP network.

[R-5.2.2-006] A UAV shall be able to use a direct UAV to UAV local broadcast communication transport service when the sending and receiving UAVs are served by the same or different PLMNs.

[R-5.2.2-007] The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service at relative speeds of up to 320kmph.

[R-5.2.2-008] The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service with variable message payloads of 50-1500 bytes, not including security-related message component(s).

[R-5.2.2-009] The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which supports a range of up to 600m.

[R-5.2.2-010] The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which can transmit messages at a frequency of at least 10 messages per second.

[R-5.2.2-011] The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which can transmit messages with an end-to-end latency of at most 100ms.

5.3 Void

5.4 Security

[R-5.4-001] The 3GPP system shall protect the transport of data between the UAS and UTM.

[R-5.4-002] The 3GPP system shall protect against spoofing attacks of the UAS identities.

[R-5.4-003] The 3GPP system shall allow non-repudiation of data sent between the UAS and UTM at the application layer.

[R-5.4-004] The 3GPP system shall support the capability to provide different levels of integrity and privacy protection for the different connections between UAS and UTM as well as the data being transferred via those connections.

[R-5.4-005] The 3GPP system shall support confidentiality protection of identities related to the UAS and personally identifiable information.

[R-5.4-006] The 3GPP system shall support regulatory requirements (e.g. Lawful Intercept) for UAS traffic.