Intelligent power grid operation ticket management system and method based on cloud collaboration and block chain

Abstract

The invention provides an intelligent power grid operation ticket management system based on cloud collaboration and a block chain. The intelligent power grid operation ticket management system comprises a data acquisition module used for acquiring power grid topological data, power grid real-time state data and intelligent power grid operation tasks in real time through a data acquisition interface; the operation ticket generation module is used for generating an operation ticket draft; the operation ticket checking module is used for checking to obtain a checked operation ticket; the operation ticket approval module is used for assigning the approval process of the verified operation ticket to each corresponding approval node for approval to obtain an approved operation ticket; the operation ticket execution module is used for executing an operation instruction on the approved operation ticket on the to-be-operated equipment on the premise of matching the to-be-operated equipment and the approved operation ticket; and the operation ticket management module is used for storing the complete life cycle data of the operation ticket into the evidence storage chain and storing the operation record data of the operation equipment into the machine account chain. According to the invention, the safety, traceability and management efficiency of power grid operation can be significantly improved.

Description

Technical Field

[0001] This application relates to the field of power engineering technology, specifically to a smart grid operation ticket management system and method based on cloud collaboration and blockchain. Background Technology

[0002] Power grid operation tickets are a core management tool for power system dispatching and operation and maintenance, covering key information such as equipment operation instructions, safety measures, and process approvals. Traditional operation ticket management systems suffer from problems such as data fragmentation across different regions or departments, resulting in low collaboration efficiency; reliance on centralized databases for operation ticket circulation, posing a risk of privilege abuse; reliance on centralized storage for historical operation records, making them prone to loss or tampering; and multi-level manual approval leading to inefficiency.

[0003] Therefore, there is an urgent need for a smart grid operation ticket management system and method based on cloud collaboration and blockchain to improve the security and traceability of grid operations, while also enhancing the level of intelligence in dispatch management. Summary of the Invention

[0004] The purpose of this application is to provide a smart grid operation ticket management system and method based on cloud collaboration and blockchain, so as to solve the technical problems mentioned in the background.

[0005] To achieve the above objectives, the first aspect of this application discloses a smart grid operation ticket management system based on cloud collaboration and blockchain, comprising: The data acquisition module is used to acquire power grid topology data, real-time power grid status data, and smart grid operation tasks in real time through the data acquisition interface; The operation ticket generation module is used by the operation ticket service program to analyze the received smart grid operation tasks, combined with grid topology data and real-time grid status data, to obtain smart grid operation instructions in order to complete the smart grid operation tasks and generate a draft operation ticket. The operation ticket verification module is used to perform real-time verification of the draft operation ticket using a black-box simulation method to obtain the verified operation ticket. The operation ticket approval module is used to assign the approval process of verified operation tickets to the corresponding approval nodes based on the risk level of the operation tickets predicted by the risk prediction model, so as to obtain approved operation tickets. The operation ticket execution module is used to execute the operation instructions on the approved operation ticket on the device to be operated, provided that the device to be operated and the approved operation ticket are matched. The operation ticket management module is used to store the complete lifecycle data of the operation ticket into the evidence storage chain and the execution record data of the operation equipment into the ledger chain.

[0006] Furthermore, the specific methods by which the operation ticket service program analyzes the received smart grid operation task, combined with grid topology data and real-time grid status data, to obtain smart grid operation instructions in order to complete the smart grid operation task and generate a draft operation ticket include: The operation ticket service program determines the equipment to be operated and its target status based on the received smart grid operation task. Perform a topology lookup based on the connection point number of the device to be operated to find all switches, disconnectors and grounding switches of the device to be operated. By combining the status of all switches, disconnectors and grounding switches of the equipment to be operated, the real-time operating status of the equipment to be operated can be determined; Based on the operating status of the equipment to be operated, analyze how to operate the equipment to achieve the target state and obtain smart grid operation instructions; Enter the smart grid operation instructions into the operation ticket template to generate a draft operation ticket.

