Traceable and trustworthy system for digital product passport (DPP) of internet of things (IOT) product using cyber-physical coupled tokens and method thereof

Abstract

A traceable and trustworthy system for digital product passport (DPP) of internet of things (IoT) product using cyber-physical coupled tokens and method thereof is disclosed. By deploying a product smart contract and a DPP contract on the blockchain, when producing a IoT product, the encrypted IoT product registration information (including a product public key) is embedded into the IoT product along with the product private key as supplementary information. During primary registration, the primary registration function is executed to generate a digital token based on the supplementary information. When secondary delivery of a previously registered IoT product is desired, the secondary delivery function is executed to set the delivery conditions, and upon fulfilling the delivery conditions, the ownership of the digital token is transferred. During proof recording, the digital data of the IoT product is signed to generate a proof value, which is then written into the DPP contract for verification. The mechanism is help to improve the traceability and trustworthiness of cyber-physical coupled products.

Description

Technical Field

[0001] This invention relates to a verification system and method, particularly a traceable and trustworthy system and method for digital product passports that apply virtual-real coupled tokens to Internet of Things (IoT) products. Prior Technology

[0002] In recent years, with the popularization and vigorous development of digitalization, various applications of virtual-real coupling have sprung up like mushrooms after rain. Virtual-real coupling refers to a physical item having both "physical existence" and "digital existence" at the same time, such as paper degree certificates and electronic degree certificates, physical products and electronic production and sales records, etc.

[0003] Generally, traditional hybrid physical and virtual products require simultaneous delivery during transactions to maintain ownership of both the "physical existence (e.g., IoT products)" and the "digital existence (e.g., the corresponding hybrid token for IoT products)" within the same stakeholder. This applies whether it's from the issuer to the end-user or secondary market delivery between different holders (referred to as secondary delivery). However, effectively proving the traceability and trustworthiness of the relationship between the "physical existence" and the "digital existence" has always been a pressing issue for manufacturers.

[0004] Currently, a common technical approach is to embed two-dimensional barcodes into the surface of physical objects through printing, etching, or similar methods, allowing users to scan the barcode to obtain information related to the physical object. However, this method is easily counterfeited and stolen, and therefore, it is still insufficient to solve the problems of traceability and trustworthiness of products that combine physical and virtual elements.

[0005] In summary, it is clear that previous technologies have long suffered from insufficient traceability and trustworthiness of virtual-physical coupled products. Therefore, it is necessary to propose improved technical means to solve this problem. Summary of the Invention

[0006] This invention discloses a traceable and trustworthy system and method for applying virtual-real coupled tokens to digital product passports in Internet of Things (IoT) products.

[0007] First, this invention discloses a traceable and trustworthy system for digital product passports applied to IoT products using virtual-real coupled tokens. This system includes: a product issuer host, a primary login host, a secondary delivery receiver host, a storage host, and a verification host. The product issuer host comprises a deployment module and a production module. The deployment module is used to deploy product smart contracts on the blockchain. These smart contracts include a primary login function and a secondary delivery function. The production module connects to the deployment module and, during the production of IoT products, encrypts the login information corresponding to the IoT product to form encrypted product content. This encrypted content, along with the product private key, is embedded as additional information into the IoT product. The login information includes the product public key corresponding to the product private key. Next, the primary login host, connected to the blockchain, comprises a login module and a delivery module. The system comprises several modules: a login module and a delivery module. The login module executes a primary login function to generate a digital token for the IoT product based on additional information when the product has not yet undergone primary login. It also records the product's public key as a verification basis for secondary delivery. The delivery module, connected to the login module, executes a secondary delivery function to set delivery conditions when a secondary delivery is desired for an IoT product with a logged-in digital token. These conditions include a receiver message and a pending question, which must be answered using both the product's private key and the receiver's private key. The secondary delivery receiver, connected to a blockchain, answers the pending question upon receiving the IoT product using its own private key and the product's private key from the additional information. A correct answer fulfills the delivery conditions, transferring ownership of the IoT product's digital token to the secondary delivery receiver. In the evidence storage host, it connects to the blockchain and has write permissions to a pre-deployed digital product passport smart contract on the blockchain. During evidence storage, it uses the product's private key to sign N digital data points of the IoT product, generating N corresponding evidence values, which are then written into the digital product passport smart contract as evidence records. The digital product passport smart contract includes the contract address of the product smart contract, the unique identifier of the IoT product, and its corresponding N evidence values, where N is a positive integer. Finally, in the verification host, it connects to the blockchain and, during verification, recalculates N new evidence values ​​based on the N digital data points and compares them one by one with the N existing evidence values. If all comparisons match, it checks whether the corresponding unique identifier matches the IoT product. If so, it proves that the N digital data points of the IoT product are traceable and trustworthy.

