Method and system for connecting a controller for a machine to a higher-level IT system

• US 9,787,682 B2
• Filed: 09/26/2013
• Issued: 10/10/2017
• Est. Priority Date: 09/27/2012
• Status: Active Grant

• Current Assignee: Siemens AG
• Original Assignee: Siemens AG
• Inventors: Birzer, Johannes, Ordenewitz, Rainer
• Primary Examiner(s): Shiferaw, Eleni
• Assistant Examiner(s): Lapian, Alexander
• Application Number:
  US14/038,228
• Publication Number:
  US 20140090017A1
• Time in Patent Office: 1,475 Days
• CPC Class Codes: G06F 21/56 Computer malware detection or handling, e.g. anti-virus arrangements
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Abstract

In a method for securely connecting a controller for a machine or plant to a higher-level IT system, an integration layer is provided between the controller and the IT system, a controller image of the controller is generated in the integration layer, and the controller image is accessed from the IT system. The IT system thus always accesses the controller image rather than directly the controller. This prevents malware from gaining access to the controller e.g. via a network.

Claims

1. A method for connecting at least one controller for a machine or plant to a higher-level IT system in a manufacturing environment, comprising:

providing a integration layer,

providing a controller image of the controller in the integration layer, said controller image having data describing a current state of the controller using parameters monitored by the higher-level IT system, wherein the integration layer comprises a configuration file defining characteristics of the controller image, said parameters including incoming sensor signals to the controller or outgoing actuator signals from the controller and being composed of a combination of a sum of the same or other parameters,

accessing the controller image of the controller in the integration layer from the higher-level IT system,

configuring the controller to initiate all communication with the integration layer and the controller so as to be invisible to the higher-level IT system in the computer network,

prior to transmitting a controller-relevant data or data derived from the controller relevant data to the integration layer, filtering the controller relevant data or transforming the controller-relevant data into a generic data model, and

back-transforming the controller-relevant data transmitted to the integration layer into a proprietary data model prior to forwarding the controller-relevant data to the integration layer,

wherein the controller image is accessed in the integration layer via a Controller Data Access (CDA) interface, wherein the configuration file is accessed via a Controller data Configuration (CDC) interface, and wherein a complete separation is provided between a data transmission from the integration layer to the higher-level IT system via the Controller Data Access interface and a data transmission from the higher-level IT system to the integration layer via the Controller Data Configuration interface.

2. The method of claim 1, wherein the integration layer is provided on at least one of a standard hardware and software platform.

8. The method of claim 1, wherein the controller image in the integration layer is a mirror image of the controller image communicated to the integration layer, further comprising the step of deriving data used in the controller image using a combination of parameters monitored by the controller.

12. The method of claim 1, wherein said controller retrieves configuration data provided by the higher-level IT system to the integration layer from the integration layer.

3. A system for connecting at least one controller for a machine or plant to a higher-level IT system in a manufacturing environment, comprising:

a controller,

a higher-level IT system,

a hardware integration layer connected between the controller and the IT system, and

an image of the controller in said integration layer, said controller image having data describing a current state of the controller using parameters, monitored by the higher-level IT system, wherein the integration layer comprises a configuration file defining characteristics of the controller image, said parameters including incoming sensor signals to the controller or outgoing actuator signals from the controller and being composed of a combination of a sum of the same or other parameters, said controller being configured to initiate all communication between the integration layer and the controller so as to be invisible to the higher-level IT system in the computer network, wherein prior to transmitting a controller-relevant data or data derived from the controller relevant data to the integration layer the controller relevant data is filtered or transformed into a generic data model and back-transformed into a proprietary data model prior to being forwarded to the integration layer, and

a Controller Data Access (CDA) interface for accessing the controller image and a Controller Data Configuration (CDC) interface for accessing the configuration file, wherein a complete separation is performed between a data transmission from the integration layer to the higher-level IT system via the Controller Data Access interface and a data transmission from the higher-level IT system to the integration layer via the Controller Data Configuration interface.

4. The system of claim 3, wherein the integration layer is provided on at least one of a standard hardware and a software platform.

5. The system of claim 3, wherein the controller comprises a memory for accumulating controller-relevant data.

6. The system of claim 3, wherein the controller comprises filtering and transformation unit for filtering a controller-relevant data collected by the controller or transforming the controller-relevant data into a generic data model.

7. The system of claim 6, wherein the integration layer comprises a transformation unit which back-transforms the data stored in form of a generic data model into data stored in form of a controller-specific data model.

9. The system of claim 3, wherein the controller image in the integration layer is a mirror image of the controller image communicated to the integration layer from the controller, further comprising:

data in the controller image communicated to the integration layer from the controller derived using a combination of parameters monitored by the controller.

10. The system of claim 3, further comprising a proxy server connected to communicate a controller image to the integration layer.

13. The system of claim 3, wherein said controller retrieves configuration data provided by the higher-level IT system to the integration layer from the integration layer.

11. Apparatus for connecting at least one controller for a machine or plant to a higher-level IT system in a manufacturing environment, comprising:

a hardware integration layer adapted to be connected between the controller and the IT system, and

an image of the controller adapted to be provided in said integration said integration layer, said controller image having data describing a current state of the controller using parameters, monitored by the higher-level IT system, wherein the integration layer comprises a configuration file defining characteristics of the controller image, said parameters including incoming sensor signals to the controller or outgoing actuator signals from the controller and being composed of a combination of a sum of the, same or other parameters, wherein the controller is configured to initiate all communication between it and the integration layer so as to be invisible in a computer network, the higher-level IT system accessing data describing a current state of the controller in the image of the controller in said integration layer, wherein prior to transmitting a controller-relevant data or data derived from the controller relevant data to the integration layer the controller relevant data is filtered or transformed into a generic data model and back-transformed into a proprietary data model prior to being forwarded to the integration layer, and

a Controller Data Access (CDA) interface for accessing the controller image and a Controller Data Configuration (CDC) interface for accessing the configuration file, wherein a complete separation is performed between a data transmission from the integration layer to the higher-level IT system via the Controller Data Access interface and a data transmission from the higher-level IT system to the integration layer via the Controller Data Configuration interface.

14. The apparatus of claim 11, wherein said controller retrieves configuration data provided by the higher-level IT system to the integration layer from the integration layer.