Debugging Distributed Control Node

By automatically discovering and configuring DCN in the process automation network, the complexity and time-consuming issues of debugging heterogeneous equipment are resolved, enabling rapid and reliable equipment replacement and upgrades, and improving the system's automation level and availability.

CN117044175BActive Publication Date: 2026-11-17YOKOGAWA ELECTRIC CORP
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202280021526.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2021-03-22
Filing Date
2022-03-22
Publication Date
2026-11-17
Estimated Expiration
2042-03-22

AI Technical Summary

Technical Problem

In process automation systems, debugging and installing heterogeneous hardware and software devices from different vendors is complex and time-consuming, requires a lot of effort and knowledge, and is prone to human error and system interruption.

Method used

By using automatic discovery and configuration technology, distributed control nodes (DCNs) broadcast or multicast messages in the process automation network to automatically identify and match OT capabilities, push IT and OT configuration data, and enable collaboration between DCNs and network nodes, including security policies and updates.

Benefits of technology

It reduces debugging time and human error, improves system availability, ensures rapid replacement or upgrade of DCN, and provides improved system availability and reduced outages.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117044175B_ABST
    Figure CN117044175B_ABST
Patent Text Reader

Abstract

This document describes an implementation for commissioning a Distributed Control Node (DCN) into a process automation network. In various implementations, one or more messages transmitted by the DCN on the process automation network announcing that the DCN has joined the network can be detected. Based on these messages, one or more operational technology (OT) capabilities of the DCN can be determined. Based on these OT capabilities, for example by configuring the DCN to cooperate with one or more other process automation nodes on the network to achieve at least partial automation of a process, the DCN can be commissioned into the process automation network.
Need to check novelty before this filing date? Find Prior Art

Description

Background Technology

[0001] In some process automation systems, heterogeneous hardware and software supplied by various vendors are common. Therefore, commissioning and installing equipment from different vendors can require significant effort and knowledge or familiarity with each type of equipment. Each device may have different hardware and software specifications, as well as different operational technology (OT) capabilities, such as sensing, control, actuation, and computation. Summary of the Invention

[0002] This document describes implementations for commissioning devices (such as computational and / or input / output (I / O) gates, referred to in some scenarios as distributed control nodes (DCNs)) to process automation networks. More specifically, but not exclusively, this document describes implementations for automatically discovering the type and / or operational technology (OT) capabilities of DCNs added to process automation networks, such as process automation networks conforming to open standards that allow the integration of heterogeneous components from various vendors. These type and / or OT capabilities may include, for example, software and hardware specifications, supported OT capabilities (e.g., protocols, signal types, control runtime engines, etc.), open standard conformance profiles, etc. Furthermore, techniques for automatically configuring newly added devices based on information collected during the discovery process are proposed. The techniques described herein can save time and effort, reduce human error, and / or mitigate system downtime or other system interruptions. For example, faulty DCNs can be replaced or upgraded more quickly while providing improved and / or uninterrupted system availability.

[0003] In some implementations, a method for commissioning a DCN to a process automation network can be implemented using one or more processors and may include: detecting one or more messages transmitted by the DCN on the process automation network, wherein the one or more messages notify that the DCN has joined the process automation network; determining one or more operational technology (OT) capabilities of the DCN based on the one or more messages; and commissioning the DCN to the process automation network based on the one or more OT capabilities, wherein commissioning includes configuring the DCN to cooperate with one or more other process automation nodes on the process automation network to achieve at least partial automation of processes.

[0004] In various embodiments, the method may further include: identifying one or more other process automation nodes on the process automation network that are compatible with the DCN, based on one or more OT capabilities. In various embodiments, identification may include matching at least one actuator on the process automation network to the DCN based on its profile. In various embodiments, identification may include matching at least one sensor on the process automation network to the DCN based on its profile.

[0005] In various implementations, detection may include receiving a message as a multicast message. In various implementations, configuration may include causing configuration data to be installed on the DCN, wherein the configuration data facilitates cooperation between the DCN and one or more other nodes on the process automation network to achieve at least partial automation of the process. In various implementations, causing may include pushing the configuration data to the DCN via the process automation network.

[0006] In various implementations, the added OT capabilities of the DCN may include one or more of the following: the count of the DCN's input / output (I / O) channels; the type of the DCN's I / O channels; the range limitation associated with the DCN; the preferred unit of measurement for the DCN; the DCN's update frequency; one or more analog-to-digital conversion parameters of the DCN; one or more signal conditioning parameters of the DCN; or any combination thereof.

[0007] In various implementations, the method may further include verifying or authenticating the DCN based on data received from a vendor system associated with the DCN via one or more computer networks. In some such implementations, verification may include cross-referencing identification information associated with the DCN and the data received from the vendor system.

