JP2017223797A - Map update data management device, map data update system and update data structure for map - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a map update data management device capable of shortening an interval of map data correction processing or the like and preventing a conflict from being generated in correction or the like of a road network over multiple differential files.SOLUTION: Map data including at least network information of roads are handled as an aggregate of map data for each mesh corresponding to a predetermined area. The map data at a predetermined time point are defined as a reference, (n+1)th differential data are successively generated as a differential of the map data that are updated by n-th ((n) is a natural number equal to or greater than 1) while defining the mesh as a unit. An identifier capable of identifying differential data before the n-th differential data is added to the (n+1)th differential data, and differential data until the (n+1)th differential data are preserved. Thus, even if map data are corrected within a short period of time, differential data to be used for update can be easily identified, and a road map can be updated without conflict.SELECTED DRAWING: Figure 2

Description

  The present invention relates to management of update data of a map.

  In recent years, with the development of navigation technology, maps are referred to in various forms such as personal navigation that operates with a smart phone or the like as well as a car navigation device, and a device that uses a dedicated small terminal. In such a map reference, there is a problem of how quickly and accurately the map data is updated. If an old map remains as it is, it may occur that a route that cannot be passed is guided or a route that can be opened and passed is not guided, which may impair the convenience of the user. For this reason, techniques for updating maps have been proposed (for example, Patent Documents 1 and 2 below).

JP 2011-158339 A JP 2010-224442 A

  In Patent Document 1, the map is updated in units of finely divided meshes so that the amount of information reflecting the modification of the road falls within a certain range. Further, in Patent Document 2, an attempt is made to easily update the map by providing map difference information for each predetermined period.

  It is an object of the present invention to provide a map update data management apparatus, a map update data management system, and a data structure of data used for the map update data management apparatus capable of appropriate updating.

  SUMMARY An advantage of some aspects of the invention is to solve at least a part of the problems described above, and the invention can be implemented as the following aspects or application examples.

  As one embodiment, the map update data management apparatus handles map data including at least road network information as a set of map data for each mesh corresponding to a predetermined area, and the map data at a predetermined time point is As a reference, the (n + 1) th difference data is generated in units of the mesh as the difference from the map data updated by the difference data up to the nth time (n is a natural number of 1 or more), and the generated A difference data storage unit that stores the (n + 1) th difference data; and an identifier adding unit that assigns an identifier that can be distinguished from the difference data before the nth time to the (n + 1) th difference data. The storage unit is provided with a map update data management device that sequentially stores the difference data up to the (n + 1) th difference data.

  Moreover, as one embodiment, there is a map data update system for updating existing map data stored in a device that performs at least processing using a map, using map update data stored in a server, wherein the server includes: , Map data including at least road network information is treated as a set of map data for each mesh corresponding to a predetermined area, and the (n + 1) th difference data is the nth time based on the map data at a predetermined time point. As the difference from the map data updated with the difference data up to (n is a natural number equal to or greater than 1), the first to (n + 1) th difference data generated from the first to the (n + 1) th difference is generated as an identifier. A difference data storage unit for identifiably storing using the device, and communicating with the device to update the map data of the device A determination unit that determines a situation using the identifier, the device receives the difference data by communicating with a map data storage unit that stores map data and the server, and has already been applied to the m-th time. An update unit that specifies difference data after (m <n + 1) using the identifier, and updates the map data by sequentially applying the difference data from the (m + 1) th time to the (n + 1) th time in units of the mesh. A map data update system is provided.

  Further, as one embodiment, the map update data structure for updating the map data, the map data including at least the network information of the road is handled as a set of map data for each mesh corresponding to a predetermined area, Using the map data recorded at a predetermined time as a reference, the mesh is used as a difference between the (n + 1) th difference data and the map data updated with the difference data up to the nth time (n is a natural number of 1 or more). Update for maps in which the mth (m is an integer between 1 and n) generated as a unit and the (n + 1) th difference data are stored in a file format on a recording medium together with an identifier for identifying each difference data. A data structure is provided.

  In one embodiment, the map update data management device includes a predetermined type of content included in a first mesh corresponding to a first region in map data, and the first in the map data. Group information indicating that the predetermined type of content included in the second mesh corresponding to the second region adjacent to the region is the same group, and using the group information, the first mesh A map data management device comprising: an update unit that controls to update the predetermined type of content included in the second mesh when the predetermined type of content included in the second mesh is updated Is provided.

  Also, as one embodiment, a predetermined type of content included in the first mesh corresponding to the first region in the map data, the data structure of the update management data used for updating the map data And group information indicating that the predetermined type of content included in the second mesh corresponding to the second region adjacent to the first region in the map data is the same group, The group information is a process for controlling so that the predetermined type of content included in the second mesh is also updated when the predetermined type of content included in the first mesh is updated. A data structure of update management data to be used is provided.

