A power outage data credible management method based on a blockchain

Abstract

The application discloses a power outage data credible management method based on a block chain, relates to the technical field of power supply reliability management, and comprises the following steps: data chain management: obtaining power outage events and reliability data, performing hash calculation, generating a unique data fingerprint, and writing the hash value and related metadata into a block chain; chain configuration management: performing failure compensation operation after a chain failure event is triggered; on-chain verification management: comparing the hash calculation with the original block chain storage, automatically and manually verifying the consistency of business data; verification task management: comparing the hash calculation of power supply reliability power outage data with the on-chain hash value, marking the inconsistent items and recording; on-chain traceability management: displaying a traceability list in reverse chronological order, locating corresponding items according to query conditions, and checking the on-chain storage track and operation history. The application can improve the defects of the prior art and improve the efficiency and accuracy of data verification.

Description

Technical Field

[0001] This invention relates to the field of power supply reliability management technology, and in particular to a blockchain-based trusted management method for power outage data. Background Technology

[0002] In traditional power supply reliability management, the management and verification of power outage data suffer from problems such as insufficient transparency, poor traceability, and low verification efficiency. In particular, the differences in power supply reliability management between different regions can easily affect the accuracy of reported matters. Currently, the main problems in this field are as follows: (1) Low data credibility: Data such as power outage events, user power outage time, and reliability indicators are stored in provincial and headquarters databases, which poses a risk of post-event tampering and falsification. Especially when benchmarking and assessing across regions, it is difficult to prove the authenticity of the data. (2) Low data verification efficiency: Traditional verification relies on manual sampling and cross-comparison. Faced with massive data verification, the workload is huge, the efficiency is extremely low, and errors are easy to occur, making it impossible to achieve comprehensive and timely auditing. (3) Weak traceability: The data modification history, verification records, and other log information are stored in a centralized database, which lacks credibility and cannot form a complete and tamper-proof audit evidence chain.

[0003] In current technological practices, blockchain technology is applied to different fields. In terms of power supply reliability management, there is still a lack of end-to-end technical solutions that can organically integrate functions such as trusted data storage, automatic consistency verification, intelligent compensation on-chain, and full-link traceability. Existing technologies lack an efficient, transparent, and traceable data management and verification method.

[0004] In current technological practices, although blockchain technology has achieved initial applications in data storage in fields such as finance and supply chain, its generalized architecture is difficult to meet the specific needs of high-real-time and high-reliability business scenarios such as power supply reliability management. Existing solutions generally suffer from three core defects: First, traditional centralized storage models cannot guarantee the immutability of critical business data related to power outages throughout the entire process of generation, transmission, and storage, resulting in data silos between multi-source systems (such as SCADA, distribution automation, and electricity consumption information collection systems); Second, business rules are not encoded on-chain, and key processes such as power outage time calculation and responsibility area determination still rely on manual intervention, lacking an automatic consistency verification mechanism based on smart contracts; Third, traceability capabilities remain at the surface level of data association, failing to construct an evidence chain that runs through all stages of the source system, data analysis, and business applications. Summary of the Invention

[0005] The technical problem to be solved by this invention is to provide a blockchain-based trusted management method for power outage data, which can overcome the shortcomings of existing technologies, improve data traceability, and enhance the efficiency and accuracy of data verification.

[0006] To solve the above-mentioned technical problems, the technical solution adopted by the present invention is as follows.

[0007] A blockchain-based trusted management method for power outage data includes the following steps:

[0008] Data on-chain management: Power outage event and reliability data are obtained through a standardized on-chain evidence storage interface. The raw data is hashed to generate a unique data fingerprint. The smart contract is called to write the hash value and related metadata into the blockchain to complete the trusted evidence storage.

[0009] On-chain configuration management: Perform on-chain failure detection, and perform failure compensation operations when an on-chain failure event is triggered to ensure that the data is completely uploaded to the chain;

[0010] On-chain verification management: By comparing hash calculations with the original evidence stored on the blockchain, the consistency of business data is automatically and manually verified, and a structured verification report is generated.

[0011] Verification task management: After performing hash calculation on the power supply reliability outage data, compare it with the hash value on the blockchain, mark the items with inconsistent comparison results and record them;

[0012] On-chain traceability management: Completely record the verification history of each power outage, forming a traceability list that can be displayed in reverse chronological order. Locate the corresponding event based on the query conditions and view its on-chain evidence storage trajectory and operation history.