[0008] On the other hand, the DCN may include logic / circuit for: transmitting one or more messages on the process automation network, wherein the one or more messages notify the DCN that it has joined the process automation network and convey one or more OT capabilities of the DCN; receiving configuration data from a configuration node through the process automation network, wherein the configuration data includes: IT configuration data that enables the DCN to participate in network communication with other nodes on the process automation network, and OT configuration data that enables the DCN to cooperate with one or more compatible actuators or sensors on the process automation network to achieve at least partial automation of the process; and exchanging data with one or more of the compatible actuators or sensors according to the configuration data to achieve at least partial automation of the process.

[0009] In various implementations, the circuit may be configured to receive software or firmware updates from or under the guidance of a configuration node. In various implementations, IT configuration data may include security certificates for facilitating encrypted communication. In various implementations, IT configuration data may include time-sensitive networking settings.

[0010] Additionally, some implementations include one or more processors of one or more computing devices, wherein the one or more processors are operable to execute instructions stored in associated memory, and wherein the instructions are configured to cause any of the foregoing methods to be performed. Some implementations also include one or more non-transitory computer-readable storage media storing computer instructions executable by one or more processors to perform any of the foregoing methods.

[0011] It should be understood that all combinations of the foregoing and additional concepts described in more detail herein are considered part of the subject matter disclosed herein. For example, all combinations of the claimed subject matter appearing at the end of this disclosure are considered part of the subject matter disclosed herein. Attached Figure Description

[0012] Figure 1 An environment in which selected aspects of this disclosure can be implemented according to various embodiments is schematically depicted.

[0013] Figure 2 Examples of how the techniques described herein can be implemented according to various embodiments are illustrated.

[0014] Figure 3 An exemplary method for performing selected aspects of this disclosure is illustrated.

[0015] Figure 4 Another exemplary method for performing a selected aspect of this disclosure is illustrated.

[0016] Figure 5 An exemplary computer architecture on which selected aspects of this disclosure may be implemented is schematically illustrated. Detailed Implementation

[0017] This document describes implementations for commissioning equipment to handle automated applications and / or systems. More specifically, but not exclusively, this document describes implementations for automatically discovering the types and / or operational technology (OT) capabilities of equipment, such as distributed control nodes (DCNs), added to process automation networks, such as those conforming to open standards that allow the integration of heterogeneous components from various vendors. These types and / or OT capabilities may include, for example, software and hardware specifications, supported OT capabilities (e.g., protocols, signal types, control runtime engines, etc.), open standard conformance profiles, etc. Furthermore, techniques for automatically configuring equipment based on information collected during the discovery process are proposed. The techniques described herein can save time and effort, reduce human error, and / or mitigate system downtime and / or failures. For example, a faulty DCN can be replaced or upgraded more quickly while providing improved and / or uninterrupted system availability.

[0018] In various implementations, when a DCN or other similar device connects to a process automation network, the DCN can announce itself, for example, by broadcasting or multicasting one or more messages on the process automation network. Configuration nodes on the process automation network (e.g., a central server) can detect these messages and determine the operational capabilities (OT) of the added DCN. Based on these OT capabilities, the configuration nodes can debug the added DCN into the process automation network. In some implementations, this debugging may include applying security policies and / or updates, and configuring the added DCN to cooperate with one or more other nodes on the process automation network to achieve at least partial automation of the process.

[0019] As used herein, "at least partially automated process" includes any process within a process automation system that is achieved collaboratively by multiple devices with little or no human intervention. A common example of a at least partially automated process is a process loop in a process automation network that operates one or more actuators automatically (without human intervention) based on the output of one or more sensors. Some at least partially automated processes can be subprocesses of the entire process automation system, such as the single process loops mentioned earlier. Other at least partially automated processes can include all or most of the entire process automation system. In some cases, the degree of process automation can exist along gradients, ranges, or scales of automation. Processes that are partially automated but still require human intervention can be at one end of the scale or close to one end. Processes that require less human intervention can be close to the other end of the scale, representing fully autonomous processes. Process automation is generally used to automate processes in a variety of fields, such as the manufacture, development, and / or refining of chemicals (e.g., chemical processing), catalysts, machinery, etc.

[0020] In various implementations, the newly added DCN can be configured (e.g., pushed) with one or both of information technology (IT) configuration data (operating system, device drivers, security and network policies, etc.) and OT configuration data. The IT configuration data enables the DCN to securely participate in network communications with other nodes on the process automation network and may include, for example, networking parameters, hardware parameters, etc. In some cases, the IT configuration data may be determined at least in part based on the added DCN's IT capabilities (such as redundancy); interfaces (serial, USB, Ethernet, wireless, etc.); storage type (e.g., hard disk drive, solid-state drive, memory card, etc.); time-sensitive networking; Global Positioning System (GPS) capabilities; or any combination thereof.

