Management and update system for automation devices connected to OT network of automation plant

Through the centralized management and update system of device management and update user units, the independence and security problems of equipment management and update in automation factories are solved, cross-component updates and comprehensive security management are achieved, and the flexibility of automation systems is improved. and security.

CN118922814APending Publication Date: 2024-11-08PHOENIX CONTACT GMBH & CO KG
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380030113.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-24
Filing Date
2023-03-23
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

The prior art lacks a manufacturer-independent approach to management and updates, making it difficult to achieve cross-component updates and comprehensive security management in automated factories, especially with connections between IT and OT networks.

Method used

A device management and update system is designed to provide interface selection, readout services, update planning services, update file search services, checking and allocation services and update services through device management and update user units to achieve centralization of multiple automation equipment. Manage and update to ensure compatibility and security of update files.

Benefits of technology

Manufacturer-independent management and updates of automation equipment are implemented, providing the possibility of cross-component updates and comprehensive security, improving the flexibility and compatibility of updates, ensuring the security of automation systems at all levels.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118922814A_ABST
    Figure CN118922814A_ABST
Patent Text Reader

Abstract

The present invention relates to a management and update system for automation devices of an automation system connected to an OT network, comprising a device management and update subscriber unit programmed to provide: a service for selecting and establishing a communication interface, the communication interface is used for generating a communication link with automation equipment in a plurality of connected automation equipment; a readout service for enabling readout of the device type information stored in the automation device from each of the automation devices having the communication link, and for holding the corresponding readout device type information; a service for planning an update request for each of the plurality of automation devices for which the read device type information is stored; a service for establishing a communication link with at least one memory unit and retrieving an update file stored in the memory unit; and a server for functionally checking the publication of each retrieved update file for the plurality of automation devices according to the stored device type information, and if the result of the checking of one of the retrieved update files is the publication performed for the automation device, storing the publication for the plurality of automation devices, and if the result of the checking of the one of the retrieved update files is the publication performed for the automation device. If yes, the updating file is distributed to the service of the equipment type information stored by the automation equipment; and a service for transmitting the respective update file assigned to each automation device along with the update command in accordance with the saved device type information associated with the automation device, and the transmission being functionally based on the update request planned for each automation device.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a system for managing and updating automation equipment connected to an OT network of an automation factory. Background Art

[0002] Conventionally, the updating of automation devices (hereinafter also referred to as industrial automation devices) connected to the OT network of an automated factory, in particular the updating of the firmware on these devices, can only be done locally and individually for each device. Therefore, different tools are used for many devices. New developments for individual devices are planned or have been started. However, to the knowledge of the applicant, no or only device-specific standards are currently in use.

[0003] There are so-called "device management tools" for managing industrial automation devices, such as the tool sold by Etherwan under the name "eVue" for device-specific network configuration and monitoring, the software sold by Perle under the name "PerleView" for its network components, or the "Mobile Device Management" from Phoenix Contact Cyber ​​Security GmbH for updating its "MGuard" devices for remote maintenance and monitoring via mobile networks.

[0004] However, based on such “device management tools”, there are further requirements, in particular regarding a comprehensive and modular device management system while ensuring end-to-end security (“Security” in English).

[0005] It has long been known that computers, IT infrastructure and even mobile terminal devices have the need to fill security gaps or expand functions. For automation equipment, such as PLC (Programmable Logic Controller) or network components in factories, these requirements have long been no problem, and the closer IT and OT are to each other (i.e., "Information Technology" (IT) describes / involves electronic data processing and "Operational Technology" (OT) involves hardware and software infrastructure for direct monitoring and / or control of industrial plants, equipment, processes and events), the more the automation market needs device and update management, i.e., "device and update management". The internationally standardized ISA95 model that divides automation into five levels is used to distinguish between IT and OT in the context of the present invention. The top two levels include the parent company level and the operational management level. The digital processes at these levels are assigned to IT and are carried out in the IT network set up for this purpose. The automation processes at the lower three levels (i.e., process management level, control level and field level) are controlled via an appropriately set up OT network. Therefore, the connection between the two networks (including data exchange) always requires a link.

[0006] For example, DE 10 2006 010 539 A1 describes the regular updating of a user profile of a program-controlled device and the updating of a program of the device in accordance with this update.

[0007] For example, EP 3 764 221 A1 describes the updating of a software version of an application on an automation device, wherein the updated version is first executed in a protected area of ​​a data processing device using historical process data in order to generate test correction data, and before being exchanged with the updated version of the application, the test correction data is compared with correction data generated by the application of the automation device based on the historical process data.

[0008] For example, DE 10 2015 112 040 A1 describes a firmware update for a control device for a process control, whereby the manufacturer performs a device-specific authorization check and, on this basis, provides a device-specific activation code in order to perform the firmware update by means of an update device that can be connected to the control device on the user side.

[0009] For example, EP 3 001 310 A1 describes a method for updating firmware of components of industrial automation devices, whereby the components to be updated and the firmware versions available for updating are determined based on stored compatibility relationships between different firmware versions available for the components and stored information about the firmware version currently used in the components.