[0007] Furthermore, the specific methods for obtaining verified operation tickets by using the black-box simulation method to perform real-time verification of the draft operation ticket include: Verify whether the initial state of the first operation instruction on the operation ticket timing is consistent with the real-time state of the corresponding device to be operated; If they match, the device to be operated in the first operation instruction is set; if they do not match, the operation ticket is rejected. Following the verification method of the first operation instruction mentioned above, all operation instructions of the verification operation ticket are traversed sequentially to obtain the verified operation ticket.

[0008] Furthermore, the specific method for assigning the approved operation tickets to the corresponding approval nodes based on the risk level predicted by the risk prediction model is as follows: Input the operation instructions on the operation ticket into the power grid prediction model to obtain the risk level of the operation ticket; The risk levels of the operation tickets include no risk, low risk, medium-high risk, high risk, and special risk; When the risk level is classified as no risk, no approval is required. When the risk level is classified as low risk, the approval process is assigned to the duty officer for approval and approval is obtained. When the risk level is classified as medium to high risk, the approval process is sequentially assigned to the duty officer and then approved by the specialist. When the risk level is divided into no risk or high risk, the approval process is sequentially assigned to the duty officer, station manager, and dispatch center for approval. When the risk level is divided into no risk or special risk, the approval process is sequentially assigned to the station manager, the dispatch center, and the shift leader of the dispatch center for approval. After approval, you will receive an approved operation ticket.

[0009] Furthermore, the specific methods for executing the operation instructions on the approved operation ticket on the equipment to be operated, provided that the equipment to be operated and the approved operation ticket are matched, include: After the operator confirms that the approved operation ticket is in the approved state and has not expired, the edge gateway constructs a token payload, signs the token payload with the private key, and generates an encrypted token for the operator and the approved operation ticket. Compare the operation number, operation permissions of the operating device, and edge node signature carried by the encryption token with the number, operation permissions, and edge node signature on the approved operation ticket. If the two match, the operator scans the RFID tag of the equipment to be operated to match the approved operation ticket, and executes the operation instructions on the operation ticket on the equipment to be operated.

[0010] Furthermore, specific methods for storing the complete lifecycle data of the operation ticket into the evidence storage chain and the execution record data of the operation equipment into the ledger chain include: The complete lifecycle data of the operation ticket is divided into data fragments according to the region, and the hash value of the complete lifecycle data of the operation ticket is stored in the evidence storage chain using a Merkel-Patricia tree. The complete lifecycle data of the operation ticket includes: the operation ticket generation record, the operation ticket approval record, and the operation ticket execution record; The leaf nodes of the Merkel-Patricia tree include: operation number and timestamp; Use oracles to obtain operation record data of operating devices containing proof of authenticity, and store it in the blockchain network ledger chain.

[0011] Furthermore, it also includes: The operation ticket audit module is used to obtain the complete lifecycle data of the operation ticket on the evidence storage chain and the execution record of the operation equipment on the ledger chain after receiving an audit request, and verify consistency.

[0012] The second aspect of this application discloses a smart grid operation ticket management method based on cloud collaboration and blockchain, comprising the following steps: Real-time acquisition of power grid topology data, real-time power grid status data, and smart grid operation tasks is achieved through data acquisition interfaces. The operation ticket service program analyzes the received smart grid operation tasks, combined with grid topology data and real-time grid status data, to obtain smart grid operation instructions in order to complete the smart grid operation tasks and generate a draft operation ticket. The black-box simulation method is used to verify the draft operation ticket in real time to obtain the verified operation ticket; The approval process for verified operation tickets is assigned to the corresponding approval nodes based on the risk level of the operation tickets predicted by the risk prediction model, and the approved operation tickets are obtained. Under the premise of matching the equipment to be operated with the approved operation ticket, execute the operation instructions on the approved operation ticket on the equipment to be operated; The complete lifecycle data of the operation ticket is stored in the evidence storage chain, and the execution record data of the operation equipment is stored in the ledger chain.

[0013] A third aspect of this application discloses a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of a smart grid operation ticket management method based on cloud collaboration and blockchain.

[0014] The fourth aspect of this application discloses a computer program product, including a computer program / instruction, which, when executed by a processor, implements the steps of a smart grid operation ticket management method based on cloud collaboration and blockchain.

