SYSTEM AND METHOD FOR GENERATING A NON-FUNGIBLE TOKEN ASSOCIATED TO AN ITEM

Abstract

The present invention relates to a method for creating a non-fungible token associated to an item, wherein the method comprises the steps of: providing general information about the item; providing information about the owner of the item; confirming the information about the owner of the item; and generating the non-fungible token based on the general information about the item, wherein the step of generating the non-fungible token comprises storing the confirmed information about the owner of the item in the non-fungible token.

Claims

1. Method for generating a non-fungible token associated to an item, wherein the method comprises the steps of: providing general information about the item; providing information about the owner of the item; confirming the information about the owner of the item; and generating the non-fungible token based on the general information about the item, wherein the step of generating the non-fungible token comprises storing the confirmed information about the owner of the item in the non-fungible token.

2. Method according to claim 1, wherein the method further comprises the step of confirming the general information about the item, and wherein the non-fungible token is generated based on the confirmed general information about the item.

3. Method according to claim 1, wherein the step of confirming the information about the owner of the item comprises verifying the identity of the owner of the item or biometric identifiers of the owner of the item.

4. Method according to claim 1, wherein the method further comprises the steps of, for all parts of the item, providing information about the creation of the corresponding part of the item, for all parts of the item validating the provided information about the creation of the corresponding part of the item, wherein, for all parts of the item, the validated information about the creation of the corresponding part is respectively stored in the non-fungible token together with information about when the corresponding part of the item was created or an IP address used when creating the corresponding part of the item or an electronic signature of the creator of the corresponding part of the item.

5. The method according to claim 4, wherein the method comprises the step of using a cryptographic function to create a digest based on the confirmed information about the owner of the item, or the validated information about the creation of each of the parts of the item, respectively together with the information about when the corresponding part of the item was created, or the IP address used when creating the corresponding part of the item, or the electronic signature of the creator of the corresponding part of the item, and wherein the digest is stored in the non-fungible token.

6. Method according to claim 1, wherein the method further comprises the step of storing the non-fungible token on a decentralized storage system.

7. Method according to claim 1, wherein the method further comprises the step of providing at least one governance parameter for the non-fungible token, and wherein the step of generating the non-fungible token comprises generating the non-fungible token based on the general information about the item and the at least one governance parameter.

8. Method for authenticating an item, wherein the method comprises the steps of: Generating a non-fungible token associated to the item by a method for generating a non-fungible token associated to an item according to claim 1; and Authenticating the item based on the generated non-fungible token associated to the item.

9. System for generating a non-fungible token associated to an item, wherein the system is configured to execute a method for generating a non-fungible token associated to an item according to claim 1.

10. System for authenticating an item, wherein the system comprises a receiver that is configured to receive a non-fungible token associated to an item generated by a system for generating a non-fungible token associated to an item according to claim 9, and wherein the system is configured to authenticate the item based on the received non-fungible token associated to the item.

11. Computer program product comprising instructions which, when executed by a computer, cause the computer to carry out the steps of the method for generating a non-fungible token associated to an item according to claim 1.

Description

DESCRIPTION OF THE DRAWINGS

[0042] Embodiments of the invention will now be described with reference to the drawings.

[0043] FIG. 1 illustrates a flow chart of a method for authenticating items according to embodiments of the invention;

[0044] FIG. 2 illustrates a system for authenticating items according to embodiments of the invention.

DETAILED DESCRIPTION

[0045] FIG. 1 illustrates a flow chart of a method 1 for authenticating items according to embodiments of the invention.

[0046] When a medical device such as a pacemaker or a deep brain stimulation device is accessed or updated, it is important to first verify that it is allowed to correspondingly access or to update the medical device, in order to avoid significant health risks.

[0047] For example, there are implantable devices used to monitor physiological parameters and to deliver stimulation signals or therapy to selected organs. An external programmer is often used by physicians or technicians to communicate data with an implantable device. The data may include measured parameters, electrocardiograms, markers, instructions, identification information and other such data.

