JP6136511B2 - Map difference data distribution device, vehicle navigation device, and map difference data distribution method - Google Patents

Description

  The present invention relates to a map difference data distribution device that distributes map difference data to a vehicle navigation device, a vehicle navigation device to which difference data is distributed from the map difference data distribution device, and a map difference data distribution method.

  A technique for updating a part of map data corresponding to a newly created road is known (for example, Patent Document 1). In patent document 1, map data is memorize | stored in the memory | storage device with which the navigation apparatus for vehicles is provided. And the map data for the update produced one by one in the cartography company is distributed to the vehicle navigation device by radio.

  Further, map data including data for each road level divided into a plurality of is known (for example, Patent Document 2). The map data described in Patent Document 2 has a hierarchical structure describing a network of roads belonging to the road level for each road level.

Japanese Patent No. 4682809 JP 2012-163908 A

  The difference data, which is the map data of the updated portion, is created due to changes in elements (hereinafter referred to as map elements) shown on the map, such as addition or deletion of roads. However, the order in which the map difference data is distributed to the vehicle navigation device is not always the map element change order. In consideration of the capacity of the map storage device of the vehicle navigation device and the amount of communication data, the map difference data distributed to the vehicle navigation device may be part of all the map difference data. is there. Note that even if all map difference data is distributed, if a plurality of map difference data are distributed, only a part of all map difference data is distributed until the last distribution is performed. .

  When only a part of all the map difference data is distributed, the route search accuracy may be lowered. In particular, when only a part of all map difference data is distributed to map data having a hierarchical structure as in Patent Document 2, the following explanation may occur as a decrease in route search accuracy. is there.

  In a route search using map data having a hierarchical structure, a part from a starting point to a destination is divided into several ranges, and partial routes are searched using data of a predetermined hierarchy for each range. The route created at a certain level and the route created immediately above it need to be continuous. Therefore, nodes that exist together in the upper and lower hierarchies must be the end points of the routes in those hierarchies. Since the nodes that exist in the upper and lower layers are nodes that connect the roads in the lower layer to the roads in the upper layer, this node is hereinafter referred to as an upper road connection node.

  Here, for example, when a new road is established and an old road near the road is deleted, only difference data indicating that the old road has been deleted is distributed. As a result, there is a possibility that a link to the upper road connection node becomes longer than a route that is originally possible, and as a result, a route that becomes a detour is searched.

  The present invention has been made based on this circumstance, and the object of the present invention is to provide a map that distributes map difference data that can prevent the vehicle navigation device from searching for a route that makes a detour. The object is to provide a difference data distribution device, a vehicle navigation device to which difference data is distributed from the map difference data distribution device, and a map difference data distribution method.

A first invention for achieving the object includes a map storage device (34) storing original map data describing a road data indicating a road connection relationship using nodes and links in a hierarchical structure. A map difference data distribution device (100) for sequentially distributing difference data, which is updated map data not included in the original map data, to a vehicle navigation device (3) that performs route search based on map data. A difference data storage unit (121) for storing the difference data, and the difference data storage unit, as the difference data, link reduced data corresponding to a reduced link that is a reduced link direction; And at least one additional link data corresponding to a newly established road around the reduced link is stored. For at least one combination of small data and the link addition data, the link addition when the data has not been delivered, delivery rules is to deliver the pre-Symbol link additional data prior to said link reduced data defined It is characterized by having a setting state storage unit (122) that stores.

  2nd invention receives the said difference data from the map difference data delivery apparatus of 1st invention, and performs a route search based on the received difference data and the said original map data memorize | stored in the said map memory | storage device. A vehicle navigation device characterized by the above.

A third invention includes a map storage device that stores original map data that describes road data in a hierarchical structure indicating road connection relationships using nodes and links, and performs a route search based on the original map data A map difference data distribution method for sequentially distributing difference data, which is map data of an updated part not included in the original map data, for a navigation device for a vehicle,
Each layer of the original map data is divided into a plurality of meshes to describe road data, and a lower layer having an upper layer among the layers is a section including the mesh for each of the meshes. A section that includes at least one higher-level road connection node that is also a node that exists in the hierarchy one level above, so that all links in the mesh can reach the higher-level road connection node in the same section A route block is set,
The link reduction data, which is the difference data regarding the reduction link that is a link whose direction that can be reduced, is distributed to the vehicle navigation device, but the link addition data corresponding to the newly established road around the reduction link is If it is not delivered to the vehicle navigation device and is not delivered, a link that does not have a route to reach the upper road connection node in the route section is generated in the same mesh as the reduced link. When the determination condition is satisfied, the link reduction data and the link addition data are delivered to the vehicle navigation device at one time together with the link reduction data or before the link reduction data. Map difference data delivery method.

  According to the first to third inventions, the link addition data is delivered to the vehicle navigation device at one time together with the link reduction data or before the link reduction data. Even though a new road is newly established near the road that has become inaccessible, the route search process of the vehicle navigation device cannot search for a route that passes through the new road, but searches for a route that makes a detour. Can be suppressed.

