Configuration Method And Internet Of Things Device

Abstract

To configure an Internet of Things, IoT, device for collecting data from industrial devices, the IoT device is coupled to a IoT platform. The IoT platform stores device twin data of the industrial devices. The device twin data includes configuration information. The IoT device retrieves the configuration information from the device twin data stored in the IoT platform and uses the configuration information for collecting data from the industrial devices.

Claims

1. A method of configuring an Internet of Things, IoT, device for collecting data from industrial devices, wherein the IoT device is coupled to an IoT platform via a communication channel, wherein the IoT platform stores device twin data of the industrial devices, the device twin data including configuration information, the method comprising: retrieving, by the IoT device and via the communication channel, the configuration information from the device twin data stored in the IoT platform; and using, by the IoT device, the configuration information for collecting data from the industrial devices.

2. The method of claim 1, wherein using the configuration information comprises configuring a data collection logic of the IoT device.

3. The method of claim 2, wherein configuring the data collection logic comprises setting one or several of: protocol address of datapoints for read, write, or execute operations; read intervals; timeouts; rules for data transformation; parameters of data transmission from the IoT device to the IoT platform.

4. The method of claim 2, further comprising collecting, by the IoT device, data from the industrial devices and generating, by the IoT device, data for transmission to the IoT platform based on the data collected from the industrial devices.

5. The method of claim 1, wherein the configuration information comprises a protocol configuration and the method further includes storing the protocol configuration in the IoT device for use by a data collection logic of the IoT device.

6. The method of claim 1, further comprising retrieving, by the IoT device, additional configuration information from the IoT platform in response to establishment of a communicative coupling between the IoT device and an additional industrial device.

7. The method of claim 1, wherein the device twin data uses a strongly typed definition to model data associated with an industrial device and the configuration information associated with the industrial device.

8. The method of claim 1, comprising performing a data synchronization of the device twin data between the IoT device and the IoT platform.

9. The method of claim 8, wherein the data synchronization is performed via the communication channel used by the IoT device to retrieve the configuration information, wherein the data synchronization is a bidirectional data synchronization between the IoT device and the IoT platform.

10. The method of claim 1, wherein the industrial devices comprise devices of an industrial automation control system.

11. The method of claim 1, wherein the IoT device is an IoT Edge device or Gateway device.

12. An Internet of Things, IoT, device for collecting data from industrial devices comprising: at least one first interface adapted to communicatively couple the IoT device with the industrial devices; a second interface adapted to communicatively couple the IoT device to a IoT platform; a memory or storage device adapted to store configuration information retrieved via the second interface from device twin data of the industrial devices stored in the IoT platform; and a circuit adapted to collect, via the at least one first interface, data from the industrial devices in accordance with the retrieved configuration information.

13. The IoT device of claim 12, wherein the IoT device is configured for: retrieving, by the IoT device and via the communication channel, the configuration information from the device twin data stored in the IoT platform; and using the configuration information for collecting data from the industrial devices.

14. An IoT platform computer system, comprising: a memory or storage device adapted to store device twin data of industrial devices, wherein the device twin data for the industrial devices includes configuration information required by an Internet of Things, IoT, device when collecting data from the respective industrial device; and an interface adapted to output the configuration information to the IoT device.

15. A system, comprising: an IoT device for collecting data from industrial devices, the IOT device having: at least one first interface adapted to communicatively couple the IoT device with the industrial devices; a second interface adapted to communicatively couple the IoT device to an IoT platform, a memory or storage device adapted to store configuration information retrieved via the second interface from device twin data of the industrial devices stored in the IoT platform; and a circuit adapted to collect, via the at least one first interface, data from the industrial devices in accordance with the retrieved configuration information an IoT platform computer system communicatively coupled to the IoT device, the IOT platform having: a memory or storage device adapted to store device twin data of industrial devices, wherein the device twin data for the industrial devices includes configuration information required by the IoT device when collecting data from the respective industrial device; and an interface adapted to output the configuration information to the IoT device; and a plurality of industrial devices, communicatively coupled to the IoT device, wherein the IoT device is adapted to collect data from the plurality of industrial devices in accordance with configuration information retrieved by the IoT device from the IoT platform computer system.

16. The method of claim 1, wherein the industrial devices are power system devices.

17. The method of claim 10, wherein the industrial devices comprise devices of a substation automation system.

