A product trusted identification and traceability method based on content addressing

Abstract

A trusted traceability method for the manufacturing industry based on a content identification addressing algorithm. It includes the steps of system initialization, product identification generation, product traceability, and data identification resolution. The beneficial effects of the trusted traceability method for the manufacturing industry based on a content identification addressing algorithm provided by the present invention are: 1. There is only one unique identifier for the entire product life cycle, and the identifier is compatible with all existing data identification systems in the industrial field and compatible with various heterogeneous data storage formats. 2. The data of the entire product life cycle is stored in layers, and the target data can be accurately obtained through iterative query and identification resolution, and the traceability process is coherent and reliable. 3. Data encoding, traceability operations are recorded on the entire chain, and data queries for the entire life cycle of product design, production, transportation, and sales are reliable.

Description

Technical Field

[0001] The present invention belongs to the technical field of product traceability, and in particular relates to a product trusted identification and traceability method based on content addressing. Background Art

[0002] With the rapid development of internet technology in recent years, traditional industrial structures are undergoing transformation. Emerging information technologies, such as the Industrial Internet, are improving traditional industrial systems in various ways. Product traceability, a typical application scenario within the Industrial Internet, can trace product status, production processes, raw materials, and other information throughout its entire lifecycle, from design, manufacturing, and distribution. This facilitates data exchange and trust between users and businesses, as well as between upstream and downstream enterprises, thereby improving the level of intelligence. Identification and resolution systems are crucial for achieving product traceability. Identification technology assigns unique identifiable codes to products, raw materials, and even equipment for resource management. Resolution technology involves resolving identifiers to obtain the corresponding storage address or directly access the data itself. Although my country's identification resolution system has taken shape and is gradually being implemented, several challenges remain. First, multiple domestic and international identification resolution systems coexist, such as Handle and OID systems abroad and Ecode, NIOT, local implementations, and internal enterprise identification systems in China. These systems are isolated and lack interoperability mechanisms. Second, data heterogeneity caused by differing data collection, storage, and resolution standards across these systems creates data silos. Finally, the traceability platform operated by product manufacturers lacks a unified query interface, making it difficult to distinguish authenticity, and the development of reliable traceability technology is insufficient.

[0003] Content-addressing technology

[0004] Unlike the address-based addressing widely used on the existing internet, the "address" used to locate data in content-addressed addressing technology is derived from the data itself, rather than simply resolved from a fixed "domain name" address. Content-addressed addressing technology offers advantages such as data integrity verification, distributed data storage, parallel data retrieval, and content-specific relevance. Furthermore, to address the difficulty of updating data after adopting content-addressed addressing algorithms, a naming system similar to the existing Internet domain name system (DNS) has emerged. This system implements content-updatable content addressing by assigning a "domain name" to the content-addressed identifier, with data storage nodes independently maintaining the mapping between the "domain name" and the content-addressed identifier. However, a complete and practical method currently exists in the field of product traceability technology. Summary of the Invention

[0005] In order to solve the above problems, the purpose of the present invention is to provide a product trusted identification and traceability method based on content addressing.

[0006] To achieve the above-mentioned objectives, the content-addressable product trusted identification and traceability method provided by the present invention includes the following steps performed in sequence:

[0007] 1) System initialization:

[0008] Each participant runs a blockchain node and generates an operator address. The system administrator organizes and runs the consortium chain, and each node registers its identity with the system administrator. The system administrator deploys the smart contract and broadcasts the contract address. Each node calls the Operatorregister function in the smart contract to complete the registration.

[0009] 2) Product identification generation:

[0010] The product producer determines the product data PD, and then uses the content-addressed identification algorithm to generate the data identifier PDI corresponding to the product data PD; then names the data identifier PDI and specifies a unique and immutable domain name as the product identifier PDIN; finally, the product identifier PDIN, the product production stage name, and the data identifier PDI are used as parameters to call the smart contract SC and record it on the consortium chain; the non-product producer only produces data for the corresponding stage, and then generates the corresponding data identifier PDI, and then uses the above product identifier PDIN, the corresponding stage name, and the data identifier PDI as parameters to call the smart contract SC and record it on the consortium chain;

[0011] 3) Product traceability:

[0012] After purchasing a product, the user obtains the product identifier PDIN. When they want to initiate traceability, they submit a traceability request to the system administrator. The system administrator determines whether to approve the request based on the additional permission management mechanism. If approved, the user's address Account is stored in the smart contract SC. The user calls the smart contract SC with the product identifier PDIN and the product stage as parameters, and the return value is the required data identifier PDI.

