Event-based synchronization in a file sharing environment

• US 10,235,331 B1
• Filed: 06/18/2015
• Issued: 03/19/2019
• Est. Priority Date: 06/18/2015
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Inventors: Hrebicek, Ondrej, Kumar, Srin, Lee, Eric, Verma, Ashwani, Rondeau, Andrew
• Primary Examiner(s): Leroux, Etienne P
• Application Number:
  US14/743,306
• Time in Patent Office: 1,370 Days
• CPC Class Codes: G06F 16/148 File search processing
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

Techniques to synchronize data across a plurality of endpoints are disclosed. An indication that data associated with a file or other object included in a synchronization set has been changed is received from a first synchronization endpoint associated with the synchronization set. A synchronization event that reflects the change is created and added to a synchronization event stream that is accessible to a second endpoint associated with the synchronization set.

Claims

1. A method of synchronizing data, comprising:

receiving, by one or more processors associated with a synchronization server, from a first synchronization endpoint associated with a synchronization set an indication that data associated with a file or other object comprising the synchronization set has been changed;

creating, by the one or more processors associated with the synchronization server, and adding to a synchronization event stream that is accessible to one or more second endpoints associated with the synchronization set a synchronization event that reflects the change; and

propagating, by the one or more processors associated with the synchronization server, a change in the data associated with a file or other object comprising the synchronization set to the one or more second endpoints via one or more networks, the propagating the change comprising;

receiving, by the one or more processors associated with the synchronization server, a request for information associated with an update to the synchronization stream, wherein the request for information associated with an update to the synchronization stream is communicated to the synchronization server by the-one or more second endpoints; and

providing, by the one or more processors associated with the synchronization server, at least a part of the synchronization event stream to the one or more second endpoints in response to the request for information associated with an update to the synchronization stream, wherein the synchronization event stream is used in connection with a determination of whether the changed data can be merged with an existing synchronization event that is already present in the event stream.

2. The method of claim 1, wherein the first synchronization endpoint comprises a first synchronization client.

3. The method of claim 2, wherein the one or more second endpoints comprises a second synchronization client, and wherein the synchronization event is created and added to the synchronization event stream at a synchronization server to which the first synchronization client and the second synchronization client have access.

4. The method of claim 1, wherein the changed data comprises file content data.

5. The method of claim 1, wherein the changed data comprises metadata.

6. The method of claim 1, wherein the synchronization event stream is accessible to the one or more second endpoints via a network connection to a synchronization server configured to respond to queries from the second endpoint with respect to the synchronization event stream.

7. The method of claim 6, wherein the one or more second endpoints are configured to query the synchronization server to determine whether the synchronization event stream includes any events that have not yet been downloaded to the one or more second endpoints.

8. The method of claim 7, wherein the query is based at least in part on an event sequence number.

9. The method of claim 7, wherein the one or more second endpoints are configured to request download of one or more events that have not yet been downloaded to the one or more second endpoints.

10. A system to synchronize data, comprising:

a communication interface; and

one or more processors associated with a synchronization server coupled to the communication interface and configured to;

receive from a first synchronization endpoint associated with a synchronization set, via the communication interface, an indication that data associated with a file or other object comprising the synchronization set has been changed;

create and add to a synchronization event stream that is accessible to one or more second endpoints associated with the synchronization set a synchronization event that reflects the change; and

propagate a change in the data associated with a file or other object comprising the synchronization set to the one or more second endpoints via one or more networks, wherein propagating the change comprises;

receive a request for information associated with an update to the synchronization stream, wherein the request for information associated with an update to the synchronization stream is communicated to the synchronization server by the one or more second endpoints; and

provide at least a part of the synchronization event stream to the one or more second endpoints in response to the request for information associated with an update to the synchronization stream, wherein the synchronization event stream is used in connection with a determination of whether the changed data can be merged with an existing synchronization event that is already present in the event stream.

11. The system of claim 10, wherein the first synchronization endpoint comprises a first synchronization client.

12. The system of claim 11, wherein the one or more second endpoints comprises a second synchronization client, and wherein the synchronization event is created and added to the synchronization event stream at a synchronization server to which the first synchronization client and the second synchronization client have access.

13. The system of claim 10, wherein the changed data comprises file content data.

14. The system of claim 10, wherein the changed data comprises metadata.

15. The system of claim 10, wherein the synchronization event stream is accessible to the one or more second endpoints via a network connection to a synchronization server configured to respond to queries from the second endpoint with respect to the synchronization event stream.

16. The system of claim 15, wherein the one or more second endpoints are configured to query the synchronization server to determine whether the synchronization event stream includes any events that have not yet been downloaded to the one or more second endpoints.

17. The system of claim 16, wherein the query is based at least in part on an event sequence number.

18. The system of claim 16, wherein the one or more second endpoints are configured to request download of one or more events that have not yet been downloaded to the one or more second endpoints.

19. A computer program product to synchronize data, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

receiving, by a synchronization server, from a first synchronization endpoint associated with a synchronization set an indication that data associated with a file or other object comprising the synchronization set has been changed;

creating, by the synchronization server, and adding to a synchronization event stream that is accessible to a second endpoint associated with the synchronization set a synchronization event that reflects the change; and

propagating, by the synchronization server, a change in the data associated with a file or other object comprising the synchronization set to the one or more second endpoints via one or more networks, the propagating the change comprising;

receiving, by the synchronization server, a request for information associated with an update to the synchronization stream, wherein the request for information associated with an update to the synchronization stream is communicated to the synchronization server by the one or more second endpoints; and

providing, by the synchronization server, at least a part of the synchronization event stream to the second endpoint in response to the request for information associated with an update to the synchronization stream, wherein the synchronization event stream is used in connection with a determination of whether the changed data can be merged with an existing synchronization event that is already present in the event stream.