[0010] For example, EP 3 588 277 A1 describes a firmware update in which a firmware package is compiled for a device complex having at least one hierarchical higher device and at least one hierarchical lower device, and distributed and applied in a top-down order, starting with sending to hierarchical higher devices. Crucially, the firmware package compiled for the device complex is sent to a single device in the complex, which then coordinates further distribution.

[0011] For example, EP 3 696 699 A1 describes a firmware update in an electronic device, wherein, after receiving an update file containing new firmware, a signature and a certificate with verification information, the verification information is first compared with the verification information read from the electronic device, and then the signature is checked only based on the comparison (if necessary), and finally the actual update is performed based on the signature.

[0012] For example, WO 2016 / 092003 A1 (EP3230856) describes a firmware update of a device, wherein a firmware file is transferred from a loading tool to the device, taking into account firmware-specific and / or device-specific loading information. In order to be able to use only one loading tool to firmware update different devices, the loading information is intended to be stored separately from the loading tool on at least one external data source and loaded by the loading tool.

[0013] For example, US2018 / 0357058 A1 describes a firmware update in which available firmware updates are determined by a product compatibility and download center based on a configuration template, and the required firmware update files and firmware update plan are automatically determined based on this template, thereby delivering the required firmware update files to the industrial components in an order determined by the firmware update plan.

[0014] For example, US2018 / 0359144 A1 describes a firmware update in a manner similar to the latter document, but in which a firmware update menu is provided to the user by an update server via a web interface within an application running on the user unit, and a selection made by the user is received via the web interface, based on which the required firmware update files and a firmware update plan are determined, and the required firmware update files are transmitted to the industrial components in an order determined by the firmware update plan.

[0015] For example, EP 2 189 900 A1 describes a software update in which an update applicable to the configuration of a node of a process control system is identified, update software and associated metadata related to the applicability of the software to the node are provided, and installation of the updated software is performed from a workstation communicating with the node of the process control system based on the metadata.

[0016] For example, DE 102 40 584 A1 describes an installation of a new operating program for a safety controller, wherein a download device for accepting new operating programs is provided in the safety controller, which download device enables or blocks acceptance of new operating programs in a fail-safe manner depending on release information.

[0017] For example, EP 3 923 095 A1 describes a software update of a technical system, wherein configuration parameters including operating parameters of a production process of the technical system are recorded, and software updates for elements of the technical system are loaded, wherein an update configuration for the software update of the elements is determined based on the operating parameters and the software update, and the update configuration and / or the software update is transmitted to an update server, wherein the update server controls and / or monitors and / or records the software update of the elements of the technical system based on the update configuration. Summary of the invention

[0018] Against the background of the above-mentioned prior art, the object of the present invention is to demonstrate a new method, in particular for the manufacturer-independent management and updating of industrial automation equipment in automated plants, such as industrial automation equipment such as programmable logic controllers, IO modules (input / output modules), frequency converters, robots, network devices, power supplies or other components used in automation technology, thereby not only providing the possibility of cross-component updates but also providing consistent security at all levels of the automation system.

[0019] The solution according to the invention is provided by a system having the features of claim 1 and by a data storage medium according to claim 10. Useful embodiments of the invention are subject matter of the dependent claims.

[0020] Therefore, the present invention proposes a management and update system for automation equipment connected to an OT network of an automation factory, the management and update system comprising a device management and update user unit connected to the OT network, and a plurality of automation equipment of the automation factory is further connected to the OT network. The device management and update user unit is also programmed to provide:

[0021] an interface selection and connection service, which is configured to select and set a communication interface for establishing a communication link with an automation device of a plurality of connected automation devices,

[0022] a readout service, which is arranged for enabling reading out of device type information stored in the automation device from each automation device with which a communication link is established, and for saving the respective readout device type information,

[0023] an update scheduling service arranged for scheduling an update request for each automation device of a plurality of automation devices for which the read device type information is stored,

[0024] - an update file retrieval service arranged to establish a communication link with at least one storage device and to retrieve update files stored in the storage device,

[0025] a checking and assigning service arranged to functionally check the publication of each retrieved update file for the plurality of automation devices according to the stored device type information and to assign the update file to the device type information stored for the automation device if the result of the checking for one of the retrieved update files is a publication for the automation device,

[0026] An update service is arranged to send a corresponding update file assigned to each automation device together with an update command according to the stored device type information, and said sending is functionally based on an update request planned for each automation device.

[0027] Therefore, a significant advantage of the present invention over the above-mentioned prior art can be seen in the fact that with a device management and update user unit provided according to the present invention, which unit is connected to the same OT network in addition to a plurality of automation devices of the automation system, in particular a central device management and update component is created using hardware and software components, with which the updating of the individual automation devices can be centrally controlled with the aid of definable update plans (preferably by the respective users). This centrally created device management and update component can also be used to simultaneously check whether an update is applicable to a specific automation device. In addition, the centrally created device management and update component is thus able to perform corresponding updates for individual automation devices, which provides a high degree of flexibility. This also advantageously allows, in particular with the aid of an update plan service, the order and version of updates, such as the software to be updated, to be centrally but individually specified for each individual automation device by the device management and update user unit.

