An epr supply chain inventory data management method and system

Abstract

This invention relates to the field of data management technology, specifically to an EPR supply chain inventory data management method and system. The method includes: receiving an update instruction for original inventory information; identifying the inventory information to be updated using an inventory master information database; modifying the value field of the inventory information to be updated to obtain modified inventory information; temporarily storing and marking the modified inventory information to obtain temporary information in a pending-submission marked state; confirming the aggregate hash value of the temporary information in the pending-submission marked state and digitally signing the aggregate hash value to generate an operation intent credential; and replacing the corresponding original inventory information in the inventory master information database with the temporary information in the pending-submission marked state based on the operation intent credential to obtain a replaced inventory master information database. The purpose of this invention is to solve the problem that existing technologies cannot provide reliable and verifiable operation credentials, leading to low collaboration efficiency and trust in the supply chain.

Description

Technical Field

[0001] This invention relates to the field of data management technology, specifically to an EPR supply chain inventory data management method and system. Background Technology

[0002] Under the Extended Producer Responsibility (EPR) framework, the management of inventory information for high-value recycled parts is affected by market conditions, requiring frequent and comprehensive adjustments to inventory information. While existing data encryption management methods can ensure the confidentiality of data throughout its entire lifecycle, in a distributed processing environment, if a batch value update operation is performed on a large amount of original inventory information and the update process is unexpectedly interrupted, it may lead to inconsistencies in the internal logical value of the data. For example, some information may have been updated to the new value, while others may retain the old value, thus creating a physically secure but logically contradictory dataset.

[0003] Furthermore, without fully decrypting the original information or revealing irrelevant specific values, how to provide downstream partners in the supply chain with a credible certificate proving that a specific value update operation has been correctly and completely executed across all relevant information, thereby maintaining the overall trust foundation of the supply chain, is a critical issue that urgently needs to be addressed in the current technological field. Existing technologies struggle to effectively address data inconsistencies caused by update interruptions and cannot provide credible and verifiable operational certificates, resulting in low collaboration efficiency and trust levels within the supply chain. Summary of the Invention

[0004] The purpose of this invention is to provide an EPR supply chain inventory data management method and system to solve the problem that existing technologies cannot provide reliable and verifiable operational credentials, resulting in low collaboration efficiency and trust in the supply chain.

[0005] To achieve the above objectives, the present invention adopts the following technical solution: an EPR supply chain inventory data management method, comprising:

[0006] After receiving the update instruction for the original inventory information, the inventory master information database is used to identify the inventory information to be updated;

[0007] Modify the value field of the inventory information to be updated to obtain the modified inventory information;

[0008] The modified inventory information is temporarily stored and marked to obtain temporary information in the pending submission and marking state;

[0009] Confirm the aggregated hash value of the temporary information of the pending submission mark status, and digitally sign the aggregated hash value to generate an operation intent credential;

[0010] Based on the operation intent certificate, the temporary information of the pending submission mark status is replaced with the corresponding original inventory information in the inventory master information database to obtain the replaced inventory master information database.

[0011] Furthermore, this application also proposes a step of confirming the aggregated hash value of the temporary information of the pending submission mark status, and digitally signing the aggregated hash value to generate an operation intent credential, including:

[0012] Identify the value portion to be modified and the value portion that remains unchanged in the temporary information of the pending submission mark state;

[0013] Confirm the first aggregate hash value of the value portion to be modified, and confirm the second aggregate hash value of the value portion that remains unchanged;

[0014] After digitally signing the first aggregated hash value and the second aggregated hash value respectively, an operation intent credential is generated.

[0015] Furthermore, this application also proposes a step of confirming the aggregated hash value of the temporary information of the pending submission mark status, and digitally signing the aggregated hash value to generate an operation intent credential, which further includes:

[0016] When the generation of the operation intent certificate is interrupted, a recovery operation identifier is generated corresponding to the stored inventory information and the temporary information of the interrupted pending submission mark status.

[0017] Based on the stored inventory information and recovery operation identifier, generate audit records for updated inventory information and audit records associated with the recovery operation identifier;

[0018] Based on the audit records associated with the updated inventory information and the recovery operation identifier, the aggregated hash value is confirmed, and the aggregated hash value is digitally signed to generate an operation intent credential.

[0019] Furthermore, this application also proposes a step of temporarily storing and marking the modified inventory information to obtain temporary information in a pending-submission marking state, including:

[0020] The modified inventory information is subjected to a security-level sharing process to obtain multiple secret share information.

[0021] The multiple secret share information is distributed and stored in the storage nodes of the intention temporary storage area, and the inventory information corresponding to each secret share is marked as temporary information in the pending submission mark state.

[0022] Furthermore, this application also proposes a step of identifying the inventory information to be updated using the inventory master information database after receiving the update instruction for the original inventory information, including:

[0023] Upon receiving an update instruction for the original inventory information, non-sensitive information for identification is extracted from the original inventory information, and the non-sensitive information is converted into metadata that can be queried.

[0024] Using preset filtering conditions in the inventory master information database, perform a query operation on the metadata to determine the original inventory information to be updated that meets the filtering conditions;

[0025] The original inventory information to be updated is decrypted to obtain the inventory information to be updated.

[0026] Furthermore, this application also proposes that after the step of replacing the corresponding original inventory information in the inventory master database with the temporary information of the pending submission mark based on the operation intent certificate to obtain the replaced inventory master database, it further includes:

[0027] Confirm the first verification value of the temporary information of the pending submission mark status, and confirm the second verification value of the temporary information of the pending submission mark status in the replaced inventory master information database;

[0028] Compare the first check value and the second check value to obtain the check value comparison result;

[0029] If the checksum comparison result indicates that the first checksum and the second checksum are the same, then the checksum comparison result is stored in the audit log;

[0030] If the verification value comparison result indicates that the first verification value and the second verification value are inconsistent, then based on the operation intention certificate, the temporary information of the pending submission mark status is used to replace the corresponding original inventory information in the inventory master information database to obtain the replaced inventory master information database.

[0031] Furthermore, this application also proposes a step of generating an operation intent credential after digitally signing the first aggregated hash value and the second aggregated hash value respectively, including:

[0032] Based on the first aggregated hash value and the second aggregated hash value, a hierarchical hash structure is constructed for the temporary storage information of the pending submission mark status;

[0033] A hierarchical hash structure of the temporary information of the pending submission mark state is digitally signed to generate an initial credential of operation intent;

[0034] Based on the modified inventory information, the affected node hash values ​​in the hierarchical hash structure are re-determined to obtain a new root hash value;

[0035] Based on the new root hash value and the preset voucher version identifier, generate a new voucher containing the operation intent, which includes the new root hash value and the voucher version identifier;

[0036] The new credential containing the stated operational intent is digitally signed;

[0037] Associate the new operation intent certificate with the initial operation intent certificate to generate an operation intent certificate.