[0008] Furthermore, this invention also discloses a traceable and trustworthy method for applying virtual-real coupled tokens to digital product passports in IoT products. The steps include: the product issuer host deploying a product smart contract on a blockchain, the product smart contract including a primary login function and a secondary delivery function; during IoT product production, the product issuer host encrypts the login message corresponding to the IoT product to form encrypted product content, and embeds this encrypted product content and the product private key as additional information into the IoT product, wherein the login message includes a product public key corresponding to the product private key; when the IoT product has not undergone primary login, the primary login host executes the primary login function to generate a digital token for the corresponding IoT product based on the additional information, and records the product public key as the verification basis for secondary delivery; when it is necessary to perform secondary delivery on an IoT product that has already logged in with a digital token, the primary login host first executes the secondary delivery function to set delivery conditions, the delivery conditions including a receiving end message and a pending question, the pending question requiring the use of the product private key. The system responds using the receiver's private key; upon receiving the IoT product, the secondary delivery receiver answers the pending questions using the receiver's private key and the product's private key in the additional message. A correct answer indicates that the delivery conditions are met, transferring ownership of the IoT product's digital token to the secondary delivery receiver. During evidence storage, only the storage host with write permissions is allowed to sign the N digital data of the IoT product using the product's private key to generate corresponding N evidence values, which are then written into a pre-deployed digital product passport smart contract on the blockchain as evidence records. The digital product passport smart contract includes the product smart contract's contract address, the IoT product's unique identifier, and its corresponding N evidence values, where N is a positive integer. During verification, the verification host recalculates N new evidence values ​​based on the N digital data and compares them one by one with the N evidence values. If all comparisons match, it is determined whether the corresponding unique identifier is consistent with the IoT product. If so, it proves that the N digital data of the IoT product are traceable and trustworthy.

[0009] The system and method disclosed in this invention are as described above. The difference from prior art lies in that this invention deploys product smart contracts and digital product passport smart contracts on a blockchain. When producing IoT products, the login information of the IoT product (including the product public key) is encrypted and embedded into the IoT product along with the product private key as additional information. During initial login, a primary login function is executed to generate a digital token based on the additional information. When a secondary delivery is desired for a logged-in IoT product, a secondary delivery function is executed to set delivery conditions, and ownership of the digital token is transferred upon fulfillment of the delivery conditions. During notarization, the digital data of the IoT product is signed to generate a notarized value, which is then written into the digital product passport smart contract for verification.

[0010] Through the above-mentioned technical means, the present invention can achieve the technical effect of improving the traceability and trustworthiness of virtual-real coupled products. Simple Explanation of the Diagram

[0011] Figure 1 is a system block diagram of the traceable and trustworthy system of digital product passports for Internet of Things products that applies virtual and real coupling tokens according to the present invention. Figures 2A and 2B are flowcharts of the present invention's method for applying virtual-real coupled tokens to digital product passports for Internet of Things products in a traceable and trustworthy manner. Figure 3A is a schematic diagram of deploying a product smart contract using the present invention. Figure 3B is a schematic diagram of additional information of the present invention. Figure 3C is a schematic diagram of performing a primary login using the present invention. Figure 3D is a schematic diagram of applying the present invention for secondary delivery. Figure 3E is a schematic diagram illustrating the application of this invention for evidence preservation and verification. Implementation

