Patent Grant
8965291
This disclosure relates generally to avionic data. More particularly, this disclosure relates to communicating avionic data based on the type of data and the quality of available communication channels.
As known, avionic data is typically collected from various areas of an aircraft. The avionic data is stored in data files on the aircraft. The data files are periodically communicated from the aircraft to a ground-based system. The aircraft also receives some data files from the ground-based systems to the aircraft. Some of the data files contain more critical data than other data files. As can be appreciated, communicating the data files containing the more critical data is more important than communicating other data files.
The data files may be wirelessly communicated through various communication channels, such as cellular channels, broadband Ethernet channels, WiFi channels, etc. The availability of channels for communicating the data files may change as the aircraft moves relative to the ground-based system. Often, some of the available communication channels are more expensive to use than other available communication channels.
Although a communication channel is available, that channel may be a experiencing a low quality of service. Atmospheric changes, mobile obstructions, availability of free channel bandwidth can all affect wireless quality of service, for example. For instance, when using a WiFi channel connected to a Gatelink service access point while the aircraft is parked at a gate, the system will have to share the available bandwidth of that access point with other transmitters. This could reduce the WiFi channel quality of service to a quality less than another competing communication channel of the same cost. As can be appreciated, the quality of a channel can change during a transmission. Transmitting data files using a channel with a low quality of service may result in a longer transmission time than if the data files were transmitted using a higher quality channel. If the selected channel is experiencing a low quality of service, multiple attempts may be required before a data file is successfully communicated.
An example avionic data communication method includes establishing a plurality of available channels using a channel controller. The channel controller also establishes a quality of service for each of the plurality of available channels. The channel controller then selects one of the available channels. The quality of service of the selected channel is not less than the quality of service of another channel within the plurality of available channels. The method then communicates a type of data using the selected channel.
Another example avionic data communication method includes establishing a plurality of available channel types using a channel controller. The channel controller module selects one of the plurality of available channel types. The quality of service of the selected channel type is not less than the quality of service of another channel type within the plurality of available channel types. The method communicates selected data between an aircraft and a ground-based system using the selected channel type.
An example avionic data communication arrangement includes a switcher module that is configured to select a communication channel from a plurality of available communication channels. The selected communication channel has a quality of service that is not less than the quality of service of another communication channel within the plurality of available channels. A controller module is configured to select data for a transmission that has an associated cost of transmission that does not exceed a cost of transmission threshold for the established channel.
These and other features of the disclosed examples can be best understood from the following specification and drawings, the following of which is a brief description.
During operation, air is pulled into the gas turbine engine 10 by the fan section 14, pressurized by the compressors 18 and 22, mixed with fuel, and burned in the combustor 26. The turbines 30 and 34 extract energy from the hot combustion gases flowing from the combustor 26. The residual energy is then expanded through the nozzle section to produce thrust.
In a two-spool design, the high-pressure turbine 30 utilizes the extracted energy from the hot combustion gases to power the high-pressure compressor 22 through a high speed shaft 38, and the low-pressure turbine 34 utilizes the extracted energy from the hot combustion gases to power the low-pressure compressor 18 and the fan section 14 through a low speed shaft 42.
In this example, a data communication arrangement 46 is mounted to the aircraft 12. The data communication arrangement 46 is configured to communicate avionic data between the aircraft 12 and a ground-based system 62. Example avionic data includes data collected from sensors 52 mounted within the gas turbine engine 10. The sensors 52 collect avionic data about the engine 10 during operation, such as temperatures, pressures, altitudes, etc.
The examples described in this disclosure are not limited to any specific aircraft or aircraft engine architecture. Additional examples may include avionic data from other areas of the aircraft, such as the landing gear system, environmental control system, braking system, navigational system, entertainment system, etc.
Referring now to
Avionic data is collected onboard the aircraft 12 and stored in data files 70 within a memory portion 74. A transmitter section 78 of the example arrangement 46 is configured to communicate the data files 70 to the ground-based system 62 using one of a plurality of communication channel types 82. The channel types 82 may include a cellular channel, a broadband Ethernet channel, a Wi-Fi channel, a WiMax channel, etc.
The example data communication arrangement 46 communicates selected ones of the data files 70 to the ground-based system 62 using one or more of the communication channel types 82. Off-load software within the data communication arrangement 46 is used to select communication channel types 82 for communicating the data files 70. Communication channel types 82 are selected based on the availability of the communication channel types 82, the present quality of service of the communication channel types 82, the cost of transmission, or some combination of these. The data communication arrangement 46 selects data files 70 for transmission based on the selected communication channel types 82.
The example data communication arrangement 46 is dynamic. For example, the data communication arrangement may periodically select a new one of the communication channel types 82 based on changes in the quality of service of the selected channel, even if a communication channel is in use.
The example data communication arrangement is also adaptive. For example, the data communication arrangement 46 may detect that certain ones of the communication channel types 82 are low service quality when the aircraft 12 is in certain positions relative to the ground-based system 62. The data communication arrangement 46 defaults to select another channel based on this information.
As can be appreciated, channel availability is dependent in part upon the location of the aircraft 12 relative to the ground-based system 62. That is, one or more of the communication channel types 66 may be unable to communicate the data files 70 due to the location of the aircraft 12 relative to the ground-based system 62. Other factors may influence the availability of channel types 66. In this example, the data files 70 communicate though one of the plurality of communication channel types 82 when the aircraft 12 is docked at a gate. In another example, the ground-based system 62 communicates with the aircraft 12 when the aircraft 12 is in flight, or when the aircraft 12 is docked in a maintenance facility, or when transitioning between locations while on the ground.
The transmitter section 78 includes many types of transmitters. For example, the transmitter section 78 includes a cellular transmitter used to transmit the data files 70 to the ground-based system 62 using a cellular type of communication channel. The transmitter section 78 further includes a WiFi transmitter used to transmit the data files 70 to the ground-based system 62 using a WiFi type of communication channel. Other types of transmitters as previously stated are housed in the transmitter section 78 depending on the channel types 82.
The example channel controller 54 continually monitors the availability of the channel types 82. If a channel type is available, that channel type is able to communicate data files 70 between the aircraft 12 and the ground-based system 62. At certain times, only one of the channel types 82 may be available. At other times, some or all of the channel types 82 may be available. A person having skill in this art and the benefit of this disclosure would understand how to monitor the availability of the channel types 82.
The example channel controller 54 also monitors the quality of service of the channel types 82. As can be appreciated, some of the channel types 82 may have a transmission quality that is different than others of the channel types 82. In another example, a controller (not shown) within the ground-based system 62 monitors the transmission quality of the channel types 82.
Various factors can influence the quality of service of the channel types 82, such as the atmosphere's effect on wireless signals, mobile obstructions, the time of day, and the availability of free channel bandwidth. The channel controller 54 is configured to monitor the transmission quality of the channel types 82 in addition to the availability of the channel type 82.
In one example of how the channel controller 54 monitors quality of service, the channel controller 54 and the ground-based system 62 communicate to determine the effective throughput for each of the channel types 82 that are available. The one of the channel types 82 having the highest effective throughput is considered to have the highest transmission quality or quality of service. That one of the channel types 82 is then used for communication of the data files 70. A channel having a low transmission quality may result in delayed transmissions or errors in transmissions. For example, bit errors during transmission may require multiple transmission attempts and therefore longer transmission times.
If there is no substantial difference between the transmission qualities of the channel types 82 that are available, the channel controller 54 may utilize more than one of the channel types 82 for communication.
If there is no substantial difference between the transmission qualities of the channel types 82 that are available, the channel controller 54 may select a channel for communication based on the costs associated with the transmission.
In one example, the channel controller 54 selects one of the channel types 82 having a higher cost of transmission because the transmission quality of that channel is higher quality than another one of the channel types 82 that is available.
The data controller 58 within the example arrangement 46 is configured to select the data files 70 for transmission. The data controller 58 may select some or all of the data files 70. Various factors influence the data controller 58 to select certain types of data files 70. The data controller 58 may base the selection of data files 70 on the types of data in the data files 70, the costs of transmission, the communication channel types 82 available for communication, the quality of service level of the channel types 66 available for communication, or some combination of these.
In one example, the data files 70 are stored within directories and classified as including critical data, intermediate data, non-critical data, events, or health files. Communicating the critical data is typically more important than communicating the health data, for example. The data controller 58 thus prioritizes transmitting the data files 70 that contain the critical data above the data files 70 that contain the health data. If only some of the channel types 82 are available for communication but costly, the data controller 58 initiates communication of only critical data from the data files 70. The health files, events, and non-critical data are held in the memory portion 74 until channel type 82 is available that is less expensive.
In this example, each of the channel types 82 has a cost-of-transmission threshold. A database 84 stored within the memory portion 74 stores the cost-of-transmission thresholds for each of the channel types. The data files 70 also have associated costs, which are stored in the database 84. After one of the channel types 82 is selected, only the data files 70 having associated costs at or below the cost-of-transmission threshold for the selected one of the channel types 82 are selected for transmission. The cost-of-transmission threshold for the channel types 82 may change depending on the position of the aircraft 12 relative to the ground-based system 62.
In the event that multiple channels are available for communication, the channel controller 54 may communicate data across the highest quality of service channel. In another example, the channel controller communicates data across a lower quality of service channel, but a channel that is less expensive to use than the other available channels within the channel types 66.
Many computing devices can be used to implement various functions described herein. For example, the channel controller 54, the data controller 58, the transmitter section 78, and the memory portion 74 may comprise portions of a dual architecture micro server card.
Further, in terms of hardware architecture, the arrangement 46 can additionally include one or more input and/or output (I/O) device interface(s) that are communicatively coupled via a local interface. The local interface can include, for example but not limited to, one or more buses and/or other wired or wireless connections. The local interface may have additional elements, which are omitted for simplicity, such as additional controllers, buffers (caches), drivers, repeaters, and receivers to enable communications. Further, the local interface may include address, control, and/or data connections to enable appropriate communications among the aforementioned components.
An example processor used within the channel controller 54, the data controller 58, or both, executes software code, particularly software code stored in the memory portion 74. The processor can be a custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the computing device, a semiconductor based microprocessor (in the form of a microchip or chip set) or generally any device for executing software instructions.
The memory portion 74 can include any one or combination of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, VRAM, etc.)) and/or nonvolatile memory elements (e.g., ROM, hard drive, tape, CD-ROM, etc.). Moreover, the memory may incorporate electronic, magnetic, optical, and/or other types of storage media. Note that the memory can also have a distributed architecture, where various components are situated remotely from one another, but can be accessed by the processor.
The software in the memory portion 74 may include one or more additional or separate programs, each of which includes an ordered listing of executable instructions for implementing logical functions. A system component embodied as software may also be construed as a source program, executable program (object code), script, or any other entity comprising a set of instructions to be performed. When constructed as a source program, the program is translated via a compiler, assembler, interpreter, or the like, which may or may not be included within the memory.
The Input/Output devices that may be coupled to system I/O Interface(s) may include input devices, for example but not limited to, a keyboard, mouse, scanner, microphone, camera, proximity device, etc. Further, the Input/Output devices may also include output devices, for example but not limited to, a printer, display, etc. Finally, the Input/Output devices may further include devices that communicate both as inputs and outputs, for instance but not limited to, a modulator/demodulator (modem; for accessing another device, system, or network), a radio frequency (RF) or other transceiver, a telephonic interface, a bridge, a router, etc.
Referring to
Features of the disclosed examples include communicating data between an aircraft and a ground-based system across a selected communication channel. The communication channel is selected based on based on the availability of the communication channel types 82, the quality of the communication channel types 82, the cost of transmission, or some combination of these. Data is selected for transmission based on the selected communication channel types 82.
The preceding description is exemplary rather than limiting in nature. Variations and modifications to the disclosed examples may become apparent to those skilled in the art that do not necessarily depart from the essence of this disclosure. Thus, the scope of legal protection given to this disclosure can only be determined by studying the following claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4989230 | Gillig et al. | Jan 1991 | A |
| 5189734 | Bailey et al. | Feb 1993 | A |
| 5203012 | Patsiokas et al. | Apr 1993 | A |
| 5260988 | Schellinger et al. | Nov 1993 | A |
| 5274837 | Childress et al. | Dec 1993 | A |
| 5287541 | Davis et al. | Feb 1994 | A |
| 5301359 | Van den Heuvel et al. | Apr 1994 | A |
| 5331635 | Ota | Jul 1994 | A |
| 5347272 | Ota | Sep 1994 | A |
| 5408684 | Yunoki et al. | Apr 1995 | A |
| 5428636 | Meier | Jun 1995 | A |
| 5457711 | Kellermann | Oct 1995 | A |
| 5475864 | Hamabe | Dec 1995 | A |
| 5475868 | Duque-Anton et al. | Dec 1995 | A |
| 5491690 | Alfonsi et al. | Feb 1996 | A |
| 5506888 | Hayes et al. | Apr 1996 | A |
| 5513379 | Benveniste et al. | Apr 1996 | A |
| 5519884 | Duque-Anton et al. | May 1996 | A |
| 5526404 | Wiedeman et al. | Jun 1996 | A |
| 5530701 | Stillman et al. | Jun 1996 | A |
| 5544222 | Robinson et al. | Aug 1996 | A |
| 5551066 | Stillman et al. | Aug 1996 | A |
| 5561836 | Sowles et al. | Oct 1996 | A |
| 5566173 | Steinbrecher | Oct 1996 | A |
| 5594718 | Weaver, Jr. et al. | Jan 1997 | A |
| 5594943 | Balachandran | Jan 1997 | A |
| 5649308 | Andrews | Jul 1997 | A |
| 5826188 | Tayloe et al. | Oct 1998 | A |
| 5886988 | Yun et al. | Mar 1999 | A |
| 6047165 | Wright et al. | Apr 2000 | A |
| 6091709 | Harrison et al. | Jul 2000 | A |
| 6104914 | Wright et al. | Aug 2000 | A |
| 6108307 | McConnell et al. | Aug 2000 | A |
| 6108523 | Wright et al. | Aug 2000 | A |
| 6115365 | Newberg et al. | Sep 2000 | A |
| 6148179 | Wright et al. | Nov 2000 | A |
| 6154636 | Wright et al. | Nov 2000 | A |
| 6154637 | Wright et al. | Nov 2000 | A |
| 6160998 | Wright et al. | Dec 2000 | A |
| 6163681 | Wright et al. | Dec 2000 | A |
| 6167238 | Wright | Dec 2000 | A |
| 6167239 | Wright et al. | Dec 2000 | A |
| 6173159 | Wright et al. | Jan 2001 | B1 |
| 6181990 | Grabowsky et al. | Jan 2001 | B1 |
| 6201797 | Leuca et al. | Mar 2001 | B1 |
| 6205471 | Gilchrist et al. | Mar 2001 | B1 |
| 6249913 | Galipeau et al. | Jun 2001 | B1 |
| 6272343 | Pon et al. | Aug 2001 | B1 |
| 6308044 | Wright et al. | Oct 2001 | B1 |
| 6308045 | Wright et al. | Oct 2001 | B1 |
| 6353779 | Simon et al. | Mar 2002 | B1 |
| 6408180 | McKenna et al. | Jun 2002 | B1 |
| 6438468 | Muxlow et al. | Aug 2002 | B1 |
| 6477152 | Hiett | Nov 2002 | B1 |
| 6499027 | Weinberger | Dec 2002 | B1 |
| 6501733 | Falco et al. | Dec 2002 | B1 |
| 6516192 | Spaur et al. | Feb 2003 | B1 |
| 6522867 | Wright et al. | Feb 2003 | B1 |
| 6636789 | Bird et al. | Oct 2003 | B2 |
| 6745010 | Wright et al. | Jun 2004 | B2 |
| 6757712 | Bastian et al. | Jun 2004 | B1 |
| 6760757 | Lundberg et al. | Jul 2004 | B1 |
| 6775545 | Wright et al. | Aug 2004 | B2 |
| 6795408 | Hiett | Sep 2004 | B1 |
| 6816458 | Kroon | Nov 2004 | B1 |
| 6816728 | Igloi et al. | Nov 2004 | B2 |
| 6847801 | de La Chapelle et al. | Jan 2005 | B2 |
| 6882843 | Comer | Apr 2005 | B1 |
| 6894611 | Butz et al. | May 2005 | B2 |
| 6943699 | Ziarno | Sep 2005 | B2 |
| 6990319 | Wright et al. | Jan 2006 | B2 |
| 7035634 | Mead et al. | Apr 2006 | B2 |
| 7065367 | Michaelis et al. | Jun 2006 | B2 |
| 7120389 | de La Chapelle et al. | Oct 2006 | B2 |
| 7370283 | Othmer | May 2008 | B2 |
| RE40479 | Wright et al. | Sep 2008 | E |
| 7426387 | Wright et al. | Sep 2008 | B2 |
| 7426388 | Wright et al. | Sep 2008 | B1 |
| 7428412 | Wright et al. | Sep 2008 | B2 |
| 7444146 | Wright et al. | Oct 2008 | B1 |
| 7519014 | Allen et al. | Apr 2009 | B2 |
| 7613154 | Caspi et al. | Nov 2009 | B2 |
| 7616960 | Anke et al. | Nov 2009 | B2 |
| 20020018008 | Wright et al. | Feb 2002 | A1 |
| 20020137521 | Kim et al. | Sep 2002 | A1 |
| 20020155823 | Preston et al. | Oct 2002 | A1 |
| 20030043811 | Leuca et al. | Mar 2003 | A1 |
| 20030210680 | Rao et al. | Nov 2003 | A1 |
| 20040092278 | Diepstraten et al. | May 2004 | A1 |
| 20040095901 | Rajkotia | May 2004 | A1 |
| 20040218605 | Gustafsson et al. | Nov 2004 | A1 |
| 20040264475 | Kowalski | Dec 2004 | A1 |
| 20050009525 | Evslin | Jan 2005 | A1 |
| 20050047425 | Liu et al. | Mar 2005 | A1 |
| 20050159160 | Chambers et al. | Jul 2005 | A1 |
| 20050181791 | Mielke et al. | Aug 2005 | A1 |
| 20050275563 | Ziarno | Dec 2005 | A1 |
| 20060057974 | Ziarno et al. | Mar 2006 | A1 |
| 20060094417 | Allen et al. | May 2006 | A1 |
| 20060276127 | Cruz et al. | Dec 2006 | A1 |
| 20070026868 | Schulz et al. | Feb 2007 | A1 |
| 20070130599 | Monroe | Jun 2007 | A1 |
| 20070156296 | Wright et al. | Jul 2007 | A1 |
| 20070232230 | Anke et al. | Oct 2007 | A1 |
| 20080205283 | McGuffin et al. | Aug 2008 | A1 |
| 20090041041 | True et al. | Feb 2009 | A1 |
| 20090201886 | Lee et al. | Aug 2009 | A1 |
| 20090282469 | Lynch et al. | Nov 2009 | A1 |
| 20100232295 | True et al. | Sep 2010 | A1 |
| 20100304739 | Rooks et al. | Dec 2010 | A1 |
| Number | Date | Country |
|---|---|---|
| 0890907 | Jan 1999 | EP |
| 1096699 | May 2001 | EP |
| 2190144 | May 2010 | EP |
| 2787658 | Jun 2000 | FR |
| 2863133 | Jun 2005 | FR |
| 2347586 | Sep 2000 | GB |
| 2012551 | Jan 1990 | JP |
| 0014987 | Mar 2000 | WO |
| 2005040963 | May 2005 | WO |
| 2006052171 | May 2006 | WO |
| 2007013878 | Feb 2007 | WO |
| 2009039148 | Mar 2009 | WO |
| Entry |
|---|
| Extended European Search Reported dated Oct. 10, 2011. EP App. No. 11171956.3-1249. |
| Number | Date | Country | |
|---|---|---|---|
| 20120015606 A1 | Jan 2012 | US |
