US20210118249A1 - Autonomous vehicle salvage and repair - Google Patents
Autonomous vehicle salvage and repair Download PDFInfo
- Publication number
- US20210118249A1 US20210118249A1 US14/934,357 US201514934357A US2021118249A1 US 20210118249 A1 US20210118249 A1 US 20210118249A1 US 201514934357 A US201514934357 A US 201514934357A US 2021118249 A1 US2021118249 A1 US 2021118249A1
- Authority
- US
- United States
- Prior art keywords
- vehicle
- autonomous
- repairs
- damage
- semi
- 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.)
- Abandoned
Links
- 230000008439 repair process Effects 0.000 title claims abstract description 131
- 238000000034 method Methods 0.000 claims abstract description 145
- 230000006378 damage Effects 0.000 claims abstract description 96
- 230000015654 memory Effects 0.000 claims description 27
- 230000001771 impaired effect Effects 0.000 claims description 13
- 238000012544 monitoring process Methods 0.000 abstract description 34
- 238000004891 communication Methods 0.000 description 102
- 238000010586 diagram Methods 0.000 description 26
- 238000005516 engineering process Methods 0.000 description 22
- 230000009471 action Effects 0.000 description 21
- 238000012360 testing method Methods 0.000 description 19
- 230000007613 environmental effect Effects 0.000 description 16
- 238000011156 evaluation Methods 0.000 description 15
- 230000006735 deficit Effects 0.000 description 13
- 230000006870 function Effects 0.000 description 13
- 230000008569 process Effects 0.000 description 13
- 230000008859 change Effects 0.000 description 12
- 230000004044 response Effects 0.000 description 10
- 238000012502 risk assessment Methods 0.000 description 10
- 238000005067 remediation Methods 0.000 description 9
- 230000006399 behavior Effects 0.000 description 8
- 230000001276 controlling effect Effects 0.000 description 8
- 230000000875 corresponding effect Effects 0.000 description 8
- 238000013500 data storage Methods 0.000 description 7
- 238000012986 modification Methods 0.000 description 7
- 230000004048 modification Effects 0.000 description 7
- 230000008901 benefit Effects 0.000 description 6
- 230000000737 periodic effect Effects 0.000 description 6
- 238000010276 construction Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 238000012546 transfer Methods 0.000 description 5
- 238000004458 analytical method Methods 0.000 description 4
- 238000013473 artificial intelligence Methods 0.000 description 4
- 238000001514 detection method Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 230000001133 acceleration Effects 0.000 description 3
- 230000007257 malfunction Effects 0.000 description 3
- 238000003860 storage Methods 0.000 description 3
- 239000013589 supplement Substances 0.000 description 3
- 238000012795 verification Methods 0.000 description 3
- 206010039203 Road traffic accident Diseases 0.000 description 2
- 208000027418 Wounds and injury Diseases 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 2
- 230000003044 adaptive effect Effects 0.000 description 2
- 238000007792 addition Methods 0.000 description 2
- 230000036626 alertness Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 2
- 230000001186 cumulative effect Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 208000014674 injury Diseases 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000002265 prevention Effects 0.000 description 2
- 239000000047 product Substances 0.000 description 2
- 238000012552 review Methods 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 230000003190 augmentative effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000009833 condensation Methods 0.000 description 1
- 230000005494 condensation Effects 0.000 description 1
- 238000007796 conventional method Methods 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 230000000881 depressing effect Effects 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 230000007717 exclusion Effects 0.000 description 1
- 230000001815 facial effect Effects 0.000 description 1
- 210000003811 finger Anatomy 0.000 description 1
- 239000000446 fuel Substances 0.000 description 1
- 231100001261 hazardous Toxicity 0.000 description 1
- 238000010438 heat treatment Methods 0.000 description 1
- 238000003384 imaging method Methods 0.000 description 1
- 230000003116 impacting effect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 239000003550 marker Substances 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000003278 mimic effect Effects 0.000 description 1
- 238000012806 monitoring device Methods 0.000 description 1
- 230000036651 mood Effects 0.000 description 1
- 238000001556 precipitation Methods 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 230000004043 responsiveness Effects 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000001228 spectrum Methods 0.000 description 1
- 210000003813 thumb Anatomy 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
- 238000004804 winding Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/02—Detecting, measuring or recording pulse, heart rate, blood pressure or blood flow; Combined pulse/heart-rate/blood pressure determination; Evaluating a cardiovascular condition not otherwise provided for, e.g. using combinations of techniques provided for in this group with electrocardiography or electroauscultation; Heart catheters for measuring blood pressure
- A61B5/02028—Determining haemodynamic parameters not otherwise provided for, e.g. cardiac contractility or left ventricular ejection fraction
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/40—Detecting, measuring or recording for evaluating the nervous system
- A61B5/4058—Detecting, measuring or recording for evaluating the nervous system for evaluating the central nervous system
- A61B5/4064—Evaluating the brain
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/40—Detecting, measuring or recording for evaluating the nervous system
- A61B5/4076—Diagnosing or monitoring particular conditions of the nervous system
- A61B5/4094—Diagnosing or monitoring seizure diseases, e.g. epilepsy
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/68—Arrangements of detecting, measuring or recording means, e.g. sensors, in relation to patient
- A61B5/6887—Arrangements of detecting, measuring or recording means, e.g. sensors, in relation to patient mounted on external non-worn devices, e.g. non-medical devices
- A61B5/6893—Cars
-
- A—HUMAN NECESSITIES
- A61—MEDICAL OR VETERINARY SCIENCE; HYGIENE
- A61B—DIAGNOSIS; SURGERY; IDENTIFICATION
- A61B5/00—Measuring for diagnostic purposes; Identification of persons
- A61B5/72—Signal processing specially adapted for physiological signals or for diagnostic purposes
- A61B5/7271—Specific aspects of physiological measurement analysis
- A61B5/7282—Event detection, e.g. detecting unique waveforms indicative of a medical condition
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60K—ARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
- B60K35/00—Instruments specially adapted for vehicles; Arrangement of instruments in or on vehicles
-
- 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
- B60W10/00—Conjoint control of vehicle sub-units of different type or different function
- B60W10/04—Conjoint control of vehicle sub-units of different type or different function including control of propulsion units
-
- 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
- B60W30/00—Purposes of road vehicle drive control systems not related to the control of a particular sub-unit, e.g. of systems using conjoint control of vehicle sub-units
- B60W30/06—Automatic manoeuvring for parking
-
- 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
- B60W30/00—Purposes of road vehicle drive control systems not related to the control of a particular sub-unit, e.g. of systems using conjoint control of vehicle sub-units
- B60W30/08—Active safety systems predicting or avoiding probable or impending collision or attempting to minimise its consequences
- B60W30/09—Taking automatic action to avoid collision, e.g. braking and steering
-
- 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
- B60W30/00—Purposes of road vehicle drive control systems not related to the control of a particular sub-unit, e.g. of systems using conjoint control of vehicle sub-units
- B60W30/08—Active safety systems predicting or avoiding probable or impending collision or attempting to minimise its consequences
- B60W30/095—Predicting travel path or likelihood of collision
- B60W30/0956—Predicting travel path or likelihood of collision the prediction being responsive to traffic or environmental parameters
-
- 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
- B60W40/00—Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models
- B60W40/02—Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models related to ambient conditions
-
- 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
- B60W40/00—Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models
- B60W40/08—Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models related to drivers or passengers
-
- 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
- B60W40/00—Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models
- B60W40/08—Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models related to drivers or passengers
- B60W40/09—Driving style or behaviour
-
- 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
- B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
- B60W50/02—Ensuring safety in case of control system failures, e.g. by diagnosing, circumventing or fixing failures
-
- 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
- B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
- B60W50/02—Ensuring safety in case of control system failures, e.g. by diagnosing, circumventing or fixing failures
- B60W50/0205—Diagnosing or detecting failures; Failure detection models
-
- 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
- B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
- B60W50/04—Monitoring the functioning of the control system
- B60W50/045—Monitoring control system parameters
-
- 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
- B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
- B60W50/08—Interaction between the driver and the control system
- B60W50/082—Selecting or switching between different modes of propelling
-
- 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
- B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
- B60W50/08—Interaction between the driver and the control system
- B60W50/12—Limiting control by the driver depending on vehicle state, e.g. interlocking means for the control input for preventing unsafe operation
-
- 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
- B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
- B60W50/08—Interaction between the driver and the control system
- B60W50/14—Means for informing the driver, warning the driver or prompting a driver intervention
-
- 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/005—Handover processes
- B60W60/0053—Handover processes from vehicle to occupant
-
- 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/005—Handover processes
- B60W60/0059—Estimation of the risk associated with autonomous or manual driving, e.g. situation too complex, sensor failure or driver incapacity
-
- 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/007—Emergency override
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B62—LAND VEHICLES FOR TRAVELLING OTHERWISE THAN ON RAILS
- B62D—MOTOR VEHICLES; TRAILERS
- B62D15/00—Steering not otherwise provided for
- B62D15/02—Steering position indicators ; Steering position determination; Steering aids
- B62D15/027—Parking aids, e.g. instruction means
- B62D15/0285—Parking performed automatically
-
- 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/26—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
- G01C21/34—Route searching; Route guidance
- G01C21/3407—Route searching; Route guidance specially adapted for specific applications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
- G05D1/00—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots
- G05D1/0055—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots with safety arrangements
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
- G05D1/00—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots
- G05D1/0088—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots characterized by the autonomous decision making process, e.g. artificial intelligence, predefined behaviours
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
- G05D1/00—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots
- G05D1/02—Control of position or course in two dimensions
- G05D1/021—Control of position or course in two dimensions specially adapted to land vehicles
- G05D1/0212—Control of position or course in two dimensions specially adapted to land vehicles with means for defining a desired trajectory
- G05D1/0214—Control of position or course in two dimensions specially adapted to land vehicles with means for defining a desired trajectory in accordance with safety or protection criteria, e.g. avoiding hazardous areas
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
- G05D1/00—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots
- G05D1/02—Control of position or course in two dimensions
- G05D1/021—Control of position or course in two dimensions specially adapted to land vehicles
- G05D1/0276—Control of position or course in two dimensions specially adapted to land vehicles using signals provided by a source external to the vehicle
- G05D1/0278—Control of position or course in two dimensions specially adapted to land vehicles using signals provided by a source external to the vehicle using satellite positioning signals, e.g. GPS
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
- G05D1/00—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots
- G05D1/20—Control system inputs
- G05D1/24—Arrangements for determining position or orientation
- G05D1/247—Arrangements for determining position or orientation using signals provided by artificial sources external to the vehicle, e.g. navigation beacons
- G05D1/248—Arrangements for determining position or orientation using signals provided by artificial sources external to the vehicle, e.g. navigation beacons generated by satellites, e.g. GPS
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05D—SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
- G05D1/00—Control of position, course, altitude or attitude of land, water, air or space vehicles, e.g. using automatic pilots
- G05D1/60—Intended control result
- G05D1/617—Safety or protection, e.g. defining protection zones around obstacles or avoiding hazards
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0201—Market modelling; Market analysis; Collecting market data
- G06Q30/0206—Price or cost determination based on market factors
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
- G06Q30/0217—Discounts or incentives, e.g. coupons or rebates involving input on products or services in exchange for incentives or rewards
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/08—Insurance
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/02—Registering or indicating driving, working, idle, or waiting time only
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
- G07C5/0808—Diagnosing performance data
-
- G—PHYSICS
- G08—SIGNALLING
- G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
- G08B25/00—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems
- G08B25/01—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems characterised by the transmission medium
- G08B25/10—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems characterised by the transmission medium using wireless transmission systems
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/09—Arrangements for giving variable traffic instructions
- G08G1/091—Traffic information broadcasting
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/09—Arrangements for giving variable traffic instructions
- G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/14—Traffic control systems for road vehicles indicating individual free spaces in parking areas
-
- 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
- B60W40/00—Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models
- B60W40/08—Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models related to drivers or passengers
- B60W2040/0809—Driver authorisation; Driver identity check
-
- 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
- B60W40/00—Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models
- B60W40/08—Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models related to drivers or passengers
- B60W2040/0818—Inactivity or incapacity of driver
-
- 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
- B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
- B60W2050/0062—Adapting control system settings
- B60W2050/007—Switching between manual and automatic parameter input, and vice versa
- B60W2050/0071—Controller overrides driver automatically
-
- 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
- B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
- B60W2050/0062—Adapting control system settings
- B60W2050/007—Switching between manual and automatic parameter input, and vice versa
- B60W2050/0073—Driver overrides controller
-
- 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
- B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
- B60W2050/0062—Adapting control system settings
- B60W2050/0075—Automatic parameter input, automatic initialising or calibrating means
-
- 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
- B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
- B60W50/02—Ensuring safety in case of control system failures, e.g. by diagnosing, circumventing or fixing failures
- B60W50/0205—Diagnosing or detecting failures; Failure detection models
- B60W2050/0215—Sensor drifts or sensor failures
-
- 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
- B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
- B60W50/04—Monitoring the functioning of the control system
- B60W50/045—Monitoring control system parameters
- B60W2050/046—Monitoring control system parameters involving external transmission of data to or from the vehicle, e.g. via telemetry, satellite, Global Positioning System [GPS]
-
- 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
- B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
- B60W50/08—Interaction between the driver and the control system
- B60W50/14—Means for informing the driver, warning the driver or prompting a driver intervention
- B60W2050/143—Alarm means
-
- 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
- B60W2420/00—Indexing codes relating to the type of sensors based on the principle of their operation
- B60W2420/40—Photo, light or radio wave sensitive means, e.g. infrared sensors
- B60W2420/403—Image sensing, e.g. optical camera
-
- 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
- B60W2540/00—Input parameters relating to occupants
- B60W2540/043—Identity of occupants
-
- 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
- B60W2540/00—Input parameters relating to occupants
- B60W2540/22—Psychological state; Stress level or workload
-
- 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
- B60W2540/00—Input parameters relating to occupants
- B60W2540/221—Physiology, e.g. weight, heartbeat, health or special needs
-
- 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
- B60W2540/00—Input parameters relating to occupants
- B60W2540/26—Incapacity
-
- 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/45—External transmission of data to or from the vehicle
-
- 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
- B60W2756/00—Output or target parameters relating to data
- B60W2756/10—Involving external transmission of data to or from the vehicle
-
- 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
- B60W2900/00—Indexing codes relating to the purpose of, or problem solved of road vehicle drive control systems not otherwise provided for in groups B60W30/00
Definitions
- the present disclosure generally relates to systems and methods for operating, monitoring, assessing, or insuring autonomous or semi-autonomous vehicles.
- Vehicles are typically operated by a human vehicle operator who controls both steering and motive controls. Operator error, inattention, inexperience, misuse, or distraction leads to many vehicle accidents each year, resulting in injury and damage. Autonomous or semi-autonomous vehicles augment vehicle operators' information or replace vehicle operators' control commands to operate the vehicle in whole or part with computer systems based upon information from sensors within the vehicle.
- Vehicle or automobile insurance exists to provide financial protection against physical damage and/or bodily injury resulting from traffic accidents and against liability that could arise therefrom.
- a customer purchases a vehicle insurance policy for a policy rate having a specified term.
- the insurer pays for damages to the insured which are caused by covered perils, acts, or events as specified by the language of the insurance policy.
- the payments from the insured are generally referred to as “premiums,” and typically are paid on behalf of the insured over time at periodic intervals.
- An insurance policy may remain “in-force” while premium payments are made during the term or length of coverage of the policy as indicated in the policy.
- An insurance policy may “lapse” (or have a status or state of “lapsed”), for example, when premium payments are not being paid or if the insured or the insurer cancels the policy.
- Premiums may be typically determined based upon a selected level of insurance coverage, location of vehicle operation, vehicle model, and characteristics or demographics of the vehicle operator.
- the characteristics of a vehicle operator that affect premiums may include age, years operating vehicles of the same class, prior incidents involving vehicle operation, and losses reported by the vehicle operator to the insurer or a previous insurer.
- Past and current premium determination methods do not, however, account for use of autonomous vehicle operating features.
- the present embodiments may, inter alia, alleviate this and/or other drawbacks associated with conventional techniques.
- the present embodiments may be related to autonomous or semi-autonomous vehicle functionality, including driverless operation, accident avoidance, or collision warning systems. These autonomous vehicle operation features may either assist the vehicle operator to more safely or efficiently operate a vehicle or may take full control of vehicle operation under some or all circumstances.
- the present embodiments may also facilitate risk assessment and premium determination for vehicle insurance policies covering vehicles with autonomous operation features. For instance, a consumer may opt-in to a rewards program that rewards them, such as in the form of insurance discounts, for affirmatively sharing data related to their vehicles and/or autonomous features with an insurance provider.
- a computer such as an on-board computer, mobile device, or server communicatively connected to the vehicle
- a computer associated with the vehicle may (1) receive an indication of damage to the autonomous or semi-autonomous vehicle; (2) receive operating data regarding operation of the vehicle during (i) a time period without the damage to the autonomous or semi-autonomous vehicle and (ii) a time period with the damage to the autonomous or semi-autonomous vehicle; (3) determine one or more repairs associated with the damage based upon the operating data; and/or (4) determine an expected cost associated with the one or more repairs.
- the operating data may include information from one or more sensors disposed within the autonomous or semi-autonomous vehicle and/or information regarding the operation of one or more autonomous operation features of the autonomous or semi-autonomous vehicle.
- the one or more repairs associated with the damage may be determined at least in part based upon a specialty repair service, in which case the expected cost may further include a cost associated with the specialty repair service.
- the expected cost may be determined based upon information regarding actual costs of repairs to a plurality of other vehicles. Additionally, or alternatively, determining the expected cost may include determining a range of expected costs associated with the one or more repairs. The computer may further determine a plurality of expected costs within the determined range and cause the plurality of expected costs to be presented to an insurance customer associated with the vehicle. A maximum payment for the one or more repairs associated with the damage may also be determined based upon the determined range of expected costs and/or presented to an insurance customer associated with the vehicle.
- the computer may cause the expected cost associated with the one or more repairs to be presented to an insurance customer associated with the vehicle, along with a plurality of options regarding the one or more repairs.
- the computer may receive a selection by the insurance customer of one or more of the presented plurality of options. Based upon the selection, the computer may cause a payment to be made to one or more of the following: the insurance customer, a beneficiary of an insurance policy associated with the insurance customer, and/or a repair facility.
- the plurality of options may include one or more options to have the one or more repairs performed at one or more repair facilities.
- the one or more options may further include one or more cost estimates based upon the operating data.
- the one or more options to have the one or more repairs performed at one or more repair facilities may include one or more estimates of time required for the one or more repairs.
- the methods may be provided in corresponding computer systems including at least one or more processors and a non-transitory program memory coupled to the one or more processors and storing executable instructions.
- the computer systems may further include or be communicatively connected to one or more sensors, communication components or devices, or other equipment as described herein.
- a tangible, non-transitory computer-readable medium storing instructions corresponding to each of the embodiments or aspects described above may be provided.
- Each of the methods or executable instructions of the computer systems or computer-readable media may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
- FIG. 1 illustrates a block diagram of an exemplary computer network, a computer server, a mobile device, and an on-board computer for implementing autonomous vehicle operation, monitoring, evaluation, and insurance processes in accordance with the described embodiments;
- FIG. 2 illustrates a block diagram of an exemplary on-board computer or mobile device
- FIG. 3 illustrates a flow diagram of an exemplary autonomous vehicle operation method in accordance with the presently described embodiments
- FIG. 4 illustrates a flow diagram of an exemplary monitoring method during vehicle operation in accordance with the presently described embodiments
- FIG. 5 illustrates a flow diagram of an exemplary operating status assessment method in accordance with the presently described embodiments
- FIG. 6 illustrates a flow diagram of an exemplary operating status monitoring method in accordance with the presently described embodiments
- FIGS. 7A-B illustrate flow diagrams depicting exemplary vehicle operation hand-off methods in accordance with the presently described embodiments
- FIG. 8 illustrates a flow diagram depicting an exemplary vehicle operator identification method in accordance with the presently described embodiments
- FIG. 9 illustrates a flow diagram depicting an exemplary vehicle operator use monitoring and evaluation method in accordance with the presently described embodiments.
- FIG. 10 illustrates a flow diagram depicting an exemplary cost comparison method in accordance with the presently described embodiments.
- FIG. 11 illustrates a flow diagram depicting an exemplary autonomous operation feature update method in accordance with the presently described embodiments
- FIG. 12 illustrates a flow diagram depicting an exemplary autonomous vehicle repair method in accordance with the presently described embodiments.
- FIG. 13 illustrates a flow diagram depicting an exemplary infrastructure communication method in accordance with the presently described embodiments.
- the systems and methods disclosed herein generally relate to evaluating, monitoring, and managing risks related to the operation of autonomous or semi-autonomous vehicles having autonomous (or semi-autonomous) operation features.
- the systems and methods further relate to pricing and processing vehicle insurance policies for autonomous or semi-autonomous vehicles.
- the autonomous operation features may take full control of the vehicle under certain conditions, viz. fully autonomous operation, or the autonomous operation features may assist the vehicle operator in operating the vehicle, viz. partially autonomous operation.
- Fully autonomous operation features may include systems within the vehicle that pilot the vehicle to a destination with or without a vehicle operator present (e.g., an operating system for a driverless car).
- Partially autonomous operation features may assist the vehicle operator in limited ways (e.g., automatic braking or collision avoidance systems).
- the type and quality of the autonomous operation features may affect the risks related to operating a vehicle, both individually and/or in combination.
- configurations and settings of the autonomous operation features may further impact the risks.
- some embodiments evaluate the quality of each autonomous operation feature and/or combination of features.
- Additional embodiments evaluate the risks associated with the vehicle operator interacting with the autonomous operation features.
- Further embodiments address the relative risks associated with control of some aspects of vehicle control by the autonomous operation features or by the vehicle operator.
- Still further embodiments address use of information received or generated by the autonomous operation features to manage risk and/or damage.
- Some autonomous operation features may be adapted for use under particular conditions, such as city driving or highway driving. Additionally, the vehicle operator may be able to configure settings relating to the features or may enable or disable the features individually or in groups. For example, the vehicle operator may select a mode of operation for the autonomous or semi-autonomous vehicle, which may adjust settings for one or more autonomous operation features. Therefore, some embodiments monitor use of the autonomous operation features, which may include the settings or levels of feature use during vehicle operation, as well as the selection of features or settings of the autonomous operation features chosen by the vehicle operator.
- Information obtained by monitoring feature usage may be used to determine risk levels associated with vehicle operation, either generally or in relation to a vehicle operator.
- total risk may be determined by a weighted combination of the risk levels associated with operation while autonomous operation features are enabled (with relevant settings) and the risk levels associated with operation while autonomous operation features are disabled.
- settings or configurations relating to vehicle operation may be monitored and used in determining vehicle operating risk.
- risk category or price may be determined based upon factors relating to the evaluated effectiveness of the autonomous vehicle features.
- the risk or price determination may also include traditional factors, such as location, vehicle type, and level of vehicle use. For fully autonomous vehicles, factors relating to vehicle operators may be excluded entirely. For partially autonomous vehicles, factors relating to vehicle operators may be reduced in proportion to the evaluated effectiveness and monitored usage levels of the autonomous operation features.
- the risk level and/or price determination may also include an assessment of the availability of external sources of information. Location and/or timing of vehicle use may thus be monitored and/or weighted to determine the risk associated with operation of the vehicle.
- the present embodiments may relate to assessing and pricing insurance based upon autonomous (or semi-autonomous) functionality of a vehicle, utilization of the autonomous (or semi-autonomous) functionality of the vehicle, and/or operation of the vehicle by a human operator.
- the vehicle operator may not control the operations of the vehicle directly, in which case the assessment, rating, and pricing of insurance may exclude consideration of the vehicle operator.
- a smart vehicle may maneuver itself without human intervention and/or include sensors, processors, computer instructions, and/or other components that may perform or direct certain actions conventionally performed by a human operator.
- An analysis of how artificial intelligence facilitates avoiding accidents and/or mitigates the severity of accidents may be used to build a database and/or model of risk assessment. After which, automobile insurance risk and/or premiums (as well as insurance discounts, rewards, and/or points) may be adjusted based upon autonomous or semi-autonomous vehicle functionality, such as by groups of autonomous or semi-autonomous functionality or individual features. In one aspect, an evaluation may be performed on how artificial intelligence, and the usage thereof, impacts automobile accidents and/or automobile insurance claims.
- the types of autonomous or semi-autonomous vehicle-related functionality or technology that may be used with the present embodiments to replace human driver actions may include and/or be related to the following types of functionality: (a) fully autonomous (driverless); (b) limited driver control; (c) vehicle-to-vehicle (V2V) wireless communication; (d) vehicle-to-infrastructure (and/or vice versa) wireless communication; (e) automatic or semi-automatic steering; (f) automatic or semi-automatic acceleration; (g) automatic or semi-automatic braking; (h) automatic or semi-automatic blind spot monitoring; (i) automatic or semi-automatic collision warning; (j) adaptive cruise control; (k) automatic or semi-automatic parking/parking assistance; (l) automatic or semi-automatic collision preparation (windows roll up, seat adjusts upright, brakes pre-charge, etc.); (m) driver acuity/alertness monitoring; (n) pedestrian detection; (o) autonomous or semi-autonomous backup systems; (p) road
- the autonomous or semi-autonomous functionality or technology may include and/or may be related to: (t) driver alertness or responsive monitoring; (u) pedestrian detection; (v) artificial intelligence and/or back-up systems; (w) navigation or GPS-related systems; (x) security and/or anti-hacking measures; and/or (y) theft prevention systems.
- the adjustments to automobile insurance rates or premiums based upon the autonomous or semi-autonomous vehicle-related functionality or technology may take into account the impact of such functionality or technology on the likelihood of a vehicle accident or collision occurring.
- a processor may analyze historical accident information and/or test data involving vehicles having autonomous or semi-autonomous functionality. Factors that may be analyzed and/or accounted for that are related to insurance risk, accident information, or test data may include (1) point of impact; (2) type of road; (3) time of day; (4) weather conditions; (5) road construction; (6) type/length of trip; (7) vehicle style; (8) level of pedestrian traffic; (9) level of vehicle congestion; (10) atypical situations (such as manual traffic signaling); (11) availability of internet connection for the vehicle; and/or other factors. These types of factors may also be weighted according to historical accident information, predicted accidents, vehicle trends, test data, and/or other considerations.
- the benefit of one or more autonomous or semi-autonomous functionalities or capabilities may be determined, weighted, and/or otherwise characterized.
- the benefit of certain autonomous or semi-autonomous functionality may be substantially greater in city or congested traffic, as compared to open road or country driving traffic.
- certain autonomous or semi-autonomous functionality may only work effectively below a certain speed, e.g., during city driving or driving in congestion.
- Other autonomous or semi-autonomous functionality may operate more effectively on the highway and away from city traffic, such as cruise control.
- Further individual autonomous or semi-autonomous functionality may be impacted by weather, such as rain or snow, and/or time of day (day light versus night).
- fully automatic or semi-automatic lane detection warnings may be impacted by rain, snow, ice, and/or the amount of sunlight (all of which may impact the imaging or visibility of lane markings painted onto a road surface, and/or road markers or street signs).
- Automobile insurance premiums, rates, discounts, rewards, refunds, points, or other costs may be adjusted based upon the percentage of time or vehicle usage that the vehicle is the driver, i.e., the amount of time a specific driver uses each type of autonomous (or even semi-autonomous) vehicle functionality. Such premiums, rates, discounts, rewards, refunds, points, or other costs may further be adjusted based upon the extent of use of the autonomous operation features, including settings or modes impacting the operation of the autonomous operation features. Moreover, information regarding the vehicle environment during use (e.g., weather, traffic, time of day, etc.) may be included in insurance adjustment determinations, as may traditional information regarding one or more vehicle operators (and the extent to which each vehicle operator uses the vehicle).
- Such usage information for a particular vehicle may be gathered over time and/or via remote wireless communication with the vehicle.
- One embodiment may involve a processor on the vehicle, such as within a vehicle control system or dashboard, monitoring in real-time the vehicle operator and/or the use of autonomous operation features while the vehicle is operating.
- Other types of monitoring may be remotely performed, such as via wireless communication between the vehicle and a remote server, or wireless communication between a vehicle-mounted dedicated device (that is configured to gather autonomous or semi-autonomous functionality usage information) and a remote server.
- the vehicle may transmit and/or receive communications to or from external sources, such as other vehicles (V2V), infrastructure (e.g., a bridge, traffic light, railroad crossing, toll both, marker, sign, or other equipment along the side of a road or highway), pedestrians, databases, or other information sources external to the vehicle.
- V2V vehicles
- infrastructure e.g., a bridge, traffic light, railroad crossing, toll both, marker, sign, or other equipment along the side of a road or highway
- pedestrians databases, or other information sources external to the vehicle.
- V2V communication may allow a vehicle to identify other vehicles approaching an intersection even when the direct line between the vehicle and the other vehicles is obscured by buildings.
- the V2V wireless communication from a first vehicle to a second vehicle may indicate that the first vehicle is braking, which may include the degree to which the vehicle is braking.
- the second vehicle may automatically or autonomously brake in advance of detecting the deceleration of the first vehicle based upon sensor data.
- Insurance premiums, rates, ratings, discounts, rewards, special offers, points, programs, refunds, claims, claim amounts, or other costs associated with an insurance policy may be adjusted for, or may otherwise take into account, the foregoing functionality and/or the other functionality described herein.
- insurance policies may be updated based upon installed autonomous operation features, the extent of use of the autonomous operation features, V2V wireless communication, and/or vehicle-to-infrastructure or infrastructure-to-vehicle wireless communication.
- the present embodiments may assess and price insurance risks at least in part based upon autonomous operation features that replace some actions of the vehicle operator in controlling the vehicle, including settings and operating status of the autonomous operation features.
- FIG. 1 illustrates a block diagram of an exemplary autonomous vehicle insurance system 100 on which the exemplary methods described herein may be implemented.
- the high-level architecture includes both hardware and software applications, as well as various data communications channels for communicating data between the various hardware and software components.
- the autonomous vehicle insurance system 100 may be roughly divided into front-end components 102 and back-end components 104 .
- the front-end components 102 may obtain information regarding a vehicle 108 (e.g., a car, truck, motorcycle, etc.) and the surrounding environment.
- An on-board computer 114 may utilize this information to operate the vehicle 108 according to an autonomous operation feature or to assist the vehicle operator in operating the vehicle 108 .
- the front-end components 102 may include one or more sensors 120 installed within the vehicle 108 that may communicate with the on-board computer 114 .
- the front-end components 102 may further process the sensor data using the on-board computer 114 or a mobile device 110 (e.g., a smart phone, a tablet computer, a special purpose computing device, etc.) to determine when the vehicle is in operation and information regarding the vehicle.
- the front-end components 102 may communicate with the back-end components 104 via a network 130 .
- Either the on-board computer 114 or the mobile device 110 may communicate with the back-end components 104 via the network 130 to allow the back-end components 104 to record information regarding vehicle usage.
- the back-end components 104 may use one or more servers 140 to receive data from the front-end components 102 , determine use and effectiveness of autonomous operation features, determine risk levels or premium price, and/or facilitate purchase or renewal of an autonomous vehicle insurance policy.
- the front-end components 102 may be disposed within or communicatively connected to one or more on-board computers 114 , which may be permanently or removably installed in the vehicle 108 .
- the on-board computer 114 may interface with the one or more sensors 120 within the vehicle 108 (e.g., an ignition sensor, an odometer, a system clock, a speedometer, a tachometer, an accelerometer, a gyroscope, a compass, a geolocation unit, a camera, a distance sensor, etc.), which sensors may also be incorporated within or connected to the on-board computer 114 .
- the front-end components 102 may further include a communication component 122 to transmit information to and receive information from external sources, including other vehicles, infrastructure, or the back-end components 104 .
- the mobile device 110 may supplement the functions performed by the on-board computer 114 described herein by, for example, sending or receiving information to and from the mobile server 140 via the network 130 .
- the on-board computer 114 may perform all of the functions of the mobile device 110 described herein, in which case no mobile device 110 may be present in the system 100 . Either or both of the mobile device 110 or on-board computer 114 may communicate with the network 130 over links 112 and 118 , respectively. Additionally, the mobile device 110 and on-board computer 114 may communicate with one another directly over link 116 .
- the mobile device 110 may be either a general-use personal computer, cellular phone, smart phone, tablet computer, phablet, wearable electronics, PDA (personal digital assistant), smart glasses, smart watches, smart bracelet, pager, computing device configured for wired or wireless RF (radio frequency) communication, a dedicated vehicle use monitoring device, and/or other mobile computing device. Although only one mobile device 110 is illustrated, it should be understood that a plurality of mobile devices 110 may be used in some embodiments.
- the on-board computer 114 may be a general-use on-board computer capable of performing many functions relating to vehicle operation or a dedicated computer for autonomous vehicle operation. Further, the on-board computer 114 may be installed by the manufacturer of the vehicle 108 or as an aftermarket modification or addition to the vehicle 108 . In some embodiments or under certain conditions, the mobile device 110 or on-board computer 114 may function as thin-client devices that outsource some or most of the processing to the server 140 .
- the sensors 120 may be removably or fixedly installed within the vehicle 108 and may be disposed in various arrangements to provide information to the autonomous operation features.
- the sensors 120 may be included one or more of a GPS (Global Positioning System) unit, other satellite-based navigation unit, a radar unit, a LIDAR (Light Detection and Ranging) unit, an ultrasonic sensor, an infrared sensor, a camera, an accelerometer, a tachometer, and/or a speedometer.
- Some of the sensors 120 e.g., radar, LIDAR, or camera units
- Other sensors 120 may provide data for determining the location or movement of the vehicle 108 .
- Other sensors 120 may be directed to the interior or passenger compartment of the vehicle 108 , such as cameras, microphones, pressure sensors, thermometers, or similar sensors to monitor the vehicle operator and/or passengers within the vehicle 108 .
- Information generated or received by the sensors 120 may be communicated to the on-board computer 114 or the mobile device 110 for use in autonomous vehicle operation.
- the communication component 122 may receive information from external sources, such as other vehicles or infrastructure.
- the communication component 122 may also send information regarding the vehicle 108 to external sources.
- the communication component 122 may include a transmitter and a receiver designed to operate according to predetermined specifications, such as the dedicated short-range communication (DSRC) channel, wireless telephony, Wi-Fi, or other existing or later-developed communications protocols.
- DSRC dedicated short-range communication
- the received information may supplement the data received from the sensors 120 to implement the autonomous operation features.
- the communication component 122 may receive information that an autonomous vehicle ahead of the vehicle 108 is reducing speed, allowing the adjustments in the autonomous operation of the vehicle 108 .
- the front-end components may include an infrastructure communication device 124 for monitoring the status of one or more infrastructure components 126 .
- the infrastructure communication device 124 may include or be communicatively connected to one or more sensors (not shown) for detecting information relating to the condition of the infrastructure component 126 .
- the sensors (not shown) may generate data relating to weather conditions, traffic conditions, or operating status of the infrastructure component 126 .
- the infrastructure communication device 124 may be configured to receive the sensor data generated and determine a condition of the infrastructure component 126 , such as weather conditions, road integrity, construction, traffic, available parking spaces, etc.
- the infrastructure communication device 124 may further be configured to communicate information to vehicles 108 via the communication component 122 . In some embodiments, the infrastructure communication device 124 may receive information from the vehicles 108 , while, in other embodiments, the infrastructure communication device 124 may only transmit information to the vehicles 108 .
- the on-board computer 114 may directly or indirectly control the operation of the vehicle 108 according to various autonomous operation features.
- the autonomous operation features may include software applications or routines implemented by the on-board computer 114 to control the steering, braking, or throttle of the vehicle 108 .
- the on-board computer 114 may be communicatively connected to the controls or components of the vehicle 108 by various electrical or electromechanical control components (not shown).
- the vehicle 108 may be operable only through such control components (not shown).
- the control components may be disposed within or supplement other vehicle operator control components (not shown), such as steering wheels, accelerator or brake pedals, or ignition switches.
- the front-end components 102 may communicate with the back-end components 104 via the network 130 .
- the network 130 may be a proprietary network, a secure public internet, a virtual private network or some other type of network, such as dedicated access lines, plain ordinary telephone lines, satellite links, cellular data networks, combinations of these. Where the network 130 comprises the Internet, data communications may take place over the network 130 via an Internet communication protocol.
- the back-end components 104 may include one or more servers 140 .
- Each server 140 may include one or more computer processors adapted and configured to execute various software applications and components of the autonomous vehicle insurance system 100 , in addition to other software applications.
- the server 140 may further include a database 146 , which may be adapted to store data related to the operation of the vehicle 108 and its autonomous operation features.
- Such data might include, for example, dates and times of vehicle use, duration of vehicle use, use and settings of autonomous operation features, speed of the vehicle 108 , RPM or other tachometer readings of the vehicle 108 , lateral and longitudinal acceleration of the vehicle 108 , incidents or near collisions of the vehicle 108 , communication between the autonomous operation features and external sources, environmental conditions of vehicle operation (e.g., weather, traffic, road condition, etc.), errors or failures of autonomous operation features, or other data relating to use of the vehicle 108 and the autonomous operation features, which may be uploaded to the server 140 via the network 130 .
- the server 140 may access data stored in the database 146 when executing various functions and tasks associated with the evaluating feature effectiveness or assessing risk relating to an autonomous vehicle.
- the autonomous vehicle insurance system 100 is shown to include one vehicle 108 , one mobile device 110 , one on-board computer 114 , and one server 140 , it should be understood that different numbers of vehicles 108 , mobile devices 110 , on-board computers 114 , and/or servers 140 may be utilized.
- the system 100 may include a plurality of servers 140 and hundreds of mobile devices 110 or on-board computers 114 , all of which may be interconnected via the network 130 .
- the database storage or processing performed by the one or more servers 140 may be distributed among a plurality of servers 140 in an arrangement known as “cloud computing.” This configuration may provide various advantages, such as enabling near real-time uploads and downloads of information as well as periodic uploads and downloads of information. This may in turn support a thin-client embodiment of the mobile device 110 or on-board computer 114 discussed herein.
- the server 140 may have a controller 155 that is operatively connected to the database 146 via a link 156 .
- additional databases may be linked to the controller 155 in a known manner.
- additional databases may be used for autonomous operation feature information, vehicle insurance policy information, and vehicle use information.
- the controller 155 may include a program memory 160 , a processor 162 (which may be called a microcontroller or a microprocessor), a random-access memory (RAM) 164 , and an input/output (I/O) circuit 166 , all of which may be interconnected via an address/data bus 165 . It should be appreciated that although only one microprocessor 162 is shown, the controller 155 may include multiple microprocessors 162 .
- the memory of the controller 155 may include multiple RAMs 164 and multiple program memories 160 .
- the I/O circuit 166 is shown as a single block, it should be appreciated that the I/O circuit 166 may include a number of different types of I/O circuits.
- the RAM 164 and program memories 160 may be implemented as semiconductor memories, magnetically readable memories, or optically readable memories, for example.
- the controller 155 may also be operatively connected to the network 130 via a link 135 .
- the server 140 may further include a number of software applications stored in a program memory 160 .
- the various software applications on the server 140 may include an autonomous operation information monitoring application 141 for receiving information regarding the vehicle 108 and its autonomous operation features, a feature evaluation application 142 for determining the effectiveness of autonomous operation features under various conditions, a compatibility evaluation application 143 for determining the effectiveness of combinations of autonomous operation features, a risk assessment application 144 for determining a risk category associated with an insurance policy covering an autonomous vehicle, and an autonomous vehicle insurance policy purchase application 145 for offering and facilitating purchase or renewal of an insurance policy covering an autonomous vehicle.
- the various software applications may be executed on the same computer processor or on different computer processors.
- the various software applications may include various software routines stored in the program memory 160 to implement various modules using the process 162 . Additionally, or alternatively, the software applications or routines may interact with various hardware modules that may be installed within or connected to the server 140 . Such modules may implement part of all of the various exemplary methods discussed herein or other related embodiments.
- Such modules may include a vehicle control module for determining and implementing control decisions to operate the vehicle 108 , a system status module for determining the operating status of autonomous operation features, a monitoring module for monitoring the operation of the vehicle 108 , a remediation module for correcting abnormal operating states of autonomous operation features, an insurance module for determining risks and costs associated with operation of the vehicle 108 , an alert module for generating and presenting alerts regarding the vehicle 108 or the vehicle operator, a risk assessment module for determining risks associated with operation of the vehicle 108 by the autonomous operation features or by the vehicle operator, an identification module for identifying or verifying the identity of the vehicle operator, an information module for obtaining information regarding a vehicle operator or vehicle 108 , a use cost module for determining costs associated with operation of the vehicle 108 , a comparison module for comparing one or more costs associated with owning or operating the vehicle 108 , an update module for updating an autonomous operation feature of the vehicle 108 , or other modules.
- a vehicle control module for determining and implementing control decisions to operate the
- FIG. 2 illustrates a block diagram of an exemplary mobile device 110 and/or an exemplary on-board computer 114 consistent with the system 100 .
- the mobile device 110 and/or on-board computer 114 may include a display 202 , a GPS unit 206 , a communication unit 220 , an accelerometer 224 , one or more additional sensors (not shown), a user-input device (not shown), and/or, like the server 140 , a controller 204 .
- the mobile device 110 and on-board computer 114 may be integrated into a single device, or either may perform the functions of both.
- the on-board computer 114 (or mobile device 110 ) may interface with the sensors 120 to receive information regarding the vehicle 108 and its environment, which information may be used by the autonomous operation features to operate the vehicle 108 .
- the controller 204 may include a program memory 208 , one or more microcontrollers or microprocessors (MP) 210 , a RAM 212 , and an I/O circuit 216 , all of which are interconnected via an address/data bus 214 .
- the program memory 208 may include an operating system 226 , a data storage 228 , a plurality of software applications 230 , and/or a plurality of software routines 240 .
- the operating system 226 may include one of a plurality of general purpose or mobile platforms, such as the AndroidTM, iOS®, or Windows® systems, developed by Google Inc., Apple Inc., and Microsoft Corporation, respectively.
- the operating system 226 may be a custom operating system designed for autonomous vehicle operation using the on-board computer 114 .
- the data storage 228 may include data such as user profiles and preferences, application data for the plurality of applications 230 , routine data for the plurality of routines 240 , and other data related to the autonomous operation features.
- the controller 204 may also include, or otherwise be communicatively connected to, other data storage mechanisms (e.g., one or more hard disk drives, optical storage drives, solid state storage devices, etc.) that reside within the vehicle 108 .
- FIG. 2 depicts only one microprocessor 210
- the controller 204 may include multiple microprocessors 210 .
- the memory of the controller 204 may include multiple RAMs 212 and multiple program memories 208 .
- FIG. 2 depicts the I/O circuit 216 as a single block, the I/O circuit 216 may include a number of different types of I/O circuits.
- the controller 204 may implement the RAMs 212 and the program memories 208 as semiconductor memories, magnetically readable memories, or optically readable memories, for example.
- the one or more processors 210 may be adapted and configured to execute any of one or more of the plurality of software applications 230 or any one or more of the plurality of software routines 240 residing in the program memory 204 , in addition to other software applications.
- One of the plurality of applications 230 may be an autonomous vehicle operation application 232 that may be implemented as a series of machine-readable instructions for performing the various tasks associated with implementing one or more of the autonomous operation features according to the autonomous vehicle operation method 300 .
- Another of the plurality of applications 230 may be an autonomous communication application 234 that may be implemented as a series of machine-readable instructions for transmitting and receiving autonomous operation information to or from external sources via the communication unit 220 .
- Still another application of the plurality of applications 230 may include an autonomous operation monitoring application 236 that may be implemented as a series of machine-readable instructions for sending information regarding autonomous operation of the vehicle to the server 140 via the network 130 .
- the plurality of software applications 230 may call various of the plurality of software routines 240 to perform functions relating to autonomous vehicle operation, monitoring, or communication. In some embodiments, the plurality of software routines may further assess risk levels or determine insurance policy costs and adjustments.
- One of the plurality of software routines 240 may be a configuration routine 242 to receive settings from the vehicle operator to configure the operating parameters of an autonomous operation feature.
- Another of the plurality of software routines 240 may be a sensor control routine 244 to transmit instructions to a sensor 120 and receive data from the sensor 120 .
- Still another of the plurality of software routines 240 may be an autonomous control routine 246 that performs a type of autonomous control, such as collision avoidance, lane centering, and/or speed control.
- the autonomous vehicle operation application 232 may cause a plurality of autonomous control routines 246 to determine control actions required for autonomous vehicle operation.
- one of the plurality of software routines 240 may be a monitoring and reporting routine 248 that monitors and transmits information regarding autonomous vehicle operation to the server 140 via the network 130 .
- Yet another of the plurality of software routines 240 may be an autonomous communication routine 250 for receiving and transmitting information between the vehicle 108 and external sources to improve the effectiveness of the autonomous operation features.
- any of the plurality of software routines 240 may be designed to operate independently of the software applications 230 or in conjunction with the software applications 230 to implement modules associated with the methods discussed herein using the microprocessor 210 of the controller 204 . Additionally, or alternatively, the software applications 230 or software routines 240 may interact with various hardware modules that may be installed within or connected to the mobile device 110 or the on-board computer 114 . Such modules may implement part of all of the various exemplary methods discussed herein or other related embodiments.
- such modules may include a vehicle control module for determining and implementing control decisions to operate the vehicle 108 , a system status module for determining the operating status of autonomous operation features, a monitoring module for monitoring the operation of the vehicle 108 , a remediation module for correcting abnormal operating states of autonomous operation features, an insurance module for determining risks and costs associated with operation of the vehicle 108 , an alert module for generating and presenting alerts regarding the vehicle 108 or the vehicle operator, a risk assessment module for determining risks associated with operation of the vehicle 108 by the autonomous operation features or by the vehicle operator, an identification module for identifying or verifying the identity of the vehicle operator, an information module for obtaining information regarding a vehicle operator or vehicle 108 , a use cost module for determining costs associated with operation of the vehicle 108 , a comparison module for comparing one or more costs associated with owning or operating the vehicle 108 , an update module for updating an autonomous operation feature of the vehicle 108 , and/or other modules.
- a vehicle control module for determining and implementing control decisions to
- the controller 204 of the on-board computer 114 may implement a vehicle control module by the autonomous vehicle operation application 232 to communicate with the sensors 120 to receive information regarding the vehicle 108 and its environment and process that information for autonomous operation of the vehicle 108 .
- the controller 204 may further implement a communication module based upon the autonomous communication application 234 to receive information for external sources, such as other autonomous vehicles, smart infrastructure (e.g., electronically communicating roadways, traffic signals, or parking structures), or other sources of relevant information (e.g., weather, traffic, local amenities).
- Some external sources of information may be connected to the controller 204 via the network 130 , such as the server 140 or internet-connected third-party databases (not shown).
- the autonomous vehicle operation application 232 and the autonomous communication application 234 are shown as two separate applications, it should be understood that the functions of the autonomous operation features may be combined or separated into any number of the software applications 230 or the software routines 240 .
- the controller 204 may further implement a monitoring module by the autonomous operation monitoring application 236 to communicate with the server 140 to provide information regarding autonomous vehicle operation.
- This may include information regarding settings or configurations of autonomous operation features, data from the sensors 120 regarding the vehicle environment, data from the sensors 120 regarding the response of the vehicle 108 to its environment, communications sent or received using the communication component 122 or the communication unit 220 , operating status of the autonomous vehicle operation application 232 and the autonomous communication application 234 , and/or commands sent from the on-board computer 114 to the control components (not shown) to operate the vehicle 108 .
- the information may be received and stored by the server 140 implementing the autonomous operation information monitoring application 141 , and the server 140 may then determine the effectiveness of autonomous operation under various conditions by implementing the feature evaluation application 142 and the compatibility evaluation application 143 .
- the effectiveness of autonomous operation features and the extent of their use may be further used to determine risk associated with operation of the autonomous vehicle by the server 140 implementing a risk assessment module or insurance module associated with the risk assessment application 144 .
- the mobile device 110 or the on-board computer 114 may include additional sensors, such as the GPS unit 206 or the accelerometer 224 , which may provide information regarding the vehicle 108 for autonomous operation and other purposes.
- the communication unit 220 may communicate with other autonomous vehicles, infrastructure, or other external sources of information to transmit and receive information relating to autonomous vehicle operation.
- the communication unit 220 may communicate with the external sources via the network 130 or via any suitable wireless communication protocol network, such as wireless telephony (e.g., GSM, CDMA, LTE, etc.), Wi-Fi (802.11 standards), WiMAX, Bluetooth, infrared or radio frequency communication, etc.
- the communication unit 220 may provide input signals to the controller 204 via the I/O circuit 216 .
- the communication unit 220 may also transmit sensor data, device status information, control signals, and/or other output from the controller 204 to one or more external sensors within the vehicle 108 , mobile devices 110 , on-board computers 114 , and/or servers 140 .
- the mobile device 110 and/or the on-board computer 114 may include a user-input device (not shown) for receiving instructions or information from the vehicle operator, such as settings relating to an autonomous operation feature.
- the user-input device may include a “soft” keyboard that is displayed on the display 202 , an external hardware keyboard communicating via a wired or a wireless connection (e.g., a Bluetooth keyboard), an external mouse, a microphone, or any other suitable user-input device.
- the user-input device may also include a microphone capable of receiving user voice input.
- FIG. 3 illustrates a flow diagram of an exemplary autonomous vehicle operation method 300 , which may be implemented by the autonomous vehicle insurance system 100 .
- the method 300 may begin at block 302 when the controller 204 receives a start signal.
- the start signal may be a command from the vehicle operator through the user-input device to enable or engage one or more autonomous operation features of the vehicle 108 .
- the vehicle operator 108 may further specify settings or configuration details for the autonomous operation features.
- the settings may relate to one or more destinations, route preferences, fuel efficiency preferences, speed preferences, and/or other configurable settings relating to the operation of the vehicle 108 .
- fully autonomous vehicles may include additional features or settings permitting them to operate without passengers or vehicle operators within the vehicle.
- a fully autonomous vehicle may receive an instruction to find a parking space within the general vicinity, which the vehicle may do without the vehicle operator. The vehicle may then be returned to a selected location by a request from the vehicle operator via a mobile device 110 or otherwise. This feature may further be adapted to return a fully autonomous vehicle if lost or stolen.
- the settings may include enabling or disabling particular autonomous operation features, specifying thresholds for autonomous operation, specifying warnings or other information to be presented to the vehicle operator, specifying autonomous communication types to send or receive, specifying conditions under which to enable or disable autonomous operation features, and/or specifying other constraints on feature operation.
- a vehicle operator may set the maximum speed for an adaptive cruise control feature with automatic lane centering.
- the settings may further include a specification of whether the vehicle 108 should be operating as a fully or partially autonomous vehicle.
- the start signal may consist of a request to perform a particular task (e.g., autonomous parking) and/or to enable a particular feature (e.g., autonomous braking for collision avoidance).
- the start signal may be generated automatically by the controller 204 based upon predetermined settings (e.g., when the vehicle 108 exceeds a certain speed and/or is operating in low-light conditions).
- the controller 204 may generate a start signal when communication from an external source is received (e.g., when the vehicle 108 is on a smart highway or near another autonomous vehicle).
- the controller 204 may receive sensor data from the sensors 120 during vehicle operation at block 304 .
- the controller 204 may also receive information from external sources through the communication component 122 and/or the communication unit 220 .
- the sensor data may be stored in the RAM 212 for use by the autonomous vehicle operation application 232 .
- the sensor data may be recorded in the data storage 228 and/or transmitted to the server 140 via the network 130 .
- the sensor data may alternately either be received by the controller 204 as raw data measurements from one of the sensors 120 and/or may be preprocessed by the sensor 120 prior to being received by the controller 204 .
- a tachometer reading may be received as raw data and/or may be preprocessed to indicate vehicle movement or position.
- a sensor 120 comprising a radar and/or LIDAR unit may include a processor to preprocess the measured signals and send data representing detected objects in 3-dimensional space to the controller 204 .
- the autonomous vehicle operation application 232 , other applications 230 , and/or routines 240 may cause the controller 204 to process the received sensor data at block 306 in accordance with the autonomous operation features.
- the controller 204 may process the sensor data to determine whether an autonomous control action is required and/or to determine adjustments to the controls of the vehicle 108 .
- the controller 204 may receive sensor data indicating a decreasing distance to a nearby object in the vehicle's path and process the received sensor data to determine whether to begin braking (and, if so, how abruptly to slow the vehicle 108 ).
- the controller 204 may process the sensor data to determine whether the vehicle 108 is remaining with its intended path (e.g., within lanes on a roadway).
- the controller 204 may determine appropriate adjustments to the controls of the vehicle to maintain the desired bearing. If the vehicle 108 is moving within the desired path, the controller 204 may nonetheless determine whether adjustments are required to continue following the desired route (e.g., following a winding road). Under some conditions, the controller 204 may determine to maintain the controls based upon the sensor data (e.g., when holding a steady speed on a straight road).
- the controller 204 may cause the control components of the vehicle 108 to adjust the operating controls of the vehicle to achieve desired operation at block 310 .
- the controller 204 may send a signal to open or close the throttle of the vehicle 108 to achieve a desired speed.
- the controller 204 may control the steering of the vehicle 108 to adjust the direction of movement.
- the vehicle 108 may transmit a message or indication of a change in velocity or position using the communication component 122 and/or the communication unit 220 , which signal may be used by other autonomous vehicles to adjust their controls.
- the controller 204 may also log or transmit the autonomous control actions to the server 140 via the network 130 for analysis.
- the controller 204 may continue to receive and process sensor data at blocks 304 and 306 until an end signal is received by the controller 204 at block 312 .
- the end signal may be automatically generated by the controller 204 upon the occurrence of certain criteria (e.g., the destination is reached or environmental conditions require manual operation of the vehicle 108 by the vehicle operator). Additionally, or alternatively, the vehicle operator may pause, terminate, and/or disable the autonomous operation feature or features using the user-input device or by manually operating the vehicle's controls, such as by depressing a pedal or turning a steering instrument. When the autonomous operation features are disabled or terminated, the controller 204 may either continue vehicle operation without the autonomous features or may shut off the vehicle 108 , depending upon the circumstances.
- the controller 204 may alert the vehicle operator in advance of returning to manual operation.
- the alert may include a visual, audio, and/or other indication to obtain the attention of the vehicle operator.
- the controller 204 may further determine whether the vehicle operator is capable of resuming manual operation before terminating autonomous operation. If the vehicle operator is determined not be capable of resuming operation, the controller 204 may cause the vehicle to stop and/or take other appropriate action.
- FIG. 4 illustrates a flow diagram depicting an exemplary monitoring method 400 during vehicle operation, which may be implemented by the autonomous vehicle insurance system 100 .
- the method 400 may monitor the operation of the vehicle 108 and adjust risk levels and rates based upon vehicle use.
- the exemplary embodiment is described as primarily performed by the on-board computer 114 , the method 400 may be implemented by the mobile device 110 , the on-board computer 114 , the server 140 , or a combination thereof.
- the on-board computer 114 may determine the configuration and operating status of the autonomous operation features (including the sensors 120 and the communication component 122 ) at block 404 .
- the identity of the vehicle operator may be determined and/or verified at block 406 , which identity may be used to determine or receive a vehicle operator profile at block 408 .
- the vehicle operator profile may contain information regarding the vehicle operator's ability to manually operate the vehicle and/or past use of autonomous operation features by the vehicle operator.
- Information from the sensors 120 and/or external data from the communication component 122 may be used at block 410 to determine environmental conditions in which the vehicle 108 is operating. Together, this information determined at blocks 404 - 410 may be used at block 412 to determine one or more risk levels associated with operation of the vehicle, from which may be determined a costs associated with an insurance policy at block 414 .
- information regarding the determined cost may be presented to the vehicle operator or other insurance customer associated with the vehicle 108 at block 416 .
- the vehicle operator and/or insurance customer may be presented with recommendations or options regarding the cost associated with the insurance policy at block 418 . Presentation of options may assist the vehicle operator and/or insurance customer in reducing the cost by allowing the vehicle operator and/or insurance customer to select a lower-cost option (e.g., by adjusting the settings associated with the autonomous operation features).
- the vehicle operator and/or insurance customer may be able to select one or more of the options to effect an adjustment in the risk levels and/or insurance cost.
- the method 400 may continue monitoring operation of the vehicle 108 at block 420 , and adjustments may be made to the risk levels and insurance costs. If the settings associated with the autonomous operation features are determined to have changed at block 422 (e.g., as a result of the vehicle operator taking manual operation of additional controls), the one or more risk levels may be determined based upon the new settings at block 412 , in which case the blocks 414 - 422 may be repeated. When no changes have been made to the settings, the method 400 may further check for changes to the environmental conditions and/or operating status of the autonomous operation features at block 424 . If changes are determined to have occurred at block 424 , the one or more risk levels may be determined based upon the new settings at block 412 , as at block 422 .
- the method 400 may determine whether vehicle operations are ongoing or whether operation is complete at block 426 . When vehicle operation is ongoing, the method 400 may continue to monitor vehicle operation at block 420 . When vehicle operation is complete, information regarding operation of the vehicle may be recorded at block 428 , at which point the method 400 may terminate.
- the on-board computer 114 may receive an indication of vehicle operation. This indication may be received from the vehicle operator (either directly or through the mobile device 110 ), and/or it may be generated automatically. For example, the on-board computer 114 or the mobile device 110 may automatically generate an indication of vehicle operation when the vehicle starts operation (e.g., upon engine ignition, system power-up, movement of the vehicle 108 , etc.). Upon receiving the indication of vehicle operation, the on-board computer 114 may initiate a system check and/or begin recording information regarding operation of the vehicle 108 .
- the on-board computer 114 may determine the configuration and operating status of one or more autonomous operation features of the vehicle 108 . This may include determining the configuration, settings, and/or operating status of one or more hardware or software modules for controlling part or all of the vehicle operation, aftermarket components disposed within the vehicle to provide information regarding vehicle operation, and/or sensors 120 disposed within the vehicle. In some embodiments, a software version, model version, and/or other identification of the feature or sensor may be determined. In further embodiments, the autonomous operation feature may be tested to assess proper functioning, which may be accomplished using a test routine or other means.
- the sensors 120 or the communication component 122 may be assessed to determine their operating status (e.g., quality of communication connections, signal quality, noise, responsiveness, accuracy, etc.).
- test signals may be sent to one or more of the sensors 120 , responses to which may be received and/or assessed by the on-board computer to determine operating status.
- signals received from a plurality of sensors may be compared to determine whether any of the sensors are malfunctioning. Additionally, signals received from the sensors may be used, in some embodiments, to calibrate the sensors.
- the on-board computer 114 may determine the identity of the vehicle operator. To determine the identity of the vehicle operator, the on-board computer 114 may receive and process information regarding the vehicle operator. In some embodiments, the received information may include sensor data from one or more sensors 120 configured to monitor the interior of the vehicle. For example, a camera or other photographic sensor may provide photographic information regarding the vehicle operator, which may be processed and compared with other photographic data for a plurality of persons to determine the identity of the vehicle operator. In further embodiments, the on-board computer may receive information from a mobile computing device associated with the vehicle operator, such as a mobile phone or wearable computing device. For example, a mobile phone may connect to the on-board computer 114 , which may identify the vehicle operator. Additional steps may be taken to verify the identity of the vehicle operator, such as comparing a weight sensed on a seat or use of voice recognition algorithms.
- the on-board computer 114 may determine and/or access a vehicle operator profile based upon the identity of the vehicle operator determined at block 406 .
- the vehicle operator profile may include information regarding the vehicle operator's style of operating the vehicle, including information regarding past operation of one or more vehicles by the vehicle operator. This information may further contain past vehicle operator selections of settings for one or more autonomous operation features.
- the on-board computer 114 may request or access the vehicle operator profiled based upon the determined identity.
- the on-board computer 114 may generate the vehicle operator profile from information associated with the identified vehicle operator.
- the vehicle operator profile may include information relating to one or more risks associated with operation of the vehicle by the vehicle operator.
- the vehicle operator profile for a driver may include information relating to risk levels based upon past driving patters or habits in a variety of relevant environments, which may include risk levels associated with manual operation of the vehicle by the driver.
- the vehicle operator profile may include information regarding default settings used by the vehicle operator for the autonomous operation features.
- the on-board computer 114 may determine environmental conditions within which the vehicle 108 is or is likely to be operating. Such environmental conditions may include weather, traffic, road conditions, time of day, location of operation, type of road, and/or other information relevant to operation of the vehicle. The environmental conditions may be determined based upon signals received from the sensors 120 , from external data received through the communication component 122 , and/or from a combination of sources. The environmental conditions may then be used in determining risk levels associated with operation of the vehicle 108 .
- the on-board computer may determine one or more risk levels associated with operation of the vehicle 108 .
- the risk levels may be determined based upon a combination of risk factors relating to the autonomous operation features and/or risk factors relating to the vehicle operation.
- Risks associated with the autonomous operation features may be determined based upon the configuration and/or operating status of the autonomous operation features, the settings of the autonomous operation features, and the vehicle environment. Risks associated with the vehicle operation may be determined based upon the autonomous operation features settings (i.e., the extent to which the vehicle operator will be controlling vehicle operations) and/or the vehicle operator profile.
- the combined risk may account for the likelihood of the autonomous operation features and/or the vehicle operator controlling vehicle operations with respect to relevant functions of the vehicle 108 .
- the on-board computer 114 may determine a cost associated with an insurance policy based upon the one or more risks.
- the server 140 may receive information regarding the vehicle operator and the autonomous operation features and/or may determine the cost associated with the insurance policy based upon the risks.
- the cost may be based upon risk levels associated with separate autonomous operation features, interaction between autonomous operation features, the design and capabilities of the vehicle 108 , the past operating history of the vehicle operator as included in the vehicle operator profile, and/or other information regarding the probability of an accident, collision, and/or other loss event involving the vehicle 108 .
- Each of the separate risks may depend upon the environmental conditions, and the risks may be weighted based upon the likelihood of each situation.
- a total risk may be determined relating to operation of the vehicle under foreseeable conditions with specific settings and configurations of autonomous operation features by a specific vehicle operator.
- the total risk may be used to determine one or more costs associated with the insurance policy, such as a premium and/or discount.
- information regarding the cost associated with the insurance policy may be presented to the vehicle operator or insurance customer at block 416 .
- the information may be presented by a display, such as the display 202 of the on-board computer 114 or the mobile device 110 .
- the information may be presented either for informational purposes or to receive acceptance of the vehicle operator or insurance customer.
- the insurance cost information may include an indication of one or more of a premium, rate, rating, discount, reward, special offer, points level, program, refund, and/or other costs associated with one or more insurance policies.
- summary information may be presented regarding insurance costs, including a risk level (e.g., high risk, low risk, a risk/cost level on a spectrum, etc.).
- presentation of insurance cost information may be suppressed or delayed (e.g., cost information may be presented in summary form on a periodic billing statement).
- options or recommendations regarding the cost associated with the insurance policy may be presented to the vehicle operator or insurance customer at block 418 .
- the options or recommendations may likewise be presented by a display, such as the display 202 of the on-board computer 114 and/or the mobile device 110 .
- the options or recommendations may include information regarding costs associated with other settings or configurations of the autonomous operation features (e.g., enabling additional features, selecting an operating mode with lower risks under the determined environmental conditions, etc.).
- the recommendations or options may be presented for informational purposes only, requiring the vehicle operator or insurance customer to make any adjustments separately (e.g., through a settings module or other means of adjusting settings for the autonomous operation features).
- the vehicle operator or insurance customer may select one or more of the options, whereby adjustments to the configuration or settings of the autonomous operation features may be caused to be implemented by the on-board computer 114 or other controlling device.
- the options or recommendations may include options or recommendations to update the software version of one or more autonomous operation features, in which case information regarding a cost associated with updating the features (if applicable) may be presented. Once the information and/or options or recommendations regarding insurance costs have been presented at blocks 416 - 418 (including, in some embodiments, while such presentation is occurring), the on-board computer 114 may monitor operation of the vehicle 108 .
- the on-board computer 114 may monitor operation of the vehicle 108 , including autonomous operation feature control decisions, signals from the sensors 120 , external data from the communication component 122 , and/or control decisions of the vehicle operator. Monitoring vehicle operation may include monitoring data received directly from the features, sensors, and/or other components, as well as summary information regarding the condition, movement, and/or environment of the vehicle 108 .
- the on-board computer 114 and/or mobile device 110 may cause the operating data to be stored or recorded, either locally in the data storage 228 and/or via server 140 in the program memory 160 and/or the database 146 . Monitoring may continue until vehicle operation is complete (e.g., the vehicle has reached its destination and shut down), including during any updates or adjustments.
- the on-board computer 114 may determine whether any changes have been made to the settings or configuration of the autonomous operation features. If such changes or adjustments have been made, the on-board computer 114 may proceed to determine new risk levels and insurance costs at blocks 412 - 414 and/or present the information to the vehicle operator or insurance customer at blocks 416 - 418 , as discussed above. In some embodiments, minor changes below a minimum change threshold may be ignored when determining whether any changes have been made. In further embodiments, the cumulate effect of a plurality of such minor changes below the minimum change threshold may be considered as a change at block 422 when the cumulative effect of the minor changes reaches and/or exceeds the minimum change threshold.
- the on-board computer 114 may further determine whether any changes in the environmental conditions and/or operating status of the autonomous operation features or sensors have occurred. Although these steps are illustrated separately for clarity, it should be understood that they may be further divided or combined in various embodiments.
- the on-board computer 114 may determine whether any changes have occurred to the environmental conditions of the vehicle 108 and/or the operating status of the autonomous operation features, sensors 120 , or communication component 122 . Such changes may occur when weather or traffic conditions change, when sensors 120 malfunction or become blocked by debris, and/or when the vehicle 108 leaves an area where external data is available via the communication component 122 . When such changes occur, the risk levels associated with control of the vehicle 108 by the vehicle operator and the autonomous operation features may likewise change. Therefore, it may be advantageous to adjust the use of the autonomous operation features to account for such changes.
- the on-board computer 114 may proceed to determine new risk levels and insurance costs at blocks 412 - 414 and/or present the information to the vehicle operator or insurance customer at blocks 416 - 418 , as discussed above, when such changes are determined to have occurred at block 424 . Similar to the determination at block 422 , minor changes below a minimum change threshold may be ignored at block 424 , unless the cumulative effect of the changes reaches or exceeds the minimum change threshold. When no changes are determined to have occurred at block 424 , the method 400 may continue to monitor the operation of the vehicle 108 until vehicle operation is determined to have ended.
- the on-board computer 114 may determine whether vehicle operations are complete. This may include determining whether a command to shut down the vehicle 108 has been received, whether the vehicle 108 has remained idle at a destination for a predetermined period of time, and/or whether the vehicle operator has exited the vehicle 108 . Until operation is determined at block 426 to be complete (i.e., when the vehicle trip has concluded), the on-board computer 114 may continue to monitor vehicle operation at block 420 , as discussed above. When operation is determined to be complete at block 426 , the on-board computer 114 may further cause a record of the operation of the vehicle 108 to be made or stored.
- Such records may include operating data (in full or summary form) and may be used for assessing risks associated with one or more autonomous operation features or the vehicle operator.
- records of operating data may be generated and stored continually during operation.
- the partial or completed records may be transmitted to the server 140 to be stored in the database 146 . After completion and recordation of the vehicle operation, the method 400 may terminate.
- FIG. 5 illustrates a flow diagram depicting an exemplary operating status assessment method 500 that may be used to determine operation status of the autonomous operation features, sensors 120 , and/or communication component 122 , as indicated in blocks 404 and 424 above.
- the method 500 may evaluate the autonomous operation features of the vehicle 108 (including sensors 120 ) and determine whether they are operating correctly, are malfunctioning, and/or are operating with impaired or degraded quality. Such determinations may be particularly important as the vehicle 108 ages or in environments that may block or damage sensors 120 . In such cases, the original effectiveness of the autonomous operation features may be reduced as sensors become less accurate or processing of the sensor data is slowed (such as by software version updates that improve accuracy but require greater computational resources).
- the exemplary method 500 may be implemented regularly to ensure appropriate risk assessment, as well as periodically to certify the operating status level of the vehicle for roadworthiness or insurance rate adjustment.
- periodic evaluation may be performed using special purpose computing devices and/or by licensed or authorized third parties. Periodic evaluation may further include more thorough testing and analysis of the vehicle 108 , which may include testing at a test environment.
- the exemplary embodiment is described as primarily performed by the on-board computer 114 , the method 500 may be implemented by the mobile device 110 , the on-board computer 114 , the server 140 , or a combination thereof.
- the configuration of the sensors 120 may be determined at block 504 .
- the functioning of autonomous operation feature software routines may further be determined at block 506 .
- a test signal may be transmitted to the sensors 120 at block 508 , and/or sensor data may be received at block 510 .
- the sensor data may include a response to the test signal, as well as other signals from the sensors based upon the vehicle environment or operation of the vehicle 108 .
- the operating status of the autonomous operation features and components may be determined at block 512 . If any impairments are detected at block 514 , the method 500 may attempt to remediate the impairments at block 516 .
- an alert may be generated and presented to the vehicle operator or an insurance customer at block 520 .
- a report indicating the operational status of the autonomous operation features may be generated at block 522 .
- the report may be transmitted to an insurer at block 524 , and/or a cost associated with an insurance policy associated with the vehicle 108 may be determined at block 526 . The determined cost may be presented with the report at block 528 to the vehicle operator or insurance customer.
- the on-board computer 114 may receive an indication of a request to check the operating status of the autonomous operation features of the vehicle 108 .
- the request may be generated in response to a user interaction with the mobile device 110 or a special-purpose computing device communicatively connected to the vehicle 108 .
- an application running on the mobile device 110 may allow the user of the mobile device 110 to request an evaluation of the autonomous operation features.
- a special-purpose computing device may be connected to the vehicle 108 (wirelessly or via a communication port) to evaluate the operating status of the autonomous operation features.
- the request may be automatically generated by the on-board computer 114 in response to the occurrence of an event, such as receipt of a command to start the vehicle, receipt of a command to shut off the vehicle, receipt of an indication of a collision involving the vehicle, or receipt of an indication of damage to the vehicle.
- the request may be generated by the server 140 and transmitted to the on-board computer 114 to determine the operating status of the autonomous operation features. Such server-generated requests may be used for insurance rating, and may be generated periodically.
- the request may further include information regarding the extent of the evaluation of the operating status of the autonomous operation features. For example, the request may indicate that only software or sensors are to be evaluated, or the request may indicate one or more tolerances within which the system components may be determined to be operating properly.
- the on-board computer 114 may determine the configuration of the sensors 120 disposed within or communicatively connected to the vehicle 108 . This may include determining any of the number, type, location, technical specifications, or characteristics of the sensors 120 . In further embodiments, the on-board computer 114 may determine normal functioning characteristics and output ranges for the sensors 120 , which may be used in determining whether the sensors 120 are functioning normally. Determining normal functioning characteristics may include requesting such information from the server 140 or accessing such information stored within the data storage 228 . In some embodiments, the configuration of one or more communication components 122 may also be determined at block 504 .
- the on-board computer 114 may execute one or more software diagnostic routines to evaluate the operation of the software components of the autonomous operation features.
- a special-purpose computing device or mobile device 110 may execute the routines or receive the output of the routines.
- the software diagnostic routines may cause test inputs to be presented to the autonomous operation features and receive responses based upon the test inputs.
- the software diagnostic routines may simulate sensor inputs corresponding to a situation in which the autonomous operation features should cause the vehicle to brake, then record the control signals generated by the autonomous operation features.
- the control signals output from the autonomous operation feature software may be disconnected from the operating controls of the vehicle 108 or suppressed during evaluation to prevent the vehicle 108 from physically responding to the test inputs.
- the on-board computer 114 may generate and transmit one or more test signals to the sensors 120 .
- the test signals may cause the sensors 120 to respond with status information, such as verification of the communicative connection, signal quality, a predetermined set of response signals, or other information regarding the sensors.
- the test signals may cause the sensors 120 to enter a test mode or execute a calibration routine, in which case information regarding the operating status of the sensors 120 may be generated at the sensors 120 and transmitted to the on-board computer 114 .
- the on-board computer 114 may further generate and transmit test signals to the communication component 122 .
- the on-board computer 114 may receive sensor data from the sensors 120 or communication components 122 .
- the received sensor data may include responses to test signals.
- the received sensor data may, in some embodiments, also or alternatively include sensor data generated in the ordinary course of operation of the sensors.
- the received sensor data may include data indicating sensor readings of obstacles within sensor range of the vehicle 108 .
- Such ordinary course sensor data may be combined and compared to determine the operating status of each of a plurality of sensors connected to the vehicle 108 .
- the on-board computer 114 may determine the operating status of the autonomous operation features, including the sensors 120 and the communication component 122 , based upon the received information at blocks 506 and 510 . This may include determining the signal quality or accuracy of the sensor data or the accuracy or response time of the autonomous operation feature software. In some embodiments, determining the operating status of a sensor 120 may include determining an expected sensor output signal based upon information received from other sensors 120 and comparing the actual output signal from the sensor to the expected output signal. To avoid minor deviations from expected sensor or software operation from being interpreted as a malfunction, a range of values indicating a normal operating status may be allowed for the sensors and software.
- a sensor signal within the normal range may be treated as indicating a normal operating status even if the value is slightly different from the expected value.
- sensors 120 from which no signal is received may be determined to be missing, malfunctioning, or damaged. Some sensors 120 may further be determined to be blocked based upon the received sensor data.
- the on-board computer 114 may determine whether any of the autonomous operation features, sensors 120 , or communication components 122 have an impaired operating status. If all are operating normally, then the on-board computer 114 may proceed to generate a report at block 522 . If any impairments are detected at block 514 , however, the on-board computer 114 may attempt to remediate the impairment at block 516 . Remediation attempts may be determined based upon the type of feature or component, as well as the type of impairment. For example, a remediation attempt for autonomous operation feature software errors may include rebooting or reinstalling a portion of the software. As another example, a signal error in a sensor 120 may be remediated by calibration of the sensor 120 based upon available sensor data.
- Some vehicles 108 may include remediation components (not shown) for certain types of common impairments of some or all sensors 120 .
- sensors 120 may become blocked by snow or ice in cold climates, so heating elements may be disposed within the vehicle 108 to melt accumulated snow or ice from an area around the sensors 120 .
- Other types of blockages such as by snow, ice, rain, dirt, mud, or condensation, may be addressed with other remediation components.
- a report may be generated at block 522 . If one or more impairments remain, then an alert may be generated and presented to the vehicle operator or insurance customer at block 520 .
- the alert may include information regarding the type of autonomous operation feature or sensor impairment, the severity of the impairment, an impact on risks associated with autonomous operation, whether some autonomous operation features must be disabled, or recommendations regarding autonomous operation features use and settings.
- the on-board computer 114 may generate a report at block 522 .
- the on-board computer 114 may generate a report indicating the operating status of the autonomous operation features and components based upon the information received at blocks 506 and 510 . If remediation of one or more impairments has been attempted, the report may so indicate and may be adjusted based upon the results determined at block 518 .
- the report may include information regarding impaired features or sensors, while in other embodiments the report may include information all features and sensors regarding.
- the report may include recommendations regarding autonomous operation feature use or settings, as well as recommendation maintenance or updates.
- the report may include a certification of the operating status of the autonomous operation features, sensors, or other components.
- the report may include information regarding maintenance performed on the vehicle 108 , which may be recorded in the data storage 228 . Where the evaluation is performed by an authorized or licensed third party, information regarding the third party may be included in the report.
- the report may be transmitted to a server 140 associated with an insurer for determination of costs or adjustments to one or more insurance policies.
- the server 140 may determine one or more costs associated with the one or more insurance policies based upon the report.
- the one or more costs may include one or more of the following: a premium, a discount, a surcharge, a rate level, a cost based upon a distance traveled, a cost based upon a vehicle trip, or a cost based upon a duration of vehicle operation.
- the server 140 may first determine one or more adjustments to risk levels based upon the information in the report. For example, a risk level associated with an autonomous operation feature may be increased if one or more sensors used by the feature are impaired. The risk levels may be further used to determine costs based upon expected loss rates for the vehicle 108 and the vehicle operator.
- the report may be presented to the vehicle operator or insurance customer by a display, such as display 202 .
- the report may be presented in full or may be summarized for ease of use.
- the one or more costs associated with the insurance policy determined at block 526 may also be presented.
- the report includes a certification of the status of the autonomous operation features and components
- the certification may also be presented to the vehicle operator or insurance customer.
- the certification may be further transmitted to an account associated with the vehicle operator or insurance customer or may be transmitted to a third party, such as a government agency.
- the vehicle operator or insurance customer may be presented with an option to save, record, print, or transmit the report.
- FIG. 6 illustrates a flow diagram of an exemplary operating status monitoring method 600 that may be used to determine operation status of the autonomous operation features, sensors 120 , and/or communication component 122 , in addition to or alternatively to the exemplary method 500 above.
- the method 600 may be implemented while the vehicle 108 is in operation to monitor the operating status of the autonomous operation features and components.
- the method 600 may monitor the vehicle operating data at block 602 to determine operating status of the autonomous operation features and components at block 604 .
- a change in operating status is detected at block 606 , one or more corresponding changes in risk levels may be determined at block 608 .
- the method 600 may determine whether control of the vehicle 108 can be safely transferred to the vehicle operator at block 616 . If the vehicle operator is prepared and able to assume control of the vehicle 108 , then vehicle operation may be transferred to the vehicle operator at block 620 . If control cannot be safely transferred, the vehicle 108 may cease operations and shut down at block 618 . Once the vehicle 108 is no longer operating, the method 600 may terminate.
- the exemplary embodiment is described as primarily performed by the on-board computer 114 , the method 600 may be implemented by the mobile device 110 , the on-board computer 114 , the server 140 , or a combination thereof.
- FIGS. 7A-B illustrate flow diagrams depicting exemplary vehicle operation hand-off methods 700 that may be used to transfer operation of the vehicle 108 from one or more autonomous operation features to the vehicle operator.
- FIG. 7A illustrates hand-off of control when determined necessary based upon heightened risk levels associated with operation by the one or more autonomous operation features under the environmental conditions.
- FIG. 7B illustrates hand-off of control when requested by the vehicle operator while one or more autonomous operation features are performing vehicle control tasks.
- the methods 700 illustrated in FIGS. 7A and 7B may be combined or separately implemented in various embodiments. Although the exemplary embodiment is described as primarily performed by the on-board computer 114 , the exemplary method 700 may be implemented by the mobile device 110 , the on-board computer 114 , the server 140 , and/or a combination thereof.
- Exemplary vehicle operation hand-off method 700 may be implemented at any time when one or more autonomous operation features are controlling part or all of the operation of the vehicle 108 .
- the method 700 may begin by identifying the vehicle operator at block 702 and receiving a vehicle operator profile for the vehicle operator at block 704 .
- the operating data (including, in some embodiments, sensor data and external data) may be received and used to monitor operation of the vehicle 108 .
- a request to disable one or more autonomous operation features may be received from the vehicle operator at block 732 .
- Autonomous risk levels associated with operation of the vehicle 108 by the autonomous operation features and operator risk levels associated with operation of the vehicle 108 by the vehicle operator may be determined at block 708 and 710 , respectively.
- the determined risk levels may be used at block 712 to determine whether to disable one or more autonomous operation features.
- the determination of whether to disable one or more autonomous operation features may further be based upon the preparedness level of the vehicle operator determined at block 716 .
- the method 700 may transfer control to the vehicle operator. In some embodiments, this may include determining whether the vehicle operator is able to safely assume control by determining whether the vehicle operator's preparedness level is above a transfer threshold level at block 718 . If so, an alert may be presented to the vehicle operator at block 720 to notify the vehicle operator of the transfer of control from the one or more autonomous operation features before transferring operation at block 722 .
- an alert may be presented at block 730 to attempt to prepare the vehicle operator to assume control if the risk levels associated with continued operation by the autonomous operation features do not exceed a critical risk threshold at block 726 .
- the vehicle operator's preparedness level may be determined again at block 716 and evaluated at block 718 . If the risk levels exceed the critical threshold at block 726 or the vehicle operator's preparedness level is below the minimum threshold at block 724 , the vehicle 108 may discontinue operation at block 728 and the method 700 may end.
- the method 700 may continue to monitor the operating data at block 706 . If the vehicle operator requested that one or more autonomous operation features be disabled, the method 700 may present an alert at block 734 to notify the vehicle operator that disabling the autonomous operation features is not recommended. In some embodiments, options to override the determination not to disable the autonomous operation features may be presented to the vehicle operator at block 736 , which the vehicle operator may select at block 738 . If the vehicle operator is determined at block 740 to have not selected an option to override the determination, the method 700 may continue to monitor operation data at block 706 .
- control of operation may be transferred from the one or more autonomous operation features to the vehicle operator.
- one or more risk levels associated with disabling the autonomous operation features may be determined at block 742 . If the risk levels are determined to be below a critical threshold at block 744 , control may be transferred to the vehicle operator. If the risk levels meet or exceed the critical threshold at block 744 , the vehicle 108 may instead discontinue operation at block 728 and the method 700 may end.
- FIG. 8 illustrates a flow diagram depicting an exemplary vehicle operator identification method 800 that may be used to adjust an insurance policy associated with the vehicle operator or vehicle 108 .
- the exemplary method 800 may begin with receipt of a request to identify the vehicle operator of the vehicle at block 802 .
- the vehicle operator may be identified by sensor data or received indications of identity, such as from a mobile device 110 .
- the method 800 may further determine whether the vehicle operator is authorized to operate the vehicle 108 at block 812 . If the vehicle operator is not authorized, an alert may be generated and vehicle operations may be limited at blocks 814 - 816 .
- a vehicle operator profile associated with the vehicle operator may be obtained at block 818 , and/or an insurance policy associated with the vehicle 108 or the vehicle operator may be identified at block 820 .
- operating data of the vehicle 108 may be received and used to adjust the vehicle operator profile and the insurance policy at blocks 822 - 826 .
- the method 800 may terminate.
- the exemplary embodiment is described as primarily performed by the on-board computer 114 , the method 800 may be implemented by the mobile device 110 , the on-board computer 114 , the server 140 , and/or a combination thereof.
- FIG. 9 illustrates a flow diagram depicting an exemplary vehicle operator use monitoring and evaluation method 900 that may be used to determine skill or risk levels associated with a vehicle operator or adjust an insurance policy.
- the exemplary method 900 may begin with determining the identity of the vehicle operator at block 902 . If a vehicle operator profile can be found for the vehicle operator at block 904 , the vehicle operator profile may be accessed at block 912 . If no vehicle operator profile can be found for the vehicle operator at block 904 , a vehicle operator profile may be created based upon vehicle operations and stored for future use at blocks 906 - 910 .
- the newly created vehicle operator profile may be generated at block 908 with vehicle operating data from only a short time period or may include only information regarding configuration and/or settings of the autonomous operation features, in which case operation of the vehicle may continue after the vehicle operator profile is generated. If operation is determined to be ongoing at block 914 , vehicle operation may be monitored and the vehicle operator profile may be updated at blocks 916 - 924 . In some embodiments, the vehicle operator may be able to select an option of a mode for vehicle operation. If such a mode selection is detected at block 916 , the settings of the autonomous operation features may be adjusted at block 918 . Vehicle operation may be monitored at block 920 based upon received operating data, which may be used to determine adjustments to the vehicle operator profile at block 922 .
- the method 900 may determine risk or skill levels associated with the vehicle operator at blocks 926 - 928 . These determined levels may be used at blocks 930 - 934 to generate a report or adjust an insurance policy.
- the exemplary embodiment is described as primarily performed by the on-board computer 114 , the method 900 may be implemented by the mobile device 110 , the on-board computer 114 , the server 140 , and/or a combination thereof.
- the vehicle operator profile may include information regarding the vehicle operator, including an operating style of the vehicle operation.
- the operating style may include information regarding frequency with which the vehicle operator operates the vehicle manually, uses one or more autonomous operation features, selects one or more settings for the autonomous operation features, and/or takes control from the autonomous operation features under various conditions.
- the operating style may further include information regarding observed control decisions made by the vehicle operator, such as rate of acceleration, frequency of lane changes, use of vehicle signaling devices, distances maintained from other vehicles or pedestrians, and/or other aspects of vehicle operation. For example, vehicle operator decisions regarding how long to stop at a stop sign or when to begin accelerating from such a stop in the presence of other vehicles or pedestrians may be included in the operating style.
- the vehicle operator profile may further include information regarding vehicle operator skill levels, as described below.
- the vehicle operator profile may include a risk profile or information regarding one or more risk levels associated with operation of the vehicle by the vehicle operator.
- risk levels may be associated with particular configurations or settings of autonomous operation features and/or particular conditions of the vehicle environment (e.g., time of day, traffic levels, weather, etc.).
- the vehicle operator profile may include information regarding attentiveness of the vehicle operator while the vehicle is being autonomously operated. For example, some vehicle operators may typically pay attention to road conditions while a vehicle is operating in a fully autonomous mode, while other vehicle operators may typically engage in other activities.
- the vehicle operator profile may include information regarding decisions made by the vehicle operator regarding actions that would result in adjustments to costs associated with an insurance policy (e.g., accepting or rejecting recommendations to optimize autonomous operation feature use to lower insurance costs).
- the vehicle operator profile or vehicle operator behavior data may indicate how well the specific vehicle operator drives in rain, snow, sleet, ice, heavy traffic, road construction, stop-and-go traffic, bumper-to-bumper traffic, country or rural traffic, and/or city or downtown street traffic.
- the current environment (or condition) may include or be rain, ice, snow, fog, heavy traffic, bumper-to-bumper traffic, road construction, city traffic, country or rural traffic, and/or may be associated with a type of road, such as a two-lane or four-lane highway, and/or downtown city street or other street having several traffic lights.
- the operating mode may include one or more settings or configurations of autonomous operation features.
- operating modes may include adjustments to settings that cause the autonomous operation features to control the vehicle 108 in a more or less aggressive manner with respect to speed, distance from other vehicles, distance from pedestrians, etc.
- the settings may cause the vehicle 108 to remain at least a minimum distance from other vehicles (which may depend upon vehicle speed or road conditions), and/or modes may set different minimum distances. Examples of modes may include a city driving mode, a highway driving mode, a rush operation mode, a smooth operation mode, a cautious mode, and/or a user-defined mode.
- an operating mode may be based upon the vehicle operator profile.
- the vehicle profile may include information indicating an operating style of the vehicle operator based upon observations of control commands by the vehicle operator, which profile information may be used to generate an operation mode that mimics the style of the vehicle operator.
- the operating style may mimic this length of time to provide an experience that seems normal or customary to the vehicle operator.
- FIG. 10 illustrates a flow diagram depicting an exemplary cost comparison method 1000 that may be used to compare costs associated with vehicles, some of which may include autonomous operation features.
- the exemplary method 1000 may begin by receiving a command to generate a comparison report between two or more alternative transportation options for an insurance customer or other user.
- the method 1000 may further receive information regarding one or more vehicle operators may be received at block 1004 and/or information regarding a first vehicle and a second vehicle at block 1006 .
- the first and second vehicles may differ in autonomous operation features or other characteristics.
- Cost levels associated with obtaining, operating, and insuring the first vehicle and the second vehicle may be determined at block 1008 , and/or a recommendation based upon the costs may be determined at block 1010 .
- a report including the costs levels, recommendation, and/or related information may be generated at block 1012 and presented to the insurance customer or other user at block 1014 . Additionally, one or more options may be presented along with the report at block 1016 , such as options to perform another comparison or present additional information. If an option is selected at block 1018 , the corresponding action may be performed at block 1020 .
- the exemplary embodiment is described as primarily performed by the server 140 , the method 1000 may be implemented by the mobile device 110 , the on-board computer 114 , the server 140 , and/or a combination thereof.
- FIG. 11 illustrates a flow diagram depicting an exemplary autonomous operation feature update method 1100 that may be used to identify, recommend, and/or install updates to autonomous operation features in appropriate autonomous or semi-autonomous vehicles.
- the updates may include software version updates.
- the exemplary method 1100 may begin with the receipt of an indication of an available update to an autonomous operation feature at block 1102 , which may include an update to a version of autonomous operation feature software.
- a plurality of vehicles having the autonomous operation feature may be identified at block 1104 based upon recorded features or communication with the plurality of vehicles.
- a change in one or more risk levels associated with the update may be determined for some or all of the identified vehicles at block 1106 , and/or a change in a cost associated with one or more of the plurality of vehicles may be determined at block 1108 . If the determined changes in risk levels or insurance costs meet certain criteria for installing the update at block 1110 , a notification regarding the update may be presented to an insurance customer at block 1112 . The notification may further include information regarding costs associated with the update. If an indication of acceptance of the update is received at block 1114 , the update may be installed at block 1116 .
- the method 1100 may be implemented by the mobile device 110 , the on-board computer 114 , the server 140 , and/or a combination thereof.
- FIG. 12 illustrates a flow diagram depicting an exemplary autonomous vehicle repair method 1200 that may be used to determine repairs needed as a result of damage to an autonomous or semi-autonomous vehicle.
- the exemplary method 1200 may begin by receiving an indication of damage to the vehicle 108 at block 1202 and/or receiving operating data associated with the vehicle 108 at block 1204 . Based upon the operating data, the type and extent of damage to the vehicle 108 may be determined at block 1206 , and/or repairs needed to fix the damage may be determined at block 1208 . Additionally, one or more expected costs (or ranges of costs) for the repairs may be estimated at block 1210 .
- An insurance policy associated with the vehicle 108 may be identified, and/or a maximum payment for the repairs may be determined at block 1212 based upon the estimated costs and the insurance policy.
- Information regarding the estimated cost or costs and the maximum payment under the insurance policy may be presented to an insurance customer at block 1214 .
- options associated with the repairs may be presented to the insurance customer at block 1216 , and/or a selection of one or more options may be received at block 1218 .
- An insurer or other party may cause a payment to be made at block 1220 to the insurance customer, beneficiary, or other relevant party based upon the estimated costs of repairing the damage and the selected option.
- the on-board computer 114 or server 140 may receive an indication of damage to the vehicle 108 .
- the indication may be received from a vehicle operator and/or insurance customer, and/or the indication may be automatically generated upon a determination of damage.
- the sensors 120 may provide sensor data to the on-board computer 114 that indicates a collision with another vehicle or other object.
- the substantially simultaneous disconnection and/or malfunction of a plurality of sensors 120 located in close proximity within the vehicle 108 may cause the on-board computer 114 to generate an indication of damage to the vehicle 108 .
- the on-board computer 114 and/or server 140 may receive operating data regarding operation of the vehicle.
- the operating data may cover operation of the vehicle both before and after the damage occurred, covering a period of time without the damage and a period of time with the damage.
- the operating data may include information received from the sensors 120 and/or the communication component 122 .
- the operating data may further include information regarding autonomous operation features, such as configurations or settings, and/or information regarding command controls issued by the autonomous operation features and/or vehicle operator.
- the operating data may further include information derived or determined from the sensor or other data, such as vehicle speed and/or direction.
- the operating data for the time period with damage may include sensor data and/or other data regarding the vehicle and/or the vehicle environment. Such data may be useful in determining the likely extent of the damage by determining damaged areas and/or systems of the vehicle 108 .
- the server 140 may determine damage to the vehicle 108 based upon the received operating data.
- the operating data may be compared against operating data for a plurality of previous instances of known vehicle damage stored within the database 146 to determine likely damage. Such assessment may be based information from similar vehicles (e.g., vehicles of the same make and model, body type, size, or production year).
- the operating data may be processed to generate a model of the vehicle in its environment at the time of the damage. For example, the operating data may indicate relative speeds and/or trajectories of vehicles involved in a collision with the vehicle 108 . This model may then be further used to determine likely damage based upon information regarding the vehicle 108 and/or previous loss reports for other vehicles.
- the determined damage may be reviewed by a verification routine of the server 140 and/or by a reviewer to verify that the determined level of damage appears to match the actual level of damage. Verification may include assessing the operating status of the sensors 120 and/or communication component 122 . In some embodiments, the damage may be determined based upon input from a special-purpose computing device or a human assessor.
- the server 140 may determine one or more repairs associated with the determined damage to the vehicle 108 .
- the repairs may be determined based upon comparisons of information regarding previously repaired vehicles' damage and repairs.
- the repairs may be determined based upon models and/or relationships between types of damage and types of repairs.
- the repairs may include replacing and/or fixing damage to one or more vehicle components, including the vehicle frame and body.
- the repairs may include alternative likely repairs, such that performance of one repair may foreclose the necessity of another repair.
- the operating data may indicate two or more probably types of damage, but only one type of damage may be present. Thus, repair of one type of likely damage would obviate the need to repair the other types of likely damage.
- the repairs may include one or more general repair services and/or one or more specialty repair services. General repair services may be performed by most vehicle repair facilities, whereas specialty repair services may require specialized equipment, materials, and/or expertise to perform the repairs.
- the server 140 may determine expected costs associated with the one or more repairs determined at block 1208 .
- the costs may include both direct costs of repair, as well as indirect costs, such as vehicle rental while the vehicle 108 is being repaired.
- the costs may be determined based upon information regarding actual costs of repairs performed on a plurality of other vehicles.
- the repair costs for other vehicles may be used to determine a range of expected costs and/or an average cost for each repair.
- the range of expected costs may further be used to determine one or more expected cost levels associated with the repairs, such as a median cost, a mean cost, a high cost or low cost (e.g., levels based upon percentages such as the 80 th percentile or the 20 th percentile of costs), costs associated with different likely damage levels, and/or indirect costs based upon the extent of the repairs.
- the costs may also be based upon comparisons of costs in one or more relevant geographic areas.
- minor damage occurring during a long-distance trip may not preclude operation of the vehicle 108 through the remainder of the trip, in which case costs associated with repair in multiple geographic areas may be determined (e.g., an area where the damage occurred, an area corresponding to a destination of the trip, or an area corresponding to the home location of the vehicle operator or insurance customer).
- the costs may be determined based upon quotes received from one or more repair facilities based upon the determined repairs and/or operating data.
- the server 140 may determine one or more maximum payments for the repairs to the vehicle 108 .
- the maximum payments may be based upon the determined costs of the repairs.
- the maximum payment may be based upon the range of repair costs.
- the maximum payment may be set to a level based upon the distribution of repair costs within the range, such that the maximum payment is equal to an actual cost of repairs for a vehicle at a certain percentile of vehicles within the actual repair cost range (e.g., 70 th percentile).
- the maximum payment may be based in whole or part upon the insurance policy under which payment may be made.
- a maximum payment amount may be set by the insurance policy, which may, in some embodiments, be further limited based upon the expected costs and/or range of expected costs determined at block 1210 .
- the server 140 may cause the one or more expected costs to be presented to the insurance customer, using the display 202 and/or other means.
- the maximum payment may be presented to the insurance customer together with the expected costs. For example, where a plurality of alternatives are presented regarding the repairs, each expected cost may include an indication of whether it is below the maximum payment.
- the server 140 may cause one or more options regarding the repairs to be presented to the insurance customer.
- the options may indicate timing, extent, and/or location of the repairs and may be associated with different costs for the repairs.
- the options may include options of one or more repair facilities at which the vehicle 108 may be repaired. Each facility may further be associated with a cost estimate and/or an estimate of a length of time required to complete the repairs.
- the estimates of costs and/or time for each facility may be based upon the operating data and/or determined damage.
- the estimates of costs and/or time for one or more of the repair facilities may be based upon quoted estimates solicited from the repair facilities received by the server 140 .
- the options may be presented together with an indication of whether each exceeds the maximum payment, such as by a warning presented in connection with any options that exceed the maximum payment.
- the server 140 may receive a selection of one or more of the options from the insurance customer or other authorized user. Upon receiving the selection, the server 140 may cause a payment to be made at block 1220 based upon the one or more selections. The payment may be made to the insurance customer and/or beneficiary of the insurance policy, or the payment may be made to a repair facility and/or other party associated with the repairs. In some embodiments, the server 140 may further facility the repairs by scheduling the repairs at a repair facility, arranging towing of the vehicle to the repair facility, and/or arranging a temporary replacement vehicle for the vehicle operator and/or insurance customer. Once all actions relating to the repair and/or payment have been implemented, the method 1200 may terminate.
- a computer-implemented method for responding to damage to an autonomous or semi-autonomous vehicle relating to a collision or other loss may be provided.
- an indication of damage to the autonomous or semi-autonomous vehicle, and/or operating data regarding operation of the vehicle during (i) a time period without the damage to the autonomous or semi-autonomous vehicle, and (ii) a time period with the damage to the autonomous or semi-autonomous vehicle may be received at a remote server, such as via wireless communication from the customer's vehicle controller or mobile device. Repairs associated with the damage may be determined at the remote server based upon the operating data, as well as an expected cost associated with the repairs.
- Insurance discounts may be provided to risk averse customers that timely repair damaged vehicles or features that impact vehicle safety. For instance, insurance discounts or quote may be generated and transmitted from a remote server or associated transceiver to the customer's vehicle controller/control system or mobile device for their review and/or approval.
- a customer may opt into a rewards or other type of program, and willingly share their vehicle data with an insurance provider.
- risk averse drivers and vehicle owners may receive discounts or insurance cost savings related to auto and other types of insurance from the insurance provider.
- FIG. 13 illustrates a flow diagram depicting an exemplary infrastructure communication method 1300 that may be used to detect and communicate information regarding infrastructure components to vehicles.
- the exemplary method 1300 may begin with the infrastructure communication device 124 receiving information regarding the infrastructure component 126 from one or more sensors at block 1302 .
- the information may be used at block 1304 to determine a message regarding the infrastructure component 126 .
- the message may be augmented at block 1306 by information associated with a sponsor or other party affiliated with the infrastructure communication device 124 .
- the message may then be encoded at block 1308 and transmitted at block 1310 , which may cause the message to be presented to the vehicle operator of the vehicle 108 at block 1312 .
- the exemplary embodiment describes one infrastructure communication device 124 communicating with one vehicle 108 , it should be understood than any number of infrastructure communication devices 124 may communicate with any number of vehicles 108 .
- a computer-implemented method of accident reconstruction or fault determination may be provided.
- the method may include (1) gathering or collecting data from one or more vehicle-mounted sensors and/or one or more autonomous or semi-autonomous functionality or technology systems of a vehicle, via one or more processors (such as a smart vehicle controller and/or insurance provider remote processor or server) in wired or wireless communication with the one or more vehicle-mounted sensors and/or the one or more autonomous or semi-autonomous functionality or technology systems, the data showing operation of the vehicle and/or how the one or more autonomous or semi-autonomous functionality or technology systems performed before, during, and/or after a vehicle accident involving the vehicle, the vehicle being insured by an insurance provider; (2) reconstructing the scene of the vehicle accident and/or a series of events leading up to the vehicle accident, via the one or more processors; (3) determining, via the one or more processors, one or more causes of the vehicle accident (whether human driver error or faulty autonomous or semi-autonomous functionality or technology) based upon the reconstruction of the vehicle accident; (4)
- a computer-implemented method of updating an insurance policy may be provided.
- the method may include (a) gathering or receiving, at or via one or more processors (such as either a local processor associated with a smart vehicle and/or a remote processor or server associated with an insurance provider), data indicative of (1) vehicle usage, and/or (2) vehicle drivers for an insured vehicle; (b) analyzing the data, via the one or more processors, to determine (i) an amount and/or (ii) type of vehicle usage for each vehicle driver; (c) based upon the amount of vehicle usage for each vehicle driver and/or the type of vehicle usage for each vehicle driver, via the one or more processors, updating or adjusting an insurance policy (such as a premium, rate, rewards or points program, discount, etc.) for the insured vehicle; (d) transmitting, under the direction or control of the one or more processors, the updated or adjusted insurance policy (or otherwise causing the updated or adjusted insurance policy to be presented or displayed to the insured) to a mobile device of the insured for their review, modification, and/or
- the amount of vehicle usage may include an amount of time and/or miles that each individual vehicle driver drives the vehicle.
- the type of vehicle usage may include characterizing various periods of driving and/or trips as city driving; country driving; freeway or highway driving city street driving; heavy traffic or congested traffic driving; driving in good weather; driving in hazardous weather; rush hour driving; and/or time-of-day driving.
- the vehicle drivers may be identified from mobile device signature; seat pressure sensors and weight; image recognition techniques performed upon images of the driver; and/or biometric devices (such as heart beat or rate characteristics; voice print; and/or thumb or finger prints).
- a computer-implemented method of updating an insurance policy using biometric device data may include (a) gathering or receiving, at or via one or more processors (such as either a local processor associated with a smart vehicle and/or a remote processor or server associated with an insurance provider), data from a biometric device indicative of whom is driving an insured vehicle; (b) gathering or receiving, at or via the one or more processors, data indicative of vehicle usage for a single trip and/or driving or driver behavior during the single trip; (c) updating or adjusting, at or via the one or more processors, an insurance policy (such as a premium, rate, rewards or points program, discount, etc.) for the insured vehicle based upon (1) whom is driving the insured vehicle (and/or his or her driving profile or score), and/or (2) the data indicative of vehicle usage for the single trip and/or the driving or driver behavior exhibited during the single trip to facilitate more accurate risk assessment and/or cost savings to the insured.
- the method may include additional, fewer, or alternate actions, including those discussed elsewhere
- a computer-implemented method of updating an insurance policy may include (1) gathering or receiving, at or via one or more processors (such as either a local processor associated with a smart vehicle and/or a remote processor or server associated with an insurance provider), data from a biometric device identifying a driver of an insured vehicle; (2) gathering or receiving, at or via the one or more processors, data indicative of driving or driver behavior for the driver identified from the biometric device data; (3) generating, at or via the one or more processors, a usage-based insurance policy for the insured vehicle based upon (i) the identity of the driver determined from the biometric device data, and/or (ii) the data indicative of driving or driver behavior exhibited by the driver to facilitate more accurate risk assessment and/or provide cost savings to the insured.
- the method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
- a computer-implemented method of generating or updating an usage-based insurance policy for an autonomous or semi-autonomous vehicle having multiple drivers may be provided.
- the method may include (1) identifying, via one or more processors (such as a vehicle-mounted local processor or remote insurance provider processor or server), multiple drivers that drive a vehicle, the vehicle having one or more autonomous or semi-autonomous technologies or functionalities; (2) determining, via the one or more processors, a driving behavior for each of the multiple drivers; (3) determining, via the one or more processors, (i) an amount that each autonomous or semi-autonomous technology or functionality is used, and/or (ii) a type of autonomous or semi-autonomous technology or functionality that is employed by each of the multiple drivers; (4) generating or updating, via the one or more processors, an insurance policy (such as a premium, rate, discount, rewards or points program, etc.) for the vehicle based upon (a) the driving behavior for each of the multiple drivers determined, (b) the amount that each autonomous or semi-autonomous
- a computer-implemented method of updating an insurance policy may be provided.
- the method may include (1) gathering or receiving, at or via one or more processors (such as either a local processor associated with a smart vehicle and/or a remote processor or server associated with an insurance provider), data indicative of a software version installed on or in an insured vehicle that is associated with an autonomous or semi-autonomous functionality; (2) determining, at or via the one or more processors, that the software version is out of date or a (safer or less risky) new software version exists and/or is available for download; (3) generating, at or via the one or more processors, a recommendation to an insured to update or upgrade to the new software version, and transmitting that recommendation under the direction or control of the one or more processors to a mobile device or insured vehicle controller (such as via wireless communication or data transmission); (4) determining, at or via the one or more processors, (or receiving an indication) that the insured has updated or upgraded to the new software version associated with the autonomous or semi-autonomous functionality; and/or
- the vehicle 108 may be a fully autonomous vehicle operating without a vehicle operator's input or presence. In other embodiments or under other conditions, the vehicle operator may control the vehicle 108 with or without the assistance of the vehicle's autonomous operation features. For example, the vehicle may be fully autonomous only above a minimum speed threshold or may require the vehicle operator to control the vehicle during periods of heavy precipitation. Alternatively, the autonomous vehicle may perform all relevant control functions using the autonomous operation features under all ordinary operating conditions. In still further embodiments, the vehicle 108 may operate in either a fully or a partially autonomous state, while receiving or transmitting autonomous communications.
- the risk level or premium associated with an insurance policy covering the autonomous vehicle may be determined based upon the risks associated with the autonomous operation features, without reference to risks associated with the vehicle operator.
- the risk level or premium associated with an insurance policy covering the autonomous vehicle may be based upon risks associated with both the autonomous operation features and the vehicle operator performing manual vehicle operation.
- the risk level or premium associated with an insurance policy covering the autonomous vehicle may be determined based in part upon a determination of the expected use of autonomous communication features by external sources in the relevant environment of the vehicle 108 during operation of the vehicle 108 .
- the present embodiments may relate to data acquisition.
- Data may be gathered via devices employing wireless communication technology, such as Bluetooth or other IEEE communication standards.
- a Bluetooth enabled smartphone or mobile device, and/or an in-dash smart and/or communications device may collect data.
- the data associated with the vehicle, and/or vehicle or driver performance, that is gathered or collected at, or on, the vehicle may be wirelessly transmitted to a remote processor or server, such as a remote processor or server associated with an insurance provider.
- the mobile device 110 may receive the data from the on-board computer 114 or the sensors 120 , and may transmit the received data to the server 140 via the network 130 , and the data may be stored in the database 146 .
- the transmitted data may include real-time sensor data, a summary of the sensor data, processed sensor data, operating data, environmental data, communication data, or a log such data.
- Data may be generated by autonomous or semi-autonomous vehicles and/or vehicle mounted sensors (or smart sensors), and then collected by vehicle mounted equipment or processors, including Bluetooth devices, and/or an insurance provider remote processor or server.
- vehicle mounted equipment or processors including Bluetooth devices, and/or an insurance provider remote processor or server.
- the data gathered may be used to analyze vehicle decision making.
- a processor may be configured to generate data on what an autonomous or semi-autonomous vehicle would have done in a given situation had the driver not taken over manual control/driving of the vehicle or alternative control actions not taken by the autonomous or semi-autonomous operation features. This type of control decision data (related to vehicle decision making) may be useful with respect to analyzing hypothetical situations.
- an application may interact with a vehicle to receive and/or retrieve data from autonomous or semi-autonomous processors and sensors.
- the data retrieved may be related to radar, cameras, sensor output, computer instructions or application output.
- Other data related to a smart vehicle controller, car navigation unit information (including route history information and typical routes taken), GPS unit information, odometer and/or speedometer information, and smart equipment data may also be gathered or collected.
- the application and/or other computer instructions may be associated with an insurance provider remote processor or server.
- the control decision data may further include information regarding control decisions generated by one or more autonomous operation features within the vehicle.
- the operating data and control decision data gathered, collected, and/or acquired may facilitate remote evaluation and/or analysis of what the autonomous or semi-autonomous vehicle was “trying to do” (brake, slow, turn, accelerate, etc.) during operation, as well as what the vehicle actually did do.
- the data may reveal decisions, and the appropriateness thereof, made by the artificial intelligence or computer instructions associated with one or more autonomous or semi-autonomous vehicle technologies, functionalities, systems, and/or pieces of equipment.
- the data may include information related to what the vehicle would have done in a situation if the driver had not taken over (beginning manual vehicle control).
- control decisions data may include information regarding control decisions not implemented by the autonomous operation features to control the vehicle. This may occur when an autonomous operation feature generates a control decision or associated control signal, but the control decision or signal is prevented from controlling the vehicle because the autonomous feature or function is disabled, the control decision is overridden by the vehicle operator, the control signal would conflict with another control signal generated by another autonomous operation feature, a more preferred control decision is generated, and/or an error occurs in the on-board computer 114 or the control system of the vehicle.
- a vehicle operator may disable or constrain the operation of some or all autonomous operation features, such as where the vehicle is operated manually or semi-autonomously.
- the disabled or constrained autonomous operation features may, however, continue to receive sensor data and generate control decision data that is not implemented.
- one or more autonomous operation features may generate more than one control decision in a relevant period of time as alternative control decisions.
- Some of these alternative control decisions may not be selected by the autonomous operation feature or an autonomous operation control system to control the vehicle.
- such alternative control decisions may be generated based upon different sets of sensor or communication data from different sensors 120 or include or excluding autonomous communication data.
- the alternative control decisions may be generated faster than they can be implemented by the control system of the vehicle, thus preventing all control decisions from being implemented.
- control decision data In addition to control decision data, other information regarding the vehicle, the vehicle environment, or vehicle operation may be collected, generated, transmitted, received, requested, stored, and/or recorded in connection with the control decision data. Additional operating data including sensor data from the sensors 120 , autonomous communication data from the communication component 122 or the communication unit 220 , location data, environmental data, time data, settings data, configuration data, and/or other relevant data may be associated with the control decision data.
- a database or log may store the control decision data and associated information.
- the entries in such log or database may include a timestamp indicating the date, time, location, vehicle environment, vehicle condition, autonomous operation feature settings, and/or autonomous operation feature configuration information associated with each entry.
- Such data may facilitate evaluating the autonomous or semi-autonomous technology, functionality, system, and/or equipment in hypothetical situations and/or may be used to calculate risk, and in turn adjust insurance policies, premiums, discounts, etc.
- vehicle may refer to any of a number of motorized transportation devices.
- a vehicle may be a car, truck, bus, train, boat, plane, motorcycle, snowmobile, other personal transport devices, etc.
- an “autonomous operation feature” of a vehicle means a hardware or software component or system operating within the vehicle to control an aspect of vehicle operation without direct input from a vehicle operator once the autonomous operation feature is enabled or engaged.
- autonomous vehicle means a vehicle including at least one autonomous operation feature.
- a “fully autonomous vehicle” means a vehicle with one or more autonomous operation features capable of operating the vehicle in the absence of or without operating input from a vehicle operator.
- insurance policy or “vehicle insurance policy,” as used herein, generally refers to a contract between an insurer and an insured. In exchange for payments from the insured, the insurer pays for damages to the insured which are caused by covered perils, acts, or events as specified by the language of the insurance policy. The payments from the insured are generally referred to as “premiums,” and typically are paid by or on behalf of the insured upon purchase of the insurance policy or over time at periodic intervals.
- premiums typically are paid by or on behalf of the insured upon purchase of the insurance policy or over time at periodic intervals.
- insurance policy premiums are typically associated with an insurance policy covering a specified period of time, they may likewise be associated with other measures of a duration of an insurance policy, such as a specified distance traveled or a specified number of trips.
- the amount of the damages payment is generally referred to as a “coverage amount” or a “face amount” of the insurance policy.
- An insurance policy may remain (or have a status or state of) “in-force” while premium payments are made during the term or length of coverage of the policy as indicated in the policy.
- An insurance policy may “lapse” (or have a status or state of “lapsed”), for example, when the parameters of the insurance policy have expired, when premium payments are not being paid, when a cash value of a policy falls below an amount specified in the policy, or if the insured or the insurer cancels the policy.
- insurer insuring party
- insurance provider are used interchangeably herein to generally refer to a party or entity (e.g., a business or other organizational entity) that provides insurance products, e.g., by offering and issuing insurance policies.
- an insurance provider may be an insurance company.
- insured insured party
- polyicyholder policyholder
- customer are used interchangeably herein to refer to a person, party, or entity (e.g., a business or other organizational entity) that is covered by the insurance policy, e.g., whose insured article or entity is covered by the policy.
- a person or customer (or an agent of the person or customer) of an insurance provider fills out an application for an insurance policy.
- the data for an application may be automatically determined or already associated with a potential customer.
- the application may undergo underwriting to assess the eligibility of the party and/or desired insured article or entity to be covered by the insurance policy, and, in some cases, to determine any specific terms or conditions that are to be associated with the insurance policy, e.g., amount of the premium, riders or exclusions, waivers, and the like.
- the insurance policy may be in-force, (i.e., the policyholder is enrolled).
- an insurance provider may offer or provide one or more different types of insurance policies.
- Other types of insurance policies may include, for example, commercial automobile insurance, inland marine and mobile property insurance, ocean marine insurance, boat insurance, motorcycle insurance, farm vehicle insurance, aircraft or aviation insurance, and other types of insurance products.
- autonomous or semi-autonomous vehicle; telematics; interconnected home; mobile device; and/or other data may be collected or received by an insurance provider remote server, such as via direct or indirect wireless communication or data transmission, after a customer affirmatively consents or otherwise opts into an insurance discount, reward, or other program.
- the insurance provider may then analyze the data received with the customer's permission to provide benefits to the customer.
- risk averse customers may receive insurance discounts or other insurance cost savings based upon data that reflects low risk behavior and/or technology that mitigates or prevents risk to (i) insured assets, such as autonomous or semi-autonomous vehicles, and/or (ii) autonomous or semi-autonomous vehicle operators or passengers.
- routines, subroutines, applications, or instructions may constitute either software (code embodied on a non-transitory, tangible machine-readable medium) or hardware.
- routines, etc. are tangible units capable of performing certain operations and may be configured or arranged in a certain manner.
- one or more computer systems e.g., a standalone, client or server computer system
- one or more hardware modules of a computer system e.g., a processor or a group of processors
- software e.g., an application or application portion
- a hardware module may be implemented mechanically or electronically.
- a hardware module may comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC) to perform certain operations.
- a hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. It will be appreciated that the decision to implement a hardware module mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.
- the term “hardware” should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein.
- hardware is temporarily configured (e.g., programmed)
- the hardware need not be configured or instantiated at any one instance in time.
- Software may accordingly configure a processor, for example, to constitute a particular hardware module at one instance of time and to constitute a different hardware module at a different instance of time.
- Hardware elements can provide information to, and receive information from, other hardware elements. Accordingly, the described hardware may be regarded as being communicatively coupled.
- processors may be temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented modules that operate to perform one or more operations or functions.
- the modules referred to herein may, in some example embodiments, comprise processor-implemented modules.
- the methods or routines described herein may be at least partially processor-implemented.
- the performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but deployed across a number of machines.
- the processor or processors may be located in a single location (e.g., within a home environment, an office environment or as a server farm), while in other embodiments the processors may be distributed across a number of locations.
- Coupled and “connected” along with their derivatives.
- some embodiments may be described using the term “coupled” to indicate that two or more elements are in direct physical or electrical contact.
- the term “coupled,” however, may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other.
- the embodiments are not limited in this context.
- the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having” or any other variation thereof, are intended to cover a non-exclusive inclusion.
- a process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
- “or” refers to an inclusive or and not to an exclusive or.
- use of the “a” or “an” are employed to describe elements and components of the embodiments herein. This is done merely for convenience and to give a general sense of the description.
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Automation & Control Theory (AREA)
- Business, Economics & Management (AREA)
- Health & Medical Sciences (AREA)
- General Physics & Mathematics (AREA)
- Transportation (AREA)
- Mechanical Engineering (AREA)
- Finance (AREA)
- Accounting & Taxation (AREA)
- Life Sciences & Earth Sciences (AREA)
- Strategic Management (AREA)
- Development Economics (AREA)
- Theoretical Computer Science (AREA)
- Remote Sensing (AREA)
- Radar, Positioning & Navigation (AREA)
- Human Computer Interaction (AREA)
- Economics (AREA)
- General Business, Economics & Management (AREA)
- Marketing (AREA)
- Neurology (AREA)
- Entrepreneurship & Innovation (AREA)
- Medical Informatics (AREA)
- Aviation & Aerospace Engineering (AREA)
- Game Theory and Decision Science (AREA)
- Heart & Thoracic Surgery (AREA)
- Molecular Biology (AREA)
- Biophysics (AREA)
- Pathology (AREA)
- Biomedical Technology (AREA)
- Veterinary Medicine (AREA)
- Public Health (AREA)
- General Health & Medical Sciences (AREA)
- Animal Behavior & Ethology (AREA)
- Surgery (AREA)
- Chemical & Material Sciences (AREA)
- Combustion & Propulsion (AREA)
- Physiology (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
Abstract
Methods and systems for monitoring use, determining risk, and pricing insurance policies for a vehicle having one or more autonomous or semi-autonomous operation features are provided. According to certain aspects, a computer-implemented method for responding to damage to an autonomous or semi-autonomous vehicle relating to a collision or other loss may be provided. With the customer's permission, an indication of damage to the autonomous or semi-autonomous vehicle, and/or operating data regarding operation of the vehicle during (i) a time period without the damage to the autonomous or semi-autonomous vehicle, and (ii) a time period with the damage to the autonomous or semi-autonomous vehicle may be received. Repairs associated with the damage may be determined based upon the operating data, as well as an expected cost associated with the repairs. Insurance discounts may be provided to risk averse customers that timely repair damaged vehicles or features that impact vehicle safety.
Description
- This application claims the benefit of U.S. Provisional Application No. 62/079,533 (filed Nov. 13, 2014); U.S. Provisional Application No. 62/103,831 (filed Jan. 15, 2015); U.S. Provisional Application No. 62/103,836 (filed Jan. 15, 2015); U.S. Provisional Application No. 62/103,838 (filed Jan. 15, 2015); U.S. Provisional Application No. 62/103,840 (filed Jan. 15, 2015); U.S. Provisional Application No. 62/103,855 (filed Jan. 15, 2015); U.S. Provisional Application No. 62/103,856 (filed Jan. 15, 2015); U.S. Provisional Application No. 62/103,891 (filed Jan. 15, 2015); U.S. Provisional Application No. 62/103,893 (filed Jan. 15, 2015); U.S. Provisional Application No. 62/103,895 (filed Jan. 15, 2015); U.S. Provisional Application No. 62/103,907 (filed Jan. 15, 2015); U.S. Provisional Application No. 62/103,911 (filed Jan. 15, 2015); and U.S. Provisional Application No. 62/103,914 (filed Jan. 15, 2015). The entirety of each of the foregoing provisional applications is incorporated by reference herein.
- Additionally, the present application is related to co-pending U.S. patent application Ser. No. 14/934,326 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,333 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/931,339 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,343 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,345 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,347 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,352 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,355 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,361 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,371 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,381 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,385 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,388 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,393 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,400 (filed Nov. 6, 2015); and co-pending U.S. patent application Ser. No. 14/934,405 (filed Nov. 6, 2015).
- The present disclosure generally relates to systems and methods for operating, monitoring, assessing, or insuring autonomous or semi-autonomous vehicles.
- Vehicles are typically operated by a human vehicle operator who controls both steering and motive controls. Operator error, inattention, inexperience, misuse, or distraction leads to many vehicle accidents each year, resulting in injury and damage. Autonomous or semi-autonomous vehicles augment vehicle operators' information or replace vehicle operators' control commands to operate the vehicle in whole or part with computer systems based upon information from sensors within the vehicle.
- Vehicle or automobile insurance exists to provide financial protection against physical damage and/or bodily injury resulting from traffic accidents and against liability that could arise therefrom. Typically, a customer purchases a vehicle insurance policy for a policy rate having a specified term. In exchange for payments from the insured customer, the insurer pays for damages to the insured which are caused by covered perils, acts, or events as specified by the language of the insurance policy. The payments from the insured are generally referred to as “premiums,” and typically are paid on behalf of the insured over time at periodic intervals. An insurance policy may remain “in-force” while premium payments are made during the term or length of coverage of the policy as indicated in the policy. An insurance policy may “lapse” (or have a status or state of “lapsed”), for example, when premium payments are not being paid or if the insured or the insurer cancels the policy.
- Premiums may be typically determined based upon a selected level of insurance coverage, location of vehicle operation, vehicle model, and characteristics or demographics of the vehicle operator. The characteristics of a vehicle operator that affect premiums may include age, years operating vehicles of the same class, prior incidents involving vehicle operation, and losses reported by the vehicle operator to the insurer or a previous insurer. Past and current premium determination methods do not, however, account for use of autonomous vehicle operating features. The present embodiments may, inter alia, alleviate this and/or other drawbacks associated with conventional techniques.
- The present embodiments may be related to autonomous or semi-autonomous vehicle functionality, including driverless operation, accident avoidance, or collision warning systems. These autonomous vehicle operation features may either assist the vehicle operator to more safely or efficiently operate a vehicle or may take full control of vehicle operation under some or all circumstances. The present embodiments may also facilitate risk assessment and premium determination for vehicle insurance policies covering vehicles with autonomous operation features. For instance, a consumer may opt-in to a rewards program that rewards them, such as in the form of insurance discounts, for affirmatively sharing data related to their vehicles and/or autonomous features with an insurance provider.
- In accordance with the described embodiments, the disclosure herein generally addresses systems and methods for responding to damage to an autonomous or semi-autonomous vehicle relating to a collision or other loss. A computer (such as an on-board computer, mobile device, or server communicatively connected to the vehicle) associated with the vehicle may (1) receive an indication of damage to the autonomous or semi-autonomous vehicle; (2) receive operating data regarding operation of the vehicle during (i) a time period without the damage to the autonomous or semi-autonomous vehicle and (ii) a time period with the damage to the autonomous or semi-autonomous vehicle; (3) determine one or more repairs associated with the damage based upon the operating data; and/or (4) determine an expected cost associated with the one or more repairs. The operating data may include information from one or more sensors disposed within the autonomous or semi-autonomous vehicle and/or information regarding the operation of one or more autonomous operation features of the autonomous or semi-autonomous vehicle. The one or more repairs associated with the damage may be determined at least in part based upon a specialty repair service, in which case the expected cost may further include a cost associated with the specialty repair service.
- In some embodiments, the expected cost may be determined based upon information regarding actual costs of repairs to a plurality of other vehicles. Additionally, or alternatively, determining the expected cost may include determining a range of expected costs associated with the one or more repairs. The computer may further determine a plurality of expected costs within the determined range and cause the plurality of expected costs to be presented to an insurance customer associated with the vehicle. A maximum payment for the one or more repairs associated with the damage may also be determined based upon the determined range of expected costs and/or presented to an insurance customer associated with the vehicle.
- In further embodiments, the computer may cause the expected cost associated with the one or more repairs to be presented to an insurance customer associated with the vehicle, along with a plurality of options regarding the one or more repairs. Once the cost and options have been presented, the computer may receive a selection by the insurance customer of one or more of the presented plurality of options. Based upon the selection, the computer may cause a payment to be made to one or more of the following: the insurance customer, a beneficiary of an insurance policy associated with the insurance customer, and/or a repair facility. The plurality of options may include one or more options to have the one or more repairs performed at one or more repair facilities. The one or more options may further include one or more cost estimates based upon the operating data. The one or more options to have the one or more repairs performed at one or more repair facilities may include one or more estimates of time required for the one or more repairs.
- In each of the embodiments or aspects described above, the methods may be provided in corresponding computer systems including at least one or more processors and a non-transitory program memory coupled to the one or more processors and storing executable instructions. The computer systems may further include or be communicatively connected to one or more sensors, communication components or devices, or other equipment as described herein. In yet another aspect, a tangible, non-transitory computer-readable medium storing instructions corresponding to each of the embodiments or aspects described above may be provided. Each of the methods or executable instructions of the computer systems or computer-readable media may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
- Advantages will become more apparent to those skilled in the art from the following description of the preferred embodiments which have been shown and described by way of illustration. As will be realized, the present embodiments may be capable of other and different embodiments, and their details are capable of modification in various respects. Accordingly, the drawings and description are to be regarded as illustrative in nature and not as restrictive.
- The figures described below depict various aspects of the applications, methods, and systems disclosed herein. It should be understood that each figure depicts an embodiment of a particular aspect of the disclosed applications, systems and methods, and that each of the figures is intended to accord with a possible embodiment thereof. Furthermore, wherever possible, the following description refers to the reference numerals included in the following figures, in which features depicted in multiple figures are designated with consistent reference numerals.
-
FIG. 1 illustrates a block diagram of an exemplary computer network, a computer server, a mobile device, and an on-board computer for implementing autonomous vehicle operation, monitoring, evaluation, and insurance processes in accordance with the described embodiments; -
FIG. 2 illustrates a block diagram of an exemplary on-board computer or mobile device; -
FIG. 3 illustrates a flow diagram of an exemplary autonomous vehicle operation method in accordance with the presently described embodiments; -
FIG. 4 illustrates a flow diagram of an exemplary monitoring method during vehicle operation in accordance with the presently described embodiments; -
FIG. 5 illustrates a flow diagram of an exemplary operating status assessment method in accordance with the presently described embodiments; -
FIG. 6 illustrates a flow diagram of an exemplary operating status monitoring method in accordance with the presently described embodiments; -
FIGS. 7A-B illustrate flow diagrams depicting exemplary vehicle operation hand-off methods in accordance with the presently described embodiments; -
FIG. 8 illustrates a flow diagram depicting an exemplary vehicle operator identification method in accordance with the presently described embodiments; -
FIG. 9 illustrates a flow diagram depicting an exemplary vehicle operator use monitoring and evaluation method in accordance with the presently described embodiments; -
FIG. 10 illustrates a flow diagram depicting an exemplary cost comparison method in accordance with the presently described embodiments; and -
FIG. 11 illustrates a flow diagram depicting an exemplary autonomous operation feature update method in accordance with the presently described embodiments; -
FIG. 12 illustrates a flow diagram depicting an exemplary autonomous vehicle repair method in accordance with the presently described embodiments; and -
FIG. 13 illustrates a flow diagram depicting an exemplary infrastructure communication method in accordance with the presently described embodiments. - The systems and methods disclosed herein generally relate to evaluating, monitoring, and managing risks related to the operation of autonomous or semi-autonomous vehicles having autonomous (or semi-autonomous) operation features. The systems and methods further relate to pricing and processing vehicle insurance policies for autonomous or semi-autonomous vehicles. The autonomous operation features may take full control of the vehicle under certain conditions, viz. fully autonomous operation, or the autonomous operation features may assist the vehicle operator in operating the vehicle, viz. partially autonomous operation. Fully autonomous operation features may include systems within the vehicle that pilot the vehicle to a destination with or without a vehicle operator present (e.g., an operating system for a driverless car). Partially autonomous operation features may assist the vehicle operator in limited ways (e.g., automatic braking or collision avoidance systems).
- The type and quality of the autonomous operation features may affect the risks related to operating a vehicle, both individually and/or in combination. In addition, configurations and settings of the autonomous operation features may further impact the risks. To account for the effects on such risks, some embodiments evaluate the quality of each autonomous operation feature and/or combination of features. Additional embodiments evaluate the risks associated with the vehicle operator interacting with the autonomous operation features. Further embodiments address the relative risks associated with control of some aspects of vehicle control by the autonomous operation features or by the vehicle operator. Still further embodiments address use of information received or generated by the autonomous operation features to manage risk and/or damage.
- Some autonomous operation features may be adapted for use under particular conditions, such as city driving or highway driving. Additionally, the vehicle operator may be able to configure settings relating to the features or may enable or disable the features individually or in groups. For example, the vehicle operator may select a mode of operation for the autonomous or semi-autonomous vehicle, which may adjust settings for one or more autonomous operation features. Therefore, some embodiments monitor use of the autonomous operation features, which may include the settings or levels of feature use during vehicle operation, as well as the selection of features or settings of the autonomous operation features chosen by the vehicle operator.
- Information obtained by monitoring feature usage may be used to determine risk levels associated with vehicle operation, either generally or in relation to a vehicle operator. In such situations, total risk may be determined by a weighted combination of the risk levels associated with operation while autonomous operation features are enabled (with relevant settings) and the risk levels associated with operation while autonomous operation features are disabled. For fully autonomous vehicles, settings or configurations relating to vehicle operation may be monitored and used in determining vehicle operating risk.
- In addition to use in controlling the vehicle, information regarding the risks associated with vehicle operation with and without the autonomous operation features may then be used to determine risk categories or premiums for a vehicle insurance policy covering a vehicle with autonomous operation features. Risk category or price may be determined based upon factors relating to the evaluated effectiveness of the autonomous vehicle features. The risk or price determination may also include traditional factors, such as location, vehicle type, and level of vehicle use. For fully autonomous vehicles, factors relating to vehicle operators may be excluded entirely. For partially autonomous vehicles, factors relating to vehicle operators may be reduced in proportion to the evaluated effectiveness and monitored usage levels of the autonomous operation features. For vehicles with autonomous communication features that obtain information from external sources (e.g., other vehicles or infrastructure), the risk level and/or price determination may also include an assessment of the availability of external sources of information. Location and/or timing of vehicle use may thus be monitored and/or weighted to determine the risk associated with operation of the vehicle.
- The present embodiments may relate to assessing and pricing insurance based upon autonomous (or semi-autonomous) functionality of a vehicle, utilization of the autonomous (or semi-autonomous) functionality of the vehicle, and/or operation of the vehicle by a human operator. In some embodiments, the vehicle operator may not control the operations of the vehicle directly, in which case the assessment, rating, and pricing of insurance may exclude consideration of the vehicle operator. A smart vehicle may maneuver itself without human intervention and/or include sensors, processors, computer instructions, and/or other components that may perform or direct certain actions conventionally performed by a human operator.
- An analysis of how artificial intelligence facilitates avoiding accidents and/or mitigates the severity of accidents may be used to build a database and/or model of risk assessment. After which, automobile insurance risk and/or premiums (as well as insurance discounts, rewards, and/or points) may be adjusted based upon autonomous or semi-autonomous vehicle functionality, such as by groups of autonomous or semi-autonomous functionality or individual features. In one aspect, an evaluation may be performed on how artificial intelligence, and the usage thereof, impacts automobile accidents and/or automobile insurance claims.
- The types of autonomous or semi-autonomous vehicle-related functionality or technology that may be used with the present embodiments to replace human driver actions may include and/or be related to the following types of functionality: (a) fully autonomous (driverless); (b) limited driver control; (c) vehicle-to-vehicle (V2V) wireless communication; (d) vehicle-to-infrastructure (and/or vice versa) wireless communication; (e) automatic or semi-automatic steering; (f) automatic or semi-automatic acceleration; (g) automatic or semi-automatic braking; (h) automatic or semi-automatic blind spot monitoring; (i) automatic or semi-automatic collision warning; (j) adaptive cruise control; (k) automatic or semi-automatic parking/parking assistance; (l) automatic or semi-automatic collision preparation (windows roll up, seat adjusts upright, brakes pre-charge, etc.); (m) driver acuity/alertness monitoring; (n) pedestrian detection; (o) autonomous or semi-autonomous backup systems; (p) road mapping systems; (q) software security and anti-hacking measures; (r) theft prevention/automatic return; (s) automatic or semi-automatic driving without occupants; and/or other functionality. Additionally or alternatively, the autonomous or semi-autonomous functionality or technology may include and/or may be related to: (t) driver alertness or responsive monitoring; (u) pedestrian detection; (v) artificial intelligence and/or back-up systems; (w) navigation or GPS-related systems; (x) security and/or anti-hacking measures; and/or (y) theft prevention systems.
- The adjustments to automobile insurance rates or premiums based upon the autonomous or semi-autonomous vehicle-related functionality or technology may take into account the impact of such functionality or technology on the likelihood of a vehicle accident or collision occurring. For instance, a processor may analyze historical accident information and/or test data involving vehicles having autonomous or semi-autonomous functionality. Factors that may be analyzed and/or accounted for that are related to insurance risk, accident information, or test data may include (1) point of impact; (2) type of road; (3) time of day; (4) weather conditions; (5) road construction; (6) type/length of trip; (7) vehicle style; (8) level of pedestrian traffic; (9) level of vehicle congestion; (10) atypical situations (such as manual traffic signaling); (11) availability of internet connection for the vehicle; and/or other factors. These types of factors may also be weighted according to historical accident information, predicted accidents, vehicle trends, test data, and/or other considerations.
- In one aspect, the benefit of one or more autonomous or semi-autonomous functionalities or capabilities may be determined, weighted, and/or otherwise characterized. For instance, the benefit of certain autonomous or semi-autonomous functionality may be substantially greater in city or congested traffic, as compared to open road or country driving traffic. Additionally or alternatively, certain autonomous or semi-autonomous functionality may only work effectively below a certain speed, e.g., during city driving or driving in congestion. Other autonomous or semi-autonomous functionality may operate more effectively on the highway and away from city traffic, such as cruise control. Further individual autonomous or semi-autonomous functionality may be impacted by weather, such as rain or snow, and/or time of day (day light versus night). As an example, fully automatic or semi-automatic lane detection warnings may be impacted by rain, snow, ice, and/or the amount of sunlight (all of which may impact the imaging or visibility of lane markings painted onto a road surface, and/or road markers or street signs).
- Automobile insurance premiums, rates, discounts, rewards, refunds, points, or other costs may be adjusted based upon the percentage of time or vehicle usage that the vehicle is the driver, i.e., the amount of time a specific driver uses each type of autonomous (or even semi-autonomous) vehicle functionality. Such premiums, rates, discounts, rewards, refunds, points, or other costs may further be adjusted based upon the extent of use of the autonomous operation features, including settings or modes impacting the operation of the autonomous operation features. Moreover, information regarding the vehicle environment during use (e.g., weather, traffic, time of day, etc.) may be included in insurance adjustment determinations, as may traditional information regarding one or more vehicle operators (and the extent to which each vehicle operator uses the vehicle).
- Such usage information for a particular vehicle may be gathered over time and/or via remote wireless communication with the vehicle. One embodiment may involve a processor on the vehicle, such as within a vehicle control system or dashboard, monitoring in real-time the vehicle operator and/or the use of autonomous operation features while the vehicle is operating. Other types of monitoring may be remotely performed, such as via wireless communication between the vehicle and a remote server, or wireless communication between a vehicle-mounted dedicated device (that is configured to gather autonomous or semi-autonomous functionality usage information) and a remote server.
- Additionally, in some embodiments, the vehicle may transmit and/or receive communications to or from external sources, such as other vehicles (V2V), infrastructure (e.g., a bridge, traffic light, railroad crossing, toll both, marker, sign, or other equipment along the side of a road or highway), pedestrians, databases, or other information sources external to the vehicle. Such communication may allow the vehicle to obtain information regarding other vehicles, obstacles, road conditions, or environmental conditions that could not be detected by sensors disposed within the vehicle. For example, V2V communication may allow a vehicle to identify other vehicles approaching an intersection even when the direct line between the vehicle and the other vehicles is obscured by buildings. As another example, the V2V wireless communication from a first vehicle to a second vehicle (following the first vehicle) may indicate that the first vehicle is braking, which may include the degree to which the vehicle is braking. In response, the second vehicle may automatically or autonomously brake in advance of detecting the deceleration of the first vehicle based upon sensor data.
- Insurance premiums, rates, ratings, discounts, rewards, special offers, points, programs, refunds, claims, claim amounts, or other costs associated with an insurance policy may be adjusted for, or may otherwise take into account, the foregoing functionality and/or the other functionality described herein. For instance, insurance policies may be updated based upon installed autonomous operation features, the extent of use of the autonomous operation features, V2V wireless communication, and/or vehicle-to-infrastructure or infrastructure-to-vehicle wireless communication. The present embodiments may assess and price insurance risks at least in part based upon autonomous operation features that replace some actions of the vehicle operator in controlling the vehicle, including settings and operating status of the autonomous operation features.
-
FIG. 1 illustrates a block diagram of an exemplary autonomousvehicle insurance system 100 on which the exemplary methods described herein may be implemented. The high-level architecture includes both hardware and software applications, as well as various data communications channels for communicating data between the various hardware and software components. The autonomousvehicle insurance system 100 may be roughly divided into front-end components 102 and back-end components 104. The front-end components 102 may obtain information regarding a vehicle 108 (e.g., a car, truck, motorcycle, etc.) and the surrounding environment. An on-board computer 114 may utilize this information to operate thevehicle 108 according to an autonomous operation feature or to assist the vehicle operator in operating thevehicle 108. To monitor thevehicle 108, the front-end components 102 may include one ormore sensors 120 installed within thevehicle 108 that may communicate with the on-board computer 114. The front-end components 102 may further process the sensor data using the on-board computer 114 or a mobile device 110 (e.g., a smart phone, a tablet computer, a special purpose computing device, etc.) to determine when the vehicle is in operation and information regarding the vehicle. In some embodiments of thesystem 100, the front-end components 102 may communicate with the back-end components 104 via anetwork 130. Either the on-board computer 114 or themobile device 110 may communicate with the back-end components 104 via thenetwork 130 to allow the back-end components 104 to record information regarding vehicle usage. The back-end components 104 may use one ormore servers 140 to receive data from the front-end components 102, determine use and effectiveness of autonomous operation features, determine risk levels or premium price, and/or facilitate purchase or renewal of an autonomous vehicle insurance policy. - The front-
end components 102 may be disposed within or communicatively connected to one or more on-board computers 114, which may be permanently or removably installed in thevehicle 108. The on-board computer 114 may interface with the one ormore sensors 120 within the vehicle 108 (e.g., an ignition sensor, an odometer, a system clock, a speedometer, a tachometer, an accelerometer, a gyroscope, a compass, a geolocation unit, a camera, a distance sensor, etc.), which sensors may also be incorporated within or connected to the on-board computer 114. The front-end components 102 may further include acommunication component 122 to transmit information to and receive information from external sources, including other vehicles, infrastructure, or the back-end components 104. In some embodiments, themobile device 110 may supplement the functions performed by the on-board computer 114 described herein by, for example, sending or receiving information to and from themobile server 140 via thenetwork 130. In other embodiments, the on-board computer 114 may perform all of the functions of themobile device 110 described herein, in which case nomobile device 110 may be present in thesystem 100. Either or both of themobile device 110 or on-board computer 114 may communicate with thenetwork 130 overlinks mobile device 110 and on-board computer 114 may communicate with one another directly overlink 116. - The
mobile device 110 may be either a general-use personal computer, cellular phone, smart phone, tablet computer, phablet, wearable electronics, PDA (personal digital assistant), smart glasses, smart watches, smart bracelet, pager, computing device configured for wired or wireless RF (radio frequency) communication, a dedicated vehicle use monitoring device, and/or other mobile computing device. Although only onemobile device 110 is illustrated, it should be understood that a plurality ofmobile devices 110 may be used in some embodiments. The on-board computer 114 may be a general-use on-board computer capable of performing many functions relating to vehicle operation or a dedicated computer for autonomous vehicle operation. Further, the on-board computer 114 may be installed by the manufacturer of thevehicle 108 or as an aftermarket modification or addition to thevehicle 108. In some embodiments or under certain conditions, themobile device 110 or on-board computer 114 may function as thin-client devices that outsource some or most of the processing to theserver 140. - The
sensors 120 may be removably or fixedly installed within thevehicle 108 and may be disposed in various arrangements to provide information to the autonomous operation features. Among thesensors 120 may be included one or more of a GPS (Global Positioning System) unit, other satellite-based navigation unit, a radar unit, a LIDAR (Light Detection and Ranging) unit, an ultrasonic sensor, an infrared sensor, a camera, an accelerometer, a tachometer, and/or a speedometer. Some of the sensors 120 (e.g., radar, LIDAR, or camera units) may actively or passively scan the vehicle environment for obstacles (e.g., other vehicles, buildings, pedestrians, etc.), lane markings, or signs or signals. Other sensors 120 (e.g., GPS, accelerometer, or tachometer units) may provide data for determining the location or movement of thevehicle 108.Other sensors 120 may be directed to the interior or passenger compartment of thevehicle 108, such as cameras, microphones, pressure sensors, thermometers, or similar sensors to monitor the vehicle operator and/or passengers within thevehicle 108. Information generated or received by thesensors 120 may be communicated to the on-board computer 114 or themobile device 110 for use in autonomous vehicle operation. - In some embodiments, the
communication component 122 may receive information from external sources, such as other vehicles or infrastructure. Thecommunication component 122 may also send information regarding thevehicle 108 to external sources. To send and receive information, thecommunication component 122 may include a transmitter and a receiver designed to operate according to predetermined specifications, such as the dedicated short-range communication (DSRC) channel, wireless telephony, Wi-Fi, or other existing or later-developed communications protocols. The received information may supplement the data received from thesensors 120 to implement the autonomous operation features. For example, thecommunication component 122 may receive information that an autonomous vehicle ahead of thevehicle 108 is reducing speed, allowing the adjustments in the autonomous operation of thevehicle 108. - In further embodiments, the front-end components may include an
infrastructure communication device 124 for monitoring the status of one ormore infrastructure components 126. Theinfrastructure communication device 124 may include or be communicatively connected to one or more sensors (not shown) for detecting information relating to the condition of theinfrastructure component 126. The sensors (not shown) may generate data relating to weather conditions, traffic conditions, or operating status of theinfrastructure component 126. Theinfrastructure communication device 124 may be configured to receive the sensor data generated and determine a condition of theinfrastructure component 126, such as weather conditions, road integrity, construction, traffic, available parking spaces, etc. Theinfrastructure communication device 124 may further be configured to communicate information tovehicles 108 via thecommunication component 122. In some embodiments, theinfrastructure communication device 124 may receive information from thevehicles 108, while, in other embodiments, theinfrastructure communication device 124 may only transmit information to thevehicles 108. - In addition to receiving information from the
sensors 120, the on-board computer 114 may directly or indirectly control the operation of thevehicle 108 according to various autonomous operation features. The autonomous operation features may include software applications or routines implemented by the on-board computer 114 to control the steering, braking, or throttle of thevehicle 108. To facilitate such control, the on-board computer 114 may be communicatively connected to the controls or components of thevehicle 108 by various electrical or electromechanical control components (not shown). In embodiments involving fully autonomous vehicles, thevehicle 108 may be operable only through such control components (not shown). In other embodiments, the control components may be disposed within or supplement other vehicle operator control components (not shown), such as steering wheels, accelerator or brake pedals, or ignition switches. - In some embodiments, the front-
end components 102 may communicate with the back-end components 104 via thenetwork 130. Thenetwork 130 may be a proprietary network, a secure public internet, a virtual private network or some other type of network, such as dedicated access lines, plain ordinary telephone lines, satellite links, cellular data networks, combinations of these. Where thenetwork 130 comprises the Internet, data communications may take place over thenetwork 130 via an Internet communication protocol. - The back-
end components 104 may include one ormore servers 140. Eachserver 140 may include one or more computer processors adapted and configured to execute various software applications and components of the autonomousvehicle insurance system 100, in addition to other software applications. Theserver 140 may further include adatabase 146, which may be adapted to store data related to the operation of thevehicle 108 and its autonomous operation features. Such data might include, for example, dates and times of vehicle use, duration of vehicle use, use and settings of autonomous operation features, speed of thevehicle 108, RPM or other tachometer readings of thevehicle 108, lateral and longitudinal acceleration of thevehicle 108, incidents or near collisions of thevehicle 108, communication between the autonomous operation features and external sources, environmental conditions of vehicle operation (e.g., weather, traffic, road condition, etc.), errors or failures of autonomous operation features, or other data relating to use of thevehicle 108 and the autonomous operation features, which may be uploaded to theserver 140 via thenetwork 130. Theserver 140 may access data stored in thedatabase 146 when executing various functions and tasks associated with the evaluating feature effectiveness or assessing risk relating to an autonomous vehicle. - Although the autonomous
vehicle insurance system 100 is shown to include onevehicle 108, onemobile device 110, one on-board computer 114, and oneserver 140, it should be understood that different numbers ofvehicles 108,mobile devices 110, on-board computers 114, and/orservers 140 may be utilized. For example, thesystem 100 may include a plurality ofservers 140 and hundreds ofmobile devices 110 or on-board computers 114, all of which may be interconnected via thenetwork 130. Furthermore, the database storage or processing performed by the one ormore servers 140 may be distributed among a plurality ofservers 140 in an arrangement known as “cloud computing.” This configuration may provide various advantages, such as enabling near real-time uploads and downloads of information as well as periodic uploads and downloads of information. This may in turn support a thin-client embodiment of themobile device 110 or on-board computer 114 discussed herein. - The
server 140 may have acontroller 155 that is operatively connected to thedatabase 146 via alink 156. It should be noted that, while not shown, additional databases may be linked to thecontroller 155 in a known manner. For example, separate databases may be used for autonomous operation feature information, vehicle insurance policy information, and vehicle use information. Thecontroller 155 may include aprogram memory 160, a processor 162 (which may be called a microcontroller or a microprocessor), a random-access memory (RAM) 164, and an input/output (I/O)circuit 166, all of which may be interconnected via an address/data bus 165. It should be appreciated that although only onemicroprocessor 162 is shown, thecontroller 155 may includemultiple microprocessors 162. Similarly, the memory of thecontroller 155 may includemultiple RAMs 164 andmultiple program memories 160. Although the I/O circuit 166 is shown as a single block, it should be appreciated that the I/O circuit 166 may include a number of different types of I/O circuits. TheRAM 164 andprogram memories 160 may be implemented as semiconductor memories, magnetically readable memories, or optically readable memories, for example. Thecontroller 155 may also be operatively connected to thenetwork 130 via alink 135. - The
server 140 may further include a number of software applications stored in aprogram memory 160. The various software applications on theserver 140 may include an autonomous operationinformation monitoring application 141 for receiving information regarding thevehicle 108 and its autonomous operation features, afeature evaluation application 142 for determining the effectiveness of autonomous operation features under various conditions, acompatibility evaluation application 143 for determining the effectiveness of combinations of autonomous operation features, arisk assessment application 144 for determining a risk category associated with an insurance policy covering an autonomous vehicle, and an autonomous vehicle insurancepolicy purchase application 145 for offering and facilitating purchase or renewal of an insurance policy covering an autonomous vehicle. The various software applications may be executed on the same computer processor or on different computer processors. - The various software applications may include various software routines stored in the
program memory 160 to implement various modules using theprocess 162. Additionally, or alternatively, the software applications or routines may interact with various hardware modules that may be installed within or connected to theserver 140. Such modules may implement part of all of the various exemplary methods discussed herein or other related embodiments. Such modules may include a vehicle control module for determining and implementing control decisions to operate thevehicle 108, a system status module for determining the operating status of autonomous operation features, a monitoring module for monitoring the operation of thevehicle 108, a remediation module for correcting abnormal operating states of autonomous operation features, an insurance module for determining risks and costs associated with operation of thevehicle 108, an alert module for generating and presenting alerts regarding thevehicle 108 or the vehicle operator, a risk assessment module for determining risks associated with operation of thevehicle 108 by the autonomous operation features or by the vehicle operator, an identification module for identifying or verifying the identity of the vehicle operator, an information module for obtaining information regarding a vehicle operator orvehicle 108, a use cost module for determining costs associated with operation of thevehicle 108, a comparison module for comparing one or more costs associated with owning or operating thevehicle 108, an update module for updating an autonomous operation feature of thevehicle 108, or other modules. - Exemplary Mobile Device or on-Board Computer
-
FIG. 2 illustrates a block diagram of an exemplarymobile device 110 and/or an exemplary on-board computer 114 consistent with thesystem 100. Themobile device 110 and/or on-board computer 114 may include adisplay 202, aGPS unit 206, acommunication unit 220, anaccelerometer 224, one or more additional sensors (not shown), a user-input device (not shown), and/or, like theserver 140, acontroller 204. In some embodiments, themobile device 110 and on-board computer 114 may be integrated into a single device, or either may perform the functions of both. The on-board computer 114 (or mobile device 110) may interface with thesensors 120 to receive information regarding thevehicle 108 and its environment, which information may be used by the autonomous operation features to operate thevehicle 108. - Similar to the
controller 155, thecontroller 204 may include aprogram memory 208, one or more microcontrollers or microprocessors (MP) 210, aRAM 212, and an I/O circuit 216, all of which are interconnected via an address/data bus 214. Theprogram memory 208 may include anoperating system 226, adata storage 228, a plurality ofsoftware applications 230, and/or a plurality ofsoftware routines 240. Theoperating system 226, for example, may include one of a plurality of general purpose or mobile platforms, such as the Android™, iOS®, or Windows® systems, developed by Google Inc., Apple Inc., and Microsoft Corporation, respectively. Alternatively, theoperating system 226 may be a custom operating system designed for autonomous vehicle operation using the on-board computer 114. Thedata storage 228 may include data such as user profiles and preferences, application data for the plurality ofapplications 230, routine data for the plurality ofroutines 240, and other data related to the autonomous operation features. In some embodiments, thecontroller 204 may also include, or otherwise be communicatively connected to, other data storage mechanisms (e.g., one or more hard disk drives, optical storage drives, solid state storage devices, etc.) that reside within thevehicle 108. - As discussed with reference to the
controller 155, it should be appreciated that althoughFIG. 2 depicts only onemicroprocessor 210, thecontroller 204 may includemultiple microprocessors 210. Similarly, the memory of thecontroller 204 may includemultiple RAMs 212 andmultiple program memories 208. AlthoughFIG. 2 depicts the I/O circuit 216 as a single block, the I/O circuit 216 may include a number of different types of I/O circuits. Thecontroller 204 may implement theRAMs 212 and theprogram memories 208 as semiconductor memories, magnetically readable memories, or optically readable memories, for example. - The one or
more processors 210 may be adapted and configured to execute any of one or more of the plurality ofsoftware applications 230 or any one or more of the plurality ofsoftware routines 240 residing in theprogram memory 204, in addition to other software applications. One of the plurality ofapplications 230 may be an autonomousvehicle operation application 232 that may be implemented as a series of machine-readable instructions for performing the various tasks associated with implementing one or more of the autonomous operation features according to the autonomousvehicle operation method 300. Another of the plurality ofapplications 230 may be anautonomous communication application 234 that may be implemented as a series of machine-readable instructions for transmitting and receiving autonomous operation information to or from external sources via thecommunication unit 220. Still another application of the plurality ofapplications 230 may include an autonomousoperation monitoring application 236 that may be implemented as a series of machine-readable instructions for sending information regarding autonomous operation of the vehicle to theserver 140 via thenetwork 130. - The plurality of
software applications 230 may call various of the plurality ofsoftware routines 240 to perform functions relating to autonomous vehicle operation, monitoring, or communication. In some embodiments, the plurality of software routines may further assess risk levels or determine insurance policy costs and adjustments. One of the plurality ofsoftware routines 240 may be aconfiguration routine 242 to receive settings from the vehicle operator to configure the operating parameters of an autonomous operation feature. Another of the plurality ofsoftware routines 240 may be asensor control routine 244 to transmit instructions to asensor 120 and receive data from thesensor 120. Still another of the plurality ofsoftware routines 240 may be anautonomous control routine 246 that performs a type of autonomous control, such as collision avoidance, lane centering, and/or speed control. In some embodiments, the autonomousvehicle operation application 232 may cause a plurality ofautonomous control routines 246 to determine control actions required for autonomous vehicle operation. Similarly, one of the plurality ofsoftware routines 240 may be a monitoring and reporting routine 248 that monitors and transmits information regarding autonomous vehicle operation to theserver 140 via thenetwork 130. Yet another of the plurality ofsoftware routines 240 may be anautonomous communication routine 250 for receiving and transmitting information between thevehicle 108 and external sources to improve the effectiveness of the autonomous operation features. - Any of the plurality of
software routines 240 may be designed to operate independently of thesoftware applications 230 or in conjunction with thesoftware applications 230 to implement modules associated with the methods discussed herein using themicroprocessor 210 of thecontroller 204. Additionally, or alternatively, thesoftware applications 230 orsoftware routines 240 may interact with various hardware modules that may be installed within or connected to themobile device 110 or the on-board computer 114. Such modules may implement part of all of the various exemplary methods discussed herein or other related embodiments. - For instance, such modules may include a vehicle control module for determining and implementing control decisions to operate the
vehicle 108, a system status module for determining the operating status of autonomous operation features, a monitoring module for monitoring the operation of thevehicle 108, a remediation module for correcting abnormal operating states of autonomous operation features, an insurance module for determining risks and costs associated with operation of thevehicle 108, an alert module for generating and presenting alerts regarding thevehicle 108 or the vehicle operator, a risk assessment module for determining risks associated with operation of thevehicle 108 by the autonomous operation features or by the vehicle operator, an identification module for identifying or verifying the identity of the vehicle operator, an information module for obtaining information regarding a vehicle operator orvehicle 108, a use cost module for determining costs associated with operation of thevehicle 108, a comparison module for comparing one or more costs associated with owning or operating thevehicle 108, an update module for updating an autonomous operation feature of thevehicle 108, and/or other modules. - When implementing the exemplary autonomous
vehicle operation method 300, thecontroller 204 of the on-board computer 114 may implement a vehicle control module by the autonomousvehicle operation application 232 to communicate with thesensors 120 to receive information regarding thevehicle 108 and its environment and process that information for autonomous operation of thevehicle 108. In some embodiments, including external source communication via thecommunication component 122 or thecommunication unit 220, thecontroller 204 may further implement a communication module based upon theautonomous communication application 234 to receive information for external sources, such as other autonomous vehicles, smart infrastructure (e.g., electronically communicating roadways, traffic signals, or parking structures), or other sources of relevant information (e.g., weather, traffic, local amenities). Some external sources of information may be connected to thecontroller 204 via thenetwork 130, such as theserver 140 or internet-connected third-party databases (not shown). Although the autonomousvehicle operation application 232 and theautonomous communication application 234 are shown as two separate applications, it should be understood that the functions of the autonomous operation features may be combined or separated into any number of thesoftware applications 230 or thesoftware routines 240. - In some embodiments, the
controller 204 may further implement a monitoring module by the autonomousoperation monitoring application 236 to communicate with theserver 140 to provide information regarding autonomous vehicle operation. This may include information regarding settings or configurations of autonomous operation features, data from thesensors 120 regarding the vehicle environment, data from thesensors 120 regarding the response of thevehicle 108 to its environment, communications sent or received using thecommunication component 122 or thecommunication unit 220, operating status of the autonomousvehicle operation application 232 and theautonomous communication application 234, and/or commands sent from the on-board computer 114 to the control components (not shown) to operate thevehicle 108. The information may be received and stored by theserver 140 implementing the autonomous operationinformation monitoring application 141, and theserver 140 may then determine the effectiveness of autonomous operation under various conditions by implementing thefeature evaluation application 142 and thecompatibility evaluation application 143. The effectiveness of autonomous operation features and the extent of their use may be further used to determine risk associated with operation of the autonomous vehicle by theserver 140 implementing a risk assessment module or insurance module associated with therisk assessment application 144. - In addition to connections to the
sensors 120, themobile device 110 or the on-board computer 114 may include additional sensors, such as theGPS unit 206 or theaccelerometer 224, which may provide information regarding thevehicle 108 for autonomous operation and other purposes. Furthermore, thecommunication unit 220 may communicate with other autonomous vehicles, infrastructure, or other external sources of information to transmit and receive information relating to autonomous vehicle operation. Thecommunication unit 220 may communicate with the external sources via thenetwork 130 or via any suitable wireless communication protocol network, such as wireless telephony (e.g., GSM, CDMA, LTE, etc.), Wi-Fi (802.11 standards), WiMAX, Bluetooth, infrared or radio frequency communication, etc. Furthermore, thecommunication unit 220 may provide input signals to thecontroller 204 via the I/O circuit 216. Thecommunication unit 220 may also transmit sensor data, device status information, control signals, and/or other output from thecontroller 204 to one or more external sensors within thevehicle 108,mobile devices 110, on-board computers 114, and/orservers 140. - The
mobile device 110 and/or the on-board computer 114 may include a user-input device (not shown) for receiving instructions or information from the vehicle operator, such as settings relating to an autonomous operation feature. The user-input device (not shown) may include a “soft” keyboard that is displayed on thedisplay 202, an external hardware keyboard communicating via a wired or a wireless connection (e.g., a Bluetooth keyboard), an external mouse, a microphone, or any other suitable user-input device. The user-input device (not shown) may also include a microphone capable of receiving user voice input. -
FIG. 3 illustrates a flow diagram of an exemplary autonomousvehicle operation method 300, which may be implemented by the autonomousvehicle insurance system 100. Themethod 300 may begin atblock 302 when thecontroller 204 receives a start signal. The start signal may be a command from the vehicle operator through the user-input device to enable or engage one or more autonomous operation features of thevehicle 108. In some embodiments, thevehicle operator 108 may further specify settings or configuration details for the autonomous operation features. For fully autonomous vehicles, the settings may relate to one or more destinations, route preferences, fuel efficiency preferences, speed preferences, and/or other configurable settings relating to the operation of thevehicle 108. In some embodiments, fully autonomous vehicles may include additional features or settings permitting them to operate without passengers or vehicle operators within the vehicle. For example, a fully autonomous vehicle may receive an instruction to find a parking space within the general vicinity, which the vehicle may do without the vehicle operator. The vehicle may then be returned to a selected location by a request from the vehicle operator via amobile device 110 or otherwise. This feature may further be adapted to return a fully autonomous vehicle if lost or stolen. - For other autonomous vehicles, the settings may include enabling or disabling particular autonomous operation features, specifying thresholds for autonomous operation, specifying warnings or other information to be presented to the vehicle operator, specifying autonomous communication types to send or receive, specifying conditions under which to enable or disable autonomous operation features, and/or specifying other constraints on feature operation. For example, a vehicle operator may set the maximum speed for an adaptive cruise control feature with automatic lane centering. In some embodiments, the settings may further include a specification of whether the
vehicle 108 should be operating as a fully or partially autonomous vehicle. In embodiments where only one autonomous operation feature is enabled, the start signal may consist of a request to perform a particular task (e.g., autonomous parking) and/or to enable a particular feature (e.g., autonomous braking for collision avoidance). In other embodiments, the start signal may be generated automatically by thecontroller 204 based upon predetermined settings (e.g., when thevehicle 108 exceeds a certain speed and/or is operating in low-light conditions). In some embodiments, thecontroller 204 may generate a start signal when communication from an external source is received (e.g., when thevehicle 108 is on a smart highway or near another autonomous vehicle). - After receiving the start signal at
block 302, thecontroller 204 may receive sensor data from thesensors 120 during vehicle operation atblock 304. In some embodiments, thecontroller 204 may also receive information from external sources through thecommunication component 122 and/or thecommunication unit 220. The sensor data may be stored in theRAM 212 for use by the autonomousvehicle operation application 232. In some embodiments, the sensor data may be recorded in thedata storage 228 and/or transmitted to theserver 140 via thenetwork 130. The sensor data may alternately either be received by thecontroller 204 as raw data measurements from one of thesensors 120 and/or may be preprocessed by thesensor 120 prior to being received by thecontroller 204. For example, a tachometer reading may be received as raw data and/or may be preprocessed to indicate vehicle movement or position. As another example, asensor 120 comprising a radar and/or LIDAR unit may include a processor to preprocess the measured signals and send data representing detected objects in 3-dimensional space to thecontroller 204. - The autonomous
vehicle operation application 232,other applications 230, and/orroutines 240 may cause thecontroller 204 to process the received sensor data atblock 306 in accordance with the autonomous operation features. Thecontroller 204 may process the sensor data to determine whether an autonomous control action is required and/or to determine adjustments to the controls of thevehicle 108. For example, thecontroller 204 may receive sensor data indicating a decreasing distance to a nearby object in the vehicle's path and process the received sensor data to determine whether to begin braking (and, if so, how abruptly to slow the vehicle 108). As another example, thecontroller 204 may process the sensor data to determine whether thevehicle 108 is remaining with its intended path (e.g., within lanes on a roadway). If thevehicle 108 is beginning to drift or slide (e.g., as on ice or water), thecontroller 204 may determine appropriate adjustments to the controls of the vehicle to maintain the desired bearing. If thevehicle 108 is moving within the desired path, thecontroller 204 may nonetheless determine whether adjustments are required to continue following the desired route (e.g., following a winding road). Under some conditions, thecontroller 204 may determine to maintain the controls based upon the sensor data (e.g., when holding a steady speed on a straight road). - When the
controller 204 determines an autonomous control action is required atblock 308, thecontroller 204 may cause the control components of thevehicle 108 to adjust the operating controls of the vehicle to achieve desired operation atblock 310. For example, thecontroller 204 may send a signal to open or close the throttle of thevehicle 108 to achieve a desired speed. Alternatively, thecontroller 204 may control the steering of thevehicle 108 to adjust the direction of movement. In some embodiments, thevehicle 108 may transmit a message or indication of a change in velocity or position using thecommunication component 122 and/or thecommunication unit 220, which signal may be used by other autonomous vehicles to adjust their controls. As discussed further below, thecontroller 204 may also log or transmit the autonomous control actions to theserver 140 via thenetwork 130 for analysis. - The
controller 204 may continue to receive and process sensor data atblocks controller 204 atblock 312. The end signal may be automatically generated by thecontroller 204 upon the occurrence of certain criteria (e.g., the destination is reached or environmental conditions require manual operation of thevehicle 108 by the vehicle operator). Additionally, or alternatively, the vehicle operator may pause, terminate, and/or disable the autonomous operation feature or features using the user-input device or by manually operating the vehicle's controls, such as by depressing a pedal or turning a steering instrument. When the autonomous operation features are disabled or terminated, thecontroller 204 may either continue vehicle operation without the autonomous features or may shut off thevehicle 108, depending upon the circumstances. - Where control of the
vehicle 108 must be returned to the vehicle operator, thecontroller 204 may alert the vehicle operator in advance of returning to manual operation. The alert may include a visual, audio, and/or other indication to obtain the attention of the vehicle operator. In some embodiments, thecontroller 204 may further determine whether the vehicle operator is capable of resuming manual operation before terminating autonomous operation. If the vehicle operator is determined not be capable of resuming operation, thecontroller 204 may cause the vehicle to stop and/or take other appropriate action. -
FIG. 4 illustrates a flow diagram depicting anexemplary monitoring method 400 during vehicle operation, which may be implemented by the autonomousvehicle insurance system 100. Themethod 400 may monitor the operation of thevehicle 108 and adjust risk levels and rates based upon vehicle use. Although the exemplary embodiment is described as primarily performed by the on-board computer 114, themethod 400 may be implemented by themobile device 110, the on-board computer 114, theserver 140, or a combination thereof. Upon receiving an indication of vehicle operation atblock 402, the on-board computer 114 may determine the configuration and operating status of the autonomous operation features (including thesensors 120 and the communication component 122) atblock 404. The identity of the vehicle operator may be determined and/or verified atblock 406, which identity may be used to determine or receive a vehicle operator profile atblock 408. The vehicle operator profile may contain information regarding the vehicle operator's ability to manually operate the vehicle and/or past use of autonomous operation features by the vehicle operator. Information from thesensors 120 and/or external data from thecommunication component 122 may be used atblock 410 to determine environmental conditions in which thevehicle 108 is operating. Together, this information determined at blocks 404-410 may be used atblock 412 to determine one or more risk levels associated with operation of the vehicle, from which may be determined a costs associated with an insurance policy atblock 414. In some embodiments, information regarding the determined cost may be presented to the vehicle operator or other insurance customer associated with thevehicle 108 atblock 416. In still further embodiments, the vehicle operator and/or insurance customer may be presented with recommendations or options regarding the cost associated with the insurance policy atblock 418. Presentation of options may assist the vehicle operator and/or insurance customer in reducing the cost by allowing the vehicle operator and/or insurance customer to select a lower-cost option (e.g., by adjusting the settings associated with the autonomous operation features). In some embodiments, the vehicle operator and/or insurance customer may be able to select one or more of the options to effect an adjustment in the risk levels and/or insurance cost. - The
method 400 may continue monitoring operation of thevehicle 108 atblock 420, and adjustments may be made to the risk levels and insurance costs. If the settings associated with the autonomous operation features are determined to have changed at block 422 (e.g., as a result of the vehicle operator taking manual operation of additional controls), the one or more risk levels may be determined based upon the new settings atblock 412, in which case the blocks 414-422 may be repeated. When no changes have been made to the settings, themethod 400 may further check for changes to the environmental conditions and/or operating status of the autonomous operation features atblock 424. If changes are determined to have occurred atblock 424, the one or more risk levels may be determined based upon the new settings atblock 412, as atblock 422. When no changes have occurred, themethod 400 may determine whether vehicle operations are ongoing or whether operation is complete atblock 426. When vehicle operation is ongoing, themethod 400 may continue to monitor vehicle operation atblock 420. When vehicle operation is complete, information regarding operation of the vehicle may be recorded atblock 428, at which point themethod 400 may terminate. - At
block 402, the on-board computer 114 may receive an indication of vehicle operation. This indication may be received from the vehicle operator (either directly or through the mobile device 110), and/or it may be generated automatically. For example, the on-board computer 114 or themobile device 110 may automatically generate an indication of vehicle operation when the vehicle starts operation (e.g., upon engine ignition, system power-up, movement of thevehicle 108, etc.). Upon receiving the indication of vehicle operation, the on-board computer 114 may initiate a system check and/or begin recording information regarding operation of thevehicle 108. - At
block 404, the on-board computer 114 may determine the configuration and operating status of one or more autonomous operation features of thevehicle 108. This may include determining the configuration, settings, and/or operating status of one or more hardware or software modules for controlling part or all of the vehicle operation, aftermarket components disposed within the vehicle to provide information regarding vehicle operation, and/orsensors 120 disposed within the vehicle. In some embodiments, a software version, model version, and/or other identification of the feature or sensor may be determined. In further embodiments, the autonomous operation feature may be tested to assess proper functioning, which may be accomplished using a test routine or other means. Additionally, thesensors 120 or thecommunication component 122 may be assessed to determine their operating status (e.g., quality of communication connections, signal quality, noise, responsiveness, accuracy, etc.). In some embodiments, test signals may be sent to one or more of thesensors 120, responses to which may be received and/or assessed by the on-board computer to determine operating status. In further embodiments, signals received from a plurality of sensors may be compared to determine whether any of the sensors are malfunctioning. Additionally, signals received from the sensors may be used, in some embodiments, to calibrate the sensors. - At
block 406, the on-board computer 114 may determine the identity of the vehicle operator. To determine the identity of the vehicle operator, the on-board computer 114 may receive and process information regarding the vehicle operator. In some embodiments, the received information may include sensor data from one ormore sensors 120 configured to monitor the interior of the vehicle. For example, a camera or other photographic sensor may provide photographic information regarding the vehicle operator, which may be processed and compared with other photographic data for a plurality of persons to determine the identity of the vehicle operator. In further embodiments, the on-board computer may receive information from a mobile computing device associated with the vehicle operator, such as a mobile phone or wearable computing device. For example, a mobile phone may connect to the on-board computer 114, which may identify the vehicle operator. Additional steps may be taken to verify the identity of the vehicle operator, such as comparing a weight sensed on a seat or use of voice recognition algorithms. - At
block 408, the on-board computer 114 may determine and/or access a vehicle operator profile based upon the identity of the vehicle operator determined atblock 406. The vehicle operator profile may include information regarding the vehicle operator's style of operating the vehicle, including information regarding past operation of one or more vehicles by the vehicle operator. This information may further contain past vehicle operator selections of settings for one or more autonomous operation features. In some embodiments, the on-board computer 114 may request or access the vehicle operator profiled based upon the determined identity. In other embodiments, the on-board computer 114 may generate the vehicle operator profile from information associated with the identified vehicle operator. The vehicle operator profile may include information relating to one or more risks associated with operation of the vehicle by the vehicle operator. For example, the vehicle operator profile for a driver may include information relating to risk levels based upon past driving patters or habits in a variety of relevant environments, which may include risk levels associated with manual operation of the vehicle by the driver. In some embodiments, the vehicle operator profile may include information regarding default settings used by the vehicle operator for the autonomous operation features. - At
block 410, the on-board computer 114 may determine environmental conditions within which thevehicle 108 is or is likely to be operating. Such environmental conditions may include weather, traffic, road conditions, time of day, location of operation, type of road, and/or other information relevant to operation of the vehicle. The environmental conditions may be determined based upon signals received from thesensors 120, from external data received through thecommunication component 122, and/or from a combination of sources. The environmental conditions may then be used in determining risk levels associated with operation of thevehicle 108. - At
block 412, the on-board computer may determine one or more risk levels associated with operation of thevehicle 108. The risk levels may be determined based upon a combination of risk factors relating to the autonomous operation features and/or risk factors relating to the vehicle operation. Risks associated with the autonomous operation features may be determined based upon the configuration and/or operating status of the autonomous operation features, the settings of the autonomous operation features, and the vehicle environment. Risks associated with the vehicle operation may be determined based upon the autonomous operation features settings (i.e., the extent to which the vehicle operator will be controlling vehicle operations) and/or the vehicle operator profile. The combined risk may account for the likelihood of the autonomous operation features and/or the vehicle operator controlling vehicle operations with respect to relevant functions of thevehicle 108. - At
block 414, the on-board computer 114 may determine a cost associated with an insurance policy based upon the one or more risks. In some embodiments, theserver 140 may receive information regarding the vehicle operator and the autonomous operation features and/or may determine the cost associated with the insurance policy based upon the risks. The cost may be based upon risk levels associated with separate autonomous operation features, interaction between autonomous operation features, the design and capabilities of thevehicle 108, the past operating history of the vehicle operator as included in the vehicle operator profile, and/or other information regarding the probability of an accident, collision, and/or other loss event involving thevehicle 108. Each of the separate risks may depend upon the environmental conditions, and the risks may be weighted based upon the likelihood of each situation. In some embodiments, a total risk may be determined relating to operation of the vehicle under foreseeable conditions with specific settings and configurations of autonomous operation features by a specific vehicle operator. The total risk may be used to determine one or more costs associated with the insurance policy, such as a premium and/or discount. - In some embodiments, information regarding the cost associated with the insurance policy may be presented to the vehicle operator or insurance customer at
block 416. The information may be presented by a display, such as thedisplay 202 of the on-board computer 114 or themobile device 110. The information may be presented either for informational purposes or to receive acceptance of the vehicle operator or insurance customer. The insurance cost information may include an indication of one or more of a premium, rate, rating, discount, reward, special offer, points level, program, refund, and/or other costs associated with one or more insurance policies. Additionally, or alternatively, summary information may be presented regarding insurance costs, including a risk level (e.g., high risk, low risk, a risk/cost level on a spectrum, etc.). In some embodiments, presentation of insurance cost information may be suppressed or delayed (e.g., cost information may be presented in summary form on a periodic billing statement). - In further embodiments, options or recommendations regarding the cost associated with the insurance policy may be presented to the vehicle operator or insurance customer at
block 418. The options or recommendations may likewise be presented by a display, such as thedisplay 202 of the on-board computer 114 and/or themobile device 110. The options or recommendations may include information regarding costs associated with other settings or configurations of the autonomous operation features (e.g., enabling additional features, selecting an operating mode with lower risks under the determined environmental conditions, etc.). In some embodiments, the recommendations or options may be presented for informational purposes only, requiring the vehicle operator or insurance customer to make any adjustments separately (e.g., through a settings module or other means of adjusting settings for the autonomous operation features). In other embodiments, the vehicle operator or insurance customer may select one or more of the options, whereby adjustments to the configuration or settings of the autonomous operation features may be caused to be implemented by the on-board computer 114 or other controlling device. In some embodiments, the options or recommendations may include options or recommendations to update the software version of one or more autonomous operation features, in which case information regarding a cost associated with updating the features (if applicable) may be presented. Once the information and/or options or recommendations regarding insurance costs have been presented at blocks 416-418 (including, in some embodiments, while such presentation is occurring), the on-board computer 114 may monitor operation of thevehicle 108. - At
block 420, the on-board computer 114 may monitor operation of thevehicle 108, including autonomous operation feature control decisions, signals from thesensors 120, external data from thecommunication component 122, and/or control decisions of the vehicle operator. Monitoring vehicle operation may include monitoring data received directly from the features, sensors, and/or other components, as well as summary information regarding the condition, movement, and/or environment of thevehicle 108. The on-board computer 114 and/ormobile device 110 may cause the operating data to be stored or recorded, either locally in thedata storage 228 and/or viaserver 140 in theprogram memory 160 and/or thedatabase 146. Monitoring may continue until vehicle operation is complete (e.g., the vehicle has reached its destination and shut down), including during any updates or adjustments. - At
block 422, the on-board computer 114 may determine whether any changes have been made to the settings or configuration of the autonomous operation features. If such changes or adjustments have been made, the on-board computer 114 may proceed to determine new risk levels and insurance costs at blocks 412-414 and/or present the information to the vehicle operator or insurance customer at blocks 416-418, as discussed above. In some embodiments, minor changes below a minimum change threshold may be ignored when determining whether any changes have been made. In further embodiments, the cumulate effect of a plurality of such minor changes below the minimum change threshold may be considered as a change atblock 422 when the cumulative effect of the minor changes reaches and/or exceeds the minimum change threshold. When no changes to the settings or configuration of the autonomous operation features are determined to have been made atblock 422, the on-board computer 114 may further determine whether any changes in the environmental conditions and/or operating status of the autonomous operation features or sensors have occurred. Although these steps are illustrated separately for clarity, it should be understood that they may be further divided or combined in various embodiments. - At
block 424, the on-board computer 114 may determine whether any changes have occurred to the environmental conditions of thevehicle 108 and/or the operating status of the autonomous operation features,sensors 120, orcommunication component 122. Such changes may occur when weather or traffic conditions change, whensensors 120 malfunction or become blocked by debris, and/or when thevehicle 108 leaves an area where external data is available via thecommunication component 122. When such changes occur, the risk levels associated with control of thevehicle 108 by the vehicle operator and the autonomous operation features may likewise change. Therefore, it may be advantageous to adjust the use of the autonomous operation features to account for such changes. Thus, the on-board computer 114 may proceed to determine new risk levels and insurance costs at blocks 412-414 and/or present the information to the vehicle operator or insurance customer at blocks 416-418, as discussed above, when such changes are determined to have occurred atblock 424. Similar to the determination atblock 422, minor changes below a minimum change threshold may be ignored atblock 424, unless the cumulative effect of the changes reaches or exceeds the minimum change threshold. When no changes are determined to have occurred atblock 424, themethod 400 may continue to monitor the operation of thevehicle 108 until vehicle operation is determined to have ended. - At
block 426, the on-board computer 114 may determine whether vehicle operations are complete. This may include determining whether a command to shut down thevehicle 108 has been received, whether thevehicle 108 has remained idle at a destination for a predetermined period of time, and/or whether the vehicle operator has exited thevehicle 108. Until operation is determined atblock 426 to be complete (i.e., when the vehicle trip has concluded), the on-board computer 114 may continue to monitor vehicle operation atblock 420, as discussed above. When operation is determined to be complete atblock 426, the on-board computer 114 may further cause a record of the operation of thevehicle 108 to be made or stored. Such records may include operating data (in full or summary form) and may be used for assessing risks associated with one or more autonomous operation features or the vehicle operator. As noted above, in some embodiments, records of operating data may be generated and stored continually during operation. In some embodiments, the partial or completed records may be transmitted to theserver 140 to be stored in thedatabase 146. After completion and recordation of the vehicle operation, themethod 400 may terminate. -
FIG. 5 illustrates a flow diagram depicting an exemplary operatingstatus assessment method 500 that may be used to determine operation status of the autonomous operation features,sensors 120, and/orcommunication component 122, as indicated inblocks method 500 may evaluate the autonomous operation features of the vehicle 108 (including sensors 120) and determine whether they are operating correctly, are malfunctioning, and/or are operating with impaired or degraded quality. Such determinations may be particularly important as thevehicle 108 ages or in environments that may block ordamage sensors 120. In such cases, the original effectiveness of the autonomous operation features may be reduced as sensors become less accurate or processing of the sensor data is slowed (such as by software version updates that improve accuracy but require greater computational resources). Theexemplary method 500 may be implemented regularly to ensure appropriate risk assessment, as well as periodically to certify the operating status level of the vehicle for roadworthiness or insurance rate adjustment. In some embodiments, periodic evaluation may be performed using special purpose computing devices and/or by licensed or authorized third parties. Periodic evaluation may further include more thorough testing and analysis of thevehicle 108, which may include testing at a test environment. Although the exemplary embodiment is described as primarily performed by the on-board computer 114, themethod 500 may be implemented by themobile device 110, the on-board computer 114, theserver 140, or a combination thereof. - Upon receiving a request to determine the operating status of the autonomous operation features of the
vehicle 108 atblock 502, the configuration of thesensors 120 may be determined atblock 504. The functioning of autonomous operation feature software routines may further be determined atblock 506. A test signal may be transmitted to thesensors 120 atblock 508, and/or sensor data may be received atblock 510. The sensor data may include a response to the test signal, as well as other signals from the sensors based upon the vehicle environment or operation of thevehicle 108. Based upon the received information, the operating status of the autonomous operation features and components may be determined atblock 512. If any impairments are detected atblock 514, themethod 500 may attempt to remediate the impairments atblock 516. If impairments are detected to remain at block 518 after the remediation attempt, an alert may be generated and presented to the vehicle operator or an insurance customer at block 520. When no impairments are detected or after presentation of the alert, a report indicating the operational status of the autonomous operation features may be generated atblock 522. In some embodiments, the report may be transmitted to an insurer atblock 524, and/or a cost associated with an insurance policy associated with thevehicle 108 may be determined atblock 526. The determined cost may be presented with the report atblock 528 to the vehicle operator or insurance customer. Once the report has been presented, the exemplary method may end. - At
block 502, the on-board computer 114 may receive an indication of a request to check the operating status of the autonomous operation features of thevehicle 108. In some embodiments, the request may be generated in response to a user interaction with themobile device 110 or a special-purpose computing device communicatively connected to thevehicle 108. For example, an application running on themobile device 110 may allow the user of themobile device 110 to request an evaluation of the autonomous operation features. Similarly, a special-purpose computing device may be connected to the vehicle 108 (wirelessly or via a communication port) to evaluate the operating status of the autonomous operation features. In other embodiments, the request may be automatically generated by the on-board computer 114 in response to the occurrence of an event, such as receipt of a command to start the vehicle, receipt of a command to shut off the vehicle, receipt of an indication of a collision involving the vehicle, or receipt of an indication of damage to the vehicle. In yet further embodiments, the request may be generated by theserver 140 and transmitted to the on-board computer 114 to determine the operating status of the autonomous operation features. Such server-generated requests may be used for insurance rating, and may be generated periodically. In some embodiments, the request may further include information regarding the extent of the evaluation of the operating status of the autonomous operation features. For example, the request may indicate that only software or sensors are to be evaluated, or the request may indicate one or more tolerances within which the system components may be determined to be operating properly. - At
block 504, the on-board computer 114 may determine the configuration of thesensors 120 disposed within or communicatively connected to thevehicle 108. This may include determining any of the number, type, location, technical specifications, or characteristics of thesensors 120. In further embodiments, the on-board computer 114 may determine normal functioning characteristics and output ranges for thesensors 120, which may be used in determining whether thesensors 120 are functioning normally. Determining normal functioning characteristics may include requesting such information from theserver 140 or accessing such information stored within thedata storage 228. In some embodiments, the configuration of one ormore communication components 122 may also be determined atblock 504. - At
block 506, the on-board computer 114 may execute one or more software diagnostic routines to evaluate the operation of the software components of the autonomous operation features. In some embodiments, a special-purpose computing device ormobile device 110 may execute the routines or receive the output of the routines. The software diagnostic routines may cause test inputs to be presented to the autonomous operation features and receive responses based upon the test inputs. For example, the software diagnostic routines may simulate sensor inputs corresponding to a situation in which the autonomous operation features should cause the vehicle to brake, then record the control signals generated by the autonomous operation features. Of course, the control signals output from the autonomous operation feature software may be disconnected from the operating controls of thevehicle 108 or suppressed during evaluation to prevent thevehicle 108 from physically responding to the test inputs. - At
block 508, in some embodiments, the on-board computer 114 may generate and transmit one or more test signals to thesensors 120. The test signals may cause thesensors 120 to respond with status information, such as verification of the communicative connection, signal quality, a predetermined set of response signals, or other information regarding the sensors. In some embodiments, the test signals may cause thesensors 120 to enter a test mode or execute a calibration routine, in which case information regarding the operating status of thesensors 120 may be generated at thesensors 120 and transmitted to the on-board computer 114. In further embodiments, the on-board computer 114 may further generate and transmit test signals to thecommunication component 122. - At
block 510, the on-board computer 114 may receive sensor data from thesensors 120 orcommunication components 122. The received sensor data may include responses to test signals. The received sensor data may, in some embodiments, also or alternatively include sensor data generated in the ordinary course of operation of the sensors. For example, the received sensor data may include data indicating sensor readings of obstacles within sensor range of thevehicle 108. Such ordinary course sensor data may be combined and compared to determine the operating status of each of a plurality of sensors connected to thevehicle 108. - At
block 512, the on-board computer 114 may determine the operating status of the autonomous operation features, including thesensors 120 and thecommunication component 122, based upon the received information atblocks sensor 120 may include determining an expected sensor output signal based upon information received fromother sensors 120 and comparing the actual output signal from the sensor to the expected output signal. To avoid minor deviations from expected sensor or software operation from being interpreted as a malfunction, a range of values indicating a normal operating status may be allowed for the sensors and software. Thus, a sensor signal within the normal range may be treated as indicating a normal operating status even if the value is slightly different from the expected value. Additionally,sensors 120 from which no signal is received may be determined to be missing, malfunctioning, or damaged. Somesensors 120 may further be determined to be blocked based upon the received sensor data. - At
block 514, the on-board computer 114 may determine whether any of the autonomous operation features,sensors 120, orcommunication components 122 have an impaired operating status. If all are operating normally, then the on-board computer 114 may proceed to generate a report atblock 522. If any impairments are detected atblock 514, however, the on-board computer 114 may attempt to remediate the impairment atblock 516. Remediation attempts may be determined based upon the type of feature or component, as well as the type of impairment. For example, a remediation attempt for autonomous operation feature software errors may include rebooting or reinstalling a portion of the software. As another example, a signal error in asensor 120 may be remediated by calibration of thesensor 120 based upon available sensor data. Somevehicles 108 may include remediation components (not shown) for certain types of common impairments of some or allsensors 120. For example,sensors 120 may become blocked by snow or ice in cold climates, so heating elements may be disposed within thevehicle 108 to melt accumulated snow or ice from an area around thesensors 120. Other types of blockages, such as by snow, ice, rain, dirt, mud, or condensation, may be addressed with other remediation components. - If remediation is determined at block 518 to successfully address all impairments, a report may be generated at
block 522. If one or more impairments remain, then an alert may be generated and presented to the vehicle operator or insurance customer at block 520. The alert may include information regarding the type of autonomous operation feature or sensor impairment, the severity of the impairment, an impact on risks associated with autonomous operation, whether some autonomous operation features must be disabled, or recommendations regarding autonomous operation features use and settings. In addition to the alert generated and presented at block 520, the on-board computer 114 may generate a report atblock 522. - At
block 522, the on-board computer 114 may generate a report indicating the operating status of the autonomous operation features and components based upon the information received atblocks vehicle 108, which may be recorded in thedata storage 228. Where the evaluation is performed by an authorized or licensed third party, information regarding the third party may be included in the report. - At
block 524, the report may be transmitted to aserver 140 associated with an insurer for determination of costs or adjustments to one or more insurance policies. Atblock 526, theserver 140 may determine one or more costs associated with the one or more insurance policies based upon the report. The one or more costs may include one or more of the following: a premium, a discount, a surcharge, a rate level, a cost based upon a distance traveled, a cost based upon a vehicle trip, or a cost based upon a duration of vehicle operation. In some embodiments, theserver 140 may first determine one or more adjustments to risk levels based upon the information in the report. For example, a risk level associated with an autonomous operation feature may be increased if one or more sensors used by the feature are impaired. The risk levels may be further used to determine costs based upon expected loss rates for thevehicle 108 and the vehicle operator. - At
block 528, the report may be presented to the vehicle operator or insurance customer by a display, such asdisplay 202. The report may be presented in full or may be summarized for ease of use. In some embodiments, the one or more costs associated with the insurance policy determined atblock 526 may also be presented. If the report includes a certification of the status of the autonomous operation features and components, the certification may also be presented to the vehicle operator or insurance customer. In some embodiments, the certification may be further transmitted to an account associated with the vehicle operator or insurance customer or may be transmitted to a third party, such as a government agency. In some embodiments, the vehicle operator or insurance customer may be presented with an option to save, record, print, or transmit the report. -
FIG. 6 illustrates a flow diagram of an exemplary operatingstatus monitoring method 600 that may be used to determine operation status of the autonomous operation features,sensors 120, and/orcommunication component 122, in addition to or alternatively to theexemplary method 500 above. Themethod 600 may be implemented while thevehicle 108 is in operation to monitor the operating status of the autonomous operation features and components. Themethod 600 may monitor the vehicle operating data atblock 602 to determine operating status of the autonomous operation features and components atblock 604. When a change in operating status is detected atblock 606, one or more corresponding changes in risk levels may be determined atblock 608. If the changes in risk levels are determined to cause the risk levels to exceed an alert threshold but not a critical threshold atblocks block 614. If the risk levels are determined to exceed the critical threshold atblock 612, themethod 600 may determine whether control of thevehicle 108 can be safely transferred to the vehicle operator atblock 616. If the vehicle operator is prepared and able to assume control of thevehicle 108, then vehicle operation may be transferred to the vehicle operator atblock 620. If control cannot be safely transferred, thevehicle 108 may cease operations and shut down atblock 618. Once thevehicle 108 is no longer operating, themethod 600 may terminate. Although the exemplary embodiment is described as primarily performed by the on-board computer 114, themethod 600 may be implemented by themobile device 110, the on-board computer 114, theserver 140, or a combination thereof. -
FIGS. 7A-B illustrate flow diagrams depicting exemplary vehicle operation hand-offmethods 700 that may be used to transfer operation of thevehicle 108 from one or more autonomous operation features to the vehicle operator.FIG. 7A illustrates hand-off of control when determined necessary based upon heightened risk levels associated with operation by the one or more autonomous operation features under the environmental conditions.FIG. 7B illustrates hand-off of control when requested by the vehicle operator while one or more autonomous operation features are performing vehicle control tasks. Themethods 700 illustrated inFIGS. 7A and 7B may be combined or separately implemented in various embodiments. Although the exemplary embodiment is described as primarily performed by the on-board computer 114, theexemplary method 700 may be implemented by themobile device 110, the on-board computer 114, theserver 140, and/or a combination thereof. - Exemplary vehicle operation hand-off
method 700 may be implemented at any time when one or more autonomous operation features are controlling part or all of the operation of thevehicle 108. Themethod 700 may begin by identifying the vehicle operator atblock 702 and receiving a vehicle operator profile for the vehicle operator atblock 704. Atblock 706, the operating data (including, in some embodiments, sensor data and external data) may be received and used to monitor operation of thevehicle 108. In some embodiments, a request to disable one or more autonomous operation features may be received from the vehicle operator atblock 732. Autonomous risk levels associated with operation of thevehicle 108 by the autonomous operation features and operator risk levels associated with operation of thevehicle 108 by the vehicle operator may be determined atblock block 712 to determine whether to disable one or more autonomous operation features. In some embodiments, the determination of whether to disable one or more autonomous operation features may further be based upon the preparedness level of the vehicle operator determined atblock 716. - When it is determined to disable one or more autonomous operation features at
block 714, themethod 700 may transfer control to the vehicle operator. In some embodiments, this may include determining whether the vehicle operator is able to safely assume control by determining whether the vehicle operator's preparedness level is above a transfer threshold level atblock 718. If so, an alert may be presented to the vehicle operator atblock 720 to notify the vehicle operator of the transfer of control from the one or more autonomous operation features before transferring operation atblock 722. If the vehicle operator's preparedness level is determined to be below the transfer threshold but above a minimum threshold atblock 724, an alert may be presented atblock 730 to attempt to prepare the vehicle operator to assume control if the risk levels associated with continued operation by the autonomous operation features do not exceed a critical risk threshold atblock 726. Once the alert is presented to the vehicle operator atblock 730, the vehicle operator's preparedness level may be determined again atblock 716 and evaluated atblock 718. If the risk levels exceed the critical threshold atblock 726 or the vehicle operator's preparedness level is below the minimum threshold atblock 724, thevehicle 108 may discontinue operation atblock 728 and themethod 700 may end. - When it is determined not to disable the one or more autonomous operation features at
block 714, themethod 700 may continue to monitor the operating data atblock 706. If the vehicle operator requested that one or more autonomous operation features be disabled, themethod 700 may present an alert atblock 734 to notify the vehicle operator that disabling the autonomous operation features is not recommended. In some embodiments, options to override the determination not to disable the autonomous operation features may be presented to the vehicle operator atblock 736, which the vehicle operator may select atblock 738. If the vehicle operator is determined atblock 740 to have not selected an option to override the determination, themethod 700 may continue to monitor operation data atblock 706. If the vehicle operator is determined atblock 740 to have selected an option to override the determination, control of operation may be transferred from the one or more autonomous operation features to the vehicle operator. In some embodiments, one or more risk levels associated with disabling the autonomous operation features may be determined atblock 742. If the risk levels are determined to be below a critical threshold atblock 744, control may be transferred to the vehicle operator. If the risk levels meet or exceed the critical threshold atblock 744, thevehicle 108 may instead discontinue operation atblock 728 and themethod 700 may end. -
FIG. 8 illustrates a flow diagram depicting an exemplary vehicleoperator identification method 800 that may be used to adjust an insurance policy associated with the vehicle operator orvehicle 108. Theexemplary method 800 may begin with receipt of a request to identify the vehicle operator of the vehicle atblock 802. At blocks 804-810, the vehicle operator may be identified by sensor data or received indications of identity, such as from amobile device 110. Once the identity of the vehicle operator has been determined (or cannot be determined), themethod 800 may further determine whether the vehicle operator is authorized to operate thevehicle 108 atblock 812. If the vehicle operator is not authorized, an alert may be generated and vehicle operations may be limited at blocks 814-816. If the vehicle operator is authorized, a vehicle operator profile associated with the vehicle operator may be obtained atblock 818, and/or an insurance policy associated with thevehicle 108 or the vehicle operator may be identified atblock 820. During vehicle operation, operating data of thevehicle 108 may be received and used to adjust the vehicle operator profile and the insurance policy at blocks 822-826. When vehicle operation has been determined to be complete atblock 828, themethod 800 may terminate. Although the exemplary embodiment is described as primarily performed by the on-board computer 114, themethod 800 may be implemented by themobile device 110, the on-board computer 114, theserver 140, and/or a combination thereof. -
FIG. 9 illustrates a flow diagram depicting an exemplary vehicle operator use monitoring andevaluation method 900 that may be used to determine skill or risk levels associated with a vehicle operator or adjust an insurance policy. Theexemplary method 900 may begin with determining the identity of the vehicle operator atblock 902. If a vehicle operator profile can be found for the vehicle operator atblock 904, the vehicle operator profile may be accessed atblock 912. If no vehicle operator profile can be found for the vehicle operator atblock 904, a vehicle operator profile may be created based upon vehicle operations and stored for future use at blocks 906-910. The newly created vehicle operator profile may be generated atblock 908 with vehicle operating data from only a short time period or may include only information regarding configuration and/or settings of the autonomous operation features, in which case operation of the vehicle may continue after the vehicle operator profile is generated. If operation is determined to be ongoing atblock 914, vehicle operation may be monitored and the vehicle operator profile may be updated at blocks 916-924. In some embodiments, the vehicle operator may be able to select an option of a mode for vehicle operation. If such a mode selection is detected atblock 916, the settings of the autonomous operation features may be adjusted atblock 918. Vehicle operation may be monitored atblock 920 based upon received operating data, which may be used to determine adjustments to the vehicle operator profile atblock 922. The adjustments may then be used to update the vehicle operator profile atblock 924. When operation is complete, themethod 900 may determine risk or skill levels associated with the vehicle operator at blocks 926-928. These determined levels may be used at blocks 930-934 to generate a report or adjust an insurance policy. Although the exemplary embodiment is described as primarily performed by the on-board computer 114, themethod 900 may be implemented by themobile device 110, the on-board computer 114, theserver 140, and/or a combination thereof. - The vehicle operator profile may include information regarding the vehicle operator, including an operating style of the vehicle operation. The operating style may include information regarding frequency with which the vehicle operator operates the vehicle manually, uses one or more autonomous operation features, selects one or more settings for the autonomous operation features, and/or takes control from the autonomous operation features under various conditions. The operating style may further include information regarding observed control decisions made by the vehicle operator, such as rate of acceleration, frequency of lane changes, use of vehicle signaling devices, distances maintained from other vehicles or pedestrians, and/or other aspects of vehicle operation. For example, vehicle operator decisions regarding how long to stop at a stop sign or when to begin accelerating from such a stop in the presence of other vehicles or pedestrians may be included in the operating style. The vehicle operator profile may further include information regarding vehicle operator skill levels, as described below. In some embodiments, the vehicle operator profile may include a risk profile or information regarding one or more risk levels associated with operation of the vehicle by the vehicle operator. Such risk levels may be associated with particular configurations or settings of autonomous operation features and/or particular conditions of the vehicle environment (e.g., time of day, traffic levels, weather, etc.).
- In further embodiments, the vehicle operator profile may include information regarding attentiveness of the vehicle operator while the vehicle is being autonomously operated. For example, some vehicle operators may typically pay attention to road conditions while a vehicle is operating in a fully autonomous mode, while other vehicle operators may typically engage in other activities. In some embodiments, the vehicle operator profile may include information regarding decisions made by the vehicle operator regarding actions that would result in adjustments to costs associated with an insurance policy (e.g., accepting or rejecting recommendations to optimize autonomous operation feature use to lower insurance costs).
- The vehicle operator profile or vehicle operator behavior data may indicate how well the specific vehicle operator drives in rain, snow, sleet, ice, heavy traffic, road construction, stop-and-go traffic, bumper-to-bumper traffic, country or rural traffic, and/or city or downtown street traffic. The current environment (or condition) may include or be rain, ice, snow, fog, heavy traffic, bumper-to-bumper traffic, road construction, city traffic, country or rural traffic, and/or may be associated with a type of road, such as a two-lane or four-lane highway, and/or downtown city street or other street having several traffic lights.
- The operating mode may include one or more settings or configurations of autonomous operation features. For example, operating modes may include adjustments to settings that cause the autonomous operation features to control the
vehicle 108 in a more or less aggressive manner with respect to speed, distance from other vehicles, distance from pedestrians, etc. As an example, the settings may cause thevehicle 108 to remain at least a minimum distance from other vehicles (which may depend upon vehicle speed or road conditions), and/or modes may set different minimum distances. Examples of modes may include a city driving mode, a highway driving mode, a rush operation mode, a smooth operation mode, a cautious mode, and/or a user-defined mode. - In some embodiments, an operating mode may be based upon the vehicle operator profile. For example, the vehicle profile may include information indicating an operating style of the vehicle operator based upon observations of control commands by the vehicle operator, which profile information may be used to generate an operation mode that mimics the style of the vehicle operator. Thus, if the vehicle operator typically stops at stop signs for a particular length of time, the operating style may mimic this length of time to provide an experience that seems normal or customary to the vehicle operator.
-
FIG. 10 illustrates a flow diagram depicting an exemplarycost comparison method 1000 that may be used to compare costs associated with vehicles, some of which may include autonomous operation features. Theexemplary method 1000 may begin by receiving a command to generate a comparison report between two or more alternative transportation options for an insurance customer or other user. Themethod 1000 may further receive information regarding one or more vehicle operators may be received atblock 1004 and/or information regarding a first vehicle and a second vehicle atblock 1006. The first and second vehicles may differ in autonomous operation features or other characteristics. Cost levels associated with obtaining, operating, and insuring the first vehicle and the second vehicle may be determined atblock 1008, and/or a recommendation based upon the costs may be determined atblock 1010. A report including the costs levels, recommendation, and/or related information may be generated atblock 1012 and presented to the insurance customer or other user atblock 1014. Additionally, one or more options may be presented along with the report atblock 1016, such as options to perform another comparison or present additional information. If an option is selected atblock 1018, the corresponding action may be performed atblock 1020. Although the exemplary embodiment is described as primarily performed by theserver 140, themethod 1000 may be implemented by themobile device 110, the on-board computer 114, theserver 140, and/or a combination thereof. -
FIG. 11 illustrates a flow diagram depicting an exemplary autonomous operationfeature update method 1100 that may be used to identify, recommend, and/or install updates to autonomous operation features in appropriate autonomous or semi-autonomous vehicles. In some embodiments, the updates may include software version updates. Theexemplary method 1100 may begin with the receipt of an indication of an available update to an autonomous operation feature atblock 1102, which may include an update to a version of autonomous operation feature software. A plurality of vehicles having the autonomous operation feature may be identified atblock 1104 based upon recorded features or communication with the plurality of vehicles. A change in one or more risk levels associated with the update may be determined for some or all of the identified vehicles atblock 1106, and/or a change in a cost associated with one or more of the plurality of vehicles may be determined atblock 1108. If the determined changes in risk levels or insurance costs meet certain criteria for installing the update atblock 1110, a notification regarding the update may be presented to an insurance customer atblock 1112. The notification may further include information regarding costs associated with the update. If an indication of acceptance of the update is received atblock 1114, the update may be installed atblock 1116. Although the exemplary embodiment is described as primarily performed by theserver 140, themethod 1100 may be implemented by themobile device 110, the on-board computer 114, theserver 140, and/or a combination thereof. -
FIG. 12 illustrates a flow diagram depicting an exemplary autonomousvehicle repair method 1200 that may be used to determine repairs needed as a result of damage to an autonomous or semi-autonomous vehicle. Theexemplary method 1200 may begin by receiving an indication of damage to thevehicle 108 atblock 1202 and/or receiving operating data associated with thevehicle 108 atblock 1204. Based upon the operating data, the type and extent of damage to thevehicle 108 may be determined atblock 1206, and/or repairs needed to fix the damage may be determined atblock 1208. Additionally, one or more expected costs (or ranges of costs) for the repairs may be estimated atblock 1210. An insurance policy associated with thevehicle 108 may be identified, and/or a maximum payment for the repairs may be determined atblock 1212 based upon the estimated costs and the insurance policy. Information regarding the estimated cost or costs and the maximum payment under the insurance policy may be presented to an insurance customer atblock 1214. Additionally, options associated with the repairs may be presented to the insurance customer atblock 1216, and/or a selection of one or more options may be received atblock 1218. An insurer or other party may cause a payment to be made atblock 1220 to the insurance customer, beneficiary, or other relevant party based upon the estimated costs of repairing the damage and the selected option. Although the exemplary embodiment is described as primarily performed by theserver 140, themethod 1200 may be implemented by themobile device 110, the on-board computer 114, theserver 140, and/or a combination thereof. - At
block 1202, the on-board computer 114 orserver 140 may receive an indication of damage to thevehicle 108. The indication may be received from a vehicle operator and/or insurance customer, and/or the indication may be automatically generated upon a determination of damage. For example, thesensors 120 may provide sensor data to the on-board computer 114 that indicates a collision with another vehicle or other object. Alternatively, the substantially simultaneous disconnection and/or malfunction of a plurality ofsensors 120 located in close proximity within thevehicle 108 may cause the on-board computer 114 to generate an indication of damage to thevehicle 108. - At
block 1204, the on-board computer 114 and/orserver 140 may receive operating data regarding operation of the vehicle. The operating data may cover operation of the vehicle both before and after the damage occurred, covering a period of time without the damage and a period of time with the damage. The operating data may include information received from thesensors 120 and/or thecommunication component 122. The operating data may further include information regarding autonomous operation features, such as configurations or settings, and/or information regarding command controls issued by the autonomous operation features and/or vehicle operator. The operating data may further include information derived or determined from the sensor or other data, such as vehicle speed and/or direction. Where the vehicle is inoperable following the damage, the operating data for the time period with damage may include sensor data and/or other data regarding the vehicle and/or the vehicle environment. Such data may be useful in determining the likely extent of the damage by determining damaged areas and/or systems of thevehicle 108. - At
block 1206, theserver 140 may determine damage to thevehicle 108 based upon the received operating data. In some embodiments, the operating data may be compared against operating data for a plurality of previous instances of known vehicle damage stored within thedatabase 146 to determine likely damage. Such assessment may be based information from similar vehicles (e.g., vehicles of the same make and model, body type, size, or production year). In some embodiments, the operating data may be processed to generate a model of the vehicle in its environment at the time of the damage. For example, the operating data may indicate relative speeds and/or trajectories of vehicles involved in a collision with thevehicle 108. This model may then be further used to determine likely damage based upon information regarding thevehicle 108 and/or previous loss reports for other vehicles. In some embodiments, the determined damage may be reviewed by a verification routine of theserver 140 and/or by a reviewer to verify that the determined level of damage appears to match the actual level of damage. Verification may include assessing the operating status of thesensors 120 and/orcommunication component 122. In some embodiments, the damage may be determined based upon input from a special-purpose computing device or a human assessor. - At
block 1208, theserver 140 may determine one or more repairs associated with the determined damage to thevehicle 108. In some embodiments, the repairs may be determined based upon comparisons of information regarding previously repaired vehicles' damage and repairs. In further embodiments, the repairs may be determined based upon models and/or relationships between types of damage and types of repairs. The repairs may include replacing and/or fixing damage to one or more vehicle components, including the vehicle frame and body. In some embodiments, the repairs may include alternative likely repairs, such that performance of one repair may foreclose the necessity of another repair. For example, the operating data may indicate two or more probably types of damage, but only one type of damage may be present. Thus, repair of one type of likely damage would obviate the need to repair the other types of likely damage. In some embodiments, the repairs may include one or more general repair services and/or one or more specialty repair services. General repair services may be performed by most vehicle repair facilities, whereas specialty repair services may require specialized equipment, materials, and/or expertise to perform the repairs. - At
block 1210, theserver 140 may determine expected costs associated with the one or more repairs determined atblock 1208. The costs may include both direct costs of repair, as well as indirect costs, such as vehicle rental while thevehicle 108 is being repaired. The costs may be determined based upon information regarding actual costs of repairs performed on a plurality of other vehicles. In some embodiments, the repair costs for other vehicles may be used to determine a range of expected costs and/or an average cost for each repair. The range of expected costs may further be used to determine one or more expected cost levels associated with the repairs, such as a median cost, a mean cost, a high cost or low cost (e.g., levels based upon percentages such as the 80th percentile or the 20th percentile of costs), costs associated with different likely damage levels, and/or indirect costs based upon the extent of the repairs. The costs may also be based upon comparisons of costs in one or more relevant geographic areas. For example, minor damage occurring during a long-distance trip may not preclude operation of thevehicle 108 through the remainder of the trip, in which case costs associated with repair in multiple geographic areas may be determined (e.g., an area where the damage occurred, an area corresponding to a destination of the trip, or an area corresponding to the home location of the vehicle operator or insurance customer). In some embodiments, the costs may be determined based upon quotes received from one or more repair facilities based upon the determined repairs and/or operating data. - At
block 1212, theserver 140 may determine one or more maximum payments for the repairs to thevehicle 108. The maximum payments may be based upon the determined costs of the repairs. In some embodiments, the maximum payment may be based upon the range of repair costs. For example, the maximum payment may be set to a level based upon the distribution of repair costs within the range, such that the maximum payment is equal to an actual cost of repairs for a vehicle at a certain percentile of vehicles within the actual repair cost range (e.g., 70th percentile). In further embodiments, the maximum payment may be based in whole or part upon the insurance policy under which payment may be made. For example, a maximum payment amount may be set by the insurance policy, which may, in some embodiments, be further limited based upon the expected costs and/or range of expected costs determined atblock 1210. - At
block 1214, theserver 140 may cause the one or more expected costs to be presented to the insurance customer, using thedisplay 202 and/or other means. In some embodiments, the maximum payment may be presented to the insurance customer together with the expected costs. For example, where a plurality of alternatives are presented regarding the repairs, each expected cost may include an indication of whether it is below the maximum payment. - At
block 1216, theserver 140 may cause one or more options regarding the repairs to be presented to the insurance customer. The options may indicate timing, extent, and/or location of the repairs and may be associated with different costs for the repairs. In some embodiments, the options may include options of one or more repair facilities at which thevehicle 108 may be repaired. Each facility may further be associated with a cost estimate and/or an estimate of a length of time required to complete the repairs. In some embodiments, the estimates of costs and/or time for each facility may be based upon the operating data and/or determined damage. In further embodiments, the estimates of costs and/or time for one or more of the repair facilities may be based upon quoted estimates solicited from the repair facilities received by theserver 140. The options may be presented together with an indication of whether each exceeds the maximum payment, such as by a warning presented in connection with any options that exceed the maximum payment. - At
block 1218, theserver 140 may receive a selection of one or more of the options from the insurance customer or other authorized user. Upon receiving the selection, theserver 140 may cause a payment to be made atblock 1220 based upon the one or more selections. The payment may be made to the insurance customer and/or beneficiary of the insurance policy, or the payment may be made to a repair facility and/or other party associated with the repairs. In some embodiments, theserver 140 may further facility the repairs by scheduling the repairs at a repair facility, arranging towing of the vehicle to the repair facility, and/or arranging a temporary replacement vehicle for the vehicle operator and/or insurance customer. Once all actions relating to the repair and/or payment have been implemented, themethod 1200 may terminate. - According to certain aspects, a computer-implemented method for responding to damage to an autonomous or semi-autonomous vehicle relating to a collision or other loss may be provided. With the customer's permission, an indication of damage to the autonomous or semi-autonomous vehicle, and/or operating data regarding operation of the vehicle during (i) a time period without the damage to the autonomous or semi-autonomous vehicle, and (ii) a time period with the damage to the autonomous or semi-autonomous vehicle may be received at a remote server, such as via wireless communication from the customer's vehicle controller or mobile device. Repairs associated with the damage may be determined at the remote server based upon the operating data, as well as an expected cost associated with the repairs. Insurance discounts may be provided to risk averse customers that timely repair damaged vehicles or features that impact vehicle safety. For instance, insurance discounts or quote may be generated and transmitted from a remote server or associated transceiver to the customer's vehicle controller/control system or mobile device for their review and/or approval.
- With the foregoing, a customer may opt into a rewards or other type of program, and willingly share their vehicle data with an insurance provider. In return, risk averse drivers and vehicle owners may receive discounts or insurance cost savings related to auto and other types of insurance from the insurance provider.
-
FIG. 13 illustrates a flow diagram depicting an exemplaryinfrastructure communication method 1300 that may be used to detect and communicate information regarding infrastructure components to vehicles. Theexemplary method 1300 may begin with theinfrastructure communication device 124 receiving information regarding theinfrastructure component 126 from one or more sensors atblock 1302. The information may be used atblock 1304 to determine a message regarding theinfrastructure component 126. In some embodiments, the message may be augmented atblock 1306 by information associated with a sponsor or other party affiliated with theinfrastructure communication device 124. The message may then be encoded atblock 1308 and transmitted atblock 1310, which may cause the message to be presented to the vehicle operator of thevehicle 108 at block 1312. Although the exemplary embodiment describes oneinfrastructure communication device 124 communicating with onevehicle 108, it should be understood than any number ofinfrastructure communication devices 124 may communicate with any number ofvehicles 108. - In one aspect, a computer-implemented method of accident reconstruction or fault determination may be provided. The method may include (1) gathering or collecting data from one or more vehicle-mounted sensors and/or one or more autonomous or semi-autonomous functionality or technology systems of a vehicle, via one or more processors (such as a smart vehicle controller and/or insurance provider remote processor or server) in wired or wireless communication with the one or more vehicle-mounted sensors and/or the one or more autonomous or semi-autonomous functionality or technology systems, the data showing operation of the vehicle and/or how the one or more autonomous or semi-autonomous functionality or technology systems performed before, during, and/or after a vehicle accident involving the vehicle, the vehicle being insured by an insurance provider; (2) reconstructing the scene of the vehicle accident and/or a series of events leading up to the vehicle accident, via the one or more processors; (3) determining, via the one or more processors, one or more causes of the vehicle accident (whether human driver error or faulty autonomous or semi-autonomous functionality or technology) based upon the reconstruction of the vehicle accident; (4) generating, updating, or adjusting, via the one or more processors, (i) an insurance claim associated with the vehicle accident, and/or (ii) an insurance policy, premium, rate, discount, or reward based upon the one or more causes of the vehicle accident determined from the reconstruction of the vehicle accident; and/or (5) communicating or transmitting, from the one or more processors, the insurance claim or insurance policy generated, updated, or adjusted to a mobile device of an insured or owner of the vehicle insured by the insurance provider. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
- In one aspect, a computer-implemented method of updating an insurance policy may be provided. The method may include (a) gathering or receiving, at or via one or more processors (such as either a local processor associated with a smart vehicle and/or a remote processor or server associated with an insurance provider), data indicative of (1) vehicle usage, and/or (2) vehicle drivers for an insured vehicle; (b) analyzing the data, via the one or more processors, to determine (i) an amount and/or (ii) type of vehicle usage for each vehicle driver; (c) based upon the amount of vehicle usage for each vehicle driver and/or the type of vehicle usage for each vehicle driver, via the one or more processors, updating or adjusting an insurance policy (such as a premium, rate, rewards or points program, discount, etc.) for the insured vehicle; (d) transmitting, under the direction or control of the one or more processors, the updated or adjusted insurance policy (or otherwise causing the updated or adjusted insurance policy to be presented or displayed to the insured) to a mobile device of the insured for their review, modification, and/or approval; and/or (e) receiving, at or via the one or more processors, from the mobile device of the insured (such as via wireless communication) an approval of the updated or adjusted insurance policy of the insured to facilitate more accurate insurance pricing and/or insurance cost savings. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
- For instance, the amount of vehicle usage may include an amount of time and/or miles that each individual vehicle driver drives the vehicle. The type of vehicle usage may include characterizing various periods of driving and/or trips as city driving; country driving; freeway or highway driving city street driving; heavy traffic or congested traffic driving; driving in good weather; driving in hazardous weather; rush hour driving; and/or time-of-day driving.
- The vehicle drivers may be identified from mobile device signature; seat pressure sensors and weight; image recognition techniques performed upon images of the driver; and/or biometric devices (such as heart beat or rate characteristics; voice print; and/or thumb or finger prints).
- In one aspect, a computer-implemented method of updating an insurance policy using biometric device data may be provided. The method may include (a) gathering or receiving, at or via one or more processors (such as either a local processor associated with a smart vehicle and/or a remote processor or server associated with an insurance provider), data from a biometric device indicative of whom is driving an insured vehicle; (b) gathering or receiving, at or via the one or more processors, data indicative of vehicle usage for a single trip and/or driving or driver behavior during the single trip; (c) updating or adjusting, at or via the one or more processors, an insurance policy (such as a premium, rate, rewards or points program, discount, etc.) for the insured vehicle based upon (1) whom is driving the insured vehicle (and/or his or her driving profile or score), and/or (2) the data indicative of vehicle usage for the single trip and/or the driving or driver behavior exhibited during the single trip to facilitate more accurate risk assessment and/or cost savings to the insured. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein. For instance, the biometric device may verify an identity of the driver based upon heartbeat, facial recognition techniques, and/or mood.
- In another aspect, a computer-implemented method of updating an insurance policy may be provided. The method may include (1) gathering or receiving, at or via one or more processors (such as either a local processor associated with a smart vehicle and/or a remote processor or server associated with an insurance provider), data from a biometric device identifying a driver of an insured vehicle; (2) gathering or receiving, at or via the one or more processors, data indicative of driving or driver behavior for the driver identified from the biometric device data; (3) generating, at or via the one or more processors, a usage-based insurance policy for the insured vehicle based upon (i) the identity of the driver determined from the biometric device data, and/or (ii) the data indicative of driving or driver behavior exhibited by the driver to facilitate more accurate risk assessment and/or provide cost savings to the insured. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
- In one aspect, a computer-implemented method of generating or updating an usage-based insurance policy for an autonomous or semi-autonomous vehicle having multiple drivers may be provided. The method may include (1) identifying, via one or more processors (such as a vehicle-mounted local processor or remote insurance provider processor or server), multiple drivers that drive a vehicle, the vehicle having one or more autonomous or semi-autonomous technologies or functionalities; (2) determining, via the one or more processors, a driving behavior for each of the multiple drivers; (3) determining, via the one or more processors, (i) an amount that each autonomous or semi-autonomous technology or functionality is used, and/or (ii) a type of autonomous or semi-autonomous technology or functionality that is employed by each of the multiple drivers; (4) generating or updating, via the one or more processors, an insurance policy (such as a premium, rate, discount, rewards or points program, etc.) for the vehicle based upon (a) the driving behavior for each of the multiple drivers determined, (b) the amount that each autonomous or semi-autonomous technology or functionality is used by each of the multiple drivers, and/or (c) the type of autonomous or semi-autonomous technology or functionality that is employed by each of the multiple drivers to facilitate providing insurance-related cost savings to the insured and/or to provide an enticement to an insured family to implement safety enhancing technology or functionality. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
- In one aspect, a computer-implemented method of updating an insurance policy may be provided. The method may include (1) gathering or receiving, at or via one or more processors (such as either a local processor associated with a smart vehicle and/or a remote processor or server associated with an insurance provider), data indicative of a software version installed on or in an insured vehicle that is associated with an autonomous or semi-autonomous functionality; (2) determining, at or via the one or more processors, that the software version is out of date or a (safer or less risky) new software version exists and/or is available for download; (3) generating, at or via the one or more processors, a recommendation to an insured to update or upgrade to the new software version, and transmitting that recommendation under the direction or control of the one or more processors to a mobile device or insured vehicle controller (such as via wireless communication or data transmission); (4) determining, at or via the one or more processors, (or receiving an indication) that the insured has updated or upgraded to the new software version associated with the autonomous or semi-autonomous functionality; and/or (5) updating or adjusting, at or via the one or more processors, an insurance policy (such as a premium, rate, rewards or points program, discount, etc.) for the insured vehicle based upon the insured updating or upgrading to the new software version associated with an autonomous or semi-autonomous functionality to facilitate providing cost savings to the insured and/or enticing drivers to update vehicle software to most recent versions and/or versions that perform better. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
- Risk profiles or risk levels associated with one or more autonomous operation features determined above may be further used to determine risk categories or premiums for vehicle insurance policies covering autonomous vehicles. In some embodiments or under some conditions, the
vehicle 108 may be a fully autonomous vehicle operating without a vehicle operator's input or presence. In other embodiments or under other conditions, the vehicle operator may control thevehicle 108 with or without the assistance of the vehicle's autonomous operation features. For example, the vehicle may be fully autonomous only above a minimum speed threshold or may require the vehicle operator to control the vehicle during periods of heavy precipitation. Alternatively, the autonomous vehicle may perform all relevant control functions using the autonomous operation features under all ordinary operating conditions. In still further embodiments, thevehicle 108 may operate in either a fully or a partially autonomous state, while receiving or transmitting autonomous communications. - Where the
vehicle 108 operates only under fully autonomous control by the autonomous operation features under ordinary operating conditions or where control by a vehicle operator may be disregarded for insurance risk and price determination, the risk level or premium associated with an insurance policy covering the autonomous vehicle may be determined based upon the risks associated with the autonomous operation features, without reference to risks associated with the vehicle operator. Where thevehicle 108 may be operated manually under some conditions, the risk level or premium associated with an insurance policy covering the autonomous vehicle may be based upon risks associated with both the autonomous operation features and the vehicle operator performing manual vehicle operation. Where thevehicle 108 may be operated with the assistance of autonomous communications features, the risk level or premium associated with an insurance policy covering the autonomous vehicle may be determined based in part upon a determination of the expected use of autonomous communication features by external sources in the relevant environment of thevehicle 108 during operation of thevehicle 108. - In one aspect, the present embodiments may relate to data acquisition. Data may be gathered via devices employing wireless communication technology, such as Bluetooth or other IEEE communication standards. In one embodiment, a Bluetooth enabled smartphone or mobile device, and/or an in-dash smart and/or communications device may collect data. The data associated with the vehicle, and/or vehicle or driver performance, that is gathered or collected at, or on, the vehicle may be wirelessly transmitted to a remote processor or server, such as a remote processor or server associated with an insurance provider. The
mobile device 110 may receive the data from the on-board computer 114 or thesensors 120, and may transmit the received data to theserver 140 via thenetwork 130, and the data may be stored in thedatabase 146. In some embodiments, the transmitted data may include real-time sensor data, a summary of the sensor data, processed sensor data, operating data, environmental data, communication data, or a log such data. - Data may be generated by autonomous or semi-autonomous vehicles and/or vehicle mounted sensors (or smart sensors), and then collected by vehicle mounted equipment or processors, including Bluetooth devices, and/or an insurance provider remote processor or server. The data gathered may be used to analyze vehicle decision making. A processor may be configured to generate data on what an autonomous or semi-autonomous vehicle would have done in a given situation had the driver not taken over manual control/driving of the vehicle or alternative control actions not taken by the autonomous or semi-autonomous operation features. This type of control decision data (related to vehicle decision making) may be useful with respect to analyzing hypothetical situations.
- In one embodiment, an application, or other computer or processor instructions, may interact with a vehicle to receive and/or retrieve data from autonomous or semi-autonomous processors and sensors. The data retrieved may be related to radar, cameras, sensor output, computer instructions or application output. Other data related to a smart vehicle controller, car navigation unit information (including route history information and typical routes taken), GPS unit information, odometer and/or speedometer information, and smart equipment data may also be gathered or collected. The application and/or other computer instructions may be associated with an insurance provider remote processor or server.
- The control decision data may further include information regarding control decisions generated by one or more autonomous operation features within the vehicle. The operating data and control decision data gathered, collected, and/or acquired may facilitate remote evaluation and/or analysis of what the autonomous or semi-autonomous vehicle was “trying to do” (brake, slow, turn, accelerate, etc.) during operation, as well as what the vehicle actually did do. The data may reveal decisions, and the appropriateness thereof, made by the artificial intelligence or computer instructions associated with one or more autonomous or semi-autonomous vehicle technologies, functionalities, systems, and/or pieces of equipment. The data may include information related to what the vehicle would have done in a situation if the driver had not taken over (beginning manual vehicle control). Such data may include both the control actions taken by the vehicle and control actions the autonomous or semi-autonomous operation features would have caused the vehicle to take. Thus, in some embodiments, the control decisions data may include information regarding control decisions not implemented by the autonomous operation features to control the vehicle. This may occur when an autonomous operation feature generates a control decision or associated control signal, but the control decision or signal is prevented from controlling the vehicle because the autonomous feature or function is disabled, the control decision is overridden by the vehicle operator, the control signal would conflict with another control signal generated by another autonomous operation feature, a more preferred control decision is generated, and/or an error occurs in the on-
board computer 114 or the control system of the vehicle. - For example, a vehicle operator may disable or constrain the operation of some or all autonomous operation features, such as where the vehicle is operated manually or semi-autonomously. The disabled or constrained autonomous operation features may, however, continue to receive sensor data and generate control decision data that is not implemented. Similarly, one or more autonomous operation features may generate more than one control decision in a relevant period of time as alternative control decisions. Some of these alternative control decisions may not be selected by the autonomous operation feature or an autonomous operation control system to control the vehicle. For example, such alternative control decisions may be generated based upon different sets of sensor or communication data from
different sensors 120 or include or excluding autonomous communication data. As another example, the alternative control decisions may be generated faster than they can be implemented by the control system of the vehicle, thus preventing all control decisions from being implemented. - In addition to control decision data, other information regarding the vehicle, the vehicle environment, or vehicle operation may be collected, generated, transmitted, received, requested, stored, and/or recorded in connection with the control decision data. Additional operating data including sensor data from the
sensors 120, autonomous communication data from thecommunication component 122 or thecommunication unit 220, location data, environmental data, time data, settings data, configuration data, and/or other relevant data may be associated with the control decision data. In some embodiments, a database or log may store the control decision data and associated information. In further embodiments, the entries in such log or database may include a timestamp indicating the date, time, location, vehicle environment, vehicle condition, autonomous operation feature settings, and/or autonomous operation feature configuration information associated with each entry. Such data may facilitate evaluating the autonomous or semi-autonomous technology, functionality, system, and/or equipment in hypothetical situations and/or may be used to calculate risk, and in turn adjust insurance policies, premiums, discounts, etc. - The disclosure herein relates to insurance policies for vehicles with autonomous operation features. Accordingly, as used herein, the term “vehicle” may refer to any of a number of motorized transportation devices. A vehicle may be a car, truck, bus, train, boat, plane, motorcycle, snowmobile, other personal transport devices, etc. Also as used herein, an “autonomous operation feature” of a vehicle means a hardware or software component or system operating within the vehicle to control an aspect of vehicle operation without direct input from a vehicle operator once the autonomous operation feature is enabled or engaged. The term “autonomous vehicle” means a vehicle including at least one autonomous operation feature. A “fully autonomous vehicle” means a vehicle with one or more autonomous operation features capable of operating the vehicle in the absence of or without operating input from a vehicle operator.
- Additionally, the term “insurance policy” or “vehicle insurance policy,” as used herein, generally refers to a contract between an insurer and an insured. In exchange for payments from the insured, the insurer pays for damages to the insured which are caused by covered perils, acts, or events as specified by the language of the insurance policy. The payments from the insured are generally referred to as “premiums,” and typically are paid by or on behalf of the insured upon purchase of the insurance policy or over time at periodic intervals. Although insurance policy premiums are typically associated with an insurance policy covering a specified period of time, they may likewise be associated with other measures of a duration of an insurance policy, such as a specified distance traveled or a specified number of trips. The amount of the damages payment is generally referred to as a “coverage amount” or a “face amount” of the insurance policy. An insurance policy may remain (or have a status or state of) “in-force” while premium payments are made during the term or length of coverage of the policy as indicated in the policy. An insurance policy may “lapse” (or have a status or state of “lapsed”), for example, when the parameters of the insurance policy have expired, when premium payments are not being paid, when a cash value of a policy falls below an amount specified in the policy, or if the insured or the insurer cancels the policy.
- The terms “insurer,” “insuring party,” and “insurance provider” are used interchangeably herein to generally refer to a party or entity (e.g., a business or other organizational entity) that provides insurance products, e.g., by offering and issuing insurance policies. Typically, but not necessarily, an insurance provider may be an insurance company. The terms “insured,” “insured party,” “policyholder,” and “customer” are used interchangeably herein to refer to a person, party, or entity (e.g., a business or other organizational entity) that is covered by the insurance policy, e.g., whose insured article or entity is covered by the policy. Typically, a person or customer (or an agent of the person or customer) of an insurance provider fills out an application for an insurance policy. In some cases, the data for an application may be automatically determined or already associated with a potential customer. The application may undergo underwriting to assess the eligibility of the party and/or desired insured article or entity to be covered by the insurance policy, and, in some cases, to determine any specific terms or conditions that are to be associated with the insurance policy, e.g., amount of the premium, riders or exclusions, waivers, and the like. Upon approval by underwriting, acceptance of the applicant to the terms or conditions, and payment of the initial premium, the insurance policy may be in-force, (i.e., the policyholder is enrolled).
- Although the exemplary embodiments discussed herein relate to automobile insurance policies, it should be appreciated that an insurance provider may offer or provide one or more different types of insurance policies. Other types of insurance policies may include, for example, commercial automobile insurance, inland marine and mobile property insurance, ocean marine insurance, boat insurance, motorcycle insurance, farm vehicle insurance, aircraft or aviation insurance, and other types of insurance products.
- Although the text herein sets forth a detailed description of numerous different embodiments, it should be understood that the legal scope of the invention is defined by the words of the claims set forth at the end of this patent. The detailed description is to be construed as exemplary only and does not describe every possible embodiment, as describing every possible embodiment would be impractical, if not impossible. One could implement numerous alternate embodiments, using either current technology or technology developed after the filing date of this patent, which would still fall within the scope of the claims.
- In one aspect, autonomous or semi-autonomous vehicle; telematics; interconnected home; mobile device; and/or other data, including that discussed elsewhere herein, may be collected or received by an insurance provider remote server, such as via direct or indirect wireless communication or data transmission, after a customer affirmatively consents or otherwise opts into an insurance discount, reward, or other program. The insurance provider may then analyze the data received with the customer's permission to provide benefits to the customer. As a result, risk averse customers may receive insurance discounts or other insurance cost savings based upon data that reflects low risk behavior and/or technology that mitigates or prevents risk to (i) insured assets, such as autonomous or semi-autonomous vehicles, and/or (ii) autonomous or semi-autonomous vehicle operators or passengers.
- It should also be understood that, unless a term is expressly defined in this patent using the sentence “As used herein, the term ‘______’ is hereby defined to mean . . . ” or a similar sentence, there is no intent to limit the meaning of that term, either expressly or by implication, beyond its plain or ordinary meaning, and such term should not be interpreted to be limited in scope based upon any statement made in any section of this patent (other than the language of the claims). To the extent that any term recited in the claims at the end of this disclosure is referred to in this disclosure in a manner consistent with a single meaning, that is done for sake of clarity only so as to not confuse the reader, and it is not intended that such claim term be limited, by implication or otherwise, to that single meaning. Finally, unless a claim element is defined by reciting the word “means” and a function without the recital of any structure, it is not intended that the scope of any claim element be interpreted based upon the application of 35 U.S.C. § 112(f).
- Throughout this specification, plural instances may implement components, operations, or structures described as a single instance. Although individual operations of one or more methods are illustrated and described as separate operations, one or more of the individual operations may be performed concurrently, and nothing requires that the operations be performed in the order illustrated. Structures and functionality presented as separate components in example configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements fall within the scope of the subject matter herein.
- Additionally, certain embodiments are described herein as including logic or a number of routines, subroutines, applications, or instructions. These may constitute either software (code embodied on a non-transitory, tangible machine-readable medium) or hardware. In hardware, the routines, etc., are tangible units capable of performing certain operations and may be configured or arranged in a certain manner. In example embodiments, one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware modules of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware module that operates to perform certain operations as described herein.
- In various embodiments, a hardware module may be implemented mechanically or electronically. For example, a hardware module may comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC) to perform certain operations. A hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. It will be appreciated that the decision to implement a hardware module mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.
- Accordingly, the term “hardware” should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. Considering embodiments in which hardware is temporarily configured (e.g., programmed), the hardware need not be configured or instantiated at any one instance in time. Software may accordingly configure a processor, for example, to constitute a particular hardware module at one instance of time and to constitute a different hardware module at a different instance of time. Hardware elements can provide information to, and receive information from, other hardware elements. Accordingly, the described hardware may be regarded as being communicatively coupled.
- The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented modules that operate to perform one or more operations or functions. The modules referred to herein may, in some example embodiments, comprise processor-implemented modules. Similarly, the methods or routines described herein may be at least partially processor-implemented. The performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processor or processors may be located in a single location (e.g., within a home environment, an office environment or as a server farm), while in other embodiments the processors may be distributed across a number of locations.
- Unless specifically stated otherwise, discussions herein using words such as “processing,” “computing,” “calculating,” “determining,” “presenting,” “displaying,” or the like may refer to actions or processes of a machine (e.g., a computer) that manipulates or transforms data represented as physical (e.g., electronic, magnetic, or optical) quantities within one or more memories (e.g., volatile memory, non-volatile memory, or a combination thereof), registers, or other machine components that receive, store, transmit, or display information. As used herein any reference to “one embodiment” or “an embodiment” means that a particular element, feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment. Some embodiments may be described using the expression “coupled” and “connected” along with their derivatives. For example, some embodiments may be described using the term “coupled” to indicate that two or more elements are in direct physical or electrical contact. The term “coupled,” however, may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other. The embodiments are not limited in this context.
- As used herein, the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having” or any other variation thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Further, unless expressly stated to the contrary, “or” refers to an inclusive or and not to an exclusive or. In addition, use of the “a” or “an” are employed to describe elements and components of the embodiments herein. This is done merely for convenience and to give a general sense of the description. In this description, and the claims that follow, the singular also includes the plural unless it is obvious that it is meant otherwise. This detailed description is to be construed as exemplary only and does not describe every possible embodiment, as describing every possible embodiment would be impractical, if not impossible. One could implement numerous alternate embodiments, using either current technology or technology developed after the filing date of this application.
- Upon reading this disclosure, those of skill in the art will appreciate still additional alternative structural and functional designs for system and a method for assigning mobile device data to a vehicle through the disclosed principles herein. Thus, while particular embodiments and applications have been illustrated and described, it is to be understood that the disclosed embodiments are not limited to the precise construction and components disclosed herein. Various modifications, changes and variations, which will be apparent to those skilled in the art, may be made in the arrangement, operation and details of the method and apparatus disclosed herein without departing from the spirit and scope defined in the appended claims.
- The particular features, structures, or characteristics of any specific embodiment may be combined in any suitable manner and in any suitable combination with one or more other embodiments, including the use of selected features without corresponding use of other features. In addition, many modifications may be made to adapt a particular application, situation or material to the essential scope and spirit of the present invention. It is to be understood that other variations and modifications of the embodiments of the present invention described and illustrated herein are possible in light of the teachings herein and are to be considered part of the spirit and scope of the present invention.
Claims (20)
1. A computer-implemented method for identifying and responding to damage to an autonomous or semi-autonomous vehicle relating to a collision or other loss, comprising:
collecting, by one or more processors, pre-event sensor data generated by a plurality of sensors disposed at a plurality of areas within the autonomous or semi-autonomous vehicle during operation of the autonomous or semi-autonomous vehicle occurring at a first time period prior to an event causing the damage, wherein the plurality of sensors are used by one or more autonomous operation features to control operation of the autonomous or semi-autonomous vehicle;
generating, at one or more processors, an indication of damage to the autonomous or semi-autonomous vehicle resulting from the event causing the damage;
collecting, by one or more processors, post-event sensor data generated by two or more of the plurality of sensors disposed within the autonomous or semi-autonomous vehicle during a second time period following a completion of the event causing the damage;
determining, by the one or more processors, an impaired operating status of two or more of the plurality of sensors based on sensor data generated by the plurality of sensors, including the pre-event sensor data and the post-event sensor data;
accessing stored data including identification of the two or more sensors determined to have the impaired operating status;
determining, by one or more processors based on the accessed data, a likely type and extent of the damage, including determining damaged areas of the vehicle, caused by the event based on the determined impaired operating status of the two or more of the plurality of sensors and a determination of a proximity of the two or more sensors to one another; and
determining, by one or more processors, one or more repairs associated with the damage based upon the likely type and extent of the damage.
2. The computer-implemented method of claim 1 , further comprising: determining, by one or more processors, an expected cost associated with the one or more repairs.
3. The computer-implemented method of claim 2 , wherein determining the one or more repairs associated with the damage further includes determining at least one specialty repair service and wherein determining the expected cost associated with the one or more repairs includes determining a cost associated with the at least one specialty repair service.
4. The computer-implemented method of claim 2 , wherein determining the expected cost includes determining a range of expected costs associated with the one or more repairs.
5. The computer-implemented method of claim 4 , further comprising:
determining, by one or more processors, a plurality of expected costs within the determined range, wherein each of the expected costs indicates a total cost for all of the one or more repairs associated with the damage;
determining, by one or more processors, a maximum payment for the one or more repairs associated with the damage based upon the determined range of expected costs; and
causing, by one or more processors, the plurality of expected costs and the maximum payment to be presented to an insurance customer associated with the autonomous or semi-autonomous vehicle.
6. The computer-implemented method of claim 2 , further comprising:
causing, by one or more processors, the expected cost associated with the one or more repairs to be presented to an insurance customer associated with the autonomous or semi-autonomous vehicle;
causing, by one or more processors, a plurality of options regarding the one or more repairs to be presented to the insurance customer;
receiving, at one or more processors, a selection by the insurance customer of one or more of the presented plurality of options; and
causing, by one or more processors, a payment to be made based upon the received selection to at least one of the following: the insurance customer, a beneficiary of an insurance policy associated with the insurance customer, or a repair facility.
7. The computer-implemented method of claim 6 , wherein the plurality of options regarding the one or more repairs includes one or more options to have the one or more repairs performed at one or more repair facilities.
8. The computer-implemented method of claim 7 , wherein the one or more options to have the one or more repairs performed at one or more repair facilities include one or more cost estimates based upon the likely type and extent of the damage.
9. The computer-implemented method of claim 7 , wherein the one or more options to have the one or more repairs performed at one or more repair facilities include one or more estimates of time required for the one or more repairs.
10. A computer system for identifying and responding to damage to an autonomous or semi-autonomous vehicle relating to a collision or other loss, comprising:
one or more processors;
a plurality of sensors disposed at a plurality of areas within the autonomous or semi-autonomous vehicle and communicatively connected to the one or more processors; and
a program memory coupled to the one or more processors and storing executable instructions that when executed by the one or more processors cause the computer system to:
collect pre-event sensor data generated by the plurality of sensors during operation of the autonomous or semi-autonomous vehicle occurring at a first time period prior to an event causing the damage, wherein the plurality of sensors are used by one or more autonomous operation features to control operation of the autonomous or semi-autonomous vehicle;
generate an indication of damage to the autonomous or semi-autonomous vehicle resulting from the event causing the damage;
collect post-event sensor data generated by two or more of the plurality of sensors during a second time period following a completion of the event causing the damage;
determine an impaired operating status of two or more of the plurality of sensors based on sensor data generated by the plurality of sensors, including the pre-event sensor data and the post-event sensor data;
access stored data including identification of the two or more sensors determined to have the impaired operating status;
determine a likely type and extent of the damage based upon the accessed data, including determining damaged areas of the vehicle, caused by the event based on the determined impaired operating status of the two or more of the plurality of sensors and a proximity of the two or more sensors to one another; and
determine one or more repairs associated with the damage based upon the likely type and extent of the damage.
11. The computer system of claim 10 , wherein the executable instructions further cause the computer system to determine an expected cost associated with the one or more repairs, including determining a range of expected costs associated with the one or more repairs based upon information regarding actual costs of repairs to a plurality of other vehicles.
12. The computer system of claim 11 , wherein the program memory further includes executable instructions that cause the computer system to:
determine a plurality of expected costs within the determined range, wherein each of the expected costs indicates a total cost for all of the one or more repairs associated with the damage;
determine a maximum payment for the one or more repairs associated with the damage based upon the determined range of expected costs; and
cause the plurality of expected costs and the maximum payment to be presented to an insurance customer associated with the autonomous or semi-autonomous vehicle.
13. The computer system of claim 10 , wherein the program memory further includes executable instructions that cause the computer system to:
determine an expected cost associated with the one or more repairs;
cause the expected cost associated with the one or more repairs to be presented to an insurance customer associated with the autonomous or semi-autonomous vehicle;
cause a plurality of options regarding the one or more repairs to be presented to the insurance customer;
receive a selection by the insurance customer of one or more of the presented plurality of options;
cause a payment to be made based upon the received selection to at least one of the following: the insurance customer, a beneficiary of an insurance policy associated with the insurance customer, or a repair facility.
14. The computer system of claim 13 , wherein the plurality of options regarding the one or more repairs includes one or more options to have the one or more repairs performed at one or more repair facilities.
15. The computer system of claim 14 , wherein the one or more options to have the one or more repairs performed at one or more repair facilities include one or more of the following: one or more cost estimates based upon the likely type and extent of the damage or one or more estimates of time required for the one or more repairs.
16. A tangible, non-transitory computer-readable medium storing executable instructions for identifying and responding to damage to an autonomous or semi-autonomous vehicle relating to a collision or other loss that, when executed by at least one processor of a computer system, cause the computer system to:
collect pre-event sensor data generated by a plurality of sensors disposed at a plurality of areas within the autonomous or semi-autonomous vehicle during operation of the autonomous or semi-autonomous vehicle occurring at a first time period prior to an event causing the damage, wherein the plurality of sensors are used by one or more autonomous operation features to control operation of the autonomous or semi-autonomous vehicle;
generate an indication of damage to the autonomous or semi-autonomous vehicle resulting from the event causing the damage;
collect post-event sensor data generated by two or more of the plurality of sensors disposed within the autonomous or semi-autonomous vehicle during a second time period following a completion of the event causing the damage;
determine an impaired operating status of two or more of the plurality of sensors based on sensor data generated by the plurality of sensors, including the pre-event sensor data and the post-event sensor data;
access stored data including identification of the two or more sensors determined to have the impaired operating status;
determine a likely type and extent of the damage based on the accessed data, including determining damaged areas of the vehicle, caused by the event based on the determined impaired operating status of the two or more of the plurality of sensors and a proximity of the two or more sensors to one another; and
determine one or more repairs associated with the damage based upon the likely type and extent of the damage.
17. The tangible, non-transitory computer-readable medium of claim 16 , wherein the executable instructions further cause the computer system to determine an expected cost associated with the one or more repairs, including determining a range of expected costs associated with the one or more repairs based upon information regarding actual costs of repairs to a plurality of other vehicles.
18. The tangible, non-transitory computer-readable medium of claim 17 , further comprising executable instructions that cause the computer system to:
determine a plurality of expected costs within the determined range, wherein each of the expected costs indicates a total cost for all of the one or more repairs associated with the damage;
determine a maximum payment for the one or more repairs associated with the damage based upon the determined range of expected costs; and
cause the plurality of expected costs and the maximum payment to be presented to an insurance customer associated with the autonomous or semi-autonomous vehicle.
19. The tangible, non-transitory computer-readable medium of claim 16 , further comprising executable instructions that cause the computer system to:
determine an expected cost associated with the one or more repairs;
cause the expected cost associated with the one or more repairs to be presented to an insurance customer associated with the autonomous or semi-autonomous vehicle;
cause a plurality of options regarding the one or more repairs to be presented to the insurance customer;
receive a selection by the insurance customer of one or more of the presented plurality of options;
cause a payment to be made based upon the received selection to at least one of the following: the insurance customer, a beneficiary of an insurance policy associated with the insurance customer, or a repair facility.
20. The tangible, non-transitory computer-readable medium of claim 19 , wherein the plurality of options regarding the one or more repairs includes one or more options to have the one or more repairs performed at one or more repair facilities and further include one or more of the following: one or more cost estimates based upon the likely type and extent of the damage or one or more estimates of time required for the one or more repairs.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/934,357 US20210118249A1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle salvage and repair |
Applications Claiming Priority (14)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201462079533P | 2014-11-13 | 2014-11-13 | |
US201562103907P | 2015-01-15 | 2015-01-15 | |
US201562103893P | 2015-01-15 | 2015-01-15 | |
US201562103895P | 2015-01-15 | 2015-01-15 | |
US201562103914P | 2015-01-15 | 2015-01-15 | |
US201562103856P | 2015-01-15 | 2015-01-15 | |
US201562103836P | 2015-01-15 | 2015-01-15 | |
US201562103831P | 2015-01-15 | 2015-01-15 | |
US201562103891P | 2015-01-15 | 2015-01-15 | |
US201562103855P | 2015-01-15 | 2015-01-15 | |
US201562103838P | 2015-01-15 | 2015-01-15 | |
US201562103911P | 2015-01-15 | 2015-01-15 | |
US201562103840P | 2015-01-15 | 2015-01-15 | |
US14/934,357 US20210118249A1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle salvage and repair |
Publications (1)
Publication Number | Publication Date |
---|---|
US20210118249A1 true US20210118249A1 (en) | 2021-04-22 |
Family
ID=61872545
Family Applications (42)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/934,357 Abandoned US20210118249A1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle salvage and repair |
US14/934,326 Active 2037-05-03 US10431018B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle operating status assessment |
US14/934,388 Active 2037-06-21 US10416670B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle control assessment and selection |
US14/934,355 Active 2037-01-22 US10915965B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle insurance based upon usage |
US14/934,385 Active 2037-04-03 US10166994B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle operating status assessment |
US14/934,343 Active 2037-02-27 US10157423B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle operating style and mode monitoring |
US14/934,361 Active US11127290B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle infrastructure communication device |
US14/934,393 Active 2037-11-10 US10266180B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle control assessment and selection |
US14/934,333 Active 2038-03-30 US10336321B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle control assessment and selection |
US14/934,400 Active 2037-09-14 US10241509B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle control assessment and selection |
US14/934,347 Active 2036-01-11 US9946531B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle software version assessment |
US14/934,339 Active 2037-05-02 US10246097B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle operator identification |
US14/934,371 Active 2036-03-12 US10007263B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle accident and emergency response |
US14/934,352 Active 2037-01-06 US10831204B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle automatic parking |
US14/934,381 Abandoned US20200219197A1 (en) | 2014-11-13 | 2015-11-06 | Personal insurance policies |
US14/934,405 Active 2036-02-18 US9944282B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle automatic parking |
US15/869,777 Active US10353694B1 (en) | 2014-11-13 | 2018-01-12 | Autonomous vehicle software version assessment |
US15/895,533 Active US10821971B1 (en) | 2014-11-13 | 2018-02-13 | Autonomous vehicle automatic parking |
US15/935,556 Active 2036-02-25 US10831191B1 (en) | 2014-11-13 | 2018-03-26 | Autonomous vehicle accident and emergency response |
US16/170,130 Active 2036-04-02 US10943303B1 (en) | 2014-11-13 | 2018-10-25 | Autonomous vehicle operating style and mode monitoring |
US16/178,809 Active 2036-02-05 US10940866B1 (en) | 2014-11-13 | 2018-11-02 | Autonomous vehicle operating status assessment |
US16/238,911 Active 2036-11-12 US11175660B1 (en) | 2014-11-13 | 2019-01-03 | Autonomous vehicle control assessment and selection |
US16/266,490 Active US11014567B1 (en) | 2014-11-13 | 2019-02-04 | Autonomous vehicle operator identification |
US16/266,162 Active 2036-10-10 US11173918B1 (en) | 2014-11-13 | 2019-02-04 | Autonomous vehicle control assessment and selection |
US16/406,418 Active US10824415B1 (en) | 2014-11-13 | 2019-05-08 | Autonomous vehicle software version assessment |
US16/418,385 Active 2036-10-09 US11247670B1 (en) | 2014-11-13 | 2019-05-21 | Autonomous vehicle control assessment and selection |
US16/509,605 Active US10824144B1 (en) | 2014-11-13 | 2019-07-12 | Autonomous vehicle control assessment and selection |
US16/540,545 Active US11532187B1 (en) | 2014-11-13 | 2019-08-14 | Autonomous vehicle operating status assessment |
US16/697,396 Active 2035-12-22 US11720968B1 (en) | 2014-11-13 | 2019-11-27 | Autonomous vehicle insurance based upon usage |
US16/750,038 Active 2036-02-10 US11500377B1 (en) | 2014-11-13 | 2020-01-23 | Autonomous vehicle control assessment and selection |
US16/810,375 Active 2036-04-06 US11393041B1 (en) | 2014-11-13 | 2020-03-05 | Autonomous vehicle insurance based upon usage |
US16/914,337 Active 2036-07-29 US11740885B1 (en) | 2014-11-13 | 2020-06-27 | Autonomous vehicle software version assessment |
US17/074,397 Active US11748085B2 (en) | 2014-11-13 | 2020-10-19 | Autonomous vehicle operator identification |
US17/073,823 Abandoned US20210031756A1 (en) | 2014-11-13 | 2020-10-19 | Autonomous vehicle automatic parking |
US17/075,828 Active 2036-01-31 US11494175B2 (en) | 2014-11-13 | 2020-10-21 | Autonomous vehicle operating status assessment |
US17/078,659 Active 2036-07-29 US11645064B2 (en) | 2014-11-13 | 2020-10-23 | Autonomous vehicle accident and emergency response |
US17/078,640 Active 2037-02-11 US11726763B2 (en) | 2014-11-13 | 2020-10-23 | Autonomous vehicle automatic parking |
US17/572,156 Active US11977874B2 (en) | 2014-11-13 | 2022-01-10 | Autonomous vehicle control assessment and selection |
US17/847,444 Pending US20220318924A1 (en) | 2014-11-13 | 2022-06-23 | Autonomous vehicle insurance based upon usage |
US17/963,421 Active US11954482B2 (en) | 2014-11-13 | 2022-10-11 | Autonomous vehicle control assessment and selection |
US17/975,234 Pending US20230053773A1 (en) | 2014-11-13 | 2022-10-27 | Autonomous vehicle automatic parking |
US17/985,944 Pending US20230070573A1 (en) | 2014-11-13 | 2022-11-14 | Autonomous Vehicle Operating Status Assessment |
Family Applications After (41)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/934,326 Active 2037-05-03 US10431018B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle operating status assessment |
US14/934,388 Active 2037-06-21 US10416670B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle control assessment and selection |
US14/934,355 Active 2037-01-22 US10915965B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle insurance based upon usage |
US14/934,385 Active 2037-04-03 US10166994B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle operating status assessment |
US14/934,343 Active 2037-02-27 US10157423B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle operating style and mode monitoring |
US14/934,361 Active US11127290B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle infrastructure communication device |
US14/934,393 Active 2037-11-10 US10266180B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle control assessment and selection |
US14/934,333 Active 2038-03-30 US10336321B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle control assessment and selection |
US14/934,400 Active 2037-09-14 US10241509B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle control assessment and selection |
US14/934,347 Active 2036-01-11 US9946531B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle software version assessment |
US14/934,339 Active 2037-05-02 US10246097B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle operator identification |
US14/934,371 Active 2036-03-12 US10007263B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle accident and emergency response |
US14/934,352 Active 2037-01-06 US10831204B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle automatic parking |
US14/934,381 Abandoned US20200219197A1 (en) | 2014-11-13 | 2015-11-06 | Personal insurance policies |
US14/934,405 Active 2036-02-18 US9944282B1 (en) | 2014-11-13 | 2015-11-06 | Autonomous vehicle automatic parking |
US15/869,777 Active US10353694B1 (en) | 2014-11-13 | 2018-01-12 | Autonomous vehicle software version assessment |
US15/895,533 Active US10821971B1 (en) | 2014-11-13 | 2018-02-13 | Autonomous vehicle automatic parking |
US15/935,556 Active 2036-02-25 US10831191B1 (en) | 2014-11-13 | 2018-03-26 | Autonomous vehicle accident and emergency response |
US16/170,130 Active 2036-04-02 US10943303B1 (en) | 2014-11-13 | 2018-10-25 | Autonomous vehicle operating style and mode monitoring |
US16/178,809 Active 2036-02-05 US10940866B1 (en) | 2014-11-13 | 2018-11-02 | Autonomous vehicle operating status assessment |
US16/238,911 Active 2036-11-12 US11175660B1 (en) | 2014-11-13 | 2019-01-03 | Autonomous vehicle control assessment and selection |
US16/266,490 Active US11014567B1 (en) | 2014-11-13 | 2019-02-04 | Autonomous vehicle operator identification |
US16/266,162 Active 2036-10-10 US11173918B1 (en) | 2014-11-13 | 2019-02-04 | Autonomous vehicle control assessment and selection |
US16/406,418 Active US10824415B1 (en) | 2014-11-13 | 2019-05-08 | Autonomous vehicle software version assessment |
US16/418,385 Active 2036-10-09 US11247670B1 (en) | 2014-11-13 | 2019-05-21 | Autonomous vehicle control assessment and selection |
US16/509,605 Active US10824144B1 (en) | 2014-11-13 | 2019-07-12 | Autonomous vehicle control assessment and selection |
US16/540,545 Active US11532187B1 (en) | 2014-11-13 | 2019-08-14 | Autonomous vehicle operating status assessment |
US16/697,396 Active 2035-12-22 US11720968B1 (en) | 2014-11-13 | 2019-11-27 | Autonomous vehicle insurance based upon usage |
US16/750,038 Active 2036-02-10 US11500377B1 (en) | 2014-11-13 | 2020-01-23 | Autonomous vehicle control assessment and selection |
US16/810,375 Active 2036-04-06 US11393041B1 (en) | 2014-11-13 | 2020-03-05 | Autonomous vehicle insurance based upon usage |
US16/914,337 Active 2036-07-29 US11740885B1 (en) | 2014-11-13 | 2020-06-27 | Autonomous vehicle software version assessment |
US17/074,397 Active US11748085B2 (en) | 2014-11-13 | 2020-10-19 | Autonomous vehicle operator identification |
US17/073,823 Abandoned US20210031756A1 (en) | 2014-11-13 | 2020-10-19 | Autonomous vehicle automatic parking |
US17/075,828 Active 2036-01-31 US11494175B2 (en) | 2014-11-13 | 2020-10-21 | Autonomous vehicle operating status assessment |
US17/078,659 Active 2036-07-29 US11645064B2 (en) | 2014-11-13 | 2020-10-23 | Autonomous vehicle accident and emergency response |
US17/078,640 Active 2037-02-11 US11726763B2 (en) | 2014-11-13 | 2020-10-23 | Autonomous vehicle automatic parking |
US17/572,156 Active US11977874B2 (en) | 2014-11-13 | 2022-01-10 | Autonomous vehicle control assessment and selection |
US17/847,444 Pending US20220318924A1 (en) | 2014-11-13 | 2022-06-23 | Autonomous vehicle insurance based upon usage |
US17/963,421 Active US11954482B2 (en) | 2014-11-13 | 2022-10-11 | Autonomous vehicle control assessment and selection |
US17/975,234 Pending US20230053773A1 (en) | 2014-11-13 | 2022-10-27 | Autonomous vehicle automatic parking |
US17/985,944 Pending US20230070573A1 (en) | 2014-11-13 | 2022-11-14 | Autonomous Vehicle Operating Status Assessment |
Country Status (1)
Country | Link |
---|---|
US (42) | US20210118249A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11307577B2 (en) * | 2016-03-08 | 2022-04-19 | Toyota Jidosha Kabushiki Kaisha | Autonomous driving control device |
US20230028145A1 (en) * | 2021-07-26 | 2023-01-26 | Toyota Jidosha Kabushiki Kaisha | Information processing device, reward determination method, and storage medium |
Families Citing this family (285)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10657597B1 (en) * | 2012-02-17 | 2020-05-19 | United Services Automobile Association (Usaa) | Systems and methods for dynamic insurance premiums |
US10176517B2 (en) * | 2014-03-13 | 2019-01-08 | Gary Goralnick | Advertising-integrated car |
US9972054B1 (en) | 2014-05-20 | 2018-05-15 | State Farm Mutual Automobile Insurance Company | Accident fault determination for autonomous vehicles |
US11669090B2 (en) | 2014-05-20 | 2023-06-06 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature monitoring and evaluation of effectiveness |
US10599155B1 (en) | 2014-05-20 | 2020-03-24 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation feature monitoring and evaluation of effectiveness |
US10373259B1 (en) | 2014-05-20 | 2019-08-06 | State Farm Mutual Automobile Insurance Company | Fully autonomous vehicle insurance pricing |
US10354330B1 (en) | 2014-05-20 | 2019-07-16 | State Farm Mutual Automobile Insurance Company | Autonomous feature use monitoring and insurance pricing |
US10475127B1 (en) | 2014-07-21 | 2019-11-12 | State Farm Mutual Automobile Insurance Company | Methods of providing insurance savings based upon telematics and insurance incentives |
US20210118249A1 (en) | 2014-11-13 | 2021-04-22 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle salvage and repair |
WO2016103189A1 (en) * | 2014-12-27 | 2016-06-30 | Husqvarna Ab | Weather collection and aggregation via robotic vehicle |
US9836963B1 (en) | 2015-01-20 | 2017-12-05 | State Farm Mutual Automobile Insurance Company | Determining corrective actions based upon broadcast of telematics data originating from another vehicle |
JP6398758B2 (en) * | 2015-02-03 | 2018-10-03 | 株式会社デンソー | Vehicle communication equipment |
EP3272610B1 (en) * | 2015-04-21 | 2019-07-17 | Panasonic Intellectual Property Management Co., Ltd. | Information processing system, information processing method, and program |
US10077056B1 (en) | 2015-04-24 | 2018-09-18 | State Farm Mutual Automobile Insurance Company | Managing self-driving behavior of autonomous or semi-autonomous vehicle based upon actual driving behavior of driver |
KR101639804B1 (en) * | 2015-05-15 | 2016-07-25 | 주식회사 한글과컴퓨터 | Autonomous smart car capable relief and methot for operating thereof |
US10131362B1 (en) | 2015-06-23 | 2018-11-20 | United Services Automobile Association (Usaa) | Automobile detection system |
DE102015212313A1 (en) * | 2015-07-01 | 2017-01-05 | Robert Bosch Gmbh | Concept for transferring a vehicle from a start position to a destination position |
CN107924632B (en) * | 2015-08-19 | 2022-05-31 | 索尼公司 | Information processing apparatus, information processing method, and program |
US20210272207A1 (en) | 2015-08-28 | 2021-09-02 | State Farm Mutual Automobile Insurance Company | Vehicular driver profiles and discounts |
US10252727B1 (en) * | 2015-09-04 | 2019-04-09 | United Services Automobile Association (Usaa) | Systems and methods for configuring a vehicle |
US11040725B2 (en) | 2015-09-04 | 2021-06-22 | Inrix Inc. | Manual vehicle control notification |
JP6559043B2 (en) * | 2015-10-23 | 2019-08-14 | 本田技研工業株式会社 | Navigation server and navigation system |
US20180272965A1 (en) * | 2015-10-27 | 2018-09-27 | Ford Global Technologies, Llc | Enhanced vehicle system notification |
US10769518B1 (en) * | 2015-12-29 | 2020-09-08 | State Farm Mutual Automobile Insurance Company | Method of controlling for undesired factors in machine learning models |
US10460600B2 (en) | 2016-01-11 | 2019-10-29 | NetraDyne, Inc. | Driver behavior monitoring |
US10134278B1 (en) | 2016-01-22 | 2018-11-20 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle application |
US10747234B1 (en) | 2016-01-22 | 2020-08-18 | State Farm Mutual Automobile Insurance Company | Method and system for enhancing the functionality of a vehicle |
US10324463B1 (en) | 2016-01-22 | 2019-06-18 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle operation adjustment based upon route |
US11441916B1 (en) | 2016-01-22 | 2022-09-13 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle trip routing |
US11719545B2 (en) | 2016-01-22 | 2023-08-08 | Hyundai Motor Company | Autonomous vehicle component damage and salvage assessment |
US11242051B1 (en) | 2016-01-22 | 2022-02-08 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle action communications |
US10395332B1 (en) | 2016-01-22 | 2019-08-27 | State Farm Mutual Automobile Insurance Company | Coordinated autonomous vehicle automatic area scanning |
US11220258B2 (en) | 2016-01-26 | 2022-01-11 | Cambridge Mobile Telematics Inc. | Systems and methods for sensor-based vehicle crash prediction, detection, and reconstruction |
WO2017142935A1 (en) | 2016-02-15 | 2017-08-24 | Allstate Insurance Company | Real time risk assessment and operational changes with semi-autonomous vehicles |
US11250514B2 (en) | 2016-02-15 | 2022-02-15 | Allstate Insurance Company | Early notification of non-autonomous area |
JP6323480B2 (en) | 2016-03-02 | 2018-05-16 | 住友電気工業株式会社 | Program update system, program update method, and computer program |
US20170253237A1 (en) * | 2016-03-02 | 2017-09-07 | Magna Electronics Inc. | Vehicle vision system with automatic parking function |
US11373245B1 (en) * | 2016-03-04 | 2022-06-28 | Allstate Insurance Company | Systems and methods for detecting digital security breaches of connected assets based on location tracking and asset profiling |
US10474168B1 (en) * | 2016-05-16 | 2019-11-12 | United Services Automobile Association | Unmanned vehicle security guard |
EP3469437A4 (en) | 2016-06-13 | 2020-03-25 | Xevo Inc. | Method and system for providing auto space management using virtuous cycle |
JP6778872B2 (en) * | 2016-06-28 | 2020-11-04 | パナソニックIpマネジメント株式会社 | Driving support device and driving support method |
US10832331B1 (en) * | 2016-07-11 | 2020-11-10 | State Farm Mutual Automobile Insurance Company | Systems and methods for allocating fault to autonomous vehicles |
US11119489B1 (en) | 2016-07-13 | 2021-09-14 | United Services Automobile Association (Usaa) | Autonomous vehicle haven seeking system and method |
EP3491358A4 (en) | 2016-07-31 | 2019-07-31 | Netradyne, Inc. | Determining causation of traffic events and encouraging good driving behavior |
US11042938B1 (en) * | 2016-08-08 | 2021-06-22 | Allstate Insurance Company | Driver identity detection and alerts |
US9811085B1 (en) | 2016-08-18 | 2017-11-07 | Allstate Insurance Company | Generating and transmitting parking instructions for autonomous and non-autonomous vehicles |
US11425530B2 (en) * | 2016-08-18 | 2022-08-23 | Allstate Insurance Company | Generating and transmitting parking instructions for autonomous and non-autonomous vehicles |
US20180053237A1 (en) * | 2016-08-18 | 2018-02-22 | Allstate Insurance Company | Generating and Transmitting Parking Instructions for Autonomous and Non-Autonomous Vehicles |
DE102016216520A1 (en) * | 2016-09-01 | 2018-03-01 | Robert Bosch Gmbh | Method and system for operating a vehicle |
US10663965B2 (en) * | 2016-09-01 | 2020-05-26 | Ford Global Technologies, Llc | Permissions for partially autonomous vehicle operation |
US11155267B2 (en) * | 2016-10-11 | 2021-10-26 | Samsung Electronics Co., Ltd. | Mobile sensor platform |
EP3531397B1 (en) * | 2016-10-21 | 2022-07-20 | Mitsubishi Electric Corporation | Autonomous driving support apparatus and autonomous driving support method |
US11024160B2 (en) * | 2016-11-07 | 2021-06-01 | Nio Usa, Inc. | Feedback performance control and tracking |
JP6618455B2 (en) * | 2016-11-28 | 2019-12-11 | 日立オートモティブシステムズ株式会社 | Electronic control device, in-vehicle system, and power supply control method |
US10012993B1 (en) | 2016-12-09 | 2018-07-03 | Zendrive, Inc. | Method and system for risk modeling in autonomous vehicles |
JP6895634B2 (en) * | 2016-12-16 | 2021-06-30 | パナソニックIpマネジメント株式会社 | Information processing systems, information processing methods, and programs |
EP3566201A4 (en) | 2016-12-22 | 2020-11-25 | Xevo Inc. | Method and system for providing artificial intelligence analytic (aia) services for performance prediction |
EP3343306B1 (en) * | 2016-12-28 | 2019-08-07 | Faurecia Automotive Seating, LLC | Occupant-status prediction system |
US10817891B1 (en) * | 2016-12-29 | 2020-10-27 | State Farm Mutual Automobile Insurance Company | Vehicle risk aversion and reward system |
US10202103B2 (en) * | 2016-12-29 | 2019-02-12 | Intel Corporation | Multi-modal context based vehicle theft prevention |
FR3061694B1 (en) * | 2017-01-12 | 2019-05-31 | Valeo Schalter Und Sensoren Gmbh | METHOD FOR CONTROLLING AN AUTONOMOUS MOTOR VEHICLE |
US11321951B1 (en) * | 2017-01-19 | 2022-05-03 | State Farm Mutual Automobile Insurance Company | Apparatuses, systems and methods for integrating vehicle operator gesture detection within geographic maps |
US10585440B1 (en) | 2017-01-23 | 2020-03-10 | Clearpath Robotics Inc. | Systems and methods for using human-operated material-transport vehicles with fleet-management systems |
US11521271B2 (en) * | 2017-02-06 | 2022-12-06 | Allstate Insurance Company | Autonomous vehicle control systems with collision detection and response capabilities |
US10029685B1 (en) * | 2017-02-24 | 2018-07-24 | Speedgauge, Inc. | Vehicle speed limiter |
JP6524129B2 (en) * | 2017-03-07 | 2019-06-05 | 本田技研工業株式会社 | Driving support device |
DE102017203981A1 (en) * | 2017-03-10 | 2018-09-13 | Audi Ag | Method for operating a parking environment in the event of alarm conditions and motor vehicle |
US10521977B2 (en) * | 2017-03-27 | 2019-12-31 | GM Global Technology Operations LLC | Methods and systems for integrated vehicle sensor calibration and maintenance |
JP6722132B2 (en) * | 2017-04-27 | 2020-07-15 | クラリオン株式会社 | Recommended operation output device, recommended operation output method, and recommended operation output system |
US10942525B2 (en) | 2017-05-09 | 2021-03-09 | Uatc, Llc | Navigational constraints for autonomous vehicles |
DE102017110159A1 (en) * | 2017-05-10 | 2018-11-15 | Claas Tractor Sas | Agricultural working machine |
JP6509940B2 (en) * | 2017-05-10 | 2019-05-08 | 本田技研工業株式会社 | Driving support device and driving support method |
DE102017208163A1 (en) * | 2017-05-15 | 2018-11-15 | Robert Bosch Gmbh | Method and device for operating an automated vehicle |
US11080806B2 (en) | 2017-05-23 | 2021-08-03 | Uber Technologies, Inc. | Non-trip risk matching and routing for on-demand transportation services |
US11282009B2 (en) | 2017-05-23 | 2022-03-22 | Uatc, Llc | Fleet utilization efficiency for on-demand transportation services |
US10789835B2 (en) | 2017-05-23 | 2020-09-29 | Uatc, Llc | Fractional risk performance evaluation for autonomous vehicles |
US10697789B2 (en) | 2017-05-23 | 2020-06-30 | Uatc, Llc | Individualized risk routing for human drivers |
US10884902B2 (en) * | 2017-05-23 | 2021-01-05 | Uatc, Llc | Software version verification for autonomous vehicles |
US11288612B2 (en) | 2017-05-23 | 2022-03-29 | Uatc, Llc | Generalized risk routing for human drivers |
US10762447B2 (en) * | 2017-05-23 | 2020-09-01 | Uatc, Llc | Vehicle selection for on-demand transportation services |
US11282016B2 (en) | 2017-05-23 | 2022-03-22 | Uatc, Llc | Individualized risk vehicle matching for an on-demand transportation service |
US10501091B2 (en) * | 2017-05-23 | 2019-12-10 | Uber Technologies, Inc. | Software version and mode switching for autonomous vehicles |
US10489721B2 (en) | 2017-05-23 | 2019-11-26 | Uatc, Llc | Path segment risk regression system for on-demand transportation services |
US10262471B2 (en) | 2017-05-23 | 2019-04-16 | Uber Technologies, Inc. | Autonomous vehicle degradation level monitoring |
CN109032102B (en) * | 2017-06-09 | 2020-12-18 | 百度在线网络技术(北京)有限公司 | Unmanned vehicle testing method, device, equipment and storage medium |
DE102017210109A1 (en) | 2017-06-16 | 2018-12-20 | Volkswagen Aktiengesellschaft | A method of assisting a maneuvering process of a motor vehicle and system for assisting a maneuvering operation of a motor vehicle |
KR102286050B1 (en) * | 2017-06-23 | 2021-08-03 | 현대자동차주식회사 | Method for preventing diagnostic errors in vehicle network and apparatus for the same |
EP3643574B1 (en) * | 2017-06-23 | 2021-08-04 | Nissan Motor Co., Ltd. | Parking control method and parking control device |
EP3421308B1 (en) * | 2017-06-29 | 2021-08-11 | Volvo Car Corporation | Method and vehicle for activating an autonomous braking maneuver |
CN112204518A (en) * | 2017-07-21 | 2021-01-08 | 苹果公司 | Multi-radio interface for software reconfiguration |
US10922424B2 (en) * | 2017-08-17 | 2021-02-16 | M2MD Technologies, Inc. | Method and system for securely providing vehicle services data to a vehicle |
WO2019045694A1 (en) | 2017-08-29 | 2019-03-07 | Ford Global Technologies, Llc | Vehicle security systems and methods |
US11386498B1 (en) | 2017-09-06 | 2022-07-12 | State Farm Mutual Automobile Insurance Company | Using historical data for subrogation on a distributed ledger |
US10872381B1 (en) | 2017-09-06 | 2020-12-22 | State Farm Mutual Automobile Insurance Company | Evidence oracles |
US11416942B1 (en) | 2017-09-06 | 2022-08-16 | State Farm Mutual Automobile Insurance Company | Using a distributed ledger to determine fault in subrogation |
US10891694B1 (en) | 2017-09-06 | 2021-01-12 | State Farm Mutual Automobile Insurance Company | Using vehicle mode for subrogation on a distributed ledger |
US10984481B1 (en) * | 2017-09-15 | 2021-04-20 | United Services Automobile Association (Usaa) | Systems and methods for determining premium rate for semi-autonomous and/or autonomous vehicles |
US10957201B2 (en) * | 2017-09-15 | 2021-03-23 | Qualcomm Incorporated | System and method for relative positioning based safe autonomous driving |
EP3459827B1 (en) * | 2017-09-25 | 2022-07-27 | Volvo Car Corporation | Method and system for automated parking of a vehicle |
WO2019068042A1 (en) | 2017-09-29 | 2019-04-04 | Netradyne Inc. | Multiple exposure event determination |
US10580304B2 (en) * | 2017-10-02 | 2020-03-03 | Ford Global Technologies, Llc | Accelerometer-based external sound monitoring for voice controlled autonomous parking |
JP7095968B2 (en) * | 2017-10-02 | 2022-07-05 | トヨタ自動車株式会社 | Management device |
US10545751B2 (en) * | 2017-10-03 | 2020-01-28 | Accenture Global Solutions Limited | Automated usage driven engineering |
WO2019075341A1 (en) * | 2017-10-12 | 2019-04-18 | Netradyne Inc. | Detection of driving actions that mitigate risk |
WO2019079807A1 (en) * | 2017-10-20 | 2019-04-25 | Zendrive, Inc. | Method and system for vehicular-related communications |
US11334951B1 (en) * | 2017-10-27 | 2022-05-17 | Wells Fargo Bank, N.A. | Trip-segment payments for vehicle insurance |
US10802486B1 (en) * | 2017-11-01 | 2020-10-13 | United Services Automobile Association (Usaa) | Autonomous vehicle repair |
WO2019087379A1 (en) * | 2017-11-06 | 2019-05-09 | 本田技研工業株式会社 | Vehicle, vehicle monitoring server, vehicle monitoring system, and vehicle monitoring method |
US11273778B1 (en) * | 2017-11-09 | 2022-03-15 | Amazon Technologies, Inc. | Vehicle voice user interface |
JP6859931B2 (en) * | 2017-11-15 | 2021-04-14 | トヨタ自動車株式会社 | Autonomous driving system |
JP6907895B2 (en) | 2017-11-15 | 2021-07-21 | トヨタ自動車株式会社 | Autonomous driving system |
EP3717996B1 (en) | 2017-11-27 | 2023-12-20 | Zendrive, Inc. | System and method for vehicle sensing and analysis |
DE102017129787A1 (en) * | 2017-12-13 | 2019-06-13 | HELLA GmbH & Co. KGaA | Vehicle with a camera for detecting a body part of a user and method for the operation of the vehicle |
US20190187691A1 (en) | 2017-12-18 | 2019-06-20 | Steeringz, Inc. | Safety of autonomous vehicles by remote support request |
US11104331B2 (en) * | 2017-12-28 | 2021-08-31 | Intel Corporation | Autonomous techniques for vehicles with balance input |
US10642269B2 (en) * | 2018-01-03 | 2020-05-05 | Denso International America, Inc. | Vehicle localization system |
US10894544B2 (en) * | 2018-01-04 | 2021-01-19 | International Business Machines Corporation | Protective action for protecting autonomous vehicles from impending weather conditions |
US10776096B2 (en) * | 2018-01-12 | 2020-09-15 | Blackberry Limited | Method and system for controlling software updates on a network connected device |
EP3514744A1 (en) * | 2018-01-23 | 2019-07-24 | Hitachi, Ltd. | Vehicle operation analysis of a driver |
WO2019144222A1 (en) * | 2018-01-24 | 2019-08-01 | Clearpath Robotics Inc. | Systems and methods for maintaining vehicle state information |
US11059494B1 (en) | 2018-02-15 | 2021-07-13 | State Farm Mutual Automobile Insurance Company | System and method for transferring preferences for autonomous driving |
US11108804B2 (en) * | 2018-02-27 | 2021-08-31 | Blackberry Limited | Providing secure inter-vehicle data communications |
US10495474B2 (en) * | 2018-03-12 | 2019-12-03 | Micron Technology, Inc. | Re-routing autonomous vehicles using dynamic routing and memory management |
US10551835B2 (en) * | 2018-03-12 | 2020-02-04 | Toyota Research Institute | Systems and methods for operator skill mitigation |
US20190291745A1 (en) * | 2018-03-23 | 2019-09-26 | Ford Global Technologies, Llc | Method and apparatus for environment-sensitive selective drive-mode enablement |
US10755492B2 (en) * | 2018-03-28 | 2020-08-25 | Cummins Inc. | Vehicle hazard management system |
US10935974B1 (en) * | 2018-04-19 | 2021-03-02 | State Farm Mutual Automobile Insurance Company | Manual control re-engagement in an autonomous vehicle |
DE102018206720A1 (en) * | 2018-05-02 | 2019-11-07 | Audi Ag | Method for performing a software update in a control unit of a motor vehicle and a correspondingly configured motor vehicle |
US11297089B2 (en) * | 2018-05-02 | 2022-04-05 | Blackberry Limited | Providing secure sensor data to automated machines |
US11245583B2 (en) | 2018-05-03 | 2022-02-08 | Micron Technology, Inc. | Determining whether a vehicle should be configured for a different region |
DE102018207379A1 (en) * | 2018-05-14 | 2019-11-14 | Audi Ag | Method for operating a motor vehicle system on the basis of a user-specific user setting, storage medium, assignment device, motor vehicle and server device for operating on the Internet |
US10953888B2 (en) | 2018-05-22 | 2021-03-23 | International Business Machines Corporation | Autonomous vehicle monitoring |
US10921812B2 (en) * | 2018-05-22 | 2021-02-16 | International Business Machines Corporation | System and method for rendezvous coordination of an autonomous automotive vehicle with an ambulance |
DE102018218845A1 (en) * | 2018-11-05 | 2020-05-07 | Volkswagen Aktiengesellschaft | Motor vehicle |
US11287816B2 (en) | 2018-06-11 | 2022-03-29 | Uatc, Llc | Navigational constraints for autonomous vehicles |
CN109278861B (en) * | 2018-07-05 | 2021-06-11 | 惠州市德赛西威汽车电子股份有限公司 | Steering wheel return-to-normal reminding method and system based on automobile look-around |
US20200017124A1 (en) * | 2018-07-12 | 2020-01-16 | Sf Motors, Inc. | Adaptive driver monitoring for advanced driver-assistance systems |
US11318961B2 (en) * | 2018-07-20 | 2022-05-03 | Lg Electronics Inc. | Robot for vehicle and control method thereof |
US10909866B2 (en) * | 2018-07-20 | 2021-02-02 | Cybernet Systems Corp. | Autonomous transportation system and methods |
JP7225596B2 (en) * | 2018-07-30 | 2023-02-21 | トヨタ自動車株式会社 | Program update system, program update server and vehicle |
US10981578B2 (en) * | 2018-08-02 | 2021-04-20 | GM Global Technology Operations LLC | System and method for hardware verification in an automotive vehicle |
KR102625398B1 (en) * | 2018-08-17 | 2024-01-17 | 현대자동차주식회사 | Vehicle and control method for the same |
US10576994B1 (en) * | 2018-08-22 | 2020-03-03 | Nio Usa, Inc. | Autonomous system operator cognitive state detection and alerting |
JP7107095B2 (en) * | 2018-08-28 | 2022-07-27 | トヨタ自動車株式会社 | Autonomous driving system |
JP7158655B2 (en) * | 2018-08-28 | 2022-10-24 | マツダ株式会社 | Stop support device |
US10943137B2 (en) | 2018-09-12 | 2021-03-09 | Computime Ltd. | Biometric data capturing and analysis |
US11170899B2 (en) * | 2018-09-12 | 2021-11-09 | Computime Ltd. | Biometric data capturing and analysis using a hybrid sensing systems |
US10720058B2 (en) | 2018-09-13 | 2020-07-21 | Volvo Car Corporation | System and method for camera or sensor-based parking spot detection and identification |
EP3624001B1 (en) | 2018-09-13 | 2024-05-01 | Volvo Car Corporation | Methods and systems for parking line marker detection and pairing and parking spot detection and classification |
US10984659B2 (en) | 2018-09-13 | 2021-04-20 | Volvo Car Corporation | Vehicle parking availability map systems and methods |
US10812624B2 (en) * | 2018-09-14 | 2020-10-20 | Cisco Technology, Inc. | Firmware/software over the air (FOTA) scheduling for connected vehicles |
US10650623B2 (en) | 2018-09-18 | 2020-05-12 | Avinew, Inc. | Detecting of automatic driving |
US11273841B2 (en) * | 2018-09-20 | 2022-03-15 | Toyota Research Institute, Inc. | Method and apparatus for spoofing prevention |
US11495028B2 (en) * | 2018-09-28 | 2022-11-08 | Intel Corporation | Obstacle analyzer, vehicle control system, and methods thereof |
KR102628282B1 (en) * | 2018-10-10 | 2024-01-24 | 현대자동차주식회사 | Vehicle and control method thereof |
JP7344009B2 (en) * | 2018-10-17 | 2023-09-13 | パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカ | Information processing device, information processing method and program |
US11700356B2 (en) * | 2018-10-26 | 2023-07-11 | AutoBrains Technologies Ltd. | Control transfer of a vehicle |
US11648951B2 (en) | 2018-10-29 | 2023-05-16 | Motional Ad Llc | Systems and methods for controlling actuators based on load characteristics and passenger comfort |
US10894542B2 (en) * | 2018-10-30 | 2021-01-19 | International Business Machines Corporation | Driving feedback based safety system |
US10793106B2 (en) * | 2018-11-05 | 2020-10-06 | Robert Turley | Automobile tracking and notification device and service |
US11046304B2 (en) | 2018-11-12 | 2021-06-29 | Argo AI, LLC | Rider selectable ride comfort system for autonomous vehicle |
US11378965B2 (en) * | 2018-11-15 | 2022-07-05 | Toyota Research Institute, Inc. | Systems and methods for controlling a vehicle based on determined complexity of contextual environment |
WO2020111090A1 (en) * | 2018-11-28 | 2020-06-04 | 株式会社オートネットワーク技術研究所 | Monitoring device, monitoring program, and monitoring method |
US10729378B2 (en) | 2018-11-30 | 2020-08-04 | Toyota Motor North America, Inc. | Systems and methods of detecting problematic health situations |
CN109615545A (en) * | 2018-12-13 | 2019-04-12 | 平安医疗健康管理股份有限公司 | Special medicine medical insurance pricing method, device, equipment and medium based on data analysis |
US11085779B2 (en) * | 2018-12-14 | 2021-08-10 | Toyota Research Institute, Inc. | Autonomous vehicle route planning |
US11368440B2 (en) * | 2018-12-18 | 2022-06-21 | GM Global Technology Operations LLC | Detecting operation of an autonomous vehicle on an untrusted network |
US11809184B1 (en) * | 2018-12-27 | 2023-11-07 | United Services Automobile Association (Usaa) | Autonomous vehicle mode during unsafe driving conditions |
US10625745B1 (en) * | 2019-01-07 | 2020-04-21 | Sean Tremblay | Automated driver's exam system |
KR102368840B1 (en) * | 2019-01-25 | 2022-03-02 | 한국전자기술연구원 | Connected car big data acquisition device, system and method |
US11285844B2 (en) | 2019-01-31 | 2022-03-29 | Toyota Motor Engineering & Manufacturing North America, Inc. | Vehicle seat with morphing portions |
US11810363B2 (en) | 2019-01-31 | 2023-11-07 | Toyota Motor North America, Inc. | Systems and methods for image processing using mobile devices |
GB2581331B (en) * | 2019-02-05 | 2021-06-02 | Ford Global Tech Llc | A method and system for vehicle protection |
US11526816B2 (en) * | 2019-02-27 | 2022-12-13 | Uber Technologies, Inc. | Context-based remote autonomous vehicle assistance |
CN109949168A (en) * | 2019-02-28 | 2019-06-28 | 中科云创(厦门)科技有限公司 | Data processing method and device applied to property insurance |
JP7218623B2 (en) * | 2019-03-08 | 2023-02-07 | 住友電装株式会社 | VEHICLE UPDATE DEVICE, UPDATE PROCESSING SYSTEM, UPDATE PROCESSING METHOD, AND COMPUTER PROGRAM |
US10885725B2 (en) * | 2019-03-18 | 2021-01-05 | International Business Machines Corporation | Identifying a driving mode of an autonomous vehicle |
US11370330B2 (en) * | 2019-03-22 | 2022-06-28 | Toyota Motor Engineering & Manufacturing North America, Inc. | Vehicle seat with morphing portions |
US11710097B2 (en) | 2019-03-22 | 2023-07-25 | BlueOwl, LLC | Systems and methods for obtaining incident information to reduce fraud |
US11752901B2 (en) | 2019-03-28 | 2023-09-12 | Toyota Motor Engineering & Manufacturing North America, Inc. | Vehicle seat with tilting seat portion |
JP7402861B2 (en) * | 2019-03-28 | 2023-12-21 | パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカ | Information processing method and information processing system |
JP7460044B2 (en) * | 2019-03-29 | 2024-04-02 | インテル・コーポレーション | Autonomous vehicle, and apparatus, program, and computer-readable medium relating to an autonomous vehicle system |
US11321972B1 (en) | 2019-04-05 | 2022-05-03 | State Farm Mutual Automobile Insurance Company | Systems and methods for detecting software interactions for autonomous vehicles within changing environmental conditions |
US11048261B1 (en) | 2019-04-05 | 2021-06-29 | State Farm Mutual Automobile Insurance Company | Systems and methods for evaluating autonomous vehicle software interactions for proposed trips |
US11138814B1 (en) * | 2019-04-10 | 2021-10-05 | State Farm Mutual Automobile Insurance Company | Technology for implementing a reverse communication session for automotive devices |
US10699580B1 (en) | 2019-04-17 | 2020-06-30 | Guident Ltd. | Methods and systems for emergency handoff of an autonomous vehicle |
GB2607172B (en) | 2019-04-25 | 2023-11-01 | Motional Ad Llc | Graphical user interface for display of autonomous vehicle behaviors |
US11472291B2 (en) | 2019-04-25 | 2022-10-18 | Motional Ad Llc | Graphical user interface for display of autonomous vehicle behaviors |
US11385884B2 (en) * | 2019-04-29 | 2022-07-12 | Harman International Industries, Incorporated | Assessing cognitive reaction to over-the-air updates |
US11886390B2 (en) | 2019-04-30 | 2024-01-30 | JFrog Ltd. | Data file partition and replication |
US11386233B2 (en) | 2019-04-30 | 2022-07-12 | JFrog, Ltd. | Data bundle generation and deployment |
US11340894B2 (en) | 2019-04-30 | 2022-05-24 | JFrog, Ltd. | Data file partition and replication |
US11262763B2 (en) | 2019-05-01 | 2022-03-01 | Smartdrive Systems, Inc. | Systems and methods for using risk profiles for creating and deploying new vehicle event definitions to a fleet of vehicles |
US11609579B2 (en) | 2019-05-01 | 2023-03-21 | Smartdrive Systems, Inc. | Systems and methods for using risk profiles based on previously detected vehicle events to quantify performance of vehicle operators |
US11300977B2 (en) * | 2019-05-01 | 2022-04-12 | Smartdrive Systems, Inc. | Systems and methods for creating and using risk profiles for fleet management of a fleet of vehicles |
US11209817B2 (en) * | 2019-05-06 | 2021-12-28 | Argo AI, LLC | Method and system for real-time diagnostics and fault monitoring in a robotic system |
US11164403B2 (en) | 2019-05-06 | 2021-11-02 | Argo AI, LLC | Method and system for real-time diagnostics and fault monitoring in a robotic system |
EP3969077A1 (en) | 2019-05-13 | 2022-03-23 | Starkey Laboratories, Inc. | Ear-worn devices for communication with medical devices |
US11281920B1 (en) * | 2019-05-23 | 2022-03-22 | State Farm Mutual Automobile Insurance Company | Apparatuses, systems and methods for generating a vehicle driver signature |
WO2020242065A1 (en) * | 2019-05-31 | 2020-12-03 | 주식회사 라운지랩 | Robot movement control method based on risk level determination and mobile robot device using same |
WO2020248205A1 (en) * | 2019-06-14 | 2020-12-17 | Beijing Voyager Technology Co., Ltd. | Systems and methods for monitoring a vehicle |
US11226803B2 (en) | 2019-06-27 | 2022-01-18 | International Business Machines Corporation | Dynamic message embedded within application new feature rollout |
US11458974B2 (en) | 2019-07-08 | 2022-10-04 | Toyota Motor Engineering & Manufacturing North America, Inc. | Fleet-based average lane change and driver-specific behavior modelling for autonomous vehicle lane change operation |
US10972289B2 (en) | 2019-07-19 | 2021-04-06 | JFrog, Ltd. | Software release verification |
JP7140069B2 (en) * | 2019-07-22 | 2022-09-21 | トヨタ自動車株式会社 | Information processing device, information processing system, program, and information processing method |
US11366468B2 (en) * | 2019-07-25 | 2022-06-21 | Honeywell International Inc. | System and method for autonomously monitoring highly automated vehicle operations |
US11175669B2 (en) * | 2019-08-01 | 2021-11-16 | Toyota Motor Engineering & Manufacturing North America, Inc. | Increasing consumer confidence in autonomous vehicles |
US11840248B2 (en) * | 2019-09-05 | 2023-12-12 | Ford Global Technologies, Llc | Method and system for categorizing powertrain torque requests |
US11459028B2 (en) * | 2019-09-12 | 2022-10-04 | Kyndryl, Inc. | Adjusting vehicle sensitivity |
KR20210033308A (en) * | 2019-09-18 | 2021-03-26 | 현대자동차주식회사 | Apparatus for updating of vehicle over the air and method thereof |
DE102019127974B4 (en) * | 2019-10-16 | 2023-11-02 | Allianz Partners SAS | Method and system for evaluating driving behavior |
US11417208B1 (en) | 2019-10-29 | 2022-08-16 | BlueOwl, LLC | Systems and methods for fraud prevention based on video analytics |
US11388351B1 (en) | 2019-10-29 | 2022-07-12 | BlueOwl, LLC | Systems and methods for gate-based vehicle image capture |
CN112750323A (en) * | 2019-10-30 | 2021-05-04 | 上海博泰悦臻电子设备制造有限公司 | Management method, apparatus and computer storage medium for vehicle safety |
CN112758098B (en) * | 2019-11-01 | 2022-07-22 | 广州汽车集团股份有限公司 | Vehicle driving authority take-over control method and device based on driver state grade |
US11704106B2 (en) * | 2019-11-08 | 2023-07-18 | Toyota Jidosha Kabushiki Kaisha | Program update system and vehicle management server |
KR20210066317A (en) * | 2019-11-28 | 2021-06-07 | 현대자동차주식회사 | Apparatus and method for monitoring epilepsy driver using brain wave |
US11775010B2 (en) | 2019-12-02 | 2023-10-03 | Zendrive, Inc. | System and method for assessing device usage |
KR20210076620A (en) * | 2019-12-16 | 2021-06-24 | 현대자동차주식회사 | Vehicle and controlling method of vehicle |
US11605248B2 (en) * | 2019-12-20 | 2023-03-14 | Westinghouse Air Brake Technologies Corporation | Systems and methods for communicating vehicular event alerts |
US20210192636A1 (en) * | 2019-12-23 | 2021-06-24 | By Miles Ltd. | Computing Vehicle Insurance Charges |
US11367140B2 (en) * | 2019-12-30 | 2022-06-21 | International Business Machines Corporation | Dynamic cyber insurance using a distributed ledger |
JP2021112995A (en) * | 2020-01-20 | 2021-08-05 | 本田技研工業株式会社 | Control system, control method, vehicle, and program |
US11514729B2 (en) | 2020-02-28 | 2022-11-29 | Toyota Motor North America, Inc. | Transport behavior observation |
US11461087B2 (en) * | 2020-02-28 | 2022-10-04 | Toyota Motor North America, Inc. | Transport sensor data update |
US11039771B1 (en) | 2020-03-03 | 2021-06-22 | At&T Intellectual Property I, L.P. | Apparatuses and methods for managing tasks in accordance with alertness levels and thresholds |
JP2021149702A (en) * | 2020-03-19 | 2021-09-27 | 本田技研工業株式会社 | Accommodation area management apparatus |
CN111391859A (en) * | 2020-03-23 | 2020-07-10 | 东风小康汽车有限公司重庆分公司 | Vehicle owner identification early warning method and system |
US11834060B2 (en) * | 2020-03-31 | 2023-12-05 | Denso International America, Inc. | System and method for managing vehicle subscriptions |
US11210869B2 (en) * | 2020-03-31 | 2021-12-28 | Calpro Adas Solutions, Llc | Vehicle safety feature identification and calibration |
US11625937B2 (en) * | 2020-04-06 | 2023-04-11 | Toyota Motor Engineering & Manufacturing North America, Inc. | Methods and systems for monitoring human body weight with vehicle sensors and big data AI analytics |
US11615200B2 (en) * | 2020-04-14 | 2023-03-28 | Toyota Motor North America, Inc. | Providing video evidence |
US11999355B2 (en) * | 2020-04-28 | 2024-06-04 | Toyota Motor North America, Inc. | Driver-provided vehicle passenger registry |
US11560143B2 (en) | 2020-05-26 | 2023-01-24 | Magna Electronics Inc. | Vehicular autonomous parking system using short range communication protocols |
US11599949B2 (en) * | 2020-06-03 | 2023-03-07 | The Travelers Indemnity Company | Systems and methods for multivariate artificial intelligence (AI) smart cards |
US11919423B2 (en) | 2020-06-19 | 2024-03-05 | Toyota Motor North America, Inc. | Weight and pressure related validation |
US11281450B2 (en) | 2020-06-23 | 2022-03-22 | Toyota Motor North America, Inc. | Secure transport software update |
US11880670B2 (en) | 2020-06-23 | 2024-01-23 | Toyota Motor North America, Inc. | Execution of transport software update |
US11653186B2 (en) | 2020-06-26 | 2023-05-16 | BlueOwl, LLC | Systems and methods for determining application status |
US11399261B1 (en) | 2020-06-26 | 2022-07-26 | BlueOwl, LLC | Systems and methods for determining mobile device status |
US11363426B1 (en) | 2020-07-07 | 2022-06-14 | BlueOwl, LLC | Systems and methods for verifying reliability of sensor data received from mobile devices |
JP7490486B2 (en) * | 2020-07-28 | 2024-05-27 | 株式会社日立製作所 | Software inquiry information management system and software inquiry information management method |
US11396305B2 (en) * | 2020-07-30 | 2022-07-26 | Toyota Research Institute, Inc. | Systems and methods for improving driver warnings during automated driving |
US20220051340A1 (en) * | 2020-08-14 | 2022-02-17 | GM Global Technology Operations LLC | System and Method Using Crowd-Sourced Data to Evaluate Driver Performance |
US11713060B2 (en) | 2020-09-18 | 2023-08-01 | Guident Ltd. | Systems and methods for remote monitoring of a vehicle, robot or drone |
US11387985B2 (en) * | 2020-10-01 | 2022-07-12 | Toyota Motor North America, Inc. | Transport occupant data delivery |
JP2022061873A (en) * | 2020-10-07 | 2022-04-19 | トヨタ自動車株式会社 | Agent device for vehicle, agent system for vehicle and agent program for vehicle |
US20230237584A1 (en) * | 2020-10-29 | 2023-07-27 | BlueOwl, LLC | Systems and methods for evaluating vehicle insurance claims |
US20220135047A1 (en) * | 2020-11-03 | 2022-05-05 | Toyota Motor North America, Inc. | Managing data delivery in a transport |
US11835949B2 (en) | 2020-11-24 | 2023-12-05 | Mobile Industrial Robots A/S | Autonomous device safety system |
US11860680B2 (en) | 2020-11-24 | 2024-01-02 | JFrog Ltd. | Software pipeline and release validation |
US20220176957A1 (en) * | 2020-12-09 | 2022-06-09 | Aptiv Technologies Limited | Indirect Verification of Speed Limits Based on Contextual Information For Autonomous and Semi-Autonomous Driving Systems |
US11794764B2 (en) | 2020-12-21 | 2023-10-24 | Toyota Motor North America, Inc. | Approximating a time of an issue |
US11554671B2 (en) | 2020-12-21 | 2023-01-17 | Toyota Motor North America, Inc. | Transport data display cognition |
US11770701B2 (en) | 2021-02-05 | 2023-09-26 | Argo AI, LLC | Secure communications with autonomous vehicles |
US11449950B2 (en) | 2021-02-19 | 2022-09-20 | Allstate Insurance Company | Data processing systems with machine learning engines for dynamically generating risk index dashboards |
US11861950B2 (en) | 2021-02-24 | 2024-01-02 | Toyota Motor North America, Inc. | Device modification from transport operation |
US11370391B1 (en) | 2021-03-10 | 2022-06-28 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle authorized use determination |
JP2022160237A (en) * | 2021-04-06 | 2022-10-19 | ウーブン・プラネット・ホールディングス株式会社 | Remote assistance device and remote assistance method |
US11782692B2 (en) * | 2021-04-16 | 2023-10-10 | Toyota Motor North America, Inc. | Transport component acceptance |
US12008100B2 (en) | 2021-04-19 | 2024-06-11 | Toyota Motor North America, Inc. | Transport component tamper detection based on impedance measurements |
US11787434B2 (en) | 2021-04-19 | 2023-10-17 | Toyota Motor North America, Inc. | Modification of transport functionality based on modified components |
CN115237510A (en) * | 2021-04-23 | 2022-10-25 | 沃尔沃汽车公司 | Advice provision apparatus, system, and method for vehicle |
US11922447B1 (en) | 2021-05-12 | 2024-03-05 | Block, Inc. | Biometric-based payment rewards |
US11565717B2 (en) * | 2021-06-02 | 2023-01-31 | May Mobility, Inc. | Method and system for remote assistance of an autonomous agent |
DE102021115516A1 (en) | 2021-06-16 | 2022-12-22 | Audi Aktiengesellschaft | Motor vehicle with interrupting device for a driver assistance device |
US11958474B2 (en) | 2021-07-20 | 2024-04-16 | Atieva, Inc. | Parking assistance with smooth handover, parking completion, or parking correction |
KR20230014544A (en) * | 2021-07-21 | 2023-01-30 | 현대자동차주식회사 | Autonomous Vehicle, Control system for remotely controlling the same, and method thereof |
US11851091B2 (en) | 2021-09-14 | 2023-12-26 | Motional Ad Llc | Immobility detection within situational context |
US11845454B2 (en) | 2021-09-14 | 2023-12-19 | Motional Ad Llc | Operational envelope detection with situational assessment |
US11912313B2 (en) * | 2021-10-04 | 2024-02-27 | Arriver Software Llc | Human machine interaction monitor |
US20230122124A1 (en) * | 2021-10-20 | 2023-04-20 | Qualcomm Incorporated | Autonomous driving network vehicle alerting |
US11897379B2 (en) | 2021-10-20 | 2024-02-13 | Toyota Motor Engineering & Manufacturing North America, Inc. | Seat with shape memory material member actuation |
US11623655B1 (en) | 2021-10-29 | 2023-04-11 | Geotab Inc. | Systems and methods for restricting the use of a vehicle operator's electronic device |
US11993270B2 (en) * | 2021-12-03 | 2024-05-28 | Bendix Commercial Vehicle Systems, Llc | System and method for driving style driver identity determination and control of vehicle functions |
US11887200B2 (en) * | 2021-12-10 | 2024-01-30 | GM Global Technology Operations LLC | Systems and methods for enabling yielding decisions, conflict resolution, and user profile generation |
US20230192100A1 (en) * | 2021-12-22 | 2023-06-22 | Arriver Software Llc | Awareness checker for enhancing collaborative driving supervision |
CN114326679B (en) * | 2021-12-30 | 2023-07-18 | 深蓝汽车科技有限公司 | Method and system for refreshing controller based on one-edition integrated software |
DE102022107381A1 (en) | 2022-03-29 | 2023-10-05 | Valeo Schalter Und Sensoren Gmbh | Adjusting detection of objects based on receiving ultrasonic echo signals with a vehicle's ultrasonic sensors |
US11943263B2 (en) | 2022-06-02 | 2024-03-26 | Vmware, Inc. | Recommendation engine for improved user experience in online meetings |
US11936516B2 (en) * | 2022-06-02 | 2024-03-19 | Vmware, Inc. | Using hardware profiles of hardware components to determine performance issues of user devices |
US20230399016A1 (en) * | 2022-06-14 | 2023-12-14 | Gm Cruise Holdings Llc | Multi-mode vehicle controller |
US20240053974A1 (en) * | 2022-08-11 | 2024-02-15 | Ford Global Technologies, Llc | Secure update and audit of electronic control units |
FR3139402A1 (en) * | 2022-09-01 | 2024-03-08 | Renault S.A.S | METHOD FOR ASSESSING THE SAFETY OF A VEHICLE WITH DRIVING DELEGATION |
US20240184691A1 (en) * | 2022-12-05 | 2024-06-06 | Gm Cruise Holdings Llc | Testing software changes and determining a repeatability of software tests |
Family Cites Families (885)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4218763A (en) | 1978-08-04 | 1980-08-19 | Brailsford Lawrence J | Electronic alarm signaling system |
JPS56105967U (en) | 1980-01-15 | 1981-08-18 | ||
JPS5750097A (en) | 1980-09-08 | 1982-03-24 | Nissan Motor | Automotive warning device |
US7663502B2 (en) | 1992-05-05 | 2010-02-16 | Intelligent Technologies International, Inc. | Asset system control arrangement and method |
US5367456A (en) | 1985-08-30 | 1994-11-22 | Texas Instruments Incorporated | Hierarchical control system for automatically guided vehicles |
US4833469A (en) | 1987-08-03 | 1989-05-23 | David Constant V | Obstacle proximity detector for moving vehicles and method for use thereof |
US5214582C1 (en) | 1991-01-30 | 2001-06-26 | Edge Diagnostic Systems | Interactive diagnostic system for an automobile vehicle and method |
US7596242B2 (en) | 1995-06-07 | 2009-09-29 | Automotive Technologies International, Inc. | Image processing for vehicular applications |
US5368484A (en) | 1992-05-22 | 1994-11-29 | Atari Games Corp. | Vehicle simulator with realistic operating feedback |
GB2268608A (en) | 1992-06-10 | 1994-01-12 | Norm Pacific Automat Corp | Vehicle accident prevention and recording system |
US5453939A (en) | 1992-09-16 | 1995-09-26 | Caterpillar Inc. | Computerized diagnostic and monitoring system |
US5436839A (en) | 1992-10-26 | 1995-07-25 | Martin Marietta Corporation | Navigation module for a semi-autonomous vehicle |
JP3269153B2 (en) | 1993-01-06 | 2002-03-25 | 三菱自動車工業株式会社 | Arousal level determination device |
JPH06197888A (en) | 1993-01-06 | 1994-07-19 | Mitsubishi Motors Corp | Doze warning device for vehicle |
US5363298A (en) | 1993-04-29 | 1994-11-08 | The United States Of America As Represented By The Secretary Of The Navy | Controlled risk decompression meter |
US5983161A (en) | 1993-08-11 | 1999-11-09 | Lemelson; Jerome H. | GPS vehicle collision avoidance warning and control system and method |
US5515026A (en) | 1994-01-28 | 1996-05-07 | Ewert; Roger D. | Total alert driver safety system |
US7421321B2 (en) | 1995-06-07 | 2008-09-02 | Automotive Technologies International, Inc. | System for obtaining vehicular information |
US5626362A (en) | 1994-06-07 | 1997-05-06 | Interactive Driving Systems, Inc. | Simulator for teaching vehicle speed control and skid recovery techniques |
ES2108613B1 (en) | 1994-09-01 | 1998-08-01 | Perez Salvador Minguijon | SYSTEM TO ASSESS RISK IN AUTOMOBILE VEHICLES. |
US5499182A (en) | 1994-12-07 | 1996-03-12 | Ousborne; Jeffrey | Vehicle driver performance monitoring system |
US5689241A (en) | 1995-04-24 | 1997-11-18 | Clarke, Sr.; James Russell | Sleep detection and driver alert apparatus |
US8036788B2 (en) | 1995-06-07 | 2011-10-11 | Automotive Technologies International, Inc. | Vehicle diagnostic or prognostic message transmission systems and methods |
US20080161989A1 (en) | 1995-06-07 | 2008-07-03 | Automotive Technologies International, Inc. | Vehicle Diagnostic or Prognostic Message Transmission Systems and Methods |
US5835008A (en) | 1995-11-28 | 1998-11-10 | Colemere, Jr.; Dale M. | Driver, vehicle and traffic information system |
US8090598B2 (en) | 1996-01-29 | 2012-01-03 | Progressive Casualty Insurance Company | Monitoring system for determining and communicating a cost of insurance |
US8140358B1 (en) | 1996-01-29 | 2012-03-20 | Progressive Casualty Insurance Company | Vehicle monitoring system |
US5797134A (en) | 1996-01-29 | 1998-08-18 | Progressive Casualty Insurance Company | Motor vehicle monitoring system for determining a cost of insurance |
US5710503A (en) | 1996-02-01 | 1998-01-20 | Aims Systems, Inc. | On-line battery monitoring system with defective cell detection capability |
US6400835B1 (en) | 1996-05-15 | 2002-06-04 | Jerome H. Lemelson | Taillight mounted vehicle security system employing facial recognition using a reflected image |
US6265978B1 (en) | 1996-07-14 | 2001-07-24 | Atlas Researches, Ltd. | Method and apparatus for monitoring states of consciousness, drowsiness, distress, and performance |
JP3272960B2 (en) | 1996-08-19 | 2002-04-08 | 株式会社データ・テック | Driving recorder and vehicle operation analyzer |
US6271745B1 (en) | 1997-01-03 | 2001-08-07 | Honda Giken Kogyo Kabushiki Kaisha | Keyless user identification and authorization system for a motor vehicle |
GB9700090D0 (en) | 1997-01-04 | 1997-02-19 | Horne James A | Sleepiness detection for vehicle driver |
US6253129B1 (en) | 1997-03-27 | 2001-06-26 | Tripmaster Corporation | System for monitoring vehicle efficiency and vehicle and driver performance |
US7870010B2 (en) | 1997-07-31 | 2011-01-11 | Raymond Anthony Joao | Apparatus and method for processing lease insurance information |
US6275231B1 (en) | 1997-08-01 | 2001-08-14 | American Calcar Inc. | Centralized control and management system for automobiles |
JP3429438B2 (en) | 1997-08-22 | 2003-07-22 | 富士通株式会社 | Driving method of AC type PDP |
US8965677B2 (en) | 1998-10-22 | 2015-02-24 | Intelligent Technologies International, Inc. | Intra-vehicle information conveyance system and method |
US7983802B2 (en) | 1997-10-22 | 2011-07-19 | Intelligent Technologies International, Inc. | Vehicular environment scanning techniques |
US7979172B2 (en) | 1997-10-22 | 2011-07-12 | Intelligent Technologies International, Inc. | Autonomous vehicle travel control systems and methods |
US7979173B2 (en) | 1997-10-22 | 2011-07-12 | Intelligent Technologies International, Inc. | Autonomous vehicle travel control systems and methods |
US8209120B2 (en) | 1997-10-22 | 2012-06-26 | American Vehicular Sciences Llc | Vehicular map database management techniques |
US7647180B2 (en) | 1997-10-22 | 2010-01-12 | Intelligent Technologies International, Inc. | Vehicular intersection management techniques |
US7791503B2 (en) | 1997-10-22 | 2010-09-07 | Intelligent Technologies International, Inc. | Vehicle to infrastructure information conveyance system and method |
US8255144B2 (en) | 1997-10-22 | 2012-08-28 | Intelligent Technologies International, Inc. | Intra-vehicle information conveyance system and method |
DE59809476D1 (en) | 1997-11-03 | 2003-10-09 | Volkswagen Ag | Autonomous vehicle and method for controlling an autonomous vehicle |
US6285931B1 (en) | 1998-02-05 | 2001-09-04 | Denso Corporation | Vehicle information communication system and method capable of communicating with external management station |
US20010005217A1 (en) | 1998-06-01 | 2001-06-28 | Hamilton Jeffrey Allen | Incident recording information transfer device |
US6141611A (en) | 1998-12-01 | 2000-10-31 | John J. Mackey | Mobile vehicle accident data system |
AU1812100A (en) | 1998-11-06 | 2000-05-29 | Phoenix Group, Inc. | Mobile vehicle accident data system |
US6704434B1 (en) | 1999-01-27 | 2004-03-09 | Suzuki Motor Corporation | Vehicle driving information storage apparatus and vehicle driving information storage method |
US7539628B2 (en) | 2000-03-21 | 2009-05-26 | Bennett James D | Online purchasing system supporting buyer affordability screening |
US6570609B1 (en) | 1999-04-22 | 2003-05-27 | Troy A. Heien | Method and apparatus for monitoring operation of a motor vehicle |
AT410531B (en) | 1999-05-25 | 2003-05-26 | Bernard Ing Douet | METHOD AND SYSTEM FOR AUTOMATIC DETECTION OR MONITORING THE POSITION OF AT LEAST ONE RAIL VEHICLE |
US6983313B1 (en) | 1999-06-10 | 2006-01-03 | Nokia Corporation | Collaborative location server/system |
DE19934862C1 (en) | 1999-07-24 | 2001-03-01 | Bosch Gmbh Robert | Navigation method and navigation system for motor vehicles |
US7124088B2 (en) | 1999-07-30 | 2006-10-17 | Progressive Casualty Insurance Company | Apparatus for internet on-line insurance policy service |
US20020049535A1 (en) | 1999-09-20 | 2002-04-25 | Ralf Rigo | Wireless interactive voice-actuated mobile telematics system |
US6661345B1 (en) | 1999-10-22 | 2003-12-09 | The Johns Hopkins University | Alertness monitoring system |
US6246933B1 (en) | 1999-11-04 | 2001-06-12 | BAGUé ADOLFO VAEZA | Traffic accident data recorder and traffic accident reproduction system and method |
US7110947B2 (en) | 1999-12-10 | 2006-09-19 | At&T Corp. | Frame erasure concealment technique for a bitstream-based feature extractor |
US6298290B1 (en) | 1999-12-30 | 2001-10-02 | Niles Parts Co., Ltd. | Memory apparatus for vehicle information data |
WO2001063194A1 (en) | 2000-02-22 | 2001-08-30 | Corning Incorporated | Method for controlling the firing of ceramics |
US8103526B1 (en) | 2000-03-07 | 2012-01-24 | Insweb Corporation | System and method for flexible insurance rating calculation |
US6553354B1 (en) | 2000-04-04 | 2003-04-22 | Ford Motor Company | Method of probabilistically modeling variables |
US6323761B1 (en) | 2000-06-03 | 2001-11-27 | Sam Mog Son | Vehicular security access system |
US6477117B1 (en) | 2000-06-30 | 2002-11-05 | International Business Machines Corporation | Alarm interface for a smart watch |
US20020111725A1 (en) | 2000-07-17 | 2002-08-15 | Burge John R. | Method and apparatus for risk-related use of vehicle communication system data |
US20020103622A1 (en) | 2000-07-17 | 2002-08-01 | Burge John R. | Decision-aid system based on wirelessly-transmitted vehicle crash sensor information |
US7904219B1 (en) | 2000-07-25 | 2011-03-08 | Htiip, Llc | Peripheral access devices and sensors for use with vehicle telematics devices and systems |
US20020016655A1 (en) | 2000-08-01 | 2002-02-07 | Joao Raymond Anthony | Apparatus and method for processing and/or for providing vehicle information and/or vehicle maintenance information |
SE0002804D0 (en) | 2000-08-01 | 2000-08-01 | Promind Ab | Technology for continuously mapping the behavior / behavior of the vehicle / driver to determine the reaction coefficient of the vehicle or the vehicle. driver's skill coefficient, and device for graphical presentation of these coefficients |
US20050091175A9 (en) | 2000-08-11 | 2005-04-28 | Telanon, Inc. | Automated consumer to business electronic marketplace system |
US20090109037A1 (en) | 2000-08-11 | 2009-04-30 | Telanon, Inc. | Automated consumer to business electronic marketplace system |
US7349860B1 (en) | 2000-08-24 | 2008-03-25 | Creative Innovators Associates, Llc | Insurance incentive program having a term of years for promoting the purchase or lease of an automobile |
US6556905B1 (en) | 2000-08-31 | 2003-04-29 | Lisa M. Mittelsteadt | Vehicle supervision and monitoring |
US7941258B1 (en) | 2000-08-31 | 2011-05-10 | Strategic Design Federation W, Inc. | Automobile monitoring for operation analysis |
US9151692B2 (en) | 2002-06-11 | 2015-10-06 | Intelligent Technologies International, Inc. | Asset monitoring system using multiple imagers |
US7135961B1 (en) | 2000-09-29 | 2006-11-14 | International Business Machines Corporation | Method and system for providing directions for driving |
US7565230B2 (en) | 2000-10-14 | 2009-07-21 | Temic Automotive Of North America, Inc. | Method and apparatus for improving vehicle operator performance |
JP3834463B2 (en) | 2000-10-13 | 2006-10-18 | 株式会社日立製作所 | In-vehicle failure alarm reporting system |
US6909947B2 (en) | 2000-10-14 | 2005-06-21 | Motorola, Inc. | System and method for driver performance improvement |
WO2002056139A2 (en) | 2000-10-26 | 2002-07-18 | Digimarc Corporation | Method and system for internet access |
US6727800B1 (en) | 2000-11-01 | 2004-04-27 | Iulius Vivant Dutu | Keyless system for entry and operation of a vehicle |
US6879969B2 (en) | 2001-01-21 | 2005-04-12 | Volvo Technological Development Corporation | System and method for real-time recognition of driving patterns |
US20020103678A1 (en) | 2001-02-01 | 2002-08-01 | Burkhalter Swinton B. | Multi-risk insurance system and method |
US6964023B2 (en) | 2001-02-05 | 2005-11-08 | International Business Machines Corporation | System and method for multi-modal focus detection, referential ambiguity resolution and mood classification using multi-modal input |
US20020107716A1 (en) | 2001-02-07 | 2002-08-08 | Kevin Callahan | Methods and apparatus for scheduling an in-home appliance repair service |
US20020146667A1 (en) | 2001-02-14 | 2002-10-10 | Safe Drive Technologies, Llc | Staged-learning process and system for situational awareness training using integrated media |
JP2002318844A (en) | 2001-02-15 | 2002-10-31 | Hitachi Ltd | Method for managing vehicle |
JP2002259708A (en) | 2001-03-06 | 2002-09-13 | Toyota Motor Corp | Vehicular insurance bill calculating system, on-vehicle device, and server device |
US7027621B1 (en) | 2001-03-15 | 2006-04-11 | Mikos, Ltd. | Method and apparatus for operator condition monitoring and assessment |
JP3620466B2 (en) | 2001-05-14 | 2005-02-16 | トヨタ自動車株式会社 | Severity judgment device |
US7266532B2 (en) | 2001-06-01 | 2007-09-04 | The General Hospital Corporation | Reconfigurable autonomous device networks |
US7042347B2 (en) | 2001-06-19 | 2006-05-09 | Cherouny Peter H | Electronic programmable speed limiter |
US6579233B2 (en) | 2001-07-06 | 2003-06-17 | Science Applications International Corp. | System and method for evaluating task effectiveness based on sleep pattern |
US7298387B2 (en) | 2001-08-22 | 2007-11-20 | Polaroid Corporation | Thermal response correction system |
ES2598109T3 (en) | 2001-09-06 | 2017-01-25 | Northwest Biotherapeutics, Inc. | Compositions and methods for lymphocyte activation of monocytic dendritic cells and T cells to generate a Th-1 response |
JP3775494B2 (en) | 2001-09-21 | 2006-05-17 | 日本電気株式会社 | Information processing apparatus for billing system and billing information collecting method |
US20030200123A1 (en) | 2001-10-18 | 2003-10-23 | Burge John R. | Injury analysis system and method for insurance claims |
US6701234B1 (en) | 2001-10-18 | 2004-03-02 | Andrew John Vogelsang | Portable motion recording device for motor vehicles |
US6473000B1 (en) | 2001-10-24 | 2002-10-29 | James Secreet | Method and apparatus for measuring and recording vehicle speed and for storing related data |
JP4227743B2 (en) | 2001-11-19 | 2009-02-18 | 株式会社デンソー | Anti-theft system |
US8211123B2 (en) * | 2001-12-21 | 2012-07-03 | Abbott Laboratories | Suture trimmer |
US7395219B2 (en) | 2001-12-08 | 2008-07-01 | Kenneth Ray Strech | Insurance on demand transaction management system |
US6741168B2 (en) | 2001-12-13 | 2004-05-25 | Samsung Electronics Co., Ltd. | Method and apparatus for automated collection and transfer of collision information |
EP1324274A3 (en) | 2001-12-28 | 2005-11-02 | Matsushita Electric Industrial Co., Ltd. | Vehicle information recording system |
US7386376B2 (en) | 2002-01-25 | 2008-06-10 | Intelligent Mechatronic Systems, Inc. | Vehicle visual and non-visual data recording system |
US6944536B2 (en) | 2002-02-01 | 2005-09-13 | Medaire, Inc. | Method and system for identifying medical facilities along a travel route |
US6721632B2 (en) | 2002-02-05 | 2004-04-13 | International Business Machines Corporation | Wireless exchange between vehicle-borne communications systems |
CN101115646B (en) | 2002-03-19 | 2011-11-16 | 汽车系统实验室公司 | Vehicle rollover detection system |
US20030182183A1 (en) | 2002-03-20 | 2003-09-25 | Christopher Pribe | Multi-car-pool organization method |
JP2003276470A (en) | 2002-03-22 | 2003-09-30 | Nissan Motor Co Ltd | Information presentation control device |
JP3631471B2 (en) | 2002-04-09 | 2005-03-23 | 株式会社東芝 | Liquid crystal display controller |
US20040005927A1 (en) | 2002-04-22 | 2004-01-08 | Bonilla Victor G. | Facility for remote computer controlled racing |
US20040077285A1 (en) | 2002-04-22 | 2004-04-22 | Bonilla Victor G. | Method, apparatus, and system for simulating visual depth in a concatenated image of a remote field of action |
US7290275B2 (en) | 2002-04-29 | 2007-10-30 | Schlumberger Omnes, Inc. | Security maturity assessment method |
JP2003323555A (en) | 2002-04-30 | 2003-11-14 | Hewlett Packard Japan Ltd | Method and system for information distribution |
US8035508B2 (en) | 2002-06-11 | 2011-10-11 | Intelligent Technologies International, Inc. | Monitoring using cellular phones |
US9082237B2 (en) | 2002-06-11 | 2015-07-14 | Intelligent Technologies International, Inc. | Vehicle access and security based on biometrics |
US20130267194A1 (en) | 2002-06-11 | 2013-10-10 | American Vehicular Sciences Llc | Method and System for Notifying a Remote Facility of an Accident Involving a Vehicle |
JP2004017889A (en) | 2002-06-19 | 2004-01-22 | Advics:Kk | Automatic brake |
US20040019539A1 (en) | 2002-07-25 | 2004-01-29 | 3Com Corporation | Prepaid billing system for wireless data networks |
US20040198441A1 (en) | 2002-07-29 | 2004-10-07 | George Cooper | Wireless communication device and method |
US7102496B1 (en) | 2002-07-30 | 2006-09-05 | Yazaki North America, Inc. | Multi-sensor integration for a vehicle |
KR100489357B1 (en) | 2002-08-08 | 2005-05-16 | 주식회사 하이닉스반도체 | Cell array structure in nonvolatile ferroelectric memory device and scheme for operating the same |
US6795759B2 (en) | 2002-08-26 | 2004-09-21 | International Business Machines Corporation | Secure logging of vehicle data |
US7676062B2 (en) | 2002-09-03 | 2010-03-09 | Automotive Technologies International Inc. | Image processing for vehicular applications applying image comparisons |
DE10240838A1 (en) | 2002-09-04 | 2004-03-18 | Robert Bosch Gmbh | Motor vehicle accident reconstruction method, in which driving data for use in accident reconstruction is captured from existing onboard control electronics and used to generate a dynamic 3D kinematic model which is recorded |
JP3699434B2 (en) | 2002-10-03 | 2005-09-28 | 三菱電機株式会社 | Vehicle anti-theft device |
US6832141B2 (en) | 2002-10-25 | 2004-12-14 | Davis Instruments | Module for monitoring vehicle operation through onboard diagnostic port |
US10176476B2 (en) | 2005-10-06 | 2019-01-08 | Mastercard Mobile Transactions Solutions, Inc. | Secure ecosystem infrastructure enabling multiple types of electronic wallets in an ecosystem of issuers, service providers, and acquires of instruments |
JP3829793B2 (en) | 2002-11-06 | 2006-10-04 | 株式会社デンソー | Emergency call device |
US7202792B2 (en) | 2002-11-11 | 2007-04-10 | Delphi Technologies, Inc. | Drowsiness detection system and method |
KR100480727B1 (en) | 2002-11-26 | 2005-04-07 | 엘지전자 주식회사 | Apparatus for controlling heater of a dryer |
US7725334B2 (en) | 2002-11-27 | 2010-05-25 | Computer Sciences Corporation | Computerized method and system for estimating liability for an accident using dynamic generation of questions |
CN1778125A (en) | 2002-12-27 | 2006-05-24 | 诺基亚公司 | Position-based service for mobile communication terminal |
US20040158476A1 (en) | 2003-02-06 | 2004-08-12 | I-Sim, Llc | Systems and methods for motor vehicle learning management |
JP4235465B2 (en) | 2003-02-14 | 2009-03-11 | 本田技研工業株式会社 | Riding simulation equipment |
US7737859B2 (en) | 2003-02-24 | 2010-06-15 | Electronic Navigation Research Institute, An Independent Administrative Institution | Psychosomatic state determination system |
US7138922B2 (en) | 2003-03-18 | 2006-11-21 | Ford Global Technologies, Llc | Drowsy driver monitoring and prevention system |
DE10314119A1 (en) | 2003-03-28 | 2004-10-21 | Dieter Dr. Bastian | Process for determining an integral risk potential for a road user and device for carrying out the process |
US7587287B2 (en) | 2003-04-04 | 2009-09-08 | Abbott Diabetes Care Inc. | Method and system for transferring analyte test data |
US6970102B2 (en) | 2003-05-05 | 2005-11-29 | Transol Pty Ltd | Traffic violation detection, recording and evidence processing system |
US20040226043A1 (en) | 2003-05-07 | 2004-11-11 | Autodesk, Inc. | Location enabled television |
US7071821B2 (en) | 2003-05-14 | 2006-07-04 | Bellsouth Intellectual Property Corporation | Method and system for alerting a person to a situation |
ATE505775T1 (en) | 2003-05-15 | 2011-04-15 | Speedgauge Inc | SYSTEM AND METHOD FOR EVALUATION OF VEHICLE AND OPERATOR PERFORMANCE |
WO2004114055A2 (en) | 2003-05-23 | 2004-12-29 | Nnt, Inc. | An enterprise resource planning system with integrated vehicle diagnostic and information system |
BRPI0411056A (en) | 2003-06-06 | 2007-04-17 | Volvo Technology Corp | method and arrangement for controlling vehicle subsystems based on interpretive driver activity |
US7292152B2 (en) | 2003-06-12 | 2007-11-06 | Temic Automotive Of North America, Inc. | Method and apparatus for classifying vehicle operator activity state |
US20040260579A1 (en) | 2003-06-19 | 2004-12-23 | Tremiti Kimberly Irene | Technique for providing automobile insurance |
US8275417B2 (en) | 2003-06-27 | 2012-09-25 | Powerwave Technologies, Inc. | Flood evacuation system for subterranean telecommunications vault |
US7206697B2 (en) | 2003-10-14 | 2007-04-17 | Delphi Technologies, Inc. | Driver adaptive collision warning system |
JP2005096744A (en) | 2003-09-01 | 2005-04-14 | Matsushita Electric Ind Co Ltd | Occupant certifying system |
US7711584B2 (en) | 2003-09-04 | 2010-05-04 | Hartford Fire Insurance Company | System for reducing the risk associated with an insured building structure through the incorporation of selected technologies |
US9311676B2 (en) | 2003-09-04 | 2016-04-12 | Hartford Fire Insurance Company | Systems and methods for analyzing sensor data |
US7424414B2 (en) | 2003-09-05 | 2008-09-09 | Road Safety International, Inc. | System for combining driving simulators and data acquisition systems and methods of use thereof |
US7797107B2 (en) | 2003-09-16 | 2010-09-14 | Zvi Shiller | Method and system for providing warnings concerning an imminent vehicular collision |
US7095336B2 (en) | 2003-09-23 | 2006-08-22 | Optimus Corporation | System and method for providing pedestrian alerts |
US7069118B2 (en) | 2003-09-30 | 2006-06-27 | International Business Machines Corporation | Apparatus, system, and method for exchanging vehicle identification data |
US7542915B2 (en) | 2003-09-30 | 2009-06-02 | The Boeing Company | System of charging for automobile insurance |
US7149533B2 (en) | 2003-10-01 | 2006-12-12 | Laird Mark D | Wireless virtual campus escort system |
US7092799B2 (en) | 2003-10-10 | 2006-08-15 | General Motors Corporation | Method and system for remotely inventorying electronic modules installed in a vehicle |
US7023333B2 (en) | 2003-10-22 | 2006-04-04 | L-3 Communications Mobile Vision, Inc. | Automatic activation of an in-car video recorder using a vehicle speed sensor signal |
US20050088521A1 (en) | 2003-10-22 | 2005-04-28 | Mobile-Vision Inc. | In-car video system using flash memory as a recording medium |
US20050093684A1 (en) | 2003-10-30 | 2005-05-05 | Cunnien Cole J. | Frame assembly for a license plate |
US7877275B2 (en) | 2003-11-13 | 2011-01-25 | General Motors Llc | System and method for maintaining and providing personal information in real time |
US20050108910A1 (en) | 2003-11-22 | 2005-05-26 | Esparza Erin A. | Apparatus and method for promoting new driver awareness |
US7389178B2 (en) | 2003-12-11 | 2008-06-17 | Greenroad Driving Technologies Ltd. | System and method for vehicle driver behavior analysis and evaluation |
US7783505B2 (en) | 2003-12-30 | 2010-08-24 | Hartford Fire Insurance Company | System and method for computerized insurance rating |
JP4140720B2 (en) | 2004-01-14 | 2008-08-27 | 三菱電機株式会社 | Vehicle behavior reproduction system |
WO2005083605A1 (en) | 2004-02-26 | 2005-09-09 | Aioi Insurance Co., Ltd. | Insurance fee calculation device, insurance fee calculation program, insurance fee calculation method, and insurance fee calculation system |
US7680694B2 (en) | 2004-03-11 | 2010-03-16 | American Express Travel Related Services Company, Inc. | Method and apparatus for a user to shop online in a three dimensional virtual reality setting |
US7482911B2 (en) | 2004-03-11 | 2009-01-27 | Bayerische Motoren Werke Aktiengesellschaft | Process for the output of information in a vehicle |
US8694475B2 (en) | 2004-04-03 | 2014-04-08 | Altusys Corp. | Method and apparatus for situation-based management |
US7761351B2 (en) | 2004-04-29 | 2010-07-20 | Ford Motor Company | Method and system for assessing the risk of a vehicle dealership defaulting on a financial obligation |
US7895054B2 (en) | 2004-05-06 | 2011-02-22 | Humana Inc. | Pharmacy personal care account |
JP4532181B2 (en) | 2004-06-24 | 2010-08-25 | 日産自動車株式会社 | VEHICLE DRIVE OPERATION ASSISTANCE DEVICE AND VEHICLE HAVING VEHICLE DRIVE OPERATION ASSISTANCE DEVICE |
US20060031103A1 (en) | 2004-08-06 | 2006-02-09 | Henry David S | Systems and methods for diagram data collection |
US20100143872A1 (en) | 2004-09-03 | 2010-06-10 | Gold Cross Benefits Corporation | Driver safety program based on behavioral profiling |
US20060053038A1 (en) | 2004-09-08 | 2006-03-09 | Warren Gregory S | Calculation of driver score based on vehicle operation |
US7176813B2 (en) | 2004-09-10 | 2007-02-13 | Xanavi Informatics Corporation | System and method for processing and displaying traffic information in an automotive navigation system |
US7519362B2 (en) | 2004-09-13 | 2009-04-14 | Laperch Richard C | Personal wireless gateway and method for implementing the same |
US20060079260A1 (en) | 2004-09-17 | 2006-04-13 | Nextel Communications, Inc. | Ad-hoc dispatch chatroom |
GB2419430B (en) | 2004-10-22 | 2008-05-21 | Irobot Corp | Systems and Methods for Control of a Vehicle |
US7499776B2 (en) | 2004-10-22 | 2009-03-03 | Irobot Corporation | Systems and methods for control of an unmanned ground vehicle |
US7499774B2 (en) | 2004-10-22 | 2009-03-03 | Irobot Corporation | System and method for processing safety signals in an autonomous vehicle |
EP1815225A4 (en) | 2004-10-25 | 2010-04-28 | Payment Protection Sys Inc | Method and system for monitoring a vehicle |
US7890355B2 (en) | 2004-10-29 | 2011-02-15 | Milemeter, Inc. | System and method for the assessment, pricing, and provisioning of distance-based vehicle insurance |
US7991629B2 (en) | 2004-10-29 | 2011-08-02 | Milemeter, Inc. | System and method for the assessment, pricing, and provisioning of distance-based vehicle insurance |
US7987103B2 (en) | 2004-10-29 | 2011-07-26 | Milemeter, Inc. | System and method for the assessment, pricing, and provisioning of distance-based vehicle insurance |
US7865378B2 (en) | 2004-10-29 | 2011-01-04 | Milemeter, Inc. | System and method for the assessment, pricing, and provisioning of distance-based vehicle insurance |
US20070299700A1 (en) | 2004-10-29 | 2007-12-27 | Milemeter, Inc. | System and Method for Assessing Earned Premium for Distance-Based Vehicle Insurance |
US7348895B2 (en) | 2004-11-03 | 2008-03-25 | Lagassey Paul J | Advanced automobile accident detection, data recordation and reporting system |
US7253724B2 (en) | 2004-11-05 | 2007-08-07 | Ford Global Technologies, Inc. | Vehicle pre-impact sensing and control system with driver response feedback |
CN101057463B (en) | 2004-11-11 | 2010-10-06 | Nxp股份有限公司 | Device and method for event-triggered communication between and among a plurality of nodes |
DE602004017336D1 (en) | 2004-11-24 | 2008-12-04 | Harman Becker Automotive Sys | Driver information system |
US7908080B2 (en) | 2004-12-31 | 2011-03-15 | Google Inc. | Transportation routing |
US7937278B1 (en) | 2005-01-18 | 2011-05-03 | Allstate Insurance Company | Usage-based insurance cost determination system and method |
WO2006088916A2 (en) | 2005-02-14 | 2006-08-24 | Regents Of The University Of Minnesota | Vehicle position system using passive roadway tags |
US20060184295A1 (en) | 2005-02-17 | 2006-08-17 | Steve Hawkins | On-board datalogger apparatus and service methods for use with vehicles |
JP4650028B2 (en) | 2005-03-02 | 2011-03-16 | 株式会社デンソー | Driving evaluation device and driving evaluation system |
JP2006252138A (en) | 2005-03-10 | 2006-09-21 | Omron Corp | Apparatus for photographing driver and apparatus for monitoring driver |
US20060212195A1 (en) | 2005-03-15 | 2006-09-21 | Veith Gregory W | Vehicle data recorder and telematic device |
US7353034B2 (en) | 2005-04-04 | 2008-04-01 | X One, Inc. | Location sharing and tracking using mobile phones or other wireless devices |
US20060229777A1 (en) | 2005-04-12 | 2006-10-12 | Hudson Michael D | System and methods of performing real-time on-board automotive telemetry analysis and reporting |
JP4735310B2 (en) | 2005-04-15 | 2011-07-27 | 株式会社デンソー | Driving support device |
US7451041B2 (en) | 2005-05-06 | 2008-11-11 | Facet Technology Corporation | Network-based navigation system having virtual drive-thru advertisements integrated with actual imagery from along a physical route |
US7835834B2 (en) | 2005-05-16 | 2010-11-16 | Delphi Technologies, Inc. | Method of mitigating driver distraction |
CN101228546A (en) | 2005-06-01 | 2008-07-23 | 茵诺苏伦斯公司 | Motor vehicle traveling data collection and analysis |
US7327238B2 (en) | 2005-06-06 | 2008-02-05 | International Business Machines Corporation | Method, system, and computer program product for determining and reporting tailgating incidents |
DE102005026479B4 (en) | 2005-06-09 | 2017-04-20 | Daimler Ag | Method for inattention recognition as a function of at least one driver-individual parameter |
AU2006256372B2 (en) | 2005-06-09 | 2009-10-22 | Greenroad Driving Technologies Ltd. | System and method for displaying a driving profile |
US7693612B2 (en) | 2005-06-23 | 2010-04-06 | International Business Machines Corporation | Method and system for updating code embedded in a vehicle |
EP1904347B1 (en) | 2005-07-11 | 2011-09-28 | Volvo Technology Corporation | Methods and arrangement for performing driver identity verification |
WO2007019584A2 (en) | 2005-08-09 | 2007-02-15 | Icap Technologies, Inc. | Device and method relating to the emotional state of a person |
US7945358B2 (en) | 2005-08-18 | 2011-05-17 | Environmental Systems Products Holdings Inc. | System and method for testing the integrity of a vehicle testing/diagnostic system |
JP2007069719A (en) | 2005-09-06 | 2007-03-22 | Honda Access Corp | Data recording device for vehicle |
US20070088469A1 (en) | 2005-10-04 | 2007-04-19 | Oshkosh Truck Corporation | Vehicle control system and method |
US7663495B2 (en) | 2005-10-12 | 2010-02-16 | The Penn State Research Foundation | Vigilance monitoring technique for vehicle operators |
US8005467B2 (en) | 2005-10-14 | 2011-08-23 | General Motors Llc | Method and system for providing a telematics readiness mode |
US7733224B2 (en) | 2006-06-30 | 2010-06-08 | Bao Tran | Mesh network personal emergency response appliance |
AU2006304838B2 (en) | 2005-10-21 | 2011-07-28 | Deere & Company | Systems and methods for obstacle avoidance |
US7920944B2 (en) | 2005-10-21 | 2011-04-05 | General Motors Llc | Vehicle diagnostic test and reporting method |
JP4971625B2 (en) | 2005-11-14 | 2012-07-11 | 富士通テン株式会社 | Driving support device and driving information calculation system |
JP2007145200A (en) | 2005-11-28 | 2007-06-14 | Fujitsu Ten Ltd | Authentication device for vehicle and authentication method for vehicle |
US20070132773A1 (en) | 2005-12-08 | 2007-06-14 | Smartdrive Systems Inc | Multi-stage memory buffer and automatic transfers in vehicle event recording systems |
US10878646B2 (en) | 2005-12-08 | 2020-12-29 | Smartdrive Systems, Inc. | Vehicle event recorder systems |
US8626418B2 (en) | 2005-12-15 | 2014-01-07 | International Business Machines Corporation | Method and system for monitoring speed of a vehicle |
DE102005062019A1 (en) * | 2005-12-22 | 2007-06-28 | Robert Bosch Gmbh | Messages e.g. traffic messages, coding method for describing e.g. traffic congestion in road network, involves including supplementary messages in contents of messages, where supplementary messages contain supplementing message contents |
US9459622B2 (en) | 2007-01-12 | 2016-10-04 | Legalforce, Inc. | Driverless vehicle commerce network and community |
US7423540B2 (en) | 2005-12-23 | 2008-09-09 | Delphi Technologies, Inc. | Method of detecting vehicle-operator state |
US20140172727A1 (en) | 2005-12-23 | 2014-06-19 | Raj V. Abhyanker | Short-term automobile rentals in a geo-spatial environment |
US20070159354A1 (en) | 2006-01-09 | 2007-07-12 | Outland Research, Llc | Intelligent emergency vehicle alert system and user interface |
JPWO2007080921A1 (en) | 2006-01-13 | 2009-06-11 | 日本電気株式会社 | Information recording system, information recording apparatus, information recording method, and information collection program |
US7516010B1 (en) | 2006-01-27 | 2009-04-07 | Navteg North America, Llc | Method of operating a navigation system to provide parking availability information |
EP1984868A4 (en) | 2006-02-13 | 2010-08-25 | All Protect Llc | Method and system for controlling a vehicle given to a third party |
DE102006006850B4 (en) | 2006-02-15 | 2022-12-29 | Bayerische Motoren Werke Aktiengesellschaft | Method of aligning a pivotable vehicle sensor |
US20070208498A1 (en) | 2006-03-03 | 2007-09-06 | Inrix, Inc. | Displaying road traffic condition information and user controls |
GB0605069D0 (en) | 2006-03-14 | 2006-04-26 | Airmax Group Plc | Method and system for driver style monitoring and analysing |
US8996240B2 (en) | 2006-03-16 | 2015-03-31 | Smartdrive Systems, Inc. | Vehicle event recorders with integrated web server |
US8050863B2 (en) | 2006-03-16 | 2011-11-01 | Gray & Company, Inc. | Navigation and control system for autonomous vehicles |
US9201842B2 (en) | 2006-03-16 | 2015-12-01 | Smartdrive Systems, Inc. | Vehicle event recorder systems and networks having integrated cellular wireless communications systems |
EP2008257A2 (en) | 2006-03-30 | 2008-12-31 | Asher S. Saban | Protecting children and passengers with respect to a vehicle |
US20080106390A1 (en) | 2006-04-05 | 2008-05-08 | White Steven C | Vehicle power inhibiter |
US8314708B2 (en) | 2006-05-08 | 2012-11-20 | Drivecam, Inc. | System and method for reducing driving risk with foresight |
JP4965162B2 (en) | 2006-05-10 | 2012-07-04 | トヨタ自動車株式会社 | Arrhythmia monitoring device for vehicles |
US9635534B2 (en) | 2006-05-16 | 2017-04-25 | RedSky Technologies, Inc. | Method and system for an emergency location information service (E-LIS) from automated vehicles |
US8095394B2 (en) | 2006-05-18 | 2012-01-10 | Progressive Casualty Insurance Company | Rich claim reporting system |
US20080258890A1 (en) | 2006-05-22 | 2008-10-23 | Todd Follmer | System and Method for Remotely Deactivating a Vehicle |
US20080294690A1 (en) | 2007-05-22 | 2008-11-27 | Mcclellan Scott | System and Method for Automatically Registering a Vehicle Monitoring Device |
DE102006024606A1 (en) * | 2006-05-26 | 2007-11-29 | Bayerische Motoren Werke Ag | Method for functional testing of a control device for a motor vehicle |
US7498954B2 (en) | 2006-05-31 | 2009-03-03 | International Business Machines Corporation | Cooperative parking |
US20070282638A1 (en) | 2006-06-04 | 2007-12-06 | Martin Surovy | Route based method for determining cost of automobile insurance |
US7698086B2 (en) | 2006-06-08 | 2010-04-13 | Injury Sciences Llc | Method and apparatus for obtaining and using event data recorder triage data |
CN101466305B (en) | 2006-06-11 | 2012-05-30 | 沃尔沃技术公司 | Method for determining and analyzing a location of visual interest |
US8947531B2 (en) | 2006-06-19 | 2015-02-03 | Oshkosh Corporation | Vehicle diagnostics based on information communicated between vehicles |
US8139109B2 (en) | 2006-06-19 | 2012-03-20 | Oshkosh Corporation | Vision system for an autonomous vehicle |
US20130164715A1 (en) | 2011-12-24 | 2013-06-27 | Zonar Systems, Inc. | Using social networking to improve driver performance based on industry sharing of driver performance data |
US7813888B2 (en) | 2006-07-24 | 2010-10-12 | The Boeing Company | Autonomous vehicle rapid development testbed systems and methods |
US20080027761A1 (en) | 2006-07-25 | 2008-01-31 | Avraham Bracha | System and method for verifying driver's insurance coverage |
US7571682B2 (en) | 2006-08-07 | 2009-08-11 | Bianco Archangel J | Safe correlator system for automatic car wash |
US7570158B2 (en) | 2006-08-17 | 2009-08-04 | At&T Intellectual Property I, L.P. | Collaborative incident media recording system and related methods |
US7609150B2 (en) | 2006-08-18 | 2009-10-27 | Motorola, Inc. | User adaptive vehicle hazard warning apparatuses and method |
US8781442B1 (en) | 2006-09-08 | 2014-07-15 | Hti Ip, Llc | Personal assistance safety systems and methods |
US20080064014A1 (en) | 2006-09-12 | 2008-03-13 | Drivingmba Llc | Simulation-based novice driver instruction system and method |
DE602006015194D1 (en) | 2006-09-15 | 2010-08-12 | Saab Ab | Apparatus and method for generating input information for simulation equipment |
US20080082372A1 (en) | 2006-09-29 | 2008-04-03 | Burch Leon A | Driving simulator and method of evaluation of driver competency |
US8531521B2 (en) | 2006-10-06 | 2013-09-10 | Sightlogix, Inc. | Methods and apparatus related to improved surveillance using a smart camera |
JP4840069B2 (en) | 2006-10-12 | 2011-12-21 | アイシン・エィ・ダブリュ株式会社 | Navigation system |
US20080114530A1 (en) | 2006-10-27 | 2008-05-15 | Petrisor Gregory C | Thin client intelligent transportation system and method for use therein |
US8989959B2 (en) | 2006-11-07 | 2015-03-24 | Smartdrive Systems, Inc. | Vehicle operator performance history recording, scoring and reporting systems |
US8868288B2 (en) | 2006-11-09 | 2014-10-21 | Smartdrive Systems, Inc. | Vehicle exception event management systems |
US8532862B2 (en) | 2006-11-29 | 2013-09-10 | Ryan A. Neff | Driverless vehicle |
EP2110797B1 (en) | 2006-12-05 | 2015-10-07 | Fujitsu Limited | Traffic situation display method, traffic situation display system, vehicle-mounted device, and computer program |
US7813886B2 (en) | 2006-12-07 | 2010-10-12 | Picarro, Inc. | Calibration of frequency monitors having dual etalon signals in quadrature |
US20080147267A1 (en) | 2006-12-13 | 2008-06-19 | Smartdrive Systems Inc. | Methods of Discretizing data captured at event data recorders |
US8139820B2 (en) | 2006-12-13 | 2012-03-20 | Smartdrive Systems Inc. | Discretization facilities for vehicle event data recorders |
US20080143497A1 (en) | 2006-12-15 | 2008-06-19 | General Motors Corporation | Vehicle Emergency Communication Mode Method and Apparatus |
US7899560B2 (en) | 2007-01-09 | 2011-03-01 | Swiss Reinsurance Company | Electronic switching apparatus and method for switching autonomous intervention means for automatically redressing malfunctions |
US7792328B2 (en) | 2007-01-12 | 2010-09-07 | International Business Machines Corporation | Warning a vehicle operator of unsafe operation behavior based on a 3D captured image stream |
WO2008091621A1 (en) | 2007-01-23 | 2008-07-31 | Alan Goodrich | An unobitrusive system and method for monitoring the physiological condition of a target user of a vehicle |
US7692552B2 (en) | 2007-01-23 | 2010-04-06 | International Business Machines Corporation | Method and system for improving driver safety and situational awareness |
JP4400624B2 (en) | 2007-01-24 | 2010-01-20 | トヨタ自動車株式会社 | Dozing prevention device and method |
US20080180237A1 (en) | 2007-01-30 | 2008-07-31 | Fayyad Salem A | Vehicle emergency communication device and a method for transmitting emergency textual data utilizing the vehicle emergency communication device |
WO2008097499A1 (en) | 2007-02-02 | 2008-08-14 | Hartford Fire Insurance Company | Safety evaluation and feedback system and method |
JP5056067B2 (en) | 2007-02-26 | 2012-10-24 | 株式会社デンソー | Dozing alarm device |
US8123686B2 (en) | 2007-03-01 | 2012-02-28 | Abbott Diabetes Care Inc. | Method and apparatus for providing rolling data in communication systems |
JP4984974B2 (en) | 2007-03-02 | 2012-07-25 | 富士通株式会社 | Driving support system and in-vehicle device |
JP4720770B2 (en) | 2007-04-02 | 2011-07-13 | トヨタ自動車株式会社 | Information recording system for vehicles |
US7853375B2 (en) | 2007-04-10 | 2010-12-14 | Maurice Tuff | Vehicle monitor |
US8117049B2 (en) | 2007-04-10 | 2012-02-14 | Hti Ip, Llc | Methods, systems, and apparatuses for determining driver behavior |
US20080255887A1 (en) | 2007-04-10 | 2008-10-16 | Autoonline Gmbh Informationssysteme | Method and system for processing an insurance claim for a damaged vehicle |
US20080312969A1 (en) | 2007-04-20 | 2008-12-18 | Richard Raines | System and method for insurance underwriting and rating |
US20080258885A1 (en) | 2007-04-21 | 2008-10-23 | Synectic Systems Group Limited | System and method for recording environmental data in vehicles |
US8239092B2 (en) | 2007-05-08 | 2012-08-07 | Smartdrive Systems Inc. | Distributed vehicle event recorder systems having a portable memory data transfer system |
US10157422B2 (en) | 2007-05-10 | 2018-12-18 | Allstate Insurance Company | Road segment safety rating |
US9932033B2 (en) | 2007-05-10 | 2018-04-03 | Allstate Insurance Company | Route risk mitigation |
US10096038B2 (en) | 2007-05-10 | 2018-10-09 | Allstate Insurance Company | Road segment safety rating system |
KR100778059B1 (en) | 2007-05-22 | 2007-11-21 | (주)텔릭스타 | Apparatus and system blowing out dozing off motorways using facial recognition technology |
CA2685973C (en) | 2007-05-23 | 2017-08-22 | Otman A. Basir | Recording and reporting of driving characteristics using wireless mobile device |
WO2008151103A1 (en) | 2007-05-31 | 2008-12-11 | Hti Ip, Llc | Methods, systems, and apparatuses for consumer telematics |
JP4560739B2 (en) | 2007-06-29 | 2010-10-13 | アイシン・エィ・ダブリュ株式会社 | Own vehicle position recognition device and own vehicle position recognition program |
US7925423B2 (en) | 2007-08-31 | 2011-04-12 | Embarq Holdings Company, Llc | System and method for traffic condition detection |
US20090069953A1 (en) | 2007-09-06 | 2009-03-12 | University Of Alabama | Electronic control system and associated methodology of dynamically conforming a vehicle operation |
WO2009038797A2 (en) | 2007-09-20 | 2009-03-26 | Evolution Robotics | Robotic game systems and methods |
US8566126B1 (en) | 2007-09-24 | 2013-10-22 | United Services Automobile Association | Systems and methods for processing vehicle or driver performance data |
US8180655B1 (en) | 2007-09-24 | 2012-05-15 | United Services Automobile Association (Usaa) | Systems and methods for processing vehicle or driver performance data |
US7812740B2 (en) | 2007-09-27 | 2010-10-12 | Verizon Patent And Licensing Inc. | Systems, devices, and methods for providing alert tones |
US7719431B2 (en) | 2007-10-05 | 2010-05-18 | Gm Global Technology Operations, Inc. | Systems, methods and computer products for drowsy driver detection and response |
US20090106135A1 (en) | 2007-10-19 | 2009-04-23 | Robert James Steiger | Home warranty method and system |
US8065166B2 (en) | 2007-10-30 | 2011-11-22 | Onemednet Corporation | Methods, systems, and devices for managing medical images and records |
US20090132294A1 (en) | 2007-11-15 | 2009-05-21 | Haines Samuel H | Method for ranking driver's relative risk based on reported driving incidents |
US20090140887A1 (en) | 2007-11-29 | 2009-06-04 | Breed David S | Mapping Techniques Using Probe Vehicles |
US8031062B2 (en) | 2008-01-04 | 2011-10-04 | Smith Alexander E | Method and apparatus to improve vehicle situational awareness at intersections |
US9665910B2 (en) | 2008-02-20 | 2017-05-30 | Hartford Fire Insurance Company | System and method for providing customized safety feedback |
US8185330B2 (en) | 2008-03-26 | 2012-05-22 | Agilent Technologies, Inc. | Automatic placement of measurement gates |
US8019629B1 (en) | 2008-04-07 | 2011-09-13 | United Services Automobile Association (Usaa) | Systems and methods for automobile accident claims initiation |
US9026304B2 (en) | 2008-04-07 | 2015-05-05 | United Parcel Service Of America, Inc. | Vehicle maintenance systems and methods |
US8605947B2 (en) | 2008-04-24 | 2013-12-10 | GM Global Technology Operations LLC | Method for detecting a clear path of travel for a vehicle enhanced by object detection |
JP4547721B2 (en) | 2008-05-21 | 2010-09-22 | 株式会社デンソー | Automotive information provision system |
US20090300065A1 (en) | 2008-05-30 | 2009-12-03 | Birchall James T | Computer system and methods for improving identification of subrogation opportunities |
KR101141874B1 (en) | 2008-06-04 | 2012-05-08 | 주식회사 만도 | Apparatus, Method for Dectecting Critical Areas and Pedestrian Detection Apparatus Using Same |
US8068983B2 (en) | 2008-06-11 | 2011-11-29 | The Boeing Company | Virtual environment systems and methods |
US20100004995A1 (en) | 2008-07-07 | 2010-01-07 | Google Inc. | Claiming Real Estate in Panoramic or 3D Mapping Environments for Advertising |
US8346468B2 (en) | 2008-07-08 | 2013-01-01 | Sky-Trax Incorporated | Method and apparatus for collision avoidance |
BRPI0916722A2 (en) | 2008-07-31 | 2019-09-24 | Choicepoint Services Inc | steering performance data provision system and method of obtaining steering performance data |
KR101040118B1 (en) | 2008-08-04 | 2011-06-09 | 한국전자통신연구원 | Apparatus for reconstructing traffic accident and control method thereof |
US7973674B2 (en) | 2008-08-20 | 2011-07-05 | International Business Machines Corporation | Vehicle-to-vehicle traffic queue information communication system and method |
JP4602444B2 (en) | 2008-09-03 | 2010-12-22 | 株式会社日立製作所 | Driver driving skill support apparatus and driver driving skill support method |
US8140359B2 (en) | 2008-09-11 | 2012-03-20 | F3M3 Companies, Inc, | System and method for determining an objective driver score |
FR2936631B1 (en) | 2008-09-29 | 2011-03-25 | Act Concepts | METHOD AND DEVICE FOR AUTHENTICATING TRANSMITTED DATA RELATING TO THE USE OF A VEHICLE AND / OR BEHAVIOR OF ITS DRIVER |
JP2010086265A (en) | 2008-09-30 | 2010-04-15 | Fujitsu Ltd | Receiver, data display method, and movement support system |
KR101502012B1 (en) | 2008-10-06 | 2015-03-12 | 엘지전자 주식회사 | Telematics terminal and method for notifying emrergency condition using the same |
US8027853B1 (en) | 2008-10-23 | 2011-09-27 | United States Automobile Associates (USAA) | Systems and methods for self-service vehicle risk adjustment |
US20100106346A1 (en) | 2008-10-23 | 2010-04-29 | Honeywell International Inc. | Method and system for managing flight plan data |
US20100106514A1 (en) * | 2008-10-24 | 2010-04-29 | Sirius Xm Radio Inc. | Travel related services via SDARS |
US8126642B2 (en) | 2008-10-24 | 2012-02-28 | Gray & Company, Inc. | Control and systems for autonomously driven vehicles |
CN102292754B (en) | 2008-11-07 | 2014-07-30 | 沃尔沃拉斯特瓦格纳公司 | Method and system for combining sensor data |
US20100131300A1 (en) | 2008-11-26 | 2010-05-27 | Fred Collopy | Visible insurance |
US8473143B2 (en) | 2008-12-02 | 2013-06-25 | Caterpillar Inc. | System and method for accident logging in an automated machine |
JP2010164944A (en) | 2008-12-16 | 2010-07-29 | Olympus Corp | Projection optical system and visual display apparatus using the same |
TWI399565B (en) | 2008-12-31 | 2013-06-21 | Univ Nat Taiwan | Pressure sensing based localization and tracking system |
US20100198491A1 (en) | 2009-02-05 | 2010-08-05 | Paccar Inc | Autonomic vehicle safety system |
US8188887B2 (en) | 2009-02-13 | 2012-05-29 | Inthinc Technology Solutions, Inc. | System and method for alerting drivers to road conditions |
US8207698B2 (en) | 2009-02-24 | 2012-06-26 | Ford Global Technologies, Llc | Electric drive system for an automotive vehicle |
US8451105B2 (en) | 2009-02-25 | 2013-05-28 | James Holland McNay | Security and driver identification system |
US8054168B2 (en) | 2009-02-27 | 2011-11-08 | General Motors Llc | System and method for estimating an emergency level of a vehicular accident |
US9674458B2 (en) | 2009-06-03 | 2017-06-06 | Flir Systems, Inc. | Smart surveillance camera systems and methods |
US8244408B2 (en) | 2009-03-09 | 2012-08-14 | GM Global Technology Operations LLC | Method to assess risk associated with operating an autonomic vehicle control system |
US8332242B1 (en) | 2009-03-16 | 2012-12-11 | United Services Automobile Association (Usaa) | Systems and methods for real-time driving risk prediction and route recommendation |
US9727920B1 (en) | 2009-03-16 | 2017-08-08 | United Services Automobile Association (Usaa) | Insurance policy management using telematics |
US8040247B2 (en) | 2009-03-23 | 2011-10-18 | Toyota Motor Engineering & Manufacturing North America, Inc. | System for rapid detection of drowsiness in a machine operator |
US8108655B2 (en) | 2009-03-24 | 2012-01-31 | International Business Machines Corporation | Selecting fixed-point instructions to issue on load-store unit |
US8395529B2 (en) | 2009-04-02 | 2013-03-12 | GM Global Technology Operations LLC | Traffic infrastructure indicator on head-up display |
WO2010114620A1 (en) | 2009-04-03 | 2010-10-07 | Certusview Technologies, Llc | Methods, apparatus, and systems for documenting and reporting events via geo-referenced electronic drawings |
US8352112B2 (en) | 2009-04-06 | 2013-01-08 | GM Global Technology Operations LLC | Autonomous vehicle management |
BRPI0925336A2 (en) | 2009-04-07 | 2016-04-26 | Volvo Technology Corp | method and system for enhancing vehicle traffic safety and efficiency |
DE102009018761A1 (en) | 2009-04-27 | 2010-10-28 | Bayerische Motoren Werke Aktiengesellschaft | Process for updating software components |
US20100286845A1 (en) | 2009-05-11 | 2010-11-11 | Andrew Karl Wilhelm Rekow | Fail-safe system for autonomous vehicle |
WO2010132555A1 (en) | 2009-05-12 | 2010-11-18 | The Children's Hospital Of Philadelhia | Individualized mastery-based driver training |
US8751293B2 (en) | 2009-05-14 | 2014-06-10 | Microsoft Corporation | Delivering contextual advertising to a vehicle |
US20100299021A1 (en) | 2009-05-21 | 2010-11-25 | Reza Jalili | System and Method for Recording Data Associated with Vehicle Activity and Operation |
US9916625B2 (en) | 2012-02-02 | 2018-03-13 | Progressive Casualty Insurance Company | Mobile insurance platform system |
US8106769B1 (en) | 2009-06-26 | 2012-01-31 | United Services Automobile Association (Usaa) | Systems and methods for automated house damage detection and reporting |
US20110009093A1 (en) | 2009-07-13 | 2011-01-13 | Michael Self | Asynchronous voice and/or video communication system and method using wireless devices |
US8427326B2 (en) | 2009-07-30 | 2013-04-23 | Meir Ben David | Method and system for detecting the physiological onset of operator fatigue, drowsiness, or performance decrement |
FR2948759B1 (en) | 2009-07-31 | 2011-08-12 | Movea | METHOD FOR ESTIMATING THE ORIENTATION OF A SOLID IN MOTION |
CA2754159C (en) | 2009-08-11 | 2012-05-15 | Certusview Technologies, Llc | Systems and methods for complex event processing of vehicle-related information |
US9412130B2 (en) | 2009-08-19 | 2016-08-09 | Allstate Insurance Company | Assistance on the go |
US9384491B1 (en) | 2009-08-19 | 2016-07-05 | Allstate Insurance Company | Roadside assistance |
US8645014B1 (en) | 2009-08-19 | 2014-02-04 | Allstate Insurance Company | Assistance on the go |
US9552726B2 (en) | 2009-08-24 | 2017-01-24 | Here Global B.V. | Providing driving condition alerts using road attribute data |
EP2290633B1 (en) | 2009-08-31 | 2015-11-04 | Accenture Global Services Limited | Computer-implemented method for ensuring the privacy of a user, computer program product, device |
JP4816780B2 (en) | 2009-09-11 | 2011-11-16 | 株式会社デンソー | On-vehicle charge / discharge control device and partial control device included therein |
US8473131B2 (en) | 2009-09-28 | 2013-06-25 | Powerhydrant Llc | Method and system for charging electric vehicles |
US8645005B2 (en) | 2009-10-01 | 2014-02-04 | Alfred B. Elkins | Multipurpose modular airship systems and methods |
WO2011047125A1 (en) | 2009-10-14 | 2011-04-21 | Summit Mobile Solutions, Inc. | Method and system for damage reporting and repair |
US8253589B2 (en) | 2009-10-20 | 2012-08-28 | GM Global Technology Operations LLC | Vehicle to entity communication |
US8604920B2 (en) | 2009-10-20 | 2013-12-10 | Cartasite, Inc. | Systems and methods for vehicle performance analysis and presentation |
US9082308B2 (en) | 2009-10-20 | 2015-07-14 | Cartasite Inc. | Driver performance analysis and consequence |
WO2011057217A2 (en) | 2009-11-06 | 2011-05-12 | University Of Utah Research Foundation | Method for gathering, processing, and analyzing data to determine crash risk associated with driving behavior |
US8339268B2 (en) | 2009-11-10 | 2012-12-25 | GM Global Technology Operations LLC | Driver configurable drowsiness prevention |
WO2011060388A1 (en) | 2009-11-13 | 2011-05-19 | Zoll Medical Corporation | Community-based response system |
US8423239B2 (en) | 2009-11-23 | 2013-04-16 | Hti Ip, L.L.C. | Method and system for adjusting a charge related to use of a vehicle during a period based on operational performance data |
US8386168B2 (en) | 2009-11-24 | 2013-02-26 | Verizon Patent And Licensing Inc. | Traffic data collection in a navigational system |
US20110128161A1 (en) | 2009-11-30 | 2011-06-02 | Gm Global Technology Operations, Inc. | Vehicular warning device for pedestrians |
KR101081129B1 (en) * | 2009-11-30 | 2011-11-07 | 엘지이노텍 주식회사 | Light emitting device and fabrication method thereof |
US20120056758A1 (en) | 2009-12-03 | 2012-03-08 | Delphi Technologies, Inc. | Vehicle parking spot locator system and method using connected vehicles |
JP5045796B2 (en) | 2009-12-03 | 2012-10-10 | 株式会社デンソー | Vehicle approach warning system, portable warning terminal, and in-vehicle communication device |
DE102009056786A1 (en) | 2009-12-03 | 2011-06-09 | Continental Automotive Gmbh | Mobile interface and system for controlling vehicle functions |
US20110137684A1 (en) | 2009-12-08 | 2011-06-09 | Peak David F | System and method for generating telematics-based customer classifications |
US8452482B2 (en) | 2009-12-10 | 2013-05-28 | GM Global Technology Operations LLC | Self testing systems and methods |
JP5269755B2 (en) | 2009-12-10 | 2013-08-21 | 株式会社日立製作所 | Cross-person support vehicle system and cross-person support method |
US8742987B2 (en) | 2009-12-10 | 2014-06-03 | GM Global Technology Operations LLC | Lean V2X security processing strategy using kinematics information of vehicles |
US8635091B2 (en) | 2009-12-17 | 2014-01-21 | Hartford Fire Insurance Company | Systems and methods for linking vehicles to telematics-enabled portable devices |
US20110161119A1 (en) | 2009-12-24 | 2011-06-30 | The Travelers Companies, Inc. | Risk assessment and control, insurance premium determinations, and other applications using busyness |
US20110304465A1 (en) | 2009-12-30 | 2011-12-15 | Boult Terrance E | System and method for driver reaction impairment vehicle exclusion via systematic measurement for assurance of reaction time |
US9558520B2 (en) | 2009-12-31 | 2017-01-31 | Hartford Fire Insurance Company | System and method for geocoded insurance processing using mobile devices |
US8805707B2 (en) | 2009-12-31 | 2014-08-12 | Hartford Fire Insurance Company | Systems and methods for providing a safety score associated with a user location |
WO2011086661A1 (en) | 2010-01-12 | 2011-07-21 | トヨタ自動車株式会社 | Collision position predicting device |
US8384534B2 (en) | 2010-01-14 | 2013-02-26 | Toyota Motor Engineering & Manufacturing North America, Inc. | Combining driver and environment sensing for vehicular safety systems |
DE102010001006A1 (en) | 2010-01-19 | 2011-07-21 | Robert Bosch GmbH, 70469 | Car accident information providing method for insurance company, involves information about accident is transmitted from sensor to data processing unit of driverless car by communication module of car over network connection |
US20110190972A1 (en) | 2010-02-02 | 2011-08-04 | Gm Global Technology Operations, Inc. | Grid unlock |
US9254781B2 (en) | 2010-02-02 | 2016-02-09 | Craig David Applebaum | Emergency vehicle warning device and system |
US20110196571A1 (en) | 2010-02-09 | 2011-08-11 | At&T Mobility Ii Llc | System And Method For The Collection And Monitoring Of Vehicle Data |
US20120010906A1 (en) | 2010-02-09 | 2012-01-12 | At&T Mobility Ii Llc | System And Method For The Collection And Monitoring Of Vehicle Data |
US20120004933A1 (en) | 2010-02-09 | 2012-01-05 | At&T Mobility Ii Llc | System And Method For The Collection And Monitoring Of Vehicle Data |
US9043041B2 (en) | 2010-02-12 | 2015-05-26 | Webtech Wireless Inc. | Monitoring aggressive driving operation of a mobile asset |
US20110251751A1 (en) | 2010-03-11 | 2011-10-13 | Lee Knight | Motorized equipment tracking and monitoring apparatus, system and method |
EP2544914B1 (en) | 2010-03-12 | 2019-03-13 | Tata Consultancy Services Ltd. | A system for vehicle security, personalization and cardiac activity monitoring of a driver |
US8618922B2 (en) | 2010-03-30 | 2013-12-31 | GM Global Technology Operations LLC | Method and system for ensuring operation of limited-ability autonomous driving vehicles |
US9189485B2 (en) | 2010-04-26 | 2015-11-17 | Hitachi, Ltd. | Time-series data diagnosing/compressing method |
US8548646B1 (en) | 2010-05-04 | 2013-10-01 | Clearpath Robotics Inc. | Distributed hardware architecture for unmanned vehicles |
US20110279263A1 (en) | 2010-05-13 | 2011-11-17 | Ryan Scott Rodkey | Event Detection |
US20120109692A1 (en) | 2010-05-17 | 2012-05-03 | The Travelers Indemnity Company | Monitoring customer-selected vehicle parameters in accordance with customer preferences |
US20120101855A1 (en) | 2010-05-17 | 2012-04-26 | The Travelers Indemnity Company | Monitoring client-selected vehicle parameters in accordance with client preferences |
WO2011146466A2 (en) * | 2010-05-17 | 2011-11-24 | The Travelers Companies, Inc. | Monitoring customer-selected vehicle parameters |
US20160086393A1 (en) | 2010-05-17 | 2016-03-24 | The Travelers Indemnity Company | Customized vehicle monitoring privacy system |
US8258978B2 (en) | 2010-05-19 | 2012-09-04 | Garmin Switzerland Gmbh | Speed limit change notification |
US8700353B2 (en) | 2010-05-27 | 2014-04-15 | Incheck Technologies, Inc. | MEMS accelerometer device |
US8744745B2 (en) | 2010-06-08 | 2014-06-03 | General Motors Llc | Method of using vehicle location information with a wireless mobile device |
DK2405132T3 (en) | 2010-07-09 | 2016-08-15 | Siemens Ag | Wind turbine, drive assembly, wind turbine cell system, methods of converting rotational energy and methods for building a nacelle and for re-equipping a wind turbine |
JP2012022837A (en) | 2010-07-13 | 2012-02-02 | Canon Inc | Image display unit |
US9418554B2 (en) | 2014-08-07 | 2016-08-16 | Verizon Patent And Licensing Inc. | Method and system for determining road conditions based on driver data |
KR101605453B1 (en) | 2010-08-25 | 2016-04-01 | 네이버 주식회사 | Internet telematics service providing system and internet telematics service providing method for providing mileage-related driving information |
GB2483251A (en) | 2010-09-01 | 2012-03-07 | Ricardo Uk Ltd | Driver feedback system and method |
US8968197B2 (en) | 2010-09-03 | 2015-03-03 | International Business Machines Corporation | Directing a user to a medical resource |
US20120062392A1 (en) | 2010-09-14 | 2012-03-15 | Ferrick David P | System and Method for Protecting Assets from Harm and for Reducing Insurance Risk |
US20120066007A1 (en) | 2010-09-14 | 2012-03-15 | Ferrick David P | System and Method for Tracking and Sharing Driving Metrics with a Plurality of Insurance Carriers |
US8750853B2 (en) | 2010-09-21 | 2014-06-10 | Cellepathy Ltd. | Sensor-based determination of user role, location, and/or state of one or more in-vehicle mobile devices and enforcement of usage thereof |
US20120083668A1 (en) | 2010-09-30 | 2012-04-05 | Anantha Pradeep | Systems and methods to modify a characteristic of a user device based on a neurological and/or physiological measurement |
US9296299B2 (en) | 2011-11-16 | 2016-03-29 | Autoconnect Holdings Llc | Behavioral tracking and vehicle applications |
US8509982B2 (en) | 2010-10-05 | 2013-08-13 | Google Inc. | Zone driving |
US8447231B2 (en) | 2010-10-29 | 2013-05-21 | GM Global Technology Operations LLC | Intelligent telematics information dissemination using delegation, fetch, and share algorithms |
US8718054B2 (en) | 2010-11-03 | 2014-05-06 | Broadcom Corporation | Bridge routing module |
US20120108909A1 (en) | 2010-11-03 | 2012-05-03 | HeadRehab, LLC | Assessment and Rehabilitation of Cognitive and Motor Functions Using Virtual Reality |
KR20120058230A (en) | 2010-11-29 | 2012-06-07 | 한국전자통신연구원 | Safe operation apparatus for mobile objects and method thereof |
US9507413B2 (en) | 2010-12-03 | 2016-11-29 | Continental Automotive Systems, Inc. | Tailoring vehicle human machine interface |
US20120143630A1 (en) | 2010-12-07 | 2012-06-07 | International Business Machines Corporation | Third party verification of insurable incident claim submission |
EP2652718B1 (en) | 2010-12-15 | 2018-09-26 | Andrew William Wright | Method and system for logging vehicle behaviour |
US9026134B2 (en) | 2011-01-03 | 2015-05-05 | Qualcomm Incorporated | Target positioning within a mobile structure |
EP2666138A4 (en) | 2011-01-17 | 2014-08-06 | Imetrik Technologies Inc | Computer-implemented method and system for reporting a confidence score in relation to a vehicle equipped with a wireless-enabled usage reporting device |
US9086297B2 (en) | 2011-01-20 | 2015-07-21 | Telenav, Inc. | Navigation system having maneuver attempt training mechanism and method of operation thereof |
US8788220B2 (en) | 2011-01-21 | 2014-07-22 | The United States Of America As Represented By The Secretary Of The Navy | Vehicle damage detection system |
US8928495B2 (en) | 2011-01-24 | 2015-01-06 | Lexisnexis Risk Solutions Inc. | Systems and methods for telematics monitoring and communications |
CA2764829A1 (en) | 2011-01-25 | 2012-07-25 | Hemisphere Centre for Mental Health & Wellness Inc. | Automated cognitive testing methods and applications therefor |
KR20120086140A (en) | 2011-01-25 | 2012-08-02 | 한국전자통신연구원 | Mobile and apparatus for providing auto valet parking service and method thereof |
US20120197669A1 (en) | 2011-01-27 | 2012-08-02 | Kote Thejovardhana S | Determining Cost of Auto Insurance |
EP2484573B1 (en) | 2011-02-08 | 2017-12-13 | Volvo Car Corporation | Method for reducing the risk of a collision between a vehicle and a first external object |
JP5729861B2 (en) | 2011-02-08 | 2015-06-03 | 本田技研工業株式会社 | Vehicle driving support device |
US8902054B2 (en) | 2011-02-10 | 2014-12-02 | Sitting Man, Llc | Methods, systems, and computer program products for managing operation of a portable electronic device |
US8698639B2 (en) | 2011-02-18 | 2014-04-15 | Honda Motor Co., Ltd. | System and method for responding to driver behavior |
US8731736B2 (en) | 2011-02-22 | 2014-05-20 | Honda Motor Co., Ltd. | System and method for reducing driving skill atrophy |
US9542846B2 (en) | 2011-02-28 | 2017-01-10 | GM Global Technology Operations LLC | Redundant lane sensing systems for fault-tolerant vehicular lateral controller |
US8725311B1 (en) | 2011-03-14 | 2014-05-13 | American Vehicular Sciences, LLC | Driver health and fatigue monitoring system and method |
US9928524B2 (en) | 2011-03-14 | 2018-03-27 | GM Global Technology Operations LLC | Learning driver demographics from vehicle trace data |
EP2500887B1 (en) | 2011-03-17 | 2020-09-09 | Harman Becker Automotive Systems GmbH | Description of a Road Segment Using ISO 17572-3 |
US8593277B2 (en) | 2011-03-17 | 2013-11-26 | Kaarya, LLC. | System and method for proximity detection |
US8880289B2 (en) | 2011-03-17 | 2014-11-04 | Toyota Motor Engineering & Manufacturing North America, Inc. | Vehicle maneuver application interface |
WO2012129437A2 (en) | 2011-03-23 | 2012-09-27 | Tk Holdings Inc. | Driver assistance system |
JP2012222435A (en) | 2011-04-05 | 2012-11-12 | Denso Corp | Portable terminal, vehicle-mounted device, communication system, program for portable terminal, and control method |
US20120256769A1 (en) | 2011-04-07 | 2012-10-11 | GM Global Technology Operations LLC | System and method for real-time detection of an emergency situation occuring in a vehicle |
DE102011016772B4 (en) | 2011-04-12 | 2024-04-25 | Mercedes-Benz Group AG | 12.04.2021Method and device for monitoring at least one vehicle occupant and method for operating at least one assistance device |
US20120271500A1 (en) | 2011-04-20 | 2012-10-25 | GM Global Technology Operations LLC | System and method for enabling a driver to input a vehicle control instruction into an autonomous vehicle controller |
US8665118B1 (en) * | 2011-04-21 | 2014-03-04 | Google Inc. | Parking information aggregation platform |
US9581997B1 (en) | 2011-04-22 | 2017-02-28 | Angel A. Penilla | Method and system for cloud-based communication for automatic driverless movement |
US9424606B2 (en) | 2011-04-28 | 2016-08-23 | Allstate Insurance Company | Enhanced claims settlement |
WO2012150591A2 (en) | 2011-05-03 | 2012-11-08 | Alon Atsmon | Automatic content analysis method and system |
US20120289819A1 (en) | 2011-05-09 | 2012-11-15 | Allergan, Inc. | Implant detector |
US20120286974A1 (en) | 2011-05-11 | 2012-11-15 | Siemens Corporation | Hit and Run Prevention and Documentation System for Vehicles |
US9229450B2 (en) | 2011-05-31 | 2016-01-05 | Hitachi, Ltd. | Autonomous movement system |
US8466807B2 (en) | 2011-06-01 | 2013-06-18 | GM Global Technology Operations LLC | Fast collision detection technique for connected autonomous and manual vehicles |
US20120316455A1 (en) | 2011-06-10 | 2012-12-13 | Aliphcom | Wearable device and platform for sensory input |
US20130006674A1 (en) | 2011-06-29 | 2013-01-03 | State Farm Insurance | Systems and Methods Using a Mobile Device to Collect Data for Insurance Premiums |
US20110307188A1 (en) | 2011-06-29 | 2011-12-15 | State Farm Insurance | Systems and methods for providing driver feedback using a handheld mobile device |
KR20130004824A (en) | 2011-07-04 | 2013-01-14 | 현대자동차주식회사 | Vehicle control system |
US8762044B2 (en) | 2011-07-13 | 2014-06-24 | Dynamic Research, Inc. | System and method for testing crash avoidance technologies |
US9165470B2 (en) | 2011-07-25 | 2015-10-20 | GM Global Technology Operations LLC | Autonomous convoying technique for vehicles |
DE102011109564B4 (en) | 2011-08-05 | 2024-05-02 | Mercedes-Benz Group AG | Method and device for monitoring at least one vehicle occupant and method for operating at least one assistance device |
US20130038437A1 (en) | 2011-08-08 | 2013-02-14 | Panasonic Corporation | System for task and notification handling in a connected car |
US8554468B1 (en) | 2011-08-12 | 2013-10-08 | Brian Lee Bullock | Systems and methods for driver performance assessment and improvement |
DE102011110486A1 (en) * | 2011-08-17 | 2013-02-21 | Daimler Ag | Method and device for monitoring at least one vehicle occupant and method for operating at least one assistance device |
US8538785B2 (en) | 2011-08-19 | 2013-09-17 | Hartford Fire Insurance Company | System and method for computing and scoring the complexity of a vehicle trip using geo-spatial information |
US20130044008A1 (en) | 2011-08-19 | 2013-02-21 | Gpsi, Llc | Enhanced emergency system using a hazard light device |
EP2564765B1 (en) | 2011-09-02 | 2017-12-13 | Volvo Car Corporation | System and method for improving a performance estimation of an operator of a vehicle |
MX337513B (en) | 2011-09-19 | 2016-03-09 | Tata Consultancy Services Ltd | A computing platform for development and deployment of sensor-driven vehicle telemetry applications and services. |
US20130073193A1 (en) | 2011-09-19 | 2013-03-21 | Cambridge Silicon Radio Limited | Collaborative traffic monitoring |
US20160189544A1 (en) | 2011-11-16 | 2016-06-30 | Autoconnect Holdings Llc | Method and system for vehicle data collection regarding traffic |
US20130131907A1 (en) | 2011-11-17 | 2013-05-23 | GM Global Technology Operations LLC | System and method for managing misuse of autonomous driving |
US20130144652A1 (en) | 2011-12-02 | 2013-06-06 | Children's Medical Center Corporation | Systems and methods for assessing medical record complexity and risk of adverse events |
US20130227409A1 (en) | 2011-12-07 | 2013-08-29 | Qualcomm Incorporated | Integrating sensation functionalities into social networking services and applications |
US9008853B2 (en) | 2011-12-07 | 2015-04-14 | GM Global Technology Operations LLC | Vehicle operator identification and operator-configured services |
CN103188647A (en) | 2011-12-29 | 2013-07-03 | 北京网秦天下科技有限公司 | Method and system for statistically analyzing and warning Internet surfing flow of mobile terminal |
US8915738B2 (en) | 2012-01-24 | 2014-12-23 | Toyota Motor Engineering & Manufacturing North America, Inc. | Driver quality assessment for driver education |
US9650762B2 (en) | 2012-01-24 | 2017-05-16 | Harnischfeger Technologies, Inc. | System and method for monitoring mining machine efficiency |
US9381916B1 (en) | 2012-02-06 | 2016-07-05 | Google Inc. | System and method for predicting behaviors of detected objects through environment representation |
DE102012002695A1 (en) | 2012-02-14 | 2013-08-14 | Wabco Gmbh | Method for determining an emergency braking situation of a vehicle |
US10657597B1 (en) * | 2012-02-17 | 2020-05-19 | United Services Automobile Association (Usaa) | Systems and methods for dynamic insurance premiums |
US20130218604A1 (en) | 2012-02-21 | 2013-08-22 | Elwha Llc | Systems and methods for insurance based upon monitored characteristics of a collision detection system |
US20130218603A1 (en) | 2012-02-21 | 2013-08-22 | Elwha Llc | Systems and methods for insurance based upon characteristics of a collision detection system |
US9299108B2 (en) | 2012-02-24 | 2016-03-29 | Tata Consultancy Services Limited | Insurance claims processing |
US20130226624A1 (en) | 2012-02-24 | 2013-08-29 | B3, Llc | Systems and methods for comprehensive insurance loss management and loss minimization |
DE102012202914A1 (en) | 2012-02-27 | 2013-08-29 | Robert Bosch Gmbh | Diagnostic method and diagnostic device for a vehicle component of a vehicle |
DE102012101686A1 (en) | 2012-03-01 | 2013-09-05 | Continental Teves Ag & Co. Ohg | Method for a driver assistance system for the autonomous longitudinal and / or transverse control of a vehicle |
US9429943B2 (en) | 2012-03-05 | 2016-08-30 | Florida A&M University | Artificial intelligence valet systems and methods |
US20130245881A1 (en) | 2012-03-14 | 2013-09-19 | Christopher G. Scarbrough | System and Method for Monitoring the Environment In and Around an Automobile |
US9235941B2 (en) | 2012-03-14 | 2016-01-12 | Autoconnect Holdings Llc | Simultaneous video streaming across multiple channels |
US8340902B1 (en) | 2012-03-15 | 2012-12-25 | Yan-Hong Chiang | Remote vehicle management system by video radar |
GB2500581B (en) | 2012-03-23 | 2014-08-20 | Jaguar Land Rover Ltd | Method and system for controlling the output of information to a driver based on an estimated driver workload |
US8847781B2 (en) | 2012-03-28 | 2014-09-30 | Sony Corporation | Building management system with privacy-guarded assistance mechanism and method of operation thereof |
DE102012007119A1 (en) | 2012-04-05 | 2013-10-24 | Audi Ag | Method for operating a motor vehicle during and / or after a collision |
US8791838B2 (en) | 2012-04-10 | 2014-07-29 | Inrix, Inc. | Parking resource management |
US8589065B2 (en) | 2012-04-10 | 2013-11-19 | Inrix, Inc. | Parking based route navigation |
US8718861B1 (en) | 2012-04-11 | 2014-05-06 | Google Inc. | Determining when to drive autonomously |
US8700251B1 (en) | 2012-04-13 | 2014-04-15 | Google Inc. | System and method for automatically detecting key behaviors by vehicles |
US20130278441A1 (en) | 2012-04-24 | 2013-10-24 | Zetta Research and Development, LLC - ForC Series | Vehicle proxying |
DE102012008858A1 (en) | 2012-04-28 | 2012-11-08 | Daimler Ag | Method for performing autonomous parking process of motor vehicle e.g. passenger car, involves storing target position and/or last driven trajectory of vehicle in suitable device prior to start of autonomous vehicle parking operation |
US20130304514A1 (en) | 2012-05-08 | 2013-11-14 | Elwha Llc | Systems and methods for insurance based on monitored characteristics of an autonomous drive mode selection system |
US8595037B1 (en) | 2012-05-08 | 2013-11-26 | Elwha Llc | Systems and methods for insurance based on monitored characteristics of an autonomous drive mode selection system |
US8781669B1 (en) | 2012-05-14 | 2014-07-15 | Google Inc. | Consideration of risks in active sensing for an autonomous vehicle |
US9891709B2 (en) | 2012-05-16 | 2018-02-13 | Immersion Corporation | Systems and methods for content- and context specific haptic effects using predefined haptic effects |
US8880291B2 (en) | 2012-05-17 | 2014-11-04 | Harman International Industries, Inc. | Methods and systems for preventing unauthorized vehicle operation using face recognition |
US9037394B2 (en) * | 2012-05-22 | 2015-05-19 | Hartford Fire Insurance Company | System and method to determine an initial insurance policy benefit based on telematics data collected by a smartphone |
US8768565B2 (en) | 2012-05-23 | 2014-07-01 | Enterprise Holdings, Inc. | Rental/car-share vehicle access and management system and method |
US20130317786A1 (en) | 2012-05-24 | 2013-11-28 | Fluor Technologies Corporation | Feature-based rapid structure modeling system |
US10387960B2 (en) | 2012-05-24 | 2019-08-20 | State Farm Mutual Automobile Insurance Company | System and method for real-time accident documentation and claim submission |
US8917182B2 (en) | 2012-06-06 | 2014-12-23 | Honda Motor Co., Ltd. | System and method for detecting and preventing drowsiness |
US9020876B2 (en) | 2012-06-07 | 2015-04-28 | International Business Machines Corporation | On-demand suggestion for vehicle driving |
US20130339062A1 (en) | 2012-06-14 | 2013-12-19 | Seth Brewer | System and method for use of social networks to respond to insurance related events |
US9183163B2 (en) | 2012-06-27 | 2015-11-10 | Ubiquiti Networks, Inc. | Method and apparatus for distributed control of an interfacing-device network |
US20140004734A1 (en) | 2012-06-27 | 2014-01-02 | Phan F. Hoang | Insertion tool for memory modules |
US20140002651A1 (en) | 2012-06-30 | 2014-01-02 | James Plante | Vehicle Event Recorder Systems |
US9165469B2 (en) | 2012-07-09 | 2015-10-20 | Elwha Llc | Systems and methods for coordinating sensor operation for collision detection |
US9558667B2 (en) | 2012-07-09 | 2017-01-31 | Elwha Llc | Systems and methods for cooperative collision detection |
JP5857898B2 (en) * | 2012-07-11 | 2016-02-10 | 三菱電機株式会社 | Power amplifier |
DE102012106522A1 (en) | 2012-07-18 | 2014-01-23 | Huf Hülsbeck & Fürst Gmbh & Co. Kg | Method for authenticating a driver in a motor vehicle |
US9038436B2 (en) | 2012-07-30 | 2015-05-26 | Alcotek, Inc. | Fuel cell for use in an alcohol breath tester |
US20140039934A1 (en) | 2012-08-01 | 2014-02-06 | Gabriel Ernesto RIVERA | Insurance verification system (insvsys) |
US20140047371A1 (en) | 2012-08-10 | 2014-02-13 | Smartdrive Systems Inc. | Vehicle Event Playback Apparatus and Methods |
US10380905B2 (en) | 2012-08-10 | 2019-08-13 | Xrs Corporation | Network communications for transportation management |
WO2014028010A2 (en) | 2012-08-15 | 2014-02-20 | Empire Technology Development Llc | Estimating insurance risks and costs |
US8862321B2 (en) | 2012-08-15 | 2014-10-14 | GM Global Technology Operations LLC | Directing vehicle into feasible region for autonomous and semi-autonomous parking |
DE102012017497B3 (en) | 2012-08-17 | 2013-12-05 | Audi Ag | Traffic system for autonomous driving and method for determining a vehicle damage |
CA2882603A1 (en) | 2012-08-21 | 2014-02-27 | Insurance Services Office, Inc. | Apparatus and method for analyzing driving performance data |
DE102012214852B4 (en) | 2012-08-21 | 2024-01-18 | Robert Bosch Gmbh | Method and device for selecting objects in the surroundings of a vehicle |
US20140059066A1 (en) | 2012-08-24 | 2014-02-27 | EmoPulse, Inc. | System and method for obtaining and using user physiological and emotional data |
US8996228B1 (en) | 2012-09-05 | 2015-03-31 | Google Inc. | Construction zone object detection using light detection and ranging |
US9056395B1 (en) | 2012-09-05 | 2015-06-16 | Google Inc. | Construction zone sign detection using light detection and ranging |
KR102075110B1 (en) | 2012-09-07 | 2020-02-10 | 주식회사 만도 | Apparatus of identificating vehicle based vehicle-to-vehicle communication, and method of thereof |
US9221396B1 (en) | 2012-09-27 | 2015-12-29 | Google Inc. | Cross-validating sensors of an autonomous vehicle |
US9665101B1 (en) | 2012-09-28 | 2017-05-30 | Waymo Llc | Methods and systems for transportation to destinations by a self-driving vehicle |
US9188985B1 (en) | 2012-09-28 | 2015-11-17 | Google Inc. | Suggesting a route based on desired amount of driver interaction |
JP5920743B2 (en) | 2012-09-28 | 2016-05-18 | 株式会社日立製作所 | Autonomous mobile device and autonomous mobile system |
US9274525B1 (en) | 2012-09-28 | 2016-03-01 | Google Inc. | Detecting sensor degradation by actively controlling an autonomous vehicle |
US9156476B2 (en) | 2012-10-02 | 2015-10-13 | Trevor O'Neill | System and method for remote control of unmanned vehicles |
US20140095214A1 (en) | 2012-10-03 | 2014-04-03 | Robert E. Mathe | Systems and methods for providing a driving performance platform |
WO2014059084A1 (en) | 2012-10-11 | 2014-04-17 | Automatic Labs, Inc. | Reputation system based on driving behavior |
US9566908B2 (en) | 2012-10-12 | 2017-02-14 | Newtrax Hodlings inc | Context-aware collision devices and collision avoidance system comprising the same |
US9282436B2 (en) | 2012-10-17 | 2016-03-08 | Cellco Partnership | Method and system for adaptive location determination for mobile device |
CN105050868B (en) | 2012-10-17 | 2018-12-21 | 安全堡垒有限责任公司 | Equipment for detecting and preventing the attack to the vehicles |
US9443207B2 (en) | 2012-10-22 | 2016-09-13 | The Boeing Company | Water area management system |
US20140114692A1 (en) | 2012-10-23 | 2014-04-24 | InnovaPad, LP | System for Integrating First Responder and Insurance Information |
US9489635B1 (en) | 2012-11-01 | 2016-11-08 | Google Inc. | Methods and systems for vehicle perception feedback to classify data representative of types of objects and to request feedback regarding such classifications |
US9007198B2 (en) | 2012-11-02 | 2015-04-14 | Toyota Motor Engineering & Manufacturing North America, Inc. | Adaptive Actuator interface for active driver warning |
US20140129301A1 (en) | 2012-11-07 | 2014-05-08 | Ford Global Technologies, Llc | Mobile automotive wireless communication system enabled microbusinesses |
US8880239B2 (en) | 2012-11-07 | 2014-11-04 | Ford Global Technologies, Llc | Credential check and authorization solution for personal vehicle rental |
DE102012022336A1 (en) | 2012-11-14 | 2014-05-15 | Valeo Schalter Und Sensoren Gmbh | Method for carrying out an at least semi-autonomous parking operation of a motor vehicle in a garage, parking assistance system and motor vehicle |
US20150006023A1 (en) | 2012-11-16 | 2015-01-01 | Scope Technologies Holdings Ltd | System and method for determination of vheicle accident information |
DE102012111991A1 (en) | 2012-11-20 | 2014-05-22 | Conti Temic Microelectronic Gmbh | Method for a driver assistance application |
US20150338227A1 (en) | 2012-11-22 | 2015-11-26 | Freescale Semiconductor, Inc. | Navigation system |
US20140149148A1 (en) | 2012-11-27 | 2014-05-29 | Terrance Luciani | System and method for autonomous insurance selection |
US8457880B1 (en) | 2012-11-28 | 2013-06-04 | Cambridge Mobile Telematics | Telematics using personal mobile devices |
US9031729B2 (en) | 2012-11-29 | 2015-05-12 | Volkswagen Ag | Method and system for controlling a vehicle |
US8825258B2 (en) | 2012-11-30 | 2014-09-02 | Google Inc. | Engaging and disengaging for autonomous driving |
US8914225B2 (en) | 2012-12-04 | 2014-12-16 | International Business Machines Corporation | Managing vehicles on a road network |
US20140159856A1 (en) | 2012-12-12 | 2014-06-12 | Thorsten Meyer | Sensor hierarchy |
US8930269B2 (en) | 2012-12-17 | 2015-01-06 | State Farm Mutual Automobile Insurance Company | System and method to adjust insurance rate based on real-time data about potential vehicle operator impairment |
US8981942B2 (en) | 2012-12-17 | 2015-03-17 | State Farm Mutual Automobile Insurance Company | System and method to monitor and reduce vehicle operator impairment |
US9081650B1 (en) | 2012-12-19 | 2015-07-14 | Allstate Insurance Company | Traffic based driving analysis |
US10796510B2 (en) | 2012-12-20 | 2020-10-06 | Brett I. Walker | Apparatus, systems and methods for monitoring vehicular activity |
US9761139B2 (en) | 2012-12-20 | 2017-09-12 | Wal-Mart Stores, Inc. | Location based parking management system |
US9443436B2 (en) | 2012-12-20 | 2016-09-13 | The Johns Hopkins University | System for testing of autonomy in complex environments |
KR101449210B1 (en) | 2012-12-27 | 2014-10-08 | 현대자동차주식회사 | Apparatus for converting driving mode of autonomous vehicle and method thereof |
US9665997B2 (en) | 2013-01-08 | 2017-05-30 | Gordon*Howard Associates, Inc. | Method and system for providing feedback based on driving behavior |
US8909428B1 (en) | 2013-01-09 | 2014-12-09 | Google Inc. | Detecting driver grip on steering wheel |
US10713726B1 (en) | 2013-01-13 | 2020-07-14 | United Services Automobile Association (Usaa) | Determining insurance policy modifications using informatic sensor data |
KR102002420B1 (en) | 2013-01-18 | 2019-10-01 | 삼성전자주식회사 | Smart home system with portable gateway |
US9049584B2 (en) | 2013-01-24 | 2015-06-02 | Ford Global Technologies, Llc | Method and system for transmitting data using automated voice when data transmission fails during an emergency call |
GB201301710D0 (en) | 2013-01-31 | 2013-03-20 | Cambridge Consultants | Condition Monitoring Device |
US9149236B2 (en) | 2013-02-04 | 2015-10-06 | Intel Corporation | Assessment and management of emotional state of a vehicle operator |
KR101736306B1 (en) | 2013-02-27 | 2017-05-29 | 한국전자통신연구원 | Apparatus and method for copiloting between vehicle and driver |
US20140240132A1 (en) | 2013-02-28 | 2014-08-28 | Exmovere Wireless LLC | Method and apparatus for determining vehicle operator performance |
US10386492B2 (en) | 2013-03-07 | 2019-08-20 | Trimble Inc. | Verifiable authentication services based on global navigation satellite system (GNSS) signals and personal or computer data |
US9019092B1 (en) | 2013-03-08 | 2015-04-28 | Allstate Insurance Company | Determining whether a vehicle is parked for automated accident detection, fault attribution, and claims processing |
US8799034B1 (en) | 2013-03-08 | 2014-08-05 | Allstate University Company | Automated accident detection, fault attribution, and claims processing |
US9454786B1 (en) | 2013-03-08 | 2016-09-27 | Allstate Insurance Company | Encouraging safe driving using a remote vehicle starter and personalized insurance rates |
US20140257868A1 (en) | 2013-03-10 | 2014-09-11 | State Farm Mutual Automobile Insurance Company | Systems and methods for processing vehicle insurance based on acuity testing performance |
US9122933B2 (en) | 2013-03-13 | 2015-09-01 | Mighty Carma, Inc. | After market driving assistance system |
US20140272811A1 (en) | 2013-03-13 | 2014-09-18 | Mighty Carma, Inc. | System and method for providing driving and vehicle related assistance to a driver |
US8876535B2 (en) | 2013-03-15 | 2014-11-04 | State Farm Mutual Automobile Insurance Company | Real-time driver observation and scoring for driver's education |
US9959687B2 (en) | 2013-03-15 | 2018-05-01 | John Lindsay | Driver behavior monitoring |
US20140279707A1 (en) | 2013-03-15 | 2014-09-18 | CAA South Central Ontario | System and method for vehicle data analysis |
US8731977B1 (en) | 2013-03-15 | 2014-05-20 | Red Mountain Technologies, LLC | System and method for analyzing and using vehicle historical data |
US20140278571A1 (en) | 2013-03-15 | 2014-09-18 | State Farm Mutual Automobile Insurance Company | System and method for treating a damaged vehicle |
US9224293B2 (en) | 2013-03-16 | 2015-12-29 | Donald Warren Taylor | Apparatus and system for monitoring and managing traffic flow |
US20140278840A1 (en) | 2013-03-15 | 2014-09-18 | Inrix Inc. | Telemetry-based vehicle policy enforcement |
US8954340B2 (en) | 2013-03-15 | 2015-02-10 | State Farm Mutual Automobile Insurance Company | Risk evaluation based on vehicle operator behavior |
KR101751163B1 (en) | 2013-03-15 | 2017-06-26 | 폭스바겐 악티엔 게젤샤프트 | System for determining a route of vehicle and the method thereof |
SE540269C2 (en) | 2013-03-19 | 2018-05-22 | Scania Cv Ab | Device and method for regulating an autonomous vehicle |
US9342074B2 (en) * | 2013-04-05 | 2016-05-17 | Google Inc. | Systems and methods for transitioning control of an autonomous vehicle to a driver |
CN104380349A (en) | 2013-04-15 | 2015-02-25 | 弗莱克斯电子有限责任公司 | Vehicle intruder alert detection and indication |
US20150024705A1 (en) | 2013-05-01 | 2015-01-22 | Habib Rashidi | Recording and reporting device, method, and application |
US10247854B2 (en) * | 2013-05-07 | 2019-04-02 | Waymo Llc | Methods and systems for detecting weather conditions using vehicle onboard sensors |
GB2513880B (en) | 2013-05-08 | 2016-06-01 | Caterpillar Inc | Vehicle anti-theft apparatus and method |
US9003196B2 (en) | 2013-05-13 | 2015-04-07 | Hoyos Labs Corp. | System and method for authorizing access to access-controlled environments |
US20160083285A1 (en) | 2013-05-29 | 2016-03-24 | Nv Bekaert Sa | Heat resistant separation fabric |
US9147353B1 (en) | 2013-05-29 | 2015-09-29 | Allstate Insurance Company | Driving analysis using vehicle-to-vehicle communication |
US20140358592A1 (en) | 2013-05-31 | 2014-12-04 | OneEvent Technologies, LLC | Sensors for usage-based property insurance |
US8954205B2 (en) | 2013-06-01 | 2015-02-10 | Savari, Inc. | System and method for road side equipment of interest selection for active safety applications |
KR101515496B1 (en) | 2013-06-12 | 2015-05-04 | 국민대학교산학협력단 | Simulation system for autonomous vehicle for applying obstacle information in virtual reality |
ES2664573T3 (en) | 2013-06-12 | 2018-04-20 | Bosch Corporation | Control device for a vehicle or pedestrian passenger protection device and a control system |
CN105308524A (en) | 2013-06-28 | 2016-02-03 | 通用电气航空系统有限公司 | Method for diagnosing a horizontal stabilizer fault |
DE102014109079A1 (en) | 2013-06-28 | 2014-12-31 | Harman International Industries, Inc. | DEVICE AND METHOD FOR DETECTING THE INTEREST OF A DRIVER ON A ADVERTISING ADVERTISEMENT BY PURSUING THE OPERATOR'S VIEWS |
KR101470190B1 (en) | 2013-07-09 | 2014-12-05 | 현대자동차주식회사 | Apparatus for processing trouble of autonomous driving system and method thereof |
US8874301B1 (en) | 2013-07-09 | 2014-10-28 | Ford Global Technologies, Llc | Autonomous vehicle with driver presence and physiological monitoring |
US9053516B2 (en) | 2013-07-15 | 2015-06-09 | Jeffrey Stempora | Risk assessment using portable devices |
US20160036899A1 (en) | 2013-07-15 | 2016-02-04 | Strawberry Media, Inc. | Systems, methods, and apparatuses for implementing an incident response information management solution for first responders |
US20150025917A1 (en) | 2013-07-15 | 2015-01-22 | Advanced Insurance Products & Services, Inc. | System and method for determining an underwriting risk, risk score, or price of insurance using cognitive information |
US20150161738A1 (en) | 2013-12-10 | 2015-06-11 | Advanced Insurance Products & Services, Inc. | Method of determining a risk score or insurance cost using risk-related decision-making processes and decision outcomes |
DE102013214383A1 (en) | 2013-07-23 | 2015-01-29 | Robert Bosch Gmbh | Method and device for providing a collision signal with regard to a vehicle collision, method and device for managing collision data regarding vehicle collisions, and method and device for controlling at least one collision protection device of a vehicle |
US20150032581A1 (en) | 2013-07-26 | 2015-01-29 | Bank Of America Corporation | Use of e-receipts to determine total cost of ownership |
JP6429368B2 (en) | 2013-08-02 | 2018-11-28 | 本田技研工業株式会社 | Inter-vehicle communication system and method |
US20150039350A1 (en) | 2013-08-05 | 2015-02-05 | Ford Global Technologies, Llc | Vehicle operations monitoring |
US20150045983A1 (en) | 2013-08-07 | 2015-02-12 | DriveFactor | Methods, Systems and Devices for Obtaining and Utilizing Vehicle Telematics Data |
US9135756B2 (en) | 2013-08-14 | 2015-09-15 | Hti Ip, L.L.C. | Providing communications between a vehicle control device and a user device via a head unit |
US9947051B1 (en) | 2013-08-16 | 2018-04-17 | United Services Automobile Association | Identifying and recommending insurance policy products/services using informatic sensor data |
US20150066284A1 (en) | 2013-09-05 | 2015-03-05 | Ford Global Technologies, Llc | Autonomous vehicle control for impaired driver |
AT514754B1 (en) * | 2013-09-05 | 2018-06-15 | Avl List Gmbh | Method and device for optimizing driver assistance systems |
US9898086B2 (en) | 2013-09-06 | 2018-02-20 | Immersion Corporation | Systems and methods for visual processing of spectrograms to generate haptic effects |
US8935036B1 (en) | 2013-09-06 | 2015-01-13 | State Farm Mutual Automobile Insurance Company | Systems and methods for updating a driving tip model using telematics data |
EP2848488B2 (en) | 2013-09-12 | 2022-04-13 | Volvo Car Corporation | Method and arrangement for handover warning in a vehicle having autonomous driving capabilities |
EP2849017B1 (en) | 2013-09-12 | 2016-04-20 | Volvo Car Corporation | Method and arrangement for pick-up point retrieval timing |
US9424607B2 (en) | 2013-09-20 | 2016-08-23 | Elwha Llc | Systems and methods for insurance based upon status of vehicle software |
US10169821B2 (en) | 2013-09-20 | 2019-01-01 | Elwha Llc | Systems and methods for insurance based upon status of vehicle software |
US20150088373A1 (en) | 2013-09-23 | 2015-03-26 | The Boeing Company | Optical communications and obstacle sensing for autonomous vehicles |
US9150224B2 (en) | 2013-09-24 | 2015-10-06 | Ford Global Technologies, Llc | Transitioning from autonomous vehicle control to to driver control to responding to driver control |
US20150100189A1 (en) | 2013-10-07 | 2015-04-09 | Ford Global Technologies, Llc | Vehicle-to-infrastructure communication |
EP3056394B1 (en) | 2013-10-08 | 2022-11-30 | ICTK Holdings Co., Ltd. | Vehicle security network device and design method therefor |
US20150100191A1 (en) | 2013-10-09 | 2015-04-09 | Ford Global Technologies, Llc | Monitoring autonomous vehicle steering |
US9096199B2 (en) | 2013-10-09 | 2015-08-04 | Ford Global Technologies, Llc | Monitoring autonomous vehicle braking |
US9021024B1 (en) * | 2013-10-14 | 2015-04-28 | Xueming Tang | Method and apparatus for controlling access to information and applications between clients in a telecommunications network |
FR3012098B1 (en) | 2013-10-17 | 2017-01-13 | Renault Sa | SYSTEM AND METHOD FOR CONTROLLING VEHICLE WITH DEFECT MANAGEMENT |
US9361650B2 (en) | 2013-10-18 | 2016-06-07 | State Farm Mutual Automobile Insurance Company | Synchronization of vehicle sensor information |
US20150112731A1 (en) | 2013-10-18 | 2015-04-23 | State Farm Mutual Automobile Insurance Company | Risk assessment for an automated vehicle |
JP5975964B2 (en) | 2013-10-18 | 2016-08-23 | 富士通株式会社 | Information processing program, information processing method, information processing apparatus, and information processing system |
US9262787B2 (en) | 2013-10-18 | 2016-02-16 | State Farm Mutual Automobile Insurance Company | Assessing risk using vehicle environment information |
US9892567B2 (en) | 2013-10-18 | 2018-02-13 | State Farm Mutual Automobile Insurance Company | Vehicle sensor collection of other vehicle information |
US8954226B1 (en) | 2013-10-18 | 2015-02-10 | State Farm Mutual Automobile Insurance Company | Systems and methods for visualizing an accident involving a vehicle |
US20150112800A1 (en) | 2013-10-18 | 2015-04-23 | State Farm Mutual Automobile Insurance Company | Targeted advertising using vehicle information |
US10395318B2 (en) | 2013-10-24 | 2019-08-27 | Hartford Fire Insurance Company | System and method for administering insurance discounts for mobile device disabling technology |
US9177475B2 (en) * | 2013-11-04 | 2015-11-03 | Volkswagen Ag | Driver behavior based parking availability prediction system and method |
US20150127570A1 (en) | 2013-11-05 | 2015-05-07 | Hti Ip, Llc | Automatic accident reporting device |
US9529584B2 (en) | 2013-11-06 | 2016-12-27 | General Motors Llc | System and method for preparing vehicle for remote reflash event |
JP6272347B2 (en) | 2013-11-08 | 2018-01-31 | 株式会社日立製作所 | Autonomous traveling vehicle and autonomous traveling system |
DE102013223240B3 (en) | 2013-11-14 | 2014-10-30 | Volkswagen Aktiengesellschaft | Motor vehicle with occlusion detection for ultrasonic sensors |
US9401056B2 (en) | 2013-11-19 | 2016-07-26 | At&T Intellectual Property I, L.P. | Vehicular simulation |
US9475496B2 (en) | 2013-11-22 | 2016-10-25 | Ford Global Technologies, Llc | Modified autonomous vehicle settings |
US10088844B2 (en) * | 2013-11-22 | 2018-10-02 | Ford Global Technologies, Llc | Wearable computer in an autonomous vehicle |
US9517771B2 (en) * | 2013-11-22 | 2016-12-13 | Ford Global Technologies, Llc | Autonomous vehicle modes |
US20150149265A1 (en) | 2013-11-27 | 2015-05-28 | GM Global Technology Operations LLC | Controlled parking of autonomous vehicles |
JP6042794B2 (en) | 2013-12-03 | 2016-12-14 | 本田技研工業株式会社 | Vehicle control method |
US20150161894A1 (en) | 2013-12-05 | 2015-06-11 | Elwha Llc | Systems and methods for reporting characteristics of automatic-driving software |
US9123250B2 (en) | 2013-12-05 | 2015-09-01 | Elwha Llc | Systems and methods for reporting real-time handling characteristics |
US20150158495A1 (en) | 2013-12-05 | 2015-06-11 | Elwha Llc | Systems and methods for reporting characteristics of operator performance |
US9707942B2 (en) | 2013-12-06 | 2017-07-18 | Elwha Llc | Systems and methods for determining a robotic status of a driving vehicle |
US9164507B2 (en) | 2013-12-06 | 2015-10-20 | Elwha Llc | Systems and methods for modeling driving behavior of vehicles |
US20150161554A1 (en) | 2013-12-11 | 2015-06-11 | Uber Technologies, Inc. | Intelligent dispatch system for selecting service providers |
KR20150070801A (en) | 2013-12-17 | 2015-06-25 | 현대자동차주식회사 | Method for transmitting traffic information using vehicle to vehicle communications |
US9715378B2 (en) | 2013-12-18 | 2017-07-25 | International Business Machines Corporation | Automated software update scheduling |
US20150166069A1 (en) | 2013-12-18 | 2015-06-18 | Ford Global Technologies, Llc | Autonomous driving style learning |
US20150170287A1 (en) | 2013-12-18 | 2015-06-18 | The Travelers Indemnity Company | Insurance applications for autonomous vehicles |
US9406177B2 (en) | 2013-12-20 | 2016-08-02 | Ford Global Technologies, Llc | Fault handling in an autonomous vehicle |
US9650051B2 (en) | 2013-12-22 | 2017-05-16 | Lytx, Inc. | Autonomous driving comparison and evaluation |
US20160301698A1 (en) | 2013-12-23 | 2016-10-13 | Hill-Rom Services, Inc. | In-vehicle authorization for autonomous vehicles |
KR101475040B1 (en) | 2013-12-23 | 2014-12-24 | 한국교통대학교산학협력단 | Method and System for Providing Social Network Service Based on Traffic Information |
US9677529B2 (en) | 2013-12-25 | 2017-06-13 | Denso Corporation | Vehicle diagnosis system and method |
KR20150076627A (en) | 2013-12-27 | 2015-07-07 | 한국전자통신연구원 | System and method for learning driving information in vehicle |
US20150187194A1 (en) | 2013-12-29 | 2015-07-02 | Keanu Hypolite | Device, system, and method of smoke and hazard detection |
US10134091B2 (en) | 2013-12-31 | 2018-11-20 | Hartford Fire Insurance Company | System and method for determining driver signatures |
US10023114B2 (en) | 2013-12-31 | 2018-07-17 | Hartford Fire Insurance Company | Electronics for remotely monitoring and controlling a vehicle |
US20150187015A1 (en) | 2013-12-31 | 2015-07-02 | Hartford Fire Insurance Company | System and method for destination based underwriting |
US20150187019A1 (en) * | 2013-12-31 | 2015-07-02 | Hartford Fire Insurance Company | Systems and method for autonomous vehicle data processing |
US20150187016A1 (en) | 2013-12-31 | 2015-07-02 | Hartford Fire Insurance Company | System and method for telematics based underwriting |
US9524156B2 (en) | 2014-01-09 | 2016-12-20 | Ford Global Technologies, Llc | Flexible feature deployment strategy |
US9766874B2 (en) | 2014-01-09 | 2017-09-19 | Ford Global Technologies, Llc | Autonomous global software update |
US9995584B1 (en) | 2014-01-10 | 2018-06-12 | Allstate Insurance Company | Driving patterns |
US20150203107A1 (en) | 2014-01-17 | 2015-07-23 | Ford Global Technologies, Llc | Autonomous vehicle precipitation detection |
US9199642B2 (en) | 2014-01-21 | 2015-12-01 | Elwha Llc | Vehicle collision management responsive to traction conditions in an avoidance path |
US9221395B2 (en) | 2014-01-21 | 2015-12-29 | Arvinmeritor Technology, Llc | System and method of monitoring wheel end seal assembly wear |
US9390451B1 (en) | 2014-01-24 | 2016-07-12 | Allstate Insurance Company | Insurance system related to a vehicle-to-vehicle communication system |
US9355423B1 (en) | 2014-01-24 | 2016-05-31 | Allstate Insurance Company | Reward system related to a vehicle-to-vehicle communication system |
WO2015116022A1 (en) | 2014-01-28 | 2015-08-06 | GM Global Technology Operations LLC | Situational awareness for a vehicle |
CN106575476A (en) | 2014-01-30 | 2017-04-19 | 波尔图大学 | Device and method for self-automated parking lot for autonomous vehicles based on vehicular networking |
WO2015118325A1 (en) | 2014-02-04 | 2015-08-13 | Sudak Menachem | Monitoring system and method |
DE102014001554B4 (en) | 2014-02-05 | 2016-07-14 | Audi Ag | Method for automatically parking a vehicle and associated control device |
US9390567B2 (en) | 2014-02-05 | 2016-07-12 | Harman International Industries, Incorporated | Self-monitoring and alert system for intelligent vehicle |
US9666069B2 (en) | 2014-02-14 | 2017-05-30 | Ford Global Technologies, Llc | Autonomous vehicle handling and performance adjustment |
US9205805B2 (en) | 2014-02-14 | 2015-12-08 | International Business Machines Corporation | Limitations on the use of an autonomous vehicle |
US9079587B1 (en) | 2014-02-14 | 2015-07-14 | Ford Global Technologies, Llc | Autonomous control in a dense vehicle environment |
US20150235323A1 (en) | 2014-02-19 | 2015-08-20 | Himex Limited | Automated vehicle crash detection |
US10783587B1 (en) | 2014-02-19 | 2020-09-22 | Allstate Insurance Company | Determining a driver score based on the driver's response to autonomous features of a vehicle |
US9940676B1 (en) | 2014-02-19 | 2018-04-10 | Allstate Insurance Company | Insurance system for analysis of autonomous driving |
US10803525B1 (en) | 2014-02-19 | 2020-10-13 | Allstate Insurance Company | Determining a property of an insurance policy based on the autonomous features of a vehicle |
US10796369B1 (en) | 2014-02-19 | 2020-10-06 | Allstate Insurance Company | Determining a property of an insurance policy based on the level of autonomy of a vehicle |
US9709984B2 (en) | 2014-02-19 | 2017-07-18 | Lenovo Enterprise Solutions (Singapore) Pte. Ltd. | Administering a recall by an autonomous vehicle |
US10783586B1 (en) | 2014-02-19 | 2020-09-22 | Allstate Insurance Company | Determining a property of an insurance policy based on the density of vehicles |
US10373257B1 (en) | 2014-02-21 | 2019-08-06 | Arity International Limited | Vehicle telematics and account management |
US9915925B2 (en) | 2014-02-25 | 2018-03-13 | Honeywell International Inc. | Initiated test health management system and method |
US10380693B2 (en) | 2014-02-25 | 2019-08-13 | State Farm Mutual Automobile Insurance Company | Systems and methods for generating data that is representative of an insurance policy for an autonomous vehicle |
US9567007B2 (en) | 2014-02-27 | 2017-02-14 | International Business Machines Corporation | Identifying cost-effective parking for an autonomous vehicle |
US9511764B2 (en) | 2014-02-28 | 2016-12-06 | Ford Global Technologies, Llc | Semi-autonomous mode control |
WO2015134311A1 (en) | 2014-03-03 | 2015-09-11 | Inrix Inc | Traffic obstruction detection |
EP2915718B1 (en) | 2014-03-04 | 2018-07-11 | Volvo Car Corporation | Apparatus and method for continuously establishing a boundary for autonomous driving availability and an automotive vehicle comprising such an apparatus |
US9734685B2 (en) | 2014-03-07 | 2017-08-15 | State Farm Mutual Automobile Insurance Company | Vehicle operator emotion management system and method |
US9053588B1 (en) | 2014-03-13 | 2015-06-09 | Allstate Insurance Company | Roadside assistance management |
AU2015230052B2 (en) * | 2014-03-14 | 2019-12-12 | Veritide Limited | Substance or contamination detection |
EP2921363A1 (en) | 2014-03-18 | 2015-09-23 | Volvo Car Corporation | Vehicle, vehicle system and method for increasing safety and/or comfort during autonomous driving |
EP2921362B1 (en) | 2014-03-18 | 2020-08-12 | Volvo Car Corporation | Vehicle, vehicle system and method for increasing safety and/or comfort during autonomous driving |
EP2922033B1 (en) | 2014-03-18 | 2018-11-21 | Volvo Car Corporation | A vehicle sensor diagnosis system and method and a vehicle comprising such a system |
US20160189303A1 (en) | 2014-03-21 | 2016-06-30 | Gil Emanuel Fuchs | Risk Based Automotive Insurance Rating System |
US9383214B2 (en) | 2014-03-31 | 2016-07-05 | Telenav, Inc. | Navigation system with device recognition mechanism and method of operation thereof |
EP3127403B8 (en) | 2014-04-04 | 2019-04-10 | Signify Holding B.V. | System and methods to support autonomous vehicles via environmental perception and sensor calibration and verification |
EP3650262A1 (en) | 2014-04-04 | 2020-05-13 | Superpedestrian, Inc. | Systems, methods, and devices for the operation of electrically motorized vehicles |
KR101934321B1 (en) | 2014-04-09 | 2019-01-02 | 엠파이어 테크놀로지 디벨롭먼트 엘엘씨 | Sensor data anomaly detector |
US9507345B2 (en) | 2014-04-10 | 2016-11-29 | Nissan North America, Inc. | Vehicle control system and method |
US10179588B2 (en) | 2014-04-11 | 2019-01-15 | Nissan North America, Inc. | Autonomous vehicle control system |
US11836802B2 (en) | 2014-04-15 | 2023-12-05 | Speedgauge, Inc. | Vehicle operation analytics, feedback, and enhancement |
WO2015160900A1 (en) | 2014-04-15 | 2015-10-22 | Maris, Ltd | Assessing asynchronous authenticated data sources for use in driver risk management |
US9135803B1 (en) | 2014-04-17 | 2015-09-15 | State Farm Mutual Automobile Insurance Company | Advanced vehicle operator intelligence system |
US20150310758A1 (en) | 2014-04-26 | 2015-10-29 | The Travelers Indemnity Company | Systems, methods, and apparatus for generating customized virtual reality experiences |
EP2940672B1 (en) | 2014-04-29 | 2018-03-07 | Fujitsu Limited | Vehicular safety system |
US9365213B2 (en) | 2014-04-30 | 2016-06-14 | Here Global B.V. | Mode transition for an autonomous vehicle |
CN106664431A (en) | 2014-05-06 | 2017-05-10 | 大陆-特韦斯股份有限公司 | Method and system for detecting and/or backing up video data in a motor vehicle |
US9399445B2 (en) | 2014-05-08 | 2016-07-26 | International Business Machines Corporation | Delegating control of a vehicle |
US9972054B1 (en) | 2014-05-20 | 2018-05-15 | State Farm Mutual Automobile Insurance Company | Accident fault determination for autonomous vehicles |
US10373259B1 (en) | 2014-05-20 | 2019-08-06 | State Farm Mutual Automobile Insurance Company | Fully autonomous vehicle insurance pricing |
US10354330B1 (en) | 2014-05-20 | 2019-07-16 | State Farm Mutual Automobile Insurance Company | Autonomous feature use monitoring and insurance pricing |
US10185999B1 (en) | 2014-05-20 | 2019-01-22 | State Farm Mutual Automobile Insurance Company | Autonomous feature use monitoring and telematics |
US9475422B2 (en) | 2014-05-22 | 2016-10-25 | Applied Invention, Llc | Communication between autonomous vehicle and external observers |
US9631933B1 (en) | 2014-05-23 | 2017-04-25 | Google Inc. | Specifying unavailable locations for autonomous vehicles |
DE102014210147A1 (en) | 2014-05-27 | 2015-12-03 | Continental Teves Ag & Co. Ohg | Vehicle control system for autonomous guidance of a vehicle |
US10166916B2 (en) | 2014-05-30 | 2019-01-01 | State Farm Mutual Automobile Insurance Company | Systems and methods for determining a vehicle is at an elevated risk for an animal collision |
KR102186350B1 (en) | 2014-05-30 | 2020-12-03 | 현대모비스 주식회사 | Apparatus and method for requesting emergency call about vehicle accident using driving information of vehicle |
US9656606B1 (en) | 2014-05-30 | 2017-05-23 | State Farm Mutual Automobile Insurance Company | Systems and methods for alerting a driver to vehicle collision risks |
US20150356797A1 (en) | 2014-06-05 | 2015-12-10 | International Business Machines Corporation | Virtual key fob with transferable user data profile |
US11216887B1 (en) | 2014-06-12 | 2022-01-04 | Allstate Insurance Company | Virtual simulation for insurance |
US9282447B2 (en) | 2014-06-12 | 2016-03-08 | General Motors Llc | Vehicle incident response method and system |
DE102014211557A1 (en) | 2014-06-17 | 2015-12-31 | Robert Bosch Gmbh | Valet parking procedure and system |
US9465346B2 (en) | 2014-06-24 | 2016-10-11 | Kabushiki Kaisha Toshiba | Metallic color image forming apparatus and metallic color image forming method |
WO2016000035A1 (en) | 2014-06-30 | 2016-01-07 | Evolving Machine Intelligence Pty Ltd | A system and method for modelling system behaviour |
US9229460B1 (en) * | 2014-07-01 | 2016-01-05 | Innophase Inc. | Radio frequency peak detection with subthreshold biasing |
US20170221150A1 (en) | 2014-07-08 | 2017-08-03 | Matan BICHACHO | Behavior dependent insurance |
US9208526B1 (en) | 2014-07-11 | 2015-12-08 | State Farm Mutual Automobile Insurance Company | Method and system for categorizing vehicle treatment facilities into treatment complexity levels |
US9760702B1 (en) | 2014-07-14 | 2017-09-12 | Jpmorgan Chase Bank, N.A. | Systems and methods for driver authentication through embedded sensing |
US9805602B2 (en) | 2014-07-21 | 2017-10-31 | Ford Global Technologies, Llc | Parking service |
US9972184B2 (en) | 2014-07-24 | 2018-05-15 | State Farm Mutual Automobile Insurance Company | Systems and methods for monitoring a vehicle operator and for monitoring an operating environment within the vehicle |
US9766625B2 (en) * | 2014-07-25 | 2017-09-19 | Here Global B.V. | Personalized driving of autonomously driven vehicles |
US9189897B1 (en) | 2014-07-28 | 2015-11-17 | Here Global B.V. | Personalized driving ranking and alerting |
US9282430B1 (en) | 2014-07-30 | 2016-03-08 | Allstate Insurance Company | Roadside assistance service provider assignment system |
US10354329B2 (en) | 2014-08-06 | 2019-07-16 | Hartford Fire Insurance Company | Smart sensors for roof ice formation and property condition monitoring |
US9157752B1 (en) | 2014-08-08 | 2015-10-13 | Continental Automotive Systems, Inc. | System and method for theft and medical emergency event for self-driving vehicle |
US9514651B2 (en) | 2014-08-19 | 2016-12-06 | Here Global B.V. | Optimal warning distance |
WO2016028228A1 (en) | 2014-08-21 | 2016-02-25 | Avennetz Technologies Pte Ltd | System, method and apparatus for determining driving risk |
US9948898B2 (en) | 2014-08-22 | 2018-04-17 | Verizon Patent And Licensing Inc. | Using aerial imaging to provide supplemental information about a location |
US10377303B2 (en) | 2014-09-04 | 2019-08-13 | Toyota Motor Engineering & Manufacturing North America, Inc. | Management of driver and vehicle modes for semi-autonomous driving systems |
US9997077B2 (en) | 2014-09-04 | 2018-06-12 | Honda Motor Co., Ltd. | Vehicle operation assistance |
US9773281B1 (en) | 2014-09-16 | 2017-09-26 | Allstate Insurance Company | Accident detection and recovery |
US10102590B1 (en) | 2014-10-02 | 2018-10-16 | United Services Automobile Association (Usaa) | Systems and methods for unmanned vehicle management |
US9663112B2 (en) | 2014-10-09 | 2017-05-30 | Ford Global Technologies, Llc | Adaptive driver identification fusion |
US9716758B2 (en) | 2014-10-13 | 2017-07-25 | General Motors Llc | Network-coordinated DRx transmission reduction for a network access device of a telematics-equipped vehicle |
US9377315B2 (en) | 2014-10-22 | 2016-06-28 | Myine Electronics, Inc. | System and method to provide valet instructions for a self-driving vehicle |
US20160116913A1 (en) | 2014-10-23 | 2016-04-28 | James E. Niles | Autonomous vehicle environment detection system |
US9424751B2 (en) | 2014-10-24 | 2016-08-23 | Telogis, Inc. | Systems and methods for performing driver and vehicle analysis and alerting |
DE102014221764A1 (en) | 2014-10-27 | 2016-04-28 | Robert Bosch Gmbh | Device and method for operating a parking space |
SG10201407100PA (en) | 2014-10-30 | 2016-05-30 | Nec Asia Pacific Pte Ltd | System For Monitoring Event Related Data |
US9547985B2 (en) | 2014-11-05 | 2017-01-17 | Here Global B.V. | Method and apparatus for providing access to autonomous vehicles based on user context |
US9804594B2 (en) | 2014-11-07 | 2017-10-31 | Clearpath Robotics, Inc. | Self-calibrating sensors and actuators for unmanned vehicles |
US9430944B2 (en) | 2014-11-12 | 2016-08-30 | GM Global Technology Operations LLC | Method and apparatus for determining traffic safety events using vehicular participative sensing systems |
US20210118249A1 (en) | 2014-11-13 | 2021-04-22 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle salvage and repair |
US9524648B1 (en) | 2014-11-17 | 2016-12-20 | Amazon Technologies, Inc. | Countermeasures for threats to an uncrewed autonomous vehicle |
US9466154B2 (en) | 2014-11-21 | 2016-10-11 | International Business Machines Corporation | Automated service management |
US10614726B2 (en) | 2014-12-08 | 2020-04-07 | Life Long Driver, Llc | Behaviorally-based crash avoidance system |
CN107107818B (en) | 2014-12-26 | 2020-06-19 | 横滨橡胶株式会社 | Direction indicator lamp device and anti-collision system |
US20160187368A1 (en) | 2014-12-30 | 2016-06-30 | Google Inc. | Systems and methods of detecting failure of an opening sensor |
US10429177B2 (en) | 2014-12-30 | 2019-10-01 | Google Llc | Blocked sensor detection and notification |
US9712549B2 (en) | 2015-01-08 | 2017-07-18 | Imam Abdulrahman Bin Faisal University | System, apparatus, and method for detecting home anomalies |
US10198772B2 (en) | 2015-01-14 | 2019-02-05 | Tata Consultancy Services Limited | Driver assessment and recommendation system in a vehicle |
US9836963B1 (en) | 2015-01-20 | 2017-12-05 | State Farm Mutual Automobile Insurance Company | Determining corrective actions based upon broadcast of telematics data originating from another vehicle |
US9390452B1 (en) | 2015-01-28 | 2016-07-12 | Allstate Insurance Company | Risk unit based policies |
US9361599B1 (en) | 2015-01-28 | 2016-06-07 | Allstate Insurance Company | Risk unit based policies |
US10216196B2 (en) | 2015-02-01 | 2019-02-26 | Prosper Technology, Llc | Methods to operate autonomous vehicles to pilot vehicles in groups or convoys |
US10678261B2 (en) | 2015-02-06 | 2020-06-09 | Aptiv Technologies Limited | Method and apparatus for controlling an autonomous vehicle |
US20160231746A1 (en) | 2015-02-06 | 2016-08-11 | Delphi Technologies, Inc. | System And Method To Operate An Automated Vehicle |
US9942056B2 (en) | 2015-02-19 | 2018-04-10 | Vivint, Inc. | Methods and systems for automatically monitoring user activity |
US10049505B1 (en) | 2015-02-27 | 2018-08-14 | State Farm Mutual Automobile Insurance Company | Systems and methods for maintaining a self-driving vehicle |
US9701305B2 (en) | 2015-03-10 | 2017-07-11 | GM Global Technology Operations LLC | Automatic valet parking |
DE102015204359A1 (en) | 2015-03-11 | 2016-09-15 | Robert Bosch Gmbh | Driving a motor vehicle in a parking lot |
KR101675306B1 (en) | 2015-03-20 | 2016-11-11 | 현대자동차주식회사 | Accident information manage apparatus, vehicle having the same and method for managing accident information |
KR101656808B1 (en) | 2015-03-20 | 2016-09-22 | 현대자동차주식회사 | Accident information manage apparatus, vehicle having the same and method for managing accident information |
US9371072B1 (en) | 2015-03-24 | 2016-06-21 | Toyota Jidosha Kabushiki Kaisha | Lane quality service |
WO2016156236A1 (en) | 2015-03-31 | 2016-10-06 | Sony Corporation | Method and electronic device |
US20160292679A1 (en) | 2015-04-03 | 2016-10-06 | Uber Technologies, Inc. | Transport monitoring |
US9643606B2 (en) | 2015-04-14 | 2017-05-09 | Ford Global Technologies, Llc | Vehicle control in traffic conditions |
US9809163B2 (en) | 2015-04-14 | 2017-11-07 | Harman International Industries, Incorporation | Techniques for transmitting an alert towards a target area |
US9522598B2 (en) | 2015-04-16 | 2016-12-20 | Verizon Patent And Licensing Inc. | Vehicle occupant emergency system |
US9694765B2 (en) | 2015-04-20 | 2017-07-04 | Hitachi, Ltd. | Control system for an automotive vehicle |
US9874451B2 (en) | 2015-04-21 | 2018-01-23 | Here Global B.V. | Fresh hybrid routing independent of map version and provider |
US20160314224A1 (en) | 2015-04-24 | 2016-10-27 | Northrop Grumman Systems Corporation | Autonomous vehicle simulation system |
US9505494B1 (en) | 2015-04-30 | 2016-11-29 | Allstate Insurance Company | Enhanced unmanned aerial vehicles for damage inspection |
DE102015208914B4 (en) | 2015-04-30 | 2020-09-24 | Volkswagen Aktiengesellschaft | Procedure for assisting a vehicle |
US10102586B1 (en) | 2015-04-30 | 2018-10-16 | Allstate Insurance Company | Enhanced unmanned aerial vehicles for damage inspection |
US9948477B2 (en) | 2015-05-12 | 2018-04-17 | Echostar Technologies International Corporation | Home automation weather detection |
CN104933293A (en) | 2015-05-22 | 2015-09-23 | 小米科技有限责任公司 | Road information processing method and device |
US9733096B2 (en) | 2015-06-22 | 2017-08-15 | Waymo Llc | Determining pickup and destination locations for autonomous vehicles |
US9511767B1 (en) | 2015-07-01 | 2016-12-06 | Toyota Motor Engineering & Manufacturing North America, Inc. | Autonomous vehicle action planning using behavior prediction |
US20170015263A1 (en) | 2015-07-14 | 2017-01-19 | Ford Global Technologies, Llc | Vehicle Emergency Broadcast |
US20170017734A1 (en) | 2015-07-15 | 2017-01-19 | Ford Global Technologies, Llc | Crowdsourced Event Reporting and Reconstruction |
US9785145B2 (en) | 2015-08-07 | 2017-10-10 | International Business Machines Corporation | Controlling driving modes of self-driving vehicles |
US10023231B2 (en) | 2015-08-12 | 2018-07-17 | Madhusoodhan Ramanujam | Parking autonomous vehicles |
US9805519B2 (en) | 2015-08-12 | 2017-10-31 | Madhusoodhan Ramanujam | Performing services on autonomous vehicles |
US10220705B2 (en) | 2015-08-12 | 2019-03-05 | Madhusoodhan Ramanujam | Sharing autonomous vehicles |
US9805605B2 (en) | 2015-08-12 | 2017-10-31 | Madhusoodhan Ramanujam | Using autonomous vehicles in a taxi service |
US20210272207A1 (en) | 2015-08-28 | 2021-09-02 | State Farm Mutual Automobile Insurance Company | Vehicular driver profiles and discounts |
DE102015216494A1 (en) | 2015-08-28 | 2017-03-02 | Robert Bosch Gmbh | Method and device for detecting at least one sensor function of at least one first sensor of at least one first vehicle |
US10013697B1 (en) | 2015-09-02 | 2018-07-03 | State Farm Mutual Automobile Insurance Company | Systems and methods for managing and processing vehicle operator accounts based on vehicle operation data |
CN107924528A (en) | 2015-09-04 | 2018-04-17 | 罗伯特·博世有限公司 | Access and control for the driving of autonomous driving vehicle |
US9587952B1 (en) | 2015-09-09 | 2017-03-07 | Allstate Insurance Company | Altering autonomous or semi-autonomous vehicle operation based on route traversal values |
US10181266B2 (en) | 2015-09-11 | 2019-01-15 | Sony Corporation | System and method to provide driving assistance |
KR20170034023A (en) | 2015-09-18 | 2017-03-28 | 삼성전자주식회사 | Method and apparatus for resoruce allocaton in v2x communicaton system |
US10150448B2 (en) | 2015-09-18 | 2018-12-11 | Ford Global Technologies. Llc | Autonomous vehicle unauthorized passenger or object detection |
US9847033B1 (en) | 2015-09-25 | 2017-12-19 | Amazon Technologies, Inc. | Communication of navigation data spoofing between unmanned vehicles |
US9834224B2 (en) | 2015-10-15 | 2017-12-05 | International Business Machines Corporation | Controlling driving modes of self-driving vehicles |
DE102015220823B4 (en) | 2015-10-26 | 2024-01-25 | Robert Bosch Gmbh | Method for detecting a malfunction of at least one sensor for controlling a restraint device of a vehicle, control device and vehicle |
US20180218453A1 (en) | 2015-10-28 | 2018-08-02 | Fractal Industries, Inc. | Platform for autonomous management of risk transfer |
US10737577B2 (en) | 2015-11-04 | 2020-08-11 | Ford Global Technologies, Llc | Control strategy for charging electrified vehicle over multiple locations of a drive route |
US9720415B2 (en) | 2015-11-04 | 2017-08-01 | Zoox, Inc. | Sensor-based object-detection optimization for autonomous vehicles |
US9958864B2 (en) | 2015-11-04 | 2018-05-01 | Zoox, Inc. | Coordination of dispatching and maintaining fleet of autonomous vehicles |
US9754490B2 (en) | 2015-11-04 | 2017-09-05 | Zoox, Inc. | Software application to request and control an autonomous vehicle service |
US9632502B1 (en) | 2015-11-04 | 2017-04-25 | Zoox, Inc. | Machine-learning systems and techniques to optimize teleoperation and/or planner decisions |
US9944192B2 (en) | 2015-11-13 | 2018-04-17 | Nio Usa, Inc. | Electric vehicle charging station system and method of use |
US10242558B2 (en) | 2015-11-16 | 2019-03-26 | Google Llc | Systems and methods for handling latent anomalies |
US9939279B2 (en) | 2015-11-16 | 2018-04-10 | Uber Technologies, Inc. | Method and system for shared transport |
CA2947892A1 (en) | 2015-11-23 | 2017-05-23 | Wal-Mart Stores, Inc. | Navigating a customer to a parking space |
US20170148101A1 (en) | 2015-11-23 | 2017-05-25 | CSI Holdings I LLC | Damage assessment and repair based on objective surface data |
KR101786228B1 (en) | 2015-12-01 | 2017-10-18 | 현대자동차주식회사 | Failure dignosis method for vehicle |
KR101786237B1 (en) | 2015-12-09 | 2017-10-17 | 현대자동차주식회사 | Apparatus and method for processing failure detection and calibration of sensor in driver assist system |
US9709988B2 (en) | 2015-12-09 | 2017-07-18 | Ford Global Technologies, Llc | Identification of acceptable vehicle charge stations |
US10386835B2 (en) | 2016-01-04 | 2019-08-20 | GM Global Technology Operations LLC | System and method for externally interfacing with an autonomous vehicle |
US10134278B1 (en) | 2016-01-22 | 2018-11-20 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle application |
US10747234B1 (en) | 2016-01-22 | 2020-08-18 | State Farm Mutual Automobile Insurance Company | Method and system for enhancing the functionality of a vehicle |
US9940834B1 (en) | 2016-01-22 | 2018-04-10 | State Farm Mutual Automobile Insurance Company | Autonomous vehicle application |
WO2017142935A1 (en) | 2016-02-15 | 2017-08-24 | Allstate Insurance Company | Real time risk assessment and operational changes with semi-autonomous vehicles |
US11250514B2 (en) | 2016-02-15 | 2022-02-15 | Allstate Insurance Company | Early notification of non-autonomous area |
US10026317B2 (en) | 2016-02-25 | 2018-07-17 | Ford Global Technologies, Llc | Autonomous probability control |
US9986404B2 (en) | 2016-02-26 | 2018-05-29 | Rapidsos, Inc. | Systems and methods for emergency communications amongst groups of devices based on shared data |
US10319157B2 (en) | 2016-03-22 | 2019-06-11 | GM Global Technology Operations LLC | System and method for automatic maintenance |
US9964948B2 (en) | 2016-04-20 | 2018-05-08 | The Florida International University Board Of Trustees | Remote control and concierge service for an autonomous transit vehicle fleet |
EP3239686A1 (en) | 2016-04-26 | 2017-11-01 | Walter Steven Rosenbaum | Method for determining driving characteristics of a vehicle |
US20170329346A1 (en) | 2016-05-12 | 2017-11-16 | Magna Electronics Inc. | Vehicle autonomous parking system |
US9725036B1 (en) | 2016-06-28 | 2017-08-08 | Toyota Motor Engineering & Manufacturing North America, Inc. | Wake-up alerts for sleeping vehicle occupants |
US20180013831A1 (en) | 2016-07-11 | 2018-01-11 | Hcl Technologies Limited | Alerting one or more service providers based on analysis of sensor data |
US20180053411A1 (en) | 2016-08-19 | 2018-02-22 | Delphi Technologies, Inc. | Emergency communication system for automated vehicles |
US20190005464A1 (en) | 2016-08-31 | 2019-01-03 | Faraday&Future Inc. | System and method for scheduling vehicle maintenance services |
US20180080995A1 (en) | 2016-09-20 | 2018-03-22 | Faraday&Future Inc. | Notification system and method for providing remaining running time of a battery |
US20180091981A1 (en) | 2016-09-23 | 2018-03-29 | Board Of Trustees Of The University Of Arkansas | Smart vehicular hybrid network systems and applications of same |
US11155267B2 (en) | 2016-10-11 | 2021-10-26 | Samsung Electronics Co., Ltd. | Mobile sensor platform |
US9817400B1 (en) | 2016-12-14 | 2017-11-14 | Uber Technologies, Inc. | Vehicle servicing system |
US10095239B1 (en) | 2017-03-31 | 2018-10-09 | Uber Technologies, Inc. | Autonomous vehicle paletization system |
US10889196B2 (en) | 2017-06-02 | 2021-01-12 | CarFlex Corporation | Autonomous vehicle servicing and energy management |
US10510195B2 (en) | 2017-06-29 | 2019-12-17 | Tesla, Inc. | System and method for monitoring stress cycles |
US10571917B2 (en) | 2017-11-10 | 2020-02-25 | Uatc, Llc | Systems and methods for providing a vehicle service via a transportation network for autonomous vehicles |
US20190146491A1 (en) | 2017-11-10 | 2019-05-16 | GM Global Technology Operations LLC | In-vehicle system to communicate with passengers |
US11040726B2 (en) | 2017-12-15 | 2021-06-22 | Baidu Usa Llc | Alarm system of autonomous driving vehicles (ADVs) |
-
2015
- 2015-11-06 US US14/934,357 patent/US20210118249A1/en not_active Abandoned
- 2015-11-06 US US14/934,326 patent/US10431018B1/en active Active
- 2015-11-06 US US14/934,388 patent/US10416670B1/en active Active
- 2015-11-06 US US14/934,355 patent/US10915965B1/en active Active
- 2015-11-06 US US14/934,385 patent/US10166994B1/en active Active
- 2015-11-06 US US14/934,343 patent/US10157423B1/en active Active
- 2015-11-06 US US14/934,361 patent/US11127290B1/en active Active
- 2015-11-06 US US14/934,393 patent/US10266180B1/en active Active
- 2015-11-06 US US14/934,333 patent/US10336321B1/en active Active
- 2015-11-06 US US14/934,400 patent/US10241509B1/en active Active
- 2015-11-06 US US14/934,347 patent/US9946531B1/en active Active
- 2015-11-06 US US14/934,339 patent/US10246097B1/en active Active
- 2015-11-06 US US14/934,371 patent/US10007263B1/en active Active
- 2015-11-06 US US14/934,352 patent/US10831204B1/en active Active
- 2015-11-06 US US14/934,381 patent/US20200219197A1/en not_active Abandoned
- 2015-11-06 US US14/934,405 patent/US9944282B1/en active Active
-
2018
- 2018-01-12 US US15/869,777 patent/US10353694B1/en active Active
- 2018-02-13 US US15/895,533 patent/US10821971B1/en active Active
- 2018-03-26 US US15/935,556 patent/US10831191B1/en active Active
- 2018-10-25 US US16/170,130 patent/US10943303B1/en active Active
- 2018-11-02 US US16/178,809 patent/US10940866B1/en active Active
-
2019
- 2019-01-03 US US16/238,911 patent/US11175660B1/en active Active
- 2019-02-04 US US16/266,490 patent/US11014567B1/en active Active
- 2019-02-04 US US16/266,162 patent/US11173918B1/en active Active
- 2019-05-08 US US16/406,418 patent/US10824415B1/en active Active
- 2019-05-21 US US16/418,385 patent/US11247670B1/en active Active
- 2019-07-12 US US16/509,605 patent/US10824144B1/en active Active
- 2019-08-14 US US16/540,545 patent/US11532187B1/en active Active
- 2019-11-27 US US16/697,396 patent/US11720968B1/en active Active
-
2020
- 2020-01-23 US US16/750,038 patent/US11500377B1/en active Active
- 2020-03-05 US US16/810,375 patent/US11393041B1/en active Active
- 2020-06-27 US US16/914,337 patent/US11740885B1/en active Active
- 2020-10-19 US US17/074,397 patent/US11748085B2/en active Active
- 2020-10-19 US US17/073,823 patent/US20210031756A1/en not_active Abandoned
- 2020-10-21 US US17/075,828 patent/US11494175B2/en active Active
- 2020-10-23 US US17/078,659 patent/US11645064B2/en active Active
- 2020-10-23 US US17/078,640 patent/US11726763B2/en active Active
-
2022
- 2022-01-10 US US17/572,156 patent/US11977874B2/en active Active
- 2022-06-23 US US17/847,444 patent/US20220318924A1/en active Pending
- 2022-10-11 US US17/963,421 patent/US11954482B2/en active Active
- 2022-10-27 US US17/975,234 patent/US20230053773A1/en active Pending
- 2022-11-14 US US17/985,944 patent/US20230070573A1/en active Pending
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11307577B2 (en) * | 2016-03-08 | 2022-04-19 | Toyota Jidosha Kabushiki Kaisha | Autonomous driving control device |
US11703858B2 (en) | 2016-03-08 | 2023-07-18 | Toyota Jidosha Kabushiki Kaisha | Autonomous driving control device |
US20230028145A1 (en) * | 2021-07-26 | 2023-01-26 | Toyota Jidosha Kabushiki Kaisha | Information processing device, reward determination method, and storage medium |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11645064B2 (en) | Autonomous vehicle accident and emergency response | |
US12032945B2 (en) | Autonomous vehicle accident and emergency response |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: STATE FARM MUTUAL AUTOMOBILE INSURANCE COMPANY, ILLINOIS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FIELDS, BRIAN MARK;HUANG, CHIEN CHE;WAZEER, MOHAMED A.;AND OTHERS;SIGNING DATES FROM 20160119 TO 20160323;REEL/FRAME:038094/0773 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |