JP2014240920A - Map update device, map update system, and method for managing map update - Google Patents

Abstract

PROBLEM TO BE SOLVED: To obtain a map update device for determining a block to be updated without retaining all sets of versions in all sets of adjacent blocks up to the present.SOLUTION: When an update range in which a map is updated is designated, an update block extraction unit extracts, with respect to the update range, a block belonging to an update group having a portion common to the update range and belonging to an old version update group referable from the update group having the portion common to the update range as a block to be updated, and determines, with respect to the block to be updated, a latest version among the update group or the old update group to which the block to be updated belongs as an update version of the block to be updated.

Description

  The present invention is updated at any time using a map update device and a map update device for transmitting update data of map data to a car navigation device using map data, a mobile computer, a personal computer, or a terminal device such as a mobile phone. The present invention relates to a map update system for displaying a map on a terminal device and a map update management method.

  In the navigation and map display search software by the car navigation device, it is necessary to update the map data to be used as new as possible so that the situation shown in the map data matches the current actual situation. Since the map data is updated, for example, once a month, the map data of the terminal device that performs the car navigation or the map system is updated with the updated data reflecting the updated data. In updating such map data, instead of updating all the map data in the range such as the whole country or the world held by the terminal, the update data to be distributed is updated by partially updating only the data used mainly. A technique for saving the amount and the update processing time in the car navigation device is disclosed (Patent Document 1).

  In Patent Document 1, in a map that is converted into data for each section into which the map is divided, the map data that is held for the section that has been updated in the designated update area is updated, and the adjacent section that is adjacent to the updated section is also updated. However, in order to ensure the consistency of the road network connection between the sections, the update by the latest or past update data is additionally performed. For example, a section that has been updated may be updated as necessary even outside the update area, and updates may be executed using past update data even in sections that are not currently updated inside or outside the update area. The partition to be updated is determined by the server, and necessary update data is transmitted to the terminal device. Update of only necessary parts limited to the vicinity of the update area is realized without causing inconsistency in the road network.

  Further, in a map information system that downloads and uses server map data from time to time using a computer network, the updated map data of the server is used as the downloaded pre-updated map data held in the cache of the terminal device. A technique used instead is disclosed (Patent Document 2). In Patent Document 2, when a new drawing portion is required for new display or scrolling of a map, for example, the update time of map data held in the cache and the map of the server are used by using the cache management function of the web browser. The latest map data is used in comparison with the data update time. Alternatively, when map data is downloaded, if new and updated map data exists, the version number is notified from the server to the browser, and thereafter the browser downloads the map data identified by the URL specifying the version. To be configured.

JP 2011-158339 A Special table 2007-531004 gazette

  However, in the map updating apparatus as shown in Patent Document 1, in order to match the connection of the road network with the adjacent section, the road network element extending over the adjacent section is changed, and both are updated together. Otherwise, the set of both versions at the time when matching cannot be obtained is retained for all adjacent partition sets from the past to the present. In the determination of matching with an adjacent partition, it is determined whether the versions of both partitions are consistent with reference to the version set of the partition set. Otherwise, it is added as an update partition sequentially so that the adjacent partition is updated to a consistent version. In order to operate in this way, there is a problem that all sets of versions between adjacent sections must be retained for all adjacent section sets from the past to the present.

  Further, when determining the update section for the terminal device, the map update apparatus, which is the server, stores the current version information of all sections in order to refer to the version information of the necessary sections for the map held by the terminal device. Or the map update device must be notified from the terminal device. Furthermore, in order to determine the update partition, it is necessary to sequentially update the adjacent partition every time an update request is made while referring to the version of the update partition and the adjacent partition and the version set data of the adjacent partition set. There has been a problem that it has to be determined whether or not.

  Further, the map information system as shown in Patent Document 2 is configured to obtain the latest version of a map for a newly required section. In some operation, for example, pan operation (map scroll operation), necessary sections of the display area are sequentially downloaded. For this reason, when a map of a section adjacent to a downloaded map is newly downloaded, if the map is updated at that time, the map of the adjacent section becomes a new version. For this reason, an old version map and a new version map are adjacent to each other, and there is a problem in that there is a risk that an excess or deficiency or displacement of a figure occurs at the boundary portion. As described above, there has been a problem that an inconsistency occurs in a map in an operation such as a pan operation.

The present invention has been made to solve the above-described problems, and is a map update device that determines a partition to be updated without retaining all version pairs in all adjacent partition pairs up to the present. The purpose is to obtain. Furthermore, to obtain a map update apparatus that determines a section to be updated without holding version information of all sections of the map that the terminal device currently has in the map update apparatus as a server or transmitting the version information from the terminal apparatus to the map update apparatus. It is aimed. Furthermore, it aims at obtaining the map update apparatus which determines an update area, without searching an adjacent area.
Another object of the present invention is to obtain a map information system that executes a pan operation so that inconsistency does not occur at the boundary between sections on the map system.

  The map updating apparatus according to the present invention includes a storage unit that stores map data for each version at the time of update, update management data for managing a section where the map data has been updated, and a section that needs to be updated simultaneously. An area classification unit for grouping into update groups, and a partition common to the update group, and an old version update group that is an update group at the time of updating the map data of a version older than the version of the update group can be referred to When the area structuring unit for generating the update management data structured as described above and the update range for updating the map are designated, based on the update management data, the update section, and the update for each update section An update section extracting unit that determines a version, and an update version that refers to the map data and determines the section to be updated for each section An update data generation unit for generating update data for updating to the network, and the update range from the terminal device via the communication network, and update status data indicating the update status of the map data of the terminal device in an update group A communication unit that receives and transmits the update data to the terminal device, and the update section extraction unit is configured to update the update range with respect to the update range when an update range for updating the map is designated. A partition belonging to the update group having a common part and the old version update group that can be referred to from the update group having a common part with the update range is extracted as the partition to be updated, and for the partition to be updated, The update bar of the partition for updating the latest version of the update group or the old update group to which the partition to be updated belongs. It is intended to determine as ® down.

According to the present invention, partitions that need to be updated at the same time are grouped into regions as update groups, and structured as update management data so that update groups in previous version updates that have a common partition can be referenced. As a result, when the range for updating the map is specified, the section to be updated by the update management data and its updated version can be easily identified.
In addition, by dividing the areas that need to be updated at the same time into update areas and grouping them into update management data, it is possible to easily identify the sections to be updated by the update management data when a range for updating the map is specified. This is a remarkable effect.

  In addition, the map update device divides the sections that need to be updated at the same time into areas as update groups, and is structured as update management data so that the update groups in previous version updates that have a common section can be referenced. The update range specified by the terminal devices connected by the communication network can be easily identified by the update management data and the update version thereof and can be transmitted to the terminal device as update data. There is an effect.

In addition, the map updating device divides the sections that need to be updated at the same time into areas as update groups, and easily updates the sections to be updated with the update management data for the update range specified by the terminal devices connected by the communication network. The present invention has an unprecedented remarkable effect that the information can be specified and transmitted to the terminal device.
In addition, by dividing the areas that need to be updated at the same time into areas as update groups, and structured as update management data so that update groups in previous version updates that have a common partition can be referenced, This presents an unprecedented remarkable effect that a section to be updated by update management data and its update version can be easily specified when a range for updating the map is designated.

