Data comparison verification method and system based on block chain and oracle machine

Abstract

The invention relates to the technical field of data verification, in particular to a data comparison verification method and system based on a block chain and an oracle machine. According to the method, the second to-be-compared data generated at all the metering terminals included in the aggregation control unit in the last period is acquired in the block chain through the data uplink contract, and the security and credibility of the source of the second to-be-compared data are ensured. The first to-be-compared data is obtained through the oracle machine, so that credible access to the under-chain data from the block chain becomes possible, the source channel of the multi-source data is expanded, and the first to-be-compared data is ensured to be true and credible. The aggregation of the second to-be-compared data and the comparison of the first to-be-compared data and the aggregated second to-be-compared data are performed through the data comparison contract deployed in the block chain, so that the influence of human intervention is avoided, and the fairness and justice of data comparison are ensured. And finally, the verification result is uploaded to the block chain for recording, so that the transparency and non-tampering property of the verification process are ensured.

Description

Technical Field

[0001] This application relates to the technical field of data verification, and in particular, to a data comparison and verification method and system based on blockchain and oracle. Background Art

[0002] Promoting new energy storage, source-load aggregators and other third parties to provide power auxiliary services and participate in the power auxiliary service market as independent entities is a key point in the construction of the new power system and the dispatching operation of the new business format. Distributed resources mainly participate in the day-ahead invitation of the demand response market, and there are few actual applications in the real-time control of the power grid. Different from traditional power generation units, the external characteristics of source-load aggregators are the representation of the dynamic performance of the aggregation and coordination of a large number of distributed resources, and highly informatization is required to solve the complementary and collaborative problems between strongly uncertain individual units. It is a clean, low-carbon, safe and efficient light-asset solution. However, the physical nodes of large-scale distributed resources are scattered, information acquisition is difficult, and there are many stakeholders. Their participation in the operation of the power system requires solving many technical challenges. Among them, how to solve the problems of the credibility and cross-verification technology of the metering data of distributed energy and the aggregated data of aggregators is a relatively key issue.

[0003] Metering data is the data collected and uploaded by metering terminals, belonging to the data collected by Internet of Things hardware devices. There are many aggregation control units under each aggregator, and there are multiple metering terminals under each aggregation control unit. The aggregator aggregates the metering data under each aggregation control unit in seconds.

[0004] Currently, the traditional solution to such problems is to develop centralized data aggregation and comparison services, first process data from different sources into data under the same dimension, such as second-level data based on aggregation control units, and then compare the data from different sources according to pre-set comparison rules, and save the comparison results. However, the above solutions cannot solve the problem of the credibility of data sources, nor can they solve the problems of data tampering and credible cross-verification in the process of data cross-comparison and data result storage. Summary of the Invention

[0005] To at least overcome to some extent the problems in the related art that it is difficult to solve the credibility and cross-verification of the metering data of distributed energy and the aggregated data of aggregators, this application provides a data comparison and verification method and system based on blockchain and oracle.

[0006] The solution of this application is as follows: According to the first aspect of the embodiments of this application, a data comparison and verification method based on blockchain and oracle is provided, including: When entering the current cycle, call the oracle contract and the data on-chain contract through the data comparison contract deployed on the blockchain; Invoke the data acquisition interface of the oracle service through the oracle contract to obtain the first data to be compared generated at each aggregation control unit in the previous cycle; Invoke the data on-chain contract to obtain the second data to be compared generated at all metering terminals included in the aggregation control unit in the previous cycle in the blockchain; Through the data comparison contract, aggregate the second data to be compared in units of the aggregation control unit to which it belongs, and based on the preset comparison rules, compare the first data to be compared and the aggregated second data to be compared; Verify whether the first data to be compared and the second data to be compared are credible according to the comparison result, and upload the verification result to the blockchain.

[0007] Preferably, the method further includes: Bind a blockchain on-chain account to each metering terminal through a pair of public and private keys; Deploy a data on-chain contract at the metering terminal, and upload the actual energy consumption data generated at the metering terminal to the blockchain through the data on-chain contract.

