WO2024046552A1

WO2024046552A1 - Computer-implemented method for setting up a new component in a technical facility and control system for a technical facility

Info

Publication number: WO2024046552A1
Application number: PCT/EP2022/074181
Authority: WO
Inventors: Anna Palmin
Original assignee: Siemens Aktiengesellschaft
Priority date: 2022-08-31
Filing date: 2022-08-31
Publication date: 2024-03-07

Abstract

The invention relates to a computer-implemented method for setting up at least one new component in a technical facility with a device inventory. The computer-implemented method comprises the following steps: a) providing specific configuration rules for configuring a new component, b) monitoring the device inventory with regard to the occurrence of a predefined change that indicates the registration of a new component in the device inventory, c) if the predefined change occurs, determining component data indicative of the registered new component depending on the device inventory, d) determining a specific type of configuration data and a specific provision type for the registered new component depending on the provided specific configuration rules and the determined indicative component data, and e) providing the determined specific type of configuration data in the registered new component depending on the determined specific provision type.

Description

Computer-implemented method for setting up a new component in a technical system and control system for a technical system

The present invention relates to a computer-implemented method and a computer program product for setting up a new component in a technical system. In addition, the present invention relates to a control system for a technical system.

An industrial technical system, for example an LoT system (“Internet of Things”), conventionally has system components registered in a device inventory of the technical system. After configuring one of the registered system components, the respective system component is set up to carry out various actions, for example applying for certificates and communicating with other communication partners, such as other system components, in the context of the technical system.

If a new component (system component) is to be introduced into the technical system, it is first added to a device inventory of the technical system and registered there. Such an introduction is preferably carried out manually by a user or automatically. Automated procedures include, for example, "Secure Device Provisioning" according to OPC UA Part 21 ("Open Platform Communications Unified Architecture"), the procedure for so-called "Bootstrapping a remote secure key infrastructure" (BRSKI) or the Secure Setup procedure IEC 60802 TSN-IA. In the course of registering the new component, such automated procedures usually carry out a validation of the identity of the new component, including the verification of the manufacturer-specific certificates, for example the "Initial Device Identifier" certificates (IDevID certificates). However, at this point in time, the respective newly registered system component does not have any configuration data, such as the address of the responsible registration authority or the address of a certificate revocation list distribution point (CDP). ).

In addition, it may be that a new component, before it is added to the technical system and registered in it, is preconfigured using different manufacturer and/or product family-specific tools, such as different engineering tools. It is also possible that the new component only uses its own integrated databases and/or device lists and therefore only contains selected system components that are usually added manually. This new component is then added to the device inventory of the technical system. In particular, this means that the newly added and registered system component is listed in the device inventory of the technical system, but does not have any configuration data and is not configured and therefore cannot, for example, carry out any of the various actions mentioned above.

Against this background, one object of the present invention is to improve the setting up of new components in a technical system.

According to a first aspect, a computer-implemented method for setting up at least one new component in a technical system with a device inventory is proposed. The method has the following steps: a) providing specific configuration rules for configuring a new component, b) monitoring the device inventory for an occurrence of a predetermined change, which includes registering a new component in the device inventory, c) determining, upon occurrence of the predetermined change, component data indicative of the registered new component depending on the device inventory, d) determining a specific type of configuration data and a specific provision type for the registered new component depending on the provided specific configuration rules and the determined indicative component data, and e) providing the determined specific type of configuration data in the registered new component depending on the determined specific provision type.

The computer-implemented method according to the first aspect has the technical effect that, after the addition and registration of a new component in the device inventory of the technical system, for each registered new component, a uniform and automated process for loading (providing) the Depending on the registered new component, the specific type of configuration data determined is provided in the registered new component depending on the specific provision type determined for the registered new component. By loading the determined specific type of configuration data into the registered new component (system component), this is then configured. This can then communicate in the context of the technical system and carry out various actions, such as applying for application-specific certificates, validating certificates from communication partners and transmitting security events to a server, such as a syslog server. This results in the following advantages:

Since the specific type of configuration data and the specific provision type are determined individually for each registered new component, the respective registered new component is advantageously provided with only the configuration data relevant to it, i.e the specific type of configuration data determined for the registered new component. This means that when configuring the registered new component, not simply all data and thus also irrelevant data, but only the specific type of configuration data determined for the registered new component is provided in the registered new component. The freely available storage space of a system component memory is thus optimized.

As a result, the advantage of the present method is that it is possible for different system components, which require different specific types of configuration data according to their technical functionalities and/or capabilities, to use the respective ones in different ways, i.e. depending on the specific provision type determined to load the specific type of configuration data determined for the system component into the respective system component. This targeted loading or provision increases the communication security and reliability of the technical system.

