Map data management device and map data management method
The map data management device addresses the challenge of timely updates by predicting and prioritizing mesh updates, allowing for bulk data downloads, thus efficiently managing map data updates and ensuring timely delivery to map applications.
Patent Information
- Application Number
- PCT/JP2023/020306
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-31
- Publication Date
- 2024-12-05
AI Technical Summary
Existing map data management systems face challenges in updating map data in a timely manner, especially when the number of meshes that need to be updated increases, such as in cases where mesh sizes are small or when updating a wide area, leading to potential delays in meeting requests from map applications.
A map data management device that includes a map database, a map access unit, an update map data download unit, and a map update control unit, which predicts the meshes that will be requested by a map application and updates only the necessary meshes, allowing for bulk downloads of update data when no meshes within a predetermined range need updating, thereby reducing the overall time required for updates.
This approach significantly shortens the time required to update map data, ensuring that updates are performed efficiently and effectively, even in scenarios with a large number of meshes, by optimizing the download and update process based on vehicle position and update status.
Smart Images

Figure JP2023020306_05122024_PF_FP_ABST
Abstract
Description
Map data management device and map data management method
[0001] The present disclosure relates to a map data management device that manages updates to map data.
[0002] In-vehicle devices that execute map applications that operate using map data provided from a map database, such as car navigation devices, ADAS (Advanced Driver-Assistance Systems) devices, and autonomous driving devices, are becoming more and more common. In order to provide the map application with the latest map data, such in-vehicle devices preferably have a function for downloading and acquiring the latest map data from a map distribution server and updating the map data stored in the map database provided in the in-vehicle device.
[0003] Generally, map databases store map data for each area (called a "mesh") obtained by dividing a map into a mesh. For example, Patent Document 1 listed below discloses a technology that predicts a mesh for which a map application will request map data based on the position information of a vehicle equipped with an on-board device, and prioritizes updating the map data for the mesh predicted to be requested by the map application, thereby preventing map data updates from being delayed in response to a request from the map application.
[0004] International Publication No. 2022 / 085173
[0005] For example, when the size of each mesh is small (e.g., several hundred meters) and the map data is divided into small sections, or when updating map data for a wide area, if the number of meshes that need to be updated increases, there is a concern that the map data updates may not be able to keep up with requests from the map application. Even with the technology of Patent Document 1, when predicting meshes for which map data will be requested by the map application for an area distant from the vehicle equipped with the on-board device, the number of meshes that need to be updated may increase, and a similar problem may arise. To fundamentally solve this problem, it is desirable to shorten the time required to update map data.
[0006] The present disclosure has been made to solve the above-mentioned problems, and aims to provide a map data management device that can shorten the time required to update map data.
[0007] The map data management device according to the present disclosure includes a map database that stores map data for each mesh obtained by dividing a map into meshes; a map access unit that provides the map application of the in-vehicle device with the map data stored in the map database in response to a request from the map application; an update map data download unit that downloads update map data from a map distribution server to update the map data for each mesh to the latest map data; and a map update control unit that updates the map data stored in the map database using the update map data. The map update control unit predicts meshes for which map data will be requested by the map application based on the position of the vehicle in which the in-vehicle device is installed, identifies the meshes predicted to request map data as predicted requested meshes, identifies meshes among the predicted requested meshes for which map data stored in the map database are not the latest as meshes requiring update, and updates the map data for the meshes requiring update. When there are no more meshes requiring update within a predetermined range based on the vehicle position, the update map data download unit increases the number of meshes requiring update for which update map data will be downloaded in a batch, or the map update control unit increases the number of meshes requiring update for which map data will be updated in a batch.
[0008] According to the map data management device according to the present disclosure, the time required to update map data can be reduced.
[0009] The objects, features, aspects, and advantages of the present disclosure will become more apparent from the following detailed description and the accompanying drawings.
[0010] FIG. 1 is a block diagram showing a configuration of a map data management device according to embodiment 1. FIG. 2 is a diagram for explaining the operation of the map data management device according to embodiment 1. FIG. 3 is a diagram for explaining the operation of the map data management device according to embodiment 1. FIG. 4 is a flowchart showing map update processing of the map data management device according to embodiment 1. FIG. 5 is a diagram for explaining a first modification of the operation of the map data management device according to embodiment 1. FIG. 6 is a diagram for explaining a third modification of the operation of the map data management device according to embodiment 1. FIG. 7 is a diagram for explaining the operation of the map data management device according to embodiment 2. FIG. 8 is a diagram for explaining the operation of the map data management device according to embodiment 2. FIG. 9 is a flowchart showing map update processing of the map data management device according to embodiment 2. FIG. 10 is a diagram showing an example of a hardware configuration of a map data management device.
[0011] <Embodiment 1> Fig. 1 is a block diagram showing the configuration of a map data management device 10 according to embodiment 1. As shown in Fig. 1, the map data management device 10 is incorporated into an in-vehicle device 20 that includes a communication device 21, a positioning unit 22, a map application 23, and a pre-read map data storage unit 24. Hereinafter, the vehicle in which the in-vehicle device 20 is installed will be referred to as the "host vehicle."
[0012] However, the map data management device 10 does not necessarily have to be built into the in-vehicle device 20, and may be a portable device, such as a mobile phone or a smartphone, that is externally attached to the in-vehicle device 20. Furthermore, some of the functions of the map data management device 10 may be implemented on an external server that can communicate with the map data management device 10.
[0013] The communication device 21 is a means by which the in-vehicle device 20 communicates with the outside. The map data management device 10 can access the map distribution server 30, which distributes the latest map data, using the communication device 21. The communication device 21 may be a communication means dedicated to the in-vehicle device 20, or may be a general-purpose communication means such as a mobile phone or a smartphone.
[0014] The positioning unit 22 measures the current position of the vehicle by using positioning signals received from the Global Navigation Satellite System (GNSS), outputs from sensors (e.g., speed sensors, direction sensors, etc.) of the vehicle, map data acquired from the map data management device 10, etc.
[0015] The map application 23 is a functional block constructed by the in-vehicle device 20 executing a program, and realizes, for example, a navigation function, an ADAS function, an autonomous driving function, etc. The map application 23 requests map data required for its operation from the map data management device 10, and realizes each of the above functions using the map data provided by the map data management device 10.
[0016] Although not shown in the figure, the map application 23 can acquire information necessary to realize each function from surrounding sensors, vehicle condition sensors, etc. of the vehicle. Furthermore, when the map application 23 realizes an ADAS function, an autonomous driving function, etc., it can control the driving control system of the vehicle, such as the steering wheel, accelerator, and brakes. When the map application 23 realizes a navigation function, an operation input device for the user to input a destination, etc., a display device that presents the user with a planned driving route, an audio output device that provides audio route guidance to the user, etc. are connected to the in-vehicle device 20.
[0017] The prefetch map data storage unit 24 is a temporary memory that stores map data provided from the map data management device 10 to the map application 23. A cache memory that can be accessed by the map application 23 at high speed may be used as the prefetch map data storage unit 24.
[0018] The map application 23 requests map data (e.g., map data around the current location of the vehicle) required for, for example, the navigation function, the ADAS function, and the automatic driving function from the map data management device 10. The map data management device 10 transmits the map data requested by the map application 23 to the pre-read map data storage unit 24 for storage. When the map data requested by the map application 23 is stored in the map application 23, the map application 23 performs operations using the map data, thereby realizing the navigation function, the ADAS function, the automatic driving function, and the like. Each time the required map data changes as the vehicle travels, the map application 23 requests map data from the map data management device 10.
[0019] As shown in FIG. 1, the map data management device 10 includes a map database 11, a map access unit 12, a map update control unit 13, an update map data download unit 14, an update status storage unit 15, and an update map data storage unit 16.
[0020] The map database 11 is a storage medium that stores map data for each mesh obtained by dividing a map into meshes.
[0021] The map data in the map database 11 is managed in units of meshes. Map data stored in the map database 11 can be updated in units of meshes. There are no restrictions on the size of one mesh; for example, a rectangle of 1 km x 1 km may be defined as one mesh. There are also no restrictions on the method of managing map data in the map database 11. For example, map data for one mesh may be managed as one file, one file may contain map data for multiple meshes, or map data for one mesh may be divided into multiple files.
[0022] In response to a request from the map application 23, the map access unit 12 provides the map application 23 with map data stored in the map database 11. As described above, the map data provided to the map application 23 is stored in the pre-read map data storage unit 24, which is a temporary memory. In other words, the map data is provided to the map application 23 by saving the map data in the pre-read map data storage unit 24.
[0023] It is desirable that the map access unit 12 does not write duplicate map data that is already stored in the prefetch map data storage unit 24 to the prefetch map data storage unit 24. This prevents unnecessary (duplicate) writing processes from being performed, and enables the map data to be provided to the map application 23 at high speed.
[0024] The map update control unit 13 performs processing to update the map data stored in the map database 11. The update map data downloading unit 14 uses the communication device 21 to access the map distribution server 30 and downloads the latest map data that the map update control unit 13 uses to update the map data from the map distribution server 30. Hereinafter, the latest map data that the update map data downloading unit 14 downloads from the map distribution server 30 is referred to as "update map data."
[0025] The update map data storage unit 16 is a storage medium that temporarily stores the update map data that the update map data download unit 14 downloads from the map distribution server 30. The map update control unit 13 uses the update map data stored in the update map data storage unit 16 to update the map data stored in the map database 11.
[0026] The update status storage unit 15 is a storage medium that stores update status data, which is data for managing the update status of the map data stored in the map database 11 (i.e., whether the map data is up to date) on a mesh-by-mesh basis. In this embodiment, the map update control unit 13 accesses the map distribution server 30 in advance (for example, when the map data management device 10 is started up), via the update map data download unit 14, and compares the version of the map data for each mesh stored in the map database 11 with the version of the map data for each mesh stored in the map distribution server 30 to determine whether the map data for each mesh stored in the map database 11 needs to be updated, and stores the result as update status data in the update status storage unit 15. Storing the update status data in advance in the update status storage unit 15 reduces the number of times the map update control unit 13 accesses the map distribution server 30 to determine whether the map data needs to be updated, thereby enabling faster processing.
[0027] Although the number of times of accessing the map distribution server 30 increases, the map update control unit 13 may access the map distribution server 30 and check whether the map data needs to be updated each time it becomes necessary. In this case, the update status storage unit 15 is not necessary.
[0028] The operation of the map update control unit 13 will now be described in detail. Prior to updating the map data, the map update control unit 13 predicts meshes for which map data will be requested by the map application 23. In this embodiment, the map update control unit 13 predicts meshes within a predetermined range that include a mesh to which the planned driving route of the vehicle belongs, as meshes for which map data will be requested by the map application 23.
[0029] For example, when the map application 23 requests map data for a 3x3 mesh centered on a mesh containing the current position of the vehicle, the map update control unit 13 predicts the mesh containing the planned driving route of the vehicle and the meshes included in the 3x3 mesh centered on the mesh containing the planned driving route as the meshes for which map data will be requested by the map application 23. Hereinafter, the meshes predicted to request map data from the map application 23 will be referred to as "predicted requested meshes."
[0030] When the request prediction meshes are identified, the map update control unit 13 identifies, among the request prediction meshes, meshes for which the map data stored in the map database 11 is not up to date as "meshes requiring update." By referencing the update status data stored in the update status storage unit 15, the map update control unit 13 can quickly determine whether the map data for each mesh stored in the map database 11 is up to date.
[0031] When the mesh requiring update is identified, the map update control unit 13 instructs the update map data downloading unit 14 to download the update map data of the mesh requiring update from the map distribution server 30. The update map data downloaded by the update map data downloading unit 14 is stored in the update map data storage unit 16, and the map update control unit 13 uses the update map data stored in the update map data storage unit 16 to update the map data of the mesh requiring update.
[0032] If there are multiple meshes that require updating, the map update control unit 13 downloads update map data and updates the map data in order of the meshes that require updating, starting with the mesh closest to the current position of the vehicle in the direction of travel. This reduces the possibility that the map data update will not be completed in time to meet a request from the map application.
[0033] Furthermore, if there are multiple meshes requiring update, the update map data downloading unit 14 can download update map data for multiple meshes requiring update in a batch. However, the map update control unit 13 changes the upper limit of the number of meshes requiring update for which the update map data downloading unit 14 will download update map data in a batch, depending on whether or not there are meshes requiring update within a predetermined range based on the vehicle's position. That is, if there are meshes requiring update within a predetermined range based on the vehicle's position, the map update control unit 13 limits the number of meshes requiring update for which update map data will be downloaded in a batch, and if there are no meshes requiring update within the predetermined range based on the vehicle's position, the map update control unit 13 increases the upper limit of the number of meshes requiring update for which update map data will be downloaded in a batch, thereby increasing the number of meshes requiring update for which update map data will be downloaded in a batch.
[0034] In this embodiment, when there are meshes requiring update within a 20 x 20 mesh centered on the position of the vehicle, the map update control unit 13 sets the upper limit of the number of meshes requiring update for which update map data will be downloaded in a batch to 10, and when there are no more meshes requiring update within the 20 x 20 mesh centered on the position of the vehicle, the map update control unit 13 sets the upper limit of the number of meshes requiring update for which update map data will be downloaded in a batch to 40.
[0035] For example, assume that the map database 11 stores map data as shown in Fig. 2. Each square in Fig. 2 is a mesh. As shown in Fig. 2, if there are meshes requiring update within a 20 x 20 mesh (the area surrounded by a thick dashed line) centered on the position of the vehicle, the upper limit of the number of meshes requiring update for which update map data will be downloaded in a batch is set to 10. Therefore, in the situation shown in Fig. 2, 10 meshes requiring update that are relatively close to the position of the vehicle in the direction of travel are selected as the meshes requiring update (the area surrounded by a thick dotted line) for which update map data will be downloaded in a batch next.
[0036] Thereafter, as the map data update progresses, when there are no more meshes requiring update within the 20 x 20 mesh centered on the vehicle's position, as shown in Figure 3, the upper limit on the number of meshes requiring update for which update map data will be downloaded in a batch is set to 40. Therefore, in the situation shown in Figure 3, 40 meshes requiring update that are relatively close to the vehicle's position in the direction of travel are selected as the meshes requiring update from which update map data will be downloaded in a batch next.
[0037] The process of downloading update map data from the map distribution server 30 includes a main download process and an additional overhead process that is executed before the main process. When downloading update map data for multiple meshes that require updating all at once, overhead processing is required only once, which shortens the overall download process time compared to downloading update map data for multiple meshes that require updating individually, and reduces the time required to update the map data. However, if the number of meshes that require updating for which update map data is to be downloaded all at once is very large, the amount of data to be downloaded becomes enormous, which increases the time required for each bulk download, and there is a risk that the map data will not be updated in time to meet requests from the map application.
[0038] Therefore, in the first embodiment, when there are meshes requiring update within a predetermined range based on the position of the vehicle, that is, when there are meshes requiring update near the vehicle, the map update control unit 13 limits the number of meshes requiring update for which update map data is downloaded in one batch, thereby shortening the time required to download each piece of update map data and quickly updating the map data for the meshes requiring update near the vehicle. This prevents the map data from being updated too late to meet a request from the map application.
[0039] When there are no more meshes requiring update near the vehicle, the map update control unit 13 increases the number of meshes requiring update for which update map data is downloaded in bulk, thereby reducing the number of overhead processes and the overall download processing time, thereby shortening the time required to update the map data.
[0040] 4 is a flowchart showing the map data update process performed by the map data management device 10 according to embodiment 1. The operation of the map data management device 10 involved in the map data update process will be described below with reference to the flowchart in FIG.
[0041] When the map data update process is started, the map update control unit 13 acquires information about the vehicle's position from the positioning unit 22 (step S101). Then, the map update control unit 13 refers to the update status data stored in the update status storage unit 15 to check the update status of the 20×20 mesh centered on the vehicle's position, i.e., whether or not there are any meshes that require updating (step S102).
[0042] If there is a mesh requiring update within the 20 x 20 mesh centered on the vehicle's position (YES in step S103), the map update control unit 13 sets the upper limit of the number of meshes requiring update for which update map data is to be downloaded in a batch to 10 (step S104).If there is no mesh requiring update within the 20 x 20 mesh centered on the vehicle's position (NO in step S103), the map update control unit 13 sets the upper limit of the number of meshes requiring update for which update map data is to be downloaded in a batch to 40 (step S105).
[0043] Next, the map update control unit 13 selects meshes requiring update for which update map data is to be downloaded (step S106). In this embodiment, meshes requiring update that are relatively close to the current position of the vehicle in the direction of travel are selected. The upper limit of the number of meshes requiring update selected in step S106 is the value set in step S104 or step S105.
[0044] The update map data downloading unit 14 then downloads the update map data of the selected meshes requiring update all at once, and stores it in the update map data storage unit 16 (step S107).
[0045] When the update map data is stored in the update map data storage unit 16, the map update control unit 13 updates the map data of the mesh that needs to be updated using the update map data in the update map data storage unit 16 (step S108). After that, the process returns to step S101, and the above processing is repeated.
[0046] [Variation 1] In the first embodiment, an example was shown in which, when there are no more meshes requiring update within a 20x20 mesh centered on the position of the vehicle, the upper limit of the number of meshes requiring update for which update map data is to be downloaded in one batch is increased. In other words, an example was shown in which the above-mentioned "predetermined range based on the position of the vehicle" is changed to "a 20x20 mesh centered on the position of the vehicle."
[0047] However, the "predetermined range based on the position of the vehicle" may be defined in any way. For example, the "predetermined range based on the position of the vehicle" may be "a 20 x 20 mesh centered on the position of the vehicle that is aligned with the expressway" or "a 20 x 20 mesh centered on the position of the vehicle that is aligned with the planned driving route of the vehicle." In this case, as shown in FIG. 5 , even if there are meshes requiring update that remain in a location away from the expressway or the planned driving route of the vehicle (e.g., a part of a ramp leading from the expressway, which is the planned driving route, to an interchange exit), the map update control unit 13 increases the upper limit of the number of meshes requiring update for which update map data is to be downloaded in a batch.
[0048] In the first embodiment, an example was shown in which the upper limit of the number of meshes requiring update for which update map data is to be downloaded in a batch is switched between 10 and 40 depending on whether or not there are any meshes requiring update within a 20×20 mesh centered on the position of the vehicle. In other words, an example was shown in which the upper limit of the number of meshes requiring update for which update map data is to be downloaded in a batch is set to two levels: 10 and 40.
[0049] However, the upper limit may be changed in multiple stages, such as three or more stages. For example, after there are no more meshes requiring update within a predetermined range based on the vehicle's position, the map update control unit 13 may increase the number of meshes requiring update for which update map data is to be downloaded in a batch in multiple stages as the range without meshes requiring update expands.
[0050] [Variation 3] As mentioned above, there are no restrictions on the management method of the map data in the map database 11; for example, one file may contain map data for multiple meshes. When such a management method is adopted, map data for meshes that need to be updated simultaneously may span multiple files, as shown in Figure 6. In the example of Figure 6, the map data for 40 meshes that need to be updated next are spread across four files (files A to D). In such a case, it becomes necessary to process multiple files simultaneously, which may result in lower processing efficiency and longer processing times than when processing a single file.
[0051] Therefore, in this modified example, when map data for a mesh that requires updating spans multiple files, the map update control unit 13 performs the map data update process separately for each file. In other words, the map update control unit 13 determines the range of map data to be updated simultaneously so that it fits within a single map data file. In the example of Figure 6, the map update control unit 13 performs the update process for the map data of the 40 meshes that require updating next, dividing it into the ranges of files A to D. This eliminates the need to process multiple files simultaneously, and reduces the decline in processing efficiency.
[0052] <Embodiment 2> In embodiment 2, the operation of the map update control unit 13 in the map data management device 10 differs from embodiment 1. Since the rest is basically the same as embodiment 1, the operation of the map update control unit 13 will be mainly described here, and descriptions that overlap with embodiment 1 will be omitted.
[0053] In the second embodiment, when there are multiple meshes that require updating, the map update control unit 13 changes the number of meshes that require updating for which the map data is to be updated in a batch, depending on whether or not there are any meshes that require updating within a predetermined range based on the position of the vehicle. That is, when there are meshes that require updating within a predetermined range based on the position of the vehicle, the map update control unit 13 limits the number of meshes that require updating for which the map data is to be updated in a batch, and when there are no more meshes that require updating within the predetermined range based on the position of the vehicle, the map update control unit 13 increases the number of meshes that require updating for which the map data is to be updated in a batch.
[0054] The upper limit of the number of update-requiring meshes for which update map data is downloaded in one batch, that is, the number of update-requiring meshes for which update map data can be acquired in one download, may be fixed.
[0055] In this embodiment, when there is a mesh requiring update within a 20 x 20 mesh centered on the position of the vehicle, the map update control unit 13 updates the map data of the mesh requiring update corresponding to the downloaded update map data in one go each time update map data is downloaded; and when there is no longer a mesh requiring update within the 20 x 20 mesh centered on the position of the vehicle, the map update control unit 13 updates the map data of the mesh requiring update corresponding to the four downloads of update map data in one go each time update map data is downloaded four times.
[0056] For example, assume that the map database 11 stores map data as shown in FIG. 7 . Furthermore, the number of update-requiring meshes for which update map data can be obtained in one download is 10. As shown in FIG. 7 , if update-requiring meshes exist within a 20×20 mesh (the area surrounded by the thick dashed line) centered on the vehicle's position, each time update map data is downloaded, the map data for the update-requiring meshes corresponding to the downloaded update map data is updated all at once. Therefore, in the situation shown in FIG. 7 , the number of downloads of update map data to be performed before the next map data batch update is set to 1. Therefore, when update map data for 10 update-requiring meshes (the area surrounded by the thick dotted line) that are relatively close to the vehicle's position in the traveling direction is downloaded in the next download, the map data for those 10 update-requiring meshes is updated all at once.
[0057] Thereafter, as the map data update progresses, when there are no more meshes requiring update within the 20x20 mesh centered on the vehicle's position, as shown in Figure 8, every time update map data is downloaded four times, the map data for the meshes requiring update corresponding to the update map data downloaded four times is updated in bulk. Therefore, in the situation shown in Figure 8, the number of downloads of update map data to be performed before the next map data bulk update is set to four. Therefore, when update map data for 40 meshes requiring update that are relatively close to the vehicle's position in the direction of travel (the four areas surrounded by thick dotted lines) is downloaded in the next four downloads, the map data for those 40 meshes requiring update will be updated in bulk.
[0058] The process of updating the map data in the map database 11 includes a main process, which is a map data rewrite process, and an additional process, overhead processing, which is executed before the main process. Updating map data for multiple meshes that require updating all at once requires fewer overhead processes than updating them in multiple batches. Updating the map data for multiple meshes that require updating all at once reduces the overall time required for the map data update process, and shortens the time required to update the map data. However, if the number of meshes that require updating map data for a batch update is very large, the time required for the batch update will be long, and there is a risk that the map data update will not be completed in time to meet requests from the map application.
[0059] Therefore, in the second embodiment, when there are meshes that need to be updated within a predetermined range based on the position of the vehicle, that is, when there are meshes that need to be updated near the vehicle, the map update control unit 13 limits the number of meshes that need to be updated for which map data is updated in a batch, thereby shortening the time required to update each mesh and quickly updating the map data for meshes that need to be updated near the vehicle. This prevents the map data from being updated too late to meet a request from the map application.
[0060] When there are no more meshes requiring update near the vehicle, the map update control unit 13 increases the number of meshes requiring update for which the map data is to be updated in a batch, thereby reducing the number of overhead processes and shortening the overall time required for the map data update process. This reduces the time required to update the map data.
[0061] Furthermore, if the number of meshes to which update map data can be downloaded in one batch cannot be freely changed due to constraints on the map distribution server 30, the method of embodiment 1 cannot be applied, but the method of embodiment 2 can be applied.
[0062] 9 is a flowchart showing the map data update process performed by the map data management device 10 according to embodiment 2. The operation of the map data management device 10 involved in the map data update process will be described below with reference to the flowchart in FIG.
[0063] When the map data update process is started, the map update control unit 13 acquires information about the vehicle's position from the positioning unit 22 (step S201). Then, the map update control unit 13 refers to the update status data stored in the update status storage unit 15 to check the update status of the 20×20 mesh centered on the vehicle's position, i.e., whether or not there are any meshes that require updating (step S202).
[0064] If there is a mesh requiring update within the 20×20 mesh centered on the vehicle's position (YES in step S203), the map update control unit 13 sets the number of downloads N of update map data to be performed before the bulk update of the map data to 1 (step S204).If there is no mesh requiring update within the 20×20 mesh centered on the vehicle's position (NO in step S203), the map update control unit 13 sets the number of downloads N of update map data to be performed before the bulk update of the map data to 4 (step S205).
[0065] Next, the map update control unit 13 selects meshes requiring update for which update map data is to be downloaded (step S206). In this embodiment, meshes requiring update that are relatively close to the current position of the vehicle in the direction of travel are selected. In this embodiment, the upper limit of the number of meshes requiring update selected in step S206 is set to 10.
[0066] The update map data downloading unit 14 then downloads the update map data of the selected meshes requiring update all at once, and stores it in the update map data storage unit 16 (step S207).
[0067] The map update control unit 13 checks whether or not N downloads of update map data (N is the value set in step S204 or step S205) have been stored in the update map data storage unit 16. If N downloads of update map data have not been stored in the update map data storage unit 16 (NO in step S208), the process returns to step S206, where more update map data is downloaded and stored in the update map data storage unit 16.
[0068] When the update map data for the N downloads has been stored in the update map data storage unit 16 (YES in step S208), the map update control unit 13 collectively updates the map data of the meshes that require updating using the update map data in the update map data storage unit 16 (step S209). After that, the process returns to step S201, and the above processing is repeated.
[0069] [Variation 1] In the second embodiment, an example has been shown in which, when there are no more meshes requiring update within a 20x20 mesh centered on the position of the vehicle, the map update control unit 13 increases the number of meshes requiring update for which the map data is to be collectively updated (specifically, the number of times update map data is downloaded before the collectively updated map data is completed). In other words, an example has been shown in which the above-mentioned "predetermined range based on the position of the vehicle" is set to "a 20x20 mesh centered on the position of the vehicle."
[0070] However, the "predetermined range based on the position of the host vehicle" may be defined in any way. For example, the "predetermined range based on the position of the host vehicle" may be "a 20 x 20 mesh centered on the position of the host vehicle that is aligned with the expressway" or "a 20 x 20 mesh centered on the position of the host vehicle that is aligned with the planned route of the host vehicle." In this case, as shown in FIG. 5 , even if there are meshes requiring update that remain in a location away from the expressway or the planned route of the host vehicle (part of a ramp leading from the expressway, which is the planned route, to an interchange exit), the map update control unit 13 increases the number of meshes requiring update for which the map data is to be collectively updated.
[0071] In the second embodiment, an example was shown in which the number of downloads (N) of update map data to be performed before a batch update of map data is performed is switched between 1 and 4 depending on whether or not there are any meshes that require updating within a 20×20 mesh centered on the position of the vehicle. In other words, an example was shown in which the upper limit on the number of meshes that require updating for a batch update of map data is set to two levels: 10 and 40.
[0072] However, the upper limit may be changed in multiple stages of three or more. For example, after there are no more meshes requiring update within a predetermined range based on the position of the vehicle, the map update control unit 13 may increase the number of meshes requiring update to be updated in multiple stages as the range without meshes requiring update expands.
[0073] [Variation 3] As mentioned above, when one file of map data in the map database 11 contains map data for multiple meshes, the map data for meshes that require updating and are to be updated in bulk may span multiple files, as shown in Figure 6. In the example of Figure 6, the map data for the 40 meshes that require updating that will be updated next spans four files (files A to D). In such a case, it becomes necessary to process multiple files simultaneously, which raises concerns that processing efficiency will decrease and processing time will be longer than when processing a single file.
[0074] Therefore, in this modified example, when map data for a mesh that requires updating spans multiple files, the map update control unit 13 performs the map data update process separately for each file. In other words, the map update control unit 13 determines the range of map data to be updated simultaneously so that it fits within a single map data file. In the example of Figure 6, the map update control unit 13 performs the update process for the map data of the 40 meshes that require updating next, dividing it into the ranges of files A to D. This eliminates the need to process multiple files simultaneously, and reduces the decline in processing efficiency.
[0075] <Hardware Configuration Example> Figures 10 and 11 are diagrams showing examples of the hardware configuration of the map data management device 10. The functions of the components of the map data management device 10 shown in Figure 1 are realized, for example, by a processing circuit 50 shown in Figure 10. That is, the map data management device 10 includes a processing circuit 50 for providing map data stored in the map database 11 to the map application 23 in response to a request from the map application 23 of the in-vehicle device 20, downloading update map data, which is the latest map data for each mesh, from the map distribution server 30, and updating the map data stored in the map database 11 using the update map data. Furthermore, in the process of updating the map data stored in the map database 11, the processing circuit 50 identifies, among the meshes predicted to receive map data requests, meshes for which the map data stored in the map database 11 is not the latest as update-requiring meshes, updates the map data for the update-requiring meshes, and, when there are no more update-requiring meshes within a predetermined range based on the vehicle's position, increases the number of update-requiring meshes for which update map data is to be downloaded in a batch or the number of update-requiring meshes for which map data is to be updated in a batch. The processing circuit 50 may be dedicated hardware, or may be configured using a processor (also called a central processing unit (CPU), processing device, arithmetic unit, microprocessor, microcomputer, or DSP (Digital Signal Processor)) that executes a program stored in memory.
[0076] When the processing circuitry 50 is dedicated hardware, the processing circuitry 50 may be, for example, a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a combination of these. The functions of the components of the map data management device 10 may be realized by individual processing circuits, or these functions may be realized together by a single processing circuit.
[0077] 11 shows an example of the hardware configuration of the map data management device 10 in which the processing circuit 50 is configured using a processor 51 that executes a program. In this case, the functions of the components of the map data management device 10 are realized by software, etc. (software, firmware, or a combination of software and firmware). The software, etc. is written as a program and stored in the memory 52. The processor 51 realizes the functions of each unit by reading and executing the program stored in the memory 52. That is, the map data management device 10 includes the memory 52 for storing programs that, when executed by the processor 51, result in the following processes: providing map data stored in the map database 11 to the map application 23 of the in-vehicle device 20 in response to a request from the map application 23; downloading update map data, which is the latest map data for each mesh, from the map distribution server 30; and updating the map data stored in the map database 11 using the update map data. Furthermore, the processor 51 that executes this program performs the following operations in updating the map data stored in the map database 11: identifying, among the meshes predicted to require map data, meshes for which the map data stored in the map database 11 is not up-to-date as meshes requiring update; updating the map data of the meshes requiring update; and, when there are no more meshes requiring update within a predetermined range based on the vehicle's position, increasing the number of meshes requiring update for which update map data is to be downloaded in a batch or the number of meshes requiring update for which map data is to be updated in a batch. In other words, this program can be said to cause a computer to execute the procedures and methods of operation of the components of the map data management device 10.
[0078] Here, the memory 52 may be, for example, a non-volatile or volatile semiconductor memory such as a RAM (Random Access Memory), a ROM (Read Only Memory), a flash memory, an EPROM (Erasable Programmable Read Only Memory), or an EEPROM (Electrically Erasable Programmable Read Only Memory), a HDD (Hard Disk Drive), a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, a DVD (Digital Versatile Disc), and a drive device for such a disk, or any other storage medium that will be used in the future.
[0079] The above describes a configuration in which the functions of the components of the map data management device 10 are realized either by hardware or software, etc. However, this is not a limitation, and the map data management device 10 may be configured such that some of the components are realized by dedicated hardware and other components are realized by software, etc. For example, the functions of some of the components may be realized by the processing circuit 50 as dedicated hardware, and the functions of other components may be realized by the processing circuit 50 as the processor 51 reading and executing a program stored in the memory 52.
[0080] As described above, the map data management device 10 can realize the above-mentioned functions by using hardware, software, or a combination of these.
[0081] It is possible to freely combine the embodiments, and to modify or omit the embodiments as appropriate.
[0082] The above description is illustrative in all respects, and it is understood that countless variations not illustrated can be envisioned.
[0083] 10 Map data management device, 11 Map database, 12 Map access unit, 13 Map update control unit, 14 Update map data download unit, 15 Update status storage unit, 16 Update map data storage unit, 20 In-vehicle device, 21 Communication device, 22 Positioning unit, 23 Map application, 24 Pre-read map data storage unit, 30 Map distribution server, 50 Processing circuit, 51 Processor, 52 Memory.
Claims
a map access unit that provides a map application of an in-vehicle device with map data stored in the map database in response to a request from the map application; an update map data download unit that downloads update map data from a map distribution server to update the map data of each mesh to the latest map data; and a map update control unit that updates the map data stored in the map database using the update map data, wherein the map update control unit predicts meshes for which map data will be requested by the map application based on the position of a vehicle in which the in-vehicle device is mounted, and identifies the meshes predicted to be requested for map data as requested predicted meshes, identifies meshes among the requested predicted meshes for which map data stored in the map database is not the latest as meshes requiring update, and updates the map data of the meshes requiring update, and when there are no more meshes requiring update within a predetermined range based on the position of the vehicle, increases the number of meshes requiring update for which the update map data download unit will download update map data in a batch, or the number of meshes for which the map update control unit will update map data in a batch.
2. The map data management device according to claim 1, wherein said map update control unit determines the range of map data to be updated simultaneously so that the range fits within one file of map data in said map database.
3. The map data management device of claim 1, wherein the map update control unit increases in multiple stages the number of meshes requiring update for which the update map data download unit downloads update map data in a batch, or the number of meshes requiring update for which the map update control unit updates map data in a batch, as the range without meshes requiring update expands after there are no meshes requiring update within a predetermined range based on the vehicle position.
4. A map data management method for managing a map database storing map data for each mesh obtained by dividing a map into meshes, comprising: a map access unit of a map data management device provides map data stored in the map database to a map application of an in-vehicle device in response to a request from the map application; an update map data download unit of the map data management device downloads update map data from a map distribution server to update map data for each mesh to the latest map data; a map update control unit of the map data management device updates the map data stored in the map database using the update map data; and in a process of updating the map data stored in the map database, the map update control unit predicts a mesh for which map data will be requested by the map application based on the position of the vehicle in which the in-vehicle device is mounted, and identifies the mesh predicted to be requested for map data as a requested predicted mesh; and identifies a mesh among the requested predicted meshes for which map data stored in the map database is not the latest as a mesh requiring update, and updates the map data for the mesh requiring update. when there are no more update-requiring meshes within a predetermined range based on the vehicle position, the update map data download unit increases the number of update-requiring meshes for which update map data is to be downloaded in a batch by the update map data download unit, or the number of update-requiring meshes for which map data is to be updated in a batch by the map update control unit.
Citation Information
Patent Citations
Map data update method, car navigation system, car navigation device and map center
JP2008309677A
Navigation device and navigation system
JP2011163951A
Potato egg sandwich
KR1020220002017A
Pre-fetching navigation maps
US8374782B2
Map presentation device
WO2019188165A1
