Trusted event processing method and system for data exchange and tracing

By obtaining and verifying evidence storage credentials in a decentralized environment, the event transactions are constructed for evidence storage, the problem of event process separation is solved, the full verification and audit of event release, delivery and processing is realized, and credible events are improved Traceability of processing.

CN117714106BActive Publication Date: 2024-11-29PEKING UNIV
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202311585132.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-11-24
Publication Date
2024-11-29
Estimated Expiration
2043-11-24

AI Technical Summary

Technical Problem

In a decentralized environment, distributed ledger and smart contract technology are difficult to realize the full verification and audit of the event process, resulting in the separation of the event process, unable to cover the entire process of the event from release, delivery to processing, affecting the processing of trusted events Traceability.

Method used

By obtaining the evidence storage credentials between the event publishing system and the event subscription system, verifying the event transaction information, and constructing event transactions for evidence storage based on the event data proof model, generating the second evidence storage credibility to ensure the entire process of the event process. Realize verification and audit of event release, delivery and processing processes.

Benefits of technology

Through the transfer of evidence storage credentials and the data storage level, the full verification and audit of the event process is realized, the traceability of trusted event processing is improved, and the information dependence relationship between event steps is trustworthy.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117714106B_ABST
    Figure CN117714106B_ABST
Patent Text Reader

Abstract

The present application provides a trusted event processing method and system for data exchange tracing, the method comprising: obtaining an event and a first evidence credential published by an event publishing system; verifying the relevant information of the event publishing transaction according to the first evidence credential; if the relevant information of the event publishing transaction is verified, constructing an event transaction according to the event data evidence model, and storing the event transaction, generating a second evidence credential; passing the event and the second evidence credential to the event subscription system, so that the event subscription system verifies the relevant information of the event transaction according to the second evidence credential, processes the event if the relevant information of the event transaction is verified, constructs an event processing transaction according to the event data evidence model, and stores the event processing transaction. In this way, the verification and auditing of the entire process of events from publishing, transmission to processing are realized, and the traceability of trusted event processing is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of decentralized event technology, and in particular to a trusted event processing method and system for data exchange and tracing. Background Art

[0002] In distributed event mechanisms and platforms, events are persisted in the central node or cluster that serves as a broadcast medium to ensure the availability of the event mechanism. In a decentralized environment, technologies such as distributed ledgers and smart contract technologies with trusted storage capabilities can be used for event persistence, and can also provide verification capabilities based on trusted persistent data as a strong support for trust.

[0003] The complete event process mainly includes three steps: publishing, transmission and processing. However, in the decentralized event mechanism of distributed ledger and smart contract technology, each step of the event process is stored separately. The event process after persistence is fragmented and cannot cover the entire event process, which is not conducive to the verification and audit of the event process. Therefore, how to realize the verification and audit of the entire event process from publishing, transmission to processing, and improve the traceability of trusted event processing is a technical problem that needs to be solved urgently. Summary of the invention

[0004] In view of the above problems, the embodiments of the present application provide a trusted event processing method and system for data exchange tracing, so as to overcome the above problems or at least partially solve the above problems.

[0005] In a first aspect of an embodiment of the present application, a trusted event processing method for data exchange tracing is disclosed, which is applied to an event center system. The method includes:

[0006] Acquire an event published by an event publishing system and a first evidence credential, wherein the first evidence credential represents evidence certification information of an event publishing transaction;

[0007] Verifying the relevant information of the event publishing transaction according to the first stored evidence;

[0008] When the relevant information of the event publishing transaction is verified, construct an event transaction according to the event data notarization model, and notarize the event transaction, and generate a second notarization voucher, wherein the second notarization voucher represents notarization certification information of the event transaction;

[0009] The event and the second evidence credential are passed to the event subscription system, so that the event subscription system verifies the relevant information of the event transaction according to the second evidence credential; if the relevant information of the event transaction is verified, the event is processed, an event processing transaction is constructed according to the event data evidence model, and the event processing transaction is notarized.

[0010] Optionally, the method further comprises:

[0011] Get event process audit request;

[0012] According to the event subject in the event process audit request, the event process data is obtained from the distributed ledger, the distributed ledger includes: a ledger for storing event data and a ledger for deploying smart contracts, and the event process data includes: the subject of the event, event content information, event publishing transactions, and event processing transactions;

[0013] The event process data is reproduced and compared to obtain the event process audit results.

[0014] Optionally, according to the event subject in the event process audit request, an event transaction list formed by the stored event data is obtained from the account book of the stored event data;

[0015] Determine an event transaction from the event transaction list, and obtain event transaction information from the account book of the stored event data according to the event transaction ID, wherein the event transaction information includes: event subject, event content, event publishing transaction ID and event transaction ID;

[0016] According to the event publishing transaction ID, obtain the event publishing transaction from the ledger of the deployed smart contract;

[0017] According to the event transaction ID, an event processing transaction is obtained from the ledger of the deployed smart contract.

[0018] Optionally, the event publishing transaction is stored in a block, the transaction sequence in the block is a Merkle tree, the first stored evidence is a leaf node and a root of the Merkle tree, and a hash value of the event publishing transaction; and the relevant information of the event publishing transaction is verified according to the first stored evidence, including:

[0019] Determine whether a leaf node of the Merkle tree has a stored hash value, where the stored hash value is determined when the event publishing transaction is stored;

[0020] In the case where the stored hash value exists in the leaf node of the Merkle tree, reconstruct the Merkle tree according to the leaf node of the Merkle tree, and compare the root hash value of the reconstructed Merkle tree with the hash value of the event publishing transaction;

[0021] When the tree root hash value and the event publishing transaction hash value are the same, it is determined that the relevant information of the event publishing has been verified.

[0022] Optionally, the event data evidence model defines a complete event process based on the transaction data structure, and the event process includes: event subject, event content, evidence data of event release during the event process, evidence data of event transmission during the event process, and evidence data of event processing during the event process.

[0023] Optionally, the event transaction is recorded, including:

[0024] The event transaction is recorded in the event sequence in chronological order;

[0025] Constructing a data dependency relationship between the event transaction and a first execution sequence, and constructing a data dependency relationship between the event data and a second execution sequence, wherein the event series is a sequence in which the event center system stores the event transactions, the first execution sequence is a sequence in which the event publishing system stores event publishing transactions, and the second execution sequence is a sequence in which the event subscription system stores event processing transactions.

[0026] A second aspect of the embodiment of the present application discloses a trusted event processing method for data exchange tracing, which is applied to an event publishing system. The method includes:

[0027] Get execution request;

[0028] Processing the execution request and publishing events to the event center system;

[0029] An event publishing transaction is constructed according to the event data notarization model, the event publishing transaction is notarized, and a first credential is generated and sent to the event center system. The first notarization credential represents the notarization certification information of the event publishing transaction.

[0030] Optionally, the event publishing transaction is recorded, including:

[0031] Attesting the event publishing transaction in the first execution sequence according to the time sequence;

[0032] A data dependency relationship is constructed between the event publishing transaction and the event sequence, wherein the event sequence is a sequence of event transactions stored in the event center system, and the first execution sequence is a sequence of event publishing transactions stored in the event publishing system.

[0033] A third aspect of the embodiments of the present application discloses a trusted event processing method for data exchange tracing, which is applied to an event subscription system. The method includes:

[0034] Acquire the event and the second evidence credential transmitted by the event center system, where the second evidence credential represents evidence proof information of the event transaction;

[0035] Verifying relevant information of the event transaction according to the second stored evidence;

[0036] If the relevant information of the event transaction is verified, the event is processed;

[0037] An event processing transaction is constructed according to the event data notarization model, and the event processing data is notarized.

[0038] Optionally, the event processing transaction is recorded, including:

[0039] Attesting the event publishing transaction on the second execution sequence in chronological order;

[0040] A data dependency relationship is constructed between the event processing transaction and the event sequence, wherein the event sequence is a sequence of event transactions stored in the event center system, and the second execution sequence is a sequence of event processing transactions stored in the event subscription system.

[0041] A fourth aspect of the embodiments of the present application discloses a trusted event processing system for data exchange tracing, including:

[0042] An event publishing system is used to obtain and process execution requests, publish events to an event center system, construct an event publishing transaction according to an event data notarization model, notarize the event publishing transaction, generate a first voucher and send it to the event center system, wherein the first notarization voucher represents notarization certification information of the event publishing transaction;

[0043] An event center system is used to obtain an event and a first evidence credential, and verify the relevant information of the event publishing transaction according to the first evidence credential. If the relevant information of the event publishing transaction is verified, the event transaction is constructed according to the event data evidence model, and the event transaction is evidenced, and a second evidence credential is generated, and the event and the second evidence credential are transmitted to the event subscription system, wherein the second evidence credential represents the evidence certification information of the event transaction;

[0044] An event subscription system is used to obtain the event and the second evidence credential transmitted by the event center system, verify the relevant information of the event transaction based on the second evidence credential, process the event if the relevant information of the event transaction is verified, construct an event processing transaction according to the event data evidence model, and store the event processing transaction.

[0045] The embodiments of the present application include the following advantages:

[0046] In an embodiment of the present application, an event and a first evidence credential published by an event publishing system are obtained, and then the relevant information of the event publishing transaction is verified according to the first evidence credential. If the relevant information of the event publishing transaction is verified, an event transaction is constructed according to an event data evidence model, and the event transaction is evidenced, and a second evidence credential is generated. Finally, the event and the second evidence credential are passed to an event subscription system, so that the event subscription system verifies the relevant information of the event transaction according to the second evidence credential. If the relevant information of the event transaction is verified, the event is processed, an event processing transaction is constructed according to the event data evidence model, and the event processing transaction is evidenced.

[0047] Because before the event is transmitted, the relevant information of the event release transaction is verified based on the first evidence credential, and the first evidence credential is the evidence proof information of the event release transaction, the execution process of the event release can be reproduced based on the first evidence credential and the relevant information of the event release transaction stored, so as to prove the authenticity of the event. By storing the event data and generating the second evidence credential for transmission, the second evidence credential is the evidence proof information of the event transaction, so the event release and transmission process can be reproduced based on the second evidence credential and the relevant information of the event transaction stored, so as to prove the authenticity and correctness of the event. In this way, by storing the event-related information of each step of the event, and generating evidence credential (i.e., the first evidence credential and the second evidence credential) for transmission, and then establishing an association between the event-related data and the evidence data of the process at the data storage level, the credibility of the event information dependency between different event steps is guaranteed, thereby realizing the verification and audit of the entire process of the event from release, transmission to processing, and improving the traceability of trusted event processing. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments of the present application will be briefly introduced below. 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 paying any creative labor.

[0049] Figure 1 It is a flowchart of a trusted event processing method for data exchange tracing applied to an event center system provided by an embodiment of the present application;

[0050] Figure 2 It is a schematic diagram of verifying relevant information of an event publishing transaction provided by an embodiment of the present application;

[0051] Figure 3It is a schematic diagram of event data state anchoring provided by an embodiment of the present application;

[0052] Figure 4 It is a schematic diagram of verification during an event provided by an embodiment of the present application;

[0053] Figure 5 It is a schematic diagram of an event process audit provided by an embodiment of the present application;

[0054] Figure 6 is a schematic diagram of an event data storage model provided in an embodiment of the present application;

[0055] Figure 7 It is a schematic diagram of constructing transaction data to achieve state anchoring provided by an embodiment of the present application;

[0056] Figure 8 It is a flowchart of the steps of a trusted event processing method for data exchange tracing applied to an event publishing system provided by an embodiment of the present application;

[0057] Fig. 9 It is a flowchart of the steps of a trusted event processing method for data exchange tracing applied to an event subscription system provided by an embodiment of the present application;

[0058] Fig.10 It is a structural diagram of a trusted event processing system for data exchange tracing provided in an embodiment of the present application. DETAILED DESCRIPTION

[0059] In order to make the above-mentioned purposes, features and advantages of the present application more obvious and understandable, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0060] In a decentralized environment, to prove that data or processes are trustworthy, that is, in line with expectations, distributed ledger technology and smart contract technology are generally used. Providing trusted support for the entire event process is also inseparable from these two technologies. The mainstream blockchain technology in distributed ledgers is based on peer-to-peer networks, cryptography, game theory, consensus algorithms and other technologies, providing participants with write-only shared storage and consensus-based writing to ensure that written data is loss-proof, tamper-proof and trustworthy. Blockchain-based smart contract technology utilizes this shared storage. By storing the code and execution request sequence of the smart contract in the shared storage, all participating nodes construct and execute according to this unique sequence, maintaining a smart contract with a globally unique state and tracking its execution requests, it can provide trusted evidence of the process.