[0012] The following will describe the implementation of the present invention in detail with reference to the drawings and embodiments, so that the process of how the present invention uses technical means to solve technical problems and achieve technical effects can be fully understood and implemented accordingly.

[0013] First, before explaining the traceable and trustworthy system and method for applying virtual-real coupled tokens to digital product passports of IoT products disclosed in this invention, let's clarify the terms defined in this invention. The virtual-real coupled tokens mentioned in this invention refer to digital tokens coupled / bound to physical IoT products. The IoT products are "physical entities," while the digital tokens are virtual "digital entities." "Product issuer host" refers to the host used by the manufacturer or issuer of the IoT product / goods. "Primary login host" refers to the host used for the initial login of the IoT product / goods. "Secondary delivery sending host" refers to the host used by the seller (current holder) when the IoT product / goods are traded in a second-hand transaction (including transactions beyond the second hand). In the first second-hand transaction, the "primary login host" is also the "secondary delivery sending host." "Secondary delivery receiving host" refers to the host used by the buyer when the IoT product / goods are traded in a second-hand transaction. The aforementioned "secondary" includes the interpretation of a power of sequence, and is not limited to the second time. Furthermore, the "product smart contract" and "digital product passport smart contract" mentioned in this invention refer to smart contracts pre-deployed on the blockchain network. The former is used to process digital tokens (such as Tokens), while the latter is bound to the product smart contract for evidence storage, such as writing / verifying evidence records. In fact, the smart contract refers to a computer program that drives the execution of instructions based on predetermined conditions and transmitted information. Specifically, the smart contract is written using procedural languages ​​such as Solidity, Serpent, LLL, EtherScript, Sidechain, etc., and can contain various functions, events, parameter states, etc., such as a primary login function and a secondary delivery function. Taking Ethereum as an example, its smart contracts are compiled into binary code and an Application Binary Interface (ABI) to broadcast the smart contract to the blockchain network. Miners or validators then upload the smart contract to the blockchain and obtain the corresponding address. This completes the deployment of the smart contract through blockchain transactions. Afterward, each node can execute the corresponding smart contract based on this address and use different instructions to change the smart contract's state on the blockchain and detect whether events have been triggered.

[0014] Please refer to Figure 1 first. Figure 1 is a system block diagram of the traceable and trustworthy digital product passport system for IoT products using virtual-real coupled tokens, as described in this invention. This system includes: a product issuer host 110, a primary login host 120, a secondary delivery receiver host 130, a certificate storage host 140, and a verification host 150. In actual implementation, each host can use a wired network, such as Ethernet, Power Line Communication (PLC), etc., or a wireless network, such as Wi-Fi, Zigbee, LoRa (Long Range), or similar technologies, to connect to the blockchain network or become one of the nodes in the blockchain network.

[0015] The product issuer host 110 includes a deployment module 111 and a production module 112. The deployment module 111 deploys a product smart contract on the blockchain, the product smart contract including a primary login function and a secondary delivery function. The production module 112 connects to the deployment module 111 and, during the production of IoT products, the product issuer host 110 encrypts the login message corresponding to the IoT product to form encrypted product content. This encrypted product content, along with the product private key, is embedded as additional information into the IoT product. The login message includes the product public key corresponding to the product private key. In practice, the product smart contract may also include owner information.