It is a block diagram which shows the structure of the map update apparatus which concerns on Embodiment 1 of this invention. It is a block diagram which shows the structure of the terminal device which concerns on Embodiment 1 of this invention. It is a figure which shows an example of the update of the division of map data in a map update apparatus. It is a figure explaining the example which specifies the update group which should transmit update data with respect to a terminal device among update groups in a map update apparatus, when update is requested | required from a terminal device. It is a figure which shows an example in case the update group of the version before it which has a common part with the update group of the newest version exists. It is a figure explaining the division to update about the map data of the state shown in FIG. It is a figure which shows an example of the link from the new update group to the update group of the version before it used by the area | region structure part. It is a figure explaining the update group set which needs an update when there exists an update group in the update range. FIG. 9 is a diagram for explaining a section that requires an update determined by the updated section extraction unit based on FIG. 8 and its version. It is a figure which shows the example of the version of the map data of a terminal device. It is a figure which shows an example of the data of the new root update group for terminal devices which an update data generation part produces | generates. It is a flowchart of operation | movement of the map update apparatus at the time of giving a new version map by update of map data. It is a figure which shows the example of the data of the update group which the area | region classification part put together. It is a flowchart which shows operation | movement of the map update apparatus in the case of producing required update data and transmitting to a terminal device with respect to the request | requirement from a terminal device. It is an example of the data showing the update range. It is an example of the update status data which the terminal device terminal device has memorized. It is a flowchart which shows operation | movement of a terminal device. It is a flowchart which shows operation | movement of the map update apparatus which concerns on Embodiment 2 of this invention. In the map update apparatus which concerns on Embodiment 2, it is a figure explaining an example of the extraction method of the update group which requires an update. It is a block diagram which shows the structure of the terminal device which concerns on Embodiment 3 of this invention. It is a block diagram which shows the structure of the map update apparatus 1 which concerns on Embodiment 3 of this invention. It is a block diagram which shows the structure of the terminal device which concerns on Embodiment 3 of this invention. It is a figure which shows an example of a division buffer and a clipping range. It is a figure explaining an example of the update of a partition buffer. It is a flowchart which shows operation | movement of the terminal device of Embodiment 3 of this invention. It is a figure which shows an example of the candidate division data which a map update apparatus transmits. It is a flowchart which shows operation | movement of the map update apparatus which concerns on Embodiment 3 of this invention. It is a figure which shows an example of the update management data of the map update apparatus of Embodiment 3. 14 is a flowchart illustrating an operation for obtaining candidate partition data in response to a request from a terminal device in the map update device according to the third embodiment.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
Embodiment 1 FIG.
FIG. 1 is a block diagram showing a configuration of a map update device 1 according to Embodiment 1 of the present invention.
As shown in FIG. 1, the map update device 1 includes a storage unit 4, a region segmentation unit 5, a region structuring unit 6, an update segment extraction unit 7, an update data generation unit 8, and a communication unit 9. Prepare. The storage unit 4 stores map data 2 and update management data 3.
The storage unit 4 is a hard disk or memory that is a storage unit, and the map data 2 stored in the storage unit 4 is map information. The update management data 3 stored in the storage unit 4 is data in which update sections of the map are grouped and expressed in a hierarchical graph.
The area dividing unit 5 is an area dividing means for grouping sections that need to be updated at the same time as update groups.

The area structuring unit 6 has the update group grouped by the area partitioning unit 5 and a common partition with the update group, and the update group (old version older than that of the update group) prior to the update group. It is a region structuring means that makes the update management data 3 structured so that a group) can be referred to.
The update partition extraction unit 7 is an update partition extraction unit that determines a partition that needs to be updated from the update management data and an update version for each partition that needs to be updated when a range for updating the map is designated.
The update data generation unit 8 is update data generation means for generating update data for updating a partition that needs to be updated to an update version determined for each partition.
The communication unit 9 is a communication unit that performs communication with the terminal device 11 such as a car navigation device.

FIG. 2 is a block diagram showing a configuration of terminal apparatus 11 according to Embodiment 1 of the present invention.
The terminal device 11 is, for example, a car navigation device or a personal computer. The terminal device 11 is connected to the map update device 1 via a communication network 10 such as a computer network, a wired communication network, or a wireless communication circuit to constitute a map update system. Yes.
As illustrated in FIG. 2, the terminal device 11 includes a storage unit 14, an update range designation unit 15, a communication unit 16, a map update unit 17, and a map display unit 18. The storage unit 14 stores map data 12 and update status data 13.

The storage unit 14 is a hard disk or memory that is a storage unit, and the map data 12 stored in the storage unit 14 is map information. The update status data 13 stored in the storage unit 14 is update status data indicating the update status of the map data 12.
The update range designation unit 15 is an update range designation unit for designating a range for updating the map.
The communication unit 16 is a communication unit that performs communication with the map update device 1.
The map update unit 17 updates the map data 12 held in the storage unit 14 with the map update data transmitted from the map update device 1.
The map display unit 18 displays a map based on the map data 12 updated by the map update unit 17 on a display unit such as a display. The display unit may be provided in the terminal device 11 or may be provided with a display device outside the terminal device 11.

  In the use of car navigation, map display, route search, and the like often limit the range of a map to be used, such as an area where a user lives. By updating partly in such a range, it is possible to save the communication amount of update data and the processing related to the update. In the first embodiment, the terminal device 11 designates an update range of the map and transmits it to the map update device 1, and the map update device 1 reliably determines the section for the update range received from the terminal device 11. Update to the latest map, and determine and update the sections that need to be updated around the update range and the updated version so that the road network and the features to be drawn are aligned with the map. An embodiment in which update data of each section is transmitted to the terminal device 11 and the terminal device 11 updates the map data 12 held by the update data received from the map update device 1 will be described.

The map data is assumed to be divided and held for each section divided by region, and update data is also generated for each section. The update data is data indicating a new version of map data or a difference for changing an old version of map data to a new version.
A section is also called a tile. For example, an area obtained by dividing coordinate values according to latitude and longitude at equal intervals, or an area obtained by dividing a map as an image in plane rectangular coordinates by a certain pixel size. is there. In general, a plurality of levels of detail are set by adopting a plurality of division widths or scales, but the operation at a single level will be described below. In a plurality of levels, the map is updated by repeating the operation for each level.

Here, the update group will be described in detail first.
In the map update device 1, the update section in which the map data 2 has been updated is divided into groups by the region partition unit 5, and the region structuring unit 6 updates the update group grouped by the region partition unit 5 to the previous update, That is, the update management data 3 structured so that an update group (old version update group) in an old version can be referred to is generated.
FIG. 3 is a diagram illustrating an example of the update of the section of the map data 2 in the map update device 1.
As shown in FIG. 3, it is assumed that the map data 2 is divided into sections 19 and a road 20 that spans sections A and B is newly established by updating from version V0 to version V1. In this case, when only the section A is updated, the road 20 is not connected by the section A of the version V1 and the section B of the version V0. In this way, when there are additions, deletions, and position changes across the section 19, if both sections are not updated at the same time, the excess or deficiency of the features or the displacement of the coordinates (hereinafter referred to as inconsistency) will occur. ) Occurs.

