AIRCRAFT COMMUNICATIONS NETWORK WITH DISTRIBUTED RESPONSIBILITY FOR COMPATIBILITY CONFIRMATION

• US 20160105326A1
• Filed: 10/13/2015
• Published: 04/14/2016
• Est. Priority Date: 10/13/2014
• Status: Abandoned Application

• Current Assignee: Gulfstream Aerospace Corporation (General Dynamics Corporation)
• Original Assignee: Gulfstream Aerospace Corporation (General Dynamics Corporation)
• Inventors: Smart, Derek
• Application Number:
  US14/881,600
• Publication Number:
  US 20160105326A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 41/0873 Checking configuration conflicts between network elements
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies

Abstract

Aircraft communications networks, network devices, and methods of determining compatibility on an aircraft communications network are disclosed herein. The aircraft communications network includes, but is not limited to, a communications bus, a first network device, and a second network device. The first network device is communicatively coupled with the communications bus and is configured to publish on the communications bus a configuration manifest that describes a compatible configuration of hardware and software for the aircraft communications network. The second network device is communicatively coupled with the communications bus and is configured to receive the configuration manifest from the first network device over the communications bus, compare the configuration manifest to a second hardware and software profile that describes the second network device, and disable outputs of the second network device in response to detecting that the configuration manifest differs from the second hardware and software profile.

Claims

1. An aircraft communications network comprising:

a communications bus;

a first network device communicatively coupled with the communications bus, the first network device configured to publish on the communications bus a configuration manifest that describes a compatible configuration of hardware and software for the aircraft communications network; and

a second network device communicatively coupled with the communications bus, the second network device configured to;

receive the configuration manifest from the first network device over the communications bus;

compare the configuration manifest to a second hardware and software profile that describes the second network device; and

disable outputs of the second network device in response to detecting a difference between the configuration manifest and the second hardware and software profile.

2. The aircraft communications network of claim 1, wherein the second network device is further configured to determine that the second network device is incompatible with the aircraft communications network in response to detecting the difference between the configuration manifest and the second hardware and software profile.

3. The aircraft communications network of claim 2, wherein the second network device is further configured to generate a configuration failure alert on the communications bus in response to determining that the second network device is incompatible with the aircraft communications network.

4. The aircraft communications network of claim 1, further comprising a sensor communicatively coupled with the second network device, and wherein the second hardware and software profile describes both the second network device and the sensor.

5. The aircraft communications network of claim 1, wherein the first network device is further configured to store the configuration manifest.

6. The aircraft communications network of claim 5, wherein the second network device is further configured to store the configuration manifest.

7. The aircraft communications network of claim 6, wherein the first network device is further configured to:

receive the configuration manifest from the second network device across the communications bus;

compare the configuration manifest to a first hardware and software profile that describes the first network device; and

disable outputs of the first network device in response to the configuration manifest differing from the first hardware and software profile.

8. The aircraft communications network of claim 7, wherein the first network device is further configured to compare the configuration manifest stored on the first network device with the first hardware and software profile.

9. The aircraft communications network of claim 8, wherein the second network device is further configured to compare the configuration manifest stored on the second network device with the second hardware and software profile.

10. The aircraft communications network of claim 6, wherein the configuration manifest is stored solely on at least one of the first network device and the second network device.

11. A network device for an aircraft communications network, the network device comprising:

a computer hardware component including an input/output (I/O) portion configured for connecting to an aircraft communications bus; and

a software component loaded into the computer hardware component,

wherein the computer hardware component and the software component cooperate to configure the network device to;

receive a configuration manifest through the I/O portion;

compare the configuration manifest to a hardware and software profile that describes the computer hardware component and the software component; and

disable outputs from the network device through the I/O portion in response to detecting that the configuration manifest differs from the hardware and software profile.

12. The network device of claim 11, wherein the network device is further configured to determine that the network device is incompatible with the aircraft communications network in response to detecting that the configuration manifest differs from the hardware and software profile.

13. The network device of claim 12, wherein the network device is further configured to generate a configuration failure alert at the I/O portion in response to determining that the network device is incompatible with the aircraft communications network.

14. The network device of claim 11, wherein the computer hardware component further includes a sensor input portion, and wherein hardware and software profile describes a sensor coupled with the sensor input portion, the computer hardware component, and the software component.

15. The network device of claim 11, wherein the network device is further configured to store the configuration manifest and to publish the configuration manifest at the I/O portion.

16. A method of determining compatibility of a network device with an aircraft communications network, the method comprising:

publishing on a communications network, by a first network device, a configuration manifest that describes a compatible configuration of hardware and software for the aircraft communications network;

receiving, at a second network device, the configuration manifest; and

comparing, at the second network device, the configuration manifest to a second hardware and software profile that describes the second network device.

17. The method of claim 16, further comprising disabling outputs of the second network device in response to determining that the configuration manifest differs from the second hardware and software profile.

18. The method of claim 16, further comprising generating a configuration failure alert on the aircraft communications network in response to determining that the configuration manifest differs from the second hardware and software profile.

19. The method of claim 16, further comprising retrieving the configuration manifest from an electronic storage device on the first network device.

20. The method of claim 16, further comprising:

retrieving the configuration manifest from an electronic storage device on the second network device;

publishing on the communications network, by the second network device, the configuration manifest;

receiving, at the first network device, the configuration manifest; and

comparing, at the first network device, the configuration manifest with a first hardware and software profile that describes the first network device.