ASSEMBLY CONTROL WITH AUTHENTICATION OF CONTROL SYSTEM

Abstract

An embedded processing system includes processing circuitry, a memory system, and a plurality of attached modular components. The attached modular components are each provided with a nameplate including at least part and serial number data. The processing circuitry is operable to receive the nameplate information from each of the attached modular components and compare the received nameplate information with stored nameplate information for the particular attached modular component. The processing circuitry is operable to communicate with the attached modular component if the received nameplate information matches the stored nameplate information and identify a fault if the received nameplate information conflicts with the stored nameplate information. A method and an assembly are also disclosed.

Claims

1. An embedded processing system comprising: processing circuitry; a memory system; a plurality of attached modular components, the attached modular components each being provided with a nameplate including at least part and serial number data; and the processing circuitry being operable to receive the nameplate information from each of the attached modular components and compare the received nameplate information with stored nameplate information for the particular attached modular component, and the processing circuitry being operable to communicate with the attached modular component if the received nameplate information matches the stored nameplate information and identify a fault if the received nameplate information conflicts with the stored nameplate information.

2. The system as set forth in claim 1, wherein the nameplate information is encrypted.

3. The system as set forth in claim 2, wherein the attached modular components include modules within the embedded processing system communicating outwardly to effectors on a controlled system, and receiving sensed values from sensors associated with the controlled system.

4. The system as set forth in claim 3, wherein the attached components also include nodes being control systems for auxiliary devices on the controlled system, and the nodes communicating into the embedded processing system, but being located outwardly of the embedded processing system.

5. The system as set forth in claim 3, wherein at least one of the attached modular components is manufactured by a supplier other than a manufacturer of the controlled system.

6. The system as set forth in claim 1, wherein if a fault is detected on one of said attached modular component, a control algorithm is updated to report to all other attached modular components on a reconfiguration that does not rely upon the fault detected attached modular component.

7. The system as set forth in claim 1, wherein at least one of the attached modular components is manufactured by a supplier other than a manufacturer of a controlled system.

8. A method comprising: attaching a plurality of attached modular components to an embedded processing system, the attached modular components each being provided with a nameplate including at least part and serial number data; and the embedded processing system receiving the nameplate information from each of the attached modular components and comparing the received nameplate information with stored nameplate information for the particular attached component, and communicating with the attached modular component if the received nameplate information matches the stored nameplate information and identifying a fault if the received nameplate information conflicts with the stored nameplate information.

9. The method as set forth in claim 8, wherein the nameplate information is encrypted.

10. The method as set forth in claim 9, wherein the attached modular components include modules within the embedded processing system communicating outwardly to effectors on a controlled system, and receiving sensed values from sensors associated with the controlled system.

11. The method as set forth in claim 10, wherein the attached components also include nodes being control systems for auxiliary devices on the controlled system, and the nodes communicating into the embedded processing system, but being located outwardly of the embedded processing system.

12. The method as set forth in claim 10, wherein at least one of the attached is manufactured by a supplier other than a manufacturer of the controlled system.

13. The method as set forth in claim 8, wherein if a fault is detected on one of said attached modular component, a control algorithm is updated to report to all other attached modular components on a reconfiguration that does not rely upon the fault detected attached component.

14. The method as set forth in claim 8, wherein at least one of the attached modular components is manufactured by a supplier other than a manufacturer of a controlled system.

15. An assembly comprising: a plurality of effectors and sensors and an embedded processing system; the embedded processing system having: processing circuitry; a memory system; a plurality of attached modular components, the attached modular components each being provided with an encrypted nameplate including at least part and serial number data; and the processing circuitry being operable to receive the nameplate information from each of the attached modular components and compare the received nameplate information with stored nameplate information for the particular attached modular component, and the processing circuitry being operable to communicate with the attached modular component if the received nameplate information matches the stored nameplate information and identify a fault if the received nameplate information conflicts with the stored nameplate information.

16. The assembly as set forth in claim 15, wherein the attached modular components include modules within the embedded processing system communicating outwardly to the effectors, and receiving sensed values from the sensors.

17. The assembly as set forth in claim 16, wherein the attached components include nodes being control systems for auxiliary devices on a controlled system, and the nodes communicating into the embedded processing system, but being located outwardly of the embedded processing system.

18. The assembly as set forth in claim 15, wherein at least one of the attached modular components is manufactured by a supplier other than a manufacturer of the controlled system.

19. The assembly as set forth in claim 15, wherein if a fault is detected on one of said attached modular component, a control algorithm is updated to report to all other said attached modular components on a reconfiguration that does not rely upon the fault detected attached modular component.

