|Publication number||USRE42465 E1|
|Application number||US 11/388,171|
|Publication date||Jun 14, 2011|
|Filing date||Mar 23, 2006|
|Priority date||Jan 17, 2001|
|Also published as||US6711578|
|Publication number||11388171, 388171, US RE42465 E1, US RE42465E1, US-E1-RE42465, USRE42465 E1, USRE42465E1|
|Inventors||Kelly McCaw, Ravi Duggaraju, Cole Goeppinger, Brad Jarvinen|
|Original Assignee||Access Co., Ltd.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (6), Referenced by (3), Classifications (7), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present invention relates to a method for synchronizing multiple copies of one or more databases in a network environment including electronic devices.
As the components required to build a computer system have reduced in size, new categories of computer systems have emerged. One of the more recent categories of computer systems is the portable or “palmtop” computer system, or personal digital assistant (PDA). A palmtop computer system is a computer that is small enough to be held in the hand of a user and is thus “palm-sized.” As a result, palmtops are readily carried about in a briefcase or purse, and some palmtops are compact enough to fit into a person's pocket. By virtue of their size, palmtop computer systems are also lightweight and so are exceptionally portable and convenient.
Further development of PDAs has enabled their use for portable, and even wireless, access to computer networks. The portability and convenience, and, most importantly, the ready ability to synchronize a palmtop device with other computers and data sources, makes such devices ideal for use in networks that serve the workplace as well as the home.
Synchronization is a process that provides the ability to coordinate the databases maintained on a PDA with copies, or versions, of the same and similar databases maintained on a desktop or other computer, or other electronic device, such as a cell phone. Not only is the access to data generally more readily available on a desktop, but desktops or other networked devices have ready access to printers and communication with other devices in the network and the internet on a continuing basis.
Typically, in a network having a portable electronic device, a 2-way synchronization is accomplished with the portable electronic device in a cradle that communicates with the desktop. Synchronization is initiated at the PDA and the user can generally select whether the PDA's database is to be written over (one-way), or the desktop's database is to be written over (one-way the other way), or all modifications on each are to be incorporated in the other (two-way). Typically, the latter synchronization, two-way, is the most useful.
Historically, however, as the number of databases grows, the number of required synchronizations grows exponentially. Each additional copy of each database needs to be synchronized with all the other copies, resulting in a growth of time required on the order of 2n, where n is the number of database copies to be synchronized. This number is repeated for each database maintained.
In a complex network, with a dynamic set of databases, the time devoted to necessary synchronizations grows and could begin to drag down system performance with even a modest number of databases and copies. More importantly, if synchronization takes too long, users will begin to initiate synchronization less frequently than necessary, or worse, avoid it entirely.
What is required, therefore, is a mechanism for rapidly and reliably synchronizing multiple copies of one or more databases in a network environment. The need further exists to allow the expansion of the number of copies of a database that are synchronized without unnecessary limit and without an exponential increase in the amount of time required to accomplish the synchronization process.
The present invention relates to a method for the rapid and reliable synchronization of multiple copies of one or more databases in a network environment. In one embodiment, the method allows the synchronization of an increasing number of copies of multiple databases without an attendant exponential increase in the amount of time required to accomplish the synchronization.
The present invention relates to a method for synchronizing databases in a network environment. Specifically, the present invention pertains to a method of using a set of hierarchical rules to enable an efficient and speedy synchronization between multiple copies of a database. The present invention enables an “n-way” synchronization of databases where “n”, the number of databases synchronized, is essentially any number more than two. The present invention provides rule-based, n-way, synchronization by identifying a focus copy of the database, comparing the data records of the focus copy against the same records in other copies of the database to identify those records that are deleted or modified with respect to the focus copy. A record that is deleted in one database copy but remains unmodified in any other copy is deleted in all database copies. If a record has been both deleted in one copy and modified in another, the invention transmits the modified record across all databases copies and a deleted record is treated like a modified record. The database is cycled through so that all database copies are eventually processed like the focus. On subsequent cycles, records that have already been processed by a focus database are skipped. By performing this process, the method enabled by the present invention allows the speedy maintenance of multiple, synchronized, databases without the inadvertent loss of any data record.
An embodiment of the present invention operates in a system having multiple copies of a database, and includes a method of synchronizing the multiple copies of the database comprising the steps of: a) identifying a focus copy of the multiple copies of the database; b) comparing records of the focus copy against records having a same identification tag but contained in other copies of the database to identify deleted and modified records with respect to the focus copy; c) removing from all the copies of the database a record indicated by step b) as being deleted by any copy of the database, provided the record was not also modified by any other copy of the database; d) with respect to any modified record indicated by step b), writing the modified record to all the copies of the database that do not already contain the modified record; and e) selecting a new focus copy of the copies of the database and repeating steps b)-e) until all the copies of the database have been processed as a focus copy.
Embodiments include the above and those wherein step b) only processes previously unprocessed records of the focus copy. Embodiments further include the above and those wherein step b) also identifies new records of the focus copy and wherein further step d) applies to the new records. Embodiments also include the above and those wherein step d) applies to a record that has been modified in one copy but deleted in another copy of the database.
Embodiments include the above and those wherein step d) applies to a record that has been modified in one copy but deleted in two other copies of the database. Embodiments include the above and those wherein, with respect to a record that has been modified in more than one copy, step d) writes the modifications of the record to all copies of the database that do not already contain the modifications.
The operation of this invention can be best visualized by reference to the drawings.
Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings. While the invention will be described in conjunction with these specific embodiments, it will be understood that they are not intended to limit the invention to these embodiments. On the contrary, the invention is intended to cover alternatives, modifications and equivalents, which may be included within the spirit and scope of the invention as defined by the appended claims. Furthermore, in the following detailed description of the present invention, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be obvious to one of ordinary skill in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to unnecessarily obscure aspects of the present invention.
Some portions of the detailed descriptions that follow are presented in terms of procedures, logic blocks, processing, and other symbolic representations of operations on data bits within a computer memory. These descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. A procedure, logic block, process, etc., is here, and generally, conceived to be a self-consistent sequence of steps or instructions leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated in a computer system. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, bytes, values, elements, symbols, characters, terms, numbers, or the like.
It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussions, it is appreciated that throughout the present invention, discussions utilizing terms such as “setting,” “storing,” “scanning,” “receiving,” “sending,” “disregarding,” “entering,” or similar terms, refer to the action and processes of a computer system or similar intelligent electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
The embodiment of the present invention discussed herein relates to a method of accomplishing, and a system for enabling, the synchronization of multiple versions of one or more databases resident on different devices in a network environment. This embodiment refers to a hardwired cradle connected or wirelessly connected palmtop device or PDA synchronizing to any number of databases coupled to the same network. The network can be a local area network (LAN) or a wide area network (WAN) or merely a cradle connected to a stand-alone desktop. Other embodiments of the present invention, though, may be implemented as synchronizations between laptops, between desktops, or any combination of each.
In this discussion of some embodiments of the present invention, the terms “palmtop”, “palm device”, “PDA”, “handheld device”, and “handheld computer” are used more or less interchangeably. In each case, they refer to a class of small, user-portable, computing devices that are capable of coupling with a host device, such as a desktop or laptop computer, and with which the devices can participate in a synchronization between databases. The term “synchronization” refers to the act of making all synchronized versions of a database agree in content.
The operation of this embodiment of the present invention and the environment in which its operates may be best understood by reference to the figures.
A typical palmtop device is illustrated in
Further illustration of these devices is given in
Infrared communication mechanism 513 (e.g., an infrared emitter and detector device) is for sending and receiving information from other similarly equipped devices or, in this embodiment, communicating with a host device in a network (see
To illustrate the implementation of an RF link in an embodiment of the present invention, a signal (e.g., radio) receiver/transmitter device 514 is also shown in
With reference still to
The typical connection between a portable computing device and it associated host device is by a cradle connected to a serial port on the host device.
Referring again to
With or without the connection to the network, a synchronization initiated by either portable device 102 or host device 107 is normally limited to the database copies on each. Since there are two versions of each synchronized database, one each resident on host device 107 and portable device 102, this is known as a “2-way” synchronization.
When the number of versions, or copies, of any database being synchronized is more than two, the technical aspects of synchronization increase significantly. The letter “n” is used mathematically to indicate an integer of undetermined size. In synchronization parlance, it is used to indicate any integer larger than two and it refers to the number of versions of a database being synchronized. Thus a more-than-two-way synchronization is known as an “n-way” synchronization. Referring again to
Two-way synchronizations are, in most embodiments, relatively simple processes, wherein data records within a database are compared and modified as necessary. At the initialization of synchronization, each data record is checked for modification, addition or deletion which is indicated by a flag associated with each record in the database. Flags are set only if no synchronization has taken place since the action to the record. Each data record is compared with modified records in the database version in either device being written to the other device. An added data record is also written -to the other device. A record deleted from one device is deleted from the other on verification.
Each record in each device is checked for a change since last synchronization. The device initiating the synchronization is the resident device of the initial “focus” version of the database. This two-way synchronization is illustrated by block diagram of
Portable computer system 720 is the PDA and computer system 700 is the host device. The enabling of file sharing between the two devices is accomplished in file sharing manager 702 and conduit 740. During synchronization between portable computer system 720 and database 710, delta records 730a and 730b are passed through conduit 740 between database 326 and a database resident on portable computer system 720 under control of the file sharing manager 702. Delta records 730a and 730b represent changes (including additions) that occurred on either portable computer system 720 or on computer system 700. After synchronization, these two databases will contain the same information. Namely, records updated on portable computer system 720 are reflected in database 710 and vice versa. The synchronization process (including the file sharing manager) is described in U.S. Pat. No. 6,006,274 by Hawkins et al., issued Dec. 21, 1999, assigned to the assignee of the present invention and incorporated herein by reference. Synchronization is also described in U.S. Pat. No. 5,727,202 by Kucala, issued Mar. 10, 1998, assigned to the assignee of the present invention and incorporated herein by reference, and also in U.S. Pat. No. 5,832,489 by Kucala, issued Nov. 3, 1998, assigned to the assignee of the present invention and incorporated herein by reference.
In the embodiment of the present invention discussed here uses parts of the synchronization system above. As the number of databases increases the number of operations involved in a synchronization increases exponentially. Approximately 2n synchronization operations, as described in the paragraph previous, are required for “n” database versions. A synchronization in a network such as that shown in
Rule-Based n-Way Synchronization reduces the number of iterative operations required with an n-way synchronization. It does so by invoking a set of hierarchical rules (See Table of Rules,
The remainder of this discussion focuses on the operation of a rule-based n-way synchronization as it is implemented in one embodiment of the present invention. The discussion herein is not meant to exclude any other of the many different combinations of processes that could still be included within the framework of the present invention, but the detailed discussion of this specific embodiment will serve to illuminate the concepts under which the present invention operates.
To outline the rule set and the operations associated with each,
Situation 810c is the same as situation 810a, except that same record identification that was deleted is also modified in another database copy. In this case, the action taken is that the modified record is added to all database copies that do not already contain the modification and the deletion is ignored. Situation 810d is an identical deletion of the same record from two or more database copies. The action to be taken is the same as for situation 810a. In situation 810e, a record of the focus database copy is modified. The action to be taken is that this modified record is added in each other copy not already having the modification. The situation 810f is that a record of the focus database copy is modified by two copies. In this case, each modified record is added to each database copy (using the record's same identification tag) that does not already have the modification. In situation 810g, a record was added to the focus database copy. This situation is treated just as a modification, e.g., the action of situation 810e is performed.
At situation 810h, a record of the focus database is modified, but this same record is modified in two other database copies. The action taken is the same as for situation 810f. In situation 810i, a record of the focus database copy is modified and this same record is also modified twice again in other database copies. The action to be taken is that each modified record is added in each other copy not already having the modification. Lastly, in situation 810j, a record of the focus database is modified and an identical modification is made in another copy. The action taken is that a single modification is added to each other database copy that does not contain the record.
After database copy “DB1” is the focus, next database copy “DB2” is made the focus, and these rules of
The operation of an n-way synchronization under the rule structure can be visualized by reference to the flowcharts in
After a focus database is selected, process 1000 on
If other modifications have occurred to the same record ID in another database, then all the modifications are compared, 1050. If the modifications are identical, then the focus database record is written to all databases, 1080. If the modifications are not identical, then each modification is written to each copy. The focus database record modification is written to the existing record in the other databases and a new record ID is established that reflects each new modification to the same record found in the other databases, 1110. The process then looks to the next record in the list of changes in the focus database, 1120.
If the record modification flag is a deletion, the record ID is checked in all other databases for modification, 1100. If it has been modified in another database, the modified record is written to all, 1080, and none are deleted. If the record has not been modified in another database, it is deleted in all copies, 1120. Once each modified record in the focus database is accounted for, 1130, the process moves on to the next database, 1140/930. Each database in the loop is taken through the same process until no unmodified records remain, 940, then the synchronization is ended, 950.
With the process outlined in this embodiment of the present invention, only changed data records are considered. This avoids redundancies of checking and rechecking the modification status of each data record with comparison with each database. Also, when a new database is processed as the focus database, any record that was previously processed by another focus database is skipped, thereby preventing a geometric growth in processing time.
The foregoing discussion of one embodiment of the present invention demonstrates a method for rapid and reliable synchronization of multiple copies, or versions, of one or more databases in a network environment. The method discussed, while not limiting of all possible embodiments of the invention, provides the synchronization of an upwardly increasable number of copies of multiple databases without an attendant exponential increase in the amount of time and resources required to accomplish the synchronization.
The foregoing descriptions of specific embodiments of the present invention have been presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed, and obviously many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the Claims appended hereto and their equivalents.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5680609 *||Jun 10, 1994||Oct 21, 1997||Intel Corporation||Method and apparatus for synchronizing file deletions in computer systems|
|US5884325 *||Oct 9, 1996||Mar 16, 1999||Oracle Corporation||System for synchronizing shared data between computers|
|US6141663 *||Mar 18, 1994||Oct 31, 2000||Unimax Systems Corporation||Automatic external data synchronization method|
|US6401104 *||Jul 3, 1999||Jun 4, 2002||Starfish Software, Inc.||System and methods for synchronizing datasets using cooperation among multiple synchronization engines|
|US6549921 *||Aug 1, 2000||Apr 15, 2003||Emc Corporation||Method and apparatus for performing point in time backup operation in a computer system|
|US7096228 *||Mar 27, 2002||Aug 22, 2006||Microsoft Corporation||Method and system for managing data records on a computer network|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8799215 *||Jul 19, 2010||Aug 5, 2014||Accenture Global Services Limited||Data processing method, system, and computer program product|
|US9230004||Jun 25, 2014||Jan 5, 2016||Accenture Global Services Limited||Data processing method, system, and computer program product|
|US20110016086 *||Jul 19, 2010||Jan 20, 2011||Accenture Global Services Gmbh||Data processing method, system, and computer program product|
|U.S. Classification||707/610, 707/692, 707/999.101|
|Cooperative Classification||Y10S707/99942, G06F17/30286|
|Sep 15, 2011||FPAY||Fee payment|
Year of fee payment: 8
|Oct 30, 2015||REMI||Maintenance fee reminder mailed|
|Mar 23, 2016||LAPS||Lapse for failure to pay maintenance fees|