The figure which shows an example of a schematic structure of the map difference data delivery system 100 to which this invention was applied. The block diagram which shows the function of the extraction server side control part 13 of FIG. The figure explaining the structure of base map data 5 The figure explaining route division 53 The figure explaining the road level used in route search processing Examples of map element categories and subcategories The figure explaining the mismatch which does not reach the upper road connection node 55 Dependency list example Sequence diagram showing the flow of processing in the map difference data distribution system 100

<Map difference data distribution system 100>
A map difference data distribution system 100 shown in FIG. 1 includes a map difference extraction server 1 and an update management server 2. The map difference data distribution system 100 is connected to a vehicle navigation device 3 (hereinafter simply referred to as a navigation device 3). Deliver differential data.

<Map difference extraction server 1>
As shown in FIG. 1, the map difference extraction server 1 includes an extraction server side communication unit 11, an extraction server side storage unit 12, and an extraction server side control unit 13. The extraction server side communication unit 11 communicates with the update management server 2 and the navigation device 3 via a communication network.

  The extraction server side storage unit 12 is a rewritable storage device such as a hard disk, and includes a map difference database (DB) 121 and a list storage unit 122 in which a dependency list described later is stored. Each of the map difference DB 121 and the list storage unit 122 has a structure using a partial storage area of the extraction server side storage unit 12. The map difference DB 121 corresponds to a difference data storage unit in claims, and the list storage unit 122 corresponds to a setting state storage unit in claims.

  The map difference DB 121 is a database that stores map difference data. The map difference data is map element data that needs to be updated from the base map data 5 (see FIG. 3). The base map data 5 corresponds to the original map data in the claims, and is data of a map (that is, an entire map) for a predetermined range such as the entire country where the map difference data distribution system 100 is applied. is there. The structure of the base map data 5 will be further described later with reference to FIGS.

  The map elements are, for example, characters indicating roads, POIs (Points Of Interest), backgrounds, place names, and the like. Data, character data for displaying place names, and POI data of various facilities.

  Therefore, when a road or POI is added or changed after the base map is created, road data, POI data, or the like is created as map difference data. The map difference data is provided to the map difference extraction server from an external server (not shown), for example. In addition, some map difference data are collected and difference group data are comprised. Distribution to the navigation device 3 is performed in units of the difference group data. A group of map elements corresponding to each of the map difference data collected in the difference group data is called a difference group.

  The extraction server side control unit 13 is mainly configured by a microcomputer including a CPU, a ROM, a RAM, a backup RAM, an I / O and the like (all not shown). The extraction server side control unit 13 executes various control programs stored in the ROM based on various types of information input from the extraction server side communication unit 11, so that the difference group extraction unit 131 (first number) shown in FIG. 1 equivalent extraction unit), a dependency difference group extraction unit 132 (corresponding to a second difference extraction unit), a distribution data creation unit 133, a data URL transmission unit 134, and a distribution unit 135. Specific processing of each part will be described later with reference to FIG.

<Update management server 2>
The update management server 2 includes a management server side communication unit 21, an update management DB 22, and a management server side control unit 23. The management server side communication unit 21 communicates with the map difference extraction server 1 and the navigation device 3 via the communication network.

  The update management DB 22 stores discrimination information for discriminating map difference data distributed from the map difference extraction server 1 to the navigation device 3, and each navigation device 3 when there are a plurality of navigation devices 3. The discrimination information is stored for each user. The determination information is, for example, a difference group ID that has been distributed to the navigation device 3. The difference group ID is an ID assigned to each difference group.

  The management server side control unit 23 is mainly configured by a microcomputer including a CPU, ROM, RAM, backup RAM, I / O, etc. (all not shown). The management server side control unit 23 executes various control programs stored in the ROM based on various information input from the management server side communication unit 21 and the update management DB 22, thereby performing various processes illustrated in FIG. 9. Execute.

