|Publication number||US6915312 B2|
|Application number||US 09/928,609|
|Publication date||Jul 5, 2005|
|Filing date||Aug 13, 2001|
|Priority date||Dec 16, 1997|
|Also published as||US6275831, US20020116405|
|Publication number||09928609, 928609, US 6915312 B2, US 6915312B2, US-B2-6915312, US6915312 B2, US6915312B2|
|Inventors||Eric O. Bodnar, Chris LaRue, Bryan Dube, Shekhar Kirani, Sethuraman Suresh|
|Original Assignee||Starfish Software, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (38), Referenced by (36), Classifications (14), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present application is a continuation of U.S. application Ser. No. 09/136,212, filed Aug. 18, 1998, now U.S. Pat. No. 6,275,831; which is related to and claims the benefit of priority from the following commonly owned, formerly U.S. provisional patent applications: Ser. No. 60/069,731, filed Dec. 16, 1997, and entitled DATA PROCESSING ENVIRONMENT WITH SYNCHRONIZATION METHODS EMPLOYING A UNIFICATION DATABASE; Ser. No. 60/094,972, filed Jul. 31, 1998, and entitled SYSTEM AND METHODS FOR SYNCHRONIZING TWO OR MORE DATASETS; and Ser. No. 60/094,824, filed Jul. 31, 1998, now abandoned and entitled DATA PROCESS ENVIRONMENT WITH METHODS PROVIDING CONTEMPORANEOUS SYNCHRONIZATION OF TWO OR MORE CLIENTS. The disclosures of the foregoing provisional applications are hereby incorporated by reference in their entirety, including any appendices or attachments thereof, for all purposes. The present application is also related to the following co-pending, commonly owned U.S. patent application, the disclosures of which are hereby incorporated by reference in their entirety, including any appendices or attachments thereof, for all purposes: Ser. No. 09/136,215, filed Aug. 18, 1998, now U.S. Pat. No. 6,295,541, and entitled SYSTEM AND METHODS FOR SYNCHRONIZING TWO OR MORE DATASETS. The present application is also related to the following commonly owned U.S. patent applications, the disclosures of which are hereby incorporated by reference in their entirety, including any appendices or attachments thereof, for all purposes: Ser. No. 08/609,983, filed Feb. 29, 1996, now U.S. Pat. No. 5,845,257, and entitled SYSTEM AND METHODS FOR SCHEDULING AND TRACKING EVENTS ACROSS MULTIPLE TIME ZONES; Ser. No. 09/020,047, filed Feb. 6, 1998, now U.S. Pat. No. 6,216,131, and entitled METHODS FOR MAPPING DATA FIELDS FROM ONE DATA SET TO ANOTHER IN A DATA PROCESSING ENVIRONMENT; and Ser. No. 08/923,612, filed Sep. 4, 1997, and entitled SYSTEM AND METHODS FOR SYNCHRONIZING INFORMATION AMONG DISPARATE DATASETS.
The file of this patent contains a computer program listing appendix submitted on one compact disc, including a duplicate compact disc, in a file named “APPENDIX.TXT”, having a date of creation of Jun. 28, 2004 and a size of 28,672 bytes. The contents of the compact disc are hereby incorporated by reference.
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
The present invention relates generally to management of information or sets of data (i.e., “data sets”) stored on electronic devices and, more particularly, to a system implementing methods for maintaining synchronization of disparate data sets among a variety of such devices, particularly synchronizing three or more devices at a time.
With each passing day, there is ever increasing interest in providing synchronization solutions for connected information appliances. Here, the general environment includes “appliances” in the form of electronic devices such as cellular phones, pagers, hand-held devices (e.g., PalmPilot™ and Windows™ CE devices), as well as desktop computers and the emerging “NC” device (i.e., a “network computer” running, for example, a Java virtual machine or a browser).
As the use of information appliances is ever growing, often users will have their data in more than one device, or in more than one desktop application. Consider, for instance, a user who has his or her appointments on a desktop PC (personal computer) but also has a battery-powered, hand-held device for use in the field. What the user really wants is for the information of each device to remain synchronized with all other devices in a convenient, transparent manner. Still further, the desktop PC is typically connected to a server computer, which stores information for the user. The user would of course like the information on the server computer to participate in the synchronization, so that the server also remains synchronized.
A particular problem exists as to how one integrates disparate information—such as calendaring, scheduling, and contact information—among multiple devices, especially three or more devices. For example, a user might have a PalmPilot (“Pilot”) device, a REX™ device, and a desktop application (e.g., Starfish Sidekick running on a desktop computer). Currently, in order to have all three synchronized, the user must follow a multi-step process. For instance, the user might first synchronize data from the REX™ device to the desktop application, followed by synchronizing data from the desktop application to the Pilot device. The user is not yet done, however. The user must synchronize the Pilot back to the REX™ device, to complete the loop. Description of the design and operation of the REX™ device itself (available as Model REX-3, from Franklin Electronic Publishers of Burlington, N.J.) is provided in commonly-owned U.S. patent application Ser. No. 08/905,463, filed Aug. 4, 1997, and entitled, U
Expectantly, the above point-to-point approach is disadvantageous. First, the approach requires user participation in multiple steps. This is not only time consuming but also error prone. Further, the user is required to purchase at least two products. Existing solutions today are tailored around a device-to-desktop PTM (Personal Information Manager) synchronization, with no product capable of supporting concurrent synchronization of three or more devices. Thus for a user having three or more devices, he or she must purchase two or more separate synchronization products. In essence, existing products to date only provide peer-to-peer synchronization between two points, such as between point A and point B. There is no product providing synchronization from, say, point A to point B to point C, all at the same time. Instead, the user is required to perform the synchronization manually by synchronizing point A to point B, followed by synchronizing point B to point C, then followed by point C back to point A, for completing the loop.
As a related disadvantage, existing systems adopt what is, in essence, an approach having a “hard-coded” link for performing synchronization for a given type of data. Suppose, for example, that a user desires to update his or her synchronization system for now accommodating the synchronization of e-mail data (e.g., Microsoft® Outlook e-mail). With existing synchronization products, the user cannot simply plug in a new driver or module for supporting this new data type. To the point, existing products today do not provide a generic framework into which data type-specific modules may plug into. As a result, these products are inflexible. In the event that the user encounters a new type of data for which synchronization is desired, he or she is required to update all or substantially all of the synchronization product. The user cannot simply plug in a driver or module for supporting synchronization of the new data type. All told, existing synchronization products today assume that users will only perform point-to-point (i.e., two device) synchronization, such as between a hand-held device and a desktop application running on a PC.
This assumption is far removed from reality, however. Users are more likely today to have data among multiple devices, such as among a desktop computer, a server computer (e.g., company network at the user's place of employment), and two or more portable devices (e.g., a laptop computer and a hand-held device). Given the substantial effort required to manually keep three or more devices synchronized, the benefits of synchronization largely remain unrealized for most computer and information application users today.
What is needed is a system providing methods which allows a user of information processing devices to synchronize user information, such as user-supplied contact lists, from one device to any number of other devices, including three or more devices concurrently. The present invention fulfills this and other needs.
The present invention introduces the notion of a reference database: the Grand Unification Database or GUD. 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 (or by specially-designated one of the client data sets) 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. Suppose, for instance, that a user has two synchronization clients: a first data set residing on a desktop computer and a second data set residing on a hand-held device. The GUD introduces a third data set, a middleware database. This third data set provides a super-set of the other two client data sets. Therefore, if the user now includes a third client, such as a server computer storing user information, the synchronization system of the present invention 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.
Internally, the system of the present invention employs “type plug-in” modules, each one for supporting a particular data type. Since the core synchronization engine treats data generically as “blob” objects, type-specific support is provided by the corresponding plug-in module. Each plug-in module is a type-specific module having an embedded record API (application programming interface) that each synchronization client may link to, for providing type-specific interpretation of blob data. For instance, the system may include one type-specific record API for contact information, another for calendar information, and yet another for memo information. In this manner, each client may employ a type-specific API for correctly interpreting and processing particular blob data. The engine, on the other hand, is concerned with correct propagation of data, not interpretation of that data. It therefore treats the data itself generically. In this fashion, the present invention provides a generic framework supporting concurrent synchronization of an arbitrary number of synchronization clients or devices.
Also internally, the synchronization system of the present invention employs an “action queue,” for optimizing the actual synchronization work performed. In contrast to conventional point-to-point (i.e., binary) synchronization systems, the synchronization system of the present invention does not immediately transmit updates or changes as soon as they are detected. Instead, the system determines or tabulates changes, net of all clients, before undertaking the actual work (e.g., record insertion) of synchronizing a particular client. In particular, all actions or tasks which are to be performed for a client by the system during synchronization are queued in the outbound action queue. This allows the system to apply synchronization logic or intelligence to the queue for further improving system performance, such as eliminating any activities which are redundant or moot. For example, if the system receives a request from two different clients to update a given record (i.e., conflict), the system, applying internal synchronization logic, can eliminate propagating the first update, as it is rendered moot by the second update. In this manner, the system can apply a first-level resolution of requests that are conflicting (or complimentary) and, as a result, eliminate those synchronization activities which are redundant or moot.
An exemplary method for synchronizing multiple data sets includes first establishing a data repository for facilitating synchronization of user information maintained among multiple data sets, the data repository storing user information from the data sets. At least one mapping is stored which specifies how user information may be transformed for storage at a given data set. Upon receiving a request for synchronizing at least one data set, the system may, based on user information stored at the data set(s) and based on the mapping, propagate to the data repository from each data set(s) any changes made to the user information, to the extent that such changes can be reconciled with user information already present at the data repository. Further, based on user information stored at said data repository and based on the mapping, the system may propagate to each data set(s) any changes to the user information which have been propagated to the data repository, to the extent that such changes are not present at the data set.
The following description will focus on the presently-preferred embodiment of the present invention, which is operative in an environment typically including desktop computers, server computers, and portable computing devices, occasionally or permanently connected to one another, where synchronization support is desired. The present invention, however, is not limited to any particular environment or device. Instead, those skilled in the art will find that the present invention may be advantageously applied to any environment or application where contemporaneous synchronization among an arbitrary number of devices (i.e., “synchronization clients”), especially three or more devices, is desirable. The description of the exemplary embodiments which follows is, therefore, for the purpose of illustration and not limitation.
System Hardware and Software
The present invention may be embodied on an information processing system such as the system 100 of
In operation, program logic (implementing the methodology described below) is loaded from the storage device or mass storage 107 into the main memory 102, for execution by the processor 101. During operation of the program (logic), the user enters commands through the keyboard 104 and/or pointing device 105 which is typically a mouse, a track ball, or the like. The computer system displays text and/or graphic images and other data on the display device 106, such as a cathode-ray tube or an LCD display. A hard copy of the displayed information, or other information within the system 100, may be obtained from the output device 108 (e.g., a printer). In a preferred embodiment, the computer system 100 includes an IBM PC-compatible personal computer (available from a variety of vendors, including IBM of Armonk, N.Y.) running Windows 9x or Windows NT (available from Microsoft Corporation of Redmond, Washington). In a specific embodiment, the system 100 is an Internet or intranet or other type of network server and receives input from and sends output to a remote user via the interface 109 according to standard techniques and protocols.
System 120 includes a user interface (UI) 160, preferably a Graphical User Interface (GUI), for receiving user commands and data and for producing output to the user. These inputs, in turn, may be acted upon by the system 100 in accordance with instructions from operating system module 140, windows module 150, and/or client application module(s) 145. The UI 160 also serves to display the user prompts and results of operation from the OS 140, windows 150, and application(s) 145, whereupon the user may supply additional inputs or terminate the session. In the preferred embodiment, OS 140 and windows 150 together comprise Microsoft Windows software (e.g., Windows 9x or Windows NT). Although shown conceptually as a separate module, the UI is typically provided by interaction of the application modules with the windows shell and the OS 140.
Of particular interest herein is a synchronization system or “Synchronizer” 200 of the present invention, which implements methodology for contemporaneous synchronization of an arbitrary number of devices or “clients.” Before describing the detailed construction and operation of the Synchronizer 200, it is helpful to first briefly review the basic application of synchronization to everyday computing tasks.
Brief Overview of Synchronization
Many software applications, such as personal productivity applications as Starfish Sidekick® and Lotus® Organizer, have sets of data or “data sets” (e.g., address books and calendars). Consider for instance a user scenario where an account executive needs to coordinate contacts and events with other employees of the XYZ corporation. When traveling, this executive carries a laptop PC with Starfish Sidekick® installed. At home, she and her husband use Lotus® Organizer to plan their family's activities. When on family outings, the account executive carries her PalmPilot™ hand-held organizer. As the foregoing illustrates, a user often needs a means for synchronizing selected information from the data sets his or her applications rely upon. The account executive would not want to schedule a business meeting at the same time as a family event, for example.
Conventionally, the process of synchronizing or reconciling data sets has been a binary process—that is, two logical data sets are synchronized at a time. Any arbitrary synchronization topology will be supported. Here, the system guarantees synchronization stability and the avoidance of undesirable side effects (cascading updates, record duplication, or the like). Data sets do not need to be directly connected but, instead, can be connected via a “store-and-forward” transport, such as electronic mail.
B. Synchronization Design
1. Synchronization Type
Data set synchronization may, for convenience of description, be divided into two types: content-oriented and record-oriented. Content-oriented synchronization correlates data set records based on the values of user-modifiable fields. Value correlation requires semantic (or at least advanced syntactic) processing that the human brain is very good at and computers are not. For example, a record in one data set with a name field valued “Johann S. Bach” and a record in asecond data set with a name field valued “J. S. Bach” could possibly refer to the same real-world person. A human being might arrive at this conclusion by correlating associated data (addresses) or drawing upon external information (e.g., Bach is an unusual name in the U.S.). Creating program logic or code with the ability to make these type of decisions is computationally very expensive.
Record-oriented synchronization correlates data set records by assuming that each record can be uniquely identified throughout its lifetime. This unique identifier is usually implemented as a non-modifiable, hidden field containing a “Record ID”. Record-oriented synchronization algorithms usually require maintaining a mapping from one set of record IDs to another. In a preferred embodiment, the system employs record-oriented synchronization.
Record-oriented synchronization is conceptually simple and may be summarized as follows. In the rules below, A and B refer to two data sets which have a synchronization relationship. The rules are assumed to be symmetrical.
The actual synchronization logic in synchronization systems often needs to make processing decisions based on comparing the time at which past events occurred. For example, it is necessary to know if a record was modified before or after the last synchronization transaction. This requires recording the time of various events. A “timestamp” value may be employed to this purpose. Typically, data sets involved in synchronization support timestamps, or can be supplied with suitable timestamps, in a conventional manner. In conjunction with the usage of timestamps to compare the relative timing of record creation or modification, the clocks on the respective devices may themselves be synchronized.
3. Record Transformations
During synchronization, a synchronization system will typically transform records from one application-usage-schema set to another application-usage-schema set, such as transforming from a Starfish Sidekick® card file for business contacts to a corresponding PalmPilot™ data set. Typically, there is a one-to-one relationship between records in these two data sets, that is, between the source and target data sets. If this is not the case, however, the component of the system that interacts with a non-conforming data set may include logic to handle this non-conformance.
The record transformations themselves are a combination of field mappings and conversions from a source record to a target record. Exemplary types of field mappings include, for instance, the following.
With an understanding of the basic process of synchronizing information or computing devices, the reader may now better appreciate the teachings of the present invention for providing improved methodology for contemporaneous synchronization of an arbitrary number of devices (i.e., synchronization clients). The following description focuses on specific modifications to a synchronization system for implementing the improved synchronization methodology.
Synchronization System Providing Contemporaneous Synchronization of Two or More Clients
A. General Design Considerations
The present invention introduces the notion of a “Grand Unification Database” (GUD)—a central repository or reference database for user data. 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 (or by specially-designated one of the client data sets) 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. Suppose, for instance, that a user has two synchronization clients: a first data set residing on a desktop computer and a second data set residing on a hand-held device. The GUD introduces a third data set, a middleware database. This third data set provides a super-set of the other two client data sets. Therefore, if the user now includes a third client, such as a server computer storing user information (or other information which the user desires synchronization to), the synchronization system of the present invention 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.
Internally, the system of the present invention employs a driver-based architecture providing type-specific “plug-in” modules, each one for supporting a particular data type. Since the core synchronization engine treats data generically as “blob” objects, type-specific support is provided by the corresponding plug-in module. Each plug-in module is a type-specific module having an embedded record API (application programming interface) that each synchronization client may link to, for providing type-specific interpretation of blob data. For instance, the system may include one type-specific record API for contact information, another for calendar information, and yet another for memo information. In this manner, each client may employ a type-specific API for correctly interpreting and processing particular blob data. The engine, on the other hand, is concerned with correct propagation of data, not interpretation of that data. It therefore treats the data itself generically. In this fashion, the present invention provides a generic framework supporting concurrent synchronization of an arbitrary number of synchronization clients or devices.
Also internally, the synchronization system of the present invention employs an “action queue,” for optimizing the actual synchronization work performed. In contrast to conventional point-to-point (i.e., binary) synchronization systems, the synchronization system of the present invention does not immediately transmit updates or changes as soon as they are detected. Instead, the system determines or tabulates changes, net of all clients, before undertaking the actual work (e.g., record insertion) of synchronizing a particular client. In particular, all actions or tasks which are to be performed for a client by the system during synchronization are queued in the outbound action queue. This allows the system to apply synchronization logic or intelligence to the queue for further improving system performance, such as eliminating any activities which are redundant or moot. For example, if the system receives a request from two different clients to update a given record (i.e., conflict), the system, applying internal synchronization logic, can eliminate propagating the first update, as it is rendered moot by the second update. In this manner, the system can apply a first-level resolution of requests that are conflicting or complementary and, as a result, eliminate those synchronization activities which are redundant or moot.
B. Overview of Synchronization System Internal Architecture
The GUD 210, as previously described, serves as a central repository storing record data and mappings which dictate how records are transformed (i.e., from one data set to another). The synchronization engine 230 includes generic logic for managing the GUD 210, including locating and interpreting information in the GUD. Based on the information in the GUD 210 and client requests, the synchronization engine 230 builds the action queue 240, adding or removing specific tasks from the queue as necessary for carrying out synchronization transactions. The action queue 240 itself is an array of task entries; it may grow or shrink, depending on the current number of entries that it stores. In the currently-preferred embodiment, the array is sorted by record ID, that is, according to the record ID of the corresponding record from the GUD. Since entries are sorted by record ID, the task of identifying entries in conflict is simplified.
To communicate with the clients, the synchronization engine 230 employs the client API 220. The client API provides database engine-like functionality. For example, API function calls are provided for moving to records, reading records, and writing records. In the currently-preferred embodiment, clients accessors 221, 223 are “accessor” portions of the synchronization system which, in turn, communicate directly with the “real” clients, such as REX. By implementing its architecture such that all clients communicate commonly through the client API 220, the system 200 provides plug-in capability for supporting new clients.
In order for the system to correctly determine record information in the GUD 210, the synchronization engine 230 communicates with type drivers or modules (e.g., X type 251 and Y type 253) through the type API 250. As previously described, each type, such as calendar, contacts, and the like, is associated with a particular type module. The type API 250 allows the synchronization engine 230 to ask common questions about information stored in the GUD 210. For example, if the synchronization engine 230 needs to determine whether two records are identical, it can request a record comparison operation by the corresponding type module, using the type API 250. In comparison to the client API 220, the type API 250 is comparatively small. By implementing its architecture such that all type-specific requests are communicated commonly through the type API 250, the system 200 provides built-in extensibility. When support is desired for a new type, one need only plug in a new type module. Any client which wants to communicate with that new type now has automatically gained support for that new type. In the currently-preferred embodiment, a type module is unaware of any specific clients which it supports. Clients, on the other hand, typically know what types that each desires to synchronize with.
As also shown, each client accessor can communicate directly with the type modules, using a record API 260. In the currently-preferred embodiment, each type module surfaces its own record API, such as record API 260 for type module 251. The underlying record API is specific for each type. Each accessor communicates with a desired type module, not through the synchronization engine 230, but instead through the exposed record API for the desired type. Thus, in effect, there is a direct communication path between client accessors and type modules. In typical use, the record API is employed by a client accessor to create or write record-specific information. For example, if the client desires to write a “subject” for a contact record, the client, operating through the corresponding client accessor, can invoke the corresponding record API for requesting this service. In response to invocation of the record API, the corresponding type module would service the API call for assisting with creating or editing the underlying record, in the matter requested by the client. The actual work of creating or editing the record is typically performed by the client; however, the corresponding type module returns specific information about the given type, so that the client knows exactly how the record is structured. As a simple example, the record API might return information indicating that a particular record type consists of a structure having four string data members, each being 64 bytes long. Based on such information, the client now knows how to interpret and process that type.
C. Synchronization System Detailed Internal Architecture
Also shown, mapping tables 320 store entries comprising a reference ID 321, a source ID 322, a checksum or integrity value (e.g., CRC) 323, and a last modification (mod) timestamp 324. The reference ID 321 is the same ID as associated with a record in the data table 310. The source ID 322 is the record ID for the record, as it was received from the client. The last modification timestamp 324 establishes when the record was last synchronized through the system. The timestamp (e.g., system time structure) reflects the time on the system clock of the machine which is being synchronized. Optionally, the system stores a comparison value or checksum (e.g., cyclic redundancy checking or CRC) 323, for use with those clients that do not support timestamps. If the checksum is not used, the system stores 0 as its value.
Each table itself is linked to a particular client, through a table ID, with the correspondence being stored as configuration information (which in the currently-preferred environment exists as a higher level than the synchronization engine). In this manner, each one of the mapping tables can be associated with an appropriate client. The end result is that the system maintains a mapping table for each client. Thus, for a given record ID, the system can easily determine (from the above-described reference ID-to-source ID correspondence) where that record maps to for all clients. Consider, for instance, a particular record residing on a REX device. Based on the source ID for that record, the system can determine from the mapping table the corresponding mapping table item for that source ID. Now, the system has sufficient information allowing the particular record to be synchronized, as required by the user. When the data is completely synchronized with all clients, all mapping tables in the system will store that record ID (i.e., the record ID is now common to all tables once the data is completely synchronized with all clients).
2. Action Queue
The action queue stores entries of a particular action type, which are used during synchronization to indicate all actions needed to be performed by the system. In the currently-preferred embodiment, six action types are defined:
The CLIENT action types are used to indicate particular synchronization work which is required to be performed for a particular client. Suppose, for instance, that the synchronization engine determines that the REX client needs to be updated, as a result of actions undertaken by other clients; the REX client need not be currently available (e.g., need not be currently connected to the system). In such a case, the engine can post to the action queue appropriate action entries for indicating the synchronization work which is required to be performed the next time the REX client is connected. In a manner similar to that described above for the GUD, the system can specify an update (CLIENT_UPDATE), add (CLIENT_ADD), and/or delete (CLIENT_DELETE) action, on a per client basis. In the instance of an update or delete action, there already exists a corresponding mapping table item. For an add action, however, the system undertakes as its first action item the task of creating a new mapping table item. Therefore, when the add action is eventually performed, the table item will be created as well. On the other hand, should the action be canceled, the mapping table item will not be created.
Additional pieces of information are tracked by each entry in the action queue: (1) record data, (2) source client, and (3) timestamp. The record data is the actual data (or a reference to the actual data) obtained from the client. In this manner, the actual data may be associated with a particular action. The source client indicates which client the action originated from. This is useful, for instance, during synchronization, so that the system does not attempt to synchronize the client from which the data just arrived. The timestamp stored in an action queue entry is the last modification time of the record from the source client. This is stored for possible use during conflict resolution (which is described in further detail below).
As previously described, the entries in the action queue are sorted by reference ID. In this manner, the system can quickly determine action queue entries which are potentially in conflict. For example, if the queue contains three entries all having the same reference ID, the system must examine those entries for uncovering any conflicts. The actual conflict resolution rules applied in the system are described below.
3. Methodology of System Operation
Conflict resolution requires further explanation. As previously described, the entries in the action queue are sorted by reference ID. In this m a miner, the system can quickly determine action queue entries which are potentially in conflict. For example, if the queue contains three entries all having the same reference ID, the system must examine those entries for uncovering any conflicts. Not only are items in the action queue sorted by a reference ID but, as a second level of ordering, they are also sorted by action. GUD updates are always sorted to the top, thus establishing their priority over other types. Now, the following exemplary conflict resolution rules may be applied:
Rule 0: GUD_UPDATE + <entry(ies) other than GUD_UPDATE> GUD_UPDATE wins; delete all others Rule 1: GUD_UPDATE + GUD_UPDATE GUD_UPDATE with greatest timestamp wins (or display UI) Rule 2: GUD_UPDATE + GUD_DELETE GUD_UPDATE (take data over non-data) Rule 3: CLIENT_UPDATE + CLIENT_UPDATE (from another client) Leave both (i.e., same)
Once conflicts have been resolved the action queue is ready for use. Specifically, at step 404, the system processes all remaining action entries in the action queue. The actions themselves are performed on a transaction-level basis, where a transaction comprises all actions performed on a given record GUD ID. Thereafter, the system may perform cleanup, including closing any open databases and freeing,any initialized data structures (e.g., type).
While the invention is described in some detail with specific reference to a single-preferred embodiment and certain alternatives, there is no intent to limit the invention to that particular embodiment or those specific alternatives.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4769796||Mar 5, 1987||Sep 6, 1988||Levine Alfred B||Time management scheduler|
|US4866611||Jan 29, 1987||Sep 12, 1989||International Business Machines Corporation||Method for automatically reconciling entries on two copies of independently maintained electronic calendars|
|US4881179||Mar 11, 1988||Nov 14, 1989||International Business Machines Corp.||Method for providing information security protocols to an electronic calendar|
|US4977520||Feb 3, 1988||Dec 11, 1990||Ibm Corp.||Method to facilitate a reply to electronic meeting invitation in an interactive multi-terminal system employing electronic calendars|
|US5113380||Aug 24, 1989||May 12, 1992||Levine Alfred B||Multiple option electronic scheduler and rescheduler|
|US5224212||May 1, 1989||Jun 29, 1993||Motorola, Inc.||Asynchronous operation in a database management system|
|US5390320||May 3, 1994||Feb 14, 1995||Grumman Aerospace Corporation||Automatically converting structured analysis tool database outputs into an integrated simulation model via transportable standardized metafile|
|US5392390||Apr 10, 1992||Feb 21, 1995||Intellilink Corp.||Method for mapping, translating, and dynamically reconciling data between disparate computer platforms|
|US5442783||Sep 24, 1993||Aug 15, 1995||Motorola, Inc.||Method and apparatus for transferring data base information|
|US5510981||Oct 28, 1993||Apr 23, 1996||International Business Machines Corporation||Language translation apparatus and method using context-based translation models|
|US5519606||Jan 21, 1992||May 21, 1996||Starfish Software, Inc.||System and methods for appointment reconciliation|
|US5666530||Dec 2, 1992||Sep 9, 1997||Compaq Computer Corporation||System for automatic synchronization of common file between portable computer and host computer via communication channel selected from a plurality of usable channels there between|
|US5666553||Jul 22, 1994||Sep 9, 1997||Puma Technology, Inc.||Method for mapping, translating, and dynamically reconciling data between disparate computer platforms|
|US5684984||Sep 29, 1994||Nov 4, 1997||Apple Computer, Inc.||Synchronization and replication of object databases|
|US5684990 *||Jan 11, 1995||Nov 4, 1997||Puma Technology, Inc.||Synchronization of disparate databases|
|US5701423||Apr 7, 1994||Dec 23, 1997||Puma Technology, Inc.||Method for mapping, translating, and dynamically reconciling data between disparate computer platforms|
|US5706509 *||Apr 28, 1995||Jan 6, 1998||Intel Corporation||Application independent record level synchronization|
|US5708828||May 25, 1995||Jan 13, 1998||Reliant Data Systems||System for converting data from input data environment using first format to output data environment using second format by executing the associations between their fields|
|US5710922||Dec 18, 1995||Jan 20, 1998||Apple Computer, Inc.||Method for synchronizing and archiving information between computer systems|
|US5727202||Oct 18, 1995||Mar 10, 1998||Palm Computing, Inc.||Method and apparatus for synchronizing information on two different computer systems|
|US5729735||Feb 8, 1995||Mar 17, 1998||Meyering; Samuel C.||Remote database file synchronizer|
|US5758150 *||Oct 6, 1995||May 26, 1998||Tele-Communications, Inc.||System and method for database synchronization|
|US5758355||Aug 7, 1996||May 26, 1998||Aurum Software, Inc.||Synchronization of server database with client database using distribution tables|
|US5761667||Aug 7, 1996||Jun 2, 1998||Bmc Software, Inc.||Method of optimizing database organization using sequential unload/load operations|
|US5778346||May 17, 1996||Jul 7, 1998||Starfish Software, Inc.||System and methods for appointment reconcilation|
|US5778389||May 23, 1996||Jul 7, 1998||Electronic Data Systems Corporation||Method and system for synchronizing computer file directories|
|US5813009||Jul 28, 1995||Sep 22, 1998||Univirtual Corp.||Computer based records management system method|
|US5832487||Dec 14, 1996||Nov 3, 1998||Novell, Inc.||Replicated object identification in a partitioned hierarchy|
|US5845293||Mar 26, 1997||Dec 1, 1998||Microsoft Corporation||Method and system of associating, synchronizing and reconciling computer files in an operating system|
|US5848426||Feb 5, 1996||Dec 8, 1998||Metanetics Corporation||Automatic data translation between different business systems|
|US5862325||Sep 27, 1996||Jan 19, 1999||Intermind Corporation||Computer-based communication system and method using metadata defining a control structure|
|US5909570||Jun 9, 1997||Jun 1, 1999||Webber; David R. R.||Template mapping system for data translation|
|US5913214||Aug 8, 1996||Jun 15, 1999||Massachusetts Inst Technology||Data extraction from world wide web pages|
|US5926816 *||Oct 9, 1996||Jul 20, 1999||Oracle Corporation||Database Synchronizer|
|US5978804||Apr 10, 1997||Nov 2, 1999||Dietzman; Gregg R.||Natural products information system|
|US6000000 *||May 4, 1998||Dec 7, 1999||3Com Corporation||Extendible method and apparatus for synchronizing multiple files on two different computer systems|
|US6275831 *||Aug 18, 1998||Aug 14, 2001||Starfish Software, Inc.||Data processing environment with methods providing contemporaneous synchronization of two or more clients|
|US6295541 *||Aug 18, 1998||Sep 25, 2001||Starfish Software, Inc.||System and methods for synchronizing two or more datasets|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7490112 *||Sep 4, 1997||Feb 10, 2009||Intellisync Corporation||System and methods for synchronizing information among disparate datasets|
|US7844965 *||Dec 11, 2003||Nov 30, 2010||International Business Machines Corporation||Providing user applications for accessing data on multiple platforms from a removable storage medium|
|US7899917||Feb 1, 2007||Mar 1, 2011||Microsoft Corporation||Synchronization framework for occasionally connected applications|
|US8024421||Oct 4, 2007||Sep 20, 2011||Welch Allyn, Inc.||Device data sheets and data dictionaries for a dynamic medical object information base|
|US8214566||Jul 23, 2010||Jul 3, 2012||Welch Allyn, Inc.||Configurable health-care equipment apparatus|
|US8402161||Oct 4, 2007||Mar 19, 2013||Welch Allyn, Inc.||Communication of information between a plurality of network elements|
|US8484612||Oct 4, 2007||Jul 9, 2013||Welch Allyn, Inc.||Application generator for a dynamic medical object information base|
|US8499108||Jun 1, 2012||Jul 30, 2013||Welch Allyn, Inc.||Configurable health-care equipment apparatus|
|US8527995 *||Feb 27, 2008||Sep 3, 2013||Microsoft Corporation||Synchronization system for entities maintained by multiple applications|
|US8543540 *||May 9, 2012||Sep 24, 2013||Bertec Corporation||System and method for the merging of databases|
|US8543999||Mar 30, 2006||Sep 24, 2013||Welch Allyn, Inc.||Communication of information between a plurality of network elements|
|US8700569||Feb 23, 2013||Apr 15, 2014||Bertec Corporation||System and method for the merging of databases|
|US8788687||Oct 4, 2007||Jul 22, 2014||Welch Allyn, Inc.||Dynamic medical object information base|
|US8856380||Feb 21, 2013||Oct 7, 2014||Welch Allyn, Inc.||Communication of information between a plurality of network elements|
|US9043278||Apr 14, 2014||May 26, 2015||Bertec Corporation||System and method for the merging of databases|
|US9614932||May 9, 2013||Apr 4, 2017||Microsoft Technology Licensing, Llc||Managing and implementing web application data snapshots|
|US20040006578 *||Nov 27, 2002||Jan 8, 2004||Trsunyeng Yu||System and method for distributed concurrent version management|
|US20040024834 *||Aug 2, 2002||Feb 5, 2004||Andrew Alegria||Sharing personal information between computing devices|
|US20050086199 *||Nov 10, 2004||Apr 21, 2005||Champagne Darryl G.||Transferring records between two databases|
|US20050132369 *||Dec 11, 2003||Jun 16, 2005||International Business Machines Corporation||Universal user roaming method, system and program product|
|US20050138119 *||Dec 23, 2003||Jun 23, 2005||Nokia Corporation||User-location service for ad hoc, peer-to-peer networks|
|US20070150895 *||Dec 6, 2006||Jun 28, 2007||Kurland Aaron S||Methods and apparatus for multi-core processing with dedicated thread management|
|US20080082683 *||Oct 4, 2007||Apr 3, 2008||Welch Allyn, Inc.||Communication of information between a plurality of network elements|
|US20080133699 *||Oct 4, 2007||Jun 5, 2008||Craw Chad E||Device Data Sheets and Data Dictionaries for a Dynamic Medical Object Information Base|
|US20080134133 *||Oct 4, 2007||Jun 5, 2008||Dellostritto James J||Application generator for a dynamic medical object information base|
|US20080140770 *||Oct 4, 2007||Jun 12, 2008||Dellostritto James J||Dynamic medical object information base|
|US20080162728 *||Jan 3, 2007||Jul 3, 2008||Microsoft Corporation||Synchronization protocol for loosely coupled devices|
|US20080189439 *||Feb 1, 2007||Aug 7, 2008||Microsoft Corporation||Synchronization framework for occasionally connected applications|
|US20090055235 *||Aug 23, 2007||Feb 26, 2009||International Business Machines Corporation||system and method for assisted handling of cascading meeting changes|
|US20090217289 *||Feb 27, 2008||Aug 27, 2009||Microsoft Corporation||Synchronization system for entities maintained by multiple applications|
|US20090300169 *||Jun 3, 2008||Dec 3, 2009||Microsoft Corporation||Synchronization throttling based on user activity|
|US20100005448 *||Mar 30, 2006||Jan 7, 2010||Welch Allyn, Inc.||Communication of information between a plurality of network elements|
|US20110022748 *||Jul 23, 2010||Jan 27, 2011||Welch Allyn, Inc.||Configurable health-care equipment apparatus|
|USD632397||Jul 22, 2010||Feb 8, 2011||Welch Allyn, Inc.||Portions of a patient-monitor housing|
|USD635681||Jul 22, 2010||Apr 5, 2011||Welch Allyn, Inc.||Patient-monitor housing|
|USD671222||Jul 22, 2010||Nov 20, 2012||Welch Allyn, Inc.||Module for a patient-monitor or the like|
|U.S. Classification||707/624, 709/220, 707/E17.032, 707/696, 707/999.203, 707/951, 707/999.01, 707/999.201|
|Cooperative Classification||Y10S707/99954, Y10S707/99952, Y10S707/951, G06F17/30575|
|Nov 14, 2005||AS||Assignment|
Owner name: INTELLISYNC CORPORATION, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:STARFISH SOFTWARE, INC.;REEL/FRAME:017006/0624
Effective date: 20051111
Owner name: INTELLISYNC CORPORATION,CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:STARFISH SOFTWARE, INC.;REEL/FRAME:017006/0624
Effective date: 20051111
|Dec 4, 2008||FPAY||Fee payment|
Year of fee payment: 4
|Dec 5, 2012||FPAY||Fee payment|
Year of fee payment: 8
|Feb 10, 2017||REMI||Maintenance fee reminder mailed|