[0015] The beneficial effects of the technical solutions provided in this application include significantly improving the safety, traceability, and management efficiency of power grid operation. Attached Figure Description

[0016] Figure 1 This is a flowchart illustrating an embodiment of the smart grid operation ticket management system based on cloud collaboration and blockchain of this application; Detailed Implementation

[0017] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0018] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0019] Example 1 The first aspect of this invention proposes a smart grid operation ticket management system based on cloud collaboration and blockchain, such as... Figure 1 As shown, the system includes: The data acquisition module is used to acquire topology data, real-time status data and smart grid operation tasks of power grid equipment in real time through the data acquisition interface; In this embodiment, the smart grid operation task is "220kV I bus outage maintenance".

[0020] The operation ticket generation module is used by the operation ticket service program to analyze the received smart grid operation tasks, combined with the topology data and real-time status data of the power grid equipment, to obtain smart grid operation instructions and generate a draft operation ticket. The operation ticket verification module is used to perform real-time verification of the draft operation ticket using a black-box simulation method to obtain the verified operation ticket. The operation ticket approval module is used to assign the approval process of verified operation tickets to the corresponding approval nodes based on the risk level of the operation tickets predicted by the risk prediction model, so as to obtain approved operation tickets. The operation ticket execution module is used to execute the operation instructions on the approved operation ticket on the device to be operated, provided that the device to be operated and the approved operation ticket are matched. The operation ticket management module is used to store the complete lifecycle data of the operation ticket into the evidence storage chain and the operation record data of the operating equipment into the ledger chain.

[0021] In the above technical solution, the specific method by which the operation ticket service program analyzes the received smart grid operation task, combined with grid equipment topology data and real-time status data of grid equipment, to obtain smart grid operation instructions and generate a draft operation ticket includes: The operation ticket service program determines the equipment to be operated and its target status based on the received smart grid operation task. Perform a topology lookup based on the connection point number of the device to be operated to find all switches, disconnectors and grounding switches of the device to be operated. By combining the status of all switches, disconnectors and grounding switches of the equipment to be operated, the real-time operating status of the equipment to be operated can be determined; Based on the operating status of the equipment to be operated, analyze how to operate the equipment to achieve the target state and obtain smart grid operation instructions; Enter the smart grid operation instructions into the operation ticket template to generate a draft operation ticket.

[0022] In this embodiment, based on the device to be operated, a topology search is performed according to the connection point number to find the associated devices of the device to be operated. For example, if the device to be operated is a line, then based on the connection point number of the line endpoint, the topology search finds all switches, disconnectors and grounding switches at this end and all switches, disconnectors and grounding switches at the opposite end. The search stops when the busbar is found.

[0023] By combining the real-time status of switches, disconnectors, and grounding switches, the status of various equipment such as lines, busbars, and main transformers can be determined. For example, for a switch, if the switch is in the closed position, both disconnectors are in the closed position, and the grounding switch in the switch bay is in the open position, it is in operation. If the switch is in the open position, both disconnectors are in the open position, and the grounding switch in the bay is in the closed position, it is under maintenance. For a main transformer, if one of the three switches is in operation, it is in operation. If all three switches are in cold standby and the main transformer grounding switch is in the closed position, it is under maintenance. For a line, if both line switches are in operation, the line is in operation. If both line switches are in cold standby and the line grounding switch is in the closed position, it is under maintenance.

[0024] Based on the real-time status of the power grid and the target status of the devices to be operated, analyze whether all the associated devices and devices to be operated need to be operated, and what kind of operation needs to be performed to complete the smart grid operation instructions.

[0025] Enter the smart grid operation instructions into the operation ticket template to generate a draft operation ticket.

[0026] The specific methods for obtaining verified operation tickets by real-time verification of draft operation tickets using the black-box simulation method in the above technical solution include: Verify whether the initial state of the first operation instruction on the operation ticket timing is consistent with the real-time state of the corresponding device to be operated; If they match, the device to be operated in the first operation instruction is set; if they do not match, the operation ticket is rejected. Following the verification method of the first operation instruction mentioned above, all operation instructions of the verification operation ticket are traversed sequentially to obtain the verified operation ticket.

