Intelligent field device proxy
By introducing a field device agent to process data from front-end devices and communicate with the server, the problems of complexity and high power consumption of field devices are solved, achieving a low-cost, low-energy-consumption, and highly secure device design.
Patent Information
- Application Number
- CN202610581051.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2025-05-06
- Filing Date
- 2026-04-29
- Publication Date
- 2026-11-06
AI Technical Summary
The complexity and high power consumption of field equipment, coupled with the need for frequent updates, lead to increased equipment costs and energy consumption.
A field device agent is introduced, including first and second interfaces, a virtualization module, a converter component, and an update component, to process data from the front-end device and communicate with the server, reducing the complexity of the front-end device and the need for updates.
Significantly reduce the complexity and power consumption of front-end devices, enabling low-cost, low-power device designs while improving security and flexibility.
Smart Images
Figure CN123048100A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of field devices, and more particularly to an intelligent field device agent. The invention also relates to a field device system and its applications. Background Technology
[0002] In many cases, field devices typically include not only front-end sensors but also a large number of additional logic components (e.g., for processing data from the front-end sensors, for diagnostic components, for supporting advanced protocols) and / or more components. This not only increases the complexity of the field device (e.g., resulting in hundreds of thousands of lines of code) but also increases its power consumption and / or requires regular updates to the field device's code. Therefore, components designed to reduce the complexity of field devices are essential. Summary of the Invention
[0003] The purpose of this disclosure is to provide a field device with reduced complexity.
[0004] This objective is achieved through the subject matter of the independent claims. Further embodiments will become apparent from the dependent claims and the following description.
[0005] One aspect relates to a field device agent for transforming values from a front-end device and sending them to a server, wherein the front-end device does not have components for function updates. The field device agent includes: a first interface supporting a first communication line between the field device agent and the front-end device; a second interface supporting a second communication line between the field device agent and the server; and a virtualization module. The virtualization module includes a sandbox component, a converter component, and an update component.
[0006] By providing this field device proxy, the complexity of the front-end device can be significantly reduced. Therefore, the front-end device can contain only the sensor, an ADC (analog-to-digital converter) that converts the sensor's analog values into digital values, and components for supporting the protocol for transmitting the digital values. Due to its simplicity (or: reduced complexity), the front-end device does not have components for function updates. In other words, nothing inside the front-end device—specifically, any entries in its memory—can be changed during operation. The only exception might be updates performed upon initial installation of the front-end device, such as programming WORM (Write-once, Read-Many) memory, which may contain, for example, the front-end device's serial number, MAC address, etc. "Function updates" that are not permitted or even impossible can include updates for: correcting the transformed digital values of the sensor (e.g., to compensate for aging effects), changing the specific details of the transmission protocol, removing bugs in the front-end device's firmware, etc. The lack of components for function updates does not preclude "write" commands to the front-end device, for example, to request data transfer.
[0007] It should be noted that the following description of field device agents primarily refers to front-end devices that include sensors. However, another embodiment of the front-end device may include an actuator. Most of the considerations below can be applied in a similar or analogous manner to such an "actuator front-end device".
[0008] A field device agent is an "intermediate" device between the front-end device and the server. For example, the server can be a PLC (Programmable Logic Controller) or other type of control device in an industrial automation factory. The server can be a PC, an enterprise computer, and / or part of the so-called "cloud." The field device agent can be a standalone device or can be integrated into the server. Typically, the field device agent is physically separate from the front-end device.
[0009] The communication components between the field device agent and the front-end device typically support simple communication methods (e.g., a simple serial bus), but are not limited to this. The first interface of the field device agent supports a first communication line (or communication component) between the field device agent and the front-end device. Essentially, the first interface of the field device agent can support multiple protocols for selection by both the front-end device and the field device agent. In some embodiments, the first interface can be designed as an adaptive interface, allowing at least some protocols to be selected automatically. The first interface can be configured to receive digital values (e.g., measurements) from the front-end device. Furthermore, the first interface can also be configured to send "request" (e.g., data request) commands to the front-end device. For example, the communication line can be protected by encryption components. The first interface may include a first buffer for receiving data from the first communication line.
[0010] The field device agent also includes a second interface. This second interface supports a second communication line between the field device agent and the server. The second interface may include a second buffer (“back-end buffer”). The second interface may support or be configured to support advanced protocols such as OPC UA (Open Platform Unified Communication Architecture).
[0011] Field device agents include virtualization modules. If multiple front-end devices are connected to a field device agent, the agent can include multiple isolated virtualization modules. "Isolation" can include logical isolation between virtualization modules. To ensure isolation between virtualization modules, each module can include a sandbox component. Virtualization functionality within a virtualization module can be accomplished by a so-called "Platform as a Service (PaaS)" component, such as Docker software, which provides so-called "containers" that are isolated from each other and bundle their own software, libraries, and configuration files. Host resources (e.g., CPU, memory, network access) are available to all device agents. Containers can communicate through well-defined channels. Each device agent can be addressed via its own IP address. Isolation between virtualization modules can, for example, provide the advantage that the impact of an error is limited to the container where the error occurred. Additional virtual networks can be configured within the host, through which device agents can communicate. This makes it possible to centralize functions such as PROFINET communication. This is not mandatory. Each container can also be implemented independently, or a hybrid approach can be used.
[0012] The field device agent includes a converter component that can be configured to transform a digital value from a first interface into a value and protocol that a second interface can evaluate. For example, when a front-end device is configured to perform temperature measurement using a PTC (Positive Temperature Coefficient) sensor (e.g., a "Pt100" sensor), the front-end device's ADC can send the digital value "130.3" (e.g., ohms) to the first interface of the field device agent. The converter component can then transform this digital value into a digital temperature value of 78.5°C, allowing the second interface to send this value, along with any additional values required and / or useful by the server, to the server.
[0013] The field device agent includes an update component. This update component can support all functional updates that the front-end device cannot perform, such as bug fixes and adaptations.
[0014] This approach provides a simplified component for a field device (more precisely, a front-end device) by offloading all the complexity of the field device to a field device agent. Therefore, a "field device" includes both the front-end device and the field device agent. The front-end device is intentionally designed to be inflexible and has very few components. Thus, the front-end device can be a low-cost, low-power device. Furthermore, since the front-end device lacks components for feature updates, this concept can serve as the basis for a highly secure field device. To achieve a complete security concept, more components may be required.
[0015] In various embodiments, the virtualization module further includes at least one of the following: an encryption machine; a protocol engine; a data processing unit; a data analysis unit; a data storage unit for measuring and diagnosing measurements; an access control unit; a self-diagnostic unit; and / or a process diagnostic unit. The self-diagnostic unit can construct and / or check checksums or CRC (Cyclic Redundancy Check) for checking data integrity. Alternatively, device health status can be constituted by additional auxiliary measurements performed by the front-end device (and triggered by the field device agent). For example, this helps improve effective signal noise, effective signal amplitude, and / or effective jitter, etc. The term "effective" can be interpreted as what is provided at the output of the field device agent. For this purpose, the process diagnostic unit can analyze primary and secondary measurements from the front-end device to detect process conditions, such as detecting bubbles in flowing fluid in a pipe by detecting density transients, or detecting foam on a fluid in a tank. This may result in a weakened reflected signal from the laser beam, for example, the laser beam may be directed downwards from the top of the tank onto the fluid to be measured.
[0016] In various embodiments, the first communication line is a secure communication line. This can ensure or improve the data integrity of the first communication line.
[0017] In various embodiments, the front-end device is configured to send values to a field device agent periodically and / or on demand. The frequency of periodic sending can be determined at the manufacturing plant or during initial installation. When on-demand value sending is permitted, the communication line (and / or protocol) may enable bidirectional communication, but no changes to anything (e.g., memory entries in the front-end device) are permitted through this bidirectional communication.
[0018] In various embodiments, the transmission frequency has an upper and / or lower limit. The upper and / or lower limits can be applied to periodic transmission, for example, to determine traffic volume in a precise manner. The upper and / or lower limits can also be applied to on-demand transmission. In this case, the selection of the upper limit (i.e., the maximum frequency) can avoid DDoS attacks and / or consider another criterion. The selection of the lower limit (i.e., the minimum frequency) can implement a "stay-on" function.
[0019] In various embodiments, the first communication line and / or the second communication line may be wired and / or wireless.
[0020] In some embodiments, the first communication line and the second communication line may be implemented as a single line, for example, by using Ethernet APL.
[0021] In various embodiments, the first communication line supports at least one of the following protocols: Highway Addressable Remote Sensor (HART) protocol; Modbus protocol; Message Queuing Telemetry Transport (MQTT) protocol; (simple) serial bus protocols, such as RS-232, DALI, SPI, CAN bus, I... 2 C, UNI / O, 1-Wire; or proprietary protocols. Field device agents can support multiple protocols.
[0022] In various embodiments, the field device agent is physically separated from the front-end device. In these embodiments, the field device agent may operate on higher-performance and / or higher-energy-demand equipment. The field device agent may be connected to a conventional energy network, while the front-end device may not be connected to a conventional energy network and may even be an autonomous device.
[0023] In various embodiments, the field device agent is physically integrated into the server device. This can be particularly advantageous in industrial plant scenarios, as the server can be integrated into the controller device, for example, into a PLC.
[0024] In various embodiments, the second interface is configured to support at least one of the following: Open Platform Communication Unified Architecture (OPC UA), PROFINET protocol, any Ethernet and / or IP protocol, or Modbus protocol.
[0025] One aspect relates to a field device system, which includes a front-end device and a field device agent according to any one of the preceding claims.
[0026] In some embodiments, the front-end device is one of the following: a temperature measuring device; a fill level measuring device; a flow measuring device; a pressure measuring device; or a pH or conductivity measuring device. Alternatively, the front-end device may not be a measuring front-end, but may only be used to forward values received, for example, via a communication component (e.g., Bluetooth).
[0027] In various embodiments, the field device agent is configured to combine values from multiple front-end devices. This field device agent can support the combination of functions from multiple front-end devices, for example, for redundancy and / or for combining functions. An example could be a combination of two PTCs, or a combination of a PTC and an NTC for temperature measurement.
[0028] One aspect relates to a field device agent for transforming values from a server and sending them to a front-end device, wherein the front-end device does not have components for function updates. The field device agent includes: a third interface supporting a third communication line between the server and the field device agent; a fourth interface supporting a fourth communication line between the field device agent and the front-end device; and a virtualization module. The virtualization module includes: a sandbox component; a converter component; and an update component. This embodiment is particularly suitable for front-end devices similar to actuators.
[0029] One aspect involves a field device agent used to transform values (especially measurements) sent from front-end devices into a value format suitable for the server.
[0030] To further clarify, this disclosure will be described with reference to embodiments shown in the accompanying drawings. These embodiments are merely examples and not limitations. Attached Figure Description
[0031] Figure 1 The field equipment according to the prior art is schematically depicted;
[0032] Figure 2 A field device according to an embodiment is schematically depicted;
[0033] Figure 3 and Figure 4 A field device according to an embodiment is schematically depicted;
[0034] Figure 5a and Figure 5b A plurality of field devices according to embodiments are schematically depicted. Detailed Implementation
[0035] Figure 1A field device 500 according to the prior art is schematically illustrated. Field device 500 includes a sensor 510 (e.g., a temperature sensor, such as Pt100). Field device 500 includes an ADC 520 (analog-to-digital converter) that converts analog values from sensor 510 into digital values. These digital values are then sent to a control and computing device 530 within the field device (e.g., a CPU with combined memory and registers), so that calibrated and / or otherwise processed values can be forwarded to server 300 via communication line 350. Communication line 350 may support advanced protocols such as OPC UA (Open Platform Unified Communication Architecture). Field device 500 can provide high flexibility and rich information. However, these types of field devices have at least high power consumption and sometimes require frequent updates due to their complexity, for example, to ensure high flexibility. Note that the arrows in this figure and subsequent figures depict the "primary information direction," not a unique information direction. Information (e.g., control signals and / or trigger signals) may also be sent in the opposite direction of the arrows.
[0036] Figure 2 A field device system 400 according to an embodiment is schematically illustrated. The field device system 400 includes a front-end device 200 and a field device agent 100. The front-end device 200 includes a sensor 210 (e.g., a temperature sensor, such as Pt100) and an ADC 220. The front-end device 200 also includes a bus interface 230 for sending data to and (optionally) receiving data from a first interface 250. The front-end device 200 does not have components for function updates. The field device agent 100 processes data from the front-end device 200 and sends the processed data to a server 300 via a second communication line 350. Therefore, from the server's perspective, it appears as if it is receiving data from a conventional field device. However, this processing is not performed in the front-end device 200, but rather in the field device agent 100 (e.g., in its virtualization module 140). Because of this, the front-end device 200 can be designed as a low-cost device with very low power consumption.
[0037] Figure 3 A field device system 400 is schematically illustrated, comprising two front-end devices 200a and 200b, and a field device agent 100. Details of the front-end device 200 are provided below. Figure 2The following is shown. Front-end devices 200a and 200b send data (“raw data”) to the first interface 110 of the field device agent 100 via the first interface 250. The data from the front-end devices 200a and 200b is then forwarded to virtualization modules 140a and 140b, respectively. Each of the front-end devices 200a and 200b may correspond to a corresponding virtualization module 140a and 140b, that is, each front-end device 200a and 200b may send its data to the corresponding virtualization modules 140a and 140b for processing, these modules being logically independent and separate from each other, for example, through virtualization components. Virtualization module 140b is depicted as being behind virtualization module 140a. Each virtualization module 140a and 140b includes a sandbox component 142, a converter component 144, and an update component 146. Virtualization modules 140a and 140b may also include further components, such as an encryption machine for supporting secure communication. Virtualization modules 140a and 140b process the data and send it to the second interface 120. The second interface 120 then sends the data to the server 300 via the second communication line 350.
[0038] Figure 4 The field device system 450 is schematically shown, which includes two front-end devices 200a and 200b and a field device agent 100. Figure 4 and Figure 3 Very similar, but front-end devices 200a and 200b do not include sensor 210 (see Figure 2 Instead, each component contains an actuator. This actuator can be one of the following: a valve, a motor, a heater, and / or other types of actuators. Therefore, with Figure 3 In contrast, the data transmission direction is reversed. Server 300 sends data to field device agent 100 via third communication line 358. From the server's perspective, it appears as if data is being sent to a traditional field device. Communication line 358 can be connected to... Figure 3 The second communication line 350 is identical to the first communication line 250. Data is received by the third interface 118 and forwarded to the virtualization modules 140a and 140b of the front-end devices 200a and 200b, respectively. Virtualization modules 140a and 140b may have the same structure as the sensor front-end devices, but of course, they have a "reverse" function. Therefore, virtualization modules 140a and 140b transform data from server 300 into data for controlling the front-end devices 200a and 200b. This data is transmitted via the fourth interface 128 and the fourth communication line 258. The fourth communication line 258 may support a protocol similar to the first communication line 250.
[0039] Figure 5aA field device system 450 is schematically illustrated, comprising three sensor front-end devices 200a to 200c and a field device agent 100. Each virtualization module 140a to 140c supports one front-end device 200a to 200c. The front-end devices 200a to 200c are connected to the field device agent 100 via a first communication line 250. The field device agent 100 is connected to a server 300 via a second communication line 350.
[0040] Figure 5b and Figure 5a Very similar. Figure 5b The field device system 450 is also schematically shown, comprising three sensor front-end devices 200a to 200c and a field device agent 100. Figure 5a In contrast, front-end devices 200a to 200c are connected to field device agent 100 and server 300 via physically shared communication lines "250, 350". Logically, these shared communication lines "250, 350" still support two communication lines: a first logical communication line 250 from front-end devices 200a to 200c to field device agent 100, and a second logical communication line 350 from field device agent 100 to server 300. For example, these shared communication lines "250, 350" could be an Ethernet APL bus.
[0041] Reference Symbol List
[0042] 100 General Field Equipment Agents
[0043] 110 First Interface
[0044] 118 Third Interface
[0045] 120 Second Interface
[0046] 128 Fourth Interface
[0047] 140 Virtualization Module
[0048] 142 Sandbox Components
[0049] 144 Converter Components
[0050] 146 Updated Components
[0051] 200 front-end devices
[0052] 210 sensor
[0053] 220 Analog-to-Digital Converter (ADC)
[0054] 230 bus interface
[0055] 250 First Communication Line
[0056] 258 Fourth Communication Line
[0057] 300 server
[0058] 350 Second Communication Line
[0059] 358 Third Communication Line
[0060] 400, 450 field equipment systems
[0061] 500 field devices
[0062] 510 sensor
[0063] 520 Analog-to-Digital Converter (ADC)
[0064] 530 Control and computing equipment
Claims
1. A field device agent (100) for transforming values from a front-end device (200) and sending them to a server (300), wherein the front-end device (200) does not have components for function updates, the field device agent (100) comprising: A first interface (110) supports a first communication line (250) between the field device agent (100) and the front-end device (200). The second interface (120) supports a second communication line (350) between the field device agent (100) and the server (300). as well as The virtualization module (140) includes: Sandbox components (142); Converter component (144); and Update component (146).
2. The field device agent (100) according to claim 1, wherein the virtualization module (140) further comprises at least one of the following: Encryption machine; Protocol engine; Data processing unit; Data analysis unit; A data storage unit, used for measuring and diagnosing measurements; Access control unit; Self-diagnostic unit; and / or Process diagnostic unit.
3. The field device agent (100) according to any one of the preceding claims. The first communication line (250) is a secure communication line.
4. The field device agent (100) according to any one of the preceding claims. The front-end device (200) is configured to send the value to the field device agent (100) periodically and / or on demand.
5. The field equipment agent (100) according to claim 4. The transmission frequency mentioned therein has an upper limit and / or a lower limit.
6. The field device agent (100) according to any one of the preceding claims. The first communication line (250) and / or the second communication line (350) are wired and / or wireless.
7. The field device agent (100) according to any one of the preceding claims. The first communication line (250) supports at least one of the following protocols: High-speed addressable remote transducer HART protocol; Modbus protocol; Message Queuing Telemetry Delivery (MQTT) protocol; or Proprietary agreement.
8. The field device agent (100) according to any one of the preceding claims. The field device agent (100) is physically separated from the front-end device (200).
9. The field device agent (100) according to any one of the preceding claims. The field device agent (100) is physically integrated into the server (300) device.
10. The field device agent (100) according to any one of the preceding claims. The second interface (120) is configured to support at least one of the following: Open Platform Communication Unified Architecture (OPC UA) protocol, PROFINET protocol, Ethernet APL, or Modbus protocol.
11. A field device system (400) comprising a front-end device (200) and a field device agent (100) according to any one of the preceding claims.
12. The field device system (400) according to claim 11, wherein the front-end device (200) is one of the following: Temperature measuring equipment; Fill level measuring equipment; Flow measurement equipment; Pressure measuring equipment; or pH or conductivity measuring equipment.
13. The field device system (400) according to claim 11 or 12, wherein the field device agent (100) is configured to combine values from a plurality of front-end devices (200).
14. A field device agent (100) for transforming values from a server (300) and sending them to a front-end device (200), wherein the front-end device (200) does not have components for function updates, the field device agent (100) comprising: The third interface (118) supports a third communication line (358) between the server (300) and the field device agent (100). The fourth interface (128) supports a fourth communication line (258) between the field device agent (100) and the front-end device (200). as well as The virtualization module (140) includes: Sandbox components (142); Converter component (144); and Update component (146).
15. A field device agent (100) for converting values, particularly measurements, sent from a front-end device (200) into a value format suitable for a server (300).