[0048] With the advent of far field communications for implantable devices, cloud-based software or parameter updates are possible. Whether the data used by the implantable device is set or updated by an external, near-filed programmer or a far field programmer or cloud system, it is essential to prevent unauthorized or unintended communications with an implantable device. Such communications can result in a minor inconvenience or tragic, life threatening, consequences or any level of risk in between those extremes.

[0049] Further, it is important to incorporate security between communication devices, for example Internet of Things (IOT)-devices, to avoid significant security issues.

[0050] For example, it is important to ensure traceability of the data and operations created and performed, respectively, by IoT-devices.

[0051] Therein, it is known to use utility or non-fungible tokens in applications that require immutable evidence of valid agreement or contracts between different parties, provenance or ownership, what has been proven as extremely reliable.

[0052] A utility token is a simple token that enables future access to items respectively assets or products or services offered by an organization. Thus, a utility token offers a specific utility within a decentralized application. Therein, utility tokens usually are a form of digital assets created for spending within a blockchain ecosystem.

[0053] Further, a non-fungible token is a unique and non-interchangeable unit of data stored in a digital ledger, respectively a digital asset that contains identifying information recorded in one or more smart contracts. In particular, a non-fungible token is a unit of data stored on a digital ledger, respectively a blockchain ledger, that can be sold and traded, wherein the non-fungible token can be associated with a particular digital or physical asset and a license to use the asset for a specific purpose.

[0054] Non-fungible tokens are advantageous regarding proof of ownership of an item, wherein since non-fungible tokens are on a blockchain network, they can help in associating ownership to a single user or account. In particular, non-fungible tokens are indivisible and cannot be distributed among multiple owners. Further, non-fungible tokens are respectively unique, wherefore they can be used to verify authenticity of an item. Furthermore, non-fungible tokens are easily tradeable freely on particular markets with a wide range of options for trading.

[0055] However, once a non-fungible token is lost or stolen, it is generally irretrievable. Further, there is a risk of false or corrupted data inherent in the file validation processes and non-fungible tokens are usually stored on centralized servers which are vulnerable to attacks. Therefore, there is a need for a method for creating generating an improved non-fungible token.

[0056] According to the method shown in FIG. 1, general information about an item is provided by a user in a step 2, information about the owner of the item is provided by at least one further user in a step 3, the information about the owner of the item is confirmed in a step 4, and in a step 5 a non-fungible token is created based on the general information about the item, wherein the step 5 of generating the non-fungible token comprises storing the confirmed information about the owner of the item in the non-fungible token.

[0057] That the confirmed information about the owner of the item is stored in the non-fungible token has the advantage that the lawful owner of the item can always be identified, whereby immutable trust can be created. The method can also be used to reissue a stolen or lost non-fungible token in a simple manner to its lawful owner, wherein the non-fungible token can be reissued based on the owner's validated identity and a proof of creation of the item, wherein retrieving the non-fungible token can be further subject to legal due diligence, and wherein the lost or stolen original non-fungible token is burnt.

[0058] Further, the non-fungible token can be generated in an effective and cost-efficient manner, as the provided information can easily be provided via known input means, wherefore no expensive and time-consuming modifications of the corresponding data processing system are required.

[0059] Therefore, FIG. 1 shows a method 1 for generating an improved non-fungible token associated to an item.

[0060] As shown in FIG. 1, the method further comprises a step 6 of confirming the general information about the item, wherein the non-fungible token is generated based on the confirmed general information about the item, and wherein the general information can for example be confirmed based on input provided by at least a third party.

[0061] According to the embodiments of FIG. 1, the step 3 of confirming the information about the owner of the item comprises verifying the credentials of the user, for example by verifying biometric information of the user such as fingerprint recognition or biometric iris recognition, or by a KYC (Know Your Customer) process, wherein the non-fungible token is only generated if the credentials of the owner of the item have been successfully verified.