[0021] OT configuration data can be generated, at least in part, based on the OT capabilities of the added DCN and / or the compatibility of those OT capabilities with the OT capabilities of other devices in the process automation system. In many cases, OT capabilities can be included in a “profile” associated with the added DCN. OT capabilities can vary widely across industries. In some cases, OT capabilities may include, but are not limited to: the count of input / output (I / O) channels of the added DCN; one or more types of one or more I / O channels of the added DCN; range limitations associated with the added DCN; the preferred unit of measurement of the added DCN; the update frequency of the added DCN; one or more analog-to-digital conversion parameters of the added DCN; one or more signal conditioning parameters of the added DCN; supported open standard protocols, such as Open Platform Communication (OPC) Unified Architecture (OPCUA) and / or Modbus; or any combination thereof. OT configuration data may include, for example, identifiers of compatible process automation nodes on the process automation system (e.g., IP addresses), OT parameters to be used during operation (e.g., units of measurement, range adjustments, open communication protocols, etc.).

[0022] In some implementations, IT and OT capabilities and / or configuration data may overlap and / or be combined. In other implementations, they may be separated.

[0023] Now for reference Figure 1 An exemplary environment 100 is schematically depicted that can implement various aspects of this disclosure. A process automation management system 102 is operatively coupled to a process automation network 106 in a process automation facility 108. The process automation facility 108 can take many forms and can be designed to implement any number of at least partially automated processes. For example, the process automation facility 108 can take the form of a chemical processing plant, an oil or gas refinery, a catalyst plant, a manufacturing facility, etc.

[0024] The process automation network 106 can be implemented using a variety of wired and / or wireless communication technologies, including but not limited to the IEEE 802.3 standard (Ethernet), IEEE 802.11 (Wi-Fi), cellular networks (such as 3GPP Long Term Evolution (“LTE”) or other wireless protocols designated as 3G, 4G, 5G and higher), and / or other types of communication networks with various topologies (e.g., mesh). Process automation is typically used in scenarios where failure costs are often high in terms of human safety and stakeholder financial costs. Therefore, in various implementations, the process automation network 106 can be configured with redundancy and / or backup to provide high availability (HA) and / or high quality of service (QoS).

[0025] The process automation management system 102 may include a debugging module 104 and a database 105 that stores information used by the debugging module 104 to practice selected aspects of this disclosure. Various aspects of the process automation management system 102, such as the debugging module 104, can be implemented using any combination of hardware and software. In some embodiments, the process automation management system 102 may be implemented across multiple computer systems as part of what is commonly referred to as "cloud infrastructure" or simply "the cloud." However, this is not necessary, and... Figure 1 For example, the process automation management system 102 is implemented within a process automation facility 108, such as in a single building or across a single building campus or other industrial infrastructure. In such an implementation, the process automation management system 102 may be implemented on one or more local computing systems (such as on one or more server computers).

[0026] In addition to the process automation management system 102, various other nodes are operatively coupled to the process automation network 106. Figure 1 In this context, for example, N (positive integer) DCNs 110-1 to 110-N are operatively coupled to the process automation network 106. Each DCN may include circuitry or logic 112 that can take various forms, such as a processor executing instructions in memory, a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc. Each DCN 110 may have a specific role to play in the process automation network 106. The “computing” DCN may, for example, control a process loop (e.g., a chemical process loop), where various “field” devices (e.g., devices with sensors and / or actuators) interface with each other to perform a number of functional control blocks (FBs).

[0027] Each DCN 110 may have various input / output (I / O) components that define at least some of its OT capabilities and, more generally, its role at the process automation facility 108. For example, the first DCN 110-1 includes a flow transmitter (FT) component 114-1 and an actuator (e.g., a valve) 116-1. In some embodiments, software components implemented on DCN 110-1 (or any other DCN mentioned herein) can convert analog signals to digital signals and / or convert signals between different units of measurement. Additionally, in some embodiments, software components implemented on DCN 110-1 can be configured to convert data between various protocols. For example, a vendor-specific DCN (or other legacy equipment) may not be natively configured to use the OPC Unified Architecture (OPC UA) to transmit data. In some such embodiments, another DCN 110 may be deployed to convert the data from the vendor's proprietary format to OPC UA. Some of these DCN 110s can be referred to as “gateways” or “bridges” because they form a link between legacy technologies and standards such as OPC UA.

[0028] Actuator 116-1 (and other actuators described herein) can be any electrical, hydraulic, mechanical, and / or pneumatic component controllable to influence some aspect of the process automation workflow occurring at process automation facility 108. In many cases, actuator 116 can perform its function in response to various signals, such as sensor signals or commands from a computational DCN (which itself can monitor sensor signals). Some non-limiting examples of actuator 116 include, but are not limited to, valves, pistons, rotors, switches, heaters, coolers, agitators, syringes, vacuum-generating devices, conveyors, tracks, gears, grippers, motors, relays, servo mechanisms, etc.

