Operation and maintenance emergency process management system and method based on intelligent contract and consensus mechanism

Abstract

The invention relates to an operation and maintenance emergency process management system and method based on an intelligent contract and a consensus mechanism, the system comprises an emergency management module, an intelligent contract module and a consensus mechanism module, the method comprises the following steps: collecting monitoring data in different monitoring system nodes, different monitoring data corresponding to different scenes; calling a judgment type intelligent contract, performing emergency scene judgment according to the collected different monitoring data, and outputting to obtain a plurality of emergency scene judgment results; performing consensus processing on the plurality of emergency scene judgment results to obtain an emergency scene consensus result; based on an emergency scene consensus result, calling a disposal type smart contract, creating an emergency work order, associating the emergency scene with a corresponding emergency disposal command, and disposing related assets; and calling a recording type intelligent contract, and recording a disposal result and emergency process information. Compared with the prior art, the method can effectively solve the problems of decision delay and errors in the emergency process caused by individual experience differences.

Description

Technical Field

[0001] This invention relates, and in particular, to an operation and maintenance emergency process management system and method based on smart contracts and consensus mechanisms. Background Technology

[0002] Emergency management refers to the deployment and management of measures for emergency and abnormal operational situations that occur during data center operations and maintenance. Data center infrastructure operations may encounter emergencies, which pose the greatest challenge to the reliability and business continuity of data center infrastructure. Identifying and handling emergencies is a crucial indicator of operational capability. The purpose of emergency management is to handle sudden emergencies promptly and correctly, achieving the expected results, reducing or eliminating impact, and restoring the availability of data center infrastructure systems. The scope of emergency management includes all emergencies that arise during infrastructure operations and maintenance.

[0003] Traditional emergency management in operations and maintenance (O&M) often involves reactive responses after an O&M failure or sudden event. This stage primarily focuses on emergency measures and post-disaster reconstruction, characterized by its temporary, passive, and localized nature. Within this framework, it encompasses various response phases, including prevention and preparedness, monitoring and early warning, emergency response, and post-event recovery and reconstruction. Effective management of each phase evolves from initial manual processing to subsequent information-based processing. However, throughout this process, the coordination between each phase relies entirely on human judgment and handling. For example, emergency prevention and preparedness depend on intuitive judgments based on past experience; whether to enter an emergency and the subsequent response methods are also human choices. Due to individual differences, differing judgments can easily arise, and human negligence can lead to decision-making delays and errors during the emergency process. Summary of the Invention

[0004] The purpose of this invention is to overcome the shortcomings of the existing technology by providing an operation and maintenance emergency process management system and method based on smart contracts and consensus mechanisms, and to solve the problem of decision-making delays and errors caused by individual experience differences during the emergency process.

[0005] The objective of this invention can be achieved through the following technical solution: an operation and maintenance emergency process management system based on smart contracts and consensus mechanisms, including an emergency management module, a smart contract module, and a consensus mechanism module. The emergency management module is used to collect and store monitoring data from different scenarios and transmit it to the smart contract module, as well as convert it into emergency response commands and create emergency work orders.

[0006] The smart contract module is used to determine emergency scenarios, handle emergency response commands, and process emergency work orders.

[0007] The consensus mechanism module is used to process the judgment results of different emergency scenarios through consensus processing.

[0008] Furthermore, the emergency management module is connected to multiple monitoring system nodes to collect monitoring data for different scenarios.

[0009] A method for managing operational emergency processes based on smart contracts and consensus mechanisms includes the following steps:

[0010] A1. Collect monitoring data from different monitoring system nodes, where different monitoring data correspond to different scenarios;

[0011] A2. Call the judgment-type smart contract to make emergency scenario judgments based on different collected monitoring data, and output multiple emergency scenario judgment results;

[0012] A3. Perform consensus processing on the judgment results of multiple emergency scenarios to obtain the consensus results of the emergency scenarios;

[0013] A4. Based on the consensus results of the emergency scenario, call the disposal smart contract to create an emergency work order, associate the emergency scenario with the corresponding emergency disposal command, and dispose of the relevant assets.

[0014] A5. Call the recording smart contract to record the handling results and emergency process information.

