IP Library Granted Patent US 12,366,462
Granted Patent B2
US 12,366,462 · App. 17/576,545 · Granted Jul 22, 2025

Validating high definition mapping data

Inventors: Ryan Waskiewicz (Pittsburgh, PA); Brad Krupa (Pittsburgh, PA); Mark Theodore Tomczak (Pittsburgh, PA); Daniel Scott Fitzpatrick (Pittsburgh, PA)
Assignee: Volkswagen Group of America Investments, LLC
G01C21/387B60W60/001G01C21/3837G01C21/3896
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,366,462
App. No.
17/576,545
Granted
Jul 22, 2025
Kind
B2
Abstract

Disclosed herein are system and method embodiments to implement a validation of a vector map. The validation process may merge proposed and persisted high-definition mapping data, evaluate the high-definition mapping data with a set of customizable validation rules, return/persist validation results, and provide a means to acknowledge validation failures to minimize creation of problematic vector map content.

Claims (40)

1. A method of generating a vector map, the method comprising:

receiving, by a map data store, a proposed vector map content change to features defined on the vector map, wherein the features are associated with traffic control measures to direct operations of an autonomous vehicle;

testing the proposed vector map content change against a vector map policy, wherein the vector map policy represents rules defining functional principles of the traffic control measures for at least the proposed vector map content change;

receiving a first indication that the proposed vector map content change failed the testing;

in response to receiving a user acknowledgement of the failed testing, validating the user acknowledgment;

outputting, to the map data store, an indicator of the validation to assist in publishing a new version of the vector map based on the failure, wherein the indicator of the validation includes a severity level of a validation failure selected from a set of multiple validation failure severity levels, and wherein the severity level indicates a significance of the validation failure to a health of the vector map;

publishing, based on the indicator, the new version of the vector map, wherein the new version includes a first map parcel with validation failures below a severity threshold and a second map parcel with the validation failures above the severity threshold; and

communicating the new version of the vector map to the autonomous vehicle, wherein the second map parcel is flagged as non-operational for the autonomous vehicle.

2. The method of claim 1 , wherein the indicator further comprises a valid or invalid status of the user acknowledgement.

3. The method of claim 2 , further comprising, for the valid status, checking the severity threshold of the failed testing to at least partially assist in a publishing decision.

4. The method of claim 2 , further comprising, for the invalid status, initiating a repair of the proposed vector map content change.

5. The method of claim 1 , wherein the severity threshold comprises any of: experimental, critical, flagged, required, information only, or warning.

6. The method of claim 1 , wherein the second map parcel is flagged by suppressing publishing of a map area where the proposed vector map content change is located.

7. The method of claim 6 , wherein the publishing further comprises adding the second map parcel to a list of suppressed areas for the new version of the vector map.

8. The method of claim 1 , wherein the vector map features comprise any of:

streets, buildings, traffic signs or traffic signals.

9. A vector map processing system, comprising:

a memory; and

at least one processor coupled to the memory and configured to:

define features on a vector map, wherein the features are associated with traffic control measures to direct operations of an autonomous vehicle;

receive a proposed vector map content change to the features on the vector map;

test the proposed vector map content change against a vector map policy, wherein the vector map policy represents rules defining functional principles of the traffic control measures for the vector map content;

receive a testing indication that the proposed vector map content change failed the testing and a severity of the failed testing;

receive a user acknowledgement of the testing indication that the proposed vector map content change failed the testing and the severity of the failure;

in response to receiving the user acknowledgment, validate the user acknowledgment;

output a validation indication to assist in publishing a new version of the vector map based on the failure, wherein the indicator of the validation includes a severity level of a validation failure selected from a set of multiple validation failure severity levels, and wherein the severity level indicates a significance of the validation failure to a health of the vector map;

publish, based on the indicator, the new version of the vector map, wherein the new version includes a first map parcel with validation failures below a severity threshold and a second map parcel with validation failures above the severity threshold; and