[0016] Next, in the primary login host 120, which is connected to the blockchain, the primary login host 120 includes a login module 121 and a delivery module 122. The login module 121 executes a primary login function to generate a digital token for the corresponding IoT product based on additional information when the IoT product has not undergone primary login, and records the product's public key as the verification basis for secondary delivery. The delivery module 122 connects to the login module 121 and, when secondary delivery is desired for an IoT product with a logged-in digital token, the primary login host 120 first executes a secondary delivery function to set delivery conditions. These delivery conditions include a receiver message and a pending question, which must be answered using the product's private key and the receiver's private key. In practice, the digital token may include a non-fungible token (NFT) and is generated by the primary login host 120, which serves as a public key infrastructure (PKI). In addition, the primary login function may include the product issuer's public key as the verification basis for primary login, which is used to decrypt the content encrypted with the product issuer's private key in the IoT product. When the specified message (such as a certain character, number, symbol, etc.) is obtained after decryption, it means that the verification is successful.

[0017] Next, in the secondary delivery receiver host 130, which is connected to the blockchain, upon receiving an IoT product, it answers a pending question using the receiver's private key and the product's private key from the attached message. A correct answer indicates that the delivery conditions are met, transferring ownership of the IoT product's digital token to the secondary delivery receiver. In practice, the pending question can be calculated using the product's private key and the receiver's private key; when the answer is correct, ownership of the IoT product's digital token is transferred.

[0018] In the evidence storage host 140, it connects to the blockchain and has write permissions to a pre-deployed digital product passport smart contract on the blockchain. This is used to sign N digital data points of the IoT product using the product's private key during evidence storage, generating N corresponding evidence storage values, which are then written into the digital product passport smart contract as evidence records. The digital product passport smart contract includes: the contract address of the product smart contract, the unique identifier of the IoT product, and its corresponding N evidence storage values, where N is a positive integer. In practice, the digital data may include additional information, the address of the primary login host and the address of the secondary delivery receiving host, and a Uniform Resource Identifier (URI) related to the IoT product, at least one of these three. This allows for the tracing of the IoT product's lifecycle data, including the complete transaction process, such as deriving the transaction order from the order of recorded addresses, and further obtaining corresponding product information, such as owner information, from the IoT product's unique identifier.

[0019] Finally, in the part of the verification host 150, it is connected to the blockchain to recalculate N new evidence values ​​based on N digital data during verification and compare them one by one with the N evidence values. When all the comparisons match, it is then determined whether the corresponding unique identification code is consistent with the IoT product. If so, it proves that the N digital data of the IoT product are traceable and trustworthy.

[0020] It should be noted that, in practical implementation, the host and its modules described in this invention can be partially or completely based on hardware, for example, through hardware processors such as integrated circuit chips, system-on-chips (SoCs), complex programmable logic devices (CPLDs), and field programmable gate arrays (FPGAs). The control instructions can be written using combinational language instructions, instruction set architecture instructions, machine instructions, machine-dependent instructions, microinstructions, firmware instructions, or any combination of one or more programming languages ​​to form logic circuits. These programming languages ​​include object-oriented programming languages ​​such as Common Lisp, Python, C++, Objective-C, Smalltalk, Delphi, Java, Swift, C#, Perl, Ruby, and PHP, as well as conventional procedural programming languages ​​such as C or similar languages.