Another advantage of the present method is that it makes a well-founded contribution to meeting the requirements of the international standard IEC 62443-3-3 regarding. of the central computer-implemented device inventory as the basis for a configuration management process. In addition, the present method also meets the requirements in the Zero Trust context according to the SP-800-207 standard of the National Institute of Standards and Technology.

The term “set up” can also be understood to mean the terms “accept” or “introduce”.

The technical system can be a system from the process industry or an automation system, such as a chemical, pharmaceutical, petrochemical system or a system from the food and beverage industry. medium industry act. This also includes all systems from the manufacturing and production industry and plants in which, for example, cars or all kinds of goods are produced. Furthermore, the technical system can also be designed as an energy generation system, such as a wind turbine, a solar system or a power plant.

“Registering” a new component involves including the unique identification number, such as the component number or the serial number, of the new component in the device inventory. The new component is “registered” in the device inventory in particular manually by a user or automatically using a tool, such as an “anomaly detection tool” or a registrar, for example in accordance with OPC UA Part 21 or BRSKI.

Examples of indicative component data are: the name, the manufacturer, the serial number, the address and/or URL of a registration authority, an IDevID certificate, a possibly existing LDevID-Generic certificate (English "Locally Significant Device Identifier-Generic -Certificate"), certificate-specific component user profiles and/or a registration method. In particular, the indicative component data is determined from the device inventory, for example from information about the registered new component.

The term “indicative” is understood in particular to mean that the component data is specific to the respective registered new component or provides information about the registered new component.

Deploying includes deploying or loading the identified specific type of configuration data into the registered new component. Preferably, the determined specific type of configuration data is loaded into or stored in the memory of the registered new component. After deploying according to step e) the registered new component is configured. The term “configured” is understood in particular to mean that the registered new component has received all the necessary configuration data so that it can communicate with other system components in the context of the technical system and can carry out the various actions mentioned above. Steps c) to e) of the present method are preferably used to "configure" the registered new component.

According to one embodiment, the method comprises: f) sending a certificate request for issuing at least one certificate for the registered new component at least depending on the specific type of configuration data provided, and g) receiving, upon successful validation of the sent certificate request, the at least an issued certificate.

The issued certificate is in particular designed at least as an application-specific or component-specific certificate. This certificate preferably enables the registered new component to communicate and exchange data with other system components in the technical system.

According to a further embodiment, the specific configuration rules provided have registration-specific, in particular a specific type of registration method, manufacturer-specific, component-specific and/or protocol-specific configuration rules.

At least the registration-specific configuration rules can be provided manually, for example by a user of the technical system, or automatically, in particular in the device inventory. The specific type of registration process preferably indicates the registration process by which the new component was registered in the device inventory.

A certain type of registration process, which automatically registers the new component in the device inventory, has, for example, an automated registration using ORC UA Part 21, BRSKI, TLS (Transport Layer Security) or "Anomaly Detection" without PoO (English). . “Proof of Originality”) on . The term "without PoO" means in particular that for this particular type of registration, registration is carried out using a discovery procedure without validation of the manufacturer-specific IDevID certificate. The “Anomaly Detection” registration process without PoO is particularly used when registering so-called Legacy and/or brownfield system components carried out in the technical system.

Manufacturer-specific configuration rules are rules that, for example, include the manufacturer of the registered new component when configuring the registered new component.

Component-specific configuration rules are rules that, for example, include the product name of the registered new component when configuring the registered new component. In addition, component-specific configuration rules can be provided based on further product-specific information.

Examples of protocol-specific configuration rules are rules which, for example, include the communication protocol used, such as TLS, when configuring the registered new component.

According to a further embodiment, the specific configuration rules are provided preconfigured and/or provided at least at a predetermined point in time during the life of the technical system.

The specific configuration rules are provided preconfigured, in particular, in the device inventory. The term “Deploy at run time” indicates automated deployment of the specific configuration rules. The automated provision of the specific configuration rules can also include provision using artificial intelligence, in particular using machine learning. Automated provisioning can also be customized using artificial intelligence. Here, an artificial intelligence can be trained or adapted to determine which registered new component is configured depending on which specific configuration rules.

According to a further embodiment, the determination according to step d) includes assigning the registered new component to a specific component type depending on the specific configuration rules provided and the determined indicative component data, with a respective specific component type being assigned to a respective specific component type Type of configuration data is assigned, wherein the specific component type is designed at least as a first manufacturer-specific component type, as a second manufacturer-specific component type or as a system-specific component type.

