System and method for secure storage, transfer and retrieval of content addressable information

• US 8,261,066 B2
• Filed: 03/30/2005
• Issued: 09/04/2012
• Est. Priority Date: 09/07/1999
• Status: Expired due to Term

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Carpentier, Paul R., Van Riel, Jan F., Teugels, Tom
• Primary Examiner(s): Vu, Kim
• Assistant Examiner(s): TRUVAN, LEYNNA THANH
• Application Number:
  US11/094,026
• Publication Number:
  US 20050172124A1
• Time in Patent Office: 2,715 Days
• Field of Search: 707 1- 9, 707/100, 707/102, 707/103.R, 707/103.Y, 707/103.Z, 707/200, 707202-203, 707/212, 709212-216, 726 3- 4, 726 18- 19
• US Class Current: 713/165
• CPC Class Codes: G06F 16/30 of unstructured textual data document management systems G06F16/93
• CPC Class Codes: G06F 21/00 Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
• CPC Class Codes: G06F 21/60 Protecting data
• CPC Class Codes: G06F 21/64 Protecting data integrity, e.g. using checksums, certificates or signatures
• CPC Class Codes: H04L 69/00 Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass networks security protocols H04L9/40; wireless communication networks H04W
• CPC Class Codes: H04L 9/0861 Generation of secret information including derivation or calculation of cryptographic keys or passwords
• CPC Class Codes: H04L 9/0894 Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage
• CPC Class Codes: H04L 9/3236 using cryptographic hash functions
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

An algorithm (such as the MD5 hash function) is applied to a file to produce an intrinsic unique identifier (IUI) for the file (or message digest). The file is encrypted using its IUI as the key for the encryption algorithm. An algorithm is then applied to the encrypted file to produce an IUI for the encrypted file. The encrypted file is safely stored or transferred within a network and is uniquely identifiable by its IUI. The encrypted file is decrypted using the IUI of the plaintext file as the key. The IUI serves as both a key to decrypt the file and also as verification that the integrity of the plaintext file has not been compromised. IUIs for any number of such encrypted files may be assembled into a descriptor file that includes meta data for each file, the IUI of the plaintext file and the IUI of the encrypted file. An algorithm is applied to the descriptor file to produce an IUI for the descriptor file. The plaintext descriptor file is then encrypted using the descriptor file IUI as a key for the encryption algorithm. An algorithm is applied to the encrypted descriptor file to produce an IUI for the encrypted descriptor file. The IUI of the encrypted descriptor file is a location-independent identifier to locate the encrypted descriptor file. A flattened descriptor file includes the IUIs of encrypted data files and the IUI of the encrypted descriptor file. An algorithm is applied to the flattened descriptor file to produce its own IUI.

Claims

1. A method of managing a plurality of digital assets stored in a computer system comprising at least a first computer, the plurality of digital assets comprising a first digital asset, the first digital asset comprising content and having associated metadata, the method comprising acts of:

(A) creating a customized first descriptor file that comprises content that includes at least some of the metadata associated with the first digital asset and an identifier of the first digital asset that is based, at least in part, on a cryptographic hash of at least some of the content of the first digital asset, the first descriptor file being a first type of descriptor file that is one of a plurality of customized descriptor file types created by a user, at least some metadata and behavior being automatically added to the first descriptor file based on the first descriptor file being of the first type, wherein the behavior that is automatically added to the first descriptor file based on the first descriptor file being of the first type is specified by the user and causes the first descriptor file to be placed in a particular folder based on the first descriptor file being of the first type, wherein the particular folder in which the first descriptor file is placed is specified by the user; and

(B) storing the first descriptor file on the computer system in the particular folder so that the first descriptor file is accessible as one of the plurality of digital assets and creating an identifier of the first descriptor file that is based, at least in part, on a cryptographic hash of at least some of the content of the first descriptor file.

2. The method of claim 1, wherein the plurality of digital assets comprises a second digital asset, the second digital asset comprising data and having associated metadata, and wherein the method further comprises acts of:

(C) creating a second descriptor file that comprises at least some of the metadata associated with the second digital asset, the second descriptor file being a second type of descriptor file, at least some metadata being automatically added to the second descriptor file based on the second descriptor file being of the second type, wherein the at least some metadata automatically added to the second descriptor file differs in at least some respects from the at least some metadata automatically added to the first descriptor file; and