[0061] Therefore, in order to support the credibility of the entire event process, the event process must first be tracked and the relevant data must be stored. That is, for the event transmission step in the event process, the event information can be stored in the distributed ledger; for the three steps of event subscription, publishing and processing, the relevant logic of the event subscriber and publisher can be written as a smart contract to track and store relevant information. However, after the event process is stored by this method, although the relevant information of the entire event process can be guaranteed to be credible, it is still not credible throughout the process. Because when using the stored data to audit the event process, only one step of the event process can be audited, and the relevant information of the entire process cannot be directly obtained. For this reason, an audit mechanism for the event process is needed, so as to provide trusted credentials for subsequent steps in the event process for verification, and provide event-centric audit capabilities after the event process, so as to find all data and process information related to the event from the event.

[0062] In order to realize the event process audit function, this application proposes a trusted event processing method for data exchange traceability. The event process data is recorded. Since the recorded data of the event process is scattered in different sequences and may even be distributed in different distributed ledgers, in order to ensure the credibility of the dependency relationship between the data, a one-way one-time recorded credential is used to ensure the credibility of the event information dependency relationship across ledgers. By passing the recorded credential, and then establishing an association between the event-related data and the recorded data of the process at the data storage level, it is convenient to allow each step in the event process to verify the previous step, so as to meet the trusted step-by-step transmission; at the same time, it is also convenient to audit the entire event process according to the data association after the event process. Therefore, the verification and audit of the entire process of the event from release, transmission to processing is realized, which improves the traceability of trusted event processing.

[0063] Reference Figure 1 As shown, Figure 1This is a flowchart of a trusted event processing method for data exchange tracing applied to an event center system provided by an embodiment of the present application. Figure 1 As shown, the method may include steps S110 to S140:

[0064] Step S110: Acquire an event published by the event publishing system and a first evidence credential, wherein the first evidence credential represents evidence certification information of the event publishing transaction.

[0065] In the embodiment of the present application, the event publishing system refers to the event publisher or event publishing contract. The event publishing system will publish an event in the process of processing the execution request, and then store the relevant information of the event release in the form of a transaction (event transaction), and generate a first evidence certificate and send it to the event center system. The first evidence certificate refers to the event transaction formed by the event release, which represents the evidence certification information of the event release transaction, and is used to synchronize the state of the evidence data formed by the event release step to the sequence or account book where the evidence data of the event transmission step is located, so as to ensure the credibility of the event information dependency relationship between different event steps.

[0066] The event center system refers to the event center, which is a broadcast medium that can store and transmit events published by the event publishing system. After the event publishing system publishes an event, the event center system obtains the event, and in order to determine the authenticity and correctness of the event, it also obtains the first evidence credential, so that the relevant information of the event publishing transaction can be verified based on the first evidence credential.

[0067] Step S120: Verify the relevant information of the event publishing transaction according to the first evidence credential.

[0068] In the embodiment of the present application, the first evidence credential is a set of cryptographic proofs that can prove the existence of event publishing and the event status, as well as locked, so that the transferred or synchronized party (event center system) can verify the correctness and authenticity of the event publishing transaction without the need for additional data or requesting very little data from the event publishing system. Specifically, based on the first evidence credential and the relevant information of the event publishing transaction stored, the execution process of the event publishing can be reproduced, thereby proving the correctness and authenticity of the event.

[0069] In an optional embodiment, the event publishing transaction is stored in the block, the transaction sequence in the block is a Merkle tree, and the first evidence is the leaf nodes and root of the Merkle tree, as well as the hash value of the event publishing transaction.

[0070] The Merkle tree is a binary tree composed of hash values. The leaf nodes of the Merkle tree are the hash values ​​of the transaction information, that is, the block ID, and the non-leaf nodes are the hash values ​​of the values ​​of their child nodes. For the Merkle tree, any change in a leaf node will lead to a huge change in the value from the root node to the leaf node, so it can be used to verify whether the event publishing transaction is in the transaction sequence without the need for any other transaction content.

[0071] Further, the relevant information of the event publishing transaction is verified according to the first evidence credential, including steps A1 to A3:

[0072] Step A1: Determine whether a leaf node of the Merkle tree has a stored hash value, where the stored hash value is determined when the event publishing transaction is stored.

[0073] Step A2: When the stored hash value exists in the leaf node of the Merkle tree, the Merkle tree is reconstructed according to the leaf node of the Merkle tree, and the root hash value of the reconstructed Merkle tree is compared with the hash value of the event publishing transaction.

[0074] Step A3: When the tree root hash value and the event publishing transaction hash value are the same, it is determined that the relevant information of the event publishing has been verified.

[0075] In the present application embodiment, Figure 2 As shown, the relevant information of the event release transaction is stored in the block, and the transaction sequence in the block is composed of a Merkle tree. The leaf nodes and the root of the Merkle tree, as well as the hash value of the event release transaction, are used as the first evidence to verify the authenticity of the event release transaction and the correctness of the event release transaction evidence data. Among them, the block ID list is used to indicate the workload consumed in reaching a consensus, and can be used to request data from the ledger for further verification.

[0076] When verifying the relevant information of the event publishing transaction, first execute step A1 to determine whether there is a stored hash value in the leaf node of the Merkle tree, where the stored hash value is the ID of the event publishing transaction, so the stored hash value is determined when the event publishing transaction is stored. Specifically, compare the stored hash value (the ID of the event publishing transaction) with the leaf node of the Merkle tree (i.e., the block ID). If there is a block ID that is the same as the ID of the event publishing transaction, it means whether there is a stored hash value in the leaf node of the Merkle tree, which further indicates the correctness of the event publishing. Then execute steps A2 and A3 to reconstruct the Merkle tree, and compare the root hash value of the reconstructed Merkle tree with the hash value of the event publishing transaction to verify the authenticity of the event publishing.

[0077] Step S130: When the relevant information of the event publishing transaction is verified, the event transaction is constructed according to the event data notarization model, and the event transaction is notarized, and a second notarization credential is generated, wherein the second notarization credential represents the notarization certification information of the event transaction.

[0078] In the embodiment of the present application, in order to facilitate the subsequent full audit of the complete event process, the event center system stores the event data reliably after receiving the published event. The event data evidence model is defined based on the transaction data structure. The event data evidence model can describe the evidence data of event-related information and its associated information, and then use the event data evidence model to guide the evidence of event process related information.

[0079] Specifically, the event data is constructed and stored according to the event data storage model, where the event data is data in the form of transactions. In addition, in order to synchronize the state of the stored data formed in the event transmission step to the sequence or account book where the stored data in the subsequent event processing step is located, so as to ensure the credibility of the event information dependency relationship between different event steps, after the event center system completes the event data storage, a second storage voucher is generated. The second voucher refers to the transaction that stores the event data.