[0013] As a preferred approach, during the data on-chain management process, JSON format data of power outage events is obtained in real time from the power grid resource business platform through the API gateway. The data is then cleaned and standardized to ensure the integrity and consistency of the on-chain data. A distributed node network is built based on the State Grid consortium blockchain platform, and the PBFT consensus mechanism is adopted to ensure data consistency and system fault tolerance among nodes, thereby achieving secure storage of power outage event data.

[0014] As a preferred approach, in the on-chain configuration management, the response status of the State Grid Chain API interface is monitored in real time through a data tracking component. When an abnormal HTTP status code or a blockchain transaction receipt status of false is detected, the power outage data is automatically marked as an on-chain failure, and the failure reason, timestamp, and other contextual information are recorded in the SQL exception log table. Automatic retries are implemented using a message queue-based dead-letter queue mechanism. When an on-chain failure event is triggered, the system encapsulates the failure data into a compensation message and puts it into the retry queue, dynamically adjusting the retry interval through an exponential backoff algorithm. A Redis atomic counter is used to create a retry count key for each failure data. Before each retry, the count is counted using the INCR command. When the count exceeds the configured threshold, the data is automatically transferred to the manual intervention queue, and an alarm is sent to the operations and maintenance personnel. The details of the compensation failure data are also displayed visually on the dashboard.

[0015] As a preferred approach, in on-chain verification management, the State Grid Chain OpenAPI interface is used to securely interact with the underlying blockchain network to achieve trusted acquisition, verification, and evidence storage of data such as power outage events on the chain. A verification engine is built using Spring Boot to realize verification rule management, transaction scheduling, and audit log recording. A visual operation interface is built using the Vue.js framework to provide users with intuitive data query, verification result display, and interactive functions.

[0016] As a preferred approach, the Spring Cloud framework is used to implement inter-service communication in the verification task management, task status data is persistently stored in the database, and task query performance is improved by using Redis caching.

[0017] As a preferred approach, in on-chain traceability management, the Elasticsearch engine is used for full-text search, data query services are provided through the GraphQL interface, and web browser components are used to achieve visual tracking and auditing of on-chain transactions.

[0018] The beneficial effects of adopting the above technical solution are as follows:

[0019] (1) It pioneered a three-in-one on-chain evidence storage mechanism for power outage information / events / reliability data, and adopted dual hash anchoring technology to establish an atomic-level trust foundation.

[0020] (2) The dynamic compensation strategy achieves 99.7% high reliability of data on the chain.

[0021] (3) The penetrating traceability engine improves data consistency and integrity. This invention proposes a method for realizing the on-chain data of power outages and the verification of on-chain data based on blockchain technology. It solves the problems of poor traceability and low verification efficiency of power outage data management, reduces the workload of grassroots employees, improves the overall efficiency of power supply reliability management, and provides a trusted data infrastructure for the collaboration of "source-grid-load-storage". Attached Figure Description

[0022] Figure 1 This is a schematic diagram of a specific embodiment of the present invention. Detailed Implementation

[0023] In the following description of the embodiments, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods are omitted so as not to obscure the description of this application with unnecessary detail.

[0024] See Figure 1 The blockchain-based trusted management method for power outage data provided by this invention includes the following steps:

[0025] Data on-chain management: Power outage events and reliability data are obtained through a standardized on-chain evidence storage interface. The raw data is hashed to generate a unique data fingerprint. The smart contract is then called to write the hash value and related metadata into the blockchain to complete trusted evidence storage.

[0026] On-chain configuration management: Performs on-chain failure detection, and performs failure compensation operations when an on-chain failure event is triggered to ensure that the data is completely uploaded to the chain.

[0027] On-chain verification management: By comparing hash calculations with the original evidence stored on the blockchain, the consistency of business data is automatically and manually verified, and a structured verification report is generated.

[0028] Verification Task Management: After performing hash calculation on the power supply reliability outage data, compare it with the hash value on the blockchain, mark the items with inconsistent comparison results and record them.

[0029] On-chain traceability management: Completely record the verification history of each power outage, forming a traceability list that can be displayed in reverse chronological order. Locate the corresponding event based on the query conditions and view its on-chain evidence storage trajectory and operation history.

[0030] During the data on-chain management process, JSON format data of power outage events is obtained in real time from the power grid resource business platform via an API gateway. The data is then cleaned and standardized to ensure the integrity and consistency of the on-chain data. A distributed node network is built based on the State Grid consortium blockchain platform, employing the PBFT consensus mechanism to ensure data consistency and system fault tolerance among nodes, achieving secure storage of power outage event data. Specifically, this includes the following four aspects:

[0031] (1) Data collection: Obtain power outage event data in real time from the business middle platform through HTTP requests or MQ messages, including structured data such as power outage time, power outage area, and power outage reason.

