Carbon account data management system, method and apparatus, device, and medium

Abstract

The present application discloses a carbon account data management system, method and apparatus, a device, and a medium. A carbon account application management device acquires, for respective carbon account applications of organizations, low-carbon transaction data collected by the carbon account applications, and sends the low-carbon transaction data to a transaction deduplication management device; the transaction deduplication management device acquires carbon account identifiers, transaction information, and low-carbon behavior information carried in the low-carbon transmission data, determines a repeated cumulative transaction identification result of the low-carbon transaction data on the basis of the carbon account identifiers, transaction information, and low-carbon behavior information carried in the low-carbon transmission data, calculates, on the basis of the identification result, carbon emission reduction amounts corresponding to the low-carbon transaction data, and sends the carbon emission reduction amounts to the carbon account application management device; and the carbon account application management device bundles the carbon emission reduction amounts on the basis of the carbon account identifiers to obtain a bundled carbon emission reduction amount, determines a bundled transaction on the basis of the carbon account identifiers and the bundled carbon emission reduction amount, and sends the bundled transaction to a corresponding blockchain node. A solution for achieving interconnections and intercommunications between carbon account applications of organizations, and unified management of carbon account data is provided.

Description

A carbon account data management system, method, device, equipment and medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on March 20, 2024, with application number 202410324542.8 and application name "A carbon account data management system, method, device, equipment and medium", the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of environmental protection and energy conservation technology, and in particular to a carbon account data management system, method, device, equipment and medium. Background Art

[0004] Achieving carbon peak and carbon neutrality is a major strategic decision made by my country within the broader global context, aimed at promoting green, healthy, and high-quality economic and social development. Building a green, low-carbon society requires not only changes on the production side but also the active participation of consumers, fostering comprehensive reform of the entire industrial chain. Individuals play a key role in driving society towards green and low-carbon goals, and the establishment and development of personal carbon accounts has become a crucial tool for promoting low-carbon initiatives. Currently, the exploration of personal carbon accounts demonstrates a flourishing trend, with multiple stakeholders, including local governments, businesses, platforms, and financial institutions, contributing to the development of these accounts.

[0005] While this diversified exploration is crucial for the development of individual carbon accounts, it also presents a series of industry pain points. For example, existing carbon accounting applications by various institutions independently collect low-carbon trading data and calculate carbon emission reductions according to their own prescribed standards. This leads to fragmented data management and calculations, and a lack of unified carbon accounting data management. Summary of the Invention

[0006] The present application provides a carbon account data management system, method, apparatus, equipment and medium for providing an implementation solution for interconnecting carbon account applications of various institutions and unified management of carbon account data.

[0007] In a first aspect, the present application provides a carbon account data management system, the system comprising: a carbon account application management device and a transaction deduplication management device;

[0008] The carbon account application management device is used to obtain the low-carbon transaction data collected by the carbon account application of each institution, and send the low-carbon transaction data to the transaction deduplication management device;

[0009] The transaction deduplication management device is configured to obtain and determine a duplicate cumulative transaction identification result of the low-carbon transaction data based on the carbon account identifier, transaction information, and low-carbon behavior information carried in the low-carbon transaction data, calculate the carbon emission reduction amount corresponding to the low-carbon transaction data based on the identification result, and send the carbon emission reduction amount to the carbon account application management device;

[0010] The carbon account application management device is used to aggregate the carbon emission reduction according to the carbon account identifier to obtain an aggregated carbon emission reduction; determine an aggregate transaction according to the carbon account identifier and the aggregated carbon emission reduction, and send the aggregate transaction to a corresponding blockchain node.

[0011] In a second aspect, the present application provides a carbon account data management method, which is applied to a transaction deduplication management device, and the method includes:

[0012] Receiving low-carbon transaction data sent by the carbon account application management device, wherein the low-carbon transaction data is low-carbon transaction data collected by the carbon account application obtained by the carbon account application management device for each institution's carbon account application;

[0013] Obtain and determine the repeated cumulative transaction identification result of the low-carbon transaction data based on the carbon account identification, transaction information and low-carbon behavior information carried in the low-carbon transaction data, calculate the carbon emission reduction corresponding to the low-carbon transaction data based on the identification result, and send the carbon emission reduction to the carbon account application management device; enable the carbon account application management device to aggregate the carbon emission reduction according to the carbon account identification to obtain the aggregated carbon emission reduction; determine the aggregated transaction based on the carbon account identification and the aggregated carbon emission reduction, and send the aggregated transaction to the corresponding blockchain node.

[0014] In a third aspect, the present application provides a carbon account data management method, which is applied to a carbon account application management device, and the method includes:

[0015] For each institution's respective carbon account application, obtain low-carbon transaction data collected by the carbon account application, and send the low-carbon transaction data to a transaction deduplication management device; cause the transaction deduplication management device to obtain and, based on the carbon account identifier, transaction information, and low-carbon behavior information carried in the low-carbon transaction data, determine a duplicate cumulative transaction identification result for the low-carbon transaction data; calculate the carbon emission reduction corresponding to the low-carbon transaction data based on the identification result; and send the carbon emission reduction amount to the carbon account application management device;

[0016] The carbon emission reduction amount is aggregated according to the carbon account identifier to obtain an aggregated carbon emission reduction amount; an aggregate transaction is determined according to the carbon account identifier and the aggregated carbon emission reduction amount, and the aggregate transaction is sent to a corresponding blockchain node.

[0017] In a fourth aspect, the present application provides a carbon account data management method, which is applied to a transaction audit device, and the method includes:

[0018] Receiving and, based on the identifier of the transaction aggregation batch and the identifier of the low-carbon transaction data to be audited, obtaining the low-carbon transaction data to be audited, the corresponding carbon emission reduction amount, and the first signature from the carbon account application management device;

[0019] Determine a first Merkle root hash value corresponding to the low-carbon transaction data to be audited based on a Merkle tree path proof algorithm, the low-carbon transaction data to be audited, the corresponding carbon emission reduction amount, and the first signature; obtain a second Merkle root hash value from a blockchain node corresponding to the identifier of the transaction aggregation batch, and determine a transaction data audit result based on the first Merkle root hash value and the second Merkle root hash value;

[0020] Determine the hash value corresponding to the low-carbon transaction data to be audited, calculate the hash value and the summary value of the carbon emission reduction, and sign the summary value to obtain a second signature; determine the carbon emission reduction audit result based on the second signature and the first signature.

[0021] In a fifth aspect, the present application provides a carbon account data management device, which is applied to a transaction deduplication management device, and the device includes:

[0022] a first receiving module, configured to receive low-carbon transaction data sent by a carbon account application management device, wherein the low-carbon transaction data is low-carbon transaction data collected by the carbon account application management device for each institution's carbon account application;

[0023] A sending module is used to obtain and determine the repeated cumulative transaction identification result of the low-carbon transaction data based on the carbon account identification, transaction information and low-carbon behavior information carried in the low-carbon transaction data, calculate the carbon emission reduction corresponding to the low-carbon transaction data based on the identification result, and send the carbon emission reduction to the carbon account application management device; enable the carbon account application management device to aggregate the carbon emission reduction according to the carbon account identification to obtain the aggregated carbon emission reduction; determine the aggregated transaction based on the carbon account identification and the aggregated carbon emission reduction, and send the aggregated transaction to the corresponding blockchain node.

[0024] In a sixth aspect, the present application provides a carbon account data management device, which is applied to a carbon account application management device, and the device includes:

[0025] an acquisition module configured to acquire, for each institution's respective carbon account application, low-carbon transaction data collected by the carbon account application, and send the low-carbon transaction data to a transaction deduplication management device; enable the transaction deduplication management device to acquire and, based on the carbon account identifier, transaction information, and low-carbon behavior information carried in the low-carbon transaction data, determine a duplicate cumulative transaction identification result for the low-carbon transaction data; calculate the carbon emission reduction amount corresponding to the low-carbon transaction data based on the identification result; and send the carbon emission reduction amount to the carbon account application management device;

[0026] The first determination module is used to aggregate the carbon emission reduction according to the carbon account identifier to obtain an aggregated carbon emission reduction; determine an aggregate transaction according to the carbon account identifier and the aggregated carbon emission reduction, and send the aggregate transaction to a corresponding blockchain node.

[0027] In a seventh aspect, the present application provides a carbon account data management device, which is applied to a transaction audit device, and the device includes:

[0028] a second receiving module, configured to receive and, based on the identifier of the transaction aggregation batch and the identifier of the low-carbon transaction data to be audited, obtain the low-carbon transaction data to be audited, the corresponding carbon emission reduction amount, and the first signature from the carbon account application management device;

[0029] A second determination module is configured to determine a first Merkle root hash value corresponding to the low-carbon transaction data to be audited based on a Merkle tree path proof algorithm, the low-carbon transaction data to be audited, the corresponding carbon emission reduction amount, and the first signature; obtain a second Merkle root hash value from a blockchain node corresponding to the identifier of the transaction aggregation batch, and determine a transaction data audit result based on the first Merkle root hash value and the second Merkle root hash value;

[0030] The third determination module is used to determine the hash value corresponding to the low-carbon transaction data to be audited, calculate the hash value and the summary value of the carbon emission reduction, and sign the summary value to obtain a second signature; determine the carbon emission reduction audit result based on the second signature and the first signature.

[0031] In an eighth aspect, the present application provides an electronic device, comprising a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus;

[0032] Memory for storing computer programs;

[0033] The processor is used to implement the method steps when executing the program stored in the memory.

[0034] In a ninth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method steps described are implemented.

[0035] The above technical solution has the following advantages or beneficial effects:

[0036] In this application, a carbon account application management device obtains low-carbon transaction data collected by each institution's carbon account application and sends the low-carbon transaction data to a transaction deduplication management device. The transaction deduplication management device then identifies duplicate accumulated transactions in the low-carbon transaction data based on the carbon account identifier, transaction information, and low-carbon behavior information contained in the low-carbon transaction data. Based on the identification results, it calculates the carbon emission reduction corresponding to the low-carbon transaction data and sends the carbon emission reduction to the carbon account application management device. This solves the problem of fragmented carbon account data, which occurs when each institution's carbon account application manages and calculates its own carbon account data. The carbon account application management device aggregates the carbon emission reduction based on the carbon account identifier to obtain an aggregated carbon emission reduction. Based on the carbon account identifier and the aggregated carbon emission reduction, it determines aggregated transactions, achieving unified management of carbon account data. Aggregated transactions are sent to the corresponding blockchain node. By combining the technical characteristics of blockchain, this enables traceability of low-carbon transaction data, providing a foundation for low-carbon transaction data auditing. This application provides a solution for interconnecting and interoperating carbon account applications across institutions and for unified management of carbon account data. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0038] Figure 1 is a schematic diagram of the structure of the carbon account data management system provided by this application;

[0039] FIG2 is a schematic diagram of the structure of the Merkle tree provided in this application;

[0040] Figure 3 is a schematic diagram of the Merkle tree provided by this application;

[0041] FIG4 is a schematic diagram of the structure of the carbon account data management system provided by this application;

[0042] FIG5 is a schematic diagram of the carbon account data management process provided by this application;

[0043] FIG6 is a schematic diagram of the carbon account data management process provided by this application;

[0044] FIG7 is a schematic diagram of the carbon account data management process provided by this application;

[0045] Figure 8 is a diagram of the carbon account data management system architecture provided by this application;

[0046] Figure 9 is a flow chart of carbon account data management provided by this application;

[0047] Figure 10 is a schematic diagram of transaction aggregation provided by this application;

[0048] Figure 11 is a flowchart of a single transaction audit provided by this application;

[0049] Figure 12 is a flowchart of a single account audit provided by this application;

[0050] FIG13 is a schematic diagram of the structure of the carbon account data management device provided by this application;

[0051] FIG14 is a schematic diagram of the structure of the carbon account data management device provided by this application;

[0052] FIG15 is a schematic diagram of the structure of the carbon account data management device provided by this application;

[0053] FIG16 is a schematic diagram of the structure of an electronic device provided in this application. DETAILED DESCRIPTION

[0054] In order to make the purpose and implementation of this application clearer, the exemplary implementation of this application will be clearly and completely described below in conjunction with the drawings in the exemplary embodiments of this application. Obviously, the described exemplary embodiments are only part of the embodiments of this application, not all of the embodiments.