[0021] Please refer to Figures 2A and 2B. Figures 2A and 2B are flowcharts of the traceable and trustworthy method for applying virtual-real coupled tokens to digital product passports for IoT products according to the present invention. The steps include: the product issuer host 110 deploys a product smart contract on the blockchain, the product smart contract including a primary login function and a secondary delivery function (step 210); when producing IoT products, the product issuer host 110 encrypts the login information corresponding to the IoT product to form encrypted product content, and attaches this encrypted product content and the product private key together. The message is embedded in the IoT product, wherein the login message includes the product public key corresponding to the product private key (step 220); when the IoT product has not performed primary login, the primary login host 120 executes the primary login function to generate the corresponding IoT product's digital token based on the additional message, and records the product public key as the verification basis for secondary delivery (step 230); when it is necessary to perform secondary delivery on an IoT product that has already logged in with a digital token, the primary login host 120 first executes the secondary delivery function to set delivery conditions, wherein the delivery conditions include the receiving end message and the question to be answered. The pending questions require answers using the product's private key and the receiver's private key (step 240). Upon receiving the IoT product, the secondary delivery receiver 130 answers the pending questions using the receiver's private key and the product's private key from the additional message. A correct answer indicates that the delivery conditions are met, transferring ownership of the IoT product's digital token to the secondary delivery receiver (step 250). During evidence storage, only the evidence storage host 140 with write permissions is allowed to use the product's private key to sign N digital data points of the IoT product, generating corresponding N evidence storage values ​​and writing them to a pre-deployed blockchain. The digital product passport smart contract serves as a record of evidence. The digital product passport smart contract includes the contract address of the product smart contract, the unique identifier of the IoT product, and its corresponding N stored values, where N is a positive integer (step 260). During verification, the verification host 150 recalculates N new stored values ​​based on the N digital data and compares them one by one with the N stored values. If all comparisons match, it is determined whether the corresponding unique identifier is consistent with the IoT product. If so, it proves that the N digital data of the IoT product are traceable and trustworthy (step 270). Through the above steps, by deploying the product smart contract and the digital product passport smart contract on the blockchain, when producing the IoT product, the login information of the IoT product (including the product public key) is encrypted and embedded into the IoT product along with the product private key as additional information. During initial login, the initial login function is executed to generate a digital token based on the additional information. When a second delivery is desired for an already logged-in IoT product, a second-level delivery function is executed to set delivery conditions, and when the delivery conditions are met, ownership of the digital token is transferred.During the notarization process, the digital data of the IoT product is signed to generate a notarized value, which is then written into the digital product passport smart contract for verification.

[0022] The following description, in conjunction with Figures 3A to 3E, illustrates an embodiment. Please refer to Figure 3A first, which is a schematic diagram of deploying a product smart contract using this invention. In actual implementation, the product issuer host 110 possesses an issuer public key and an issuer private key. When the product issuer host 110 successfully deploys the product smart contract 301 on the blockchain 300, each node's blockchain 300 will have a product smart contract 301 containing a primary login function 310 and a secondary delivery function 320. The primary login function 310 contains the product issuer public key 311.

[0023] As shown in Figure 3B, which is a schematic diagram of the additional information of the present invention. In actual implementation, when the product publisher host 110 produces the IoT product, it prepares the necessary information for logging into the IoT product as login information (including: the product public key). Then, the login information is encrypted using the publisher's private key to form encrypted product content, and together with the product private key, it is embedded (e.g., by printing, etching, laser engraving, or similar methods) into the IoT product as additional information 330. It should be noted that the present invention does not limit the way additional information is embedded into the IoT product, and any way that can combine additional information with the IoT product does not depart from the scope of application of the present invention.

[0024] As shown in Figure 3C, Figure 3C is a schematic diagram of performing primary registration using the present invention. In actual implementation, primary registration can also be called initial registration. When the purchaser obtains the physical device 450 corresponding to the IoT product from the issuer, the purchaser reads the encrypted product content 430 and the product private key 440 through the primary registration host 120, and transmits the encrypted product content 430 to the primary registration function 310. The primary registration function 310 decrypts the encrypted product content 430 using the stored product issuer public key 311 to obtain the decrypted content. When the decrypted content matches the registration message, the ownership of the digital token 510 is transferred to the primary registration host 120 to complete the primary registration.

[0025] As shown in Figure 3D, Figure 3D is a schematic diagram of secondary delivery using this invention. In practice, secondary delivery can also be referred to as second-hand product transfer. When a secondary delivery is desired for an already registered IoT product, the current product holder can call the secondary delivery function 320 through the secondary delivery sending host 610 to set delivery conditions, namely: specifying the digital token 510 to be delivered, the address of the secondary delivery receiving host 620, and the delivery timeout, etc., as delivery conditions. Then, the secondary delivery sending host 610 requests the secondary delivery receiving host 620 to provide encrypted delivery content based on the address of the secondary delivery receiving host 620. When the current product holder has indeed delivered the physical device 450 corresponding to the IoT product to the buyer, a delivery condition can be set through the secondary delivery sending host 610 for the secondary delivery function 320, such as: determining the receiving end, a question that needs to be answered using the product private key and the receiving end private key, and the delivery timeout, etc. If the delivery is completed before the timeout period and the question is answered correctly, ownership of the digital token 510 is transferred to the designated receiver, namely, the secondary delivery receiver host 620. In this way, the ownership of the IoT product and its digital token 510 is maintained in a consistent manner.