[0008] Preferably, uploading the actual energy consumption data generated at the metering terminal to the blockchain through the data on-chain contract includes: Based on a preset frequency, process the actual energy consumption data generated at the metering terminal into data to be uploaded according to the on-chain data structure; Sign the data to be uploaded with the account private key; Invoke the data upload interface in the data on-chain contract to initiate a data upload request to the blockchain node; After the signature verification of the data to be uploaded by the blockchain node passes, complete the on-chain process.

[0009] Preferably, the fields of the on-chain data structure at least include: metering terminal identifier, operating status, active power, and acquisition timestamp; The fields of the first data to be compared generated at the obtained aggregation control unit at least include: aggregation control unit identifier, aggregation control unit name, active power, and acquisition timestamp.

[0010] Preferably, the method further includes: Deploy an oracle contract at the oracle; Through the oracle contract, build a connection between the oracle service and the data providing service of the aggregation control unit.

[0011] Preferably, the method further includes: Invoke the data acquisition interface of the oracle service through the oracle contract to obtain the inclusion relationship between the aggregation control unit and the metering terminal.

[0012] Preferably, based on a preset comparison rule, comparing the first data to be compared and the aggregated second data to be compared includes: Calculating the average value of the first active power of each aggregation control unit according to the first data to be compared; Calculating the average value of the second active power of each aggregation control unit according to the aggregated second data to be compared; Comparing the average value of the first active power and the average value of the second active power.

[0013] Preferably, verifying whether the first data to be compared and the second data to be compared are credible according to the comparison result includes: Calculating the ratio of the average value of the first active power and the average value of the second active power; Judging whether the ratio of the average value of the first active power and the average value of the second active power is within a preset credibility interval; If the ratio of the average value of the first active power and the average value of the second active power is within the preset credibility interval, it is verified that the first data to be compared and the second data to be compared are credible; otherwise, it is verified that the first data to be compared and the second data to be compared are not credible.

[0014] Preferably, the preset credibility interval is 90% - 110%.

[0015] According to the second aspect of the embodiments of the present application, a data comparison and verification based on blockchain and oracle is provided, including: A processor and a memory; The processor is connected to the memory through a communication bus: Wherein, the processor is used to call and execute the program stored in the memory; The memory is used to store a program, and the program is at least used to execute a data comparison and verification method based on blockchain and oracle as described in any one of the above.

[0016] The technical solution provided by the present application may include the following beneficial effects: The data comparison and verification method based on blockchain and oracle in this application includes: when entering the current cycle, calling the oracle contract and the data on-chain contract through the data comparison contract deployed on the blockchain; calling the data acquisition interface of the oracle service through the oracle contract to obtain the first data to be compared generated at each aggregation control unit in the previous cycle; obtaining the second data to be compared generated at all metering terminals included in the aggregation control unit in the previous cycle in the blockchain through the data on-chain contract; aggregating the second data to be compared by the data comparison contract in units of the affiliated aggregation control unit, and comparing the first data to be compared and the aggregated second data to be compared based on a preset comparison rule; verifying whether the first data to be compared and the second data to be compared are credible according to the comparison result, and uploading the verification result to the blockchain.

[0017] In this application, the first data to be compared generated at the aggregation control unit and the second data to be compared generated at the metering terminal are verified based on the cycle to ensure the real-time nature of data comparison and verification. Obtaining the second data to be compared generated at all metering terminals included in the aggregation control unit in the previous cycle in the blockchain through the data on-chain contract ensures the security and credibility of the source of the second data to be compared. Obtaining the first data to be compared through the oracle makes it possible to access off-chain data trustworthily from the blockchain, expands the source channels of multi-source data, and also ensures the authenticity and credibility of the acquisition of the first data to be compared. The aggregation of the second data to be compared and the comparison of the first data to be compared and the aggregated second data to be compared are both carried out through the data comparison contract deployed on the blockchain, avoiding the influence of human intervention, ensuring the fairness and impartiality of data comparison, and thus further ensuring the credibility of data comparison. Finally, the verification result is uploaded to the blockchain for recording to ensure the transparency and immutability of the verification process. As a distributed ledger, the blockchain can provide publicly verifiable data verification results for all relevant parties.