[0055] It should be noted that the brief descriptions of terms in this application are only for the purpose of facilitating the understanding of the embodiments described below, and are not intended to limit the embodiments of this application. Unless otherwise specified, these terms should be understood according to their ordinary and usual meanings.

[0056] In the specification and claims of this application and the accompanying drawings, the terms "first," "second," "third," etc. are used to distinguish similar or similar objects or entities, and are not necessarily intended to limit a particular order or sequence, unless otherwise noted. It should be understood that the terms used in this manner are interchangeable under appropriate circumstances.

[0057] The terms "comprise," "include," and "have," and any variations thereof, are intended to cover but not exclude inclusion; for example, a product or device comprising a list of components is not necessarily limited to all the components expressly listed but may include other components not expressly listed or inherent to such product or device.

[0058] The term "module" refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and / or software code that is capable of performing the functionality associated with that element.

[0059] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some or all of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

[0060] For ease of explanation, the above description has been made with reference to specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or to limit the embodiments to the specific forms disclosed above. Based on the above teachings, various modifications and variations are possible. The above embodiments are selected and described to better explain the principles and practical applications, so that those skilled in the art can better utilize the embodiments and various different variations of the embodiments suitable for specific use considerations.

[0061] FIG1 is a schematic diagram of the structure of the carbon account data management system provided by this application, including: a carbon account application management device 11 and a transaction deduplication management device 12;

[0062] The carbon account application management device 11 is used to obtain low-carbon transaction data collected by the carbon account application of each institution, and send the low-carbon transaction data to the transaction deduplication management device 12;

[0063] The transaction deduplication management device 12 is configured to obtain and determine a duplicate cumulative transaction identification result of the low-carbon transaction data based on the carbon account identifier, transaction information, and low-carbon behavior information carried in the low-carbon transaction data, calculate the carbon emission reduction amount corresponding to the low-carbon transaction data based on the identification result, and send the carbon emission reduction amount to the carbon account application management device 11;

[0064] The carbon account application management device 11 is used to aggregate the carbon emission reduction according to the carbon account identifier to obtain an aggregated carbon emission reduction; determine an aggregate transaction according to the carbon account identifier and the aggregated carbon emission reduction, and send the aggregate transaction to the corresponding blockchain node.

[0065] The carbon accounting application management device can be an institutional device that maintains the carbon accounting application, or an integrated platform device. Institutional devices can be computers, servers, and other devices within the institution, while integrated platform devices can be computers, servers, and other devices within the integrated platform. Each institution can have its own carbon accounting application to collect low-carbon trading data. There is a correspondence between the carbon accounting application management device and each institution's carbon accounting application, and there must be at least one carbon accounting application management device. For some carbon accounting applications, individual carbon accounting integration platforms exist within the industry. In these cases, after the carbon accounting application collects low-carbon trading data, it first sends the low-carbon trading data to the corresponding integrated platform device, which then sends the low-carbon trading data to the transaction deduplication management device. For other carbon accounting applications, the corresponding institutional device obtains the low-carbon trading data collected by the carbon accounting application, and then sends the low-carbon trading data to the transaction deduplication management device. The transaction deduplication management device can be a computer, server, or other device.

[0066] After the carbon account application collects low-carbon transaction data, it sends the low-carbon transaction data to the carbon account application management device. The carbon account application management device obtains the low-carbon transaction data collected by the carbon account application and sends the low-carbon transaction data to the transaction deduplication management device. Low-carbon transaction data is represented as tx = (code, cid, td, lcd). The low-carbon transaction data field description is shown in the following table:

[0067] The transaction deduplication management device records each low-carbon transaction data received, and for the currently received low-carbon transaction data, obtains the carbon account identification, transaction information and low-carbon behavior information carried in the low-carbon transaction data. The duplicate cumulative transaction identification result of the low-carbon transaction data is determined based on the carbon account identification, transaction information and low-carbon behavior information carried in the low-carbon transaction data. Among them, the identification result includes whether the low-carbon transaction data is a duplicate cumulative transaction and whether the low-carbon transaction data is not a duplicate cumulative transaction. If, in each low-carbon transaction data recorded by the transaction deduplication management device, there is low-carbon transaction data that is exactly the same as the carbon account identification, transaction information and low-carbon behavior information carried by the currently received low-carbon transaction data, then the identification result is determined to be that the low-carbon transaction data is a duplicate cumulative transaction; otherwise, the identification result is determined to be that the low-carbon transaction data is not a duplicate cumulative transaction.

[0068] The carbon emission reduction corresponding to the low-carbon transaction data is calculated based on the identification result, and the carbon emission reduction is sent to the carbon account application management device. Optionally, the transaction deduplication management device is configured to determine the carbon emission reduction corresponding to the low-carbon transaction data as 0 if the identification result indicates that the low-carbon transaction data is a duplicate cumulative transaction; and to determine the carbon emission reduction corresponding to the low-carbon transaction data according to a preset carbon emission reduction algorithm if the identification result indicates that the low-carbon transaction data is not a duplicate cumulative transaction.

[0069] If the identification result is that the low-carbon transaction data is a repeated cumulative transaction, it means that the carbon emission reduction of the low-carbon transaction data has been calculated, and the carbon emission reduction corresponding to the low-carbon transaction data is directly determined to be 0. If the identification result is that the low-carbon transaction data is not a repeated cumulative transaction, it means that the carbon emission reduction of the low-carbon transaction data has not been calculated. At this time, the carbon emission reduction corresponding to the low-carbon transaction data is determined according to the preset carbon emission reduction algorithm. The carbon account data management system provided by this application realizes the unified management of the low-carbon transaction data collected by each carbon account application. When calculating the carbon emission reduction, the preset carbon emission reduction algorithm is uniformly used for calculation, which solves the problem that each carbon account application uses different algorithms to calculate the carbon emission reduction, resulting in scattered data and poor accuracy.

[0070] The transaction deduplication management device sends the carbon emission reduction to the carbon account application management device. The carbon account application management device aggregates the carbon emission reduction according to the carbon account identifier to obtain the aggregated carbon emission reduction. Optionally, the carbon emission reductions of the same carbon account identifier can be accumulated and aggregated to obtain the aggregated carbon emission reduction corresponding to the carbon account identifier. Optionally, the aggregation time period can be specified. For example, the carbon emission reductions of the same carbon account identifier within a certain time period can be accumulated and aggregated regularly to obtain the aggregated carbon emission reduction corresponding to the carbon account identifier of this time period. Optionally, the carbon emission reductions of the same institution with the same carbon account identifier within a certain time period can be accumulated and aggregated regularly to obtain the aggregated carbon emission reduction corresponding to the carbon account identifier of this institution in this time period.

[0071] An aggregated transaction is determined based on the carbon account identifier and aggregated carbon emission reductions, and the aggregated transaction is sent to the corresponding blockchain node. The aggregated transaction includes, but is not limited to, the carbon account identifier and aggregated carbon emission reductions, and may also include, for example, an organization identifier and a security verification signature. Optionally, a correspondence between the carbon account application management device and the blockchain node is pre-stored. After determining the aggregated transaction, the carbon account application management device sends the aggregated transaction to the corresponding blockchain node.

[0072] In this application, a carbon account application management device obtains low-carbon transaction data collected by each institution's carbon account application and sends the low-carbon transaction data to a transaction deduplication management device. The transaction deduplication management device then identifies duplicate accumulated transactions in the low-carbon transaction data based on the carbon account identifier, transaction information, and low-carbon behavior information contained in the low-carbon transaction data. Based on the identification results, it calculates the carbon emission reduction corresponding to the low-carbon transaction data and sends the carbon emission reduction to the carbon account application management device. This solves the problem of fragmented carbon account data, which occurs when each institution's carbon account application manages and calculates its own carbon account data. The carbon account application management device aggregates the carbon emission reduction based on the carbon account identifier to obtain an aggregated carbon emission reduction. Based on the carbon account identifier and the aggregated carbon emission reduction, it determines aggregated transactions, achieving unified management of carbon account data. Aggregated transactions are sent to the corresponding blockchain node. By combining the technical characteristics of blockchain, this enables traceability of low-carbon transaction data, providing a foundation for low-carbon transaction data auditing. This application provides a solution for interconnecting and interoperating carbon account applications across institutions and for unified management of carbon account data.

[0073] In order to ensure the security and integrity of low-carbon transaction data, in this application, the transaction deduplication management device is used to generate an asymmetric key pair based on the trusted execution environment TEE and send the public key in the asymmetric key pair to the carbon account application management device;

[0074] The carbon account application management device is configured to encrypt the low-carbon transaction data using the public key and send the obtained ciphertext data to the transaction deduplication management device;

[0075] The transaction deduplication management device is used to decrypt the ciphertext data using the private key in the asymmetric key pair to obtain the low-carbon transaction data.

[0076] The Trusted Execution Environment (TEE) is described as follows:

[0077] It refers to a secure isolation area (enclave) built on a computing platform using software and hardware methods to ensure the confidentiality and integrity of the data and code in this secure isolation area throughout its life cycle. TEE has several main interfaces:

[0078] HW.load(prog)→eid loads the code to be run in the enclave in the trusted execution environment area and returns the unique identification identifier eid, setting the private initial environment state of the enclave to 0.

[0079] HW.Run(eid,in)→(out,quote) executes the code identified by eid in the enclave according to the input value in, updates the environment state mem and returns the output value out and the verification quote. Where quote = quote HW (prog,out) is the enclave's signature on the program hash value and output value, proving that the output value is indeed the result of executing the prog code from a real TEE enclave.

[0080] HW.QuoteVerify(quote) → σ allows anyone to verify HW (σ, quote) = true. Taking SGX as an example, SGX provides a verification service that generates a signature σ based on quote. The signature is a signature of (quote||b), b∈{0,1}. When b is 1, it means that quote is authentic and valid. Therefore, anyone can verify whether quote is authentic and valid based on b in the signature.

[0081] Key features of TEE include:

[0082] Isolation: TEE provides an isolated execution environment that is separated from the operating system and other applications, preventing unauthorized access.

[0083] Secure Boot: The TEE is typically established when the device boots up to ensure its integrity and security. This typically involves hardware root keys and boot authentication.

[0084] Data protection: TEE can be used to encrypt and protect sensitive data stored in it, making it inaccessible to malicious attackers outside the device.

[0085] Remote attestation: TEE can be used to verify the identity of a device to ensure secure communication with a remote server.

[0086] Application isolation: TEE allows multiple applications to run on the same device, isolated from each other to prevent malicious applications from interfering with other applications or obtaining sensitive information.

[0087] Integrity checking: TEE can check the integrity of applications and the operating system to ensure they have not been tampered with.

[0088] Asymmetric key pairs can be randomly generated within the secure enclave. The public key can be sent externally, while the private key never leaves the enclave. Applications outside the TEE encrypt data with the public key and send it to the TEE. The private key can only be retrieved and decrypted by a specific authorized code within the enclave.

[0089] In this application, the carbon emission reduction transactions submitted by different institutions are decrypted and deduplicated based on the trusted execution environment TEE, and the carbon emission reduction amount is calculated according to the standard, and the results and signatures are returned.

[0090] The transaction deduplication management device is used to determine the hash value corresponding to the low-carbon transaction data, calculate the hash value and the summary value of the carbon emission reduction, and sign the summary value.

[0091] The carbon account application management device is used to determine transaction aggregation batches according to a preset period, determine the institutional identification carried by each low-carbon transaction data in the transaction aggregation batch; aggregate the carbon emission reductions corresponding to the same carbon account identification of the same institutional identification to obtain the aggregated carbon emission reductions.

[0092] The carbon account application management device regularly packages the N latest carbon emission reduction transactions under the name of the same institution according to a preset period to form an aggregated transaction. Aggregate the carbon emission reduction amounts corresponding to the same carbon account identifier of the same institution to obtain the aggregated carbon emission reduction amount. For example, the five transaction data under the name of the same institution that are regularly packaged are N(1): cid001,100g; N(2): cid003,400g; N(3): cid001,150g; N(4): cid003,100; N(5): cid002,90g. N(1) refers to the first of the five transaction data, cid001 refers to the carbon account identifier cid001, and 100g refers to the carbon emission reduction amount of 100g. Aggregate the carbon emission reduction amounts corresponding to the same carbon account identifier of the same institution to obtain the aggregated carbon emission reduction amount: cid001,250g; cid002,90g; cid003,500g.