[0032] (2) Data preprocessing: First, data cleaning (handling missing values ​​and outliers) is performed. Then, the data is formatted using the JSON Canonicalization Scheme to ensure the uniformity of field sorting and encoding format. The data preprocessing first sets the original data as Draw. After cleaning and standardization, Dstd is obtained. The processing formula is as follows: Dstd = Canonicalize(Draw).

[0033] (3) Hash calculation: The SHA-256 hash algorithm is used to encrypt and calculate the preprocessed data to generate a hash value Hdata. The algorithm formula is as follows: Hdata=SHA256(Dstd). The algorithm generates a fixed-length hash value of 256 bits after steps such as padding, block processing, and 64 rounds of encryption loop, which serves as the unique digital fingerprint of the data.

[0034] (4) On-chain evidence storage: The smart contract is called through the RESTful API interface provided by the State Grid Chain to form a transaction body Tx, which consists of metadata such as data hash value Hdata, timestamp t, and submitter digital signature σ. The formula is as follows: Tx={Hdata,t,σ,metadata}Block←Block∪Tx is signed by the SM2 national cryptographic algorithm and submitted to the blockchain network. After the nodes reach consensus through the PBFT consensus mechanism, it is written into the block, and the transaction hash and block height are generated as evidence storage certificate.

[0035] This scheme combines cryptographic algorithms and distributed ledger technology to ensure the immutability and traceability of power outage event data. At the same time, it adopts a hybrid architecture of storing the original data off-chain and storing the evidence hash value on-chain, which balances system performance and data security.

[0036] In the on-chain configuration management, the response status of the State Grid Chain API interface is monitored in real time through the monitoring component. When an HTTP status code other than 200 (such as network timeout, node unavailability, or other anomalies) or a blockchain transaction receipt status of false is detected, the power outage data is automatically marked as an on-chain failure, and the failure reason, timestamp, and other context information are recorded in the SQL exception log table. Automatic retries are implemented using a dead-letter queue mechanism based on message queues. When an on-chain failure event is triggered, the system encapsulates the failure data into a compensation message and puts it into the retry queue. The retry interval is dynamically adjusted through an exponential backoff algorithm (1 minute for the first time, 2 minutes for the second time, and 4 minutes for the third time). A Redis atomic counter is used to create a retry count key (key format: retry:event_id) for each failure data. The count is made using the INCR command before each retry. When the count exceeds the configured threshold (default 3 times), the data is automatically transferred to the manual intervention queue, and an alarm is sent to the operation and maintenance personnel. The details of the compensation failure data are also displayed visually on the dashboard.

[0037] This solution achieves automatic fault tolerance in scenarios where data upload fails through a closed-loop design of monitoring, retrying, and management. It ensures the eventual consistency of data upload and avoids waste of system resources through retry limit and backoff mechanism, effectively improving the reliability and operational efficiency of on-chain data management.

[0038] In on-chain verification management, the State Grid Chain OpenAPI interface is used to securely interact with the underlying blockchain network, enabling trusted acquisition, verification, and evidence storage of data such as power outage events. A verification engine is built using Spring Boot to manage verification rules, schedule transactions, and record audit logs. A visual interface is constructed using the Vue.js framework, providing users with intuitive data query, verification result display, and interactive functions. The implementation comprises five core components:

[0039] (1) Event selection: Users can query the list of power outage events from the power grid business database through the Web interface. The system uses the GraphQL interface to achieve efficient data query. After the user selects a specific event, the user can obtain a complete JSON data packet.

[0040] (2) Hash calculation: Using the same standardized processing procedure (JSON Canonicalization Scheme) as when it is put on the chain, SHA-256 hash calculation is performed on the selected data to generate a 64-bit hexadecimal hash value H_current; the current hash H_current = SHA256(D_current).

[0041] (3) On-chain hash comparison: Through the RESTful verification interface provided by the State Grid Chain, the original hash value H_curren stored on the chain is obtained by passing in the unique event ID. The comparison results are as follows: The system uses the Constant Time Compare algorithm to compare hash values ​​to prevent time-series attacks.

[0042] (4) Result recording: Write the comparison results (including comparison time, operator, event ID, hash value comparison status) to the Elasticsearch log system, mark the inconsistencies with the "data tampering" flag, and trigger real-time alarm notifications.

[0043] (5) Report generation: Based on the JasperReport reporting engine, a PDF verification report is generated, which includes visual comparison charts, digital signatures and timestamps. It supports blockchain evidence verification QR codes, and users can download the audit report through a secure HTTPS connection.