<Navigation device 3>
The navigation device 3 may be an in-vehicle navigation device or a portable navigation device that can be brought into the vehicle. Hereinafter, the case where an in-vehicle navigation device is used as the navigation device 3 will be described as an example.

  First, a schematic configuration of the navigation device 3 will be described. As shown in FIG. 1, the navigation device 3 includes a communication device 31, a position detector 32, an external input interface (I / F) unit 33, a navigation-side storage device 34, a display device 36, a voice output device 37, and an operation switch group 38. A remote control terminal (hereinafter referred to as a remote control) 39, a remote control sensor 40, and a control device 41.

  The communication device 31 communicates with the map difference extraction server 1 and the update management server 2 via a communication network. As the communication device 31, for example, various devices such as an in-vehicle communication module such as a DCM (data communication module) used for telematics communication can be adopted.

  Each of the position detectors 32 has a well-known acceleration sensor, gyroscope, and receiver for a satellite positioning system such as GPS (Global Positioning System) that detects the position of its own device based on radio waves from the satellite. The current position of the user of the user apparatus (hereinafter referred to as user position) is sequentially detected. For example, the user position is assumed to be coordinates represented by latitude and longitude. Note that the position detector 32 may be configured by a part of the sensors described above, or may be configured using another sensor.

  The external input I / F unit 33 is an interface for the control device 41 to acquire vehicle state information from an ECU or a sensor mounted on the vehicle. For example, it is assumed that vehicle state information is input to the external input I / F unit 33 from an ECU or a sensor mounted on the vehicle via an in-vehicle LAN or the like. An example of the vehicle state information includes an on / off signal of an accessory (ACC) power source.

  In the present embodiment, the navigation-side storage device 34 includes an SD card and an interface that accommodates the SD card. Of course, other rewritable storage media may be used instead of the SD card. A map data storage area is set in the navigation side storage device 34. The map data storage area is set by a partition, for example.

  The above-described base map data, map difference data, and the like are stored in this map data storage area. Therefore, the navigation-side storage device 34 corresponds to the map storage device in the claims. The base map data is stored in advance in the map data storage area at the time of shipment. On the other hand, map difference data is sequentially acquired from the outside and stored.

  The display device 36 is capable of full color display, for example, and can be configured using a liquid crystal display, an organic EL display, or the like. The voice output device 37 includes a speaker or the like, and outputs a guidance voice or the like based on an instruction from the control device 41.

  For example, a touch switch or a mechanical switch integrated with the display device 36 is used as the operation switch group 38, and an operation instruction for various functions is given to the control device 41 by a switch operation. The remote control 39 is provided with a plurality of operation switches (not shown). By inputting various command signals to the control device 41 via the remote control sensor 40 by the switch operation, the control device 41 has the same function as the operation switch group 38. Can be executed.

  The control device 41 is mainly composed of a microcomputer including a CPU, ROM, RAM, backup RAM, and the like. Then, the control device 41 performs a route search process and a diagram based on various information input from the communication device 31, the position detector 32, the external input I / F 33, the navigation side storage device 34, the operation switch group 38, and the remote control sensor 39. The process shown in 9 is executed. Details of the processing in the control device 41 will be described later.

<Structure of base map data>
As shown in FIG. 3, the base map data 5 includes road data 51 and background data 52. Both the road data 51 and the background data 52 have a structure divided into a plurality of hierarchies (hereinafter, levels). However, the number of levels differs between the road data 51 and the background data 52. The road data 51 has four levels from level 0 to level 3, and the background data 52 has six levels from level 0 to level 5. Note that the number of levels in both the road data 51 and the background data 52 is not limited to the example of FIG.

  The background data 52 is data of a portion drawn as a background in the road map to be displayed. The road data 51 includes various data other than the background. For example, the road data 51 includes data describing the connection relationship of roads necessary for route calculation. A road is represented using a node indicating a branch point and a link indicating a road section between the nodes.

  Both the road data 51 and the background data 52 are data for each rectangular mesh (hereinafter referred to as mesh unit data) obtained by subdividing the rectangular area including the map recording area. The base map data 5 includes a data file group including mesh unit data and a management data file for managing the mesh unit data group. The mesh unit data is arranged in an order corresponding to the arrangement of meshes.

<Hierarchical structure of road data>
The level of the road data 51 is determined in consideration of the type of road (such as an expressway or a national road) and the connection relationship between the roads. For example, a highway connecting cities is set as level 3 road data 51, and other highways and main national roads are set as level 2 road data. Narrow streets and private roads are assumed to be level 0 road data 51, and other roads (national roads not included in level 2 road data 51, ordinary roads running in the city, etc.) are assumed to be level 1 roads. Of course, these are merely examples, and may be designed as appropriate.

  The road level of each road is determined so that roads belonging to each road level are always connected to other roads. Therefore, when national highway n is not connected to other national highways but only to general roads, national highway n is not classified into the road level to which many national roads belong, but is classified into the road level to which general roads belong. The On the other hand, general roads may be classified into road levels to which national roads belong. This connection includes a connection with a higher road level. That is, it is not always necessary to be connected within the same road level, and it is only necessary to include the upper road level.

  The reason why the roads belonging to each road level are always connected to other roads is because the route calculation is considered for each hierarchy. The road data 51 stores the same road data in only one level.

  The road data 51 at each level is data in units of meshes, and each mesh at the upper level is the size of a plurality of meshes at the lower level as shown in FIG.