Therefore, the area classification unit 5 collects adjacent sections that need to be updated at the same time as areas, and sets this as an update group 22. The same update group 22 is created by installing roads and features (adding data), removing (deleting data), moving (changing data coordinate values), changing attributes, etc. across adjacent sections. This is the case. Further, more simply, it is an adjacent section where both of the features have been changed in the update to the same version. When the feature is changed as in the former, since the adjacent sections change simultaneously, the latter belongs to the same update group 22 as well. Here, a single changed partition whose alignment with the surroundings does not become a problem is also set as one update group 22, and a changed partition always belongs to one update group 22.
If the partition is updated in the update group 22 unit, it can be matched with the surrounding partitions, so that no mismatch occurs during the update.

FIG. 4 illustrates an example in which, in a case where an update is requested from the terminal device 11, the map updating device 1 specifies the update group 24 that should transmit update data to the terminal device 11 among the update groups 22. FIG.
When an update range 23 is designated from the terminal device 11 and an update is requested, the map update device 1 extracts an update group 24 that includes all or part of the update range 23 from the update group 22 and updates the update group 24. A section 25 constituting the group 24 is set as an update section. Even without searching for an adjacent section, the update section 25 can be determined by the intersection determination between the update group 22 and the update range 23. In this way, the update group 24 having the common area with the update range 23 is extracted from the update group 22, and this partition is updated.

For example, when the map data is updated periodically, the area structuring unit 6 generates update management data 3 that hierarchically manages the update groups 22 of the respective update versions. For example, the update group 22 of the map data 2 in the latest version can be updated consistently with the map data 2 in the immediately preceding version. If the partition of the update group 22 of the latest version has a common part with the update group 22 of the previous version, that is, overlaps, the update group 22 of the latest version must be updated unless the update group of the previous version is updated. Updates may cause inconsistencies with surrounding compartments. This will be described with reference to FIG.
FIG. 5 is a diagram illustrating an example in which an update group 22 of an earlier version having a common part with the update group 22 of the latest version exists. In FIG. 5, the version V0 is assumed to be the initial state, the latest version Vm, and the previous version Vn.

In the update group 26 of the previous version Vn, the feature 27 such as a road is changed. In addition, the feature 30 is changed in the update group 29 of the new version Vm having the partition 28 in common with the update group 26. As shown in the figure, when the update of the feature 27 extends to the common section 28 and other sections, the update group 26 of the previous version Vn is updated in the update group 29 of the new version Vm. Otherwise, the feature 27 is in a state where only the portion included in the section 28 is updated, and is not updated in other sections. For this reason, inconsistency arises between the adjacent divisions. Therefore, the update group of the previous version to be superposed must be updated in accordance with the update of the new update group 29 even if it is not in the update range 23. Of course, the common partition is updated to a new version.
FIG. 6 is a diagram for explaining sections to be updated for the map data in the state shown in FIG. The update range 23 in FIG. 6 is an update range designated by the terminal device 11.
When updating the update group 29 of the new version Vm that falls within the update range 23, the map update device 1 also updates the sections belonging to the update group 26 of the previous version.

  Therefore, when the area classification unit 5 updates the map data 2, that is, when updating to the latest version Vm, the area division unit 5 classifies the updated section into the update group 22, and the area structuring unit 6 In order to easily obtain the update group 26 of Vn, it is determined whether each update group has a common partition with the update group 26 of the previous version Vn, and if it has a common partition, the update group 29 of the new version Vm is determined. Then, link data for referring to the update group 26 of the previous version Vn is obtained. This means that the data for identifying the update group 29 of the new version Vm and the update group 26 of the previous version Vn to be superimposed, for example, a pair of identification numbers for identifying the update group is converted into data, and the information can be easily obtained. To get. By doing in this way, the update groups 29 and 26 as shown in FIG. 6 can be specified easily.

  FIG. 7 is a diagram illustrating an example of a link from a new update group to an update group of an earlier version, which is used by the area structuring unit 6. In FIG. 7, version V0 is in an initial state, and thereafter, updated to versions V1, V2, and V3, and only changed sections are represented by hatching or the like. The j-th update group of version Vi, i = 1, 2, 3 is represented as Gij, and the update group of the previous version having a common partition is represented by an arrow.

  As shown in FIG. 7, the link 31 from the new update group 22 to the update group 22 of the previous version constitutes a graph having the update group 22 as a node 32, and this is referred to as an update graph 33. Note that data representing this graph structure may be held independently from the data of the update group 22. Since the update of the map data 2 is executed sequentially, the links between update groups are spread over several layers. Therefore, when updating an update group, in order to prevent inconsistency between partitions, all the update groups 22 to which links 31 are extended are updated from the update group 22 to be updated. By following the above, it is possible to easily identify the partition and its version that need to be updated.

  Note that an update group of an earlier version (old version update group) traced by a link from a certain update group 22 is referred to as a lower update group of the update group 22. Data of the update group 22 managed by the update graph 33 is update management data 3. The update management data 3 is stored in the storage unit 4.

Next, an operation in which the update partition extraction unit 7 extracts a partition to be updated with respect to the specified update range 23 from the update group 22 managed by the update graph 33 as described in FIG. 7 will be described.
When the communication unit 9 of the map update device 1 receives the update range 23 specified by the terminal device 11 from the terminal device 11 via the communication unit 16, that is, when the update range 23 for updating the map is specified, the update section The extraction unit 7 searches the update graph 33 and extracts an update group 22 having a common part with the update range 23. Specifically, a partition belonging to an update group 22 having a common part with the update range 23 and a lower update group that can be referred to from the update group 22 having a common part with the update range 23 is extracted as the partition to be updated. When the update range 23 is fixed and the map data 12 of the terminal device 11 is updated every time the map data 2 is updated, the update is performed only from the update group of the latest version. Here, each update group 22 may be configured to be managed by a multi-dimensional data management structure such as a kd tree so that the search for the update group 22 that falls within the update range 23 can be executed efficiently.

Next, a description will be given of determination of a partition that needs to be updated by the update partition extraction unit 7 and its version when there is an update group 22 in the update range 23.
FIG. 8 is a diagram for explaining an update group set that needs to be updated when there is an update group 22 in the update range 23.
In FIG. 8, the set of update groups 22 that need to be updated is represented by an update group set S34. S is a set of the update group 22 in the update range 23 and the update group 22 traced by the link 31 from the update group 22 in the update range 23. When one update group is selected, the selected update group 22 and the update group 22 to be traced from the selected update group 22 can be determined from the update graph 33. Hereinafter, the update group 22 traced from the selected update group 22 will be referred to as an update subgraph of the selected update group 22. In addition, since the updated subgraph has a tree structure, the update group 22 corresponding to the root portion of the tree structure is hereinafter referred to as a root update group. Therefore, S is a set of update groups 22 belonging to at least one of the update subgraphs, with the update group 22 in the update range 23 as a root update group. In the left diagram of FIG. 8, in order to express the link from the root update group in an easy-to-understand manner, the arrow from the update group G31 that does not enter S is not drawn.