Assigning has the advantage that for each registered new component it can be determined individually which specific component type the registered new component corresponds to. Based on the determined specific component type, it can then be determined which specific type of configuration data should be provided to the registered new component or which specific type of configuration data the registered new component requires. This advantageously ensures that Depending on the specific component type, the respective registered new component is only provided with the specific type of configuration data assigned to it and is not provided with a specific type of configuration data of another specific component type that does not correspond to the determined specific component type of the registered new one Component corresponds to . This optimizes the freely available storage space in the memory of the system component and increases the reliability of the technical system.

This “individualization” of the specific types of configuration data is carried out in particular because different system components require different specific types of configuration data depending on their technical functionalities and/or capabilities.

While an OPC UA system component, for example, does not usually contact the registration authority (RA) of the technical system directly, but in particular only via a so-called. can contact the "OPC UA Global Discovery Server" and therefore preferably does not need the address and/or URL (uniform resource locator) of the RA, a system component designed as an industrial edge component or network component that has a certificate can be used. Uses administrative protocol, apply for certificates directly from the RA. An industrial edge component in particular therefore requires the address and/or URL of the RA and thus a specific type of configuration data which has the address and/or URL of the RA.

In addition, the various system components in a heterogeneous industrial IoT/OT environment (English "Operational Technology") are particularly set up to reach various certificate revocation list distribution points via network technology. The specific types of configuration data can therefore also differ in this point. Namely, the system components For example, if it is registered by an "Anomaly Detection Tool" that validates an IDevID certificate, the certificate from the highest certification authority (Root Certification Authority (RCA)) of the technical system may not be subsequently registered loaded into the system component as a trust anchor. In this case, the trust anchor would therefore have to be provided as part of a specific type of configuration data in the system component.

On the other hand, if an asset component is registered in the device inventory through a secure device onboarding tool (such as BRSKI Registrar), the trust anchor is preferably loaded into or deployed to the asset component as part of the onboarding according to the specification. In this case, it is therefore not necessary for the trust anchor to be contained in the specific type of configuration data that is provided in the system component.

An example of a first manufacturer-specific component type is a network component from a specific manufacturer.

An example of a second manufacturer-specific component type is a controller or a control system, for example for a programmable logic controller, from a specific manufacturer.

An example of a system-specific component type is a network component or a controller from another manufacturer, but which has been registered in the technical system.

According to a further embodiment, a specific provision type is designed as a first, a second or a third specific provision type, the first specific provision type being an automatic tized provision of the determined specific type of configuration data by means of an automation entity, wherein the second specific provision type has an automated provision of the determined specific type of configuration data using a specific protocol, in particular a network protocol, and wherein the third specific provision type has a manual one Providing the determined specific type of configuration data based on an input from a user of the technical system or a control system for the technical system.

In the present case, a control system is understood to mean a computer-aided technical system that has functionalities for displaying, controlling and guiding a technical system. The control system can in particular extend over a cloud that is connected to several technical systems. The registered new component can also be located in the cloud. A majority of registered new components can also be distributed across several technical systems.

An example of an automation entity is an engineering tool, such as: B. the TIA portal (“Totally Integrated Automation Portal”), or a runtime tool such as. B. the S IMATIC Automation Tool (SAT).

If an interface, such as an API (application programming interface), is present, in particular between a second provisioning unit of the control system and the automation entity, the first specific provisioning type can be used. According to step e), the specific type of configuration data is provided in the registered new component, in particular by means of the second provision unit and preferably depending on the automation entity. The specific type of configuration data loaded into the system component is preferably stored in a configuration cache of the second provision unit.

A specific protocol is, for example, NETCONF (Network Configuration Protocol), SOAP (Simple Object Access Protocol) or REST (Representational State Transfer).

For example, to use the second specific provision type, the provision according to step e), in particular by means of the second provision unit, depending on a JSON body (JavaScript Object Notation Body) created for the provision of the registered new component. carried out .

If the second provisioning unit of the control system can access the registered new component directly via a specific or standardized protocol, the second specific provisioning type can be used. According to step e), the specific type of configuration data is provided in the registered new component, in particular by means of the second provision unit and preferably using the specific protocol.

The second provision unit can also be set up to signal to the user of the technical system via an output that the user has entered the specific type of configuration data by means of an input in the system component or the control system, manually or using a tool. such as an engineering tool or a runtime tool, in the system component.

A user is, for example, a customer or an operator of the technical system. For example, the specific type of configuration data can be provided in the system component by means of manual input by the user using a user input device via the graphical interface of the TIA portal or directly in the second provision unit. Here, the user input device is in particular set up to receive input of the specific type of configuration data from the user.

Alternatively, the provision according to step e) can be carried out using a command line tool in which the specific type of configuration data is transferred directly to the registered new component.

According to a further embodiment, step c) further comprises:

Setting up, after the predetermined change has occurred, at least one component-specific certificate depending on the registered new component in the device inventory.

