Method for integrating automated technical field devices in a distributed ledger

Abstract

This invention relates to an automation field device (FG) having an operating electronics (BE) and multiple parameters (PA1, PA2, PA3, PAn). The operating electronics (BE) is designed to operate the field device (FG) based on the parameters (PA1, PA2, PA3, ..., PAn) and to acquire or process data based on the parameters. Firmware (FW) having a software container (SC) is assigned to the operating electronics (BE). The software container (SC) is designed to execute installed code (CD) and, by means of the code (CD), establish a communication connection to a distributed ledger (DL) via a higher-level communication network through at least one of the output units (OP1, OP2) to integrate the field device (FG) into the distributed ledger (DL), process and / or combine at least a portion of the acquired or processed data into result data, and transmit the result data to the distributed ledger (DL). The invention further relates to a method for integrating a field device according to the invention into a distributed ledger (DL) designed according to distributed ledger technology.

Description

Technical Field

[0001] This invention relates to a field device with operating electronics and multiple parameters, employing automation technology. Additionally, the invention includes a method for integrating the field device according to the invention into a distributed ledger. Background Technology

[0002] Automation components used in industrial facilities are known from existing technologies. For example, field devices are used as automation components in process automation and manufacturing automation technologies. Generally, field devices refer to all process-oriented devices that provide or process process-related information. Therefore, field devices are used to detect and / or influence process variables. Measuring devices or sensors are used to detect process variables. These devices are used for, for example, pressure and temperature measurements, conductivity measurements, flow rate measurements, pH measurements, fill level measurements, etc., and capture the corresponding process variables such as pressure, temperature, conductivity, pH value, fill level, flow rate, etc. Actuators are used to influence process variables. For example, these devices are pumps or valves that can affect the flow rate of fluid in a pipeline or the fill level in a tank. In addition to the aforementioned field devices, automation components should also be understood to include gateways, edge devices, remote I / O, radio adapters, or, in general, devices deployed at the field level.

[0003] Various types of field equipment are manufactured and sold by the Swiss Endershaus Group.

[0004] In modern industrial facilities, field devices are typically connected via communication networks, such as fieldbuses. Fieldbus, These higher-level units (such as SPCs, PLCs, etc.) connect to higher-level units. Typically, these higher-level units are control or control systems, such as SPCs (Stored Programmable Controllers) or PLCs (Programmable Logic Controllers). Higher-level units are used for process control, process visualization, process monitoring, and commissioning of field devices. Measured values ​​acquired by field devices—especially sensors—are transmitted to one or more higher-level units via a connected bus system. Additionally, data transfer from higher-level units to field devices is also required via the bus system—particularly for configuring and parameterizing field devices, and for controlling actuators.

[0005] Custody and transfer systems are specifically used in the oil and gas industry and for the trading and transport of materials between two operators. Such systems comprise one or more automated components for capturing the quantity of the physical material being transported and for storing the transaction data. All transactions must be executed and recorded in a tamper-proof and impeccable manner. The automated components, particularly the field equipment, must be calibrated and certified by an authoritative body in this regard.

[0006] Databases based on so-called DLT (Distributed Ledger Technology), implemented via the internet or local networks, can be used for secure recording of transactions. Distributed ledger technology allows all data stored in the database to be stored across multiple networked participant nodes. The total number of all unique data entries is called the "ledger." With appropriate measures, it is ensured that new transactions to be added are taken over in all copies of the ledger, and that all participant nodes reach a consensus on the current state of the ledger. Known examples of such DLTs are "blockchain," "blockDAG," or "TDAG."

[0007] If you want to integrate a network-connected field device into a specific DLT environment (such as the environment of a trading partner, metrology board, or government agency), you must add DLT environment-specific components (such as code or hardware) to the field device.

[0008] However, only the developers of the field devices can load the software components needed to integrate the field devices into the distributed ledger. Customers cannot provide their own DLT code for the field devices. Nor can they select specific data points provided by the field devices and put them into the distributed ledger (such as process variables, configuration / status information, etc.). Therefore, it is not possible to quickly integrate field devices into the distributed ledger. Summary of the Invention

[0009] This invention is based on the goal of integrating field devices into a distributed ledger in a simple manner.

[0010] This objective is achieved through a field device with operating electronics and multiple parameters, wherein the operating electronics are configured to operate the field device based on the parameters and to collect or process data based on the parameters, and wherein the operating electronics are assigned firmware with a software container, the software container comprising:

[0011] - A limited number of input units, used to acquire or process data based on parameters of field devices;

[0012] - A limited number of outputs corresponding to the communication channels of the measuring equipment, wherein the communication channels for connecting field devices are designed with higher-level communication networks, such as the Internet or local networks;

[0013] -A specific amount of reserved memory space in the electronic device unit is used to install code;

[0014] -A specific amount of reserved main memory in the electronic device unit required to execute the installed code;

[0015] - A specific amount of processor runtime is reserved for the electronic device unit to execute the installed code;

[0016] The software container is configured to: execute installed code and, by means of the code, establish a communication link to the distributed ledger via a higher-level communication network through at least one of the outputs, integrate field devices into the distributed ledger, process and / or combine at least a portion of the collected or processed data into result data, and transmit the result data to the distributed ledger.

[0017] The field devices according to the present invention can be easily and quickly integrated into any distributed ledger. A distributed ledger refers to a database configured according to distributed ledger technology, existing across multiple locations or multiple participant nodes. To this end, the firmware of the field device is updated to include a specific software container. The software container can execute code for integrating the field device into the distributed ledger, data processing, and data transfer to the distributed ledger, while keeping the resources of the electronic device unit available for these tasks. The code can be freely selected for any distributed ledger, including those from third-party providers. The code can be rewritten as needed.

[0018] Field devices mentioned in connection with the method according to the invention have been given as examples in the introductory section of this description. For example, field devices related to the invention are used in storage and transfer systems. However, it should be understood that field devices can be used in any use case in other industries.

[0019] According to an advantageous embodiment of the field device of the invention, the field device is a measuring device having at least one sensor unit for collecting physical raw measurement variables of a process engineering process, a network device, particularly a gateway, remote I / O, a switch or edge device, or a control unit, particularly a control unit. Further examples of field devices have been set forth in the introductory section of this description.

[0020] According to an advantageous embodiment of the field device of the present invention, the data collected or processed based on parameters is at least one of the following:

[0021] - The raw measurement variables acquired by the sensor unit;

[0022] - Measured values ​​formed from the original measurement variables and other variables, such as the volume transferred or calculated within a defined time interval;

[0023] - Status information, especially status information corresponding to NAMUR recommendations; and

[0024] - Diagnostic data, especially heart rate data.

[0025] It goes without saying that all data generated by field devices, even data not listed in this article, can be loaded into the distributed ledger.

[0026] According to an advantageous embodiment of the field device according to the invention, the specified code has a network address of the distributed ledger and a login routine for the distributed ledger. In addition to access data (e.g., username and password), the login routine also contains specific information about how the field device must behave in the distributed ledger, such as the frequency data of the distributed ledger that it can transmit, whether the field device forms an active participant node (e.g., to verify transactions of other field devices), whether the field device stores at least a portion of the distributed ledger, etc.

[0027] Furthermore, the objective is achieved by a method for incorporating field devices according to the invention into a distributed ledger designed, in particular, according to blockchain, block DAG, or TDAG, the method comprising:

[0028] - Install the software code loaded into the field device within a software container;

[0029] - Process or combine data from at least one of the input sections into result data;

[0030] - Establish a communication link to the distributed ledger via a higher-level communication network through at least one of the outputs; and

[0031] - The result data is transmitted to the distributed ledger via at least one of the outputs.

[0032] The method according to the invention enables the integration of field devices into a distributed ledger without rewriting the firmware of the field devices (in the sense of adaptation, recompilation, and installation) during each integration process.

[0033] According to an advantageous variant of the field device according to the invention, the field device is integrated into the distributed ledger after a communication connection with the distributed ledger is initially established according to the code. For this purpose, the aforementioned login routine, which is part of the code, is used.

[0034] According to an advantageous variant of the field device according to the invention, after integration into a distributed ledger, the field device functions as a participant node, particularly as a light node. A light node is characterized by storing a portion of the data in the entire ledger. However, a light node must be connected to a full node to ensure the accuracy of the stored data. In some cases, where performance is suitable, a field device can also be designed as a full node, thus participating in the verification of current transactions of other participants and also being able to store the complete ledger. The precise attributes and tasks of light nodes or full nodes vary depending on the corresponding type of digital ledger technology, as can be seen in the relevant specifications. The necessary resources of the electronic device unit used to perform these tasks are protected from interference by a software container.