The update partition extraction unit 7 sets each update group 22 belonging to the update group set S so as to update the partition included in each update group 22 to the version of each update group 22. However, if an update with a newer version than the update group 22 has already been specified for the partition, the update with the new version is prioritized. As a result, the partition requiring the update and its version are determined.
FIG. 9 is a diagram for explaining a section that needs to be updated and its version determined by the updated section extraction unit 7 based on FIG.
As shown in FIG. 9, the update request partition 35 that needs to be updated is a union partition of the partition 36 of each update group in the update group set S, and the update version of each partition 36 includes the partition. This is the latest update group version of the update group 22 in the group set S. FIG. 9 also shows hatching with priority given to the new version.
The map update device 1 transmits update data to the terminal device 11 on the basis of the sections requiring update and the version of each section determined in this way.

  However, it is conceivable that the map data 12 of the terminal device 11 is also updated at a certain previous stage. In this case, only the section whose version of the update request section 35 is newer as described in FIG. 9 than the version of each section of the map data 12 of the terminal device 11 is updated. That is, the map update device 1 transmits only the update data of the section having a version newer than the version of each section of the map data 12 of the terminal device 11 to the terminal device 11. Therefore, the map update device 1 needs to grasp the update status of the map data 12 of the terminal device 11. As a method for grasping the update status of the map data 12 of the terminal device 11, it may be possible to transmit the current version information of all the sections of the terminal device 11 to the map update device 1. The data (update status data) of one or more root update groups that have been updated is transmitted.

  The data of the root update group transmitted by the terminal device 11 is obtained at the time of the extraction operation of the update partition extraction unit 7 when the update partition is selected in the past map update device 1, and is updated at the time of past update. At the same time, it is transmitted to the terminal device 11. As described above, if a root update group is specified, an updated partition and version are determined by the updated subgraph 33, and accordingly, the terminal device 11 is determined based on the data of the root update group transmitted from the terminal device 11. The update partition extraction unit 7 narrows down the partition to be updated by restoring the current version of each partition and comparing the current version of each partition of the restored terminal device 11 with the extracted version of the update request partition 35 Can do. The past root update group data is, for example, an identification number that designates an update group, and is a root update group related to the update range 23. Therefore, the number is much smaller than the total number of partitions, and the amount of transmission data is small. Reduced.

FIG. 10 is a diagram illustrating an example of the version of the map data 12 of the terminal device 11.
For example, it is assumed that the update group G22 enters the update range 23 in the version V2 stage shown in FIG. 7 and the update is performed with G22 as the root update group.
In this case, as shown in FIG. 10, the map data 12 of the terminal device 11 is updated with priority given to the version of G22 in the section of G22 and G13 to which a link is established. Therefore, the update partition extraction unit 7 compares the update status of FIG. 10 and narrows down the update partition by excluding the partitions that have already been updated from FIG. As a result of narrowing down, for example, the update partition extraction unit 7 is a partition that is hatched in FIG. 10 among the partitions 36 of the update request partition 35 in FIG. 9 and that has the same hatching indicating the version and that already satisfies the update. This is determined as an update section.

Next, the update data generation unit 8 will be described.
The update data generation unit 8 reads the update data for the version of the section requiring the update from the map data 2 of the storage unit 4. Alternatively, the update data is created from the map data 2 in the storage unit 4. The update data is the specified version of the map data 2 that replaces each section, or is difference data that updates each section from the current version of the terminal device 11 to the specified version.

Further, the update data generation unit 8 integrates the update group 22 searched within the update range 23 and the root update group received from the terminal device 11 to generate a new root update group for the terminal device 11 and receive it. Update the root update group data. This is the data obtained by combining the update group 22 in the update range 23 and the root update group received from the terminal device 11, excluding duplicate data and data included in other update subgraphs. .
FIG. 11 is a diagram illustrating an example of new root update group data for the terminal device 11 generated by the update data generation unit. In FIG. 11, after the update by the update range 23, two partition groups G <b> 32 and G <b> 33 constitute a root update group 37.

The communication unit 9 transmits the update data generated by the update data generation unit 8 and the data of the new root update group to the terminal device 11 via the communication network 10.
In the terminal device 11, the map data 12 is updated with the update data transmitted from the map update device 1, and the update status data 13 is replaced with the data of the new root update group.

  The storage unit 4 of the map update device 1 stores map data 2 of each version or difference data between the map data 2 of each version, and additionally stores update management data 3 including the above-described update graph. Is done. The map data 2 may be managed by a database. The update range 23 is, for example, a municipality or a prefecture where the user of the terminal device 11 resides, an action range, a current location of the terminal device 11 or a range including a route traveled in the past. The terminal device 11 may be set automatically or may be freely changed by the user.

Next, the detail of operation | movement of the map update apparatus 1 which concerns on Embodiment 1 of this invention is demonstrated.
FIG. 12 is a flowchart of the operation of the map update device 1 when a new version of the map is given by updating the map data 2. It is assumed that the new version of the map data 2 is already stored in the storage unit 4.
The area classification unit 5 compares the new version of the map data 2 and the map data 2 of the previous version for each section, determines whether there is a data change, that is, an update, and extracts an updated section. (Step ST1). However, when the new version of the map data 2 is given as difference data obtained by extracting only the changed portion from the map data of the previous version, if the difference data includes substantial changes, the section is Extract as an updated partition.

Next, the area classification unit 5 classifies the updated section extracted in step ST1 into update groups 22 (step ST2). This is a group of adjacent updated sections in one group, or a group of adjacent sections when the feature data on the adjacent section is changed.
FIG. 13 is a diagram illustrating an example of the data 38 of the update group 22 compiled by the area classification unit 5. As shown in FIG. 13, the data 38 of the update group 22 includes the update group 22 identification number G ₀ and version number V, the number of partitions N belonging thereto, and a set of the respective identification numbers T _{1 to} T _N. Composed. FIG. 13 shows an example in which information about the link added in step ST3 described later is also added. Specifically, the number M of links to the update group 22 of the lower level, that is, the previous version, and the identification field numbers G _{1 to} G _M of the update group 22 are shown.

The area structuring unit 6 receives the data 38 of the update group 22 divided by the area dividing unit 5 in step ST2, and generates data for managing the update group 22 using the update graph 33 (step ST3). Specifically, the update group 22 of the previous version having a common partition with the update group 22 is extracted, and a link to the extracted update group 22 of the previous version is provided. Each update group 22 is expressed in a data format as shown in FIG. 13, for example, and is stored in the storage unit 4 as update management data 3.
By managing the update of the map by the update management data 3, that is, the update group 22 and the update graph 33, the operation when the updated map is given is completed.

FIG. 14 is a flowchart illustrating the operation of the map update device 1 when necessary update data is created and transmitted to the terminal device 11 in response to a request from the terminal device 11.
The communication unit 9 of the map update device 1 receives the map update request, the update range 23, and the update status data 13 from the terminal device 11 (step ST101). Here, the update range 23 is, for example, a rectangle designated by a latitude / longitude range.
FIG. 15 is an example of data representing the update range 23. As shown in FIG. 15, the update range 23 is represented by data 39 including a lower limit (Bs, Ls) and an upper limit (Be, Le) of latitude and longitude. The update range 23 is not limited to the rectangle specified by the latitude / longitude range, and may be a set of sections.

The update status data 13 received from the terminal device 11 indicates the root update group of the update group in the update so far, and is composed of, for example, the number K and the identification numbers R _{1 to} R _K as shown in FIG. Data 40. If no update has been performed, K is 0.