[0027] In this embodiment, one of the operation instructions on the operation ticket is: switch the 220kV antenna line from operation to maintenance. Here, "operation" is the initial state of the operation ticket, and the real-time state of the operating equipment is the real-time state of the antenna line stored in the SCADA system. The state verification is to compare whether the initial state of the operation ticket and the real-time state of the operating equipment are consistent.

[0028] At the start of the verification, the real-time status of the antenna line equipment is "running". After the initial status verification passes, the operation ticket service needs to execute this command to continue the subsequent verification, so a setting is required. Setting involves modifying the remote signaling values ​​of switches and disconnectors in the simulation application based on the equipment status.

[0029] In the above technical solution, the specific method for assigning the approved operation ticket to the corresponding approval node based on the risk level of the operation ticket predicted by the risk prediction model to obtain the approved operation ticket is as follows: Input the operation instructions on the operation ticket into the power grid prediction model to obtain the risk level of the operation ticket; The risk levels of the operation tickets include no risk, low risk, medium-high risk, high risk, and special risk; When the risk level is classified as no risk, no approval is required. When the risk level is classified as low risk, the approval process is assigned to the duty officer for approval. When the risk level is classified as medium to high risk, the approval process is sequentially assigned to the duty officer and then approved by the specialist. When the risk level is divided into no risk or high risk, the approval process is sequentially assigned to the duty officer, station manager, and dispatch center for approval. When the risk level is divided into no risk and special risk, the approval process is sequentially assigned to the station manager, the dispatch center, and the shift leader of the dispatch center for approval.

[0030] In this embodiment, the operation instruction is risk-free when it is a routine information query; low risk when it is a regular equipment status switch; medium-high risk when it is a change involving critical business and the failure of the operation may affect other businesses; high risk when it is a power grid switching operation, a change of operating mode, multi-device assistance, or multi-device status switch; and special risk when it is an emergency accident handling operation, such as a system failure.

[0031] In the above technical solution, the specific method for executing the operation instructions on the approved operation ticket on the equipment to be operated, under the premise of matching the equipment to be operated and the approved operation ticket, includes: After the operator confirms that the approved operation ticket is in the approved state and has not expired, the edge gateway constructs a token payload, signs the token payload with the private key, and generates an encrypted token for the operator and the approved operation ticket. Compare the operation number, operation permissions of the operating device, and edge node signature carried by the encryption token with the number, operation permissions, and edge node signature on the approved operation ticket. If the two match, the operator scans the RFID tag of the equipment to be operated to match the approved operation ticket, and executes the operation instructions on the operation ticket on the equipment to be operated.

[0032] In this embodiment, once the operation ticket is approved, the edge gateway will receive an approval notification, including detailed information about the operation ticket and a list of operators authorized to execute the operation ticket.

[0033] Once the operator arrives on-site and confirms that the approved operation ticket is in an "approved" state and has not expired, they scan the operation ticket's QR code using a mobile terminal. After the edge gateway verifies the operator's identity and the operation ticket's status, it dynamically generates an encrypted token. The encrypted token includes: operator ID, edge gateway ID, issuance time, expiration time, exp (e.g., current time + 8 minutes), authorized operation list (e.g., a list of allowed devices and operation types), and a digital signature (e.g., signing the above content using the edge gateway's private key).

[0034] Encryption Token Generation Steps: Authentication: The edge gateway first verifies the operator's identity (e.g., by scanning the operator's employee card QR code or fingerprint) and confirms that the operator is in the list of those authorized to execute the operation ticket; Construct Token Payload: As described above, assemble the various fields of the token; Digital Signature: Sign the payload using the edge gateway's private key to generate a token in JWT (JSON Web Token) format; Return Token: Return the generated token to the operator's mobile terminal.

[0035] In subsequent operations, the mobile terminal will present the encryption token for each step the operator performs. The edge gateway will verify the validity of the encryption token before allowing the operation to proceed.