The schematic block diagram which shows the map data update system of embodiment. The block diagram which shows the function of each part of the map update data management apparatus, update server, and vehicle which comprise a map data update system. The flowchart which shows the authoring process which a map update data management apparatus performs. Explanatory drawing explaining the state of the map data before and behind update. Explanatory drawing which shows the update data of the road network put together into one group. Explanatory drawing which shows the other example of the update data of the road network put together into one group. The flowchart which shows the update process routine of the map of the vehicle side and the update server side. Explanatory drawing which shows the preparation status of the catalog which collected the content of the change within the predetermined period of a map according to area. Explanatory drawing which shows the application condition of the catalog in the vehicle side for every area. The flowchart which shows the update management process routine performed by the update server side. Explanatory drawing which shows the version number for every group which compiled the correction | amendment of the road network, and the mesh number updated. Explanatory drawing which shows a mode that the version number of the mesh by which correction of a road network is made is updated in relation to another group.

A. Embodiment:
FIG. 1 is a schematic configuration diagram of a map data update system 10. As shown in the figure, a map data update system 10 includes a map update data management device 20, an update server 30 connected to the map update data management device 20 through a dedicated line 11, and the update server 30 is a wide area such as the Internet. It is composed of base stations 40 and 50 connected by a network (hereinafter referred to as WAN) 12. Each base station 40, 50 can communicate data with vehicles 41, 43, 51, 52, etc. traveling on the ground using 3G or 4G wireless communication technology used for mobile phones and the like.

  As shown in FIG. 2, the map update data management device 20, the update server 30, the vehicle 41, etc. are closely linked in that they exchange map update data. As a whole, the map data update system 10 Is realized. The map update data management device 20 includes a difference data generation unit 21, an identifier assignment unit 22, and a data storage unit 23. As will be described later, the difference data generation unit 21 generates difference data between once generated map data (hereinafter referred to as reference map data) and map data after a predetermined period has elapsed. The map data includes surface elevation, data of features such as rivers, railways / stations, roads, parks, and facilities, and road network data representing the connection relationship between roads. The road network data representing the connection relationship between the roads is a set of data representing the connection relationship between the links divided into links constituting the road. A connection point between links may be managed as a node. Each link is assigned a unique ID (hereinafter referred to as RID), and each link is managed by this RID. The road network data is a set of information on how links that can be identified by RID are connected.

  Road network data is generally used for navigation and automatic driving in vehicles. For this reason, the reference map data needs to cover a range where navigation or the like is performed. For example, in the case of Japan, the reference map data includes road network data of all over Japan. For the convenience of managing maps, it is not practical to treat Japan as a single data because the amount of information contained in the map data becomes too large. Therefore, the target area is divided into areas of a predetermined size (hereinafter referred to as meshes), and data is managed in units of meshes. The size of the mesh is determined based on ease of management. In this embodiment, it is several kilometers square.

  Map data including road network data used for navigation and autonomous driving can be obtained at a certain point even if reference map data including road network data is created by specifying the state of the target region, for example, the whole country of Japan. Since feature data is constantly changing, it is necessary to update to the latest data in as short a time as possible. The data to be updated is the difference data created by the difference data generation unit 21. In the present embodiment, the difference data generation unit 21 generates difference data for a target area about every two weeks. Also, for the convenience of generating difference data within a short period of time, instead of making difference data for all of Japan at once, for each region, for example, Hokkaido, Tohoku, Kanto, Chubu ... Generate difference data. Difference data may be generated in units of smaller units, for example, prefectures.

  In this embodiment, the difference data is generated by inputting new data from a terminal (not shown) by an operator in charge of updating the map data of the area. Alternatively, it may be automatically generated based on travel data from the probe car. The difference data generation process will be described in detail later.

  The identifier assigning unit 22 of the map update data management device 20 assigns an identifier for distinguishing a plurality of difference data when they are sequentially generated in time series. Any identifier can be used as long as it is unique so that the difference data can be distinguished, and it is sufficient that the time series of the difference data can be identified. For example, a numerical value that monotonously increases or decreases with time series, such as a version number, may be added to the difference data. Alternatively, it may be a unique number created by a hash function. In the case of such numbers, when the next difference data is created and a new number is assigned, a management table that connects these numbers with a pointer is created, and the connection relationship of unique numbers generated by a hash function etc. Should be recorded.

  The data storage unit 23 stores the difference data generated by the difference data generation unit 21 and provided with the identifier by the identifier adding unit 22, and outputs it in response to an external request. Since a plurality of difference data are generated, a data storage device such as a hard disk having a capacity for storing these data, and necessary data are taken out from the data storage device and requested to the update server 30 in the present embodiment. Any configuration can be used as long as it can output. Since the difference data is usually handled in the form of a file, it can be realized by a computer having a database function that operates under an OS having some kind of file management system. Of course, the map update data management device 20 itself may be realized by a necessary computer, or may be realized by a different computer for each unit.

  The update server 30 is a server for updating map data included in the vehicle 41 or the like in response to a request from the vehicle 41 or the like. The update server 30 includes a management unit 31 and an update data storage unit 32. The update data storage unit 32 obtains the difference data managed by the map update data management device 20 according to the type of the vehicle 41 and the like managed by the update data storage device 20, and stores this. Map data according to the navigation system provided in the vehicle 41 or the like is required. Accordingly, the management unit 31 of the update server 30 corresponds to the type of vehicle such as the vehicle 41 that requested the data, and if necessary, rearranges the data and matches the format, and directs the WAN 12 to the vehicle 41 and the like. Send through. The process in which the update server 30 prepares update data in response to a request from the vehicle will be described later.

  The vehicle 41 or the like includes an update unit 61, a map data storage unit 62, a navigation control unit 65, and the like. The navigation control unit 65 performs so-called route search based on the map data stored in the map data storage unit 62, and guides the route on which the vehicle travels to the destination while displaying the map. For this navigation, it is desirable to keep the map close to the actual road conditions. Therefore, the update unit 61 acquires update data from the update server 30 as necessary, and updates the map data stored in the map data storage unit 62.

  Next, the authoring process will be described with reference to FIG. In order to realize the map data update system 10 described with reference to FIGS. 1 and 2, difference data reflecting changes in roads and features from the reference map data created at a predetermined time. Processing to generate is required. This is the map authoring process. This process may be performed in the map update data management apparatus 20 shown in FIG. 1, or may be performed by a completely different apparatus or system.

  The premise of the map authoring process is the existence of reference map data created as a reflection of the state of roads and features at a predetermined time. In the authoring process, changes from the reference map data are sequentially generated as difference data in time series. When the process shown in FIG. 3 is started, an authoring area is first identified (step S100). The region may be a district such as Hokkaido, Tohoku, or the like, or an administrative boundary such as a prefecture or a municipality. Or you may decide in geometrical ranges, such as 20 kilometers square. You may use the mesh itself mentioned later.

  When the area to be authored is specified, the latest map data of the specified area, that is, reference map data is called (step S110). Processing for storing the version number n of the reference map data is performed (step S120). In this embodiment, version numbers that are sequentially incremented are used as identifiers.

  Then, the process which corrects a map is performed (step S130). Modifying a map is a process of adding links identified by RIDs or adding / modifying information of connections with other existing links when a road is newly established, if it is road network data. If a new road is created between an existing road and another existing road, a link with a new RID will be provided corresponding to the new road. When the link is connected, the link is divided at the connection point and replaced with a new link. When the correction of the map is completed, the map is saved (step S140), and the version number n + 1 is assigned to the new map (step S150).

  FIG. 4 is an explanatory diagram showing an example of such a map update. It is assumed that the roads before the change and having RIDs 31, 32, and 33 exist in the road network (road NW), the version is 1, and this is the latest data. In this road NW, it is assumed that a new road is newly added to the illustrated information of the road of RID31 and a new branch is provided to the road of RID32. In this case, not only a new road with RID 111 is added to the road NW, but the road with RID 32 is deleted, and new roads RID 112, 113, and 114 are added. The roads of RID 31 and 33 are not changed and are maintained as they are. However, since these are roads related to the deletion of the road of RID 32 and the newly added road, the version of all these roads is 2. Since the correction of the road occurs individually, if the correction is repeated, the version n is incremented each time, but the version of the road NW that is not corrected is left with the old number. Therefore, when the correction proceeds, a plurality of versions of data are mixed in the road NW.

  In FIG. 4, the correction for the road NW is illustrated, but the map data includes feature data in addition to the road NW. Corrections are also made to these feature data. For example, if a facility is newly established or abolished, these are also treated as corrections to map data. Although not shown in particular, such a difference in correction target is handled as a content type representing a predetermined type of content, and is recorded separately from the data of the road NW.

  When the correction of the map for the identified area is completed, the version n map is compared with the version n + 1 map to generate difference data (step S160). The difference data is generated by collecting the corrected road NW data (an example of which is shown in FIG. 4) generated for each map correction operation. Of course, the map after the correction work is completed may be compared with the map before the correction.

  The generation of difference data is performed by treating the range covered by one road change as one group. FIG. 5 shows an example of generation of difference data. In the example of FIG. 5, a version n = 3 and a new road connecting two roads existing in the meshes MS <b> 1 to 9 are created with version n = 4. In this case, the correction of the road covers the meshes MS1, 3, 4-6. These road corrections in the mesh MS are recorded as the group ID 100. Since each road RID is recorded in association with one of the meshes MS, not only the meshes MS4 to 6 in which roads are newly established, but also roads connected to roads existing in these meshes are recorded. The mesh is also recorded as a modified mesh that belongs to the group ID 100. The group ID in the embodiment is an example of group information indicating that predetermined types of content are the same group. The table shown at the bottom of FIG. 5 shows a range that can be corrected by one group ID. The content of the change of the road NW in each mesh is recorded separately.

  The change shown in FIG. 5 is an example when version 4 is updated. The generation of such difference data is sequentially performed for all the specified regions, and if all the difference data in version n + 1 = 4 is generated (step S160), it is determined whether all correction operations have been completed ( Step S170) If there is another area to be corrected, the process returns to Step S100 and the above processing is repeated. When the processing for all the areas that require correction work is completed, the process exits to “END” and ends the authoring process.

  By the authoring process described above, difference data for each region is created sequentially. Even if attention is paid to one area, the map data is updated many times over a predetermined period, so that difference files having different version numbers are created as many times as the number of times the update is performed. In each difference file, the version number of each mesh included in the difference file is the version number when the correction is performed. The process of generating difference data by the authoring process shown in FIG. 3 corresponds to the difference data generation unit 21 shown in FIG. 2, and the process of adding the version number n + 1 to the difference data in the authoring process of FIG. This corresponds to the identifier assigning unit 22 shown in FIG.

  The differential data generated in this way and the identifier assigned thereto are temporarily stored in the data storage unit 23 and are appropriately transmitted to the update server 30 via the dedicated line 11. The update server 30 that has received the difference data with the identifier stores and manages the difference data in the update data storage unit 32 by the management unit 31. The management unit 31 reads the difference data and the like from the update data storage unit 32 and exchanges with the vehicle 41 (43, 51, 52) by the process described below. The vehicle 41 or the like includes a map data storage unit 62, and a navigation control unit displays a map on a display (not shown) or provides route guidance using map data including road NW data stored therein. The vehicle 41 or the like operates the update unit 61 according to a user instruction, connects to the update server 30 via the WAN 12 such as the Internet, receives necessary difference data, and stores the map stored in the map data storage unit 62 Update the data.

  Such map data update processing will be described with reference to FIG. FIG. 7 is an explanatory diagram illustrating in parallel a vehicle-side map update process routine performed by the update unit 61 such as the vehicle 41 and an update server-side update process routine performed by the management unit 31 of the update server 30. This process is started from the vehicle side. When a user such as the vehicle 41 desires to update map data used for in-vehicle navigation, the update unit 61 inquires of the update server 30 about an update catalog (step S200). The update catalog is data indicating the update status for each region. An example of the update catalog is shown in FIG. In this example, the update catalog is divided for each region such as Hokkaido, Tohoku,..., And a catalog number is given according to the difference in the last update date. Since the authoring cycle and schedule differ depending on the region, the maximum value of the catalog number and the last update date are also different. Receiving the inquiry, the update server 30 transmits the catalog list managed by the management unit 31 to the vehicle side (step S300). In this embodiment, the catalog number and the version number n + 1 at the time of update are the same number.

