Aircraft network monitoring and authentication

Abstract

A system and method for compiling and monitoring a list of aircraft components to determine if a threshold is met. Monitoring of a network of aircraft components can be provided using the list and thresholds to monitor the health and safety of the aircraft network and its components. The system can then indicate or alert when a threshold is met or exceeded. Such an alert can be displayed on a display, for example, to a pilot or a remote monitoring station.

Description

Technical Field

[0001] The present disclosure relates to a method and apparatus for monitoring and certifying the health and safety of networked aircraft avionics equipment and components. Background Art

[0002] Aircraft are typically equipped with systems and electronic systems of avionics, as well as networks that interconnect many or all of the systems and electronic systems of avionics. However, traditional cybersecurity measures are not easily applicable to aircraft or avionics environments. In addition, there is a trend to bundle sensor and other measurement data into large data buses, which increases the likelihood of equipment or software failures due to common mode failures that affect a wide range of aircraft functions beyond the initial failure. Therefore, creative means are needed to protect and monitor aircraft networks, or to utilize cybersecurity means tailored for aviation implementations. Summary of the invention

[0003] Aspects and advantages of the invention will be set forth in part in the following description, or may be obvious from the description, or may be learned through practice of the invention.

[0004] In one aspect, the present disclosure relates to a method for monitoring the health and safety of networked avionics on an aircraft, the method comprising: generating a list including executable items and libraries representing networked avionics; monitoring the list; and issuing an alert when one or more networked avionics provided on the list meets a predetermined threshold.

[0005] In another aspect, the present disclosure is directed to a network system for an aircraft, comprising: a set of aircraft parts; a network that communicatively and electronically interconnects the set of aircraft parts; a configuration management unit that is in electronic communication with the network and is configured to detect or measure the set of aircraft parts on the network, wherein the configuration management unit is configured to generate a list representing a configuration of the network and the set of aircraft parts; wherein the list includes executable items or libraries associated with the set of aircraft parts and the network; and wherein the configuration management unit is configured to monitor the list to determine whether the configuration is no longer approved by the configuration management unit.

[0006] In yet another aspect, the present disclosure relates to a method of monitoring network security in an aircraft, the method comprising: generating a list representing an aircraft network and one or more aircraft components on the aircraft network; periodically monitoring the list; and indicating on a display which functions of the aircraft may be affected or affected when one or more aircraft components monitored on the list reach a predetermined threshold.

[0007] These and other features, aspects and advantages of the present invention will become better understood with reference to the following description and appended claims.The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the present invention and, together with the description, serve to explain the principles of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] In the figure:

[0009] Figure 1 is a schematic diagram of an exemplary aircraft and its network system in accordance with various aspects described herein.

[0010] Figure 2 is a diagram showing an exemplary display representing a non-exhaustive list of an aircraft network and its components. DETAILED DESCRIPTION

[0011] Aspects of the present invention relate to a system and method for monitoring the health and safety of networked aircraft avionics or other components. Aspects of the present disclosure also relate to monitoring and certification of the health and safety of networked aircraft avionics and components. Although the disclosure provided herein is described with reference to an aircraft including an avionics chassis and associated networked aircraft, it should be understood that alternative embodiments on alternative aircraft are conceivable, including those that include or do not include an avionics chassis or box, or those that include more, less or different aircraft or network components as described herein. Although the description generally relates to an avionics chassis, it should be understood that the monitoring or safety elements do not have to include an avionics chassis or be routed through an avionics chassis. Similarly, the systems and methods described herein will also have applicability in other mobile or carrier environments where network monitoring and health certification are desired, such as non-aircraft, terrestrial or other environments, and any non-traditional networked systems where traditional safety or monitoring devices are not easy to work with or suffer from unique challenges similar to aircraft.

[0012] Although "a group" of various elements will be described, it will be understood that "a group" may include any number of corresponding elements, including only one element. The use of the term "proximal" or "proximal ground" refers to moving in the direction toward another component, or a component is relatively closer to another component compared to another reference point. In addition, as used herein, although the sensor may be described as "sensing" or "measuring" the corresponding value, sensing or measuring may include determining an indication of a corresponding value or a value related thereto, rather than directly sensing or measuring the value itself. The sensed or measured value may be further provided to an additional component. For example, the value may be provided to a controller module or processor, and the controller module or processor may perform processing on the value to determine a representative value or an electrical characteristic representing the value. In addition, although terms such as "voltage", "current" and "electricity" may be used here, for those skilled in the art, these terms may be interrelated when describing aspects of circuit or circuit operation.

