System and method for peer-to-peer file exchange mechanism from multiple sources

• US 20030145093A1
• Filed: 11/12/2002
• Published: 07/31/2003
• Est. Priority Date: 03/19/2001
• Status: Abandoned Application

• Current Assignee: Imesh Incorporated
• Original Assignee: Imesh Incorporated
• Inventors: Magazinik, Igor, Oren, Elan
• Application Number:
  US10/275,865
• Publication Number:
  US 20030145093A1
• Time in Patent Office: Days
• US Class Current: 709/229
• CPC Class Codes: G06F 16/152 using file content signatures, e.g. hash values
• CPC Class Codes: G06F 16/1834 implemented based on peer-to-peer networks, e.g. gnutella p2p communication protocols H04L67/104
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1063 Discovery through centralising entities
• CPC Class Codes: H04L 67/108 characterised by resources being split in blocks or fragments
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A system and a method for file exchanges between peer computational devices connected through a network, for peer-to-peer file exchanges. The present invention enables the peer devices to retrieve information about the location of files of interest from a central location authority, which features a centralized database. Therefore, the system and method of the present invention features a mixture of client/server and peer-to-peer communication functionality, in which the bandwidth-intensive, computationally heavy process of retrieving files is performed locally, through a peer-to-peer process; while the computationally lighter and less bandwidth-intensive process of determining the location of any particular file is performed locally. The system of the present invention features a plurality of distributed, decentralized file provision computational devices, which are peer devices and which optionally operate a client module, and a central location authority, for locating files of interest between computational devices connected to the network through communication with the client module. These files are preferably tagged with a file identifier, while each peer device has an associated user identifier. Therefore, files can be managed within the system of the present invention, and can even be blocked from being allowed into the system of the present invention. In addition, the action of users can optionally be controlled by controlling the activities of peer devices. According to preferred embodiments of the present invention, multiple peer devices are considered in order determine from which peer device the file should be downloaded.

Claims

1. A method for file transfer between a plurality of peer devices connected through a network, the method comprising the stages of:

(a) associating each peer device with a unique peer device identifier;

(b) associating each file with a unique file identifier;

(c) requesting a particular file by the peer device according to said unique file identifier;

(d) controlling access by a particular peer device to the network according to said unique peer device identifier; and

(e) controlling access of said file to the network according to said unique file identifier.

2. The method of claim 1, wherein stage (e) includes the stage of blocking an unauthorized file from the network.

3. The method of claim 1, wherein stage (d) includes the stage of registering a new peer device for a user on the network.

4. The method of claim 3, wherein stage (d) includes the stage of charging said user for each file transfer according to said unique peer device identifier and according to said unique file identifier.

5. The method of claim 1, further comprising the stages of:

(e) requesting a file according to a file identifier from the peer device.

6. The method of claim 5, wherein stage (e) further comprises the stages of:

(i) identifying a plurality of peer devices storing said file;

(ii) selecting a peer device for downloading said file according to at least one peer device criterion; and

(iii) downloading said file from said peer device.

7. The method of claim 6, wherein said file is signed before being downloaded in order to verify that the correct file is completely and correctly received.

8. The method of claim 6, wherein stage (iii) further comprises the stages of:

(1) dividing said file into a plurality of chunks; and

(2) downloading each chunk from said peer device.

9. The method of claim 8, wherein if said connection to said peer device is broken, a connection to a different peer device is established in order to download the next chunk.

10. The method of claim 6, wherein stage (ii) further comprises the stage of selecting a plurality of peer devices for downloading, such that stage (iii) is performed with said plurality of peer devices.

11. The method of claims 6 or 10, wherein each peer device selected for downloading is connected to the same ISP (Internet Service Provider) as a requesting peer device, said requesting peer device requesting said particular file for downloading.

12. The method of any of claims 1-11, wherein said unique file identifier is a unique file pointer, featuring at least a file signature for said particular file.

13. The method of claim 12, wherein said file signature is compared to an original signature stored at said peer device for downloading to determine whether said particular file has been altered.

14. The method of either of claims 12 or 13, further comprising:

after downloading said particular file by said requesting peer device, comparing said file signature to said original signature to determine whether said particular file has been altered.

15. A system for controlled peer-to-peer file transfer for a user through a network, comprising:

(a) a plurality of peer devices connected to the network, each peer device having a unique peer identifier; and

(b) a central authority for holding a list of available files and for storing said peer identifiers, said central authority receiving a request for a file from a peer device and determining whether said peer device should receive said file, such that if said peer device should receive said file, said central authority sends a peer identifier of a peer device storing said file to said requesting peer device.

16. The system of claim 15, further comprising:

(c) a centralized database at said central authority for holding said list of available files and said peer identifiers; and

(d) a plurality of slice servers for serving a portion of said list of available files and said peer identifiers to each requesting peer device.

17. The system of claims 15 or 16, further comprising a search engine for searching through said list of available files according to a request from a requesting peer device.

18. The system of any of claims 15-17, further comprising a business server for charging the user for each file transfer by said peer device.

19. The system of claim 18, wherein said business server further determines a scope of services for being provided to a requesting peer device.

20. The system of claims 18 or 19, wherein said business server further determines whether at least one search result from said search engine is sent to said requesting peer device.

21. The system of any of claims 15-20, further comprising a local database for storing at least said particular file at said peer device for downloading, wherein said local database is synchronized with said centralized database.