WO2022074792A1 - 地図データ更新装置及び地図データ更新方法 - Google Patents

地図データ更新装置及び地図データ更新方法 Download PDF

Info

Publication number
WO2022074792A1
WO2022074792A1 PCT/JP2020/038164 JP2020038164W WO2022074792A1 WO 2022074792 A1 WO2022074792 A1 WO 2022074792A1 JP 2020038164 W JP2020038164 W JP 2020038164W WO 2022074792 A1 WO2022074792 A1 WO 2022074792A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
update
mesh
map
map data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2020/038164
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
康志 小高
光生 下谷
聖悟 金澤
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Mitsubishi Electric Corp
Original Assignee
Mitsubishi Electric Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Mitsubishi Electric Corp filed Critical Mitsubishi Electric Corp
Priority to US18/018,916 priority Critical patent/US12474177B2/en
Priority to PCT/JP2020/038164 priority patent/WO2022074792A1/ja
Priority to DE112020007664.4T priority patent/DE112020007664T5/de
Priority to JP2022555202A priority patent/JP7378633B2/ja
Priority to CN202080105331.5A priority patent/CN116209877B/zh
Publication of WO2022074792A1 publication Critical patent/WO2022074792A1/ja
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
    • G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
    • G01C21/38—Electronic maps specially adapted for navigation; Updating thereof
    • G01C21/3804—Creation or updating of map data
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W60/00—Drive control systems specially adapted for autonomous road vehicles
    • B60W60/001—Planning or execution of driving tasks
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
    • G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
    • G01C21/38—Electronic maps specially adapted for navigation; Updating thereof
    • G01C21/3804—Creation or updating of map data
    • G01C21/3859—Differential updating map data
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
    • G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
    • G01C21/38—Electronic maps specially adapted for navigation; Updating thereof
    • G01C21/3863—Structures of map data
    • G01C21/387—Organisation of map data, e.g. version management or database structures
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W2556/00—Input parameters relating to data
    • B60W2556/40—High definition maps