[0013] The terms "coupled," "fixed," "attached," and the like refer to both direct coupling, fixing, or attachment as well as indirect coupling, fixing, or attachment through one or more intermediate components or features, unless otherwise specified herein.

[0014] The singular forms "a," "an," and "the" include plural references unless the context clearly dictates otherwise.

[0015] Approximate language, as used in this specification and claims, is used to modify any quantitative representation that may be permissibly varied without resulting in a change in the basic function to which it is related. Thus, values ​​modified by one or more terms, such as "approximately," "approximately," and "substantially," are not limited to the precise values ​​specified. In at least some instances, approximate language may correspond to the precision of an instrument used to measure a value, or the precision of a method or machine used to construct or manufacture a component and / or system. For example, approximate language may mean within a margin of 10%.

[0016] All directional references (e.g., radial, axial, upper, lower, upward, downward, left, right, side, front, rear, top, bottom, above, below, vertical, horizontal, clockwise, counterclockwise) are only used for identification purposes to help the reader understand the present disclosure, and do not generate restrictions, particularly restrictions on position, orientation or its use. In addition, unless otherwise specified, connection references (e.g., attachment, connection, connection and engagement) will be broadly understood and may include relative motion between intermediate members and elements between element sets. Therefore, connection references do not necessarily infer that two elements are directly connected and connected to each other in a fixed relationship. In a non-limiting example, connection or disconnection may be selectively configured, connected or connectable to provide, enable, disable or similarly electrical connection between various elements. In a non-limiting example, the power distribution bus connection or disconnection may be enabled or operated by a switch, bus connection logic or any other connector configured to enable or disable the energization of the electrical load downstream or between the buses.

[0017] As used herein, a "system," "controller," "avionics," "component," "configuration management unit," or "controller module" may include at least one processor and memory, rather than requiring at least one processor and memory for each component. A controller module, configuration management unit, or other similar component may include any known processor, microcontroller, or logic device, including, but not limited to, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a full authority digital engine control (FADEC), a proportional controller (P), a proportional integral controller (PI), a proportional differential controller (PD), a proportional integral differential controller (PID controller), a hardware accelerated logic controller (e.g., for encoding, decoding, transcoding, etc.), or the like, or a combination thereof. Non-limiting examples of controller modules may be configured or adapted to run, operate, or otherwise execute program code to achieve an operation or functional result, including performing various methods, functions, processing tasks, calculations, comparisons, sensed or measured values, etc., to achieve or realize the technical operations or operations described herein. The operation or functional result may be based on one or more inputs, stored data values, sensed or measured values, true or false indications, etc. Although "program code" is described, non-limiting examples of operable or executable instruction sets may include routines, programs, objects, components, data structures, algorithms, etc., which have the technical effect of performing specific tasks or realizing specific abstract data types. In another non-limiting example, the controller module may also include a data storage component accessible by the processor, including a memory, whether it is a transient memory, a volatile memory, or a non-transient memory or a non-volatile memory. Non-limiting examples of memory may include random access memory (RAM), read-only memory (ROM), flash memory, or one or more different types of portable electronic memory, such as an optical disc, a DVD, a CD-ROM, etc., or any appropriate combination of these types of memory. The processor may be configured to run any appropriate program or executable instruction, which is designed to perform various methods, functions, processing tasks, calculations, etc., to enable or implement the technical operations or operations described herein. The program may include a computer program product, which may include a machine-readable medium for carrying or having a machine-executable instruction or data structure stored thereon. This machine-readable medium may be any available medium, which may be accessed by a general or special-purpose computer or other machine with a processor. Generally speaking, such computer programs may include routines, programs, objects, components, data structures, algorithms, etc. that have the technical effect of performing specific tasks or implementing specific abstract data types.

[0018] Additionally, as used herein, an element that is "electrically connected," "electrically coupled," "communicatively coupled," or "in signal communication" may include electrical transmissions or signals that are sent, received, or communicated with such connected or coupled elements. Furthermore, such electrical connections or couplers may include wired or wireless connections or combinations thereof.

[0019] The present invention may be implemented in any network or electrical control, operation or communication system, any aircraft avionics system or network or other aircraft electrical system. Non-limiting examples of circuit environments that may include aspects of the present disclosure may include an aircraft power system architecture that enables power to be generated or supplied from a power source (e.g., a generator or power storage unit or device) and delivered to a set of electrical loads. Additional non-limiting elements may be included in such an architecture, such as sensors, transmitters, or transceivers in non-limiting examples.