18. The IoT device of claim 12, wherein the industrial devices are power system devices.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0115] The subject-matter of the invention will be explained in more detail with reference to preferred exemplary embodiments which are illustrated in the attached drawings, in which:

[0116] FIG. 1 is a block diagram representation of a system according to an embodiment.

[0117] FIG. 2 is a flow chart of a method according to an embodiment.

[0118] FIG. 3 is a flow chart of a method according to an embodiment.

[0119] FIGS. 4 and 5 are block diagram representations of a system according to an embodiment.

[0120] FIG. 6 is a block diagram representation of a system according to an embodiment.

DETAILED DESCRIPTION

[0121] Exemplary embodiments of the invention will be described with reference to the drawings in which identical or similar reference signs designate identical or similar elements. While some embodiments will be described in the context of specific industrial systems, such as substation automation systems, electric grids, microgrids, distributed energy resources, distribution or transmission networks, the embodiments are not limited thereto.

[0122] While exemplary embodiments will be described in the context of a specific number of industrial devices coupled to an Internet of Things (IoT) device, the number of industrial devices is not particularly limited. It will be appreciated that greater or smaller numbers of industrial devices may be coupled to an IoT device.

[0123] It will be appreciated that, as used herein, the term “device twin” refers to a digital twin of an industrial device. The term “industrial devices” used herein refers to devices that include devices of power systems, without being limited thereto.

[0124] The features of embodiments may be combined with each other, unless specifically noted otherwise.

[0125] FIG. 1 is a block diagram of system that includes an industrial system 10, an IoT device 30, and an IoT platform 50, which may be implemented by a cloud. The industrial system 10 comprises a plurality of industrial devices 11, 12, 13 that may be communicatively coupled to the IoT device 30.

[0126] The industrial system 10 may be a substation or substation automation system. The industrial devices 11, 12, 13 may include primary and/or secondary devices of the substation automation system. The industrial devices 11, 12, 13 may be other devices of an electric power system are of another industrial system. For illustration, the industrial system 10 may to be a distributed energy resource (DER) or microgrid.

[0127] The IoT device 30 may be an Edge or Gateway.

[0128] The IoT device 30 is operative to collect data from the industrial devices 11, 12, 13. The IoT device 30 has one or several first interfaces 31, 32, 33 to communicatively couple the IoT device 30 to the industrial devices 11, 12, 13. The IoT device 30 may be adapted to read data from the industrial devices 11, 12, 13, even when the industrial devices 11, 12, 13 operate in accordance with two or more different industrial protocols. For example, a first industrial device 11 may be an IEC61850-conformant device, and a second industrial device 12 may be a modbus-conformant device. Accordingly, the first interfaces 31, 32, 33 may include different interfaces for retrieving data from the IEC61850-conformant device and from the modbus-conformant device.

[0129] The IoT device 30 performs the data collection based on a data control logic 34. The data control logic determines 34 when and how data are read from or written to the industrial devices 11, 12, 30. The IoT device 30 may have one or several circuits, such as integrated circuits, including one or several of the following: processors, microprocessors, controllers, microcontrollers, application specific integrated circuits, to execute the data control logic 34 and to control the data control logic 34 in accordance with techniques that will be described in more specifically below.

[0130] The IoT device 30 has a device twin storage 35, which may be implemented as a storage device of a memory. Data collected from the industrial devices 11, 12, 13 may be stored in the device twin storage 35, optionally after additional processing. For illustration, the data collected from the industrial devices 11, 12, 13 may be used to adjust model parameters of the device twins in the device twin storage 35.

[0131] The IoT device 30 has a second interface 36, which may be a wired or wireless interface adapted to communicate with a wide area network or the internet. A secure communication channel may be established between the IoT device 30 and the IoT platform 50. The secure communication channel may be used for a bidirectional synchronization of device twin data stored in the IoT device and in the IoT platform 50.

[0132] The IoT platform 50 may be implemented as IoT cloud platform. The IoT cloud 50 platform may include one or several computers 51, servers 51 or server farms.

[0133] The IoT platform 50 may include one or several computer(s) or server(s), at least some of which may be provided on-site in the industrial system 10.

[0134] The IoT platform 50 includes a storage device 52 for storing device twin data. The device twin data 61, 62, 63 associated with the several industrial devices 11, 12, 13 may include data that is the result of a synchronization between the IoT device 30 and the IoT platform 50.

