IoT devices and configuration methods

Abstract

In order to configure an Internet of Things (IoT) device (30) for collecting data from industrial devices (11-13), the IoT device (30) is coupled to an IoT platform (50). The IoT platform (50) stores device twin data (61, 64, 67) of the industrial devices (11-13). The device twin data (61, 64, 67) includes configuration information (62, 65, 68). The IoT device (30) retrieves the configuration information (62, 65, 68) from the device twin data (61, 64, 67) stored in the IoT platform (50), and collects data from the industrial devices (11-13) using the configuration information (62, 65, 68).

Description

Technical Field

[0001] The present invention relates to industrial systems, in particular power systems, such as substation automation (SA) systems. The present invention relates to technology that allows data of industrial equipment, such as equipment of SA systems, to be collected to generate and / or maintain digital twins. Background Art

[0002] To ensure stable operation of industrial systems, such as substation automation systems, microgrids, distribution networks, or transmission networks, digital twins may be useful. Such digital twins may be used to simulate the operation of industrial systems, perform maintenance and / or reconfiguration tasks, or perform other control operations.

[0003] H. Zhang et al., "A digital twin-based approach for designing and decoupling of hollow glass production line", IEEE Transactions, Vol. 5, 2017, pp. 26901-26911, discloses a method for quickly and individually designing hollow glass production lines using a digital twin-based approach. The digital twin is used to verify the production line solution in the design and pre-production stages.

[0004] US 2016 / 0333854A1 discloses a digital twin interface for managing a wind farm having a plurality of wind turbines. The digital twin interface includes a graphical user interface (GUI) that displays a digital equivalent of the wind farm. The interface also includes one or more control features configured to optimize the performance of the wind farm.

[0005] When using Internet of Things (IoT) technology associated with industrial systems such as substation automation systems, devices such as Edges, Gateways, etc. can be used to collect data from primary devices (circuit breakers, transformers, etc.) through industrial standard protocols such as IEC61850 or modbus. Configuration of IoT devices is usually required to perform collection on industrial protocols. This configuration of IoT devices can instruct the data collection logic of the IoT device about which protocol address to collect data from, how often to read data, how to convert data into a custom data structure, and how to submit it to the cloud platform.

[0006] To perform this device configuration, various techniques may be considered.

[0007] In one approach, the protocol configuration is hard-coded in the IoT device. This approach does not require on-site personnel. However, the data collection logic of the IoT device is limited to a small number of industrial devices and cannot be configured or changed by the user. This limited flexibility may undesirably restrict the use of the device. For example, when a new industrial device is deployed that was unknown when the protocol configuration was hard-coded in the IoT device, the IoT device may no longer work with this new industrial device.

[0008] In a different approach, the protocol configuration is edited by a human expert and stored on the IoT device that holds the data collection logic. This approach provides enhanced versatility. However, field personnel or remote access to the IoT device is required to modify the configuration on the IoT device. Field personnel increase the complexity of the configuration task. Remote control of the configuration process for data collection logic may cause additional security risks. In either case, the process is prone to errors.

[0009] In yet another method, a special message can be used to transfer files or other information to the device. In this case, an additional transmission channel is needed to push files to the IoT device.

[0010] Therefore, these methods of configuring the data collection logic of IoT devices that collect data from devices of industrial systems have various disadvantages. To illustrate, the various methods described above handle protocol configuration in a manner that limits their applicability to a limited number of selected industrial devices and / or selected protocols, or requires on-site personnel configuration.

[0011] US 2019 / 0123967A1 discloses a technology in which a mapping is established between a device that is a tenant of an IoT support service and a tenant of a first third-party cloud service. On the IoT support service, device twins are stored so that each device twin corresponds to a corresponding IoT device, and so that each device twin includes at least a first part and a second part, the first part including properties of the corresponding IoT device, and the second part including properties associated with the first third-party cloud service. The IoT support service is used to call a first method associated with at least one IoT device based on metadata in at least one corresponding device twin. The first method is associated with the first third-party cloud service. Summary of the invention

[0012] There is a continuing need in the art for improved methods, devices, and systems for configuring data collection logic for Internet of Things (IoT) devices deployed in Industrial Internet of Things solutions. There is a continuing need in the art for improved methods, devices, and systems for configuring data collection logic for IoT devices that mitigate some of the above-mentioned disadvantages.