[0020] Figure 1 An aircraft 10 is schematically shown including an aircraft network 12 having an avionics chassis 14 that may contain one or more of a CPU, a controller, a management unit, or a configuration management unit for controlling, communicating, and operating various aspects associated with the flight of the aircraft 10 or components associated with the aircraft 10. The aircraft 10 may utilize or incorporate a number of electrical components for operating various aspects of the aircraft 10 for flight or non-flight operations (e.g., maintenance). Figure 1 The illustrated network 12, as generally used herein, includes a communication system contained within the aircraft 10. However, it should be understood that the network 12 may include additional remote features, such as a remote memory unit, or even a control tower or airport that communicates with the network 12 remote from the aircraft 10.

[0021] Non-limiting examples of aircraft electrical components may include an avionics chassis 14, a turbine engine 16 including a turbine engine component 20 (disposed on each wing 18), a flap 22, a leading edge slat 24, a transceiver 26, or a landing gear 28. A non-limiting list of additional components may include sensors or other aircraft electrical components, such as buttons, displays, user interfaces, control panels, communication devices (such as headphones or speakers) and associated controllers, processors, or memory units. Non-limiting examples of sensors may include temperature sensors, pressure sensors, vibration sensors, sound or noise sensors, air temperature sensors, or any other desired sensors disposed on the aircraft. In addition, a control panel disposed in the cockpit of the aircraft 10 includes a plurality of electrical components associated with the operation of the aircraft 10. Components of the control panel may be included as part of the aircraft network 12. In addition, other electrical components may be included as part of a network, such as electrical components in the cabin of the aircraft, such as lighting, air conditioning, or passenger entertainment and connectivity. Other components may include devices, such as network switches or interface devices. For example, the interface device may be a remote interface unit (RIU). Additional components may include an Internet router or transmitter or other connection element. Other contemplated components include, but are not limited to, humidity sensors, noise or decibel sensors, gas sensors, pollution sensors, pressure sensors, air speed sensors, angle of attack sensors, weather radar, surveillance radar, altimeters, turbulence radar, lidar, and communications transmitters such as radios or satellites.

[0022] In addition, one or more elements may be provided in the turbine engine or a component thereof 20. More specifically, the turbine engine 16 itself may include a number of electrical components, such as air temperature sensors or air speed sensors, or other components related to the operation of the engine, which may communicate with or be controlled by a pilot or person remotely operating the aircraft 10, for example, via a transceiver 26.

[0023] The avionics chassis 14 or any component along the network 12 may be a specific configuration management unit (CMU) 30 dedicated to monitoring operation or security of the network 12, or alternatively, the CMU 30 may be configured as a network switch or system thereof, or an interface unit or even a separate element thereof, with functionality specifically dedicated to monitoring and authentication of the network 12. In non-limiting examples, monitoring may include monitoring component throughput, monitoring throughput capacity, monitoring memory usage, monitoring memory capacity, monitoring temperature, monitoring pressure, monitoring latency, monitoring energy usage, etc.

[0024] Reference now Figure 2 , regardless of the aircraft 10( Figure 1), one or more components (preferably many) may be compiled into a list 40, which may be provided on a display 42, depending on the number, type, or organization of components on the aircraft 10. Such a list 40 may be, for example, a virtual list, and may be stored in a controller, memory, or avionics chassis 14, and displayed on the display 42 as an executable, software, or program 44. In addition, the list 40 may be loaded on demand, or reloaded or populated for each flight, or during flight, such as on demand or based on a schedule. The list 40 may include loaded executables and / or libraries associated with multiple components, or historical data related thereto. For example, the transceiver 26 may include a set of communication executables, such as a send executable or a receive / parse executable that may be included in the list 40. In general, the list 40 may include executable or software-type functions and operations thereof associated with multiple components on the aircraft 10, such as active / inactive status, health status, or other related operations specific to the component 20.

[0025] Similarly, the list 40 may include libraries or configuration files, such as parameter data items, which contain information related to parameters, measurements, or other information related to the operation of the items on the list 40, which may be related to operating routines, external functions, or component functions, or variables that can be parsed and ultimately compiled and viewed. Such a library may include information related to a particular aircraft 10, network 12, engine component 20, its operation, and historical data related to the elements of the library.