(D) storing the second descriptor file on the computer system so that the second descriptor file is accessible as one of the plurality of digital assets.

3. The method of claim 1, wherein the first computer manages storage of the first digital asset, wherein the computer system further comprises a second computer having an application program that generates the first digital asset, and wherein the act (B) comprises an act of storing the first descriptor file in a manner that enables the first descriptor file to be accessed by the application program.

4. The method of claim 1, wherein the act (B) comprises an act of storing the first descriptor file as a file on the computer system.

5. The method of claim 1, further comprising an act of:

(C) creating a unique identifier for the first descriptor file, the unique identifier comprising information that identifies the first descriptor file as belonging to a class of digital assets that comprise metadata relating to other digital assets.

6. The method of claim 5, further comprising an act of:

(D) creating a unique identifier for the first digital asset, the unique identifier for the first digital asset comprising information that identifies the first digital asset as belonging to a class of digital assets that do not comprise metadata relating to other digital assets.

7. The method of claim 1, wherein the first computer is a silo that manages storage of the first digital asset.

8. The method of claim 1, wherein the first computer is a file server that manages storage of the first digital asset.

9. The method of claim 1, wherein the first computer is a storage system that manages storage of the first digital asset.

10. The method of claim 1, wherein the computer system comprises a plurality of computers in addition to the first computer, wherein the plurality of computers are interconnected by at least one network, and wherein each of the plurality of computers manages storage of one or more of the plurality of digital assets.

11. The method of claim 1, wherein the computer system further comprises a second computer and at least one network, and wherein the first and second computers are peer computers coupled by the at least one network.

12. The method of claim 1, wherein the first computer manages storage of the second digital asset, and wherein the act (B) comprises an act of storing the second digital asset on the first computer.

13. The method of claim 1, wherein the first computer manages storage of the second digital asset, and wherein the act (B) comprises an act of storing the second digital asset on a storage device managed by the first computer.

14. The method of claim 1, wherein the act (A) comprises an act of creating the descriptor file to include at least one searchable keyword associated with the first digital asset.

15. The method of claim 14, wherein the at least one searchable keyword is descriptive of the first digital asset.

16. The method of claim 1, wherein the act (A) comprises creating the first descriptor file to comprise at least some metadata added to the first descriptor file based on the first descriptor file being of the first type.

17. The method of claim 16, wherein the act (A) comprises creating the first descriptor file to comprise at least some metadata automatically added to the first descriptor file based on the first descriptor file being of the first type.

18. The method of claim 16, wherein the act (A) comprises creating the first descriptor file to comprise at least some metadata added to the first descriptor file, in response to a prompt of a user of the computer system, based on the first descriptor file being of the first type.

19. The method of claim 1, wherein the act (A) comprises creating the first descriptor file to comprise at least one behavior added to the first descriptor file based on the first descriptor file being of the first type.

20. At least one non-transitory computer readable medium encoded with instructions that, when executed on a computer system, perform a method of managing a plurality of digital assets stored in the computer system, wherein the computer system comprises at least a first computer, the plurality of digital assets comprising a first digital asset, the first digital asset comprising content and having associated metadata, the method comprising acts of:

(A) creating a customized first descriptor file that comprises content that includes at least some of the metadata associated with the first digital asset and an identifier of the first digital asset that is based, at least in part, on a cryptographic hash of at least some of the content of the first digital asset, the first descriptor file being a first type of descriptor file that is one of a plurality of customized descriptor file types created by a user, at least some metadata and behavior being automatically added to the first descriptor file based on the first descriptor file being of the first type, wherein the behavior that is automatically added to the first descriptor file based on the first descriptor file being of the first type is specified by the user and causes the first descriptor file to be placed in a particular folder based on the first descriptor file being of the first type, wherein the particular folder in which the first descriptor file is placed is specified by the user; and

(B) storing the first descriptor file on the computer system in the particular folder so that the first descriptor file is accessible as one of the plurality of digital assets and creating an identifier of the first descriptor file that is based, at least in part, on a cryptographic hash of at least some of the content of the first descriptor file.

21. The at least one non-transitory computer readable medium of claim 20, wherein the plurality of digital assets comprises a second digital asset, the second digital asset comprising data and having associated metadata, and wherein the method further comprises acts of:

(C) creating a second descriptor file that comprises at least some of the metadata associated with the second digital asset, the second descriptor file being a second type of descriptor file, at least some metadata being automatically added to the second descriptor file based on the second descriptor file being of the second type, wherein the at least some metadata automatically added to the second descriptor file differs in at least some respects from the at least some metadata automatically added to the first descriptor file; and

(D) storing the second descriptor file on the computer system so that the second descriptor file is accessible as one of the plurality of digital assets.

22. The at least one non-transitory computer readable medium of claim 20, wherein the first computer manages storage of the first digital asset, wherein the computer system further comprises a second computer having an application program that generates the first digital asset, and wherein the act (B) comprises an act of storing the first descriptor file in a manner that enables the first descriptor file to be accessed by the application program.

23. The at least one non-transitory computer readable medium of claim 20, wherein the act (B) comprises an act of storing the first descriptor file as a file on the computer system.

24. The at least one non-transitory computer readable medium of claim 20, wherein the method further comprises an act of:

(C) creating a unique identifier for the first descriptor file, the unique identifier comprising information that identifies the first descriptor file as belonging to a class of digital assets that comprise metadata relating to other digital assets.

25. The at least one non-transitory computer readable medium of claim 24, wherein the method further comprises an act of:

(D) creating a unique identifier for the first digital asset, the unique identifier for the first digital asset comprising information that identifies the first digital asset as belonging to a class of digital assets that do not comprise metadata relating to other digital assets.

26. The at least one non-transitory computer readable medium of claim 20, wherein the first computer is a silo that manages storage of the first digital asset.

27. The at least one non-transitory computer readable medium of claim 20, wherein the first computer is a file server that manages storage of the first digital asset.

28. The at least one non-transitory computer readable medium of claim 20, wherein the first computer is a storage system that manages storage of the first digital asset.

29. The at least one non-transitory computer readable medium of claim 20, wherein the computer system comprises a plurality of computers in addition to the first computer, wherein the plurality of computers are interconnected by at least one network, and wherein each of the plurality of computers manages storage of one or more of the plurality of digital assets.

30. The at least one non-transitory computer readable medium of claim 20, wherein the computer system further comprises a second computer and at least one network, and wherein the first and second computers are peer computers coupled by the at least one network.

31. The at least one non-transitory computer readable of claim 20, wherein the first computer manages storage of the second digital asset, and wherein the act (B) comprises an act of storing the second digital asset on the first computer.

32. The at least one non-transitory computer readable medium of claim 20, wherein the first computer manages storage of the second digital asset, and wherein the act (B) comprises an act of storing the second digital asset on a storage device managed by the first computer.

33. The at least one non-transitory computer readable medium of claim 20, wherein the act (A) comprises an act of creating the descriptor file to include at least one searchable keyword associated with the first digital asset.

34. The at least one non-transitory computer readable medium of claim 33, wherein the at least one searchable keyword is descriptive of the first digital asset.

35. The at least one non-transitory computer readable medium of claim 20, wherein the act (A) comprises creating the first descriptor file to comprise at least some metadata added to the first descriptor file based on the first descriptor file being of the first type.

36. The at least one non-transitory computer readable medium of claim 35, wherein the act (A) comprises creating the first descriptor file to comprise at least some metadata automatically added to the first descriptor file based on the first descriptor file being of the first type.

37. The at least one non-transitory computer readable medium of claim 35, wherein the act (A) comprises creating the first descriptor file to comprise at least some metadata added to the first descriptor file, in response to a prompt of a user of the computer system, based on the first descriptor file being of the first type.

38. The at least one non-transitory computer readable medium of claim 20, wherein the act (A) comprises creating the first descriptor file to comprise at least one behavior added to the first descriptor file based on the first descriptor file being of the first type.

39. At least one computer, in a computer system, for managing a plurality of digital assets stored in the computer system, wherein the plurality of digital assets comprising a first digital asset, the first digital asset comprising content and having associated metadata, the at least one computer comprising:

at least one storage device; and

at least one controller, coupled to the at least one storage device, that;