<Route section defined in the mesh of road data>
A route section 53 is further set for each mesh in the road data except for the highest level. FIG. 4 shows a route section 53 and a corresponding mesh 54 corresponding to the route section 53. The route section 53 is a section that includes the corresponding mesh 54 and is a section that is set to include at least one upper road connection node 55. Further, all the links existing in the corresponding mesh 54 can reach the upper road connection node 55 in the same section only through the links in the same section.

  In FIG. 4, a road 56 indicated by a solid line is a road existing at a level including the corresponding mesh 54, and a road 57 indicated by a broken line indicates a road existing one level above. The upper road connection node 55 is an intersection of the roads 56 and 57. That is, the upper road connection node 55 is a node that exists at a level including the corresponding mesh 54 and is also present at a level one level above it.

  Therefore, in the route search process using the road data 51 having a structure in which data corresponding to each road is stored in a plurality of levels as in the present embodiment, a route passing through the upper road connection node 55 is determined. By searching, a route search using road data 51 of a plurality of levels can be performed.

  A basic size is set for the route section 53. For example, the basic size is 3 × 3 with the corresponding mesh 54 as the center. If the upper road connection node 55 exists in this basic size range, the route section 53 is set to the basic size. However, when the upper road connection node 55 does not exist within the basic size, the route section 53 is appropriately expanded to a range including the upper road connection node 55. The route section 53 illustrated in FIG. 4 is also an example expanded from the basic size.

  FIG. 5 is a diagram for explaining road levels used in route search processing for searching for a route from a departure point to a destination. In the route search processing, first, a partial route that reaches the upper road connection node 55 (not shown in FIG. 5) within the range of the route section 53 determined by the corresponding mesh 54 including the departure point, using the road data 51 of level 0. Explore. In the search using the level 1 road data 51, the upper road connection node 55 connected to the level 2 road starts from the upper road connection node 55 which is the end point of the partial route searched by the level 0 road data 51. Search for partial paths. In the search using the level 2 road data 51, the upper road connection node 55 connected to the level 3 road starts from the upper road connection node 55 that is the end point of the partial route searched by the level 1 road data 51. Search for partial paths.

  Similarly, on the destination side, a partial route from the destination to the upper road connection node 55 is searched using the level 0 road data 51 and connected to the level 2 road using the level 1 road data 51. A partial route to the upper road connection node 55 is searched, and a route to the upper road connection node 55 connected to the level 3 road is searched using the level 2 road data 51.

  In the route search using the level 3 road data 51, the upper road connection node 55 on the side connected to the level 3 road of the partial route searched on the departure side, and the level of the partial route searched on the destination side The route between the upper road connection node 55 on the side connected to the third road is searched.

  Note that the route section 53 is also set at level 3. The level 3 route section 53 is set to include the departure point and the destination. The level 3 route section 53 is also in common with the lower level route section 53 in that it defines a range for route search at a certain level.

<Hierarchical structure of background data>
As shown in FIG. 3, the background data 52 is managed in six layers, and the background data 52 of each level is used properly according to the display scale during the drawing process. For example, the level 0 background data 52 is used for drawing a map when the display scale is set to 1/2000 to 1/10000, and the level 1 background data 52 has a display scale of 1. Used when drawing a map when set to / 80,000 to 1/40000. The background data 52 is also data in mesh units, and the mesh of the background data 52 at the level where the road data 51 exists is a mesh having the same size, shape, and position as the road data 51.

<Description of difference group data>
Next, difference group data will be described. The difference group data includes a plurality of map difference data. Each map difference data is created based on the update of map elements such as roads and facilities. The update of the map element occurs, for example, due to new construction or deletion of roads, addition or deletion of facilities, and the like.

  The difference group data is associated with the mesh ID that is the ID of the mesh, whereby the difference group data is managed in units of meshes. Further, the difference group data is given an ID for identifying the difference group data (hereinafter, difference group ID).

  For example, when the updated map element is a road section sandwiching an intersection, the difference group data is a set of link data and node data representing the road section. As another example, when the updated map element is a facility, it becomes a collection of POI data, character data, and the like representing the facility.

  Difference groups are formed based on the categories and subcategories of map elements. FIG. 6 is a diagram illustrating the categories and subcategories of map elements. Which category (or subcategory) and which category (or subcategory) are to be the same group is set in advance. As an example, a rule is set such that a link indicating a road and a background around the link are set to the same difference group. Difference groups are formed based on this rule in principle.

<Explanation of dependency list>
Next, the dependency list will be described. The dependency list is a list showing the dependency relationship between the difference groups, and the distribution rule that the dependency destination difference group needs to be distributed at the same time as the dependency source difference group or the dependency destination difference group needs to be distributed first. It is the list | wrist which showed the combination of the difference group data which must be followed. The distribution corresponding to one request from the navigation device 3 is counted as one time. Even if the distribution is divided for convenience in relation to the amount of data, etc., it is a single distribution.

  The dependency relationship means that if the data of a certain map element (hereinafter referred to as the first map element) is updated, the data of the other map elements (hereinafter referred to as the second map element) must be updated in advance. This refers to a relationship that causes inconsistency in map data combined with difference group data (hereinafter sometimes simply referred to as map data).

  A typical example of inconsistency occurring in map data is that the first map element is isolated from other map elements. For example, if the map element is a road, it means that the road is not connected to another road. As an example of inconsistency other than isolation, there is a state in which a link that does not have a route reaching the upper road connection node 55 is generated in the route section. A specific example of the latter inconsistency and dependency to avoid it will be described below.