[0026] Similarly, other related static memory items can be incorporated into the list of executable items. Non-limiting examples of static memory items can include items of executable code (partial or complete) and other constants or values. It can also include a list of all known variables that are considered static or should be considered static at a given point or time (e.g., after program initialization), or at a specific flight time (e.g., takeoff or landing). In addition, it is envisioned that changes in code can be identified when variables are expected to remain static but eventually change. Such changes can be used to identify problems. In addition, it is envisioned that static memory can include function pointers.

[0027] The list 40 may be a file stored on a memory that can be accessed on demand by portions of the network 12. Alternatively, the list 40 may be populated on demand. For example, each time the aircraft 10 is operated or inspected, the network 12 may be instructed to populate the list 40. For example, each time the aircraft 10 is started, the list 40 may be automatically populated based on specific parts available on the network 12. In addition, any stored or saved information from a previous population of the list may be saved in a memory (on the aircraft or remote). Such a previous list or information may be used or compared with the current list 40 to determine if there are any differences or thresholds that may indicate a health or safety issue with one or more components or the network 12 itself. For example, if the previous list build included 30 items and the current list build includes 29 items, the CMU 30 on the network 12 may compare the list 40 with the stored information to determine where the difference is located and how to possibly check or remedy the problem. More specifically, the absence of an item on the list may indicate that the health of that particular item not in the list 40 requires attention. Additionally, this difference or threshold may be indicated on the display 42 in the form of an alert 46, as will be described in greater detail below.

[0028] During the generation of the list 40, during the operation of the aircraft 10 or as needed, the components on the network 12 can be internally secured, such as using a cryptographic signature or token that can be shared between the network 12. Such a signature or token can be used to securely verify each engine component or even its physical presence on the aircraft 10 or network 12. In addition, the use of a token, or in conjunction with other techniques such as signatures, the system can be used to prevent malicious programs, executable items or other items from counterfeiting or mimicking the good health of the system. The token can be something provided by the CMU 30.

[0029] After or during the generation of the list 40, in a non-limiting example, the network configuration may be approved, disapproved, or no longer approved. Approval will result from the expected items provided on the list 40. The disapproved list 40 may be a list that simply requires approval before proceeding, or may be a list 40 that has some unexpected items, differences, thresholds, or other errors that require attention. The no longer approved list 40 is a list 40 that has been previously approved, but is no longer approved during the monitoring of the network 12. The disapproved list 40 may indicate that a threshold has been met, where the threshold may include a difference from the originally generated list, or a difference in a value associated with a component on the network, such as a change in throughput, operation, or encryption approval. The threshold may be met by any appropriate difference between the current list and the original or previous list.

[0030] Approval or disapproval may be passed along or from the network 12, and it is also contemplated that such approval is provided to the network 12, such as an override or other enforcement measure. For example, a communication may be made to the pilot via the display 42, such as a visual indication or other warning about upcoming or required maintenance, including an alarm 46 as shown. Such visual indications may be on a display in the cockpit, for example, or on a maintenance display. The maintenance display may be in the cockpit, where the pilot may view it, or may be located in a convenient place for a maintenance crew on the aircraft. In another example, the maintenance display may be remote from the aircraft and may be viewed by a maintenance crew or a person remote from the aircraft. Thus, the display 42 may be remote from the aircraft. In addition, the communication may be in the form of an alert to the pilot, operator, air traffic controller, or other operator, where there may or will be safety implications, and the action or response may be required. Such a response or communication may depend on a particular system. Such a response may include, for example, disabling a particular system by pulling a circuit breaker, or may include performing activities such as releasing masks to passengers or changing altitude due to decompression of the cabin. Additional reactions may include diverting the flight, changing the flight plan, or even landing as soon as possible. In another example, the communication may be remote, such as sending a wireless signal message to a maintenance system indicating required maintenance on the network 12 or the aircraft 10. In such an example, the display 42 may be remote from the aircraft 10 and in wireless communication with the network 12.

[0031] It is further contemplated that approval is not required. For example, at the start of operation of the aircraft 10, an internal system that is part of the network 12 may simply populate the list 40 without any other action at this time. On the other hand, it is contemplated that an approved list 40 may be required prior to takeoff or landing of the aircraft or in the event that a manual override is required.

[0032] After the initial generation of the list 40 and any initial actions taken, the CMU 30 may perform monitoring of the network 12 or specific elements or portions thereof. Monitoring may generally include measuring or requesting information related to the network 12 and making determinations based on the measurements or information. Monitoring may indicate the health of a device, or changes in the health of a device or thereof over time.