[0028] Furthermore, a description configuration file, such as a firmware, can preferably be assigned to each update file in order to perform a check of the release of each retrieved update file. Thus, in addition to the stored information read out from the automation device, the corresponding description file can also be used in the centrally created device management and update component when checking whether an update should be performed, so that the compatibility between the automation device and its updates or update files can be ensured to the greatest extent possible. If a signature is contained in the update file in an appropriate manner, the authenticity and thus the authenticity of the update file itself can preferably be checked using a public key which can be stored or has been stored in the memory of the centrally created device management and update component.

[0029] The present invention also provides a data storage medium having program code stored thereon, the program code being designed to enable a data processing device connectable to an OT network to provide device management of corresponding settings and update user units when programmed using the program code. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The features and advantages of the invention which have been outlined above, as well as other features and advantages of the invention, will be shown in detail in the following description by means of examples of preferred embodiments and variants, with reference to the accompanying drawings, in which:

[0031] Figure 1 is an overview of a device management and updating user unit integrated into an exemplary management and updating system for automation devices connected to an OT network of an automation factory according to the present invention,

[0032] Figure 2 is an exemplary user interface for device and update management on a device management and update subscriber unit according to the present invention, wherein an operating screen is opened for an overview of definable or defined update storage locations,

[0033] Figure 3 yes Figure 2 An exemplary user interface is shown in which an operation screen is open for displaying / selecting an imported update file,

[0034] Figure 4 is based on Figure 2 An exemplary user interface of Figure 3 Release update files,

[0035] Figure 5 is an exemplary overview of the communication links that may be achieved by means of device management and updating of subscriber units according to the present invention,

[0036] Figure 6 is based on Figure 2 An exemplary user interface of wherein an operation screen is open for specifying a communication interface and a communication link,

[0037] Figure 7 is based on Figure 2 An exemplary user interface of FIG. 1 wherein an operation screen is open for displaying and organizing assets contained in each automation device,

[0038] Figure 8 is based on Figure 2 An exemplary user interface of FIG. 1 wherein an operation screen is open for creating an update plan,

[0039] Fig. 9 Yes Figure 2 An exemplary user interface is shown in which an operation screen is opened after starting an update plan.

[0040] Fig.10 is based on Figure 2 An exemplary user interface of wherein an operation screen is open for record updating,

[0041] Fig.11 is an overview of an exemplary overall architecture of a management and update system according to the present invention, and

[0042] Fig.12 is an overview of an exemplary overlay management platform for multiple device management and updating subscriber units in the context of a management and update system according to the present invention. DETAILED DESCRIPTION

[0043] Reference below Figures 1 to 12 On this basis, examples of preferred embodiments and variants of the management and updating system according to the invention are outlined and shown in a highly simplified form for the sake of clarity.

[0044] Figure 1 An exemplary embodiment of the present invention is shown for automation devices 200 a to 200 d connected to an OT network of an automation factory.

[0045] For the sake of clarity, Figure 1 The management and update system 100, which is not shown in detail, is also referred to as the DaUM system ("Device and Update Management System") below, which in particular comprises or integrates a device management and update user unit 110 connected to the OT network and to which a plurality of automation devices 200a to 200d of the automation plant are connected and are therefore installed there. As will be explained in more detail below, the device management and update user unit 110 is also programmed to provide various services. Figure 1 In the present disclosure, these services for managing and updating the system are collectively referred to as DaUM services ("Device and Update Management Services") and collectively ensure dynamic monitoring of assets and functions, in particular of automation devices installed on OT networks, in the context of management and updating.

[0046] It should be noted that in the context of the present invention, assets generally include any type of hardware (e.g., servers and switches) and software (e.g., firmware, applications, configurations, and supporting systems) of an automation environment that supports activities in the context of an automated factory where automation equipment is connected to an OT network. This also generally includes confidential information that must be protected from unauthorized access or unauthorized use, disclosure, modification, destruction, and / or theft.

[0047] For example, suppose you want to create a new file to update Figure 1The automation devices 200a to 200d shown are connected to an OT network and installed, and the automation devices 200a to 200d are subsequently to be updated using files, which usually depend on the manufacturer, the corresponding firmware and software modules being initially provided by the manufacturer via product development as files, having associated quality assurance and being stored or temporarily stored in a storage device. In particular, the storage device can also be a storage device of the manufacturer, but within the scope of the present invention it can in principle include any type of storage device, such as a USB flash drive or a storage space that can be accessed via the Internet. In particular, the storage device therefore essentially represents a central update repository, which is provided as a source related to these files and intended for updating, and which is stored in the storage device. Figure 1 and hereinafter also referred to as "Cure" ("Central Update Repository").

[0048] Hence, in the context of the present invention, the device management and update subscriber unit 110 is initially programmed to provide an update file retrieval service, ie in particular to set up a communication link with at least one storage device and to retrieve update files stored in the storage device.