[0015] Furthermore, the monitoring data in step A1 includes host emergency scenario data, network emergency scenario data, service emergency scenario data, emergency response data, emergency response process data, and scenario data weights.

[0016] Furthermore, the host emergency scenario data includes the duration of host disconnection, the list of services deployed on the host, host port listening information, host core file information, and host syslog logs;

[0017] The network emergency scenario data includes network device logs, network device packet loss rate, network device latency, and dial-up test logs;

[0018] The service emergency scenario data includes a service list, service restart count, service port listening data, service link data, average service response time, average service execution time, number of non-200 return codes, and number of service error logs.

[0019] The emergency response data includes emergency response command steps, execution time, and execution results;

[0020] The emergency response process data includes work order name, status, previous step information, next step information, type, dependencies, associated templates, notification strategy, and notification personnel;

[0021] The scenario data weights include weights for disconnection, packet loss rate, core file, listener loss, latency, test failure, service restart, and response time.

[0022] Further, step A2 includes the following steps:

[0023] A21. Pre-screen the monitoring data. When the weight of the monitoring data for a certain scenario exceeds the preset ratio of the weight of the data for other scenarios, record the scenario ID.

[0024] A22. When the monitoring data weights of multiple scenarios are θc1-θ C If the difference is within the preset threshold, then record multiple scene IDs.

[0025] Furthermore, the specific process of step A3 is as follows: signing is performed using a public key for different scenario IDs;

[0026] When more than 2N+1 monitoring system nodes receive the signature of a certain scenario ID, it indicates that different nodes have reached a consensus on the judgment of the emergency scenario and broadcast the scenario ID.

[0027] Furthermore, step A4 specifically includes the following steps:

[0028] A41. Based on the agreed-upon scenario ID, invoke the disposal smart contract to create an emergency work order and associate the emergency scenario with the corresponding emergency disposal command;

[0029] A42. Execute emergency response orders and dispose of the relevant assets.

[0030] Furthermore, the emergency response command is specifically a computer-recognizable command corresponding to emergency process operation behavior.

[0031] Furthermore, the emergency process information recorded in step A5 includes emergency response time and emergency monitoring data, and the emergency monitoring data includes relevant data before, during, and after the emergency.

[0032] Compared with the prior art, the present invention has the following advantages:

[0033] This invention establishes an emergency management module, a smart contract module, and a consensus mechanism module. The emergency management module collects and stores monitoring data from different scenarios and transmits it to the smart contract module, converting it into emergency response commands and creating emergency work orders. The smart contract module determines the emergency scenario, processes the emergency response commands, and handles the emergency work orders. The consensus mechanism module performs consensus processing on the judgment results for different emergency scenarios. By running smart contracts during emergency operations, relevant steps in the emergency process are automatically triggered under preset conditions, solving problems such as errors and delays caused by individual differences in experience. Through the node consensus mechanism, consensus and confirmation can be reached for complex emergency scenarios in a very short time, thereby triggering smart contracts, reducing human judgment factors, and solving the problems of decision-making delays and errors in emergency management.

[0034] This invention designs a judgment-type smart contract, a disposal-type smart contract, and a recording-type smart contract. The judgment-type smart contract assesses emergency scenarios based on different collected monitoring data; the disposal-type smart contract invokes and executes emergency disposal commands; and the recording-type smart contract processes emergency work orders, recording the disposal results and data from the entire emergency process. By using smart contracts, emergency steps in consensus-based emergency scenarios are automatically executed, improving disposal efficiency and avoiding errors in individual handling processes.

[0035] This invention performs consensus processing on the judgment results of multiple emergency scenarios to obtain a consensus result for the emergency scenario. By adopting a consensus mechanism, the monitoring data collected by different nodes can be automatically formed into a corresponding situation of an emergency scenario without relying on individual experience, which greatly improves the efficiency of emergency judgment and avoids the impact of individual differences on the judgment of emergency scenarios. Attached Figure Description

[0036] Figure 1 This is a schematic diagram of the system structure of the present invention;

[0037] Figure 2 This is a schematic diagram of the method flow of the present invention;

[0038] Figure 3 This is a schematic diagram of the application framework for an example.