[0033] More specifically, monitoring can include measuring specific aspects of the network 12, or specific aspects of elements on the network 12. In a non-limiting example, such network elements can include switches or interfaces, and the aspects that can be measured can include throughput or remaining throughput capacity. In a non-limiting example, additional measured aspects can include memory usage, memory capacity, processor usage, processor capacity, jitter, latency, vibration, sound, or temperature. Such measured aspects can be compared to specific thresholds. Meeting or exceeding the threshold can indicate a poor or degraded health of an element of the network 12, or can be used to schedule maintenance. Similarly, it should be understood that meeting or exceeding the threshold can also indicate a breach of network security.

[0034] During monitoring of the network 12 or aspects thereof, values, lists, or other information may be requested or stored continuously, periodically, or on demand, and compared to other values ​​or thresholds to determine if there are any trends, such as unexpected behavior at a level that may not reach a set threshold. Such trends may be established by comparing periodic measurements to each other, or over time, such as differences between a recent measurement and a previous periodic measurement. For example, a component on the network 12 with a temperature threshold of 500°F but an operating temperature of 300°F may require maintenance or inspection if the temperature has a consistent upward trend toward a threshold but has not yet reached the threshold. In doing so, the network 12 may provide anticipation of problems related to the health or safety of the network 12, particularly before the problem becomes a problem or a failure occurs.

[0035] Furthermore, it is contemplated that the CMU 30 may update or change the rule-based analysis of the network 12 based on trend information collected during monitoring or based on historical information stored on the network 12 (e.g., in memory). Furthermore, the CMU 30 may update or change the rule-based analysis based on current information, such as during or out of flight.

[0036] For example, a component on the network 12 may have a temperature threshold of 500°F, but an operating temperature of 300°F. However, during flight, reduced external temperatures and reduced pressures result in a standard operating temperature of the component of 280°F. Therefore, in this case, it is contemplated that the CMU 30 may change the rule for the standard operating temperature of the network 12. For example, such a change may be that during flight, the threshold temperature is reduced to 480°F, because the standard operating temperature also drops by 20 degrees during flight conditions. In another example, the change or correction based on the rule change may be based on a percentage. More specifically, reducing the operating temperature from 300°F to 280°F provides a reduction of approximately 7%. Therefore, the threshold during flight may be reduced to 467°F, also reduced by the same percentage. While this is merely exemplary, it should be understood that utilizing or analyzing historical data and making real-time comparisons or adjustments may provide specific rules for updating the CMU 30 to more accurately monitor the health and safety of the network 12 in real time as conditions may change. In another example, the rule does not need to be changed, but may be included as a new rule. For example, the rule would be something like “During flight, the threshold temperature value is 480°F” and could be used along with the original rule without modifying the original rule.

[0037] The CMU 30 may be preloaded with an aircraft architecture. The aircraft architecture may include information such as how many redundant data buses there are, and what information is being passed through the data buses and from which sources. For example, if a data bus is about to be lost, data sources that are only available on one bus may be routed through one or more other buses if network capacity and capabilities permit. Another example of an architecture may include which aircraft functions are bundled in which devices. For example, in a 'federated system', each box has one aircraft function, while the current trend is to move toward integrated avionics systems, where multiple aircraft functions are within a box. Knowledge of box failures allows prediction and warning of which aircraft functions may be reduced or affected, and then allows the system to have dynamic reconfiguration of aircraft and systems to compensate for these functions. This dynamic reconfiguration may be performed in flight or before flight with or without pilot intervention. The aircraft architecture may include information related to the network 12 and the elements and components thereon. More specifically, information related to the network 12 or its components may include default values, thresholds, the number of components, the type of components, or any other historical information that may be relevant to monitoring and analysis of network components. Additionally, utilizing the aircraft architecture can provide early warnings, for example, to pilots or maintenance personnel that some aircraft components or functions may be or have met a threshold, have been affected by a failure, or if a failure is expected or imminent. An IMA cabinet with multiple processing cards is also envisioned, where each card can be subordinate to a separate aircraft function, and the cards can be used as redundancy to account for system impacts or failures. By dynamically reconfiguring the system as needed, lower criticality functions can be changed or updated to replace higher criticality components or functions. Such a system will require cards that are lower in overall cost, lighter in weight, and that improve power savings or efficiency while maintaining or improving overall system safety and protection.

