Method and apparatus for reconciling data between devices

FIELD OF THE INVENTION

0001This invention relates to reconciling data between devices and more particularly to using wireless data transfers between devices to reconcile databases maintained on more than one device.

BACKGROUND OF THE INVENTION

0002Many computer based systems include databases of information relating to, for example, mailing lists, calendars, etc. Often times users of these databases maintain them on two or more computers. Currently, most of these databases require a user to manually input initial data in all the maintained databases and to manual input new in formation to each database for any given addition or change. Requiring manual input from the user makes these systems difficult to use and prone to errors.

0003Automatic reconciliation systems help minimize the manual input errors. These systems, typically, operate by establishing a direct communication link between each communication device, and running a reconciliation procedure under user control. For example, U.S. Patent 5,701,423, issued to Crozier on December 23, 1997, entitled METHOD FOR MAPPING, TRANSLATING, AND DYNAMICALLY RECONCILING DATA PLATFORMS, the disclosure of which is expressly incorporated herein by reference, discloses using an application program and connection between a handheld computer and a desktop computer to reconcile databases between the two disparate computing systems. Similarly, U.S. Patent 5,832,489, issued to Kucala on November 3, 1998, entitled METHOD AND APPARATUS FOR SYNCHRONIZING INFORMATION ON TWO DIFFERENT COMPUTER SYSTEMS, the disclosure of which is expressly incorporated herein by reference, discloses establishing a communication link between a palmtop computer and a desk top computer having databases with similar formats. Finally, U.S. Patent 5,790,974, issued to Tognazzini on August 4, 1998, entitled PORTABLE CALENDARING DEVICE HAVING PERCEPTUAL AGENT MANAGING CALENDAR ENTRIES, the disclosure of which is expressly incorporated herein by reference, discloses using a wireless communication link to synchronize data between a portable calendar system and an office calendar system. Therefore, a system for reconciling databases on two or more disparate computing systems that does not require either a direct communication link or user involvement is desirable.

SUMMARY OF THE INVENTION

0004To attain the advantages and in accordance with the purpose of the invention, as embodied and broadly described herein, a method for reconciling databases using a central server is provided. The central server receives new information input into a database and updates the database stored at the central server. The central server determines whether at least one remote computing device requires the new information and transfers the new information to the remote computing device.

0005The present invention also provides for a central server capable of reconciling databases between at least two remote computing devices. The central server has a memory for storing the database, a device identifier list, and an update list. A receiver of the central server is adapted to receive a communication file containing new information from one of the remote computing devices. The central server has a central processing unit that converts the communication file into a format compatible with the with central database and updates the central database. The central server also has a transmitter adapted to establish a communication link with the at least two remote computing devices.

0006The present invention also provides for a computer program product for reconciling databases. The computer program product includes a computer usable medium having computer readable code embodied therein for reconciling the databases. The computer usable medium having a receiving module configured to receive new information at the a central server. An updating module is configured to update a database stored at the central server. A determining module determines whether at least one remote computing device requires the received new information and a transmitting module is configured to transmit the new information to that computing device.

0007The foregoing and other features, utilities and advantages of the invention will be apparent from the following more particular description of a preferred embodiment of the invention as illustrated in the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWING

0008The objects, features, and advantages of the present invention will be apparent from the following detailed description of the preferred embodiment of the invention with reference to the following drawings: <ul id="ul0001" list-style="none" compact="compact"><li>Fig. 1 is a functional block diagram of a plurality of devices in accordance with the present invention;</li><li>Fig. 2 is a functional block diagram of central server 102 of Fig. 1;</li><li>Fig. 3 is a block diagram of a file structure in memory 220 of Fig. 2 in accordance with the present invention;</li><li>Fig. 4, is a functional block diagram of remote computing device 106 of Fig. 1;</li><li>Fig. 5, is a block diagram of a file structure in memory 420 of Fig. 4 in accordance with the present invention;</li><li>Fig. 6 is a flow chart describing inputting information to a database at a remote computing device in accordance with the present invention;</li><li>Fig. 7 is a flow chart describing inputting information received from a remote computing device to a database at a central server;</li><li>Fig. 8 is a flow chart describing transmitting information from a central server to a remote computing device; and</li><li>Fig. 9 is a flow chart describing the operation of a remote computing device after it has received information from a central server.</li></ul>

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