This catalog is stored in the update data storage unit 32 in the update server 30.
"District name" + "Catalog number" + "Last updated"
Is provided by a file system managed by a computer. Accordingly, when the update data storage unit 32 is viewed, map data including at least road network information is handled as a set of map data for each mesh corresponding to a predetermined area, and the map recorded at a predetermined time point. With the data as a reference, the (m + 1) th difference data is generated in units of the mesh as a difference from the map data updated with the difference data up to the nth time (n is a natural number of 1 or more). The difference data from the first time (m is an integer between 1 and n) to the (n + 1) th time are stored in the form of a file on the recording medium together with a catalog number (version number) which is an identifier for identifying each difference data. It will be. Therefore, FIG. 8 may be considered to represent the data structure of the difference file stored in the update data storage unit 32. Since each catalog is unique by “district name” + “catalog number”, “last update date” is not included in the file name, and may be treated as a time stamp of each file.

  When receiving the catalog list, the update unit 61 such as the vehicle 41 matches the update record stored in the map data storage unit 62, displays the catalog, and performs a process of selecting the user (step S210). FIG. 9 shows an example of this display. The update unit 61 displays the information already updated on the vehicle side in a superimposed manner on the catalog list received from the update server 30 side. In the example shown in FIG. 9, catalog numbers 1 and 2 for the Tohoku area, catalog numbers 1 to 3 for the Kanto area, and catalog numbers 1 to 3 for the Chubu area are displayed on the map data on the vehicle side on November 2, 2015. It is reflected and it can be seen that it has been updated. The user sees this display and selects the catalog number to be updated this time. Selection is performed by designating a necessary catalog number with a tap or the like from a list displayed on a display (not shown) included in the navigation control unit 65.

  When the catalog is selected, the update unit 61 of the vehicle 41 or the like transmits the next selected catalog number and update information in the vehicle, that is, which catalog has been updated to the update server 30 side. (Step S220). The update information in the vehicle is transmitted because the selection by the user is not to select all the catalogs to be updated, but only to select the maximum number of catalogs to be updated. . For example, if the user selects the catalog number 6 in the Kanto area, the update information in the vehicle, that is, the updated catalog number 3 is transmitted in the example shown in FIG. The server 30 side can know that the catalog applied this time is catalog numbers 4-6. Of course, all catalog numbers to be updated on the vehicle side may be specified and transmitted to the update server 30 side.

  The management unit 31 of the update server 30 that has received the transmission of the catalog number or the like selects update data to be applied from the catalog number or the like (step S310), and performs an update management process (step S400). This update management process (step S400) is a process for matching the difference data so that no contradiction occurs in the data when applying a plurality of catalogs. Details of the update management process in this embodiment are shown in FIG.

  FIG. 10 is a flowchart showing the update management processing routine. When this process is started, the management unit 31 first receives the difference data recorded in the catalog (step S410). The difference data is data collected for each group ID shown in FIGS. When this difference data is received, the processes in and after step S420 are repeated until all the target catalogs are completed. The target catalog is applied in the order of smaller catalog numbers.

  When a catalog with one catalog number is taken out as a target catalog, the processing from step S430 onward is repeated with all meshes having update data in the catalog as target meshes. That is, update management data is first created for all meshes included in the target catalog (step S440). An example of this is shown in FIG. Since the update process this time is for catalog numbers 4 to 6, update data included in the version number (current Ver. 4 in FIG. 11) 4 is first read and created as update management data. In FIG. 11, it is registered in the update management data that the mesh numbers 1, 3, 4, 5, 6 collected as the group ID 100 include data to be updated for the current Ver = 4 content type road NW. Is done.

  Next, it is determined whether there is another mesh that needs to be updated (step S450). In the same catalog number, meshes that need to be updated are associated with each other, so the determination in step S450 is “NO”, and the determination for the next mesh is continued without doing anything. When the determination is completed, the catalog number is incremented, and the process for all meshes is repeated, another mesh may be found that needs to be updated. In the example shown in FIG. 11, mesh number 5 is an update target with catalog number 4, but as shown with reference ST <b> 2, it is also an update target with catalog number 6, and the same group ID 101. It can be seen that the mesh number 8 in FIG. Therefore, in this case, the mesh numbers 5 and 8 are added to the update management data, and updated together with the meshes 1 and 3 to 6 that are required to be updated with the catalog number 4. As a result, the current Ver of the mesh numbers 5 and 8 becomes 6, and in addition to this, the mesh number 1 is also set to the current Ver6 (see FIG. 1, reference ST1). The update management data in this state is shown in FIG.

  The update management data is created by performing the processing described above for all meshes for all catalogs to be updated. This update management data sequentially reflects the update status of the road NW and the like recorded in the target catalog, and ensures continuity that does not cause any contradiction in the road NW or the like.

  The update management data created in this way is transmitted to the vehicle side by the management unit 31 (step S320). Upon receiving the transmission of all update management data, the update unit 61 receives the update data (step S230), and updates the map data for all the update data (step S240) (step S250). In FIG. 7, the update is applied to each road RID constituting the road NW on behalf of all map data. When the update for all the update data is completed, the vehicle-side update information (FIG. 9) is updated (step S260), and all the processes are terminated.

  By the above process, the map data including the navigation road NW stored in the map data storage unit 62 such as the vehicle 41 is updated to the selected catalog number of the region selected in the update process. In addition, since data in a plurality of catalogs created by authoring every predetermined period is applied as update management data (FIG. 12), data is applied even when a plurality of catalogs are applied. Updated without contradiction. For this reason, there is no case where the road NW is interrupted in route search or the like and an appropriate route search cannot be performed. The road map can be updated for each district, and even in that case, it is not always necessary to update the latest catalog. Therefore, it is possible to keep the communication data amount and update time required for updating the road map data within an appropriate range. For example, when going to a district where the vehicle does not normally travel due to a sudden business trip or the like, only the road map data leading to that district needs to be updated.

  According to the map data update system 10 of the above-described embodiment, the map data is updated (authoring process) every predetermined period, and a difference file with the result of authoring performed before that is stored in the form of a catalog. Each catalog is stored with an identifier of version number n + 1. In each catalog, the updated road NW data, etc., is saved in a format in which meshes in the range where the road changes, etc. are collected by the same group ID, and the version number after the update and the version number before the update of the data Are also recorded. For this reason, the structure of each difference data can be simplified. When updating the map data on the vehicle 41 side or the like, the catalog on which the difference data necessary for the update is recorded by managing which catalog in which district is applied on the vehicle side. Can be easily identified.

  In addition, when updating, the difference data in the catalog to be applied is collected and compiled as update management data, and then reflected in the map data on the vehicle side. For this reason, it is possible to easily balance simple difference data and reliable update of map data without contradiction.