[0029] Each DCN 110 can have different OT capabilities relative to one or more (e.g., all) other DCN 110s. Figure 1 For example, the second DCN 110-2 includes an FT component 114-2 but no actuator. The third DCN 110-3 includes a sensor 118-3 but no actuator. The sensor 118-3 (and elsewhere herein) can take various forms, including but not limited to pressure sensors, temperature sensors, flow sensors (e.g., FT component 114), various types of proximity sensors, optical sensors (e.g., photodiodes), pressure wave sensors (e.g., microphones), humidity sensors (e.g., humidity-sensitive resistors), radiation dosimeters, laser absorption spectrometers (e.g., multi-pass optical cells), etc. Similar to the first DCN 110-1, the fourth DCN 110-4 also includes both the FT component 114-4 and the actuator 116-4.

[0030] Unlike DCNs 110-1 through 110-4, DCN-N does not include any inputs / outputs (actuators or sensors). Instead, DCN-N can be a "computation-only" DCN whose role is to facilitate collaboration between itself and one or more other DCNs 110 on the process automation network 106 to achieve at least partial automation of the process. For example, DCN 110-N can control a single process loop (e.g., a chemical process control loop) involving one or more other DCNs 110. In some cases, computational DCN 110 can perform a role similar to an autopilot on an aircraft—computational DCN 110 can receive various signals and control various actuators based on those signals and various criteria and / or thresholds. For example, computational DCN 110 can monitor various sensors 118 to determine data about chemical levels, (e.g., flow rates across valves), tank temperatures, control rates, etc., and can control one or more actuators 116 based on these data and / or comparisons of these data with various criteria and / or thresholds. For example, the computing DCN 110-N can control the actuator 116-4 by transmitting appropriate commands to the DCN 116-4 that can optionally conform to a protocol specific to the DCN 116-4.

[0031] As previously mentioned, adding a DCN to the process automation network 106 (whether as a new addition, replacement, or upgrade) can be complex and cumbersome due to the heterogeneity between different DCNs; this remains true even with the increasing implementation of open standards for process automation. Therefore, this document describes improved techniques for commissioning or “loading” DCNs into the process automation network 106. In some implementations, these improved techniques are implemented at least in part by the commissioning module 104. However, this is not intended to be limiting, and in other implementations, the techniques described herein can be implemented elsewhere, such as a logical distribution of DCNs 112-1 to 112-N across DCNs 110-1 to 110-N.

[0032] In various implementations, when a DCN such as a third DCN 110-3 connects to the process automation network 106, as indicated by arrow A, the third DCN 110-3 can "announce" itself to other nodes on the process automation network 106. For example, the third DCN 110-3 can use technologies such as broadcasting and / or multicasting (e.g., multicast domain name service (multicast DNS)) to transmit one or more messages on the process automation network 106. These messages can announce that the third DCN 110-3 has joined the process automation network 106 and can convey one or more OT capabilities of the third DCN 110-3.

[0033] In some implementations, each DCN may have its own custom profile (e.g., an open standards conformance profile) that conveys information about its model, serial number, security level, number and nature of I / O channels (such as FT component 114, actuator 116, and / or sensor 118), data format for each I / O channel, etc. These profiles, which can describe the baseline functionality of the DCN, can take various forms, such as those conforming to Representational State Transition (REST), JavaScript Object Notation (JSON), and Extensible Markup Language (XML). These profiles can be used, for example, by the debugging module 104 and / or other nodes of the process automation network 106 to determine which DCNs 110 are compatible with each other. For example, the debugging module 104 may maintain a list of active DCN profiles in database 105, enabling it to match newly added DCNs 110 with other DCNs 110 already connected to the process automation network 106. It can support various types of profiles, such as I / O profiles (e.g., ampere to volt, analog to digital), alarm handling profiles, actuator profiles, sensor profiles, etc. In some implementations, the debugging module 104 can use a lookup table or other similar mechanism (e.g., a dynamic database) to match the profile of one DCN 110 with the profile of another DCN 110 (soft match or exact match) to identify compatible DCNs.

[0034] In various implementations, the debugging module 104 can be configured to detect one or more messages transmitted by the third DCN 110-3 on the process automation network 106, as indicated by the arrow marked "A". Based on the one or more messages transmitted by the third DCN 110-3, for example, as Figure 1 As part of the discovery handshake, indicated by the arrow marked "B", the debug module 104 can determine the IT and / or OT capabilities of the third DCN 110-3. Figure 1 In the example, the third DCN 110-3 includes sensor 118-3. As described elsewhere in this document, these IT and / or OT capabilities may include, for example: software specifications; operating system (OS) specifications; hardware specifications; data formatting and / or communication protocols, such as supported open standard protocols, such as OPC UA and / or Modbus; signal types; control runtime engine; I / O channel count; I / O channel type; range limitations; preferred units of measurement; update frequency; one or more analog-to-digital conversion parameters; one or more signal conditioning parameters, etc.