Definitions

  • This disclosure relates to a map data updating device and a map data updating method.
  • a map database containing road data on a map (hereinafter, the database may be abbreviated as "DB") is used.
  • the map DB distribution server distributes (transmits) the latest map DB to the in-vehicle terminal, and the in-vehicle terminal distributes (transmits) the latest map DB to the map DB from the map DB distribution server.
  • Various techniques for updating the map DB based on this have been proposed.
  • the map DB of the map DB distribution server is updated periodically or irregularly
  • the map DB is stored in the map DB distribution server, and every time a new version of the map DB is generated. , The corresponding version of the map DB is delivered.
  • the nationwide or specific range of the map DB is represented by an aggregate of a plurality of areas obtained by dividing the range into a specific rectangular shape called a mesh (parcel).
  • the in-vehicle terminal updates the map DB, it requests the map DB distribution server to upgrade the map DB (update the version), and updates the map DB to the latest map DB at the time of distribution from the map DB distribution server.
  • Patent Document 1 proposes a configuration for storing a version upgrade list (version upgrade management file) that lists flags for update presence / absence for each version for each mesh.
  • an object of the present disclosure is to provide a technique capable of reducing the data size of the file for managing the update of the mesh file.
  • the map data updating device selectively updates a plurality of mesh files corresponding to one or more of a plurality of meshes obtained by dividing the map data by communicating with a server. It is a data updater, and has a bit array in which the positions of a plurality of bits are associated with the mesh IDs of a plurality of mesh files, and the 1-bit flag information indicating the necessity of updating the mesh file is the bit array.
  • a storage unit that stores the update necessity management file stored at the position corresponding to the mesh ID of the mesh file, and a specific mesh file that is a mesh file specified as a target to be used in a vehicle among a plurality of mesh files. Update unit that updates the specific mesh file based on the mesh ID and the update necessity management file, and updates the update necessity management file based on the update result of the specific mesh file and the received information received from the server. And.
  • the bit array has a bit array in which the positions of the plurality of bits are associated with the mesh IDs of the plurality of mesh files, and the 1-bit flag information indicating the necessity of updating the mesh file is included in the bit array.
  • the update necessity management file stored in the position corresponding to the mesh ID of the mesh file is used. With such a configuration, it is possible to reduce the data size of the file for managing the update of the mesh file.
  • FIG. It is a block diagram which shows the structure of the map DB update apparatus which concerns on Embodiment 1.
  • FIG. It is a figure which shows the data example of the update necessity management file which concerns on Embodiment 1.
  • FIG. It is a block diagram which shows the structure of the in-vehicle terminal which concerns on Embodiment 2.
  • It is a flowchart which shows the operation of the in-vehicle terminal which concerns on Embodiment 2.
  • FIG. 1 It is a figure which shows the mesh area which concerns on Embodiment 3. It is a flowchart which shows the operation of the vehicle control device which concerns on Embodiment 3. It is a flowchart which shows the operation of the vehicle control device which concerns on Embodiment 3. It is a flowchart which shows the operation of the vehicle control device which concerns on Embodiment 3. It is a figure which shows the mesh area which concerns on the modification 2 of Embodiment 3. It is a block diagram which shows the structure of the vehicle control device which concerns on Embodiment 4. FIG. It is a block diagram which shows the hardware composition of the map DB update apparatus which concerns on other modification. It is a block diagram which shows the hardware composition of the map DB update apparatus which concerns on other modification.
  • FIG. 1 is a block diagram showing a configuration of a map DB update device 1 and the like, which is a map data update device according to the first embodiment.
  • the map DB update device 1 can be moved together with the vehicle, for example, by being installed in the vehicle or being brought into the vehicle.
  • the vehicle that can be moved together with the map DB update device 1 and is the subject of attention may be referred to as "own vehicle”.
  • the map DB which is map data, is stored in the own vehicle or the map DB update device 1.
  • This map DB is divided into a plurality of meshes, and each of the plurality of mesh files corresponds to one or more meshes. That is, one mesh file corresponds to a part of the map DB.
  • one mesh file is described as corresponding to the range of one rectangular mesh, but may correspond to the range of a plurality of rectangular meshes.
  • the mesh file of the map DB is updated as appropriate, and the updated mesh file is transferred from the map DB distribution server 61 to the map DB update device 1 in response to a request from the map DB update device 1. It will be delivered.
  • the map DB update device 1 selectively updates a plurality of mesh files by communicating with such a map DB distribution server 61.
  • selectively updating a plurality of mesh files corresponds to updating one or more of the plurality of mesh files.
  • the map DB update device 1 of FIG. 1 includes a storage unit 11 and an update unit 12.
  • the storage unit 11 stores the update necessity management file.
  • FIG. 2 is a diagram showing a data example of the update necessity management file.
  • the update necessity management file has a bit array. In the bit array, the positions of the plurality of bits are associated with the mesh ID for identifying the plurality of mesh files.
  • FIG. 2 shows an example in which the map DB is divided into eight mesh files, and the eight mesh files are identified by the mesh IDs [1] to [8]. Then, the mesh ID [1] is associated with the position of the leftmost bit, the mesh ID [2] is associated with the position of the bit to the right of the mesh ID [1], and ... Is associated with the mesh ID [8].
  • the bit position and the mesh ID are associated with each other so that the mesh ID increases from the left to the right of the bit position.
  • the correspondence between these is the map DB. It may be changed as appropriate in consideration of the efficiency of data storage of the update device 1.
  • the update necessity flag which is 1-bit flag information indicating the necessity of updating the mesh file, is stored in the above bit array at the position corresponding to the mesh ID of the mesh file. For example, it is assumed that the update necessity flag having a 1-bit value of "1" indicates update necessity and the update necessity flag having a 1-bit value of "0" indicates update necessity.
  • the update necessity flag whose value is “0” is stored at the position corresponding to the mesh ID [1]
  • the mesh file of the mesh ID [1] does not need to be updated. It is shown.
  • the update necessity flag whose value is "1” is stored at the position corresponding to the mesh ID [2]
  • the mesh file of the mesh ID [2] needs to be updated. It is shown.
  • the mesh file specified as the target to be used in the own vehicle is referred to as a "specific mesh file".
  • the specific mesh file may be one mesh file or a plurality of mesh files.
  • the update unit 12 of FIG. 1 updates the specific mesh file stored in the own vehicle or the map DB update device 1 based on the mesh ID of the specific mesh file and the update necessity management file.
  • the update unit 12 receives the new mesh files of the mesh IDs [2] and [4] from the map DB distribution server 61. Then, the update unit 12 updates the specific mesh file (mesh file of mesh IDs [2] and [4]) stored in the own vehicle or the map DB update device 1 with the received mesh file.
  • the update unit 12 updates the update necessity management file based on the update result of the specific mesh file and the received information received from the map DB distribution server 61.
  • the update unit 12 sets the update necessity flags of the mesh IDs [2] and [4] of the update necessity management file. , Update from update required ("1") to update unnecessary (“0").
  • the update unit 12 has the mesh ID [3] of the update necessity management file of FIG.
  • the update necessity flag is updated from update unnecessary (“0”) to update necessary (“1”).
  • the map DB update device 1 has a bit array in which the positions of a plurality of bits are associated with the mesh IDs of the plurality of mesh files, and the necessity of updating the mesh file is determined.
  • the update necessity management file in which the 1-bit flag information to be shown is stored in the position corresponding to the mesh ID of the mesh file in the bit array is used.
  • the specific mesh file which is the mesh file specified as the target to be used in the own vehicle
  • the update necessity management file is used as the update necessity management file. Update based on.
  • the update of the mesh file which is less necessary, is suppressed, so that the consumption of the CPU resource and the memory resource of the own vehicle can be reduced.
  • FIG. 3 is a block diagram showing a configuration of an in-vehicle terminal 31a or the like provided with a map DB updating device 1 which is a map data updating device according to the second embodiment.
  • a map DB updating device 1 which is a map data updating device according to the second embodiment.
  • the in-vehicle terminal 31a communicates with the map DB distribution server 61 via the communication terminal 62.
  • the map DB distribution server 61 is the same as the map DB distribution server 61 of the first embodiment. However, the map DB distribution server 61 according to the second embodiment manages the version management file described later.
  • the in-vehicle terminal 31a uses the map DB, and the map DB is appropriately updated by the map DB updating device 1.
  • the in-vehicle terminal 31a of FIG. 3 includes not only the map DB update device 1, but also the map DB storage unit 32 which is a map data storage unit, the satellite positioning device 33, the vehicle sensor 34, and the own vehicle position which is a vehicle position detection unit. It includes a detection unit 35, a map DB access unit 36 which is a map data access unit, and a map application 37.
  • the map DB storage unit 32 stores a plurality of mesh files for the map DB which is map data.
  • one mesh file corresponds to the range of one rectangular mesh, but the present invention is not limited to this.
  • the map DB of the map DB storage unit 32 is, for example, a normal-precision map DB which is normal-precision map data and a high-precision map which is high-precision map data which is higher in accuracy than the normal-precision map DB.
  • the normal accuracy map DB is, for example, a map DB including the road shape of the road center line and having an error of several m level.
  • the high-precision map DB is, for example, a map DB that includes a lane shape of a lane center line and has an error of several centimeters.
  • the satellite positioning device 33 is, for example, a GNSS (Global Navigation Satellite System) receiver such as a GPS (Global Positioning System) receiver, and acquires positioning data indicating the position of the own vehicle measured by the satellite.
  • GNSS Global Navigation Satellite System
  • GPS Global Positioning System
  • the vehicle sensor 34 detects the sensor information of the own vehicle such as the vehicle speed pulse of the own vehicle and the acceleration of the own vehicle.
  • the vehicle sensor 34 may include a device that detects a state around the own vehicle.
  • the own vehicle position detection unit 35 detects the position of the own vehicle based on the positioning data acquired by the satellite positioning device 33 and the sensor information detected by the vehicle sensor 34.
  • the own vehicle position detection unit 35 may perform map matching processing of the position of the own vehicle based on the road shape included in the map DB of the map DB storage unit 32.
  • the map DB access unit 36 specifies the mesh file requested by the map application 37 among the plurality of mesh files stored in the map DB storage unit 32 as the specific mesh file described in the first embodiment. Then, the map DB access unit 36 outputs the map update request of the specific mesh file to the map DB update unit 12a of the map DB update device 1.
  • the map DB update unit 12a that has received the map update request performs a process of appropriately updating the specific mesh file.
  • the specific mesh file of the map DB storage unit 32 may or may not be updated by the process of the map DB update unit 12a.
  • the map DB access unit 36 reads the processed specific mesh file from the map DB storage unit 32 and outputs it to the map application 37.
  • the map application 37 is an application that uses a mesh file of the map DB, and requests a mesh file from the map DB access unit 36 based on the position of the own vehicle detected by the own vehicle position detection unit 35.
  • a navigation application for example, a navigation application, an ADAS application, an AD application, and the like are used.
  • the map DB update device 1 of FIG. 3 includes an update necessity management information storage unit 11a, a map DB update unit 12a, a communication I / F (interface) unit 13, and a new update information storage unit 14.
  • the update necessity management information storage unit 11a of FIG. 3 is included in the concept of the storage unit 11 of FIG. 1, and the map DB update unit 12a of FIG. 3 is included in the concept of the update unit 12 of FIG.
  • the update necessity management information storage unit 11a stores the update necessity management file similar to the update necessity management file described in the first embodiment.
  • the map DB update unit 12a When the map DB update unit 12a receives a map update request for the specific mesh file from the map DB access unit 36, the map DB update unit 12a receives a map update request for the specific mesh file, and the specific mesh of the map DB storage unit 32 is based on the mesh ID of the specific mesh file and the update necessity management file. Determine if you want to update the file.
  • the map DB update unit 12a determines that the specific mesh file is to be updated, the map DB update unit 12a receives a new mesh file corresponding to the specific mesh file from the map DB distribution server 61 via the communication I / F unit 13. Then, the map DB update unit 12a updates the specific mesh file of the map DB storage unit 32 with the received mesh file. Further, the map DB update unit 12a updates the update necessity management file based on the update result of the specific mesh file and the received information received from the map DB distribution server 61 via the communication I / F unit 13.
  • the communication I / F unit 13 controls the communication of the communication terminal 62 to communicate with the map DB distribution server 61.
  • any component of the map DB update device 1 transmits or receives to the map DB distribution server 61 via the communication I / F unit 13 or the like, and the component transmits or receives to the map DB distribution server 61. It may be abbreviated when it is received.
  • the new update information storage unit 14 appropriately stores the update file received from the map DB distribution server 61.
  • the received information according to the second embodiment is an update file, and this update file is generated based on the version control file managed by the map DB distribution server 61.
  • FIG. 4 is a diagram showing a mesh area, a mesh file, and a version control file according to the second embodiment.
  • the map area indicated by the map DB is divided into a plurality of mesh areas in a specific rectangular shape called a mesh (parcel).
  • the map area shown by the map DB is divided into 5 ⁇ 7 mesh areas.
  • a mesh ID for identifying the mesh area is assigned to each of the plurality of mesh areas.
  • 01 is assigned as a mesh ID to the lower left mesh area. Then, (i) adding 1 to the mesh ID number as it advances one step to the right, and (ii) assigning the next number of the mesh ID of the mesh area at the right end to the mesh area at the left end above the stage. And do.
  • the mesh ID assignment rule is not limited to this, and other assignment rules may be used.
  • the partial map DB including the road links and nodes in each mesh area is stored in the mesh file as shown in FIG. 4 (b).
  • m 1 to M
  • vn the version of the map DB.
  • M 35
  • a mesh file of 35 is used.
  • n indicates the version of the map DB.
  • FIG. 4C is a diagram showing a version control file according to the second embodiment. For example, a name indicating the version of the version control file (Ver.n in the example of FIG. 4C and n ⁇ 3) is given to the file name of the version control file.
  • the version of the map DB (Ver.3 in the example of FIG. 4C) when the mesh file of the mesh ID [01] is updated is stored as the version of the mesh file.
  • the version of the map DB (Ver.2 in the example of FIG. 4C) when the mesh file of the mesh ID [02] is updated is stored as the version of the mesh file.
  • the mesh file version is also stored at the following address.
  • the versions of the plurality of mesh files are often different from each other.
  • the version of the mesh file is the same as or smaller than the version of the map DB.
  • the version of the version control file is substantially the same as the version of the map DB because it is updated when any of the plurality of mesh files is updated.
  • the version of the map DB is Ver.
  • the versions of all the mesh files in the version control file are Ver. It is 1. Since the version control file as shown in FIG. 4D is not substantially used in the second embodiment, the version is Ver. The version control file of 1 does not have to be set.
  • FIG. 5 shows when the map DB is updated n times, that is, the version of the map DB is Ver. It is a figure which shows the various files stored in the vehicle-mounted terminal 31a and the map DB distribution server 61 when it is n.
  • the map DB distribution server 61 stores M ⁇ n mesh files with versions 1 to n, and n version control files with versions 1 to n.
  • the in-vehicle terminal 31a M mesh files having a version of n or less are stored, and one update necessity management file is stored. Even if the mesh file of one mesh ID in the map DB distribution server 61 is updated, the mesh file of the one mesh ID in the in-vehicle terminal 31a is not updated unless requested by the map application 37. Therefore, the version of the mesh file of the in-vehicle terminal 31a and the version of the mesh file of the map DB distribution server 61 may be the same or different even if the mesh ID is the same. That is, the version of the mesh file of the in-vehicle terminal 31a is somewhat independent of the version of the mesh file of the map DB distribution server 61.
  • the map DB distribution server 61 is the difference between the version management file (map DB) of the latest version (first version) and the version management file (map DB) of the version immediately before the latest version (second version). Generate an update file based on.
  • the update file is a file having the same data format as the update necessity management file, and the necessity of updating the mesh file is set for each mesh ID.
  • the map DB distribution server 61 sets the update necessity flag of the mesh ID of the update necessity management file for the mesh file that needs to be updated by the in-vehicle terminal 31a due to the update to the version control file. Generate an update file for.
  • the map DB distribution server 61 sets the update necessity flag of the mesh ID of the update necessity management file to be unnecessary for the mesh file that does not need to be updated by the in-vehicle terminal 31a due to the update to the version control file. Generate an update file for.
  • the update necessity flag having a value of "1" indicates that the specific mesh file having the corresponding mesh ID needs to be updated, and the update necessity flag having a value of "0". Indicates that the specific mesh file of the corresponding mesh ID does not need to be updated.
  • ⁇ Operation> 6 to 8 are flowcharts showing the operation of the in-vehicle terminal 31a according to the second embodiment.
  • the own vehicle position detection unit 35 in step S1 determines the position of the own vehicle based on the positioning data acquired by the satellite positioning device 33 and the sensor information detected by the vehicle sensor 34. To detect.
  • the own vehicle position detection unit 35 may perform map matching processing of the position of the own vehicle based on the road shape included in the map DB of the map DB storage unit 32.
  • the map application 37 acquires the position of the own vehicle detected by the own vehicle position detection unit 35.
  • step S2 the map application 37 requests the map DB access unit 36 for a mesh file required by the map application 37 based on the position of the own vehicle detected by the own vehicle position detection unit 35.
  • the map DB access unit 36 identifies the mesh file requested by the map application 37 as a specific mesh file, and outputs a map update request for the specific mesh file to the map DB update unit 12a.
  • the map DB update unit 12a that has received the map update request performs a process of appropriately updating the specific mesh file of the map DB storage unit 32.
  • the map DB access unit 36 reads the processed specific mesh file from the map DB storage unit 32.
  • step S3 the map application 37 acquires a specific mesh file read from the map DB storage unit 32 by the map DB access unit 36.
  • step S4 the map application 37 executes a navigation function, an ADAS function (driving support function), an AD function (automatic driving function), and the like using the specific mesh file acquired from the map DB access unit 36.
  • ADAS function driving support function
  • AD function automatic driving function
  • step S5 the vehicle-mounted terminal 31a terminates the map application 37 based on, for example, the stop of the drive source of the own vehicle (for example, at least one of the engine and the motor), or the presence or absence of the termination instruction of the map application 37. Judge whether or not. If it is determined to end, the operation of FIG. 6 ends, and if it is not determined to end, the process returns to step S1.
  • step S11 the map DB access unit 36 determines whether or not a mesh file request has been received from the map application 37. If it is determined that the request has been received, the process proceeds to step S12, and if it is not determined that the request has been received, the process of step S11 is repeated.
  • step S12 the map DB access unit 36 identifies the mesh file requested by the map application 37 as a specific mesh file, and outputs a map update request for the specific mesh file to the map DB update unit 12a.
  • the output of the map update request corresponds to an inquiry as to whether or not the specific mesh file has been updated to the latest.
  • step S13 the map DB access unit 36 determines whether or not the map data ready information has been received from the map DB update unit 12a.
  • the map data ready information is information output from the map DB update unit 12a to the map DB access unit 36 after the map DB update unit 12a that has received the map update request performs a process of appropriately updating the specific mesh file. Is. If it is determined that the map data ready information has been received, the process proceeds to step S14, and if it is not determined that the map data ready information has been received, the process of step S13 is repeated.
  • step S14 the map DB access unit 36 reads the specific mesh file from the map DB storage unit 32.
  • step S15 the map DB access unit 36 outputs the read specific mesh file to the map application 37. After that, the process returns to step S11.
  • the map DB update unit 12a confirms whether or not the version of the map DB has been updated on the map DB distribution server 61.
  • the map DB update unit 12a may make an inquiry to the map DB distribution server 61 on a regular or irregular basis, or the map DB distribution server 61 notifies the map DB update unit 12a on a regular or irregular basis. It may be a method.
  • step S22 If it is confirmed that the version has been updated, the process proceeds to step S22, and if it is not confirmed that the version has been updated, the process proceeds to step S23.
  • step S22 the map DB update unit 12a receives the update file generated based on the version management file from the map DB distribution server 61, and updates the update necessity management file based on the update file.
  • the update necessity flag corresponding to the mesh ID is updated as required for update.
  • the update of the update necessity management file will be described in detail later. After that, the process proceeds to step S23.
  • step S23 the map DB update unit 12a determines whether or not the map update request for the specific mesh file has been received from the map DB access unit 36. If it is determined that the map update request has been received, the process proceeds to step S24, and if it is not determined that the map update request has been received, the process returns to step S21.
  • step S24 the map DB update unit 12a acquires the update necessity flag of the position corresponding to the mesh ID of the specific mesh file in the bit array of the update necessity management file.
  • step S25 the map DB update unit 12a determines whether or not the update necessity flag indicates the update necessity. When it is determined that the update necessity flag indicates that update is necessary, the process proceeds to step S26, and when it is determined that the update necessity flag does not indicate update necessity (indicates that update is not necessary). Process proceeds to step S29.
  • step S26 the map DB update unit 12a requests a new mesh file from the map DB distribution server 61 for the specific mesh file indicated to be updated by the update necessity flag, and the map DB distribution server 61 requests a new mesh file. To receive.
  • step S27 the map DB update unit 12a overwrites the specific mesh file of the map DB storage unit 32 with the received mesh file.
  • the specific mesh file indicated as needing to be updated by the update necessity flag of the update necessity management file is updated.
  • step S28 the map DB update unit 12a needs to update the update necessity flag of the specific mesh file updated in step S27 among the update necessity management files (“1”) to update unnecessary (“0”). Update to. Since the update necessity flag updated to update unnecessary (“0”) is maintained as update unnecessary until it is updated in step S22, the processes of steps S26 to S28 are performed with respect to the update necessity flag. not.
  • step S29 the map DB update unit 12a outputs the map data ready information to the map DB access unit 36. After that, the process returns to step S21. Although not shown, the operations of FIGS. 6 to 8 are terminated by turning off the power or the like.
  • ⁇ Operation example> 9 and 10 are diagrams showing an operation example of the in-vehicle terminal 31a according to the second embodiment.
  • the map DB storage unit 32 and the update necessity management information storage unit 11a include a memory for which a power supply is secured or a non-volatile memory. Then, it is assumed that the mesh file and the update necessity management file are stored in their memories so that they will not disappear even if the drive source of the own vehicle (for example, at least one of the engine and the motor) is stopped.
  • the map DB distribution server 61 has Ver. Since only one mesh file exists, the version control file has the data as shown in FIG. 9A.
  • the update necessity management file in the initial state of the in-vehicle terminal 31a is the data as shown in FIG. 9B. Since the map DB of the in-vehicle terminal 31a is the latest version, the processes of steps S21, S23, S24, S25, and S29 in FIG. 8 are performed in order, but the update necessity management file in steps S22 and S28 is changed. not.
  • the version of the map DB of the map DB distribution server 61 is Ver. It is assumed that the version control file is updated to 2 and the data is as shown in FIG. 9 (c).
  • the mesh files of the mesh IDs [01], [06], [07], and [08] are Ver. It has been updated to 2, and the other mesh files have not been updated.
  • the updated new mesh file is stored in the map DB distribution server 61.
  • the version of the map DB is Ver.
  • the map DB distribution server 61 creates an update file (Ver. 2) as shown in FIG. 9 (d) according to the version upgrade of the map DB (version management file).
  • the update file has the same data format as the update necessity management file, and in the update file, the mesh ID, the bit address of the mesh file, and the update flag are associated with each other.
  • the update flag having a value of "1" indicates that the mesh file having the corresponding mesh ID has been updated in the map DB distribution server 61
  • the update flag having the value "0" indicates that the mesh file having the corresponding mesh ID has been updated. It shows that the mesh file has not been updated in the map DB distribution server 61.
  • the update flag of the update file is set by the map DB distribution server 61 based on the difference between the latest version of the version control file and the version control file of the version immediately before the latest version.
  • the version control file of the version immediately before the latest version is the version control file of FIG. 9 (a)
  • the version control file of the latest version is the version control file of FIG. 9 (c). Therefore, in the version upgrade from FIG. 9A to FIG. 9C to the version control file, "1" is set as the update flag for the updated mesh file, and the update flag is set for the unupdated mesh file. Is set to "0".
  • the map DB update unit 12a of the map DB update device 1 receives the update file of FIG. 9D from the map DB distribution server 61, the map DB update unit 12a performs the process of step S22 of FIG. For example, the map DB update unit 12a performs a bit operation for updating the update necessity management file based on the update file of FIG. 9D and the update necessity management file of FIG. 9B.
  • the map DB update unit 12a updates the update necessity management file as shown in FIG. 9E by performing bit-wise OR processing as a bit operation.
  • the update necessity management file is updated only by the bit-wise OR processing in this way, the update necessity management file can be updated at high speed.
  • the version of the map DB of the map DB distribution server 61 is Ver. It is assumed that the version control file has been updated to 3 and the data is as shown in FIG. 10 (a).
  • the mesh files of the mesh IDs [01], [02], and [03] are Ver. Updated to 3.
  • the mesh files of the mesh IDs [04] and [05] are Ver.
  • the mesh file of mesh ID [06], [07], [08] is Ver. It remains at 2.
  • the updated new mesh file is stored in the map DB distribution server 61.
  • the version of the map DB is Ver.
  • the map DB distribution server 61 updates the map DB (version management file) as shown in FIG. 10 (b) according to the version upgrade of the map DB (version management file) from FIG. 9 (b) to FIG. 10 (a).
  • Create (Ver.3) In the update file of FIG. 10B, when the version control file is upgraded, "1" is set as the update flag for the updated mesh file, and "0" is set as the update flag for the unupdated mesh file. File. As a result, "1” is set in the update flag of the mesh IDs [01] to [03], and "0” is set in the update flag of the mesh IDs [04] to [08].
  • the map DB update unit 12a of the map DB update device 1 receives the update file of FIG. 10B from the map DB distribution server 61, the map DB update unit 12a performs the process of step S22 of FIG. For example, the map DB update unit 12a performs a bit operation for updating the update necessity management file based on the update file of FIG. 10 (b) and the update necessity management file of FIG. 9 (f). In the second embodiment, the map DB update unit 12a updates the update necessity management file as shown in FIG. 10 (c) by performing bit-wise OR processing as a bit operation.
  • the update necessity flag of the mesh ID [06] is "0" at the time of FIG. 9 (f).
  • the latest version of the mesh file of mesh ID [06] is Ver. Since it is 2, the update necessity flag of the mesh ID [06] of the update necessity management file is "0".
  • Ver. In the version control file of 3, the latest version of the mesh file with mesh ID [06] is Ver. If it is 3, the update necessity flag of the mesh ID [06] of the update necessity management file becomes "1".
  • FIG. 10 (e) is a diagram showing a version of each mesh file of the in-vehicle terminal 31a when the update necessity management file of FIG. 10 (d) is obtained.
  • the information of FIG. 10 (e) may be appropriately stored in the in-vehicle terminal 31a. If the process of storing the information shown in FIG. 10 (e) indicating the version status is executed when the CPU resource of the in-vehicle terminal 31a is surplus, the deterioration of the real-time property of updating the mesh file due to the execution of the storage process is suppressed. can do.
  • FIG. 11 is a diagram showing a data example of the update necessity management file according to the second embodiment when the number of meshes is relatively large.
  • the mesh IDs [01] to [16] are stored in the 16-bit WORD data of the WORD address (0), and the mesh IDs [17] to [32] are of the WORD address (1). It is stored in 16-bit WORD data.
  • the update necessity management file can be updated at high speed.
  • the map DB distribution server 61 transmits (distributes) the version control file as shown in FIGS. 9 (b) and 10 (a), and the map DB update unit 12a generates an update file based on the version control file.
  • the map DB update unit 12a is between the version management file of the version (first version) newly received from the map DB distribution server 61 and the version management file of the version immediately before that version (second version). You may generate an update file based on the difference between.
  • the map DB update unit 12a may perform a bit operation for updating the update necessity management file based on the update file and the update necessity management file.
  • the latest version of the map DB is stored in the in-vehicle terminal 31a at the time of release. Then, in step S22 of FIG. 8 when the in-vehicle terminal 31a is in operation, the map DB update unit 12a has the latest version (Ver.nb) of the map DB obtained from the map DB distribution server 61 and the map DB of the in-vehicle terminal 31a. Compare with the version of (Ver.na).
  • the map DB update unit 12a is Ver. In order to update the update necessity management file of the map DB of na, Ver. From na + 1 to Ver. The update file up to nb is requested to the map DB distribution server 61, bit operation is performed, and the update necessity management file is updated.
  • the map DB update unit 12a may first perform a bit operation between a plurality of update files, and then perform a bit operation between the calculation result and the update necessity management file. Alternatively, the map DB update unit 12a may use Ver.
  • the update necessity management file of na's map DB and Ver. Bit operation is performed with the update file of na + 1, and the update necessity management file obtained by the bit operation and Ver. Bit operations may be performed on the update file of na + 2, and then bit operations on the update necessity management file and the update file may be performed in the order of the update file versions.
  • the update necessity flag having a value of "0" may indicate update necessity
  • the update necessity flag having a value of "1” may indicate update necessity.
  • the map DB update unit 12a performs bit-wise AND processing instead of bit-wise OR processing as bit operation, the same operation as in the second embodiment can be realized.
  • the update necessity management information storage unit 11a includes the non-volatile memory, and the update necessity management file and the like are stored in the non-volatile memory, but the present invention is not limited to this.
  • the update necessity management information storage unit 11a includes a non-volatile memory and a high-speed memory having a processing speed higher than that of the non-volatile memory.
  • the high-speed memory is, for example, a cache memory including an L1 cache, an L2 cache, an L3 cache, ..., Which is built in a SoC (system on chip).
  • the map DB update unit 12a loads at least a part of the update necessity management file stored in the non-volatile memory into the high-speed memory as an update necessity management work file at a predetermined start timing. .. At least a part of the update necessity management file may be the entire update necessity management file, or may be a part of the update necessity management file as in the modification 5 described later.
  • the predetermined start timing includes, for example, when the map DB update device 1 is started up by turning on the power, when the mesh file is upgraded, when the CPU load of the map DB update device 1 is small, and the like.
  • the map DB update unit 12a updates using the update necessity management work file instead of the update necessity management file. Specifically, the map DB update unit 12a updates the specific mesh file of the map DB storage unit 32 based on the mesh ID of the specific mesh file and the update necessity management work file. The map DB update unit 12a updates the update necessity management work file based on the received information such as the update file received from the map DB distribution server 61 and the update result of the specific mesh file.
  • the map DB update unit 12a stores the update necessity management work file in the non-volatile memory as at least a part of the update necessity management file at a predetermined end timing. As a result, the update of the update necessity management work file is reflected in the update necessity management file.
  • the predetermined end timing includes, for example, a shutdown time due to the power off of the map DB update device 1.
  • FIG. 12 is a flowchart showing an operation mainly performed by the map DB update unit 12a of the map DB update device 1 among the operations of the in-vehicle terminal 31a according to the present modification 4.
  • the operation of FIG. 12 is the same as the operation of adding steps S31 to S36 to the operation of FIG.
  • steps S31 to S36 will be mainly described.
  • step S31 the map DB update unit 12a uses at least a part of the update necessity management file stored in the non-volatile memory of the update necessity management information storage unit 11a as an update necessity management work file, and updates the update necessity. Load into the high-speed memory of the management information storage unit 11a.
  • step S21 If it is confirmed in step S21 that the version has been updated, the process proceeds to step S32, and if it is not confirmed that the version has been updated, the process proceeds to step S23.
  • step S32 the map DB update unit 12a performs the same processing as in step S22 of FIG. 8 in the update necessity management work file instead of the update necessity management file. Since the update necessity management work file is loaded in the high-speed memory, the map DB update unit 12a can perform the process of step S32 at a higher speed than the process of step S22. After that, the process proceeds to step S23.
  • step S23 If it is determined in step S23 that the map update request has been received, the process proceeds to step S33, and if it is not determined that the map update request has been received, the process proceeds to step S35.
  • step S33 the map DB update unit 12a performs the same processing as in step S24 of FIG. 8 in the update necessity management work file instead of the update necessity management file. Since the update necessity management work file is loaded in the high-speed memory, the map DB update unit 12a can perform the process of step S33 at a higher speed than the process of step S24.
  • step S25 If it is determined in step S25 that the update necessity flag indicates the need for update, the process proceeds to step S26, and if it is determined that the update necessity flag does not indicate the need for update, the process proceeds to step S26. Proceed to S29.
  • step S34 the map DB update unit 12a performs the same processing as in step S28 of FIG. 8 in the update necessity management work file instead of the update necessity management file. Since the update necessity management work file is loaded in the high-speed memory, the map DB update unit 12a can perform the process of step S34 at a higher speed than the process of step S28. After that, the processes of steps S29 and S35 are performed.
  • step S35 the map DB update unit 12a determines whether or not the predetermined end timing has been reached. If it is determined that the predetermined end timing has been reached, the process proceeds to step S36, and if it is not determined that the predetermined end timing has been reached, the process returns to step S21.
  • step S36 the map DB update unit 12a stores the update necessity management work file in the non-volatile memory as at least a part of the update necessity management file. After that, the operation of FIG. 12 ends.
  • the processing related to the update necessity management file can be performed at high speed. Since the size of the update necessity management file is small, it is possible to store the update necessity management work file in a high-speed memory in which a relatively small capacity is prepared, particularly a cache memory such as an L1 cache or an L2 cache.
  • the load is loaded into the high-speed memory in the same manner as in the modification 4.
  • the map DB update unit 12a uses only the sub-update necessity management file, which is a part of the update necessity management file stored in the non-volatile memory, as the update necessity management work file in the high-speed memory. Load into the cache memory that is.
  • the sub-update necessity management file is a partial file that manages the vehicle position mesh file, which is the mesh file in which the own vehicle is located, among the update necessity management files.
  • the sub-update necessity management stored in the cache memory is performed according to the change of the enlarged mesh area in which the own vehicle is located due to the movement of the own vehicle.
  • the file is switched.
  • the sub-update necessity management file is stored in the cache memory and the sub-update necessity management file can be switched as appropriate, the usage efficiency of the cache memory having a relatively small size is obtained. Can be enhanced.
  • the sub-update necessity management file is not limited to the partial file that manages the vehicle position mesh file among the update necessity management files, but is a partial file that manages the mesh file requested by the map application 37. May be good.
  • the update necessity management work file includes the first update necessity management work file and the second update necessity management work file.
  • the cache memory which is a high-speed memory, includes a first high-speed memory and a second high-speed memory, and the first high-speed memory has a higher processing speed than the second high-speed memory.
  • the L1 cache is used for the first high-speed memory
  • the L2 cache and the L3 cache are used for the second high-speed memory.
  • other combinations may be used for the first high-speed memory and the second high-speed memory, or an L4 cache or the like may be combined.
  • the first update necessity management work file corresponding to the sub update necessity management file is loaded in the first high-speed memory.
  • the second update necessity management work file corresponding to the update necessity management file covering the map excluding the sub update necessity management file is loaded in the second high-speed memory.
  • the first high-speed memory is used, so that the update is necessary or not. Can be determined at high speed.
  • the mesh file requested by the map application 37 does not move next to it and the access to the map DB is not continuous, it is slower than the first high-speed memory, but the main such as the non-volatile memory.
  • a second high speed memory which is faster than the memory, is used. Therefore, even in this case, the processing related to the update necessity management file can be performed at a high speed to some extent.
  • the map application 37 is an ADAS application or an AD application, the required mesh file is migrated as the own vehicle continuously moves on the traveling route which is the route of the own vehicle. The above effect is effective.
  • FIG. 13 is a block diagram showing a configuration of a vehicle control device 31b or the like provided with a map DB update device 1 which is a map data update device according to the third embodiment.
  • a map DB update device 1 which is a map data update device according to the third embodiment.
  • the configuration of the vehicle control device 31b according to the third embodiment is the same as the configuration in which the traveling control unit 38 and the peripheral detection sensor 39 are added in the configuration of the in-vehicle terminal 31a (FIG. 3) according to the second embodiment. ..
  • the map DB of the map DB storage unit 32 uses not only the above-mentioned normal accuracy map DB and high accuracy map DB but also the information detected by the peripheral detection sensor 39 to determine the position of the own vehicle. It includes a facility map DB which is facility map data for identification.
  • FIG. 14 is a diagram showing a mesh region according to the third embodiment.
  • 14 (a) shows the mesh area of the high-precision map DB
  • FIG. 14 (b) shows the mesh area of the normal-precision map DB
  • FIG. 14 (c) shows the mesh area of the facility map DB.
  • the mesh size (the size of the mesh area) of the normal accuracy map DB, the high accuracy map DB, and the facility map DB is set. They are the same as each other, and their mesh files are managed by one update necessity management file. Then, the specific mesh file and the update necessity management file are collectively updated for the meshes of the normal accuracy map DB, the high accuracy map DB, and the facility map DB.
  • the map application 37 searches for a traveling route (route on which the own vehicle travels) based on the position of the own vehicle detected by the own vehicle position detection unit 35 based on the positioning data and the sensor information and the normal accuracy map DB. (presume. For searching the travel route, for example, a search function similar to that of a general navigation device is used.
  • the map DB access unit 36 obtains at least one of a mesh file on the travel route, a mesh file around it, and a mesh file in front of the travel route based on the travel route information acquired from the map application 37. Specify as a specific mesh file.
  • the travel route information may be any information such as the link ID, the link shape, the coordinates of the branch point, or other information that can identify the mesh file corresponding to the travel route.
  • the map DB access unit 36 outputs the map update request of the specific mesh file to the map DB update unit 12a of the map DB update device 1.
  • the map DB update unit 12a that has received the map update request performs a process of appropriately updating the specific mesh file.
  • the map DB access unit 36 outputs the facility map DB after the processing by the map DB update unit 12a to the own vehicle position detection unit 35. Further, the map DB access unit 36 outputs the high-precision map DB after the processing by the map DB update unit 12a to the map application 37.
  • the peripheral detection sensor 39 which is a sensor of the vehicle, detects information around the own vehicle.
  • the peripheral detection sensor 39 for example, an image recognition sensor that recognizes an image around the own vehicle taken by the camera, LiDAR (light detection and ranging), and the like are used.
  • the own vehicle position detection unit 35 controls the running of the own vehicle based on the facility map DB after the processing by the map DB update unit 12a and the information around the own vehicle detected by the peripheral detection sensor 39. Detects the position of the own vehicle used for. For example, the own vehicle position detection unit 35 collates the shape of the facility stored in the facility map DB with the image recognition result detected by the peripheral detection sensor 39, and detects the position of the own vehicle in lane units. The accuracy of the position of the own vehicle detected in this way is higher than the accuracy of the position of the own vehicle detected based on the positioning data of the satellite positioning device 33 and the sensor information of the vehicle sensor 34. The position of the own vehicle detected based on the facility map DB and the information around the own vehicle of the peripheral detection sensor 39 may be used for searching the traveling route after the position of the own vehicle is detected.
  • the map application 37 acquires the position of the own vehicle detected by the own vehicle position detection unit 35 based on the facility map DB and the information around the own vehicle of the peripheral detection sensor 39, and determines the position of the own vehicle. A configuration for outputting to the travel control unit 38 will be described. However, the present invention is not limited to this, and the position detection unit 35 of the own vehicle may directly output the position of the own vehicle to the traveling control unit 38.
  • the map application 37 provides road information in front of or around the own vehicle based on the position of the own vehicle from the own vehicle position detection unit 35 and the high-precision map DB after processing by the map DB update unit 12a. Is output to the travel control unit 38.
  • the road information in front of the own vehicle includes, for example, the shape of a lane and the position information of a signboard, and the output format may be relative coordinates with the own vehicle as the origin.
  • the travel control unit 38 controls the travel of the own vehicle based on the output information from the map application 37. That is, the high-precision map data after the processing by the map DB update unit 12a is indirectly used for controlling the traveling of the vehicle.
  • the travel control unit 38 for example, an ADAS ECU (Electronic Control Unit) and an AD ECU (Electronic Control Unit) capable of controlling in lane units are used.
  • ⁇ Operation> 15 and 16 are flowcharts showing the operation of the vehicle control device 31b according to the third embodiment. First, the operation mainly performed by the traveling control unit 38 will be described with reference to FIG.
  • step S41 the travel control unit 38 acquires the position of the own vehicle based on the facility map DB after the processing by the map application 37 and the map DB update unit 12a. Further, the travel control unit 38 acquires road information in front of or around the own vehicle extracted based on the high-precision map DB after the processing by the map DB update unit 12a is performed from the map application 37.
  • step S42 the travel control unit 38 controls the travel of the own vehicle based on the position of the own vehicle and the road information.
  • step S43 the travel control unit 38 determines whether or not the drive source of the own vehicle has stopped. If it is determined that the drive source has stopped, the operation of FIG. 15 ends, and if it is not determined that the drive source has stopped, the process returns to step S41.
  • step S51 the own vehicle position detection unit 35 detects the position of the own vehicle based on the positioning data of the satellite positioning device 33 and the sensor information of the vehicle sensor 34.
  • step S52 the map application 37 searches for a travel route based on the position of the own vehicle and the normal accuracy map DB.
  • the position of the own vehicle detected in step S51 may be used as the position of the own vehicle used for searching the travel route.
  • step S53 the map application 37 outputs the travel route information to the map DB access unit 36.
  • step S54 the map application 37 performs the same application end determination process as in step S5 (FIG. 6).
  • the map DB access unit 36 acquires travel route information from the map application 37.
  • the route information is not limited to this, and may be acquired from a navigation device on the vehicle system, an external smartphone device, a server application, or the like.
  • the map DB access unit 36 is at least one of a mesh file of the high-precision map DB on the travel route, a mesh file around it, and a mesh file in front of the travel route, based on the information of the travel route. Select (specify) one of them as a specific mesh file.
  • step S63 the map DB access unit 36 outputs a map update request for the specific mesh file to the map DB update unit 12a. After that, the process returns to step S61. At this time, the same processing as in steps S13 to S15 of FIG. 7 may be performed.
  • step S25 and step S26 are performed for the normal accuracy map DB, the high accuracy map DB, and the facility map DB.
  • the high-precision map data after the processing by the map DB updating unit 12a is used for controlling the traveling of the own vehicle, and the processing by the map DB updating unit 12a is performed.
  • the facility map data after this is used to detect the position of the own vehicle.
  • the data with enhanced real-time performance for updating can be used for controlling the running of the own vehicle such as ADAS and AD.
  • the mesh files of the normal accuracy map DB, the high accuracy map DB, and the facility map DB are managed by one update necessity management file.
  • the mesh files of the normal accuracy map DB, the high accuracy map DB, and the facility map DB are not always updated at the same time.
  • the update necessity may be set individually in the three types of map DBs. ..
  • the map DB update unit 12a may update the specific mesh file and the update necessity management file individually in all of the normal accuracy map DB, the high accuracy map DB, and the facility map DB.
  • one update necessity management file is assigned to any two of the normal accuracy map DB, the high accuracy map DB, and the facility map DB, and another update necessity management file is assigned to the remaining one.
  • the necessity of updating the two types of map DB and the necessity of updating the one type of map DB may be set individually.
  • the map DB update unit 12a may update the specific mesh file and the update necessity management file individually in the two types of map DB and the one type of map DB.
  • the facility map DB is stored in the update necessity management file for each facility category
  • the facility map DB having a plurality of facility categories may be stored in a plurality of update necessity management files.
  • the mesh sizes of the normal accuracy map DB, the high accuracy map DB, and the facility map DB are the same as each other, but the size is not limited to this.
  • the mesh sizes may be different from each other.
  • FIG. 18 is a diagram showing a mesh region according to the present modification 2.
  • FIG. 18A shows the mesh area of the high-precision map DB
  • FIG. 18B shows the mesh area of the normal-precision map DB
  • FIG. 18C shows the mesh area of the facility map DB.
  • the mesh size of the high-precision map DB is the smallest, and the mesh size of the facility map DB is the largest, but the size is not limited to this.
  • the mesh size may be set based on the data size of the map DB and the update frequency, not the type of the map DB. For example, the larger the data size, the smaller the mesh size may be set, and the more frequently updated, the smaller the mesh size may be set. Further, the mesh sizes may be different from each other in two instead of three of the normal accuracy map DB, the high accuracy map DB, and the facility map DB.
  • the update necessity management information storage unit 11a includes a high-speed memory as in the fourth modification of the second embodiment.
  • the high-speed memory of the present modification 3 includes the first, second, and third high-speed memories having different processing speeds from each other. The processing speed of the first high-speed memory is the highest, and the processing speed of the third high-speed memory is the lowest.
  • the update necessity management work file corresponding to the update necessity management file is the first and first mesh files used for a plurality of mesh files of the high-precision map DB, the facility map DB, and the normal-precision map DB, respectively. Includes 2nd and 3rd update necessity management work files. Then, the update necessity management file for managing the high-precision map DB is loaded as the first update necessity management work file in the first high-speed memory having the highest processing speed. The update necessity management file that manages the facility map DB is loaded into the second high-speed memory as the second update necessity management work file. The update necessity management file that manages the normal accuracy map DB is loaded as the third update necessity management work file in the third high-speed memory having the lowest processing speed. Then, the same operation (FIG. 12) as in the modified example 4 of the second embodiment is performed on the first, second, and third update necessity management work files.
  • FIG. 19 is a block diagram showing a configuration of a vehicle control device 31b or the like provided with a map DB update device 1 which is a map data update device according to the fourth embodiment.
  • a map DB update device 1 which is a map data update device according to the fourth embodiment.
  • the map DB update device 1 according to the fourth embodiment is different from the map DB update device 1 (FIG. 13) according to the third embodiment in that the map DB storage unit 32 and the map DB access unit 36 are further provided. Even with such a configuration, the same effect as that of the third embodiment can be obtained.
  • the configuration of the map DB update device 1 is not limited to the configuration of FIG. 13 and the configuration of FIG.
  • the map DB update device 1 of the vehicle control device 31b may be configured to further include at least one of a map DB storage unit 32, a own vehicle position detection unit 35, and a map DB access unit 36. That is, the map DB update device 1 of the vehicle control device 31b may be configured to further include components other than the map DB update device 1 among the components of the vehicle control device 31b of FIG.
  • the vehicle control device 31b (FIG. 13) described in the third embodiment is modified in the fourth embodiment, the same applies to the in-vehicle terminal 31a (FIG. 3) described in the second embodiment. It may be a modified configuration.
  • the map DB update device 1 of the vehicle-mounted terminal 31a may be configured to further include at least one of a map DB storage unit 32, a vehicle position detection unit 35, and a map DB access unit 36. That is, the map DB update device 1 of the vehicle-mounted terminal 31a may be configured to further include components other than the map DB update device 1 among the components of the vehicle-mounted terminal 31a of FIG.
  • the storage unit 11 and the update unit 12 of FIG. 1 described above are hereinafter referred to as “update unit 12 and the like”.
  • the update unit 12 and the like are realized by the processing circuit 81 shown in FIG. That is, the processing circuit 81 updates the specific mesh file based on the storage unit 11 that stores the update necessity management file, the mesh ID of the specific mesh file, and the update necessity management file, and the specific mesh file. It includes an update unit 12 that updates the update necessity management file based on the update result and the received information received from the map DB distribution server 61.
  • Dedicated hardware may be applied to the processing circuit 81, or a processor that executes a program stored in the memory may be applied to the processing circuit 81.
  • the processor corresponds to, for example, a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, a DSP (Digital Signal Processor), and the like.
  • the processing circuit 81 may be, for example, a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, an ASIC (Application Specific Integrated Circuit), or an FPGA (Field Programmable Gate). Array), or a combination of these.
  • Each of the functions of each part such as the update unit 12 may be realized by a circuit in which the processing circuits are distributed, or the functions of each part may be collectively realized by one processing circuit.
  • the processing circuit 81 When the processing circuit 81 is a processor, the functions of the update unit 12 and the like are realized by combining with software and the like.
  • the software or the like corresponds to, for example, software, firmware, or software and firmware.
  • Software and the like are described as programs and stored in memory.
  • the processor 82 applied to the processing circuit 81 realizes the functions of each part by reading and executing the program stored in the memory 83. That is, when the map DB update device 1 is executed by the processing circuit 81, the specific mesh file is based on the step of storing the update necessity management file, the mesh ID of the specific mesh file, and the update necessity management file.
  • the step of updating the update necessity management file based on the update result of the specific mesh file and the received information received from the map DB distribution server 61 is a program that will be executed as a result.
  • a memory 83 for storing the file 83 is provided.
  • this program causes the computer to execute the procedure or method of the update unit 12 or the like.
  • the memory 83 is, for example, non-volatile such as RAM (RandomAccessMemory), ROM (ReadOnlyMemory), flash memory, EPROM (ErasableProgrammableReadOnlyMemory), EPROM (ElectricallyErasableProgrammableReadOnlyMemory), or the like.
  • Volatile semiconductor memory HDD (HardDiskDrive), magnetic disk, flexible disk, optical disk, compact disk, mini disk, DVD (DigitalVersatileDisc), its drive device, etc., or any storage medium that will be used in the future. You may.
  • each function of the update unit 12 and the like is realized by either hardware or software has been described above.
  • the present invention is not limited to this, and a configuration may be configured in which a part of the update unit 12 or the like is realized by dedicated hardware and another part is realized by software or the like.
  • the update unit 12 realizes its function by a processing circuit 81 as dedicated hardware and an interface, and other than that, the processing circuit 81 as a processor 82 reads a program stored in the memory 83. It is possible to realize the function by executing it.
  • the processing circuit 81 can realize each of the above-mentioned functions by hardware, software, or a combination thereof.
  • the map DB update device 1 described above includes a vehicle device such as a PND (Portable Navigation Device), a navigation device, an ADAS function, and a travel control device for performing an AD function, and a mobile phone, a smartphone, a tablet, or the like. It can also be applied to a map DB update system constructed as a system by appropriately combining a communication terminal including a terminal, a function of an application installed in at least one of a vehicle device and a communication terminal, and a server. In this case, each function or each component of the map DB update device 1 described above may be distributed and arranged in each device for constructing the system, or may be centrally arranged in any of the devices. May be good.
  • a vehicle device such as a PND (Portable Navigation Device), a navigation device, an ADAS function, and a travel control device for performing an AD function
  • a mobile phone a smartphone, a tablet, or the like. It can also be applied to a map DB update system constructed as a system by appropriately
  • map DB update device 11 storage unit, 12 update unit, 32 map DB storage unit, 35 own vehicle position detection unit, 36 map DB access unit, 61 map DB distribution server.

Landscapes

  • Engineering & Computer Science (AREA)
  • Radar, Positioning & Navigation (AREA)
  • Remote Sensing (AREA)
  • Automation & Control Theory (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Human Computer Interaction (AREA)
  • Transportation (AREA)
  • Mechanical Engineering (AREA)
  • Navigation (AREA)
  • Instructional Devices (AREA)
  • Traffic Control Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
PCT/JP2020/038164 2020-10-08 2020-10-08 地図データ更新装置及び地図データ更新方法 Ceased WO2022074792A1 (ja)

Priority Applications (5)

Application Number Priority Date Filing Date Title
US18/018,916 US12474177B2 (en) 2020-10-08 2020-10-08 Map data update apparatus and map data update method
PCT/JP2020/038164 WO2022074792A1 (ja) 2020-10-08 2020-10-08 地図データ更新装置及び地図データ更新方法
DE112020007664.4T DE112020007664T5 (de) 2020-10-08 2020-10-08 Kartendaten-Aktualisierungsvorrichtung und Kartendaten-Aktualisierungsverfahren
JP2022555202A JP7378633B2 (ja) 2020-10-08 2020-10-08 地図データ更新装置及び地図データ更新方法
CN202080105331.5A CN116209877B (zh) 2020-10-08 2020-10-08 地图数据更新装置和地图数据更新方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2020/038164 WO2022074792A1 (ja) 2020-10-08 2020-10-08 地図データ更新装置及び地図データ更新方法

Publications (1)

Publication Number Publication Date
WO2022074792A1 true WO2022074792A1 (ja) 2022-04-14

Family

ID=81126365

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2020/038164 Ceased WO2022074792A1 (ja) 2020-10-08 2020-10-08 地図データ更新装置及び地図データ更新方法

Country Status (5)

Country Link
US (1) US12474177B2 (https=)
JP (1) JP7378633B2 (https=)
CN (1) CN116209877B (https=)
DE (1) DE112020007664T5 (https=)
WO (1) WO2022074792A1 (https=)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115913323A (zh) * 2022-10-14 2023-04-04 西安空间无线电技术研究所 一种基于时空网格的低轨接入选择方法、存储介质

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE112020007664T5 (de) * 2020-10-08 2023-10-05 Mitsubishi Electric Corporation Kartendaten-Aktualisierungsvorrichtung und Kartendaten-Aktualisierungsverfahren
CN115186048A (zh) * 2022-08-03 2022-10-14 浙江吉利控股集团有限公司 基于地理网格的地图数据更新方法、装置、设备及介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006220524A (ja) * 2005-02-10 2006-08-24 Alpine Electronics Inc 地図更新処理用データ作成方法、地図更新方法及び装置
JP2012037798A (ja) * 2010-08-10 2012-02-23 Mitsubishi Electric Corp 地図情報処理装置
JP2018169316A (ja) * 2017-03-30 2018-11-01 アイシン・エィ・ダブリュ株式会社 通信端末、サーバ装置、移動案内システム及びコンピュータプログラム

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004008073A1 (ja) * 2002-07-17 2004-01-22 Xanavi Informatics Corporation ナビゲーション方法、ナビゲーションシステムのための処理方法、地図データ管理装置、地図データ管理プログラム、及びコンピュータプログラム
JP5082295B2 (ja) * 2006-05-19 2012-11-28 株式会社デンソー 地図データ提供装置
US20120130944A1 (en) * 2009-10-21 2012-05-24 Hisanobu Masuda Map information processing device
WO2012095974A1 (ja) 2011-01-13 2012-07-19 パイオニア株式会社 地図データ更新装置、地図データ更新方法及び地図データ更新プログラム、並びに地図データ更新システム
US20130038625A1 (en) * 2011-08-10 2013-02-14 Isao Nakajima Method and apparatus for rendering anti-aliased graphic objects
JP2015125359A (ja) * 2013-12-27 2015-07-06 株式会社日立製作所 地図データ配信システム
KR101599133B1 (ko) * 2014-06-09 2016-03-15 주식회사 엔지스테크널러지 네비게이션 장치의 지도 데이터 제공 방법 및 시스템
JP2017116373A (ja) * 2015-12-24 2017-06-29 株式会社シーズ・ラボ 地図更新装置、地図更新サーバおよび地図更新方法
JP6747097B2 (ja) * 2016-06-29 2020-08-26 アイシン・エィ・ダブリュ株式会社 サーバ装置及びコンピュータプログラム
CA3037575A1 (en) * 2016-09-22 2018-03-29 The University Of British Columbia Geometric modelling for facilitating simulation for manufacturing operations
US20190313224A1 (en) * 2018-04-10 2019-10-10 GM Global Technology Operations LLC Automated vehicle systems and control logic for smart data exchanges using enhanced bloom filters
CN111475514B (zh) * 2019-01-23 2023-05-26 阿里巴巴集团控股有限公司 地图数据制作方法、更新方法及装置、介质、设备
DE112020007664T5 (de) * 2020-10-08 2023-10-05 Mitsubishi Electric Corporation Kartendaten-Aktualisierungsvorrichtung und Kartendaten-Aktualisierungsverfahren

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006220524A (ja) * 2005-02-10 2006-08-24 Alpine Electronics Inc 地図更新処理用データ作成方法、地図更新方法及び装置
JP2012037798A (ja) * 2010-08-10 2012-02-23 Mitsubishi Electric Corp 地図情報処理装置
JP2018169316A (ja) * 2017-03-30 2018-11-01 アイシン・エィ・ダブリュ株式会社 通信端末、サーバ装置、移動案内システム及びコンピュータプログラム

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115913323A (zh) * 2022-10-14 2023-04-04 西安空间无线电技术研究所 一种基于时空网格的低轨接入选择方法、存储介质

Also Published As

Publication number Publication date
US12474177B2 (en) 2025-11-18
CN116209877B (zh) 2025-02-25
US20230304825A1 (en) 2023-09-28
JP7378633B2 (ja) 2023-11-13
DE112020007664T5 (de) 2023-10-05
CN116209877A (zh) 2023-06-02
JPWO2022074792A1 (https=) 2022-04-14

Similar Documents

Publication Publication Date Title
US8700330B2 (en) Vehicle navigation device and method
JP7378633B2 (ja) 地図データ更新装置及び地図データ更新方法
CN109387208B (zh) 一种地图数据的处理方法、装置、设备和介质
JP7297169B2 (ja) 地図データ管理装置および地図データ管理方法
JP2006003385A (ja) 地図データ提供装置
US20090216771A1 (en) Map update system, methods, and programs
CN114162140A (zh) 一种最优车道匹配方法及系统
US10001381B2 (en) Presentation plan creation apparatus, information presentation apparatus, and presentation plan creation method
JP7447272B2 (ja) 地図提供システム
CN1892181A (zh) 数据结构、信息生成装置、信息生成方法以及导航设备
US10452530B2 (en) Information processing apparatus and information processing method
CN105631038B (zh) 导航地图的生成方法和系统，及具有该系统的电子设备
CN111337045A (zh) 车辆导航方法和装置
CN112182129B (zh) 高精度地图更新方法及装置
WO2024247171A1 (ja) 地図データ管理装置および地図データ管理方法
JP7202197B2 (ja) 地図提供装置
WO2022153528A1 (ja) 地図データ管理装置および地図データ管理方法
US20130002658A1 (en) Vehicle navigation device and method
JP7162724B2 (ja) 車載制御装置
JP2021124813A (ja) 処理システム及びデータ構造
US20250378065A1 (en) Method, apparatus and computer program to manage map data
JP6403407B2 (ja) データ更新方法、データ更新システム及び端末装置
WO2026023002A1 (ja) 運転支援策定装置、運転支援策定システム、および運転支援策定方法
CN113010622A (zh) 实时交通数据的处理方法、装置及电子设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20956739

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022555202

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 112020007664

Country of ref document: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20956739

Country of ref document: EP

Kind code of ref document: A1

WWG Wipo information: grant in national office

Ref document number: 202080105331.5

Country of ref document: CN

WWG Wipo information: grant in national office

Ref document number: 18018916

Country of ref document: US