[0093] The carbon account application management device is used to determine the identifiers of each carbon account in the transaction aggregation batch and the corresponding aggregated carbon emission reduction amount;

[0094] For each piece of low-carbon transaction data in the transaction aggregation batch, record the identifier of the low-carbon transaction data, determine the carbon emission reduction amount and signature corresponding to the low-carbon transaction data; use each piece of low-carbon transaction data, the carbon emission reduction amount and signature corresponding to each low-carbon transaction data as data nodes of a Merkle tree; and determine the Merkle tree root hash value based on each data node;

[0095] The aggregated transaction is determined according to the identifier of the transaction aggregation batch, the identifiers of each carbon account, the aggregated carbon emission reduction corresponding to each carbon account identifier and the Merkle tree root hash value, and the aggregated transaction is sent to the corresponding blockchain node.

[0096] The carbon account application management device block regularly packages N latest carbon emission reduction transactions under the name of the same organization to form an aggregated transaction BundledTx. The aggregated transaction contains the following content:

[0097] Where bid is the identifier of the transaction batch, cid_i is the identifier of the carbon account with a change in the i-th carbon reduction, Δer_i is the change in the i-th carbon reduction, and MRH is the Merkle tree root hash value. Generally speaking, the larger N is, the higher the compression rate and the higher the supported transactions per second.

[0098] Where MRH is the root hash value of the Merkle tree consisting of N transaction data as leaf nodes. The N leaf nodes of the Merkle tree contain the following transaction data (k=1,...N);

[0099] tx k ,er k ,Q k ; Represent the low-carbon transaction data, carbon emission reduction change and TEE signature involved in the k-th transaction respectively. Figure 2 is a schematic diagram of the Merkle tree structure provided by this application. According to the schematic diagram of the Merkle tree structure shown in Figure 2, the Merkle tree root hash value MRH can be determined. As shown in Figure 2, the data nodes include: n1 = (code1||cid1||td1||lcd1||er1||Q1), n2 = (code2||cid2||td2||lcd2||er2||Q2), ..., n N =(code N ||cid N ||td N ||lcd N ||er N ||Q N ). Leaf nodes include: h1=Hash(n1), h2=Hash(n2), ..., h N =Hash(n N ); the upper leaf nodes include Hash(h1||h2), ..., Hash(h N-1 ||h N ). The root node includes: Hash(h left ||h right ).

[0100] The Merkle tree is described as follows:

[0101] Figure 3 is a schematic diagram of the Merkle tree provided by this application. As shown in Figure 3, the Merkle tree is a tree structure that stores the hash values ​​of leaf nodes. Therefore, the combined hash of L1 and L2 can be hashed, and the same hash operation can be performed on L3 and L4. The process is then recursively applied to these hashes until only one hash value remains, which is the hash of the root node of the Merkle tree. The Merkle tree usually looks like an inverted tree structure, with the root node at the top, forking downward, and the leaf nodes at the bottom. Using the Merkle tree, it is possible to effectively verify whether a specific data item is part of the tree structure. The hash value of the root node is called the Merkle tree root hash.

[0102] For the Merkle tree, we can provide a path proof to prove that a certain data exists in the leaf node of the Merkle tree. We express this algorithm as:

[0103] MT.verify(MRH,data,authpath);

[0104] Where MRH is the root hash of the Merkle tree, data is the data of a leaf node, and authpath is the authentication path from a specific node to the root. For example, if we want to prove that L2 is in a Merkle tree with the root hash MRH, we need to provide an authentication path authpath consisting of Hash0-0 and Hash1 to verify MRH? = H(Hash1||H(Hash0-0||H(L2))).

[0105] FIG4 is a schematic diagram of the structure of the carbon account data management system provided by the present application, wherein the system further comprises: a transaction audit device 13;

[0106] The transaction audit device 13 is configured to receive and, based on the identifier of the transaction aggregation batch and the identifier of the low-carbon transaction data to be audited, obtain the low-carbon transaction data to be audited, the corresponding carbon emission reduction amount, and the first signature from the carbon account application management device;

[0107] Determine a first Merkle root hash value corresponding to the low-carbon transaction data to be audited based on a Merkle tree path proof algorithm, the low-carbon transaction data to be audited, the corresponding carbon emission reduction amount, and the first signature; obtain a second Merkle root hash value from a blockchain node corresponding to the identifier of the transaction aggregation batch, and determine a transaction data audit result based on the first Merkle root hash value and the second Merkle root hash value;

[0108] Determine the hash value corresponding to the low-carbon transaction data to be audited, calculate the hash value and the summary value of the carbon emission reduction, and sign the summary value to obtain a second signature; determine the carbon emission reduction audit result based on the second signature and the first signature.

[0109] The present application provides a selective single transaction audit method, in which the auditing agency can initiate a selective single transaction audit request to the carbon account application management device through the transaction audit device (supervision platform), and carry the identifier of the transaction aggregation batch and the identifier of the low-carbon transaction data to be audited in the request. Based on the identifier of the transaction aggregation batch and the identifier of the low-carbon transaction data to be audited, the transaction audit device obtains the low-carbon transaction data to be audited and the corresponding carbon emission reduction and the first signature from the carbon account application management device. The present application refers to the signature obtained by the transaction audit device based on the identifier of the transaction aggregation batch and the identifier of the low-carbon transaction data to be audited as the first signature.

[0110] Based on the Merkle tree path proof algorithm and the low-carbon transaction data to be audited, the corresponding carbon emission reduction amount, and the first signature, a first Merkle tree root hash value corresponding to the low-carbon transaction data to be audited is determined. It should be noted that during the audit process, the Merkle tree root hash value calculated according to the Merkle tree path proof algorithm is referred to as the first Merkle tree root hash value. The transaction audit device determines the corresponding blockchain node based on the identifier of the transaction aggregation batch, and then obtains the Merkle tree root hash value from the blockchain node corresponding to the identifier of the transaction aggregation batch. The Merkle tree root hash value obtained from the blockchain node is referred to as the second Merkle tree root hash value.

[0111] The transaction data audit result is determined based on the first Merkle root hash value and the second Merkle root hash value. If the first Merkle root hash value and the second Merkle root hash value are the same, the transaction data audit result is determined to be correct; if the first Merkle root hash value and the second Merkle root hash value are different, the transaction data audit result is determined to be incorrect.

[0112] Based on the identifier of the transaction aggregation batch and the identifier of the low-carbon transaction data to be audited, the low-carbon transaction data to be audited, the corresponding carbon emission reduction, and the first signature are obtained. Then, the hash value corresponding to the low-carbon transaction data to be audited is calculated. Then, the hash value and the summary value of the carbon emission reduction are calculated and signed to obtain a second signature. The carbon emission reduction audit result is then determined based on the second signature and the first signature. If the second signature is the same as the first signature, the carbon emission reduction audit result is determined to be correct. If the second signature is different from the first signature, the carbon emission reduction audit result is determined to be incorrect.

[0113] The blockchain node only has the Merkle root hash value (MRH) of the aggregated transaction, but not the plaintext of the relevant carbon emission reduction transaction. The auditing agency can choose to audit a single transaction index (any transaction from 1,...N) in the aggregated transaction batch BundledTx(bid) submitted by a specific institution. The regulatory platform requests the data and path proof corresponding to the bid and index from the carbon account application management device. The carbon account application management device prepares the relevant raw data and Merkle tree path proof for the transaction:

[0114] (code index ,cid index ,td index ,lcd index ,er index ,Q index )

[0115] authpath

[0116] The regulatory platform reads the MRH corresponding to the aggregated transaction from the blockchain and performs the following verification:

[0117] MT.verify(MRH,H(code index ||cid index ||td index ||lcd index ||er index ||Q index ),authpath)

[0118] &&

[0119] TEE.verifyQoute(Q index ,prog||H(tx index )||er index )

[0120] The first verification, MT.verify, proves the correctness of the transaction data, namely, that the transaction is included in the aggregated transactions on the blockchain. This is achieved by verifying that the data node corresponding to the original transaction is a leaf node in the Merkle tree. The second verification, TEE.verifyQoute, verifies the correctness of the carbon reduction calculation by verifying the TEE signature. Specifically, it verifies that er is calculated based on the correct program prog and the correct input tx. The calculation is verified by verifying the TEE signature of the actual input transaction and the carbon reduction amount.

[0121] The transaction audit device is configured to receive and, based on the identifier of the transaction aggregation batch and the identifier of the carbon account to be audited, obtain from the carbon account application management device the low-carbon transaction data of each carbon account identifier to be audited, as well as the first carbon emission reduction amount and the third signature corresponding to each low-carbon transaction data;

[0122] Determine, based on the Merkle tree path proof algorithm and the respective low-carbon transaction data and the respective corresponding first carbon emission reduction amounts and third signatures, the third Merkle tree root hash values ​​corresponding to the respective low-carbon transaction data; obtain the fourth Merkle tree root hash value from the blockchain node corresponding to the identifier of the transaction aggregation batch, and determine the transaction data audit result according to the respective third Merkle tree root hash values ​​and the fourth Merkle tree root hash value;

[0123] Determining the hash value corresponding to each of the low-carbon transaction data, calculating the digest value of each hash value and the corresponding first carbon emission reduction amount, and signing the digest value to obtain each fourth signature to be audited; determining the first audit result of the carbon emission reduction amount based on each fourth signature and each third signature;

[0124] Determine a first aggregated carbon emission reduction for each first carbon emission reduction; obtain a second aggregated carbon emission reduction corresponding to the carbon account identifier from the blockchain node corresponding to the identifier of the transaction aggregation batch; and determine a second audit result of the carbon emission reduction based on the first aggregated carbon emission reduction and the second aggregated carbon emission reduction.

[0125] The present application provides a selective single-account audit method. The auditing agency can initiate a selective single-account audit request to the carbon account application management device through the transaction audit device (regulatory platform), and the request carries the identifier of the transaction aggregation batch and the identifier of the carbon account to be audited. The transaction audit device obtains the low-carbon transaction data of each carbon account identifier to be audited and the corresponding first carbon emission reduction and third signature from the carbon account application management device. The present application refers to the signature obtained by the transaction audit device based on the identifier of the transaction aggregation batch and the identifier of the carbon account to be audited as the third signature.

[0126] Based on the Merkle tree path proof algorithm and the respective low-carbon transaction data and the respective corresponding first carbon emission reduction amount and third signature, the third Merkle tree root hash value corresponding to each of the low-carbon transaction data is determined. It should be noted that during the audit process, each Merkle tree root hash value calculated according to the Merkle tree path proof algorithm is referred to as the third Merkle tree root hash value. The transaction audit device determines the corresponding blockchain node based on the identifier of the transaction aggregation batch, and then obtains the Merkle tree root hash value from the blockchain node corresponding to the identifier of the transaction aggregation batch. The Merkle tree root hash value obtained from the blockchain node is referred to as the fourth Merkle tree root hash value.

[0127] The transaction data audit result is determined based on the fourth Merkle root hash value and each of the third Merkle root hash values. If each of the third Merkle root hash values ​​is the same as the fourth Merkle root hash value, the transaction data audit result for the carbon account is determined to be correct. If any of the third Merkle root hash values ​​is different from the fourth Merkle root hash value, the transaction data audit result for the carbon account is determined to be incorrect.

[0128] The transaction audit device obtains each low-carbon transaction data of the carbon account identification to be audited and the corresponding first carbon emission reduction and third signature based on the identification of the transaction aggregation batch and the carbon account identification to be audited, determines the hash value corresponding to each low-carbon transaction data, calculates the summary value of each hash value and the corresponding first carbon emission reduction, and signs each summary value respectively to obtain each fourth signature to be audited.

[0129] For each low-carbon transaction data to be audited, if the fourth signature and the corresponding third signature corresponding to each low-carbon transaction data are the same, then the first audit result of the carbon emission reduction of the carbon account is determined to be that the carbon emission reduction calculation is correct; otherwise, the first audit result of the carbon emission reduction of the carbon account is determined to be that the carbon emission reduction calculation is incorrect.

