This microservice exposes a public API to record telemetry. It processes and moves telemetry to various storage platforms.
This microservice additionally exposes interfaces to request recent aircraft
telemetry. It streams processed telemetry to other microservices in need of
up-to-date aircraft status (such as svc-scheduler
and svc-guidance
).
Attribute | Description |
---|---|
Maintainer(s) | Services Team |
Stuckee | A.M. Smith (@ServiceDog) |
Status | Development |
Document | Description |
---|---|
High-Level Concept of Operations (CONOPS) | Overview of Arrow microservices. |
High-Level Interface Control Document (ICD) | Interfaces and frameworks common to all Arrow microservices. |
Requirements - svc-telemetry |
Requirements and user stories for this microservice. |
Interface Control Document (ICD) - svc-telemetry |
Defines the inputs and outputs of this microservice. |
Software Design Document (SDD) - svc-telemetry |
Specifies the internal activity of this microservice. |
Live telemetry can be used to update itineraries, confirm departure and arrival, predict unsafe conditions, and inform a customer of flight status.
Other microservices (such as svc-guidance
and svc-scheduler
) may request real-time flight status and telemetry to determine or improve routing.
svc-telemetry
should expose a public API for:
- Networked assets (vertiports, aircraft) to post telemetry data.
- Authorized users to stream telemetry data.
- Authorized users to request specific telemetry data.
It should expose a private API for:
- Other microservices to request flight status (e.g.
svc-scheduler
). - Other microservices to stream telemetry data (e.g.
svc-guidance
).
If telemetry is not being actively pushed to the network, svc-telemetry
should subscribe to existing ADS-B streams from third-party providers, such as Aerion, flightradar24, or FlightAware.
- These services cost a subscription fee but provide wide coverage.
- These services receive their ADS-B telemetry from proprietary facilities and through public crowdsourcing
- Individuals with software-defined radio USB dongles can forward capture ADS-B to the service in return for enterprise features on the service.
- They process the data, store it, and provide "real-time" streams to subscribers.
See the ICD for this microservice.
The types of telemetry supported are:
- ADS-B
- Conventional aircraft and ground telemetry
- ADS-B 1090 MHz broadcasts are required for all aircraft in USA and Europe.
- ADS-B Formation
svc-telemetry
also accepts the UUID of the sender that captured the ADS-B message.
- CCSDS
- Typically used in space applications.
- Data segment containing Arrow-defined telemetry formats for eVTOL.
Asset managers have the choice to stream ADS-B directly to the svc-telemetry
microservice, allowing the Arrow network to respond faster to real-time events than data that goes through a third-party ADS-B provider.
Real-time telemetry data may be considered by svc-scheduler
when calculating the estimated trip length. In a learning system, sufficient telemetry data may come to dissuade routes with excessive turbulence or headwinds.
The collection, storage, and providing of telemetry could be a point of revenue for the network. Would require authentication enforcement for API requests to specific endpoints.
See the High-Level CONOPS.
See the High-Level CONOPS.
Energy Efficiency
Telemetry can be used to refine routing and improve aircraft energy efficiency. For example, aircraft experiencing increased turbulence along a specific route will report sudden elevation changes in telemetry, which may inform future routes to avoid the region.
Fire Alerts
Real-time aircraft status can alert the network to aircraft crashes or other fire hazards that may pose a danger to the environment.
Vertiport Managers
Vertiport managers may track incoming aircraft through real-time telemetry and status streams.
Sales
Telemetry data may be marketable. Thorough business research may be conducted to pursue potential customers and correctly price data.
General Failures
A failure of this component could hinder the ability of svc-scheduler
or svc-guidance
to avoid unsafe flight conditions.
Data Corruption
Corrupt telemetry (such as bit flips) could appear to the system as if the asset has moved, had sudden acceleration, or has a new status. This could cause issues in svc-scheduler
or svc-guidance
. Checksums should be enforced on all received packets.
See Arrow Glossary.