B. Variations:
B1. About hardware configuration:
Another configuration example of the above embodiment will be described as a modified example from the first embodiment. In the said 1st Embodiment, although the vehicle-mounted navigation apparatus which performs a route search was assumed as a device which comprises the map data update system 10, it is not restricted to this, If it is a device which performs the process using map data As a device constituting a system, any of a vehicle-mounted map display device, a portable map display device, a portable route search device, a mobile phone on which an application for displaying a map and displaying a route to a destination is operated It may be adopted. In addition to these, a fixed map display device or a route search device may be used as a device.

  In the first embodiment, the dedicated update server 30 is provided between the map update data management device 20 that generates the difference data and the vehicle 41 or the like. However, the map update data management device 20 and the update server 30 once You may comprise. In addition, the map update data management device 20 and the update server 30 are connected via the dedicated line 11, but may be configured to be connected via the WAN 12 or the like as long as security can be secured by using a technology such as VPN.

  In addition, in the above-described embodiment, the connection between the vehicle 41 and the update server 30 is performed by wireless communication via the base stations 40 and 50. However, the vehicle 41 or the like is wired and updated at the store such as a dealer. It is also possible to update the map data by connecting to a device corresponding to. Alternatively, a storage medium such as a CD, DVD, or flash ROM containing a catalog may be set in a player provided in the vehicle 41 or the like, and update processing may be performed by reading difference data therefrom.