The update section extraction unit 7 first updates the update group 22 of the update group set S including the update group 22 having the common area and the update range 23 received in step ST101 and the update group 22 of the updated subgraph from the update management data 3. Extract (step ST102). The update group 22 having a common section with the update range 23 may be configured to specify a section included in the latitude / longitude range indicated by the update range 23 and extract the update group 22 including the section.
Next, the update partition extraction unit 7 obtains an update partition for executing an update without inconsistency from the update group 22 having the update range 23 and the common partition extracted in step ST102 (step ST103). Specifically, for the update group 22 of the update group set S composed of the update group 22 extracted in step ST102 and the update group of the updated subgraph, an update request partition 35 that is the union of the partitions belonging to the update group 22 is obtained. The latest version among the versions specified by the update group is specified for each partition 36. The update partition extraction unit 7 combines the update request partition 35 and the version specified for the partition into update request partition data 41 (see FIG. 9). In FIG. 9, the update request section data 41 is represented by indicating the version information designated for each section in the update request section 35 by changing the hatching. In order to update the update range, the partition indicated in the update request partition data is updated to the version.

  The update partition extraction unit 7 obtains current partition data 42 (see FIG. 10) indicating which version of each partition of the terminal device 11 is updated from the update status data 13 of the terminal device 11 received in step ST101 (see FIG. 10). Step ST104). The specific method for obtaining the existing partition data 42 is to obtain a partition that is the union of partitions belonging to the root update group of the terminal device 11 and all the update groups of the updated subgraph, as in step ST103. What is necessary is just to designate the newest version among the versions designated by these update groups for each partition.

  The update partition extraction unit 7 compares the update request partition data 41 obtained in step ST103 with the existing partition data 42 obtained in step ST104, and corrects the update request partition data 41 (step ST105). Specifically, a partition in the update request partition data 41 is included in the current partition data 42, and the version specified in the update request partition data 41 is the same as the current version of the terminal device 11 indicated in the current partition data 42. Or earlier than that, the partition does not need to be updated further, and is excluded from the update request partition data 41. That is, regarding the partition specified in the update request partition data 41, the update is executed when the terminal device 11 has not reached the version.

The update data generation unit 8 updates the update data for updating each partition described in the update request partition data 41 corrected by the update partition extraction unit 7 in step ST105 to the version described in the update request partition data 41. Generate (step ST106).
The update data generation unit 8 updates the update status data 13 received from the terminal device 11 in step ST101 (step ST107). Specifically, the update group 22 searched for within the update range 23 is added to the root update group indicated in the update status data 13, and there are duplicates in the update group 22, and update subgraphs of other update groups The update performed by the terminal device 11 so far, that is, the version of each section can be reproduced by the root update group and the update group of the updated subgraph.

  The communication unit 9 sends the update data generated by the update data generation unit 8 in step ST106 and the update status data updated by the update data generation unit 8 in step ST107, that is, the updated root update group data to the terminal device 11. Transmit (step ST108).

FIG. 17 is a flowchart showing the operation of the terminal device 11. The terminal device 11 is a car navigation device, for example.
The update range designation unit 15 of the terminal device 11 sets the update range 23 of the map data 12 held in the storage unit 14 (step ST201).
The communication unit 16 transmits the update range 23 set in step ST201 and the update status data 13 stored in the storage unit 14 to the map update device 1 (step ST202). In response to this, the map update device 1 creates update data for the terminal device 11 by the operation shown in the flowchart of FIG.

The communication unit 16 receives the update data and the updated update status data 13 from the map update device 1 (step ST203).
The map updating unit 17 updates the map data 12 in the storage unit 14 with the update data received by the communication unit 16 in step ST203 (step ST204). Specifically, if the update data replaces the map data of the section shown in the update data, replaces the section, or if the update data represents the difference between the existing map data of the section, the difference between the existing map data Append or delete the given data.
In step ST204, the map update unit 17 replaces the update status data 13 with the update status data received by the communication unit in step ST203.
Thereafter, the map display unit 18 displays a map using the map data 12 updated by the map update unit 17 in step ST204.

  In this way, upon receiving the update range 23 from the terminal device 11, the map update device 1 determines the section to be updated and its update version, creates update data, and transmits it to the terminal device 11. This is the minimum section that needs to be updated in order to update the update range 23 to the latest version and to match the features between sections. The terminal device 11 receives the update data from the map update device 1 and updates the map data 12 of the corresponding section.

  As described above, according to the first embodiment, it is possible to update the map in a daily required range to the latest one with a small amount of communication and update calculation. In addition, since update groups that are hierarchized are used to select partitions that need to be updated, update data that are update partitions and update versions are obtained without searching between adjacent partitions while comparing their update versions. be able to.

In the first embodiment, the terminal device 11 is configured to manage the update status of the map data 12 by the update status data 13 and transmit the update status data 13 to the map update device 1 even in the map update. However, of course, all versions of each section may be stored in the storage unit 14, and all the information on the current version of each section may be transmitted to the map update device 1 in the map update. In this case, step ST104 in FIG. 14 is omitted because the version of each section of the map data 12 of the terminal device 11 is already known.
Further, in step ST108 in FIG. 14, the update version information of the update data section is transmitted to the terminal device 11 instead of the updated root update group. In step ST203, the terminal device 11 receives the update version information of the update data section, and updates the version information of the update section with the update version instead of updating the update status data 13 in step ST204.

  In the first embodiment, the terminal device 11 is configured to manage the update status of the map data 12 by the update status data 13 and transmit the update status data 13 to the map update device 1 in the map update. The update status data 13 may be stored in the storage unit 4 of the map update device 1 instead of the terminal device 11. In this case, step ST202 of FIG. 17 transmits the identification number which the terminal device 11 identifies instead of the update status data 13 to the map update apparatus 1. In step ST <b> 101 of FIG. 14, the map update device 1 receives an identification number for identifying the terminal device 11 instead of the update status data 13, and reads the update status data 13 corresponding to the identification number from the storage unit 4. In step ST107 of FIG. 14, the updated update status data 13 is stored in the storage unit 4. The terminal device 11 does not receive the updated root update group data in step ST203 and does not update the update status data 13 in step ST204.

Embodiment 2. FIG.
In the first embodiment, the map update device 1 extracts an update section (step ST103 in FIG. 14), reproduces the update status of the terminal device 11 (step ST104 in FIG. 14), compares them, and updates them. The section is determined (step ST105 in FIG. 14). In the second embodiment, an embodiment in which the operation is performed without reproducing the update status of the terminal device 11 will be described.
Since the configuration of the map updating apparatus 1 according to the second embodiment of the present invention is the same as that shown in FIG. 1 in the first embodiment, detailed description thereof is omitted. The configuration of the terminal device 11 according to Embodiment 2 of the present invention is also the same as that shown in FIG.

  FIG. 18 is a flowchart showing the operation of the map update device 1 according to the second embodiment of the present invention. In addition, description is abbreviate | omitted about the operation | movement same as the operation | movement of the map update apparatus 1 of Embodiment 1 shown in FIG. The operation of the map update device 1 when updating the map data 2 to a new version is the same as that described with reference to FIG. Further, since the configuration and operation of the terminal device 11 are the same as those described in the first embodiment, detailed description thereof is omitted.

  Step ST101 to step ST102 and step ST106 to step ST108 in FIG. 18 are the same as the operations described in step ST101 to step ST102 and step ST106 to step ST108 in FIG. That is, the operation of the map update device 1 according to the second embodiment is the operation of obtaining the current partition data from the root update group of the terminal device 11 from the operation of the map update device 1 according to the first embodiment (step in FIG. 14). ST104) and the operation (step ST105 in FIG. 14) for correcting the update request partition data based on the obtained current partition data are omitted, and the operation of step ST2103 is newly added.

  When the update group of the update group set S obtained in step ST103 of FIG. 14 described in the first embodiment is included in one or more update subgraphs of the root update group of the terminal device 11, The update indicated by the update group has already been performed on the map data 12 of the terminal device 11. The same applies to the update group below the update group.