[0036] The specific methods for storing the complete lifecycle data of the operation ticket into the blockchain network's evidence storage chain and storing the operation record data of the device to be operated into the blockchain network's ledger chain in the above technical solution include: The complete lifecycle data of the operation ticket is divided into data fragments according to the region, and the hash value of the complete lifecycle data of the operation ticket is stored in the blockchain network evidence storage chain using a Merkel-Patricia tree. In this embodiment, the specific process of storing the hash value of the complete lifecycle data of the operation ticket into the blockchain network's evidence storage chain using a Merkel-Patricia tree is as follows: Whenever an event occurs on an operation ticket, such as generation, approval, execution, or archiving, we create a record containing details of that event and calculate the hash value of that record, for example, using SHA-256.

[0037] The record includes the operation ticket ID, event type, timestamp, participant signature, version number, etc. This hash value is then used as the data to be stored.

[0038] MPT is a key-value tree. We need to determine the key and value.

[0039] Key: We use a combination of operation ticket ID and version number, for example: operation ticket ID_version number. The version number starts from 1 and increments with each event, thus ensuring that each event has a unique key.

[0040] Value: Stores the hash value of the event, and may also contain some metadata, such as the timestamp of the digital signature.

[0041] Insert the key-value pair corresponding to each event into the MPT.

[0042] MPT constructs tree nodes step by step based on the hexadecimal characters of the keys. There are four types of tree nodes: extension nodes, branch nodes, leaf nodes, and null nodes.

[0043] Ultimately, each key-value pair will be represented as a leaf node. The path of the leaf node is determined by the key, and the stored value is metadata such as encoded event hash and timestamp.

[0044] Since MPT is a type of Merkle tree, each node has a hash value. The hash value of the root node represents the state of the entire state tree and is included in the block header.

[0045] When we need to verify an event, we can provide the node hash on the leaf node path corresponding to the event to prove that the event is indeed included in the block.

[0046] We can track the entire history of an operation ticket using the version number. A new version is generated for each event and inserted into the MPT (Motion Management Tablet). Therefore, by using the operation ticket ID and version number, we can retrieve all historical events for that operation ticket.

[0047] In addition to the event hash, the values ​​stored in the leaf nodes also include the timestamp of the digital signature. This ensures that the timestamp of each event is also fully recorded and verified.

[0048] Assuming the operation ticket ID is "OST-20250623-001", the version number of the first event is 1, and the key is "OST-20250623-001_1".

[0049] The value can be a structure containing: event hash: 0x89a3f... (calculated from event data), timestamp: 1720000000.

[0050] When inserting multiple events, MPT shares paths based on the key prefix, thus saving space.

[0051] Each block has an MPT root hash, which is written into the block header. Once a block is confirmed, its event records cannot be tampered with, because any modification will cause the root hash to change.

[0052] To verify an event, we need to provide the hashes of all sibling nodes along the path from the root node to the leaf node of that event. The verifier can start from the leaf node, calculate the hashes layer by layer, and finally compare them with the known root hash.

[0053] The complete lifecycle data of the operation ticket includes: the operation ticket generation record, the operation ticket approval record, and the operation ticket execution record.

[0054] Use oracles to obtain operation record data of operating devices containing proof of authenticity, and store it in the blockchain network ledger chain.

[0055] In this embodiment, the oracle obtains the operation record data of the operating device containing the proof of authenticity by: the data provider SCADA system generating a proof that the device status data is authentic and is generated according to predetermined rules, such as sensor readings.

[0056] This proof is generated using zk-SNARKs circuits, which encode the business logic for data generation, such as sensor readings needing to be within a certain range and data signatures being correct. The oracle uploads the data along with the proof to the blockchain, where a smart contract verifies the proof. If the verification passes, the data is accepted as genuine and stored or used.

[0057] The above technical solution also includes: an operation ticket audit module, which, upon receiving an audit request, allows the relay chain to obtain the complete lifecycle data of the operation ticket on the evidence storage chain and the execution records of the operation equipment on the ledger chain to verify consistency.