[0135] In the device twin data 61, 64, 67, the storage device 52 stores configuration information 62, 65, 68 respectively associated with one of the industrial devices 11, 12, 13. The configuration information 62, 65, 68 may be present even when the IoT platform 50 has not yet received any data collected by the IoT device 30. The configuration information 62, 65, 68 may provide instructions for how the data collection logic 34 is to collect and, optionally, process and transmit data from the industrial device represented by the digital twin in which the configuration information is stored.

[0136] The device twin 61, 64, 67 may preferably use a defined, strongly typed definition to model data and the configuration information 62, 65, 68.

[0137] The configuration information 62, 65, 68 may specify relevant protocol parameters that are to be used by the IoT device 30 for collecting data from the associated industrial device 11, 12, 13. For illustration, first configuration information 62 stored in first device twin data 61 may define protocol parameters used by the IoT device 30 to configure the data collection logic 34 of the IoT device 30 for collecting data from the first industrial device 11. Second configuration information 65 stored in the second device twin data 64 may define protocol parameters used by the IoT device 30 to configure the data collection logic 34 of the IoT device 30 for collecting data from the second industrial device 12. Third configuration information 68 stored in the second device twin data 67 may define protocol parameters used by the IoT device 30 to configure the data collection logic 34 of the IoT device 30 for collecting data from the third industrial device 13.

[0138] The configuration information 62, 65, 68 may include the following parameters in isolation or in combination: [0139] protocol address of datapoints for read, write, and/or execute operations; [0140] read intervals; [0141] timeouts; [0142] rules for data transformation; [0143] parameters of data transmission from the IoT device to the IoT platform.

[0144] During operation of the system, bidirectional synchronization between the IoT device 30 and the IoT platform 50 may cause the IoT device 30 to retrieve the configuration information 62, 65, 68 from the IoT platform 50. The configuration information 62, 65, 68 may be stored locally in the IoT device 30 as local configuration information 41, 42, 43 and/or may be processed further. In either case, the configuration information 62, 64, 68 associated with the protocols of the industrial devices 11, 12, 13 connected to the IoT device 30 may be used to control the data collection logic 34.

[0145] The IoT device 30 may then automatically use the retrieved configuration information when collecting data from the industrial devices 11, 12, 13 connected to the IoT device 30.

[0146] The configuration information may additionally also determine how the collected data is to be processed for storing in the device twin storage 35 or 4 synchronization with the device twin storage in the IoT platform 50.

[0147] Thus, the protocol configuration 62, 65, 68 is stored as part of the device twin 61, 64, 67 of each connected industrial device 11, 12, 13. This digital twin 61, 64, 67 may be persisted in the IoT platform 50 or another IoT platform and may be accessible to users and applications. The configuration information 62, 65, 68 is used to store protocol configurations that are then applied by the data collection logic 34 located in the IoT device 30. This configuration may include settings that are required to read using the protocol, write, and execute commands. It may contain: protocol address of datapoints for read, write and execute operations; time-related information, such as read intervals, timeouts, etc.; transformation rules to transform data; and/or other information.

[0148] The device twin data including the configuration 61, 64, 67 is synchronized between IoT device 30 and the IoT platform 50 or another IoT platform. Only the device twin data which is relevant for an IoT device is synchronized. I.e., when only industrial devices 11, 12, 13 are connected to the IoT device 30, only the respective configuration information is synchronized, as will be explained in more detail with reference to FIGS. 3 to 5. Plural IoT devices can thus be deployed to cover large installations and multiple operators, as will be described in more detail with reference to FIG. 6. The device twin synchronization can be realized using the same, secure communication channel as the telemetry data.

[0149] The configuration is then be used by the data collection logic 34 to retrieve data from the industrial devices 11, 12, 13, transform it and send it as the telemetry data to the IoT platform 50 or other IoT platform.

[0150] FIG. 2 is a flow chart of a method 70 according to an embodiment. The method 70 may be performed automatically by the IoT device 30.

[0151] At step 71, configuration information stored in the device twins 61, 64, 67 in the IoT platform 50 is retrieved by the IoT device 30. The configuration information is retrieved only for those industrial devices 11, 12, 13 that are coupled to the IoT device 30. The configuration information may be retrieved during bidirectional synchronization of device twin data between the IoT device 30 and the IoT platform 50.

