Breakout Group II – Driver Behavior Modeling, Simulation & Testbeds

• What data/factors need to be collected behavior modeling• How to capture driver compliance?• Active Behavior vs. Passive• Incentives

– What (insurance!)– How to evaluate

• How Big the data should be for a credible model?• Sensitive behavior data vs. Safety?• Intra-vehicle data vs. Inter-vehicle data• Do we need new simulation tools?

– What?– How?

• Testbeds• How Driverless vehicles would change game.

– Motivation: validate the models– Scope: from single car to multiple cars– Must expand existing testbeds (VA Tech, Michigan,

Luxemburg)– Must retrofit simulation (eg Veins) to allow driver

model validation – State of art: now only V2V– Research/Implement Challenge: size, incentives,

collection of data, etc

Testbed

– On board units (OBD, smart phone, ..)– Body motion sensors– Fatigue sensors– External vehicle data (distance to car in front, stop

lights, general traffic&road conditions, etc).– Who is managing data?– Who is using/sharing the data?

Data Collection:

• Motivation: Privacy at all levels– in Emergency messages can one include sensitive

info if that saves lives?• Segment sensitive data into risk likelihood/

reaction times• When do we share date for safety over privacy

Sensitive behavior data vs. Safety?

• We need context/driver behavior models– More intra-driver (attitude, perception, previous

cash experience) details• Models that bridge gap between individual

driver and system at large– Retrofit the urban simulation model to include a

detailed (experimentally validated) driver model• Current models include driver behavior only at

rudimentary level

Do we need new simulation tools?

• Model for phasein/phaseout driver (from autonomous to cockpit control)– Google glass driving?

• Levels of automation (0-4)• Vehicle protection from cyber attacks– Requires revisiting the driver model

How Driverless vehicles change driver behavior.