ASD-STAN PREN 4709-002 PDF

This document provides means of compliance with the “Direct Remote Identification” requirements set in Regulation (EU) 2019/945 on Unmanned Aircraft Systems.

“Direct remote identification” means a system that ensures the local broadcast of information about a UA in operation.

More specifically, this document addresses drone’s capability to be identified during the whole duration of the flight, in real time and with no specific connectivity or ground infrastructure link, by existing mobile devices when within the broadcasting range. Such functionality, based on an open and documented transmission protocol (described in this document) contributes to address security threats and to support drones’ operators’ obligations with respect to citizens’ fundamental rights to privacy and protection of personal data. It can be used by law enforcement people, critical infrastructure managers, and public to get an instantaneous information on the drone flying around, providing various information such as UA serial number, UA navigation data and operational status, UAS Operator registration number and position as defined in the Delegated Regulation (EU) 2019/945.

Since Regulation (EU) 2019/945 requires DRI information to be broadcasted using an “open and documented protocol”, this standard does not define technological measures to protect the confidentiality of the data broadcasted.

Security

This document is limited to ensure conformity of the UAS with the requirements set in Parts 2,3,4 and 6 of Regulation (EU) 2019/945. Therefore:

- This document does not include the capability to store securely the UAS operator registration number.

- This document does not include the capability to protect communication against user and/or malicious modification of sensors output values involved in DRI information computation (like GNSS, Barometer, Magnetometer, and Accelerometer…) and the DRI radio-transmitter interface.

- This document does not include the capability to protect against user and/or malicious software and hardware modification of the geographical position, the timestamp, the height, the take-off position, the speed, or the route course of the UA/Add-on.

- This document does not include the capability to ensure DRI data integrity verification, or the capability to ensure detection that the UA/Add-on’s serial number is unique, when received by the Receiver Mobile Device. However, to provide such capabilities, a Digital Signature may be added to the DRI message.

- This document does not include the capability to ensure DRI data received by the receiver mobile device are genuine and come from a UA/Add-on belonging to a registered UAS Operator, or the capability to ensure detection of spoofing of the UAS Operator Registration Number. However, to provide such capabilities, a Digital Signature may be added to the DRI message.

DRI Display Software

This subclause is not to be considered as a DRI requirement, but for information only, in order for compatible mobile receiver devices to get DRI data interpretation and display capability.

As described in 4.2 the interested person uses a receiver mobile device (such as a smartphone) with specific RID Display Software to receive and display the information contained in Remote ID broadcasted by an UA.

To be easily accessible, the Display Software should be publicly available.

The Software should display all mandatory information described in 4.3. A way to display Remote ID could be a map view showing the position of the UA(s) together with the position of the smartphone.

All transport methods for Remote ID described in Clause 6 should be processed and displayed by the Software to be used as a testing tool. As the transport methods have different hardware requirements, a specific mobile receiver device may not be able to receive all transport methods. The Software should show the user which transport methods are supported by the present mobile receiver device.