Apparatus and methods for providing data synchronization by facilitating data synchronization system design

• US 6,928,467 B2
• Filed: 02/01/2001
• Issued: 08/09/2005
• Est. Priority Date: 02/02/2000
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: InnoPath Software, Inc. (Qualcomm, Inc.)
• Inventors: Peng, Luosheng
• Primary Examiner(s): VU, VIET DUY
• Application Number:
  US09/776,598
• Publication Number:
  US 20010048728A1
• Time in Patent Office: 1,650 Days
• Field of Search: 709/203, 709/219, 709/213, 709/217, 709/248, 707/104, 707/10, 707/203, 719/319, 719/329
• US Class Current: 709/219
• CPC Class Codes: G06F 12/121 using replacement algorithms
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 51/06 Message adaptation to terminal or network requirements
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• 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 67/288 Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data
• 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: H04W 28/10 Flow control between communication endpoints
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99935 : Query augmenting and refining, e.g. inexact access
• CPC Class Codes: Y10S 707/99936 : Pattern matching access
• CPC Class Codes: Y10S 707/99945 : Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99948 : Application of database or data structure, e.g. distributed, multimedia, or image

Abstract

Object stores are used as building blocks to construct a system with variable complexity on a network. Typically, an object store comprises information (e.g., data) stored in object format, or objects. The objects and object stores are managed by an object version management mechanism that adapts to different object store types and optimizes resource consumption by each object store. Various data fields are used to indicate an object'"'"'s version within an object store. Version information is used to compare the states among matching object replicas in matching object stores. Utilizing both the object store based system and the object version management mechanism, a data synchronization protocol is developed. The data synchronization protocol is capable of adapting to different types of object stores and the characteristics of network connection media to optimize data synchronization.

Claims

1. A method for facilitating data synchronization, comprising the steps of:

(a) obtaining a list of encoding methods from a remote object store;

(b) extracting a first set of objects to be synchronized with said remote object store;

(c) packing said first set of objects, their associated identifiers and synchronization versions into a request synchronization message;

(d) sending said request synchronization message to said remote object store;

(e) receiving a response synchronization message from said remote object store, said response synchronization message indicating a number of updated objects at the remote object store; and

(f) resetting a corresponding set of synchronization versions to said updated objects.

2. The method of claim 1, further comprising the steps of:

(1) checking object store replica information corresponding to said remote object store;

(2) sending a request message to said remote object store if any information is missing from said object store replica information;

(3) receiving a response from said remote object store; and

(4) registering said response in said object store replica information.

3. The method of claim 1, further comprising the steps of:

(1) updating objects based on said request synchronization message at said remote object store; and

(2) sending a response synchronization message providing a number of objects received and processed.

4. The method of claim 1, further comprising the step of:

adding a field in said request synchronization message indicating whether said request synchronization message is a last request to said remote object store.

5. A computer program product for facilitating data synchronization, comprising:

(a) logic code for obtaining a list of encoding methods from a remote object store;

(b) logic code for extracting a first set of objects to be synchronized with said remote object store;

(c) logic code for packing said first set of objects, their associated identifiers and synchronization versions into a request synchronization message;

(d) logic code for sending said request synchronization message to said remote object store;

(e) logic code for receiving a response synchronization message from said remote object store, said response synchronization message indicating a number of updated objects at the remote object store; and

(f) logic code for resetting a corresponding set of synchronization versions to said updated objects.

6. The computer program product of claim 5, further comprising:

(1) logic code for checking object store replica information corresponding to said remote object store;

(2) logic code for sending a request message to said remote object store if any information is missing from said object store replica information;

(3) logic code for receiving a response from said remote object store; and

(4) logic code for registering said response in said abject store replica information.

7. The computer program product of claim 5, further comprising:

(1) logic code for updating objects based on said request synchronization message at said remote object store; and

(2) logic code for sending a response synchronization message providing a number of objects received and processed.

8. The computer program product of claim 5, further comprising:

logic code for adding a field in said request synchronization message indicating whether said request synchronization message is a last request to said remote object store.