[0080] In an optional embodiment, storing the event data includes: writing the event data to the local storage of the event center system for storage, or writing the event data to a distributed ledger node for storage.

[0081] In the embodiment of the present application, the event center system can store event data in a variety of ways. The event center system can provide support for different distributed ledgers, and then write the event data to the nodes distributed in the ledgers for storage; at the same time, the event center system itself has a cache function, and then the event data can be written to the local storage of the event center system for storage. In the specific implementation, the event center system gives priority to storing event data in the nodes of the distributed ledger. When the distributed ledger is not available, consider writing the event data to the local storage of the event center system for storage.

[0082] Step S140: pass the event and the second evidence credential to the event subscription system, so that the event subscription system verifies the relevant information of the event transaction according to the second evidence credential, and if the relevant information of the event transaction is verified, processes the event, constructs an event processing transaction according to the event data evidence model, and stores the event processing transaction.

[0083] In the embodiment of the present application, the event subscription system refers to the event subscriber or event subscription contract. After the event center system completes the event data evidence storage, it transmits the event to the event subscription system to trigger the event subscription system to process the event. The event subscription system also transmits the second evidence credential to the event subscription system so that the event subscription system can verify the relevant information of the event transaction according to the second evidence credential before processing the event to ensure the authenticity and correctness of the event.

[0084] Then, through the above steps S110 to S140, the event-related information of each step of the event is stored, and a storage voucher (i.e., the first storage voucher and the second storage voucher) is generated for transmission, and then an association is established between the event-related data and the storage data of the process at the data storage level, ensuring the credibility of the event information dependency relationship between different event steps, that is, anchoring the event data state. Therefore, the verification and audit of the entire event process from release, transmission to processing is realized, and the traceability of trusted event processing is improved.

[0085] Specifically, taking the example of storing data in the blockchain, the process of anchoring the event data state (i.e., the trustworthiness of the event information dependency relationship between different event steps) is explained. Figure 3It is a schematic diagram of an event data state anchoring provided by an embodiment of the present application. Specifically, the blockchain above is a trusted storage formed by a ledger with a smart contract deployed, and the blockchain below is a trusted storage formed by a ledger in which the event center stores event data. From left to right is the order of block creation. The transaction data formed by the three steps of the event process has been stored in two blockchains. When the event publishing system publishes an event in the process of processing an execution request, it is then passed to the event center system; and the event transaction formed by this execution request is provided to the event center system as the first evidence credential through the smart contract chain. After that, the event center system, based on the event data evidence model, constructs an event transaction and stores evidence using the transaction data and event data formed by the execution request when verifying that the event is true and correct. Similarly, the event center system provides the transaction with the event data stored as the second evidence credential to the smart contract chain, so that the event subscription system can verify the relevant information of the event transaction based on the second evidence credential when processing the event, and then process the event.

[0086] In an embodiment of the present application, a complete event process is expressed and notarized as three transactions, and the dependency relationship between the steps of the event process is also expressed and saved using state anchoring. This data structure can then be used to verify each step in the event process. The verification in the event process mainly occurs in the last two steps of the decentralized event process: the event center system needs to confirm whether the event is an event that is actually released by the event publishing system (i.e., step S120 verifies the relevant information of the event publishing transaction based on the first notarized credential), and the event subscription system also needs to confirm whether the event comes from the real event publishing system and whether the received event has been intercepted or tampered with (i.e., step S140 the event subscription system verifies the relevant information of the event transaction based on the second notarized credential).

[0087] Figure 4 This is a schematic diagram of verification in an event process provided by an embodiment of the present application. It can be seen that after the event publishing system completes the event publishing transaction evidence, it provides the first evidence credential to the event center information. After receiving the event, the event center system verifies the relevant information of the event publishing transaction according to the first evidence credential to determine the authenticity of the event. After completing the event transaction evidence, the event center system passes the event to the event subscription system and provides the second evidence credential to the event subscription system. Then, before processing the event, the event subscription system verifies the authenticity and correctness of the event according to the second evidence credential.

[0088] In an optional embodiment, in order to support trustworthiness, after the event process, it is usually necessary to retrieve all relevant data of the event process, reproduce and compare, so as to check whether the event process is consistent with the expectations of the event publishing system and the event subscription system. Specifically, the event process audit includes steps B1 to B3:

[0089] Step B1: Obtain an event process audit request.

[0090] Step B2: According to the event subject in the event process audit request, the event process data is obtained from the distributed ledger, the distributed ledger includes: a ledger for storing event data and a ledger for deploying smart contracts, and the event process data includes: the subject of the event, event content information, event publishing transactions and event processing transactions.

[0091] Step B3: Reproduce and compare the event process data to obtain the event process audit results.

[0092] In the embodiment of the present application, based on the evidence data stored in each step of the event process, starting from the event, the evidence data is retrieved to obtain all relevant data of the event process, and then the audit of the event process is completed based on the event process data. Among them, the event process audit request is a request initiated for the subject to be audited, and the event process audit request is sent to the event center system by forwarding to trigger the event center system to audit the entire process of the event. In other words, as long as the event center system obtains the event process audit request, it will trigger the execution of step B2 to retrieve the event process data from the distributed ledger.

[0093] Specifically, Figure 5 As shown, according to the event subject in the event process audit request, the event process data is obtained from the distributed ledger, including: according to the event subject in the event process audit request, an event transaction list formed by the evidence event data is obtained from the ledger of the evidence event data; an event transaction is determined from the event transaction list, and event transaction information is obtained from the ledger of the evidence event data according to the ID of the event transaction, and the event transaction information includes: event subject, event content, event publishing transaction ID and event transaction ID; according to the event publishing transaction ID, an event publishing transaction is obtained from the ledger of the deployed smart contract; according to the event transaction ID, an event processing transaction is obtained from the ledger of the deployed smart contract.

[0094] In this way, all the related transactions obtained by storing the event process data related to the event are retrieved, and then the event center system executes step B3 to reproduce and compare the event process data to check whether the event process is correct and complete the audit of the event process.

[0095] In an optional embodiment, the event data evidence model defines a complete event process based on the transaction data structure, and the event process includes: event subject, event content, evidence data of event release during the event process, evidence data of event transmission during the event process, and evidence data of event processing during the event process.

[0096] The event data notarization model is defined based on the transaction data structure, specifically:

[0097] (1) Define the form of the transaction.