[0026] As shown in Figure 3E, which is a schematic diagram illustrating the application of this invention for evidence storage and verification, in practice, an initial holder is first designated. This holder then pre-deploys a digital product passport smart contract 710 on blockchain 300. This contract only allows the evidence storage host 730 with write permissions to sign N digital data points of the IoT product using the product's private key, thereby generating N corresponding evidence storage values. For example, the signing result can be directly used as the evidence storage value. Next, these evidence storage values ​​are written into the digital product passport smart contract 710 as evidence storage records (721a~721n), which can also be considered as lifecycle data. It is particularly important to note that the digital product passport smart contract 710 contains the contract address of the product smart contract 301, meaning that the digital product passport smart contract 710 is bound to the product smart contract 301. In addition, the digital product passport smart contract 710 also contains the IoT product's unique identifier 720 and its corresponding N evidence storage values ​​forming the evidence storage records (721a~721n). Furthermore, the Digital Product Passport smart contract 710 can also standardize the conversion methods of digital data, such as N-ary encoding and hash algorithms, to encode and hash the digital data before signing. Next, the holder can designate a writer with write permissions (i.e., the certificate storage host 730) to write to the Digital Product Passport smart contract 710, even specifying the number of writes, expiration time, etc. In this way, the certificate storage host 730 can convert the digital data according to the specifications to obtain the certificate value and write it to the Digital Product Passport smart contract 710. Afterwards, to verify the trustworthiness of the digital data, the verification host 740 can first convert the obtained digital data according to the same specifications to obtain a new certificate value, and then compare it with the certificate records (721a~721n) on blockchain 300. If they are completely identical, it means that the digital data is consistent and trustworthy.

[0027] In summary, the difference between this invention and prior art lies in deploying product smart contracts and digital product passport smart contracts on the blockchain. When producing IoT products, the product's login information (including the product's public key) is encrypted and embedded into the IoT product along with the product's private key as additional information. During initial login, a primary login function is executed to generate a digital token based on the additional information. When a secondary delivery is desired for a logged-in IoT product, a secondary delivery function is executed to set delivery conditions, and ownership of the digital token is transferred upon fulfillment of the delivery conditions. During notarization, the digital data of the IoT product is signed to generate a notarized value, which is then written into the digital product passport smart contract for verification. This technical approach solves the problems existing in prior art, thereby achieving the technical effect of improving the traceability and trustworthiness of virtual-physical coupled products.

[0028] Although the present invention has been disclosed above with reference to the foregoing embodiments, it is not intended to limit the present invention. Anyone skilled in the art can make some modifications and refinements without departing from the spirit and scope of the present invention. Therefore, the scope of patent protection of the present invention shall be determined by the scope of the patent application attached to this specification.

