Synchronization View

• US 20060117368A1
• Filed: 02/09/2006
• Published: 06/01/2006
• Est. Priority Date: 10/23/2003
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Fisher, Oliver G., Dunn, Melissa W., Perlow, Jon, Erickson, Paul, Park, Vivien
• Granted Patent: US 7,870,097 B2
• Time in Patent Office: Days
• US Class Current: 725/114
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

Systems and methods are disclosed for synchronizing data stored in remote stores. Data stored in locations such as computer applications, consumer electronic devices and Internet websites is synchronized with a central database within a computer device. The computer device may also store constraints that limit the type of data that may be synchronized with individual stores. A graphical user interface may use different formats or icons to distinguish between data stored in a store and data included within the central database.

Claims

1. A method of maintaining related data stored in a plurality of stores, the method comprising:

(a) maintaining at least one publisher record that identifies data stored in a remote store;

(b) maintaining a composite record that identifies a composite of data stored in the plurality of stores;

(c) displaying in a first format in a graphical user interface data identified in the publisher record; and

(d) displaying in a second format in the graphical user interface data included in the composite record and not included in the publisher record;

wherein the first format is different from the second format.

2. The method of claim 1, wherein the first format includes characters having a first darkness level and the second format includes characters having a second darkness level.

3. The method of claim 1, wherein one of the first and second formats includes an icon.

4. The method of claim 1, further comprising:

(e) receiving an edit command to edit data included in the composite record;

(f) in response to (e) editing the composite record;

(g) determining whether the edit command applies to the data included in the publisher record;

(h) when the edit command applies to the data included in the publisher record, editing the publisher record.

5. The method of claim 4, further including:

(i) transmitting edit information to the store when the edit command applies to the data included in the publisher record.

6. The method of claim 5, wherein the composite record and the publisher record are part of a computer operating system.

7. The method of claim 1, wherein the data stored on the store comprises contact data.

8. The method of claim 1, wherein the data stored on the store comprises calendar data.

9. The method of claim 1, wherein the data stored on the store comprises a digital certificate.

10. A method of updating contact data stored on a plurality of computing devices, the method comprising:

receiving at a computer operating system an edit instruction to edit contact data stored on a first computer device;

coupling the first computer device to a second computer device that stores contact data;

transmitting updated contact data information from the operating system of the first computer device to the second computer device.

11. The method of claim 10, wherein the updated contact data information includes a new contact record.

12. The method of claim 10, further including:

receiving at the operating system of the first computer device updated contact data information transmitted from the second computer device.

13. A computer readable medium containing computer readable instructions for causing a computer device to perform the steps comprising:

(a) maintaining at least one publisher record that identifies data stored in a store;

(b) maintaining a composite record that identifies a composite of data stored in the plurality of stores;

(c) displaying in a first format in a graphical user interface data identified in the publisher record; and

(d) displaying in a second format in the graphical user interface data included in the composite record and not included in the publisher record.