[0038] Furthermore, this application also proposes that after the step of associating the new operation intent credential with the initial operation intent credential to generate the operation intent credential, it further includes:

[0039] Based on the new credential of the operation intent and the initial credential of the operation intent, replacement event information is generated;

[0040] The replacement event information is recorded in the preset distributed ledger data, and the replaced distributed ledger data is confirmed;

[0041] Provides a query port for the validity status of the replaced distributed ledger data.

[0042] Furthermore, this application also proposes a step for decrypting the original inventory information to be updated to obtain the inventory information to be updated, including:

[0043] After processing the original inventory information to be updated in batches, the original inventory information to be updated in each batch is decrypted to obtain the decrypted inventory information corresponding to each batch.

[0044] The decrypted inventory information for each batch is summarized to obtain the inventory information to be updated.

[0045] This application also proposes an EPR supply chain inventory data management system, including:

[0046] The identification module is used to identify the inventory information to be updated using the inventory master information database after receiving the update instruction for the original inventory information.

[0047] The modification module is used to modify the value field of the inventory information to be updated, thereby obtaining the modified inventory information.

[0048] The processing module is used to temporarily store and mark the modified inventory information to obtain temporary information in the marked state to be submitted.

[0049] The confirmation module is used to confirm the aggregated hash value of the temporary information of the pending submission mark status, and to digitally sign the aggregated hash value to generate an operation intent credential.

[0050] The replacement module is used to replace the corresponding original inventory information in the inventory master information database with the temporary information of the pending submission mark status based on the operation intention certificate, so as to obtain the replaced inventory master information database.

[0051] Compared with existing technologies, the EPR supply chain inventory data management method and system of the present invention have the following advantages:

[0052] This invention identifies the inventory information requiring updating when it receives an update instruction for the original inventory information, utilizing the inventory master information database. After identification, the value fields of these inventory information items to be updated are precisely modified to obtain the modified inventory information. The modified inventory information is not immediately written to the master information database but is temporarily stored and marked, forming temporary information in a pending-submission marked state. The aggregate hash value of the temporary information in the pending-submission marked state is further confirmed. The aggregate hash value, as a unique digital fingerprint of all data content to be updated, efficiently reflects the overall state of the data. This aggregate hash value is digitally signed to generate an operation intent credential. This not only includes proof of data integrity but also ensures the authenticity and non-repudiation of the operation through digital signing. Even if the update process is interrupted, the completed operation intent can be traced and verified through this credential. Based on the generated authoritative operation intent credential, the temporary information in the pending-submission marked state replaces the corresponding original inventory information in the inventory master information database. This ensures that only verified and signed updates ultimately take effect. The resulting replaced inventory master information database contains all updated value information. This avoids data inconsistencies caused by batch update interruptions and provides credible audit evidence to external parties through credentials, thereby improving the efficiency and trust of supply chain collaboration. Attached Figure Description

[0053] To more clearly illustrate the specific embodiments of the present invention, the accompanying drawings used in the specific embodiments will be briefly described below. In all the drawings, the elements or parts are not necessarily drawn to scale.

[0054] Figure 1 This is a flowchart of an EPR supply chain inventory data management method according to the present invention.

[0055] Figure 2 This is a structural block diagram of an EPR supply chain inventory data management system according to the present invention.

[0056] In the diagram: 210, Identification module; 220, Modification module; 230, Processing module; 240, Confirmation module; 250, Replacement module.

[0057] The implementation and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0058] The following drawings disclose several embodiments of the present invention. For clarity, many practical details will be described in the following description. However, it should be understood that these practical details are not intended to limit the invention. That is, in some embodiments of the invention, these practical details are not essential. Furthermore, for the sake of simplicity, some conventional structures and components will be shown in the drawings in a simple schematic manner.

[0059] It should be noted that all directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of the present invention are only used to explain the relative positional relationship and movement of each component in a certain specific posture (as shown in the figure). If the specific posture changes, the directional indication will also change accordingly.

[0060] Furthermore, in this invention, the use of terms such as "first" and "second" is for descriptive purposes only and does not specifically refer to any order or sequence, nor is it intended to limit the invention. They are merely used to distinguish components or operations described using the same technical terms, and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include at least one of those features. Additionally, the technical solutions of various embodiments can be combined with each other, but only if they are feasible for those skilled in the art. If a combination of technical solutions is contradictory or impossible to implement, such a combination should be considered nonexistent and not within the scope of protection claimed by this invention.

[0061] To further understand the content, features, and effects of this invention, the following embodiments are provided, and detailed descriptions are given below in conjunction with the accompanying drawings:

[0062] Please see Figure 1 This invention provides an EPR supply chain inventory data management method, comprising the following steps:

[0063] S100: After receiving the update instruction for the original inventory information, identify the inventory information to be updated using the inventory master information database. The inventory master information database is a centralized or distributed database that stores the original inventory information of all high-value recycled parts in the EPR supply chain. It can be implemented using relational databases, non-relational databases, or distributed ledger technologies, such as MySQL, MongoDB, or blockchain networks. Its main purpose is to achieve centralized management and efficient querying of inventory data, serving as the fundamental source of all inventory information.

[0064] S200. Modify the value field of the inventory information to be updated to obtain the modified inventory information. The value field is a specific data item in the inventory information used to record the economic value of high-value recycled items. It can be implemented using numeric, floating-point, or encrypted numeric data formats, such as numbers representing monetary amounts or percentages representing estimated values. Its main purpose is to reflect the market value or subsidy value of recycled items and to support subsequent value update operations.

[0065] S300. The modified inventory information is temporarily stored and marked to obtain temporary information in the pending-commit status. The temporary storage and marking process involves temporarily storing the modified inventory information in an independent area and attaching a status identifier to it. This can be implemented using memory caching, temporary file storage, or a dedicated temporary storage database. For example, data can be written to a temporary buffer and set to a "pending commit" status bit. This primarily provides a buffer and verification phase before the data is officially written to the main database, ensuring the integrity and controllability of the data during the update process. The pending-commit status temporary information is a set of modified and temporarily stored inventory data that is explicitly marked by the system as awaiting final confirmation and submission to the main database. This can be implemented using data records with specific status tags, pending items in a queue, or temporary datasets with specific access controls, such as data batches marked "pending_commit". This provides a clear intermediate state in the data update process, facilitating subsequent aggregation, signing, and verification operations by the system.

