METHOD OF IMPROVING DATABASE INTEGRITY FOR DRIVER ASSISTANCE APPLICATIONS

• US 20090037465A1
• Filed: 07/31/2007
• Published: 02/05/2009
• Est. Priority Date: 07/31/2007
• Status: Active Grant

• Current Assignee: Robert Bosch GmbH
• Original Assignee: Robert Bosch GmbH
• Inventors: Sangorrin, Jorge Sans, Marti, Lukas Michael
• Granted Patent: US 10,007,675 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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 the steps of:

obtaining first sensor data from a vehicle sensor;

comparing the first sensor data to data in the database; and

if the first sensor data does not match the database data;

determining whether data from a single vehicle sensor or from a plurality of vehicle sensors is required to update the database;

updating the database if consistent data from a required number of vehicle sensors is available;

identifying a loss of database integrity if data from a plurality of vehicle sensors is required to update the database but is not available; and

identifying anomalous driving if;

data from a plurality of vehicle sensors is required to update the database and is available; and

the first sensor data is not confirmed by data from other vehicle sensors.

2. The method of claim 1 wherein, if data from the required number of vehicle sensors is unavailable, the method comprises the further steps of:

obtaining data from the required number of vehicle sensors at a second point in time that is later than a first point in time at which data from the required number of vehicle sensors is unavailable; and

updating the database with the data obtained from the required number of vehicle sensors.

3. The method of claim 1 wherein, if anomalous driving is identified, the method comprises the further step of excluding the first sensor data from updates of the database.

4. The method of claim 1 wherein the database is disposed at a central location disposed remotely from the vehicles.

5. The method of claim 1 wherein the comparing step is performed by a processor disposed remotely from the vehicles.

6. The method of claim 1 wherein the obtaining step comprises transmitting a radio frequency signal from the vehicle while the vehicle is traveling.

7. The method of claim 1 wherein the obtaining step comprises transmitting a non-radio frequency signal from the vehicle while the vehicle is at a service station.

8. The method of claim 1 wherein the database is related to both time-variant parameters and time-invariant parameters of the vehicles'"'"' environment.

9. A method of maintaining a database for a plurality of vehicles, said method comprising the steps of:

obtaining first sensor data from a vehicle sensor;

comparing the first sensor data to data in the database; and

if the first sensor data does not match the database data;

determining whether data from a single vehicle sensor or from a plurality of vehicle sensors is required to update the database;

updating the database if data from a required number of vehicle sensors is available; and

identifying a loss of database integrity if data from the required number of vehicle sensors is unavailable.

10. The method of claim 9 wherein the database is updated if consistent data from a required number of vehicle sensors is available.

11. The method of claim 9 wherein, if data from the required number of vehicle sensors is unavailable, the method comprises the further steps of:

obtaining data from the required number of vehicle sensors at a second point in time that is later than a first point in time at which data from the required number of vehicle sensors is unavailable; and

updating the database with the data obtained from the required number of vehicle sensors.

12. The method of claim 9 wherein, if anomalous driving is identified, the method comprises the further step of excluding the first sensor data from updates of the database.

13. The method of claim 9 wherein the database is disposed at a central location disposed remotely from the vehicles.

14. The method of claim 9 wherein the comparing step is performed by a processor disposed remotely from the vehicles.

15. The method of claim 9 wherein the obtaining step comprises at least one of:

transmitting a radio frequency signal from the vehicle; and

transmitting a non-radio frequency signal from the vehicle while the vehicle is at a service station.

16. The method of claim 9 wherein the database is related to both time-variant parameters and time-invariant parameters of the vehicles'"'"' environment.

17. A method of maintaining a database for a plurality of vehicles, said method comprising the steps of:

obtaining first sensor data from a vehicle sensor;

comparing the first sensor data to data in the database; and

if the first sensor data does not match the database data, identifying anomalous driving if;

data from a plurality of vehicle sensors is required to update the database and is available; and

the first sensor data is not confirmed by data from other vehicle sensors.

18. The method of claim 17 wherein, if anomalous driving is identified, the method comprises the further step of excluding the first sensor data from updates of the database.

19. The method of claim 17 wherein if the first sensor data does not match the database data, the method comprises the further steps of:

determining whether data from a single vehicle sensor or from a plurality of vehicle sensors is required to update the database; and

updating the database if consistent data from a required number of vehicle sensors is available.

20. The method of claim 19 wherein, if data from the required number of vehicle sensors is unavailable, the method comprises the further steps of:

obtaining data from the required number of vehicle sensors at a second point in time that is later than a first point in time at which data from the required number of vehicle sensors is unavailable; and

updating the database with the data obtained from the required number of vehicle sensors.