Detecting low fidelity sync data

• US 8,019,898 B2
• Filed: 03/04/2008
• Issued: 09/13/2011
• Est. Priority Date: 04/30/2004
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Starbuck, Bryan T., Potter, David R.
• Primary Examiner(s): Pwu; Jeffrey
• Assistant Examiner(s): Waqas; Saad A
• Application Number:
  US12/041,875
• Publication Number:
  US 20080155122A1
• Time in Patent Office: 1,288 Days
• Field of Search: 709/248
• US Class Current: 709/248
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users

Abstract

The present invention provides for a distributed computing system that is capable of determining when data needs to be synced between two computer devices because data has changed on at least a remote device. More particularly, the present invention provides for a sync adapter that uses sync data to detect that a property on a device is new and needs to synchronize with corresponding data on another machine. The sync data is specific to the two devices in that the sync data mirrors data that was last synchronized between these two computing devices. Other example embodiments use the sync data to detect and mark data as low fidelity data for identifying any date and time information associated with the low fidelity data as potentially unreliable.

Claims

1. In a distributed computing system comprising at least one local machine and at least one remote device, wherein at least some of the data stored on the at least one remote device is low fidelity data, a method of determining whether data on the at least one remote device needs to be updated during synchronization with the at least one local machine because data has changed on one of the at least one remote device or the at least one local machine, the method comprising the acts of:

initiating a first synchronization of data stored on a local machine and data stored on a remote device, wherein the data stored on the remote device includes low fidelity data for at least one property of the data being synched, wherein low fidelity data is data that is not marked with a timestamp of the last update to the data;

synchronizing the data on the local machine and the data on the remote device;

storing at the local machine sync data relating to the low fidelity data for the at least one property, the sync data mirroring the data, including the at least one property, stored on the remote device at the time of the first synchronization;

updating the at least one property stored on the remote machine;

initiating a second synchronization of the data stored on the local machine with the data stored on the remote device;

determining that the at least one property has been updated on the remote device by comparing the at least one property stored on the remote device with the at least one property stored in the sync data stored at the local machine;

upon determining that the at least one property stored on the remote device is different than the at least one property stored in the sync data, determining whether the at least one property stored on the local machine has also been updated such that;

upon determining that the at least one property stored on the local machine has also been updated, conducting a conflict resolution to determine whether the at least one property stored on the remote device or the at least one property stored on the local machine should be synchronized; and

upon determining that the at least one property stored on the local machine has not also been updated, synchronizing the at least one property stored on the remote device to the local machine including storing a timestamp with the at least one property stored on the local machine, the timestamp being set to an increment after the time of the last known update to the at least one property on the local machine before the second synchronization such that the update made to the at least one property on the remote device has precedence over any update made to the at least one property on the local machine prior to the timestamp.

2. The method of claim 1, further comprising:

determining via the conflict resolution that the at least one property stored on the remote device should be synchronized, and synchronizing the at least one property stored on the remote device to the local machine to replace the at least one property stored on the local machine.

3. The method of claim 1, further comprising:

determining via the conflict resolution that the at least one property stored on the local machine should be synchronized, and synchronizing the at least one property stored on the local machine to the remote device to replace the at least one property stored on the remote device.

4. The method of claim 1, wherein the conflict resolution includes prompting the user to select either the at least one property stored on the remote device or the at least one property stored on the local machine.

5. The method of claim 1, wherein the local machine is a server and the remote device is a personal computer or PDA.

6. The method of claim 1, wherein the local machine is a personal computer or PDA and the remote device is a server.

7. The method of claim 1, wherein the sync data is stored as metadata.

8. The method of claim 1, wherein the data stored on the remote device and the data stored on the local machine include information about a contact and the at least one property is information about the contact.

9. The method of claim 1, wherein the at least one property includes one or more of an address, phone number, email address, or web page.

10. One or more computer storage media having stored thereon computer-executable instructions, which when executed perform the following method:

initiating a first synchronization of data stored on a local machine and data stored on a remote device, wherein the data stored on the remote device includes low fidelity data for at least one property of the data being synched, wherein low fidelity data is data that is not marked with a timestamp of the last update to the data;