[0035] Based on the detected OT capabilities, the commissioning module 104 can commission the third DCN 110-3 to the process automation network 106. For example, as indicated by the arrow marked "C", the commissioning module 104 can configure the third DCN 110-3 to cooperate with one or more other process automation nodes on the process automation network to achieve at least partial automation of the process. In some embodiments, the commissioning module 104 can push various IT and / or OT configuration information to the third DCN 110-3, and the third logic 112-3 uses the various IT and / or OT configuration information to cooperate with other DCNs to achieve at least partial automation of the process. In some of those embodiments, the commissioning module 104 is able to select or generate at least some of the IT and / or OT configuration information based on the determined IT and / or OT capabilities of the third DCN 110-3.

[0036] IT configuration information may include, but is not limited to, OS or other software updates, firmware updates, software applications, and / or libraries designed and / or compiled for a specific OS and / or central processing unit (CPU) architecture for the DCN. In some implementations, the configuration information may include security certificates (e.g., public keys) that the DCN can use to implement encrypted communication on the process automation network 106. In some implementations, the configuration information may additionally or alternatively include Time-Sensitive Networking (TSN) settings.

[0037] In some implementations, for example, as part of a discovery handshake indicated by the arrow marked "C", the debug module 104 can authenticate the DCN to be added (such as the third DCN 110-3 in this example) to ensure that the DCN to be added is legitimate and does not pose a security risk to the process automation network 106. Figure 1 In this example, process automation management system 102 is operatively coupled to a number of M (positive integers) supplier systems 122-1 to 122-M via one or more networks 120 (e.g., the Internet). Each supplier system 122 may be associated with a supplier (not depicted) of one or more components (e.g., DCN 110-1 to 110-N) used in process automation facility 108.

[0038] In some cases, supplier system 122 can be configured to use various authentication technologies to authenticate different types of credentials forwarded to it by process automation management system 102. As a non-limiting example, a public encryption key from its respective supplier can be provided to each DCN 110. DCN 110 and / or process automation management system 102 can use this public key to encrypt some handshake data and then send that handshake data to the corresponding supplier system 122. Supplier system 122 can use its own private key to decrypt the handshake data; if decryption is successful, DCN 110 can be authenticated. Other variations of public key encryption are contemplated. In other implementations, as part of the discovery handshake indicated by the arrow marked "C", DCN 110 can provide other credentials, such as digital certificates, which the corresponding supplier system 122 can verify before DCN 110 is allowed to operate fully on process automation network 106.

[0039] In some implementations, the supplier system 122 can verify not only the legitimacy of the DCN 110, but also whether the DCN 110 conforms to the expected / requested standards associated with the process automation facility 108. For example, various identifying information associated with the added DCN 110 (such as serial number, model, batch number, etc.) can be cross-referenced with purchase and / or work orders created for the process automation facility 108. Additionally or alternatively, the IT and / or OT capabilities of the added DCN 110 can be compared with known parameters of the process automation facility 108 and / or process automation network 106 to ensure compatibility. In some implementations, the supplier system 122 can push digital keys / certificates and / or other data including these to the process automation management system 102, enabling the commissioning module 104 to perform these checks locally. As an example, for a large purchase order of DCNs, the supplier system 122 can provide a file or list of relevant information about the new DCN (e.g., serial number / model, capabilities, etc.) that can be used locally by the commissioning module 104 to perform these checks.

[0040] Now for reference Figure 2 An exemplary debugging process flow between the debugging module 104 and the four DCNs 210-1 to 210-4 is schematically depicted. Figure 2 In the middle, time progresses downwards on the page. The first DCN 210-1, with actuator 216-1, advertises itself to the debugging module 104 in the upper left corner. As previously mentioned, this advertisement message can be broadcast or multicast by the first DCN 210-1 on the process automation network 106. In the latter case, the debugging module 104 may have a network identifier, such as an IP address included in the multicast address list. As indicated by the dashed line on the left, the advertisement may include operational techniques (…). Figure 2 The “OT” profile (e.g., an open standard conformance profile) specifies that the first DCN 210-1 has an actuator 216-1 in the form of a pressure valve, without a sensor, and is capable of receiving (hypothetically) “A” format digital input. The profile does not necessarily need to be transmitted in this manner, and Figure 2 The profiles depicted are for illustrative purposes only. Based on the OT profiles and / or other data (e.g., security data) provided by the first DCN 210-1, the debug module 104 can generate and / or retrieve configuration data and provide it back to the first DCN 210-1, which can then implement it locally.

[0041] Next, the second DCN 210-2 is connected to the network ( Figure 1 In step 106), a similar exchange occurs with the debugging module 104. The second DCN 210-2 has a different OT profile, which specifies that it has no actuator, has a voltage thermometer (sensor 218-2), and indicates that it outputs an analog signal indicating temperature. Then, the third DCN 210-3 is connected to the network ( Figure 1 In 106), a similar exchange occurs with the debugging module 104. The third DCN 210-3 has a different OT profile, which specifies that it does not have actuators, does not have sensors, and has an FT component 214-3 that converts analog data into digital data.