[0044] This solution provides an end-to-end trusted verification mechanism for power outage event data through standardized verification processes and cryptographic guarantees. It not only meets regulatory audit requirements but also significantly improves verification efficiency through automated comparison and report generation, ensuring the consistency and verifiability of on-chain and off-chain data.

[0045] In the task management process, the Spring Cloud framework is used to implement inter-service communication, task status data is persistently stored in a database, and Redis caching is used to improve task query performance. The implementation involves four core steps:

[0046] (1) Task order generation: Users configure verification parameters (including time range, region filtering, event type, etc.) through the front-end interface. The system backend generates task work orders through the workflow engine Activiti, stores task metadata (task ID, creator, creation time, verification rules) in the database, and initializes the task status to "pending execution".

[0047] (2) Task execution: The task scheduling center triggers the execution engine through the Quartz timed task framework, automatically pulls all power outage event data that meet the conditions, and uses the parallel computing framework ForkJoinPool to perform standardized hash calculation (SHA-256 algorithm) on each item. Then, it calls the State Grid Chain verification interface in batches to compare the hash values ​​on the chain and uses asynchronous non-blocking IO (Netty framework) to improve the comparison efficiency.

[0048] (3) Task order query: Provides a multi-dimensional composite query interface, supports combined queries based on task status, time range, creator and other conditions. The query results are returned to the front end for display through pagination technology. At the same time, it provides a visual dashboard of task details, which displays the task progress, number of items to be checked and the abnormal ratio in real time.

[0049] (4) Task Check Report: The structured report is dynamically generated based on the template engine (Apache POI), which includes a check overview, consistency statistics charts (visualized through ECharts), and a detailed table of abnormal data. The report output format supports both PDF and Excel formats, and users can obtain the report through a secure download link.

[0050] This solution enables batch reliable verification of large-scale power outage event data through automated task scheduling and batch processing mechanisms, significantly improving verification efficiency. Through comprehensive task status management and visualization, it provides managers with comprehensive task monitoring and audit tracking capabilities, ensuring the systematic and standardized nature of power supply reliability data verification.

[0051] In on-chain traceability management, the Elasticsearch engine is used for full-text search, data query services are provided through the GraphQL interface, and web browser components are used to achieve visual tracking and auditing of on-chain transactions. The implementation includes three core components:

[0052] (1) Source tracing list generation: Based on the unique identifier of the power outage event (such as eventId), the system aggregates data from the business database, blockchain browser API and verification record library through the data association engine, and automatically generates a structured source tracing list containing key information such as the initial data version, timestamps of each verification, block height, and transaction hash. The list items are arranged in reverse chronological order and the data consistency status of each link is marked.

[0053] (2) Source traceability query: Provides an intelligent query interface that supports combined queries based on multiple dimensions such as event ID, time range, block height, transaction hash, and verification results. The query engine uses Elasticsearch inverted index technology to achieve millisecond-level response. It also supports fuzzy matching and synonym expansion queries. The returned results include highlighted key information.

[0054] (3) Source traceability details display: The timeline visualization technology (based on AntV G6 graph engine) is used to fully display the source traceability details of the power outage event throughout its entire life cycle, including data collection time, original hash value, each on-chain record (including block height, transaction hash, gas consumption), each verification result (verifier, verification time, hash comparison result), data change record (if any), and other key information. On-chain evidence storage and verification functions are also provided. Users can directly click on the transaction hash to jump to the State Grid Chain Browser to view the original transaction details on the chain.

[0055] This solution combines multi-source data fusion with the immutability of blockchain to achieve reliable traceability of power outage events throughout their entire lifecycle. It provides convenient query and verification methods while lowering the technical threshold through visualization, offering transparent regulatory tools and decision support for power supply reliability management, and effectively improving the credibility and traceability efficiency of power outage event handling.

[0056] This invention employs a lightweight TEE (Trusted Execution Environment) combined with national cryptographic algorithms (SM2 / SM3) to perform real-time trustworthy measurement of source data at the edge, ensuring data reliability from its generation. Data hash values ​​are processed through a high-throughput streaming pipeline in collaboration with blockchain light nodes, achieving millisecond-level on-chain evidence storage. Based on the business rules of the "Power Supply Reliability Evaluation Regulations," an on-chain smart contract verification engine is constructed, deeply integrating Verifiable Random Functions (VRF) and Zero-Knowledge Proofs (zk-SNARKs) to form a verifiable verification system that balances randomness, fairness, and data privacy, achieving fully automated compliance verification. Compensation execution is automatically triggered based on preset business rules, achieving a precise and unattended compensation process. Simultaneously, the system uses a Merkle Patricia Trie (MPT) to construct a full-link state tree, encoding the hash values ​​of key links such as user power outage events, outage duration, and associated equipment onto the chain according to business logic, forming an immutable cryptographic evidence chain that supports trusted, penetrating traceability across the entire chain from the power user side to the power grid side.