Therefore, when an update group is included in the update subgraph of the update status data 13 of the terminal device 11, the update group and its lower update group need not be considered in determining the update partition.
FIG. 19 is a diagram illustrating an example of an update group extraction method that requires updating in the map updating device 1 according to the second embodiment. Here, for example, a case will be described in which the terminal device 11 is updating the updated subgraph by the G22 update group in the version V2 shown in FIG.

As shown in FIG. 19, the update group set S determined from the update range 23 excluding the update subgraph indicating the update status of the terminal device 11 is an update group that really needs to be updated. A group set S′43 is assumed.
In step ST2103 of FIG. 18, when obtaining the update request partition data 41, the update partition extraction unit 7 updates updates derived from the root update group received from the terminal device 11 in step ST101 among the update groups of the update group set S. Extraction is performed only for sections belonging to the update group set S ′ excluding those included in the subgraph.

Other operations are the same as those in step ST103 of FIG. 14 described in the first embodiment. That is, for all update groups in the update group set S ′, a partition that is a union of partitions belonging to the update group is obtained, and the latest version among the versions specified by these update groups is specified for each partition. With this operation, only further update sections from the current update status of the terminal device 11 are extracted, so that the operations of step ST104 and step ST105 in FIG. 14 can be omitted.
FIG. 20 is an example of the update request partition data 41 obtained from the update group set S ′ shown in FIG.

  As described above, according to the second embodiment, the update group set is compared with the update subgraph indicating the update status of the terminal device 11, and the update group that has already been updated is excluded from the update group set. The number of update groups to be taken into account when creating the update request partition data 41 can be reduced, and the processing effort can be reduced.

Embodiment 3 FIG.
In the prior art, the latest version of the map is obtained for a newly required section. In the pan operation (map scroll operation), necessary sections of the display area are sequentially downloaded. For this reason, when a map of a section adjacent to a downloaded map is newly downloaded, if the map is updated at that time, the map of the adjacent section becomes a new version. Thus, in the pan operation, there is a problem that inconsistencies occur in the map. In the third embodiment, even when map data newly acquired from the map update device is updated while the map system is being used, a map information system that executes a pan operation so that inconsistency does not occur at the boundary between sections An embodiment capable of obtaining the above will be described.

FIG. 21 is a block diagram showing the configuration of the map update device 1 according to Embodiment 3 of the present invention.
The same components as those shown in FIG. 1 in the first and second embodiments are denoted by the same reference numerals, and redundant description is omitted. The first and second embodiments are different from those shown in FIG. 1 in that the area structuring unit 6 and the update data generating unit 8 are not provided and a distribution control unit 52 is added.
The distribution control unit 52 is a distribution control unit that reads out map data of a section requested from the terminal device 11 from the storage unit 4 and controls distribution.

FIG. 22 is a block diagram showing a configuration of terminal apparatus 11 according to Embodiment 3 of the present invention. In the third embodiment, the terminal device 11 is, for example, a personal computer.
The same components as those shown in FIG. 2 in the first and second embodiments are denoted by the same reference numerals, and redundant description is omitted. In the first and second embodiments shown in FIG. 2, the storage unit 14 stores the partition buffer 44 in place of the map data 12 and the update status data 13, and the update range specifying unit 15 is not provided. The difference is that the update control unit 45 is provided.
The partition buffer 44 is a part of the map data. The map display unit 18 clips the map data in the partition buffer 44 and displays it on a display unit such as a display. The display unit may be provided in the terminal device 11 or may be provided with a display device outside the terminal device 11.
The update control unit 45 controls the update of the partition buffer 44.
As in the first and second embodiments, the map updating system is configured by connecting the map updating device 1 and the terminal device 11 via a communication network 10 such as a wired or wireless computer network or a telephone line.

  When using a map system that displays a map on a personal computer or the like, and confirms the current position, searches for a target point, or performs navigation, the storage unit 14 of the terminal device 11 includes an area that is currently displayed, and a wider area. The map data of a certain number of sections constituting the section buffer 44 is stored. Then, the map display unit 18 performs clipping for extracting an area to be displayed within the range of the partition buffer 44, and displays the map data on a display unit such as a display.

FIG. 23 is a diagram illustrating an example of the partition buffer 44 and the clipping range 46.
As shown in FIG. 23, the partition buffer 44 is a continuous partition that forms a rectangle of, for example, 5 sections in the latitude direction (direction a in FIG. 23) and 5 sections in the longitude direction (direction b in FIG. 23). When the map display unit 18 pans (scrolls) the map displayed on the display unit, the map update device is limited to the inside of the partition buffer 44 if the clipping range 46 to be displayed is sequentially moved in the partition buffer 44. The map of the area moved in a short time can be displayed without performing communication with 1.
Here, the section buffer 44 has five sections in the latitude direction and the longitude direction, but the present invention is not limited to this and can be set as appropriate.

FIG. 24 is a diagram for explaining an example of updating the partition buffer 44.
It is assumed that the clipping range 46 has moved in the direction of the arrow from the state shown in FIG. Thus, when the display range exceeds the partition buffer 44, as shown in FIG. 24, the terminal device 11 requests the map update device 1 for map data of a new partition necessary for display, and the map update device 1 The map data of the new section received from is taken into the section buffer 44. At that time, the new section is replaced with section data of a part far from the one column in the latitude direction or one row in the longitude direction.