[0042] Finally, the fourth DCN 210-4 is connected to the network. The fourth DCN 210-4 does not include any sensors, actuators, or FT components, which can be communicated in its own announcement (in...). Figure 2 (No label is shown). Instead, during the configuration process, the debug module 104 can communicate to the fourth DCN 210-4 which other process automation nodes are compatible. As shown in the dashed label in the lower right corner, the compatible nodes include the first DCN 210-1 (DCN1), the second DCN 210-2 (DCN2), and the third DCN 210-3 (DCN3). For each compatible DCN, a network identifier such as an IP address is provided, along with relevant data about the role each compatible DCN serves. Based on these IP addresses, the fourth DCN 210-4 can then collaborate with the other DCNs 210-1 through 210-3 to achieve at least some of the automation processes, in whole or in part.

[0043] Figure 3This is a flowchart illustrating an exemplary method 300 of a selected aspect of the present disclosure, practicing according to embodiments disclosed herein. For convenience, the operations of the flowchart are described with reference to a system performing the operations. This system may include various components of various computer systems, such as one or more components of a process automation management system 102, including a debugging module 104. Furthermore, although the operations of method 300 are shown in a specific order, this is not intended to be limiting. One or more operations may be reordered, omitted, or added.

[0044] At box 302, the system can detect, for example, the DCN (e.g., via debug module 104) by means of the debug module 104. Figure 1 (110-3) Messages transmitted on process automation network 106. In various embodiments, the message may announce that an added DCN has joined process automation network 106. In some embodiments, the announcement message may be broadcast by the added DCN to all nodes on process automation network 106. In other embodiments, the message may be multicast by the added DCN to one or more target nodes (e.g., members of a multicast list), such as process automation management system 102.

[0045] Based on this message or a subsequent message transmitted by the added DCN, at block 304, the system can determine one or more OT capabilities of the added DCN. For example, the message or subsequent message may include one or more profiles of the added DCN (e.g., an open standards conformance profile). The debugging module 104 can match these one or more profiles of the added DCN with one or more profiles of other DCNs on the process automation network 106 stored in database 105. For example, in some implementations, based on one or more OT capabilities of the added DCN, the system, for example through the debugging module 104, can identify one or more other process automation nodes on the process automation network that are compatible with the added DCN based on their respective profiles.

[0046] More specifically, in some embodiments, the system may match at least one actuator 116 / 216 of the process automation network 106 with an added DCN based on a profile of at least one actuator. Additionally or alternatively, in some embodiments, the system may match at least one sensor 118 / 218 of the process automation network 106 with an added DCN based on a profile of at least one sensor. Additionally or alternatively, in some embodiments, the system may match at least one FT component 114 / 214 of the process automation network 106 with an added DCN based on a profile of at least one FT component.

[0047] Based on one or more OT capabilities, at block 306, the system can, for example, debug the added DCN to process automation network 106 via debugging module 104. In various embodiments, the operations associated with debugging at block 306 can take various forms. In many embodiments, debugging at block 306 may include: at block 308, contacting various certification centers (such as...) Figure 1 The DCN added to the applicable supplier system (122) authentication. Authentication in box 308 can be performed in various ways, such as using public-key cryptography, security certificates, two-factor authentication, etc.

[0048] At block 310, the system, for example via debugging module 104, can configure the added DCN to cooperate with one or more other process automation nodes (e.g., other DCNs) on the process automation network to achieve at least partial automation of the process. In some embodiments, as part of the configuration of block 310, the system can cause configuration data to be installed on the added DCN at block 312. The configuration data can facilitate cooperation between the added DCN and one or more other nodes on the process automation network to achieve at least partial automation of the process. In various embodiments, the configuration data may include IT configuration data and / or OT configuration data, the IT configuration data enabling the added DCN to participate in network communication with other nodes on process automation network 106, and the OT configuration data enabling the added DCN to cooperate with one or more compatible FT components 114, actuators 116, and / or sensors 118 on process automation network 106 to achieve at least partial automation of the process.

[0049] Figure 4 This is a flowchart illustrating an exemplary method 400 for practicing selected aspects of this disclosure in a DCN 110 / 210 according to embodiments disclosed herein. Although the operations of method 400 are shown in a specific order, this is not intended to be limiting. One or more operations may be reordered, omitted, or added.

[0050] At box 402, DCN 110 / 210 can transmit one or more messages on process automation network 106. Similar to the previous example, one or more messages can announce that the DCN has joined process automation network 106 and convey one or more OT capabilities of the DCN.

[0051] At box 404, DCN 110 / 210 can receive configuration data from a configuration node, such as commissioning module 104, via process automation network 106. This configuration data can vary between implementations. In some implementations, the configuration data may include IT configuration data received at box 406. IT configuration data may include, for example, IP addresses, subnet hosts, network credentials, DNS (including multicast DNS) data, and any other parameters that enable the DCN to participate in network communications with other nodes on process automation network 106. IT configuration may also include other IT parameters such as redundancy capabilities, interfaces, storage type, TSN, GPS capabilities, etc.