<Avoidance of inconsistency that does not reach upper road connection node 55>
In FIG. 7, a road corresponding to the link L1 (hereinafter simply referred to as the link L1) is newly established, and instead, a road corresponding to the link L2 existing around the link L1 (hereinafter simply referred to as the link L2) is deleted. This is an example. In FIG. 7, white circles indicate nodes, and line segments indicate links. In the example of FIG. 7, there is only one upper road connection node 55 in the route section 53.

  The state of FIG. 7A is a state before the link L2 is deleted and before the link L1 is newly established. All the links in the corresponding mesh 54 can reach the upper road connection node 55 only through the route section 53.

  The state in FIG. 7B shows a state in which the link L1 is added and the link L2 is deleted. Even in the state of FIG. 7B, all the links in the corresponding mesh 54 can reach the upper road connection node 55 only through the route section 53.

  The state of FIG. 7C is an example on the assumption that the difference data indicating the deletion of the link L2 has been distributed, but the difference data indicating the addition of the link L1 has not been distributed. In the state of FIG. 7C, the link L3 in the corresponding mesh 54 cannot reach the upper road connection node 55 only through the route section 53. If the state shown in FIG. 7C is reached, the route search process described above is hindered. Therefore, in this embodiment, the difference data indicating the deletion of the link L2 is distributed, but the difference data indicating the addition of the link L1 is not distributed. Specifically, a dependency relationship is set such that difference data indicating deletion of the link L2 (corresponding to claim link reduction data) depends on difference data indicating addition of the link L1 (corresponding to claim link addition data). To do. Note that the setting condition and determination condition of the claims are that the state shown in FIG.

  When the difference data indicating the deletion of the link L2 is distributed by setting the dependency relationship, if the difference data indicating the addition of the link L1 is not distributed, the difference data indicating the addition of the link L1 is also distributed simultaneously. .

  This dependency relationship is added by the person who creates the dependency list to the dependency list when the difference data indicating the deletion of the link L2 is created and stored in the map difference DB 121.

<Example of dependency list>
FIG. 8 is an example of a dependency list. The example of FIG. 8 is only for explaining the dependency list, and is simplified from the actual dependency list. In the dependency list of FIG. 8, the dependency destination is a dependent side, and if the difference group of the ID of the dependency destination is not distributed to the dependency source, the map data is inconsistent. Since a dependency destination is necessary for a dependency source, the dependency destination is also expressed as a parent and the dependency source is also expressed as a child. In the example of FIG. 8, when the difference group with ID2 is distributed, it is defined by the dependency list that the difference group with ID1 needs to be distributed at the same time or already distributed.

  The difference group is updated at a constant distribution cycle. Therefore, the dependency list is also updated at that cycle. When each delivery for each delivery cycle is distinguished by a release number, the dependence destination and the dependence source set in the dependence list do not necessarily belong to the same numbered release. The dependent difference group may be the same as the dependent difference group or a release distributed in the past.

<Flow of processing in map difference data distribution system 100>
Next, the flow of processing for distributing distribution data will be described with reference to the sequence diagram of FIG.

<T1. Extraction information transmission process (navigation device 3)>
First, the control device 41 of the navigation device 3 (hereinafter simply referred to as the navigation device 3 in FIG. 9) performs difference extraction information transmission processing (t1). The difference extraction information transmission process is performed when a predetermined trigger is detected. The predetermined trigger is, for example, ACC power on of the host vehicle or destination setting in the navigation device 3. The ACC power on of the host vehicle may be detected based on the ACC power on / off signal acquired via the external input I / F unit 33.

  In the difference extraction information transmission process, information for extracting map difference data created after the base map stored in the navigation-side storage device 34 by the map difference extraction server 1 and the update management server 2 (hereinafter, difference) (Extraction information) is transmitted to the update management server 2.

  For example, when the ACC power-on of the host vehicle is detected, the difference extraction information is used to specify the user position (latitude / longitude) detected by the position detector 32, the version of the base map data, and the transmission source. The navigation ID as identification information is included.

  Further, the difference extraction information when the destination setting is detected includes, for example, user position coordinates (latitude / longitude) detected by the position detector 32, destination coordinates (latitude / longitude), and base map data version. , And a navigation ID. If the waypoint is also set, difference extraction information including the coordinates (latitude / longitude) of the waypoint is transmitted. Hereinafter, the processing when the ACC power-on of the host vehicle is detected is distinguished as ACC on, and the processing when the destination setting is detected is distinguished as destination setting.

<T2. Designated information determination process (update management server 2)>
When the management server side control unit 23 (hereinafter referred to as update management server 2 in FIG. 9) of the update management server 2 receives the difference extraction information, the difference extraction information and the update management DB 22 use the navigation management ID for each navigation ID. Compare with the distributed difference group data managed. And the difference group designation | designated information from which the difference group data which should be delivered this time is decided is determined from the collation result (t2). The latitude / longitude, that is, the coordinates included in the extraction information corresponds to the extraction coordinates in the claims.