[0035] In an advantageous variant of the field device according to the invention, the specified code is created by the user and loaded into the field device. For this purpose, the field device has an interface, for example, a wireless interface for communication via a wireless protocol, such as WiFi or Bluetooth LE, or a wired interface for communication via a fieldbus network or Ethernet network.

[0036] According to an advantageous variant of the field device according to the invention, the field device is specified to download codes from a database via the Internet or a higher-level communication network. In those cases where the database provides the field device with a list of downloadable codes, loading is initiated by the database itself, for example by a suitable code in the database selected by the user, or by a selection made by the user on the field device, for example by a selection on the display / operation element of the field device, such as a (touch) display. Attached Figure Description

[0037] The invention will be explained in more detail with reference to the accompanying drawings. The drawings are shown below:

[0038] Figure 1 An exemplary embodiment of the method according to the present invention is shown. Detailed Implementation

[0039] Figure 1An automated field device FG is illustrated, in this example a flow meter. However, the present invention can be applied to any type of field device FG. In addition to the measurement sensor system, the field device FG also has operating electronics BE, which includes non-volatile memory, main memory, and a microprocessor. The operation of the field device FG via the operating electronics BE is controlled by firmware FW. In this invention, the field device FG has dedicated firmware FW including a software container. The software container reserves a portion of the resources of the operating electronics BE, namely, a certain amount of reserved memory space SP for installing the code CD, a specific amount of reserved main memory AS of the operating electronics BE required to execute the installed code CD, and a certain amount of processor runtime for executing the code CD. This dedicated firmware FW is initially loaded during the manufacture of the field device FG, or the operator may rewrite the initial firmware of the field device FG at a later time using the dedicated firmware FW.

[0040] Field devices can be incorporated into the distributed ledger (DL) using dedicated firmware (FW), or more precisely, using software containers (CT).

[0041] First, the code CD is loaded into the software container CT on the field device FG. The code CD is used for subsequent connections from the field device FG to the distributed ledger DL, as well as for data preprocessing and transfer to the distributed ledger DL. In step 1.a), the field device FG downloads code from a database DB, for example, the device manufacturer's cloud-based database. For this purpose, the operator BD selects suitable code for the distributed ledger DL from the database DB. Alternatively, the operator BD generates the code CD itself in step 1.b). In step 2.), the code is loaded into the dedicated storage SP of the software container CT.

[0042] The field device FG has multiple parameters PA1, PA2, PA3, ..., PAn. These parameters PA1, PA2, PA3, ..., PAn define which data the field device FG collects or processes. This data is particularly process values, status information, or diagnostic data. The software container CT provides a limited set of inputs. A subset of parameters PA1, PA2, PA3, ..., PAn is mapped to inputs IN. Assignments occur via the configuration menu available in the FG. The code CD here defines which data is read based on which parameters PA1, PA2, PA3, ..., PAn. In the third method step, the data from the field device FG is read in based on parameters PA1 and PA3 via the corresponding assigned inputs IN. The code CD cannot directly access parameters PA1, PA2, PA3, ..., PAn here, but can only access the inputs. Then, in method step 4.), this data is processed or combined to form the result data.

[0043] After executing the code CD, the field device FG establishes a connection to the distributed ledger DL via a higher-level communication network, such as the Internet or a local area network. The field device FG has multiple interfaces or outputs OP1, OP2. In this case, output OP1 is provided for connecting to a fieldbus network through which the field device periodically transmits its data. With the help of output OP2, a connection to the distributed ledger DL is established via the higher-level communication network. For this purpose, the code CD contains login information and the address of the distributed ledger DL. It can be specified that the distributed ledger DL then transmits other software components to the field device FG, for example, when the field device FG continues to function as a light node in the distributed ledger DL. These additional software components are also stored in dedicated memory SP and executed by a software container.

[0044] In step 5.), the result data is routed to the output section OP2. The result data is then transmitted to the Distributed Ledger DL, verified according to the Distributed Ledger DL standard, and stored in the Distributed Ledger DL.

[0045] If the operator (BD) wishes to use a different distributed ledger (DL), it can load a new code CD according to steps 1.) and 2.) to replace the old code. Alternatively, multiple code CDs may be loaded, allowing the field device (FG) to function as a participant node in various distributed ledger DLs via various additional outputs.

[0046] List of reference numerals

[0047] 1.), ..., 6.) Method steps

[0048] AS Reserved Main Memory

[0049] BE operating electronic devices

[0050] BN users

[0051] CD Code

[0052] CT software container

