METHOD AND APPARATUS FOR CONTENTS DE-DUPLICATION

• US 20100250502A1
• Filed: 03/27/2009
• Published: 09/30/2010
• Est. Priority Date: 03/27/2009
• Status: Abandoned Application

• Current Assignee: Hitachi, Ltd.
• Original Assignee: Hitachi, Ltd.
• Inventors: SAIGO, Kiyokazu
• Application Number:
  US12/412,771
• Publication Number:
  US 20100250502A1
• Time in Patent Office: Days
• US Class Current: 707/692
• CPC Class Codes: G06F 16/24556 Aggregation; Duplicate elimination
• CPC Class Codes: G06Q 30/04 Billing or invoicing

Abstract

Exemplary embodiments provide in effect data de-duplication in storage servers without the need to compare every byte of stored data. In one embodiment, a method for providing contents from a content device to a storage device comprises receiving by a storage device a ticket including trade information of a trade by a user for content from a content device; receiving by the storage device from the content device attribute information of the content identified in the ticket; determining whether the storage device has the content identified in the ticket based on the attribute information; if the storage device does not have the content identified in the ticket, receiving the content identified in the ticket from the content device and storing the content in the storage device; and if the storage device has the content identified in the ticket, not receiving the content identified in the ticket from the content device.

Claims

1. A method for providing contents from a content device to a storage device, the method comprising:

receiving, by a storage device, a ticket including trade information of a trade by a user for content from a content device;

receiving, by the storage device, from the content device attribute information of the content identified in the ticket;

determining whether the storage device has the content identified in the ticket based on the attribute information;

if the storage device does not have the content identified in the ticket, receiving the content identified in the ticket from the content device and storing the content in the storage device; and

if the storage device has the content identified in the ticket, not receiving the content identified in the ticket from the content device.

2. A method according to claim 1,

wherein the determining comprises referring to a content management table which stores a content ID of each content stored in the storage device and one or more users who possess said each content;

and

wherein the method further comprises updating the content management table using the trade information on the ticket.

3. A method according to claim 1,

wherein receiving the ticket comprises receiving the ticket from the content device which issues the ticket based on an order from a client device that provides, to the content device, information on the storage device for storing the content identified in the ticket.

4. A method according to claim 1, further comprising:

authenticating the user by providing billing information of the user to the content device prior to issuing the ticket by the content device.

5. A method according to claim 1,

wherein the content device is selected by the storage device from a plurality of content devices which include one or more of content servers and cache servers that have the content identified in the ticket.

6. A method according to claim 5,

wherein the content device is selected based on at least one of a bandwidth of the content device or a network distance between the content device and the storage device.

7. A method according to claim 1,

wherein receiving the content identified in the ticket comprises receiving a plurality of divided sub-contents that make up the content.

8. A system for providing contents, the system comprising:

a content device which issues a ticket including trade information of a trade by a user for content from the content device;

a storage device which receives the ticket; and

a network connecting the content device and the storage device;

wherein the storage device

receives attribute information of the content identified in the ticket;

determines whether the storage device has the content identified in the ticket based on the attribute information;

if the storage device does not have the content identified in the ticket, receives the content identified in the ticket from the content device and storing the content in the storage device; and

if the storage device has the content identified in the ticket, does not receive the content identified in the ticket from the content device.

9. A system according to claim 8,

wherein the storage device refers to a content management table which stores a content ID of each content stored in the storage device and one or more users who possess said each content, and determines whether the storage device has the content identified in the ticket based on the attribute information and the content management table;

and

wherein the storage device updates the content management table using the trade information on the ticket.

10. A system according to claim 8, further comprising:

a client device connected to the network;

wherein the storage device receives the ticket from the content device which issues the ticket based on an order from the client device that provides, to the content device, information on the storage device for storing the content identified in the ticket.

11. A system according to claim 8, further comprising:

an authentication device connected to the network, the authentication device authenticating the user by providing billing information of the user to the content device prior to issuing the ticket by the content device.

12. A system according to claim 8,

wherein the storage device selects the content device from a plurality of content devices connected to the network which include one or more of content servers and cache servers that have the content identified in the ticket.

13. A system according to claim 12,

wherein the storage device selects the content device based on at least one of a bandwidth of the content device or a network distance between the content device and the storage device.

14. A system according to claim 8,

wherein the storage device receives from the content device a plurality of divided sub-contents that make up the content identified in the ticket.

15. A computer-readable storage medium storing a plurality of instructions for controlling a data processor to provide contents from a content device to a storage device, the plurality of instructions comprising:

instructions that cause the data processor to receive, by the storage device, a ticket including trade information of a trade by a user for content from the content device;

instructions that cause the data processor to request, by the storage device, attribute information of the content identified in the ticket from the content device;

instructions that cause the data processor to determine whether the storage device has the content identified in the ticket based on the attribute information;

if the storage device does not have the content identified in the ticket, instructions that cause the data processor to receive the content identified in the ticket from the content device and store the content in the storage device; and

if the storage device has the content identified in the ticket, instructions that cause the data processor not to receive the content identified in the ticket from the content device.

16. A computer-readable storage medium according to claim 15,

wherein the instructions that cause the data processor to determine comprise instructions that cause the data processor to refer to a content management table which stores a content ID of each content stored in the storage device and one or more users who possess said each content;

and

wherein the plurality of instructions further comprise instructions that cause the data processor to update the content management table using the trade information on the ticket.

17. A computer-readable storage medium according to claim 15,

wherein the instructions that cause the data processor to receive the ticket comprise instructions that cause the data processor to receive the ticket from the content device which issues the ticket based on an order from a client device that provides, to the content device, information on the storage device for storing the content identified in the ticket.

18. A computer-readable storage medium according to claim 15, wherein the plurality of instructions further comprise:

instructions that cause the data processor to authenticate the user by providing billing information of the user to the content device prior to issuing the ticket by the content device.

19. A computer-readable storage medium according to claim 15, wherein the plurality of instructions further comprise:

instructions that cause the data processor to select the content device by the storage device from a plurality of content devices which include one or more of content servers and cache servers that have the content identified in the ticket.

20. A computer-readable storage medium according to claim 15,

wherein the instructions that cause the data processor to receive the content identified in the ticket comprise instructions that cause the data processor to receive a plurality of divided sub-contents that make up the content.