[0058] In this embodiment, when auditing is initiated, the relay chain retrieves the operation instruction sequence from the evidence storage chain, such as "10:03:22 disconnect QF1", and obtains the physical device action record from the device ledger chain through an oracle, such as "QF1 quantile shift time 10:03:23". Using zero-knowledge proof technology, a consistency verification report is generated without exposing the original data, ensuring that the evidence chain shows a time deviation of ≤1 second between the "system instruction" and the "actual device response" and that the operation objects are completely matched. Example 2 A second aspect of this invention provides a smart grid operation ticket management method based on cloud collaboration and blockchain, comprising the following steps: Step 1: Obtain real-time power grid topology data, real-time power grid status data, and smart grid operation tasks through the data acquisition interface; Step 2: The operation ticket service program analyzes the received smart grid operation task, combined with grid topology data and real-time grid status data, to obtain smart grid operation instructions in order to complete the smart grid operation task and generate a draft operation ticket. Step 3: Use the black-box simulation method to perform real-time verification of the draft operation ticket to obtain the verified operation ticket; Step 4: The approval process for verified operation tickets is assigned to the corresponding approval nodes based on the risk level of the operation tickets predicted by the risk prediction model, and the approved operation tickets are obtained. Step 5: Under the premise of matching the equipment to be operated with the approved operation ticket, execute the operation instructions on the approved operation ticket on the equipment to be operated; Step 6: Store the complete lifecycle data of the operation ticket into the evidence storage chain, and store the execution record data of the operation equipment into the ledger chain.

[0059] Example 3 A third aspect of the present invention provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the method described in Embodiment 2.

[0060] Example 4 A fourth aspect of the present invention provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the steps of the method described in Embodiment 2.

[0061] The contents not described in detail in this specification are prior art known to those skilled in the art. Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0062] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0063] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0064] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0065] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit its scope of protection. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that after reading the present invention, they can still make various changes, modifications or equivalent substitutions to the specific implementation of the invention, but these changes, modifications or equivalent substitutions are all within the scope of protection of the pending claims of the invention.

Claims

1. A smart grid operation ticket management system based on cloud collaboration and blockchain, characterized in that, include: The data acquisition module is used to acquire power grid topology data, real-time power grid status data, and smart grid operation tasks in real time through the data acquisition interface; The operation ticket generation module is used by the operation ticket service program to analyze the received smart grid operation tasks, combined with grid topology data and real-time grid status data, to obtain smart grid operation instructions in order to complete the smart grid operation tasks and generate a draft operation ticket. The operation ticket verification module is used to perform real-time verification of the draft operation ticket using a black-box simulation method to obtain the verified operation ticket. The operation ticket approval module is used to assign the approval process of verified operation tickets to the corresponding approval nodes based on the risk level of the operation tickets predicted by the risk prediction model, so as to obtain approved operation tickets. The operation ticket execution module is used to execute the operation instructions on the approved operation ticket on the device to be operated, provided that the device to be operated and the approved operation ticket are matched. The operation ticket management module is used to store the complete lifecycle data of the operation ticket into the evidence storage chain and the execution record data of the operation equipment into the ledger chain.

2. The smart grid operation ticket management system based on cloud collaboration and blockchain as described in claim 1, characterized in that, The specific methods by which the operation ticket service program analyzes the received smart grid operation tasks, combined with grid topology data and real-time grid status data, to obtain smart grid operation instructions in order to complete the smart grid operation tasks and generate a draft operation ticket include: The operation ticket service program determines the equipment to be operated and its target status based on the received smart grid operation task. Perform a topology lookup based on the connection point number of the device to be operated to find all switches, disconnectors and grounding switches of the device to be operated. By combining the status of all switches, disconnectors and grounding switches of the equipment to be operated, the real-time operating status of the equipment to be operated can be determined; Based on the operating status of the equipment to be operated, analyze how to operate the equipment to achieve the target state and obtain smart grid operation instructions; Enter the smart grid operation instructions into the operation ticket template to generate a draft operation ticket.

3. The smart grid operation ticket management system based on cloud collaboration and blockchain as described in claim 1, characterized in that, The specific methods for obtaining verified operation tickets by using black-box simulation to perform real-time verification of draft operation tickets include: Verify whether the initial state of the first operation instruction on the operation ticket timing is consistent with the real-time state of the corresponding device to be operated; If they match, the device to be operated in the first operation instruction is set; if they do not match, the operation ticket is rejected. Following the verification method of the first operation instruction mentioned above, all operation instructions of the verification operation ticket are traversed sequentially to obtain the verified operation ticket.