(A) creates a customized first descriptor file that comprises content that includes at least some of the metadata associated with the first digital asset and an identifier of the first digital asset that is based, at least in part, on a cryptographic hash of at least some of the content of the first digital asset, the first descriptor file being a first type of descriptor file that is one of a plurality of customized descriptor file types created by a user, at least some metadata and behavior being automatically added to the first descriptor file based on the first descriptor file being of the first type, wherein the behavior that is automatically added to the first descriptor file based on the first descriptor file being of the first type is specified by the user and causes the first descriptor file to be placed in a particular folder based on the first descriptor file being of the first type, wherein the particular folder in which the first descriptor file is placed is specified by the user; and

(B) stores, on the at least one storage device, the first descriptor file in the particular folder so that the first descriptor file is accessible as one of the plurality of digital assets and creates an identifier of the first descriptor file that is based, at least in part, on a cryptographic hash of at least some of the content of the first descriptor file.

40. The at least one computer of claim 39, wherein the plurality of digital assets comprises a second digital asset, the second digital asset comprising data and having associated metadata, and wherein the at least one controller:

(C) creates a second descriptor file that comprises at least some of the metadata associated with the second digital asset, the second descriptor file being a second type of descriptor file, at least some metadata being automatically added to the second descriptor file based on the second descriptor file being of the second type, wherein the at least some metadata automatically added to the second descriptor file differs in at least some respects from the at least some metadata automatically added to the first descriptor file; and

(D) stores the second descriptor file on the at least one storage device so that the second descriptor file is accessible as one of the plurality of digital assets.

41. The at least one computer of claim 39, wherein the at least one computer is a first computer and wherein the computer system further comprises a second computer having an application program that generates the first digital asset, and wherein the at least one controller stores the first descriptor file in a manner that enables the first descriptor file to be accessed by the application program.

42. The at least one computer of claim 39, wherein the, at least one controller stores the first descriptor file as a file on the computer system.

43. The at least one computer of claim 39, wherein the at least one controller:

(C) creates a unique identifier for the first descriptor file, the unique identifier comprising information that identifies the first descriptor file as belonging to a class of digital assets that comprise metadata relating to other digital assets.

44. The at least one computer of claim 43, wherein the at least one controller:

(D) creates a unique identifier for the first digital asset, the unique identifier for the first digital asset comprising information that identifies the first digital asset as belonging to a class of digital assets that do not comprise metadata relating to other digital assets.

45. The at least one computer of claim 39, wherein the at least one computer is a silo that manages storage of the first digital asset.

46. The at least one computer of claim 39, wherein the at least one computer is a file server that manages storage of the first digital asset.

47. The at least one computer of claim 39, wherein the at least one computer is a storage system that manages storage of the first digital asset.

48. The at least one computer of claim 39, wherein the computer system comprises a plurality of computers in addition to the at least one computer, wherein the plurality of computers are interconnected by at least one network, and wherein each of the plurality of computers manages storage of one or more of the plurality of digital assets.

49. The at least one computer of claim 39, wherein the at least one computer is a first computer and wherein the computer system further comprises a second computer and at least one network, and wherein the first and second computers are peer computers coupled by the at least one network.

50. The at least one computer of claim 39, wherein the at least one computer manages storage of the second digital asset, and wherein the at least one controller stores the second digital asset on the at least one storage device.

51. The at least one computer of claim 39, wherein the at least one computer manages storage of the second digital asset, and wherein the at least one controller stores the second digital asset on the at least one storage device.

52. The at least one computer of claim 39, wherein the at least one controller creates the descriptor file to include at least one searchable keyword associated with the first digital asset.

53. The at least one computer of claim 52, wherein the at least one searchable keyword is descriptive of the first digital asset.

54. The at least one computer of claim 39, wherein the at least one controller creates the first descriptor file to comprise at least some metadata added to the first descriptor file based on the first descriptor file being of the first type.

55. The at least one computer of claim 54, wherein the at least one controller creates the first descriptor file to comprise at least some metadata automatically added to the first descriptor file based on the first descriptor file being of the first type.

56. The at least one computer of claim 54, wherein the at least one controller creates the first descriptor file to comprise at least some metadata added to the first descriptor file, in response to a prompt of a user of the computer system, based on the first descriptor file being of the first type.

57. The at least one computer of claim 39, wherein the at least one controller creates the first descriptor file to comprise at least one behavior added to the first descriptor file based on the first descriptor file being of the first type.