[0098] The basic data structure of a distributed ledger is a transaction, which mainly expresses the transfer of funds or information from one account to another, and can be represented as a triple:

[0099] Transaction= F ,U T ,D>

[0100] Among them, U F Is the initiator of the transaction (From), U T It is the recipient of the transaction (To), and D is the currency or information (Data) transferred from the initiator of the transaction to the recipient of the transaction.

[0101] In the blockchain, an account can be a user account directly controlled by the user, or a contract account controlled by the smart contract code, that is:

[0102] Account U =<Addr,B> ∈A U

[0103] Account C =<Addr,B,Code,S> ∈A C

[0104] Among them, Account U Is the user account, Account C A is the contract account, Addr is the account ID (also called account address in some blockchains, generally the public key in the user account key pair), B is the currency balance held by the account (Balance), Code is the code that controls the account (Code), and S is the current state of the contract (State). U Represents the set of all user accounts, A C Represents the set of all contract accounts. It can be concluded that:

[0105]

[0106] ​The smart contract code in the contract account is similar to the class in object-oriented programming, so there are:

[0107] Code=<V,F>

[0108] Among them, Code defines a set of variables V= <v 1 ,v 2 ,…,v n > and a set of methods F = {f 1 ,f 2 ,…,f m}. After the contract code is deployed, these variables are created and assigned values ​​in a dedicated storage space, and then changed when the method is called, corresponding to the instantiation process in object-oriented programming.

[0109] For example, Indicates v i The set of all possible values, 1≤i≤n, let:

[0110]

[0111] Then we have: i : Among them, P i is the method f i The set of all possible values ​​for the parameter. And That is, the state of a contract account is a possible set of values ​​for all variables in the contract. Blockchain-based smart contract technology generally does not allow a contract account to actively initiate an execution request to another contract account, so:

[0112] U F ∈A U ,U T ∈A U ∪A C

[0113] Considering the incentive mechanism and computing resource billing, contract execution generally consumes a certain amount of currency, so the user account also needs to pay when initiating a contract execution request. Therefore, D can also be expressed as:

[0114]

[0115] Among them, val is the amount of currency transferred in this transaction, I is the additional additional information in the transaction, It's U T A method in the code, yes A set of possible values ​​for a parameter.

[0116] (2) Define the event data notarization model based on the transaction data structure:

[0117] In actual storage, the main data structure of the transaction is shown in Table 1.

[0118] Table 1 Main transaction data structure

[0119]

[0120] Among them, Hash and BlockHash are implicit values ​​of the transaction data structure. They are not directly stored in the transaction data structure, but are used as keys in storage to index transaction data and block data. Transaction data and block data can be placed in the request to express the context of the transaction, facilitate positioning, and provide correctness proof for subsequent transactions.

[0121] It can be seen that the semantics expressed by the transaction data structure revolves around the initiator passing the message to the receiver, and also implies the context information of this process. Therefore, in the process of storing relevant information of the event process, it is also necessary to encapsulate the evidence data into a similar structure. Furthermore, the event data evidence model can be expressed as:

[0122] EventProcedure= <e=<Topic,Content> ,T P ,T D ,T H >

[0123] Among them, Topic is the event subject, Content is the event content, T P Represents an event publishing transaction, which refers to the evidence data released during the event process. D Represents event transaction, which refers to the evidence data transmitted during the event process. H Represents an event processing transaction, which refers to the evidence data of event processing during the event process.

[0124] T P It can be expressed as:

[0125]

[0126] Among them, val P is the amount of currency transferred in this transaction, and The contract accounts are A method in the code and a possible value for the method's parameters.

[0127] T D It can be expressed as:

[0128] T D =<0,0,D=<0,e>>

[0129] Where, e =<Topic,Content> is an event in the event process. D It is to record the event itself. The transaction is only for recording the event. Therefore, the initiator, recipient and amount of currency transferred of the transaction are meaningless.

[0130] T H It can be expressed as:

[0131]

[0132] in, Indicates the contract account The method for handling events with the Topic as the subject that has been registered in the code must take e as a parameter.

[0133] In the embodiment of the present application, the relevant information of the event process is recorded at each step (publishing, transmitting and processing) of the event based on the event data recording model, and then the event-related data and the recorded data of the process are associated at the data storage level, which ensures the credibility of the event information dependency between different event steps, that is, anchoring the event data state. At the storage level, the correlation of each step in the event process is represented by an ordered pair.

[0134] In an optional embodiment, the event transaction is recorded, including: recording the event transaction on an event sequence in chronological order; building a data dependency relationship between the event transaction and a first execution sequence, and building a data dependency relationship between the event data and a second execution sequence, wherein the event series is a sequence in which the event center system records the event transactions, the first execution sequence is a sequence in which the event publishing system records event publishing transactions, and the second execution sequence is a sequence in which the event subscription system records event processing transactions.

[0135] In the embodiment of the present application, when the event center system stores evidence, the event transaction is stored in the event sequence according to the time sequence; when the event publishing system stores evidence, the event publishing transaction is stored in the first execution sequence according to the time sequence; when the event subscription system stores evidence, the event processing transaction is stored in the second execution sequence according to the time sequence. Specifically, according to the formal definition of event process data, the following can be obtained: Figure 6 The schematic diagram of the event data storage model is shown. For ease of understanding, Figure 6 The block structure has been ignored. Although the smart contracts of the event publishing system and the event subscription system are deployed in the same ledger, because they communicate indirectly through the event mechanism, the execution requests of the two are still separate. Figure 6The execution requests of the event publishing system and the event subscription system respectively form two execution sequences (a first execution sequence and a second execution sequence), and the execution request processed later depends on the execution request processed earlier.

[0136] The event center system also forms an event sequence for the storage of event data, which is composed of different events under the same topic. The later-published event chain is linked to the earlier-published event, indicating the chain structure formed indirectly by blocks between transactions in the distributed ledger storage. Events are published by the event publishing system during execution, so events depend on the execution request of the event publishing system; at the same time, the event processing process is triggered after the event is passed to the event subscription system, which means that the execution request of event processing depends on the event. Figure 6 The two dotted arrows in the figure represent these two dependencies. In this way, at the storage level, the event sequence and the contract execution sequence are associated, forming a directed acyclic graph structure, which strengthens the tamper-proof nature of the stored data and is conducive to the trusted support of the entire event process.

