File transfer system

• US 7,263,528 B2
• Filed: 06/13/2002
• Issued: 08/28/2007
• Est. Priority Date: 11/13/1997
• Status: Expired due to Term

• Current Assignee: Intellectual Ventures I LLC (Intellectual Ventures LLC)
• Original Assignee: HyperSpace Communications, Inc.
• Inventors: Clarke, Christopher D., Haff, Maurice W.
• Primary Examiner(s): Al-Hashemi; Sana
• Application Number:
  US10/167,697
• Publication Number:
  US 20020184224A1
• Time in Patent Office: 1,902 Days
• Field of Search: 707/10,9,201 705/39,79,54,59 717/167,177 709/213
• US Class Current: 707/622
• CPC Class Codes: G06F 16/13 File access structures, e.g. distributed indices arrangements of input from, or output to, record carriers G06F3/06
• CPC Class Codes: H04L 2101/663 Transport layer addresses, e.g. aspects of transmission control protocol [TCP] or user datagram protocol [UDP] ports
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/10 of different types
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/0442 wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/168 above the transport layer
• 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/1078 Resource delivery mechanisms
• CPC Class Codes: H04L 67/1093 Some peer nodes performing special functions
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC
• CPC Class Codes: H04L 69/14 Multichannel or multilink protocols
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/162 involving adaptations of sockets based mechanisms secure socket layer H04L63/168
• CPC Class Codes: H04L 69/164 Adaptation or special uses of UDP protocol
• CPC Class Codes: H04L 69/326 : in the transport layer [OSI layer 4] H04L69/16 takes precedence
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 : Network security protocols
• CPC Class Codes: Y10S 707/922 : Communications
• CPC Class Codes: Y10S 707/99942 : Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 : Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99945 : Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99952 : Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99953 : Recoverability

Abstract

A file transfer system includes peer devices, including an index creating device and at least one requesting peer device. The index creating device creates an index of stored files that can be requested by peer devices. The index creating device evaluates communications requests from the peer devices and accepts communications requests in accordance with user defined criteria. The index creating device communicates with a requesting peer device when the communications request from the requesting peer device has been accepted, and also stores the index, which is linked to an identification. The requesting peer device requests files that are listed in the index linked to the identification. The requesting peer device also creates the file request, which includes a list of the selected files and the identification, transmits the file request to the index creating device, and receives the requested files listed in the index.

Claims

1. An index creating device running in a peer to peer system, comprising:

an index creating device creating an index of stored files that can be requested by peer devices, comprising;

a selective acceptance system that evaluates communications requests sent from peer devices, and accepts communications requests in accordance with user defined index criteria;

a communications system that communicates with a requesting peer device, when the communications request from the requesting peer device has been accepted;

an index generator that generates the index based on index creation options selected by a user;

a storage that stores the index; and

an index transmission system that transmits the index to the requesting peer device in response to an index request sent from the requesting peer device, wherein the transmitted index enables requesting peer devices to retrieve data from the index creating device without allowing the requesting peer devices to login or control the index creating device.

2. The device of claim 1, further comprising a file transmission system that transmits the requested files listed in the index to the requesting peer device in response to a file request sent from the requesting peer device.

3. The device of claim 2, in which the index generator links the index to an identification comprising at least one of an identification of the requesting peer device and an identification of a user of the requesting peer device;

and

the file transmission system transmits the requested files only when at least one of the requesting peer device and the user of the requesting peer device matches the identification linked to the index.

4. A file requesting device running in a peer to peer system, the file requesting device requesting files that are available from a peer device, the file requesting device comprising:

a selector that selects files from an index, which index is linked to an identification, based on a selection command, the identification comprising at least one of an identification of the file requesting device and an identification of a user of the file requesting device;

a request creation system that creates a file request, including a list of the selected files and the identification;

a transmitter that transmits the file request to the peer device; and

a receiver that receives the requested files sent from the peer device.

5. The file requesting device of claim 4, in which the index is generated by and available on the peer device.

6. A file transfer system comprising a plurality of peer devices, comprising:

an index creating device that creates an index of stored files that can be requested by peer devices, the index creating device comprising a selective acceptance system that evaluates communications requests from the peer devices, and accepts communications requests in accordance with user defined criteria;

a communications system that communicates with a requesting peer device when the communications request sent from the requesting peer device has been accepted;

an index generator that generates the index based on index creation options selected by a user and that links the index to an identification comprising at least one of an identification of the requesting peer device and an identification of a user of the requesting peer device; and

a storage that stores the index; and

at least one requesting peer device that requests files that are listed in the index, the file requesting device comprising;

a selector that selects files from the index, which index is linked to the identification, based on a selection command;

a request creation system that creates the file request, including a list of the selected files and the identification;

a transmitter that transmits the file request to the index creating device; and

a receiver that receives the requested files listed in the index.

7. The system of claim 6, in which the index creating device further comprises an index transmission system that transmits the index to the requesting peer device in response to an index request sent from the requesting peer device, wherein the transmitted index enables requesting peer devices to retrieve data from the index creating device without allowing the requesting peer devices to login or control the index creating device or other peer devices.

8. The system of claim 6, in which the index creating device further comprises a file transmission system that transmits the requested files listed in the index to the requesting peer device in response to a file request sent from the requesting peer device only when at least one of the requesting peer device and the user of the requesting peer device corresponds with the identification linked to the index.

9. An index creating method for use in a peer to peer system, the index creating method creating an index of stored files that can be requested by other peer devices, comprising:

evaluating communications requests from the other peer devices, and accepting communications requests in accordance with user defined criteria;

communicating with a requesting peer device, when the communications request sent from the requesting peer device has been accepted;

generating the index of stored files based on index creation options selected by a user; and

storing the index; and

transmitting the index to the requesting peer device in response to an index request sent from the requesting peer device, wherein the transmitted index enables requesting peer devices to retrieve data listed in the index without allowing the requesting peer devices to login or control the index creating device or other peer devices.

10. The method of claim 9, further comprising transmitting the requested files in the index to the requesting peer device in response to a file request sent from the requesting peer device.

11. The method of claim 9, further comprising requesting files that are available from a peer device, the file requesting method comprising:

selecting files from an index, which index is linked to an identification, based on a selection command, the index being generated by the peer device, the identification comprising at least one of an identification of the file requesting device and an identification of a user;

creating a file request, including a list of the selected files and the identification;

transmitting the file request to the peer device; and

receiving the requested files sent from the peer device.

12. A computer readable medium storing an index creating program running in a peer to peer system, the index creating program creating an index of stored files that can be requested by peer devices, the computer readable medium comprising:

a selective acceptance source code segment that evaluates communications requests sent from the peer devices, and accepts communications requests in accordance with user defined criteria;

a communications source code segment that communicates with a requesting peer device, when the communications request sent from the requesting peer device has been accepted;

an index generating source code segment that generates the index based on index creation options selected by a user;

a storage source code segment that stores the index; and

an index transmission source code segment that transmits the index to the requesting peer device in response to an index request sent from the requesting peer device, wherein the transmitted index enables requesting peer devices to retrieve data listed in the index without allowing the requesting peer devices to login or control the index creating device or peer devices.

13. The medium of claim 12, further comprising a file transmission source code segment that transmits the requested files in the index to the requesting peer device in response to a file request sent from the requesting peer device.

14. The medium of claim 13, in which the index generator source code segment links the index to an identification comprising at least one of an identification of the requesting peer device and an identification of a user of the requesting peer device;

and

the file transmission source code segment transmits the requested files only when at least one of the requesting peer device and the user of the requesting peer device corresponds to the identification linked to the index.

15. The medium of claim 13, in which the file transmission source code segment transmits an associated directory structure with each transmitted file.

16. The medium of claim 12, in which the selective acceptance criteria comprise authenticated identity codes.

17. The medium of claim 12, in which the index generating source code segment generates a plurality of indexes, each linked to at least one identification.

18. The medium of claim 12, in which the communications source code segment contemporaneously communicates with multiple requesting peer devices.

