Version management system and version management method for content delivery and management

• US 20050203969A1
• Filed: 03/03/2005
• Published: 09/15/2005
• Est. Priority Date: 03/15/2004
• Status: Abandoned Application

• Current Assignee: OKI Electric Industry Company Limited
• Original Assignee: OKI Electric Industry Company Limited
• Inventors: Kawabe, Kazuhiro
• Application Number:
  US11/070,254
• Publication Number:
  US 20050203969A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/125 characterised by the use of retention policies retention policies for HSM systems G06F16/185
• CPC Class Codes: G06F 16/1873 Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files

Abstract

A version management system and method, enabling discarding of old version content files through simple and low-load processing. Storage periods and holding periods are allocated to a plurality of storage elements provided in a non-newest file storage unit. When a newest version content file is registered, the content file is stored in a newest version file storage unit. A content file which has become a non-newest version content file due to the version upgrade is transferred from the newest version file storage unit to be stored in the storage element to which is allocated the storage period corresponding to the date of the version upgrade. When the above corresponding holding period has elapsed, content files within the storage element are all simultaneously deleted.

Claims

1. A version management system for content delivery and management, comprising:

a newest file storage unit, which stores newest-version content files;

a non-newest file storage unit, having a plurality of storage elements each of which receives and stores content files which have become non-newest versions due to version upgrades from said newest version file storage unit; and

,

a controller, which allocates a storage period and a holding period to each of said storage elements, transfers content files which have become non-newest versions due to said version upgrades to, and stores said files in, said storage element to which said storage period corresponding to the version upgrade date has been allocated, and deletes all content files in said storage elements at the time at which said corresponding holding period has elapsed.

2. The version management system according to claim 1, wherein said controller is constituted to;

allocate said storage periods consecutively to said storage elements,

store in order content files in all of said storage elements according to said allocated storage periods;

regard said holding period of said storage element to which the oldest storage period has been allocated is ended when said storage periods of all storage elements are ended, and deletes all of said content files stored in the storage element; and

,

allocates a new storage period to the storage element after the deletion.

3. The version management system according to claim 1, further comprising a history manager which manages content files held in each of said storage elements.

4. The version management system according to claim 3, wherein said controller is constituted to;

adds revision history information for a content file to said history manager, when the content file is stored in said storage element; and

,

deletes revision history information for a content file from said history manager, when the content file is deleted from said storage element.

5. The version management system according to claim 1, further comprising a revision management table for batch management of said storage elements in which each of said non-newest version content file is stored.

6. The version management system according to claim 5, wherein said revision management table records, for each non-newest version content file, management information comprising the filename of the content file, the version number of the content file, and the identification number of said storage element in which the content file is stored.

7. The version management system according to claim 5, wherein said controller is constituted to;

adds management information for a content file to said revision management table, when the content file is stored in said storage element; and

,

deletes management information for a content file from said revision management table, when the content file is deleted from said storage element.

8. The version management system according to claim 5, wherein said controller, upon receiving a request for viewing of a non-newest version content file from a client terminal, uses said revision management table to identify said storage element in which the requested content file is stored, reads said requested content file from said identified storage element, and transmits said file to said client terminal.

9. The version management system according to claim 1, wherein said controller, upon receiving a request for deletion of a newest version content file from a client terminal, deletes the content file from said newest version storage unit, and transfers the deleted content file to and stores the file in said storage element to which is allocated said storage period corresponding to the date of deletion.

10. The version management system according to claim 9, wherein said controller deletes the content file stored in said storage element based on the deletion request from the client terminal, at the same time as the deletion of content files that have become non-newest version files due to a version upgrade, when the holding period of the storage element is ended.

11. The version management system according to claim 1, wherein each of said storage elements is either an individual storage device, or is a storage area obtained by dividing the storage area of one or a plurality of storage devices.

12. A version control method for content delivery and management, comprising the steps of:

allocating a storage period and a holding period to each of a plurality of storage elements provided in a non-newest file storage unit;

storing newest version content files in a newest file storage unit;

transferring content files which have become non-newest version files due to a version upgrade from said newest version file storage unit to, and storing said files in, said storage element to which has been allocated said storage period corresponding to the version upgrade date; and

,

deleting all the content files in said storage elements at the time said corresponding holding period has elapsed.

13. The version control method according to claim 12, wherein;

said storage periods are allocated consecutively to said storage elements;

content files are stored in order in all of said storage elements according to said allocated storage periods,

said holding period of said storage element to which the oldest storage period has been allocated is regarded to be ended when said storage periods of all storage elements are ended, and said content files stored in the storage element are all deleted; and

,

a new storage period is allocated to the storage element after the deletion.

14. The version control method according to claim 12, further comprising the steps of:

adding revision history information for a content file to a history manager, when the content file is stored in said storage element; and

,

deleting revision history information for a content file from said history manager, when the content file is deleted from said storage element.

15. The version control method according to claim 12, further comprising the steps of:

adding management information for a content file to a revision management table, when the content file is stored in said storage element; and

,

deleting management information for a content file from said revision management table, when the content file is deleted from said storage element.

16. The version control method according to claim 15, wherein said management information stored in said revision management table comprises the filename of a non-newest version content file, the version number of the content file, and the identification number of said storage element in which the content file is stored.

17. The version control method according to claim 15, further comprising a step, when non-newest version content file viewing is requested by a client terminal, of using said revision management table to identify said storage element in which the requested content file is stored, reading said requested content file from said identified storage element, and transmitting said file to said client terminal.

18. The version control method according to claim 12, further comprising steps, when deletion of a newest version content file is requested by a client terminal, of;

deleting the content file from said newest version storage unit; and

,

transferring the deleted content file to and storing the file in said storage element to which has been allocated said storage period corresponding to the date of deletion.

19. The version control method according to claim 18, further comprising a step of deleting a content file stored in said storage element based on the deletion request from the client terminal, at the same time as deletion of content files that have become non-newest version files due to a version upgrade, when the holding period of the storage element is ended.

20. The version control method according to claim 12, wherein each of said storage elements is either an independent storage device, or is a storage area obtained by dividing the storage area of one or a plurality of storage devices.