[0039] The markings in the diagram are as follows: 1. Emergency Management Module, 2. Smart Contract Module, 3. Consensus Mechanism Module. Detailed Implementation

[0040] The present invention will now be described in detail with reference to the accompanying drawings and specific embodiments.

[0041] Example

[0042] like Figure 1As shown, an operation and maintenance emergency process management system based on smart contracts and consensus mechanisms includes an emergency management module 1, a smart contract module 2, and a consensus mechanism module 3. The emergency management module 1 and the consensus mechanism module 3 are interactively connected to the smart contract module 2, respectively. The emergency management module 1 is connected to multiple monitoring system nodes to collect and store monitoring data for different scenarios, transmit the data to the smart contract module 2, and convert it into emergency response commands and create emergency work orders.

[0043] Smart contract module 2 is used to determine emergency scenarios, handle emergency response commands, and process emergency work orders;

[0044] Consensus mechanism module 3 is used to process the consensus results of different emergency scenarios.

[0045] Based on the above system, a method for managing operational emergency processes based on smart contracts and consensus mechanisms is implemented, such as... Figure 2 As shown, it includes the following steps:

[0046] A1. Collect monitoring data from different monitoring system nodes, where different monitoring data correspond to different scenarios;

[0047] A2. Call the judgment-type smart contract to make emergency scenario judgments based on different collected monitoring data, and output multiple emergency scenario judgment results;

[0048] A3. Perform consensus processing on the judgment results of multiple emergency scenarios to obtain the consensus results of the emergency scenarios;

[0049] A4. Based on the consensus results of the emergency scenario, call the disposal smart contract to create an emergency work order, associate the emergency scenario with the corresponding emergency disposal command, and dispose of the relevant assets.

[0050] A5. Call the recording smart contract to record the handling results and emergency process information.

[0051] This embodiment applies the above-described solution, such as Figure 3 As shown, the system comprises three modules: an emergency management module, a smart contract module, and a consensus mechanism module. The smart contract and consensus mechanism modules provide the core functionality of the system, while the emergency management module serves as a platform for handling contingency plans for various emergency scenarios.

[0052] Emergency Management Module: An information module suitable for managing emergency processes in operation and maintenance. In this system, the emergency management module highly abstracts various scenarios. Essentially, it can be understood as various general emergency management systems. Its main purpose is to provide relevant data to smart contracts, set the handling methods for various emergency scenarios, and integrate with emergency procedures. Specifically, the emergency management module's functions include the following steps:

[0053] Step 1: Collect and store monitoring data from different scenarios, and be able to interface with various monitoring systems to obtain data from the following dimensions:

[0054] 1. Host emergency scenario data (duration of host outage, list of services deployed on the host, host port listening information, host core file information, host syslog logs);

[0055] 2. Network emergency scenario data (network device logs, network device packet loss rate, network device latency, dial-up test logs);

[0056] 3. Service emergency scenario data (service list, service restart count, service port listening data, service link data, service average response time, service average execution time, number of services with non-200 return codes, number of service error logs);

[0057] 4. Emergency response data (emergency response command steps, execution time, execution results);

[0058] 5. Emergency response process data (work order name, status, previous step information, next step information, type, dependencies, associated templates, notification strategy, notified personnel);

[0059] 6. Scenario data weights (weights for disconnection, packet loss rate, core file, listener loss, latency, test failure, service restart, response time, etc.).

[0060] Step 2: For the management of emergency plans, the operational behaviors during the emergency process are abstracted into command methods that computers can recognize, including but not limited to using shell scripts, Python, Go, Rust and other languages.

[0061] Step 3: Create an emergency work order and associate the emergency scenario with the corresponding emergency response command.

[0062] Smart contract module: By interfacing with the emergency management module, it continuously runs a piece of smart contract code in the background according to different scenarios. Its main functions are:

[0063] 1. Each node calculates the emergency scenario weights defined in its own smart contract based on the collected scenario data and returns the calculation results.

[0064] 2. Relying on the consensus mechanism, the consensus result of emergency scenario data triggers a specific smart contract and calls the relevant handling functions in the emergency management module for automatic handling.

[0065] 3. Use the work order function in the emergency management module to automatically create emergency process work orders and record emergency process information.