[0018] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit this application. Brief Description of the Drawings

[0019] The accompanying drawings here are incorporated into the specification and constitute a part of this specification, showing embodiments consistent with this application, and are used together with the specification to explain the principles of this application.

[0020] Figure 1 It is a schematic flowchart of a data comparison and verification method based on blockchain and oracle provided by an embodiment of this application; Figure 2 It is an implementation architecture diagram of a data comparison and verification method based on blockchain and oracle provided by an embodiment of this application; Figure 3It is a schematic structural diagram of a data comparison and verification system based on blockchain and oracle provided by an embodiment of the present application.

[0021] Reference numerals: Processor - 21; Memory - 22. Detailed implementation manners

[0022] Here, the exemplary embodiments will be described in detail, and the examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with the present application. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0023] Embodiment 1 Figure 1 It is a schematic flowchart of a data comparison and verification method based on blockchain and oracle provided by an embodiment of the present application. Refer to Figure 1 A data comparison and verification method based on blockchain and oracle includes: S11: When entering the current cycle, call the oracle contract and the data on-chain contract through the data comparison contract deployed on the blockchain; In this technical solution, the first data to be compared generated at the aggregation control unit and the second data to be compared generated at the metering terminal are verified based on the cycle, ensuring the real-time nature of data comparison and verification.

[0024] In specific practice, each cycle can be 15 minutes.

[0025] S12: Call the data acquisition interface of the oracle service through the oracle contract to obtain the first data to be compared generated at each aggregation control unit in the previous cycle; S13: Obtain the second data to be compared generated at all metering terminals included in the aggregation control unit in the previous cycle in the blockchain through the data on-chain contract; S14: Through the data comparison contract, aggregate the second data to be compared in units of the affiliated aggregation control unit, and based on the preset comparison rules, compare the first data to be compared with the aggregated second data to be compared; S15: Verify whether the first data to be compared and the second data to be compared are credible according to the comparison result, and upload the verification result to the blockchain.

[0026] Figure 2 It is an implementation architecture diagram of a data comparison and verification method based on blockchain and oracle provided by an embodiment of the present application. Refer to Figure 2, the data comparison contract on the blockchain is the core component, responsible for initiating the entire data verification process and performing data comparison. The data comparison contract will call the oracle contract and the data uploading contract to the blockchain. The oracle is used to interact with the external world and obtain data outside the blockchain. Here, it is used to obtain the "first data to be compared" from the outside, that is, the data generated by each aggregation control unit in the previous cycle. The data uploading contract to the blockchain retrieves the "second data to be compared" from the blockchain. These data are generated by each metering terminal in the aggregation control unit and have been uploaded to the blockchain.

[0027] Since there are many aggregation control units under each aggregator, and there are multiple metering terminals under each aggregation control unit. The second data to be compared obtained in this technical solution is the data at each metering terminal, while the first data to be compared is the data at each aggregation control unit. In order to compare the two, it is necessary to adjust them to the same dimension. In this technical solution, it is selected to aggregate the second data to be compared in units of the affiliated aggregation control unit, so that the aggregated second data to be compared is in units of the aggregation control unit and belongs to the same dimension as the first data to be compared.

[0028] The second data to be compared is obtained from the blockchain through the data uploading contract to the blockchain for all metering terminals included in the aggregation control unit in the previous cycle, ensuring the security and credibility of the source of the second data to be compared. The first data to be compared is obtained through the oracle, making it possible to access off-chain data trustworthily from the blockchain, expanding the source channels of multi-source data, and also ensuring the authenticity and credibility of the acquisition of the first data to be compared. The aggregation of the second data to be compared and the comparison of the first data to be compared and the aggregated second data to be compared are all carried out through the data comparison contract deployed on the blockchain, avoiding the influence of human intervention and ensuring the fairness and justice of data comparison, thus further ensuring the credibility of data comparison. Finally, the verification result is uploaded to the blockchain for recording, ensuring the transparency and immutability of the verification process. As a distributed ledger, the blockchain can provide publicly verifiable data verification results for all relevant parties.