[0130] In addition, after obtaining the first carbon emission reduction amount corresponding to each low-carbon transaction data identified by the carbon account to be audited, the first aggregate carbon emission reduction amount of each first carbon emission reduction amount is calculated, that is, each first carbon emission reduction amount is added together to obtain the first aggregate carbon emission reduction amount. Then, based on the identifier of the transaction aggregation batch, the second aggregate carbon emission reduction amount corresponding to the carbon account identifier is obtained from the corresponding blockchain node. Based on the first aggregate carbon emission reduction amount and the second aggregate carbon emission reduction amount, the second audit result of the carbon emission reduction amount is determined. If the first aggregate carbon emission reduction amount and the second aggregate carbon emission reduction amount are the same, the second audit result of the carbon emission reduction amount of the carbon account is determined to be correct carbon emission reduction calculation; otherwise, the second audit result of the carbon emission reduction amount of the carbon account is determined to be incorrect carbon emission reduction calculation.

[0131] In addition to auditing a single transaction, regulators can also choose to audit a single changed account cid in a certain aggregated transaction BundledTx(bid) of a certain institution. i The transaction audit device (regulatory platform) requests relevant data and path proof from the corresponding carbon account application management device. The carbon account application management device can be an integrated platform device or an institutional device. The transaction audit device can be a regulatory platform device. The carbon account application management device prepares and changes all account-related transaction raw data and Merkle tree path proofs:

[0132] The regulatory platform can read the MRH of the BundledTx corresponding to the institution's bid from the blockchain node, as well as the carbon emission reduction change Δer of the corresponding account being changed. i , and perform the following verification. If the output is 1, the audit passes, otherwise the audit fails.

[0133] &&

[0134] &&

[0135] The first two verifications prove the correctness of the original transaction data and the carbon reduction calculation, respectively. The second verification verifies the correctness of the carbon reduction calculation by verifying the TEE signature, that is, the correctness of the calculation of er calculated based on the correct program prog and the correct input tx. The third verification verifies the correctness of the total carbon reduction change of the account.

[0136] The carbon account application management device is used to receive and obtain the low-carbon transaction data to be audited and the corresponding carbon emission reduction and the fifth signature based on the identifier of the transaction aggregation batch and the identifier of the low-carbon transaction data to be audited; obtain the fifth Merkle tree root hash value from the blockchain node corresponding to the identifier of the transaction aggregation batch, use the fifth Merkle tree root hash value as the public input, and use the low-carbon transaction data to be audited and the corresponding carbon emission reduction and signature as the secret input; generate an arithmetic circuit of a constraint relationship based on the public input and the secret input, and generate a proof key and a verification key based on the arithmetic circuit of the constraint relationship; generate a trusted proof based on the proof key, the public input and the secret input; send the trusted proof and the verification key to the transaction audit device; the transaction audit device is used to determine the transaction data audit result based on the verification key, the public input and the trusted proof;

[0137] The carbon account application management device is used to determine the hash value corresponding to the low-carbon transaction data to be audited, calculate the hash value and the summary value of the carbon emission reduction, and sign the summary value to obtain a sixth signature; determine the carbon emission reduction audit result based on the sixth signature and the fifth signature.

[0138] This application provides a zero-knowledge proof single transaction audit method. Zero-knowledge proof means that the prover can convince the verifier that a certain statement is correct without providing any useful information to the verifier.

[0139] Zk-snark[1]: A zero-knowledge proof algorithm system that satisfies: zero knowledge, knowledge proof, simplicity and non-interactivity. In simple terms, this algorithm allows the user to prove that his secret input witness (w) satisfies all the constraints of the arithmetic circuit C, but does not disclose any secret input except the public input (x). In simple terms, assuming the secret input is w and the public input is x, the zero-knowledge proof will prove the following constraint: R(x,w)=1. It includes the following three algorithms:

[0140] KeyGen(1 λ ,C)→(pk,vk) where λ is the security parameter, C is an arithmetic circuit representing the constraint relationship, and outputs a proving key pk (proving key) and a verification key vk (verification key).

[0141] Prove(pk,x,w)→π Input the proving key and public input x and secret input w, and the verifier can generate a non-interactive and concise proof π proving R(x,w)=1.

[0142] Verify(vk,x,π)→b inputs the verification key vk and the public input x and the proof π generated in the previous step, verifies the proof, and if the output b=1, it means that the proof passes.

[0143] Auditing agencies can initiate a zero-knowledge single-transaction audit request to the carbon account application management device through the regulatory platform, carrying the identifier of the transaction aggregation batch and the identifier of the low-carbon transaction data to be audited. Based on the identifier of the transaction aggregation batch and the identifier of the low-carbon transaction data to be audited, the carbon account application management device obtains the low-carbon transaction data to be audited, the corresponding carbon emission reduction, and the fifth signature. This application refers to the signature obtained by the carbon account application management device during the zero-knowledge audit process based on the identifier of the transaction aggregation batch and the identifier of the low-carbon transaction data to be audited as the fifth signature.

[0144] The carbon account application management device determines the corresponding blockchain node based on the identifier of the transaction aggregation batch, and then obtains the Merkle root hash value from the blockchain node corresponding to the identifier of the transaction aggregation batch. The Merkle root hash value obtained from the blockchain node is referred to as the fifth Merkle root hash value. The fifth Merkle root hash value is used as the public input x, and the low-carbon transaction data to be audited, the corresponding carbon emission reduction amount, and the signature are used as the secret input w; an arithmetic circuit C with a constraint relationship is generated based on the public input x and the secret input w. A proof key pk and a verification key vk are generated based on the arithmetic circuit C with the constraint relationship. A trusted proof π is generated based on the proof key pk, the public input x, and the secret input w. The trusted proof and the verification key are sent to the transaction audit device; the transaction audit device determines the transaction data audit result based on the verification key, the public input, and the trusted proof. That is, according to Verify(vk,x,π)→b, the verification key vk and the public input x and the proof π generated in the previous step are input to verify the proof. If the output b=1, the transaction data audit result is determined to be correct, otherwise the transaction data audit result is determined to be incorrect.

[0145] The carbon account application management device obtains the low-carbon transaction data to be audited, the corresponding carbon emission reduction, and the fifth signature based on the identifier of the transaction aggregation batch and the identifier of the low-carbon transaction data to be audited. It then calculates the hash value corresponding to the low-carbon transaction data to be audited, and then calculates the hash value and the summary value of the carbon emission reduction. The summary value is signed to obtain a sixth signature. The carbon emission reduction audit result is then determined based on the sixth signature and the fifth signature. If the sixth signature and the fifth signature are identical, the carbon emission reduction audit result is determined to be correct. If the sixth signature and the fifth signature are different, the carbon emission reduction audit result is determined to be incorrect.

[0146] The blockchain node only has the Merkle tree root MRH of the aggregated transaction, but no plaintext of the relevant carbon emission reduction transaction. The auditing agency can choose to audit a single transaction index (one of 1,...N) in the aggregated transaction BundledTx(bid) submitted by a certain agency. The carbon account application management device can prove that the transaction plaintext data has not been tampered with without disclosing the transaction plaintext data, that is, it proves the correctness of the transaction data, and that the calculation of the carbon emission reduction meets the standards, that is, it proves the correctness of the carbon emission reduction calculation. This application uses zero-knowledge proof to replace the above-mentioned original data. The carbon account application management device can use zero-knowledge proof algorithms such as zk-SNARKs or zk-STARKs to complete the following zero-knowledge proof:

[0147] x=(MRH)

[0148] w=(code index ,cid index ,tdindex ,lcd index ,er index ,Q index ,authpath)

[0149] R(x,w)=1if and only if:

[0150] MT.verify(MRH,H(code index ||cid index ||td index ||lcd index ||er index ||Q index ),authpath)

[0151] &&

[0152] TEE.verifyQoute(Q index ,prog||H(tx index )||er index )

[0153] The public data x in this zero-knowledge proof problem is the root hash value of the Merkle tree, that is, the public data on the chain; the secret input (w) includes the institution code that collects the transaction, the carbon account number changed by the transaction, the transaction financial information and green information, the carbon emission change value, the TEE signature and the Merkle tree path proof. These data are flawless; the zero-knowledge proof needs to prove two relationships: these transaction data are the leaf nodes of the Merkle tree, and the carbon emission reduction amount calculated based on the green information is correct.

[0154] Taking zk-SNARKs as an example, in the initialization phase, we can transform the above problem into an arithmetic circuit C and generate the prover key pk and the verifier key vk: KeyGen(1 λ ,C)→(pk,vk). The prover key is stored by the integration platform or institution, and the verifier key is stored by the regulatory platform. When the regulatory agency requests the regulatory platform to audit the transaction corresponding to (bid, index), the regulatory platform makes a request to the relevant integration platform or institution. The integration platform or institution uses the original transaction data and the prover key to generate a zero-knowledge proof:

[0155] Prove(pk,x,w)→π

[0156] where x=(MRH),

[0157] w=(code index ,cid index ,td index ,lcd index ,erindex ,Q index ,authpath)

[0158] The integrated service platform then returns (x,π) to the supervisory platform, which performs the following verification:

[0159] Verify(vk,x,π)→b

[0160] where x=(MRH)

[0161] If b=1, the verification succeeds; otherwise, the verification fails.

[0162] The carbon account application management device is used to receive and obtain, based on the identifier of the transaction aggregation batch and the identifier of the carbon account to be audited, each low-carbon transaction data and the corresponding second carbon emission reduction amount and the seventh signature of the carbon account to be audited; obtain the sixth Merkle tree root hash value from the blockchain node corresponding to the identifier of the transaction aggregation batch, use the sixth Merkle tree root hash value as the public input, and use the each low-carbon transaction data and the corresponding second carbon emission reduction amount and the seventh signature as the secret input; generate an arithmetic circuit of a constraint relationship based on the public input and the secret input, and generate a proof key and a verification key based on the arithmetic circuit of the constraint relationship; generate a trusted proof based on the proof key, the public input and the secret input; send the trusted proof and the verification key to the transaction audit device; the transaction audit device is used to determine the transaction data audit result based on the verification key, the public input and the trusted proof;

[0163] The carbon account application management device is used to determine the hash value corresponding to each of the low-carbon transaction data, calculate the summary value of each hash value and the corresponding second carbon emission reduction, and sign the summary value to obtain each eighth signature to be audited; determine the third audit result of the carbon emission reduction based on each eighth signature and each seventh signature; determine the third aggregated carbon emission reduction of each second carbon emission reduction; obtain the fourth aggregated carbon emission reduction corresponding to the carbon account identifier from the blockchain node corresponding to the identifier of the transaction aggregation batch; determine the fourth audit result of the carbon emission reduction based on the third aggregated carbon emission reduction and the fourth aggregated carbon emission reduction.

[0164] This application provides a zero-knowledge proof single-account audit method. The auditing agency can initiate a zero-knowledge single-account audit request to the carbon account application management device through the supervision platform, and carry the identifier of the transaction aggregation batch and the identifier of the carbon account to be audited in the request. The carbon account application management device obtains the low-carbon transaction data of the carbon account identifier to be audited and the corresponding second carbon emission reduction and seventh signature based on the identifier of the transaction aggregation batch and the identifier of the carbon account to be audited. This application refers to the signature obtained by the carbon account application management device based on the identifier of the transaction aggregation batch and the identifier of the carbon account to be audited as the seventh signature, and the obtained carbon emission reduction as the second carbon emission reduction.

[0165] The carbon account application management device determines the corresponding blockchain node according to the identifier of the transaction aggregation batch, and then obtains the Merkle root hash value from the blockchain node corresponding to the identifier of the transaction aggregation batch. The Merkle root hash value obtained from the blockchain node is called the sixth Merkle root hash value. For each low-carbon transaction data item identified by the carbon account to be audited, the sixth Merkle tree root hash value is used as the public input x, and the low-carbon transaction data item, the corresponding second carbon emission reduction amount, and the seventh signature are used as the secret input w. A constraint-based arithmetic circuit C is generated based on the public input x and the secret input w. A proof key pk and a verification key vk are generated based on the constraint-based arithmetic circuit C. A trusted proof π is generated based on the proof key pk, the public input x, and the secret input w. The trusted proof π and the verification key are sent to a transaction audit device. The transaction audit device determines the transaction data audit result for the low-carbon transaction data item based on the verification key vk, the public input x, and the trusted proof π. Specifically, the verification key vk and the public input x, along with the proof π generated in the previous step, are inputted using the command Verify(vk,x,π)→b. If the output is b=1, the transaction data audit result for the low-carbon transaction data item is determined to be correct. Otherwise, the transaction data audit result for the low-carbon transaction data item is determined to be incorrect. The transaction data audit result for the carbon account is determined based on the transaction data audit results for each low-carbon transaction data item. Specifically, if the transaction data audit results of each low-carbon transaction data are all correct, then the transaction data audit result of the carbon account is determined to be correct; otherwise, the transaction data audit result of the carbon account is determined to be incorrect.