[0057] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0058] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely illustrative of the principles of the invention. Various changes and modifications can be made to the invention without departing from its spirit and scope, and all such changes and modifications fall within the scope of the present invention as claimed. The scope of protection of this invention is defined by the appended claims and their equivalents.

Claims

1. A blockchain-based trusted management method for power outage data, characterized in that... Includes the following steps: Data on-chain management: Power outage event and reliability data are obtained through a standardized on-chain evidence storage interface. The raw data is hashed to generate a unique data fingerprint. The smart contract is then called to write the hash value and related metadata into the blockchain. During the data on-chain management process, JSON format data of power outage events are obtained in real time from the power grid resource business platform through the API gateway, and the data is cleaned and format standardized. A distributed node network is built based on the State Grid Alliance Chain platform. The PBFT consensus mechanism is used to ensure data consistency and system fault tolerance among nodes. The smart contract is called through the RESTful API interface provided by the State Grid Chain. The data hash value Hdata, timestamp t, and submitter's digital signature σ are combined to form the transaction body Tx. After being signed by the SM2 national cryptographic algorithm, it is submitted to the blockchain network. After the nodes reach consensus through the PBFT consensus mechanism, it is written into the block, and the transaction hash and block height are generated as evidence. On-chain configuration management: On-chain failure detection is performed, and failure compensation operations are initiated when an on-chain failure event is triggered. In on-chain configuration management, the response status of the State Grid Chain API interface is monitored in real time through a data tracking component. When an abnormal HTTP status code or a blockchain transaction receipt status of false is detected, the power outage data is automatically marked as an on-chain failure, and the failure reason and timestamp are recorded in the SQL exception log table. Automatic retries are implemented using a message queue-based dead-letter queue mechanism. When an on-chain failure event is triggered, the system encapsulates the failure data into a compensation message and puts it into the retry queue, dynamically adjusting the retry interval through an exponential backoff algorithm. A Redis atomic counter is used to create a retry count key for each failed data entry. Before each retry, the count is counted using the INCR command. When the count exceeds the configured threshold, the data is automatically transferred to the manual intervention queue, and an alarm is sent to the operations and maintenance personnel. The details of the compensation failure data are also visualized through a dashboard. On-chain verification management: Generates a structured verification report by comparing the hash calculation with the original evidence stored on the blockchain; Verification Task Management: Power outage data related to power reliability is hashed and compared with the hash value on the blockchain. Inconsistencies are marked and recorded. The verification task management uses the Spring Cloud framework for inter-service communication, persistently stores task status data in a database, and improves task query performance through Redis caching. This includes: (1) Task order generation: Users configure verification parameters through the front-end interface, and the system back-end generates task work orders through the workflow engine Activiti and stores the task metadata in the database; (2) Task execution: The task scheduling center triggers the execution engine through the Quartz timed task framework, automatically pulls all power outage event data that meet the conditions, uses the parallel computing framework ForkJoinPool to execute the SHA-256 algorithm on each item, and then calls the State Grid Chain verification interface in batches to compare the on-chain hash values. The asynchronous non-blocking IO of the Netty framework is used to improve the comparison efficiency. (3) Task order query: Provides a multi-dimensional composite query interface. The query results are returned to the front end for display through pagination technology. At the same time, it provides a visual dashboard of task details, which displays the task progress, the number of items to be checked and the abnormality ratio in real time. (4) Task Check Report: A structured report is dynamically generated based on the Apache POI template engine, and users can obtain the report through a secure download link; On-chain traceability management: Completely record the verification history of each power outage event, forming a traceability list that can be displayed in reverse chronological order. Locate the corresponding event based on the query conditions and view its on-chain evidence storage trajectory and operation history.

2. The blockchain-based trusted management method for power outage data according to claim 1, characterized in that: In the on-chain verification and management, the State Grid Chain OpenAPI interface is used to securely interact with the underlying blockchain network to achieve trusted acquisition, verification, and evidence storage of on-chain power outage event data. The verification engine is built using Spring Boot to manage verification rules, schedule transactions, and record audit logs. A visual interface is built using the Vue.js framework to provide users with intuitive data query, verification result display, and interactive functions.

3. The blockchain-based trusted management method for power outage data according to claim 2, characterized in that: In on-chain traceability management, the Elasticsearch engine is used for full-text search, the GraphQL interface provides data query services, and a web browser component is used to realize the visualization, tracking and auditing of on-chain transactions.

Images