Systems and Methods for Accelerating Remote Data Retrieval Via Peer Nodes

• US 20140122658A1
• Filed: 10/31/2012
• Published: 05/01/2014
• Est. Priority Date: 10/31/2012
• Status: Active Grant

• Current Assignee: Vmware LLC (Broadcom, Inc.), Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: VMware, Inc. (Broadcom, Inc.)
• Inventors: Haeger, Edward Scarlett, Cenname, Michael, Skowronski, Andrew
• Granted Patent: US 9,032,050 B2
• Time in Patent Office: Days
• US Class Current: 709/219
• CPC Class Codes: H04L 67/1091 Interfacing with client-server systems or between P2P systems
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

In one embodiment, a client node generates a listing of files associated with a user account, where the listing includes one or more files that are stored remotely on a server system without being synchronized to local storage of the client node. The client node further receives a request to access a file from the listing and determines whether the file is stored locally on the client node. If the file is not stored locally on the client node, the client node discovers peer client nodes that are coupled with the client node and determines whether the file is stored locally on any peer client node. If the file is stored locally on a peer client node, the client node retrieves the file from the peer client node. If the file is not stored locally on any peer client node, the client node retrieves the file from the server system.

Claims

1. A method performed by a client node for accelerating remote data retrieval, the method comprising:

generating, by the client node, a listing of files associated with a user account, the listing of files including one or more files that are stored remotely on a server system without being synchronized to local storage of the client node, the server system being communicatively coupled with the client node via a first network;

receiving, by the client node, a request to access a file from the listing of files;

determining, by the client node, whether the file is stored locally on the client node; and

if the file is not stored locally on the client node;

discovering, by the client node, one or more peer client nodes that are communicatively coupled with the client node via a second network;

determining, by the client node, whether the file is stored locally on any of the one or more peer client nodes;

if the file is stored locally on a peer client node in the one or more peer client nodes, retrieving, by the client node, the file from the peer client node over the second network; and

if the file is not stored locally on any of the one or more peer client nodes, retrieving, by the client node, the file from the server system over the first network.

2. The method of claim 1 wherein the generating of the listing of files, the determining whether the file is stored locally on the client node, and the retrieving of the file from the server system are performed by a filesystem abstraction layer (FAL running on the client node.

3. The method of claim 2 wherein the discovering of the one or more peer client nodes, the determining whether the file is stored locally on any of one or more peer client nodes, and the retrieving of the file from the peer client node are performed by a local download component that is in communication with the FAL.

4. The method of claim 1 wherein the peer client node is communicatively coupled with the server system via the first network, and wherein the peer client node is configured to synchronize, from the server system to local storage of the peer client node via the first network, each of the files associated with the user account, thereby causing the peer client node to maintain a copy of said each file locally.

5. The method of claim 1 wherein the listing further includes one or more files that are stored remotely on the server system as well as stored locally on the client node, and wherein the method further comprises:

if the file is stored locally on the client node, retrieving the file from the local storage of the client node.

6. The method of claim 1 wherein determining whether the file is stored locally on any of the one or more peer client nodes comprises, for each of the one or more peer client nodes:

establishing a connection with the peer client node;

transmitting, to the peer client node, a request to download the file, the request including an identifier of the file; and

receiving, from the peer client node in response to the request, a copy of the file or an indication that the file is not available on the peer client node.

7. The method of claim 1 wherein the first network has lower bandwidth than the second network.

8. The method of claim 7 wherein the first network is a wide area network (WAN) and the second network is a local area network (LAN).

9. The method of claim 1 wherein the peer client node has greater local storage capacity than the client node.

10. The method of claim 1 wherein the client node is a handheld computing device.

11. The method of claim 1 wherein the client node is a virtual machine executing on a physical computer system.

12. A non-transitory computer readable storage medium embodying computer software causing a client node to execute a method, the method comprising:

generating a listing of files associated with a user account, the listing of files including one or more files that are stored remotely on a server system without being synchronized to local storage of the client node, the server system being communicatively coupled with the client node via a first network;

receiving a request to access a file from the listing of files;

determining whether the file is stored locally on the client node; and

if the file is not stored locally on the client node;

discovering one or more peer client nodes that are communicatively coupled with the client node via a second network;

determining whether the file is stored locally on any of the one or more peer client nodes;

if the file is stored locally on a peer client node in the one or more peer client nodes, retrieving the file from the peer client node over the second network; and

if the file is not stored locally on any of the one or more peer client nodes, retrieving the file from the server system over the first network.

13. The non-transitory computer readable storage medium of claim 12 wherein the generating of the listing of files, the determining whether the file is stored locally on the client node, and the retrieving of the file from the server system are performed by a filesystem abstraction layer (FAL) running on the client node.

14. The non-transitory computer readable storage medium of claim 13 wherein the discovering of the one or more peer client nodes, the determining whether the file is stored locally on any of one or more peer client nodes, and the retrieving of the file from the peer client node are performed by a local download component that is in communication with the FAL.

15. The non-transitory computer readable storage medium of claim 12 wherein the peer client node is communicatively coupled with the server system via the first network, and wherein the peer client node is configured to synchronize, from the server system to local storage of the peer client node via the first network, each of the files associated with the user account, thereby causing the peer client node to maintain a copy of said each file locally.

16. A computing device configured to accelerate remote data retrieval, the computing device comprising:

a local storage device; and

a processor configured to;

generate a listing of files associated with a user account, the listing of files including one or more files that are stored remotely on a server system without being synchronized to the local storage device, the server system being communicatively coupled with the computing device via a first network;

receive a request to access a file from the listing of files;

determine whether the file is stored in the local storage device; and

if the file is not stored in the local storage device;

discover one or more peer client nodes that are communicatively coupled with the computing device via a second network;

determine whether the file is stored locally on any of the one or more peer client nodes;

if the file is stored locally on a peer client node in the one or more peer client nodes, retrieve the file from the peer client node over the second network; and

if the file is not stored locally on any of the one or more peer client nodes, retrieve the file from the server system over the first network.

17. The computing device of claim 16 wherein the generating of the listing of files, the determining whether the file is stored in the local storage device, and the retrieving of the file from the server system are performed by a filesystem abstraction layer (FAL) running on the computing device.

18. The computing device of claim 17 wherein the discovering of the one or more peer client nodes, the determining whether the file is stored locally on any of one or more peer client nodes, and the retrieving of the file from the peer client node are performed by a local download component that is in communication with the FAL.

19. The computing device of claim 16 wherein the peer client node is communicatively coupled with the server system via the first network, and wherein the peer client node is configured to synchronize, from the server system to local storage of the peer client node via the first network, each of the files associated with the user account, thereby causing the peer client node to maintain a copy of said each file locally.

20. The computing device of claim 16 wherein the computing device is a smartphone or tablet.