When the partition buffer 44 is updated, the map data 2 of the map update device 1 is updated, and the received map data 2 of the partition becomes a new version with respect to the map data existing in the partition buffer 44 at that time. In such a case, the terminal device 11 updates the sections necessary for matching the existing sections in addition to the sections that require the map data 2 anew.
Also in the third embodiment, as in the first and second embodiments, the map update device 1 uses the area sorting unit 5 to divide the update sections that have been updated in the update of the map data 2 into groups. Since the grouping method is the same as that described in the first embodiment, a detailed description is omitted, but the update group 22 grouped by the area partitioning unit 5 is adjacent and needs to be updated simultaneously. Are grouped together as the same update group 22.

  After the map update device 1 updates the map data 2, when the terminal device 11 requests the map update device 1 for map data of a new partition, the terminal device 11 requested the map data and the partition existing in the partition buffer 44. If the update group 22 is straddling, the new version of the partition requested by the terminal device 11 matches the old version of the partition adjacent to the partition newly acquired from the map update device 1 in the partition buffer 44. No longer. For this reason, a necessary partition is updated to a new version for the partition in the partition buffer 44. In other words, even when the map data 2 of the map update device 1 is updated, the partitions in the partition buffer 44 can be matched.

  For example, when the clipping range 46 in the partition buffer 44 moves within the partition buffer 44 in accordance with the pan operation during the pan operation of the map (see FIG. 23), if the clipping range 46 exceeds the range of the partition buffer, The map area of the buffer 44 is shifted in the direction in which the clipping area 46 is moved so that the clipping area 46 fits in the partition buffer 44 (see FIG. 24). In FIG. 23, the clipping range 46 has moved to the left in the partition buffer 44 of the five partitions 48 in the vertical and horizontal directions and is going to exceed the range of the partition buffer 44. At this time, the partition 1 on the left side of the partition buffer indicated by the broken line The map is requested to the map update device 1 using the column as the request section 47. Thereafter, the terminal apparatus 11 receives the requested section 47 from the map update device 1 and reconfigures the section buffer 44 in place of the section 50 in the right column as shown in FIG. At that time, if the map data 2 of the map update device 1 has been updated, only the version of the requested section 47 to be newly stored will be increased, so that there is a possibility that inconsistency will occur at the boundary. In order to solve this, as shown in FIG. 24, the map updating apparatus 1 extracts the update group 49 including the requested partition 47 to be newly stored, and updates the partition 51 in the partition buffer 44 included therein.

FIG. 25 is a flowchart showing the operation of the terminal device 11 according to the third embodiment of the present invention.
The update control unit 45 determines a requested section 47 to be read into the section buffer 44 when a new section needs to be displayed by the pan operation (step ST3201). Specifically, as described with reference to FIG. 24, the partition is located at a position where the clipping range 46 exceeds or touches the partition buffer 44. The section is specified by, for example, an identification number assigned to the section or a set of latitude and longitude of the representative point.

The map updating unit 17 requests the map updating device 1 via the communication unit 16 for one data of the request section 47 specified by the update control unit 45 in step ST3201 (step ST3202). In response to this, the map update device 1 transmits the map data of the requested section to the terminal device 11.
The communication unit 16 receives the map data of the section from the map update device 1 (step ST3203).
The map updating unit 17 replaces the section of the section buffer 44 with the map data received by the communication unit 16 in step ST3203 (step ST3204).
The update control unit 45 determines whether there is an unprocessed requested section 47 (step ST3205). In step ST3205, when there is an unprocessed requested section 47 (in the case of “YES” in step ST3205), that is, for all sections of the requested section 47, map data is requested to the map update unit 17, and the requested section 47 When the process which receives map data is not performed, it returns to step ST3202.

  In step ST3205, when there is no unprocessed requested section 47 (in the case of “NO” in step ST3205), that is, for all sections of the requested section 47, map data is requested to the map update unit 17, and the requested section When the process of receiving the map data is completed, the update control unit 45 checks the version of the map data of the requested section 47 received from the map update device 1 and is adjacent to the requested section 47 currently stored in the section buffer 44. It is compared with the map data version of the section to be checked to determine whether or not the requested section 47 has been updated to a new version (step ST3206). Specifically, for example, if the map data has version information, it may be determined whether the version has been updated by comparing the version information using the version information, or just before the map data What is necessary is just to make it determine by comparing the information of the time modified to.

In step ST3206, when the requested section 47 has not been updated to a new version (in the case of “NO” in step ST3206), the map data of the requested section 47 is the same version as the map data of the existing section in the section buffer 44. It is determined that they are consistent, and the process ends.
In step ST3206, when the requested section 47 has been updated to a new version (in the case of “YES” in step ST3206), the update control unit 45 uses the communication unit 16 to identify data for identifying the section for the requested section 47. It transmits to the map update device 1 (step ST3207). This is because the map data of the section received from the map update device 1 in step ST3203 does not match the section adjacent to the requested section 47 in the section buffer 44 before the new section needs to be displayed by the pan operation. This is because there is a possibility. Therefore, the terminal device 11 additionally performs update of a necessary partition adjacent to the request partition 47.

In step ST3207, when receiving the data for identifying the section of the requested section 47 from the terminal device 11, the map updating apparatus 1 receives the section and assigns the section belonging to the update group 22 having the common part to the requested section 47 to the candidate section data. 53 is transmitted to the terminal device 11.
FIG. 26 is a diagram illustrating an example of candidate segment data 53 transmitted by the map update device 1.
As shown in FIG. 26, the candidate partition data 53 is composed of the number of partitions H and identification numbers T1 to TH indicating partitions, and is a partition that needs to be updated in order to be consistent with the update of the requested partition 47. If there are a plurality of update groups having a common partition with the requested partition 47, a union of partitions belonging to each update group is obtained. If there is not, only 0 is entered in the number of sections H.

Communication unit 16 receives candidate segment data 53 from map update device 1 (step ST3208).
The update control unit 45 determines whether or not there is an unprocessed candidate section in the candidate section data 53 received in step ST3208, that is, the section of the section that was in the section buffer 44 before a new section needs to be displayed by the pan operation. It is determined whether there is a version newer than the version (step ST3209). Specifically, for example, if the map data has version information, it may be determined whether the version has been updated by comparing the version information using the version information, or just before the map data What is necessary is just to make it determine by comparing the information of the time modified to.

In step ST3209, when there is no unprocessed section (in the case of “NO” in step ST3209), the process ends.
In step ST3209, when there is an unprocessed partition (in the case of “YES” in step ST3209), the update control unit 45 proceeds to step ST3210 as a candidate partition targeting the unprocessed partition, and the candidate partition targeted is It is determined whether it is within an existing partition of the partition buffer 44 (step ST3210).
In step ST3210, when the target candidate partition is not in the existing partition of the partition buffer 44 (in the case of “NO” in step ST3210), the update control unit 45 returns to step ST3209 and there is no unprocessed candidate partition. Until step ST3209 is repeated.

  In step ST3210, when the target candidate section is in an existing section of the section buffer 44 (in the case of “YES” in step ST3210), the map update unit 17 performs the section in step ST3210 on the map update device 1. The map data of the target candidate section determined to be in the existing section of the buffer 44 is requested via the communication unit 16 (step ST3211). In response to this, the map update device 1 transmits the map data 2 of the requested section to the terminal device 11.

The communication unit 16 receives the map data of the candidate section that is the target requested in step ST3211 from the map update device 1 (step ST3212).
The map update unit 17 replaces the map data in the partition buffer 44 with the map data received from the map update device 1 in step ST3212 for the target candidate partition (step ST3213). Then, it returns to step ST3209 and repeats the process after step ST3209 until there is no unprocessed candidate division.

Next, the operation of the map update device 1 will be described.
FIG. 27 is a flowchart showing the operation of the map update device 1 according to the third embodiment of the present invention. FIG. 27 shows the operation when a new version of the map is given by updating the map data 2.
FIG. 27 is a flowchart showing the operation at the time when the new version of the map shown in FIG. 12 is given in the first embodiment, excluding step ST3. For steps ST1 and ST2 in FIG. Since they are respectively the same as step ST1 and step ST2 of FIG. 12, detailed description is omitted. In Embodiment 3, the section stored in the section buffer 44 is updated as needed from the map management apparatus 1 by a zoom operation or the like in addition to a pan operation. Also, if the update interval of the map is sufficiently longer than the continuous use time of the map system operated by the terminal device 11, three or more versions will not coexist in the partition buffer 44. For this reason, it is sufficient to consider the old and new two versions, and it is not necessary to perform hierarchical management of a plurality of update versions (the process of step ST3 in FIG. 12).