[0049] To use a storage device accessible via the Internet (e.g. Figure 1 As shown, for example in the form of a CURe server), the device management and update user unit 110 is appropriately set up by programming in such a way that a defined interface to Cure can be set up via the Internet, and then the update files stored there can be retrieved from CURe via the DaUM system 100. These retrieved update files can then be conveniently stored and / or in the data repository of the DaUM system 100 itself (for clarity, Figure 1 In the example embodiment, the local repository is further processed locally in a local repository (not shown in FIG. 1 ), also referred to below as LR (“local repository”). In particular, this further processing also includes the creation of own, locally managed actual or update repositories, which appropriately contain only published updates.

[0050] On the other hand, an interface selection and connection service is provided for selecting and setting up a communication interface and for establishing a communication link with one of the plurality of connected automation devices 200a to 200d, i.e. in particular with at least one automation device and preferably with each automation device, via the device management and updating user unit 110 set up by programming. Thus, the installed devices (i.e. the automation devices 200a to 200d) are appropriately pre-set by the network management, e.g. using corresponding IP addresses and the necessary network settings, in such a way that they can also be reached via the communication link of the DaUM system 100 (which is established via the set up communication interface).

[0051] According to the invention, it is also provided that, by means of a readout service provided via the device management and updating subscriber unit 110 provided by programming, after the corresponding activation, the device type information stored therein is subsequently read out from each automation device for which a communication link has been established and is stored by the DaUM system 100. Conveniently, the device type information can also be stored in the above-mentioned own data repository.

[0052] With the help of an update planning service which is also provided via a device management and updating user unit 110 which is set up by programming and which is configured to plan update requests for each of a plurality of automation devices for which read-out device type information is stored, a user / operator (in particular through personnel in the device management department) can create a reality or update plan with the help of the DaUM system, via an operation mask of the device management and updating user unit 110, using the data contained in the above-mentioned own data storage device, in order to supply each automation device to be updated (in particular also in relation to the specific assets of the respective automation device) with a new version of firmware or other software.

[0053] In particular, since, as indicated above, the further processing of update files and thus the provision of update files to automation devices should only concern published update files or updates, a checking and allocation service is also provided via a programmably arranged device management and update user unit 110, which is arranged to functionally check the publication of each retrieved update file for a plurality of automation devices according to the stored device type information and to allocate the update file to the device type information stored for the automation device if the result of the check for one of the retrieved update files is a publication for an automation device. Furthermore, the device management and update user unit is suitably programmed to also store the allocated update files, in particular in the aforementioned own data storage means.

[0054] Then, the update service provided by the device management and update user unit 110 set by programming is finally set to send the update file including the update command distributed to each automation device according to the saved device type information, and the sending is functionally based on the update request planned for each automation device.

[0055] Furthermore, the device management and update subscriber unit is suitably arranged by programming to record a corresponding update status associated with each automation device for which the read device type information is stored.

[0056] Therefore, the management and update system according to the present invention (also referred to as DaUM system in the context of the present invention) is designed and arranged in a general manner to provide or mainly perform the following functions:

[0057] - Functionality for retrieving files for updating, in particular files stored by the respective manufacturers of the automation devices connected to the OT network;

[0058] - Functionality for setting up and managing communication interfaces of automation devices connected to OT networks;

[0059] - Functionality for managing and publishing software files to be distributed to connected automation devices;

[0060] -Function for reading current device type information;

[0061] - functionality for scheduling updates, including in particular checking files and assigning them to specific devices with end conditions and start times;

[0062] - functionality for performing updates on the device, i.e. in particular downloading and starting the update process; and appropriately

[0063] - Function to log all events.

[0064] With regard to the update file retrieval service provided via the device management and update user unit 110 provided by programming, and thus in particular with regard to the function of retrieving files for the update to be provided or to be performed, several different storage devices can be defined as sources in a practical implementation, hereinafter referred to as "cure" ("central update repository"), from which the DaUM system will obtain the update files. Since the update files can be easily obtained or transmitted as update data packages in a practical implementation, the update files are also referred to as update packages hereinafter. These are usually services provided by the device manufacturer, for automatically accessing a reality or update or the user's own data storage system, for example also accessed via the Internet. However, the update package can also be provided locally to the DaUM system via a large-capacity storage medium (for example a USB flash drive or file transfer).

[0065] An update file, ie in particular an update data package ("update package"), preferably consists of a description file, the actual update file and accompanying documentation.

[0066] In the case where the DaUM system is connected to the CURe after the communication link has been established and thus appropriately via the user interface of the device management and update user unit 110, the DaUM system preferably automatically (e.g. also periodically) queries whether there is a new version of the description file for a specific automation device (in particular for the assets contained therein). Specifically, the description file is first downloaded and then can be evaluated in the DaUM system. This can also be conveniently displayed to the user / operator via a correspondingly adjusted operating view.

[0067] The description file contains at least information about the file type, update file, manufacturer information, version information, type information, dependencies on existing previous versions and / or hardware versions, unique ID (identification code), checksum, release status and / or other accompanying documents such as license information, modification instructions ("change notes"), version instructions ("release notes"), etc. Optionally, of course, other information can be provided, such as the duration of a typical update process. The user / operator can then conveniently select the required files from the description file via the user interface, and the DaUM system then downloads the included or preferably only the selected files from cure as an update package.

[0068] If the manufacturer also provides the description file or each description file appropriately with a cryptographic signature, the DaUM system can check this signature to ensure that the file has not been modified by a potential attacker. For this reason, in particular, a plurality of public keys may be stored or have been stored in the memory of the device management and update user unit 110, and the provided checking and distribution service uses these multiple public keys to verify the signatures contained in the retrieved update file, which signatures are correspondingly created using the private key.

[0069] In particular, based on XAdES ("XML Advanced Electronic Signature"), which is known as a set of extensions for the W3C recommendation XML-DSig, which allows the use of advanced electronic signatures and specifies a precise profile for XML-DSig for use with authorized electronic signatures within the meaning of EU Directive 1999 / 93 / EC valid at the time of this application, whereby an important factor of XAdES is that the electronically signed document remains valid for a long time, even if the underlying encryption algorithm has been cracked, the DaUM system can on the one hand appropriately check only the signature itself (XAdES-B level) and not the extensions of the signature. Alternatively, however, the DaUM system can also support the use of extensions according to XAdES level LT or LTA for verifying the signature.

[0070] In particular, however, the description files are checked in the DaUM system before the associated data are used further.

[0071] All update packages supplied to the DaUM system are conveniently stored in the local data storage (LR – “Local Repository”) of the DaUM system and can be reused from there. Figure 2An exemplary user interface for device management and update management on a user unit 110 arranged according to the invention is shown, wherein a definable or defined update storage location is outlined, for example also involving a local data storage device "Local Repository" as a data source "Cure". The advantage of using LR as Cure is that during the updating of automation equipment (especially the assets contained therein), there is no need to actively connect to CURe via a USB flash drive or the Internet.

[0072] As described above, the update file retrieval service of the DaUM system can preferably be configured to automatically and independently, appropriately regularly and at an adjustable period, check whether new compatible update packages are available on a central source (i.e., cure) for at least one automation device managed via the DaUM system, which is thus configured as a quasi-middle component, and can then, for example, also send a message to the user / operator or display the message to the user / operator via a correspondingly adjusted operating view. The message or display can then also inform the user / operator whether it is a critical security update, for example, whether it should be installed urgently, or also indicate the existence of a new update package for a planned update plan (see also Figure 8 ).

[0073] In particular, by means of the checking and distribution services provided by the device management and update user unit 110 set by programming, in particular with regard to the functions of managing and publishing software files to be distributed to the connected automation devices (in particular to the assets), the commonly owned downloaded files (i.e. the files from the entire description file), the update files and the accompanying documents belonging to the update package can be aggregated again, preferably first aggregated into an update package for further processing, and then stored or temporarily stored in the own local data storage device for further processing. As shown above, the DaUM system therefore preferably receives in addition to the pure update files (such as the above-mentioned change instructions, license conditions, etc.) additional accompanying documents, which are also conveniently listed separately in the associated description file.

[0074] Furthermore, it is advantageous, in particular for security reasons, that the release of the retrieved update files of the automation device after appropriate checking for further processing or for use by an authorized user / operator with authorization to release updates for further use in the DaUM system must be explicitly released, i.e. must be specifically confirmed via the user interface so that the update package cannot be used by any other user without a corresponding explicit release.

[0075] Figure 3 An exemplary user interface is shown in which an operating screen is open for displaying / selecting imported or downloaded update files or update packages, and Figure 4An exemplary user interface is shown in which an operation screen opens to clarify the release ("approval") of an update file or update package.

[0076] It can be said that the function of setting and managing the communication interface of the automation device can also be appropriately managed by the DaUM system set as an intermediate component by means of the interface selection and connection service provided by the device management and update user unit 110 set by programming. Figure 5 An exemplary overview of a communication link that may be established with an automation device by means of a device management and update user unit 110 according to the invention is shown, in this example, the communication link is shown as an OPC UA server of the automation device as a communication partner. Thus, such a communication link may preferably also connect multiple assets of the automation device. For example, in the example of a PLC, the corresponding OPC UA server of the PLC may provide the DaUM system with a possible connection of the device with the contained assets such as firmware, applications, other apps, licenses, configurations, etc.

[0077] Therefore, the device management and update user unit 110 is preferably set by programming to save the read device type information, which is respectively assigned to the assets specified by it and included in the automation device, especially the assets related to the firmware, application or configuration of the automation device, so as to be used for respectively planning update requests for the assets specified by the saved device type information, and respectively checking the retrieved update files with respect to the assets specified by the saved device type information, and then assigning the released update files to the corresponding assets.

[0078] A communication link (also referred to below as connection) describes in particular a connection to an asset of an automation device to be updated, such as firmware, an application, an application software (app) or a specific configuration.

[0079] Figure 6 It shows that Figure 2 An exemplary user interface is shown, in which an operating screen is open for specifying communication interfaces and communication links via which such connections can be established and through which the corresponding devices can be reached and managed using the DaUM system.

[0080] Therefore, you can set up the connection to the communication partner individually under the menu items Link or Connection (see Figure 6). As mentioned above, this can be, for example, an OPC UA server, which then represents at least one asset. However, other connection types, such as SNMP (“Simple Network Management Protocol”), HawkBit (an open platform solution that integrates “software update” functions into the framework of IoT (“Internet of Things”) solutions or platforms), etc., and / or links to other communication partners can therefore be appropriately established within the scope of the present invention. Therefore, the device management and update user unit 110 is particularly configured so that different protocols from a plurality of data exchange protocols can be used within the scope of the present invention depending on the automation device and / or for operating an update file retrieval service, in particular including standardized protocols, such as OPC UA, SNMP or DCP and / or open source protocols.

[0081] The current status of the link is also conveniently displayed in the menu items Links or Connections, and assets within the connection can be scanned. The found assets can then be displayed with additional information in the overview of the "Assets" menu item (see Figure 7 ). Assets can then preferably also be edited here, for example, tags can be assigned to individual assets, i.e. additional information can be tagged on the assets, which can then be used in the subsequent process when creating an update plan. Thus, the DaUM system can identify the current status of individual assets (e.g. software / firmware) and in particular suggest the user / operator to update to a newer version, or alternatively enable the update individually if a new version (in particular a released version) is available for the asset.

[0082] As for the update scheduling service for scheduling update requests for each of a plurality of automation devices for which the read device type information is stored, it is provided via the device management and update user unit 110 established by programming, so that files can also be conveniently assigned to specific assets, and termination conditions and start times can be set.

[0083] Thus, it can be said that the DaUM system (which can be configured as an intermediate component) can be used not only to create one realization or update plan for a DaUM service (including for a specific asset), but also to create multiple realization or update plans for it. These plans contain the asset to be updated and the corresponding realization files or update packages (see Figure 8 , Fig. 9 ).

[0084] Thus, the user / operator can also specify essentially any time in the future when the update schedule should start, or start the update immediately, or leave the schedule to the DaUM system to enable the update independently. However, the update schedule must first be published by an authorized user, which is useful.

[0085] Individual components (assets) of the automation device to be updated can be selected accordingly, and preferably also different types of automation devices and assets can be combined in the update plan. For example, the order of the assets in the update plan, i.e. the chronological order of the checks and / or updates performed with respect to the individual assets, can also be changed, and / or all suitable update packages available for the update service on the DaUM system can be displayed to the user / operator so that the specific update package required for the update can be flexibly selected.

[0086] As shown above, the user / operator is also given the option to define the termination behavior of the update plan. The termination behavior determines, for example, how the DaUM system should react in the event of an asset update failure. Thus, it is also possible to define a termination policy for all assets in the plan and / or define different policies for different assets.

[0087] - For example, it is possible to individually schedule to stop the update schedule and keep all assets in their current state ("Stop and Abort All"), i.e. assets that have already been updated keep the updates, while assets that have not yet been updated are no longer updated.

[0088] - For example, it is possible to schedule individually to stop an update schedule and additionally perform a version rollback for all devices that have been updated via that schedule ("Stop and Rollback All").

[0089] - For example, individual schedules can be made to skip failed devices by leaving them as is and then continuing with the update of the next device (“skip and continue”).

[0090] - For example, it is possible to separately plan to roll back only the failed devices, i.e. reset to the last version, and otherwise continue with the update plan ("rollback and continue"). However, it is also possible to skip devices with a recorded error status, for example, if the rollback fails.

[0091] By default, the created update plans are independent of each other and are processed sequentially. However, it is also possible, for example, to execute several plans in parallel at the same time. In this case, it is advantageous to set up the DaUM system to check whether identical assets are present in the plans and to prevent access to identical assets, in particular to notify the user / operator of this event. In the case of parallel execution of plans, it can also be specified whether dependencies should exist between the individual plans, in particular dependencies specified by the user / operator. For example, depending on the (partial) failure or success of one or more updates in a first plan (e.g. plan A), a second plan (e.g. plan B) that is executed in parallel can be fully or only partially executed / stopped.

[0092] These termination policies can basically be designed in the same way as the termination policies for individual assets. Thus, the progress of the updates as well as the results of the updates within the dependencies can also be displayed to the user / operator in an appropriate manner. However, the system can also be set up in such a way that the plans are executed one after another, but depend on each other. In this case, a plan starts as soon as the previous plan has ended, or only starts at the end of the previous plan. Termination policies can also be selected or set here. These termination policies can in turn be basically the same as the termination policies for the assets. For example, depending on the (partial) failure or success of one or more updates in a first plan (e.g. plan A), a subsequent second plan (e.g. plan B) is fully or only partially executed. The progress of the updates as well as the results of the updates within the dependencies are conveniently displayed to the user.

[0093] Regarding the update service provided by the device management and update user unit 110 set by programming, that is, regarding the function of performing updates on the automation device, it is also possible to appropriately define a future time at which the update plan is started or the update is started immediately (see Fig. 9 ). However, preferably, the update plan must be issued by an authorized user.

[0094] Once the update process has started, the update files are transferred to the automation devices in sequence and the corresponding update commands are sent. Once the automation device, in particular the specified assets contained in the automation device, have been successfully updated, this is appropriately recorded and the process continues to the next device (see also Fig.10 ).

[0095] Regarding the function of recording events, preferably all steps, especially events, occurring during the processing of the update plan are recorded in the form of a log. The status of each asset before and after the update has been performed can then be displayed to the user.

[0096] Advantageously, the device management and update user unit 110 can be programmed on an edge PC, on one of the plurality of automation devices themselves, or on a central server instance of the user. For example, a data storage medium stores program code, and the program code is designed so that a data processing device that can be connected to the OT network, if programmed with the program code, provides the device management and update user unit set as described above.

[0097] For example, the entire DaUM system (see also Fig.11) can also be provided as a reloadable function. The service is preferably provided as containerized software (Docker) and can therefore be easily run on various device categories, for example on all device categories of the applicant's PLCnext product line. Applications on industrial computers as well as applications on local PLCs can thus be implemented.

[0098] Another advantage is that the DaUM system according to the present invention can also be used to provide an overlay management level for many local DaUM services. Therefore, for this purpose, it is appropriate to include a management platform that is layered over the above-mentioned multiple device management and update user units (see, for example, Fig.12 ) and is configured to provide update files that are stored in a storage device for retrieval by multiple device management and update user units.

[0099] As a further possibility, a solution can be implemented in which the management of a number of local DaUM services is performed by means of an overlay management, in particular using a management platform arranged in the IT network, in particular using a management level that is arranged as a cloud-based platform. This management level offers the possibility of centrally retrieving device information from anywhere for the automation devices connected to the local DaUM services and the assets they contain. For example, the storage device can also be located in another external network connected to the IT network (see Fig.12 ).

[0100] The main advantage of this overlay management level is that it is no longer necessary to survey and inspect the respective automation plant or OT network on site to assess the current status of the plant. A single glance at the overlay management level is usually sufficient. Every status message from each hardware device can be translated into plain text there, so that specialist knowledge is no longer required to understand them. In addition, the overlay management level can keep the device firmware up to date, thus ensuring that the latest security patches and performance improvements are always available to the devices. In addition, the functions of local DaUM services can be used via the overlay management level. Thus, this overlay management level obtains update packages from the respective manufacturers of the automation devices to be updated, for example via the Internet, and distributes the update packages to the connected DaUM services. These local DaUM services then distribute the update files locally to the connected assets. This means that only the DaUM services need to be connected to the management level, not each individual automation device or even asset.

[0101] The location of each local DaUM service can be conveniently displayed in an overview map. When a local DaUM service is selected, the user accesses information of the automation equipment and / or assets connected to the DaUM service and can manage the DaUM service and the automation equipment and / or assets.

[0102] In fact, this overlay management level can also update the distributed DaUM service itself if a new version of the DaUM service is available. This means that not only can the automation devices and / or assets be managed, but the entire system can also be monitored and updated from a central location.

[0103] Thus, for example, this management level can run in a private cloud environment or in a user's IT service. To this end, everything needed to run the service is preferably provisioned in a "container". The user only needs to provide container management.

[0104] Possible implementation scenarios for managing and updating automation devices of an automation system connected to an OT network using a management and update system according to the present invention may be as follows, for example:

[0105] The data required for the update is automatically retrieved from a repository operated by the manufacturer (e.g. the applicant) via an http-based connection, or can be stored locally on the DaUM system via a USB flash drive (local repository). This data consists of the update file itself as well as change instructions, licensing information and a description file with meta information. The description file is encoded in, for example, JSON ("JavaScript Object Notation") and contains information about the assets to which the update can be applied. As is well known, version information is traditionally a prerequisite for updates. When the data is read in, it is checked and displayed to the user.

[0106] Before the update planner carries out an update of one or more assets, the corresponding files for the update are published by an authorized person with a corresponding role in the DaUM system. As long as the update package has not yet been published, it can only be used by authorized persons. This can be desired explicitly in order to use the update package for test purposes in a protected area. In order to add further user-specific information to the update package, the user / operator can, for example, add so-called tags. Based on these tags, the user / operator can filter the required update packages in the further process.

[0107] The devices and / or assets to be managed are reached via various communication channels. The user must configure the communication interface for this. For the connection via OPC UA, the OPC UA server of the automation device must be configured. In order to distribute software to the devices via Hawkbit, the Hawkbit server must be parameterized.

[0108] The accessible automation devices / assets and their version information are displayed in the DaUM system. This information is freely selectable and can include, for example, information about the installation location, machine number, etc. The user can use these tags to filter the required automation devices / assets in further processes.

[0109] Based on the update files and the status of the accessible devices, a user with authorization can schedule updates. To do this, the user selects the automation devices / assets to be updated from a list of accessible automation devices / assets. The selected ones are transferred to the schedule and the current version status is displayed. Depending on the versions of the software / firmware available on the automation device / asset, possible update files are suggested. This check is not performed on the terminal device, but in the DaUM system. The user selects the files to be used for the automation device / asset and sets the time when the update should start. The user can also define when the update schedule should be canceled. For example, the following conditions apply here:

[0110] - Stop and Cancel All - This will leave all assets in their current state;

[0111] -Stop and Rollback - performs a version rollback on all assets that have been updated by the plan;

[0112] Skip and Continue - skip the failed asset, by leaving it as is, and continue updating the next asset;

[0113] - Rollback and Continue - Undo only the failed assets and continue with the plan execution. At the end of the planning process, the plan must be released to execute the plan. Otherwise, the plan is just saved.

[0114] Once the time to publish the schedule has arrived or the user has manually started the schedule, the DaUM system starts distributing the update package to the automation devices / assets and starts the update. After downloading the file to the automation device / asset, the system also checks whether the file has not been changed and then executes the update depending on whether the status of the automation device / asset allows the update. Successful or failed updates are reported back to the DaUM system. If the update of the automation device / asset fails, the schedule continues to be executed according to the selected termination condition. All processes in the DaUM system are recorded with time stamps and user details and are available in the DaUM system.

[0115] In summary, it can therefore be said that the management and update system "DaUM system" designed according to the invention enables manufacturer-independent management and updating of automation devices connected to an OT network by means of a device management and update user unit which is arranged as a quasi-middle component and is likewise connected to the OT network. In order to set up such a device management and update user unit, the program code stored on the data storage medium can be used for the corresponding programming of a data processing device which can be connected to the OT network.

[0116] As indicated above, these automation devices can be, for example, programmable logic controllers (PLCs), IO modules, frequency converters, robots, network devices, power supplies and / or other components used in automation technology. Advantageously, the system according to the invention can also use standardized protocols, i.e., in particular protocols based on OPC UA ("Open Platform Communication Unified Architecture"; a standard for data exchange as a platform-independent, service-oriented architecture), SNMP ("Simple Network Management Protocol", a network protocol developed by the IETF for monitoring and controlling network elements from a central station) or DCP ("Dynamic Code Programming", object-oriented programming or dynamization of service-oriented architecture), whereby software can also be distributed to the devices, for example using the EclipseHawkbit client (an open source solution from the Eclipse Foundation). In addition to the possibility of updating many different components of the automation devices of an automated plant, the necessary security, in particular application-related security (Security in English), can also be ensured at all levels at all times. In a preferred embodiment, it can be ensured that all communications (in particular including necessary commands and instructions) can only be carried out under authenticated and authorized conditions. Specifically, the requirements of the international standard IEC 62443, which defines both technical and procedural aspects of industrial network security, can be met. As is known, the requirements related to the cybersecurity of machines and systems have increased significantly in recent years. If older automation devices are present in the automation plant, which may not meet the security properties of the management and update system within the scope of the present invention, they can also be provided with new software modules and / or individually marked, for example, so that possible security risks are stored in a log, for example, and can be retrieved when required. In addition, the device management and update user unit can be run at a variety of levels, such as on an edge PC in the automation plant, on a central server instance of the user, or even on the automation device of the automation plant itself, that is, depending on the application and scale of the management and update system.

Claims

1. A management and update system for automation equipment connected to an OT network of an automation factory, include: A device management and updating user unit is connected to an OT network, to which a plurality of automation devices of the automation factory are further connected, wherein the device management and updating user unit is further programmed to provide: an interface selection and connection service, which is configured to select and set a communication interface for establishing a communication link with an automation device of a plurality of connected automation devices, a readout service arranged for enabling reading out, from each automation device with which the communication link is established, device type information stored in the automation device and for saving the respective device type information read out, an update scheduling service arranged for scheduling an update request for each automation device of said plurality of automation devices for which the read device type information is stored, - an update file retrieval service arranged for establishing a communication link with at least one storage device and for retrieving update files stored in said storage device, a checking and assigning service, arranged to functionally check the publication of each retrieved update file for said plurality of automation devices according to the stored device type information, and to assign said update file to said device type information stored for said automation device if the result of the checking for one of said retrieved update files is a publication for an automation device, An update service configured to send the update file including update commands assigned to each automation device according to the stored device type information to each automation device, and the sending is functionally based on the update request planned for each automation device.

2. The management and updating system according to claim 1, wherein the equipment management and updating user unit is also programmed to: - save the assigned update file, and / or - Recording the corresponding update status for each automation device for which the read-out device type information is saved.

3. according to the management and update system described in claim 1 or 2, wherein said equipment management and update user unit is also arranged to by programming: - used to save the read device type information, each of which is associated with an asset specified by it and included by the automation device, in particular an asset related to the firmware, application or configuration of the automation device ; for respectively scheduling said update requests for said assets specified by said stored device type information; for respectively checking said retrieved update files with respect to said assets specified by said stored device type information; And is used to assign published update files to the corresponding assets.

4. Management and updating system according to one of the preceding claims, wherein the update files for checking each retrieved update file are each retrieved together with a description file, which is associated with the stored update file and which relates in particular to information about the file type, the update file, manufacturer information, version information, type information, dependencies on existing previous versions and / or hardware versions, a unique ID, a checksum, a release status and / or information about further accompanying documents, in particular licensing information and / or change notes.

5. A management and update system according to any one of the preceding claims, wherein a plurality of public keys can be stored in the memory of the device management and update user unit, and the inspection and distribution service is set using the plurality of public keys to verify the signature created using the private key included in the update file retrieved respectively.

6. Management and updating system according to one of the preceding claims, wherein the device management and updating user unit is set up by programming on an edge PC, on one of the plurality of automation devices themselves or on a central server instance of the user.

7. A management and update system according to any of the preceding claims, wherein the device management and update user unit is further configured to use different protocols from a plurality of data exchange protocols depending on the automation device and / or for operating the update file retrieval service, in particular including standardized protocols such as OPC UA, SNMP or DCP and / or open source protocols.

8. The management and update system according to any one of the preceding claims further comprises a management platform, which is layered on a plurality of device management and update user units according to any one of the preceding claims, and is configured to provide update files stored in a storage device for retrieval by a plurality of device management and update user units.

9. Management and updating system according to one of the preceding claims, wherein the management platform is further arranged in an IT network, in particular is provided as a cloud-based platform.

10. A data storage medium having program code stored thereon, the program code enabling a data processing device connectable to an OT network to provide device management and update user units according to any one of the preceding claims when programmed with the program code.