[0066] S400. Confirm the aggregate hash value of the temporary information of the pending submission mark state, and digitally sign the aggregate hash value to generate an operation intent credential. The aggregate hash value is a digest value obtained by performing a holistic hash calculation on a group of data (e.g., the temporary information of the pending submission mark state). It can be implemented using algorithms such as Merkle root hashing, chained hashing, or simple concatenated hashing. For example, the SHA-256 algorithm performs recursive hash calculations on all pending data blocks. Its main purpose is to efficiently represent and verify the integrity and consistency of large amounts of data; any minor modification will cause the hash value to change. Digital signature refers to the process of encrypting data (e.g., the aggregate hash value) using a private key to generate an electronic credential that can verify the source and integrity of the data. It can be implemented using encryption technologies such as RSA, Elliptic Curve Digital Signature Algorithm (ECDSA), or Schnorr signature. For example, signing the aggregate hash value with a private key is mainly to ensure the non-repudiation of the operation and the authenticity of the data, proving that a specific operation was performed by an authorized party and that the data has not been tampered with. An operation intent credential is an electronic document containing key information such as a digital signature and aggregated hash value, used to prove that a specific data update operation has been authorized and fully executed. It can be implemented using digital certificates, blockchain transaction records, or signed data packets with timestamps. For example, a credential containing a signature hash value, an operation timestamp, and the identity information of the operation initiator is mainly used to provide external parties with transparent and credible audit evidence that can be verified regarding data update operations, thereby maintaining trust in the supply chain.

[0067] S500: Based on the operation intent certificate, the temporary information of the pending submission mark status is replaced with the corresponding original inventory information in the inventory master information database to obtain the replaced inventory master information database.

[0068] Specifically, when the EPR supply chain management system receives an instruction to update the value of used power battery packs, for example due to rising cobalt prices or the release of new recycling subsidies, the system first identifies all power battery pack inventory records that require value field updates through its master inventory database, which can be deployed on a PostgreSQL-based relational database cluster. These records may contain non-sensitive information such as the battery's unique serial number, initial warehousing time, and health status, as well as an encrypted value field. After identifying the inventory information to be updated, a dedicated value calculation service is invoked to recalculate and modify the value field of each battery pack based on the latest market price data and subsidy parameters. For example, the original "economic value" field is updated from the old value to the new value, resulting in the modified inventory information. This modified inventory information is not directly written to the master database but is sent to an intent staging area, which can be a Redis-based in-memory cache system, with each record marked with a "pending commit" status. Once all modified inventory information has been staging and marked as pending commit, the system initiates a hash aggregation service. This service employs a Merkle tree structure to recursively hash all pending commit flags, ultimately generating a unique Merkle root hash value, which serves as the aggregate hash value for these flags. Subsequently, the system uses a private key stored in a Hardware Security Module (HSM) to digitally sign this aggregate hash value, generating an operation intent credential. This credential can be a JSON Web Token (JWT) containing a signature, hash value, timestamp, and operator identity information. Finally, based on this generated JWT operation intent credential, the system triggers an atomic replacement operation. This operation verifies the validity of the JWT and, upon successful verification, replaces the corresponding original inventory information in the inventory master database with the pending commit flags from the intent storage area in a batch process. For example, database transactions ensure that all related record updates either succeed entirely or are rolled back entirely. After the replacement is complete, the inventory master database contains all the latest, verified, and signed value information.

[0069] In this embodiment, an operation intent credential is generated by confirming the aggregate hash value of the temporarily stored information in the pending submission status and digitally signing the aggregate hash value. Specifically, this confirmation and digital signing of the aggregate hash value of the temporarily stored information in the pending submission status can be achieved by dividing the temporarily stored information into parts to be modified and parts that remain unchanged, calculating their aggregate hash values ​​separately, and signing these hash values ​​independently. This improves the efficiency of hash calculation and signing, and enhances the flexibility of auditing and verification. However, directly calculating and signing the aggregate hash of the entire temporarily stored information is inefficient, and when the value of a part of the temporarily stored information changes, the entire aggregate hash value needs to be recalculated and signed, resulting in a waste of computing resources and hindering the auditing and verification of subsequent value update operations. This approach avoids data inconsistencies caused by batch update interruptions and provides credible audit evidence to external parties through the credential, thereby improving the collaboration efficiency and trust level of the supply chain.

[0070] In some embodiments described above, this application also proposes a step of confirming the aggregated hash value of the temporary information of the pending submission marker state, and digitally signing the aggregated hash value to generate an operation intent credential, including:

[0071] Identify the value portions to be modified and the value portions that remain unchanged in the temporary information under the pending submission status. The value portions to be modified are specific fields or data blocks in the temporary information that require data updates or content changes. These can be identified using specific field identifiers in the data structure, logical address ranges of data blocks, or metadata tags. The value portions that remain unchanged are data contents in the temporary information that do not require any modification in this update operation. These can be identified by storing them separately from the parts to be modified, distinguishing them using data indexes or content hash values.

[0072] The process involves confirming a first aggregated hash value for the value portion to be modified and a second aggregated hash value for the value portion that remains unchanged. The first aggregated hash value is a unique digest obtained by hashing the identified value portion to be modified; it can be confirmed using methods such as a combination of Merkle root hashing, block hashing, or continuous hashing of the data stream. The second aggregated hash value is a unique digest obtained by hashing the identified value portion that remains unchanged; it can be confirmed using methods similar to the first aggregated hash value, such as a combination of Merkle root hashing, block hashing, or continuous hashing of the data stream.

[0073] After digitally signing the first aggregated hash value and the second aggregated hash value respectively, an operation intent credential is generated. The digital signature utilizes asymmetric encryption technology to encrypt the hash value, ensuring data integrity and authenticity of its source. It can be implemented using encryption algorithms such as RSA, Elliptic Curve Digital Signature Algorithm (ECDSA), or Schnorr signature. The operation intent credential is an electronic certificate containing the result of digitally signing the first and second aggregated hash values, used to prove the intent and execution status of a specific data update operation. It can be generated using a data structure containing signature data, timestamps, and version information, or in the form of blockchain transaction records.

[0074] Specifically, when the system receives an instruction to update the value of inventory information and has generated temporary information in a pending submission status, it first performs an identification operation to efficiently generate the operation intent voucher. Specifically, the system compares the current pending submission status temporary information with the corresponding original inventory information before the update. By comparing each field or data block, it accurately identifies which fields or data blocks have had their values ​​modified and categorizes them as the value parts to be modified; while those fields or data blocks whose content has not changed are identified as the unchanged value parts. For example, if an inventory record contains four fields: "Product ID," "Quantity," "Unit Price," and "Total Value," when only "Unit Price" and "Total Value" change, the system will identify "Product ID" and "Quantity" as the unchanged value parts, while "Unit Price" and "Total Value" will be identified as the value parts to be modified. Subsequently, the system will perform hash value verification on these two identified parts respectively. For the value parts to be modified, the system can use the SHA-256 hash algorithm to calculate its content and obtain the first aggregate hash value. Similarly, for the unchanged value portion, the system also uses the SHA-256 hash algorithm to calculate its content, obtaining a second aggregate hash value. This segmented hashing process ensures that even with a large amount of data, each unique digest can be obtained quickly. Finally, the system digitally signs these two independent aggregate hash values ​​separately. For example, the system can use a pre-configured private key to sign the first aggregate hash value using the Elliptic Curve Digital Signature Algorithm (ECDSA) to generate a first signature; then it can sign the second aggregate hash value to generate a second signature. Finally, these two signatures, along with the corresponding hash values, timestamps, and operation type metadata, are encapsulated into a structured data packet as the final credential of operation intent. This credential can be stored in a distributed ledger or audit log for subsequent verification and traceability. In this way, even when only partial data needs to be verified later, it is not necessary to reprocess the entire information, thereby improving efficiency and audit flexibility.

