Method for optimizing synchronization

• US 7,437,484 B2
• Filed: 12/29/2003
• Issued: 10/14/2008
• Est. Priority Date: 12/29/2003
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: O'Brien, Michael R., Mammen, Ashok C., Auriemma, Stephen T., Corbett, Maria M.
• Primary Examiner(s): Patel; Ashok B.
• Assistant Examiner(s): Belani; Kishin G
• Application Number:
  US10/745,529
• Publication Number:
  US 20050165947A1
• Time in Patent Office: 1,751 Days
• Field of Search: 709/248, 709/200, 709/228, 709/232, 707/1, 707/201, 710/21, 717/168, 717/171, 717/174, 370/392, 370/509
• 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: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users

Abstract

A method is provided for optimizing a SyncML slow sync between a proprietary client and server. When a slow sync is detected, the client and server can depart from the normal SyncML protocol and process summary data without having to compare all items on a field-by-field basis.

Claims

1. A method for optimizing a slow synchronization between a client and a server, the method comprising:

receiving, at the server, a synchronization package having missing or corrupt synchronization anchors;

sending, by the server, a request to the client to initiate a slow synchronization process;

receiving a slow synchronization package, at the server, wherein the slow synchronization package comprises summary data associated with documents stored at the client;

determining, by the server, if the slow synchronization package was received from a client designated proprietary by examining a header field of the slow synchronization package, the proprietary client departing from the slow synchronization process by sending the slow synchronization package comprising the summary data associated with documents stored at the client rather than sending the documents themselves;

processing, by the server, the received summary data associated with documents stored at the client, if the client is so designated,

wherein processing the received summary data further comprises;

comparing a unique identifier and a timestamp, obtained from the summary data, for each document stored at the client with a unique identifier and timestamp for each document stored at the server; and

determining if said unique identifiers and said timestamps match for the client document and server document wherein;

if said unique identifiers do not match, sending a status to the client indicating a document that needs to be sent by the client.

2. The method of claim 1 wherein the server has been designated proprietary.

3. The method of claim 1 wherein in response to processing the status, the client modifies its timestamp to a higher value such that the document indicated in the status is included in a subsequent synchronization session.

4. The method of claim 3 wherein the server receives the document indicated in the status during the subsequent synchronization session.

5. The method of claim 1 wherein the summary data associated with documents stored at the client is sent by the proprietary client as a series of ADD commands and the server processes the ADD commands.

6. The method of claim 1 wherein the request to initiate the slow synchronization process is sent to the server, upon receipt of a synchronization package having missing or corrupt anchors at the client.

7. The method of claim 1 wherein sending, by the server, a request to the client to initiate a slow synchronization process, further comprises:

sending, by the server, a slow synchronization initialization package to the client, the slow synchronization initialization package including a request to the client to send all documents stored at the client.

8. The method of claim 7 further comprising:

determining, by the client, if the request to initiate the slow synchronization process was sent by a server designated proprietary;

wherein the proprietary client departs from the slow synchronization process by sending the slow synchronization package comprising the summary data associated with the documents stored at the client rather than the documents themselves, if the server is so designated.

9. The method of claim 8 wherein determining, by the client, if the request to initiate the slow synchronization process was sent by a server designated proprietary, further comprises:

receiving the slow synchronization initialization package; and

examining a header field to determine if the server has been designated proprietary.