A component-specific certificate is in particular an LDevID generic certificate. The component-specific certificate is set up in particular automatically, for example using a registrar. Alternatively, the component-specific certificate can be set up using a user input device which is set up to receive input from a user to set up the component-specific certificate.

According to a further embodiment, the device inventory is designed to be computer-implemented and designed as a dedicated instance in the technical system, as part of a registration point of the technical system or in a cloud that is connected to the technical system.

The device inventory can be used as a dedicated instance in a control system for the technical system, or as part of the Registration point of the control system or in a cloud, which is connected to the technical system or which can be connected to the control system. Information about the system components, in particular indicative component data, can either be contained directly in the device inventory or referenced from the device inventory.

According to a further embodiment, the predetermined change further comprises a change of at least one specific type of configuration data stored in the device inventory, the method further comprising: h) determining, when the change occurs, at least one specific type of configuration data stored in the device inventory, at least one registered component from a plurality of components registered in the device inventory, which has the stored specific type of configuration data relating to the change, and i) updating the stored specific type of configuration data and providing the updated specific type of configuration data in the at least one determined registered component depending on the determined specific provision type for the at least one registered component.

This embodiment has the advantage that steps h) and i) ensure that no outdated configuration data, but only current specific types of configuration data, are present in the registered new component as well as in the several system components registered in the device inventory. In addition, it is advantageously ensured that when providing according to step e), the determined specific type of configuration data is current and not out of date and only the currently determined specific type of configuration data according to step e) is provided in the registered new component. In particular, if the change occurs, a synchronization message is immediately triggered. process is triggered, which causes all registered system components that have subscribed to the change of at least one specific type of configuration data stored in the device inventory to be immediately synchronized accordingly by registering the updated specific type of configuration data depending on the determined specific provision type System components are loaded.

The determination according to step h) is carried out in particular by comparing the specific types of configuration data loaded into the registered components and the specific types of configuration data affected as a result of the change.

Preferably, the updated specific type of configuration data is provided in several determined registered components depending on the respective determined specific provision type for the respective registered component.

For example, the second provision unit is set up to provide the updated specific type of configuration data in the at least one determined registered component depending on the determined specific provision type for the at least one registered component.

In particular, a monitoring unit of the control system is set up to detect the occurrence of the change. When the change occurs, the monitoring unit can then be set up to update the stored specific type of configuration data and make it available in a configuration cache of the second provision unit. The second provision unit is then preferably set up to carry out the provision according to step i). According to a further embodiment, the at least one issued certificate of the registered new component is designed as a digital certificate, in particular as a public key certificate.

A digital certificate is a digital data record according to the Persons or objects (in this case registered new components, system components, machines, devices, applications and the like) and their authenticity and integrity can be checked using cryptographic methods. The digital certificate contains in particular the data required for its verification. The digital certificate is issued by the certification authority.

A certificate is at least manufacturer-specific, component-specific (system-specific) or application-specific. A manufacturer-specific certificate is, for example, an IDevID certificate (English "Initial Device Identifier Certificate"), a component-specific or a system-specific certificate is, for example, an LDevID generic certificate and an application-specific certificate is, for example, an LDevID app certificate .

An LDevID generic certificate is applied for in particular on the basis of at least one manufacturer-specific IDevID certificate and binds the respective system component to the respective (user-specific) technical system.

An LDevID app certificate is preferably applied for on the basis of at least one component-specific LDevID generic certificate and is used by the respective system components in particular to ensure secure communication between the respective system components by means of communication. nication protocols, such as OPC UA or TLS, to build and implement.

According to a second aspect, a computer program product is proposed which comprises instructions which, when the program is executed by a computer, cause it to carry out the method according to the first aspect or an embodiment of the first aspect.

A computer program product, such as B. a computer program medium, can be used, for example, as a storage medium, such as. B. Memory card, USB stick, CD-ROM, DVD, or in the form of a downloadable file provided or delivered from a server in a network. This can be done, for example, in a wireless communication network by transmitting a corresponding file with the computer program product or the computer program means.

According to a third aspect, a control system for a technical system, in particular an automation system, is proposed. The technical system has a device inventory. The control system has: a first provisioning unit for providing specific configuration rules for configuring a new component, a monitoring unit for monitoring the device inventory for an occurrence of a predetermined change, which includes registering a new component in the device inventory, a first Determination unit for determining, when the predetermined change occurs, component data indicative of the registered new component depending on the device inventory, a second determination unit for determining a specific type of configuration data and a specific provision type for the registered new component depending on the specific fish provided Configuration rules and the determined indicative component data, and a second provisioning unit for providing the determined specific type of configuration data in the registered new component depending on the determined specific provision type.

The embodiments and features described for the proposed method according to the first aspect apply accordingly to the proposed control system according to the third aspect.

