JP2014063085A - Map data distribution device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To realize a fine updating unit so as to prevent a non-contiguous link or node from constituting a single updating unit due to the presence of data commonly referred to from a plurality of links or nodes.SOLUTION: A map data distribution server, including an update data storage part for storing an update element for updating data among maps of a plurality of generations, includes: a dependent relation storage part for storing a dependent relation between update elements; and an update element correlation storage part for storing correlation between update elements. Further, an update element including an update target element of a requested map is retrieved from the update data storage part, and an update element having a dependent relation or correlation with the retrieved update element is retrieved from the dependent relation storage part and an update unit data correlation storage part, to distribute the retrieved update element together with the update element retrieved from the update data storage part.

Description

  The present invention relates to a data distribution apparatus for updating map data.

  As a map data distribution system using differential update data for partially updating map data, Patent Document 1 describes a technique of distributing and updating the road network in units without interruption. In this Patent Document 1, the update element is configured and distributed as a set of related object units of the changed difference update data.

  Further, Patent Document 2 discloses a technique for changing the update level according to the road type and changing the update level according to the distance from the designated point.

JP2007-241033 JP2007-132711A

  In general, map data used in a navigation terminal includes not only links and node road network data but also a lot of additional information such as road names and highways. These additional information is data commonly referred to from a plurality of links and nodes (hereinafter referred to as a common reference object).

  If the conventional update element creation method is applied to map data with such a data structure, each changed update data that has been changed is collected as a set of units in which the road network is not interrupted, and further inconsistent with the updated map Therefore, it is necessary to generate an update element for all the common reference objects that have changed in order to prevent the occurrence of the problem. In this case, there is a case in which one update element exists even if the link or node in which the change has occurred is discontinuous through the common reference object in which the change has occurred.

  In addition, in order to update the map data sequentially by applying multiple generations of update elements, update elements that are related between generations are applied from the oldest to prevent inconsistencies in the final updated map. There is a need to. When multiple generations of update elements created by the conventional update element creation method are applied, there may be cases where differential update data not directly related to certain differential update data is also applied.

  Furthermore, Patent Document 2 discloses a technique of dividing road types and updating according to the distance from the designated point. However, in this method, the road of the updated map road is located at a location away from the designated point. Connectivity may be lost.

  The present invention subdivides information that a user wants to update, and enables an update element creation method and an update element created thereby to enable map update in a finer update unit so that inconsistency does not occur in updated map data The map data distribution apparatus which distributes is provided.

  The present invention relates to a map data storage unit for storing multiple generations of map data and an update element that summarizes difference update data for updating map data between generations for each generation of map data, such as links and nodes. In a map data distribution server provided with an update data storage unit for storing an update element, a dependency relationship storage unit for storing a dependency relationship between an update element and a past generation update element, and an update element related storage unit for storing a relationship between the update elements Update data extraction means for creating an update element from the difference information between the map data of the previous generation and the map data of the current generation, and building the relationship between the created update element and the update element of the previous generation In accordance with the map data update request from the navigation terminal, the requested map update target element is Search the update data storage unit for update elements that summarize the differential update data, search for update elements that are dependent or related to the searched update element from the dependency storage unit and the update unit data related storage unit, A map data distribution unit that distributes to the navigation terminal together with the update element retrieved from the update data storage unit is further provided.

  In this way, the update element creation unit is a continuous link, a set of nodes, or a single object that is commonly referenced from the link and node, thereby reducing the size of each update element. By reducing the size of the update element, the relationship information between the update elements is stored in the dependency relationship storage unit and the update element relationship storage unit so that inconsistency does not occur in the updated map on the navigation terminal when a single update element is applied. In order not to cause inconsistency when distributing update elements, search for related information between update elements and distribute related update elements at the same time. Avoid alignment.

  According to the present invention, a common reference object that is commonly referred to from a plurality of objects, such as a road name and a road regulation, is configured as another update element, and the relationship between the update elements is managed separately. Since links and nodes that are not present can be grouped into different update elements and each update element can be reduced in size, map data can be distributed in fine units.