[0052] Additionally or alternatively, in some implementations, the configuration data may include OT configuration data received at block 408. Furthermore, the configuration data may enable the DCN to cooperate with one or more compatible actuators or sensors on the process automation network to achieve at least partial automation of the process. Figure 2 The dashed box in the lower right corner (“Compatible Node”) depicts a non-limiting example of OT configuration data. Based on the configuration data that the DCN can install in its own memory, at box 410, the DCN can subsequently exchange data with one or more compatible actuators or sensors, such as those associated with / hosted by the corresponding DCN, to enable at least partial automation of the process.

[0053] Figure 5 This is a block diagram of an exemplary computing device 510 that can be optionally used to perform one or more aspects of the techniques described herein. The computing device 510 typically includes at least one processor 514 that communicates with a plurality of peripheral devices via a bus subsystem 512. These peripheral devices may include a storage subsystem 524 (including, for example, a memory subsystem 525 and a file storage subsystem 526), ​​a user interface output device 520, a user interface input device 522, and a network interface subsystem 516. The input and output devices allow users to interact with the computing device 510. The network interface subsystem 516 provides an interface to an external network and is coupled to corresponding interface devices in other computing devices.

[0054] User interface input device 522 may include a keyboard, pointing devices (such as a mouse, trackball, touchpad, or graphics tablet), scanner, touchscreen integrated into a display, audio input devices (such as a voice recognition system, microphone), and / or other types of input devices. Generally, the term "input device" is intended to encompass all possible types of devices and methods for inputting information into computing device 510 or a communication network.

[0055] User interface output device 520 may include a display subsystem, a printer, a fax machine, or a non-visual display such as an audio output device. The display subsystem may include a cathode ray tube (CRT), a flat panel device such as a liquid crystal display (LCD), a projection device, or some other mechanism for creating a visible image. The display subsystem may also provide non-visual displays, such as via an audio output device. Generally, the term "output device" is intended to encompass all possible types of devices and methods for outputting information from computing device 510 to a user or another machine or computing device.

[0056] Storage subsystem 524 stores the programming and data structures that provide the functionality of some or all of the modules described herein. For example, storage subsystem 524 may include programs and data structures for performing... Figures 3 to 4 The aspects of the method chosen and used for implementation Figures 1 to 2 The logic of the various components described in the text.

[0057] These software modules are typically executed by processor 514 alone or in combination with other processors. The memory 525 used in storage subsystem 524 can include multiple memories, including main random access memory (RAM) 530 for storing instructions and data during program execution and read-only memory (ROM) 532 for storing fixed instructions. File storage subsystem 526 provides persistent storage for program and data files and may include hard disk drives, floppy disk drives, and associated removable media, CD-ROM drives, optical disk drives, or removable media cartridges. Modules implementing the functionality of certain embodiments may be stored by file storage subsystem 526 in storage subsystem 524 or in other machines accessible by processor 514.

[0058] Bus subsystem 512 provides a mechanism for enabling various components and subsystems of computing device 510 to communicate with each other as intended. Although bus subsystem 512 is schematically shown as a single bus, alternative implementations of the bus subsystem may use multiple buses.

[0059] The computing device 510 can be of various types, including workstations, servers, computing clusters, blade servers, server groups, or any other data processing system or computing device. Due to the constantly evolving nature of computers and networks, Figure 5 The description of the computing device 510 depicted herein is intended only as a specific example for illustrating some embodiments. Many other configurations of the computing device 510 may have more... Figure 5 The computing device depicted in the text has more or fewer components.

[0060] While several embodiments have been described and illustrated herein, various other means and / or structures may be utilized for performing functions and / or obtaining results and / or one or more advantages described herein, and each of these variations and / or modifications is considered to be within the scope of the embodiments described herein. More generally, all parameters, dimensions, materials, and configurations described herein are intended to be exemplary, and actual parameters, dimensions, materials, and / or configurations will depend on one or more specific applications using the teachings. Those skilled in the art will recognize or be able to determine many equivalents of the specific embodiments described herein using no more than conventional experimentation. Therefore, it should be understood that the foregoing embodiments are presented by way of example only, and embodiments may be practiced in ways other than those specifically described and claimed within the scope of the appended claims and their equivalents. Embodiments of this disclosure relate to each individual feature, system, article, material, kit, and / or method described herein. Additionally, any combination of two or more such features, systems, articles, materials, kits, and / or methods is included within the scope of this disclosure if such features, systems, articles, materials, kits, and / or methods do not contradict each other.

Claims