[0053] DB further database

[0054] DL Distributed Ledger

[0055] FG Field Equipment

[0056] FW firmware

[0057] IN Input Section

[0058] OP1 and OP2 output sections

[0059] PA1, PA2, PA3, ..., PAn parameters

[0060] PL reserves processor runtime

[0061] SP Reserved Memory Space

Claims

1. A field device (FG) for automation technology, said field device having operating electronics (BE) and multiple parameters (PA1, PA2, PA3, ..., PAn), wherein, The operating electronics (BE) is configured to operate the field device (FG) based on the parameters (PA1, PA2, PA3, ..., PAn) and to collect or process data based on the parameters, wherein firmware (FW) with a software container (SC) is assigned to the operating electronics (BE), wherein the software container (SC) includes: - A limited number of input units (IN) for acquiring or processing the data collected or processed according to the parameters (PA1, PA2, PA3, ..., PAn) of the field device (FG); - A limited number of outputs (OP1, OP2) corresponding to the communication channel of the field device, wherein the communication channel is designed to connect the field device (FG) to a higher-level communication network; - A specific amount of reserved memory space (SP) in the operating electronics (BE) is reserved for code (CD) installation; - A specific amount of reserved main memory (AS) in the operating electronics (BE) required to execute the installed code (CD); - A specific amount of processor runtime (PL) reserved for the operating electronics (BE) to execute the installed code (CD); The software container (SC) is designed to: execute installed code (CD) and, by means of the code (CD), establish a communication link to the distributed ledger (DL) via the higher-level communication network through at least one of the output units (OP1, OP2), integrate the field device (FG) into the distributed ledger (DL), process and / or combine at least a portion of the collected or processed data into result data, and transmit the result data to the distributed ledger (DL). The code (CD) has a network address of the distributed ledger (DL) and a login routine for the distributed ledger (DL). The login routine contains specific information about how the field device must behave in the distributed ledger, including: the ability to transmit frequency data of the distributed ledger, whether the field device forms an active participant node, and whether the field device stores at least a portion of the distributed ledger.

2. The field device (FG) according to claim 1, wherein, The field device (FG) is a measuring device having at least one sensor unit for acquiring physical raw measurement variables of a process engineering process, network device, remote I / O, switch or edge device, or control unit.

3. The field device (FG) according to claim 2, wherein, The network device is a gateway.

4. The field device (FG) according to claim 2, wherein, The data collected or processed according to the parameters (PA1, PA2, PA3, ..., PAn) is at least one of the following: - The raw measurement variables acquired by the at least one sensor unit; - The measured values ​​formed from the original measurement variables; - Status information; and - Diagnostic data.

5. The field device (FG) according to claim 4, wherein, The status information corresponds to the NAMUR recommendations.

6. The field device (FG) according to claim 4, wherein, The diagnostic data is heart rate data.

7. A method for incorporating a field device (FG) according to any one of claims 1 to 6 into a distributed ledger (DL), the method comprising: - Install the code (CD) loaded into the field device (FG) in the software container (SC); - Process or combine data from at least one of the input units (IN) into result data; - A communication link to the distributed ledger (DL) is established via a higher-level communication network through at least one of the output units (OP1, OP2); and - The result data is transmitted to the distributed ledger (DL) via at least one of the output units (OP1, OP2), wherein, The code (CD) has the network address of the distributed ledger (DL) and a login routine for the distributed ledger (DL), wherein the login routine contains specific information about how the field device must behave in the distributed ledger, relating to: the ability to transmit frequency data of the distributed ledger, whether the field device forms an active participant node, and whether the field device stores at least a portion of the distributed ledger.

8. The method according to claim 7, wherein, The distributed ledger (DL) is designed based on blockchain, blockDAG, or TDAG.

9. The method according to claim 7, wherein, The field device (FG) is integrated into the distributed ledger (DL) after it first establishes a communication connection with the distributed ledger (DL) according to the code (CD).

10. The method according to claim 9, wherein, After being integrated into the distributed ledger (DL), the field device (FG) functions as a participant node.

11. The method according to claim 10, wherein, After being integrated into the distributed ledger (DL), the field device (FG) functions as a light node.

12. The method according to any one of claims 9 to 11, wherein, The code (CD) is created by the user (BN) and loaded into the field device (FG).

13. The method according to any one of claims 9 to 11, wherein, The field device (FG) downloads the code (CD) from the database (DB) via the Internet or the higher-level communication network.

Images