Peer to peer remote data storage and collaboration

• US 6,928,476 B2
• Filed: 08/23/2002
• Issued: 08/09/2005
• Est. Priority Date: 08/23/2002
• Status: Expired due to Term

• Current Assignee: Seagate Technology LLC (Seagate Technology Holdings Plc)
• Original Assignee: Mirra, Inc. (Seagate Technology Holdings Plc)
• Inventors: Bucher, Tim
• Primary Examiner(s): Geckil, Mehmet B.
• Application Number:
  US10/227,328
• Publication Number:
  US 20040039829A1
• Time in Patent Office: 1,082 Days
• Field of Search: 709202-204, 709/217, 709/225, 709/229, 709/246, 713200-202
• US Class Current: 709/225
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

Remotely storing data between computers or devices across a wide area network for purposes of redundancy or collaboration. A service brokers the transfer of data between an initiating computer and a destination device, thereby establishing a peer-to-peer architecture by which data of the initiating computer can be stored remotely on the destination device. The process begins as the initiating computer issues a request for permission to store the data remotely on an identified destination device. The permission is granted if the initiating computer properly identifies the destination device using information, such as a network address or a password, that is privately communicated between the users of the destination device and the initiating computer. Accordingly, substantially any computer user having access to the Internet can achieve remote backup of data and remote collaboration of data with the assistance of a trusted third party who also is registered with the service.

Claims

1. In a system that includes at least a first appliance and a second appliance each registered and connected with a service, a method for the first appliance to store data at the second appliance, the method, comprising:

identifying, by a first appliance, a second appliance on which to store a segment of data, wherein the second appliance is registered with the service;

sending a permission request to the second appliance, the permission request forwarded to the second appliance by the service;

receiving permission from the second appliance to store the segment of data on the second appliance, wherein the permission is forwarded to the first appliance by the server; and

transferring the segment of data to the service, such that the segment of data is forwarded to the second appliance in a manner that the segment of data is dynamically updated at the second appliance.

2. The method of claim 1, wherein the permission request is transmitted initially to the service and then brokered to the remote device.

3. The method of claim 2, wherein the permission to store the segment of data is received after the second appliance grants the permission in response to the permission request.

4. The method of claim 1, wherein the permission request and the transferred segment of data are locally brokered through the first appliance such that communication with the second appliance is achieved.

5. The method of claim 1, wherein identifying, by a first appliance, a second appliance is performed without presenting to a user of the first appliance a list of remote appliances that are registered with the service.

6. The method of claim 1, wherein identifying, by a first appliance, a second appliance is performed by receiving at the first appliance receiving information identifying the second appliance from a user of the first appliance.

7. The method of claim 6, wherein the information identifying the second appliance comprises a password of the second appliance.

8. The method of claim 7, further comprising transmitting a request to store the segment of data at the second appliance, wherein the request includes the password.

9. The method of claim 8, wherein the permission to store the segment of data is received after the second appliance grants the permission in response to the permission request, and wherein the second appliance grants permission upon recognizing the password included in the permission request.

10. The method of claim 1, further comprising encrypting the segment of data prior to transmitting the segment of data to the service, such that the segment of data stored on the second appliance is inaccessible by a user of the second appliance.

11. The method of claim 1, wherein the storage of the segment of data permits remote data collaboration, the method further comprising receiving a modified version of the segment of data from the second appliance.

12. In an appliance that is in communication with a service, the service being connected to one or more remote appliances, a method for receiving data from a remote appliance, the method comprising:

receiving from the service a permission request to store a segment of data, wherein the permission request originated from a remote appliance that is registered with the service;

transmitting permission to the service in response to receiving the permission request from the remote appliance, such that the permission is forwarded to the remote appliance by the service; and

receiving and storing a dynamically updated segment of data forwarded to the appliance by the service from the remote appliance, wherein the dynamically updated segment of data originates from the remote appliance.

13. The method of claim 12, wherein communication with the remote appliance originates with a local computer and is brokered through the appliance.

14. The method of claim 12, further comprising:

prompting a user associated with the appliance to determine whether to grant the permission request from the remote appliance; and

receiving input from the user specifying that the permission request has been granted.

15. The method of claim 14, wherein prompting the user comprises informing to the user of an identity of the remote appliance.

16. The method of claim 14, wherein the segment of data is encrypted prior to being received by the appliance, such that the data is inaccessible by the user associated with the appliance.

17. The method of claim 12, wherein the permission request received from the service includes a password of the appliance, the password having been provided by a user of the remote appliance.

18. The method of claim 17, further comprising:

recognizing the password included in the permission request; and

automatically and without user input determining that the permission is to be granted based on recognizing the password.