Data processing: database and file management or data structures – Database design – Data structure types
Reexamination Certificate
2000-06-09
2003-04-15
Metjahic, Safet (Department: 2171)
Data processing: database and file management or data structures
Database design
Data structure types
C707S793000
Reexamination Certificate
active
06549902
ABSTRACT:
FIELD OF THE INVENTION
The present invention relates to a database managing device for creating the same contents between parties which are ready to communicate, and particularly to a database managing device capable of reducing the volume of data transmitted or processed during a synchronous process, and the invention also relates to a recording medium recording a program of such a database managing device.
BACKGROUND OF THE INVENTION
Conventionally, information processing devices have been in wide use, and it is not rare in recent years for one individual to own a plurality of information processing devices, for example, such as a high-performance information processing device like a desk-top personal computer and a portable information processing device like a portable information terminal. When personal information, for example, such as schedules and address book are to be managed by these plurality of information processing devices, there is need to maintain the same contents of data in any of databases provided in these information processing devices. Thus, in the case of managing, for example, personal information between a personal computer and a portable information terminal, a master database is managed by the personal computer and the data of the master database are copied to the database (portable database) of the portable information processing device, thus carrying the personal information.
In this manner, in managing the same data between a plurality of database managing devices, when data is changed in one database managing device, it is required to update the database of all the other database managing devices. Here, if each database managing device is in communications all the time, the change in data is immediately reflected in each one of these devices when the updated database managing device informs the other database managing devices that the data has been changed. However, it is not always the case that each database managing device is in communications all the time with the other devices, for example, as in the case where the database managing device is a portable information terminal. In such a case, a change in data in one device is not reflected in the databases of the other database managing devices at the time when the change is made. Thus, in order to maintain the same database, it is required to carry out a process for creating the same contents in database between parties at the time when communications are engaged between the database managing devices; namely, a synchronous process is required.
In the case of the above example, when data is changed in the portable information terminal, a synchronous process is carried out at the time when the portable information terminal is brought back to home or office, in which time data become the same between the portable database of the portable information terminal and the master database of the computer.
As an example of a conventional synchronous process, upload and download are known. Specifically, when data are changed in the personal computer, the contents of the master database are copied to the portable information terminal (download). On the other hand, when data are changed in the portable information terminal, the contents of the portable database are copied to the personal computer (upload).
Another conventional example is a synchronous process employing a sum of sets. In this synchronous process, the contents of both databases are compared at the time when communications are engaged between the two database managing devices, and a sum of sets, which contains all the information added to each database is created as a new database. Thereafter, the database thus created is stored in the both database managing devices.
For example, when the both databases initially contain data “A”, and data “B” is added to one database managing device X, and data “C” is added to the other database managing device Y, the database managing device X sends its contents “A+B” to the database managing device Y. The database managing device Y creates a sum of sets “A+B+C” from the data “A+B” received and its contents “A+C” and stores the sum of sets as a database. The database managing device Y then sends the contents of the database “A+B+C” back to the database managing device X. As a result, the contents of the database of the database managing device X are updated to “A+B+C”, which are the same as that of the database managing device Y.
However, the conventional database managing device carrying out the described synchronous process has the problem of extremely large data volume (communications volume) transmitted between the database managing devices in the synchronous process and extremely large data volume computed in each database managing device.
Specifically, in download and upload, all the contents of one database are transmitted to the other database managing device regardless of the number of data updated. For example, in the case of a database having the data of 1000 items, the data of all the 1000 items are sent even when only one item is changed. As a result, the communications volume transmitted between the database managing devices is increased. Further, the contents of the database of the database managing device of the receiving end are replaced with the database of the sending end, and thus a change in data on the receiving end is lost.
Also, in the synchronous process employing a sum of sets, in order to create a sum of sets, a database of one party is sent to the other database, and the sum of sets created is sent back as a new database. Thus, in this synchronous process, all the contents of the database are required to be sent back and forth between the database managing devices, which further increases the communications volume in the synchronous process.
Further, in the case where data is deleted only in one of the devices, the data remain in the other device. Thus, the data is included again in a new database and it is not deleted. As a result, the memory space required for storing the database is increased, and the communications volume in the synchronous process is further increased.
In order to solve these problems, another example of the synchronous process is disclosed, for example, in Japanese Unexamined Patent Publication No. 6693/1997 (Tokukaihei 9-6693) (Published Date: Jan. 10, 1997), in which update information indicative of a change or no change in data is given to each data contained in the database. Specifically, each database managing device stores, per each data stored in the database, ID information for identifying the data and update information indicative of no change/correction/addition/deletion, and when data is changed, the update information corresponding to this data is updated. In the synchronous process, ID information and update information of all data are transferred between database managing devices. The database managing device of the receiving end searches through its database data associating with the data changed in the device of the sending end based on the ID information received and compares the update information of the both parties. When data is changed only in one party, unchanged data is replaced with the data changed. When data are changed in the both parties, the data of one party is added to the database of the other party, and vice versa. In this way, in the case where data are not changed in any of the database managing devices, sending of data can be omitted, thus reducing the communications volume in the synchronous process.
However, even with the above arrangement, it is still required to transmit the ID information and update information with respect to the entire database. Further, when change is made in the both parties, the data changed in one party needs to be added to the database of the other party. Thus, the communications volume in the synchronous process is still not reduced to a sufficient level. Further, when data are changed in the both parties, the number of data in the databases is in
Camlinh Nguyen
Metjahic Safet
Nixon & Vanderhye P.C.
Sharp Kabushiki Kaisha
LandOfFree
Database managing device does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Database managing device, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Database managing device will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3049693