20. The assembly set forth in claim 15, wherein the assembly is an aircraft and the embedded processing system controls a gas turbine engine for the aircraft.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0026] FIG. 1A schematically shows a gas turbine engine on an aircraft.

[0027] FIG. 1B is a block diagram of a control system.

[0028] FIG. 2 shows an enrollment step for modules and/or nodes.

[0029] FIG. 3A shows an occurrence wherein there is a failure or a fault detection.

[0030] FIG. 3B is a flowchart showing the response to a detected fault.

[0031] FIG. 4 shows a nameplate storage system.

[0032] FIG. 5 is a flowchart of an overall authentication system.

DETAILED DESCRIPTION

[0033] FIG. 1A schematically shows an assembly 90. In a disclosed embodiment assembly 90 may be an aircraft. A gas turbine engine 91 is shown as associated with the aircraft 90. Gas turbine engine 91 has a fan 96, a compressor section 98, a combustor section 97 and a turbine section 99. It should be understood that this is a highly schematic description. While a gas turbine engine and aircraft are disclosed as the assemblies and the associated control, other assemblies and controls may benefit from this disclosure.

[0034] As shown, an embedded processing system 102 communicates with a control 94 on the aircraft 90. The embedded processing system 102 may be a full authority digital electronic controller or FADEC for engine 91.

[0035] FIG. 1B shows details of a system 100 including the embedded processing system 102 and the controlled system 104. Here, the controlled system 104 may include systems on the gas turbine engine of FIG. 1A.

[0036] The FIG. 1B system includes the embedded processing system 102 and a controlled system. The controlled system 104 can be any type of physical system that includes one or more effectors 106 controlled by one or more effector commands 108. The effector commands 108 are received from a module 140 associated with the embedded processing system 100.

[0037] Examples of effectors can include one or more motors, solenoids, valves, relays, pumps, heaters and/or other such actuation control components.

[0038] A plurality of sensors 110 can capture state data associated with the controlled system 104 and provide sensed values 112 as feedback to a module 142 in the embedded processing system 102 to enable closed-loop control of the controlled system 104 according to one or more control laws.

[0039] Examples of the sensors can include one or more temperature sensors, pressure sensors, strain gauges, level sensors, accelerometers, rate sensors, and the like.

[0040] While the controlled assembly is disclosed as a gas turbine engine, it can be other types of engines, a vehicle, a heating ventilating and air conditioning (HVAC) system, an elevator system, industrial machinery, or the like.

[0041] For purposes of explanation, embodiments are primarily described with respect to a gas turbine engine system for an aircraft 90 as the controlled system, and in particular, the gas turbine engine 91.

[0042] In the FIG. 1B example, the embedded processing system 102 includes processing circuitry 114 and a memory system 116 configured to store a plurality of configuration items, where at least one of the configuration items includes a sequence of computer executable instructions for execution by the processing circuitry 114. Types of configuration items can include data, such as constants, configurable data, and/or fault data. Examples of computer executable instructions can include software, operating system software, and/or application software. The executable instructions can be stored or organized in any manner and at any level of abstraction, such as in connection with controlling and/or monitoring operation of the controlled system 104. The processing circuitry can be any type or combination of central processing unit (CPU). including one or more of: a microprocessor, a digital signal processor, a microcontroller, an application specific integrated circuit, a field programmable gate array, or the like.

[0043] In embodiments, the memory system may include volatile memory 118 such as random access memory, and non-volatile memory 120, such as flash memory, read only memory, and/or other electronic, optical, magnetic, or any other computer readable medium onto which is stored data and algorithms in a non-transitory form.

[0044] The embedded processing system 102 can also include one or more of an input/output interface 122, a communication interface 124, a reprogramming control 126, and/or other elements.

[0045] The input/output interface 122 can include support circuitry for interfacing with the effectors 106 and sensors 110, such as filters, amplifiers, digital-to-analog converters, analog-to-digital converters, and other such circuits to support digital and/or analog interfaces. Further, the input/output interface 122 can receive or output signals to/from other sources. As one example, discrete inputs 128 can be input to the input/output interface to establish an operating mode of the embedded processing system 102, or to trigger actions by the embedded processing system 102.

[0046] A reset signal 130 may also be internally induced as a result of a loss of power detected by power conditioning circuitry, and by specific hardware or software direction. The communication interface 124 can be coupled to a communication system 132, which can include one or more direct or network communication links to systems such as a reprogramming system 134, a data repository 136, or another system. The communication system 132 may also communicate with the control 94 on the associated aircraft 90.