[0013] It is an object of the present invention to provide an improved technique for configuring data collection logic of an IoT device. It is an object of the present invention to provide a technique for configuring data collection logic of an IoT device that allows the IoT device to be used with industrial equipment (such as primary or secondary equipment of a substation automation system) whose protocol configuration has not been previously hard-coded into the IoT device. It is an object of the present invention to provide a technique that does not require field personnel to configure or reconfigure the data collection logic of the IoT device.

[0014] A method, an apparatus and a system are provided as described in the independent claims. The dependent claims define preferred embodiments.

[0015] Embodiments of the present invention use an IoT platform to store protocol configurations of industrial devices within device twin data representing the connected industrial devices. Thus, the device twin is used to store both data and configurations of the connected industrial devices, forming a holistic view of the devices. Bidirectional synchronization of the device twin ensures that the IoT device receives the configuration and allows the IoT device to correctly configure the data collection logic.

[0016] The IoT platform may be a cloud (including a server that may be off-site of an industrial system including the industrial devices) or one or more servers or computers that may be located on-site of the industrial system.

[0017] The device twin preferably uses strongly typed definitions to model the device twin's data and configuration associated with the corresponding industrial device.

[0018] Thus, the protocol configuration can be modified within the IoT platform (e.g., within the cloud) and distributed to one or more IoT devices using different protocols.

[0019] According to one aspect of the present invention, a method for configuring an IoT device for collecting data from industrial equipment, in particular power system equipment, is provided. The IoT device is coupled to an IoT platform (which may be a cloud or a computer) via a communication channel. The IoT platform stores device twin data of industrial equipment, the device twin data including configuration information. The method comprises the following steps: retrieving the configuration information from the device twin data stored in the IoT platform via the communication channel by the IoT device; and using the configuration information by the IoT device to collect data from the industrial equipment.

[0020] When configuration information is associated with an industrial device (e.g., such that a first device twin data associated with a first industrial device stores first configuration information associated with the first industrial device, and a second device twin data associated with a second industrial device stores second configuration information associated with the second industrial device), the configuration information is used by an IoT device that is separate and distinct from the industrial device to determine when and how to collect data from the corresponding industrial device.

[0021] Industrial equipment may include equipment with mechanically movable parts, sensors, actuators, merging units, protective relays, circuit breakers, transformers, generators, or other equipment.

[0022] Using the configuration information may include configuring the data collection logic of the IoT device.

[0023] Configuring the data collection logic may include instructing the data collection logic to use one or more of the following:

[0024] - The protocol address of the data point used to read, write and / or execute the operation;

[0025] -Reading interval;

[0026] -Timeout setting;

[0027] -Data conversion rules;

[0028] -Data transmission parameters from IoT devices to IoT platform.

[0029] To illustrate, using configuration information associated with a first industrial device communicatively coupled to the IoT device, data collection logic of the IoT device may be instructed to read data from or write data to the first industrial device according to a protocol address of a data point included in the configuration information associated with the first industrial device.

[0030] Alternatively or additionally, using configuration information associated with a first industrial device communicatively coupled to the IoT device, data collection logic of the IoT device may be instructed to read data from the first industrial device according to a timing that may be defined by a read interval included in the configuration information associated with the first industrial device.

[0031] Alternatively or additionally, using configuration information associated with a first industrial device communicatively coupled to the IoT device, the data collection logic of the IoT device can be instructed to terminate reading data from or writing data to the first industrial device based on a timeout included in the configuration information associated with the first industrial device.

[0032] Alternatively or additionally, using configuration information associated with a first industrial device communicatively coupled to the IoT device, data collection logic of the IoT device can be instructed to convert data read from the first industrial device to conform to an expected data format for storage in the device twin data based on a timeout included in the configuration information associated with the first industrial device.

[0033] Alternatively or additionally, using configuration information associated with a first industrial device communicatively coupled to the IoT device, data collection logic of the IoT device can be instructed to transmit data to the IoT platform to synchronize with a device twin in the IoT platform according to data transmission parameters included in the configuration information associated with the first industrial device.

[0034] The method may also include collecting data from the industrial device by the IoT device. The data collection is performed according to configuration information retrieved from the IoT platform.

[0035] The method may also include generating, by the IoT device, data for transmission to the IoT platform based on the data collected from the industrial equipment.

[0036] Configuration information may include protocol configuration.

[0037] The method may also include storing the protocol configuration in the IoT device for use by data collection logic of the IoT device.

[0038] The method may also include: in response to detecting the establishment of a communicative coupling between the IoT device and the additional industrial device, retrieving, by the IoT device, additional configuration information from the IoT platform. In this way, when the additional industrial device is communicatively coupled to the IoT device, the IoT device may be adaptively reconfigured using information within the device twin data stored in the IoT platform.