[0075] In this embodiment, processing efficiency is significantly improved when confirming the aggregate hash value of the temporarily stored information in the pending submission status and digitally signing it to generate an operation intent credential. By identifying the value portions to be modified and those that remain unchanged in the temporarily stored information, and calculating their aggregate hash values ​​and digitally signing them separately, the repetitive hash calculation and signing of the entire temporarily stored information is avoided, thereby reducing unnecessary consumption of computing resources. Furthermore, this segmented signing method makes subsequent auditing and verification of value update operations more flexible and precise, allowing for targeted verification of changed portions while ensuring the integrity of unmodified portions, thus enhancing the credibility and traceability of the data update process.

[0076] In some of the embodiments described above in this application, this application also proposes a step of confirming the aggregated hash value of the temporary information of the pending submission mark state, digitally signing the aggregated hash value, and generating an operation intent credential.

[0077] When the generation of the operation intent credential is interrupted, a recovery operation identifier is generated corresponding to the stored inventory information and the temporary information of the interrupted pending submission mark state. The recovery operation identifier is a unique identifier automatically generated by the system when an unexpected interruption occurs during the generation of the operation intent credential. Specifically, it can be a string combining a timestamp and a random number, or a hash value generated based on the interruption context information. Its purpose is to establish a logical association between the stored inventory information and the temporary information of the pending submission mark state that was not fully processed due to the interruption, providing a traceable anchor point for subsequent data recovery and state reconstruction.

[0078] Based on the stored inventory information and recovery operation identifier, audit records for updated inventory information and those associated with the recovery operation identifier are generated. The audit record for updated inventory information is a detailed record of the successfully updated and stored inventory information, which may include data snapshots before and after the update, the time of the update operation, the operator's identity, and related transaction IDs. Its purpose is to provide a complete historical view of the inventory information for which the operation has been completed, ensuring the verifiability of its status. The audit record associated with the recovery operation identifier is a log directly linked to the recovery operation identifier, recording the interruption event and its related context information. Specifically, it may include the time of the interruption, the interruption type, the affected data range, and the recovery operation identifier itself. Its purpose is to provide necessary context information and a chain of evidence for data recovery and consistency verification after the interruption, thereby supporting the auditing and verification of the entire recovery process.

[0079] Based on the audit records associated with the updated inventory information and the recovery operation identifier, the aggregated hash value is confirmed, and the aggregated hash value is digitally signed to generate an operation intent credential.

[0080] In this embodiment, by introducing a recovery and audit mechanism, the potential interruption problem during the generation of operational intent vouchers is effectively solved, thereby ensuring the consistency and reliability of EPR supply chain inventory data. Specifically, when the process of generating operational intent vouchers is unexpectedly interrupted, the system immediately responds and generates a recovery operation identifier. This identifier, as a unique association key, logically binds the currently stored inventory information with the temporary information in the pending submission state due to the interruption. This provides a clear starting point and association path for subsequent data state reconstruction and consistency verification, avoiding data isolation and state chaos. Based on the stored inventory information and this recovery operation identifier, two types of key audit records are intelligently generated. The first type is the audit record of updated inventory information, which records in detail the status and all change history of the inventory data successfully processed and updated before the interruption. The second type is the audit record associated with the recovery operation identifier, which focuses on recording detailed information about the interruption event itself, such as the time, cause, and affected data range, and associates it with the previously generated recovery operation identifier. These two types of audit records complement each other, jointly constructing a complete and traceable operational history chain, providing a reliable data foundation for subsequent aggregated hash value confirmation. Due to these comprehensive audit records, the complete data state before the interruption can be accurately reconstructed based on audit records associated with updated inventory information and recovery operation identifiers after an interruption. By confirming the aggregated hash value of this reconstructed data and further digitally signing the aggregated hash value, a credible operational intent credential is ultimately generated. This ensures that even in the event of an operational interruption, the final generated credential accurately reflects the true state of the inventory data and possesses tamper-proof and verifiable characteristics. Combined with the basic EPR supply chain inventory data management method, this solution significantly enhances the robustness and reliability of the entire data management process. By embedding interruption recovery and audit trail capabilities, this solution ensures the continuity of data flow and the consistency of final data even in the event of unexpected interruptions in a complex and dynamic distributed environment. It not only solves the problems of data inconsistency and lack of recovery mechanisms but also provides an auditable chain of evidence, thereby maintaining the trust of all parties in the supply chain in the authenticity of data and operational transparency, and improving the overall credibility of the entire EPR supply chain data management system.

[0081] In some of the embodiments described above in this application, this application also proposes a step of temporarily storing and marking the modified inventory information to obtain temporary information in a pending-submission marking state, including:

[0082] The modified inventory information undergoes a high-level secrecy sharing process to obtain multiple secret share information. High-level secrecy sharing is a technique that divides the original data into multiple encrypted fragments, called secret share information. These fragments can be implemented using the Shamir secret sharing algorithm or threshold cryptography schemes. The purpose is to improve data security and reliability; even if some shares are leaked or lost, the original data will not be completely exposed or damaged. Secret share information is an encrypted fragment generated after high-level secrecy sharing, which cannot be individually restored from the original data. Specifically, it can be an independent encrypted data block, its purpose being to distribute storage to enhance data security.

[0083] The multiple secret share information is distributed and stored across storage nodes in the intent temporary storage area, and the inventory information corresponding to each secret share is marked as temporary information in a pending submission state. The intent temporary storage area is a logical or physical region specifically used for temporarily storing data to be processed. Specifically, it can be a cluster composed of multiple independent servers or a distributed storage system, aiming to provide a secure and reliable temporary storage space for data. Storage nodes are independent computing or storage units within the intent temporary storage area used to actually store the secret share information. Specifically, they can be a physical server, a virtual machine, or a cloud storage instance, serving to support the distributed storage of the secret share information.