[0166] The carbon account application management device obtains each low-carbon transaction data of the carbon account identification to be audited and the corresponding second carbon emission reduction and seventh signature based on the identification of the transaction aggregation batch and the carbon account identification to be audited, determines the hash value corresponding to each low-carbon transaction data, calculates the summary value of each hash value and the corresponding second carbon emission reduction, and signs each summary value respectively to obtain each eighth signature to be audited.

[0167] For each low-carbon transaction data to be audited, if the eighth signature and the corresponding seventh signature corresponding to each low-carbon transaction data are the same, then the third audit result of the carbon emission reduction of the carbon account is determined to be that the carbon emission reduction calculation is correct; otherwise, the third audit result of the carbon emission reduction of the carbon account is determined to be that the carbon emission reduction calculation is incorrect.

[0168] In addition, after obtaining the second carbon emission reduction corresponding to each low-carbon transaction data identified by the carbon account to be audited, the third aggregate carbon emission reduction of each second carbon emission reduction is calculated, that is, the third aggregate carbon emission reduction is added together to obtain the third aggregate carbon emission reduction. Then, based on the identifier of the transaction aggregation batch, the fourth aggregate carbon emission reduction corresponding to the carbon account identifier is obtained from the corresponding blockchain node. Based on the third aggregate carbon emission reduction and the fourth aggregate carbon emission reduction, a fourth audit result of the carbon emission reduction is determined. If the third aggregate carbon emission reduction and the fourth aggregate carbon emission reduction are the same, the fourth audit result of the carbon emission reduction of the carbon account is determined to be correctly calculated. Otherwise, the fourth audit result of the carbon emission reduction of the carbon account is determined to be incorrectly calculated.

[0169] In addition to auditing a single transaction, regulators can also use zero-knowledge auditing to audit a single changed account cid in a certain aggregated transaction BundledTx(bid). i The service platform no longer provides the plain text of the relevant transactions, but instead completes the following zero-knowledge proof based on the zk-SNARKs or zk-STARKs zero-knowledge proof algorithm:

[0170] x=(MRH)

[0171] R(x,w)=1if and only if:

[0172] &&

[0173] &&

[0174] Taking zk-SNARKs as an example, in the initialization phase, the above problem can be converted into an arithmetic circuit and the prover key pk and the verifier key vk are generated: KeyGen(1 λ ,C)→(pk,vk). The carbon account application management device stores the certifier key, and the regulatory platform stores the verification key. When the regulatory agency submits an audit request to the regulatory platform (bid,cid i ) When a corresponding transaction request is made, the regulatory platform makes a request to the relevant carbon account application management device. The carbon account application management device generates a zero-knowledge proof using the original transaction data and the proof key:

[0175] Prove(pk,x,w)→π

[0176] where x=(MRH)

[0177] The integrated service platform then returns (x,π) to the supervisory platform, which performs the following verification:

[0178] Verify(vk,x,π)→b

[0179] where x=(MRH)

[0180] If b=1, the verification succeeds; otherwise, the verification fails.

[0181] FIG5 is a schematic diagram of the carbon account data management process provided by this application, which is applied to a transaction deduplication management device and includes the following steps:

[0182] S101: Receive low-carbon transaction data sent by a carbon account application management device, wherein the low-carbon transaction data is low-carbon transaction data collected by the carbon account application acquired by the carbon account application management device for each institution's carbon account application.

[0183] S102: Obtain and determine the repeated cumulative transaction identification result of the low-carbon transaction data based on the carbon account identification, transaction information and low-carbon behavior information carried in the low-carbon transaction data, calculate the carbon emission reduction corresponding to the low-carbon transaction data based on the identification result, and send the carbon emission reduction to the carbon account application management device; enable the carbon account application management device to aggregate the carbon emission reduction according to the carbon account identification to obtain the aggregated carbon emission reduction; determine the aggregated transaction based on the carbon account identification and the aggregated carbon emission reduction, and send the aggregated transaction to the corresponding blockchain node.

[0184] The method comprises:

[0185] generating an asymmetric key pair based on a trusted execution environment (TEE), and sending the public key in the asymmetric key pair to the carbon account application management device; causing the carbon account application management device to encrypt the low-carbon transaction data using the public key, and sending the obtained ciphertext data to the transaction deduplication management device;

[0186] The ciphertext data is decrypted using the private key in the asymmetric key pair to obtain the low-carbon transaction data.

[0187] The method comprises:

[0188] If the identification result is that the low-carbon transaction data is a repeated cumulative transaction, the carbon emission reduction corresponding to the low-carbon transaction data is determined to be 0; if the identification result is that the low-carbon transaction data is not a repeated cumulative transaction, the carbon emission reduction corresponding to the low-carbon transaction data is determined according to a preset carbon emission reduction algorithm.

[0189] The method comprises:

[0190] Determine the hash value corresponding to the low-carbon transaction data, calculate the hash value and the summary value of the carbon emission reduction, and sign the summary value.

[0191] FIG6 is a schematic diagram of the carbon account data management process provided by this application, which is applied to a carbon account application management device and includes the following steps:

[0192] S201: For each institution's respective carbon account application, obtain the low-carbon transaction data collected by the carbon account application, and send the low-carbon transaction data to the transaction deduplication management device; enable the transaction deduplication management device to obtain and determine the repeated cumulative transaction identification result of the low-carbon transaction data based on the carbon account identification, transaction information and low-carbon behavior information carried in the low-carbon transaction data, calculate the carbon emission reduction corresponding to the low-carbon transaction data based on the identification result, and send the carbon emission reduction to the carbon account application management device.

[0193] S202: Aggregate the carbon emission reduction amount according to the carbon account identifier to obtain an aggregated carbon emission reduction amount; determine an aggregate transaction according to the carbon account identifier and the aggregated carbon emission reduction amount, and send the aggregate transaction to a corresponding blockchain node.

[0194] The method comprises:

[0195] Receive a public key sent by the transaction deduplication management device, wherein the transaction deduplication management device generates an asymmetric key pair based on a trusted execution environment (TEE), and sends the public key in the asymmetric key pair to the carbon account application management device;

[0196] The low-carbon transaction data is encrypted using the public key, and the obtained ciphertext data is sent to the transaction deduplication management device; the transaction deduplication management device is enabled to decrypt the ciphertext data using the private key in the asymmetric key pair to obtain the low-carbon transaction data.

[0197] The method comprises:

[0198] Determine the transaction aggregation batch according to the preset period, and determine the institutional identification carried by each low-carbon transaction data in the transaction aggregation batch; aggregate the carbon emission reductions corresponding to the same carbon account identification of the same institutional identification to obtain the aggregated carbon emission reductions.

[0199] The method comprises:

[0200] Determine the identifiers of each carbon account in the aggregated transaction batch and the aggregated carbon emission reductions corresponding to each;

[0201] For each piece of low-carbon transaction data in the transaction aggregation batch, record the identifier of the low-carbon transaction data, determine the carbon emission reduction amount and signature corresponding to the low-carbon transaction data; use each piece of low-carbon transaction data, the carbon emission reduction amount and signature corresponding to each low-carbon transaction data as data nodes of a Merkle tree; and determine the Merkle tree root hash value based on each data node;

[0202] The aggregated transaction is determined according to the identifier of the transaction aggregation batch, the identifiers of each carbon account, the aggregated carbon emission reduction corresponding to each carbon account identifier and the Merkle tree root hash value, and the aggregated transaction is sent to the corresponding blockchain node.

[0203] The method comprises:

[0204] Receive and obtain the low-carbon transaction data to be audited and the corresponding carbon emission reduction and the fifth signature based on the identifier of the transaction aggregation batch and the identifier of the low-carbon transaction data to be audited; obtain the fifth Merkle tree root hash value from the blockchain node corresponding to the identifier of the transaction aggregation batch, use the fifth Merkle tree root hash value as a public input, and use the low-carbon transaction data to be audited and the corresponding carbon emission reduction and signature as secret inputs; generate an arithmetic circuit of a constraint relationship based on the public input and the secret input, and generate a proof key and a verification key based on the arithmetic circuit of the constraint relationship; generate a trusted proof based on the proof key, the public input and the secret input; send the trusted proof and the verification key to a transaction audit device; enable the transaction audit device to determine the transaction data audit result based on the verification key, the public input and the trusted proof;

[0205] Determine the hash value corresponding to the low-carbon transaction data to be audited, calculate the hash value and the summary value of the carbon emission reduction, and sign the summary value to obtain a sixth signature; determine the carbon emission reduction audit result based on the sixth signature and the fifth signature.

[0206] The method comprises:

[0207] Receive and, based on the identifier of the transaction aggregation batch and the identifier of the carbon account to be audited, obtain each low-carbon transaction data of the carbon account identifier to be audited and the second carbon emission reduction amount and the seventh signature corresponding to each of them; obtain the sixth Merkle tree root hash value from the blockchain node corresponding to the identifier of the transaction aggregation batch, use the sixth Merkle tree root hash value as the public input, and use the each low-carbon transaction data and the second carbon emission reduction amount and the seventh signature as the secret input; generate an arithmetic circuit of a constraint relationship based on the public input and the secret input, and generate a proof key and a verification key based on the arithmetic circuit of the constraint relationship; generate a trusted proof based on the proof key, the public input and the secret input; send the trusted proof and the verification key to a transaction audit device; enable the transaction audit device to determine the transaction data audit result based on the verification key, the public input and the trusted proof;

[0208] Determine the hash value corresponding to each of the low-carbon transaction data, calculate the summary value of each hash value and the corresponding second carbon emission reduction, and sign the summary value to obtain each eighth signature to be audited; determine the third audit result of the carbon emission reduction based on each eighth signature and each seventh signature; determine the third aggregated carbon emission reduction of each second carbon emission reduction; obtain the fourth aggregated carbon emission reduction corresponding to the carbon account identifier from the blockchain node corresponding to the identifier of the transaction aggregation batch; determine the fourth audit result of the carbon emission reduction based on the third aggregated carbon emission reduction and the fourth aggregated carbon emission reduction.

[0209] FIG7 is a schematic diagram of the carbon account data management process provided by this application, which is applied to transaction audit equipment. The process includes the following steps:

[0210] S301: Receive and, based on the identifier of the transaction aggregation batch and the identifier of the low-carbon transaction data to be audited, obtain the low-carbon transaction data to be audited, the corresponding carbon emission reduction amount, and the first signature from the carbon account application management device.

[0211] S302: Based on the Merkle tree path proof algorithm and the low-carbon transaction data to be audited and the corresponding carbon emission reduction and the first signature, determine the first Merkle tree root hash value corresponding to the low-carbon transaction data to be audited; obtain the second Merkle tree root hash value from the blockchain node corresponding to the identifier of the transaction aggregation batch, and determine the transaction data audit result according to the first Merkle tree root hash value and the second Merkle tree root hash value.

[0212] S303: Determine the hash value corresponding to the low-carbon transaction data to be audited, calculate the hash value and the summary value of the carbon emission reduction, and sign the summary value to obtain a second signature; determine the carbon emission reduction audit result based on the second signature and the first signature.

[0213] The method comprises:

[0214] receiving and, based on the identifier of the transaction aggregation batch and the identifier of the carbon account to be audited, obtaining from the carbon account application management device the low-carbon transaction data of the carbon account to be audited and the first carbon emission reduction amount and the third signature corresponding to each of the low-carbon transaction data;

[0215] Determine, based on the Merkle tree path proof algorithm and the respective low-carbon transaction data and the respective corresponding first carbon emission reduction amounts and third signatures, the third Merkle tree root hash values ​​corresponding to the respective low-carbon transaction data; obtain the fourth Merkle tree root hash value from the blockchain node corresponding to the identifier of the transaction aggregation batch, and determine the transaction data audit result according to the respective third Merkle tree root hash values ​​and the fourth Merkle tree root hash value;