[0029] This technical solution can be applied to multiple fields, especially in important systems that require ensuring data consistency and accuracy, such as: Smart grid management: The data generated by multiple metering terminals need to be compared and verified to ensure the accuracy of the metering data in the power system.

[0030] It should be noted that the method also includes: Binding a blockchain on-chain account to each metering terminal through a pair of public and private keys; Deploying a data uploading contract to the blockchain at the metering terminal, and uploading the actual energy consumption data generated at the metering terminal to the blockchain through the data uploading contract to the blockchain.

[0031] Each metering terminal has a unique blockchain account, which makes the data of each device unique, traceable, and secure. By binding the public-private key pair, the energy consumption data actually generated at the metering terminal is uploaded to the chain through the data upload contract to ensure the identity authentication and encryption security of the data upload. The identity of the data uploader is verified by the public-private key pair to improve the security and tamper-proof ability of the system. Among them, the energy consumption data actually generated at the metering terminal is uploaded to the chain through the data chain contract, including: Based on the preset frequency, the energy consumption data actually generated at the metering terminal is processed into data to be uploaded according to the uploaded data structure; Sign the data on the chain using the account private key; Call the data upload interface in the data chain contract to initiate a data upload request to the blockchain node; After the blockchain node passes the signature verification of the on-chain data, the on-chain is completed.

[0032] In practice, the preset frequency can be 1 second. The energy consumption data is uploaded regularly to ensure the real-time and accuracy of the energy consumption data.

[0033] The fields of the uplink data structure include at least: metering terminal identification, operating status, active power and collection timestamp.

[0034] The following is an example of the on-chain data structure: struct Terminal { string t_id; / / Metering terminal ID string status; / / Running status offline, online string p; / / active power string timestamp; / / Collection timestamp } This technical solution ensures that each piece of data on the chain has a corresponding metering terminal identifier, so that the data can be accurately attributed to a specific control unit, facilitating the tracking of the accuracy of each data source. Each piece of data on the chain has active power for subsequent data comparison. Each piece of data on the chain has a timestamp, which supports the backtracking and timeliness verification of historical data.

[0035] By signing with the account private key, we ensure that the upload of each piece of data is initiated by a legitimate metering terminal to prevent malicious tampering or falsification of data.

[0036] In actual practice, data is uploaded to the chain by calling the data upload interface in the data upload contract through the RPC interface or blockchain SDK.

[0037] Correspondingly, the fields of the first data to be compared generated at the aggregation control unit at least include: aggregation control unit identifier, aggregation control unit name, active power, and acquisition timestamp.

[0038] An example of the first data to be compared generated at the aggregation control unit is as follows: struct AggUnitData { string aggUnitId; / / Aggregation control unit identifier string aggUnitName; / / Aggregation control unit name string p; / / Active power string timestamp; / / Timestamp } It should be noted that the method further includes: Deploying an oracle contract at the oracle; Constructing a connection between the oracle service and the data providing service of the aggregation control unit through the oracle contract.

[0039] Deploying an oracle contract at the oracle to construct a connection between the oracle service and the data providing service of the aggregation control unit. By connecting the oracle contract with the data providing service of the aggregation control unit, it is ensured that external data can be accurately and securely introduced into the blockchain. This enhances the flexibility of the system, enabling dynamic acquisition and verification of external data from different sources.

[0040] It should be noted that the method further includes: Invoking the data acquisition interface of the oracle service through the oracle contract to obtain the inclusion relationship between the aggregation control unit and the metering terminal.

