Aeronautical message monitor

Patent metadata

Field	Value
Publication number	US-9825975-B2
Application number	US-201514829093-A
Country	US
Kind code	B2
Filing date	Aug 18, 2015
Priority date	Aug 18, 2015
Publication date	Nov 21, 2017
Grant date	Nov 21, 2017

Abstract

A system includes a transmitting line replaceable unit (TLRU) configured to receive messages including instructions for avionics receiving line replaceable units (RLRUs). The system further includes a memory configured to store validation data including a set of expected messages. A monitor is further included and is configured to monitor messages received at the TLRU and further configured to determine whether received messages are valid based on at least a portion of the set of expected messages stored in the memory. A plurality of RLRUs are further included and configured to receive message from the TLRU and to execute the instructions included in the received messages.

First claim

The invention claimed is:

1. A system aboard an aircraft, comprising:
a first line replaceable unit (LRU) configured to receive Aeronautical Radio Inc. (ARINC) messages including instructions for other line replaceable units (LRUs);
a memory configured to store validation data including a set of expected ARINC messages; and
a monitor configured to monitor ARINC messages received at the first LRU and further configured to determine whether received ARINC messages are valid based on a comparison with at least a portion of the set of expected ARINC messages stored in the memory.

2. The system of claim 1 , wherein the monitor is further configured to:
compare a first portion of a received message at the first LRU with a corresponding portion of an expected message in the set of expected messages; and
determine whether the received message is valid based on the comparing of the first portion of the received message with the corresponding portion of the expected message.

3. The system of claim 2 , wherein comparing the
message received at the first LRU includes:
perform a bit-by-bit comparison of the first portion of the received message with the corresponding portion of the expected message;
when the bit-by-bit comparison results in at least one non-match of compared bits, then for each non-match, update a counter;
compare a counter value with a plurality of predetermined threshold values; and
when the counter value meets or exceeds at least one of the predetermined threshold values, determine that the received message is not a valid message.

4. The system of claim 3 , further comprising:
an alerter;
wherein the monitor is further configured to:
instruct the alerter to issue an alert when it is determined that the counter value exceeds at least one of the plurality of predetermined threshold values.

5. The system of claim 4 , wherein the alerter illuminates a border of a flight deck instrument on a display panel when the counter value exceeds a first threshold of the plurality of threshold values.

6. The system of claim 5 , wherein the border of the flight deck instrument is displayed in one of a plurality of colors based on the one of the plurality of threshold values that was met or exceeded thereby indicating a threat level.

7. The system of claim 4 , wherein the alerter illuminates a light on a display when the counter value exceeds a second threshold of the plurality of threshold values.

8. The system of claim 1 , wherein the memory is further configured to store flight phase information for each of a plurality of flight phases in association with a respective label code in the memory; and
wherein the monitor is further configured to:
determine a current flight phase;
determine a label code in a received ARINC message;
compare the label code of the received ARINC message with a label code corresponding to the current flight phase; and
determine that the received ARINC message is valid when the label code of the received ARINC message matches the label code corresponding to the current flight phase.

9. The system of claim 1 , wherein the monitor is further configured to:
determine whether a core file associated with a received message has been altered based on at least one of a date indicating a last time the core file was written to, a date indicating when the core file was last modified, and an update schedule of the core file.

10. The system of claim 1 , further comprising:
a plurality of other line replaceable units (LRUs) configured to receive messages from the first LRU that were received at the first LRU and to execute the instructions included in the received messages.

11. A method implemented aboard an aircraft, comprising:
accessing a received Aeronautical Radio Inc. (ARINC) message that was received at a first line replaceable unit (LRU) aboard the aircraft;
comparing a first portion of the received ARINC message with a corresponding portion of an expected ARINC message; and
determining whether the received ARINC message is valid based on the comparing the first portion of the received ARINC message with the corresponding portion of the expected ARINC message.

12. The method of claim 11 , wherein comparing the first portion of the received ARINC message at the LRU includes:
performing a bit-by-bit comparison of the first portion of the received message with the corresponding portion of the expected message;
when a bit-by-bit comparison results in at least one non-match of respective bits, for each non-match, updating a counter;
comparing a counter value of the counter with a plurality of predetermined threshold values; and
when the counter value meets or exceeds at least one of the predetermined threshold values, determining that the received message is not a valid message.

13. The method of claim 12 , the method further comprising:
instructing an alerter to issue an alert when it is determined that the counter value exceeds at least one of the plurality of predetermined threshold values.

14. The method of claim 13 , wherein the alerter illuminates a border of a flight deck instrument on a display panel when the counter value exceeds a first threshold of the plurality of threshold values.

15. The method of claim 14 , wherein the border of the flight deck instrument is displayed one of a plurality of colors based on the one of the plurality of threshold values that was met or exceeded indicating a threat level.

16. The method of claim 13 , wherein the alerter illuminates a light on a display when the counter value exceeds a second threshold of the plurality of threshold value.

17. The method of claim 11 , further comprising:
storing flight phase information for each of a plurality of flight phases in association with a respective label code in a memory;
determining a current flight phase;
determining a label code in a received ARINC message;
comparing the label code of the received ARINC message with a label code corresponding to the current flight phase; and
determining whether the received ARINC message is valid when the label code of the received message ARINC matches the label code corresponding to the current flight phase.

18. A non-transitory computer-readable medium, storing a set of instructions, executable by a processor, to perform a method aboard an aircraft, comprising:
accessing an Aeronautical Radio Inc. (ARINC) message that was received at a first line replaceable unit (LRU);
comparing a first portion of the received ARINC message with a corresponding portion of an expected ARINC message; and
determining whether the received ARINC message is valid based on the comparing of the first portion of the received ARINC message with the corresponding portion of the expected ARINC message.

Assignees

• Boeing Co

Inventors

• Mitchell Timothy M
• Shelton Jason W
• Nguyen Daniel

Classifications

• H04L43/16

  Threshold monitoring · CPC title

• H04L51/046

  Interoperability with other network applications or services · CPC title

• H04L63/1416 Primary

  Event detection, e.g. attack signature detection · CPC title

• H04B7/18506

  Communications with or from aircraft, i.e. aeronautical mobile service · CPC title

• H04L67/12

  specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks · CPC title