[0013] 4) Data identification analysis:

[0014] After the user obtains the required data identifier PDI, he / she sends a data parsing request to any node in the alliance chain. The node then parses the data identifier PDI to determine the storage address of the product data fragments, and then obtains the product data fragments. After that, the product data fragments are spliced ​​into product data PD and returned to the user. At this point, product traceability is completed.

[0015] In step 1), the specific method of initializing the system is as follows:

[0016] 101) All parties, including product manufacturers and non-product manufacturers, run blockchain nodes to generate operator addresses; non-product manufacturers include product sellers, product transporters, and product designers;

[0017] 102) The consortium chain is run by the system administrator. Each node sends its real-name identity and the operator address to the system administrator, who writes all of the above information directly into the consortium chain block.

[0018] 103) The system administrator deploys the smart contract SC and broadcasts the contract address to each node;

[0019] 104) Each node uses the operator address generated in step 101) as a parameter and calls the Operatorregister function in the smart contract SC to complete the registration to facilitate future traceability.

[0020] In step 2), the specific method of generating the product identification is as follows:

[0021] 201) During the product production phase, each time a product that needs to be traced is produced, the product manufacturer first determines the product data PD. The product data PD includes production raw materials, production process, product production time, and production location. The production raw materials may include products from other product manufacturers. The storage, maintenance, and update of the product data PD are all performed by the product manufacturer.

[0022] 202) The product manufacturer uses a content-addressable identification algorithm to fragment the product data PD and then performs a hash operation to generate a data identifier PDI corresponding to the product data PD, and saves the product data fragments in the storage address;

[0023] 203) The product manufacturer names the data identifier PDI using a custom naming rule and specifies a unique and immutable domain name as the product identifier PDIN;

[0024] 204) The product producer uses the operator address registered in step 104) to call the AddData function in the smart contract SC. This function records the mapping relationship between the product identifier PDIN, the product production stage name, and the data identifier PDI in the PDIN2Stage2PDI variable of the consortium chain;

[0025] 205) The non-product producer only generates data for the corresponding stage, and then generates the corresponding data identifier PDI. Afterwards, the smart contract SC is called with the above-mentioned product identifier PDIN, the corresponding product stage name and the data identifier PDI as parameters and recorded in the PDIN2Stage2PDI variable of the alliance chain.

[0026] In step 3), the specific method of product traceability is as follows:

[0027] 301) After purchasing a product, the user obtains a unique product identifier PDIN and determines the product stage to be traced;

[0028] 302) The user sends a product traceability request to the system administrator, and the request content includes the product identifier PDIN, the product stage stage and the user address Account;

[0029] 303) The system administrator confirms whether the user has traceability authority based on the additional authority management mechanism. If so, the system administrator calls the Approveaccount function in the smart contract SC and records the user address account in the Reader2PDINStage2Bool variable of the alliance chain;

[0030] 304) The user calls the ReturnData function in the smart contract SC. This function verifies whether the user address Account that initiated the traceability has the permission to read the product data PD based on the value in the Reader2PDINStage2Bool variable. If so, it returns the required data identifier PDI.

[0031] In step 4), the specific method of data identification resolution is as follows:

[0032] 401) The user sends a data parsing request to any node node1 in the alliance chain using the data identifier PDI obtained in step 304) as a parameter;

[0033] 402) The node node1 queries the Reader2PDINStage2Bool variable recorded in step 303) to confirm whether the user has traceability permission;

[0034] 403) If yes, the node node1 will parse the data identifier PDI to determine the storage address of the product data fragment, and then obtain the product data fragment, and then splice the product data fragments into the product data PD in a readable format;

[0035] 404) The node node1 returns the product data PD to the user through the secure channel, and the product traceability is now completed.

[0036] The beneficial effects of the manufacturing trusted traceability method based on the content identification addressing algorithm provided by the present invention are:

[0037] 1. There is only one unique identifier for the entire product life cycle. This identifier is compatible with all existing data identification systems in the industrial field and is compatible with various heterogeneous data storage formats.

[0038] 2. Data throughout the product life cycle is stored in layers. Target data can be accurately obtained through iterative query and identity resolution, and the traceability process is coherent and reliable.

[0039] 3. Data coding and traceability operations are recorded on the entire chain, and data queries throughout the entire life cycle of product design, production, transportation, and sales are reliable. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 This is a flow chart of the content-addressable product trusted identification and traceability method provided by the present invention. DETAILED DESCRIPTION