[0084] In this embodiment, the modified inventory information is divided into multiple secret share information by performing classified sharing processing on the original inventory information. This division ensures that no single secret share information can reconstruct the original inventory information; only when a sufficient number of secret share information are collected can the complete inventory information be reconstructed. Subsequently, these multiple secret share information are distributed and stored on different storage nodes in the intent temporary storage area. By distributing the different secret share information across different storage nodes, even if some storage nodes fail or are attacked, the secret share information on other nodes can still be used to recover the original inventory information, thereby ensuring data persistence and integrity. At the same time, marking the inventory information corresponding to each secret share information as temporary information in a pending submission status helps the system track and manage these temporary secret share information, clarifying which inventory information has been modified and temporarily stored, thus facilitating subsequent submission and replacement operations. The combination of temporary storage and marking processing of modified inventory information ensures that the temporary data itself possesses a high level of security and reliability before generating the operation intent credential. Through classified sharing and distributed storage, even if some storage nodes in the temporary storage area are attacked or fail, the integrity and confidentiality of the original inventory information can be guaranteed. This provides a solid data foundation for subsequent confirmation of aggregated hash values, generation of operation intent vouchers, and final replacement of the corresponding original inventory information in the inventory master information database, avoiding the impact of data problems in the temporary storage stage on the accuracy and reliability of the entire inventory data management process.

[0085] In some of the embodiments described above in this application, this application also proposes a step of identifying the inventory information to be updated using the inventory master information database after receiving the update instruction for the original inventory information, including:

[0086] Upon receiving an update instruction for the original inventory information, non-sensitive information for identification is extracted from the original inventory information and converted into queryable metadata. The original inventory information is inventory data stored in ciphertext form after being processed by an encryption algorithm, with the aim of protecting the confidentiality and integrity of the inventory information. Non-sensitive information refers to data fields in the inventory information that do not contain core commercial value or personal privacy, and whose disclosure would not cause significant security risks or economic losses. Specific examples include product model, batch number, warehousing date, and storage location, with the purpose of preliminary identification and screening without decrypting the complete data. Metadata is data that describes the data, providing structured information about the content of the original inventory information, but does not contain the specific content of the original data. Specific examples include indexes, tags, summaries, or hash values, with the aim of improving the efficiency of data querying and retrieval, and supporting data filtering under encrypted conditions.

[0087] By utilizing preset filtering criteria in the inventory master information database, a query operation is performed on the metadata to identify the original inventory information to be updated that meets the filtering criteria. These preset filtering criteria are query rules or logical expressions predefined based on business needs or data characteristics before the query operation is executed, with the aim of accurately locating the target data.

[0088] The original inventory information to be updated is decrypted to obtain the inventory information to be updated.

[0089] In this embodiment, a layered identification mechanism is introduced to address the efficiency and security issues faced by traditional direct identification methods in the context of raw inventory information. Specifically, upon receiving an update instruction for raw inventory information, instead of attempting to fully decrypt a large amount of raw inventory information to identify the items to be updated, the system first extracts non-sensitive information for identification from this raw inventory information. Non-sensitive information, such as batch numbers and product models, does not involve core sensitive data, and therefore can be operated on without exposing overall data security. The extracted non-sensitive information is converted into queryable metadata. Metadata, as a type of data description data, has structured characteristics that allow the database to index and retrieve it, thus laying the foundation for subsequent filtering operations.

[0090] Based on this, the system utilizes preset filtering criteria in the inventory master database to perform query operations on these transformed metadata. Since the query targets non-sensitive metadata, rather than the original encrypted data, this process avoids large-scale decryption operations, improving identification efficiency and avoiding the risk of accidentally exposing sensitive information during the query process. It can quickly and securely identify the original inventory information to be updated that meets the filtering criteria, thus narrowing the data range requiring deep processing (i.e., decryption) to a manageable subset. Finally, only this small number of initially filtered original inventory information to be updated is decrypted to obtain the actual inventory information to be updated. This reduces overall computational overhead and time costs, avoiding unnecessary decryption operations on all original inventory information. This solution transforms the original direct identification method into a secure and efficient metadata pre-screening and on-demand decryption model. This enables the rapid and accurate location of target update data when processing large amounts of encrypted inventory data, while ensuring data security. It avoids the efficiency bottlenecks and potential security vulnerabilities caused by frequent decryption in traditional methods, thus providing a highly efficient and secure data source for subsequent operations such as inventory information modification, temporary storage, hash confirmation, and replacement, ensuring the smoothness and reliability of the entire EPR supply chain data management process.

[0091] In some embodiments described above, this application further proposes that after the step of replacing the corresponding original inventory information in the inventory master database with the temporary information of the pending submission mark based on the operation intent certificate to obtain the replaced inventory master database, the application also includes:

[0092] The system confirms the first verification value of the temporary information of the pending tag status and the second verification value of the temporary information of the pending tag status in the replaced inventory master information database. The first verification value is a fixed-length value calculated from a specific dataset, used to represent the integrity and consistency of that dataset. It can be generated using a hash algorithm (e.g., SHA-256, MD5) or cyclic redundancy check (CRC). The second verification value is a fixed-length value calculated from another specific dataset, also used to represent the integrity and consistency of that dataset. It can be generated using the same verification algorithm as the first verification value.

[0093] The first check value and the second check value are compared to obtain a check value comparison result. The check value comparison result is a judgment obtained by comparing the first check value and the second check value. Its purpose is to indicate whether the two check values ​​are the same. Specifically, it can be achieved by comparing each bit or by judging whether the values ​​are equal.

[0094] If the checksum comparison result indicates that the first checksum and the second checksum are consistent, the checksum comparison result is stored in the audit log. The audit log is a persistent storage record used to record system operations, events, or data changes. Its purpose is to provide traceability of operations, security auditing, and troubleshooting. Specifically, it can be a database table, a log file in a file system, or a distributed ledger.

[0095] If the verification value comparison result indicates that the first verification value and the second verification value are inconsistent, then based on the operation intention certificate, the temporary information of the pending submission mark status is used to replace the corresponding original inventory information in the inventory master information database to obtain the replaced inventory master information database.

[0096] Specifically, after completing the operation of replacing the corresponding original inventory information in the master inventory database with the temporary information in the pending submission status based on the operation intent credential, and obtaining the replaced master inventory database, for example, when the value information of a batch of used power battery packs has been written from the temporary storage area to the master database, the system can immediately perform data verification to verify the accuracy of this write. Specifically, the system can first calculate the first verification value of the temporary information in the pending submission status, for example, by performing a SHA-256 hash operation on all the battery pack value data blocks to be submitted in the temporary storage area to obtain a hash string. At the same time, the system can extract the value data corresponding to these battery packs that were just replaced from the replaced master inventory database and calculate its second verification value, for example, by performing a SHA-256 hash operation to obtain another hash string. Subsequently, the system can compare these two hash strings to obtain the verification value comparison result. If the two hash strings are exactly the same, it indicates that the data replacement operation is accurate and error-free. At this time, the record that passes the data consistency verification, along with the operation credential ID, timestamp, and other information, can be stored in a dedicated audit log database table. If the two hash strings are different, it indicates that an error may have occurred during the data replacement process, such as a network transmission error or storage media failure, causing the data in the master database to be inconsistent with expectations. An automatic retry mechanism can be triggered to retry the original inventory information in the master database with the temporary information marked as pending submission, based on the original operation intent credentials, until the verification passes, ensuring that the data eventually reaches a consistent state.