The monitoring unit is in particular set up to continuously monitor the device inventory with regard to the occurrence of a predetermined change. Furthermore, the monitoring unit can be set up to receive the occurrence of the predetermined change as an event message from another unit, for example the device inventory. For example, after registering the new component, an event message “New component registered in the device inventory” can be generated and transmitted to the monitoring unit from the device inventory.

According to a further embodiment, the control system has: a sending unit for sending a certificate request for issuing at least one certificate for the registered new component at least depending on the specific type of configuration data provided, and a receiving unit for receiving, upon successful validation of the sent certificate application, of at least one issued certificate.

According to a further embodiment, the control system has: a certification body, which is set up to validate the sent certificate application and, if the sent certificate is successfully validated. request to issue at least one certificate for the registered new component.

The determined specific type of configuration data provided in the registered new component according to step e) or according to the second provision unit has at least the address and / or URL of the RA, so that the registered new component or a sending unit of the control system is preferably for the registered new component, can apply for a certificate from the RA.

In particular, the sending unit is set up to send the certificate request for the registered component to the RA using a certificate management protocol (CMP). The certificate in particular has a component-specific (LDevID Generic Certificate) or an application-specific certificate (LDevID App Certificate).

The RA is then preferably set up to check the certificate application sent by the sending unit depending on the device inventory and, if the check is successful, to transmit it to the certification authority.

The certification authority is then set up to validate the certificate application sent.

The receiving unit is preferably set up to provide the at least one issued certificate of the registered new component.

In addition, the registration office is set up in particular to store the requested and issued certificate in the device inventory.

The registration authority (RA) is in particular part of a PKI (Public Key Infrastructure (PKI)). The guidance system preferably uses a PKI. The RA is an authority in a network, for example of a technical system and/or control system, which verifies an application, for example from a control system, a registered new component, a system component or a user, for a digital certificate and the certificate Certi ficate Authority (CA) announces that it will issue this.

According to a further embodiment, the first provision unit, the monitoring unit, the first investigation unit, the second investigation unit and/or the second provision unit of the control system are each as an application, in particular as a service or trained as a microservice.

Forming at least one of the respective units described above in this embodiment as an application has the advantage that the scalability or expandability of the control system and its respective units is improved, since the size of the control system can be flexibly changed using microservices, without to affect the provision of services. In other words, the respective units of the control system can be provided as dedicated services or microservices both individually to expand the control system and/or the technical system as well as together in the context of a software ecosystem and thereby better adapted to the entire certificate management of the control system become .

Microservices are information technology architecture patterns in which complex applications are generated from independent processes that can communicate with each other using language-independent programming interfaces, such as APIs. Microservices enable a modular structure of applications and have the advantage that each microservice can be developed and deployed independently without affecting other microservices. The application can also be designed as an application embedded in a container. The container is in particular a software container which is arranged in an execution environment and in which a respective application can be executed and which is separate from other containers. Applications designed as microservices or several parts of an application can also be executed independently of one another on the same hardware in a container. A group of applications can also run on different individual containers.

The respective unit, for example the first provision unit or the first determination unit, can also be implemented in terms of hardware or from a combination of hardware and/or software elements. In the case of a hardware implementation, the respective unit can be designed as a device or as part of a device, for example as a computer or as a microprocessor. In the case of a software implementation, the respective unit can be designed as a computer program product, as a function, as a routine, as part of a program code, as the application or as an executable object.

According to a further embodiment, the control system has: a control device that is set up to control at least the first provision unit, the monitoring unit, the first determination unit, the second determination unit and/or the second provision unit of the control system.

By means of the control device, an automated process for setting up the at least one new component in the control system is advantageously carried out.

The control device is set up to control the respective units of the control system in such a way that provision by means of the first provision unit, monitoring by means of the monitoring unit, determination by means of the first determination unit, determination by means of the second determination unit and provision by means of the second provision unit in a fully automated manner without human intervention ) User can be carried out in order to set up at least the new component fully automatically.

In one embodiment, the control system is designed in particular as a cluster on which the respective units of the control system are designed as a respective application embedded in a container in a respective execution environment and are controlled and executed there in particular by means of the control device. This has the advantage that the respective units can be executed separately on different system components of the control system or in the cloud and, in particular, are not tied to the different system components. A cluster or a software cluster or computer network refers to a number of networked software applications and/or their associated computers.

According to a further embodiment, the at least one new registered component is designed as a system component, wherein the system component is designed as a machine, such as a machine tool or a robot, as a field device, for example an edge device, a programmable logic controller, a sensor or a Actuator and/or as a network component, such as a network switch, a firewall component or an industrial PC, is designed.