[0041] The main roles involved in this invention are the following three categories:

[0042] The product manufacturer, as a participant in the product production phase, is responsible for maintaining product data and generating a unique product identifier for each product. The smart contract is then called with the product identifier as a parameter and announced to all participants.

[0043] Non-product manufacturers, including other product stage participants such as product sales, product transportation, product design, etc., use the product identifiers provided by the product manufacturers to add and update product data at each product stage.

[0044] The user, as the initiator of the traceability request, enters the product identifier, calls the smart contract, and obtains the product data.

[0045] The smart contract SmartContract described in this invention primarily stores four variables. One is the PDIN2Stage2PDI variable, which is a dual mapping type (i.e., mapping(string=>mapping(string=>string)). It maps the unique product identifier PDIN to a product lifecycle stage, such as production, transportation, or sales, and then to the data identifier PDI for that product stage. Another variable is the PDIN2Stage2Operators variable, which is a dual mapping type (i.e., mapping(string=>mapping(string=>address[])). It maps the product identifier PDIN to a product lifecycle stage, and then to an array of operator addresses for that stage. Only addresses within this array can add and update data. Furthermore, the Reader2PDINStage2Bool variable, which is a dual mapping type (i.e., mapping(address=>mapping(string=>bool)), records the product data that a specific address is eligible to access. Finally, the variable Admin records the address of the system administrator, typically a regulatory body.

[0046] The main function is: AddData(Account, PDIN, stage, PDI), which is called by operators of each participating party. First, the function queries the PDIN2Stage2Operators variable to determine whether the address initiating traceability is a valid operator address. Then, it stores the mapping between the product identifier PDIN, the product stage, and the data identifier PDI of that stage into the PDIN2Stage2PDI variable.

[0047] Approveaccount(Account, PDIN, stage), this function is called by the system administrator to read the data of the product corresponding to the product identifier PDIN in the product stage stage for the user address Account.

[0048] ReturnData(Account, PDIN, stage) is called by the traceability user. By entering the product identifier and the desired product stage, the return value is the data identifier (PDI) for the product at that stage. Before calling the smart contract, the traceability user must submit a request to the system administrator, who will approve or deny the user's traceability request based on the permissions management mechanism. The ApproveAccount function then stores the user's address in the Reader2PDINStage2Bool variable, where Account=>PDIN+Stage=>True. The function queries this variable and returns the corresponding product data if it evaluates to True.

[0049] UpdateData(Account, PDIN, stage, PDI) is called by each participant operator. Similar to the AddData function, it first determines whether the user address initiating the traceability has the authority to update the product data, and then directly updates the product data. The old product data corresponding to the product identifier PDIN with the same key value will be overwritten.

[0050] RegisterOperators(Account, PDIN, stage) is called by each participating operator. Each operator must first call this function to complete registration before calling AddData or UpdateData. The operator's own address, Account, is written to the PDIN2Stage2Operators variable. Once written, this variable cannot be changed and can only be exported and deleted by the system administrator. This ensures that all addresses for added and updated data are fully recorded, facilitating future traceability.

[0051] FreshOperators(Account, PDIN, stage) first verifies the identity of the traceability initiator and can only be called by system administrators. It then returns all historical operation addresses corresponding to the product stage, corresponding to the product identifier PDIN. Finally, it initializes the variable and clears the historical addresses. This function is primarily used to prevent excessive historical records from causing blockchain state explosion.

[0052] like Figure 1 As shown, the content-addressable product trusted identification and traceability method provided by the present invention includes the following steps performed in sequence:

[0053] 1) System initialization:

[0054] Each participant runs a blockchain node and generates an operator address. The system administrator organizes and runs the consortium chain, and each node registers its identity with the system administrator. The system administrator deploys the smart contract and broadcasts the contract address. Each node calls the Operatorregister function in the smart contract to complete the registration.

[0055] The specific method is as follows:

[0056] 101) All parties, including product manufacturers and non-product manufacturers, run blockchain nodes to generate operator addresses; non-product manufacturers include product sellers, product transporters, and product designers;

[0057] 102) The consortium chain is run by the system administrator. Each node sends its real-name identity and the operator address to the system administrator, who writes all of the above information directly into the consortium chain block.

[0058] 103) The system administrator deploys the smart contract SC (Smartcontract) and broadcasts the contract address to each node;

[0059] 104) Each node uses the operator address generated in step 101) as a parameter and calls the Operatorregister function in the smart contract SC to complete the registration to facilitate future traceability.