[0216] Determining the hash value corresponding to each of the low-carbon transaction data, calculating the digest value of each hash value and the corresponding first carbon emission reduction amount, and signing the digest value to obtain each fourth signature to be audited; determining the first audit result of the carbon emission reduction amount based on each fourth signature and each third signature;

[0217] Determine a first aggregated carbon emission reduction for each first carbon emission reduction; obtain a second aggregated carbon emission reduction corresponding to the carbon account identifier from the blockchain node corresponding to the identifier of the transaction aggregation batch; and determine a second audit result of the carbon emission reduction based on the first aggregated carbon emission reduction and the second aggregated carbon emission reduction.

[0218] The method comprises:

[0219] Receive the trusted proof and verification key sent by the carbon account application management device, and determine the transaction data audit result based on the verification key, public input and the trusted proof; wherein, the public input is the fifth Merkle tree root hash value obtained from the corresponding blockchain node according to the identifier of the transaction aggregation batch.

[0220] This application provides a carbon account data management system, method, device, equipment and medium, which implements a carbon emission reduction transaction deduplication and confirmation algorithm through confidential computing (trusted execution environment, TEE) to ensure the integrity of the algorithm and the confidentiality of transaction data, thereby solving the problems of repeated calculations and inconsistent calculation standards for individual carbon emission reduction behaviors. Through the transaction aggregation algorithm, the scalability of the system is improved and data privacy is protected. Through selective auditing and zero-knowledge auditing algorithms, regulatory agencies can conduct transaction audits. Based on blockchain technology, a cross-industry carbon account interconnection platform is realized, which has the advantages of multi-center interoperability and trustlessness.

[0221] This application uses a trusted execution environment to decrypt and deduplicate carbon reduction transactions submitted by different organizations, calculate carbon reduction amounts according to standards, and return the results and signatures. A Merkle tree-based carbon reduction transaction aggregation protocol protects privacy and improves transaction throughput. It provides selective auditing and zero-knowledge proof auditing algorithms to enable single-transaction or single-account transaction auditing. A blockchain-based interoperability protocol is designed to connect all of the above modules.