A new component then registered in the device inventory is in particular a system component of the technical system. A system component can also be individual measuring transducers for sensors or control devices for actuators of the technical system. A system component can also be a combination of several such components Be measuring transducers or control devices, for example a motor, a reactor, a pump or a valve system. Higher-level devices such as an automation device, an operator station server or a decentralized peripheral are also included under the term “system component”. An automation device is a technical device that is used to implement automation. This can be, for example, a programmable logic controller (field device) that represents a higher-level control function for lower-level controllers. The system component can also be designed as a local data processing unit of an industrial LoT device. In addition, the control device can be set up to control at least one system component of the plurality of system components.

Further possible implementations of the invention also include combinations of features or embodiments described above or below with regard to the exemplary embodiments that are not explicitly mentioned. The person skilled in the art will also add individual aspects as improvements or additions to the respective basic form of the invention.

Further advantageous refinements and aspects of the invention are the subject of the subclaims and the exemplary embodiments of the invention described below. The invention is further explained in more detail using preferred embodiments with reference to the accompanying figures.

Fig. 1 shows a schematic block diagram of an exemplary embodiment of a control system for a technical system; and

Fig. 2 shows a schematic flow diagram of one

Procedure for setting up a new component. In the figures, identical or functionally identical elements have been given the same reference numbers unless otherwise stated.

Fig. 1 shows a schematic block diagram of an exemplary embodiment of a control system 100 for a technical system 1, such as an automation system. The technical system 1 has the control system 100 in FIG. As shown in Fig. 1, the control system 100 has several (registered) new components 10, 30. A new component 10, 30 is designed as a field device in FIG. 1. Alternatively, the new component 10, 30 can be designed as a network component, such as a network switch, a firewall component or an industrial PC.

In addition, references to method steps S100 to S108 of FIG. 2, which shows a schematic flow diagram of an exemplary embodiment of a method for setting up a new component, are given in brackets in the following explanations for FIG. 1.

In FIG. 1, the control system 100 has a first provision unit 15, a monitoring unit 16, a first determination unit 17, a second determination unit 18 and a second provision unit 19. In Fig. 1, the (registered) new component 10 has a transmitting unit 21 and a receiving unit 22. Alternatively, the control system 100 has the transmitting unit 21 and the receiving unit 22 (not shown). In addition, the technical system 1 has a device inventory 20, which is part of the control system 100 in FIG. 1 and which is designed to be computer-implemented in FIG. The control system 100 also has a control device 40. The units 15 - 19, the device inventory 20, the new components 10, 30 are connected in FIG. 1 to the control device 40 for transmitting data (not shown). The first provision unit 15 is set up to provide specific configuration rules for configuring a new component 10 (see step S 100 of FIG. 2). The specific configuration rules provided have registration-specific, manufacturer-specific, component-specific and/or protocol-specific configuration rules. In addition, the specific configuration rules are provided preconfigured. Alternatively or additionally, the specific configuration rules are provided at least at a predetermined time during the running time of the technical system 1.

Furthermore, the monitoring unit 16 is set up to monitor the device inventory 20 with regard to the occurrence of a predetermined change, which includes registering a new component 10 in the device inventory 20 (see step S 101 of FIG. 2). For this purpose, the monitoring unit 16 is connected to the device inventory 20.

Then the first determination unit 17 is set up to determine, when the predetermined change occurs, component data iKOMP indicative of the registered new component 10 depending on the device inventory 20 (see step S 102 of FIG. 2). Here the first determination unit 17 is connected to the device inventory 20. Furthermore, the first determination unit 17 is set up to set up at least one component-specific certificate depending on the registered new component 10 in the device inventory 20 after the predetermined change has occurred.

The second determination unit 18 is then set up to determine a specific type of configuration data and a specific provision type Type1, Type2, Type3 for the registered new component 10 depending on the specific configuration rules provided and the determined indicative component data iKOMP (see step S 103 of FIG. 2). The first investigation Unit 17 is set up to transmit the determined indicative component data iKOMP to the second determination unit 18, which is indicated by an arrow between the first and second determination units 17, 18 in FIG. 1 is shown. Furthermore, the second determination unit 18 is connected to the first provision unit 15 for obtaining the provided specific configuration rules.

The determination according to the second determination unit 18 involves assigning the registered new component 10 to a specific component type depending on the specific configuration rules provided and the determined indicative component data. A respective specific type of configuration data is assigned to a respective specific component type. A specific component type is designed at least as a first manufacturer-specific component type, as a second manufacturer-specific component type or as a system-specific component type.

The second provision unit 19 is then set up to provide the determined specific type of configuration data in the registered new component 10 depending on the determined specific provision type Type1, Type2, Type3 (see step S 104 of FIG. 2). Furthermore, the second provision unit 19 is connected to the second determination unit 18 for obtaining the determined specific type of configuration data and the specific provision type Type1, Type2, Type3. The second provision unit 19 is also shown in FIG. 1 connected to the monitoring unit 16 for exchanging data.

