Aircraft FMS API Service Layer for Non-Interrupting Flight Data Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems rely on simulated or predicted flight data, which are not as accurate as actual flight data, leading to inefficiencies and safety concerns in flight operations.
Innovation Solution
A flight management system (FMS) service layer executing on a separate thread from the core functions, providing a networked node server that responds to queries from external applications for real-time flight data without interrupting core functions, using a unique client ID and secure communication protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a single thread executes both FMS core functions and handles external application queries, then device complexity is reduced, but system reliability deteriorates because queries may interrupt core functions
Solution Approach 1:
The patent divides the FMC execution threads into separate segments: one dedicated to FMS core functions and another dedicated to handling external application queries. This segmentation ensures that query processing does not interrupt core flight management operations, thereby maintaining system reliability while managing complexity through structured thread separation.
Solution Approach 2:
The patent introduces an intermediary mechanism (the second thread acting as a mediator) that handles external queries without directly interfering with the core FMS functions. This intermediary thread processes requests from external applications while maintaining isolation from the critical FMS execution path, ensuring data accuracy and system reliability.
2Adaptability or versatility
If real-time flight data is provided to multiple external applications, then adaptability improves, but device complexity increases due to multiple communication channels
Solution Approach 1:
The patent implements a universal query handling mechanism where a single second thread manages communication with multiple external applications through standardized API calls. This multi-functional approach allows the system to serve diverse client applications (flight tracking, analytics, maintenance systems) through a unified interface, improving adaptability without proportionally increasing complexity.
Solution Approach 2:
The patent uses client identifiers to create virtual copies or instances of query contexts for each external application. Each application receives data through its own isolated context managed by the second thread, allowing multiple applications to access real-time flight data simultaneously without sharing complex communication infrastructure, thus managing complexity while supporting versatility.
3Productivity
If flight data is extracted and provided to external applications, then productivity improves, but loss of information increases due to data extraction requirements
Solution Approach 1:
The patent extracts only the necessary flight data elements required by external applications through targeted queries handled by the second thread. This selective extraction approach provides fast data access to clients while minimizing the risk of information loss, as only specific data points are retrieved rather than the entire flight plan being copied or modified.
Solution Approach 2:
The patent implements feedback mechanisms where the second thread monitors and manages data requests to ensure that extraction operations do not compromise flight plan integrity. The system provides feedback about data availability and access status to external applications, ensuring that productivity gains from fast data access do not come at the cost of information accuracy or flight safety.
Data Source
Figure 1
Figure 2
AI summary
An avionics system in an aircraft for providing flight data from an onboard flight management computer (FMC) to requesting applications is disclosed. The system includes a flight management system (FMS) service layer executing on the FMC on a thread separate from a thread that executes FMS core functions. The FMS service layer provides a FMC networked node server for responding to queries from a plurality of external applications for data generated from the FMS core functions without interrupting the FMS core functions. The FMC networked node server is configured to: receive a request from a client application using a server specified API for data elements from a specified input flight plan; retrieve the specified input flight plan from the FMS core functions; extract the requested data elements; and output the requested data elements to the client application without affecting the active thread that executes FMS core functions.