synchronizing the data on the local machine and the data on the remote device;

storing at the local machine sync data relating to the low fidelity data for the at least one property, the sync data mirroring the data, including the at least one property, stored on the remote device at the time of the first synchronization;

updating the at least one property stored on the remote machine;

initiating a second synchronization of the data stored on the local machine with the data stored on the remote device;

determining that the at least one property has been updated on the remote device by comparing the at least one property stored on the remote device with the at least one property stored in the sync data stored at the local machine;

upon determining that the at least one property stored on the remote device is different than the at least one property stored in the sync data, determining whether the at least one property stored on the local machine has also been updated such that;

upon determining that the at least one property stored on the local machine has also been updated, conducting a conflict resolution to determine whether the at least one property stored on the remote device or the at least one property stored on the local machine should be synchronized; and

upon determining that the at least one property stored on the local machine has not also been updated, synchronizing the at least one property stored on the remote device to the local machine including storing a timestamp with the at least one property stored on the local machine, the timestamp being set to an increment after the time of the last known update to the at least one property on the local machine before the second synchronization such that the update made to the at least one property on the remote device has precedence over any update made to the at least one property on the local machine prior to the timestamp.

11. The computer storage media of claim 10, further comprising:

determining via the conflict resolution that the at least one property stored on the remote device should be synchronized, and synchronizing the at least one property stored on the remote device to the local machine to replace the at least one property stored on the local machine.

12. The computer storage media of claim 10, further comprising:

determining via the conflict resolution that the at least one property stored on the local machine should be synchronized, and synchronizing the at least one property stored on the local machine to the remote device to replace the at least one property stored on the remote device.

13. The computer storage media of claim 10, wherein the conflict resolution includes prompting the user to select either the at least one property stored on the remote device of the at least one property stored on the local machine.

14. The computer storage media of claim 10, wherein the local machine is a server and the remote device is a personal computer or PDA.

15. The computer storage media of claim 10, wherein the local machine is a personal computer or PDA and the remote device is a server.

16. The computer storage media of claim 10, wherein the sync data is stored as metadata.

17. The computer storage media of claim 10, wherein the data stored on the remote device and the data stored on the local machine include information about a contact and the at least one property is information about the contact.

18. The computer storage media of claim 10, wherein the at least one property includes one or more of an address, phone number, email address, or web page.

19. A system for synchronizing data between a local machine that stores high fidelity data and a remote device that stores low fidelity data, the system comprising:

a processor; and

memory storing computer executable instructions which when executed by the processor perform a method comprising;

initiating a first synchronization of data stored on a local machine and data stored on a remote device, wherein the data stored on the remote device includes low fidelity data for at least one property of the data being synched, wherein low fidelity data is data that is not marked with a timestamp of the last update to the data;

synchronizing the data on the local machine and the data on the remote device;

storing at the local machine sync data relating to the low fidelity data for the at least one property, the sync data mirroring the data, including the at least one property, stored on the remote device at the time of the first synchronization;

updating the at least one property stored on the remote machine;

initiating a second synchronization of the data stored on the local machine with the data stored on the remote device;

determining that the at least one property has been updated on the remote device by comparing the at least one property stored on the remote device with the at least one property stored in the sync data stored at the local machine;

upon determining that the at least one property stored on the remote device is different than the at least one property stored in the sync data, determining whether the at least one property stored on the local machine has also been updated such that;

upon determining that the at least one property stored on the local machine has also been updated, conducting a conflict resolution to determine whether the at least one property stored on the remote device or the at least one property stored on the local machine should be synchronized; and

upon determining that the at least one property stored on the local machine has not also been updated, synchronizing the at least one property stored on the remote device to the local machine including storing a timestamp with the at least one property stored on the local machine, the timestamp being set to an increment after the time of the last known update to the at least one property on the local machine before the second synchronization such that the update made to the at least one property on the remote device has precedence over any update made to the at least one property on the local machine prior to the timestamp.