[0039] Device twin data can use strongly typed definitions to model data associated with industrial devices and configuration information associated with industrial devices. This facilitates the distribution of configuration information (which may include relevant protocol parameters for reading data from corresponding industrial devices) to several devices that can be deployed in the same or different industrial systems.

[0040] The method may also include performing data synchronization of device twin data between the IoT device and the IoT platform. The data synchronization may also ensure that all configuration information required by the IoT device is retrieved by the IoT device and stored locally in the IoT device.

[0041] Data synchronization can be performed via the communication channel used by the IoT device to retrieve configuration information. Data synchronization can be a two-way data synchronization between the IoT device and the IoT platform. In this way, the data collection logic in the IoT device can be reconfigured as needed without the need for a separate dedicated communication channel.

[0042] The communication channel may be a secure communication channel. Various mechanisms such as authentication and / or encryption may be used to ensure secure communication. However, a separate communication channel does not need to be established to configure or reconfigure the data collection logic of the device.

[0043] The industrial equipment may include equipment of an industrial automation control system, in particular equipment of a substation automation system.

[0044] The device can be an edge device or a gateway device.

[0045] The method may also include using the data collected by the IoT device and / or by a device twin in the IoT platform to perform one or more of the following:

[0046] - simulating the industrial system or at least one industrial device of the industrial system;

[0047] - performing control operations for the industrial system, optionally including control using predicted operating states determined based on the simulation;

[0048] -Perform monitoring operations, optionally including simulation-based predictive monitoring;

[0049] -Perform configuration or reconfiguration tasks, for example by using device twins to determine new operating parameters for one or several industrial devices;

[0050] -Control the user interface that allows the operator to interact with the device twin.

[0051] The IoT devices can be cloud-connected to an IoT cloud platform. The IoT cloud platform can include servers and / or computers that are remote from the industrial system including the industrial devices.

[0052] The IoT devices may be connected to an IoT platform, which is or includes a server or computer located on-site at an industrial system including the industrial equipment.

[0053] According to another aspect of the present invention, a method for operating a device twin storage device in an IoT platform computer system is provided. The method includes storing device twin data associated with multiple industrial devices in a device twin storage device. The device twin data associated with at least a portion of the multiple industrial devices respectively include configuration information, which includes a protocol configuration indicating which protocol parameters will be used by the IoT device to collect data from the corresponding industrial device. The method also includes outputting the configuration information to the IoT device by the IoT platform.

[0054] The method may also include synchronizing, by the IoT platform, the device twin data with the IoT device.

[0055] The protocol configuration can include any one or more of the following items:

[0056] - The protocol address of the data point used to read, write and / or execute the operation;

[0057] -Reading interval;

[0058] -Timeout setting;

[0059] -Data conversion rules;

[0060] -Data transmission parameters from IoT devices to IoT platform.

[0061] The device twin data may be a strongly typed definition that models the data of the device twin and the configuration associated with the corresponding industrial device.

[0062] According to one aspect of the present invention, an IoT device for collecting data from industrial equipment, in particular from power system equipment, comprises at least one first interface suitable for communicatively coupling the IoT device with the industrial equipment; a second interface suitable for communicatively coupling the IoT device to an IoT platform; a memory or storage device suitable for storing configuration information retrieved from device twin data stored in the IoT platform via the second interface; and a circuit suitable for collecting data from the industrial equipment via the at least one first interface based on the retrieved configuration information.

[0063] The circuit may include one or more integrated circuits (ICs). The circuit may include one or more integrated semiconductor circuits, such as one or more processors, controllers, or application specific integrated circuits (ASICs).

[0064] The circuitry may be adapted to configure data collection logic of the IoT device.

[0065] The circuit may be adapted such that one or more of the following items are set to configure the data collection logic of the IoT device:

[0066] - The protocol address of the data point used to read, write and / or execute the operation;

[0067] -Reading interval;

[0068] -Timeout setting;

[0069] -Data conversion rules;

[0070] -Data transmission parameters from IoT devices to IoT platform.

[0071] To illustrate, the circuit can be adapted such that, using configuration information associated with a first industrial device communicatively coupled to the IoT device, data collection logic of the first industrial device can be instructed to read data from or write data to the first industrial device according to a protocol address of a data point included in the configuration information associated with the first industrial device.

[0072] Alternatively or additionally, the circuitry may be adapted such that, using configuration information associated with a first industrial device communicatively coupled to the IoT device, data collection logic of the IoT device may be instructed to read data from the first industrial device according to a timing that may be defined by a read interval included in the configuration information associated with the first industrial device.