[0097] In this embodiment, after the inventory information replacement operation is completed, this application introduces an immediate data consistency verification and self-correction mechanism. This effectively detects and corrects potential data inconsistencies during the replacement process, preventing information distortion caused by data errors. Simultaneously, by storing the verification results in the audit log, a reliable basis can be provided for subsequent data traceability and auditing, thereby ensuring a high degree of consistency between the data in the inventory master database and the temporary information in the pending submission status, improving the accuracy and reliability of EPR supply chain inventory data management.

[0098] In some of the embodiments described above in this application, this application also proposes a step of generating an operation intent credential after digitally signing the first aggregated hash value and the second aggregated hash value respectively, including:

[0099] Based on the first aggregated hash value and the second aggregated hash value, a hierarchical hash structure is constructed for the temporary storage information of the pending submission mark status. The hierarchical hash structure is a tree-like structure formed by aggregating data layer by layer using a hash algorithm, such as a Merkle tree. Its purpose is to decompose large amounts of data into independently verifiable small blocks and to efficiently identify and update local changes in the data.

[0100] A hierarchical hash structure of the temporary information in the pending submission status is digitally signed to generate an initial credential of operation intent. This initial credential of operation intent is the first integrity proof generated after digitally signing the hierarchical hash structure of the temporary information. Its purpose is to establish a trusted baseline state for subsequent credential updates and verification.

[0101] Based on the modified inventory information, the affected node hash values ​​in the hierarchical hash structure are recalculated to obtain a new root hash value. The affected node hash values ​​are the hash values ​​of intermediate or leaf nodes in the hierarchical hash structure whose hash values ​​need to be recalculated due to modifications to the underlying data. This aims to accurately pinpoint the range of data changes and avoid unnecessary global calculations. The new root hash value is the top-level hash value, recalculated after a local update, representing the latest state of the entire structure. Its purpose is to provide a concise and verifiable summary of overall data integrity.

[0102] Based on the new root hash value and a preset voucher version identifier, a new operation intent voucher is generated, containing both the new root hash value and the voucher version identifier. The voucher version identifier is a unique marker used to distinguish different versions of operation intent vouchers, such as a timestamp or an incrementing sequence number, designed to clearly record and trace the voucher's change history. The new operation intent voucher refers to the latest operation intent proof generated and digitally signed based on the new root hash value and voucher version identifier after the inventory information is updated, aiming to provide a valid voucher for the current, most up-to-date status.

[0103] The new credential representing the stated operational intent is digitally signed.

[0104] The new operation intent voucher is associated with the initial operation intent voucher to generate an operation intent voucher. This association involves establishing a logical link between the new operation intent voucher and the previous initial operation intent voucher after the new voucher is generated, for example, through chained references or storage in a distributed ledger. The purpose is to construct an evolution chain of vouchers, ensuring the traceability and integrity of voucher changes.

[0105] In this embodiment, a hierarchical hash structure is introduced to optimize the generation and updating mechanism of operation intent credentials. First, a hierarchical hash structure is constructed based on the first aggregated hash value of the value portion to be modified and the second aggregated hash value of the unchanged value portion in the temporary information under the pending submission flag. This structure can decompose complex inventory information into smaller, manageable hash units and aggregate them layer by layer to form a root hash value. By utilizing the first and second aggregated hash values, the system can organize the hierarchical hash structure more finely, for example, mapping the part to be modified and the part that remains unchanged to different branches or subtrees, thus laying the foundation for subsequent local updates. Subsequently, the constructed hierarchical hash structure is digitally signed to generate an initial operation intent credential, establishing the original trusted state of the credential.

[0106] When modified inventory information changes, there's no need to recalculate the hash value of the entire information and re-sign it. Instead, based on the modified inventory information, the affected node hash values ​​in the hierarchical hash structure can be accurately identified. Only hash paths where the underlying data has changed need to be recalculated, thus efficiently obtaining a new root hash value. This local update mechanism significantly reduces computational overhead. Next, based on the new root hash value and a preset voucher version identifier, a new operation intent voucher containing information from both is generated. The introduction of the voucher version identifier ensures that each voucher update has a clear version marker, guaranteeing the uniqueness and traceability of the voucher. Subsequently, this new operation intent voucher is digitally signed to ensure its integrity and immutability. Finally, this new operation intent voucher is associated with the initial operation intent voucher, for example, by embedding a reference to the previous version voucher in the voucher or recording the voucher update event in an immutable log. This association mechanism constructs a chain of voucher change history, allowing downstream partners in the supply chain to trace the evolution of vouchers and verify their validity. This solves the problems of low voucher update efficiency and inability to effectively trace change history in traditional methods, and strengthens the trust foundation of the supply chain.

[0107] In some embodiments described above, this application further proposes that after the step of associating the new operation intent credential with the initial operation intent credential to generate the operation intent credential, the application also includes:

[0108] Based on the new credential of the operation intent and the initial credential of the operation intent, replacement event information is generated. The replacement event information is structured data used to clearly record the replacement relationship between the new credential of the operation intent and the initial credential of the operation intent. Specifically, it may include the identifier of the new credential, the identifier of the old credential, the timestamp of the replacement, the information of the operation initiator, and the relevant business context. Its purpose is to provide a clear chain and basis for subsequent data traceability and status verification.

[0109] The replacement event information is recorded in a preset distributed ledger database, and the replaced distributed ledger data is confirmed. The preset distributed ledger database is a decentralized and immutable shared database implemented using blockchain technology or similar distributed ledger technology to ensure the secure, transparent, and reliable storage of the replacement event information, preventing information from being tampered with or forged.

[0110] This provides a query portal for the validity status of the replaced distributed ledger data. The replaced distributed ledger data represents the latest state of the ledger after the replacement event information has been successfully recorded in the preset distributed ledger data. Specifically, it can be reflected in newly added transaction records or blocks in the ledger, reflecting the real-time updates of the data status and serving as the basis for subsequent queries. The validity status query portal is an open interface or service that allows authorized users to query the current validity status and historical replacement records of specific data in the distributed ledger. Specifically, it can be an API interface, a web query page, or a dedicated client application, providing a convenient and reliable data verification method for all parties in the supply chain, enhancing data transparency and trust.

