Block chain-based power failure data credible management method

Abstract

The invention discloses a power failure data credible management method based on a block chain, and relates to the technical field of power supply reliability management, and the method comprises the following steps: data uplink management: obtaining a power failure event and reliability data, carrying out Hash calculation, generating a unique data fingerprint, and writing a Hash value and related metadata into the block chain; performing uplink configuration management: performing failure compensation operation after the uplink failure event is triggered; on-chain checking management: through comparison of Hash calculation and block chain original evidence, performing automatic and manual checking on business data consistency; checking task management: carrying out Hash calculation on the power supply reliability power failure data, then comparing the power supply reliability power failure data with an on-chain Hash value, marking items with inconsistent comparison results, and recording the items; and chain traceability management: displaying the traceability list according to a reverse order of time, positioning corresponding items according to query conditions, and checking chain evidence storage tracks and operation history of the corresponding items. The defects in the prior art can be overcome, and the efficiency and accuracy of data checking are improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of power supply reliability management, and in particular to a power outage data credible management method based on a block chain. BACKGROUND

[0002] In traditional power supply reliability management, the management and verification of power outage data have problems such as insufficient transparency, poor traceability, and low verification efficiency, especially in different regions, the differences in power supply reliability management easily affect the accuracy of reported matters. At present, the following problems exist in this field: (1) Low data credibility: power outage events, user power outage time, reliability indicators and other data are stored in provincial and headquarters databases, there is a risk of tampering and forgery afterwards, especially in cross-regional benchmarking, the authenticity of the data is difficult to prove. (2) Low data verification efficiency: traditional verification relies on manual sampling and cross comparison, facing massive data checking, the workload is huge, the efficiency is extremely low, and errors are easy to occur, which cannot realize comprehensive and timely auditing. (3) Weak traceability: the modification history and verification records of the data log information are stored in a centralized database, which is not credible, and cannot form a complete and tamper-proof audit evidence chain.

[0003] In the current technical practice, the block chain technology is applied in different fields, in the aspect of power supply reliability management, there is still a lack of end-to-end technical solutions that can organically integrate functions such as credible data notarization, automatic consistency verification, intelligent compensation on-chain, and full-link penetration traceability, and there is a lack of an efficient, transparent, and traceable data management and verification method in the existing technology.

[0004] In the current technical practice, although the block chain technology has achieved preliminary application in data notarization in the fields of finance and supply chain, its universal architecture cannot meet the specific needs of the high real-time and high reliability business scenarios of power supply reliability management. The existing solutions generally have three core defects: first, the traditional centralized notarization mode cannot guarantee the non-tamperability of power outage event key business data in the whole process of generation, transmission and storage, and there are data islands between multi-source systems (such as SCADA, distribution automation, and power consumption information collection system); second, the business rules are not coded on the chain, the calculation of power outage time, the determination of responsibility section and other key processes still rely on manual intervention, and there is a lack of automatic consistency verification mechanism based on smart contract; third, the traceability capability stays at the surface data correlation, and cannot build an evidence chain running through the source system, data research and judgment, and business application. SUMMARY

[0005] The technical problem to be solved by the present application is to provide a power outage data credible management method based on a block chain, which can solve the deficiencies of the prior art, improve the traceability of data, and improve the efficiency and accuracy of data verification.

[0006] To solve the above technical problems, the technical solutions adopted by the present application are as follows.

[0007] A power outage data credible management method based on a blockchain includes the following steps:

[0008] Data chaining management: obtain power outage events and reliability data through a standardized chaining storage interface, perform hash calculation on the original data to generate a unique data fingerprint, call an intelligent contract to write the hash value and related metadata into a blockchain, and complete credible storage;

[0009] Chaining configuration management: perform chaining failure detection, and perform failure compensation operations when a chaining failure event is triggered to ensure complete data chaining;

[0010] On-chain verification management: through hash calculation and comparison with original blockchain storage, automatically and manually verify the consistency of business data, and generate a structured verification report;

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

[0012] On-chain traceability management: record the verification history of each power outage item, form a traceability list that can be displayed in reverse chronological order, locate the corresponding item according to the query condition, and view the on-chain storage track and operation history.

[0013] As a preferred, in the data chaining management process, the JSON format data of the power outage event is obtained from the power grid resource business platform in real time through the API gateway, and the data is cleaned and standardized to ensure the integrity and consistency of the chained data; a distributed node network is constructed based on the State Grid alliance chain platform, the PBFT consensus mechanism is adopted to ensure the data consistency and system fault tolerance between nodes, and the safe storage of power outage event data is realized.