1. A method for commissioning a distributed control node (DCN) into a process automation network, the DCN having multiple input / output (I / O) channels, the method being implemented using one or more processors and comprising: Detect one or more messages transmitted by the DCN on the process automation network, wherein the one or more messages transmitted by the DCN on the process automation network announce that the DCN has joined the process automation network and convey the DCN's operational technology (OT) capabilities, the operational technology (OT) capabilities including the count of multiple I / O channels of the DCN and the type of the multiple I / O channels; The OT capability of the DCN is determined from the content of one or more messages transmitted by the DCN on the process automation network; and Based on one or more of the OT capabilities, the DCN is debugged into the process automation network, wherein the debugging includes: Match one or more other process automation nodes on the process automation network to the DCN; and The DCN is configured to cooperate with one or more matched other process automation nodes on the process automation network to implement a process control loop, the process control loop including: operating at least one actuator of one or more matched other process automation nodes based on one or more sensor signals generated by one or more matched other process automation nodes.

2. The method according to claim 1, wherein, The matching includes: Based on the profile of at least one actuator of the process automation network, the at least one actuator is matched with the DCN.

3. The method according to claim 1, wherein, The matching includes: Based on the profile of at least one sensor of the process automation network, the at least one sensor is matched with the DCN.

4. The method according to claim 1, wherein, The detection includes: Receive one or more of the messages as multicast messages.

5. The method according to claim 1, wherein, The configuration includes: This causes the configuration data to be installed on the DCN. The configuration data facilitates collaboration between the DCN and one or more other process automation nodes on the process automation network to achieve the process control loop.

6. The method according to claim 5, wherein, The cause includes: The configuration data is pushed to the DCN through the process automation network.

7. The method according to claim 1, wherein, The one or more OT capabilities of the added DCN also include one or more of the following: The range limitation associated with the DCN; The preferred unit of measurement for the DCN; The update frequency of the DCN; One or more analog-to-digital conversion parameters of the DCN; One or more signal conditioning parameters of the DCN; or Any combination thereof.

8. The method of claim 1, further comprising: The DCN is verified or authenticated based on data received from the supplier system associated with the DCN via one or more computer networks.

9. The method according to claim 8, wherein, The verification includes: Cross-reference is made to the identification information associated with the DCN and the data received from the supplier system.

10. A distributed control node (DCN) having multiple input / output (I / O) channels and including circuitry for: Transmit one or more messages on a process automation network, wherein, The one or more messages transmitted by the DCN on the process automation network announce that the DCN has joined the process automation network and convey one or more operational technology (OT) capabilities of the DCN, wherein the OT capabilities include the count of the plurality of I / O channels of the DCN and the type of the plurality of I / O channels; Configuration data is received from the configuration node through the process automation network, wherein the configuration data includes: Information technology (IT) configuration data, which enables the DCN to participate in network communications with other nodes on the process automation network, and OT configuration data, which enables the DCN to operate one or more compatible actuators based on one or more sensor signals generated by one or more sensors on the process automation network to implement a process control loop, wherein, based on one or more of the OT capabilities, the one or more compatible actuators are matched with the DCN; and Based on the configuration data, data is exchanged with one or more compatible actuators or sensors to implement the process control loop.

11. The DCN according to claim 10, wherein, The circuit is used to receive software or firmware updates from the configuration node or under the guidance of the configuration node.

12. The DCN according to claim 10, wherein, The IT configuration data includes security certificates used to facilitate encrypted communication.

13. The DCN according to claim 10, wherein, The IT configuration data includes time-sensitive networking settings.

14. A system for commissioning a distributed control node (DCN) into a process automation network, the DCN having multiple input / output (I / O) channels, the system comprising one or more processors that execute instructions stored in memory to: Detect one or more messages transmitted by the DCN on the process automation network, wherein, The one or more messages transmitted by the DCN on the process automation network announce that the DCN has joined the process automation network and include the DCN's operational technology (OT) capabilities, which include a count of multiple I / O channels of the DCN and the types of the multiple I / O channels; The OT capability of the DCN is determined from the content of one or more messages transmitted by the DCN on the process automation network; as well as Based on one or more of the OT capabilities, the DCN is debugged into the process automation network, wherein the instructions for debugging include instructions for the following: Match one or more other process automation nodes on the process automation network to the DCN; and The DCN is configured to cooperate with one or more matched other nodes on the process automation network to implement a process control loop, the process control loop including: operating at least one actuator of one or more matched other process automation nodes based on one or more sensor signals generated by one or more matched other process automation nodes.

15. The system of claim 14, comprising: Profiles for at least one actuator based on the process automation network, and instructions for matching the at least one actuator with the DCN.

16. The system of claim 14, comprising: A profile for at least one sensor based on the process automation network, and instructions for matching the at least one sensor with the DCN.

17. The system according to claim 14, wherein, One or more of the messages were detected as multicast messages.

18. The system according to claim 14, wherein, The instructions for configuration include instructions for causing configuration data to be installed on the DCN. The configuration data facilitates collaboration between the DCN and one or more other nodes on the process automation network to achieve the process control loop.

Citation Information

Patent Citations

  • Techniques for decentralized load balancing

    US20180239650A1

  • Management system for a plant facility and method for managing a plant facility

    US20190098072A1