The block diagram of the map data delivery system using this invention. The figure explaining an update element. The figure explaining the update element preparation method of the map between two generations. The figure explaining the update element preparation method of the map between three generations. The flowchart of the process in an update data extraction part. The flowchart of the process which updates the map data of a navigation terminal. The figure which shows the data structure of an update data memory | storage part. The figure which shows the data structure of a dependence relationship memory | storage part. The figure which shows the data structure of the update element relevant storage part. The figure which shows the data structure of an update management part.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a diagram of a map data distribution system to which an embodiment of the present invention is applied. The map distribution server 10 according to the present embodiment includes a map data storage unit 12 that stores map data of the previous generation and map data of the current generation, an update data storage unit 11 that records update element entities and attribute information, and an update. A dependency storage unit 13 that stores a dependency relationship between an element and an update element of a previous generation, an update element related storage unit 14 that stores a relationship (element related attribute) between update elements, and a generation before An update element is created from the difference information between the map data and the current generation map data, and an update data extraction unit 15 that builds a relationship between the relationship between the update elements and the update element of the previous generation, and the navigation terminal 20 Search for an update element to be distributed in response to a map data update request, and distribute the update element to the navigation terminal 20 And a map data delivery unit 16.

  The navigation terminal 20 sends the update element distribution request to the map data storage unit 24 that stores the map data, the map distribution server 10, receives the update element, and receives the update element, and the map based on the received update element information. A map update unit 23 that updates the map data in the data storage unit 24, an update management unit 25 that manages the history of update elements applied to the navigation terminal, and a navigation processing unit that has a navigation function based on the map data in the map data storage unit 24 21 is provided.

  First, an example of the update element will be described with reference to FIG. Assume that Ver1 in FIG. 2 is a map of the previous generation, and Ver2 in FIG. 2 is a map of the current generation. A thick solid line in the figure is a link 202 representing road data, and a circle in the figure is a node 201 that couples the links. A section in the figure is a parcel (mesh) 203 representing a management unit of map data managed by the navigation terminal. The changed difference data is referred to as difference update data, and the difference update data as a set of continuous links and nodes is referred to as an update element. A portion surrounded by a broken line of Ver2 corresponds to this update element.

  Next, an update element creation method in the case where a common reference object exists will be described with reference to FIG. FIG. 3 represents the map change that occurred between the two generations. Ver1 is a map of the previous generation, and Ver2 is a map of the current generation. In the Ver1 map, there are continuous rows of nodes and links across a plurality of areas. In the Ver2 map, thick solid-line links L1 and L2 are newly added to the Ver1 map, and an object A that is commonly referenced from the links L1 and L2 is newly added.

  When a conventional update element creation method for creating an update element by collecting related difference update data is applied to the change in map information from Ver1 to Ver2, it is common to link L1 and link L2 in the Ver2 map. In order to prevent inconsistency in the updated map with the new addition of the object A referred to in FIG. 2, the difference update data indicating the addition of the link L1, the difference update data indicating the addition of the link L2, and the object A These three pieces of difference update data constitute one update element.

  On the other hand, when the update element creation method according to the present invention is applied, an object A that is commonly referenced from a plurality of links and nodes is created as a single update element E1. Further, the difference update data of the links L1 and L2 whose changes are discontinuous are assumed to be different update elements E2 and E3, respectively.

  Thereby, since each update element can be distributed individually, it is possible to suppress transmission of unnecessary difference update data and reduce the amount of distribution data.

  At this time, since the directly related differential update data is collected and becomes different update elements, when the update element E2 and the update element E3 are distributed, if the update element E1 is not distributed, the update map E1 is not updated. Consistency may occur. Therefore, the map distribution server 10 is provided with the update element relation storage unit 14 to store element relation attribute information relating to the relation from the update element E2 to the update element E1 and the relation from the update element E3 to the update element E1.

  When the update element is distributed, the update data distribution unit 16 retrieves the relevance of the update element from the update element relation storage unit 14, and when the update element E2 is distributed, the update element E1 having the relevance with the update element E2 In the same manner, when the update element E3 is distributed, the update element E1 having relevance is also distributed, thereby preventing inconsistency in the updated map to which the distributed update element is applied.

  Next, the relationship of update elements between multiple generations will be described using FIG. FIG. 4 shows the map information further changed from the Ver2 generation map shown in FIG. 3, where Ver3 is the current generation map, Ver2 is the previous generation map, and Ver1 is the second generation map. It shows the change of the map during. In Ver1, there are continuous nodes and links across a plurality of areas. In Ver2, thick solid links L1 and L2 are added to Ver1, and a common reference object A that is commonly referenced from the links L1 and L2 is added. In the newly added Ver3 map, a thick solid line link L3 is added to the Ver2 map, and the common reference object A referenced from the link L3 is changed to the common reference object B.

  When the conventional update element creation method is applied to this change in map information, the difference update data to which the common reference object A is added and the link L1 to be related through this data are added in Ver2. The difference update data and the additional difference update data of the link L2 are combined to create an update element. Similarly, in Ver3, the difference update data for adding the link L3 and the difference update data for updating the common reference object A to the common reference object B are combined to create an update element. In addition, when the Ver3 update element is distributed, it is necessary to distribute the Ver2 update element so that inconsistency does not occur in the updated map. Therefore, a dependency relationship from the update element of Ver3 to the update element of Ver2 is given.

  However, since the update elements of Ver3 and Ver2 are both configured as a set of a plurality of difference update data, when the difference update data is distributed to add the link L3 on the Ver3 map, the update elements are consecutive. The difference update data of the link L2 and the link L1 that are not present are also delivered simultaneously.

  Next, the relationship of update elements between generations when the update element creation method according to the present invention is applied will be described with reference to FIG. In the Ver2 map, as in the description with reference to FIG. 3, the individual update elements E <b> 1, respectively, from the difference update data for adding the common reference object A, the difference update data for adding the link L <b> 1, and the difference update data for adding the link L <b> 2. E2 and E3 are created, and an element-related attribute from the update element E2 to the update element E1 and an element-related attribute from the update element E3 to the update element E1 are given and stored in the update element-related storage unit 14.

  In the Ver3 map, individual update elements E4 and E5 are created from the difference update data for updating the common reference object A to the common reference object B and the difference update data for adding the link L3, and updated from the update element E5. An element-related attribute is given to the element E4 and stored in the update element-related storage unit 14.

  Further, the dependency relationship from the update element E4 to the update element E1 is registered in the dependency relationship storage unit 13 of the map distribution server 10 so that inconsistency does not occur in the updated map even when a plurality of generation update elements are applied.

  At the time of update element distribution, the update data distribution unit 16 searches the update element relation storage unit 14 for the relationship of the update element to be distributed, and searches the dependency relation storage unit 13 for the dependency relationship with the update element of the past generation. To deliver. In the case of the example of FIG. 4, when the update element E5 of Ver3 is distributed, only the update element E4 related to the update element E5 and the update element E1 having a dependency relationship with the update element E4 are distributed. Therefore, since the difference update data of the link L2 and the link L1 is not distributed, the distribution data amount can be reduced.

  FIG. 7 is a diagram illustrating a data structure of the update data storage unit 11. As shown here, the update data storage unit 11 creates an “update element ID” that uniquely identifies an update element, an “affiliation area” that identifies which area the update element belongs to, and for which generation the update element belongs to "Data version" that identifies whether the update element is owned, "attribute information" that identifies what attribute information the update element has, "dependency building information" required for intergenerational dependency construction, and update data It has an “update element entity” that is an entity. The column of “attribute information” does not have to be one, and a plurality of columns may be provided according to the map data distribution pattern.

  FIG. 8 is a diagram illustrating a data structure of the dependency relationship storage unit 13. The dependency relationship storage unit 13 stores update element IDs of past generations that need to be applied in advance for a certain update element. This dependency relationship storage unit 13 includes an “update element ID” that uniquely identifies the update element that is the source, a “data version” that indicates the generation in which the update element is generated, and updates of update elements of past generations on which the update element depends The “dependent update element ID” that is an element ID and the “dependent data version” that indicates the generation in which the update element of the dependent update element ID is generated are stored.

  FIG. 9 is a diagram illustrating a data structure of the update element related storage unit 14. The element-related attribute from one update element to another update element is recorded in the update element-related storage unit 14, but in this embodiment, as the element-related attribute, “update element ID” and related to the update element The correspondence relationship of “related update element ID” which is the update element ID of the update element to be stored is stored. The update element relation storage unit 14 stores data such that the correspondence between the update element ID and the related update element ID is unique.

  FIG. 10 is a diagram illustrating a data structure of the update management unit 25 of the navigation terminal 20. The update management unit 25 stores information on update elements that have been applied to the map data stored in the map data storage unit 24 of the navigation burden 20. Specifically, an “applied update element ID” that is an update element ID of an update element that has already been applied and a “data version” of the update element are stored.

  FIG. 5 is a flowchart showing processing in the update data extraction unit 15 of the map distribution server 10 of FIG. The update data extraction unit 15 first extracts difference information between a previous generation map as a reference for obtaining a difference and a current generation map as a processing target (S501). Next, the common reference object and other data are classified (S502). In the example of FIG. 4, the difference update data for adding the common reference object A or the difference update data for updating the common reference object A to the common reference object B is the common reference object, and the link L1 and the link L2 are added. Difference update data or the difference update data to which the link L3 is added is data other than the common reference object.

  Returning to the description of FIG. Next, the common reference object is created as a single update element, and the update element entity data (update element entity) and the detailed attribute information of the update element are registered in the update data storage unit 11 (S503). In the example of FIG. 4, the update elements E1 and E4 correspond to update element entities.

  Next, differential update data other than the common reference object is collected in units of continuous link differential update data to create an update element. The update element created in this way is a set of differential update data in a section in which changed links are continuous. Then, the created update element entity and its detailed attribute information are registered in the update data storage unit 11 (S504). In the example of FIG. 4, update elements E2, E3, and E5 correspond to this.

  Next, the element relation attribute between the update elements is registered in the update element relation storage unit 14 as the relation between the update elements so that inconsistency does not occur in the updated map (S505). In the example of FIG. 4, the element-related attribute from the update element E2 to the update element E1, the element-related attribute from the update element E3 to the update element E1, and the element-related attribute from the update element E5 to the update element E4 are updated as relevance. It is registered in the element relation storage unit 14.

  Next, in order to make it possible to apply update elements of multiple generations, update element IDs of past generations on which the generated update elements depend are retrieved from the update data storage unit 11 and registered in the dependency relationship storage unit 13 (S506). In the example of FIG. 4, the dependency relationship from the update element E4 to the update element E1 corresponds to this.

  FIG. 6 is a flowchart showing operations from when the navigation terminal 20 makes a map data update request to the map distribution server 10 until the navigation terminal 20 updates the map data.

