Server-assisted and peer-to-peer synchronization

• US 8,239,479 B2
• Filed: 06/22/2007
• Issued: 08/07/2012
• Est. Priority Date: 06/22/2007
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Sagar, Akash J., Moromisato, George P., Chung, Richard Yiu-Sai, Ozzie, Raymond E., Ozzie, Jack E., Reed, David Richard, Vernal, Michael Steven, Fedorov, Vladimir Dmitri, Annamalai, Muthukaruppan
• Primary Examiner(s): Winder, Patrice
• Assistant Examiner(s): Hussain, Tauqir
• Application Number:
  US11/766,985
• Publication Number:
  US 20080317068A1
• Time in Patent Office: 1,873 Days
• Field of Search: 709/217
• US Class Current: 709/217
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• 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/1074 for supporting data block transmission mechanisms file transfer H04L67/06
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

Systems and methods for synchronizing data between endpoints using elements of centralized and decentralized synchronization systems and communication topologies are disclosed. Such systems and methods may in some cases synchronize some subset of data with a centralized endpoint while another subset of data is synchronized in a decentralized fashion directly with other endpoints. Such systems and methods may include a variety of cooperative functionality to assist in the synchronization of data between endpoints.

Claims

1. One or more computer-readable memory devices or storage devices having instructions stored thereon that, when executed by a computing device, cause a method to be performed, the method comprising:

synchronizing a feed maintained by a server endpoint with another feed maintained by a first endpoint, the synchronizing comprising, by the server endpoint;

obtaining metadata from the first endpoint, wherein the metadata obtained from the first endpoint includes an identifier of a blob that can be retrieved from one or more locations, and at least a portion of the blob can be retrieved from an individual location other than the server endpoint; and

updating the feed maintained by the server endpoint by merging the metadata obtained from the first endpoint with other metadata maintained by the server endpoint;

updating a blob lookup service with one or more blob locators that identify the one or more locations from where the blob can be retrieved, wherein an individual blob locator identifies the individual location other than the server endpoint from where the portion of the blob can be retrieved; and

,

communicating the merged metadata, including at least the identifier of the blob, to other endpoints that have subscribed to receive metadata updates,

wherein at least the synchronizing is performed using a synchronization protocol for communicating the feed maintained by the server endpoint and the feed maintained by the first endpoint, and

wherein, in at least one instance, an individual other endpoint that has subscribed to receive the metadata updates obtains the portion of the blob from the location other than the server endpoint and does not obtain the portion from the server endpoint.

2. The computer-readable memory devices or storage devices of claim 1, the method further comprising:

receiving a request from the individual other endpoint for the individual blob locator that identifies the individual location other than the server endpoint from where the portion of the blob can be retrieved;

identifying the individual blob locator using the blob lookup service; and

communicating the individual blob locator to the individual other endpoint.

3. The computer-readable memory devices or storage devices of claim 1, wherein a second individual blob locator of the one or more blob locators identifies a second individual location from where a second portion of the blob can be retrieved, the method further comprising:

receiving a request for at least one blob locator of the one or more blob locators;

identifying the individual blob locator associated with the individual location and the second individual blob locator associated with the second individual location; and

communicating the individual blob locator and the second individual blob locator in response to the request.

4. The computer-readable memory devices or storage devices of claim 1, the method further comprising:

accepting a request to cache the portion of the blob;

retrieving the portion of the blob;

storing the portion of the blob in a blob cache; and

updating the blob lookup service with a second location that identifies the blob cache.

5. The computer-readable memory devices or storage devices of claim 1, the method further comprising:

accepting a request to store the portion of the blob in a non-transient cloud storage data store;

retrieving the portion of the blob; and

storing the portion of the blob in the cloud storage data store.

6. The one or more computer-readable memory devices or storage devices of claim 1, wherein the one or more locations from where the blob can be retrieved include:

a device endpoint other than the first endpoint or the server endpoint,

a blob cache service, or

a cloud storage service.

7. The one or more computer-readable memory devices or storage devices of claim 1, wherein the identifier of the blob comprises at least one of:

a string of alphanumeric characters,

a uniform resource locator, or

a uniform resource identifier.

8. A method comprising:

synchronizing a feed maintained by a server endpoint with a first endpoint, the synchronizing comprising, by the server endpoint;

obtaining metadata from the first endpoint, wherein the metadata obtained from the first endpoint includes an identifier of a blob that has been newly created or modified by the first endpoint and the blob is not communicated to the server endpoint with the metadata; and

updating the feed maintained by the server endpoint by merging the metadata obtained from the first endpoint with other metadata maintained by the server endpoint;

updating a blob lookup service with a blob locator that identifies the first endpoint as a location from where the blob can be retrieved;

communicating the merged metadata, including at least the identifier of the blob, to a second endpoint that has subscribed to receive metadata updates,

wherein at least the synchronizing is performed using a synchronization protocol for communicating the feed maintained by the server, and

wherein, in at least one instance, the second endpoint obtains the blob from the first endpoint using the blob locator that identifies the first endpoint.

9. The method according to claim 8, wherein the other metadata maintained by the server endpoint comprises other identifiers of other blobs that are provided by other endpoints and are not provided by the server endpoint.

10. The method according to claim 8, wherein the second endpoint does not obtain the identifier of the blob from the first endpoint before the identifier of the blob is communicated to the second endpoint by the server endpoint.

11. The method according to claim 8, further comprising:

receiving a request from the second endpoint for the blob locator that identifies the first endpoint;

identifying the blob locator using the blob lookup service; and

communicating the blob locator to the second endpoint.

12. The method according to claim 11, wherein different portions of the blob are provided to the second endpoint by multiple other endpoints.

13. The method according to claim 12, further comprising communicating other blob locators identifying the multiple other endpoints to the second endpoint.

14. The method according to claim 13, wherein the second endpoint downloads the blob from the first endpoint and at least some of the multiple other endpoints at least partly in parallel.

15. A system comprising:

a storage service;

a blob lookup service; and

a processing unit configured to execute one or more of the storage service or the blob lookup service;

wherein the storage service is configured to;

obtain metadata from a first device endpoint, wherein the metadata obtained from the first device endpoint includes an identifier of a blob that has been newly created or modified by the first device endpoint;

update a feed maintained by the storage service by merging the metadata obtained from the first device endpoint with other metadata maintained by the storage service;

update the blob lookup service with a blob locator that identifies the first device endpoint as a location from where the blob can be retrieved by other device endpoints; and

communicate the merged metadata to the other device endpoints using a synchronization protocol for communicating the feed maintained by the storage service;

wherein the blob lookup service is configured to provide the blob locator to the other device endpoints upon request.

16. The system according to claim 15, wherein the blob lookup service is further configured to provide, to the other device endpoints, other blob locators identifying at least a second device endpoint that has previously registered with the blob lookup service as having the blob.

17. The system according to claim 15, further comprising the first device endpoint.

18. The system according to claim 17, further comprising the other device endpoints.

19. The system according to claim 15, wherein the synchronization protocol comprises a Simple Sharing Extensions (SSE) protocol.

20. The system according to claim 15, further comprising a cloud storage service configured to store the blob using multiple redundant data stores and to provide the blob to at least some of the other device endpoints upon request.