[0137] Furthermore, taking the event publishing system A, event subscription system B and event center system of event T as examples, how to construct transaction data to achieve state anchoring in the actual evidence storage process is explained. Figure 7 As shown in the figure, both event publishing system A and event subscription system B are smart contracts, which are deployed in the distributed ledger and maintained and executed by the blockchain system. During the deployment process of the contract, the constructor is called to construct and assign values ​​to member variables to create the initial state of the contract. The account ID of event publishing system A is 0x0002, and when its ping method is called, it will publish an event with the subject T. The account ID of event publishing system B is 0x0003, which subscribes to event subject T during construction and uses the handler method to process the event when it is received. The cluster where the event center system with subject T is located acts as a broadcast medium in the transmission process of events with subject T. Event publishing system A and event subscription system B have been constructed, and event subscription system B has subscribed to event subject T from the event center system. The event center system has saved relevant subscription information: event subscription system and event processing method of event subscription system.

[0138] At this time, account 0x0001 submitted a transaction requesting the execution of the ping method of contract 0x0002 (contract A's ID) with a parameter of 1. Event publishing system A then published event e. During this event, the newly generated data and its associated relationships are as follows Figure 7As shown. The contract execution process initiated by 0x0001 has been tracked by the ledger and stored as transaction hash1. The contract execution process can be easily reproduced through transaction hash1 and the previously executed execution request stored in the blockchain to prove that this transaction has published an event and obtained the content of the published event.

[0139] After event e is published, it first reaches the event center system through the transmission process, and then is stored by the event center system. Because this event is published during the execution of transaction hash1, the transmission of the event can be regarded as publishing an event to the event center system related to topic T during the execution of transaction hash1, which conforms to the expression mode of the event data storage model, so it can be constructed as transaction hash2, which directly means that transaction hash1 publishes an event e to event topic T. Transaction hash2 is the storage of event information by the event center system. Combined with transaction hash1, the complete event publishing and transmission process can be obtained, and it can be verified whether the event published by event publishing system A has been tampered with during the transmission process.

[0140] Then, event e is passed to event subscription system B, triggering the event processing steps in the event process. According to the subscription information, event subscription system B will use the handler method to process event e. However, most blockchains that support smart contracts do not support execution requests initiated by contract accounts to contract accounts, unless the execution request is triggered by another user account to the contract account. Therefore, the event proxy subcomponent in the event delivery component will actually initiate the contract execution request. The event processing step can be understood as the evidence of transaction hash2 triggering the handler method of event subscription system B. In line with the expression mode of the event data evidence model, it can be constructed as transaction hash3, which directly means that transaction hash2 requests to execute the handler method of contract 0x0003 (ID of event subscription system B), with the parameter being event e. Transaction hash3 evidences the relevant information of the event processing steps. Combined with transaction hash2, the complete event processing process can be obtained, verifying whether the event has been tampered with during the process of the event center system passing it to the event subscription system, and reproducing the execution process of handler(e) to verify the correctness of the execution result.

[0141] In this way, the relevant information in the three steps of the entire event process is stored. The three transactions contain most of the relevant information in the three steps. Through contract execution reproduction and comparison with the stored data, it is possible to verify whether the event process meets expectations, that is, to prove its credibility. The transactions formed by the two steps of event transmission and event processing contain relevant information of the previous transaction, anchoring the state, which helps the reliable transmission of the event process and facilitates the retrieval of related data to support the audit of the entire event process.

[0142] In the above example, the transaction initiator and receiver fields are filled with the transaction ID and event subject string, which is not allowed in some strictly restricted distributed ledgers. In this case, the event center can be used to create corresponding accounts in the ledger to circumvent this restriction. Specifically, after receiving the event, the event center system first stores the relevant data of the transaction in the event publishing process as a transaction sent from the event subject account to a new account (the content is the relevant trusted credentials, such as the transaction ID, the ID of the block where the exchange is located, etc.), and then stores the event data itself as a transaction sent from the new account to the event subject account. The position of the two transactions in the ledger can be used to express the dependency relationship. When the event is passed to the event subscription system to trigger the event processing step, it can also be processed in a similar way, except that it is handed over to the event proxy subcomponent on the node that directly interacts with the contract. This approach also meets the requirements of side chain technology and state anchoring.

[0143] There is a dependency that is not expressed in the event data storage model, that is, the dependency of the event processing step on the event subscription step, because only when the event subscription system subscribes to the topic first, the event center system will pass the event to the event subscription system after receiving the event. However, in the event mechanism, event publishing, transmission and processing are a complete event process, and the dependency between the three is more important than the dependency of event processing on event subscription. Moreover, in the application embodiment, event subscription is regarded as an event publishing process without subscribers, and relevant information can be stored independently, and the dependency is reflected by the time sequence relationship between the two process storage data (the dependency between blocks in the account book also reflects the time sequence), so it is not expressed in the model.

[0144] In summary, in the embodiment of the present application, since the relevant information of the event release transaction is verified based on the first evidence credential before the event is transmitted, the first evidence credential is the evidence proof information of the event release transaction, so the execution process of the event release can be reproduced based on the first evidence credential and the relevant information of the event release transaction stored, so as to prove the authenticity of the event. By storing the event data and generating the second evidence credential for transmission, the second evidence credential is the evidence proof information of the event transaction, so the event release and transmission process can be reproduced based on the second evidence credential and the relevant information of the event transaction stored, so as to prove the authenticity and correctness of the event. In this way, by storing the event-related information of each step of the event, and generating evidence credential (i.e., the first evidence credential and the second evidence credential) for transmission, and then establishing an association between the event-related data and the evidence data of the process at the data storage level, the credibility of the event information dependency between different event steps is guaranteed, thereby realizing the verification and audit of the entire process of the event from release, transmission to processing, and improving the traceability of trusted event processing.

[0145] Reference Figure 8 As shown, Figure 8 This is a flowchart of a trusted event processing method for data exchange tracing applied to an event publishing system provided by an embodiment of the present application. Figure 8 As shown, the method may include steps S810 to S830:

[0146] Step S810: Get an execution request.

[0147] Step S820: Process the execution request and publish an event to the event center system.

[0148] Step S830: construct an event publishing transaction according to the event data notarization model, notarize the event publishing transaction, and generate a first credential to send to the event center system, where the first notarization credential represents the notarization certification information of the event publishing transaction.

[0149] In the embodiment of the present application, the event publishing system refers to the event publisher or event publishing contract. The event publishing system will publish an event in the process of processing the execution request, and then store the relevant information of the event release in the form of a transaction (event transaction), and generate a first evidence certificate and send it to the event center system. The first evidence certificate refers to the event transaction formed by the event release, which represents the evidence certification information of the event release transaction, and is used to synchronize the state of the evidence data formed by the event release step to the sequence or account book where the evidence data of the event transmission step is located, so as to ensure the credibility of the event information dependency relationship between different event steps.

[0150] In an optional embodiment, the event publishing transaction is recorded, including: recording the event publishing transaction on a first execution sequence in chronological order; and constructing a data dependency relationship between the event publishing transaction and an event sequence, wherein the event sequence is a sequence of event transactions recorded by the event center system, and the first execution sequence is a sequence of event publishing transactions recorded by the event publishing system.

[0151] In an embodiment of the present application, when notarizing a data publishing transaction, in order to establish an association between event-related data and the notarized data of the process at the data storage level, so as to ensure the credibility of the event information dependency relationship between different event steps, an ordered sequence is used to notarize the event publishing transaction.

[0152] Reference Fig. 9 As shown, Fig. 9 This is a flowchart of a trusted event processing method for data exchange tracing applied to an event subscription system provided by an embodiment of the present application. Fig. 9 As shown, the method may include steps S910 to S940:

[0153] Step S910: Acquire the event and the second evidence credential transmitted by the event center system, where the second evidence credential represents the evidence proof information of the event transaction.

[0154] Step S920: Verify the relevant information of the event transaction according to the second evidence credential.

[0155] Step S930: When the relevant information of the event transaction is verified, the event is processed.

[0156] Step S940: Construct an event processing transaction according to the event data notarization model, and notarize the event processing data.

[0157] In the embodiment of the present application, the event subscription system refers to the event subscriber or event subscription contract. After the event center system completes the event data evidence storage, it transmits the event to the event subscription system to trigger the event subscription system to process the event. The event subscription system also transmits the second evidence credential to the event subscription system so that the event subscription system can verify the relevant information of the event transaction according to the second evidence credential before processing the event to ensure the authenticity and correctness of the event.

[0158] In an optional embodiment, the event processing transaction is recorded, including: recording the event publishing transaction on a second execution sequence in chronological order; and constructing a data dependency relationship between the event processing transaction and the event sequence, wherein the event sequence is a sequence of event transactions recorded by the event center system, and the second execution sequence is a sequence of event processing transactions recorded by the event subscription system.

[0159] In an embodiment of the present application, when notarizing a data processing transaction, in order to establish an association between event-related data and the notarized data of the process at the data storage level to ensure the credibility of the event information dependency relationship between different event steps, an ordered sequence is used to notarize the event publishing transaction.

[0160] Reference Fig.10 As shown, Fig.10 Schematic diagram of a trusted event processing system for data exchange tracing provided by an embodiment of the present application. Fig.10 As shown, the system includes:

[0161] An event publishing system is used to obtain and process execution requests, publish events to an event center system, construct an event publishing transaction according to an event data notarization model, notarize the event publishing transaction, generate a first voucher and send it to the event center system, wherein the first notarization voucher represents notarization certification information of the event publishing transaction;

[0162] An event center system is used to obtain an event and a first evidence credential, and verify the relevant information of the event publishing transaction according to the first evidence credential. If the relevant information of the event publishing transaction is verified, the event transaction is constructed according to the event data evidence model, and the event transaction is evidenced, and a second evidence credential is generated, and the event and the second evidence credential are transmitted to the event subscription system, wherein the second evidence credential represents the evidence certification information of the event transaction;

[0163] An event subscription system is used to obtain the event and the second evidence credential transmitted by the event center system, verify the relevant information of the event transaction based on the second evidence credential, process the event if the relevant information of the event transaction is verified, construct an event processing transaction according to the event data evidence model, and store the event processing transaction.

[0164] In the embodiment of the present application, the evidence of relevant information in the three steps of the event process is realized through the event publishing system, the event center system and the event subscription system. The three transactions (event publishing transaction, event transaction and event processing transaction) contain most of the relevant information of the three steps, and then through the contract execution reproduction and comparison with the evidence data, it can be verified whether the event process meets expectations, that is, it is proved to be credible. The transactions formed by the two steps of event transmission and event processing contain relevant information of the previous transaction, anchoring the state, which is conducive to the reliable transmission of the event process, and also facilitates the retrieval of related data to support the audit of the entire event process.

[0165] Furthermore, the event center system includes: an event transmission component and an event process audit component, and a distributed ledger service. The event process audit component includes: a proof sub-component, an audit sub-component, and a ledger reading and writing sub-component.

[0166] In the embodiment of the present application, a distributed ledger for deploying smart contracts and a distributed ledger for storing event data can be deployed in the same cluster at the same time. Both the event publishing system and the event subscription system are smart contracts deployed in the blockchain system. The event publishing system and the event subscription system use the basic event service provided by the event delivery component, and the event delivery component relies on the event process audit component to verify the event process steps and store event information. A distributed ledger is deployed in the event center system deployment cluster, and each node has a distributed ledger service. The event process audit component on the node interacts with the distributed ledger through this service.

[0167] Among them, the evidence sub-component receives the event data evidence request from the event delivery component, encapsulates the event information into an event transaction and stores it in the distributed ledger. After receiving the event data evidence request, the evidence sub-component will encapsulate the transaction ID and evidence of the smart contract execution request that triggered the event as part of the transaction data to establish data association and enable the trusted proof to be transmitted during the event process. After the evidence data is stored, the evidence sub-component will return the ID and evidence (second evidence credential) of the event data evidence to the event delivery component, and finally pass it to the subscriber of the event as part of the event information. The audit sub-component provides event process audit services and handles event process audit requests. Specifically, it includes verification requests for the previous step of each step in the event process, retrieval of all events according to the event subject, and requests to retrieve all relevant information for a specific event; the audit sub-component constructs a query request based on the association between the audit requirements and the event evidence data, and reads data from the ledger through the ledger read-write sub-component.

[0168] The ledger read-write subcomponent directly interacts with the distributed ledger service, is responsible for reading and writing the distributed ledger, and is relied upon by the other two subcomponents. The ledger read-write subcomponent provides support for different distributed ledgers, which is the key to shielding the heterogeneity of ledgers. In addition, the ledger read-write subcomponent has a cache function, which temporarily provides the ability to retrieve evidence data when the distributed ledger service is unavailable.

[0169] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0170] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods and systems according to the embodiments of the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of the processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0171] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1A function specified in one or more boxes.

