Accounting for update notifications in synchronizing data that may be represented by different data structures

• US 20050144312A1
• Filed: 12/23/2004
• Published: 06/30/2005
• Est. Priority Date: 01/24/2001
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Fishman, Neil S., Seinfeld, Marc E., Kadyk, Donald J.
• Granted Patent: US 7,293,046 B2
• Time in Patent Office: Days
• US Class Current: 709/237
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 67/01 Protocols
• 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/922 Communications
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

Methods, systems, and computer program products for synchronizing data stored at one or more message clients with data stored at a message server where the message clients may receive update notifications and may represent the data using different data structures than the message server uses to represent the same data. A token is associated with each data change that occurs at the message server. The message server sends each change and associated token to the message clients. When the message clients request a synchronization, the tokens they received are returned to the message server for comparison with the tokens the message server sent to the message clients. If the message clients do not return a particular token, the message server determines that the clients did not receive the corresponding change and resends the change to the message clients. Tokens may also be used to divide a change into one or more portions, with only one portion being provided initially. Then, in response to receiving the token associated with the portion, the message server may provide the remaining portion of the message to the message clients.

Claims

1. A computer program product comprising one or more computer-readable media having computer-executable instructions for implementing a method, in an electronic messaging environment that includes a message server and one or more message clients, for enabling synchronization of data stored at the one or more message clients with data stored at the message server, while accounting for one or more update notifications that either may or may not have been received by the one or more message clients and while accounting for any differences in how the message server and the one or more message clients store data, the method comprising:

a step for providing, over an unreliable communication channel, a plurality of notifications to the one or more message clients without requesting or receiving acknowledgement of receipt of the notifications by the one or more message clients, the plurality of notifications including (i) a plurality of changes to the data stored at the message server, and (ii) a plurality of tokens identifying each of the plurality of changes;

a step for determining whether or not the one or more message clients are missing any of the plurality of notifications based on whether or not the one or more message clients can provide back each of the plurality of tokens identifying each of the plurality of changes;

an act of sending a list identifying missing notifications to the one or more corresponding message clients;

receiving a request from the one or more message clients to resend the one or more missing notifications; and

an act of resending the one or more missing notifications to the one or more requesting message clients.

2. A computer program product as recited in claim 1, wherein the unreliable communication channel comprises a wireless communication channel.

3. A computer program product as recited in claim 1, further comprising a step for providing a collection object to the one or more message clients, the collection object representing a state of the data stored at the one or more message clients.

4. A computer program product as recited in claim 1, wherein the step for providing any change associated with a missing notification further comprises a step for providing any token associated with a missing notification.

5. A computer program product as recited in claim 1, further comprising an act of compressing the plurality of tokens to produce tokens that are unique to each of the one or more message clients.

6. A computer program product as recited in claim 1, wherein the data stored at the message server includes at least one of contact data, calendar data, task data, and email data and wherein the one or more message clients comprise one of a portable personal computer, a cellular telephone, a pager, and a personal digital assistant.

7. A computer program product as recited in claim 1, wherein at least one change made in the message server data is divided into a first portion and a second portion, and at least one notification corresponds to the first portion, the method further comprising a step for providing the second portion to the one or more message clients in response to receiving a token associated with the first portion.