Synchronization adapter for synchronizing data to applications that do not directly support synchronization

• US 9,298,795 B2
• Filed: 10/16/2012
• Issued: 03/29/2016
• Est. Priority Date: 06/19/2008
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Suthar, Paresh, Ozzie, Jack, Lees, Steven
• Primary Examiner(s): Woo, Isaac M
• Application Number:
  US13/652,589
• Publication Number:
  US 20130041867A1
• Time in Patent Office: 1,260 Days
• Field of Search: 707 60-899, 707/610
• US Class Current: 1/1
• CPC Class Codes: G06F 16/1794 Details of file format conversion
• CPC Class Codes: G06F 16/2358 Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: G06F 16/275 Synchronous replication

Abstract

A synchronization adapter is coupled to the application that does not support synchronization and generates the necessary synchronization metadata for all data in the application that is to be synchronized. The synchronization adapter then combines the metadata to the actual data to be synchronized to form a synchronization feed. The synchronization feed is stored in an internal cache (or data store) which is internal to the application, or an external cache (or data store), which is external to the application, or it can be stored in both caches. The synchronization adapter also intermittently determines whether the application data has changed, thus warranting a change in its metadata, or whether a synchronization operation is warranted to synchronization operation is warranted to synchronize the data with data in another application. In either case, the synchronization adapter makes the changes to the data, or performs a synchronization operation.

Claims

1. A synchronization endpoint system, comprising:

a first synchronization component that receives a synchronization feed that includes a data item of an application and synchronization metadata that is separate from the data item, the synchronization metadata having a synchronization metadata format and defines how to synchronize the data item in accordance with a synchronization protocol, wherein the synchronization metadata is derived from and associated with the data item of the application, and wherein the application does not support the synchronization metadata format; and

a second synchronization component that receives the synchronization feed, supports the synchronization metadata format, and incorporates the data item and the associated synchronization metadata into an application function of the synchronization endpoint system.

2. The system of claim 1, wherein the synchronization feed is a modified synchronization feed.

3. The system of claim 1, wherein the synchronization metadata is modified synchronization metadata.

4. The system of claim 1, wherein the second synchronization component utilizes the synchronization metadata to selectively synchronize the data item based on a data change determination.

5. The system of claim 1, wherein the second synchronization component utilizes the synchronization metadata to selectively synchronize the data item based on a determination related to an amount of time that has passed since a previous synchronization operation.

6. A computer-implemented synchronization adapter, comprising a metadata generator that receives an indication of an item in an application that is to be synchronized to one or more of a plurality of other applications, wherein the metadata generator also generates synchronization metadata for the item in the application, the synchronization metadata enabling synchronization of the item in accordance with a synchronization protocol, and the synchronization metadata having a format that is not supported by the application.

7. The adapter of claim 6, wherein the adapter includes a synchronization component that utilizes the synchronization metadata to synchronize the item with one or more of the plurality of other applications.

8. The adapter of claim 6, wherein the adapter includes a synchronization component that utilizes the synchronization metadata to synchronize a data item related to but different than said item with one or more of the plurality of other applications.

9. The adapter of claim 6, wherein the adapter includes a filtering component that applies a filter to said item and, based on the application of the filter, selectively synchronizes the item with one or more of the plurality of other applications.

10. The adapter of claim 6, wherein the adapter stores the synchronization metadata in a data store internal to the first application.

11. The adapter of claim 6, wherein the adapter stores the synchronization metadata in a data store external to the first application.

12. The adapter of claim 6, wherein the adapter is associated with a change detector that determines that the item has changed, and wherein the adapter responds to the determination by utilizing the synchronization metadata to synchronize the item as changed with one or more of the plurality of other applications.

13. The adapter of claim 6, wherein the adapter includes a synchronization component that utilizes the synchronization metadata to synchronize the item with a synchronization endpoint.

14. The adapter of claim 6, wherein the adapter utilizes the synchronization metadata to selectively synchronize the item based on a data change determination.

15. The adapter of claim 6, wherein the adapter utilizes the synchronization metadata to selectively synchronize the item based on a determination related to an amount of time that has passed since a previous synchronization operation.

16. A method of synchronizing data, comprising:

receiving, at a synchronization adapter from a first application, a plurality of data items to be synchronized with one or more other applications;

generating, with the synchronization adapter, synchronization metadata for each of the plurality of data items to be synchronized, the synchronization metadata having a format that is not supported by the first application;

binding the synchronization metadata to corresponding data items to form a plurality of synchronization feeds, each synchronization feed comprising a given one of the data items and the synchronization metadata generated for the given data item;

receiving an indication that a particular data item in the plurality of data items has changed since a last synchronization operation;

deconstructing the synchronization feed into the particular data item and the corresponding synchronization metadata;

modifying the particular data item based on the change in the particular data item;

generating any modified synchronization metadata based on the change in the particular data item;

binding the modified data item to the modified synchronization metadata to obtain a modified synchronization feed; and

publishing the modified synchronization feed.

17. The method of claim 16, comprising receiving a synchronization teed reflecting that the particular data item has changed.

18. The method of claim 16, further comprising intermittently receiving a plurality of different synchronization feeds representing data changes.

19. The method of claim 16, wherein generating synchronization metadata for each of the plurality of data items to be synchronized comprises:

generating synchronization metadata that is separate from the data item, the synchronization metadata having a synchronization metadata format and defines how to synchronize the data item in accordance with a synchronization protocol.

20. The method of claim 16, wherein receiving an indication comprises applying a filter to the particular data item to selectively synchronize the particular data item with the one or more other applications.