<T3. Designated information transmission process (update management server 2)>
The update management server 2 transmits the difference group designation information determined at time t2 to the map difference extraction server 1 via the management server side communication unit 21 (t3). Since the coordinates included in the extraction information correspond to the extraction coordinates, the management server side control unit 23 that acquires the coordinates corresponds to the coordinate acquisition unit.

<T4. Difference group extraction processing (map difference extraction server 1)>
When the extraction server side control unit 13 of the map difference extraction server 1 receives the difference group designation information via the extraction server side communication unit 11, the extraction server side control unit 13 of the map difference extraction server 1 (in FIG. 9, Hereinafter, the difference group extraction unit 131 of the map difference extraction server 1 performs difference group extraction processing (t4).

  In the difference group extraction process, a difference group ID to be transmitted to the update management server 2 is extracted from the difference group IDs corresponding to the difference group data stored in the map difference DB 121 based on the received difference group designation information. To do. As an example, the extraction of the difference group ID is performed as follows.

  Regardless of whether the ACC is on or the destination is set, the difference group extraction process extracts the nationwide distribution difference group to be distributed this time. The nationwide distribution difference group is a difference group that is a map element spanning a wide range, such as an expressway, and that is estimated to be updated for all users. Among the nationwide distribution difference groups, those excluding the difference group indicated to have been distributed in the designated information are extracted as the nationwide distribution difference group to be distributed this time.

  As an example, a difference group including a link whose road type is a highway is determined as a nationwide distribution target difference group. The difference group ID of the nationwide distribution target difference group is hereinafter referred to as a nationwide distribution ID.

  In the difference group extraction process when ACC is on, the mesh described above includes at least a part of a mesh in a predetermined rectangular range centered on the latitude and longitude of the user position included in the difference extraction information (hereinafter referred to as a requested rectangular range). Determine the ID. The mesh specified by the mesh ID determined here is an area range in the first difference extraction unit (first difference extraction step) in the claims.

  The predetermined rectangular range is determined based on the average daily action range of the user. And the difference group (henceforth, individual distribution difference group) which is contained in the mesh which the determined mesh ID shows, and has not delivered yet is extracted. In addition, those that overlap with the nationwide distribution target difference group distributed this time are excluded from the extraction target.

  In the difference group extraction process at the time of destination setting, the mesh ID including at least a part of the mesh in the requested rectangular range centered on the latitude / longitude of the user position and the latitude / longitude of the destination included in the difference extraction information is obtained. decide. If the difference extraction information includes the latitude and longitude of the waypoint, the mesh ID including at least a part of the mesh in the requested rectangular range centered on the latitude and longitude of the waypoint is also determined.

  Further, a route search from the user position to the destination is performed, and the mesh ID of the mesh on which the searched route is placed is also determined. The route search may be performed according to a known route search method. Then, a difference group that is included in the mesh indicated by the determined mesh ID and has not been distributed is extracted. This difference group is also called an individual distribution difference group hereinafter. In addition, those that overlap with the nationwide distribution target difference group are not subject to extraction. The difference group ID of the individual distribution difference group is hereinafter referred to as a personal distribution ID.

<T5. Dependent Difference Group Extraction Processing (Map Difference Extraction Server 1)>
When a difference group is extracted, the dependence destination difference group extraction part 132 of the map difference extraction server 1 performs a dependence destination difference group extraction process (t5). In this process, with reference to the dependency list illustrated in FIG. 8, a dependency destination difference group to which the difference group extracted in the difference group extraction process depends is extracted. Note that the dependency destination difference group that has already been distributed to the navigation device 3 specified by the navigation ID is excluded from the extraction target. The difference group ID of the dependency destination difference group is hereinafter referred to as a dependency destination difference ID.

  If no difference group is extracted in the difference group extraction process, the result is returned to the update management server 2 as no difference group, and the processes after t5 are not performed.

  As described above, the dependency list is also set with dependency relationships for avoiding inconsistencies that do not reach the upper road connection node 55. Therefore, by executing this dependency destination difference group extraction process, only the difference data indicating the deletion of the link is distributed as in the example shown in FIG. It is possible to prevent the occurrence of a link that causes no path to reach the connection node 55.

<T6. Difference group ID transmission process (map difference extraction server 1)>
Next, the map difference extraction server 1 performs difference group ID transmission processing (t6). In the difference group ID transmission process, the difference group extracted in the difference data extraction process and the difference group ID of the dependency difference group extracted in the dependency difference group extraction process are transmitted to the update management server 2 via the extraction server side communication unit 11. .

<T7. Unupdated differential group extraction processing (update management server 2)>
Upon receiving the difference group ID, the update management server 2 performs an unupdated difference group extraction process (t7). In the unupdated difference group extraction process, a difference group that has not been distributed to the navigation device 3 (hereinafter referred to as an unupdated difference group) is extracted from the difference groups indicated by the received difference group ID. As an example, an unupdated difference group is extracted by extracting a difference group ID obtained by removing a distributed difference group ID stored in the update management DB 22 from the received difference group ID.

  When an unupdated difference group is not extracted in the unupdated difference group extraction process, the configuration may be such that the result is returned to the map difference extraction server 1 as no unupdated difference group. If there is no unupdated difference group, the processing after t7 is not performed.

<T8. Unupdated differential group transmission processing (update management server 2)>
The management server side control unit 23 performs an unupdated difference group transmission process (t8). In the unupdated difference group transmission process, the difference group ID of the unupdated difference group extracted in the unupdated difference group extraction process is transmitted to the map difference extraction server 1 via the management server side communication unit 21. The difference group ID of the unupdated difference group is hereinafter referred to as an unupdated group ID.

<T9. Distribution data creation processing (map difference extraction server 1)>
When the map difference extraction server 1 receives the unupdated group ID, the distribution data creation unit 133 performs distribution data creation processing (t9). In the distribution data creation process, the difference group extracted by the difference group extraction process, the dependency destination difference group extraction process, and the dependency destination difference group are divided and compressed into data that fits the specified communication size as necessary, and the distribution data Create The created distribution data is stored in a large-capacity storage device such as an HDD.

<T10. Data URL transmission processing (map difference extraction server 1)>
Next, in the map difference extraction server 1, the data URL transmission unit 134 performs a data URL transmission process (t10). In the data URL transmission process, the data URL indicating the address of the distribution data created in the distribution data creation process and stored in the storage device and the difference group ID included in the distribution data are updated via the extraction server side communication unit 11. Send to server 2.

<T11. Data URL Relay Process (Update Management Server 2)>
When the management server side control unit 23 of the update management server 2 receives the data URL transmitted from the map difference extraction server 1 via the management server side communication unit 21, the update management server 2 performs a data URL relay process (t11). ). In the data URL relay process, the received data URL is transmitted to the navigation device 3 via the management server side communication unit 21. Further, the update management server 2 stores the difference group ID transmitted from the map difference extraction server 1 in the update management DB 22 as a distributed difference group ID.