[0111] In this embodiment, the replacement relationship between the old and new documents is clarified by associating the new document with the initial document and generating replacement event information. This replacement event information is then recorded in a pre-defined distributed ledger database. The immutability and transparency of the distributed ledger ensure the authenticity and reliability of the replacement record. Once the replacement event information is successfully recorded, the data status of the distributed ledger is confirmed and updated. Finally, by providing a query port for the validity status of the replaced distributed ledger data, this solution enables all parties in the supply chain to easily query and verify the latest status of inventory information and its historical evolution. Specifically, after updating inventory information and generating a new document, the process goes beyond simply generating and associating documents; it further transforms this association into a traceable replacement event. This replacement event information, as a record with a clear timestamp and association identifier, clearly indicates which old document was replaced by which new document. Subsequently, this replacement event information is written into the distributed ledger, leaving an indelible trace of every inventory information update and document replacement. The characteristics of the distributed ledger ensure that these records cannot be tampered with once written, thus providing a highly reliable data source for the entire supply chain. When it's necessary to verify the validity of inventory information or trace its history, supply chain participants can access the distributed ledger through a query port to obtain the complete chain of document replacements, thereby verifying the validity of the current document and the authenticity of the inventory information it represents. By constructing a hierarchical hash structure, generating initial and new documents for operational intentions, and associating them, the issues of data consistency and traceability are resolved. Building upon this, the solution further solidifies the document relationships into immutable replacement event records and provides a public query mechanism. This ensures that each inventory information update not only generates new, reliable documents but also clearly records the evolution relationship between old and new documents, providing verifiable document validity status. This combination ensures high transparency and credibility throughout the entire process from document generation to its lifecycle management, effectively solving the problem of simply generating new documents without recording document replacement relationships and providing a validity query mechanism, thus enhancing the integrity and trust foundation of supply chain data management.

[0112] In some of the embodiments described above in this application, this application also proposes a step of decrypting the original inventory information to be updated to obtain the inventory information to be updated, including:

[0113] After processing the original inventory information to be updated in batches, the original inventory information in each batch is decrypted to obtain the decrypted inventory information corresponding to each batch. Batch processing involves dividing a large dataset or task into multiple smaller, independently processable data blocks or subtasks according to preset rules or capacity limitations. This can be achieved using strategies based on data volume, time windows, or resource constraints to reduce the complexity and resource consumption of a single processing operation. A batch is a set of independent data blocks or subtasks formed after batch processing; specifically, it can be a data packet containing a specific amount of original inventory information, serving as the basic unit for independent decryption operations.

[0114] The decrypted inventory information for each batch is summarized to obtain the inventory information to be updated. The summarization involves collecting, integrating, and merging the outputs of multiple independent processing units (such as batches) to form a complete and unified final result. This can be achieved through data merging, splicing, or aggregation operations, with the aim of restoring the complete inventory information to be updated.

[0115] In this embodiment, the large-scale original inventory information to be updated is processed in batches, and then the original inventory information in each batch is decrypted. Finally, the decrypted information from all batches is aggregated, thereby achieving efficient and reliable decryption of the massive original inventory information. Specifically, when the system receives the original inventory information update instruction and determines the original inventory information to be updated according to preset filtering conditions, since this information may be huge, directly decrypting it all at once would face the risk of resource exhaustion and low efficiency. Therefore, this original inventory information to be updated is first logically or physically divided into multiple smaller batches. The data volume of each batch is controlled within a manageable range, significantly reducing the computing resources and time required for a single decryption operation. Subsequently, the system independently performs the decryption operation on the original inventory information within each batch, generating the decrypted inventory information for the corresponding batch. This not only improves the success rate of a single decryption operation, but also ensures that even if the decryption of a batch is interrupted or fails due to unforeseen factors, it will not affect the normal progress of other batches, thus significantly enhancing the fault tolerance and stability of the entire decryption process. Finally, after all batches are decrypted, the independent decrypted inventory information is integrated and aggregated to restore the complete inventory information to be updated. By combining a batch decryption mechanism with the step of identifying the original inventory information to be updated, the entire inventory information update process remains efficient and reliable when handling large-scale data. Ensuring the stability and success rate of the decryption process provides a solid data foundation for subsequent inventory information modifications, temporary storage, aggregated hash value confirmation, and ultimately replacing the original information in the master inventory database. This effectively avoids issues such as interruptions or logical inconsistencies in the update process due to bottlenecks or failures in the decryption stage, thereby indirectly improving the data integrity and reliability of the entire EPR supply chain inventory data management method. Especially when facing complex and frequent batch update needs, it better supports the system in generating reliable operational credentials.

[0116] This application also proposes an EPR supply chain inventory data management system, including an identification module 210, a modification module 220, a processing module 230, a confirmation module 240, and a replacement module 250.

[0117] The identification module 210 is used to identify the inventory information to be updated using the inventory master information database after receiving the update instruction for the original inventory information.

[0118] The modification module 220 is used to modify the value field of the inventory information to be updated, so as to obtain the modified inventory information.

[0119] The processing module 230 is used to temporarily store and mark the modified inventory information to obtain temporary information in the marked state to be submitted.

[0120] The confirmation module 240 is used to confirm the aggregate hash value of the temporary information of the pending submission mark status, and to digitally sign the aggregate hash value to generate an operation intent credential.

[0121] The replacement module 250 is used to replace the corresponding original inventory information in the inventory master information database with the temporary information of the pending submission mark status based on the operation intention certificate, so as to obtain the replaced inventory master information database.

[0122] In this embodiment, the identification module 210 first interacts with the inventory master information database to locate and extract the inventory information that needs to be updated. Subsequently, the information to be updated is passed to the modification module 220, which adjusts the value fields of the inventory information according to business logic or external input, generating modified inventory information. The processing module 230 temporarily stores this modified information and assigns it a pending-commit status, forming temporary information in the pending-commit status, providing an intermediate state for subsequent data verification and potential error recovery. The confirmation module 240 calculates the aggregate hash value of the temporary information and encrypts the hash value using digital signature technology, thereby generating an operation intent credential. This credential not only proves the integrity of the data content but also ensures the non-repudiation of the operation. After receiving the confirmed operation intent credential, the replacement module 250, based on the validity of the credential, atomically replaces the corresponding original inventory information in the inventory master information database with the temporary information in the pending-commit status, thereby completing the inventory data update and obtaining the replaced inventory master information database. Specifically, the identification module 210 ensures the accuracy of the update starting point, the modification module 220 guarantees the correctness of the data content, the processing module 230 provides intermediate state management for transactions, the confirmation module 240 endows the operation with trust and traceability through digital signature technology, and the replacement module 250 is responsible for the final data persistence and consistency maintenance. This not only concretizes abstract methods and steps into operable components, but also solves the problem of data inconsistency caused by interruptions during batch data updates in a distributed environment by introducing digital signature and credential mechanisms. Furthermore, it can provide audit credentials to external parties, thereby maintaining the trust foundation of the supply chain.

[0123] The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention, and they should all be covered within the scope of the present invention specification.

Claims

