High-energy management system

Abstract

The invention relates to a high energy management system. A technique for controlling a high energy management system of an aircraft includes receiving sensor data from a plurality of high energy (HE) systems, where each of the plurality of HE systems is located in the aircraft; determining a current state of each of the plurality of HE systems based on the sensor data; determining a target state of each of the plurality of HE systems based on the current state of each of the plurality of HE systems and the HE system rule set; and automatically generating one or more control actions to enable control of one or more of the plurality of HE systems based on the target state of each of the plurality of HE systems. Examples also include receiving a task schedule to be performed on the aircraft, where determining the target state is also based on the task schedule.

Description

Technical Field

[0001] The present disclosure relates to techniques for managing a high energy (HE) system of an aircraft. More specifically, the present disclosure relates to a control system for controlling an aircraft high energy system based on a current state of the HE system and HE system rules. Background Art

[0002] During the manufacture, testing, or maintenance of an aircraft, workers may be exposed to high-energy systems (e.g., electrical systems, hydraulic systems, propulsion systems, cockpit power systems, fuel systems, etc.). These systems may be activated or deactivated accidentally and / or in a conflicting manner during manufacturing, testing, or maintenance operations, resulting in worker injuries, damage to equipment or devices, and / or maintenance delays related to unintentional exposure to high-energy systems. Currently, the only mechanism for preventing unintentional exposure to high-energy systems is through geo-fencing, in which a physical barrier or boundary is erected around the perimeter to keep people away from specific areas of the aircraft where there is a risk of exposure to high-energy systems. However, this approach has disadvantages because key employees who need to work on high-energy systems (e.g., within the perimeter) are still subject to the risk of exposure. In addition, geo-fencing does not protect equipment (e.g., within the perimeter) from damage caused by exposure. Summary of the invention

[0003] Disclosed herein are methods, apparatus, and systems for managing high energy systems in an aircraft (A / C) by determining a target state of the high energy system based on a current state and a set of high energy system rules and generating control actions based on the target state to achieve control of the high energy system. The target state is set to avoid activating incompatible systems at the same time. In some examples, the target state is further determined based on the scheduling of tasks to be performed on the aircraft (e.g., high energy system tasks). In addition, the state and mode of each high energy system on the aircraft will be transmitted to key personnel in real time, thereby providing an understanding of the state of the high energy system and potential conflicting system activations.

[0004] According to one or more examples, a method of controlling a high energy management system includes: receiving sensor data from a plurality of high energy (HE) systems, wherein each of the plurality of HE systems is located in an aircraft; determining a current state of each of the plurality of HE systems based on the sensor data; determining a target state of each of the plurality of HE systems based on the current state of each of the plurality of HE systems and a set of HE system rules; and automatically generating one or more control actions based on the target state of each of the plurality of HE systems to implement control of one or more of the plurality of HE systems.

[0005] According to one or more examples, a high energy management system controller includes a processor and a memory connected to the processor, the memory including instructions that, when executed by the processor, cause the high energy management system controller to perform operations, the operations including: receiving sensor data from a plurality of high energy (HE) systems, wherein each of the plurality of HE systems is located in an aircraft; determining a current state of each of the plurality of HE systems based on the sensor data; determining a target state of each of the plurality of HE systems based on the current state of each of the plurality of HE systems and a set of HE system rules; and automatically generating one or more control actions based on the target state of each of the plurality of HE systems in the plurality of HE systems to achieve control of one or more of the plurality of HE systems.

[0006] According to one or more examples, at least one computer-readable storage medium includes instructions that, when executed by a processor, cause a high energy management system controller to perform operations, the operations comprising: receiving sensor data from a plurality of high energy (HE) systems, wherein each of the plurality of HE systems is located in an aircraft; determining a current state of each of the plurality of HE systems based on the sensor data; determining a target state of each of the plurality of HE systems based on the current state of each of the plurality of HE systems and a set of HE system rules; and automatically generating one or more control actions based on the target state of each of the plurality of HE systems to achieve control of one or more of the plurality of HE systems.

[0007] The features, functions, and advantages that have been discussed can be achieved independently in various examples or may be combined in yet other examples, further details of which can be seen with reference to the following description and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Various advantages of the embodiments will become apparent to those skilled in the art upon reading the following description and appended claims, and by referring to the following drawings, in which:

[0009] Figure 1A to Figure 1B A block diagram illustrating an example of a high energy management system according to one or more examples is provided;

[0010] FIG. 2A to FIG. 2B A block diagram illustrating another example of a high energy management system according to one or more examples is provided;

[0011] Figure 3 A block diagram illustrating an example of a high energy management system controller according to one or more examples is provided;

[0012] FIG. 4A to FIG. 4B A flowchart illustrating an example method of controlling a high energy management system according to one or more examples is provided; and

[0013] Figure 5 A block diagram is provided that illustrates an example computing system for controlling a high energy management system according to one or more examples.

[0014] It should therefore be understood that the examples described herein are merely illustrative of the application of the disclosed principles. Reference herein to details of the illustrated examples is not intended to limit the scope of the claims, which themselves recite those features regarded as essential to the disclosure. DETAILED DESCRIPTION

[0015] Methods, devices, and systems for managing high energy systems (HEMS) in aircraft are disclosed. High energy systems are required for safe operation of aircraft, but exposure to high energy systems (HE systems) during manufacturing, testing, or maintenance can result in injury to personnel and damage to equipment or devices. "High energy" systems for aircraft are systems that present a risk of physical injury and / or equipment damage due to exposure to one or more of the following types of energy: electrical (e.g., via voltage, current, charge, etc.), thermal (e.g., via liquid, gas, material surface, etc.), pneumatic (e.g., via air under pressure), hydraulic (e.g., via liquid under pressure), mechanical / dynamic (e.g., via movement of objects), mechanical / electrical potential (e.g., via storage location or gravity), chord (e.g., via explosive materials), and / or radiation (e.g., via radio frequency, electric and magnetic field radiation, etc.).

[0016] Examples of high energy systems include one or more of an electrical system, a hydraulic system, a propulsion system, a cockpit power system, a payload and coordination system, and / or a fuel system. As an example, a hydraulic system may present a risk of bodily injury and / or equipment damage due to movement of equipment (e.g., flaps) caused not only by the fluid under pressure but also by changes in hydraulic pressure. Other examples of high energy systems for an aircraft may include one or more of a radar system, an oxygen tank (or bottle) system, a pneumatic system, a door spring system, and the like.

[0017] Therefore, there is a need to properly control high energy systems to avoid exposure that could otherwise result in injury or damage. The technology described herein meets this need by actively and continuously controlling the activation and deactivation of high energy systems to mitigate, reduce or avoid system conflicts (such as unintentional simultaneous exposure to conflicting types of high energy) that are not only dangerous but can also result in scheduling delays as well as quality issues (e.g., due to equipment damage on the aircraft). This capability supports personnel not only during the manufacturing process, but also during testing or maintenance activities.

[0018] Figure 1A to Figure 1B A block diagram illustrating an example of a high energy management system 100 according to one or more examples is provided, with reference to components and features described herein, including but not limited to the drawings and associated descriptions. Figure 1A As shown, the high energy management system 100 includes a high energy management system controller 110, a plurality of high energy (HE) systems 120, and a plurality of user devices 140. The high energy management system controller 110 communicates with each HE system 120 and each user device 140. Communications are typically exchanged between the high energy management system controller 110 and individual systems or devices (e.g., individual systems or devices in the HE systems 120 and / or user devices 140) via wireless and / or wired connections. In an example, the high energy management system 100 includes or interfaces with an operating system 145 that provides overall control or supervision of the aircraft (including supervision of the high energy management system controller 110) via one or more operations managers and / or team leaders. Reference is made herein to Figure 3 Further details regarding the energy management system controller 110 are provided.

