METHOD FOR PROVIDING FLIGHT MANAGEMENT SYSTEM DATA TO PERIPHERAL DEVICES

• US 20170063995A1
• Filed: 08/31/2015
• Published: 03/02/2017
• Est. Priority Date: 08/31/2015
• Status: Active Grant

• Current Assignee: The Boeing Co.
• Original Assignee: The Boeing Co.
• Inventors: Gunn, Peter, Ness, Patricia Suzan, Younkin, Katie, Murray, Daniel J., Cornell, Bradley D.
• Granted Patent: US 10,116,749 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: B60R 16/023 for transmission of signals between vehicle parts or subsystems
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 30/0635 Processing of requisition or of purchase orders
• CPC Class Codes: G08G 5/0021 located in the aircraft
• CPC Class Codes: G08G 5/0039 Modification of a flight plan
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Abstract

A flight management system may include a processor, a memory, a network communication interface, and a flexible data interface stored in the memory and executable by the processor. The flexible data interface is typically configured for providing an abstract data interface layer; retrieving, via the abstract data interface layer, data stored in the memory of the flight management system; and transmitting, via the network communication device, the data to a peripheral device in network communication with the flight management system.

Claims

1. A flight management system (102), comprising:

a processor (104);

a memory (106);

a network communication device;

a flexible data interface (112) stored in the memory (106), executable by the processor (104) and configured for;

providing an abstract data interface layer (113);

retrieving, via the abstract data interface layer (113), data stored in the memory (106) of the flight management system (102); and

transmitting, via the network communication device, the data to a peripheral device (124) in network communication with the flight management system (102).

2. The flight management system (102) according to claim 1, wherein:

the flexible data interface (112) is configured for determining that a trigger event has occurred;

retrieving the data stored in the memory (106) comprises retrieving the data stored in the memory (106) based on determining that the trigger event has occurred.

3. The flight management system (102) according to claim 2, wherein the trigger event is associated with a status of an aircraft (100).

4. The flight management system (102) according to claim 2, wherein the trigger event comprises receiving a request for the data from the peripheral device (124).

5. The flight management system (102) according to claim 1, wherein the abstract data interface layer (113) identifies a location of the data in the memory (106).

6. The flight management system (102) according to claim 1, wherein retrieving the data stored in the memory (106) and transmitting the data to a peripheral device (124) is based on a configuration file (114) stored in the memory (106), the configuration file (114) identifying the data and the peripheral device (124).

7. The flight management system (102) according to claim 1, wherein transmitting the data to the peripheral device (124) comprises transmitting the data to the peripheral device (124) via an onboard network system of an aircraft (100).

8. The flight management system (102) according to claim 1, wherein the peripheral device (124) is a laptop, electronic flight bag, tablet computer, or mobile device.

9. A method of providing data from a flight management system (102) to a peripheral device (124), the method comprising:

providing, via a computer processor (104), an abstract data interface layer (113);

retrieving, via a computer processor (104), data stored in a memory (106) of the flight management system (102); and

transmitting, via a network communication device, the data to a peripheral device (124) in network communication with the flight management system (102).

10. The method accordingly to claim 9, comprising determining that a trigger event has occurred;

wherein retrieving the data stored in the memory (106) comprises retrieving the data stored in the memory (106) based on determining that the trigger event has occurred.

11. The method accordingly to claim 10, wherein the trigger event is associated with a status of an aircraft (100).

12. The method accordingly to claim 10, wherein the trigger event comprises receiving a request for the data from the peripheral device (124).

13. The method accordingly to claim 9, wherein the abstract data interface layer (113) identifies a location of the data in the memory (106).

14. The method accordingly to claim 9, wherein retrieving the data stored in the memory (106) and transmitting the data to a peripheral device (124) is based on a configuration file (114) stored in the memory (106), the configuration file (114) identifying the data and the peripheral device (124).

15. The method accordingly to claim 9, wherein transmitting the data to the peripheral device (124) comprises transmitting the data to the peripheral device (124) via an onboard network system of an aircraft (100).

16. The method accordingly to claim 9, wherein the peripheral device (124) is a laptop, electronic flight bag, tablet computer, or mobile device.

17. A computer program product for providing data from a flight management system (102) to a peripheral device (124), the computer program product comprising a non-transitory computer-readable storage medium having computer-executable instructions for:

providing an abstract data interface layer (113);

retrieving data stored in a memory (106) of the flight management system (102); and

transmitting the data to a peripheral device (124) in network communication with the flight management system (102).

18. The computer program product according to claim 17, wherein:

the non-transitory computer-readable storage medium has computer-executable instructions for determining that a trigger event has occurred;

retrieving the data stored in the memory (106) comprises retrieving the data stored in the memory (106) based on determining that the trigger event has occurred.

19. The computer program product according to claim 17, wherein retrieving the data stored in the memory (106) and transmitting the data to a peripheral device (124) is based on a configuration file (114) stored in the memory (106), the configuration file (114) identifying the data and the peripheral device (124).

20. The computer program product according to claim 17, wherein transmitting the data to the peripheral device (124) comprises transmitting the data to the peripheral device (124) via an onboard network system of an aircraft (100).