Conversion of aircraft data over wireless networks for flight deck and cabin airline applications
US-10382557-B2 · Aug 13, 2019 · US
US11102302B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11102302-B2 |
| Application number | US-201916458415-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 1, 2019 |
| Priority date | Jun 30, 2016 |
| Publication date | Aug 24, 2021 |
| Grant date | Aug 24, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
An in-flight entertainment and communications (IFEC) system is configured to interconnect an avionics data bus to a local area network. An avionics interface is connectable to the avionics data bus, and receptive to avionics data transmitted on the avionics data bus by one or more avionics nodes over a predetermined protocol. A local network interface establishes the local area network, and portable electronic devices may be connectable to the local network interface over the local area network to establish a data communications link thereon. A data processor is connected to the avionics interface and the local network interface, and relays the avionics data from the avionics interface to the local network interface for transmission to the one or more portable electronics devices. This transmission is according to the predetermined protocol over the data communications link established on the local area network.
Opening claim text (preview).
What is claimed is: 1. A non-transitory computer readable medium connected to an in-flight entertainment and communications (IFEC) system and including instructions executable by the IFEC system for performing a method of regulating data traffic between computing devices connected to an onboard local area network and an aircraft avionics system, the method comprising: receiving avionics data generated by the aircraft avionics system through a first interface to an avionics bus, the avionics data including one or more data elements, wherein each data element comprises at least two fields that include a first field with data and a second field with a security classification assigned to the corresponding data; receiving sensor signals generated by a plurality of sensors through a direct sensor interface that is configured to quantize an analog signal from at least one of the plurality of sensors, the plurality of sensors including a weight on wheels sensor, a door sensor, an engine start lever sensor, and a brake sensor; selectively relaying the avionics data and the sensor signals to a network interface with a network access controller based upon the security classification to which the respective one of the data elements is assigned; and transmitting, from the network interface, the avionics data and the sensor signals selectively relayed from the network access controller to one or more of the computing devices, the network interface establishing the onboard local area network separate from the avionics bus, with the one or more of the computing devices being connected to the onboard local area network. 2. The non-transitory computer readable medium of claim 1 , wherein the method further includes receiving a message transmitted from the one or more of the computing devices. 3. The non-transitory computer readable medium of claim 2 , wherein the method further includes selectively relaying the received message to a remote communications module with the network access controller. 4. The non-transitory computer readable medium of claim 2 , wherein the method further includes selectively relaying the received message to the aircraft avionics system with the network access controller over the avionics bus. 5. The non-transitory computer readable medium of claim 2 , wherein the received avionics data is structured according to a first communication protocol, the avionics data being encapsulated within a second communication protocol different from the first communication protocol for transmitting to the one or more of the computing devices. 6. The non-transitory computer readable medium of claim 5 , wherein the one or more computing devices includes a first interface of the first communication protocol and a second interface of the second communication protocol. 7. The non-transitory computer readable medium of claim 1 , wherein one of the one or more computing devices is an electronic flight bag (EFB). 8. A non-transitory computer readable medium connected to an in-flight entertainment and communications (IFEC) system and including instructions executable by the IFEC system for performing a method of regulating data traffic between computing devices connected to an onboard local area network, the method comprising: receiving avionics sensor signals generated by a plurality of sensors through a direct sensor interface, wherein the plurality of sensors includes a weight on wheels sensor, a door sensor, an engine start lever sensor, and a brake sensor, and wherein receiving the avionics sensor signals comprises quantizing at least one avionics sensor signal; converting the received avionics sensor signals to discrete avionics sensor data, the discrete avionics sensor data including one or more data elements, wherein each data element comprises at least two fields that include a first field with data and a second field with a security classification assigned to the corresponding data; selectively relaying the discrete avionics sensor data to a network interface with a network access controller based upon the security classification to which the respective one of the data elements is assigned; transmitting, from the network interface, the discrete avionics sensor data selectively relayed from the network access controller to one or more of the computing devices, the network interface establishing the onboard local area network separate from the avionics bus, with the one or more of the computing devices being connected to the onboard local area network. 9. The non-transitory computer readable medium of claim 8 , wherein the method further includes receiving a message transmitted from the one or more of the computing devices. 10. The non-transitory computer readable medium of claim 9 , wherein the method further includes selectively relaying the received message to a remote communications module with the network access controller. 11. The non-transitory computer readable medium of claim 8 , wherein the converted avionics sensor data is structured according to a first communication protocol, the avionics data being encapsulated within a second communication protocol different from the first communication protocol for transmitting to the one or more of the computing devices. 12. The non-transitory computer readable medium of claim 11 , wherein the one or more computing devices includes a first interface of the first communication protocol and a second interface of the second communication protocol. 13. The non-transitory computer readable medium of claim 8 , wherein one of the one or more computing devices is an electronic flight bag (EFB). 14. A method for regulating data traffic between computing devices connected to an onboard local area network and one or more aircraft avionics systems, the method comprising: receiving avionics data from the one or more aircraft avionics systems, the avionics data including one or more data elements, wherein each data element comprises at least two fields that include a first field with data and a second field with a security classification assigned to the corresponding data; receiving sensor signals generated by a plurality of sensors through a direct sensor interface that is configured to quantize an analog signal from at least one of the plurality of sensors, the plurality of sensors including a weight on wheels sensor, a door sensor, an engine start lever sensor, and a brake sensor; selectively relaying the avionics data and the sensor signals to a network interface with a network access controller based upon the security classification to which the respective one of the data elements is assigned; and transmitting, from the network interface, the avionics data and the sensor signals selectively relayed from the network access controller to one or more of the computing devices, the network interface establishing the onboard local area network separate from the avionics bus, with the one or more of the computing devices being connected to the onboard local area network. 15. The method of claim 14 , wherein the avionics data is received from the one or more aircraft avionics systems through a first interface to an avionics bus. 16. The method of claim 14 , further comprising: generating a sensor data object representative of the received avionics sensor signals; and assigning the security classification to the sensor data object based upon a predefined association between specific ones of the aircraft avionics system and a corresponding security classification therefor. 17. The method of claim 14 , wherein the received avionics data is structured ac
Services for machine-to-machine communication [M2M] or machine type communication [MTC] · CPC title
specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks · CPC title
with centralised control, e.g. polling · CPC title
Filtering policies (mail message filtering H04L51/212) · CPC title
Traffic logging, e.g. anomaly detection · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.