[0172] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable terminal device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0173] 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 embodiments of the present application.

[0174] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the elements.

[0175] The above is a detailed introduction to a trusted event processing method and system for data exchange tracing provided by the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for general technical personnel in this field, according to the idea of ​​the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. An event center system for implementing a trusted event processing method for data exchange and tracing, characterized in that: Acquire an event published by an event publishing system and a first evidence credential, wherein the first evidence credential represents evidence certification information of an event publishing transaction; Verifying the relevant information of the event publishing transaction according to the first evidence credential; When the relevant information of the event publishing transaction is verified, construct an event transaction according to the event data notarization model, and notarize the event transaction, and generate a second notarization voucher, wherein the second notarization voucher represents notarization certification information of the event transaction; The event and the second evidence credential are passed to the event subscription system, so that the event subscription system verifies the relevant information of the event transaction according to the second evidence credential; if the relevant information of the event transaction is verified, the event is processed, an event processing transaction is constructed according to the event data evidence model, and the event processing transaction is notarized.

2. The event center system for implementing a trusted event processing method for data exchange and tracing according to claim 1, characterized in that: Get event process audit request; According to the event subject in the event process audit request, the event process data is obtained from the distributed ledger, the distributed ledger includes: a ledger for storing event data and a ledger for deploying smart contracts, and the event process data includes: the subject of the event, event content information, event publishing transactions, and event processing transactions; The event process data is reproduced and compared to obtain the event process audit results.

