Starfish Software, Inc.

Intellisync Corporation

Sethuraman Suresh

Eric O Bodnar

Chris LaRue

Shekhar Kirani

Bryan Dube

Philippe Richard Kahn

John S Baumgarten

A synchronization system may include: A Source (outbound). An 'Accessor' communicating with a device's data store. A corresponding Target Accessor is provided for inbound data. Both Accessors work in conjunction with a 'Conduit,' which is provided for understanding the data that is being read so that the data can be mapped to a universal schema or &#x201c;unirecord&#x201d; or to a target dataset. The Conduit serves to broker the services of the Source Accessor and the Target Accessor and to provide field mapping and conversion. Core synchronization functionality is provided by a Synchronizer or &#x201c;Sync Core&#x201d; (engine). The Synchronizer performs its specific functionality on a per record or per data item basis, such as determining which records need to be inserted, deleted, updated, or the like.

System and methods for synchronizing information among disparate datasets

A synchronization system providing multi-client synchronization is described. By storing the data that is actually being synchronized (i.e., storing the actual physical body of a memo, for instance) inside an extra database, 'Grand Unification Database' (GUD), (or by specially-designated client data set) under control of a central or core synchronization engine, rather than transferring such data on a point-to-point basis, the system of the present invention provides a repository of information that is available at all times and does not require that any other synchronization client (e.g., PIM client or hand-held device) be connected. The GUD provides a super-set of the other client data sets. Therefore, if the user now includes an additional client, such as a server computer storing user information, the synchronization system has all the information necessary for synchronizing the new client, regardless of whether any of the other clients are currently available. The system can, therefore, correctly propagate information to any appropriate client without having to 'go back' to (i.e., connect to) the original client from which that data originated.

Data processing environment with methods providing contemporaneous synchronization of two or more clients

Synchronization system and associated methods provide synchronization of an arbitrary number of datasets, including more than two datasets. To achieve this, a reference dataset is used to store a super-set of the latest or most-recent data from all user datasets to provide a repository of information that is available at all times. Therefore, if the user later wishes to synchronize a new user dataset, such as one in a server computer that stores user information, the system already has all the information necessary for synchronizing the new dataset, regardless of whether any of the other datasets are then available. Further, to simplify use, a unified user interface is provided that allows the user to easily determine which of his or her datasets are currently set to be synchronized and allows the user to conveniently alter the current settings to select one, two, or even more than two clients for synchronization. Various &ldquo;conflict&rdquo; or &ldquo;duplicate&rdquo; resolution strategies are described for intelligently handling complexities resulting from allowing synchronization for an arbitrary number of datasets and allowing synchronization using even data from datasets that are not available. Architectural support for &ldquo;plug-in&rdquo; client accessors and type modules is also provided. This allows support to be added for new datasets or new types of data merely by developing and plugging in new, compact client accessors or type modules, without updating or replacing the core synchronization engine.

System and methods for synchronizing two or more datasets

A synchronization system providing multi-client synchronization is described. By storing the data that is actually being synchronized (i.e., storing the actual physical body of a memo, for instance) inside an extra database, &ldquo;Grand Unification Database&rdquo; (GUD), (or by specially-designated client data set) under control of a central or core synchronization engine, rather than transferring such data on a point-to-point basis, the system of the present invention provides a repository of information that is available at all times and does not require that any other synchronization client (e.g., PIM client or hand-held device) be connected. The GUD provides a super-set of the other client data sets. Therefore, if the user now includes an additional client, such as a server computer storing user information, the synchronization system has all the information necessary for synchronizing the new client, regardless of whether any of the other clients are currently available. The system can, therefore, correctly propagate information to any appropriate client without having to &ldquo;go back&rdquo; to (i.e., connect to) the original client from which that data originated.

Growing community of inventors

Santa Cruz, CA, United States of America

Sethuraman Suresh