[0029] 110: Product Publisher Hosting 111: Deployment Module 112: Production Module 120: Primary Login Host 121: Login Module 122: Delivery Module 130: Secondary Delivery Receiver Host 140: Evidence Storage Host 150: Verify Host 300: Blockchain 301: Product Smart Contract 310: Basic Login Function 311: Product Publisher Public Key 320: Level 2 Delivery Form 330: Additional Message 430: Encrypted Product Content 440: Product Private Key 450: Physical device 510: Digital Tokens 610: Secondary delivery sending end host 620: Secondary Delivery Receiver Host 710: Digital Product Passport Smart Contract 720: Unique Identifier 721a~721n: Evidence Records 730: Evidence Storage Host 740: Verify Host Step 210: The product issuer's host deploys a product smart contract on a blockchain. The product smart contract includes a primary login function and primary and secondary delivery functions. Step 220: When producing an IoT product, the product issuer's host encrypts a login message corresponding to the IoT product to form encrypted product content, and embeds the encrypted product content and a product private key together as additional information into the IoT product. The login message includes a product public key corresponding to the product private key. Step 230: When the IoT product has not undergone primary login, a primary login host executes the primary login function to generate a digital token for the corresponding IoT product based on the additional information, and records the product public key as the verification basis for secondary delivery. Step 240: When performing secondary delivery on the IoT product that has been logged into the digital token, the primary login host first executes the secondary delivery function to set a delivery condition. The delivery condition includes a receiving end message and a pending question. The pending question needs to be answered using the product's private key and a receiving end private key. Step 250: Upon receiving the IoT product, the primary and secondary delivery receiver hosts answer the pending question using the receiver's private key and the product's private key from the additional message. A correct answer indicates that the delivery conditions are met, transferring ownership of the digital token of the IoT product to the secondary delivery receiver. Step 260: During the notarization process, only one notarization host with write permissions is allowed to sign N digital data points of the IoT product using the product's private key to generate N corresponding notarization values. These values ​​are then written into a digital product passport smart contract pre-deployed on the blockchain as notarization records. The digital product passport smart contract includes a contract address of the product smart contract, a unique identifier of the IoT product, and its corresponding N notarization values, where N is a positive integer. Step 270: During verification, a verification host recalculates N new evidence values ​​based on the N digital data and compares them one by one with the N existing evidence values. If all comparisons match, it is then determined whether the corresponding unique identifier is consistent with the IoT product. If so, it proves that the N digital data of the IoT product are traceable and trustworthy.

Claims

1. A traceable and trusted system for digital product passports applied to IoT products using virtual-real coupled tokens, the system comprising: a product issuer host, which includes: a deployment module for deploying a product smart contract on a blockchain, the product smart contract including a primary login function and a first- and second-level delivery function, wherein the primary login function includes a product issuer public key; and a production module connected to the deployment module, used for, when producing an IoT product, the product issuer host encrypts a login message corresponding to the IoT product with a product issuer private key to form encrypted product content, and embeds the encrypted product content and a product private key together as additional information into the IoT product, wherein... The login message includes a product public key corresponding to the product private key; a primary login host, connected to the blockchain, the primary login host includes: a login module, used to execute the primary login function to generate a digital token for the corresponding IoT product according to the additional message when the IoT product has not performed primary login, and to decrypt the encrypted content of the IoT product encrypted with the product issuer's private key using the product issuer's public key to obtain the product public key included in the login message; when the product public key matches the login message of the product issuer host, the ownership of the digital token is transferred to the primary login host, and the product public key is recorded as the verification basis for secondary delivery; A delivery module, connected to the login module, is configured to, when performing secondary delivery on an IoT product that has already been logged into with the digital token, first execute the secondary delivery function to set a delivery condition, the delivery condition including a receiving end message and a pending question, the pending question requiring the use of the product private key and a receiving end private key; a secondary delivery receiving end host, connected to the blockchain, is configured to, upon receiving the IoT product, answer the pending question using the receiving end private key and the product private key in the additional message, when the answer is correct, indicating that the delivery condition is met, thereby transferring ownership of the digital token of the IoT product to the secondary delivery receiving end. A storage host, connected to the blockchain, has write permissions to a digital product passport smart contract pre-deployed on the blockchain. During storage, it uses the product's private key to sign N digital data points of the IoT product, generating N corresponding storage values, which are then written into the digital product passport smart contract as storage records. The digital product passport smart contract includes a contract address, a unique identifier for the IoT product, and its corresponding N storage values, where N is a positive integer. A verification host, connected to the blockchain, recalculates N new storage values ​​based on the N digital data points during verification. These new storage values ​​are compared one by one with the existing N storage values. If all comparisons match, the unique identifier is checked against the IoT product. If they match, the N digital data points of the IoT product pass verification.