[0066] A smart contract is essentially an application that executes automatically under specific conditions. This solution uses the Solidity language to write smart contracts, which are categorized into different types based on their intended function:

[0067] 1. Judgment-based smart contracts: These mainly perform emergency scenario judgments based on the data connected in step 1.

[0068] 2. Handling smart contracts: These are mainly for handling emergency commands in step 2.

[0069] 3. Record-based smart contracts: These are mainly for handling emergency work orders in step 3.

[0070] The steps for writing a smart contract vary depending on the type of smart contract. The steps for writing a conditional smart contract are as follows:

[0071] Step 4: Pre-screen the monitoring data. When the weight of the monitoring data for a certain scenario is much higher than the weight of the data for other scenarios, record the scenario ID.

[0072] Step 5: When the difference between the monitoring data weights θc1-θc2 of multiple scenarios is within 10, record the multiple scenario IDs.

[0073] Step 6: Send the recorded scenario ID to the consensus mechanism module;

[0074] Step 7: After receiving the scenario ID of the consensus result, invoke the disposal smart contract.

[0075] Regarding the steps for writing the disposal-type smart contract in step 7:

[0076] Step 7.1: Using the scene ID obtained in Step 7, call and execute the emergency response command in Step 2.

[0077] Step 7.2: Record the execution result of the emergency response command in Step 2 and call the record-keeping smart contract.

[0078] The steps for writing the record-type smart contract in step 7.2 are as follows:

[0079] Step 8: Record the emergency response time and results, and record emergency monitoring data, including relevant data before, during, and after the emergency, and synchronize them to the consensus mechanism module.

[0080] Consensus Mechanism Module: Monitoring data in the emergency management module is often distributed across multiple systems, essentially forming a distributed system. In this distributed system, different hosts form a network cluster through asynchronous communication. Different monitoring information needs to draw upon existing algorithms for achieving state consensus in distributed systems to ensure that the monitoring data forms a correct and consistent consensus across the entire network, thereby enabling a consensus on the emergency scenario. The consensus mechanism module supports mainstream consensus algorithms, including Raft, Solo, and TBFT. The steps for writing the consensus mechanism module are as follows:

[0081] Step 9: After receiving the scene ID from different nodes N in Step 6, consensus is reached when T... id >=2N+1(T id (This refers to the number of scenario IDs), which means that different nodes reach a consensus on the judgment of the emergency scenario and broadcast the scenario ID.

[0082] In this embodiment, in step 1, subprocess S1 collects monitoring data from different systems. Different monitoring data correspond to different scenarios. The data collected shows that the duration of host disconnection is >0 and the network device delay is >2S. Then, step 4 is executed.

[0083] In step 4, subprocess S2 performs weighted judgment on the data received from S1. S2 determines that host emergency scenario 1 has occurred and records θ. host Emergency scenario 2 for network equipment: Record θ net Then proceed to step 5;

[0084] In step 5, the weights of the two scenes are subtracted |θ host -θ net If |<10, record the two scene IDs, E and E respectively. hostid E netid Then proceed to step 6;

[0085] In step 6, the two scene IDs are signed using the public key to obtain...

[0086] S host =rsasign(E hostid, pubkey,'sha-1') and S net =rsasign(E netid, pubkey,'sha-1')

[0087] Then proceed to step 9;

[0088] In step 9, when more than 2N+1 (N is the number of nodes) have received S host and S netAfter the signature is obtained, the signature is verified by subprocess S3. If it is the same scenario, a consensus is reached. There are two emergency scenarios: host emergency and network device emergency. Then, step 7.1 is executed.

[0089] In step 7.1, sub-process S4 is processed via E hostid and E netid, Associate it with the corresponding emergency response command and proceed to step 2;

[0090] In step 2, sub-process S5 disposes of the relevant assets based on the association passed in S4, records the disposal results, and then executes step 7.2;

[0091] In step 7.2, sub-process S6 executes step 8 based on the recorded information;

[0092] In step 8, the relevant record information is cached, and then step 3 is executed;

[0093] In step 3, subprocess S7 creates an emergency work order based on the cached information, and records the entire automatic emergency process.

Claims

1. A maintenance and emergency response management system based on smart contracts and consensus mechanisms, characterized in that, It includes an emergency management module, a smart contract module, and a consensus mechanism module. The emergency management module is used to collect and store monitoring data from different scenarios and transmit it to the smart contract module, as well as convert it into emergency response commands and create emergency work orders. The smart contract module is used to determine emergency scenarios, handle emergency response commands, and process emergency work orders. The consensus mechanism module is used to process the judgment results of different emergency scenarios through consensus processing.

2. The operation and maintenance emergency process management system based on smart contracts and consensus mechanisms according to claim 1, characterized in that, The emergency management module is connected to multiple monitoring system nodes to collect monitoring data for different scenarios.

3. A method for managing emergency operation and maintenance processes based on smart contracts and consensus mechanisms, applied to the emergency operation and maintenance process management system based on smart contracts and consensus mechanisms as described in claim 1, characterized in that, Includes the following steps: A1. Collect monitoring data from different monitoring system nodes, where different monitoring data correspond to different scenarios; A2. Call the judgment-type smart contract to make emergency scenario judgments based on different collected monitoring data, and output multiple emergency scenario judgment results; A3. Perform consensus processing on the judgment results of multiple emergency scenarios to obtain the consensus results of the emergency scenarios; A4. Based on the consensus results of the emergency scenario, call the disposal smart contract to create an emergency work order, associate the emergency scenario with the corresponding emergency disposal command, and dispose of the relevant assets. A5. Call the recording smart contract to record the handling results and emergency process information.

4. The operation and maintenance emergency process management method based on smart contracts and consensus mechanisms according to claim 3, characterized in that, The monitoring data in step A1 includes host emergency scenario data, network emergency scenario data, service emergency scenario data, emergency response data, emergency response process data, and scenario data weights.

5. The operation and maintenance emergency process management method based on smart contracts and consensus mechanisms according to claim 4, characterized in that, The host emergency scenario data includes the duration of host disconnection, the list of services deployed on the host, host port listening information, host core file information, and host syslog logs. The network emergency scenario data includes network device logs, network device packet loss rate, network device latency, and dial-up test logs; The service emergency scenario data includes a service list, service restart count, service port listening data, service link data, average service response time, average service execution time, number of non-200 return codes, and number of service error logs. The emergency response data includes emergency response command steps, execution time, and execution results; The emergency response process data includes work order name, status, previous step information, next step information, type, dependencies, associated templates, notification strategy, and notification personnel; The scenario data weights include weights for disconnection, packet loss rate, core file, listener loss, latency, test failure, service restart, and response time.

6. The operation and maintenance emergency process management method based on smart contracts and consensus mechanisms according to claim 3, characterized in that, Step A2 includes the following steps: A21. Pre-screen the monitoring data. When the weight of the monitoring data for a certain scenario exceeds the preset ratio of the weight of the data for other scenarios, record the scenario ID. A22. When the monitoring data weights of multiple scenarios are θc1-θ C If the difference is within the preset threshold, then record multiple scene IDs.

7. The operation and maintenance emergency process management method based on smart contracts and consensus mechanisms according to claim 7, characterized in that, The specific process of step A3 is as follows: Signing is performed using a public key for different scenario IDs; When more than 2N+1 monitoring system nodes receive the signature of a certain scenario ID, it indicates that different nodes have reached a consensus on the judgment of the emergency scenario and broadcast the scenario ID.

8. The operation and maintenance emergency process management method based on smart contracts and consensus mechanisms according to claim 7, characterized in that, Step A4 specifically includes the following steps: A41. Based on the agreed-upon scenario ID, invoke the disposal smart contract to create an emergency work order and associate the emergency scenario with the corresponding emergency disposal command; A42. Execute emergency response orders and dispose of the relevant assets.

9. A method for managing emergency operation and maintenance processes based on smart contracts and consensus mechanisms according to any one of claims 3 to 8, characterized in that, The emergency response command is specifically a computer-recognizable command corresponding to emergency process operation behavior.

10. The operation and maintenance emergency process management method based on smart contracts and consensus mechanisms according to claim 3, characterized in that, The emergency process information recorded in step A5 includes emergency response time and emergency monitoring data, which includes relevant data before, during, and after the emergency.

Images