19. The medium of claim 13, further comprising a data delivery credit monitoring source code segment that maintains and monitors data delivery credits, the data delivery credit monitoring source code segment detecting each transmission of requested files and debiting a credit account variable on the requesting peer device, without regard to data content.

20. The medium of claim 19, in which the data credit monitoring source code segment generates and sends a credit request to a third party credit processor that receives delivery credit requests, and increments a credit account variable on an associated one of the peer devices upon receipt of a credit request and successful comparison of the credit request against a credit authorization function.

21. A computer readable medium storing a file requesting program running in a peer to peer system, the file requesting program requesting files used in an index that are available from a peer device, the file requesting program comprising:

a selector source code segment that selects files from the index, which index is linked to an identification, based on a selection command, the identification comprising at least one of an identification of a file requesting device and/or an identification of a user of the file requesting device;

a request creation source code segment that creates a file request including a list of the selected files and the identification;

a transmitting source code segment that transmits the file request to the peer device; and

a receiving source code segment that receives the requested files sent from the peer device.

22. The medium of claim 21, in which the receiving source code segment receives an associated directory structure with each transmitted file.

23. The medium of claim 21, further comprising a return receipt source code segment that generates and sends a return receipt including point of origin, destination, and successful completion information to the peer device upon successfully completing reception of the requested file.

24. The medium of claim 21, further comprising a return receipt source code segment that generates and sends a return receipt to a third party transaction certification processor upon successfully completing reception of the requested files.

25. A computer readable medium storing a file transfer program running in a peer to peer system, the computer readable medium comprising:

a selective acceptance source code segment that evaluates communications requests sent from peer devices, and accepts communications requests in accordance with user defined criteria;

a communications source code segment that communicates with a requesting peer device, when the communications request from the requesting peer device has been accepted;

an index generator source code segment that generates the index based on index creation options selected by a user and that links the index to an identification comprising at least one of an identification of the requesting peer device and an identification of a user of the requesting peer device;

a storage source code segment that stores the index;

a selector source code segment that selects files from the index, which index is linked to the identification, based on a selection command;

a request creation source code segment that creates a file request, including a list of the selected files and the identification;

a transmitter source code segment that transmits the file request to the index creating device;

a file transmission source code segment that transmits the requested files listed in the index to the requesting peer device in response to the file request sent from the requesting peer device only when at least one of the requesting peer device and the user of the requesting peer device corresponds to the identification linked to the index; and

a receiver source code segment that receives the requested files from the index creating device.

26. The medium of claim 25, further comprising an index transmission source code segment that transmits the index to the requesting peer device in response to an index request sent from the requesting peer device, wherein the transmitted index enables requesting peer devices to retrieve data from the index creating device without allowing the requesting peer devices to login or control the index creating device.

27. The medium of claim 25, in which the selective acceptance criteria comprise authenticated identity codes.

28. The medium of claim 25, in which the index generator source code segment generates a plurality of indexes, each linked to at least one identification.

29. The medium of claim 25, in which the file transmission source code segment transmits an associated directory structure with each transmitted file and the receiver source code segment receives the associated directory structure with each received file.

30. The medium of claim 25, in which the communications source code segment contemporaneously communicates with multiple requesting peer devices.

31. The medium of claim 25, further comprising a return receipt source code segment that generates and sends a return receipt including point of origin, destination, and successful completion information to the index creating device upon successfully completing reception of the requested file.

32. The medium of claim 25, further comprising a return receipt source code segment that generates and sends a return receipt to a third party transaction certification processor upon successfully completing reception of the requested files.

33. The medium of claim 25, further comprising a data delivery credit monitoring source code segment that maintains and monitors data delivery credits, the data delivery credit monitoring source code segment detecting each transmission of requested files and debiting a credit account variable for the requesting peer device, without regard to data content.

34. The medium of claim 33, in which the data delivery credit monitoring source code segment generates and sends a credit request to a third party credit processor that receives credit requests, and increments a credit account variable on an associated one of the peer devices upon receipt of a credit request and successful comparison of the credit request against a credit authorization function.