2. The traceable and trusted system for applying virtual-real coupled tokens to digital product passports of IoT products, as requested in Request 1, wherein the digital tokens include non-fungible tokens (NFTs) and are generated through the primary login host, which serves as public key infrastructure (PKI).

3. As requested in Item 1, the application of virtual-real coupled tokens to a traceable and trusted digital product passport system for IoT products, wherein the digital data includes the additional information, the address of the primary login host and the address of the secondary delivery receiver host, and a Uniform Resource Identifier (URI) associated with the IoT product, at least one of the three.

4. As requested in Item 1, the application of virtual-real coupled tokens to a traceable and trusted digital product passport system for Internet of Things products, wherein the digital product passport smart contract includes a conversion method for the digital data, the conversion method including at least one of encoding and hash algorithms, for first encoding and hashing the digital data and then signing it to generate the stored value.

5. A traceable and trustworthy method for applying virtual-real coupled tokens to digital product passports in Internet of Things (IoT) products, comprising the following steps: A product issuer host deploys a product smart contract on a blockchain. The product smart contract includes a primary login function and a first- and second-level delivery function. The primary login function contains a product issuer public key. When producing an IoT product, the product issuer host encrypts a login message corresponding to the IoT product using a product issuer private key to form encrypted product content. The encrypted product content and the product private key are then embedded into the IoT product as an additional message. The login message contains a product public key corresponding to the product private key. When the IoT product has not undergone primary login, a primary login host executes the primary login function to generate a digital token for the IoT product based on the additional message. The primary login host decrypts the encrypted product content encrypted with the product issuer private key using the product issuer public key to obtain the product public key contained in the login message. When the product public key matches the login message of the product issuer host, ownership of the digital token is transferred to the primary login host, and the product public key is recorded as the verification basis for second-level delivery. When a secondary delivery is to be performed on an IoT product that has been logged into with the digital token, the primary login host first executes the secondary delivery function to set a delivery condition. The delivery condition includes a receiving end message and a pending question. The pending question needs to be answered using the product's private key and a receiving end private key. When the IoT product is received, the primary and secondary delivery receiving end hosts then answer the pending question using the receiving end private key and the product's private key in the additional message. A correct answer indicates that the delivery condition has been met, and ownership of the digital token of the IoT product is transferred to the secondary delivery receiving end. During evidence preservation, only one host with write permissions is allowed to sign N digital data points of the IoT product using the product's private key to generate N corresponding evidence preservation values. These values ​​are then written into a digital product passport smart contract pre-deployed on the blockchain as evidence preservation records. The digital product passport smart contract includes a contract address of the product smart contract, a unique identifier of the IoT product, and its corresponding N evidence preservation values, where N is a positive integer. During verification, a verification host recalculates N new evidence preservation values ​​based on the N digital data points and compares them one by one with the N existing evidence preservation values. If all comparisons match, the unique identifier is then checked to see if it matches the IoT product. If it does, the N digital data points of the IoT product pass verification.

6. A traceable and trusted method for applying virtual-real coupled tokens to digital product passports of IoT products, as described in Request 5, wherein the digital tokens include non-fungible tokens (NFTs) and are generated through the primary login host, which serves as a public key infrastructure (PKI).

7. A traceable and trustworthy method for applying virtual-real coupled tokens to digital product passports of IoT products, as described in Request 5, wherein the digital data includes the additional information, the address of the primary login host and the address of the secondary delivery receiver host, and a Uniform Resource Identifier (URI) associated with the IoT product, at least one of the three.

8. A traceable and trustworthy method for applying virtual-real coupled tokens to digital product passports of Internet of Things products, as described in Request 5, wherein the digital product passport smart contract includes a conversion method for the digital data, the conversion method including at least one of encoding and hash algorithms, for first encoding and hashing the digital data and then signing it to generate the stored value.

Images