|Publication number||US5684989 A|
|Application number||US 08/485,119|
|Publication date||Nov 4, 1997|
|Filing date||Jun 7, 1995|
|Priority date||May 27, 1991|
|Publication number||08485119, 485119, US 5684989 A, US 5684989A, US-A-5684989, US5684989 A, US5684989A|
|Original Assignee||Fujitsu Limited|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (13), Referenced by (30), Classifications (16), Legal Events (5)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application is a continuation of application Ser. No. 07/888,754, filed May 27, 1992, now abandoned.
1. Field of the Invention
The present invention relates to the latest managing system of terminal DB for managing terminal DB in the latest condition. An electrical power company, for example, uses the latest map of the same division (update period is about the one to seven days/section) in the plural departments such as planning, installation and maintenance department. Moreover, the division and element of the map to be used are respectively different in each department. In the case of making reference or updating map by scattering map DBs to a plurality of terminals, it is generally required to maintain the terminal map DB in the latest condition and it is also required to effectively maintain the latest condition.
2. Description of the Related Art
In the case of utilizing, after updating a map in a certain terminal, the same map in the other terminal, the latest map data is transferred and maintenance of terminal map DB consisting of setup (update) of map DB are conducted, each time when utilization is required, and thereafter planning has been conducted by utilizing the terminal map.
Maintenance of such terminal map DB has a problem that a longer waiting time is generated until planning can be done at the terminal using the latest map, because the latest map data must be transferred, for use from the host, to a terminal through a line and stored in a terminal map DB and a longer time is also required for line processing and I/O processing. Moreover, there has been a problem that the latest update terminal does not require any maintenance of terminal map DB and does not require any waiting time for utilization, namely the waiting time is fluctuated depending on the terminals. In addition, it has also been a problem that since terminals are arranged for each department, unused maps are generated in a certain terminal and therefore if maintenance is conducted for all terminals, ineffective processing is generated.
It is an object of the present invention to curtail the waiting time for using maps at a terminal by previously defining, in a distribution defining file, map numbers to be stored in the terminal map DB, and defining the terminal map DB to the latest one through transfer of the latest map data by deleting the undefined map data and informing the defined map numbers and version numbers to the host at the predetermined time or depending on instruction from the host.
The above-mentioned and other objects and features of the present invention will become more apparent from the following description when read in conjunction with the accompanying drawings. However, the drawings and descriptions are merely illustrative in nature and not restrictive.
FIG. 1 is a structural diagram of an embodiment of the present invention.
FIG. 2 is a flowchart for explaining operations of the present invention.
A means for solving the problems will be explained with reference to FIG. 1. In FIG. 1, a terminal 1 updates facilities on the map. A distribution defining file 15 is provided to previously defining the map numbers to be stored in the terminal map DB 17.
A terminal map managing DB 16 is provided to store the version numbers corresponding to map numbers. A terminal map DB 17 is provided to store map data corresponding to map numbers.
A host 2 controllably manages map data.
As shown in FIG. 1, the present invention connects a plurality of terminals 1 to a host 2 through a line, deletes map data, when it is stored in the terminal map DB 17, of the map numbers other than those defined in the distribution defining file 15 at the predetermined time (for example, night time, early morning or lunch break, etc.) or corresponding to an instruction from the host 2, also obtains, by the retrieving, the current version number of the defined map number from the terminal map managing DB 16, informs the map number and this terminal version number to the host 2 through the line and transfers the latest map data and host version number, when the terminal version number is older than the host version number, to the terminal 1 through the line to update the terminal map DB 17 and terminal map managing DB 16 to the latest ones.
Therefore, a map number to be stored in the terminal map DB 17 is previously defined in the distribution defining file 15, a map data not defined is deleted and the defined map number and the current terminal version number are informed to the host 2 at the predetermined time or depending on an instruction from the host in order to update the terminal map DB 17 to the latest one by transfer of the latest map data, thereby curtailing the waiting time at the time of utilizing a map at a terminal 1.
Structure and operation of an embodiment of the present invention will be sequentially explained in detail with reference to FIG. 1 and FIG. 2.
In FIG. 1, a terminal 1 is used for updating facilities on the map comprising elements 11 to 14.
A processing drive 11 drives the processings such as deletion of unwanted map data stored in the terminal map DB 17 of the terminal 1 or update of data to the latest map data at the predetermined time (for example, night time, early morning or lunch break, etc.) or depending on the drive signal from the host 2. (Refer to the processing flowchart of the processing drive 11 of FIG. 2.)
A delete section 12 deletes unwanted map data stored in the terminal map DB 17, namely the map data of map number not defined in the distribution defining file 15.
A map update section 13 updates map data of map number defined in the distribution defining file 15 as the latest map data to the terminal map DB 17. (Refer to the processing flowchart of the map update section 13 of FIG. 2.)
A communication section 14 exchanges data with a communication section 23 of the host 2 through the transmission line.
The distribution defining file 15 previously defines and stores map numbers of map data to be stored (resided) in the terminal map DB 17.
The terminal map managing DB 16 stores and manages version number corresponding to map number of map data to be stored in the terminal map DB 17.
The terminal map DB 17 stores map data corresponding to map number. The host 2 controls and uniquely manages map data sent from a plurality of terminals 1 connected through the line.
A version number check section 21 transfers, when the terminal 1 requests to use a map, the latest map data and host version number, in the case where a terminal version number is older than the host version number, corresponding to the message concerning the map number and terminal version number of the map to be used and updates the map data of the terminal 1 to the latest map data.
Corresponding to the operations that the terminal 1 is driven by the processing drive 11 and the map number defined in the distribution defining file 15 and the terminal version number extracted by retrieving the terminal map managing DB 16 are informed, a map distributing section 22 transfers the latest map data and host version number to the terminal 1 when the terminal version number is older than the host version number and updates the map data of map number defined in the distribution defining file 15 which may be always used by the terminal 1 to the latest map data.
The communication section 23 exchanges data with the communication section 14 of the terminal 1 through the transmission line.
The host map managing DB 24 manages the latest map data by storing the version number corresponding to the map number.
The host map DB 25 manages the map data corresponding to the map number.
A display 3 displays maps for removing and newly installing the facilities.
Next, in accordance with the sequence indicated in the flowchart of FIG. 2, operations for deleting stored map data which have lower probability of use and updating the map data which have higher probability of use to the latest map data when the terminal 1 is idle (for example, night time, early morning, lunch break, etc.) or corresponding to the drive instruction from the host 2 in the structure of FIG. 1 will be explained in detail.
In FIG. 2, the processing drive section 11 waits for the time of automatic power supply control in the step S1. In this case, the distribution start time and distribution processing procedures are previously registered for the automatic power supply control in the terminal 1 and the distributing processes of the step S5 and the successive steps are started at the distribution start time after waiting for the distribution start time set for the night time, early morning or lunch bread where the registered terminal 1 is idle.
In the step S2, the drive signal is appearing from the host 2 after the waiting time. Namely, the processing drive of host 2 waits for an event, for example, an event of update of the host map DB. When these events are generated, the drive signal is informed to the processing drive 11 of the terminal 1 after a certain waiting time in the step S4. When the start signal is informed, the processing drive 11 starts the distribution processing after the step S5.
In the step S5, the deleting section 12 is in the terminal map managing DB 16 to obtain the map numbers not defined in the distribution defining file 15 and set such map numbers to the map numbers to be deleted.
In the step S6, records of the terminal map managing DB 16 and terminal map DB 17 are deleted using the deleting map numbers as the keys. Thereby, the map data of map number which is usually unused and not defined in the distribution defining file 15 is deleted, capacity size of terminal map DB 17 is increased and ineffective use of memory source of the terminal 1 can be eliminated.
In the step S7, the map update section 13 retrieves and extract the version number of the terminal map managing DB 16 with a map number of the distribution defining file 15. The map number and terminal version number are informed to the map distributing section 22 of the host 2 through the transmission line.
In the step S8, the map distributing section 22 retrieves and extracts the version number (host version number) of the host map managing DB 24 using a map number as the key.
In the step S9, whether the terminal version number is older than the host version number or not is discriminated. When it is older (map data stored in the terminal 1 is older than the map data stored in the host 2 and is not the latest map data), the map data of the host map DB 25 is retrieved and extracted using the map number as the key in the step S10 and the host version number and map data are informed to the terminal 1 through the transmission line. On the other hand, when it is not older (the map data stored in the terminal 1 is the latest data), the host version number is informed to the terminal 1 through the transmission line.
In the step S12, the host version number informed from the host 2 is compared with the terminal version number. When the terminal version number is not older than the host version number, if the last record is not detected in the step S14, the processings of step S12 and the successive steps are repeated and if the last record is detected, processing is completed. On the other hand, when the terminal version number is older than the host version number, the host version number is stored in the terminal map managing DB 16 using the map number as the key in the step S13, the map data transferred to the terminal map DB 17 from the host 2 is stored therein and is updated to the latest data. When the last record is not detected in the step S14, the processings of step S12 and successive steps are repeated and when the last record is detected, the processing is completed.
With the processings mentioned above, the map numbers to be resided in the distribution defining file 15 are defined previously and stored, the map data of the map numbers other than those defined in the distribution defining file 15 are deleted from the terminal map managing DB 15, terminal map DB 16 at the idle time or corresponding to reception of the drive signal from the host 2, the defined map numbers and the terminal version numbers thereof are informed to the host 2, the latest map data is transferred when the terminal version number is older than the host version number and is not the latest one to update the terminal map managing DB 16 and terminal map DB 17 to the latest version number and map data. When processing is to be done in the terminal 1 using the map data, the time for down-loading the latest map data from the host 2 is no longer required, waiting time can be eliminated and quick processing can be realized by deleting the data which is not required to be resided among the map data stored in the relevant terminal 1 and updating such map data into the latest map data.
As explained above, the present invention employs a structure that a map number to be stored in the terminal map DB 17 is previously defined in the distribution defining file 15, undefined map data is deleted and defined map number and the current terminal version number are informed to the host 2 at the predetermined time or corresponding to the instruction from the host and the latest map data is received from the host 2 to update the terminal map DB 17 and terminal map managing DB 16 to the latest ones. Thereby, the waiting time for utilizing the map at the terminal 1 (the time required for down-loading the latest map data from the host 2 and executing I/O process to such map data) can be eliminated.
While the invention has been illustrated and described in great detail in the drawings and foregoing description, it will be recognized that many changes and modifications will occur to those skilled in the art. It is therefore intended, by the appended claims to cover any such changes and modifications as fall within the true spirit and scope of the invention.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US3670310 *||Sep 16, 1970||Jun 13, 1972||Infodata Systems Inc||Method for information storage and retrieval|
|US4635189 *||Mar 1, 1984||Jan 6, 1987||Measurex Corporation||Real-time distributed data-base management system|
|US4751635 *||Apr 16, 1986||Jun 14, 1988||Bell Communications Research, Inc.||Distributed management support system for software managers|
|US4833597 *||Jan 27, 1987||May 23, 1989||Hitachi, Ltd.||Dictionary/directory management method in database system|
|US5012405 *||Aug 3, 1989||Apr 30, 1991||Hitachi, Ltd.||File management system for permitting user access to files in a distributed file system based on linkage relation information|
|US5081608 *||Apr 18, 1989||Jan 14, 1992||Matsushita Electric Industrial Co., Ltd.||Apparatus for processing record-structured data by inserting replacement data of arbitrary length into selected data fields|
|US5086402 *||May 30, 1990||Feb 4, 1992||Simware, Inc.||Method for high speed data transfer|
|US5241639 *||Jan 19, 1989||Aug 31, 1993||Digital Equipment Corporation||Method for updating data from a cache address location to main memory and maintaining the cache address in registration memory|
|US5257365 *||Mar 16, 1990||Oct 26, 1993||Powers Frederick A||Database system with multi-dimensional summary search tree nodes for reducing the necessity to access records|
|US5261094 *||Apr 8, 1991||Nov 9, 1993||International Business Machines Corporation||Asynchronous replication of data changes by distributed update requests|
|US5375207 *||Nov 22, 1991||Dec 20, 1994||Hewlett-Packard Company||Remote processing of a plurality of commands during a session between a first computer and a host computer|
|US5495610 *||Jul 13, 1995||Feb 27, 1996||Seer Technologies, Inc.||Software distribution system to build and distribute a software release|
|US5539905 *||Apr 27, 1995||Jul 23, 1996||Fujitsu Limited||Map/facility exclusion control system for updating facility on a map|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US5737731 *||Aug 5, 1996||Apr 7, 1998||Motorola, Inc.||Method for rapid determination of an assigned region associated with a location on the earth|
|US5893113 *||Apr 25, 1996||Apr 6, 1999||Navigation Technologies Corporation||Update transactions and method and programming for use thereof for incrementally updating a geographic database|
|US6038568 *||Mar 22, 1999||Mar 14, 2000||Navigation Technologies Corporation||Transaction method and programming for incrementally updating a geographic database|
|US6075467 *||Aug 14, 1998||Jun 13, 2000||Toyota Jidosha Kabushiki Kaisha||Map data selection supporting device, and map data processing system and map data processing device including the same|
|US6094654 *||Jun 24, 1998||Jul 25, 2000||International Business Machines Corporation||Data management system for file and database management|
|US6185552 *||Mar 19, 1998||Feb 6, 2001||3Com Corporation||Method and apparatus using a binary search engine for searching and maintaining a distributed data structure|
|US6289276 *||Aug 10, 2000||Sep 11, 2001||Navigation Technologies Corporation||System and method for distributing information for storage media|
|US6317753||Mar 13, 2000||Nov 13, 2001||Navigation Technologies Corporation||Update system and method for geographic databases|
|US6487559||Sep 25, 2001||Nov 26, 2002||Navigation Technologies Corporation||Method for updating a geographic database|
|US6516327||Sep 24, 1999||Feb 4, 2003||International Business Machines Corporation||System and method for synchronizing data in multiple databases|
|US6728633 *||Dec 21, 2001||Apr 27, 2004||Mitsubishi Denki Kabushiki Kaisha||Map data processing apparatus and method of the same|
|US6931422 *||Nov 12, 1999||Aug 16, 2005||International Business Machines Corporation||Enhanced backup and recovery methodology|
|US7222141||Dec 20, 2002||May 22, 2007||International Business Machine Corporation||System and method for synchronizing data in multiple databases|
|US7403851||Sep 30, 2004||Jul 22, 2008||Navteq North America, Llc||Method of operating a navigation system to report effects of updated portions of a geographic database|
|US7890255 *||Jul 16, 2004||Feb 15, 2011||Mitsubishi Denki Kabushiki Kaisha||Navigation apparatus|
|US8249801||Mar 31, 2008||Aug 21, 2012||Aisin Aw Co., Ltd||Navigation device and map data updating method thereof|
|US8468127 *||Jun 18, 2013||Research In Motion Limited||System and method for synchronizing data records between multiple databases|
|US8521430||Dec 28, 2007||Aug 27, 2013||Navteq B.V.||Managing differences between geographic database versions|
|US8626442||Sep 3, 2010||Jan 7, 2014||Mitsubishi Denki Kabushiki Kaisha||Navigation apparatus|
|US9347778||Jul 24, 2013||May 24, 2016||Here Global B.V.||Managing differences between geographic database versions|
|US20020166006 *||May 3, 2001||Nov 7, 2002||Williams Robert Alan||Multiple buffers for removing unwanted header information from received data packets|
|US20030131025 *||Dec 20, 2002||Jul 10, 2003||Zondervan Quinton Yves||System and method for synchronizing data in multiple databases|
|US20050049784 *||Jul 16, 2004||Mar 3, 2005||Mitsubishi Denki Kabushiki Kaisha||Map information processing apparatus, map update information storage medium, map update information data structure, map update information creating system, and map information updating system|
|US20060074547 *||Sep 30, 2004||Apr 6, 2006||Kaufman Michael L||Method of operating a navigation system to report effects of updated portions of a geographic database|
|US20090171558 *||Dec 28, 2007||Jul 2, 2009||Navteq North America, Llc||Managing Differences Between Geographic Database Versions|
|US20100274472 *||Mar 31, 2008||Oct 28, 2010||Aisin Aw Co., Ltd.||Navigation device and map data updating method thereof|
|US20100332128 *||Sep 3, 2010||Dec 30, 2010||Mitsubishi Denki Kabushiki Kaisha||Navigation apparatus|
|US20120130953 *||Jan 30, 2012||May 24, 2012||Research In Motion Limited||System and method for synchronizing data records between multiple databases|
|WO2000026813A2 *||Nov 1, 1999||May 11, 2000||Teracom Ab||Method for updating local map displaying databases|
|WO2000026813A3 *||Nov 1, 1999||Aug 3, 2000||Frederik Carlsson||Method for updating local map displaying databases|
|U.S. Classification||707/695, 710/19, 710/33, 707/E17.005, 707/999.201, 707/812, 707/999.008, 707/999.104|
|International Classification||G06F17/30, G06F13/00, G06F12/00|
|Cooperative Classification||Y10S707/99952, G06F17/30309, Y10S707/99938, Y10S707/99945|
|Apr 12, 2001||FPAY||Fee payment|
Year of fee payment: 4
|Apr 6, 2005||FPAY||Fee payment|
Year of fee payment: 8
|May 11, 2009||REMI||Maintenance fee reminder mailed|
|Nov 4, 2009||LAPS||Lapse for failure to pay maintenance fees|
|Dec 22, 2009||FP||Expired due to failure to pay maintenance fee|
Effective date: 20091104