The map distribution server 10 receives the map data update request from the navigation terminal 20 and accepts this request (S611).
In response to this map data update request from the navigation terminal 20, the map distribution server 10 searches the update data storage unit 11 for an update element to be distributed (612). This search condition is determined based on information included in the map data update request received from the navigation terminal 20, and for example, as a search condition to be updated, for a specified area, for each road type, for each facility Updates can be specified. This search condition pattern is determined in advance between the navigation terminal 20 side and the map distribution server 10.

  Next, the map distribution server 10 searches the update element related storage unit 14 based on the update element ID of the update element as a result of search from the update data storage unit 11, and the update element searched from the update data storage unit 11 The update element ID of the update element having relevance that needs to be distributed is also searched (S613).

  Next, the map distribution server 10 searches the dependency storage unit 13 based on the update element ID searched from the update data storage unit 11 and the related update element ID searched from the update element relation storage unit 14, and applies in advance. The dependent update element ID that is the element ID of the update element that depends on the past generation that needs to be searched is searched (S614).

  Thus, the update element ID, the related update element ID, and the dependent update element ID searched based on the map data update request from the navigation terminal 20 are necessary so that the update of the requested map data does not cause inconsistency. The update element ID list (hereinafter referred to as the update target element ID list) is transmitted to the navigation terminal 20 (S615).

  When the navigation terminal 20 receives the update target element ID list transmitted from the map distribution server 10 (S622), the navigation terminal 20 performs a loop process for each update element in the update target element ID list (S623) and sends the update target sent thereto. The update management unit 25 on the navigation terminal 20 is searched for each update element in the element ID list, and it is determined whether the update element has already been applied (S624), and the update element ID of the update element determined to be unapplied is determined. It is registered in a list of unapplied update elements (hereinafter referred to as an unapplied update element list) (S625). Then, the unapplied update element list is transmitted to the map distribution server 10 to request transmission of the unapplied update element (S626).

  When the map distribution server 10 receives the unapplied update element list transmitted from the navigation terminal 20 and accepts a transmission request for the unapplied update element (S616), the map distribution server 10 based on the contents of the unapplied update element list. An update element to be distributed is searched from the update data storage unit 11 on 10 (S617), and the corresponding update element is distributed to the navigation terminal 20 (S618).

  The navigation terminal 20 receives the update element sent from the map distribution server 10 (S627), updates the map information on the navigation terminal 20 by applying the received update element (S628), and simultaneously maps from the next time onwards. In preparation for the update, the update element ID of the update element that has been applied is registered in the update management unit 25 on the navigation terminal 20.

  In this way, after configuring a common reference object that is commonly referred to by multiple update elements, such as road names and road regulations, as separate update elements, relationships such as the relationship and dependency of each update element By adopting a configuration in which the dependency relationship storage unit 13 and the update element related storage unit 14 are separately managed, it becomes possible to configure an update element by combining non-continuous links and nodes into another update element. Since each update element can be downsized, distribution of the update element is facilitated.

