Drone Remote ID is a system that allows drones to transmit identification and location information. This information can be received by other airspace participants, including authorities, pilots and the general public.

Bluetooth and WiFi Frameworks provide methods to receive and decode the Bluetooth LE and WiFi Beacon Drone Remote ID messages. At this time the frameworks support ASD-STAN and ASTM F3411 Remote ID protocols. You can download the Drone Remote ID receiving demo application from our GitHub repository. This simple demo application shows how to receive and decode Drone Remote ID broadcasting on Windows platform using any WiFi or Bluetooth adapters. The Bluetooth adapter must support Bluetooth 4 or above, Bluetooth 5 is preferred. Should you have any questions please do not hesitate to contacts us.

What is Remote ID

Remote ID requires any drone to broadcast identification information. This data includes the drone's identity, location, and flight details, providing valuable insights for authorities to monitor and track drone activities and tie these activities back to the pilot. Some have likened Remote ID to a drone license plate. Like license plates, although the drone pilot is not usually directly named, either a serial number or session ID is broadcast. This information can be used by authorized individuals, like police officers, to contact the FAA and get the drone pilots information.

Specifications

Wireless Communication Library is compliant with the following standards:

  • ASTM F3411 Specification for Remote ID and Tracking
  • ASD-STAN prEN 4709-002 Direct Remote Identification

Broadcast methods

There are four different broadcast methods are defined:

  • Bluetooth Legacy Advertising (Bluetooth 4.x)
  • Bluetooth Long Range with Extended Advertising (Bluetooth 5.x)
  • WiFi Neighbor-aware Network (Wi-Fi NaN)
  • WiFi Beacon

The broadcast method used with Bluetooth Legacy Advertising signals impose a strict size limitation on the amount of data that can be transmitted in each radio burst. Therefore the relevant data is divided into different categories and each category is transmitted via its own message.

Sample Application

The DRI demo application is available on GitHub by this link. Should you have any questions please do not hesitate to contact us.

Additional Resources