[0041] Since there are many aggregation control units under each aggregator, and there are multiple metering terminals under each aggregation control unit. In this technical solution, it is necessary to invoke the data acquisition interface of the oracle service through the oracle contract to obtain the inclusion relationship between the aggregation control unit and the metering terminal, so as to determine how to aggregate the second data to be compared uploaded by the metering terminal.

[0042] It should be noted that based on a preset comparison rule, comparing the first data to be compared and the aggregated second data to be compared includes: Calculating the average value of the first active power of each aggregation control unit according to the first data to be compared; Calculating the average value of the second active power of each aggregation control unit according to the aggregated second data to be compared; Comparing the average value of the first active power and the average value of the second active power.

[0043] It should be noted that the fields of the on-chain data structure include active power, and the fields of the first data to be compared generated at the obtained aggregation control unit also include active power. In this embodiment, the first average active power of each aggregation control unit is calculated according to the first data to be compared, the second average active power of each aggregation control unit is calculated according to the aggregated second data to be compared, and the first average active power and the second average active power are compared to verify whether the first data to be compared and the second data to be compared are credible. Comparing using the average value of active power can smooth the volatility in the data, reduce the influence of accidental errors, and improve the credibility of the data. By comparing the average values of the two data sets, the reliability and consistency of the data can be evaluated more comprehensively and accurately, rather than a single numerical comparison. Comparing using the average value of active power can smooth the volatility in the data, reduce the influence of accidental errors, and improve the credibility of the data.

[0044] It should be noted that verifying whether the first data to be compared and the second data to be compared are credible according to the comparison result includes: Calculating the ratio of the first average active power and the second average active power; Judging whether the ratio of the first average active power and the second average active power is within a preset credibility interval; If the ratio of the first average active power and the second average active power is within the preset credibility interval, it is verified that the first data to be compared and the second data to be compared are credible; otherwise, it is verified that the first data to be compared and the second data to be compared are not credible.

[0045] In specific practice, the preset credibility interval is 90% - 110%.

[0046] If the ratio of the first average active power and the second average active power is lower than 90% or higher than 110%, it indicates that the difference between the first average active power and the second average active power is large, and there is probably a problem with one of them.

[0047] Upload the verification result to the blockchain for recording to ensure the transparency and immutability of the verification process. As a distributed ledger, the blockchain can provide publicly verifiable data verification results for all relevant parties.

[0048] Embodiment 2 Figure 3 is a schematic structural diagram of a data comparison and verification system based on blockchain and oracle provided by an embodiment of the present application. Refer to Figure 3 A data comparison and verification based on blockchain and oracle includes: A processor 21 and a memory 22; The processor 21 is connected to the memory 22 through a communication bus: Among them, the processor 21 is used to call and execute the program stored in the memory 22; The memory 22 is used to store the program, and the program is at least used to execute a data comparison and verification method based on blockchain and oracle as described in any one of the above.

[0049] It can be understood that the same or similar parts in the above embodiments can be referred to each other, and the content not detailed in some embodiments can be seen in the same or similar content of other embodiments.

[0050] It should be noted that in the description of this application, the terms "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. In addition, in the description of this application, unless otherwise specified, the meaning of "a plurality" refers to at least two.

[0051] Any process or method description shown in the flowchart or described in other ways herein can be understood as representing a module, segment, or part of the code of executable instructions including one or more steps for implementing a specific logical function or process. The scope of the preferred embodiments of this application includes additional implementations, where the functions can be executed in a substantially simultaneous manner or in the reverse order according to the involved functions, rather than in the order shown or discussed. This should be understood by those skilled in the technical field of the embodiments of this application.

[0052] It should be understood that each part of this application can be implemented by hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented by software or firmware stored in the memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, any one or a combination of the following well-known technologies in the art can be used: discrete logic circuits with logic gate circuits for implementing logical functions on data signals, application-specific integrated circuits with appropriate combinational logic gate circuits, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0053] Those of ordinary skill in the technical field of this application can understand that all or part of the steps carried by the methods in the above embodiments can be completed by instructing relevant hardware through a program. The program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiments.

