Abstract: The invention relates to an electronic device generating a flight plan for an aircraft, comprising: a display module configured for displaying two flight plans simultaneously and for each flight plan, for viewing, the common elements and distinct elements with regard to the other flight plan. an acquisition module configured for acquiring a copy command. a copying module configured for copying at least one of the distinct elements from one of the two flight plans to the other flight plan based on the copy command; and a processing module configured for generating a new flight plan based on the target flight plan and the distinct element or elements which were copied.

Abstract: Systems and methods for communicating avionic data to a non-avionic device situated outside of the cockpit of an aircraft are provided. A method may comprise the steps of receiving a request, aimed at receiving avionic data from avionic systems, from a non-avionic client device; determining the distance between the non-avionic device and the cockpit of the aircraft; and adjusting the sending of data in response to the request depending on the determined distance. Developments of the invention describe the use of a wireless access point associated with a secure gateway determining the access rights to the avionic data for the non-avionic device, various sending and/or display adjustments depending notably on the distance, threshold management, various indoor positioning techniques, unilateral or bilateral communications, various notifications, the use of lightweight connected clients (for example earpiece, watch, glasses, etc.).

Abstract: Systems and methods for communicating avionic data to a non-avionic device, the method includes the steps of: receiving a flight command from a non-avionic lightweight client; determining or receiving physiological data (for example gaze tracking, heart rate, breathing rate, etc.) and/or biometric data associated with the wearer of the non-avionic lightweight client; making the insertion of the flight command into an avionic system conditional on the meeting of predefined conditions relating to the physiological and/or biometric data. Developments describe the use of distance and/or path between lightweight client and cockpit, physiological parameter management, the management of flight commands in a plurality of elementary requests, notification techniques and/or audio and/or visual rendering on various lightweight clients (for example earpiece, watch, telephone, tablet, glasses, etc.). Some software aspects are described.

Abstract: Systems and methods for communicating avionic data to a non-avionic device situated outside of the cockpit of an aircraft are provided. A method may comprise the steps of receiving a request, aimed at receiving avionic data from avionic systems, from a non-avionic client device; determining the distance between the non-avionic device and the cockpit of the aircraft; and adjusting the sending of data in response to the request depending on the determined distance. Developments of the invention describe the use of a wireless access point associated with a secure gateway determining the access rights to the avionic data for the non-avionic device, various sending and/or display adjustments depending notably on the distance, threshold management, various indoor positioning techniques, unilateral or bilateral communications, various notifications, the use of lightweight connected clients (for example earpiece, watch, glasses, etc.).

Abstract: Systems and methods for communicating avionic data to a non-avionic lightweight client device, a method includes, for example, the steps of: receiving avionic data from a plurality of avionic systems modifying the received avionic data, by adding or deleting or fusing data; displaying the modified data on one or more non-avionic lightweight clients. Developments describe the use of a wireless access point associated with a secure gateway, multiplexed communications, data sending and/or display adjustments depending on target resources, display distributions, capturing the subjective view of the wearer of the non-avionic device using a worn camera, or cooperation between flight crew members. The lightweight clients may be connected objects (for example earpiece, watch, telephone, tablet, glasses, etc.). Some software aspects are described.

Abstract: A method implemented by computer in or for a flight management system or FMS, comprises the steps of receiving requests issued by clients; determining a correspondence between the requests and predefined unitary services executable by at least one server associated with the FMS; queuing the unitary services determined in one or more queues; determining a response time associated with each request; and notifying at least one client of the response time to its request. Developments describe the processing of queues, the management of priorities, the existence of fixed-price contracts, caching mechanisms, interruptions of queues, cancellations of requests, voting mechanisms, etc. The unitary services in particular can be avionics services of ATA (Air Transport Association) type. Systems aspects and software aspects are described.

Abstract: Various methods for regulating and/or for integrating avionic systems with non-avionic or open systems are described. Developments of the invention describe in particular various methods for synchronizing data via a sharing space, methods for modifying the data, human-machine interactions, steps of optimizing calculations and bandwidth, of determining alerts relating to the risks associated with calculation differences, and mechanisms for securing the secured storage space. Software and system aspects are described (EFB and FMS).

Abstract: The system executes services by an application called “server” for at least one application called “client.” A preliminary step establishes for each service a list of calculation parameters that can be varied in a given range, called “adjustable parameters” as well as time and quality of the said service information according to the value of the said parameters. At the request of a client for a given service, the method adjusts the value of the adjustable calculation parameters as a function of a given constraint, the service being executed using the adjusted values of the said parameters.

Abstract: A system executes services by a “server” for a “client”. A preliminary step establishes a list of available services of the server, set up for the client, in which a processing time is determined releasable by the server for the client per code execution cycle minor frame (“MIF”). The system creates on start-up: NT execution tasks for the client, each having a priority of execution level and an allocated average duration of execution, a number of execution tasks (NT) being at least 1, the sum of durations of the tasks being at most the releasable processing time; execution rules associating each of the tasks with at least one service of the list; then, during each MIF cycle, the system executes the services on their associated tasks, a task executed by priority and for at most its allocated average time of execution, the non-executed part of a service being executed on its associated task in the next cycle.

Abstract: A method implemented by computer in or for a flight management system or FMS, comprises the steps of receiving requests issued by clients; determining a correspondence between the requests and predefined unitary services executable by at least one server associated with the FMS; queuing the unitary services determined in one or more queues; determining a response time associated with each request; and notifying at least one client of the response time to its request. Developments describe the processing of queues, the management of priorities, the existence of fixed-price contracts, caching mechanisms, interruptions of queues, cancellations of requests, voting mechanisms, etc. The unitary services in particular can be avionics services of ATA (Air Transport Association) type. Systems aspects and software aspects are described.

Abstract: The system executes services by an application called “server” for at least one application called “client.” A preliminary step establishes for each service a list of calculation parameters that can be varied in a given range, called “adjustable parameters” as well as time and quality of the said service information according to the value of the said parameters. At the request of a client for a given service, the method adjusts the value of the adjustable calculation parameters as a function of a given constraint, the service being executed using the adjusted values of the said parameters.

Abstract: A system executes services by a “server” for a “client”. A preliminary step establishes a list of available services of the server, set up for the client, in which a processing time is determined releasable by the server for the client per code execution cycle MIF. The system creates on start-up: NT execution tasks for the client, each having a priority of execution level and an allocated average duration of execution, NT being at least 1, the sum of durations of the tasks being at most the releasable processing time; execution rules associating each of the tasks with at least one service of the list; then, during each MIF cycle, the system executes the services on their associated tasks, a task executed by priority and for at most its allocated average time of execution, the non-executed part of a service being executed on its associated task in the next cycle.