0009While the invention has been particularly shown and described with reference to a preferred embodiment thereof, it will be understood by those skilled in the art that various other changes in the form and details may be made without departing from the spirit and scope of the invention.

0010The present invention discloses methods and apparatus for automatically reconciling databases between various computing devices. Fig. 1 shows a communication system 100 having a central server 102 and a plurality of remote computing devices 104, 106, 108, and 110. For example, computing device 104 could be a desktop computer, computing device 106 could be a laptop computer, computing device 108 could be a palmtop computer, and computing device 110 could be a cellular phone. Communication links 112 connect central server 102 with remote computing devices104, 106, 108, and 110. Thus, system 100 comprises a hub and spoke arrangement.

0011In one preferred embodiment of the present invention, communication links 112 are wireless communication links and central server 102 comprises an Internet server accessible through a wireless gateway. In this embodiment, communication between remote computing devices 104, 106, 108, and 110 and central server 102 follow the Wireless Application Protocol ("WAP") although any protocol is possible.

0012Fig. 2 shows server 102 in more detail. Central server 102 includes a central processing unit (CPU) 210, a memory 220, a wireless transmitter 230, and a wireless receiver 240. CPU 210 has resonant programs running for carrying out the operations described, herein. CPU 210, storage unit 220, wireless transmitter 230 and wireless receiver 240 are connected by bus (not specifically shown) using standard bus protocols, which are know in the art. Although represented as individual sections, many of the components in central server 102 could be combined. For example, wireless transmitter 230 and wireless receiver 240 could be combined into one transceiver.

0013Fig. 3 shows one possible file structure 300 for memory 220. File structure 300 includes a user directory list 310 having a list of users directories 312, 314, 316, etc. User directory 314, for example, contains a database directory list 320 of databases user 314 maintains reconciled over several computing devices and a device list 330 of devices user 314 owns and contain databases to be reconciled. Directory list 320 identifies databases 322, 324, 326, etc. of user 314 that user 314 wants central server 102 to reconcile with devices in device list 330. In this example, device list 330 identifies remote computing devices 104, 106, 108, and 110 (Fig. 1), but any number or types of devices could be identified. For each device 104, 106, 108 etc., device list 330 contains flags indicative of whether the device is powered at the moment. Database directory 324 contains a database 340 having information and records. Additionally, memory 320 has an update list 350 for the database 340. Device list 330 maintains a link to update list 350 containing flags indicative of whether the device database has been updated since the last time data was received by the database 340.

0014Fig. 4 shows remote computing device 106 in more detail. Remote computing device 106 includes a central processing unit (CPU) 410, a memory 420, a wireless transmitter 430, and a wireless receiver 440. CPU 410 has resonant programs running for carrying out the operations described, herein. CPU 410, storage unit 420, wireless transmitter 430 and wireless receiver 440 are connected by bus (not specifically shown) using standard bus protocols, which are know in the art. Although represented as individual sections, many of the components in central server 102 could be combined. For example, wireless transmitter 430 and wireless receiver 440 could be combined into one transceiver. As shown in Fig. 5, memory 420 contains a database directory list 510 having a list of databases 512, 514, 516, etc. Each database, for example database 512, contains a database 520 containing the records that the user has central processor 102 maintain reconciled between multiple computing devices, <i>i.e.,</i> the shared databases. Notice that device 106 can maintain databases separately from the shared databases.