B2. About the data structure:
In the above embodiment, the catalog is created for each district such as the Hokkaido district, the Tohoku district,..., But may be created more finely for each administrative boundary such as a prefecture. Alternatively, the whole country may be divided into areas of a predetermined size (for example, 20 km square) and created for each area. In addition, the range in which authoring processing is performed may be different from the range stored as a catalog. When reproducing, a plurality of persons in charge, such as prefectures and municipalities, perform authoring processing at the same time, and after completing the authoring processing at almost the same timing, the difference data may be rearranged for each district. In addition, you may provide as a single catalog nationwide without dividing into districts.

  In the above embodiment, in addition to the difference data of the road NW, the feature data is also stored in the map data with different content types, but may be created as a different catalog. Alternatively, it may have no feature data. The authoring process uses a map at any point in time as a standard map and sequentially generates the difference data from it. At any point in time, a new standard map that reflects all these difference data is created. Then, a catalog may be created again in the form of difference data from this standard map.

  In the above embodiment, in each catalog, data for update is recorded in the form of differential data from the time when the previous catalog was created, and update management data is created when the update process is performed. However, every time a catalog is created, update management data reflecting the previous difference data is created, and when the update process is performed, the catalog number to be applied is specified. Then, one corresponding catalog may be read and the update management data recorded in the catalog may be applied.

  In the above embodiment, the road NW is defined as a set of links corresponding to the road, but may be defined as a set of nodes. Alternatively, other data formats may be used. Further, the road NW may be created not in units of roads but in units of lanes.

  In the above embodiment, the mesh has a rectangular shape. However, the mesh may be a shape that covers the ground surface without gaps, that is, a so-called plane filling shape, and may be a triangle, a hexagon, or a parallelogram in addition to a square or a rectangle. Also good. Of course, if plane filling is possible, a plurality of shapes may be combined and each may be handled as a mesh.

  In the above embodiment, the identifier is recorded as a number n + 1 that is incremented each time authoring is performed when version n = 1 of the standard map. However, if the order of authoring can be specified, the identifier must be a number. It can be binary code, text, or date / time data. In the case of text or the like, management may be performed so that the context can be understood by the pointer. Further, when creating update catalog data that summarizes the difference data up to that time when creating a catalog to be written, it is not necessary to record the version number immediately before the update is performed.

