Methods and electronic devices for verifying the completeness of electronic evidence.
By introducing a comparison mechanism between the set to be executed and the set already executed, the problem of incomplete action execution in the electronic evidence preservation process is solved, ensuring that each evidence preservation action is executed according to the rules, thereby improving the reliability and integrity of the evidence preservation process.
Patent Information
- Application Number
- CN202611620913.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-10-20
- Publication Date
- 2026-11-17
AI Technical Summary
Existing electronic evidence storage systems cannot effectively verify whether each action in the electronic evidence storage process is executed completely according to the rules. There are problems such as omissions in intermediate links or direct modification of the status after processing failures.
By introducing an execution set and an execution set into the electronic evidence storage system, the verification node determines the recording status of the action credential, generates the actual successor set, and compares it with the expected successor set to ensure that the action rules have been fully executed.
It enables the completeness verification of the electronic evidence preservation process, ensuring that each preservation action is executed according to the rules, avoiding omissions or mismarking, and improving the reliability and integrity of the preservation process.
Smart Images

Figure CN123116359A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of electronic evidence preservation, and more specifically to a method and electronic device for verifying the completeness of electronic evidence preservation. Background Technology
[0002] With the development of e-government, internet finance, and online transactions, electronic data such as contracts, orders, and communication records are widely used as evidence. From its creation to its use as evidence, electronic data undergoes several stages, including collection, storage, transmission, privacy processing, third-party notarization, receipt reception, and report generation. These different stages may be completed by different business nodes, preservation nodes, and external service organizations. Due to data security and privacy protection needs, raw electronic data is sometimes only allowed to be stored within specific nodes, while other nodes can only access the processed data. Therefore, the notarization process is characterized by cross-node and cross-network characteristics.
[0003] Existing electronic evidence storage systems employ methods such as digests, digital signatures, trusted timestamps, or blockchain records to determine whether electronic data has been modified, whether a signature is valid, or whether the storage time is reliable. Some systems also record processing progress through business status or operation logs. However, the fact that data, status, and logs at each stage are formed and stored separately, and that the final document, signature, or third-party receipt passes verification, does not necessarily mean that all previously stipulated processing steps have been completed. For example, if an intermediate step is omitted, the storage receipt does not correspond correctly to the electronic data, or the completion status is directly modified after a processing failure, the final stored evidence may still appear complete in form. For processes with abnormal branches or multi-node collaborative processing, simply checking the final data is insufficient to determine whether the stipulated actions have been completely performed.
[0004] Therefore, how to verify whether all the evidence preservation actions that should be performed according to the action rules in the electronic evidence preservation process have been performed has become a technical problem that needs to be solved. Summary of the Invention
[0005] The purpose of this application is to provide a method and electronic device for verifying the completeness of electronic evidence storage, which aims to verify whether all the storage actions that should be performed according to the action rules in the electronic evidence storage process have been performed.
[0006] In a first aspect, embodiments of this application provide a method for verifying the completeness of electronic evidence storage. The method is applied to an electronic evidence storage system, which includes multiple functional nodes, including a verification node. The method includes: The action rules, execution set, and execution set corresponding to the target electronic evidence are obtained. An initial action credential is generated according to the action rules, and the credential identifier of the initial action credential is recorded in the execution set. The action credential is used to represent the evidence preservation action to be performed and the functional node for performing the evidence preservation action. The execution set is used to accumulate and record the credential identifiers of the generated action credentials, and the execution set is used to accumulate and record the credential identifiers corresponding to the executed evidence preservation actions. The verification node is used to determine the target action credential whose credential identifier has been recorded in the execution set but not in the already executed set; The target evidence storage action represented by the target action credential is executed by the functional node indicated by the target action credential, and an actual successor set is generated based on the action execution result; wherein, the actual successor set includes the successor action credential generated by the functional node after executing the target evidence storage action, and the action execution result includes at least one of the execution status and action output of the target evidence storage action; Using verification nodes, the expected set of successors for the target evidence storage action is determined according to the action rules; wherein, the expected set of successors includes all successor action credentials generated after the target evidence storage action is executed, as specified by the action rules. If the actual successor set matches the expected successor set, the credential identifier of the target action credential is recorded in the executed set, and the credential identifier of each action credential in the actual successor set is recorded in the to-be-executed set. When the credential identifier of the termination action credential specified in the action rule has been recorded in the executed set, the verification node is used to verify whether the credential identifier contained in the execution set is exactly the same as the credential identifier contained in the executed set. If the credential identifiers contained in the set to be executed are exactly the same as those contained in the set to be executed, then all the evidence preservation actions that should be performed according to the action rules in the evidence preservation process of the target electronic evidence have been performed.
[0007] In one embodiment of this application, the set to be executed and the set already executed are stored using an authentication dictionary, which is a data structure that generates root values based on the stored credential identifiers; The verification node is used to determine the target action credential whose credential identifier is recorded in the to-be-executed set but not in the already-executed set, including: Obtain the voucher identifier of the action voucher to be determined, and use the voucher identifier of the action voucher to be determined as the voucher identifier to be determined. Obtain the membership proof of the credential identifier to be determined in the execution set, the non-membership proof of the credential identifier to be determined in the execution set, and the root values of the authentication dictionary corresponding to the execution set and the authentication dictionary corresponding to the execution set. Using the verification node, based on the root value of the authentication dictionary corresponding to the execution set, the credential identifier to be determined, and the membership proof, verify whether the credential identifier to be determined belongs to the execution set; Using the verification node, based on the root value of the authentication dictionary corresponding to the executed set, the credential identifier to be determined, and the non-membership proof, it is verified whether the credential identifier to be determined does not belong to the executed set. If the credential identifier to be determined belongs to the set to be executed but not to the set already executed, the credential to be determined is determined as the target action credential.
[0008] In one embodiment of this application, the execution set and the executed set are stored using an authentication dictionary. The authentication dictionary is a data structure that generates root values based on the stored credential identifiers. The authentication dictionary corresponding to the execution set and the authentication dictionary corresponding to the executed set use the same data structure and encoding rules, and both use the credential identifier as the key. The verification node verifies whether the credential identifiers contained in the set to be executed are exactly the same as those contained in the already executed set, including: The root value of the authentication dictionary corresponding to the set to be executed is compared with the root value of the authentication dictionary corresponding to the set already executed using the verification node. If the root value of the authentication dictionary corresponding to the set to be executed is the same as the root value of the authentication dictionary corresponding to the set to be executed, it is determined that the credential identifier contained in the set to be executed is exactly the same as the credential identifier contained in the set to be executed.
[0009] In one embodiment of this application, both the authentication dictionary corresponding to the set to be executed and the authentication dictionary corresponding to the set already executed are implemented using sparse Merkle trees; The method also includes: If the root value of the authentication dictionary corresponding to the execution set is different from the root value of the authentication dictionary corresponding to the execution set, the verification node is used to start from the root node of the sparse Merkle tree corresponding to the execution set and the sparse Merkle tree corresponding to the execution set, compare the digest values of the corresponding subtrees, and continue to compare the corresponding subtrees with different digest values until the unexecuted credential identifier recorded in the execution set but not recorded in the execution set is determined. Based on the action credential corresponding to the unexecuted credential identifier, determine the unexecuted evidence storage action and the functional node used to execute the unexecuted evidence storage action.
[0010] In one embodiment of this application, the multiple functional nodes further include a source node, a secondary node, and a primary node; the source node and the secondary node are used to acquire the original electronic data included in the target electronic evidence; The target notarization action, represented by the target action credential, is executed using the functional node indicated by the target action credential, and an actual successor set is generated based on the action execution result, including: When the target action credential instructs the source node to perform the target evidence storage action, the source node saves the original electronic data, generates the original data verification value based on the evidence identifier of the target electronic evidence and the original electronic data, and sends the original electronic data and the original data verification value to the secondary node. The source node is used to generate the original data processing voucher, and the original data processing voucher is used as the action voucher in the actual successor set. The original data verification value is used to verify whether the original electronic data held by different nodes are the same; the original data processing certificate is used to instruct secondary nodes to receive and process the original electronic data.
[0011] In one embodiment of this application, the target evidence storage action represented by the target action credential is executed using the functional node indicated by the target action credential, and an actual successor set is generated based on the action execution result, including: When the target action certificate is the original data processing certificate, the secondary node generates a comparison verification value based on the received original electronic data, and compares the comparison verification value with the original data verification value. If the verification value is the same as the original data verification value, the original electronic data is stored in the secondary node and converted into isolated data that the primary node cannot directly obtain. The isolated data verification value and the proof of origin are generated based on the isolated data. The proof of origin is used to prove that the isolated data is converted from the original electronic data of the target electronic evidence. The second-level node sends isolated data, original data verification value, isolated data verification value and same-origin proof to the first-level node to generate cross-domain verification certificate, and uses the cross-domain verification certificate as the action certificate in the actual successor set. When the target action credential is a cross-domain verification credential, the first-level node regenerates the verification value based on the received isolated data, compares the regenerated verification value with the isolated data verification value, and verifies whether the same-source proof indicates that the isolated data was converted from the original electronic data of the target electronic evidence, thus obtaining the cross-domain verification result. When the cross-domain verification result represents the regenerated verification value as being identical to the isolated data verification value, and the same-source proof represents the isolated data as being converted from the original electronic data of the target electronic evidence, an actual successor set is generated.
[0012] In one embodiment of this application, the electronic evidence storage system is communicatively connected with a third-party evidence storage node; The method also includes: The primary node generates a proof verification value based on the isolated data verification value and the cross-domain verification result, and generates a proof request credential that records the proof verification value. The proof request credential is then used as the action credential in the actual successor set. The target notarization action, represented by the target action credential, is executed using the functional node indicated by the target action credential, and an actual successor set is generated based on the action execution result, including: When the target action credential is a certificate of evidence storage request credential, the first-level node sends a certificate of evidence storage request to the third-party certificate of evidence storage node and receives the certificate of evidence storage receipt returned by the third-party certificate of evidence storage node after the certificate of evidence storage record is formed; wherein, the certificate of evidence storage receipt record contains the credential identifier of the certificate of evidence storage request credential and the certificate of evidence storage verification value. The first-level node compares the voucher identifier and the verification value in the evidence storage receipt with the voucher identifier and the verification value in the evidence storage request voucher, and generates an receipt return voucher if the two comparison results are the same. The receipt return voucher is then used as the action voucher in the actual successor set. When the target action credential is a receipt return credential, the first-level node returns the evidence storage receipt to the second-level node to generate a receipt record credential, and uses the receipt record credential as the action credential in the actual successor set. When the target action credential is a receipt record credential, a receipt record is generated and saved using a secondary node; the receipt record is used to represent the correspondence between the evidence storage receipt, the target electronic evidence, the original data verification value, and the isolated data verification value. The secondary node sends confirmation information to the source node to indicate that the receipt record has been saved, and generates the actual successor set based on the receipt record.
[0013] In one embodiment of this application, generating an actual successor set based on receipt records includes: The secondary nodes generate report generation vouchers based on receipt records and preset report rules, and use the report generation vouchers as action vouchers in the actual subsequent set; the preset report rules are used to specify the report content that the actual report should include, and the report generation vouchers are used to instruct the secondary nodes to generate electronic evidence reports based on receipt records. The target notarization action, represented by the target action credential, is executed using the functional node indicated by the target action credential, and an actual successor set is generated based on the action execution result, including: When the target action credential is the report generation credential, the secondary node is used to generate an electronic evidence report based on the receipt record, and the secondary node signature is added to the electronic evidence report. The report processing voucher is generated using the secondary node and used as the action voucher in the actual successor set; the report processing voucher is used to instruct the primary node to verify and sign the electronic evidence report; When the target action credential is the report processing credential, the first-level node is used to verify the signature of the second-level node in the electronic evidence report, and to verify whether the electronic evidence and the evidence storage receipt cited in the electronic evidence report are the target electronic evidence and the evidence storage receipt, respectively. If the signature verification of the secondary node is successful and the electronic evidence and the evidence storage receipt cited in the electronic evidence report are the target electronic evidence and the evidence storage receipt, respectively, the electronic evidence report is processed by the primary node according to the preset reporting rules, and the primary node signature is added to the processed electronic evidence report to obtain the actual report. The system uses the actual report returned by the first-level node to the second-level node to generate a report verification voucher, and uses the report verification voucher as the action voucher in the actual successor set; the report verification voucher is used to instruct the second-level node to verify the actual report.
[0014] In one embodiment of this application, the target evidence storage action represented by the target action credential is executed using the functional node indicated by the target action credential, and an actual successor set is generated based on the action execution result, including: When the target action voucher is a report verification voucher, the second-level node is used to verify whether the actual report includes all the report content specified by the preset report rules, and to verify the signature of the first-level node in the actual report. If the actual report includes all report content and the signature verification of the first-level node is successful, a download license certificate is generated using the second-level node, and a termination action certificate is generated based on the download license certificate. The termination action certificate is used as the action certificate in the actual successor set. The download license certificate is used to indicate the actual report that can be obtained corresponding to the target electronic evidence, and the termination action certificate is used to instruct the verification node to perform the termination action. If the target action credential is a termination action credential, the verification node is used to check whether the electronic evidence and report indicated by the download license credential are the target electronic evidence and the actual report, respectively. If the electronic evidence and report indicated by the download license credential are the target electronic evidence and the actual report, the empty set is determined as the actual successor set.
[0015] Secondly, embodiments of this application provide an electronic device, including: The memory is configured to store instructions; and The processor is configured to retrieve the instructions from the memory and, when executing the instructions, to implement the electronic evidence preservation completeness verification method provided in the first aspect of the embodiments of this application.
[0016] In this embodiment, the electronic evidence preservation system establishes action rules, an execution set, and an executed set for the target electronic evidence, and generates initial action credentials based on the action rules. Before each preservation action is executed, it verifies that the target action credentials have been recorded in the execution set but not yet in the executed set. After the preservation action is executed, an actual successor set and a desired successor set are formed, and the execution set and the executed set are updated when the two successor sets are consistent. After the action execution is terminated, it is verified whether the credential identifiers contained in the two sets are completely identical. Therefore, preservation actions that have been generated but not yet executed by the action rules will continue to be retained in the execution set, and the verification node can use this to verify whether all preservation actions that should be executed according to the action rules in the preservation process of the target electronic evidence have been executed. Attached Figure Description
[0017] Figure 1 This is a flowchart illustrating the method for verifying the completeness of electronic evidence storage provided in this application embodiment; Figure 2 This is another flowchart illustrating the method for verifying the completeness of electronic evidence storage provided in this application embodiment; Figure 3 This is another flowchart illustrating the method for verifying the completeness of electronic evidence storage provided in this application embodiment; Figure 4 This is another flowchart illustrating the method for verifying the completeness of electronic evidence storage provided in this application embodiment; Figure 5 This is another flowchart illustrating the method for verifying the completeness of electronic evidence storage provided in this application embodiment; Figure 6 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation
[0018] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.
[0019] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.
[0020] The first aspect of this application provides a method for verifying the completeness of electronic evidence storage, which is applied to an electronic evidence storage system.
[0021] An electronic evidence storage system can be implemented by a single electronic device or by a distributed cluster of multiple electronic devices. When the system is implemented by a single electronic device, the multiple functional nodes can be represented as software modules, processes, containers, virtual machines, or trusted execution environments running on that device. These functional nodes exchange data through inter-process interfaces or internal message buses. When the system is implemented by a distributed cluster of electronic devices, each functional node can be deployed on servers, computers, edge devices, storage devices, or cryptographic devices, and communicate through controlled networks, isolated switching channels, or dedicated interfaces. Therefore, in this embodiment, nodes represent logical roles that assume corresponding processing functions and data access permissions; different nodes do not necessarily correspond to different physical devices.
[0022] Electronic devices used to implement an electronic evidence storage system may include a processor, memory, and a communication interface. The memory stores computer programs, action rules, action credentials, action execution results, authentication dictionaries, and verification materials. The processor executes the computer program to complete action credential generation, evidence storage action execution, set updates, and process completeness verification. The communication interface is used to transmit electronic data, checksums, proofs, evidence storage receipts, and reports between functional nodes. The electronic evidence storage system can also invoke electronic signature services, certificate services, and trusted time services to verify action execution nodes and the time of action occurrence.
[0023] The electronic evidence storage system comprises multiple functional nodes, including at least a verification node, and may also include source nodes, secondary nodes, and primary nodes. The source node acquires and stores the original electronic data included in the target electronic evidence. The secondary node receives, verifies, and stores the original electronic data, and converts it into isolated data. The primary node verifies the isolated data without obtaining the original electronic data and interacts with third-party storage nodes. The verification node determines the action credential according to action rules, verifies the actual successor set against the expected successor set, and verifies whether the set to be executed and the set already executed are closed. The third-party storage node is located outside the electronic evidence storage system and is used to form storage records based on storage requests sent by the primary node and return storage receipts. The third-party storage node can be a blockchain storage platform, a trusted time storage platform, a judicial storage platform, or other service nodes capable of forming verifiable storage records.
[0024] like Figure 2 As shown, the source node and secondary nodes can obtain the original electronic data of the target electronic evidence, while the primary node and third-party evidence storage node do not need to obtain the original electronic data. The secondary node sends isolated data, corresponding checksums, and proof of origin to the primary node. The isolated data can be the original electronic data after overall encryption, field-level encryption, sensitive field desensitization, digest encapsulation, or encrypted indexing. Even if multiple functional nodes are deployed in the same electronic device, the aforementioned data access boundaries can be maintained through process isolation, access control, key permissions, and storage partitioning.
[0025] In one implementation, the electronic evidence storage system sets up a raw data storage area, an action library, and a proof library. The raw data storage area is located within the authorized environment of the source node and secondary nodes, and is used to store raw electronic data and access records. The action library stores action credentials, action execution results, and execution status. The proof library stores authentication dictionary proofs, node signatures, trusted times, and action completion witnesses. Primary nodes can store segregated data, proof of origin, evidence storage receipts, and report materials, but do not store raw electronic data.
[0026] In this embodiment, the target electronic evidence refers to electronic data objects that need to be stored and have their storage process verified, such as electronic contracts, electronic invoices, business records, audio and video files, or data collected by devices. Target electronic evidence can be distinguished from other electronic evidence by an evidence identifier. Different storage processes for the same target electronic evidence can also have separate process identifiers. The electronic evidence storage system uses evidence identifiers and process identifiers to associate action rules, action credentials, the set to be executed, the set already executed, and the corresponding action execution results to the same storage process.
[0027] Action rules are rule data used to define the various evidence preservation actions and their sequential relationships in the evidence preservation process. Action rules can specify the execution nodes, execution conditions, success or failure branches, subsequent evidence preservation actions corresponding to each branch, and termination conditions for each evidence preservation action. Action rules can be implemented using state tables, deterministic finite state machines, state transition tables, or restricted scripts. Regardless of the form used, the verification node can determine the selected allowed branch and all subsequent action credentials corresponding to that branch based on the target evidence preservation action and the action execution result.
[0028] Action credentials are used to characterize evidence-preserving actions that have been determined by action rules but are yet to be executed, as well as the functional nodes used to execute those actions. Credential identifiers are used to uniquely indicate the corresponding action credentials. For ease of expression in formulas and examples, the credential identifier can be denoted as TID, the set to be executed as P, and the set already executed as F. The names used in the claims shall prevail in the main text description.
[0029] The credential identifier for an action credential can be generated using the following formula: TID = H(EID ∥ Cstate ∥ Act ∥ Role ∥ Rv ∥ Cprev ∥ Branch) Wherein, H represents cryptographic hash operation; EID represents the evidence identifier of the target electronic evidence; Cstate represents the status verification value before the execution of the target evidence preservation action; Act represents the action type; Role represents the functional node role of the node executing the target evidence preservation action; Rv represents the version of the action rule; Cprev represents the verification value of the execution result of the preceding action, the preceding evidence preservation receipt, or the preceding report; and Branch represents the normal branch, the rejection branch, the timeout branch, or the compensation branch. The action credential may also include a process identifier, execution time limit, issuing node identifier, receiving node identifier, algorithm parameter verification value, and credential format version.
[0030] Before generating the credential identifier, the electronic evidence storage system can standardize the coding of the fields involved in the credential identifier calculation according to the coding method specified in the action rules. For example, each field adopts a fixed order and carries type and length, integers use a unified code, time uses a unified time zone and precision, null values use an explicit null marker, and elements in the set are sorted according to the check value. Different functional nodes using the same action rules and the same input can thus obtain the same credential identifier.
[0031] In one implementation, the execution set and the executed set are maintained uniformly by the verification node, and each functional node submits action credentials and action execution results to the verification node. In another implementation, each functional node maintains its own authentication dictionary and sends the root value before update, the root value after update, and the update proof along with cross-node data packets. After verifying the corresponding root value and update proof, the receiving node associates the root value of the previous node with its own entry action credential. Both implementations use the same credential generation rules and the same final state verification conditions.
[0032] Please refer to the following: Figures 1-3 The method for verifying the completeness of electronic evidence storage provided in the first aspect of this application includes the following steps S100-S700: Step S100: Obtain the action rules, execution set, and execution set corresponding to the target electronic evidence; generate an initial action credential based on the action rules; and record the credential identifier of the initial action credential in the execution set. Among them, the action credential is used to represent the evidence storage action to be performed and the functional node for performing the evidence storage action, the action to be performed set is used to accumulate and record the credential identifiers of the generated action credentials, and the executed set is used to accumulate and record the credential identifiers corresponding to the executed evidence storage actions.
[0033] In this step, the electronic evidence storage system first identifies the target electronic evidence that needs to be stored and verified for completeness. The target electronic evidence can be obtained by the source node from the business system, data acquisition device, file interface, or database, or it can be read by the electronic evidence storage system from the controlled storage area based on the evidence identifier submitted by the user. The electronic evidence storage system assigns an evidence identifier to the target electronic evidence and a process identifier to this storage process. The evidence identifier and process identifier are used together to associate all processed data of the target electronic evidence in this storage process.
[0034] The electronic evidence preservation system retrieves the action rules corresponding to the target electronic evidence from the rule base based on the evidence identifier and process identifier, and obtains the "to be executed" set and "already executed" set corresponding to the preservation process from the state storage area. For newly established preservation processes, both sets can be initialized to empty sets; for resumed preservation processes, the sets after the last valid update are obtained. The "to be executed" set accumulates the credential identifiers of action credentials generated by the action rules, indicating that the corresponding preservation action has become an execution obligation of this process. The "already executed" set accumulates the credential identifiers corresponding to the executed preservation actions, indicating that the corresponding execution obligations have been completed.
[0035] The electronic evidence storage system then determines the storage actions that must be performed first in the storage process, as well as the functional nodes that will perform these actions, based on the action rules, and generates an initial action credential accordingly. For example, the action rules may stipulate that the source node should first register the original electronic data included in the target electronic evidence. The initial action credential correspondingly represents this registration action and the source node used to perform it. The electronic evidence storage system generates a credential identifier for the initial action credential and writes this identifier into the execution set. At this point, the executed set has not yet recorded this credential identifier, indicating that the initial storage action has been determined but not yet executed.
[0036] In one implementation, the electronic evidence storage system fixes the action rule version when establishing the storage process and associates the rule version and rule verification value with the initial action credential. Subsequent storage actions for the target electronic evidence continue to use the same rule version. Newly released action rules can be used in newly established storage processes, but do not directly replace the action rules used in processes in progress.
[0037] When it is necessary to migrate an ongoing process, the migration actions can be pre-defined by the old action rules. When the electronic evidence storage system executes the migration action, it fixes the root values of the execution set and the executed set before the migration, and generates a list of verification values based on the action credentials that have not yet been executed under the old rule version. The system maps each unexecuted old action credential to a continuation execution credential, compensation credential, or authorized termination credential under the new rule version according to a pre-published mapping table. The migration will fail if an old action credential has no mapped destination, has multiple disallowed mapped destinations, or the action type and execution node of the new action credential do not match the mapping table. The correspondence between the original data verification values, isolated data verification values, proof of origin, and evidence storage requests already formed before the migration remains unchanged.
[0038] Thus, establishing the rule benchmarks and initial execution obligations for this evidence preservation process for the target electronic evidence provides a clear starting point for subsequent verification.
[0039] For example, the source node obtains an electronic invoice with the number INV-2026-001 and identifies it as the target electronic evidence. The electronic evidence storage system generates an evidence identifier E1001 and a process identifier P9001 for this electronic invoice, and obtains action rule R3, as well as the execution set and executed set corresponding to this process. Action rule R3 stipulates that the source node should first register the original electronic data, so the system generates an initial action credential T01 and writes the credential identifier of T01 into the execution set. At this time, the executed set is empty, indicating that the registration action corresponding to T01 has not yet been executed.
[0040] Step S200: Use the verification node to determine the target action credential whose credential identifier is recorded in the set to be executed but not in the already executed set.
[0041] In this step, the verification node retrieves the action credentials to be determined from the pending action credentials corresponding to the target electronic evidence (there can be multiple such credentials, and each can be processed separately in subsequent processes). The verification node uses the credential identifier of the action credential as the retrieval basis to query both the execution set and the executed set. If the credential identifier is recorded in the execution set, it indicates that the action credential was generated by the initial action or a verified preceding evidence preservation action; if the credential identifier is not yet recorded in the executed set, it indicates that the evidence preservation action represented by the action credential has not yet been completed. When both conditions are met, the verification node identifies the action credential as the target action credential (there can be multiple target action credentials, and each target action credential is processed separately in subsequent processes).
[0042] The verification node can also check the evidence identifier, process identifier, action rule version, and functional node associated with the target action credential. All of the above should match the current electronic evidence storage process. If a subsequent request arrives before the corresponding preceding action credential has been generated, the electronic evidence storage system can first save the request in the isolation area without updating the execution set and the executed set; after the preceding action is completed and the corresponding action credential is generated, this step can be re-executed. For duplicate requests where the credential identifier has already been recorded in the executed set, the electronic evidence storage system can return the initial execution result but will not identify it as the target action credential again.
[0043] In this way, action credentials that have become obligations to be performed but have not yet been performed can be identified from the action credentials corresponding to the target electronic evidence, thus preventing the execution of evidence preservation actions not required by the action rules or the repeated execution of evidence preservation actions that have already been completed.
[0044] For example, when the verification node queries action credential T01, it determines that the credential identifier of T01 has been recorded in the execution set corresponding to electronic invoice E1001, but has not yet been recorded in the executed set. Therefore, T01 is identified as the target action credential. If the source node submits the same request again after T01 is completed, since the credential identifier of T01 has already been recorded in the executed set, the verification node will no longer identify it as the target action credential.
[0045] Step S300: Execute the target evidence storage action represented by the target action credential using the functional node indicated by the target action credential, and generate the actual successor set based on the action execution result; The actual successor set includes the successor action credentials generated by the functional node after executing the target evidence storage action, and the action execution result includes at least one of the execution status of the target evidence storage action and the action output.
[0046] In this step, the electronic evidence preservation system determines the functional node to perform the target evidence preservation action based on the target action credential, and provides the target action credential and the data required to perform the target evidence preservation action to the functional node. The functional node performs the target evidence preservation action according to the action type represented by the target action credential. The target evidence preservation action may be saving the original electronic data, generating a check value, converting the original electronic data into segregated data, verifying the proof of origin, sending an evidence preservation request, verifying the evidence preservation receipt, or generating an electronic evidence report.
[0047] After a functional node executes the target evidence storage action, it generates an action execution result. The action execution result includes at least one of the following: the execution status of the target evidence storage action and the action output. The execution status can indicate successful execution, verification failure, execution timeout, or the need for compensation. The action output can include a verification value, node signature, trusted time, proof of origin, evidence storage receipt, or report verification value. The functional node can generate a result verification value based on the action execution result and sign the result verification value to verify whether the action execution result was formed by the functional node indicated by the target action credential.
[0048] The functional node determines the processing branch that is actually satisfied based on the action execution result, and generates all subsequent action credentials actually generated under that branch. These subsequent action credentials constitute the actual successor set. If the action rule requires the parallel execution of multiple subsequent evidence-keeping actions, the actual successor set includes the corresponding multiple subsequent action credentials; if the execution results of different actions correspond to mutually exclusive branches, the actual successor set includes the subsequent action credentials corresponding to the branch selected by the current action execution result. For termination actions, the actual successor set can be an empty set.
[0049] In one implementation, for duplicate requests with the same credential identifier and the same action execution result, the functional node returns the initial action execution result, and the electronic evidence storage system does not repeatedly update the two sets. If the same credential identifier corresponds to two different action execution results, and both results have valid node signatures, the electronic evidence storage system retains both action execution results and their signatures to form a conflict proof, rather than overwriting the earlier result with the later one.
[0050] For target evidence storage actions that time out or fail to execute, the electronic evidence storage system does not eliminate the evidence storage action by deleting the credential identifier from the set to be executed. Action rules can pre-define retry branches or compensation branches. When the corresponding conditions are met, the functional node can retry using the same target action credential and the same input, or generate subsequent action credentials based on the action execution result for delayed evidence storage, switching to a backup third-party evidence storage node, re-conversion, or manual review.
[0051] In this way, the actual execution of the target evidence storage action is transformed into action execution results and actual subsequent sets that can be verified later, so that normal processing, failure processing and compensation processing can all continue to be passed along the action certificate.
[0052] For example, the target action credential instructs the secondary node to receive the original electronic data of electronic invoice E1001. The secondary node recalculates the checksum and compares it with the checksum of the original data sent by the source node. If they match, the action execution result includes a successful execution status and the obtained checksum. Based on this, the secondary node generates action credentials indicating subsequent saving and isolation conversion, and adds these action credentials to the actual successor set. If they differ, the action execution result is a checksum failure, and the actual successor set includes resent credentials or rejection credentials as specified by the action rules.
[0053] Step S400: Using the verification node, determine the expected successor set of the target evidence storage action according to the action rules; The expected successor set includes all successor action credentials generated after the target evidence storage action is executed, as specified in the action rules.
[0054] In this step, the verification node reads the action rule corresponding to the target electronic evidence and confirms that the version of the action rule is consistent with the version of the rule associated with the target action credential. Using the target evidence preservation action and the verified action execution result as input, the verification node determines the processing branch in the action rule corresponding to the current execution state, and then obtains all subsequent evidence preservation actions specified in that branch. Based on these subsequent evidence preservation actions and the corresponding execution nodes, the verification node generates subsequent action credentials, thereby forming the expected set of subsequent actions.
[0055] The expected successor set reflects the complete requirements of the action rule for the current target evidence storage action. If the action rule stipulates that multiple successive evidence storage actions must be executed, the expected successor set includes all corresponding successive action credentials; if the action rule stipulates multiple mutually exclusive branches, the verification node determines the successor action credentials only based on the allowed branch selected according to the execution result of this action. When a termination action has no subsequent execution obligation, the expected successor set is empty.
[0056] In one implementation, the verification node independently determines the expected successor set using a read-only rule list released with the action rule version, instead of directly using the successor list submitted by the function node. The verification node recalculates the credential identifiers for each action credential in the expected successor set using the same credential identifier generation method as the function node. This allows the verification node to check whether it has generated too few, too many, or incorrectly generated successor action credentials.
[0057] In this way, a complete subsequent benchmark is established based on the action rules corresponding to the target electronic evidence, so that the completeness of the subsequent actions is not determined solely by the functional node that executes the target evidence storage action.
[0058] For example, action rule R3 stipulates that after the second-level node completes the isolation conversion, it needs to generate an action credential for the first-level node to perform cross-domain verification. If the isolation conversion is successful, the verification node generates a cross-domain verification credential based on it and includes it in the expected successor set; if the isolation conversion fails, the expected successor set includes a re-conversion credential or a manually reviewed credential, but does not include a cross-domain verification credential.
[0059] Step S500: If the actual successor set is consistent with the expected successor set, record the credential identifier of the target action credential in the executed set, and record the credential identifier of each action credential in the actual successor set in the to be executed set.
[0060] In this step, the verification node compares the actual successor set with the expected successor set. The verification node can first compare the number of action credentials contained in the two sets, then sort the action credentials in the two sets according to a predetermined coding order, and compare the credential identifier of each corresponding action credential. When it is necessary to verify the content of the action credentials, it can also compare the action type, execution node, rule version, preceding result verification value, branch type, and parameter verification value. If both sets contain the same complete set of successor action credentials, the actual successor set is determined to be consistent with the expected successor set.
[0061] When the actual successor set matches the expected successor set, the electronic evidence storage system writes the credential identifier of the target action credential into the executed set to indicate that the target evidence storage action has been executed. Simultaneously, it writes the credential identifiers of each action credential in the actual successor set into the to-be-executed set to indicate that the corresponding subsequent evidence storage action has become a new execution obligation. These two writes can be completed using a transaction processing method where success or failure is equal. If either write fails, the set update is not confirmed, preventing situations where the target evidence storage action has been marked as completed but the subsequent action credential has not been written into the to-be-executed set.
[0062] If the actual successor set differs from the expected successor set, the electronic evidence storage system will not perform the aforementioned set update. The verification node can output action credentials that are missing from the actual successor set, action credentials that are extra in the actual successor set, or action credentials with inconsistent content, for the corresponding functional nodes to reprocess.
[0063] In one implementation, the electronic evidence storage system generates an action completion witness for the current set update. The action completion witness proves that the target evidence storage action has been executed and that the two sets have been updated based on the comparison results of the successor sets. The action completion witness may include the root values of the sets to be executed and the root values of the executed sets before and after the update, the credential identifier of the target action credential, the action execution result verification value, the selected branch, the expected successor set verification value, the node signature, the trusted time, member proof, non-member proof, and the set update proof. If original electronic data is involved, the action completion witness may only record the original data verification value and read the verification result; the original electronic data remains stored in the authorized environment of the source node or secondary node.
[0064] In this way, the completion record of the target evidence preservation action and the generation of all subsequent execution obligations are written into the corresponding set at the same time, so as to avoid the omission of its subsequent evidence preservation actions when the current action is marked as completed.
[0065] For example, the target action credential is T01, and both the actual successor set and the expected successor set include action credentials T02 and T03. After the verification node confirms that the two sets are consistent, it writes the credential identifier of T01 into the executed set and writes the credential identifiers of T02 and T03 into the to-be-executed set. If the actual successor set only includes T02, neither set is updated, and T01 still cannot be determined as completed.
[0066] Step S600: When the credential identifier of the termination action credential specified in the action rule has been recorded in the executed set, use the verification node to verify whether the credential identifier contained in the to be executed set is exactly the same as the credential identifier contained in the executed set.
[0067] In this step, the termination action credential, like other action credentials, is first determined, executed, and updated in steps S200 to S500. The credential identifier of the termination action credential has been recorded in the executed set, indicating that the evidence preservation process of the target electronic evidence has been executed to the termination position specified by the action rules. The verification node then compares the executable set and the executed set corresponding to the target electronic evidence to confirm whether each execution obligation generated before the termination action has been completed.
[0068] Verification nodes can compare credential identifiers in two sets item by item, or, if both sets use the same authentication data structure and encoding rules, compare the corresponding root values of the two sets. If the root values are the same, it is determined that the credential identifiers contained in the two sets are completely identical; if the root values are different, the verification node further obtains proof of the difference to locate credential identifiers recorded in the set to be executed but not yet recorded in the executed set. If the termination action has been executed but the two sets are still different, the process completeness condition is not met.
[0069] In one implementation, the electronic evidence storage system organizes verification materials into single-action verification packages, stage verification packages, cross-domain verification packages, receipt verification packages, and final verification packages. Single-action verification packages verify the execution of a target action credential and its subsequent sets. Stage verification packages verify the starting and ending root values of the original data processing stage, isolated data storage stage, or reporting stage. Cross-domain verification packages may include original data verification values, isolated data verification values, and proof of origin. Receipt verification packages may include evidence storage request credentials, evidence storage verification values, evidence storage receipts, and receipt verification materials. The final verification package may include the root values of each stage, necessary set proofs, proof of origin, evidence storage receipts, actual report verification values, download license credentials, and termination action credentials. During routine verification, the root values and aggregate proofs can be transmitted first; if discrepancies are found, the corresponding subtree proofs and action completion witnesses are then obtained.
[0070] For implementations that maintain the sets to be executed and the sets already executed at different stages, the global verification value can also be generated according to the following formula: G = H(EID ∥ Rv ∥ Root(Pm) ∥ Root(Fm) ∥ Cbridge ∥ Root(Pc) ∥Root(Fc) ∥ Root(Pr) ∥ Root(Fr) ∥ R3 ∥ Td) Where Pm and Fm represent the execution set and executed set in the original electronic data processing stage, respectively; Pc and Fc represent the execution set and executed set in the isolated data storage stage, respectively; Pr and Fr represent the execution set and executed set in the reporting stage, respectively; Cbridge represents the verification value for same-origin proof and cross-domain relationship; R3 represents the storage receipt; and Td represents the download license credential. This formula provides an optional multi-stage joint verification method. When using a single full-process execution set and executed set, the two sets can be directly compared.
[0071] Thus, after the termination action has been executed, it is necessary to check whether there are still action certificates that have been generated but not yet executed in the evidence storage process of the target electronic evidence, so as to prevent the process from being deemed complete in advance based solely on the termination action or the business completion status.
[0072] For example, the termination action credential T23 for electronic invoice E1001 has been recorded in the executed set, but the action credential T17 for "the secondary node sending confirmation information to the source node" is still only recorded in the to-be-executed set. The verification node thus determines that the two sets are not the same, and the evidence storage action corresponding to T17 has not yet been executed. The evidence storage process cannot be considered complete simply because T23 has been executed.
[0073] Step S700: If the credential identifiers contained in the set to be executed are exactly the same as those contained in the set to be executed, it is determined that all the evidence storage actions that should be performed according to the action rules in the evidence storage process of the target electronic evidence have been executed.
[0074] In this step, the verification node makes a completeness judgment based on the set comparison results obtained in step S600. When the credential identifiers contained in the executable set corresponding to the target electronic evidence are exactly the same as those in the executed set, each action credential generated by the action rules has a corresponding execution record. Based on this, the verification node determines that in the evidence preservation process of the target electronic evidence, all evidence preservation actions that should be performed according to the action rules have been executed, and can output a "complete" verification conclusion.
[0075] The verification node can also generate a closed witness based on the evidence identifier, process identifier, action rule version, final state set root value, and verification time of the target electronic evidence, and add a verification node signature to the closed witness. If the two sets are different and the unexecuted credential identifier can be located, "Incomplete" and the corresponding unexecuted evidence storage action can be output; if the same action credential corresponds to two different action execution results, both of which have valid signatures, "Conflict" can be output; if necessary proof, historical action rules, or certificate materials are missing, "Unable to Verify" can be output. Only when the verification conclusion is "Complete" will a valid closed witness be generated.
[0076] To prevent nodes maintaining sets from simultaneously deleting identical content from two sets and then forging the same root value, the electronic evidence storage system can associate the initial set root value with the initial action credential and action rule version, and ensure that the state after each update references the two set root values before the update. Verification nodes verify the continuous update relationship from the initial set root value to the final set root value, rather than simply comparing two final root values whose sources cannot be verified.
[0077] In one implementation, after the process is closed, the electronic evidence storage system archives detailed data of the actions according to the storage strategy, and continues to store the starting and ending root values of each stage, proof of origin, evidence storage receipts, actual report verification values, download license certificates, closure witnesses, and verification parameters of historical action rules. In the event of a subsequent dispute, the action completion witness and set of evidence can be retrieved from the archived evidence repository based on the corresponding credential identifier.
[0078] In this way, the closed state of the two sets is transformed into a conclusion on the completeness of the evidence for the target electronic evidence, so that the verification conclusion directly corresponds to "whether all evidence preservation actions that should be performed according to the action rules have been performed".
[0079] For example, the verification node confirms that both the execution set and the executed set corresponding to electronic invoice E1001 contain all the voucher identifiers actually generated by action rule R3 from T01 to T23, and confirms that the termination action voucher has been executed. Based on this, the verification node determines that all the evidence storage actions that should be executed according to action rule R3 in the evidence storage process of electronic invoice E1001 have been executed, and generates a closed witness associated with E1001, R3, and the root value of the final state set.
[0080] Through steps S100 to S700, the electronic evidence preservation system establishes action rules, an execution set, and an executed set for the target electronic evidence, and generates initial action credentials based on the action rules. Before each preservation action is executed, it verifies that the target action credentials have been recorded in the execution set but not yet in the executed set. After the preservation action is executed, the actual successor set and the expected successor set are formed respectively, and the execution set and the executed set are updated when the two successor sets are consistent. After the action execution is terminated, it is verified whether the credential identifiers contained in the two sets are completely identical. Therefore, preservation actions that have been generated but not yet executed by the action rules will continue to be retained in the execution set, and the verification node can use this to verify whether all preservation actions that should be executed according to the action rules in the preservation process of the target electronic evidence have been executed.
[0081] In one embodiment of this application, the set to be executed and the set already executed are stored using authentication dictionaries. The verification node determines whether the action credential to be determined is the target action credential through membership proof and non-membership proof.
[0082] Specifically, an authentication dictionary is a data structure capable of generating root values based on its stored credential identifiers and providing membership or non-membership proofs for specific credential identifiers. The authentication dictionary corresponding to the execution set records the credential identifiers of the generated action credentials; the authentication dictionary corresponding to the executed set records the credential identifiers corresponding to the executed evidence-gathering actions. The authentication dictionary can be a sparse Merkle tree, or it can be a Merkle-Patricia tree, vector commitment, cryptographic accumulator, or other data structures with corresponding authentication capabilities.
[0083] When performing batch storage of multiple electronic evidences, two authentication dictionaries can be established for each target electronic evidence, or a hierarchical authentication dictionary can be established. When using a hierarchical authentication dictionary, the electronic evidence storage system can obtain the sub-root value or member proof corresponding to the target electronic evidence, so that the verification node only verifies the storage process corresponding to that target electronic evidence.
[0084] The verification node is used to determine the target action credential whose credential identifier is recorded in the to-be-executed set but not in the already-executed set, including: Step A1: Obtain the voucher identifier of the action voucher to be determined, and use the voucher identifier of the action voucher to be determined as the voucher identifier to be determined.
[0085] Specifically, the verification node can receive action credentials to be determined submitted by the functional node, or it can read action credentials to be determined from the pending index corresponding to the execution set (there can be multiple such credentials, each processed separately in subsequent steps). The verification node obtains the credential identifier carried by the action credential and can recalculate the credential identifier based on the evidence identifier, action type, execution node, rule version, and preceding results in the action credential. If the recalculated credential identifier is the same as the credential identifier carried by the action credential, that credential identifier is used as the credential identifier to be determined. If they are different, it indicates that the content of the action credential or the credential identifier may have been changed, and subsequent membership verification is no longer performed.
[0086] Step A2: Obtain the membership proof of the credential identifier to be determined in the execution set, the non-membership proof of the credential identifier to be determined in the execution set, and the root values of the authentication dictionary corresponding to the execution set and the authentication dictionary corresponding to the execution set.
[0087] Specifically, the node maintaining the authentication dictionary generates a membership proof for the credential identifier to be determined within the execution set and a non-membership proof within the already executed set. Taking a sparse Merkle tree as an example, the membership or non-membership proof can include path information from the leaf node corresponding to the credential identifier to the root node, as well as the digest values of sibling nodes at each level. The verification node simultaneously obtains the root values corresponding to the two authentication dictionaries used to generate the above proofs. The membership proof, non-membership proof, and corresponding root value can be associated with the same set snapshot identifier, avoiding the combination of proofs from different update times.
[0088] Step A3: Using the verification node, verify whether the credential identifier to be determined belongs to the set to be executed, based on the root value of the authentication dictionary corresponding to the set to be executed, the credential identifier to be determined, and the membership proof.
[0089] Specifically, the verification node determines the verification path in the authentication dictionary based on the credential identifier to be determined, and calculates the digest value layer by layer using the path information provided by the membership proof to obtain the candidate root value. If the candidate root value is the same as the root value of the authentication dictionary corresponding to the execution set, and the leaf node corresponding to the credential identifier is a non-empty leaf, the verification node determines that the credential identifier to be determined belongs to the execution set. This verification indicates that the action credential to be determined has been generated by the action rule corresponding to the target electronic evidence or by a verified preceding action.
[0090] Step A4: Using the verification node, based on the root value of the authentication dictionary corresponding to the executed set, the credential identifier to be determined, and the non-membership proof, verify whether the credential identifier to be determined does not belong to the executed set.
[0091] Specifically, the verification node calculates the candidate root value corresponding to the executed set based on the same credential identifier and non-membership proof to be determined, and checks whether the leaf node corresponding to the credential identifier is an empty leaf or whether the key does not exist. If the candidate root value is the same as the root value of the authentication dictionary corresponding to the executed set, and the corresponding leaf node is empty, the verification node determines that the credential identifier to be determined does not belong to the executed set, that is, the proof-of-existence action represented by the action credential has not yet been executed.
[0092] Step A5: If the credential identifier to be determined belongs to the set to be executed but not to the set already executed, then determine the action credential to be determined as the target action credential.
[0093] Specifically, the verification node associates the membership verification result of step A3 and the non-membership verification result of step A4 with the same target electronic evidence, the same evidence storage process, and the same set of snapshots. If both verification results pass, the action credential to be determined is identified as the target action credential. If either verification result fails, the action credential is not identified as the target action credential.
[0094] In this way, the verification node can use the root values of the two authentication dictionaries and the proof for a single credential identifier to confirm whether the action credential to be determined is in the state of "already requested to be executed but not yet executed", without having to obtain all credential identifiers in the two sets.
[0095] For example, a secondary node submits action credential T07. The verification node obtains the membership proof of T07 in the execution set and the non-member proof in the executed set. The verification node verifies the above proofs by combining the root values of the two authentication dictionaries. After confirming that T07 belongs to the execution set and not to the executed set, the verification node determines T07 as the target action credential. If T07 already exists in the executed set, the secondary node is not allowed to execute the proof-storage action represented by T07 again.
[0096] In one embodiment of this application, the set to be executed and the set already executed employ authentication dictionaries that allow direct comparison of root values. The verification node determines whether the credential identifiers contained in the two sets are identical by comparing the root values of the two authentication dictionaries.
[0097] It should be noted that, in order for the root values of the two authentication dictionaries to indicate whether the credential identifiers contained in the two sets are the same, in addition to using the same data structure, encoding rules, and credential identifier key, the same credential identifier also needs to use the same leaf node value in the two authentication dictionaries. In this embodiment, the leaf node value can be set to the canonical encoding of the credential identifier and the fixed existence mark; the action execution result and node signature are stored separately in the result tree or proof library.
[0098] Specifically, both authentication dictionaries use the same key space, tree depth, empty leaf values, digest algorithm, child node combination order, and leaf node encoding method, and both use the credential identifier as the key. Action credentials with the same credential identifier are located in the same position in both authentication dictionaries and have the same leaf node value. The corresponding leaf node in the "to be executed" set indicates that the action credential has been generated; the corresponding leaf node in the "executed" set indicates that the evidence storage action represented by the action credential has been executed. The action execution result, node signature, and trusted time are not written to the leaf nodes used for comparison to avoid different root values for the same credential identifier due to different additional data.
[0099] The verification node verifies whether the credential identifiers contained in the set to be executed are exactly the same as those contained in the already executed set, including: Step B1: Use the verification node to compare the root value of the authentication dictionary corresponding to the set to be executed with the root value of the authentication dictionary corresponding to the set already executed.
[0100] Specifically, the verification node obtains two root values associated with the same target electronic evidence, the same process identifier, the same action rule version, and the same final state snapshot. The verification node first verifies the digest algorithm and encoding rules used by the two root values, and then compares the two root values. If the two root values are different, the verification node can further request subtree proof to locate the credential identifiers that differ between the two sets.
[0101] Step B2: If the root value of the authentication dictionary corresponding to the set to be executed is the same as the root value of the authentication dictionary corresponding to the set already executed, determine that the credential identifier contained in the set to be executed is exactly the same as the credential identifier contained in the set already executed.
[0102] Specifically, assuming the comparability conditions are met and a collision-resistant digest algorithm is used, if the root values of the two authentication dictionaries are the same, it indicates that the two authentication dictionaries have the same leaf node distribution. Based on this, the verification node determines that every credential identifier in the execution set is recorded in the executed set, and that there are no valid credential identifiers in the executed set that were not generated by the execution set. The verification node can also check whether the termination action credential has been recorded in the executed set, avoiding comparisons of temporarily identical intermediate sets before the evidence storage process has terminated.
[0103] In this way, the verification node can transform the item-by-item comparison of the credential identifiers contained in the two sets into a comparison of two fixed-length root values, thereby reducing the amount of data that needs to be transmitted and processed during final-state verification.
[0104] For example, the notarization process of electronic contract E2001 generates twenty-three action credentials. After the termination action is completed, the root value corresponding to the set to be executed and the root value corresponding to the executed set are both 0x8A…31, and the two root values are associated with the same process final state snapshot. Based on this, the verification node determines that the twenty-three credentials contained in the two sets are completely identical, without having to download the twenty-three action credentials one by one.
[0105] In one embodiment of this application, both the authentication dictionary corresponding to the set to be executed and the authentication dictionary corresponding to the set already executed are implemented using sparse Merkle trees. When the two root values are different, the verification node locates the unexecuted credential identifier along the subtree with different digest values and determines the corresponding evidence storage action and function node.
[0106] Specifically, the sparse Merkle tree determines the path from the root node to the leaf node based on a fixed-length credential identifier. Leaf nodes without a credential identifier use a pre-determined default digest value. The digest value of an internal node is calculated from the digest values of its left and right child nodes in a fixed order. Since the path is determined only by the credential identifier, the same credential identifier corresponds to the same leaf node position in two sparse Merkle trees, allowing verification nodes to directly compare corresponding subtrees.
[0107] In one implementation, the results of the action execution are stored separately in a result tree. The leaf nodes in the result tree can be generated as follows: The result is: Leaf = H(TID ∥ Cout ∥ Snode) Wherein, TID represents the credential identifier, Cout represents the verification value of the action execution result, and Snode represents the signature of the functional node that performed the target evidence storage action. The result tree is used to verify the action execution result; the sparse Merkle tree corresponding to the set to be executed and the set already executed is used to verify whether the credential identifier set is closed.
[0108] Step C1: If the root values of the two authentication dictionaries are different, use the verification node to compare the digest values of the corresponding subtrees starting from the root nodes of the two sparse Merkle trees, and continue to compare the corresponding subtrees with different digest values until the unexecuted credential identifier recorded in the set to be executed but not recorded in the executed set is determined.
[0109] Specifically, the verification node first compares the summary values of the left and right subtrees corresponding to the two root nodes. Subtrees with the same summary value have the same leaf node distribution and are not expanded further; subtrees with different summary values continue to compare their next-level subtrees. The verification node repeats the above process until it reaches a leaf node and determines the credential identifier that is a non-empty leaf in the sparse Merkle tree corresponding to the set to be executed and an empty leaf in the sparse Merkle tree corresponding to the already executed set. The node maintaining the sparse Merkle tree can also provide corresponding path proofs, enabling the verification node to confirm that the compared subtrees do indeed belong to the two previously obtained root values.
[0110] The differential location process can utilize only credential identifiers, tree path summaries, and action metadata, without requiring the original electronic data of the target electronic evidence. Functional nodes holding detailed data can provide action credentials with the corresponding credential identifiers and action completion witnesses when needed.
[0111] Step C2: Based on the action credential corresponding to the unexecuted credential identifier, determine the unexecuted evidence storage action and the functional node used to execute the unexecuted evidence storage action.
[0112] Specifically, the verification node retrieves the corresponding action credential using the unexecuted credential identifier as an index, and verifies whether the credential identifier recalculated from the action credential is the same as the unexecuted credential identifier. Subsequently, the verification node reads the evidence storage action and function node represented by the action credential to determine the evidence storage action that has not yet been executed and the function node that should execute the evidence storage action. The verification node can also obtain the preceding actions and action rule entries associated with the action credential, which are used to explain which preceding evidence storage action generated the unexecuted action.
[0113] In one implementation, the verification node can also combine the result tree and action completion witness to identify other anomalies. For example, if the same credential identifier corresponds to two different action execution results, both of which have valid node signatures, it indicates that there is an execution conflict for the corresponding action; if the signature node of the action execution result is inconsistent with the functional node indicated by the action credential, it indicates that the corresponding action may have been executed without authorization; if the actual successor set lacks action credentials from the expected successor set, it indicates that the subsequent action credentials are not generated completely; if the actual successor set includes action credentials not specified by the action rules, it indicates that the subsequent action credentials were generated incorrectly.
[0114] In this way, the verification node can locate the specific unexecuted credential identifier when the root values of the two sets are different, and further determine the unexecuted evidence storage action and the corresponding functional node, instead of just outputting a general verification failure result.
[0115] For example, the verification node discovers that the two sparse Merkle tree root values corresponding to electronic contract E2001 are different. Starting from the root node, the verification node compares the corresponding subtrees with different digest values, eventually locating the credential identifier T17. The action credential corresponding to T17 represents "confirmation information that the secondary node has sent a saved receipt record to the source node." Based on this, the verification node determines that the confirmation action has not yet been executed and identifies the secondary node as the functional node for executing the action.
[0116] Please refer to the following: Figures 4-5 In one embodiment of this application, the multiple functional nodes further include a source node, a secondary node, and a primary node. The source node and secondary nodes are capable of acquiring the original electronic data included in the target electronic evidence. The source node saves and sends the original electronic data based on the target action credential, and then generates an original data processing credential to instruct the secondary node to continue processing. Steps D1 to D2 are located in... Figure 4 The source processing stage of the process shown.
[0117] Specifically, the target electronic evidence may include original electronic data such as electronic contract documents, electronic invoice documents, business database records, audio and video files, or data collected by devices. The source node can obtain the original electronic data from the business system that generated the original electronic data, the acquisition device, the file interface, or the database. The secondary node receives the original electronic data sent by the source node in subsequent step D2. Therefore, both the source node and the secondary node can obtain the original electronic data included in the target electronic evidence within their respective authorized environments, while the primary node does not obtain this original electronic data.
[0118] When a source node acquires raw electronic data, it can simultaneously obtain the data type, creation time, and business identifier, and check whether the file length, format identifier, or required fields are complete. The check results are used to determine whether the acquired data can be used as the original electronic data for the target electronic evidence. The source node can also set controlled storage locations and access permissions for the raw electronic data for subsequent saving and reading verification.
[0119] The target notarization action, represented by the target action credential, is executed using the functional node indicated by the target action credential, and an actual successor set is generated based on the action execution result, including: Step D1: When the target action credential instructs the source node to perform the target evidence storage action, the source node saves the original electronic data, generates the original data verification value based on the evidence identifier of the target electronic evidence and the original electronic data, and sends the original electronic data and the original data verification value to the secondary node.
[0120] Specifically, when the target evidence storage action represented by the target action credential is source-end data processing, and instructs the source node to execute the target evidence storage action, the source node writes the original electronic data included in the target electronic evidence into the controlled storage area. After writing is complete, the source node can reread the saved data and compare the read data with the written data to confirm that the original electronic data has been completely saved. If the saving or reading verification fails, the subsequent action credential corresponding to the successful branch will not be generated.
[0121] The source node, following the data range and digest algorithm specified in the action rules, uses the evidence identifier and original electronic data of the target electronic evidence as input to generate an original data verification value. The evidence identifier participates in the calculation, ensuring that the original data verification value corresponds to the specific target electronic evidence, preventing erroneous association of electronic data with identical content but different evidence identifiers. The source node can also add its signature and trusted time to the evidence identifier, original data verification value, and action rule version.
[0122] Subsequently, the source node sends the original electronic data and the original data verification value to the secondary node indicated by the target action credential. The data packet sent by the source node may also include evidence identifier, process identifier, source node signature, action rule version, and target action credential. The source node restricts the data packet to be received only by the corresponding secondary node through node identity verification and controlled communication channels. If network transmission times out, the same target action credential and the same data packet can be used for retrying without generating new original electronic data with different content.
[0123] Step D2: Generate the original data processing certificate using the source node, and use the original data processing certificate as the action certificate in the actual successor set; wherein, the original data processing certificate is used to instruct the secondary node to receive and process the original electronic data.
[0124] Specifically, the source node generates an original data processing certificate based on the action execution result formed in step D1. This original data processing certificate is associated with the evidence identifier of the target electronic evidence, the original data verification value, the action rule version, and the secondary node, indicating that the next evidence preservation action is received and processed by the secondary node from the original electronic data sent this time. The source node uses the original data processing certificate as the action certificate in the actual successor set.
[0125] The verification node determines the expected successor set based on the same action rules. When the actual successor set matches the expected successor set, the credential identifier of the target action credential corresponding to step D1 is written into the executed set, and the credential identifier of the original data processing credential is written into the to-be-executed set. Thus, the execution obligation of the secondary node to receive and process the original electronic data is generated by the preceding processing results of the source node.
[0126] In this way, the electronic evidence storage system links the original electronic data of the target electronic evidence, the original data verification value, and the subsequent processing obligations of the secondary nodes, so that the original electronic data obtained by the secondary nodes has a clear source and proof of the preceding actions.
[0127] For example, the source node obtains electronic contract M from the contract system and uses it as the original electronic data included in the target electronic evidence E2001. The source node saves electronic contract M, generates an original data verification value Cm2001 based on the evidence identifier of E2001 and electronic contract M, and then sends electronic contract M and Cm2001 to the secondary node. After sending, the source node generates an original data processing credential T05 and adds T05 to the actual successor set. After the verification node confirms that the actual successor set is consistent with the expected successor set, it writes the credential identifier of T05 into the execution set.
[0128] In one embodiment of this application, the secondary node verifies, saves, and converts the original electronic data based on the original data processing credentials, and sends the isolated data, corresponding checksum, and proof of origin to the primary node. The primary node then performs cross-domain verification. Steps E1 to E5 follow step D2.
[0129] It should be noted that isolated data can be understood as data generated by secondary nodes based on the original electronic data, preventing primary nodes from directly accessing the original electronic data. For example, isolated data can be complete ciphertext, field-level ciphertext, anonymized data, digest data packets, or encrypted indexes.
[0130] The target notarization action, represented by the target action credential, is executed using the functional node indicated by the target action credential, and an actual successor set is generated based on the action execution result, including: Step E1: When the target action voucher is the original data processing voucher, the secondary node generates a comparison verification value based on the received original electronic data, and compares the comparison verification value with the original data verification value.
[0131] Specifically, after the verification node identifies the original data processing credential as the target action credential, the secondary node obtains the original electronic data and original data verification value sent by the source node. The secondary node uses the same data range and digest algorithm as the source node to generate a comparison verification value based on the received original electronic data and the evidence identifier of the target electronic evidence. The secondary node compares the comparison verification value with the original data verification value to determine whether the received original electronic data is the same as the data used by the source node to generate the original data verification value.
[0132] Second-level nodes can also verify the target electronic evidence, action rule version, and source node signature associated with the original data processing voucher. If the verification value differs from the original data verification value, or if the original data processing voucher does not correspond to the current target electronic evidence, the second-level node will not execute the save and isolation conversion in the success branch. Instead, it will generate a resend voucher, a rejection voucher, or a manually reviewed voucher according to the action rules.
[0133] Step E2: If the verification value is the same as the original data verification value, the original electronic data is saved using the secondary node. The original electronic data is converted into isolated data that the primary node cannot directly obtain. The isolated data verification value and the proof of origin are generated based on the isolated data. The proof of origin is used to prove that the isolated data is converted from the original electronic data of the target electronic evidence.
[0134] Specifically, if the verification value matches the original data verification value, the secondary node saves the received original electronic data to its controlled storage area. The secondary node can reread the original electronic data after saving and confirm that the reread data still corresponds to the original data verification value. If the saving or reading verification fails, subsequent isolation conversion is not performed.
[0135] After successful saving, the secondary node converts the original electronic data of the target electronic evidence into isolated data according to the conversion method and parameters specified in the action rules. The conversion method can be overall encryption, field-level encryption, sensitive field desensitization, digest encapsulation, or encrypted indexing. The secondary node generates an isolated data verification value and a proof of origin based on the converted isolated data. The proof of origin links the evidence identifier of the target electronic evidence, the original data verification value, the isolated data verification value, the action rule version, and the conversion parameters, proving that the isolated data was converted from the original electronic data of the target electronic evidence.
[0136] Proof of same origin can be achieved using zero-knowledge proof of same origin, remote proof in a trusted execution environment, joint signature, hardware signature, verifiable encryption, or other methods capable of proving the aforementioned transformation relationship. Secondary nodes can also add secondary node signatures and trusted timestamps to the isolated data verification value and the proof of same origin to prevent the original proof of same origin from being used even if the isolated data is replaced.
[0137] Step E3: Use the secondary node to send isolated data, original data verification value, isolated data verification value and same-origin proof to the primary node to generate cross-domain verification certificate, and use the cross-domain verification certificate as the action certificate in the actual successor set.
[0138] Specifically, the secondary node sends cross-domain data packets to the primary node. These cross-domain data packets include isolated data, original data checksums, isolated data checksums, and proof of origin. They may also include the evidence identifier, process identifier, secondary node signature, trusted time, and action rule version of the target electronic evidence. The cross-domain data packets do not include the original electronic data, enabling the primary node to receive data and verification materials used for evidence preservation, but not to directly obtain the original electronic data.
[0139] The second-level node simultaneously generates a cross-domain verification credential. This credential instructs the first-level node to verify the received isolated data and its source relationship, and to associate it with the target electronic evidence, the two verification values, and the proof of common origin. The second-level node uses the cross-domain verification credential as an action credential in the actual successor set. After the verification node confirms that the actual successor set matches the expected successor set, the credential identifier of the cross-domain verification credential is written into the execution set. Therefore, the cross-domain verification credential constitutes the connection between the second-level node processing stage and the first-level node processing stage.
[0140] Step E4: When the target action credential is a cross-domain verification credential, the first-level node regenerates the verification value based on the received isolated data, compares the regenerated verification value with the isolated data verification value, and verifies whether the same-origin proof indicates that the isolated data was converted from the original electronic data of the target electronic evidence, thus obtaining the cross-domain verification result.
[0141] Specifically, once the cross-domain verification credential is identified as the target action credential, the first-level node regenerates the verification value based on the received isolation data and the data range and digest algorithm specified in the action rules. The first-level node then compares the regenerated verification value with the isolation data verification value sent by the second-level node to confirm whether the isolation data remains consistent before and after the cross-domain transmission.
[0142] The first-level node also utilizes the verification parameters corresponding to the same-origin proof to verify whether the evidence identifier, original data checksum, segregated data checksum, action rule version, and transformation parameters associated with the same-origin proof are consistent with the current target electronic evidence's storage process. The first-level node does not need to decrypt or read the original electronic data. The first-level node combines the checksum comparison result and the same-origin proof verification result into a cross-domain verification result. The cross-domain verification result may also include the verification results of the second-level node's signature and trusted time.
[0143] Step E5: If the cross-domain verification result characterization regenerated verification value is the same as the isolated data verification value and the same source proof characterization isolated data is converted from the original electronic data of the target electronic evidence, generate the actual successor set.
[0144] Specifically, when the cross-domain verification result indicates that the isolated data is identical before and after transmission, and the isolated data is indeed converted from the original electronic data of the target electronic evidence, the first-level node determines the execution status of the cross-domain verification action as successful, and generates an actual successor set based on the cross-domain verification result. The actual successor set may include successor action credentials used to generate the evidence verification value and the evidence request credential.
[0145] If the regenerated verification value differs from the isolated data verification value, or if the same-source proof fails to demonstrate that the isolated data and the original electronic data of the target electronic evidence have the aforementioned conversion relationship, then the first-level node will not generate the evidence storage request certificate corresponding to the successful branch, but will instead generate a resend certificate, a reconversion certificate, or a manual review certificate according to the action rules.
[0146] In this way, the secondary node first confirms that the original electronic data it receives is the same as the data sent by the source node, and then saves and converts the original electronic data; the primary node, without obtaining the original electronic data, uses two checksums and a proof of common origin to verify the integrity and source relationship of the isolated data. Thus, the isolated data after crossing domains can continue to maintain a verifiable correspondence with the original electronic data of the target electronic evidence.
[0147] For example, the secondary node receives the electronic contract M and the original data verification value Cm2001, and recalculates the comparison verification value, which is the same as Cm2001. The secondary node saves the electronic contract M, encrypts it to obtain isolated data C2001, and generates isolated data verification value Cc2001 and a same-origin proof W2001. The secondary node sends C2001, Cm2001, Cc2001, and W2001 to the primary node and generates a cross-domain verification credential T10. The primary node recalculates the verification value of C2001 and verifies W2001. After confirming that C2001 was converted from the original electronic data M of the electronic contract E2001, it generates the actual successor set leading to the third-party evidence storage stage.
[0148] In one embodiment of this application, the electronic evidence storage system is communicatively connected to a third-party evidence storage node. The primary node generates an evidence storage request based on the isolated data verification value and the cross-domain verification result; the third-party evidence storage node generates an evidence storage record and returns an evidence storage receipt; the primary node and the secondary node sequentially complete the verification, return, and recording of the evidence storage receipt. Steps F1 to F5 follow step E5.
[0149] It should be noted that the process of "generating a certificate verification value based on the isolated data verification value and the cross-domain verification result using the first-level node..." is, in terms of process sequence, a specific implementation of generating the actual successor set after successful cross-domain verification. The following explanation assumes that the certificate request credential is a successor credential to the cross-domain verification action.
[0150] Specifically, the electronic evidence storage system can pre-store the node identifier, interface address, certificate, verification public key, request format, and receipt format of the third-party evidence storage nodes. First-level nodes communicate with the third-party evidence storage nodes through corresponding communication interfaces. A third-party evidence storage node can be a single node, or multiple candidate nodes or parallel nodes as specified by the action rules. When using multiple third-party evidence storage nodes, the action rules further specify the target evidence storage node, the allowed evidence storage branches, and all subsequent action credentials for each branch.
[0151] Step F1: Utilize the primary node to generate a proof verification value based on the isolated data verification value and the cross-domain verification result, and generate a proof request credential that records the proof verification value. Use the proof request credential as the action credential in the actual successor set.
[0152] Specifically, the primary node uses the isolated data verification value and the cross-domain verification result as the basis for generating the evidence verification value. It can also incorporate the evidence identifier, action rule version, and third-party evidence storage node identifier of the target electronic evidence into the calculation. Therefore, the evidence verification value corresponds to both the isolated data in this instance and the result of the cross-domain verification already completed by the primary node. The primary node can add its signature and trusted time to the evidence verification value.
[0153] The primary node generates an evidence storage request credential containing the evidence storage verification value. This credential instructs the primary node to initiate an evidence storage request to the corresponding third-party evidence storage node and can be associated with the target electronic evidence, the primary node's signature, the action rule version, and the evidence storage strategy. The primary node uses the evidence storage request credential as the action credential in the actual successor set of cross-domain verification actions. After the verification node confirms that the actual successor set matches the expected successor set, it writes the credential identifier of the evidence storage request credential into the execution set.
[0154] The target notarization action, represented by the target action credential, is executed using the functional node indicated by the target action credential, and an actual successor set is generated based on the action execution result, including: Step F2: If the target action credential is a certificate of evidence storage request credential, use the first-level node to send a certificate of evidence storage request to the third-party certificate of evidence storage node, and receive the certificate of evidence storage receipt returned by the third-party certificate of evidence storage node after the certificate of evidence storage record is formed; wherein, the certificate of evidence storage receipt record contains the credential identifier of the certificate of evidence storage request credential and the certificate of evidence storage verification value.
[0155] Specifically, once the evidence storage request credential is identified as the target action credential, the primary node sends an evidence storage request to the third-party evidence storage node indicated by the credential. The evidence storage request may include the evidence storage request credential, the evidence storage verification value, the primary node's signature, the trusted time, and the evidence storage strategy, but does not include the original electronic data of the target electronic evidence. The primary node can use the credential identifier of the evidence storage request credential as a basis for identifying duplicate requests.
[0156] After receiving a notarization request, the third-party notarization node forms a trusted storage record, a blockchain-anchored record, or other verifiable notarization record based on the notarization verification value, and generates a notarization receipt. The notarization receipt record, or the notarization request credential identifier and notarization verification value linked cryptographically, can also record the third-party notarization identifier, recording time, and third-party node signature. Thus, the notarization receipt can establish a corresponding relationship with the current notarization request.
[0157] When a third-party evidence storage node is temporarily unavailable, the credential identifier of the evidence storage request credential remains in the execution set. First-level nodes can retry using the same evidence storage request credential and the same request data. Upon reaching the timeout condition specified in the action rules, the system can generate a backup third-party evidence storage credential, a delayed evidence storage credential, or a manually reviewed credential. The corresponding compensation path continues verification according to its expected successor set.
[0158] Step F3: Use the first-level node to compare the voucher identifier and verification value in the evidence storage receipt with the voucher identifier and verification value in the evidence storage request voucher. If both comparison results are the same, generate an receipt return voucher and use the receipt return voucher as the action voucher in the actual successor set.
[0159] Specifically, after obtaining the evidence storage receipt, the first-level node first verifies the third-party node's signature and receipt format, and then reads the voucher identifier and evidence storage verification value from the evidence storage receipt. The first-level node compares the voucher identifier in the evidence storage receipt with the voucher identifier of the current evidence storage request voucher, and compares the evidence storage verification value in the evidence storage receipt with the evidence storage verification value recorded in the current evidence storage request voucher. If both comparison results are the same, it is determined that the evidence storage receipt corresponds to the current evidence storage request.
[0160] The first-level node generates a receipt return voucher based on the above verification results and uses the receipt return voucher as the action voucher in the actual successor set. The receipt return voucher is used to instruct the first-level node to return the evidence storage receipt to the second-level node. If any comparison result is different, no receipt return voucher is generated for the successful branch, and the evidence storage request, evidence storage receipt, and comparison result are retained to locate problems such as misbinding or misuse of evidence storage receipts.
[0161] Step F4: If the target action credential is a receipt return credential, use the first-level node to return the evidence storage receipt to the second-level node, generate a receipt record credential, and use the receipt record credential as the action credential in the actual successor set.
[0162] Specifically, once the receipt return credential is identified as the target action credential, the first-level node sends the evidence storage receipt to the second-level node. The returned data packet may include the evidence storage receipt, the third-party node's signature, the receipt verification result, the receipt return credential, and the corresponding set root value. After verifying the identity of the first-level node, the evidence storage receipt, and the receipt return credential, the second-level node receives the evidence storage receipt.
[0163] The primary node generates a receipt record credential based on the action execution result of the returned evidence receipt. This receipt record credential instructs the secondary node to record the received evidence receipt and associate it with the target electronic evidence, the original data verification value, and the segregated data verification value. The primary node uses the receipt record credential as the action credential in the actual subsequent set. In the event of network transmission failure, the same receipt return credential and the same return data packet can be used for retry.
[0164] Step F5: When the target action credential is a receipt record credential, generate and save the receipt record using the secondary node; wherein, the receipt record is used to represent the correspondence between the evidence storage receipt, the target electronic evidence, the original data verification value, and the isolated data verification value; use the secondary node to send confirmation information to the source node to represent that the receipt record has been saved, and generate the actual successor set based on the receipt record.
[0165] Specifically, once the receipt record is identified as the target action credential, the secondary node generates a receipt record based on the evidence receipt, the evidence identifier of the target electronic evidence, the original data verification value, and the segregated data verification value. The receipt record may also include a process identifier, the credential identifier of the evidence request credential, the third-party evidence identification, the evidence storage time, and the third-party node's signature. The secondary node saves the receipt record and can reread it after saving to verify the record verification value, confirming that the receipt record has been completely saved.
[0166] The secondary node then sends a confirmation message to the source node. This confirmation message indicates that the aforementioned receipt record has been saved and may include the evidence identifier of the target electronic evidence, the receipt record verification value, the third-party evidence storage identifier, and the secondary node's signature. The source node can thus confirm that the original electronic data it provided has been used to create a corresponding evidence storage receipt record.
[0167] The secondary node also generates an actual successor set based on the saved receipt records. If it is necessary to continue generating actual reports, the actual successor set includes report generation credentials; if the action rules specify other subsequent actions, the actual successor set includes the corresponding action credentials. Specific verification is still performed according to steps S400 and S500.
[0168] In this way, the evidence storage receipt is first checked against the evidence storage request document and the evidence storage verification value. Then, the first-level node returns it to the second-level node, and the second-level node establishes the correspondence between the evidence storage receipt and the target electronic evidence, the original data verification value, and the isolated data verification value. This allows for the identification of situations such as the evidence storage receipt not matching the evidence storage request, the evidence storage receipt not being returned, or the receipt record not being established.
[0169] For example, the evidence request document corresponding to electronic contract E2001 is T13, and the evidence verification value is C2-2001. The third-party evidence storage node forms evidence storage record RID88 and returns evidence storage receipt R88, which records both T13 and C2-2001. After confirming that both contents are consistent with the evidence request document, the first-level node generates an receipt return document and returns R88 to the second-level node. The second-level node saves the receipt record representing the correspondence between R88, E2001, the original data verification value Cm2001, and the isolated data verification value Cc2001, then sends confirmation information to the source node and generates a report generation document. If the received evidence storage receipt is for another electronic contract, the document identifier or evidence verification value is inconsistent, and the report processing stage cannot be entered.
[0170] In one embodiment of this application, the secondary node generates a report generation certificate based on the receipt record and preset report rules, and then generates an electronic evidence report based on the certificate. The primary node verifies and processes the electronic evidence report, obtains the actual report, and returns it to the secondary node. Steps G1 to G6 follow step F5.
[0171] The target notarization action, represented by the target action credential, is executed using the functional node indicated by the target action credential, and an actual successor set is generated based on the action execution result, including: Step G1: Use the secondary node to generate a report generation certificate based on the receipt record and the preset report rules, and use the report generation certificate as the action certificate in the actual successor set; wherein, the preset report rules are used to specify the report content that the actual report should include, and the report generation certificate is used to instruct the secondary node to generate an electronic evidence report based on the receipt record.
[0172] Specifically, after the secondary node confirms that the receipt record has been saved, it reads the preset report rule corresponding to the target electronic evidence. The preset report rule specifies the report content that the actual report should include, such as the evidence identifier of the target electronic evidence, the original data verification value, the isolated data verification value, the evidence storage verification value, the third-party evidence storage identifier, the evidence storage time, the evidence storage receipt information, and the signature information. The preset report rule can also specify the report template version, the data source of each report content, and the functional nodes that need to perform signing processing.
[0173] The secondary node generates a report generation certificate based on the receipt record and preset reporting rules. The report generation certificate is associated with the target electronic evidence, the receipt record, and the preset reporting rules, and is used to instruct the secondary node to generate an electronic evidence report based on the receipt record. The secondary node uses the report generation certificate as the action certificate in the actual successor set described in step F5. The report generation certificate in the success branch is only generated when the evidence receipt represented by the receipt record correctly corresponds to the target electronic evidence and the two data verification values.
[0174] The target notarization action, represented by the target action credential, is executed using the functional node indicated by the target action credential, and an actual successor set is generated based on the action execution result, including: Step G2: If the target action credential is a report generation credential, use the secondary node to generate an electronic evidence report based on the receipt record, and add the secondary node signature to the electronic evidence report.
[0175] Specifically, once the report generation certificate is identified as the target action certificate, the secondary node retrieves the report content specified by the pre-defined reporting rules from the receipt record, action library, and proof library. Based on this report content, the secondary node generates an electronic evidence report and makes the electronic evidence report reference the target electronic evidence and its corresponding evidence receipt. The electronic evidence report can be a PDF file, other formatted files, a structured report, or a machine-verifiable data file.
[0176] Second-level nodes calculate the verification value of the electronic evidence report according to a preset report coding method and add their signature to the electronic evidence report or the verification value. The second-level node signature indicates that the electronic evidence report was generated by the second-level node based on the corresponding receipt record. Second-level nodes can also add trusted time and signature certificate information. If necessary receipt materials are missing, the preset report rule version does not match, or the second-level node signature is incomplete, the subsequent action certificate corresponding to the successful branch will not be generated.
[0177] Step G3: Use the secondary node to generate a report processing certificate and use the report processing certificate as the action certificate in the actual successor set; wherein, the report processing certificate is used to instruct the primary node to verify and sign the electronic evidence report.
[0178] Specifically, after the electronic evidence report is generated and a second-level node signature is added, the second-level node generates a report processing credential. This report processing credential is associated with the target electronic evidence, the verification value of the electronic evidence report, the second-level node signature, the evidence storage receipt, and the preset report rules, and designates the first-level node as the functional node to perform the corresponding report processing action. The second-level node uses the report processing credential as the action credential in the actual subsequent set.
[0179] Second-level nodes can assemble an electronic evidence report, the second-level node's signature, signature certificate materials, and report processing credentials into a report processing data packet and send it to the first-level node. In the event of a transmission failure, the second-level node will retry using the same report processing credentials and the same electronic evidence report to avoid electronic evidence reports with different content corresponding to the same credential identifier.
[0180] Step G4: If the target action credential is a report processing credential, use the first-level node to verify the signature of the second-level node in the electronic evidence report, and verify whether the electronic evidence and the evidence storage receipt cited in the electronic evidence report are the target electronic evidence and the evidence storage receipt, respectively.
[0181] Specifically, once the report processing credential is identified as the target action credential, the first-level node obtains the electronic evidence report and the second-level node's signature. The first-level node recalculates the verification value of the electronic evidence report according to the report encoding method used by the second-level node when generating the report verification value, and verifies the second-level node's signature against the second-level node's certificate to confirm that the report content is consistent with the content signed by the second-level node.
[0182] The first-level node also retrieves the evidence identifier, process identifier, third-party evidence storage identifier, evidence storage request voucher identifier, or evidence storage verification value cited in the electronic evidence report, and compares them with the current target electronic evidence and the evidence storage receipt obtained in step F2. If the evidence identifier cited in the electronic evidence report is the same as the evidence identifier of the target electronic evidence, and the evidence storage receipt cited in the report is the same as the evidence storage receipt obtained this time, the electronic evidence report is determined to correspond to the target electronic evidence and the evidence storage receipt. If the signature verification of the second-level node fails or the citation relationship is inconsistent, the successful report signing process is not executed.
[0183] Step G5: If the signature verification of the secondary node is successful and the electronic evidence and the evidence storage receipt cited in the electronic evidence report are the target electronic evidence and the evidence storage receipt, respectively, the primary node processes the electronic evidence report according to the preset reporting rules, and adds the primary node signature to the processed electronic evidence report to obtain the actual report.
[0184] Specifically, after both checks in step G4 pass, the first-level node reads the preset report rules associated with the report processing voucher and processes the electronic evidence report according to these preset report rules. For example, the first-level node can add evidence verification content, signature content, certificate verification materials, or other preset report content generated by the first-level node. The above processing is based on the preset report rules and does not change the correspondence between the target electronic evidence and the evidence receipt already referenced in the electronic evidence report.
[0185] After completing the processing, the primary node generates a report verification value based on the processed electronic evidence report and adds its signature to the processed electronic evidence report or the report verification value to obtain the actual report. The actual report, as a complete report object, can include multiple report contents specified by preset reporting rules within the same file or the same structured data packet. The primary node can also add trusted timestamps and primary node certificate materials to the actual report.
[0186] Step G6: Use the primary node to return the actual report to the secondary node, generate a report verification voucher, and use the report verification voucher as the action voucher in the actual successor set; wherein, the report verification voucher is used to instruct the secondary node to verify the actual report.
[0187] Specifically, the primary node returns the actual report obtained in step G5 to the secondary node. The returned data packet may include the actual report, the primary node's signature, the report verification value, the trusted time, and certificate materials. The primary node generates a report verification voucher based on the returned actual report. The report verification voucher is associated with the target electronic evidence, the actual report, the evidence storage receipt, the preset report rules, and the secondary node, and is used to instruct the secondary node to verify the actual report.
[0188] The primary node uses the report verification voucher as the action credential in the actual successor set. The verification node determines the expected successor set corresponding to the report processing action according to the action rules, and writes the voucher identifier of the report verification voucher into the execution set when the two successor sets are consistent. If the same report verification voucher corresponds to two actual reports with different content and both have valid primary node signatures, the electronic evidence storage system determines them as execution conflicts and does not select one report to overwrite the other.
[0189] In this way, the electronic evidence report is triggered by the receipt record corresponding to the target electronic evidence, and goes through the generation and signing of the second-level node, the verification and signing of the first-level node, and the return of the actual report. Thus, a verifiable correspondence is maintained between the actual report, the target electronic evidence, and the evidence receipt.
[0190] For example, the secondary node generates a report generation certificate T19 based on the receipt record corresponding to electronic contract E2001 and the preset report rule RR2, and generates an electronic evidence report referencing the evidence storage receipt R88 based on the receipt record. After adding its signature, the secondary node generates a report processing certificate and sends the electronic evidence report to the primary node. The primary node verifies the secondary node's signature and the E2001 and R88 referenced in the report, adds evidence storage verification content and the primary node's signature according to RR2, and obtains the actual report Report-2001. The primary node returns Report-2001 to the secondary node and generates a report verification certificate T22. If the electronic evidence report references another evidence storage receipt, the primary node does not successfully generate the actual report.
[0191] In one embodiment of this application, the secondary node verifies the actual report against the report verification certificate. When the actual report content is complete and the primary node's signature verification passes, the secondary node generates a download license certificate and a termination action certificate; the verification node executes the termination action and determines the empty set as the actual successor set. Steps H1 to H3 follow step G6, constituting the report processing stage and the termination part of the entire evidence storage process.
[0192] The target notarization action, represented by the target action credential, is executed using the functional node indicated by the target action credential, and an actual successor set is generated based on the action execution result, including: Step H1: If the target action credential is a report verification credential, use the secondary node to verify whether the actual report includes all the report content specified by the preset report rules, and verify the signature of the primary node in the actual report.
[0193] Specifically, once the report verification credential is identified as the target action credential, the secondary node determines all the report content that the actual report should include based on the preset reporting rules associated with that credential. The secondary node checks each item in the actual report, including the evidence identifier, original data checksum, isolated data checksum, evidence storage checksum, third-party evidence storage identifier, evidence storage time, evidence storage receipt information, and other content specified by the preset reporting rules. For actual reports in structured data packet format, the secondary node can also verify the file list and checksum of each file within the data packet.
[0194] The second-level node recalculates the checksum of the actual report using the report encoding method adopted by the first-level node when signing, and verifies the first-level node signature in the actual report using the first-level node certificate. The first-level node signature should correspond to the current actual report and the report content that needs to be confirmed by the first-level node. If the actual report lacks any specified content or the first-level node signature verification fails, the second-level node does not generate a download license certificate, but instead generates a report correction certificate or a failure handling certificate according to the action rules.
[0195] Step H2: If the actual report includes all report content and the signature verification of the first-level node is successful, a download license certificate is generated using the second-level node, and a termination action certificate is generated based on the download license certificate. The termination action certificate is used as the action certificate in the actual successor set. The download license certificate is used to indicate the actual report corresponding to the target electronic evidence, and the termination action certificate is used to instruct the verification node to perform the termination action.
[0196] Specifically, when the actual report includes all the report content stipulated in the preset reporting rules, and the signature verification of the first-level node passes, the second-level node generates a download license certificate. The download license certificate is associated with the evidence identifier of the target electronic evidence, the checksum of the actual report, the evidence storage receipt, and the preset reporting rules, and is used to instruct the electronic evidence storage system to provide the actual report corresponding to the target electronic evidence. The download license certificate may also include the scope of permission, validity conditions, and the signature of the second-level node. The download interface only provides the corresponding actual report after obtaining and verifying the download license certificate.
[0197] The second-level node then generates a termination action credential using the download license credential as a preceding result. This termination action credential is associated with the target electronic evidence, the actual report, and the download license credential, and the verification node is designated as the functional node to execute the termination action. The second-level node uses the termination action credential as the action credential in the actual successor set of the report verification action. After the verification node confirms that the actual successor set matches the expected successor set, it writes the credential identifier of the report verification credential into the executed set and the credential identifier of the termination action credential into the set to be executed.
[0198] Step H3: If the target action credential is a termination action credential, use the verification node to check whether the electronic evidence and report indicated by the download license credential are the target electronic evidence and the actual report, respectively. If the electronic evidence and report indicated by the download license credential are the target electronic evidence and the actual report, the empty set is determined as the actual successor set.
[0199] Specifically, once the termination action credential is identified as the target action credential, the verification node obtains the download license credential referenced by the termination action credential. The verification node compares the evidence identifier in the download license credential with the evidence identifier of the target electronic evidence, and verifies whether the report indicated by it is the actual report obtained in step G5 based on the report verification value in the download license credential. The verification node can also verify the process identifier, evidence storage receipt, and secondary node signature in the download license credential to prevent download license credentials of other target electronic evidence or other evidence storage processes from being used in the current process.
[0200] When the electronic evidence indicated by the download license credential is the target electronic evidence, and the report it indicates is the actual report, the verification node determines that no new action credential will be generated after terminating the action according to the action rules. Therefore, the verification node determines the empty set as the actual successor set. Since the expected successor set corresponding to the termination action is also empty, the two successor sets are consistent, and the credential identifier of the termination action credential is written into the executed set. The verification node then compares the to-be-executed set with the executed set according to steps S600 and S700, and forms a conclusion on the completeness of the evidence for the target electronic evidence.
[0201] Thus, the download license is generated only when the actual report content is complete and the signature verification at the first-level node is successful, and the termination action certificate is associated with the target electronic evidence, the actual report, and the download license. Therefore, the electronic evidence storage system cannot prematurely terminate the storage process based solely on ordinary statuses such as "report generated" or "download allowed."
[0202] For example, after the secondary node obtains the actual report Report-2001, it verifies all report content according to the preset reporting rule RR2 and verifies the primary node's signature. Upon successful verification, the secondary node generates a download license credential Td2001 that only indicates the electronic contracts E2001 and Report-2001, and then generates a termination action credential T23. After the verification node confirms that the electronic evidence and report indicated by Td2001 are E2001 and Report-2001 respectively, it determines the empty set as the actual successor set and writes the credential identifier of T23 into the executed set. Subsequently, the verification node compares the to-be-executed set and the executed set; if the two sets are the same, it outputs a "complete" verification conclusion.
[0203] The following is an overall example that integrates the above-described embodiments: Taking the evidence preservation process of an enterprise's electronic procurement contract as an example: The source node obtains the original contract document M from the contract system and identifies it as the target electronic evidence. The electronic evidence preservation system assigns evidence identifier E3001 and process identifier P3001 to the target electronic evidence, obtains action rule R5, and the corresponding execution set and executed set. Based on action rule R5, the system generates an initial action credential for the source node to perform original electronic data processing and writes the credential identifier of this credential into the execution set.
[0204] After confirming that the initial action credential has been recorded in the "to be executed" set but not yet in the "already executed" set, the verification node identifies it as the target action credential. The source node saves the original contract file M, generates the original data verification value Cm3001 based on the evidence identifier E3001 and the original contract file M, and sends the original contract file M and Cm3001 to the secondary nodes. The source node generates the original data processing credential based on the transmission result. After confirming that the credential belongs to all the successors specified in the action rules, the verification node writes the current credential identifier into the "already executed" set and writes the credential identifier of the original data processing credential into the "to be executed" set.
[0205] The secondary node receives the original contract file M based on the original data processing voucher, generates a comparison check value, and compares it with Cm3001. If they match, the secondary node saves the original contract file M, encrypts it to obtain isolated data C3001, and generates an isolated data check value Cc3001 and a same-origin proof W3001. The secondary node sends C3001, Cm3001, Cc3001, and W3001 to the primary node, and simultaneously generates a cross-domain verification voucher. The primary node recalculates the check value of C3001 and verifies W3001, confirming that C3001 was converted from the original contract file M of the target electronic evidence E3001.
[0206] The primary node generates a verification value C2-3001 and a verification request credential T13 based on Cc3001 and the cross-domain verification result, and sends the verification request to the third-party verification node. The third-party verification node forms a verification record RID3001 and returns a verification receipt R3001. R3001 records the credential identifier of T13 and C2-3001. The primary node compares the credential identifier and verification value in R3001 with the corresponding contents in T13. If both are the same, the primary node returns R3001 to the secondary node and generates a receipt record credential.
[0207] The secondary node saves the receipt record representing the correspondence between R3001, E3001, Cm3001, and Cc3001 based on the receipt record voucher, and sends a confirmation message to the source node that the receipt record has been saved. Subsequently, the secondary node generates a report generation voucher based on the receipt record and preset reporting rules, and generates an electronic evidence report and a secondary node signature based on the voucher. The primary node verifies the secondary node signature, the target electronic evidence E3001, and the evidence storage receipt R3001, processes and signs the electronic evidence report according to the preset reporting rules, obtains the actual report Report-3001, and then returns Report-3001 to the secondary node.
[0208] The secondary node verifies whether Report-3001 includes all report content specified in the preset reporting rules and checks the primary node's signature. Upon successful verification, the secondary node generates a download license credential Td3001 and a termination action credential T23. The verification node confirms that the electronic evidence and report indicated by Td3001 are E3001 and Report-3001 respectively, designates the empty set as the actual successor set, and writes the credential identifier of T23 into the executed set. Finally, the verification node compares the to-be-executed set and the executed set. If the credential identifiers in both sets are identical, the verification node determines that all evidence preservation actions required according to action rule R5 in the evidence preservation process of the target electronic evidence E3001 have been executed.
[0209] If a secondary node fails to send confirmation information that the acknowledgment record has been saved to the source node, the credential identifier of the corresponding action credential will still be recorded in the "to be executed" set, but not in the "executed" set. Even if an actual report has been generated, the two sets will still be different, allowing the verification node to determine that the evidence storage process is incomplete and to locate the missing secondary node action.
[0210] Please see Figure 6This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. A third aspect of this application provides an electronic device 1000, including a processor 1100 and a memory 1200. The memory 1200 stores machine-executable instructions that can be executed by the processor 1100. The processor 1100 can execute the machine-executable instructions to implement the aforementioned method for verifying the completeness of electronic evidence storage. The number of electronic devices 1000 can be single or multiple (distributed electronic device cluster).
[0211] A fourth aspect of this application provides a machine-readable storage medium storing instructions that, when executed by a processor, cause the processor to implement the above-described method for verifying the completeness of electronic evidence storage.
[0212] In some embodiments, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the electronic evidence preservation completeness verification method according to the above embodiments.
[0213] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0214] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 The computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1The functions specified in one or more boxes. These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable apparatus for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.
[0215] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.
[0216] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.
[0217] Computer-readable media include both permanent and non-permanent, removable and non-removable media that can store information by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media do not include temporary computer-readable media, such as modulated data signals and carrier waves.
[0218] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.
[0219] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.
[0220] Furthermore, various different embodiments of the present invention can be combined in any way, as long as they do not violate the spirit of the present invention, they should also be regarded as the content disclosed by the present invention.
Claims
1. A method for verifying the completeness of electronic evidence storage, characterized in that, The method is applied to an electronic evidence storage system, which includes multiple functional nodes, including a verification node. The method includes: The action rules, execution set, and execution set corresponding to the target electronic evidence are obtained. An initial action credential is generated according to the action rules, and the credential identifier of the initial action credential is recorded in the execution set. The action credential is used to characterize the evidence preservation action to be performed and the functional node for performing the evidence preservation action. The execution set is used to accumulate and record the credential identifiers of the generated action credentials. The execution set is used to accumulate and record the credential identifiers corresponding to the executed evidence preservation actions. The verification node is used to determine the target action credential whose credential identifier is recorded in the set to be executed but not in the set already executed; The target evidence storage action represented by the target action credential is executed by the functional node indicated by the target action credential, and an actual successor set is generated based on the action execution result; wherein, the actual successor set includes the successor action credential generated by the functional node after executing the target evidence storage action, and the action execution result includes at least one of the execution status and action output of the target evidence storage action; Using the verification node, the expected set of successors for the target evidence storage action is determined according to the action rules; wherein, the expected set of successors includes all successor action credentials generated after the execution of the target evidence storage action as specified by the action rules; If the actual successor set matches the expected successor set, the credential identifier of the target action credential is recorded in the executed set, and the credential identifier of each action credential in the actual successor set is recorded in the to-be-executed set. When the credential identifier of the termination action credential specified in the action rule has been recorded in the executed set, the verification node is used to verify whether the credential identifier contained in the to be executed set is exactly the same as the credential identifier contained in the executed set. If the credential identifiers contained in the set to be executed are exactly the same as those contained in the set to be executed, it is determined that all evidence preservation actions that should be performed according to the action rules in the evidence preservation process of the target electronic evidence have been performed.
2. The method according to claim 1, characterized in that, The set to be executed and the set already executed are stored using an authentication dictionary, which is a data structure that generates root values based on the stored credential identifiers. The step of using the verification node to determine the target action credential whose credential identifier is recorded in the set to be executed but not in the set already executed includes: Obtain the credential identifier of the action credential to be determined, and use the credential identifier of the action credential to be determined as the credential identifier to be determined; Obtain the membership proof of the credential identifier to be determined in the execution set, the non-membership proof of the credential identifier to be determined in the execution set, and the root values of the authentication dictionary corresponding to the execution set and the authentication dictionary corresponding to the execution set, respectively; Using the verification node, based on the root value of the authentication dictionary corresponding to the execution set, the credential identifier to be determined, and the membership proof, it is verified whether the credential identifier to be determined belongs to the execution set. Using the verification node, based on the root value of the authentication dictionary corresponding to the executed set, the credential identifier to be determined, and the non-membership proof, it is verified whether the credential identifier to be determined does not belong to the executed set. If the credential identifier to be determined belongs to the set to be executed but not to the set already executed, the credential to be determined is determined as the target action credential.
3. The method according to claim 1, characterized in that, The set to be executed and the set already executed are stored using an authentication dictionary. The authentication dictionary is a data structure that generates root values based on the stored credential identifiers. The authentication dictionary corresponding to the set to be executed and the authentication dictionary corresponding to the set already executed use the same data structure and encoding rules, and both use the credential identifier as the key. The step of verifying whether the credential identifiers contained in the set to be executed are exactly the same as those contained in the set already executed includes: The root value of the authentication dictionary corresponding to the set to be executed is compared with the root value of the authentication dictionary corresponding to the set that has already been executed using the verification node; If the root value of the authentication dictionary corresponding to the set to be executed is the same as the root value of the authentication dictionary corresponding to the set already executed, it is determined that the credential identifier contained in the set to be executed is exactly the same as the credential identifier contained in the set already executed.
4. The method according to claim 3, characterized in that, Both the authentication dictionary corresponding to the set to be executed and the authentication dictionary corresponding to the set already executed are implemented using sparse Merkle trees. The method further includes: If the root value of the authentication dictionary corresponding to the set to be executed is different from the root value of the authentication dictionary corresponding to the set to be executed, the verification node is used to start from the root node of the sparse Merkle tree corresponding to the set to be executed and the sparse Merkle tree corresponding to the set to be executed, compare the digest values of the corresponding subtrees, and continue to compare the corresponding subtrees with different digest values until the unexecuted credential identifier recorded in the set to be executed but not recorded in the set to be executed is determined. Based on the action credential corresponding to the unexecuted credential identifier, determine the unexecuted evidence storage action and the functional node used to execute the unexecuted evidence storage action.
5. The method according to claim 1, characterized in that, The plurality of functional nodes also include source nodes, secondary nodes, and primary nodes; the source nodes and the secondary nodes are used to acquire the original electronic data included in the target electronic evidence; The step of executing the target evidence storage action represented by the target action credential using the functional node indicated by the target action credential, and generating an actual successor set based on the action execution result, includes: When the target action credential instructs the source node to perform the target evidence storage action, the source node saves the original electronic data, generates an original data verification value based on the evidence identifier of the target electronic evidence and the original electronic data, and sends the original electronic data and the original data verification value to the secondary node. The source node is used to generate an original data processing certificate, and the original data processing certificate is used as the action certificate in the actual successor set. The original data verification value is used to verify whether the original electronic data held by different nodes are the same; the original data processing certificate is used to instruct the secondary node to receive and process the original electronic data.
6. The method according to claim 5, characterized in that, The step of executing the target evidence storage action represented by the target action credential using the functional node indicated by the target action credential, and generating an actual successor set based on the action execution result, includes: When the target action credential is the original data processing credential, the secondary node generates a comparison verification value based on the received original electronic data, and compares the comparison verification value with the original data verification value. If the comparison check value is the same as the original data check value, the original electronic data is stored using the secondary node, and the original electronic data is converted into isolated data that the primary node cannot directly obtain. An isolated data check value and a proof of origin are generated based on the isolated data. The proof of origin is used to prove that the isolated data is converted from the original electronic data of the target electronic evidence. The second-level node sends the isolated data, the original data verification value, the isolated data verification value, and the same-origin proof to the first-level node to generate a cross-domain verification credential, and uses the cross-domain verification credential as the action credential in the actual successor set; When the target action credential is the cross-domain verification credential, the first-level node regenerates the verification value based on the received isolated data, compares the regenerated verification value with the isolated data verification value, and verifies whether the same-origin proof indicates that the isolated data was converted from the original electronic data of the target electronic evidence, thereby obtaining the cross-domain verification result. The actual successor set is generated when the cross-domain verification result indicates that the regenerated verification value is the same as the isolated data verification value and the same-origin proof indicates that the isolated data was converted from the original electronic data of the target electronic evidence.
7. The method according to claim 6, characterized in that, The electronic evidence storage system is connected to a third-party evidence storage node. The method further includes: The primary node generates a proof verification value based on the isolated data verification value and the cross-domain verification result, and generates a proof request credential that records the proof verification value, and uses the proof request credential as the action credential in the actual successor set. The step of executing the target evidence storage action represented by the target action credential using the functional node indicated by the target action credential, and generating an actual successor set based on the action execution result, includes: When the target action credential is the evidence storage request credential, the first-level node sends an evidence storage request to the third-party evidence storage node and receives an evidence storage receipt returned by the third-party evidence storage node after forming an evidence storage record; wherein, the evidence storage receipt records the credential identifier of the evidence storage request credential and the evidence storage verification value. The primary node is used to compare the voucher identifier and the verification value in the evidence storage receipt with the voucher identifier and the verification value in the evidence storage request voucher, respectively. If both comparison results are the same, an receipt return voucher is generated and the receipt return voucher is used as the action voucher in the actual successor set. When the target action credential is the receipt return credential, the first-level node returns the evidence receipt to the second-level node to generate a receipt record credential, and the receipt record credential is used as the action credential in the actual successor set. When the target action credential is the receipt record credential, the receipt record is generated and saved using the secondary node; wherein, the receipt record is used to represent the correspondence between the evidence storage receipt, the target electronic evidence, the original data verification value, and the isolated data verification value; The secondary node sends confirmation information to the source node to indicate that the receipt record has been saved, and generates the actual successor set based on the receipt record.
8. The method according to claim 7, characterized in that, The step of generating the actual successor set based on the receipt record includes: The secondary node generates a report generation certificate based on the receipt record and preset report rules, and uses the report generation certificate as an action certificate in the actual successor set; wherein, the preset report rules are used to specify the report content that the actual report should include, and the report generation certificate is used to instruct the secondary node to generate an electronic evidence report based on the receipt record; The step of executing the target evidence storage action represented by the target action credential using the functional node indicated by the target action credential, and generating an actual successor set based on the action execution result, includes: When the target action credential is the report generation credential, the electronic evidence report is generated using the secondary node based on the receipt record, and a secondary node signature is added to the electronic evidence report. The secondary node generates a report processing certificate, which is then used as an action certificate in the actual successor set; wherein, the report processing certificate is used to instruct the primary node to verify and sign the electronic evidence report; When the target action credential is the report processing credential, the first-level node is used to verify the signature of the second-level node in the electronic evidence report, and to verify whether the electronic evidence and the evidence storage receipt referenced in the electronic evidence report are the target electronic evidence and the evidence storage receipt, respectively. If the signature verification of the secondary node is successful and the electronic evidence and the evidence storage receipt referenced in the electronic evidence report are the target electronic evidence and the evidence storage receipt, respectively, the electronic evidence report is processed by the primary node according to the preset report rules, and the primary node signature is added to the processed electronic evidence report to obtain the actual report. The primary node returns the actual report to the secondary node, generates a report verification voucher, and uses the report verification voucher as an action voucher in the actual successor set; wherein, the report verification voucher is used to instruct the secondary node to verify the actual report.
9. The method according to claim 8, characterized in that, The step of executing the target evidence storage action represented by the target action credential using the functional node indicated by the target action credential, and generating an actual successor set based on the action execution result, includes: When the target action credential is the report verification credential, the secondary node is used to verify whether the actual report includes all the report content specified by the preset report rules, and to verify the signature of the primary node in the actual report; If the actual report includes all the report content and the signature verification of the first-level node is successful, a download license certificate is generated using the second-level node, and a termination action certificate is generated based on the download license certificate. The termination action certificate is used as the action certificate in the actual successor set. The download license certificate is used to indicate that the actual report corresponding to the target electronic evidence can be obtained, and the termination action certificate is used to instruct the verification node to perform a termination action. When the target action credential is the termination action credential, the verification node is used to check whether the electronic evidence and report indicated by the download license credential are the target electronic evidence and the actual report, respectively. If the electronic evidence and report indicated by the download license credential are the target electronic evidence and the actual report, the empty set is determined as the actual successor set.
10. An electronic device, characterized in that, It includes a processor and a memory, the memory storing programs or instructions that can run on the processor, the programs or instructions being executed by the processor to implement the electronic evidence preservation completeness verification method as described in any one of claims 1-9.