[0073] Alternatively or additionally, the circuitry may be adapted such that, using configuration information associated with a first industrial device communicatively coupled to the IoT device, the data collection logic of the IoT device may be instructed to terminate reading data from or writing data to the first industrial device based on a timeout included in the configuration information associated with the first industrial device.

[0074] Alternatively or additionally, the circuitry may be adapted such that, using configuration information associated with a first industrial device communicatively coupled to the IoT device, data collection logic of the IoT device may be instructed to convert data read from the first industrial device to conform to a desired data format for storage in the device twin data based on a timeout included in the configuration information associated with the first industrial device.

[0075] Alternatively or additionally, the circuitry may be adapted such that, using configuration information associated with a first industrial device communicatively coupled to the IoT device, data collection logic of the IoT device may be instructed to transmit data to the IoT platform to synchronize with a device twin in the IoT platform according to data transmission parameters included in the configuration information associated with the first industrial device.

[0076] The IoT device may be adapted to collect data from the industrial equipment. Collecting data may be performed according to configuration information retrieved from the IoT platform.

[0077] The IoT device may be adapted to generate data for transmission to the IoT platform based on data collected from the industrial equipment.

[0078] Configuration information may include protocol configuration.

[0079] The IoT device may be adapted to store the protocol configuration in the IoT device for use by the data collection logic of the IoT device.

[0080] The IoT device may be adapted to retrieve additional configuration information from the IoT platform in response to detecting establishment of a communicative coupling between the IoT device and an additional industrial device. In this way, when the additional industrial device is communicatively coupled to the IoT device, the IoT device may be adaptively reconfigured using information within the device twin data stored in the IoT platform.

[0081] The IoT device may be adapted to perform data synchronization of device twin data between the IoT device and the IoT platform. The data synchronization may also ensure that all configuration information required by the IoT device is retrieved by the IoT device and stored locally in the IoT device.

[0082] The IoT device may be adapted so that data synchronization may be performed via a communication channel that the IoT device uses to retrieve configuration information. The data synchronization may be a two-way data synchronization between the IoT device and the IoT platform. In this way, the data collection logic in the IoT device may be reconfigured as needed without the need for a separate dedicated communication channel.

[0083] The communication channel may be a secure communication channel. Various mechanisms such as authentication and / or encryption may be used to ensure secure communication. However, a separate communication channel does not need to be established to configure or reconfigure the data collection logic of the IoT device.

[0084] An IoT device may be adapted to use data collected by the IoT device to perform one or more of the following:

[0085] - simulating the industrial system or at least one industrial device of the industrial system;

[0086] - performing control operations for the industrial system, optionally including control using predicted operating states determined based on the simulation;

[0087] -Perform monitoring operations, optionally including simulation-based predictive monitoring;

[0088] -Perform configuration or reconfiguration tasks, for example by using device twins to determine new operating parameters for one or several industrial devices;

[0089] -Control the user interface that allows the operator to interact with the device twin.

[0090] The IoT device can be an IoT edge device or a gateway device.

[0091] The IoT devices can be cloud-connected to an IoT cloud platform. The IoT cloud platform can include servers and / or computers that are remote from the industrial system including the industrial devices.

[0092] The IoT device may be connected to an IoT platform that is or includes a server or computer located at a site of an industrial system including the industrial equipment.

[0093] An IoT device may be adapted to perform the method of any of the embodiments disclosed herein.

[0094] According to another aspect of the present invention, an IoT platform computer system includes: a memory or storage device suitable for storing device twin data of industrial equipment, wherein the device twin data for industrial equipment includes configuration information required by the IoT device when collecting data from the corresponding industrial equipment, and an interface suitable for outputting the configuration information to the IoT device.

[0095] The IoT platform computer system may be adapted to synchronize device twin data with IoT devices.

[0096] Configuration information may include any one or more of the following:

[0097] - The protocol address of the data point used to read, write and / or execute the operation;

[0098] -Reading interval;

[0099] -Timeout setting;

[0100] -Data conversion rules;

[0101] -Data transmission parameters from IoT devices to IoT platform.

[0102] The device twin data may be a strongly typed definition that models the data of the device twin and the configuration associated with the corresponding industrial device.

[0103] The IoT platform computer system may be adapted to use the data collected by the IoT devices to perform one or more of the following:

[0104] - simulating the industrial system or at least one industrial device of the industrial system;

[0105] - performing control operations for the industrial system, optionally including control using predicted operating states determined based on the simulation;