1. An EPR supply chain inventory data management method, characterized in that, include: After receiving the update instruction for the original inventory information, the inventory master information database is used to identify the inventory information to be updated; Modify the value field of the inventory information to be updated to obtain the modified inventory information; The modified inventory information is temporarily stored and marked to obtain temporary information in the pending submission and marking state; Confirm the aggregated hash value of the temporary information of the pending submission mark status, and digitally sign the aggregated hash value to generate an operation intent credential; Based on the operation intent certificate, the temporary information of the pending submission mark status is replaced with the corresponding original inventory information in the inventory master information database to obtain the replaced inventory master information database. The steps of confirming the aggregated hash value of the temporary information of the pending submission mark status, and digitally signing the aggregated hash value to generate an operation intent credential include: Identify the value portion to be modified and the value portion that remains unchanged in the temporary information of the pending submission mark state; Confirm the first aggregate hash value of the value portion to be modified, and confirm the second aggregate hash value of the value portion that remains unchanged; After digitally signing the first aggregated hash value and the second aggregated hash value respectively, an operation intent credential is generated; The step of generating an operation intent credential after digitally signing the first aggregated hash value and the second aggregated hash value respectively includes: Based on the first aggregated hash value and the second aggregated hash value, a hierarchical hash structure is constructed for the temporary storage information of the pending submission mark status; A hierarchical hash structure of the temporary information of the pending submission mark state is digitally signed to generate an initial credential of operation intent; Based on the modified inventory information, the affected node hash values ​​in the hierarchical hash structure are re-determined to obtain a new root hash value; wherein, the affected node hash value is the hash value of an intermediate or leaf node in the hierarchical hash structure whose hash value needs to be recalculated due to the modification of the underlying data. Based on the new root hash value and the preset voucher version identifier, generate a new voucher containing the operation intent, which includes the new root hash value and the voucher version identifier; The new credential containing the stated operational intent is digitally signed; Associate the new operation intent certificate with the initial operation intent certificate to generate an operation intent certificate.

2. The EPR supply chain inventory data management method according to claim 1, characterized in that, The steps of confirming the aggregated hash value of the temporary information of the pending submission marker state, and digitally signing the aggregated hash value to generate an operation intent credential further include: When the generation of the operation intent certificate is interrupted, a recovery operation identifier is generated corresponding to the stored inventory information and the temporary information of the interrupted pending submission mark status. Based on the stored inventory information and recovery operation identifier, generate audit records for updated inventory information and audit records associated with the recovery operation identifier; Based on the audit records associated with the updated inventory information and the recovery operation identifier, the aggregated hash value is confirmed, and the aggregated hash value is digitally signed to generate an operation intent credential.

3. The EPR supply chain inventory data management method according to claim 1, characterized in that, The steps of temporarily storing and marking the modified inventory information to obtain temporary information in the pending-submission marking state include: The modified inventory information is subjected to a security-level sharing process to obtain multiple secret share information. The multiple secret share information is distributed and stored in the storage nodes of the intention temporary storage area, and the inventory information corresponding to each secret share is marked as temporary information in the pending submission mark state.

4. The EPR supply chain inventory data management method according to claim 1, characterized in that, After receiving the update instruction for the original inventory information, the step of identifying the inventory information to be updated using the inventory master information database includes: Upon receiving an update instruction for the original inventory information, non-sensitive information for identification is extracted from the original inventory information, and the non-sensitive information is converted into metadata that can be queried. Using preset filtering conditions in the inventory master information database, perform a query operation on the metadata to determine the original inventory information to be updated that meets the filtering conditions; The original inventory information to be updated is decrypted to obtain the inventory information to be updated.

5. The EPR supply chain inventory data management method according to claim 1, characterized in that, After the step of replacing the corresponding original inventory information in the inventory master database with the temporary information of the pending submission mark based on the operation intent certificate to obtain the replaced inventory master database, the method further includes: Confirm the first verification value of the temporary information of the pending submission mark status, and confirm the second verification value of the temporary information of the pending submission mark status in the replaced inventory master information database; Compare the first check value and the second check value to obtain the check value comparison result; If the checksum comparison result indicates that the first checksum and the second checksum are the same, then the checksum comparison result is stored in the audit log; If the verification value comparison result indicates that the first verification value and the second verification value are inconsistent, then based on the operation intention certificate, the temporary information of the pending submission marked state is used to replace the corresponding original inventory information in the inventory master information database, and the replaced inventory master information database is obtained.

6. The EPR supply chain inventory data management method according to claim 1, characterized in that, After the step of associating the new operation intent certificate with the initial operation intent certificate to generate the operation intent certificate, the method further includes: Based on the new credential of the operation intent and the initial credential of the operation intent, replacement event information is generated; The replacement event information is recorded in the preset distributed ledger data, and the replaced distributed ledger data is confirmed; Provides a query port for the validity status of the replaced distributed ledger data.

7. The EPR supply chain inventory data management method according to claim 4, characterized in that, The steps for decrypting the original inventory information to be updated to obtain the updated inventory information include: After processing the original inventory information to be updated in batches, the original inventory information to be updated in each batch is decrypted to obtain the decrypted inventory information corresponding to each batch. The decrypted inventory information for each batch is summarized to obtain the inventory information to be updated.

8. An EPR supply chain inventory data management system, characterized in that, include: The identification module is used to identify the inventory information to be updated using the inventory master information database after receiving the update instruction for the original inventory information. The modification module is used to modify the value field of the inventory information to be updated, thereby obtaining the modified inventory information. The processing module is used to temporarily store and mark the modified inventory information to obtain temporary information in the marked state to be submitted. The confirmation module is used to confirm the aggregated hash value of the temporary information of the pending submission mark status, and to digitally sign the aggregated hash value to generate an operation intent credential. It is also used to identify the value portion to be modified and the value portion that remains unchanged in the temporary information of the pending submission mark state; Confirm the first aggregate hash value of the value portion to be modified, and confirm the second aggregate hash value of the value portion that remains unchanged; After digitally signing the first aggregated hash value and the second aggregated hash value respectively, an operation intent credential is generated; It is also used to construct a hierarchical hash structure for temporary information of the pending submission mark state based on the first aggregate hash value and the second aggregate hash value; A hierarchical hash structure of the temporary information of the pending submission mark state is digitally signed to generate an initial credential of operation intent; Based on the modified inventory information, the affected node hash values ​​in the hierarchical hash structure are re-determined to obtain a new root hash value; wherein, the affected node hash value is the hash value of an intermediate or leaf node in the hierarchical hash structure whose hash value needs to be recalculated due to the modification of the underlying data. Based on the new root hash value and the preset voucher version identifier, generate a new voucher containing the operation intent, which includes the new root hash value and the voucher version identifier; The new credential containing the stated operational intent is digitally signed; Associate the new operation intent certificate with the initial operation intent certificate to generate an operation intent certificate; The replacement module is used to replace the corresponding original inventory information in the inventory master information database with the temporary information of the pending submission mark status based on the operation intention certificate, so as to obtain the replaced inventory master information database.

Images