Method of improving database integrity for driver assistance applications

• US 10,007,675 B2
• Filed: 07/31/2007
• Issued: 06/26/2018
• Est. Priority Date: 07/31/2007
• Status: Active Grant

• Current Assignee: Robert Bosch GmbH
• Original Assignee: Robert Bosch GmbH
• Inventors: Marti, Lukas Michael, Sangorrin, Jorge Sans
• Primary Examiner(s): Mofiz, Apu
• Assistant Examiner(s): HOLLAND, SHERYL L
• Application Number:
  US11/831,244
• Publication Number:
  US 20090037465A1
• Time in Patent Office: 3,983 Days
• Field of Search: 707104, 707607
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/29 Geographical information databases
• CPC Class Codes: G07C 5/08 Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
• CPC Class Codes: G08G 1/0104 Measuring and analyzing of parameters relative to traffic conditions

Abstract

A method of maintaining a database for a plurality of vehicles includes obtaining first sensor data from a vehicle sensor and comparing the first sensor data to data in the database. If the first sensor data does not match the database data, it is determined whether data from a single vehicle sensor or from a plurality of vehicle sensors is required to update the database. The database is updated if consistent data from a required number of vehicle sensors is available. A loss of database integrity is identified if data from a plurality of vehicle sensors is required to update the database but is not available. Anomalous driving is identified if data from a plurality of vehicle sensors is required to update the database and is available, and if the first sensor data is not confirmed by data from other vehicle sensors.

Claims

1. A method of maintaining a database for a plurality of vehicles, said method comprising:

receiving first sensor data from a first vehicle connected to the database, the first sensor data indicating one or more parameters pertaining to an environment surrounding the first vehicle;

comparing the first sensor data to stored data in the database to identify whether the first sensor data matches the stored data using a processor connected to the database,

when the first sensor data does not match the stored data, determining whether the first sensor data is sufficient to warrant an update of the database;

when the first sensor data does not match the stored data and the first sensor data is determined to be sufficient to warrant an update of database, updating the stored data in the database based on the first sensor data;

when the first sensor data does not match the stored data and the first sensor data is determined to not be sufficient to warrant an update of database, determining whether other sensor data from other vehicles is available to confirm the first sensor data;

when the other sensor data is not available to confirm the first sensor data, declaring a loss of database integrity of the database; and

when the other sensor data is available and the other sensor data confirms the first sensor data, updating the stored data in the database based on the first sensor data and the other sensor data.

2. The method of claim 1, further comprising:

when the other sensor data is available and the other sensor data does not confirm the first sensor data, identifying the first sensor data as corresponding to anomalous driving.

3. The method of claim 2, wherein, when anomalous driving is identified, the first sensor data is excluded from updates of the database.

4. The method of claim 1, wherein the processor is remote from the first vehicle, and the first sensor data is transmitted from the first vehicle to the processor.