[0106] -Perform monitoring operations, optionally including simulation-based predictive monitoring;

[0107] -Perform configuration or reconfiguration tasks, for example by using device twins to determine new operating parameters for one or several industrial devices;

[0108] -Control the user interface that allows the operator to interact with the device twin.

[0109] A system according to an embodiment includes: an IoT device, an IoT platform computer system communicatively coupled 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 according to configuration information retrieved by the IoT device from the IoT platform computer system.

[0110] Industrial equipment may include equipment with mechanically movable parts, sensors, actuators, merging units, protective relays, circuit breakers, transformers, generators, or other equipment.

[0111] The industrial equipment may include equipment of an industrial automation control system, in particular equipment of a substation automation system.

[0112] Industrial equipment may include primary or secondary equipment in an electrical power system.

[0113] In any of the disclosed embodiments, configuration information may be stored in the IoT platform as part of the device twin.

[0114] Various effects and advantages are obtained by the method and computing system according to the present invention. To illustrate, storing the configuration inside a well-defined device twin data structure provides several benefits over traditional methods. New industrial devices can be connected to the system on-the-fly without special efforts because the configuration can be dependent on the industrial protocol but independent of the industrial device. The general concepts and structure of the device twin configuration data allow configurations of different industrial protocols to use the same concepts and infrastructure.

[0115] The IoT device can be reconfigured or adapted to new industrial devices without being limited to a specific number of predetermined industrial devices and / or protocols, and no on-site personnel is required to adapt or reconfigure the device.

[0116] The technology disclosed in this article can be applied to various industrial systems, such as substation automation, power grid, microgrid, distributed energy, distribution or transmission network, but is not limited thereto. BRIEF DESCRIPTION OF THE DRAWINGS

[0117] The subject matter of the invention will be explained in more detail with reference to preferred exemplary embodiments shown in the accompanying drawings, in which:

[0118] Figure 1 is a block diagram representation of a system according to an embodiment.

[0119] Figure 2 is a flow chart of a method according to an embodiment.

[0120] Figure 3 is a flow chart of a method according to an embodiment.

[0121] Figure 4 and Figure 5 is a block diagram representation of a system according to an embodiment.

[0122] Figure 6 is a block diagram representation of a system according to an embodiment. DETAILED DESCRIPTION

[0123] Exemplary embodiments of the present invention will be described with reference to the accompanying drawings, in which the same or similar reference numerals represent the same or similar elements. Although some embodiments will be described in the context of a specific industrial system such as a substation automation system, a power grid, a microgrid, distributed energy, a power distribution or transmission network, the embodiments are not limited thereto.

[0124] Although the exemplary embodiment 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 should be understood that a greater or lesser number of industrial devices can be coupled to the IoT device.

[0125] It should be understood that the term "equipment twin" used herein refers to a digital twin of an industrial device. The term "industrial device" used herein refers to a device including a device of a power system, but is not limited thereto.

[0126] The features of the embodiments may be combined with each other unless specifically stated otherwise.

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

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

[0129] The IoT device 30 may be an edge device or a gateway device.

[0130] The IoT device 30 is used to collect data from the industrial devices 11, 12, 13. The IoT device 30 has one or more first interfaces 31, 32, 33 to communicatively couple the IoT device 30 to the industrial devices 11, 12, 13. Even when the industrial devices 11, 12, 13 operate according to two or more different industrial protocols, the IoT device 30 can be adapted to read data from the industrial devices 11, 12, 13. For example, the first industrial device 11 can be an IEC 61850 compatible device, and the second industrial device 12 can be a modbus compatible device. Therefore, the first interfaces 31, 32, 33 can include different interfaces for retrieving data from an IEC 61850 compatible device and from a modbus compatible device.

[0131] The IoT device 30 performs data collection based on the data control logic 34. The data control logic determines 34 when and how to read data from or write data to the industrial devices 11, 12, 30. The IoT device 30 may have one or more circuits, such as integrated circuits, including one or more of the following: a processor, a microprocessor, a controller, a microcontroller, an application-specific integrated circuit, for executing the data control logic 34 and controlling the data control logic 34 according to the techniques described in more detail below.

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

[0133] The IoT device 30 has a second interface 36, which may be a wired or wireless interface suitable for communicating 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 bidirectional synchronization of device twin data stored in the IoT device and the IoT platform 50.

[0134] The IoT platform 50 can be implemented as an IoT cloud platform. The IoT cloud 50 platform can include one or more computers 51, servers 51 or server farms.

