Management of digital assets

Patent metadata

Field	Value
Publication number	US-11089096-B2
Application number	US-201816135529-A
Country	US
Kind code	B2
Filing date	Sep 19, 2018
Priority date	Sep 19, 2018
Publication date	Aug 10, 2021
Grant date	Aug 10, 2021

Abstract

An example operation may include one or more of connecting, by a recipient node, to a blockchain network configured to store links to digital assets of an owner, selecting, by the recipient node, an asset from a ledger of the owner, executing, by the recipient node, a smart contract to determine a time frame of the asset use, executing, by the recipient node, a smart contract to download the asset to the recipient node, checking, by the recipient node, if the asset is downloaded successfully, and in response to the successful download of the asset, executing, by the recipient node, a smart contract to log an asset transfer transaction onto the blockchain.

First claim

What is claimed is:

1. A system, comprising:
a processor;
a memory on which are stored machine readable instructions that when executed by the processor, cause the processor to:
connect to a blockchain network configured to store links to digital assets of an owner;
select an asset from a ledger of the owner;
execute a smart contract to determine a time frame of the asset use;
execute a smart contract to download the asset;
check if the asset is downloaded successfully; and
in response to the successful download of the asset, execute a smart contract to log an asset transfer transaction onto the blockchain.

2. The system of claim 1 , wherein the instructions are further to cause the processor to enter a key to the asset into the blockchain.

3. The system of claim 1 , wherein the instructions are further to cause the processor to sync with the blockchain prior to the download of the asset.

4. The system of claim 1 , wherein the instructions are further to cause the processor to confirm that the blockchain has a permission to access the asset and to transfers the asset to another user.

5. The system of claim 1 , wherein the instructions are further to cause the processor to resolve a file format of the asset.

6. The system of claim 1 , wherein the instructions are further to cause the processor to encode the asset owner data with the asset into a block.

7. The system of claim 6 , wherein the instructions are further to cause the processor to encode data that reflects a transfer of the asset to a new owner along with the time frame of the asset use into the block with the asset.

8. A method, comprising:
connecting, by a recipient node, to a blockchain network configured to store links to digital assets of an owner;
selecting, by the recipient node, an asset from a ledger of the owner;
executing, by the recipient node, a smart contract to determine a time frame of the asset use;
executing, by the recipient node, a smart contract to download the asset to the recipient node;
checking, by the recipient node, if the asset is downloaded successfully; and
in response to the successful download of the asset, executing, by the recipient node, a smart contract to log an asset transfer transaction onto the blockchain.

9. The method of claim 8 , further comprising entering a key to the asset into the blockchain.

10. The method of claim 8 , further comprising syncing with the blockchain prior to the download of the asset.

11. The method of claim 8 , further comprising confirming that the blockchain has a permission to access the asset and to transfers the asset to another user.

12. The method of claim 8 , further comprising resolving a file format of the asset.

13. The method of claim 8 , further comprising encoding the asset owner data with the asset into a block.

14. The method of claim 13 , further comprising encoding data that reflects a transfer of the asset to a new owner along with the time frame into the block with the asset.

15. A non-transitory computer readable medium comprising instructions, that when read by a processor, cause the processor to perform:
connecting to a blockchain network configured to store links to digital assets of an owner;
selecting an asset from a ledger of the owner;
executing a smart contract to determine a time frame of the asset use;
executing a smart contract to download the asset;
checking if the asset is downloaded successfully; and
in response to the successful download of the asset, executing a smart contract to log an asset transfer transaction onto the blockchain.

16. The non-transitory computer readable medium of claim 15 further comprising instructions, that when read by the processor, cause the processor to enter a key to the asset into the blockchain.

17. The non-transitory computer readable medium of claim 15 further comprising instructions, that when read by the processor, cause the processor to sync with the blockchain prior to the download of the asset.

18. The non-transitory computer readable medium of claim 15 further comprising instructions, that when read by the processor, cause the processor to confirm that the blockchain has a permission to access the asset and to transfers the asset to another user.

19. The non-transitory computer readable medium of claim 15 further comprising instructions, that when read by the processor, cause the processor to resolve a file format of the asset.

20. The non-transitory computer readable medium of claim 15 further comprising instructions, that when read by the processor, cause the processor to encode data that reflects a transfer of the asset to a new owner along with the time frame of the asset use into a block with the asset.

Assignees

• IBM

Inventors

• Schultz Kevin L
• Adderly Darryl
• Mannan Rosanna
• Masini Diego A
• Garagiola Andres
• Ponceleon Dulce B

Classifications

• H04L9/50

  using hash chains, e.g. blockchains or hash trees · CPC title

• G06F2221/2137

  Time limited access, e.g. to a computer or data · CPC title

• H04L67/1074 Primary

  for supporting data block transmission mechanisms (file transfer H04L67/06) · CPC title

• H04L9/3239

  involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD · CPC title

• G06F21/64

  Protecting data integrity, e.g. using checksums, certificates or signatures · CPC title