[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 penetration type traceability engine improves data consistency and integrity. The application provides a method for realizing power supply reliability power failure data chaining and on-chain data checking based on a block chain technology, solves the problems of poor traceability and low checking efficiency of power failure data management, reduces the workload of grassroots employees, improves the overall efficiency of power supply reliability management, and provides a credible data infrastructure for "source-net-load-storage" collaboration. BRIEF DESCRIPTION OF DRAWINGS

[0022] Figure 1 is the schematic diagram of one embodiment of the application. DETAILED DESCRIPTION

[0023] In the following description of the embodiments, specific details are presented to provide a thorough understanding of the embodiments of the application, but the application can be practiced without these specific details. One skilled in the art will appreciate that in other embodiments, in the absence of these specific details, the application can also be implemented. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the application with unnecessary details.

[0024] Referring to Figure 1 The power failure data credible management method based on a block chain provided by the application includes the following steps:

[0025] Data chaining management: obtain power failure events and reliability data through a standardized chaining storage interface, perform hash calculation on the original data, generate a unique data fingerprint, call an intelligent contract to write the hash value and related metadata into a block chain, and complete credible storage.

[0026] Chaining configuration management: perform failure compensation operations when the chaining fails, and ensure complete data chaining.

[0027] On-chain checking management: compare the hash calculation with the original storage of the block chain, automatically and manually check the consistency of business data, and generate a structured checking report.

[0028] Checking task management: compare the hash calculation of the power supply reliability power failure data with the on-chain hash value, mark the items with inconsistent comparison results, and record them.

[0029] On-chain traceability management: record the checking history of each power failure item, form a traceability list that can be displayed in reverse chronological order, locate the corresponding item according to the query condition, and view the on-chain storage track and operation history.

[0030] In the data chaining management process, the JSON format data of power outage events is obtained from the power grid resource business platform in real time through the API gateway, and the data is cleaned and standardized to ensure the integrity and consistency of the chained data. Based on the State Grid Alliance Chain platform, a distributed node network is constructed, and the PBFT consensus mechanism is adopted to ensure the data consistency and system fault tolerance among nodes, and the safe storage of power outage event data is realized. Specifically, it includes the following four aspects:

[0031] (1) Data collection: Real-time acquisition of power outage event data from the business platform through HTTP request or MQ message, 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, and then JSON canonicalization scheme is used for data formatting to ensure the uniformity of field ordering and encoding format. The formula for data preprocessing is as follows: Dstd = Canonicalize(Draw).

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

[0034] (4) Chaining storage: Through the RESTful API interface provided by the State Grid Chain, the smart contract is called to form a transaction body Tx with data hash value Hdata, timestamp t, and submitter digital signature σ, etc. The formula is as follows: Tx = {Hdata, t, σ, metadata} Block <- Block U Tx After signing by SM2 national encryption algorithm, it is submitted to the blockchain network, and through the PBFT consensus mechanism, the nodes reach a consensus and write it into the block, generating a transaction hash and block height as a storage certificate.

[0035] This scheme combines cryptography algorithms and distributed ledger technology to ensure the non-tamperability and traceability of power outage event data. At the same time, it adopts a hybrid architecture of off-chain storage of original data and on-chain storage of hash value, 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: By using the RESTful verification interface provided by the State Grid chain, the unique ID of the event is transmitted to obtain the original hash value H_current stored on the chain, and the comparison result is as follows: The system uses the Constant Time Compare algorithm for hash value comparison to prevent timing attacks.

[0042] (4) Result recording: The comparison result (including comparison time, operator, event ID, hash value comparison status) is written into the Elasticsearch log system, and the "data tampering" flag is marked for inconsistent items, and real-time alarm notification is triggered.

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

[0044] This scheme provides an end-to-end trusted verification mechanism for power outage event data through standardized verification processes and cryptographic guarantees, meeting regulatory audit requirements, significantly improving verification efficiency through automated comparison and report generation, and ensuring the consistency and verifiability of on-chain and off-chain data.

[0045] In the verification task management, Spring Cloud framework is used to realize inter-service communication, and task state data is stored in the database, and Redis cache is used to improve task query performance. The specific implementation includes four core links:

[0046] (1) Task sheet generation: Users configure verification parameters (including time range, regional screening, event type, etc.) through the front-end interface, and the system background generates task work orders through the workflow engine Activiti, stores task metadata (task ID, creator, creation time, verification rule) to the database, and initializes the task state to "to be executed".

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

[0048] (3) Task list query: Provide a multi-dimensional composite query interface, support combined query by task status, time range, creator, etc. Query results are returned to the front end through paging technology for display, and a visual dashboard of task details is provided to show task progress, verification items and abnormality ratio in real time.

[0049] (4) Task verification report: Based on template engine (Apache POI), dynamically generate structured reports, including verification overview, consistency statistical charts (visualized by ECharts), abnormal data details table, etc. Report output formats support PDF and Excel, and users can download reports through secure links.

[0050] This scheme realizes batch credible verification of large-scale power outage event data through automatic task scheduling and batch processing mechanism, significantly improving verification efficiency; through perfect task state management and visual display, it provides comprehensive task monitoring and audit tracking ability for managers, ensuring the systematicness and standardization of power supply reliability data verification.

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

[0052] (1) Traceability list generation: According to the unique identifier of power outage event (such as eventId), the system aggregates data from business database, blockchain browser API and verification record library through data correlation engine to automatically generate structured traceability list containing initial data version, previous verification timestamp, block height, transaction hash and other key information. List items are arranged in reverse chronological order and marked with data consistency status at each link.

[0053] (2) Traceability record query: Provide an intelligent query interface, support combined query by event ID, time range, block height, transaction hash, verification result, etc. Query engine uses Elasticsearch inverted index technology to achieve millisecond-level response, supports fuzzy matching and synonym expansion query, and returns results with key information highlighted.

[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 called to write the hash value and related metadata into the blockchain to complete the trusted evidence storage. 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; 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. 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; 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.

2. The blockchain-based trusted management method for power outage data according to claim 1, characterized in that: 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. 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.

3. The blockchain-based trusted management method for power outage data according to claim 2, characterized in that: In the on-chain configuration management, the response status of the State Grid Chain API interface is monitored in real time through the event 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 context 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 operation and maintenance personnel. The details of the compensation failure data are also displayed visually on the dashboard.

4. The blockchain-based trusted management method for power outage data according to claim 3, 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 data such as power outage events on the chain. 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.

5. The blockchain-based trusted management method for power outage data according to claim 4, characterized in that: In the task management process, the Spring Cloud framework is used to implement inter-service communication, task status data is persistently stored in the database, and task query performance is improved by using Redis caching.

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

Images