[0135] The IoT platform 50 may include one or more computers or servers, at least some of which may be provided on-site in the industrial system 10 .

[0136] 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 as a result of synchronization between the IoT device 30 and the IoT platform 50.

[0137] In the device twin data 61, 64, 67, the storage device 52 stores configuration information 62, 65, 68 associated with one of the industrial devices 11, 12, 13, respectively. The configuration information 62, 65, 68 may exist 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 collects and optionally processes and transmits data from the industrial device represented by the digital twin in which the configuration information is stored.

[0138] The device twins 61 , 64 , 67 may preferably use defined, strongly typed definitions to model data and configuration information 62 , 65 , 68 .

[0139] The configuration information 62, 65, 68 may specify relevant protocol parameters to be used by the IoT device 30 to collect data from the associated industrial devices 11, 12, 13. For illustration, the first configuration information 62 stored in the 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 to collect data from the first industrial device 11. The 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 to collect data from the second industrial device 12. The 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 to collect data from the third industrial device 13.

[0140] The configuration information 62, 65, 68 may include the following parameters individually or in combination:

[0141] - The protocol address of the data point used to read, write and / or execute the operation;

[0142] -Reading interval;

[0143] -Timeout setting;

[0144] -Data conversion rules;

[0145] -Data transmission parameters from IoT devices to IoT platform.

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

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

[0148] In addition, the configuration information may also determine how to process the collected data for storage in the device twin storage device 35 or synchronization with the device twin storage device 4 in the IoT platform 50.

[0149] Therefore, 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. The digital twin 61, 64, 67 can be saved in the IoT platform 50 or another IoT platform and can be accessed by users and applications. The configuration information 62, 65, 68 is used to store the protocol configuration that is subsequently applied by the data collection logic 34 located in the IoT device 30. The configuration may include the settings required to read, write and execute commands using the protocol. It may include: protocol addresses of data points used for reading, writing and executing operations; time-related information, such as read intervals, timeout settings, etc.; conversion rules for converted data; and / or other information.

[0150] The device twin data including configurations 61, 64, 67 are synchronized between the IoT device 30 and the IoT platform 50 or another IoT platform. Only the device twin data related to the IoT device is synchronized. That is, when only industrial devices 11, 12, 13 are connected to the IoT device 30, only the corresponding configuration information is synchronized, as will be referred to in Figures 3 to 5 Multiple IoT devices can therefore be deployed to cover large installations and multiple operators, as will be explained in more detail in Figure 6 Described in more detail, device twin synchronization can be achieved using the same secure communication channel as telemetry data.

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

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

[0153] At step 71, configuration information stored in the device twin 61, 64, 67 in the IoT platform 50 is retrieved by the IoT device 30. 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 a bidirectional synchronization of device twin data between the IoT device 30 and the IoT platform 50.

[0154] 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 from where (i.e., which protocol address to use) the IoT device 30 reads data 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.

[0155] At step 73, data from the industrial devices 11, 12, 13 is collected by the IoT device 30. This may be done continuously during operation of the industrial system 10, ie, on an ongoing basis.

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

[0157] At step 75, the digital twin data may be used to perform simulation, monitoring, control, maintenance, or other operations. Step 75 may include simulating an industrial system or at least one industrial device of an industrial system. Alternatively or additionally, step 75 may include performing a control operation of the industrial system, optionally including control using a predicted operating state determined based on a simulation. Alternatively or additionally, step 75 may include performing a monitoring operation, optionally including predictive monitoring based on a simulation. Alternatively or additionally, step 75 may include performing a configuration or reconfiguration task, such as determining new operating parameters of one or more industrial devices by using a device twin. Alternatively or additionally, step 75 may include controlling a user interface that allows an operator to interact with a device twin.

[0158] Changes in the industrial system 10 can automatically cause and adapt or reconfigure the data collection logic 34 in the device 30. For illustration, when a new industrial device is added to the industrial system 10 or an existing industrial device in the industrial system is replaced with a different industrial device, the techniques disclosed herein can automatically adapt the data collection logic 34 in the device 30. This will refer to Figures 3 to 5 Explain in more detail.

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

[0160] At step 81 , the device 30 collects data from a group of industrial devices of the industrial system 10 .

[0161] At step 82, the collected data is processed. This may include synchronizing device twin data between the IoT device 30 and the IoT platform 50, monitoring the status of the industrial system 10, controlling the industrial system 10, simulating the industrial system 10, controlling a user interface based on the device twin data, or performing other actions related to the industrial system 10.

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

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

