Data management systems and methods for distributed data storage and management using content signatures

• US 20070276823A1
• Filed: 04/06/2007
• Published: 11/29/2007
• Est. Priority Date: 05/22/2003
• Status: Abandoned Application

• Current Assignee: Carmenso Data Limited Liability Company (Intellectual Ventures LLC)
• Original Assignee: Carmenso Data Limited Liability Company (Intellectual Ventures LLC)
• Inventors: Borden, Bruce, Brand, Russell
• Application Number:
  US11/783,272
• Publication Number:
  US 20070276823A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1456 Hardware arrangements for backup
• CPC Class Codes: G06F 16/137 Hash-based content-based indexing of textual data G06F16/31
• CPC Class Codes: G06F 16/162 Delete operations erasing in storage systems G06F3/0652
• CPC Class Codes: G06F 16/1756 based on delta files
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06F 16/20 of structured data, e.g. relational data
• CPC Class Codes: G06Q 20/3825 Use of electronic signatures
• CPC Class Codes: H04L 9/3239 involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD

Abstract

Data management systems and methods for distributed content storage and management using content signatures that use file identicality properties are provided. A data management system is provided that includes a content engine for managing the storage of file content, a content signature generator that generates a unique content signature for a file processed by the content engine, a content signature comparator that compares content signatures and a content signature repository that stores content signatures. Methods are provided for the efficient management of files using content signatures that take advantage of file identicality properties. Content signature application modules and registries exist within information source clients and centralized servers to support the content signature methods.

Claims

1. A data management system, comprising:

a content engine for managing the storage of file content;

a content signature generator that generates a content signature for a file processed by a content engine for managing the storage of file content; and

a content signature comparator that compares file content signatures to determine how to process the files with the associated file content signatures.

2. The data management system of claim 1, wherein a file includes a data file, application file, system file, and/or a programmable ROM file.

3. The data management system of claim 1, wherein a content signature is a unique file identifier generated by hashing using the SHA-1, MD2, MD4, MD5, HAVAL, RIPEMD-128, RIPEMD-256, RIPEMD-160, RIPEMD-320, Tiger, SHA-2, SHA-224, SHA-256, SHA-384, and SHA-512, Panama, and Whirlpool algorithms.

4. The data management system of claim 1, further comprising:

a content signature applications module that includes one or more applications that use file content signatures to manage files based on file identicality; and

a set of content signature registries that include lists of content signatures to support one or more content signature application.

5. The data management system of claim 4, wherein the set of content signature registries includes one or more of a blocked file content signature registry, a pornographic file content signature registry, a copyright file content signature registry, a confidential document content signature registry and a classified document content signature registry.

6. The data management system of claim 1, further comprising:

an indexing engine for indexing file data content;

a metadata engine for managing metadata characterizing a file; and

a triage engine coupled to and managing said content engine, said indexing engine and said metadata engine.

7. The data management system of claim 6, further comprising an information entryway coupled to said triage engine, wherein said information entryway receives files from information source clients.

8. The data management system of claim 6, further comprising an information source modification controller wherein said information source modification controller sends commands to information source clients.

9. The data management system of claim 6, further comprising:

an index repository for containing searchable attributes of the file content and/or metadata of files;

a content repository for storing file content; and

a metadata repository for storing metadata, wherein said index repository, said content repository and said metadata repository are coupled to said information entryway.

10. A method to store a file within a file management system having a set of existing file contents and file content signatures, comprising:

receiving a file;

generating a content signature for the received file;

generating or receiving metadata for the received file;

comparing the content signature for the received file to the file content signatures that exist within the data management system;

storing the file content, file content signature and metadata for the received file when the file content signature for the received file does not match any of the file content signatures already stored within the data management system;

associating the metadata for the received file with the stored file content signature that matches the content signature for the received file and storing the metadata for the received file when the file content signature for the received file does match a file content signature already stored within the data management system.

11. The method of claim 10, wherein storing the file content, file content signatures and metadata includes storing the file content, file content signatures and/or the metadata within a relational database.

12. A method to store a multi-segmented file, comprising:

receiving the multi-segmented file having multiple files;

generate a content signature for each file within the multi-segmented file;

compare generated content signatures to existing content signatures within a data management system;

determine whether the content signatures for the files within the multi-segmented file match existing content signatures; and

when all content signatures for the files within the multi-segmented files match existing content signatures, generate metadata for the multi-segment file and store the metadata.

13. The method of claim 12, wherein the multi-segment file includes a mail file, a compressed file archive, a non-compressed file archive, an entertainment collection, a multi-part web page, a multi-page presentation, a multi-part Office document, a multi-page image file, an image file with OCR, a speech file with audio transcripts, a system paging file, a swap file, a log file, a database, a table, an append only file, and instant messenger archive, a chat archive, a history file, a journal, a virtual file system, and a revision control repository including SVN archives, or a ramdisk file.

14. A method for managing copyrighted files on a data management system, comprising:

receiving a file;

generating a content signature for the received file;

comparing the content signature for the received file to content signatures stored within a copyright file content signature registry;

determining whether the content signature for the received file matches a content signature store within the copyright file content signature registry; and

when a content signature match is determined, increment an instance count for the content signature within the copyright file content signature registry.

15. The method of claim 14, further comprising:

determining whether the instance count for the content signature exceeds a copyright threshold; and

when the copyright threshold is exceeded, performing a control action.

16. A method for controlling confidential files, comprising:

establishing a registry of content signatures for confidential documents;

enrolling participants in the registry;

transmitting content signatures for files held by participants to the registry;

compare content signatures from participants to content signatures of confidential documents within the registry; and

when a content signature from a participant matches a content signature of a confidential document, taking a control action.

17. A method to generate search results, comprising:

receiving a search request terms;

conducting a search to identify files that include the search request terms or their equivalents;

generating content signatures for the files identified by the search;

determining statistics for the files represented by the content signatures, wherein statistics include copies of files found, number of recent deletions of files and/or number of recent additions of files; and

prioritizing search results based on the statistics.

18. A method to perform computer forensics, comprising:

generating or receiving a content signature for a file under investigation;

identifying information source clients that are associated with the content signature of the file under investigation;

identifying information source clients that formerly contained the content signature of the file under investigation; and

generating a file investigation report that identifies the information source clients that are associated with the content signature of the file under investigation and/or identifies information source clients that formerly were associated with the content signature of the file under investigation.

19. A method for fetching links associated with a requested web page, comprising:

requesting a web page;

receiving a set of content signatures associated with the web page;

comparing the web page content signatures to existing content signatures stored on an information source client; and

fetching links for content signatures that do not exist within the existing content signatures.

20. A method for identifying when identical files are independently created within a network, comprising:

receiving a file;

generate a content signature for the received file;

compare content signature for the received file to content signatures for existing files;

determine whether the content signature for the received file matches an existing content signature;

when a content signature match exists, examining metadata for the received file to determine if the received file was independently developed; and

when a determination is made that the received file was not independently developed, taking a control action.