B3. About processing:
In the above embodiment, the map data is updated while communicating between the update server 30 and the vehicle 41. However, if the vehicle reads the catalog with a medium such as a DVD, the update process is performed only on the vehicle side. It can be completed with. Alternatively, if the navigation device is provided as an in-vehicle detachable device or a formable device such as a smart phone, such a device or the map data storage unit 62 is brought into a dealer or the like to update the update server 30 or the like. An update process using a catalog may be performed by connecting to a device. In this case, the update process can be a process executed only on the update server 30 side.

  The authoring process shown in FIG. 3 is an example of generating difference data, and the difference data may be created by any other process. For example, a probe car may be run, and information such as road abolition and new construction may be directly generated as difference data from information relating to travel collected by a large number of probe cars. Or you may make it produce | generate difference data from the information regarding the improvement and abolition of the road announced by the Ministry of Land, Infrastructure, Transport and Tourism or the expressway management company which manages the road.

  Although the embodiment and its modifications have been described above, the embodiment that solves at least a part of the problems is not limited to these, and can of course be implemented in various modes. For example, a part or all of the software processing described in the above embodiment can be realized by hardware. The target for updating the map data is not limited to the navigation device, but may be a simple map display device. Further, the present invention can be implemented in various modes such as a map data update method, a map data generation device and a generation method used for updating such map data. Further, the following application examples can also be implemented.