[0152] At step 72, the data collection logic 34 of the IoT device 30 is configured or controlled based on the retrieved configuration information. This may include setting when, how, and/or wherefrom (i.e., using which protocol addresses) data is read by the IoT device 30 from the industrial devices 11, 12, 13. Configuring or controlling the data collection logic 34 may also include controlling how the collected data is processed by the IoT device 30 and/or how the collected data is transmitted by the IoT device 30.

[0153] At step 73, the data from the industrial devices 11, 12, 13 is collected by the IoT device 30. This may be done continually, i.e., in an ongoing basis, during operation of the industrial system 10.

[0154] At step 74, data synchronization may be performed between the IoT device 30 and the IoT platform 50 or another IoT platform.

[0155] At step 75, the digital twin data may be used for performing simulations, monitoring, control, maintenance or other operations. Step 75 may include simulating the industrial system or at least one industrial device of the industrial system. Alternatively or additionally, step 75 may include performing control operations for the industrial system, optionally including control that uses predicted operational states determined based on simulations. Alternatively or additionally, step 75 may include performing monitoring operations, optionally including predictive monitoring based on simulations. Alternatively or additionally, step 75 may include performing configuration or reconfiguration tasks, e.g. by using the device twins to determine new operation parameters for one or several of the industrial devices. Alternatively or additionally, step 75 may include controlling a user interface that allows an operator to interact with the device twins.

[0156] Changes in the industrial system 10 may automatically cause and adaptation or reconfiguration of the data collection logic 34 in the IoT device 30. For illustration, when a new industrial devices added to the industrial system 10 or an existing industrial device in the industrial system is replaced by a different industrial device, that techniques disclosed herein may cause the data collection logic 34 in the IoT device 30 to be automatically adapted. This will be explained in more detail with reference to FIGS. 3 to 5.

[0157] FIG. 3 is a flow chart of a method 80 according to an embodiment. The method 80 may be performed automatically by the IoT device 30.

[0158] At step 81, the IoT device 30 collects data from a set of industrial devices of an industrial system 10.

[0159] At step 82, the collected data are processed. This may include synchronization of device twin data between the IoT device 30 and the IoT platform 50, monitoring the state of the industrial system 10, controlling the industrial system 10, simulating the industrial system 10, controlling a user interface in dependence on the device twin data, or performing other actions related to the industrial system 10.

[0160] At step 83, it is determined whether an additional industrial device is detected. At step 84, configuration information for the additional industrial device is retrieved from the IoT platform. These steps may be implemented as an explicit detection by the IoT device 30. For illustration, when an additional industrial device is communicatively coupled with the IoT to device 30, the IoT device 30 may use an identifier of the additional industrial device to retrieve additional configuration information from the IoT platform 50. Alternatively, the normal synchronization of device twin data between the IoT device 30 and the IoT platform 50 may cause configuration information associated with a newly connected additional industrial device to be transferred to the IoT device 30.

[0161] At step 85, the data collection logic 34 of the IoT device 30 is reconfigured based on the retrieved additional configuration information associated with the newly connected additional industrial device. Data collection continues in accordance with the reconfigured data collection logic.

[0162] FIGS. 4 and 5 illustrate operation of the system according to an embodiment when a new industrial devices communicatively coupled with the IoT device 30.

[0163] FIG. 4 shows the system with only a first set of industrial devices 11, 12 (but not the third industrial device 13) communicatively coupled to the IoT device 30. Accordingly, the configuration information 41, 42 associated with the industrial devices 11, 12 (which is synchronized with the configuration information 62, 65 in the device twin storage of the IoT platform 50) is present in the IoT device 30, thus configuring the data collection logic 34 to operate in accordance with the configuration information 41, 42 associated with the industrial devices 11, 12.

[0164] FIG. 5 shows the system when an additional industrial device 13 is communicatively coupled with the IoT device 30. Synchronization of the device twin data between the IoT device 30 and the IoT platform 50 causes the configuration information 68 to be provided by the IoT platform 50 to the IoT device 30. As previously explained, this retrieved from of configuration information may be implemented by way of the device twin data synchronization, i.e., using the same secure channel that is also used to synchronize the device twin storage 35 of the IoT device with the device twins 61, 64, 67 in the device twin storage 52.

