METHOD FOR OPERATING A DEVICE IN AN IOT SYSTEM

Description

[0001] Method for operating a device in an IoT system The invention relates to a method for operating a device, hereinafter referred to as a field device, in a system with an IoT platform.

[0002] A wide variety of field devices are now connected to an IT infrastructure, commonly referred to as the cloud, for example to enable control or monitoring of the field device, or to read out data recorded by it for any analysis. This is done via an IoT platform, which, similar to an operating system, enables access to the field device and bidirectional communication. From the document US 2018 / 026840 A1, a platform-to-platform communication architecture for a process control messaging service in a process control system or other industrial environment is known, which enables communication between field devices and an IoT platform. The document US 2020 / 103844 A1 describes a system and method for configuring a plurality of field devices, wherein the system and method provide a single application or a single utility thatthat allows a user to view, make, and modify configuration changes. US 2015 / 046125 A1 describes a method for operating a field device.

[0003] Operating the field device also includes its commissioning with the initial connection of the field device to the IoT platform, also referred to as field device connection or IoT integration.

[0004] An example of an IoT system with at least one field device includes an energy management system for a building or industrial site. Typically, the building contains many field devices, grouped into systems. These systems can include heat pumps, photovoltaic systems, electric charging stations, and / or accumulators commonly referred to as batteries. The energy management system can calculate an optimal "schedule" for energy generation / supply and consumption. To do so, it requires data from the systems or field devices, which can be obtained from a data sheet for the field device, such as the maximum charging and discharging power of the battery and its capacity. Furthermore, the energy management system requires information about the current state of the energy system; for this, it must read data collected by the field device. Furthermore, it must control the systems during operation to optimize the energy supply.