A specific provision type is designed as a first, a second or a third specific provision type Type1, Type2, Type3. The first specific provision type Typl has an automated provision of the determined specific type of configuration data using an automation entity 23.

Furthermore, the second specific provision type Type2 has an automated provision of the determined specific type of configuration data using a specific protocol P. Furthermore, the third specific provision type Type3 has a manual provision of the determined specific type of configuration data based on an input from a user of the control system 100.

The first, second and third specific deployment types Type1, Type2, Type3 are shown in FIG. 1 each shown with different arrows, which are each formed indirectly by the second provision unit 19 either via the automation entity 23, the protocol P or the user user to the registered new component 10.

In addition, the sending unit 21 is set up to send a certificate request CSR for issuing at least one certificate GERT for the registered new component 10, at least depending on the specific type of configuration data provided (see step S 105 of FIG. 2).

A certification body CA of the control system 100 is then set up to validate the sent certificate request CSR and, if the sent certificate request CSR is successfully validated, to issue at least one GERT certificate for the registered new component 10. The at least one issued certificate GERT of the registered new component 10 is shown in FIG. 1 designed as a digital public key certificate. The receiving unit 22 is then set up to receive the at least one issued certificate GERT (see step S106 of FIG. 2). In addition, the predetermined change may further comprise a change of at least one specific type of configuration data stored in the device inventory 20.

In particular, the monitoring unit 16 is set up to, when a change occurs at least one specific type of configuration data stored in the device inventory 20, at least one registered component 10 from a plurality of components 10, 30 registered in the device inventory 20, which contains the stored specific type of configuration data concerning the change has to be determined (see step S107 of FIG. 2).

Thereafter, an update unit, not shown, is set up to update the stored specific type of configuration data and the updated specific type of configuration data in the at least one determined registered component 10 depending on the determined specific provision type Type1, Type2, Type3 for the at least one registered one To provide component 10 (see step S108 of FIG. 2).

1, the first provisioning unit 15, the monitoring unit 16, the first determination unit 17, the second determination unit 18 and/or the second provisioning unit 19 are each as an application, in particular as a microservice , educated.

In addition, the control device 40 is set up to control at least the first provision unit 15, the monitoring unit 16, the first determination unit 17, the second determination unit 18 and/or the second provision unit 19 of the control system 100.

Fig. 2 shows a flow chart showing the steps of the method for setting up a new component 10, 30 (see Fig. 1) according to an exemplary embodiment. The Method includes steps S100 to S108. The respective method steps S100 to S108 have already been explained with reference to FIG. 1, which is why the method steps S100 to S108 are not described again to avoid repetition.

Although the present invention has been described using exemplary embodiments, it can be modified in many ways.

reference character list

1 technical facility

10 new component (system component)

15 first deployment unit

16 the monitoring unit

17 first investigation unit

18 second investigation unit

19 second deployment unit

20 Device Inventory

21 transmitter unit

22 reception unit

23 Automation entity

30 new components (system components)

40 control device

100 guidance system

CA certification body

GERT certificate

CSR certificate application iKOMP indicative component data

P protocol

5100 procedural step

5101 Procedural step

5102 Procedural step

5103 Procedural step

5104 Procedural step

5105 Procedural step

5106 Procedural step

5107 Procedural step

5108 Procedural step

Typl first deployment type

Type2 second deployment type

Type3 third deployment type

User User

Claims

Patent claims

1. Computer-implemented method for setting up at least one new component (10) in a technical system (1) with a device inventory (20), with the steps: a) Providing (S100) specific configuration rules for configuring a new component (10) , b) monitoring (S101) of the device inventory (20) with regard to the occurrence of a predetermined change, which includes registering a new component (10) in the device inventory (20), c) determining (S102) when the predetermined change occurs for the registered new component (10) indicative component data (iKOMP) depending on the device inventory (20), d) determining (S103) a specific type of configuration data and a specific provision type (Typl, Type2, Type3) for the registered new component (10 ) depending on the specific configuration rules provided and the determined indicative component data (iKOMP), and e) providing (S104) the determined specific type of configuration data in the registered new component (10) depending on the determined specific provision type (Typl, Type2, Type3) .

2. The method according to claim 1, characterized by: f) sending (S105) a certificate request (CSR) for issuing at least one certificate (GERT) for the registered new component (10) at least depending on the specific type of configuration data provided, and g) Receive (S 106), upon successful validation of the sent certificate request (CSR), of the at least one issued certificate (GERT).

3. Method according to claim 1 or 2, characterized in that the specific configuration rules provided have registration-specific, in particular a specific type of registration procedure, manufacturer-specific, component-specific and / or protocol-specific configuration rules.