3. The event center system for implementing a trusted event processing method for data exchange and tracing according to claim 2, characterized in that: According to the event subject in the event process audit request, the event process data is obtained from the distributed ledger, including: According to the event subject in the event process audit request, obtaining an event transaction list formed by the stored event data from the account book of the stored event data; Determine an event transaction from the event transaction list, and obtain event transaction information from the account book of the stored event data according to the event transaction ID, wherein the event transaction information includes: event subject, event content, event publishing transaction ID and event transaction ID; According to the event publishing transaction ID, obtain the event publishing transaction from the ledger of the deployed smart contract; According to the event transaction ID, an event processing transaction is obtained from the ledger of the deployed smart contract.

4. The event center system for implementing a trusted event processing method for data exchange and tracing according to claim 1, characterized in that: The event publishing transaction is stored in the block. The transaction sequence in the block is a Merkle tree. The first stored evidence is the leaf node and the root of the Merkle tree, and the hash value of the event publishing transaction. The relevant information of the event publishing transaction is verified according to the first stored evidence, including: Determine whether a leaf node of the Merkle tree has a stored hash value, where the stored hash value is determined when the event publishing transaction is stored; In the case where the stored hash value exists in the leaf node of the Merkle tree, reconstruct the Merkle tree according to the leaf node of the Merkle tree, and compare the root hash value of the reconstructed Merkle tree with the hash value of the event publishing transaction; When the tree root hash value and the event publishing transaction hash value are the same, it is determined that the relevant information of the event publishing has been verified.

5. The event center system for implementing a trusted event processing method for data exchange and tracing according to claim 1, characterized in that: The event data evidence model defines a complete event process based on the transaction data structure, and the event process includes: event subject, event content, evidence data of event release during the event process, evidence data of event transmission during the event process, and evidence data of event processing during the event process.

6. The event center system for implementing a trusted event processing method for data exchange and tracing according to claim 1, characterized in that: The event transaction is recorded as evidence, including: The event transaction is recorded in the event sequence in chronological order; Constructing a data dependency relationship between the event transaction and a first execution sequence, and constructing a data dependency relationship between the event data and a second execution sequence, wherein the event series is a sequence in which the event center system stores the event transactions, the first execution sequence is a sequence in which the event publishing system stores event publishing transactions, and the second execution sequence is a sequence in which the event subscription system stores event processing transactions.

7. A trusted event processing method for data exchange tracing, characterized in that: Applied to an event publishing system, the method comprises: Get execution request; Processing the execution request and publishing the event to the event center system as described in any one of claims 1 to 6; An event publishing transaction is constructed according to the event data notarization model, the event publishing transaction is notarized, and a first notarization credential is generated and sent to the event center system, wherein the first notarization credential represents notarization certification information of the event publishing transaction.

8. The method according to claim 7, characterized in that The event publishing transaction is recorded as evidence, including: Attesting the event publishing transaction in the first execution sequence according to the time sequence; A data dependency relationship is constructed between the event publishing transaction and the event sequence, wherein the event sequence is a sequence of event transactions stored in the event center system, and the first execution sequence is a sequence of event publishing transactions stored in the event publishing system.

9. A trusted event processing method for data exchange tracing, characterized in that: Applied to an event subscription system, the method comprises: Obtaining an event transmitted by the event center system as described in any one of claims 1 to 6 and a second evidence credential, wherein the second evidence credential represents evidence proof information of the event transaction; Verifying the relevant information of the event transaction according to the second evidence credential; If the relevant information of the event transaction is verified, the event is processed; An event processing transaction is constructed according to the event data notarization model, and the event processing data is notarized.

10. The method according to claim 9, characterized in that The event processing transaction is recorded as evidence, including: Attesting the event publishing transaction on the second execution sequence in chronological order; A data dependency relationship is constructed between the event processing transaction and the event sequence, wherein the event sequence is a sequence of event transactions stored in the event center system, and the second execution sequence is a sequence of event processing transactions stored in the event subscription system.

11. A trusted event processing system for data exchange tracing, characterized in that: include: An event publishing system is used to obtain and process execution requests, publish events to an event center system, construct an event publishing transaction according to an event data notarization model, notarize the event publishing transaction, generate a first notarization credential and send it to the event center system, wherein the first notarization credential represents notarization certification information of the event publishing transaction; An event center system is used to obtain an event and a first evidence credential, and verify the relevant information of the event publishing transaction according to the first evidence credential. If the relevant information of the event publishing transaction is verified, the event transaction is constructed according to the event data evidence model, and the event transaction is evidenced, and a second evidence credential is generated, and the event and the second evidence credential are transmitted to the event subscription system, wherein the second evidence credential represents the evidence certification information of the event transaction; An event subscription system is used to obtain the event and the second evidence credential transmitted by the event center system, verify the relevant information of the event transaction based on the second evidence credential, process the event if the relevant information of the event transaction is verified, construct an event processing transaction according to the event data evidence model, and store the event processing transaction.

Citation Information

Patent Citations

  • Transaction information processing method and related equipment

    CN115733626A

  • Storage system for cross-subject data circulation

    CN116996529A

  • Blockchain cross-chain regulation method for governance of chain by chain

    WO2023201927A1