4. The smart grid operation ticket management system based on cloud collaboration and blockchain as described in claim 1, characterized in that, The specific method for assigning approved operation tickets to corresponding approval nodes based on the risk level predicted by the risk prediction model is as follows: Input the operation instructions on the operation ticket into the power grid prediction model to obtain the risk level of the operation ticket; The risk levels of the operation tickets include no risk, low risk, medium-high risk, high risk, and special risk; When the risk level is classified as no risk, no approval is required. When the risk level is classified as low risk, the approval process is assigned to the duty officer for approval and approval is obtained. When the risk level is classified as medium to high risk, the approval process is sequentially assigned to the duty officer and then approved by the specialist. When the risk level is divided into no risk or high risk, the approval process is sequentially assigned to the duty officer, station manager, and dispatch center for approval. When the risk level is divided into no risk or special risk, the approval process is sequentially assigned to the station manager, the dispatch center, and the shift leader of the dispatch center for approval. After approval, you will receive an approved operation ticket.

5. The smart grid operation ticket management system based on cloud collaboration and blockchain according to claim 1, characterized in that, The specific methods for executing the operation instructions on the approved operation ticket on the equipment to be operated, provided that the equipment to be operated is matched with the approved operation ticket, include: After the operator confirms that the approved operation ticket is in the approved state and has not expired, the edge gateway constructs a token payload, signs the token payload with the private key, and generates an encrypted token for the operator and the approved operation ticket. Compare the operation number, operation permissions of the operating device, and edge node signature carried by the encryption token with the number, operation permissions, and edge node signature on the approved operation ticket; If the two match, the operator scans the RFID tag of the equipment to be operated to match the approved operation ticket, and executes the operation instructions on the operation ticket on the equipment to be operated.

6. The smart grid operation ticket management system based on cloud collaboration and blockchain according to claim 1, characterized in that, Specific methods for storing the complete lifecycle data of operation tickets into the evidence storage chain and storing the execution record data of operation equipment into the ledger chain include: The complete lifecycle data of the operation ticket is divided into data fragments according to the region, and the hash value of the complete lifecycle data of the operation ticket is stored in the evidence storage chain using a Merkel-Patricia tree. The complete lifecycle data of the operation ticket includes: the operation ticket generation record, the operation ticket approval record, and the operation ticket execution record; The leaf nodes of the Merkel-Patricia tree include: operation number and timestamp; Use oracles to obtain operation record data of operating devices containing proof of authenticity, and store it in the blockchain network ledger chain.

7. The smart grid operation ticket management system based on cloud collaboration and blockchain as described in claim 1, characterized in that, Also includes: The operation ticket audit module is used to obtain the complete lifecycle data of the operation ticket on the evidence storage chain and the execution record of the operation equipment on the ledger chain after receiving an audit request, and verify consistency.

8. A smart grid operation ticket management method based on cloud collaboration and blockchain, characterized in that, Includes the following steps: Real-time acquisition of power grid topology data, real-time power grid status data, and smart grid operation tasks is achieved through data acquisition interfaces. The operation ticket service program analyzes the received smart grid operation tasks, combined with grid topology data and real-time grid status data, to obtain smart grid operation instructions in order to complete the smart grid operation tasks and generate a draft operation ticket. The black-box simulation method is used to verify the draft operation ticket in real time to obtain the verified operation ticket; The approval process for verified operation tickets is assigned to the corresponding approval nodes based on the risk level of the operation tickets predicted by the risk prediction model, and the approved operation tickets are obtained. Under the premise of matching the equipment to be operated with the approved operation ticket, execute the operation instructions on the approved operation ticket on the equipment to be operated; The complete lifecycle data of the operation ticket is stored in the evidence storage chain, and the execution record data of the operation equipment is stored in the ledger chain.

9. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in claim 8.

10. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the method of claim 8.

Images