[0062] As shown in FIG. 1, the method further comprises a step 7 of, for all parts of the item, respectively providing information about the creation of the corresponding part of the item, and a step 8 of, for all parts of the item, respectively validating the information about the creation of the corresponding part of the item. The shown step 5 of generating the non-fungible token further comprises, for all parts of the item, respectively storing the validated information about the creation of the corresponding part of the item in the non-fungible token together with information about when the corresponding part of the item was created or an IP address used when creating the corresponding file or part of the item or an electronic signature of the creator of the corresponding file or part of the item.

[0063] Therein, the information when the corresponding file or part of the item was created can include a time stamp including information about a particular date and a particular time when the corresponding file or part of the item was created.

[0064] According to the embodiments of FIG. 1, the step 5 of generating the non-fungible token comprises using a cryptographic function to create a digest based on the confirmed information about the owner of the item or the validated information about the creation of each of the parts of the item, respectively together with the information about when the corresponding part of the item was created or the IP address used when creating the corresponding part of the item or the electronic signature of the creator of the corresponding part of the item, wherein the digest is thereafter stored in the non-fungible token.

[0065] Therein, the computed digest can be included in smart contract instructions for minting the non-fungible token.

[0066] Further, the computed digest and standard attributes, for example a validity period of the non-fungible token and a type of the non-fungible token, are used to create the non-fungible token and to map a smart contract respectively agreement to the non-fungible token, wherein the corresponding smart contract can be executed on the blockchain of choice. In particular, the computed digest and the standard attributes are processed to be included into corresponding smart contract instructions for minting the non-fungible token, wherein the non-fungible token is created in such a way, that the provided information characterizing the item is stored in the metadata of the non-fungible token unique resource identifier.

[0067] According to the embodiments of FIG. 1, the generated non-fungible token is further stored in a decentralized storage system, in particular a blockchain ledger. Therein, the particular decentralized storage system, on which the generated non-fungible token is stored, can for example be selected by a user.

[0068] A blockchain is a distributed ledger, similar to a database, wherein the ledger is dispersed across multiple computers that can be connected by a network. In particular, a blockchain is a ledger through which data is added and updated in real-time, wherein, once the data is added to the ledger, it cannot be removed or simply edited anymore.

[0069] The blockchain ledger can be configured to maintain a verified blockchain public ledger version of the created non-fungible token, whereby a non-fungible token and for example ownership of the corresponding item can easily and reliably be validated.

[0070] The created non-fungible token can then be hold in custody or be transferred to a wallet of the user or owner that has provided the item.

[0071] With uploading the item or the general information about the item in step 2, the owner of the item can also define whether the item should remain in the public or the private domain, wherein the choice of the user determines accessibility to the item and external user privileges.

[0072] The non-fungible token may be issued in several different scenarios for both, online and offline usage. For example, the non-fungible token may be issued to authenticate a medical device or an IoT-device. However, the created non-fungible token may for example also be used as collateral for financing regarding trade finance or as deed of ownership. Further, the created non-fungible token may for example also allow for broader application in insurance risk transfer contracts, or to protect and verify information such as intellectual property, media rights, news, scholarly articles, scientific research, art, or computer code.

[0073] Based on the created non-fungible token, further a legally binding, time stamped and reliable mechanism for authenticating items or contracts is provided.

[0074] Therein, as shown in FIG. 1, the method 1 further comprises a step 9 of authenticating the item based on the created non-fungible token associated to the item.

[0075] Based on the authentication of the item, further steps, for example security relevant steps may then be initiated. For example, in step 9 a medical device can be authenticated based on the created non-fungible token associated to the medical device, wherein, based on the authentication, it can be validated if it is allowed to correspondingly access or to update the medical device, and wherein the corresponding medical device can only be accessed or updated if it has been validated that it is allowed to access or update the medical device. Further, for example an IoT-device may only be used if it the IoT-device has been authenticated, so that traceability of the data and operations created and performed by the corresponding IoT-device can be ensured.