[0060] 2) Product identification generation:

[0061] The product manufacturer determines the product data PD (Product data), and then uses the content-addressed identification algorithm to generate the data identifier PDI (Product data identifier) ​​corresponding to the product data PD; then the data identifier PDI is named, and a unique and immutable domain name is specified as the product identifier PDIN; finally, the product identifier PDIN, the product production stage name, and the data identifier PDI are used as parameters to call the smart contract SC to record it on the consortium chain; the non-product manufacturer only produces data for the corresponding stage, and then generates the corresponding data identifier PDI, and then uses the above product identifier PDIN, the corresponding stage name, and the data identifier PDI as parameters to call the smart contract SC to record it on the consortium chain;

[0062] The specific method is as follows:

[0063] 201) During the product production phase, each time a product that needs to be traced is produced, the product manufacturer first determines the product data (PD). The product data (PD) includes production raw materials, production process, production time, production location, etc., where the production raw materials may include products from other manufacturers. The storage, maintenance, and update of the product data (PD) are all performed by the product manufacturer.

[0064] 202) The product manufacturer uses a content-addressable identification algorithm to fragment the product data PD and then performs a hash operation to generate a data identifier PDI corresponding to the product data PD, and saves the product data fragments in the storage address;

[0065] 203) The product manufacturer names the data identifier PDI using a custom naming rule and specifies a unique and immutable domain name as the product identifier PDIN;

[0066] 204) The product producer uses the operator address registered in step 104) to call the AddData function in the smart contract SC. This function records the mapping relationship between the product identifier PDIN, the product production stage name, and the data identifier PDI in the PDIN2Stage2PDI variable of the consortium chain;

[0067] 205) The non-product producer only generates data of the corresponding stage, and then generates the corresponding data identifier PDI. After that, the smart contract SC is called with the above-mentioned product identifier PDIN, the corresponding product stage name and the data identifier PDI as parameters to record it in the PDIN2Stage2PDI variable of the alliance chain; for example, the product seller, product transporter and product designer only generate data of the product sales stage, product transportation stage and product design stage, and then generate the corresponding data identifier PDI.

[0068] 3) Product traceability:

[0069] After purchasing a product, the user obtains the product identifier PDIN; when wanting to initiate traceability, the user submits a traceability request to the system administrator; the system administrator determines whether to approve the request based on the additional permission management mechanism, and stores the user address Account in the smart contract SC after approval; the user calls the smart contract SC with the product identifier PDIN and the product stage stage as parameters, and the return value is the required data identifier PDI.

[0070] The specific method is as follows:

[0071] 301) After purchasing a product, the user obtains a unique product identifier PDIN and determines the product stage to be traced, such as production (produce), transportation (ship), etc.

[0072] 302) The user sends a product traceability request to the system administrator, and the request content includes the product identifier PDIN, the product stage stage and the user address Account;

[0073] 303) The system administrator confirms whether the user has traceability authority based on the additional authority management mechanism. If so, the system administrator calls the Approveaccount function in the smart contract SC and records the user address account in the Reader2PDINStage2Bool variable of the alliance chain;

[0074] 304) The user calls the ReturnData function in the smart contract SC. This function verifies whether the user address Account that initiated the traceability has the permission to read the product data PD based on the value in the Reader2PDINStage2Bool variable. If so, it returns the required data identifier PDI.

[0075] 4) Data identification analysis:

[0076] After the user obtains the required data identifier PDI, he / she sends a data parsing request to any node in the alliance chain. The node then parses the data identifier PDI to determine the storage address of the product data fragments, and then obtains the product data fragments. After that, the product data fragments are spliced ​​into product data PD and returned to the user. At this point, product traceability is completed.

Claims