[0005] The systems or field devices must therefore be connected to the energy management system. In particular, additional field devices are usually connected, i.e., integrated, into an existing energy management system with already connected field devices. Given the current state of the art, this is complex, time-consuming, and error-prone, as can be illustrated by the example of a battery: someone on-site must identify the manufacturer and type of battery and obtain the corresponding data sheet. They must then use the data sheet to research which protocol can be used to access the battery (e.g., Modbus, BACNet, etc.). Furthermore, it is necessary to determine which measured values ​​or data (e.g., the battery's state of charge) are located in which registers, in which unit / format, and via which registers the battery can be controlled (e.g., its charging or discharging power).All of this data is then typically entered into a corresponding form / mask / UI at a terminal; only then is the connection of the additional field device possible.

[0006] If the additional field device is operated after the connection, it is exposed to aging processes and sources of error that can potentially lead to the failure of an entire system.

[0007] The object of the invention is to simplify the connection of another field device to an IoT platform, to reduce the susceptibility to errors and to improve its further operation.

[0008] These objects are achieved by a method having the features of patent claim 1 and a system having the features of patent claim 13.

[0009] Advantageous embodiments of the invention are specified in the subclaims.

[0010] The invention provides for the use of a database in which the data necessary for connecting a field device (hereinafter referred to as connectivity data) is stored, each with an associated device ID, and which the IoT platform can access. The device ID is used to identify a field device. The database comprises both device IDs and connectivity data of field devices that are connected to the IoT platform, as well as a device ID and connectivity data of at least one other field device, i.e. a field device that is not yet connected to the IoT platform. The method provides for only sending a device ID of the other field device to the IoT platform. This is compared with the device IDs stored in the database, and if there is a match, the connectivity data associated with the device ID is transmitted to the IoT platform.In particular, a comparison is made to determine whether the device ID of the additional field device matches the device ID of another field device whose data is stored in the database as described above. If this is the case, the connection between the additional field device and the IoT platform can be established using the transmitted connectivity data of the associated other field device, since the connectivity data of the other field device is relevant for connecting the additional field device. The additional field device to be connected can also be of the same type as an already connected field device and have the same device ID. In this case, after comparing the device IDs, the connectivity data of the associated field device is transmitted and used to connect the additional field device.

[0011] Further device data from the additional field device is transmitted to the IoT platform – particularly during the continued operation of the additional field device or system – and stored in the database with the associated device ID. This enables continuous learning and expansion of the database and the IoT platform. The additional device data from the additional field device and, if applicable, other field devices connected to the IoT platform are evaluated, and based on the evaluation, a signal is output to control and / or regulate the additional field device and / or other field devices or systems directly or indirectly connected to the IoT platform.

[0012] If the transmitted device ID of the additional field device is not present in the database, the device ID is saved in the database. Furthermore, the connectivity data is requested; for example, the IoT platform sends a request to another database or to the user of the additional field device or system. Once received and saved in the database, the connection is possible as described.

[0013] If the transmitted device ID of the additional field device is present in the database, but no associated connectivity data is available, the connectivity data is requested and stored as above. The method according to the invention and / or one or more functions, features, and / or steps of the method according to the invention and / or one of its embodiments can be computer-assisted.

[0014] The present invention has the advantage, for example, that the time and costs required for connecting devices to the cloud can be reduced. Furthermore, the method according to the invention is less error-prone. In particular, additional applications, such as energy management systems, can be commissioned significantly more efficiently. Furthermore, the transmitted / stored data is accessible for data analysis, allowing additional error sources and / or savings potential to be identified and utilized.

[0015] In particular, the method according to the invention enables an efficient connection of devices (or edge devices) to an IOT platform, an extension of the database with data from the field, which is then fed back to the database via the then connected IOT platform, and a categorization of the data, e.g. according to abstracted classes that are easily recognizable for the technician.

[0016] The device ID does not identify the individual field device or individual additional field device, but rather its type, preferably including all details relevant to its use (e.g., manufacturer, series, production date, and more). According to one embodiment, an image of the additional field device or a part of the additional field device, for example, a label, is transmitted as the device ID. The device ID can also be a barcode or a QR code, or the product name, possibly in conjunction with the manufacturer's name.

[0017] This advantageously enables identification of the additional field device, especially in the case of unknown connectivity data.

[0018] According to one embodiment, the connectivity data includes information about a port, a protocol, a register, and / or an abstract generic device model.

[0019] This advantageously allows for improved determination of the connectivity data required for connecting the additional field device.

[0020] Preferably, the IoT platform requests additional device data, which is also stored. For example, the IoT platform can request an on-site technician / user to enter this additional data. After this user input, the entered data is transmitted to the IoT platform. In particular, the IoT platform recognizes which data is missing or is particularly important for establishing the connection. The user is thus not prompted to enter fixed or all additional device data, but only to enter data that is useful in the aforementioned sense.

[0021] An AI method / algorithm, and thus a neural network, can be used to compare the device ID of the additional field device with device IDs stored in the database. This is particularly advantageous when an image is used as the device ID. The image can preferably be captured using a smartphone. The neural network (AI) is trained accordingly using known images of known systems. For example, training can be carried out using various photos / images of field devices from different manufacturers. This advantageously enables cross-manufacturer recognition / connection. In other words, an image of the additional field device is captured and transmitted to the IoT platform, whereupon the neural network recognizes the additional field device, determines the associated connectivity data, and then transmits it.

[0022] As additional device data, position data of the other field device, in particular GPS coordinates of its installation location, can be transmitted to the IoT platform and stored. Based on this position data, a link can then be established with external position-specific data (e.g., climate or weather). Furthermore, a probabilistic prediction or simulation regarding a service life or the cause of failure can be derived from the link or from the external position-specific data.

[0023] Alternatively or additionally, operating data recorded during operation of the additional field device can be transmitted and stored as additional device data. It is also advantageous to subsequently update this operating data, preferably regularly / continuously, during operation of the additional field device. This enables continuous monitoring and / or analysis of the temporal development of parameters or other data analyses.

[0024] Alternatively or additionally, a categorization of devices whose device IDs are stored in the database can be created. For this purpose, an abstract description of device categories can be created (e.g., a heat pump or a heat pump with a power-controlled compressor). This allows the initially available data as well as additional data collected from the field (additional device data) to be stored in a structured manner, processed in a structured manner, and made accessible for further data analysis. For example, the performance, aging, etc. of a field device can be analyzed depending on location, weather influences, and / or other parameters.

[0025] The invention is explained in more detail below using exemplary embodiments and the figures. Figure 1a schematic representation of an IoT system according to an embodiment of the present invention; and Figure 2 a flow chart of the method according to the invention.

[0026] Fig.1 shows an IoT system with an IoT platform 1 and an energy management system 6, which includes, among other things, a battery 2 as an additional field device. The battery 2 has a device ID 3 in the form of a QR code. As a field device, the energy management system 6 has a photovoltaic system 7, which is already connected to the IoT platform and can charge the battery 2. The IoT platform 1 can access a database 4 in which device IDs of the PV system and the device IDs of several batteries as other field devices are stored, each with associated connectivity data. The database can store multiple device IDs for a field device, if necessary. Furthermore, a terminal 5 connected to the IoT platform is present.

[0027] To the Figure 1To establish the connection shown between the additional field device 2 and the IoT platform 1 and thereby connect the additional field device, the Figure 2 The steps shown are carried out.

[0028] In step 10, a device ID, here QR code 3, is entered at terminal 5, for example by a technician uploading the image of QR code 3 to the IoT platform via a user interface.

[0029] In step 11, the device ID 3 is sent from the IoT platform to the database 4, which checks whether the device ID exists and whether connectivity data associated with the device ID is stored. If both are confirmed, the connectivity data, in particular the protocol used, registers, and other required parameters, are transmitted to the IoT platform in step 12, and the IoT platform uses this connectivity data to establish the connection with the additional field device 2 (step 13). Otherwise, the user is prompted to enter the required connectivity data at the terminal (step 14). This data is saved and assigned to the device ID. If the device ID is not present in the database, a corresponding new data record is created and the device ID is saved (step 15). In each of these cases, the connection to the additional field device is then established (step 13).

[0030] Once the connection is established, the battery 2 transmits additional device data to the IoT platform (step 20), such as its current charge level. The photovoltaic system also transmits additional device data, such as key data such as its location and / or operating data such as its current power output. The additional device data is evaluated, and a derived signal is generated (step 21), which can be used to control and / or regulate the battery or any field device directly or indirectly connected to the IoT platform. Furthermore, the additional device data is stored in the database.

[0031] In the example described, the battery's aging or efficiency can be determined from transmitted operating data (e.g., the required charging time or the achieved capacity) over a certain period of time. This analysis of the operating data can be used to control the charging process by the PV system, or a signal can be issued indicating maintenance measures or the need to replace the battery due to aging.

[0032] For example, the temperature dependence of the efficiency of the solar cells can be determined from the operating data of the PV system, such as temperature and power. Position data can be used to determine future weather conditions and thus the expected power output. Such an analysis enables the control of the battery charging process and / or the control of loads in the energy management system.

[0033] By transmitting additional device data to the IoT platform, which is stored in the database, a variety of different evaluations are possible. For example, a probabilistic distribution for the coefficient of performance (COP) or another parameter of a heat pump from a specific manufacturer and type can be calculated as a preferred evaluation. This information can be made available to other applications, such as an energy management system or another production optimization system, to enable improved system control with an initial configuration or parameterization.

Claims

1. Method for operating a further field device in a system containing an IoT platform that has access to a database, wherein the database stores a device ID identifying the device type and connectivity data for at least one field device linked to the IoT platform and a device ID identifying the device type and connectivity data of another field device, having the following steps: i. transferring a device ID (3), identifying the device type, of the further field device to the IoT platform (1), ii. comparing the device ID (3) of the further field device with device IDs of the field devices and the other field devices that are stored in the database (4), iii. if the device ID of the further field device matches a device ID stored in the database (4): transferring the connectivity data related to the device ID of the further field device (3) to the IoT platform (1), - making a connection between the further field device (2) and the IoT platform (1) by using the transferred connectivity data, - transferring further device data of the further field device (2) to the IoT platform (1) and storing the further device data of the further field device in association with the device ID in the database (4), - evaluating the further device data of the further field device (2) and / or of other devices (7) connected to the IoT platform (1), - outputting a signal, which is based on the evaluation, for operating the further field device (2) and / or other devices (7) directly or indirectly connected to the IoT platform.

2. Method according to Claim 1, characterized in that the connectivity data contain information about a port, a protocol, a register and / or an abstract generic device model.

3. Method according to either of the preceding claims, characterized in that after step ii) the connectivity data pertaining to the device ID of the further field device (3) are requested by the IoT platform if they are not stored in the database (4), and the received connectivity data and optionally the device ID are stored in the database (4).

4. Method according to one of the preceding claims, characterized in that the IoT platform (1) requests the further device data via a connected terminal (5).

5. Method according to one of the preceding claims, characterized in that a neural network is used for comparing the device ID of the further field device (2) with device IDs stored in the database.

6. Method according to one of the preceding claims, characterized in that the device ID (3) transferred is an image of the field device (2) or of a part of the field device.

7. Method according to one of the preceding claims, characterized in that the further device data stored are position data of the further field device (2), in particular GPS coordinates of its installation location.

8. Method according to Claim 7, characterized in that the position data are used to perform a logic combination with external position-specific data.

9. Method according to Claim 8, characterized in that the logic combination or the external position-specific data is / are used to infer a probabilistic statement / simulation with regard to service life or a cause of damage.

10. Method according to one of the preceding claims, characterized in that the further device data stored are operating data acquired during operation of the field device (2).

11. Method according to the preceding claim, characterized in that the operating data are regularly / continually updated during operation of the further field device (2).

12. Method according to one of the preceding claims, characterized in that a categorization of the field devices whose device IDs are stored in the database is produced.

13. System containing an IoT platform (1) that has access to a database (4), and at least one further field device (2), for carrying out the method according to one of Claims 1 - 11.