Cloud Flight Management Service Stateless Object Data Sync
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Flight Management Systems (FMS) lack cloud-based connectivity, data storage, and distributed computing capabilities, limiting access and updating of flight data for pilots and ground personnel, and fail to provide platform independence for multiple aircraft types and historical data management.
Innovation Solution
A cloud-based flight management service using JSON object data formats for generating and storing data sets, enabling data sharing and updating between mobile devices and cloud servers, with a stateless object system for persistent data storage and access, allowing multiple users to input and modify flight plans without re-entering entire setups.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If current embedded FMS model is used, then system simplicity is maintained, but connectivity, data storage, and distributed computing capabilities are limited
Solution Approach 1:
The patent introduces a cloud-based server as an intermediary between the FMS and external systems. The server hosts the FMS application and provides cloud storage for flight data, enabling remote access and distributed computing while keeping the onboard system simple. The server acts as a mediator that handles complex data management, analytics, and multi-user access without requiring changes to the core FMS architecture.
2Ease of operation
If data is stored locally in current FMS, then access speed is fast, but multiple personnel cannot simultaneously access and update flight data
Solution Approach 1:
The cloud-based server provides universal access to flight data for multiple users simultaneously. The system supports concurrent access by pilots, ground personnel, and other stakeholders through web-based interfaces and mobile devices. The server manages data synchronization and version control, enabling collaborative work without requiring physical presence in the cockpit or repeated data entry.
3Ease of operation
If traditional FMS data storage is used, then data security is maintained, but remote access and updating prior to flight operations is not possible
Solution Approach 1:
The system enables preliminary data entry and flight plan preparation through web-based interfaces before the actual flight operations. Ground personnel can input flight data, update procedures, and prepare documentation in advance through the cloud server. This preliminary action reduces the workload during critical flight phases while maintaining data integrity through server-side validation and secure access controls.
4Adaptability or versatility
If current FMS system is used, then platform independence is limited, but ability to support multiple aircraft types and historical data is reduced
Solution Approach 1:
The cloud-based server creates and manages digital copies of flight data, procedures, and historical records that can be accessed by multiple aircraft types and platforms. The system stores standardized flight data models that can be replicated and adapted for different aircraft configurations. This copying approach enables platform independence while maintaining data consistency across diverse flight operations without requiring separate systems for each aircraft type.
Data Source
AI summary
Methods for providing a flight management service in a cloud computing environment, the method includes: receiving, an object request by a server from a mobile device wherein the server is located in the cloud computing environment including: at least a flight management system (FMS) connected to a stateless object; processing, by the connected FMS hosted by the server, the object request generating a resource object for a particular flight plan wherein the resource object includes a data set; storing, by the connected FMS, the data set at the stateless object in the cloud environment; and sending, by the server, an object response from the connected FMS to the mobile device, for accessing the data set of the stateless object for the particular flight plan.