4. The method according to any one of claims 1 - 3, characterized in that the specific configuration rules are provided preconfigured and / or are provided at least at a predetermined time during the runtime of the technical system (1).

5. The method according to any one of claims 1 - 4, characterized in that the determination (S103) according to step d) comprises assigning the registered new component (10) to a specific component type depending on the specific configuration rules provided and the determined indicative component data, wherein a respective specific type of configuration data is assigned to a respective specific component type, wherein the specific component type is designed at least as a first manufacturer-specific component type, as a second manufacturer-specific component type or as a system-specific component type.

6. The method according to any one of claims 1 - 5, characterized in that a specific provision type is designed as a first, as a second or as a third specific provision type (Typl, Type2, Type3), the first specific provision type (Typl). automated provision of the determined specific type of configuration data by means of an automation entity (23), wherein the second specific provision type (Type2) includes automated provision of the determined specific type of configuration data based on a specific protocol (P), in particular a network protocol, and wherein the third specific provision type (Type3) involves manual provision of the determined specific type of configuration data based on an input from a user of the technical system (1) or a control system (100) for the technical system (1).

7. The method according to any one of claims 1 - 6, characterized in that step c) (S102) further comprises:

After the predetermined change has occurred, setting up at least one component-specific certificate depending on the registered new component (10) in the device inventory (20).

8. The method according to any one of claims 1 - 7, characterized in that the device inventory (20) is designed to be computer-implemented and as a dedicated instance in the technical system (1), as part of a registration point of the technical system (1) or in a cloud which is connected to the technical system (1).

9. The method according to any one of claims 1 - 8, characterized in that the predetermined change further comprises a change of at least one specific type of configuration data stored in the device inventory (20), the method further comprising: h) determining (S107) when it occurs the change of at least one specific type of configuration data stored in the device inventory (20), at least one registered component (10) from several components (10, 30) registered in the device inventory (20), which has the stored specific type of configuration data relating to the change, and i) updating (S108) the stored specific type of configuration data and providing the updated specific type of configuration data in the at least one determined registered component (10) depending on the determined specific provision type (Typl, Type2, Type3) for the at least one registered component ( 10).

10. The method according to any one of claims 2 - 9, characterized in that the at least one issued certificate (GERT) of the registered new component (10) is designed as a digital certificate, in particular as a public key certificate.

11. Computer program product, comprising commands which, when the program is executed by a computer, cause it to carry out the method according to one of claims 1-10.

12. Control system (100) for a technical system (1), in particular an automation system, wherein the technical system (1) has a device inventory (20), the control system (100) having: a first provision unit (15) for providing of specific configuration rules for configuring a new component (10), a monitoring unit (16) for monitoring the device inventory (20) with regard to the occurrence of a predetermined change, which comprises registering a new component (10) in the device inventory (20), a first determination unit (17) for determining, when the predetermined change occurs, component data (iKOMP) indicative of the registered new component (10) depending on the device inventory (20), a second determination unit (18) for determining a specific type of configuration data and a specific deployment type (Typl, Type2, Type3) for the registered new component (10) depending on the specific configuration rules provided and the determined indicative component data (iKOMP), and a second provision unit (19) for providing the determined specific type of configuration data in the registered new component (10) depending on the specific deployment type determined (Typl, Type2, Type3).

13. Control system according to claim 12, characterized by: a sending unit (21) for sending a certificate request (CSR) for issuing at least one certificate (GERT) for the registered new component (10) at least depending on the specific type of configuration data provided, and a receiving unit (22) for receiving, upon successful validation of the sent certificate request (CSR), the at least one issued certificate (GERT).

14. Control system according to claim 13, characterized by: a certification authority (CA), which is set up to validate the sent certificate request (CSR) and, if the sent certificate request (CSR) is successfully validated, the at least one certificate (GERT) for the registered to issue a new component (10).

15. Control system according to one of claims 12 - 14, characterized in that the first provision unit (15), the monitoring unit (16), the first determination unit (17), the second determination unit (18) and / or the second provision unit (19) of the control system (100) is each designed as an application, in particular as a service or as a microservice.

16. Control system according to one of claims 12 - 15, characterized by: a control device (40) which is set up to control at least the first provision unit (15), the monitoring unit (16), the first determination unit (17), the second determination unit (18) and /or the second

To control the provision unit (19) of the control system (100).

17. Control system according to one of claims 12 - 16, characterized in that at least one new registered component (10) is designed as a system component, the system component being a machine, such as a machine tool or a robot, as a field device, for example an Edge - Device, a programmable logic controller, a sensor or an actuator and/or as a network component, such as a network switch, a firewall component or an industrial PC.