FIG. 28 is a diagram illustrating an example of the update management data 54 of the map update device 1 according to the third embodiment.
As shown in FIG. 28, the update management data 54 is only information on the update partition of the new version with respect to the old version, and does not have information on the link.
FIG. 29 is a flowchart illustrating an operation for obtaining candidate partition data 53 in response to a request from the terminal device 11 in the map update device 1 according to the third embodiment. That is, the operation on the map update device 1 side corresponding to the operation of the terminal device 11 described in step ST3207 of FIG. 25 is shown.
The communication unit 9 receives the section data of the request section 47 from the terminal device 11 as an update range (step ST3101).
The update partition extraction unit 7 searches the update management data 3 for an update group 22 having a partition common to the update range received in step ST3101 and extracts it (step ST3102).
The update partition extraction unit 7 sets the data for identifying the partition belonging to the update group 22 obtained in step ST3102 as candidate partition data 53 (step ST3103), and transmits it to the terminal device 11 via the communication unit 9 (step ST3103). ST3104).

  In addition, the processing of the map update device 1 when receiving a request for one data of the request section 47 from the terminal device 11 (processing corresponding to the operation of the terminal device 11 described in step ST3202 of FIG. 25), and the terminal device 11 is processed by the map updating device 1 when it receives a request for map data of a candidate zone that is the target candidate zone determined to be within the existing zone of the zone buffer 44 (of the terminal device 11 described in step ST3211 in FIG. 25). In the processing corresponding to the operation, when the communication unit 9 of the map update device 1 receives a request from the terminal device 11, the distribution control unit 52 reads the map data 2 of the designated section from the storage unit 4, and the communication unit 9 to the terminal device 11.

  As described above, according to the third embodiment, in the map display in the map system, in addition to the sections newly required for the map display, the already owned sections are also updated for consistency. Therefore, even if the map data of the map update device is updated while using the map system, it is possible to display a consistent map.

  In the present invention, within the scope of the invention, any combination of the embodiments, or any modification of any component in each embodiment, or omission of any component in each embodiment is possible. .

  DESCRIPTION OF SYMBOLS 1 Map update apparatus, 2 Map data, 3 Update management data, 4 Storage part, 5 Area division part, 6 Area structuring part, 7 Update division extraction part, 8 Update data generation part, 9 Communication part, 10 Communication network, 11 Terminal device, 12 map data, 13 update status data, 14 storage unit, 15 update range designation unit, 16 communication unit, 17 map update unit, 18 map display unit, 44 partition buffer, 45 update control unit, 52 distribution control unit.

Claims (9)

A storage unit for storing map data for each version at the time of update, and update management data for managing a section where the map data has been updated;
An area division section for grouping partitions that need to be updated at the same time into update groups;
The update management data structured so as to be able to refer to an old version update group, which has a common partition with the update group, and is an update group at the time of updating the map data of a version older than the version of the update group A region structuring unit to generate,
When an update range for updating a map is specified, an update partition extraction unit that determines a partition to be updated and an update version for each partition to be updated based on the update management data;
An update data generating unit that refers to the map data and generates update data for updating the update section to an update version determined for each section;
A communication unit that receives the update range and update status data indicating an update status of map data of the terminal device in an update group from a terminal device via a communication network, and transmits the update data to the terminal device; Prepared,
The update partition extraction unit
When the update range for updating the map is designated, the update group having the common part with the update range and the old version that can be referred to from the update group having the common part with the update range with respect to the update range The partition belonging to the update group is extracted as the partition to be updated, and the update of the partition that updates the latest version of the update group or the old update group to which the partition to be updated belongs is updated with respect to the partition to be updated. A map update device characterized by being determined as a version. The update partition extraction unit
Based on the update status data and the update management data, the current version of the section of the map data of the terminal device is reproduced from the update status data, and the updated version for each section to be updated is compared with the current version. The map updating apparatus according to claim 1, wherein only a section having a version newer than the current version is used as the section to be updated. The update partition extraction unit
Based on the update status data and the update management data, the update group having the common part with the update range and the old update group that can be referred to from the update group having the common part with the update range, from the update status data A partition included in an update group excluding an update group to be identified and an update group that can be referred to from the update group is extracted as the partition to be updated, and the partition to be updated is included in the set of update groups, The map update device according to claim 1, wherein the latest version of the update group to which the partition to be updated belongs is determined as the version of the partition to be updated. The area section is
The map updating apparatus according to claim 1, wherein when a feature is added, deleted, moved, or changed in attribute across adjacent sections, the adjacent sections are divided into the same update group. . The area section is
The map updating apparatus according to claim 1, wherein when there is a change in a feature in both adjacent sections, the adjacent sections are divided into the same update group. A storage unit for storing map data for each version at the time of update, and update management data for managing a section where the map data has been updated;
An area division section for grouping partitions that need to be updated at the same time into update groups;
When an update range for updating the map is specified from the terminal device, an update partition extraction unit that extracts a partition to be updated based on the update management data;
A distribution control unit that reads out the map data of the section requested from the terminal device from the storage unit and controls distribution;
A communication unit that communicates with the terminal device via a communication network,
The update extraction unit
Extracting a partition belonging to the update group having a common part with the update range as the partition to be updated,
The delivery control means includes
The map update device, wherein the map data indicating the section to be updated is transmitted to the terminal device via the communication unit. The map update device according to any one of claims 1 to 5,
A storage unit for storing map data and update status data indicating an update status of the map data in an update group;
An update range specification section for specifying an update range for updating the map;
A communication unit for communicating with the map update device;
A terminal device including a map update unit that updates the map data by the update data transmitted from the map update device;
The map update device generates update data for the update range and update status data received from the terminal device, updates the received update status data and transmits the update data to the terminal device,
The terminal device updates a version of a section in which the map data is updated with the update data received from the map update device to the update version, and the update status with the update status data received from the map update device. A map update system characterized by updating data. A map updating device according to claim 6;
A storage unit for storing a part of the map data as a partition buffer;
An update control unit for controlling update of the partition buffer;
A communication unit for communicating with the map update device;
A terminal unit including a map update unit that stores map data in units of partitions received from the map update device in a partition buffer;
The map update device transmits data indicating the section to be updated to the terminal device for the update range specified by the terminal device,
The terminal device extracts a partition corresponding to the partition buffer among the partitions to be updated received from the map update device, and requests the map update device for the update data for the extracted partition,
The map update device transmits the update data corresponding to the request to the terminal device,
The said terminal device updates the division corresponding to the said division buffer with the said update data received from the said map update apparatus. The map update system characterized by the above-mentioned. A map update management method for managing an updated section of a map updated at any time by a map update device,
A region dividing unit grouping partitions that need to be updated simultaneously into regions as update groups;
The area structuring unit has a section that is common to the update group, and is structured so that an old version update group that is an update group at the time of updating the map data of a version older than the version of the update group can be referred to. And a step of generating the update management data. A map update management method comprising:

Images