[0054] In addition, each functional unit in various embodiments of the present application may be integrated into a processing module, or each unit may exist physically alone, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. When the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

[0055] The above-mentioned storage medium may be a read-only memory, a magnetic disk, an optical disc, etc.

[0056] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples", etc. means that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in a suitable manner in any one or more embodiments or examples.

[0057] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and should not be construed as limiting the present application. Those of ordinary skill in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present application.

Claims

1. A data comparison and verification method based on blockchain and oracle, characterized in that: include: When entering the current cycle, the oracle contract and the data on-chain contract are called through the data comparison contract deployed on the blockchain; Calling the data acquisition interface of the oracle service through the oracle contract to obtain the first data to be compared generated by each aggregation control unit in the previous cycle; Obtaining the second data to be compared generated at all metering terminals included in the aggregation control unit in the previous period in the blockchain through the data on-chain contract; Aggregating the second data to be compared by using the aggregation control unit to which it belongs through the data comparison contract, and comparing the first data to be compared with the aggregated second data to be compared based on a preset comparison rule; Verify whether the first data to be compared and the second data to be compared are credible based on the comparison result, and upload the verification result to the blockchain.

2. The method according to claim 1, characterized in that The method further comprises: Each metering terminal is bound to an account on the blockchain through a pair of public and private keys; A data chain contract is deployed at the metering terminal, and the energy consumption data actually generated at the metering terminal is uploaded to the chain through the data chain contract.

3. The method according to claim 2, characterized in that The energy consumption data actually generated at the metering terminal is uploaded to the chain through the data chain contract, including: Based on the preset frequency, the energy consumption data actually generated at the metering terminal is processed into data to be uploaded according to the uploaded data structure; Sign the data to be uploaded to the chain using the account private key; Call the data upload interface in the data chain contract to initiate a data upload request to the blockchain node; After the blockchain node verifies the signature of the data to be uploaded to the chain, the data is uploaded to the chain.

4. The method according to claim 3, characterized in that The fields of the uplink data structure include at least: metering terminal identification, operating status, active power and acquisition timestamp; The fields of the first data to be compared generated at the acquired aggregation control unit include at least: an aggregation control unit identifier, an aggregation control unit name, active power, and an acquisition timestamp.

5. The method according to claim 1, characterized in that The method further comprises: Deploy the oracle contract at the oracle; The oracle service is built through the oracle contract to connect with the data provision service of the aggregation control unit.

6. The method according to claim 5, characterized in that The method further comprises: The data acquisition interface of the oracle service is called through the oracle contract to obtain the inclusion relationship between the aggregation control unit and the metering terminal.

7. The method according to claim 4, characterized in that Comparing the first to-be-compared data with the aggregated second to-be-compared data based on a preset comparison rule includes: Calculate a first active power average value of each aggregation control unit according to the first data to be compared; Calculate a second active power average value of each aggregation control unit according to the aggregated second data to be compared; The first active power average value is compared with the second active power average value.

8. The method according to claim 7, characterized in that Verifying whether the first data to be compared and the second data to be compared are credible according to the comparison result includes: Calculating a ratio of the first active power average value to the second active power average value; Determining whether a ratio of the first active power average value to the second active power average value is within a preset credibility interval; If the ratio of the first average active power value to the second average active power value is within a preset credibility interval, the first data to be compared and the second data to be compared are verified to be credible; otherwise, the first data to be compared and the second data to be compared are verified to be uncredible.

9. The method according to claim 8, characterized in that The preset confidence interval is 90%-110%.

10. A data comparison and verification based on blockchain and oracle, characterized in that: include: Processor and memory; The processor and the memory are connected via a communication bus: Wherein, the processor is used to call and execute the program stored in the memory; The memory is used to store a program, and the program is at least used to execute a data comparison and verification method based on blockchain and oracle as described in any one of claims 1 to 9.

Images