[0165] It will be appreciated that in the state shown in FIG. 4, the configuration data 68 was already persistently stored in the IoT platform 50. The device twin data 67 associated with the industrial device 13 and stored in the device twin storage in the IoT platform 50 does not yet include any operational data, because the IoT device 30 has not yet started collecting data from the industrial device 13 and the state shown in FIG. 4. FIG. 6 is a block diagram of a system according to another embodiment. The system includes a first IoT device 30 and a second IoT device 30′. Both IoT devices 30, 30′ are communicatively coupled with the IoT platform 50. The first IoT device 30 may be an Edge or Gateway that collects data from a first set of industrial devices 11, 12, 13. The second IoT device 30′ may be an Edge or Gateway that collects data from a second set of industrial to devices 14, 15, 16. The second set of industrial devices 14, 15, 16 may be included in the same industrial system as the first set of industrial devices 11, 12, 13, or may be provided in a separate industrial system that may even be under the control of a different operator.

[0166] The synchronization mechanisms between the IoT devices 30, 30′ and the IoT platform 50 cause configuration information including protocol parameters to be provided to an IoT device 30, 30′ only when it is communicatively coupled with an industrial device that requires those protocol parameters.

[0167] For illustration, if the first set of industrial devices 11, 12, 13 includes IEC61850-conformant devices but does not include any modbus-conformant devices, the IoT device 30 retrieves the relevant protocol parameters for the IEC61850-conformant devices from the IoT platform 50, but does not receive the protocol parameters for modbus-conformant devices from the IoT platform 50.

[0168] For further illustration, if the second set of industrial devices 14, 15, 16 includes IEC61850-conformant devices and modbus-conformant devices, the IoT device 30 retrieves the relevant protocol parameters for the IEC61850-conformant and for modbus-conformant devices from the IoT platform 50.

[0169] The structure shown in FIG. 6 allows configuration information to be conveniently changed centrally in the IoT platform 50. Modified protocol parameters will be communicated to the IoT devices 30, 30′ in the process of device twin data synchronization.

[0170] The device twin data may be used for various purposes, such as monitoring industrial systems, control of industrial systems, simulation of industrial systems, control of a user interface used for controlling an industrial system, maintenance work, or other purposes. For illustration, the need for reconfiguring devices, taking control actions, or deploying personal for on-site maintenance work may be anticipated by performing simulations using the device twin data.

[0171] The system may include a user interface 18 which may be a human machine interface (HMI) for controlling the industrial system 10. A controller of the user interface 18 may access device twin data in the IoT platform 50 and may control the user interface 18 in dependence on the device twin data, possibly after further processing, which may include simulation.

[0172] Alternatively or additionally, the system may include a control system 17 for controlling the industrial system 10. The control system 17 may access device twin data in the IoT platform 50 and may control the user interface 18 in dependence on the device twin data, possibly after further processing, which may include simulation.

[0173] Various effects are attained by the methods, devices, and systems according to embodiments. For illustration, the methods, devices, and systems allow an IoT device 30, 30′ to be used with a variety of industrial devices operating in accordance with a variety of industrial protocols, without requiring the respective protocol configuration to be previously hardcoded into the IoT devices 30, 30′. The IoT devices 30, 33 allow the relevant information required for controlling the data collection logic 34 in the IoT device 30, 30′ to be retrieved from the IoT platform 50 via the secure communication channel that at any rate has to be established for transmitting telemetry data. I.e., device twin synchronization including the exchange of the relevant configuration information takes place over the same secure channel as the transmission of telemetry data, obviating the need for an additional communication channel.

[0174] Thus, the methods, devices, and systems according to embodiments provide enhanced techniques for collecting data from industrial devices, such as substation automation devices.

[0175] The methods, devices, and systems can be used in a substation IoT solution, without being limited thereto. The methods, devices and systems can be used during live system operation (i.e., after commissioning) for simulation, monitoring, or a control operations, without being limited thereto.

[0176] While the invention has been described in detail in the drawings and foregoing description, such description is to be considered illustrative or exemplary and not restrictive. Variations to the disclosed embodiments can be understood and effected by those skilled in the art and practicing the claimed invention, from a study of the drawings, the disclosure, and the appended claims. In the claims, the word “comprising” does not exclude other elements or steps, and the indefinite article “a” or “an” does not exclude a plurality. The mere fact that certain elements or steps are recited in distinct claims does not indicate that a combination of these elements or steps cannot be used to advantage, specifically, in addition to the actual claim dependency, any further meaningful claim combination shall be considered disclosed.