[0164] Figure 4 and Figure 5 The operation of the system according to the embodiment is shown when a new industrial device is communicatively coupled with the IoT device 30 .

[0165] Figure 4A system is shown having only the first set of industrial devices 11, 12 (and not the third industrial device 13) communicatively coupled to the IoT device 30. Therefore, 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 device of the IoT platform 50) is present in the device 30, thereby configuring the data collection logic 34 to operate according to the configuration information 41, 42 associated with the industrial devices 11, 12.

[0166] Figure 5 The system is shown 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 enables the configuration information 68 to be provided by the IoT platform 50 to the IoT device 30. As previously explained, the configuration information retrieved from the configuration information can be implemented by synchronization of the device twin data, i.e., using the same secure channel that is also used to synchronize the device twin storage device 35 of the IoT device with the device twin 61, 64, 67 in the device twin storage device 52.

[0167] It should be understood that Figure 4 In the state shown, the configuration data 68 has been 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 device 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 is in Figure 4 Status shown.

[0168] Figure 6 is a block diagram of a system according to another embodiment. The system includes a first device 30 and a second device 30'. The two devices 30, 30' are communicatively coupled to an IoT platform 50. The first IoT device 30 may be an edge or gateway that collects data from a first group of industrial devices 11, 12, 13. The second IoT device 30' may be an edge or gateway that collects data from a second group of industrial devices 14, 15, 16. The second group of industrial devices 14, 15, 16 may be included in the same industrial system as the first group 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.

[0169] When the IoT devices 30, 30' are communicatively coupled with industrial devices that require these protocol parameters, the synchronization mechanism between the IoT devices 30, 30' and the IoT platform 50 enables the configuration information including the protocol parameters to be provided to the IoT devices 30, 30'.

[0170] To illustrate, if the first group of industrial devices 11 , 12 , 13 includes IEC 61850 compliant devices but does not include any modbus compliant devices, the IoT device 30 retrieves relevant protocol parameters for IEC 61850 compliant devices from the IoT platform 50 but does not receive protocol parameters for modbus compliant devices from the IoT platform 50 .

[0171] To further illustrate, if the second group of industrial devices 14 , 15 , 16 includes IEC 61850 compatible devices and modbus compatible devices, the device 30 retrieves relevant protocol parameters of the IEC 61850 compatible and modbus compatible devices from the platform 50 .

[0172] Figure 6 The structure shown allows for convenient and centralized changes to configuration information in the IoT platform 50. The modified protocol parameters will be transmitted to the IoT devices 30, 30' during the device twin data synchronization process.

[0173] The device twin data can be used for various purposes, such as monitoring industrial systems, controlling industrial systems, simulating industrial systems, controlling user interfaces for controlling industrial systems, maintenance work, or other purposes. To illustrate, the need to reconfigure equipment, take control actions, or deploy personnel to perform field maintenance work can be anticipated by performing simulations using device twin data.

[0174] 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 based on the device twin data, possibly after further processing including simulation.

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

[0176] Various effects are obtained by the methods, devices and systems according to the embodiments. For illustration, the methods, devices and systems allow IoT devices 30, 30' to be used with various industrial devices operating according to various industrial protocols without the need to pre-hardcode the corresponding protocol configuration into the IoT devices 30, 30'. IoT devices 30, 33 allow the retrieval of relevant information required by the data collection logic 34 in the control device 30, 30' from the IoT platform 50 via a secure communication channel, which must be established at any rate for the transmission of telemetry data. That is, device twin synchronization including the exchange of relevant configuration information occurs on the same secure channel as the transmission of telemetry data, eliminating the need for an additional communication channel.

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

[0178] The method, device and system may be used in substation solutions, but not limited thereto. The method, device and system may be used to simulate, monitor or control operations during field system operation (ie, after commissioning), but not limited thereto.

[0179] Although the invention has been described in detail in the drawings and the foregoing description, such description should be considered illustrative or exemplary rather than restrictive. Variations of the disclosed embodiments can be understood and implemented by those skilled in the art and practicing the claimed invention by studying 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 different claims does not mean that a combination of these elements or steps cannot be used to advantage. Specifically, any further meaningful claim combination will be considered disclosed in addition to the actual claim dependencies.

Claims