1. A content-addressable product trusted identification and traceability method, characterized by: The content-addressable product trusted identification and traceability method comprises the following steps performed in sequence: 1) System initialization: Each participant runs a blockchain node and generates an operator address. The system administrator organizes and runs the consortium chain, and each node registers its identity with the system administrator. The system administrator deploys the smart contract and broadcasts the contract address. Each node calls the Operatorregister function in the smart contract to complete the registration. 2) Product identification generation: The product producer determines the product data PD, and then uses the content-addressed identification algorithm to generate the data identifier PDI corresponding to the product data PD; then names the data identifier PDI and specifies a unique and immutable domain name as the product identifier PDIN; finally, the product identifier PDIN, the product production stage name, and the data identifier PDI are used as parameters to call the smart contract SC and record it on the consortium chain; the non-product producer only produces data for the corresponding stage, and then generates the corresponding data identifier PDI, and then uses the above product identifier PDIN, the corresponding stage name, and the data identifier PDI as parameters to call the smart contract SC and record it on the consortium chain; 3) Product traceability: After purchasing a product, the user obtains the product identifier PDIN. When they want to initiate traceability, they submit a traceability request to the system administrator. The system administrator determines whether to approve the request based on the additional permission management mechanism. If approved, the user's address Account is stored in the smart contract SC. The user calls the smart contract SC with the product identifier PDIN and the product stage as parameters, and the return value is the required data identifier PDI. 4) Data identification analysis: After the user obtains the required data identifier PDI, he / she sends a data parsing request to any node in the alliance chain. The node then parses the data identifier PDI to determine the storage address of the product data fragments, and then obtains the product data fragments. After that, the product data fragments are spliced ​​into product data PD and returned to the user. At this point, product traceability is completed.

2. The content-addressable product trusted identification and traceability method according to claim 1, characterized in that: In step 1), the specific method of initializing the system is as follows: 101) All parties, including product manufacturers and non-product manufacturers, run blockchain nodes to generate operator addresses; non-product manufacturers include product sellers, product transporters, and product designers; 102) The consortium chain is run by the system administrator. Each node sends its real-name identity and the operator address to the system administrator, who writes all of the above information directly into the consortium chain block. 103) The system administrator deploys the smart contract SC and broadcasts the contract address to each node; 104) Each node uses the operator address generated in step 101) as a parameter and calls the Operatorregister function in the smart contract SC to complete the registration to facilitate future traceability.

3. The content-addressable product trusted identification and traceability method according to claim 2, characterized in that: In step 2), the specific method of generating the product identification is as follows: 201) During the product production phase, each time a product that needs to be traced is produced, the product manufacturer first determines the product data PD. The product data PD includes production raw materials, production process, product production time, and production location. The production raw materials may include products from other product manufacturers. The storage, maintenance, and update of the product data PD are all performed by the product manufacturer. 202) The product manufacturer uses a content-addressable identification algorithm to fragment the product data PD and then performs a hash operation to generate a data identifier PDI corresponding to the product data PD, and saves the product data fragments in the storage address; 203) The product manufacturer names the data identifier PDI using a custom naming rule and specifies a unique and immutable domain name as the product identifier PDIN; 204) The product producer uses the operator address registered in step 104) to call the AddData function in the smart contract SC. This function records the mapping relationship between the product identifier PDIN, the product production stage name, and the data identifier PDI in the PDIN2Stage2PDI variable of the consortium chain; 205) The non-product producer only generates data for the corresponding stage, and then generates the corresponding data identifier PDI. Afterwards, the smart contract SC is called with the above-mentioned product identifier PDIN, the corresponding product stage name and the data identifier PDI as parameters and recorded in the PDIN2Stage2PDI variable of the alliance chain.

4. The content-addressable product trusted identification and traceability method according to claim 1, characterized in that: In step 3), the specific method of product traceability is as follows: 301) After purchasing a product, the user obtains a unique product identifier PDIN and determines the product stage to be traced; 302) The user sends a product traceability request to the system administrator, and the request content includes the product identifier PDIN, the product stage stage and the user address Account; 303) The system administrator confirms whether the user has traceability authority based on the additional authority management mechanism. If so, the system administrator calls the Approveaccount function in the smart contract SC and records the user address account in the Reader2PDINStage2Bool variable of the alliance chain; 304) The user calls the ReturnData function in the smart contract SC. This function verifies whether the user address Account that initiated the traceability has the permission to read the product data PD based on the value in the Reader2PDINStage2Bool variable. If so, it returns the required data identifier PDI.

5. The content-addressable product trusted identification and traceability method according to claim 4, characterized in that: In step 4), the specific method of data identification resolution is as follows: 401) The user sends a data parsing request to any node node1 in the alliance chain using the data identifier PDI obtained in step 304) as a parameter; 402) The node node1 queries the Reader2PDINStage2Bool variable recorded in step 303) to confirm whether the user has traceability permission; 403) If yes, the node node1 will parse the data identifier PDI to determine the storage address of the product data fragment, and then obtain the product data fragment, and then splice the product data fragments into the product data PD in a readable format; 404) The node node1 returns the product data PD to the user through the secure channel, and the product traceability is now completed.

Images