(1) As one application example, a map update data management device is provided. The map update data management apparatus treats map data including at least road network information as a set of map data for each mesh corresponding to a predetermined area, and uses the map data at a predetermined time as a reference for the (n + 1) th time. The difference data is generated in units of the mesh as a difference from the map data updated with the difference data up to the nth time (n is a natural number of 1 or more), and the generated n + 1th difference data is the difference data. A difference data storage unit for storing; and an identifier adding unit that adds an identifier that can be distinguished from the difference data before the nth time to the (n + 1) th difference data. Here, the difference data storage unit sequentially stores the difference data up to the (n + 1) th difference data.

  The map update data management apparatus updates the map data for each mesh, and assigns an identifier that can be distinguished from the difference data before the nth time to the (n + 1) th difference data, thereby obtaining the (n + 1) th difference. The difference data up to the data can be stored so as to be distinguishable from the difference data before the nth time. For this reason, when there is a request for updating map data, necessary difference data can be easily provided. In addition, since the map data is updated for each mesh, the data capacity required for the update can be made compact. The difference data may be generated in the map update data management device, but the result generated by another device may be received and stored in the difference data storage unit.

(2) In such a map update data management device, difference data including the (n + 1) th difference data may be managed for each map data in a specific area. As a region, for example, a district such as Hokkaido, Tohoku, etc., a government or administrative district such as a prefecture or a municipality, or a mesh of a predetermined size can be assumed. Depending on how the map data is used, it may be sufficient to designate and update the area, in which case the amount of data can be reduced. The update of the map data specifying the area may be a navigation device, for example. This is because, in many cases, the area of the route search may be limited depending on the purpose of use of the user.

(3) In such a map update management device, the difference data storage unit includes a difference data generation unit that generates a file for each of the first to n-th difference data, and the difference data storage unit includes the file May be stored in an identifiable manner using the identifier. In this way, since each difference data can be handled as a file, data management on the computer is prepared. Each difference data may be managed as an individual sheet included in one file instead of being stored as a file. Alternatively, it may be stored as a single text delimited by a data delimiter code.

(4) In such a map update data management device, the (n + 1) th difference data may be generated by grouping at least the meshes to which the change of the network information of the road is made into the same group. This makes it possible to manage the scope of the change as a group and facilitate the management of update data.

(5) As another application example, there is provided a map data update system that updates at least existing map data stored in a device that performs processing using a map, using map update data stored in a server. In this other figure data update system, the server treats map data including at least road network information as a set of map data for each mesh corresponding to a predetermined area, and based on the map data at a predetermined time point, The (n + 1) th difference data is generated in units of the mesh as a difference from the map data updated with the difference data up to the nth time (n is a natural number of 1 or more), and the generated first data The difference data storage unit for storing the difference data from the nth time to the (n + 1) th time using an identifier and the device communicate with the device and determine the update status of the map data on the device side using the identifier. A determination unit. In addition, the device receives the difference data by communicating with a map data storage unit that stores map data and the server, and the difference data after the m-th time (m <n + 1) that has already been applied is the identifier. And an update unit that updates the map data by sequentially applying the difference data from the (m + 1) th time to the (n + 1) th time in units of the mesh.

  In such a map data update system, the server updates the map data for each mesh, and assigns an identifier that can be distinguished from the difference data before the nth time to the (n + 1) th time difference data. The difference data up to the first difference data is stored so as to be distinguishable from the difference data before the n-th difference data. Moreover, since the server communicates with the device and determines the update status of the map data on the device side using the identifier, the difference data after the m-th time (m <n + 1) that has already been applied is determined on the device side. Can be specified using this identifier, and the map data can be updated by sequentially applying the difference data from the (m + 1) th time to the (n + 1) th time in units of meshes.

(6) In such a map data update system, the determination unit on the server side may specify difference data to be transmitted to the device side based on a result of determining the update status. In this way, the amount of data transmitted to the device side can be reduced. In other words, all the difference data up to the (n + 1) th time may be received, the update status may be determined on the device side, and the update may be performed.

(7) In such a map data update system, the server and the device manage difference data including the (n + 1) th difference data for each map data of a specific region, and the device The update may be performed by designating the region. In this way, the update can be performed for each region, and the data amount when updating the map data can be reduced.

(8) In such a map data update system, at least one of the devices includes an in-vehicle map display device, an in-vehicle route search device, a portable map display device, a portable route search device, and displays a map to the destination. It may be any of mobile phones on which an application for displaying the route is operated. In addition to these, the present invention may be applied to a fixed map display device or a route search device.

(9) As yet another application example, a map update data structure for updating map data is specified. This update data structure for maps treats map data including at least road network information as a set of map data for each mesh corresponding to a predetermined area, and the (n + 1) th time based on the map data recorded at a predetermined time point. Difference data is generated as a difference with the map data updated with the difference data up to the nth time (n is a natural number of 1 or more), and the mth time (m is 1 or more and n or less). To the (n + 1) th difference data together with an identifier capable of identifying each difference data in the form of a file. The map update data structure in which the difference data is stored in such a form makes it easy to handle the difference data in order to extract the update data and update the map data in various apparatuses.

