CPDLC messages are used for communication between controller and pilot. Traditionally, all received and sent messages are displayed in a list box format. The pilot normally opens up the list box and opens an individual message to read. The pilot must navigate between review and new menus to read the messages. There are several different message types, such as reports, conditional clearances, and loadable messages. In the case of reports, a report is formed and sent when a particular scenario or set of conditions is met.
In one embodiment, a graphical in-flight message representation system is provided. The system comprises a sensor configured to measure a characteristic of a flight of an aircraft and a communication device configured to send and receive in-flight messages. An in-flight message is a message communicated during the flight of the aircraft. The system also comprises a display unit configured to display a graphical flight progress indicator and one or more message icons, each of the one or more message icons corresponding to a respective in-flight message. The graphical flight progress indicator is representative of the characteristic of the flight measured by the sensor. Each of the one or more message icons are displayed in location relative to the graphical flight progress indicator based on the measured characteristic of the flight when the respective in-flight message was communicated.
Understanding that the drawings depict only exemplary embodiments and are not therefore to be considered limiting in scope, the exemplary embodiments will be described with additional specificity and detail through the use of the accompanying drawings, in which:
In accordance with common practice, the various described features are not drawn to scale but are drawn to emphasize specific features relevant to the exemplary embodiments.
In the following detailed description, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration specific illustrative embodiments. However, it is to be understood that other embodiments may be utilized and that logical, mechanical, and electrical changes may be made. Furthermore, the method presented in the drawing figures and the specification is not to be construed as limiting the order in which the individual steps may be performed. The following detailed description is, therefore, not to be taken in a limiting sense.
Each message icon is depicted on the flight progress indicator 101 to indicate when and/or where the message was received or sent in relation to the flight progress. The first message icon 111 is represented graphically as a message box which appears early on the flight progress indicator 101, which in this example indicates that the message occurred while the aircraft was on the ground. Each message icon is accompanies by either an uplink indication 103 or a downlink indication 105. The uplink indication 103 indicates an uplink communication from the controller to the plane. In this example, the uplink indication 103 is displayed as an upward pointing arrow. However, the uplink indication 103 can be implemented differently in other embodiments. For example, in some embodiments, the uplink indication 103 is a word, such as “up” which accompanies each corresponding uplink message icon. The downlink indication 105 indicates a downlink communication from the plane to the controller. In this example, the downlink indication is implemented as a downward pointing arrow. However, it is to be understood that the downlink indication can be implemented differently in other embodiments. For example, in some embodiments, the downlink indication 105 is a word, such as “down” which accompanies each corresponding downlink message icon, or the message is color coded, shaded, or can have a different border outline.
In this example, the uplink message icons on the flight progress indication 101 also include a departure clearance message icon 112; a message icon 113 indicating C level 3000; a message icon 114 indicating maintain 3000; a message icon 116 indicating descent 2000 ft.; and a message icon 117 indicating a gate assignment. The message icon 114 is color coded to indicate a different status or priority of a message. In another embodiment, this can be accomplished through the use of different fonts, font sizing, or other similar techniques. The gate assignment message icon 117 is also color coded to indicate a different status and/or priority.
The message icon 115 indicates a weather request message and is accompanied by a downlink indication 105. The request weather message icon 115 is color coded to indicate a different status or priority from the other messages, similar to message icons 114 and 117. The message icons are displayed along the flight progress indicator 101 according to when the message was sent or received, and also color coded to indicate status and/or priority on one display screen. The pilot can select an individual message to open and read from this screen.
In this example, selecting a message, such as by hovering over, clicking on or otherwise pointing to the message box, will cause related messages to be highlighted with a colored border. For example, selecting message 205-1 highlights related message 205-3 with a red-colored border. In one embodiment, this indicates that the messages have related Message Identification Numbers (MIN) and Message Reference Numbers (MRN). In other embodiments, the related messages can be identified by using different color coding, font display settings, displaying the MIN and MRN numbers themselves, arrows or lines between messages, or through other changes known to those having ordinary skill in the art.
Selecting a message also displays the message on the screen and creates a response dialog 204. For example, in the example of
The response dialog 204 displays the contents of the selected message, along with response options 207. The response options in this example are “Wilco,” “Standby,” and “Unable.” In other messages, other response options may be presented depending on the message requirements, and the system requirements of other embodiments. Other response options include “Accept” and “Reject;” “Affirmative” and “Negative;” “Roger.” For these response options, a “Standby” response option will almost always accompany the other response options. For some messages, response options might include the option of responding with a report, and in some cases, not having a response option at all the message only needing to be viewed. If the message or messages do not fit on the display screen, zooming functionality may be implemented in the message display system 200. This will cause horizontal scrollbar 210 and vertical scrollbar 208 to appear on the display to navigate the message display 200. In other embodiments, the message may be opened, taking the user to the actual message page and displaying the message itself. In one embodiment, once the message has been responded to, a “Clear” button is provided in the response dialog. The “Clear” button allows the pilot to clear the message dialog.
A flight path 315 overlay is displayed as a layer of the map GUI 310. A selectable message filter 320 provides the user control over what kind of datalink communication, or what type of messages the user wishes to view on the overlay. In one embodiment, the options provided for the selectable message filter 320 are Air Traffic Control (ATC), Flight Information Service (FIS), Company or Airline Operation Communications (AOC), or ALL. Graphical representations of in-flight messages can be added as a map layer and are positioned on the flight path according to time received along the intended or actual flight path. The messages themselves are depicted on the flight path as selectable message icons 321, 323, 325, 327, and 329. Arrows originating from the message icon point to a location on the flight path 315 where the aircraft was located when the message was sent or received. A company message is shown from earlier in the flight path at message icon 329. In some embodiments, when a new message is received, the newly received message or messages can be auto-selected or auto-displayed, such as when another message isn't already being viewed. In some embodiments, a message icon is color coded to indicate that it has not been responded to. This is depicted in
The communication device 610 is coupled to a display unit 620 on which a flight progress indicator and message icons can be displayed, as discussed above. In one embodiment, the display unit 620 can graphically represent a map GUI, and has overlay functionality that allows a user or pilot to graphically layer a flight path, as well as in-flight messages from the communication device 610. The display unit 620 can be implemented as any display unit which is capable of displaying graphical content. Suitable exemplary display units include, but are not limited to, a display associated with the FMS/FMC itself, a multifunction display (MFD), and/or a display associated with a CMU/CMF. Suitable technologies for implementing the display unit 620 include, but not limited to, a cathode ray tube (CRT) display, an active matrix liquid crystal display (LCD), a passive matrix LCD, or plasma display unit.
The communication device 610 is also coupled to a user interface device 640. The user interface device is configured to provide user selections and input to the communication device 610. The user input device 640 can be implemented as, but is not limited to, keyboards, touch screens, microphones, cursor control devices, line select buttons, glareshield buttons, etc. In some embodiments, the user input device 640 comprises more than one type of input device. In addition, the user input device 640 and the display unit 620 can be implemented as a single device, such as in the case of a touch screen device, or a Multipurpose Control Display Unit (MCDU). The communication device 610 is also directly or indirectly coupled to information from one or more sensors 650. Each sensor 650 configured to measure a characteristic of the flight. For example, the sensor 650 can be implemented in one embodiment as a global positioning system (GPS) receiver to measure the geographic location of the aircraft during flight. In another embodiment, the sensor 650 can be implemented as a timer to measure the time during flight or an altimeter to measure the altitude of the aircraft. It is to be understood that other sensors can be implemented in other embodiments and that more than one sensor can be used directly or indirectly.
The communication device 610 includes a processor 611 and a memory 613 having graphical message instructions 615 stored thereon. Processor 611 executes the graphical message instructions 615 in performing the functionality discussed herein to graphically represent messages. These instructions are typically stored on any appropriate computer readable medium used for storage of computer readable instructions or data structures. The computer readable medium can be implemented as any available media that can be accessed by a general purpose or special purpose computer or processor, or any programmable logic device. Suitable processor-readable media may include storage or memory media such as magnetic or optical media. For example, storage or memory media may include conventional hard disks, Compact Disk-Read Only Memory (CD-ROM), volatile or non-volatile media such as Random Access Memory (RAM) (including, but not limited to, Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate (DDR) RAM, RAMBUS Dynamic RAM (RDRAM), Static RAM (SRAM), etc.), Read Only Memory (ROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, etc. Suitable processor-readable media may also include transmission media such as electrical, electromagnetic, or digital signals, conveyed via a communication medium such as a network and/or a wireless link.
In operation, when a message is received at the communication device 610 from the radio 630, the processor 611 sends control signals to the display unit 620 causing the display unit 620 to display a message icon representing the received message. In particular, the control signals cause the display unit 620 to display the message icon on a flight progress indicator based on when the message was received in relation to the characteristic measured by the sensor 650, as discussed above. Additionally, when a message is sent from the communication device 610, the processor 611 sends control signals to the display unit 620 to display a message icon representing the sent message on the flight progress indicator based on the characteristic measured by the sensor 650 when the message was sent, as discussed above.
In addition, as discussed above, a user can select a message icon using the user input device 640. For example, the user can select a message icon for review of a summary or for opening a response dialog, as discussed above. Based on the user input, the processor 611 provides control signals to the display unit to display the corresponding information. For example, in one embodiment, when a message is selected by hovering a pointer over a message icon, the processor 611 causes the display unit 620 to highlight related messages and/or provide a summary box with a summary of the message content. The summary of the message content is computed by the processor 611 based on the message content in the corresponding message. Hence, system 600 is configured to provide the graphical representation of messages as discussed above with respect to
Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement, which can achieve the same purpose, may be substituted for the specific embodiments shown. Therefore, it is manifestly intended that this invention be limited only by the claims and the equivalents thereof.
Number | Name | Date | Kind |
---|---|---|---|
5057835 | Factor et al. | Oct 1991 | A |
5208590 | Pitts | May 1993 | A |
6154637 | Wright | Nov 2000 | A |
6160497 | Clark | Dec 2000 | A |
6501392 | Gremmert | Dec 2002 | B2 |
6661353 | Gopen | Dec 2003 | B1 |
6700482 | Ververs et al. | Mar 2004 | B2 |
6832138 | Straub et al. | Dec 2004 | B1 |
7177731 | Sandell et al. | Feb 2007 | B2 |
7272471 | Palich et al. | Sep 2007 | B1 |
7312725 | Berson et al. | Dec 2007 | B2 |
7363119 | Griffin, III et al. | Apr 2008 | B2 |
7787999 | Barber | Aug 2010 | B1 |
7876238 | Vandenbergh et al. | Jan 2011 | B2 |
8164487 | Tsai | Apr 2012 | B1 |
8195347 | Boorman | Jun 2012 | B2 |
8285427 | Rogers et al. | Oct 2012 | B2 |
8417396 | Goodman et al. | Apr 2013 | B2 |
8686878 | Whitlow et al. | Apr 2014 | B2 |
8760319 | Kommuri | Jun 2014 | B2 |
9019128 | Kim | Apr 2015 | B1 |
9132913 | Shapiro et al. | Sep 2015 | B1 |
20030004619 | Carriker et al. | Jan 2003 | A1 |
20030193408 | Brown et al. | Oct 2003 | A1 |
20030193411 | Price | Oct 2003 | A1 |
20040059472 | Hedrick | Mar 2004 | A1 |
20040254691 | Subelet | Dec 2004 | A1 |
20050049762 | Dwyer | Mar 2005 | A1 |
20050203676 | Sandell et al. | Sep 2005 | A1 |
20070200731 | Winkler | Aug 2007 | A1 |
20070219679 | Coulmeau | Sep 2007 | A1 |
20080027629 | Peyrucain et al. | Jan 2008 | A1 |
20100153875 | O'Flynn et al. | Jun 2010 | A1 |
20110166772 | Ferro et al. | Jul 2011 | A1 |
20120215388 | Pepitone et al. | Aug 2012 | A1 |
20130249712 | Buratto et al. | Sep 2013 | A1 |
20140309821 | Poux et al. | Oct 2014 | A1 |
20140320417 | Pakki et al. | Oct 2014 | A1 |
20150002316 | Sridhar et al. | Jan 2015 | A1 |
20160019794 | Dominic et al. | Jan 2016 | A1 |
20160047674 | Ramaiah et al. | Feb 2016 | A1 |
20160161283 | Shamasundar et al. | Jun 2016 | A1 |
Number | Date | Country |
---|---|---|
2244215 | Oct 2010 | EP |
2506237 | Oct 2012 | EP |
WO 2011128835 | Oct 2011 | SG |
2009046462 | Apr 2009 | WO |
2011128835 | Oct 2011 | WO |
Entry |
---|
The European Patent Office, “European Search Report”, “from EP Counterpart of U.S. Appl. No. 13/794,089”, Jul. 11, 2014, Published in: EP. |
Baxley et al, “Use of Data Comm by Flight Crew in High-Density Terminal Areas”, “American Institute of Aeronautics and Astronautics”, Sep. 2010, pp. 1-14. |
Shamasundar et al., “Systems and Methods for Displaying Position Sensitive Datalink Messages on Avionics Displays”, “U.S. Appl. No. 14/559,755, filed Dec. 3, 2014”, Dec. 3, 2014, pp. 1-30. |
Adams et al, “Incorporating Data Link Messaging Into a Multi-Function Display for General Aviation Aircraft”, “25th International Congress of the Aeronautical Sciences”, 2006, pp. 1-9. |
Mueller, “Experimental Evaluation of an Integrated Datalink and Automation-Based Strategic Trajectory Concept”, “7th AIAA Aviation Technology, Integrated and Operations Conference”, Sep. 18-20, 2007, pp. 1-15, Publisher: American Institute of Aeronautics and Astronautics. |
U.S. Patent and Trademark Office, “Office Action”, “U.S. Appl. No. 14/559,755”, Apr. 19, 2016, pp. 1-41. |
U.S. Patent and Trademark Office, “Final Office Action”, “U.S. Appl. No. 14/559,755”, Sep. 21, 2016. |
Number | Date | Country | |
---|---|---|---|
20140253585 A1 | Sep 2014 | US |