1. A method for configuring an Internet of Things (IoT) device (30), the IoT device being used to collect data from industrial devices (11-16), in particular power system devices, wherein the IoT device (30, 30') is coupled to an IoT platform (50) via a communication channel, wherein the IoT platform (50) stores device twin data (61, 64, 67) of the industrial devices (11-16), the device twin data (61, 64, 67) comprising configuration information (62, 65, 68), the method comprising: Performing data synchronization of the device twin data (61, 64, 67) between the IoT device (30, 30') and the IoT platform (50); Retrieving the configuration information (62, 65, 68) from the device twin data (61, 64, 67) stored in the IoT platform (50) by the IoT device (30, 30') and via the communication channel; In response to establishing a communicative coupling between the IoT device (30, 30') and an additional industrial device, retrieving additional configuration information (62, 65, 68) from the IoT platform (50) by the IoT device (30, 30'); and The configuration information (62, 65, 68) is used by the IoT device (30, 30') to collect data from the industrial equipment (11-16).

2. The method of claim 1, wherein using the configuration information (62, 65, 68) comprises: The data collection logic (34) of the IoT device (30, 30') is configured.

3. The method of claim 2, wherein configuring the data collection logic (34) comprises setting one or more of the following: - The protocol address of the data point used to read, write and / or execute the operation; -Reading interval; -Timeout setting; -Data conversion rules; - Parameters of data transmission from the IoT device (30, 30') to the IoT platform (50).

4. The method according to claim 2 or 3, further comprising: The IoT devices (30, 30') collect data from the industrial devices (11-16), and the IoT devices (30, 30') generate data for transmission to the IoT platform (50) based on the data collected from the industrial devices (11-16).

5. The method according to any one of claims 1 to 3, wherein the configuration information (62, 65, 68) comprises a protocol configuration, and the method further comprises: The protocol configuration is stored in the IoT device (30, 30') for use by the data collection logic (34) of the IoT device (30, 30').

6. A method according to any one of claims 1-3, wherein the device twin data (61, 64, 67) uses strongly typed definitions to model the data associated with the industrial device (11-16) and the configuration information (62, 65, 68) associated with the industrial device (11-16).

7. The method according to claim 1, wherein the data synchronization is performed via a communication channel used by the IoT device (30, 30') to retrieve the configuration information (62, 65, 68), wherein the data synchronization is a bidirectional data synchronization between the IoT device (30, 30') and the IoT platform (50).

8. The method according to any one of claims 1-3, wherein the industrial equipment (11-16) comprises equipment of an industrial automation control system, in particular equipment of a substation automation system.

9. The method according to any one of claims 1-3, wherein the IoT device (30, 30') is an IoT edge device or a gateway device.

10. An IoT device (30) for collecting data from industrial equipment (11-16), in particular power system equipment, comprising: at least one first interface (31-33) adapted to communicatively couple the IoT device (30, 30') to the industrial device (11-16); a second interface (36) adapted to communicatively couple the IoT device (30, 30') to an IoT platform (50); a memory or storage device adapted to store configuration information (62, 65, 68), the configuration information (62, 65, 68) being retrieved from device twin data (61, 64, 67) of the industrial device (11-16) stored in the IoT platform (50) via the second interface in response to establishment of a communicative coupling between the IoT device (30, 30') and the industrial device (11-16); as well as circuitry adapted to collect data from the industrial device (11-16) via the at least one first interface (31-33) according to the retrieved configuration information (62, 65, 68), wherein the IoT device (30) is configured to perform data synchronization of the device twin data (61, 64, 67) between the IoT device (30, 30') and the IoT platform (50), The IoT device (30, 30') is adapted to perform the method according to any one of claims 1 to 9.

11. An IoT platform computer system, comprising: A memory or storage device (52) adapted to store device twin data (61, 64, 67) of an industrial device (11-16), wherein the device twin data (61, 64, 67) for the industrial device (11-16) comprises configuration information (62, 65, 68) required by an Internet of Things (IoT) device (30, 30') when collecting data from the corresponding industrial device (11-16); and An interface adapted to output the configuration information (62, 65, 68) to the IoT device (30, 30') in response to establishment of a communicative coupling between the IoT device (30, 30') and the industrial device (11-16), wherein the IoT platform is configured for bidirectional data synchronization between the IoT device (30, 30') and the IoT platform, The IoT device (30, 30') is adapted to perform the method according to any one of claims 1 to 9.

12. A system comprising: The IoT device (30, 30') according to claim 10; The IoT platform (50) computer system of claim 11, the IoT platform (50) computer system being communicatively coupled to the IoT device (30, 30'); and A plurality of industrial devices (11-16) are communicatively coupled to the IoT device (30, 30'), wherein the IoT device (30, 30') is adapted to collect data from the plurality of industrial devices (11-16) based on configuration information (62, 65, 68) retrieved by the IoT device (30, 30') from the IoT platform (50) computer system.

Images