(10) In such a map update data structure, the next difference data when the entire map data is updated may be treated as the m-th difference data. This is because there is no substantial difference data when the entire map data is updated.

  Each of the above-described embodiments and application examples solve at least a part of the problems of the conventional methods. Conventional methods (for example, the methods described in Patent Documents 1 and 2, etc.) have advantages and disadvantages, and are not sufficient as a map update data management method. For example, in the method of Patent Document 1, information is managed in units of meshes and only meshes for which update information exists are rewritten. However, the current map does not simply manage only roads, but various types of information associated with roads. It also manages features such as facilities, buildings, and parking lots. Therefore, if the map is renewed once a year or once every several years, the number of target meshes becomes enormous, which may eventually rewrite most of the original map data.

  In addition, when managing the difference information, it is sufficient that the navigation device captures and updates all the difference information every time. However, some users may perform the update operation only once in several times. It is done. In this case, for roads that have been extended by repeated expansion and construction of roads, if only the latest update information is applied in a state where all update information created in the middle is not reflected, for example, a newly established road May not be connected to existing roads. In this case, as a result, there is a road that is not connected to the road network, and there is a possibility that route search or the like cannot be performed successfully.

In short, updating map data
[1] I want to update information related to maps in as short a time as possible. In particular, since information such as opening and closing of roads is often used for navigation, it is reflected within a short period of time, for example, every two months, every two weeks, every two weeks, every ten days, or every week. ,
[2] When such short-term information is updated, it is preferable to treat it as a difference file corresponding to the updated portion. However, when a number of difference files are created in a short period of time, all the difference files are adopted by the user. Not necessarily. Even so, make sure that there is no discrepancy in the map data or roads that are not connected to the road network.
It was desired to satisfy the two conditions as much as possible.

  The above-described embodiments, modified examples, application examples, and the like solve at least a part of the above-described problems.

DESCRIPTION OF SYMBOLS 10 ... Map data update system 11 ... Dedicated line 20 ... Map update data management apparatus 21 ... Difference data generation part 22 ... Identifier assignment part 23 ... Data storage part 30 ... Update server 31 ... Management part 32 ... Update data storage part 40 ... Base Stations 41, 43, 51, 52 ... Vehicle 61 ... Update unit 62 ... Map data storage unit 65 ... Navigation control unit

Claims (6)

A management device for map update data,
Map data including at least road network information is treated as a set of map data for each mesh corresponding to a predetermined area, and the (n + 1) th difference data on the basis of the map data at a predetermined time point is the nth ( n is a difference data storage unit that stores the generated (n + 1) th difference data as a difference with the map data updated with the difference data up to 1).
An identifier assigning unit that assigns an identifier that can be distinguished from the difference data before the nth time to the (n + 1) th difference data;
With
The difference data storage unit is a map update data management device that sequentially stores difference data up to the (n + 1) th difference data. The map update data management device according to claim 1,
The map update data management device, wherein the (n + 1) th difference data is generated by grouping at least the meshes to which the network information of the road is changed into the same group. A map data update system that updates at least existing map data stored in a device that performs processing using a map, using map update data stored in a server,
The server
Map data including at least road network information is treated as a set of map data for each mesh corresponding to a predetermined area, and the (n + 1) th difference data on the basis of the map data at a predetermined time point is the nth ( n is generated as a difference from the map data updated with the difference data up to 1 (natural number equal to or greater than 1), and the generated first to (n + 1) th difference data is expressed as an identifier. A differential data storage unit for use in an identifiable manner, and
A determination unit that communicates with the device and determines the update status of the map data of the device using the identifier.
A map data storage unit for storing map data;
The difference data is received by communicating with the server, the difference data after the m-th time (m <n + 1) that has already been applied (m <n + 1) is specified using the identifier, and the difference data from the (m + 1) -th time to the (n + 1) -th time A map data update system comprising: an update unit that sequentially applies the data in units of the mesh to update the map data.
4. The map data update system according to claim 3, wherein difference data to be transmitted is specified. An update data structure for maps for updating map data,
Map data including at least road network information is handled as a set of map data for each mesh corresponding to a predetermined area, and the (n + 1) th difference data is the nth time based on the map data recorded at a predetermined time point. As the difference from the map data updated with the difference data up to (n is a natural number of 1 or more), the m + 1th to m + 1th generation (m is an integer of 1 to n) generated in units of the mesh. The difference data
An updated map data structure for storing each difference data together with an identifiable identifier in a file format on a recording medium. A management device for map update data,
A predetermined type of content included in the first mesh corresponding to the first area in the map data and a second mesh corresponding to the second area adjacent to the first area in the map data Group information indicating that the content of the predetermined type included is the same group;
Using the group information, when the predetermined type of content included in the first mesh is updated, control is performed so that the predetermined type of content included in the second mesh is also updated. Update section,
A map data management device. A data structure of management data for update used for updating map data,
A predetermined type of content included in the first mesh corresponding to the first area in the map data and a second mesh corresponding to the second area adjacent to the first area in the map data Group information indicating that the content of the predetermined type included is the same group;
The group information is a process for controlling so that the predetermined type of content included in the second mesh is also updated when the predetermined type of content included in the first mesh is updated. Data structure of management data for update used.

Images