10 Map distribution server,
DESCRIPTION OF SYMBOLS 11 Update data memory | storage part 12 Map data memory | storage part 13 Dependency relationship memory | storage part 14 Update element related memory | storage part 15 Update data extraction part 16 Map data delivery part 20 Navigation terminal 21 Navigation processing part 22 Delivery request part 23 Map update part 24 Map data memory | storage Unit 25 Update management unit 51 Map data update request 52 Update element

Claims (3)

Map data storage unit for storing multiple generations of map data, and update data storage for storing update unit data that summarizes differential update data for updating map data between generations for each generation of map data In the map data distribution device provided with a section,
A dependency storage unit that stores the dependency relationship between the update unit data and the update unit data of the past generation, and an update unit data related storage unit that stores the relationship between the update unit data;
Update data extraction that creates update unit data from the difference information between the previous generation map data and the current generation map data, and builds the dependency between the created update unit data and the past generation update unit data Means,
With
In accordance with the map data update request from the navigation terminal, the update unit data including the difference update data including the update target element of the requested map is searched from the update data storage unit, and the searched update unit data is dependent or related. And a map data distribution unit that retrieves the update unit data from the dependency relationship storage unit and the update unit data relation storage unit and distributes the update unit data to the navigation terminal together with the update unit data retrieved from the update data storage unit. Map data distribution device. The map data distribution device according to claim 1, wherein the dependency storage unit stores a relationship between update unit data including differential update data commonly referred to from a plurality of differential update data and other update unit data. ,
The map data distribution unit is differential update data that is commonly referred to from the plurality of differential update data having relevance with the update unit data retrieved from the update data storage unit so that no inconsistency occurs in the updated map. A map data distribution apparatus for searching for and distributing update unit data comprising:   3. The map data distribution device according to claim 2, wherein when the update elements of a plurality of generations are applied to the map data of the navigation terminal, the update unit data related storage unit is configured so that inconsistency does not occur in the map data after application. Records a dependency relationship between generations of differential update data commonly referred to from the plurality of differential update data, and the map data distribution unit stores the update unit data relation storage unit in the dependency relationship storage unit. A map data distribution device for searching and distributing update unit data on which differential update data commonly referred to from the plurality of differential update data is dependent.