[0222] Figure 8 is a diagram of the carbon account data management system provided by this application. It illustrates the overall architecture of the blockchain-based personal carbon account interconnection platform. Within this architecture, each organization can have its own carbon account application, which collects information about low-carbon behavior and provides specific incentives (usually in the form of carbon credits, which can be redeemed for certain benefits within the organization's application). For example, organizations X, A1, A2, A3, B1, B2, and B3.

[0223] As shown in Figure 8, the carbon account application of industry participant A1, the carbon account application of industry participant A2 and the carbon account application of industry participant A3 send low-carbon transaction data to the personal carbon account integration platform of industry A (carbon account application management device). The personal carbon account integration platform of industry A sends the low-carbon transaction data to the transaction deduplication management device. The transaction deduplication management device deduplicates the low-carbon transaction data based on the trusted execution environment TEE and returns the results to the personal carbon account integration platform of industry A. The personal carbon account integration platform of industry A sends the aggregated transaction to the blockchain node of industry A.

[0224] As shown in Figure 8, the carbon account application of industry participant B1, the carbon account application of industry participant B2 and the carbon account application of industry participant B3 send low-carbon transaction data to the B industry personal carbon account integration platform (carbon account application management device). The B industry personal carbon account integration platform sends the low-carbon transaction data to the transaction deduplication management device. The transaction deduplication management device deduplicates the low-carbon transaction data based on the trusted execution environment TEE and returns the results to the B industry personal carbon account integration platform. The B industry personal carbon account integration platform sends the aggregated transaction to the B industry blockchain node.

[0225] As shown in Figure 8, the carbon account application of institution X sends low-carbon transaction data to the transaction deduplication management device. The transaction deduplication management device deduplicates the low-carbon transaction data based on the trusted execution environment TEE and returns the results to the carbon account application of institution X. The carbon account application of institution X sends the aggregated transaction to the blockchain node of institution X.

[0226] As shown in Figure 8, the regulatory platform interacts with the regulatory agency's blockchain node to audit single transactions or single account transactions in the institutional X carbon account application, the B industry personal carbon account integration platform, and the A industry personal carbon account integration platform through selective auditing or zero-knowledge auditing.

[0227] There are two different ways for institutions to connect to the blockchain:

[0228] 1. If an industry has a personal carbon account integration platform, the carbon account applications within the industry can send original transactions to the personal carbon account integration platform of the industry, and then the personal carbon account integration platform will uniformly send aggregated transactions to the blockchain node of the industry.

[0229] 2. For some larger-scale carbon accounting applications, the institution can also directly upload the aggregated transactions to the institution’s blockchain node.

[0230] Before institutions submit aggregated transactions to the blockchain, they must first encrypt the plaintext transactions and submit them to a trusted execution environment for deduplication and confirmation. Regulators can use the regulatory platform to conduct transaction or account audits. The regulatory platform can interact with industry integration platforms, institutions, and regulatory blockchain nodes to implement selective or zero-knowledge audits.

[0231] Figure 9 is a flowchart of the carbon account data management process provided by this application. In the first method of connecting an institution to the blockchain, institution A1 uploads the original transaction to Industry A's integration platform. The Industry A integration platform encrypts the original transaction and sends it to the transaction deduplication management device. The transaction deduplication management device calculates the actual carbon emission reduction based on the trusted execution environment and returns the carbon emission reduction to the Industry A integration platform. The Industry A integration platform compresses and aggregates the transactions and submits the aggregated transactions to the blockchain. The blockchain verifies the transaction and updates the smart contract status. In the second method of connecting an institution to the blockchain, institution X encrypts the original transaction and sends it to the transaction deduplication management device. The transaction deduplication management device calculates the actual carbon emission reduction based on the trusted execution environment and returns the carbon emission reduction to institution X. Institution X compresses and aggregates the transactions and submits the aggregated transactions to the blockchain. The blockchain verifies the transaction and updates the smart contract status.

[0232] Smart contracts on the blockchain mainly store the following states:

[0233] The smart contract contains the following methods:

[0234] createAccount: Register a personal carbon account. The cid can correspond to the personal ID number one-to-one. The personal account mainly stores the total amount of personal carbon emission reduction (which can be accumulated by low-carbon behavior transactions submitted by different institutions). queryAccount: Query personal carbon account information. submitBundledTx: Submit an aggregate transaction and update the corresponding carbon account carbon emission reduction balance, and store the aggregate transaction in bundledTxs. Among them, cid is the unique identification code of the batch transaction, which can be a hash value of the content or other random value. queryBundledTx: Query the aggregate transaction.

[0235] The process of transaction deduplication management device based on the trusted execution environment TEE to perform transaction deduplication is described as follows:

[0236] During the initialization phase, we call the TEE interface and load the transaction deduplication and confirmation algorithm into the enclave.

[0237] HW.load(prog)->eid,pk;

[0238] The program randomly generates a public-private key pair, which is used to encrypt data before sending it to the enclave. This ensures that the data can only be decrypted within the enclave's algorithm. Upon successful loading, the program returns the enclave's unique identifier (eid) and the data encryption public key (pk).

[0239] The organization or integration platform encrypts the carbon emission reduction transaction plaintext with the TEE public key pk and sends it to the enclave corresponding to the trusted execution environment eid. Transaction tx = (code, cid, td, lcd).

[0240] After receiving the request, TEE calls the algorithm in the enclave:

[0241] HW.Run(eid,in)→(out,Q)

[0242] in=Enc(pk,tx)

[0243] out=H(tx)||er

[0244] Q=quoteHW(prog,out)

[0245] The algorithm performs the following verification logic:

[0246] 1. tx = Dec(sk, in): Decrypt the data using the private key.

[0247] 2. Dedup(tx): Executes a deduplication algorithm based on cid, td, and lcd to determine whether this transaction is a duplicate accumulation transaction. If it is a duplicate accumulation transaction, the result is directly returned, and the carbon emission reduction is 0.

[0248] 3. Compute (tx): Calculate the correct carbon emission reduction based on the green information according to the standards.

[0249] 4. Returns the output out and signature Q. out contains the hash value of the original transaction and the actual carbon emission reduction that should be accumulated.

[0250] The process of transaction aggregation by the carbon account application management device is described as follows:

[0251] The carbon account application management device regularly packages N latest carbon emission reduction transactions under the name of the same institution to form an aggregated transaction BundledTx. The transaction contains the following content:

[0252] Where bid is the batch number, cid i is the carbon account ID of the i-th carbon emission reduction amount, Δer i is the change in carbon emission reduction for the i-th value. Generally speaking, the larger N is, the higher the compression ratio is, and the higher the supported TPS is.

[0253] FIG10 is a schematic diagram of transaction aggregation provided by this application. As shown in FIG10 , five transaction data items (N=5) under the same institution are regularly packaged, where N(1): cid001,100g; N(2): cid003,400g; N(3): cid001,150g; N(4): cid003,100; N(5): cid002,90g. N(1) refers to the first of the five transaction data items, cid001 refers to the carbon account identifier cid001, and 100g refers to the carbon emission reduction of 100g. The carbon emission reduction amounts corresponding to the same carbon account identifier of the same institution identifier are aggregated to obtain the aggregated carbon emission reduction amounts: cid001,250g; cid002,90g; cid003,500g.

[0254] Where MRH is the root hash value of the Merkle tree consisting of N transaction data as leaf nodes. The N leaf nodes of the Merkle tree contain the following transaction data (k=1,...N);

[0255] tx k ,er k ,Q k ; respectively represent the transaction text, carbon emission reduction change and TEE signature involved in the k-th transaction.

[0256] Figure 11 is a single transaction audit flow chart provided by this application. The regulatory agency randomly checks a transaction index in a certain aggregated transaction bid of a certain industry and institution; the regulatory platform requests the bid, index corresponding data and proof from the integration platform / institution; the integration platform / institution prepares the original transaction data and the Merkle tree verification path authpath; the regulatory platform obtains the MRH corresponding to the institution's packaged transaction from the blockchain node; the blockchain node returns the MRH to the regulatory platform; the regulatory platform uses the original data to calculate the leaf node data, and verifies the Merkle tree path proof to verify the carbon emission reduction calculation results.

[0257] The blockchain only has the Merkle tree root (MRH) of the aggregated transactions, but not the plaintext (table) of the relevant carbon reduction transactions. Auditing organizations can choose to audit individual transactions (indexes 1,...N) within the aggregated transaction BundledTx(bid) submitted by a specific organization. The diagram above illustrates the selective audit process. The regulatory platform requests the data (field information contained in the tree node) and proof (Merkle tree path) corresponding to the bid and index from the integration platform (A, B) or organization (X).

[0258] Figure 12 is a single-account audit flowchart provided by this application. The regulatory agency randomly checks a changed account (bid, cid) in a certain aggregate transaction of a certain institution in a certain industry; the regulatory platform requests the data and proof corresponding to bid, cid from the integration platform / institution; the integration platform / institution prepares the original transaction data and the Merkle tree verification path authpath; the regulatory platform obtains the MRH corresponding to the institution's packaged transaction and the carbon emission reduction change value of the corresponding account from the blockchain node; the blockchain node returns the MRH and carbon emission reduction change value to the regulatory platform; the regulatory platform uses the original data to calculate the leaf node data, and verifies the Merkle tree path proof, verifies the carbon emission reduction calculation result, and verifies the carbon emission reduction change value result.

[0259] In addition to auditing a single transaction, regulators can also choose to audit a single changed account cid in a certain aggregated transaction BundledTx(bid) of a bank. i The figure above illustrates this process. The regulatory platform requests relevant data and proof from the corresponding integration platform or institution. The integration service platform prepares all transaction raw data and Merkle tree path proofs related to the account change. The regulatory platform can read the MRH of the BundledTx corresponding to the institution's bid from the blockchain, as well as the carbon emission reduction change Δer corresponding to the account being changed. i , and perform the following verification. If the output is 1, the audit passes, otherwise the audit fails.

[0260] FIG13 is a schematic diagram of the structure of the carbon account data management device provided by this application, which is applied to a transaction deduplication management device. The device includes:

[0261] A first receiving module 131 is configured to receive low-carbon transaction data sent by a carbon account application management device, wherein the low-carbon transaction data is low-carbon transaction data collected by the carbon account application management device for each institution's carbon account application;

[0262] The sending module 132 is used to obtain and determine the repeated cumulative transaction identification result of the low-carbon transaction data based on the carbon account identification, transaction information and low-carbon behavior information carried in the low-carbon transaction data, calculate the carbon emission reduction corresponding to the low-carbon transaction data based on the identification result, and send the carbon emission reduction to the carbon account application management device; enable the carbon account application management device to aggregate the carbon emission reduction according to the carbon account identification to obtain the aggregated carbon emission reduction; determine the aggregated transaction based on the carbon account identification and the aggregated carbon emission reduction, and send the aggregated transaction to the corresponding blockchain node.

[0263] FIG14 is a schematic diagram of the structure of the carbon account data management device provided by this application, which is applied to a carbon account application management device. The device includes:

[0264] An acquisition module 141 is configured to acquire, for each institution's respective carbon account application, low-carbon transaction data collected by the carbon account application, and send the low-carbon transaction data to a transaction deduplication management device; cause the transaction deduplication management device to acquire and, based on the carbon account identifier, transaction information, and low-carbon behavior information carried in the low-carbon transaction data, determine a duplicate cumulative transaction identification result for the low-carbon transaction data; calculate the carbon emission reduction amount corresponding to the low-carbon transaction data based on the identification result; and send the carbon emission reduction amount to the carbon account application management device;

[0265] The first determination module 142 is used to aggregate the carbon emission reduction amount according to the carbon account identifier to obtain an aggregated carbon emission reduction amount; determine an aggregate transaction according to the carbon account identifier and the aggregated carbon emission reduction amount, and send the aggregate transaction to a corresponding blockchain node.

[0266] FIG15 is a schematic diagram of the structure of the carbon account data management device provided by this application, which is applied to transaction audit equipment. The device includes:

[0267] The second receiving module 151 is configured to receive and obtain, from the carbon account application management device, the low-carbon transaction data to be audited, the corresponding carbon emission reduction amount, and the first signature based on the identifier of the transaction aggregation batch and the identifier of the low-carbon transaction data to be audited;

[0268] A second determination module 152 is configured to determine a first Merkle root hash value corresponding to the low-carbon transaction data to be audited based on a Merkle tree path proof algorithm, the low-carbon transaction data to be audited, the corresponding carbon emission reduction amount, and the first signature; obtain a second Merkle root hash value from a blockchain node corresponding to the identifier of the transaction aggregation batch, and determine a transaction data audit result based on the first Merkle root hash value and the second Merkle root hash value;

[0269] The third determination module 153 is used to determine the hash value corresponding to the low-carbon transaction data to be audited, calculate the hash value and the summary value of the carbon emission reduction, and sign the summary value to obtain a second signature; determine the carbon emission reduction audit result based on the second signature and the first signature.

[0270] The present application also provides an electronic device, as shown in FIG16 , comprising: a processor 161 , a communication interface 162 , a memory 163 and a communication bus 164 , wherein the processor 161 , the communication interface 162 , and the memory 163 communicate with each other via the communication bus 164 ;

[0271] The memory 163 stores a computer program, and when the program is executed by the processor 161 , the processor 161 performs any of the above method steps.

[0272] The communication bus mentioned in the electronic device mentioned above may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. This communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is used in the figure, but this does not mean that there is only one bus or only one type of bus.

[0273] The communication interface 162 is used for communication between the electronic device and other devices.

[0274] The memory may include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk memory. Alternatively, the memory may be at least one storage device located away from the processor.

[0275] The above-mentioned processor can be a general-purpose processor, including a central processing unit, a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc.

[0276] The present application also provides a computer storage readable storage medium, which stores a computer program that can be executed by an electronic device. When the program runs on the electronic device, the electronic device implements any of the above method steps when executing.

[0277] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present application.

[0278] Obviously, those skilled in the art may make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application is intended to include these modifications and variations.

Claims

1. A carbon account data management system, wherein: The system includes: a carbon account application management device and a transaction deduplication management device; The carbon account application management device is used to obtain the low-carbon transaction data collected by the carbon account application of each institution, and send the low-carbon transaction data to the transaction deduplication management device; The transaction deduplication management device is configured to obtain and determine a duplicate cumulative transaction identification result of the low-carbon transaction data based on the carbon account identifier, transaction information, and low-carbon behavior information carried in the low-carbon transaction data, calculate the carbon emission reduction amount corresponding to the low-carbon transaction data based on the identification result, and send the carbon emission reduction amount to the carbon account application management device; The carbon account application management device is used to aggregate the carbon emission reduction according to the carbon account identifier to obtain an aggregated carbon emission reduction; determine an aggregate transaction according to the carbon account identifier and the aggregated carbon emission reduction, and send the aggregate transaction to a corresponding blockchain node.

2. The system of claim 1, wherein: The transaction deduplication management device is used to generate an asymmetric key pair based on the trusted execution environment TEE, and send the public key in the asymmetric key pair to the carbon account application management device; The carbon account application management device is configured to encrypt the low-carbon transaction data using the public key and send the obtained ciphertext data to the transaction deduplication management device; The transaction deduplication management device is used to decrypt the ciphertext data using the private key in the asymmetric key pair to obtain the low-carbon transaction data.

3. The system of claim 1, wherein: The transaction deduplication management device is used to determine that the carbon emission reduction corresponding to the low-carbon transaction data is 0 if the identification result is that the low-carbon transaction data is a repeated cumulative transaction; if the identification result is that the low-carbon transaction data is not a repeated cumulative transaction, determine the carbon emission reduction corresponding to the low-carbon transaction data according to a preset carbon emission reduction algorithm.

4. The system of claim 1, wherein: The transaction deduplication management device is used to determine the hash value corresponding to the low-carbon transaction data, calculate the hash value and the summary value of the carbon emission reduction, and sign the summary value.

5. The system of claim 1, wherein: The carbon account application management device is used to determine transaction aggregation batches according to a preset period, determine the institutional identification carried by each low-carbon transaction data in the transaction aggregation batch; aggregate the carbon emission reductions corresponding to the same carbon account identification of the same institutional identification to obtain the aggregated carbon emission reductions.

6. The system of claim 5, wherein: The carbon account application management device is used to determine the identifiers of each carbon account in the transaction aggregation batch and the corresponding aggregated carbon emission reduction amount; For each piece of low-carbon transaction data in the transaction aggregation batch, record the identifier of the low-carbon transaction data, and determine the carbon emission reduction amount and signature corresponding to the low-carbon transaction data; Using each piece of low-carbon transaction data, the carbon emission reduction amount corresponding to each piece of low-carbon transaction data, and the signature as a data node of the Merkle tree; determining a Merkle tree root hash value based on each data node; The aggregated transaction is determined according to the identifier of the transaction aggregation batch, the identifiers of each carbon account, the aggregated carbon emission reduction corresponding to each carbon account identifier and the Merkle tree root hash value, and the aggregated transaction is sent to the corresponding blockchain node.

7. The system of claim 6, wherein: The system further comprises: a transaction audit device; The transaction audit device is configured to receive and, based on the identifier of the transaction aggregation batch and the identifier of the low-carbon transaction data to be audited, obtain the low-carbon transaction data to be audited, the corresponding carbon emission reduction amount, and the first signature from the carbon account application management device; Determine a first Merkle root hash value corresponding to the low-carbon transaction data to be audited based on a Merkle tree path proof algorithm, the low-carbon transaction data to be audited, the corresponding carbon emission reduction amount, and the first signature; obtain a second Merkle root hash value from a blockchain node corresponding to the identifier of the transaction aggregation batch, and determine a transaction data audit result based on the first Merkle root hash value and the second Merkle root hash value; Determine the hash value corresponding to the low-carbon transaction data to be audited, calculate the hash value and the summary value of the carbon emission reduction, and sign the summary value to obtain a second signature; determine the carbon emission reduction audit result based on the second signature and the first signature.

8. The system of claim 7, wherein: The transaction audit device is configured to receive and, based on the identifier of the transaction aggregation batch and the identifier of the carbon account to be audited, obtain from the carbon account application management device the low-carbon transaction data of each carbon account identifier to be audited, as well as the first carbon emission reduction amount and the third signature corresponding to each low-carbon transaction data; Determine, based on the Merkle tree path proof algorithm and the respective low-carbon transaction data and the respective corresponding first carbon emission reduction amounts and third signatures, the third Merkle tree root hash values ​​corresponding to the respective low-carbon transaction data; obtain the fourth Merkle tree root hash value from the blockchain node corresponding to the identifier of the transaction aggregation batch, and determine the transaction data audit result according to the respective third Merkle tree root hash values ​​and the fourth Merkle tree root hash value; Determining the hash value corresponding to each of the low-carbon transaction data, calculating the digest value of each hash value and the corresponding first carbon emission reduction amount, and signing the digest value to obtain each fourth signature to be audited; determining the first audit result of the carbon emission reduction amount based on each fourth signature and each third signature; determining a first aggregated carbon emission reduction for each first carbon emission reduction; Obtain a second aggregated carbon emission reduction corresponding to the carbon account identifier from the blockchain node corresponding to the identifier of the transaction aggregation batch; determine a second audit result of the carbon emission reduction based on the first aggregated carbon emission reduction and the second aggregated carbon emission reduction.

9. The system of claim 7, wherein: The carbon account application management device is configured to receive and, based on an identifier of a transaction aggregation batch and an identifier of the low-carbon transaction data to be audited, obtain the low-carbon transaction data to be audited, the corresponding carbon emission reduction amount, and a fifth signature; obtain a fifth Merkle tree root hash value from a blockchain node corresponding to the identifier of the transaction aggregation batch, use the fifth Merkle tree root hash value as a public input, and use the low-carbon transaction data to be audited, the corresponding carbon emission reduction amount, and the signature as secret inputs; generate an arithmetic circuit of a constraint relationship based on the public input and the secret input, and generate a proof key and a verification key based on the arithmetic circuit of the constraint relationship; generating a trusted proof based on the proof key, the public input, and the secret input; sending the trustworthy certificate and the verification key to the transaction audit device; the transaction audit device is configured to determine a transaction data audit result based on the verification key, the public input, and the trustworthy certificate; The carbon account application management device is used to determine the hash value corresponding to the low-carbon transaction data to be audited, calculate the hash value and the summary value of the carbon emission reduction, and sign the summary value to obtain a sixth signature; determine the carbon emission reduction audit result based on the sixth signature and the fifth signature.

10. The system of claim 6, wherein: The carbon account application management device is used to receive and, based on the identifier of the transaction aggregation batch and the identifier of the carbon account to be audited, obtain each low-carbon transaction data of the carbon account identifier to be audited and the second carbon emission reduction amount and the seventh signature corresponding to each of them; obtain the sixth Merkle tree root hash value from the blockchain node corresponding to the identifier of the transaction aggregation batch, use the sixth Merkle tree root hash value as a public input, and use the each low-carbon transaction data and the second carbon emission reduction amount and the seventh signature as a secret input; generate an arithmetic circuit of a constraint relationship based on the public input and the secret input, and generate a proof key and a verification key based on the arithmetic circuit of the constraint relationship; generating a trusted proof based on the proof key, the public input, and the secret input; sending the trustworthy certificate and the verification key to the transaction audit device; the transaction audit device is configured to determine a transaction data audit result based on the verification key, the public input, and the trustworthy certificate; The carbon account application management device is used to determine the hash value corresponding to each of the low-carbon transaction data, calculate the summary value of each hash value and the corresponding second carbon emission reduction, and sign the summary value to obtain each eighth signature to be audited; determine the third audit result of the carbon emission reduction based on each eighth signature and each seventh signature; determine the third aggregated carbon emission reduction of each second carbon emission reduction; obtain the fourth aggregated carbon emission reduction corresponding to the carbon account identifier from the blockchain node corresponding to the identifier of the transaction aggregation batch; determine the fourth audit result of the carbon emission reduction based on the third aggregated carbon emission reduction and the fourth aggregated carbon emission reduction.

11. A carbon account data management method, wherein: Applied to a transaction deduplication management device, the method includes: Receiving low-carbon transaction data sent by the carbon account application management device, wherein the low-carbon transaction data is low-carbon transaction data collected by the carbon account application obtained by the carbon account application management device for each institution's carbon account application; Obtain and determine the repeated cumulative transaction identification result of the low-carbon transaction data based on the carbon account identification, transaction information and low-carbon behavior information carried in the low-carbon transaction data, calculate the carbon emission reduction corresponding to the low-carbon transaction data based on the identification result, and send the carbon emission reduction to the carbon account application management device; enable the carbon account application management device to aggregate the carbon emission reduction according to the carbon account identification to obtain the aggregated carbon emission reduction; determine the aggregated transaction based on the carbon account identification and the aggregated carbon emission reduction, and send the aggregated transaction to the corresponding blockchain node.

12. The method of claim 11, wherein: The method comprises: generating an asymmetric key pair based on a trusted execution environment (TEE), and sending the public key in the asymmetric key pair to the carbon account application management device; causing the carbon account application management device to encrypt the low-carbon transaction data using the public key, and sending the obtained ciphertext data to the transaction deduplication management device; The ciphertext data is decrypted using the private key in the asymmetric key pair to obtain the low-carbon transaction data.

13. The method of claim 11, wherein: The method comprises: If the identification result is that the low-carbon transaction data is a repeated cumulative transaction, the carbon emission reduction corresponding to the low-carbon transaction data is determined to be 0; if the identification result is that the low-carbon transaction data is not a repeated cumulative transaction, the carbon emission reduction corresponding to the low-carbon transaction data is determined according to a preset carbon emission reduction algorithm.

14. The method of claim 11, wherein: The method comprises: Determine the hash value corresponding to the low-carbon transaction data, calculate the hash value and the summary value of the carbon emission reduction, and sign the summary value.

15. A carbon account data management method, wherein: Applied to a carbon account application management device, the method includes: For each institution's respective carbon account application, obtain low-carbon transaction data collected by the carbon account application, and send the low-carbon transaction data to a transaction deduplication management device; cause the transaction deduplication management device to obtain and, based on the carbon account identifier, transaction information, and low-carbon behavior information carried in the low-carbon transaction data, determine a duplicate cumulative transaction identification result for the low-carbon transaction data; calculate the carbon emission reduction corresponding to the low-carbon transaction data based on the identification result; and send the carbon emission reduction amount to the carbon account application management device; The carbon emission reduction amount is aggregated according to the carbon account identifier to obtain an aggregated carbon emission reduction amount; an aggregate transaction is determined according to the carbon account identifier and the aggregated carbon emission reduction amount, and the aggregate transaction is sent to a corresponding blockchain node.

16. The method of claim 15, wherein: The method comprises: Receive a public key sent by the transaction deduplication management device, wherein the transaction deduplication management device generates an asymmetric key pair based on a trusted execution environment (TEE), and sends the public key in the asymmetric key pair to the carbon account application management device; The low-carbon transaction data is encrypted using the public key, and the obtained ciphertext data is sent to the transaction deduplication management device; the transaction deduplication management device is enabled to decrypt the ciphertext data using the private key in the asymmetric key pair to obtain the low-carbon transaction data.

17. The method of claim 15, wherein: The method comprises: Determine the transaction aggregation batch according to the preset period, and determine the institutional identification carried by each low-carbon transaction data in the transaction aggregation batch; aggregate the carbon emission reductions corresponding to the same carbon account identification of the same institutional identification to obtain the aggregated carbon emission reductions.

18. The method of claim 17, wherein: The method comprises: Determine the identifiers of each carbon account in the aggregated transaction batch and the aggregated carbon emission reductions corresponding to each; For each piece of low-carbon transaction data in the transaction aggregation batch, record the identifier of the low-carbon transaction data, determine the carbon emission reduction amount and signature corresponding to the low-carbon transaction data; use each piece of low-carbon transaction data, the carbon emission reduction amount and signature corresponding to each low-carbon transaction data as data nodes of a Merkle tree; and determine the Merkle tree root hash value based on each data node; The aggregated transaction is determined according to the identifier of the transaction aggregation batch, the identifiers of each carbon account, the aggregated carbon emission reduction corresponding to each carbon account identifier and the Merkle tree root hash value, and the aggregated transaction is sent to the corresponding blockchain node.

19. The method of claim 18, wherein: The method comprises: Receive and obtain the low-carbon transaction data to be audited and the corresponding carbon emission reduction and the fifth signature based on the identifier of the transaction aggregation batch and the identifier of the low-carbon transaction data to be audited; obtain the fifth Merkle tree root hash value from the blockchain node corresponding to the identifier of the transaction aggregation batch, use the fifth Merkle tree root hash value as a public input, and use the low-carbon transaction data to be audited and the corresponding carbon emission reduction and signature as secret inputs; generate an arithmetic circuit of a constraint relationship based on the public input and the secret input, and generate a proof key and a verification key based on the arithmetic circuit of the constraint relationship; generate a trusted proof based on the proof key, the public input and the secret input; send the trusted proof and the verification key to a transaction audit device; enable the transaction audit device to determine the transaction data audit result based on the verification key, the public input and the trusted proof; Determine the hash value corresponding to the low-carbon transaction data to be audited, calculate the hash value and the summary value of the carbon emission reduction, and sign the summary value to obtain a sixth signature; determine the carbon emission reduction audit result based on the sixth signature and the fifth signature.

20. The method of claim 18, wherein: The method comprises: Receive and, based on the identifier of the transaction aggregation batch and the identifier of the carbon account to be audited, obtain each low-carbon transaction data of the carbon account identifier to be audited and the second carbon emission reduction amount and the seventh signature corresponding to each of them; obtain the sixth Merkle tree root hash value from the blockchain node corresponding to the identifier of the transaction aggregation batch, use the sixth Merkle tree root hash value as the public input, and use the each low-carbon transaction data and the second carbon emission reduction amount and the seventh signature as the secret input; generate an arithmetic circuit of a constraint relationship based on the public input and the secret input, and generate a proof key and a verification key based on the arithmetic circuit of the constraint relationship; generate a trusted proof based on the proof key, the public input and the secret input; send the trusted proof and the verification key to a transaction audit device; enable the transaction audit device to determine the transaction data audit result based on the verification key, the public input and the trusted proof; Determine the hash value corresponding to each of the low-carbon transaction data, calculate the summary value of each hash value and the corresponding second carbon emission reduction, and sign the summary value to obtain each eighth signature to be audited; determine the third audit result of the carbon emission reduction based on each eighth signature and each seventh signature; determine the third aggregated carbon emission reduction of each second carbon emission reduction; obtain the fourth aggregated carbon emission reduction corresponding to the carbon account identifier from the blockchain node corresponding to the identifier of the transaction aggregation batch; determine the fourth audit result of the carbon emission reduction based on the third aggregated carbon emission reduction and the fourth aggregated carbon emission reduction.

21. A carbon account data management method, wherein: Applied to a transaction auditing device, the method includes: Receiving and, based on the identifier of the transaction aggregation batch and the identifier of the low-carbon transaction data to be audited, obtaining the low-carbon transaction data to be audited, the corresponding carbon emission reduction amount, and the first signature from the carbon account application management device; Determine a first Merkle root hash value corresponding to the low-carbon transaction data to be audited based on a Merkle tree path proof algorithm, the low-carbon transaction data to be audited, the corresponding carbon emission reduction amount, and the first signature; obtain a second Merkle root hash value from a blockchain node corresponding to the identifier of the transaction aggregation batch, and determine a transaction data audit result based on the first Merkle root hash value and the second Merkle root hash value; Determine the hash value corresponding to the low-carbon transaction data to be audited, calculate the hash value and the summary value of the carbon emission reduction, and sign the summary value to obtain a second signature; determine the carbon emission reduction audit result based on the second signature and the first signature.

22. The method of claim 21, wherein: The method comprises: receiving and, based on the identifier of the transaction aggregation batch and the identifier of the carbon account to be audited, obtaining from the carbon account application management device the low-carbon transaction data of the carbon account to be audited and the first carbon emission reduction amount and the third signature corresponding to each of the low-carbon transaction data; Determine, based on the Merkle tree path proof algorithm and the respective low-carbon transaction data and the respective corresponding first carbon emission reduction amounts and third signatures, the third Merkle tree root hash values ​​corresponding to the respective low-carbon transaction data; obtain the fourth Merkle tree root hash value from the blockchain node corresponding to the identifier of the transaction aggregation batch, and determine the transaction data audit result according to the respective third Merkle tree root hash values ​​and the fourth Merkle tree root hash value; Determining the hash value corresponding to each of the low-carbon transaction data, calculating the digest value of each hash value and the corresponding first carbon emission reduction amount, and signing the digest value to obtain each fourth signature to be audited; determining the first audit result of the carbon emission reduction amount based on each fourth signature and each third signature; Determine a first aggregated carbon emission reduction for each first carbon emission reduction; obtain a second aggregated carbon emission reduction corresponding to the carbon account identifier from the blockchain node corresponding to the identifier of the transaction aggregation batch; and determine a second audit result of the carbon emission reduction based on the first aggregated carbon emission reduction and the second aggregated carbon emission reduction.

23. The method of claim 21, wherein: The method comprises: Receive the trusted proof and verification key sent by the carbon account application management device, and determine the transaction data audit result based on the verification key, public input and the trusted proof; wherein, the public input is the fifth Merkle tree root hash value obtained from the corresponding blockchain node according to the identifier of the transaction aggregation batch.

24. A carbon account data management device, wherein: Applied to a transaction deduplication management device, the device comprises: a first receiving module, configured to receive low-carbon transaction data sent by a carbon account application management device, wherein the low-carbon transaction data is low-carbon transaction data collected by the carbon account application management device for each institution's carbon account application; A sending module is used to obtain and determine the repeated cumulative transaction identification result of the low-carbon transaction data based on the carbon account identification, transaction information and low-carbon behavior information carried in the low-carbon transaction data, calculate the carbon emission reduction corresponding to the low-carbon transaction data based on the identification result, and send the carbon emission reduction to the carbon account application management device; enable the carbon account application management device to aggregate the carbon emission reduction according to the carbon account identification to obtain the aggregated carbon emission reduction; determine the aggregated transaction based on the carbon account identification and the aggregated carbon emission reduction, and send the aggregated transaction to the corresponding blockchain node.

25. A carbon account data management device, wherein: Applied to carbon account application management equipment, the device includes: an acquisition module configured to acquire, for each institution's respective carbon account application, low-carbon transaction data collected by the carbon account application, and send the low-carbon transaction data to a transaction deduplication management device; enable the transaction deduplication management device to acquire and, based on the carbon account identifier, transaction information, and low-carbon behavior information carried in the low-carbon transaction data, determine a duplicate cumulative transaction identification result for the low-carbon transaction data; calculate the carbon emission reduction amount corresponding to the low-carbon transaction data based on the identification result; and send the carbon emission reduction amount to the carbon account application management device; The first determination module is used to aggregate the carbon emission reduction according to the carbon account identifier to obtain an aggregated carbon emission reduction; determine an aggregate transaction according to the carbon account identifier and the aggregated carbon emission reduction, and send the aggregate transaction to a corresponding blockchain node.

26. A carbon account data management device, wherein: Applied to transaction auditing equipment, the device comprises: a second receiving module, configured to receive and, based on the identifier of the transaction aggregation batch and the identifier of the low-carbon transaction data to be audited, obtain the low-carbon transaction data to be audited, the corresponding carbon emission reduction amount, and the first signature from the carbon account application management device; A second determination module is configured to determine a first Merkle root hash value corresponding to the low-carbon transaction data to be audited based on a Merkle tree path proof algorithm, the low-carbon transaction data to be audited, the corresponding carbon emission reduction amount, and the first signature; obtain a second Merkle root hash value from a blockchain node corresponding to the identifier of the transaction aggregation batch, and determine a transaction data audit result based on the first Merkle root hash value and the second Merkle root hash value; The third determination module is used to determine the hash value corresponding to the low-carbon transaction data to be audited, calculate the hash value and the summary value of the carbon emission reduction, and sign the summary value to obtain a second signature; determine the carbon emission reduction audit result based on the second signature and the first signature.

27. An electronic device, wherein: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; Memory for storing computer programs; A processor, when used to execute a program stored in a memory, implements the method steps described in any one of claims 11 to 14, or implements the method steps described in any one of claims 15 to 20, or implements the method steps described in any one of claims 21 to 23.

28. A computer-readable storage medium, wherein: The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the method steps described in any one of claims 11 to 14, or implements the method steps described in any one of claims 15 to 20, or implements the method steps described in any one of claims 21 to 23.

Images