<T12. Difference data acquisition process (navigation device 3)>
When the navigation device 3 receives the data URL transmitted from the update management server 2, the navigation device 3 performs a difference data acquisition process (t12). In the differential data acquisition process, an address indicated by the received data URL is accessed, and transmission of distribution data stored at the address is requested.

<T13. Distribution processing (map difference extraction server 1)>
The map difference extraction server 1 that has received the request performs distribution processing by the distribution unit 135 (t13). Distribution data requested from the navigation device 3 is distributed to the navigation device 3 via the extraction server side communication unit 11.

<T14. Update Process (Navigation Device 3)>
When the distribution data distributed from the map difference extraction server 1 is received, the navigation device 3 stores the distribution data in the map data storage area of the navigation side storage device 34 (t14). At this time, only the storage is performed, and the base map and the difference group are synthesized at a timing (for example, when a route search process is executed) required by an application program that provides guidance based on the map data.

  The distribution data created by the delivery data creation process may be stored in a server other than the map difference extraction server 1. In this case, in the difference data acquisition process, the navigation device 3 requests the server storing the distribution data to transmit the distribution data, and the server storing the distribution data distributes the distribution data.

  As described above, the map difference data distribution system 100 of the present embodiment described above includes a dependency list (FIG. 8) in which dependency relationships for avoiding inconsistencies that do not reach the upper road connection node 55 are set. In addition to extracting the difference group in the area range determined based on the coordinates acquired from the navigation device 3 (t4 in FIG. 9), the dependency relationship with the extracted difference group as the dependency source is displayed in the dependency list (FIG. 8). If set, the dependency destination difference group determined from the dependency list is also extracted (t5). If the dependency destination difference group has not been distributed to the navigation device 3, the dependency destination difference group is also distributed to the navigation device 3. Thus, in place of the deleted road, a new road is newly established near the road, but the route search process of the navigation device 3 cannot search for a route passing through the new road, and makes a detour. It is possible to suppress searching for a route to be performed.

  As mentioned above, although embodiment of this invention was described, this invention is not limited to the above-mentioned embodiment, The following embodiment is also contained in the technical scope of this invention, and also the summary other than the following is also included. Various modifications can be made without departing from the scope.

(Modification 1)
For example, in the above-described embodiment, the difference data indicating the deletion of the link L2 (deletion link) is shown as an example of the link reduction data. There is difference data for links to which restrictions on the directions that can be passed are added.

1: map difference extraction server 2: update management server 3: vehicle navigation device 5: base map data (original map data) 11: extraction server side communication unit 12: extraction server side storage unit 13: extraction Server side control unit, 21: Management server side communication unit, 22: Update management DB, 23: Management server side control unit (coordinate acquisition unit), 51: Road data, 52: Background data, 53: Route section, 54: Corresponding Mesh: 55: upper road connection node; 56: road; 57: road; 100: map difference data distribution system; 121: map difference DB (difference data storage unit); 122: list storage unit (setting state storage unit); : Difference group extraction unit (first difference extraction unit), 132: Dependency difference group Flop extractor (second difference extraction unit), 133: distribution data creation unit, 134: data URL transmission unit, 135: delivery unit

Claims (6)