[0076] According to the embodiments of FIG. 1, based on the authentication process in step 9, only a limited, non-critical set of information associated with the item linked to the corresponding token is displayed on a display, if the authentication of the item was not successful, and a full set of information associated with the item is displayed, if the authentication of the item was successful.

[0077] Further, if the authentication was not successful, security relevant actions, for example issuing a notice to the owner of the system, a producer or a seller, or shutting down the item can be initiated.

[0078] Further, the method can be implemented in such a way, that a user that wants to authenticate the item can hold native utility tokens, in order to be able to request for authentication of the item to be linked to the created non-fungible token, whereby the security can be further improved. On the other hand, authentication of an item linked or associated with the created non-fungible token in the private domain may be limited to nominated users or authenticated approved users.

[0079] FIG. 2 illustrates a system 10 for authenticating items according to embodiments of the invention.

[0080] As shown in FIG. 2, the system 10 comprises a system for generating a non-fungible token associated to an item 11, and a system for authenticating an item 12.

[0081] According to the embodiments of FIG. 2, the system for generating a non-fungible token associated to an item 11 comprises a first input device 13 for providing general information about the item by a user, usually the owner of the item, at least one second input device 14 for providing information about the owner of the item, a confirming device 15 that is configured to confirm the information about the owner of the item, and a generating device 16 that is configured to generate a non-fungible token associated with the item based on the general information about the item, wherein the generating device is further configured to store the confirmed information about the owner of the item in the non-fungible token.

[0082] The generating device can for example be realized based on code that is stored in a memory and executable by a processor.

[0083] According to the embodiments of FIG. 2, the system 10 can be further configured in such a way, that the general information about the item can be confirmed, for example based on input provided by corresponding input means, wherein the generating device 16 is configured to generate the non-fungible token based on the confirmed general information about the item

[0084] The confirming device can for example also be realized based on code that is stored in a memory and executable by a processor or corresponding sensing means for example biometric sensing devices. In particular, according to the embodiments of FIG. 2, the confirming device 15 is configured to confirm the information about the owner by verifying the identity of the owner of the item or biometric identifiers of the owner of the item.

[0085] As shown in FIG. 2, the system for creating a non-fungible token associated to an item 11 further comprises a providing device 17 that is configured to, for all parts of the item, provide information about the creation of the corresponding part of the item, and a validating device 18 that is configured to, for all parts of the item, validate the provided information about the creation of the corresponding part of the item, wherein the generating device 16 is configured to, for parts of the item, store the validated information about the creation of the corresponding file or part in the non-fungible token together with information when the corresponding file or part of the item was created, or an IP address used when creating the corresponding file or part of the item or an electronic signature of the creator of the corresponding file or part of the item.

[0086] Therein, also the providing device and the validating device can for example both be realized based on code that is stored in a memory and executable by a processor.

[0087] According to the embodiments of FIG. 2, the generating device 16 is further configured to use a cryptographic function to create a digest based on the confirmed information about the owner of the item or the validated information about the creation of each of the parts of the item, respectively together with the information about when the corresponding part of the item was created or the IP address used when creating the corresponding part of the item or the electronic signature of the creator of the corresponding part of the item, wherein the digest is stored in the non-fungible token.

[0088] The shown system for generating a non-fungible token associated to an item 11 further comprises a storing device 19 that is configured to store the generated non-fungible token on a decentralized storage system.

[0089] The storing device can for example be realized based on code that is stored in a memory and executable by a processor.

[0090] There is further shown a receiver 20 for receiving at least one governance parameter for the non-fungible token, wherein the generating device 16 is configured to generate the non-fungible token based on the computed digest and the at least one governance parameter.

[0091] As further shown in FIG. 2, the system for authenticating an item 12 comprises a further receiver 21 for receiving the non-fungible token associated to the item generated by the system for generating a non-fungible token associated to an item 11 and an authentication device 22 that is configured to authenticate the item based on the created non-fungible token associated to the item.

[0092] Therein, the authentication device can for example be realized based on code that is stored in a memory and executable by a processor.

[0093] The shown system is further configured to execute a method for authenticating an item as described above.