0015Fig. 6 shows a flow chart 600 describing operation of remote device 106 when the user inputs new information into one of the shared databases, for example database 520. First, a user of database 520 enters new information, step 602. CPU 410 of remote computing device 106 identifies the new information, step 604, and prepares a communication file capable for transmission to central server 102, step 606. The communication file includes a user device identifier, which is unique for each device, a database identifier for database 520, and the new information. The device identifier includes a portion that is unique for each user of central server 102 but common to that users' devices as well as a portion that is unique for each different remote computing device of that user. CPU 410 then transfers the communication file to wireless transmitter 430, step 608. Wireless transmitter 430, following standard procedures of WAP or another communication protocol, establishes communication link 112 with central server 102, step 610, and transfers the communication file to central server 102, step 612. After the file is transferred, wireless transmitter 430 terminates communication link 112, step 614. As one of ordinary skill in the art would now recognize, it would be possible to program central server 102 to transmit a successful or unsuccessful file transfer signal back to remote computing device 106. Remote computing device 106 would then terminate communication link 112 on a successful signal and retransfer the file on an unsuccessful signal.

0016Fig. 7 shows a flow chart 700 describing operation of central server 102 to receive the communication file from remote computing device 106. First, wireless receiver 240 receives the communication file transmitted over communication link 112, step 702. Wireless receiver 240 transfers the communication file to CPU 210, step 704. CPU 210 uses the device identifier and database identifier to access the proper user directory and database file, step 706. CPU 210 then coverts the new information in the communication file into a format compatible with the identified database and updates the database file and a new information file (not shown), which maintains the new information until all device have been reconciled, the database identifier and the unique device identifier, step 708. Next, CPU 210 accesses update list 350, associated with the updated database 340 and gets update flags, step 710. In particular, update flag associated with remote computing device 106, which is the device that transmitted the information, is set to indicate that it is currently updated with the database in memory 220 of central server 102. The update flags associated with other remote computing devices, in this case devices 104, 108, and 110, are set to indicate that databases stored in the memory of those remote devices need updating.

0017Fig. 8 shows a flow chart 800 describing operation of central server 102 to update the databases stored in remote computing device 104. The procedures central server 102 uses to update remote computing devices 106, 108, and 110 are substantially identical to the procedures described in flow chart 800. First, CPU 210 monitors update list 350 for the need updating indication, step 802. CPU 210 then access memory 220 to retrieve the new information file stored in memory 220, step 804, and the device identifiers in device list 330 of those devices in need of updating, step 806. In this example, remote computing devices 104, 108, and 110 would need updating. CPU 210 then prepares a communication file, step 807, for transfer to remote computing device 104. The communication file includes the new information and the database identifier. The communication file is then transferred to wireless transmitter 230, step 807a. The unique device identifier indicating the user and the device is used by wireless transmitter 230 to establish a communication link 112 with remote computing device 104, step 808. Wireless transmitter 230 then transmits the communication file to remote computing device 104, step 810. CPU 210 then updates the flag in update list 350 for device 104 to indicate that the file has been updated. After transmitting the communication file, wireless transmitter 230 would terminate communication link 112, step 812. If additional remote computing devices are in need of the new information, control would return back to step 807 to update the next remote computing device. Finally, CPU 210 checks update list 350 and if all devices are indicated as updated, CPU 210 deletes the new information file, step 814. As one of ordinary skill in the art would now recognize, it would be possible to program remote computing device 104 to transmit a successful or unsuccessful file transfer signal back to central server 102. Central server 102 would then terminate communication link 112 on a successful signal and retransfer the file on an unsuccessful signal.

0018Fig. 9 is a flow chart 900 describing operation of remote computing device 104 upon reception of the communication file from central server 102. First, a wireless receiver in remote computing device 104 receives the communication file, step 902. Next, the wireless receiver transfers the file to a CPU in remote computing device 104, step 904. The CPU converts the communication file into a format compatible with the identified database and updates the indicated database file, step 906.

0019One advantage of using central server 102 is that when one or more remote computing devices are not powered, central server 102 can save new information until that device is powered. Central server 102 would store the information until the remote computing device is powered and then transfer the new information to the remote computing device. Also, while central server 102 is described using update list 350, it would be possible to use backup directories as described in U.S. Patent 5,832,489.

0020It will be apparent to those skilled in the art that various modifications and variations can be made in the method of the present invention and in construction of the preferred embodiments without departing from the scope or spirit of the invention. Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples considered as exemplary only, with the scope of protection being indicated by the following claims.