[0038] Furthermore, it is contemplated that network components may be added to the network 12 preconfigured for use in the network 12 and the CMU 30. For example, the network components may be of a 'plug and play' type, meaning that they will be preloaded with software or other information stored on a memory designed to communicate with the CMU 30 via the network 12, such that the added components may be automatically added to the list 40 of executable items or functions by the CMU 30. Alternatively, it is contemplated that components may be manually added to the CMU 30, or that the CMU 30 may be instructed to perform checks and update the list 40 as necessary to include detection of new or replaced components.

[0039] The list 40 may be continuously checked, monitored, or updated such that the CMU 30 periodically sends out to the components, for example using electrical signals, to check for the presence of components on the list 40, their absence, more than the original, or that one or more of the components have changed, such as a parameter of a component meeting a predetermined threshold, or having some operational difference or inconsistency.

[0040] This continuous monitoring can provide security and safety for effectively monitoring the network 12 or important components and features of the aircraft 10. Traditional enterprise security systems do not work easily in the aircraft environment and require deep rework to fit the aircraft system architecture, which is both time consuming and expensive. The network 12 as discussed herein provides monitoring of the aircraft and its avionics, and is customized to the avionics environment to protect the aircraft network and systems. This customization can be specific to aircraft operations and components, as well as continuous monitoring of said components.

[0041] There is a trend toward high levels of integration in multiple aircraft through the use of integrated modular avionics and interface devices that bundle sensor data information into large data buses. This bundling and use of large data buses increases the likelihood of software failures or common mode failures, which may affect a wide range of aircraft functions. Similarly, the network 12 may also consider or monitor hardware aspects of components, such as hardware failures or component disconnects. However, it should be understood that aircraft components should have the greatest resilience to wear or physical failure of these components and be protected from external factors, such as foreign object damage. Therefore, while monitoring the safety and security of the network, the CMU 30 may also effectively monitor hardware systems or their failures.

[0042] It should be appreciated that the disclosure provided herein provides an improved ability to identify or warn of aircraft system safety and health issues earlier than current methods. Such early warnings or alerts may allow the aircraft or pilot to react accordingly when a problem is discovered. Similarly, reconfiguration may be performed to maximize the use of available resources (e.g., processing power or memory storage) or to allow for reduced redundant installations. Specifically, continuous monitoring of the network 12 using the CMU 30 may provide continuous updates of the monitoring of the network 12 based on the list 40. Such continuous monitoring may update the list 40 in real time, which reduces or eliminates the need for system redundancy.

[0043] The CMU 30 and network 12 provided and discussed herein provide improved system and operational safety and security for the aircraft network 12. Similarly, the build list 40 provides for dynamic reconfiguration of the network 12 and how information is processed and used by the network 12. Additionally, the network 12, CMU 30, and related systems provide cost reduction and savings by reducing redundancy in the network 12 and by reducing transitions through unnecessary system components or routines. Additionally, improved dispatch reliability will also save costs.

[0044] To the extent not yet described, the different features and structures of each aspect can be used in combination with each other as desired. A feature that cannot or is not shown or described in all aspects is not meant to be interpreted as not being possible, but is done for the sake of brevity of description. Therefore, whether or not a new aspect is explicitly described, various features of different aspects can be mixed and matched as needed to form new aspects. Combinations or arrangements of features described herein are covered by the present disclosure.

[0045] Further aspects of the invention are provided by the subject matter of the following clauses:

[0046] 1. A method for monitoring the health and safety of networked avionics on an aircraft, the method comprising: generating a list including executable items and libraries representing networked avionics; monitoring the list; and issuing an alert when one or more networked avionics provided on the list meets a predetermined threshold.

[0047] 2. A method according to any preceding clause, wherein the executable and the library comprise a configuration file and a static memory.

[0048] 3. A method according to any preceding clause, wherein the predetermined threshold comprises one or more items on the list being absent from the list.

[0049] 4. The method of any preceding clause, wherein generating the list further comprises cryptographically verifying that the networked avionics equipment represented on the list are on board the aircraft or on a network in communication with the aircraft.

[0050] 5. A method according to any preceding clause, wherein the list further comprises an associated static memory item stored on at least one of the networked avionics devices.

[0051] 6. A method according to any preceding clause, wherein the list is generated on a configuration management unit, a network switch or an interface device.

[0052] 7. A method according to any preceding clause, wherein the list is generated on an interface device, and the interface device comprises a remote interface unit.