[0047] The reprogramming system 134 can be any type of computer system operable to load new/updated configuration items to the embedded processing system 102 for storage in the memory system 116. The reprogramming system 134 can interface to the communication system 132 to a wired, wireless, optical, or magnetic coupling. The data repository 136 can serve as a data source for updating the memory system 116, for instance, with control system data, or as a data sync to offload and clear data from the memory systems, such as fault data, history data, and the like.

[0048] As also shown, systems 145 and 148 may have control nodes 144 and 146 that communicate to the embedded processing system 102. As an example, the system 145 may be an anti-ice system.

[0049] Other examples of modules or nodes may include additional wired or wireless communication interfaces or input/output devices that are remote to optimize environmental considerations such as envelope, weight, thermal, and/or power.

[0050] In general, a module is a control system that is within the embedded processing system 102, whereas a node is outside the system 102, but communicating with it. Modular processing systems must be able to be updated to have modules and/or nodes replaced from time to time, and it would be desirable to be able to ensure the propriety and integrity of the replaced modules and controls. That is, detect any counterfeits or incorrect modules/nodes. In addition, it would be desirable to identify a fault with any of the modules and/or nodes.

[0051] As shown in FIG. 2, in an enrollment process, during production modules 140-142 and nodes 140-146 are provided with an enrollment algorithm including unique cryptographic information provided to a supplier of the module and/or node from the manufacturer of the embedded processing system 102, the control system 104, or the vehicle 90. Thus, each of the modules and nodes (collectively connected components) has a nameplate, or configuration data captured and encrypted. Such data desirably contains part and serial number data, and is digitally signed, and optionally encrypted.

[0052] As shown in FIG. 3A, the processing circuitry 114 receives the nameplate information from each of the modules and nodes. If any module or node fails authentication, or does not provide appropriate information, a fault detection process is entered.

[0053] Thus, as shown in FIG. 3B, at step 152 the system asks if there is a loss of any nodule and/or node. If so, a fault is confirmed and isolated and a system reset initiated at step 154. At step 156, all of the nodes and modules must be re-enrolled after the system reset, such as authenticating their nameplate information again.

[0054] At step 158, revalidated configuration data is utilized to meet supply chain risk management intent.

[0055] Supply chain risk management is utilized to identify against counterfeit module and/or node insert. Further, it is utilized to protect against physical tamper attacks. In step 160, configuration status/information is reported.

[0056] As an example, in step 162, there may be a limit to the number of recovery recycles.

[0057] Strict controls are utilized on the erasure of any encrypted data at step 164.

[0058] If the faulted module and/or node does not come back on line within the limit of recovery cycles, then the processing circuitry 114 is provided with new information as to the current operating state or the controlled system 104 and embedded processing system 102. As an example, if the fault occurs during a flight of the associated aircraft, the flight must be completed. Thus, by updating the processing circuitry to accommodate the controls to best affect operation without the faulted attached components the aircraft can still fly.

[0059] In step 166, a system key is generated using re-enrollment data and owner unique cryptographic information.

[0060] Each attached component updates its ledger to include the current configuration block.

[0061] FIG. 4 shows a plurality of nameplates 151A, 151B, and 151C for the modules and nodes. Such are encrypted at first step 170 and the encrypted nameplate is encrypted at a second step 171. The double encrypted information is stored in the non-volatile memory 120. This re-enrollment data is solely utilized for accommodation, step 156, in the event of a module/node loss of communication failure.

[0062] A flowchart for overall operation of the system is shown in FIG. 5. At step 172, the embedded processing system 102 receives the nameplate, or configuration data from each attached component at initialization or in real-time.

[0063] At step 174, each nameplate is authenticated to ensure appropriate configuration data.

[0064] At step 176, the system asks if the data matches the stored configuration nameplate information. If not, then the particular attached component is identified as a faulted component at step 178. The system may then reconfigure as explained with regard to FIG. 3B.

[0065] If step 176 is answered in the affirmative, the flowchart moves to step 180. After 178, the flowchart also returns to step 180. At 180, the configuration data is reported to a supply chain risk management system. As an example, this could be the control 94 on the associated aircraft 90.

[0066] At 182, the system generates cryptographic system keys with owner unique cryptographic information.

[0067] Although embodiments of this disclosure have been shown, a worker of ordinary skill in this art would recognize that modifications would come within the scope of this disclosure. For that reason, the following claims should be studied to determine the true scope and content of this disclosure.