[0019] The plurality of HE systems 120 include HE system A (120-A), HE system B (120-B), HE system C (120-A) to HE system N (120-N), and may include any number of HE systems for an aircraft. For example, the plurality of HE systems 120 may include one or more of an electrical system, a hydraulic system, a propulsion system, a cockpit power system, a payload and coordination system, and / or a fuel system. In an example, any of the HE systems may include multiple systems or subsystems (e.g., to include partitioned, distributed, and / or redundant system functions). Other examples of HE systems for an aircraft may include one or more of a radar system, an oxygen tank (or bottle) system, a pneumatic system, a door spring system, and the like. Any given HE system in the plurality of HE systems 120 is typically connected via a wired and / or wireless connection (including via a network ( Figure 1A (not shown)) is coupled (eg, connected) to the high energy management system controller 110. Figure 1B Further details regarding the architecture of the high energy management system 100 are provided.

[0020] The plurality of user devices 140 include user device A (140-A), user device B (140-B), user device C (140-C) to user device M (140-M). For example, the plurality of user devices 140 may include one or more of a desktop computer, a laptop computer, a tablet computer, a smart phone, a smart watch, etc. Any given user device in the plurality of user devices 140 is typically connected via a wired and / or wireless connection (including via a network ( Figure 1A ) is coupled (eg, connected) to the energy management system controller 110 .

[0021] Optionally, in combination with the example described above (or below), in the example, the high energy management system controller 110 also receives the ground A / C standard 125 (in Figure 1A , Figure 2A and Figure 3 The on-ground A / C standards 125 provide information to enable the high energy management system controller 110 to confirm that the aircraft is on the ground and not in flight. In such an example, the high energy management system controller 110 will actively control the HE system 120 only when the aircraft is confirmed to be in a ground state (i.e., on the ground). The high energy management system controller 110 evaluates the information from the on-ground A / C standards 125 and determines whether the aircraft is on the ground. In some examples, the ground A / C standards are determined by another module (e.g., a maintenance module or a manufacturing test module, which is in the process of controlling the HE system 120). Figure 1A ) and the result of the evaluation (eg, an indication that the aircraft is in a ground state or that the aircraft is not in a ground state) is provided to the high energy management system controller 110 as the on-ground A / C standard 125.

[0022] Optionally, in conjunction with the examples described above (or below), in an example, the high energy management system controller 110 also receives a task schedule 130 as input. The task schedule 130 provides information about tasks (e.g., manufacturing tasks, test tasks, or maintenance tasks) of high energy systems to be performed on the aircraft, as well as the timing and / or sequence of task execution. The task schedule may be provided, for example, via a scheduling tool. The tasks (and their timing / sequence) will affect the control actions taken by the high energy management system controller 110 with respect to any one or more of the HE systems 120 based at least on the HE system rules.

[0023] Now go to Figure 1B , which shows details about the architecture of the high energy management system 100, in particular the components of the HE system 120 and the communication paths between the high energy management system controller 110 and any one or more of the HE systems 120. Any given HE system in the plurality of HE systems 120 will typically have at least one sensor and at least one actuator. For example, Figure 1B As shown, HE system A (120-A) has at least one sensor 122-A and at least one actuator 124-A; similarly, HE system N (120-N) has at least one sensor 122-N and at least one actuator 124-N. The sensors and actuators are distributed through the aircraft and are typically located in or near the corresponding HE system of the aircraft.

[0024] For a given HE system, sensors provide information about the state of the HE system, and actuators provide control mechanisms to activate (turn on) or deactivate (turn off) the HE system (or a portion or component thereof). The state of a HE system relates to the operating condition of the HE system, including whether the HE system is turned on (e.g., active, powered on, etc.) or turned off (e.g., inactive, powered off, etc.). A person of ordinary skill will know the types of sensors used with any HE system, and will understand how to determine the current state of the HE system from the sensor data of any given HE system. Based on the sensor data, the high energy management system controller 110 determines the current state of each HE system 120. That is, the high energy management system controller 110 is configured to interpret the sensor data of the HE system for a given HE system so as to determine the current state of the HE system based on the data. The high energy management system controller 110 then determines the target state of each HE system 120 based on the current state and the HE system rules, and generates control actions to achieve control of the HE system 120.

[0025] In some cases, a given HE system will have multiple sensors and / or multiple actuators. As one example, for a HE system associated with a hydraulic system for setting and adjusting flaps, the hydraulic system includes multiple sensors associated with the flaps (e.g., each wing has a flap, and each flap has a sensor, etc.). Likewise, the hydraulic system includes multiple actuators associated with the flaps (e.g., each wing has a flap, and each flap has an actuator, etc.). As another example, a given HE system may have multiple sensors for redundancy purposes (e.g., redundant sensors to protect the HE system and the aircraft in the event of a sensor failure).

[0026] like Figure 1B As shown, there are typically one or more communication paths (e.g., wired and / or wireless connections) between the high energy management system controller 110 and each given HE system. For example, for a given HE system, there may be one communication path for data from sensors and another communication path for commands to actuators of that HE system. Typically, each HE system has a sub-controller ( Figure 1B 10 ), data and / or commands are transmitted between the high energy management system controller 110 and sensors and actuators for the HE system through the sub-controller. As an example, for a hydraulic system, the example HE system includes a hydraulic sub-controller that obtains sensor data (e.g., data from a pressure transducer that measures hydraulic pressure) and provides the sensor data to the high energy management system controller 110.

[0027] exist Figure 1BIn the example architectural details shown, there is a first communication path between the high energy management system controller 110 and the HE system A (120-A) for data from the sensor 122-A, a second communication path between the high energy management system controller 110 and the HE system A (120-A) for commands to the actuator 124-A, a third communication path between the high energy management system controller 110 and the HE system N (120-N) for data from the sensor 122-N, and a fourth communication path between the high energy management system controller 110 and the HE system N (120-N) for commands to the actuator 124-N. These communication paths can be separate or shared or partially overlapping. Therefore, in some examples, the communication paths between the high energy management system controller 110 and a given HE system are shared and / or overlapping.

[0028] In some examples, the high energy management system controller 110 of the high energy management system 100 is installed / embedded within the aircraft and can be located almost anywhere in the aircraft. Alternatively, in other examples, the high energy management system controller 110 is located outside the aircraft (e.g., as part of a mobile physical unit used, for example, when manufacturing or testing the aircraft) and communicates with the HE system via a wired and / or wireless connection. For example, in some other examples, the high energy management system controller 110 is integrated with a test or maintenance module (not shown). The high energy management system controller 110 is suitable for interacting with any individual HE system (e.g., as described above, via separate communication paths or via shared or overlapping paths). As an example, the high energy management system controller 110 is suitable for issuing commands to actuators of a given HE system to activate or deactivate the HE system (or a portion thereof), and then receiving sensor data (e.g., data providing the status of a given HE system), from which the high energy management system controller 110 confirms that the command was successfully executed.

[0029] Some or all components in the high energy management system 100 may be implemented using a central processing unit (CPU), a graphics processing unit (GPU), an artificial intelligence (AI) accelerator, a field programmable gate array (FPGA) accelerator, an application specific integrated circuit (ASIC), and / or via a processor with software or a combination of a processor with software and an FPGA or ASIC. More specifically, the components of the high energy management system 100 may be implemented in one or more modules as a program or logic instruction set stored in a machine or computer readable storage medium (such as a random access memory (RAM), a read-only memory (ROM), a programmable ROM (PROM), firmware, flash memory, etc.), hardware, or any combination thereof. For example, a hardware implementation may include configurable logic, fixed function logic, or any combination thereof. Examples of configurable logic include appropriately configured programmable logic arrays (PLAs), FPGAs, complex programmable logic devices (CPLDs), and general purpose microprocessors. Examples of fixed function logic include appropriately configured ASICs, combinational logic circuits, and sequential logic circuits. Configurable or fixed function logic may be implemented with complementary metal oxide semiconductor (CMOS) logic circuits, transistor-transistor logic (TTL) logic circuits, or other circuits.

[0030] For example, the computer program code for the operations performed by the high energy management system 100 may be written in any combination of one or more programming languages, including object-oriented programming languages ​​(such as Java, JavaScript, Python, C#, C++, Perl, Smalltalk, etc.) and conventional procedural programming languages ​​(such as the "C" programming language or similar programming languages). In addition, the program or logic instructions may include assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, state setting data, configuration data for integrated circuits, state information that personalizes electronic circuits and / or other structural components local to the hardware (e.g., host processor, central processing unit / CPU, microcontroller, etc.).

[0031] FIG. 2A to FIG. 2B A block diagram is provided showing another example of a high energy management system 200 according to one or more examples, with reference to the components and features described herein, including but not limited to the drawings and associated descriptions. The high energy management system 200 includes a high energy management system 100 ( Figure 1A to Figure 1B , have already been discussed), and those components and features will not be repeated except to appropriately describe the components and features of the high energy management system 200. Figure 2A As shown in the example of Figure 1A to Figure 1B), the high energy management system 200 further includes an aircraft interface module 210. From a logical point of view, the aircraft interface module 210 is located between the high energy management system controller 110 and the plurality of HE systems 120. The aircraft interface module 210 provides a communication interface between the high energy management system controller 110 and the plurality of HE systems 120, so that requests, commands, data, etc. transmitted between the high energy management system controller 110 and the plurality of HE systems 120 are routed through the aircraft interface module 210.

[0032] In essence, the aircraft interface module 210 is a pass-through device for commands and data transmitted between the high energy management system controller 110 and the plurality of HE systems 120; the aircraft interface module 210 itself does not provide HE system control functionality as described herein. Figure 2B Further details regarding the architecture of the high energy management system 200 are provided.

[0033] In some examples, the aircraft interface module 210 is a module provided as part of a manufacturing or maintenance system used in the manufacture, testing, or maintenance of aircraft HE systems. In some examples, a hybrid architecture is used in which communications between the high energy management system controller 110 and some of the plurality of HE systems 120 are routed through the aircraft interface module 210, while communications between the high energy management system controller 110 and other HE systems in the plurality of HE systems 120 are routed via a communication interface such as a Figure 1A to Figure 1B The communication paths shown are executed along the path of the communication paths and are not routed through the aircraft interface module 210 . In some examples, the on-ground A / C criteria 125 and / or the mission schedule 130 are routed to the high energy management system controller 110 through the aircraft interface module 210 .

[0034] Now go to Figure 2B , which shows details about the architecture of the high energy management system 200, particularly the components of the HE system 120 and the communication paths between the high energy management system controller 110 and any one or more of the HE systems 120 via the aircraft interface module 210. Figure 1B The architectural details shown are as follows Figure 2BAs shown, there are typically one or more communication paths (e.g., wired and / or wireless connections) between the aircraft interface module 210 and each given HE system. For example, there may be one communication path for data from sensors for a given HE system and another communication path for commands to actuators for that HE system. These communication paths may be separate or shared or partially overlapping. There are communication paths (wired and / or wireless connections) between the high energy management system controller 110 and the aircraft interface module 210, so that communications (e.g., requests, commands, data) between the high energy management system controller 110 and the HE system can be routed via the aircraft interface module 210 (e.g., acting as a pass-through device).

[0035] In some examples, the high energy management system controller 110 of the high energy management system 200 is installed / embedded within the aircraft and can be located at almost any location in the aircraft. Alternatively, in other examples, the high energy management system controller 110 is located outside the aircraft (e.g., as part of a mobile physical unit used, for example, when manufacturing or testing the aircraft) and communicates with the aircraft interface module 210 via a wired and / or wireless connection. For example, in some other examples, the high energy management system controller 110 is integrated with the aircraft interface module 210 or with a test or maintenance module (not shown). The high energy management system controller 110 is suitable for interacting with any individual HE system via a communication path between the high energy management system controller 110 and the aircraft interface module 210 and a communication path between the aircraft interface module 210 and the HE system. As an example, the high energy management system controller 110 is suitable for issuing commands for actuators of a given HE system to activate or deactivate the HE system, and then receiving sensor data (e.g., data providing the status of a given HE system), from which the high energy management system controller 110 confirms that the command was successfully executed.

[0036] Some or all components in the high energy management system 200 may be implemented using a central processing unit (CPU), a graphics processing unit (GPU), an artificial intelligence (AI) accelerator, a field programmable gate array (FPGA) accelerator, an application specific integrated circuit (ASIC), and / or via a processor with software or a combination of a processor with software and an FPGA or ASIC. More specifically, the components of the high energy management system 200 may be implemented in one or more modules as a program or logic instruction set stored in a machine or computer readable storage medium (such as a random access memory (RAM), a read-only memory (ROM), a programmable ROM (PROM), firmware, flash memory, etc.), hardware, or any combination thereof. For example, a hardware implementation may include configurable logic, fixed function logic, or any combination thereof. Examples of configurable logic include appropriately configured programmable logic arrays (PLAs), FPGAs, complex programmable logic devices (CPLDs), and general purpose microprocessors. Examples of fixed function logic include appropriately configured ASICs, combinational logic circuits, and sequential logic circuits. Configurable or fixed function logic may be implemented with complementary metal oxide semiconductor (CMOS) logic circuits, transistor-transistor logic (TTL) logic circuits, or other circuits.

[0037] For example, the computer program code for the operations performed by the high energy management system 200 may be written in any combination of one or more programming languages, including object-oriented programming languages ​​(such as Java, JavaScript, Python, C#, C++, Perl, Smalltalk, etc.) and conventional procedural programming languages ​​(such as the "C" programming language or similar programming languages). In addition, the program or logic instructions may include assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, state setting data, configuration data for integrated circuits, state information that personalizes electronic circuits and / or other structural components local to the hardware (e.g., host processor, central processing unit / CPU, microcontroller, etc.).

[0038] Figure 3 A block diagram illustrating an example of a high energy management system controller 300 according to one or more examples is provided, with reference to components and features described herein, including but not limited to the drawings and associated descriptions. The high energy management system controller 300 corresponds to the high energy management system controller 110 ( Figure 1A to Figure 1B as well as FIG. 2A to FIG. 2B , already discussed). Figure 3 As shown, the high energy management system controller 300 includes a processing module 310 and a control module 320, and the control module 320 includes a HE system rule 330. The high energy management system controller 300 communicates with the HE system 120 via a communication path between the high energy management system controller 300 and the HE system 120 (e.g., as described herein with reference to Figure 1A to Figure 1B ) or via the aircraft interface module 210 (e.g., as described herein with reference to FIG. 2A to FIG. 2B The ) receives sensor data 305 obtained from sensors of the HE system. In an example, the high energy management system controller 300 also receives on-ground A / C standards 125 and / or mission schedules 130 as input.

[0039] The high energy management system controller 300 sends a message to a user device (eg, user device 140, Figure 1A and Figure 2A ) and, if present, to the operating system (e.g. Figure 1A and Figure 2A Operating system 145, in Figure 3 The high energy management system controller 300 may also receive, for example, a communication path between the high energy management system controller 300 and the HE system 120 (e.g., as described herein with reference to “operating system”) and issue (e.g., send) status reports 312 and alerts 314. The high energy management system controller 300 may receive, for example, one or more selections / commands 322 from an authorized user via a user device and / or an operating system (when present). The high energy management system controller 300 may also receive, for example, a communication path between the high energy management system controller 300 and the HE system 120 (e.g., as described herein with reference to Figure 1A to Figure 1B ) or via the aircraft interface module 210 (e.g., as described herein with reference to FIG. 2A to FIG. 2B The ) issues a control action 340 for an actuator of the HE system 120 .

[0040] The processing module 310 receives and analyzes sensor data 305 collected from sensors of the HE systems 120 in real time. The sensor data includes feedback data about the status (including, for example, state, mode, and / or condition) related to each specific HE system. A person of ordinary skill will know the types of sensors used with any HE system and will understand how to determine the current status of any given HE system from the sensor data of the HE system. The processing module 310 is configured to interpret the sensor data of the HE system for a given HE system in order to determine the current status of the HE system based on the data. Based on the sensor data, the processing module 310 determines the current (e.g., current) status of each HE system in the HE system 120. For example, the current status may include an on state (e.g., a particular HE system is on, powered on, active / activated, etc.) or an off state (e.g., a particular HE system is off, locked / off, powered off, inactive / deactivated, etc.). The processing module 310 then sends information about the current status of the HE system to the control module 320 in real time.

[0041] In an example, the processing module 310 receives and analyzes the task schedule 130 in real time. The task schedule 130 provides information about the tasks of the high-energy system to be performed on the aircraft (including, for example, manufacturing tasks, test tasks, or maintenance tasks and details about the tasks), as well as the timing and / or sequence for performing the tasks. The processing module 310 determines the current (e.g., current) status of the scheduled tasks for the aircraft, including, for example, any delays in starting or completing a particular task, and sends information about the current status of the scheduled tasks for the aircraft to the control module 320. The processing module 310 also sends updates about the tasks (e.g., based on control actions determined by the control module 320 or overrides issued by authorized users), which may include changes to the schedule.

[0042] In an example, the processing module 310 receives and evaluates the on-ground A / C criteria 125. The on-ground A / C criteria 125 provide information to confirm that the aircraft is on the ground and not in flight. In some examples, the on-ground A / C criteria 125 include information for one or more conditions, including conditions indicating that the aircraft is on the ground and not in flight, such as weight on wheels, gear check, engine shut down, etc. In some examples, these conditions are evaluated by another module (e.g., a maintenance module, not shown), and the result of the evaluation is an indication (e.g., the aircraft is in a ground state or the aircraft is not in a ground state) provided to the processing module 310 as the on-ground A / C criteria 125.

[0043] The processing module 310 evaluates the on-ground A / C criteria 125 and determines whether the aircraft is in a ground state (i.e., on the ground). If the processing module 310 determines that the aircraft is in a ground state (i.e., on the ground) based on the on-ground A / C criteria 125, the high energy management system controller 300 will (via the control module 320) actively control the HE system 120 via control action 340; otherwise, if the aircraft is not determined to be in a ground state, the high energy management system controller 300 will not issue control action 340 to control the HE system 120. In this way, the active control of the HE system by the control module 320 is conditioned on the determination that the aircraft is in a ground state.

[0044] The control module 320 receives information about the current state of the HE system from the processing module 310 in real time. In the example, the control module 320 also receives information about the current state of the scheduled tasks of the aircraft from the processing module 310 in real time. The control module 320 evaluates the information received from the processing module 310 (i.e., including the current state of the HE system, and the current state of the scheduled tasks when provided) using the HE system rules 330 and determines a target state for each of the plurality of HE systems 120. The target state of the HE system is a state that the HE system rules 330 allow to prevent or eliminate conflicts between activation and / or deactivation of individual HE systems.

[0045] Based on the target state of each HE system 120, the control module 320 automatically generates one or more control actions 340 to achieve control of one or more HE systems in the plurality of HE systems 120. For example, when it is necessary to place the HE system in the target state, such as when the current state of the HE system does not match the target state of the HE system, the control module 320 generates a control action 340 to be sent to a specific HE system actuator. The control action 340 includes one or more commands issued to one or more actuators of a given HE system to place the HE system in the target state determined by the control module 320. For example, the command may include a command to turn on or off a specific HE system. In some examples, the commands are issued sequentially to achieve control of activation or deactivation of the HE system according to a sequence (e.g., a control sequence established by the HE system rules 330 for a given task). In an example, when the current state of the HE system matches the target state of the HE system, no control action is required and therefore no control action is generated for the HE system at that time.

[0046] Thus, by actively generating control actions 340 in real time, the control module 320 ensures that each respective HE system in the plurality of HE systems 120 is placed in (or maintained in) a target state for the HE system until it is necessary or appropriate to change the target state for the HE system based on the current state of the HE system, a change in the current state of the mission, etc. As an example, if the control module 320 determines that a hydraulic system is currently active and the current mission involves work in the vicinity of flaps on the aircraft, then based on the HE system rules, the control module 320 issues control actions to one or more actuators of the hydraulic system as needed to keep the hydraulic system active for the duration of the mission (e.g., to prevent deactivation of the hydraulic system) to prevent the flaps from falling and potentially causing harm. Additionally, based on the HE system rules 330, the control module 320 issues control actions to deactivate or maintain a deactivated state any HE system that would conflict with a hydraulic system that is active for a particular mission (e.g., to prevent activation of any conflicting HE systems during the mission).

[0047] The HE system rules 330 may be stored, for example, in a memory included in or accessible to the high energy management system controller 300. The HE system rules 330 define which HE systems can be activated (e.g., turned on) or deactivated (e.g., turned off) at the same time. In some examples, the HE system rules 330 include one or more of the following: (a) rules specifying which HE systems in a plurality of HE systems can be active with each other (e.g., a rule specifying that HE system A can be active when HE system B is active), (b) rules specifying which HE systems in a plurality of HE systems must be active with another HE system in a plurality of HE systems (e.g., a rule specifying that HE system C must be active when HE system D is active), and / or (c) rules specifying which HE systems in a plurality of HE systems cannot be active with each other (e.g., a rule specifying that HE system E must be inactive when HE system F is active).

[0048] In some examples, the HE system rules 330 further specify conditions for activating or deactivating some of the HE systems in the HE system to avoid hazardous conditions. For example, in an example, the rules specifying conditions for activating or deactivating some of the HE systems in the HE system include one or more of rules specifying an order for activating or deactivating a subset of a plurality of HE systems (e.g., various HE systems in the HE system) and / or rules specifying timing requirements associated with activating or deactivating some of the HE systems in the HE system. In an example, the rules are defined at least in part based on a type or nature of a task (e.g., a manufacturing task, a test task, or a maintenance task). As an example, for a test or maintenance task of an electrical system, the HE system rules 330 may specify that two adjacent electrical systems (i.e., two systems or components thereof that are immediately adjacent to each other) are not activated at the same time to avoid inadvertent or accidental contact with nearby systems.

[0049] For example, the timing / sequence defined by HE system rules 330 ensures that a particular HE system is not turned on or off too early or too late. In some examples, HE system rules 330 include rules that depend on the task being performed (or to be performed next). As an example, if a maintenance task involving activation of a hydraulic system is being performed, HE system rules 330 may specify that an electrical system (e.g., a system complementary to the hydraulic system) that provides power to the hydraulic system is not deactivated until the hydraulic task is completed so that power remains for the hydraulic system to have pressure to hold the aircraft component in place for the duration of the task.

[0050] The control module 320 sends information identifying conflicts or potential conflicts between HE systems (e.g., conflicting or potentially conflicting activations and / or deactivations of HE systems) to the processing module 310. Such conflicts may be caused by task scheduling, including delays in starting or completing a particular task, or unintentional human errors, or system failures, etc.

[0051] The control module 320 also communicates with the user devices 140. The control module 320 sends a status report 312 to one or more user devices 140 for display. In some examples, the status report 312 is sent to all personnel or key personnel (e.g., with primary or supervisory responsibilities) involved in manufacturing, testing, or maintenance, while in other examples, the status report 312 is sent to personnel on a project or task basis (e.g., personnel involved in a particular project or a task involving interaction or potential exposure to a particular HE system). The status report 312 provides information about the current status of one or more HE systems 120. For example, the status report 312 indicates which HE systems are in an on state and which HE systems are in an off state. In an example, the status report also provides information about the current status of scheduled tasks, including, for example, any delays in starting or completing a particular task.

[0052] The real-time status information in the status report 312 can be displayed to any digital client device, such as (but not limited to) a smart watch, a smart phone, a tablet computer, a laptop computer, a desktop computer, etc. In addition, in some examples, the real-time status information in the status report 312 is provided via a database, and a user can log in to the database to view or retrieve the status information. With this information, all key personnel will know in real time which systems are on / active and which systems are off / deactivated / locked.

[0053] In addition, the control module 320 sends an alert 314 to one or more user devices 140. In some examples, the alert 314 is sent to all personnel involved in manufacturing, testing, or maintenance, while in other examples, the alert 314 is sent to key personnel (e.g., with primary or supervisory responsibilities), or to personnel on a project or task basis (e.g., personnel involved in a specific project or task that interacts with or is potentially exposed to a specific HE system). The alert 314 provides information of higher priority or urgency than the status report 312, such as, for example, information about a target state of one or more of the multiple HE systems, or one or more control actions, changes in task scheduling, or conflicting activations and / or deactivations of HE systems (e.g., potentially involving task scheduling or delays). Such conflicts may include potential conflicts (e.g., conflicts that have not yet occurred) and may be caused by task scheduling, including delays in starting or completing specific tasks, or unintentional human errors, or system failures, etc.

[0054] As one example, when two conflicting HE systems are about to be activated simultaneously, key personnel will be alerted via sending an alarm 314; in this case, the control module 320 will issue one or more control actions 340 to deactivate (or prevent activation of) at least one or more conflicting HE systems according to the HE system rules 330. Information identifying conflicts (including potential conflicts) is provided by the control module 320 to the processing module 310. As another example, when one HE system task is delayed and now conflicts with another HE system task, an alarm 314 will be issued (e.g., sent). In an example, the alarm also provides information about missing sensor data (e.g., data that was expected but not received from any particular sensor).

[0055] The control module 320 receives one or more selections / commands 322 from one or more user devices. While the status report 312 and the alert 314 can be sent to any personnel (e.g., based on proximity to one of the multiple HE systems), the issuance of the one or more selections / commands 322 is typically limited to certain authorized personnel with supervisory responsibilities, such as an operations manager or a team leader. In response to the status report 312 and / or the alert 314, the authorized user can issue the selection / command 322 via the user device. For example, the authorized user can issue the command 322 to cancel or reschedule the task, which causes the control module to apply the HE system rule 330 to issue the control action 340 to implement the scheduling change. As another example, the authorized user can issue the command 322 to override the control module's decision to activate or deactivate a particular HE system, for example, to deactivate an emergency stop command for the HE system.

[0056] In an example, authorized personnel can issue commands to activate or deactivate any HE system on the aircraft. In an example, an authorized user via an operating system (e.g., Figure 1A and Figure 2A The control module 320 may issue a selection / command 322 to the operating system 145 in the HE system 120. For example, based on receiving the command 322, the control module 320 issues a new or modified control action 340 to one or more of the HE systems 120. In this manner, the control module 320 modifies one of the one or more control actions 340 based on the command 322.

[0057] The processing module 310 and the control module 320 operate in coordination and continuously. This enables the high energy management system controller 300 to actively monitor all HE systems on the aircraft via the processing module 310, and provide ongoing real-time status reports and alerts via the control module 320, and actively provide real-time control to activate deconfliction on the HE systems.

[0058] Some or all of the components in the high energy management system controller 300 may be implemented using one or more of a CPU, a GPU, an AI accelerator, an FPGA accelerator, an ASIC, and / or via a processor with software or a combination of a processor with software and an FPGA or ASIC. More specifically, the components of the high energy management system controller 300 may be implemented in one or more modules as a program or logic instruction set, hardware, or any combination thereof stored in a machine or computer readable storage medium (such as RAM, ROM, PROM, firmware, flash memory, etc.). For example, a hardware implementation may include configurable logic, fixed function logic, or any combination thereof. Examples of configurable logic include appropriately configured PLAs, FPGAs, CPLDs, and general purpose microprocessors. Examples of fixed function logic include appropriately configured ASICs, combinational logic circuits, and sequential logic circuits. Configurable or fixed function logic may be implemented with CMOS logic circuits, TTL logic circuits, or other circuits.

[0059] For example, the computer program code for operations performed by the high energy management system controller 300 may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, JavaScript, Python, C#, C++, Perl, Smalltalk, etc., and conventional procedural programming languages ​​such as the "C" programming language or similar programming languages. In addition, the program or logic instructions may include assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, state setting data, configuration data for integrated circuits, state information that personalizes electronic circuits and / or other structural components local to the hardware (e.g., host processor, central processing unit / CPU, microcontroller, etc.).

[0060] FIG. 4A to FIG. 4B A flow chart is provided showing an example method 400 (including process portions 400A and 400B) for controlling a high energy management system according to one or more examples, with reference to components and features described herein, including but not limited to the figures and associated descriptions. The method 400 may generally be performed in the high energy management system 100 ( Figure 1A to Figure 1B , already discussed), high energy management system 200 ( FIG. 2A to FIG. 2B , already discussed) and / or via the high energy management system controller 300 ( Figure 3, discussed above) or its components. More specifically, method 400 may be implemented as one or more modules as a set of logical instructions stored in a machine or computer readable storage medium (such as RAM, ROM, PROM, firmware, flash memory, etc.), in hardware, or in any combination thereof. For example, a hardware implementation may include configurable logic, fixed-function logic, or any combination thereof. Examples of configurable logic include appropriately configured PLAs, FPGAs, CPLDs, and general-purpose microprocessors. Examples of fixed-function logic include appropriately configured ASICs, combinational logic circuits, and sequential logic circuits. Configurable or fixed-function logic may be implemented using CMOS logic circuits, TTL logic circuits, or other circuits.

[0061] For example, computer program code for performing the operations shown in method 400 and / or the functions associated therewith may be written in any combination of one or more programming languages, including object-oriented programming languages ​​(such as Java, JavaScript, Python, C#, C++, Perl, Smalltalk, etc.) and conventional procedural programming languages ​​(such as the "C" programming language or similar programming languages). In addition, program or logic instructions may include assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, state setting data, configuration data for integrated circuits, state information that personalizes electronic circuits and / or other structural components local to hardware (e.g., host processors, central processing units / CPUs, microcontrollers, etc.).

[0062] Go to Figure 4A , illustrated processing block 410a provides for receiving sensor data from a plurality of high energy (HE) systems, wherein at block 410b, each of the plurality of HE systems is located in an aircraft. Illustrated processing block 420 provides for determining a current state of each of the plurality of HE systems based on the sensor data. Illustrated processing block 430 provides for determining a target state for each of the plurality of HE systems based on the current state of each of the plurality of HE systems and a set of HE system rules. Illustrated processing block 440 provides for automatically generating one or more control actions to implement control of one or more of the plurality of HE systems based on the target state of each of the plurality of HE systems.

[0063] In some examples, the HE system rule set includes rules specifying conditions for activating or deactivating a HE system in the plurality of HE systems, and one or more of the following: rules specifying which HE systems in the plurality of HE systems can be active with each other, rules specifying which HE systems must be active with another HE system in the plurality of HE systems, or rules specifying which HE systems cannot be active with each other. In some examples, the rules specifying conditions for activating or deactivating a HE system in the plurality of HE systems include one or more of rules specifying an order for activating or deactivating a subset of the plurality of HE systems, or rules specifying timing requirements related to activating or deactivating a HE system in the plurality of HE systems. In some examples, active control of the plurality of HE systems is conditioned upon determining that the aircraft is in a ground state. In some examples, the plurality of HE systems include one or more HE systems selected from the group consisting of an electrical system, a hydraulic system, a propulsion system, a cockpit power system, a payload and coordination system, or a fuel system.

[0064] Now go to Figure 4B In some examples, processing block 450a is shown providing for receiving a schedule of tasks to be performed on the aircraft (e.g., tasks for a high energy system), wherein at block 450b, determining a target state for each of the plurality of HE systems is further based on the schedule of tasks. In some examples, a rule specifying a condition for activating or deactivating a HE system in the plurality of HE systems is based on one or more identified tasks. In some examples, processing block 460a is shown providing for sending an alert to a user device, wherein at block 460b, the alert is based on one or more of: a target state for one or more of the plurality of HE systems, one or more control actions, or conflicting activation or deactivation of the HE systems.

[0065] In some examples, illustrated processing block 470 provides for receiving a command from a user device related to one of the plurality of HE systems, and illustrated processing block 475 provides for modifying one of the one or more control actions based on the command. In an example, the command is received from a user device of a user authorized to issue the command. In some examples, illustrated processing block 480 includes providing information about the current status of the plurality of HE systems for display on the user device.

[0066] Figure 5 A block diagram is provided showing an example of a computing system 10 for controlling a high energy management system according to one or more examples, with reference to components and features described herein, including but not limited to the drawings and associated descriptions. In the example, the computing system 10 corresponds to or implements a high energy management system 100 ( Figure 1A to Figure 1B , already discussed), high energy management system controller 110 ( Figure 1A to Figure 1B , already discussed), high energy management system 200 ( FIG. 2A to FIG. 2B , already discussed) and / or the high energy management system controller 300 ( Figure 3 , all or part of which has been discussed. Figure 5 Certain components are shown, but computing system 10 may include additional or multiple components connected in various ways. It should be understood that not all examples necessarily include Figure 5 . Computing system 10 includes one or more processors 22. In some examples, computing system 10 also includes an input / output (I / O) subsystem 24, a network interface 26, a memory 28, a data storage device 30, a user interface 32, and / or a sensor interface 34. Computing system 10 may also include a display 38. These components are coupled, connected, or otherwise in data communication via interconnect 36. In some examples, computing system 10 may interface with a separate display, such as, for example, a display installed in an aircraft as original equipment.

[0067] The processor 22 includes one or more processing devices, such as a microprocessor, a fixed application specific integrated circuit (ASIC) processor, a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a field programmable gate array (FPGA), a digital signal processor (DSP), etc., and associated circuits, logic and / or interfaces. The processor 22 may include or be connected to a memory (e.g., memory 28) storing executable instructions and / or data as needed or appropriate. The processor 22 executes such instructions to implement, control, operate, or interface with any device or feature of the high energy management system 100, the high energy management system controller 110, the high energy management system 200, and / or the high energy management system controller 300, and / or any device or feature of the high energy management system controller 300, and / or any device or feature of the high energy management system controller 110, the high energy management system 200, and / or any device or feature of the high energy management system controller 300, and / or any device or feature of the high energy management system controller 300, and / or any device or feature of the high energy management system 100, the high energy management system controller 110, the high energy management system 2 ... Figure 1A to Figure 1B , Figures 2A to 2B , Figure 3 and / or FIG. 4A to FIG. 4B The processor 22 may send or receive data from other devices (such as Figure 1A to Figure 1B , Figures 2A to 2B and / or Figure 3 The processor 22 may be a processor that can transmit, send or receive messages, requests, notifications, data, etc., using the device shown in the figure. The processor 22 may be embodied as any type of processor capable of performing the functions described herein. For example, the processor 22 may be embodied as a single-core or multi-core processor, a digital signal processor, a microcontroller, or other processor or processing / control circuit. The processor 22 may include embedded instructions (e.g., processor code).

[0068] I / O subsystem 24 includes circuits and / or components suitable for facilitating input / output operations with processor 22 , memory 28 , and other components of computing system 10 .

[0069] The network interface 26 comprises suitable logic, circuitry, and / or interfaces for sending and receiving data over one or more communication networks using one or more communication network protocols. The network interface 26 may operate under the control of the processor 22 and may send and receive data to / from one or more other devices (e.g., Figure 1A to Figure 1B , Figures 2A to 2B and / or Figure 3 ) to send / receive various requests and messages to any one or more devices shown in . Network interface 26 may include wired and / or wireless data communication capabilities; these capabilities may support data communications with wired and / or wireless communication networks (such as network 27), and also include the Internet, a wide area network (WAN), a local area network (LAN), a wireless personal area network, a wide area network, a cellular network, a telephone network, any other wired and / or wireless network for sending and receiving data signals, or any combination thereof (including, for example, a Wi-Fi network or a corporate LAN). Network interface 26 may support communication via a short-range wireless communication field (such as Bluetooth, near field communication (NFC), or radio frequency identification (RFID)). Examples of network interface 26 may include, but are not limited to, an antenna, a radio frequency transceiver, a wireless transceiver, a Bluetooth transceiver, an Ethernet port, a universal serial bus (USB) port, or any other device configured to send and receive data.

[0070] The memory 28 includes suitable logic, circuitry, and / or interfaces for storing executable instructions and / or data as necessary or appropriate to implement, control, operate, or interface with any device or feature of the high energy management system 100, the high energy management system controller 110, the high energy management system 200, and / or the high energy management system controller 300 when executed, and / or any device or feature of the high energy management system 100, the high energy management system controller 110, the high energy management system 200, and / or the high energy management system controller 30 ... any device or feature of the high energy management system controller 300, and Figure 1A to Figure 1B , Figures 2A to 2B , Figure 3 and / or FIG. 4A to FIG. 4B Memory 28 may be embodied as any type of volatile or non-volatile memory or data storage device capable of performing the functions described herein, and may include random access memory (RAM), read-only memory (ROM), write-once-read-many memory (e.g., EEPROM), removable storage drives, hard disk drives (HDDs), flash memory, solid-state memory, etc., and including any combination thereof. In operation, memory 28 may store various data and software used during operation of computing system 10, such as operating systems, applications, programs, libraries, and drivers. Memory 28 may be communicatively coupled to processor 22 directly or via I / O subsystem 24.

[0071] Data storage device 30 may include one or more devices of any type configured for short-term or long-term storage of data, such as memory devices and circuits, memory cards, hard drives, solid-state drives, non-volatile flash memory, or other data storage devices. Data storage device 30 may include or be configured as a database, such as a relational database or a non-relational database, or a combination of more than one database. In some examples, the database or other data storage device may be physically separated and / or remote from computing system 10, and / or may be located in another computing device, a database server, a cloud-based platform, or any storage device that communicates data with computing system 10.

[0072] The user interface 32 includes code for presenting information or screens on a display for a user (e.g., a user using a user device) and receiving input (including commands) from the user via an input device (e.g., a touch screen device). The user interface 32 may include a graphical user interface (GUI).

[0073] Sensor interface 34 includes circuitry and / or components suitable for facilitating the communication and / or exchange of data, commands, or signals between computing system 10 and one or more sensors, which may include one or more of sensors 122 and / or one or more of actuators 124 ( Figure 1B and Figure 2B , already discussed). The sensor interface 34 may cooperate with the network interface 26 to establish communications with one or more sensors.

[0074] The interconnect 36 includes any one or more separate physical buses, point-to-point connections, or both connected by appropriate bridges, adapters, or controllers. The interconnect 36 may include, for example, a system bus, a peripheral component interconnect (PCI) bus, a HyperTransport or Industry Standard Architecture bus, a Small Computer System Interface (SCSI) bus, a Universal Serial Bus (USB), an Inter-Integrated Circuit (I2C) bus, or an Institute of Electrical and Electronics Engineers (IEEE) Standard 694 bus (e.g., "FireWire"), or any other interconnect suitable for coupling or connecting components of the computing system 10.

[0075] Display 38 may be any type of device for presenting visual information, such as a computer monitor, a flat panel display, or a mobile device screen, and may include a liquid crystal display (LCD), a light emitting diode (LED) display, a plasma panel, or a cathode ray tube display, etc. Display 38 may include a display interface for communicating with the display. In some examples, display 38 may include a display interface for communicating with a display external to computing system 10 (e.g., a user device).

[0076] In some examples, one or more of the illustrative components of computing system 10 may be incorporated (in whole or in part) within another component or otherwise form a part of another component. For example, memory 28 or portions thereof may be incorporated within processor 22. As another example, user interface 32 may be incorporated within code in processor 22 and / or memory 28. In some examples, computing system 10 may be embodied as, but not limited to, a mobile computing device, a smart phone, a wearable computing device, an Internet of Things device, a laptop computer, a tablet computer, a notebook computer, a computer, a workstation, a server, a multiprocessor system, and / or a consumer electronic device. In some examples, computing system 10 or portions thereof are implemented in one or more modules as a set of logic instructions stored in at least one non-transitory machine or computer-readable storage medium, such as a random access memory (RAM), a read-only memory (ROM), a programmable ROM (PROM), firmware, flash memory, etc., stored in configurable logic, such as, for example, a programmable logic array (PLA), a field programmable gate array (FPGA), a complex programmable logic device (CPLD), stored in fixed-function logic hardware using circuit technology, such as, for example, an application-specific integrated circuit (ASIC), complementary metal oxide semiconductor (CMOS), or transistor-transistor logic (TTL) technology, or any combination thereof.

[0077] Examples of each of the above systems, devices, components, features and / or methods (including high energy management system 100, high energy management system controller 110, high energy management system 200, aircraft interface module 210, high energy management system controller 300, method 400 and / or any other system components) can be implemented in hardware, software or any suitable combination thereof. For example, hardware implementations may include configurable logic, fixed function logic or any combination thereof. Examples of configurable logic include appropriately configured PLAs, FPGAs, CPLDs, and general purpose microprocessors. Examples of fixed function logic include appropriately configured ASICs, combinational logic circuits, and sequential logic circuits. Configurable or fixed function logic can be implemented with CMOS logic circuits, TTL logic circuits, or other circuits.

[0078] Alternatively or additionally, all or part of the aforementioned systems, devices, components, features and / or methods may be implemented in one or more modules as a program or set of logic instructions stored in a machine or computer readable storage medium (such as RAM, ROM, PROM, firmware, flash memory, etc.) to be executed by a processor or computing device. For example, the computer program code for performing the operation of the component may be written in any combination of programming languages ​​applicable / appropriate to one or more operating systems (OS), including object-oriented programming languages ​​(such as Java, JavaScript, Python, C#, C++, Perl, Smalltalk, etc.) and conventional procedural programming languages ​​(such as "C" programming language or similar programming languages).

[0079] Additional notes and examples:

[0080] Furthermore, the present disclosure includes additional examples as detailed in the following clauses.

[0081] Clause M1. A method of controlling a high energy management system, the method comprising:

[0082] receiving sensor data from a plurality of high energy (HE) systems, wherein each of the plurality of HE systems is located in an aircraft;

[0083] determining a current state of each of the plurality of HE systems based on the sensor data;

[0084] determining a target state for each of the plurality of HE systems based on a current state of each of the plurality of HE systems and a set of HE system rules;

[0085] Based on the target state of each of the plurality of HE systems, one or more control actions are automatically generated to achieve control of one or more of the plurality of HE systems.

[0086] Clause M2. The method of clause M1, wherein the HE system rule set comprises:

[0087] a rule specifying conditions for activating or deactivating a HE system in the plurality of HE systems; and

[0088] One or more of the following:

[0089] Rules specifying which of the multiple HE systems can be active with respect to each other;

[0090] a rule specifying which high energy system of the plurality of HE systems must interact with another high energy system of the plurality of HE systems; or

[0091] Rules that specify which high energy systems in multiple HE systems cannot be active with respect to each other.

[0092] Clause M3. The method of clause M1 or M2, wherein the rule specifying conditions for activating or deactivating a HE system in the plurality of HE systems comprises one or more of the following:

[0093] rules that specify an order for activating or deactivating subsets of a plurality of HE systems; or

[0094] Rules specifying timing requirements related to activating or deactivating a HE system in a plurality of HE systems.

[0095] Clause M4. A method according to any one of clauses M1 to M3, further comprising:

[0096] receiving a schedule of tasks to be performed on the aircraft;

[0097] Wherein, determining the target state of each HE system in the plurality of HE systems is also based on the scheduling of tasks.

[0098] Clause M5. A method as described in any of clauses M1 to M4, wherein the rule specifying the conditions for activating or deactivating the HE system in the plurality of HE systems is based on one or more identified tasks.

[0099] Clause M6. The method of any one of clauses M1 to M5, wherein active control of the plurality of HE systems is conditioned upon determining that the aircraft is in a ground state.

[0100] Clause M7. A method according to any one of clauses M1 to M6, further comprising:

[0101] An alert is sent to a user equipment, wherein the alert is based on one or more of: the target state of one or more HE systems of the plurality of HE systems, the one or more control actions, or conflicting activation or deactivation of HE systems.

[0102] Clause M8. A method according to any one of clauses M1 to M7, further comprising:

[0103] receiving a command related to one of the plurality of HE systems from a user equipment; and

[0104] A control action of the one or more control actions is modified based on the command.

[0105] Clause M9. A method according to any one of clauses M1 to M8, further comprising:

[0106] Information about the current status of multiple HE systems is provided for display on user equipment.

[0107] Clause M10. A method according to any one of clauses M1 to M9, wherein the plurality of HE systems includes one or more HE systems selected from the group consisting of: an electrical system, a hydraulic system, a propulsion system, a cockpit power system, a payload and coordinate system, or a fuel system.

[0108] Clause S1. A high energy management system controller, the high energy management system controller comprising:

[0109] Processor; and

[0110] A memory coupled to the processor, the memory comprising instructions that, when executed by the processor, cause the high energy management system controller to perform operations comprising:

[0111] receiving sensor data from a plurality of high energy (HE) systems, wherein each of the plurality of HE systems is located in an aircraft;

[0112] determining a current state of each of the plurality of HE systems based on the sensor data;

[0113] determining a target state for each of the plurality of HE systems based on a current state of each of the plurality of HE systems and a set of HE system rules;

[0114] Based on the target state of each of the plurality of HE systems, one or more control actions are automatically generated to achieve control of one or more of the plurality of HE systems.

[0115] Clause S2. The high energy management system controller of clause S1, wherein the HE system rule set comprises:

[0116] a rule specifying conditions for activating or deactivating a HE system in the plurality of HE systems; and

[0117] One or more of the following:

[0118] Rules that specify which of the multiple HE systems can act on each other;

[0119] a rule specifying which one of the plurality of HE systems must be active with another one of the plurality of HE systems; or

[0120] Rules that specify which of the multiple HE systems cannot be active with respect to each other.

[0121] Clause S3. The high energy management system controller of clause S1 or S2, wherein the rule specifying conditions for activating or deactivating a HE system in the plurality of HE systems comprises one or more of the following:

[0122] rules that specify an order for activating or deactivating subsets of a plurality of HE systems; or

[0123] Rules specifying timing requirements related to activating or deactivating a HE system in a plurality of HE systems.

[0124] Clause S4. The high energy management system controller of any one of clauses S1 to S3, wherein the instructions, when executed, cause the high energy management system controller to perform further operations, the further operations comprising:

[0125] receiving a dispatch of a mission to be performed on the aircraft;

[0126] Wherein, determining the target state of each HE system in the plurality of HE systems is also based on the scheduling of tasks.

[0127] Clause S5. The high energy management system controller of any of clauses S1 to S4, wherein the rule specifying conditions for activating or deactivating the HE system of the plurality of HE systems is based on one or more identified tasks.

[0128] Clause S6. A high energy management system controller as described in any one of clauses S1 to S5, wherein active control of the plurality of HE systems by the high energy management system controller is conditioned upon determining that the aircraft is in a ground state.

[0129] Clause S7. The high energy management system controller of any one of clauses S1 to S6, wherein the instructions, when executed, cause the high energy management system controller to perform further operations, the further operations comprising:

[0130] An alert is sent to the user equipment, wherein the alert is based on one or more of: a target state of one or more HE systems among the plurality of HE systems, one or more control actions, and conflicting activation or deactivation of the HE systems.

[0131] Clause S8. The high energy management system controller of any one of clauses S1 to S7, wherein the instructions, when executed, cause the high energy management system controller to perform further operations, the further operations comprising:

[0132] receiving a command related to one of the plurality of HE systems from a user equipment; and

[0133] A control action of the one or more control actions is modified based on the command.

[0134] Clause S9. The high energy management system controller of any one of clauses S1 to S8, wherein the instructions, when executed, cause the high energy management system controller to perform further operations, the further operations comprising:

[0135] Information about the current status of multiple HE systems is provided for display on user equipment.

[0136] Clause S10. A high energy management system controller according to any one of clauses S1 to S9, wherein the plurality of HE systems include one or more HE systems selected from the group consisting of: an electrical system, a hydraulic system, a propulsion system, a cockpit power system, a payload and coordination system, or a fuel system.

[0137] Clause C1. At least one computer-readable storage medium comprising instructions that, when executed by a processor, cause the high energy management system to perform operations comprising:

[0138] receiving sensor data from a plurality of high energy (HE) systems, wherein each of the plurality of HE systems is located in an aircraft;

[0139] determining a current state of each of the plurality of HE systems based on the sensor data;

[0140] determining a target state for each of the plurality of HE systems based on a current state of each of the plurality of HE systems and a set of HE system rules;

[0141] Based on the target state of each of the plurality of HE systems, one or more control actions are automatically generated to achieve control of one or more of the plurality of HE systems.

[0142] Clause C2. At least one computer-readable storage medium as described in clause C1, wherein the set of HE system rules comprises:

[0143] a rule specifying conditions for activating or deactivating a HE system in the plurality of HE systems; and

[0144] One or more of the following:

[0145] Rules that specify which of the multiple HE systems can act on each other;

[0146] a rule specifying which one of the plurality of HE systems must be active with another one of the plurality of HE systems; or

[0147] Rules that specify which of the multiple HE systems cannot be active with respect to each other.

[0148] Clause C3. At least one computer-readable storage medium of clause C1 or C2, wherein the rule specifying conditions for activating or deactivating a HE system in the plurality of HE systems comprises one or more of:

[0149] rules that specify an order for activating or deactivating subsets of a plurality of HE systems; or

[0150] Rules specifying timing requirements related to activating or deactivating a HE system in a plurality of HE systems.

[0151] Clause C4. At least one computer-readable storage medium according to any one of clauses C1 to C3, wherein the instructions, when executed, cause the high energy management system to perform further operations, the further operations comprising:

[0152] receiving a dispatch of a mission to be performed on the aircraft;

[0153] Wherein, determining the target state of each HE system in the plurality of HE systems is also based on the scheduling of tasks.

[0154] Clause C5. The at least one computer-readable storage medium of any of clauses C1 to C4, wherein a rule specifying conditions for activating or deactivating a HE system in the plurality of HE systems is based on one or more identified tasks.

[0155] Clause C6. At least one computer-readable storage medium as described in any of clauses C1 to C5, wherein active control of the plurality of HE systems by the high energy management system controller is conditioned upon determining that the aircraft is in a ground state.

[0156] Clause C7. At least one computer-readable storage medium according to any one of clauses C1 to C6, wherein the instructions, when executed, cause the high energy management system to perform further operations, the further operations comprising:

[0157] An alert is sent to the user equipment, wherein the alert is based on one or more of: a target state of one or more of the plurality of HE systems, one or more control actions, or conflicting activation or deactivation of the HE systems.

[0158] Clause C8. At least one computer-readable storage medium according to any one of clauses C1 to C7, wherein the instructions, when executed, cause the high energy management system to perform further operations, the further operations comprising:

[0159] receiving a command related to one of the plurality of HE systems from a user equipment; and

[0160] A control action of the one or more control actions is modified based on the command.

[0161] Clause C9. At least one computer-readable storage medium according to any one of clauses C1 to C8, wherein the instructions, when executed, cause the high energy management system to perform further operations, the further operations comprising:

[0162] Information about the current status of multiple HE systems is provided for display on user equipment.

[0163] Clause C10. At least one computer-readable storage medium according to any one of clauses C1 to C9, wherein the plurality of HE systems include one or more HE systems selected from the group consisting of: an electrical system, a hydraulic system, a propulsion system, a cockpit power system, a payload and coordination system, or a fuel system.

[0164] Clause A1. An apparatus comprising means for performing the method of any of clauses M1 to M10.

[0165] Examples are applicable to all types of semiconductor integrated circuit ("IC") chips. Examples of these IC chips include, but are not limited to, processors, controllers, chipset components, programmable logic arrays (PLA), memory chips, network chips, systems on chips (SoC), solid-state drives (SSD) / NAND drive controller ASICs, etc. In addition, in some of the drawings, signal conductors are represented by lines. Some may be different to indicate more constituent signal paths, have digital labels to indicate the number of constituent signal paths, and / or have arrows at one or more ends to indicate the direction of the main information flow. However, this should not be interpreted in a limiting manner. On the contrary, such additional details may be used in conjunction with one or more exemplary examples to facilitate easier understanding of the circuit. With or without additional information, any signal line represented may actually include one or more signals that can travel in multiple directions, and may be implemented with any suitable type of signal scheme, for example, digital or analog lines implemented with differential pairs, fiber optic lines, and / or single-ended lines.

[0166] Example size / model / value / range can be given, but the example is not limited thereto. As manufacturing technology (e.g., lithography) matures over time, it is expected that smaller-sized devices can be manufactured. In addition, in order to simplify the description and discussion, known power / ground connections to IC chips and other components may be shown or not shown in the drawings, so as not to obscure certain aspects of the example. In addition, the arrangement can be shown in block diagram form, so as to avoid obscuring the example, and also considering the fact that the details of the implementation of such block diagram arrangements are highly dependent on the platform in which the example is to be implemented, that is, such details should be within the scope of those skilled in the art. In the case of elaborating specific details (e.g., circuits) in order to describe exemplary examples, it should be apparent to those skilled in the art that examples can be practiced without these specific details or with variations of these specific details. Therefore, this description is considered to be illustrative rather than restrictive.

[0167] The term "coupled" may be used herein to refer to any type of direct or indirect relationship between the components in question, and may apply to electrical, mechanical, fluid, optical, electromagnetic, electromechanical, or other connections, including logical connections via intermediate components (e.g., device A may be coupled to device C via device B). In addition, the terms "first," "second," etc., may be used herein merely to facilitate discussion and have no specific temporal or time meaning unless otherwise specified.

[0168] As used in this application and in the claims, a list of items joined by the term "one or more of" may mean any combination of the listed terms. For example, the phrase "one or more of A, B, or C" may mean A, B, C; A and B; A and C; B and C; or A, B, and C.

[0169] Those skilled in the art will appreciate from the foregoing description that the broad techniques of the examples can be implemented in a variety of forms. Therefore, while the examples have been described in conjunction with specific examples thereof, the true scope of the examples should not be so limited, as other modifications will become apparent to those skilled in the art upon studying the drawings, the specification, and the appended claims.

Claims

1. A method (400) for controlling a high energy management system (100), the method comprising: receiving sensor data (305) from a plurality of high energy systems (120), wherein each of the plurality of high energy systems is located in an aircraft; determining a current state of each of the plurality of high energy systems (120) based on the sensor data (305); determining a target state for each of the plurality of high-energy systems (120) based on the current state of each of the plurality of high-energy systems and a set of high-energy system rules (330); and Based on the target state of each of the plurality of high-energy systems, one or more control actions (340) are automatically generated to achieve control of one or more high-energy systems among the plurality of high-energy systems (120).

2. The method (400) of claim 1, wherein: The set of high energy system rules (330) includes: rules specifying conditions for activating or deactivating a high-energy system in the plurality of high-energy systems (120); and One or more of the following: rules specifying which high-energy systems of the plurality of high-energy systems (120) can be active with respect to each other; rules specifying which high-energy system of the plurality of high-energy systems (120) must be active with another high-energy system of the plurality of high-energy systems (120); and Rules specifying which high-energy systems of the plurality of high-energy systems (120) cannot interact with each other.

3. The method (400) of claim 2, wherein: The rules specifying conditions for activating or deactivating a high-energy system in the plurality of high-energy systems (120) include one or more of the following: rules specifying an order for activating or deactivating subsets of the plurality of high-energy systems (120); and Rules specifying timing requirements associated with activating or deactivating a high-energy system in the plurality of high-energy systems (120).

4. The method (400) according to claim 3, further comprising: receiving a schedule of tasks to be performed on the aircraft (130); Wherein, determining the target state of each of the plurality of high-energy systems (120) is also based on the scheduling (130) of the tasks.

5. The method (400) of claim 4, wherein: The rules specifying conditions for activating or deactivating a high-energy system in the plurality of high-energy systems (120) are based on one or more identified tasks.

6. The method (400) of claim 1, wherein: The active control of the plurality of high energy systems (120) is conditioned upon determining that the aircraft is in a ground state.

7. The method (400) of claim 1, further comprising: An alert (314) is sent to a user device (140), wherein the alert (314) is based on one or more of the following: the target state of one or more high-energy systems in the plurality of high-energy systems (120), the one or more control actions (340), and the activation or deactivation of conflicts of the high-energy systems (120).

8. The method (400) of claim 1, further comprising: receiving a command (322) related to a high-energy system in the plurality of high-energy systems (120) from a user device (140); as well as A control action of the one or more control actions (340) is modified based on the command (322).

9. A high energy management system controller (300), the high energy management system controller comprising: Processor (22); as well as a memory (28) coupled to the processor, the memory comprising instructions that, when executed by the processor (22), cause the high energy management system controller (300) to perform operations comprising: receiving sensor data (305) from a plurality of high energy systems (120), wherein each of the plurality of high energy systems is located in an aircraft; determining a current state of each of the plurality of high energy systems (120) based on the sensor data (305); determining a target state for each of the plurality of high-energy systems (120) based on the current state of each of the plurality of high-energy systems and a set of high-energy system rules (330); and Based on the target state of each of the plurality of high-energy systems, one or more control actions (340) are automatically generated to achieve control of one or more high-energy systems among the plurality of high-energy systems (120).

10. At least one computer-readable storage medium (28) comprising instructions that, when executed by a processor (22), cause an energy management system controller (300) to perform operations comprising: receiving sensor data (305) from a plurality of high energy systems (120), wherein each of the plurality of high energy systems is located in an aircraft; determining a current state of each of the plurality of high energy systems (120) based on the sensor data (305); determining a target state for each of the plurality of high-energy systems (120) based on the current state of each of the plurality of high-energy systems and a set of high-energy system rules (330); and Based on the target state of each of the plurality of high-energy systems, one or more control actions (340) are automatically generated to achieve control of one or more high-energy systems among the plurality of high-energy systems (120).

Images