[0053] 8. A method according to any preceding clause, wherein the configuration management unit comprises an aircraft architecture.

[0054] 9. The method of any preceding clause, wherein issuing an alert further comprises indicating which functions of the aircraft are affected when one or more of the networked avionics devices meet a predetermined threshold.

[0055] 10. A method according to any preceding clause, wherein the monitoring list comprises periodically measuring aspects of the networked avionics equipment and comparing the measured aspects to predetermined thresholds.

[0056] 11. A method according to any preceding clause, wherein periodically measuring comprises continuously measuring aspects of the networked avionics equipment.

[0057] 12. A method according to any preceding clause, wherein the measuring aspect comprises measuring the throughput or throughput capacity of one or more of the networked avionics.

[0058] 13. A method according to any preceding clause, wherein measuring aspects comprises measuring one or more of memory usage, memory capacity, processor usage, processor capacity, temperature, vibration, sound or pressure.

[0059] 14. The method of any preceding clause, wherein periodically measuring further comprises: storing historical information based on previous periodic measurements, and comparing a most recent periodic measurement to at least one of the previous periodic measurements to determine a trend.

[0060] 15. A method according to any preceding clause, wherein monitoring further comprises monitoring trends to identify unexpected behavior that does not meet a predetermined threshold.

[0061] 16. A method according to any preceding clause, further comprising updating the predetermined threshold based on a trend.

[0062] 17. The method of any preceding clause, further comprising reconfiguring the network of networked avionics based on the trends.

[0063] 18. A network system for an aircraft, comprising: a set of aircraft components; a network that communicatively and electronically interconnects the set of aircraft components; a configuration management unit that is capable of electronically communicating with the network and is configured to detect or measure the set of aircraft components on the network, wherein the configuration management unit is configured to generate a list representing a configuration of the network and the set of aircraft components; wherein the list includes executable items or libraries associated with the set of aircraft components and the network; and wherein the configuration management unit is configured to monitor the list to determine whether the configuration is no longer approved by the configuration management unit.

[0064] 19. A network system according to any preceding clause, wherein the monitoring list comprises one or more of monitoring throughput, monitoring throughput capacity, monitoring memory usage, monitoring memory capacity, monitoring temperature or monitoring pressure of a set of aircraft components.

[0065] 20. The network system according to any of the preceding clauses, wherein the configuration management unit is part of a configuration management unit of an architecture hosting an aircraft.

[0066] 21. A method for monitoring network security in an aircraft, the method comprising: generating a list representing an aircraft network and one or more aircraft components on the aircraft network; periodically monitoring the list; and when one or more aircraft components monitored on the list reach a predetermined threshold, indicating on a display which functions of the aircraft may be affected or affected.

[0067] 22. A method according to any preceding clause, wherein the indication on the display takes place in a cockpit of the aircraft or is displayed on a maintenance display.

[0068] 23. A method according to any preceding clause, wherein periodically monitoring the list further comprises storing historical information based on previous periodic measurements in a memory, and comparing a most recent periodic measurement to at least one of the previous periodic measurements to determine a trend.

[0069] 24. A method according to any preceding clause, wherein monitoring further comprises monitoring trends to identify unexpected behaviour that does not meet a predetermined threshold.

[0070] 25. A method according to any preceding clause, further comprising updating the predetermined threshold based on the trend.

[0071] This written description uses examples to disclose aspects of the disclosure, including the best mode, and also to enable those skilled in the art to practice aspects of the disclosure, including making and using any device or system and performing any combined methods. The patentable scope of the invention is defined by the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements that do not differ significantly from the literal language of the claims.

Claims

1. A method for monitoring the health and safety of networked avionics equipment on an aircraft, It is characterized in that The method comprises: generating a list including executable items and libraries representing the networked avionics equipment; evaluating at least one of an encrypted signature or an encrypted token for each of said networked avionics devices corresponding to said list; verifying, based on the evaluating, that each of the networked avionics equipment is at least one of physically present on the aircraft or located on a network in communication with the aircraft; monitoring the list via a configuration management unit (CMU), wherein monitoring the list includes periodically measuring aspects of the networked avionics and comparing the measured aspects to predetermined thresholds, wherein periodically measuring further includes: storing historical information based on previous periodic measurements, and comparing a most recent periodic measurement to at least one of the previous periodic measurements to determine a trend; updating the predetermined threshold based on the trend, wherein the CMU continuously monitors to provide continuous updates of monitoring of the network based on the list; When one or more of the networked avionics devices provided on the list meets the predetermined threshold, an alert is issued.

