Sensors and integration
What sensor types DroneEAR AI consumes, how they integrate, and what interfaces are the documented path into existing command systems.
Principle: normalised detection events
DroneEAR AI does not consume raw audio recordings or RF captures. It consumes normalised detection events — a source, a coarse zone, a confidence value, a bearing and a timestamp. This is important for privacy and for integration: the sensor stays with the customer, and the fusion layer receives only what it needs for correlation.
The only positional data the layer handles is public ADS-B aircraft telemetry and the public network Remote ID positions of drones that identify themselves.
Types of acoustic sensors
DroneEAR AI is designed to consume events from both basic classes of acoustic sensors:
- Pressure arrays. Classic microphones in a geometric arrangement. Direction is derived from time delay. Optimised for a specific frequency band.
- Acoustic vector sensors. Measure both acoustic pressure and particle velocity. Direction in a single point, broadband, low SWaP. Suitable for deployment on UAVs, vehicles and ground sensors.
The fusion layer does not require a specific brand or model. It requires a normalised output — a detection event with the relevant attributes.
RF sensors
The RF layer detects control and telemetry links between drone and operator. It passively captures characteristic signatures in the bands drones use. RF detection is robust against darkness, fog and dust, but does not give a precise position — only a bearing or a presence.
Radar (planned)
Radar is currently planned as a source of detection events. Like the other sensors, radar would send normalised events into the fusion layer and the layer would correlate them with other sources. Real integration requires a pilot and a partner.
Interfaces and standards
DroneEAR AI is designed to push a scored alert into the operator's command system through recognised standards. Two public feeds are live today: ADS-B air traffic and network Remote ID shown as context. The other interfaces below are the documented integration path, not shipped connectors.
| Domain | Interfaces |
|---|---|
| Identification | Remote ID (ASTM F3411), ADS-B |
| Air / drone traffic | ASTERIX, U-space / UTM |
| Military C2 | STANAG 4586 / 4609, Link 16 / STANAG 5516 |
Deployment: on-premise and air-gapped
DroneEAR AI is designed for on-premise deployment at the customer or in an air-gapped environment. Data stays with the customer, all communication is encrypted and auditable. This is important for defence applications and for civil sites with data-protection obligations.
Note
Specific integration interfaces require a pilot and a partner. This page describes the design, not shipped connectors. For a technical discussion about integration, contact us.