A vehicle navigation system that includes a map storage device (34) that stores original map data that describes road data in a hierarchical structure that indicates road connection relationships using nodes and links, and performs a route search based on the original map data. For device (3)
A map difference data distribution device (100) for sequentially distributing difference data, which is map data of an updated portion not included in the original map data,
A difference data storage unit (121) for storing the difference data;
In the difference data storage unit, as the difference data, link reduction data corresponding to a reduction link that is a link whose direction in which traffic can be reduced is reduced, and link addition data corresponding to a new road newly established around the reduction link. At least one of each is remembered,
For at least one combination of the link decreases data and the link addition data, said link additional data if not already delivered, defined to be delivered the previous SL links additional data prior to said link reduces data A map difference data distribution device comprising a setting state storage unit (122) that stores distribution rules. In claim 1,
Each layer of the original map data is divided into a plurality of meshes to describe road data, and a lower layer having an upper layer among the layers is a section including the mesh for each of the meshes. A section that includes at least one higher-level road connection node that is also a node that exists in the hierarchy one level above, so that all links in the mesh can reach the higher-level road connection node in the same section A route block is set,
The distribution rule is stored for the link reduction data and the link additional data that satisfy a setting condition,
Assuming that the setting condition is such that the reduced link corresponding to the link reduced data cannot pass and the new road corresponding to the link added data is not added, the same mesh as the reduced link, A map difference data distribution apparatus characterized in that a link is generated in which a route that reaches the upper road connection node does not exist in a route section. In claim 1 or 2,
Coordinates for acquiring extraction coordinates, which are coordinates for setting an area range for extracting difference data to be distributed to the vehicle navigation device from the difference data stored in the difference data storage unit, from the vehicle navigation device An acquisition unit (23);
Based on the extraction coordinates acquired by the coordinate acquisition unit, a region range for extracting difference data to be distributed to the vehicle navigation device is determined from the difference data stored in the difference data storage unit, and the region range is A first difference extraction unit (131) that is included and extracts difference data that has not been distributed to the vehicle navigation device as difference data to be distributed to the vehicle navigation device;
When the difference data extracted by the first difference extraction unit is the link reduction data based on the difference data extracted by the first difference extraction unit and the delivery rule stored in the setting state storage unit, A second difference extraction unit (132) for extracting link addition data distributed together with the link reduction data from the difference data storage unit;
A distribution processing unit (135) for distributing the difference data extracted by the first difference extraction unit and the second difference extraction unit to the vehicle navigation device;
A map difference data distribution device characterized by comprising: The difference data is received from the map difference data distribution device according to any one of claims 1 to 3, and the route is based on the received difference data and the original map data stored in the map storage device. A vehicle navigation device (3) characterized by performing a search process. A navigation device for a vehicle that includes a map storage device that stores original map data that describes road data in a hierarchical structure that indicates road connection relationships using nodes and links, and that performs a route search based on the original map data. A map difference data distribution method for sequentially distributing difference data that is map data of an updated portion not included in the original map data,
Each layer of the original map data is divided into a plurality of meshes to describe road data, and a lower layer having an upper layer among the layers is a section including the mesh for each of the meshes. A section that includes at least one higher-level road connection node that is also a node that exists in the hierarchy one level above, so that all links in the mesh can reach the higher-level road connection node in the same section A route block is set,
The link reduction data corresponding to the reduction link corresponding to the reduction link that is a link whose direction in which traffic can be reduced is distributed to the vehicle navigation device, but the difference data corresponding to the new road newly established around the reduction link. If the link additional data is not distributed to the vehicle navigation device and is not already distributed, there is a route that reaches the upper road connection node in the route section in the same mesh as the reduced link. If the determination condition that a link that does not occur occurs,
The map difference data delivery method, wherein the link addition data is delivered to the vehicle navigation device at one time or before the link reduction data together with the link reduction data. In claim 5,
A coordinate acquisition step of acquiring, from the vehicle navigation device, extraction coordinates that are coordinates for setting an area range for extracting difference data to be distributed to the vehicle navigation device from the difference data storage unit that stores the difference data. (T2),
Based on the extraction coordinates acquired in the coordinate acquisition step, a region range for extracting difference data to be distributed to the vehicle navigation device is determined from the difference data stored in the difference data storage unit, and the region range is A first difference extraction step (t4) that includes difference data that is included and that has not been distributed to the vehicle navigation device as difference data to be distributed to the vehicle navigation device;
The difference data extracted in the first difference extraction step and a rule set in advance based on the determination condition, wherein the link additional data is added once with the link reduction data or before the link reduction data When the difference data extracted in the first difference extraction step is the link reduction data based on the distribution rule defining the combination of the link reduction data to be distributed and the link additional data, the data is distributed together with the link reduction data. A second difference extraction unit (t5) for extracting link addition data to be extracted from the difference data storage unit;
A delivery process step (t13) for delivering the difference data extracted in the first difference extraction step and the second difference extraction step to the vehicle navigation device;
The map difference data delivery method characterized by comprising.

Images