2. The method according to claim 1, It is characterized in that The executable items and libraries include configuration files and static memory.

3. The method according to claim 1, It is characterized in that Wherein the predetermined threshold comprises one or more items on the list not being in the list.

4. The method according to claim 1, It is characterized in that Wherein the list further comprises an associated static memory entry stored on at least one of the networked avionics devices.

5. The method according to claim 1, It is characterized in that The list is generated on a configuration management unit, a network switch or an interface device.

6. The method according to claim 5, It is characterized in that Wherein the list is generated on the interface device, and the interface device comprises a remote interface unit.

7. The method according to claim 5, It is characterized in that The list is generated on the configuration management unit, and the configuration management unit includes an aircraft architecture.

8. The method according to claim 7, It is characterized in that Wherein issuing an alert further comprises indicating which functions of the aircraft may be affected when one or more of the networked avionics devices meet the predetermined threshold.

9. The method according to claim 1, It is characterized in that Wherein periodically measuring comprises continuously measuring aspects of the networked avionics equipment.

10. The method according to claim 1, It is characterized in that Wherein monitoring further comprises monitoring the trends to identify unexpected behaviors that do not meet the predetermined thresholds.

11. A network system for an aircraft, It is characterized in that include: a set of aircraft parts; a network communicatively and electronically interconnecting the set of aircraft components; a configuration management unit capable of electronically communicating with the network and configured to detect or measure the set of aircraft parts on the network, wherein the configuration management unit is configured to: generating a list representing a configuration of the network and the set of aircraft parts; evaluating at least one of an encrypted signature or an encrypted token for each aircraft part of the set of aircraft parts corresponding to the list; verifying, based on the evaluating, that each aircraft part of the set of aircraft parts is at least one of physically present on the aircraft or located on a network in communication with the aircraft; wherein the list includes executable items or libraries associated with the set of aircraft parts and the network; and wherein the configuration management unit (CMU) is configured to monitor the list to determine whether the configuration is no longer approved by the configuration management unit, wherein monitoring the list includes periodically measuring aspects of networked avionics equipment and comparing the measured aspects to predetermined thresholds, wherein periodically measuring further includes: storing historical information based on previous periodic measurements, and comparing a recent periodic measurement to at least one of the previous periodic measurements to determine a trend, wherein monitoring further includes updating the predetermined threshold based on the trend, wherein the CMU continuously monitors to provide continuous updates of monitoring of the network based on the list.

12. The network system according to claim 11, It is characterized in that Wherein monitoring the list includes one or more of monitoring throughput, monitoring throughput capacity, monitoring memory usage, monitoring memory capacity, monitoring temperature, or monitoring pressure of the set of aircraft components.

13. The network system according to claim 11, It is characterized in that The configuration management unit is part of a configuration management unit of an architecture that hosts the aircraft.

14. A method for monitoring network security in an aircraft, It is characterized in that The method comprises: generating a list representing an aircraft network and one or more aircraft parts on the aircraft network; evaluating at least one of an encrypted signature or an encrypted token for each aircraft part corresponding to the one or more aircraft parts of the list; verifying, based on the evaluating, that each of the one or more aircraft parts is at least one of physically present on the aircraft or located on a network in communication with the aircraft; periodically monitoring the list via a configuration management unit (CMU), wherein monitoring the list includes periodically measuring aspects of the networked avionics and comparing the measured aspects to predetermined thresholds, wherein periodically measuring further includes: storing historical information based on previous periodic measurements, and comparing a most recent periodic measurement to at least one of the previous periodic measurements to determine a trend; updating the predetermined threshold based on the trend, wherein the CMU continuously monitors to provide continuous updates of monitoring of the network based on the list; and monitoring the list to determine if the CMU no longer approves the configuration, and if the CMU no longer approves the configuration, dynamically reconfiguring the configuration of the network by updating a data path from which the at least one aspect is measured; Wherein the list includes executable items or libraries associated with the one or more aircraft parts and the network.

15. The method according to claim 14, It is characterized in that Wherein periodically monitoring the list further comprises storing historical information based on previous periodic measurements in a memory and comparing a most recent periodic measurement to at least one of the previous periodic measurements to determine a trend.

16. The method according to claim 14, It is characterized in that Wherein periodically monitoring further comprises monitoring the trend to identify unexpected behavior that does not meet the predetermined threshold.

Images