Redundancy switching method between redundant process control stations in distributed control system
Through edge computing and blockchain technology, the problems of data transmission delay, high single-point failure risk and poor data security in traditional decentralized control systems are solved, efficient and reliable redundant switching and automated control are achieved, and the system response speed is improved and security.
Patent Information
- Application Number
- CN202411238401.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-05
- Publication Date
- 2024-11-29
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
In traditional decentralized control systems, there are problems such as high data transmission delay, high risk of single point failure, poor data security and lack of flexible redundant switching mechanisms.
Through the distribution control function of edge computing technology, digital twins are created to achieve real-time synchronization, blockchain technology is used to store control station status and operation logs, and redundant switching logic is automatically defined and executed through smart contracts.
It significantly reduces data transmission delay, improves system response speed and reliability, enhances data security and automation, and realizes flexible redundant switching and fault tolerance.
Smart Images

Figure CN119045311A_ABST
Abstract
Description
Technical Field
[0001] The invention relates to the technical field of industrial automation and distributed control systems, and in particular to a redundant switching method between redundant process control stations in a distributed control system. Background Art
[0002] In modern industrial automation systems, distributed control systems (DCS) achieve efficient process control by distributing control functions across multiple control stations. However, traditional distributed control systems still face some major challenges. First, the data transmission delay is high. Since traditional systems need to transmit data from remote devices to central servers for processing, this not only increases communication delays and reduces system response speed, but is also easily affected by network bandwidth and stability, resulting in unstable system performance. In industrial automation scenarios, real-time requirements are high, and high data transmission delays may lead to reduced control accuracy and even cause safety accidents.
[0003] In addition, the risk of single point failure is another major problem of the traditional centralized control architecture. This architecture relies on a central server. Once the central server fails, the control function of the entire system will be affected, resulting in production stagnation and economic losses. Although reliability can be improved by redundantly configuring the central server, this method is costly, complex to maintain, and difficult to achieve flexible expansion.
[0004] Poor data security is also a significant problem in traditional systems. Data in centralized storage systems are vulnerable to attacks and tampering, and there is a high risk of data leakage. In industrial control systems, data security and integrity are crucial. Once control data is tampered with, it may lead to serious production accidents and safety hazards. Therefore, ensuring the security and tamper-proofness of data storage is an important challenge.
[0005] Traditional control systems also lack a flexible redundant switching mechanism and rely mainly on manual intervention. The switching process is complex and the response is not timely. When a fault occurs or performance degrades, redundant switching cannot be performed quickly, resulting in long system downtime, affecting production efficiency and reliability. Traditional redundant switching logic is fixed and difficult to flexibly adjust and optimize according to actual needs, and it is difficult to adapt to the dynamically changing production environment.
[0006] In order to overcome these problems, the present invention proposes a redundant switching method between redundant process control stations in a distributed control system. Summary of the invention
[0007] In view of the shortcomings of the prior art, the present invention provides a redundant switching method between redundant process control stations in a distributed control system, which solves the problems of high data transmission delay, high risk of single point failure, poor data security and lack of flexible redundant switching mechanism in the distributed control system.
[0008] To achieve the above objectives, the present invention is implemented through the following technical solutions: A method for redundant switching between redundant process control stations in a distributed control system, comprising the following steps:
[0009] S1. Use edge computing technology to distribute control functions to multiple edge nodes close to data sources;
[0010] S2. Create a digital twin for each physical control station to achieve real-time synchronization between the physical and virtual systems;
[0011] S3, distribute and store the status and operation logs of the control station through blockchain technology;
[0012] S4. Use smart contracts on the blockchain to define the triggering conditions and execution logic of redundant switching;
[0013] S5. When the edge node detects the preset trigger condition, the smart contract automatically performs the redundant switching operation.
[0014] Preferably, the step S1 specifically includes the following steps:
[0015] S1.1. Node selection:
[0016] Select the appropriate edge node location based on the location of the data source and control requirements;
[0017] Determine the hardware configuration of each edge node;
[0018] S1.2, Node deployment:
[0019] Install and configure edge computing devices such as industrial controllers, embedded computing devices, or edge servers;
[0020] Deploy the control station application to each edge node;
[0021] S1.3. Network configuration:
[0022] Configure network connections between edge nodes;
[0023] Setting up network security measures, such as firewalls and encrypted communications;
[0024] S1.4 Task Allocation:
[0025] Assign control tasks to different edge nodes;
[0026] Configure task scheduling strategies to dynamically adjust task allocation to adapt to changes in system load.
[0027] Preferably, the step S2 specifically includes the following steps:
[0028] S2.1. Digital twin model creation:
[0029] Collect various data of the physical control station, including status information, operation logs and environmental parameters; establish a digital twin model;
[0030] S2.2, Data collection and transmission:
[0031] Deploy sensors and data acquisition equipment to collect real-time operating data from physical control stations;
[0032] Configure data transfer protocols to transfer the collected data to the digital twin model;
[0033] S2.3, Real-time synchronization:
[0034] Use data synchronization algorithms to synchronize the data of the physical control station to the digital twin model in real time; set the synchronization frequency and data update strategy;
[0035] S2.4, status monitoring:
[0036] Monitor the status of the digital twin model in real time and detect abnormal situations;
[0037] Configure the alarm mechanism to issue an alarm in time when an abnormality is detected.
[0038] Preferably, the step S3 specifically includes the following steps:
[0039] S3.1、Blockchain network construction:
[0040] Choose a suitable blockchain platform, such as Hyperledger Fabric or Ethereum;
[0041] Deploy blockchain nodes on each edge node to form a blockchain network;
[0042] S3.2, Data structure design:
[0043] Design data structures for control station status and operation logs;
[0044] Define the format and protocol for data storage on the blockchain;
[0045] S3.3. Data on-chain:
[0046] Write smart contracts for data on-chain, and record the status and operation logs of the control station into the blockchain;
[0047] Regularly package the latest status and operation logs of the control station into blocks and broadcast them to the blockchain network;
[0048] S3.4, consensus algorithm:
[0049] Configure the consensus algorithm of the blockchain network, such as Raft or PBFT;
[0050] Set up consensus nodes and voting mechanisms.
[0051] Preferably, the step S4 specifically includes the following steps:
[0052] S4.1. Smart contract writing:
[0053] Write smart contracts to define the triggering conditions for redundant switching;
[0054] Define the execution logic of redundant switching in the smart contract, including task transfer and data synchronization operations;
[0055] S4.2, Contract deployment:
[0056] Deploy the written smart contract to the blockchain network;
[0057] Set the calling permissions and triggering mechanism of the smart contract;
[0058] S4.3. Testing and verification:
[0059] Test smart contracts, simulate various trigger conditions, and verify the correctness of redundant switching logic;
[0060] Fix errors in smart contracts;
[0061] S4.4. Monitoring and updating:
[0062] Configure the operation monitoring mechanism of the smart contract to monitor the execution of the smart contract in real time;
[0063] Smart contracts are regularly updated and optimized according to system requirements.
[0064] Preferably, the triggering conditions in step S4.1 include edge node failure, performance degradation of edge nodes and communication interruption of edge nodes.
[0065] Preferably, the redundant switching operation in step S5 includes the following steps:
[0066] S5.1. Trigger condition monitoring:
[0067] Deploy a monitoring mechanism on each edge node to monitor the node's operating status and performance indicators in real time;
[0068] When the trigger condition is detected to be met, a trigger signal is immediately sent to the blockchain network;
[0069] S5.2. Smart Contract Execution:
[0070] After the blockchain network receives the trigger signal, it automatically calls the smart contract;
[0071] Smart contracts perform redundant switching operations according to preset logic;
[0072] S5.3, Task Transfer:
[0073] Transfer the control task of the failed node to the backup node;
[0074] The backup node has synchronized all necessary data of the failed node through digital twin technology and immediately takes over the control task;
[0075] S5.4, Data Synchronization:
[0076] After the standby node takes over the task, it continues to synchronize data through digital twin technology;
[0077] S5.5. Log Records:
[0078] Every step of the smart contract execution is recorded on the blockchain, forming an unalterable operation log;
[0079] Through the blockchain network, all nodes share these operation logs.
[0080] Preferably, the edge computing device in step S1.2 is one or more of an industrial controller, an embedded computing device or an edge server.
[0081] Preferably, the digital twin model in step S2.1 includes a physical state model, an operation behavior model and a prediction and analysis module.
[0082] The invention provides a redundant switching method between redundant process control stations in a distributed control system.
[0083] It has the following beneficial effects:
[0084] 1. The present invention utilizes edge computing technology to distribute control functions to edge nodes close to data sources, reducing data transmission distance and communication delay, and significantly improving system response speed.
[0085] 2. The present invention uses digital twin technology to synchronize the data and status of the physical control station and the virtual model in real time, ensuring the consistency and accuracy of the data within the system and avoiding control errors caused by data asynchrony.
[0086] 3. The present invention utilizes blockchain technology to distribute and store the status and operation logs of the control station in the blockchain network, and improves the security and reliability of data storage through the decentralization and tamper-proof characteristics of blockchain.
[0087] 4. The present invention automatically defines and executes the trigger conditions and logic of redundant switching through smart contracts, realizes intelligent scheduling and fault handling of control tasks, reduces human intervention, and improves the automation level of the system.
[0088] 5. The present invention uses edge computing technology and containerized deployment to make the system have good scalability, and can flexibly adjust the number and configuration of edge nodes according to actual needs. At the same time, through smart contracts and blockchain consensus algorithms, the robustness and fault tolerance of the system are improved. BRIEF DESCRIPTION OF THE DRAWINGS
[0089] Figure 1 It is a flow chart of the present invention. DETAILED DESCRIPTION
[0090] The technical solution of the present invention will be described clearly and completely below in conjunction with the accompanying drawings of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0091] Example:
[0092] Please see attached Figure 1 The embodiment of the present invention provides a method for redundant switching between redundant process control stations in a distributed control system, comprising the following steps:
[0093] S1. Use edge computing technology to distribute control functions to multiple edge nodes close to data sources;
[0094] S2. Create a digital twin for each physical control station to achieve real-time synchronization between the physical and virtual systems;
[0095] S3, distribute and store the status and operation logs of the control station through blockchain technology;
[0096] S4. Use smart contracts on the blockchain to define the triggering conditions and execution logic of redundant switching;
[0097] S5. When the edge node detects the preset trigger condition, the smart contract automatically performs the redundant switching operation.
[0098] Specifically, the present invention utilizes edge computing technology to distribute control functions to edge nodes close to data sources, reducing data transmission distance and communication delay, and significantly improving system response speed.
[0099] Through digital twin technology, the data and status of the physical control station and the virtual model are synchronized in real time to ensure the consistency and accuracy of the data within the system and avoid control errors caused by data asynchrony.
[0100] Using blockchain technology, the status and operation logs of the control station are distributed and stored in the blockchain network. The decentralization and tamper-proof characteristics of blockchain improve the security and reliability of data storage.
[0101] By automatically defining and executing the trigger conditions and logic of redundant switching through smart contracts, intelligent scheduling and fault handling of control tasks are achieved, which reduces human intervention and improves the system's degree of automation.
[0102] Edge computing technology and containerized deployment enable the system to have good scalability, and can flexibly adjust the number and configuration of edge nodes according to actual needs. At the same time, through smart contracts and blockchain consensus algorithms, the system's robustness and fault tolerance are improved.
[0103] Monitor the status of edge nodes and digital twin models in real time, configure alarm mechanisms and operation log records, so that the system operation status is transparent and visible, which facilitates fault diagnosis and system maintenance.
[0104] Edge computing technology distributes computing resources to edge nodes close to data sources. Edge nodes independently perform control tasks, reducing the distance and delay of data transmission and improving the response speed of the system.
[0105] Each edge node runs an instance of the control station and performs data synchronization and task distribution through network connections.
[0106] At the same time, a digital twin is created for each physical control station, and the operating data of the physical control station is collected in real time by deploying sensors and data acquisition equipment.
[0107] Using the data synchronization algorithm, the collected data is synchronized to the digital twin model in real time to ensure the consistency of the status of the physical system and the virtual system.
[0108] And blockchain nodes are deployed on each edge node to form a blockchain network, through which the status and operation logs of the control station are distributed and stored.
[0109] Utilize the decentralized and tamper-proof characteristics of blockchain to ensure the security and reliability of data storage.
[0110] Write and deploy smart contracts on the blockchain to define the trigger conditions and execution logic for redundant switching.
[0111] Smart contracts can automatically perform redundant switching operations, including task transfer and data synchronization operations, based on preset trigger conditions.
[0112] When the edge node detects a preset trigger condition (such as node failure, performance degradation, communication interruption, etc.), the smart contract automatically performs a redundant switching operation to transfer the control task from the failed node to the backup node.
[0113] Through digital twin technology, the backup node has synchronized all necessary data and can immediately take over the control tasks to ensure the continuous operation of the system.
[0114] Step S1 specifically includes the following steps:
[0115] S1.1. Node selection:
[0116] Select the appropriate edge node location based on the location of the data source and control requirements;
[0117] Determine the hardware configuration of each edge node;
[0118] S1.2, Node deployment:
[0119] Install and configure edge computing devices such as industrial controllers, embedded computing devices, or edge servers;
[0120] Deploy the control station application to each edge node;
[0121] S1.3. Network configuration:
[0122] Configure network connections between edge nodes;
[0123] Setting up network security measures, such as firewalls and encrypted communications;
[0124] S1.4 Task Allocation:
[0125] Assign control tasks to different edge nodes;
[0126] Configure task scheduling strategies to dynamically adjust task allocation to adapt to changes in system load.
[0127] Specifically, the present invention achieves the following effects through a specific step S1, that is, using edge computing technology to distribute the control function to multiple edge nodes close to the data source:
[0128] By distributing computing resources to edge nodes close to data sources, the data transmission distance is reduced, thereby significantly reducing the system's communication delay and improving the system's response speed.
[0129] Distributed deployment of edge nodes avoids the risk of single point failure and improves the reliability and fault tolerance of the system.
[0130] Dynamically allocating computing resources according to control requirements improves the utilization efficiency of system resources and reduces hardware waste.
[0131] By setting up network security measures, the security of data transmission between edge nodes can be protected to prevent data leakage and attacks.
[0132] The technical solution of this step can effectively solve the following problems:
[0133] Traditional centralized control systems have high communication delays and affect system response speed because data needs to be transmitted to a remote server for processing.
[0134] The centralized architecture has the risk of single point failure. Once the central server has problems, the entire system will not be able to operate normally.
[0135] In a centralized system, computing resources cannot be dynamically adjusted according to actual needs, resulting in some resources being idle and wasted.
[0136] Data is vulnerable to attacks during transmission, and centralized storage also poses the risk of data leakage.
[0137] Its specific technical content:
[0138] S1.1 Node selection:
[0139] Select the appropriate edge node location based on the location of the data source and control requirements:
[0140] By analyzing the geographical location of the data source and the requirements of the control task, the optimal edge node location is selected to ensure that the edge node is close to the data source and reduce the data transmission distance.
[0141] When choosing node locations, consider data transmission latency Where d is the data transmission distance, c is the speed of light, and the node position is optimized by minimizing Latency.
[0142] Determine the hardware configuration of each edge node:
[0143] According to the computing requirements of the control task, select the appropriate hardware configuration to ensure that the edge node has sufficient computing power and storage capacity.
[0144] Evaluate the CPU, memory, storage and other hardware resources of each edge node and select the configuration that can meet the control task requirements.
[0145] S1.2 Node deployment:
[0146] Install and configure edge computing devices such as industrial controllers, embedded computing devices, or edge servers:
[0147] Install and configure edge computing devices at the selected location to ensure that the devices can operate normally.
[0148] Complete the physical installation and network connection configuration of the device to ensure that the device can access the data source and process data.
[0149] Deploy the Control Station application to each edge node:
[0150] Deploy the control station application to each edge node to ensure that it can run independently and perform control tasks.
[0151] Deploy applications through containerization technologies (such as Docker) to ensure the consistency and portability of applications on different nodes.
[0152] S1.3 Network configuration:
[0153] Configure network connections between edge nodes:
[0154] Connect edge nodes through high-speed networks to ensure low latency and high bandwidth for data transmission.
[0155] Use fiber optic networks or dedicated links to connect edge nodes and configure appropriate network topology to optimize data transmission efficiency.
[0156] Set up network security measures, such as firewalls and encrypted communications:
[0157] The security of data transmission between edge nodes is protected through security measures such as firewalls and encrypted communications.
[0158] Configure firewall rules to restrict unauthorized access and use SSL / TLS protocol to encrypt data transmission to ensure that data is not stolen or tampered with during transmission.
[0159] S1.4 Task Allocation:
[0160] Assign control tasks to different edge nodes:
[0161] According to the resource status of each edge node and the requirements of the control task, the tasks are reasonably allocated to each node.
[0162] Use task scheduling algorithms (such as load balancing algorithms) to dynamically allocate control tasks to ensure load balancing of each node.
[0163] Configure the task scheduling strategy to dynamically adjust task allocation to adapt to changes in system load:
[0164] Dynamically adjust the task allocation strategy according to the system operating status and load conditions to ensure efficient operation of the system.
[0165] Use dynamic task scheduling algorithms (such as dynamic load balancing algorithms) to monitor node loads in real time and dynamically adjust task allocation to avoid overloading certain nodes.
[0166] Task scheduling algorithm:
[0167] Load balancing algorithm:
[0168] This algorithm is used to calculate the load of each node according to the task requirements (T j ) and node computing power (C i ), dynamically adjust task allocation to ensure system load balancing.
[0169] Network security configuration:
[0170] Encrypted communication protocol: Use SSL / TLS protocol to encrypt data transmission. Formula:
[0171] EncryptedData=Encrypt(Data,Key)
[0172] Data is encrypted through encryption algorithms to ensure data security during transmission and prevent data leakage and tampering.
[0173] The S2 step specifically includes the following steps:
[0174] S2.1. Digital twin model creation:
[0175] Collect various data of the physical control station, including status information, operation logs and environmental parameters;
[0176] Build a digital twin model;
[0177] S2.2, Data collection and transmission:
[0178] Deploy sensors and data acquisition equipment to collect real-time operating data from physical control stations;
[0179] Configure data transfer protocols to transfer the collected data to the digital twin model;
[0180] S2.3, Real-time synchronization:
[0181] Using data synchronization algorithms, the data of the physical control station is synchronized to the digital twin model in real time;
[0182] Set synchronization frequency and data update strategy;
[0183] S2.4, status monitoring:
[0184] Monitor the status of the digital twin model in real time and detect abnormal situations;
[0185] Configure the alarm mechanism to issue an alarm in time when an abnormality is detected.
[0186] Specifically, the present invention achieves the following effects through a specific S2 step, that is, creating a digital twin for each physical control station to achieve real-time synchronization between the physical system and the virtual system:
[0187] Synchronize the data and status of the physical control station and the digital twin in real time to ensure the consistency and accuracy of data within the system and avoid control errors caused by data asynchrony.
[0188] Digital twin technology can simulate and predict the future state of physical systems, identify potential problems in advance, and provide a basis for preventive maintenance.
[0189] By real-time monitoring of the status of the digital twin model, abnormal situations can be detected in a timely manner and responded to quickly, thus improving the system's monitorability and management efficiency.
[0190] The technical solution of this step can effectively solve the following problems:
[0191] Data out of sync:
[0192] In traditional control systems, there are delays and inconsistencies in data synchronization between physical control stations and data management systems, resulting in reduced control accuracy.
[0193] Lack of predictive ability:
[0194] Traditional control systems mainly rely on real-time data and lack the ability to predict and analyze future conditions, making it difficult to perform preventive maintenance.
[0195] Incomplete system monitoring:
[0196] In traditional systems, monitoring methods are limited and it is impossible to monitor the system status in real time and comprehensively, resulting in delayed fault detection.
[0197] Its specific technical content:
[0198] S2.1 Digital twin model creation:
[0199] Collect various data of the physical control station, including status information, operation logs and environmental parameters:
[0200] Through sensors and data acquisition equipment, the operation data of the physical control station is collected, including real-time status, historical operation logs and environmental parameters.
[0201] Install temperature sensors, pressure sensors and other equipment to collect environmental parameters such as temperature and pressure; record operation logs to track the operation history of the control station.
[0202] Building a digital twin model:
[0203] Based on the collected data, a digital twin model of the physical control station is established to simulate its operating status and behavior.
[0204] Use modeling tools (such as Simulink, ANSYS, etc.) to create physical state models, operational behavior models, and predictive analysis models.
[0205] S2.2 Data collection and transmission:
[0206] Deploy sensors and data acquisition equipment to collect real-time operating data of the physical control station:
[0207] Deploy sensors and data acquisition equipment at physical control stations to ensure that operational data can be collected in real time.
[0208] Install sensors and configure data acquisition equipment to ensure the real-time and accuracy of data collection.
[0209] Configure the data transmission protocol to transfer the collected data to the digital twin model:
[0210] Configure data transmission protocols to ensure that data can be transferred to the digital twin model quickly and accurately.
[0211] Use transmission protocols such as MQTT and HTTP to configure data transmission paths and frequencies to ensure efficient and reliable data transmission.
[0212] S2.3 Real-time Sync:
[0213] Using the data synchronization algorithm, the data of the physical control station is synchronized to the digital twin model in real time:
[0214] An efficient data synchronization algorithm is used to ensure that the data of the physical control station can be updated to the digital twin model in real time.
[0215] Use time series database and stream processing technology to achieve real-time synchronization and processing of data.
[0216] Set the synchronization frequency and data update strategy:
[0217] According to system requirements, set a reasonable data synchronization frequency and update strategy to ensure the timeliness and accuracy of data.
[0218] Adjust the synchronization interval and update strategy according to the importance of the control task and the frequency of data changes to ensure the real-time performance of key data.
[0219] S2.4 Status Monitoring:
[0220] Monitor the status of the digital twin model in real time and detect anomalies:
[0221] The monitoring system can monitor the status of the digital twin model in real time and identify abnormal situations.
[0222] Set up a status monitoring dashboard to display key parameters and status information in real time, and use anomaly detection algorithms (such as cluster analysis and threshold monitoring) to identify anomalies.
[0223] Configure the alarm mechanism to issue an alarm in time when an abnormality is detected:
[0224] Configure the alarm mechanism to ensure that when an abnormality is detected, an alarm can be issued in time to remind operators to take corresponding measures.
[0225] Set alarm rules and thresholds. When the monitoring data exceeds the normal range, the alarm is triggered and notifications are sent to relevant personnel.
[0226] Data synchronization algorithm formula:
[0227] During data synchronization, you can use stream processing frameworks such as Apache Kafka and Flink to achieve efficient data synchronization.
[0228] For time series data, Kalman filters can be used for real-time data synchronization and prediction.
[0229]
[0230] in, is the state estimate for the current time step, is a priori estimate, K k is the Kalman gain, y k is the observation value, and H is the observation matrix.
[0231] This formula updates the state of the digital twin model in real time by combining current observations and prior estimates, ensuring the real-time and accuracy of the data.
[0232] Anomaly detection formula:
[0233] Anomaly detection can use statistical methods or machine learning algorithms, such as control chart methods based on mean and standard deviation: Among them, X is the data value monitored in real time, μ is the mean of the data, σ is the standard deviation of the data, and Z is the standardized value.
[0234] When the Z value exceeds the preset range (such as ±3), it is judged as an abnormal situation and the alarm mechanism is triggered.
[0235] This formula analyzes real-time monitoring data through statistical methods, detects abnormal situations in a timely manner, and ensures the stable operation of the system.
[0236] The S3 step specifically includes the following steps:
[0237] S3.1、Blockchain network construction:
[0238] Choose a suitable blockchain platform, such as Hyperledger Fabric or Ethereum;
[0239] Deploy blockchain nodes on each edge node to form a blockchain network;
[0240] S3.2, Data structure design:
[0241] Design data structures for control station status and operation logs;
[0242] Define the format and protocol for data storage on the blockchain;
[0243] S3.3. Data on-chain:
[0244] Write smart contracts for data on-chain, and record the status and operation logs of the control station into the blockchain;
[0245] Regularly package the latest status and operation logs of the control station into blocks and broadcast them to the blockchain network;
[0246] S3.4, consensus algorithm:
[0247] Configure the consensus algorithm of the blockchain network, such as Raft or PBFT;
[0248] Set up consensus nodes and voting mechanisms.
[0249] Specifically, the present invention achieves the following effects through the specific S3 step, that is, distributing and storing the status and operation logs of the control station through blockchain technology:
[0250] The decentralized and tamper-proof characteristics of blockchain ensure the storage security of control station data and prevent data from being tampered with or lost.
[0251] Through blockchain technology, all operation logs and status data are recorded in the blockchain, forming an unalterable record, which enhances the transparency and traceability of the data.
[0252] Through the consensus algorithm of the distributed blockchain network, the system can still operate normally even if some nodes fail, thus improving the system's fault tolerance.
[0253] The technical solution of this step can effectively solve the following problems:
[0254] Traditional centralized storage systems are vulnerable to attacks and data may be tampered with or lost.
[0255] Data records in traditional systems may be incomplete or untraceable, making it difficult to trace and verify the authenticity of the data when problems arise.
[0256] Centralized storage systems have the risk of single point failure. Once a problem occurs in the central storage node, the entire system will not be able to operate normally.
[0257] Its specific technical content:
[0258] S3.1 Blockchain network construction:
[0259] Choose a suitable blockchain platform such as Hyper ledger Fabric or Ethereum:
[0260] Choose a suitable blockchain platform according to system requirements. Hyper ledger Fabric is suitable for permissioned chains, and Ethereum is suitable for public chains.
[0261] Evaluate the performance, security, and scalability of each platform and choose the most suitable blockchain platform.
[0262] Deploy blockchain nodes on each edge node to form a blockchain network:
[0263] Install and configure blockchain node software on each edge node to form a decentralized blockchain network.
[0264] Complete the installation and configuration of the node software to ensure that the node can participate in the consensus and data storage of the blockchain network.
[0265] S3.2 Data structure design:
[0266] Design the data structure of the control station status and operation log:
[0267] Design data structures based on system requirements, including the status information of the control station and the format of the operation log.
[0268] Define data fields and types to ensure normalization and consistency of data structures.
[0269] Define the format and protocol for data storage on the blockchain:
[0270] Determine the storage format and transmission protocol of data on the blockchain to ensure efficient storage and transmission of data.
[0271] Use data formats such as JSON and Protobuf to define the data storage format, and use protocols such as gRPC and HTTP to define the data transmission method.
[0272] S3.3 Data on-chain:
[0273] Write a smart contract for data on-chain, and record the status and operation logs of the control station into the blockchain:
[0274] Write smart contracts to define the logic of data on-chain, including data verification, storage, and update.
[0275] Use Solidity (Ethereum) or Chaincode (Hyperledger Fabric) to write smart contracts to ensure the security and accuracy of data on the chain.
[0276] Regularly package the latest status and operation logs of the control station into blocks and broadcast them to the blockchain network:
[0277] The status and operation logs of the control station are regularly packaged into blocks and broadcast through the blockchain network to ensure that all nodes update the data synchronously.
[0278] Set up scheduled tasks, call smart contracts regularly, package the latest data into blocks, and broadcast them through the blockchain network.
[0279] S3.4 consensus algorithm:
[0280] Configure the consensus algorithm of the blockchain network, such as Raft or PBFT:
[0281] Choose a suitable consensus algorithm to ensure data consistency and reliability in the blockchain network.
[0282] Configure the consensus algorithm of Raft (suitable for efficient consensus) or PBFT (suitable for high security requirements) according to system requirements.
[0283] Set up consensus nodes and voting mechanism:
[0284] Configure the roles and voting mechanisms of consensus nodes to ensure consensus verification before data is written to the blockchain.
[0285] Define the number of consensus nodes and election rules, and set up a voting mechanism to ensure high data reliability.
[0286] Consensus algorithm formula:
[0287] Raft consensus algorithm: Leader election and log replication.
[0288] Term=max(currentterm,receivedterm)
[0289] Log = append (receivedlog)
[0290] This formula is used in the leader election and log replication process. It determines the leader node by comparing the current term with the received term, and achieves data consistency through log appending.
[0291] Data on-chain smart contract formula:
[0292] Data on-chain smart contract implementation: Solidity example:
[0293]
[0294]
[0295] The smart contract defines the data structure and storage method to achieve on-chain storage of control station status and operation logs, ensuring the security and reliability of data.
[0296] The S4 step specifically includes the following steps:
[0297] S4.1. Smart contract writing:
[0298] Write smart contracts to define the triggering conditions for redundant switching;
[0299] Define the execution logic of redundant switching in the smart contract, including task transfer and data synchronization operations;
[0300] S4.2, Contract deployment:
[0301] Deploy the written smart contract to the blockchain network;
[0302] Set the calling permissions and triggering mechanism of the smart contract;
[0303] S4.3. Testing and verification:
[0304] Test smart contracts, simulate various trigger conditions, and verify the correctness of redundant switching logic;
[0305] Fix errors in smart contracts;
[0306] S4.4. Monitoring and updating:
[0307] Configure the operation monitoring mechanism of the smart contract to monitor the execution of the smart contract in real time;
[0308] Smart contracts are regularly updated and optimized according to system requirements.
[0309] The triggering conditions in step S4.1 include edge node failure, performance degradation of edge nodes, and communication interruption of edge nodes.
[0310] Specifically, the present invention achieves the following effects through the specific S4 step, that is, using the smart contract on the blockchain to define the triggering conditions and execution logic of the redundant switching:
[0311] The automation of redundant switching is achieved through smart contracts, which reduces human intervention and improves the system's automation and response speed.
[0312] Smart contracts ensure the consistency and accuracy of the redundant switching process, enhancing the reliability and stability of the system.
[0313] Smart contracts can flexibly define and update redundant switching logic according to actual needs to adapt to the continuous changes and expansion of the system.
[0314] The technical solution of this step can effectively solve the following problems:
[0315] In traditional control systems, redundant switching relies on manual intervention, which can easily lead to system failures if the response is not timely.
[0316] The redundant switching process with manual intervention may have operational inconsistencies and errors, affecting system stability.
[0317] The switching logic in traditional systems is fixed and difficult to flexibly adjust and optimize according to actual needs.
[0318] S4.1 Smart Contract Writing:
[0319] Write a smart contract to define the triggering conditions for redundant switching:
[0320] Write smart contracts to define trigger conditions for redundancy switching, such as edge node failure, performance degradation, and communication interruption.
[0321] Specific implementation: Use Solidity (Ethereum) or Chaincode (HyperledgerFabric) to write contracts and define trigger conditions.
[0322]
[0323]
[0324] Define the execution logic of redundant switching in the smart contract, including task transfer and data synchronization operations:
[0325] Define the specific logic of task transfer and data synchronization to ensure the integrity and consistency of the switching process.
[0326] Write execution functions in smart contracts to ensure that task transfer and data synchronization are automatically executed when the trigger conditions are met.
[0327] S4.2 Contract deployment:
[0328] Deploy the written smart contract to the blockchain network:
[0329] Deploy smart contracts to the blockchain network to ensure that they can run on the network.
[0330] Use the blockchain platform's deployment tools (such as Remix, Truffle) to deploy the contract to the Ethereum or Hyperledger Fabric network.
[0331] Set the calling permissions and triggering mechanism of the smart contract:
[0332] Configure the calling permissions of the smart contract to ensure that only authorized nodes can update the status and trigger the switch.
[0333] Define permission control logic in smart contracts to ensure the security and correctness of the contracts.
[0334] S4.3 Testing and verification:
[0335] Test the smart contract, simulate various trigger conditions, and verify the correctness of the redundant switching logic:
[0336] Through the simulated test environment, the execution effect of the smart contract under different trigger conditions is verified.
[0337] Use blockchain testing tools (such as Ganache, HyperledgerCaliper) to test the contract to ensure its logical correctness.
[0338] Fix errors in smart contracts:
[0339] Based on the test results, correct the logical errors and vulnerabilities in the smart contract.
[0340] Ensure the stability and security of smart contracts through iterative development and testing.
[0341] S4.4 Monitoring and updating:
[0342] Configure the operation monitoring mechanism of the smart contract to monitor the execution of the smart contract in real time:
[0343] Configure monitoring tools to track the execution status and effects of smart contracts in real time.
[0344] Use blockchain monitoring tools (such as Etherscan, HyperledgerExplorer) to monitor the execution of the contract and record operation logs.
[0345] Regularly update and optimize smart contracts according to system requirements:
[0346] Regularly evaluate the execution effect of smart contracts and update and optimize them according to actual needs.
[0347] Manage and update smart contracts through version control and continuous integration tools (such as Git and Jenkins) to ensure that they adapt to changes in system requirements.
[0348] Trigger condition formula:
[0349] Define formulas for trigger conditions, including node failure, performance degradation, and communication loss.
[0350] Trigger=(isFaulty==true)||(performance<50)||(isConnected==false)
[0351] This formula is used to determine whether the triggering condition for redundant switching is met, ensuring the clarity and consistency of the triggering condition.
[0352] Task transfer and data synchronization formula:
[0353] Define the formulas for task migration and data synchronization to ensure the integrity of the switching process.
[0354]
[0355] DataSync=Sync(OldNode,NewNode)
[0356] This formula is used to select new task nodes and synchronize data to ensure seamless task transfer and data consistency.
[0357] The redundant switching operation in step S5 includes the following steps:
[0358] S5.1. Trigger condition monitoring:
[0359] Deploy a monitoring mechanism on each edge node to monitor the node's operating status and performance indicators in real time;
[0360] When the trigger condition is detected to be met, a trigger signal is immediately sent to the blockchain network;
[0361] S5.2. Smart Contract Execution:
[0362] After the blockchain network receives the trigger signal, it automatically calls the smart contract;
[0363] Smart contracts perform redundant switching operations according to preset logic;
[0364] S5.3, Task Transfer:
[0365] Transfer the control task of the failed node to the backup node;
[0366] The backup node has synchronized all necessary data of the failed node through digital twin technology and immediately takes over the control task;
[0367] S5.4, Data Synchronization:
[0368] After the standby node takes over the task, it continues to synchronize data through digital twin technology;
[0369] S5.5. Log Records:
[0370] Every step of the smart contract execution is recorded on the blockchain, forming an unalterable operation log;
[0371] Through the blockchain network, all nodes share these operation logs.
[0372] Specifically, the present invention achieves the following effects through the specific S5 step, that is, when the edge node detects the preset trigger condition, the smart contract automatically executes the redundant switching operation:
[0373] Through real-time monitoring and automatic triggering of redundant switching, manual intervention is reduced and the system's response speed and efficiency are improved.
[0374] Through digital twin technology and data synchronization mechanism, data consistency is ensured when the backup node takes over the task, avoiding control errors.
[0375] Each operation log is recorded through blockchain to ensure the transparency and traceability of the operation, which is convenient for auditing and management.
[0376] Automatically perform redundant switching and task transfer, reducing system downtime and enhancing system reliability and stability.
[0377] The technical solution of this step can effectively solve the following problems:
[0378] Traditional systems rely on manual fault detection and redundant switching, which has a slow response speed and easily leads to system downtime.
[0379] During the redundant switching process, untimely data synchronization can easily lead to data inconsistency and affect system operation.
[0380] Operation records in traditional systems are incomplete and difficult to track and audit.
[0381] There is a lack of automatic redundant switching mechanism, and single point failure has a great impact on system operation.
[0382] Its specific technical content:
[0383] S5.1 Trigger condition monitoring:
[0384] A monitoring mechanism is deployed on each edge node to monitor the node's operating status and performance indicators in real time:
[0385] Deploy sensors and monitoring software to collect node operation status and performance indicators in real time, such as CPU load, memory usage, network connection status, etc.
[0386] Use monitoring tools (such as Prometheus, Nagi os) to deploy monitoring mechanisms to collect and analyze node operation data in real time.
[0387] When the trigger condition is detected, a trigger signal is immediately sent to the blockchain network:
[0388] Configure trigger conditions to automatically send trigger signals to the blockchain network when node failure, performance degradation, or communication interruption is detected.
[0389] Set monitoring thresholds and alarm rules to automatically trigger signal sending when indicators exceed the normal range.
[0390] S5.2 Smart Contract Execution:
[0391] After the blockchain network receives the trigger signal, it automatically calls the smart contract:
[0392] The smart contract is called by the trigger signal and starts to execute the preset redundant switching logic.
[0393] Configure the trigger function in the smart contract, and automatically execute the redundant switching logic after receiving the trigger signal.
[0394] The smart contract performs redundant switching operations according to the preset logic:
[0395] Smart contracts perform task transfer and data synchronization operations according to defined logic.
[0396] The code logic for implementing task transfer and data synchronization in smart contracts ensures the integrity and consistency of the switching process.
[0397] S5.3 Task transfer:
[0398] Transfer the control task of the failed node to the standby node:
[0399] When a failed node cannot continue to execute tasks, the tasks are automatically transferred to the backup node.
[0400] The smart contract calls the control interface of the backup node to transfer the task execution rights.
[0401] The backup node has synchronized all necessary data of the failed node through digital twin technology and immediately takes over the control task:
[0402] The backup node uses digital twin technology to keep data synchronized with the failed node and can take over the task immediately.
[0403] The backup nodes synchronize data regularly to ensure data consistency through the digital twin model.
[0404] S5.4 Data Synchronization:
[0405] After the standby node takes over the task, it continues to synchronize data through digital twin technology:
[0406] After the standby node takes over the task, it continues to synchronize data in real time to ensure the normal operation of the system.
[0407] Use data synchronization algorithms (such as time series database synchronization and stream processing technology) to perform real-time data synchronization.
[0408] S5.5 Logging:
[0409] Every step of the smart contract execution is recorded on the blockchain, forming an unalterable operation log:
[0410] All redundant switching operations and task transfer processes are recorded on the blockchain, forming an unalterable operation log.
[0411] Every time a smart contract executes an operation, it writes relevant records to the blockchain to ensure the integrity and traceability of the log.
[0412] Through the blockchain network, all nodes share these operation logs:
[0413] Through the distributed storage mechanism of the blockchain network, it is ensured that all nodes share operation logs and increase system transparency.
[0414] Use the consensus mechanism of the blockchain network to ensure that log records are synchronized and shared among all nodes.
[0415] In step S1.2, the edge computing device can be one or more of an industrial controller, an embedded computing device or an edge server.
[0416] The digital twin model in step S2.1 includes a physical state model, an operational behavior model, and a predictive analysis module.
[0417] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the appended claims and their equivalents.
Claims
1. A method for redundant switching between redundant process control stations in a distributed control system, It is characterized in that The following steps are involved: S1. Use edge computing technology to distribute control functions to multiple edge nodes close to data sources; S2. Create a digital twin for each physical control station to achieve real-time synchronization between the physical and virtual systems; S3, distribute and store the status and operation logs of the control station through blockchain technology; S4. Use smart contracts on the blockchain to define the triggering conditions and execution logic of redundant switching; S5. When the edge node detects the preset trigger condition, the smart contract automatically performs the redundant switching operation.
2. A method for redundant switching between redundant process control stations in a distributed control system according to claim 1, It is characterized in that The S1 step specifically includes the following steps: S1.
1. Node selection: Select the appropriate edge node location based on the location of the data source and control requirements; Determine the hardware configuration of each edge node; S1.2, Node deployment: Install and configure edge computing devices such as industrial controllers, embedded computing devices, or edge servers; Deploy the control station application to each edge node; S1.
3. Network configuration: Configure network connections between edge nodes; Setting up network security measures, such as firewalls and encrypted communications; S1.4 Task Allocation: Assign control tasks to different edge nodes; Configure task scheduling strategies to dynamically adjust task allocation to adapt to changes in system load.
3. A method for redundant switching between redundant process control stations in a distributed control system according to claim 1, It is characterized in that The S2 step specifically includes the following steps: S2.
1. Creation of digital twin model: Collect various data of the physical control station, including status information, operation logs and environmental parameters; Build a digital twin model; S2.2, Data collection and transmission: Deploy sensors and data acquisition equipment to collect real-time operating data from physical control stations; Configure data transfer protocols to transfer the collected data to the digital twin model; S2.3, Real-time synchronization: Using data synchronization algorithms, the data of the physical control station is synchronized to the digital twin model in real time; Set synchronization frequency and data update strategy; S2.4, status monitoring: Monitor the status of the digital twin model in real time and detect abnormal situations; Configure the alarm mechanism to issue an alarm in time when an abnormality is detected.
4. A method for redundant switching between redundant process control stations in a distributed control system according to claim 1, It is characterized in that The S3 step specifically includes the following steps: S3.1、Blockchain network construction: Choose a suitable blockchain platform, such as Hyperledger Fabric or Ethereum; Deploy blockchain nodes on each edge node to form a blockchain network; S3.2, Data structure design: Design data structures for control station status and operation logs; Define the format and protocol for data storage on the blockchain; S3.
3. Data on-chain: Write smart contracts for data on-chain, and record the status and operation logs of the control station into the blockchain; Regularly package the latest status and operation logs of the control station into blocks and broadcast them to the blockchain network; S3.4, consensus algorithm: Configure the consensus algorithm of the blockchain network, such as Raft or PBFT; Set up consensus nodes and voting mechanisms.
5. A method for redundant switching between redundant process control stations in a distributed control system according to claim 1, It is characterized in that The S4 step specifically includes the following steps: S4.
1. Smart contract writing: Write smart contracts to define the triggering conditions for redundant switching; Define the execution logic of redundant switching in the smart contract, including task transfer and data synchronization operations; S4.2, Contract deployment: Deploy the written smart contract to the blockchain network; Set the calling permissions and triggering mechanism of the smart contract; S4.
3. Testing and verification: Test smart contracts, simulate various trigger conditions, and verify the correctness of redundant switching logic; Fix errors in smart contracts; S4.
4. Monitoring and updating: Configure the operation monitoring mechanism of the smart contract to monitor the execution of the smart contract in real time; Smart contracts are regularly updated and optimized according to system requirements.
6. A method for redundant switching between redundant process control stations in a distributed control system according to claim 5, It is characterized in that The triggering conditions in step S4.1 include edge node failure, performance degradation of edge nodes, and communication interruption of edge nodes.
7. A method for redundant switching between redundant process control stations in a distributed control system according to claim 1, It is characterized in that The redundant switching operation in step S5 includes the following steps: S5.
1. Trigger condition monitoring: Deploy a monitoring mechanism on each edge node to monitor the node's operating status and performance indicators in real time; When the trigger condition is detected to be met, a trigger signal is immediately sent to the blockchain network; S5.
2. Smart Contract Execution: After the blockchain network receives the trigger signal, it automatically calls the smart contract; Smart contracts perform redundant switching operations according to preset logic; S5.3, Task Transfer: Transfer the control task of the failed node to the backup node; The backup node has synchronized all necessary data of the failed node through digital twin technology and immediately takes over the control task; S5.4, Data Synchronization: After the standby node takes over the task, it continues to synchronize data through digital twin technology; S5.
5. Log Records: Every step of the smart contract execution is recorded on the blockchain, forming an unalterable operation log; Through the blockchain network, all nodes share these operation logs.
8. A method for redundant switching between redundant process control stations in a distributed control system according to claim 2, It is characterized in that The edge computing device in step S1.2 may be one or more of an industrial controller, an embedded computing device or an edge server.
9. A method for redundant switching between redundant process control stations in a distributed control system according to claim 3, It is characterized in that The digital twin model in step S2.1 includes a physical state model, an operation behavior model and a prediction and analysis module.
Citation Information
Cited By
IOT edge communication base station for verification of flexible intelligent driving electric energy meter
CN120075313A