communicate the new version of the vector map to the autonomous vehicle, wherein the second map parcel is flagged as non-operational for the autonomous vehicle.

10. The vector map processing system of claim 9 , wherein the at least one processor is further configured to suppress an area that includes the second map parcel, including the proposed vector map content change, during the publishing of the new version of the vector map.

11. The vector map processing system of claim 10 , wherein the at least one processor is further configured to add the suppressed area to a list of suppressed areas for the new version of the vector map.

12. The vector map processing system of claim 9 , wherein the vector map features comprise any of: streets, buildings, stop signs or traffic signals.

13. The vector map processing system of claim 9 , wherein the validation indication further comprises a valid or invalid status.

14. A method of publishing a vector map comprising:

defining features in one or more areas of the vector map, wherein the features are associated with traffic control measures to direct operations of an autonomous vehicle;

receiving a proposed vector map content change to the features on the vector map;

testing the proposed vector map content change against a vector map policy, wherein the vector map policy is represented by rules defining functional principles of the traffic control measures of the vector map content change;

receiving an indication that the proposed vector map content change fails the testing;

determining that a user acknowledgement was not received for the failed testing;

publishing, based on the user acknowledgement not being received for the failed testing, a new version of the vector map by suppressing an area of the vector map where the vector map content change is located; and

communicating the new version of the vector map to the autonomous vehicle, wherein the suppressed area is non-operational for the autonomous vehicle.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 7, 2024
From: ARGO AI, LLC
To: VOLKSWAGEN GROUP OF AMERICA INVESTMENTS, LLC
Reel/Frame 069113/0265 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 18, 2022
From: WASKIEWICZ, RYAN; KRUPA, BRAD; TOMCZAK, MARK THEODORE; FITZPATRICK, DANIEL SCOTT
To: ARGO AI, LLC
Reel/Frame 058679/0126 →
Continuity (1)
Related Publication 20230228594A1 · Jul 20, 2023
References Cited (27)
US 9514378B2 · Armstrong-Crews et al. · 2016 [cited by applicant]
US 10054678B2 · Mei et al. · 2018 [cited by applicant]
US 10200877B1 · Skidmore · 2019 [cited by examiner]
US 10220766B2 · Soehner et al. · 2019 [cited by applicant]
US 10416679B2 · Lipson et al. · 2019 [cited by applicant]
US 10445599B1 · Hicks · 2019 [cited by applicant]
US 20060047420A1 · Tanaka · 2006 [cited by applicant]
US 20170248693A1 · Kim · 2017 [cited by applicant]
US 20180157269A1 · Prasad et al. · 2018 [cited by applicant]
US 20180284779A1 · Nix · 2018 [cited by applicant]
US 20180299534A1 · LaChapelle et al. · 2018 [cited by applicant]
US 20190129009A1 · Eichenholz et al. · 2019 [cited by applicant]
US 20190390965A1 · Jiao et al. · 2019 [cited by applicant]
US 20200159244A1 · Chen et al. · 2020 [cited by applicant]
US 20210108926A1 · Tran · 2021 [cited by examiner]
US 20210157316A1 · Liu · 2021 [cited by examiner]
US 20210356277A1 · Fok · 2021 [cited by examiner]
US 20220057231A1 · Ma et al. · 2022 [cited by applicant]
US 20220341750A1 · Akbarzadeh · 2022 [cited by examiner]
CN 111272190B · 2023 [cited by examiner]
EP 3349146A1 · 2018 [cited by applicant]
EP 3396408A1 · 2018 [cited by applicant]
KR 1020210153696A · 2021 [cited by applicant]
WO WO2020023358A1 · 2020 [cited by applicant]
WO WO2010027795A1 · 2020 [cited by applicant]
Machine Translation. (Year: 2020). [cited by examiner]
International Search Report and Written Opinion of the International Searching Authority directed to related International Patent Application No. PCT/US2023/060556, mailed May 9, 2023; 8 pages. [cited by applicant]