1	Connected Vehicle Update Brian Cronin, Team Leader, Research, Intelligent Transportation Systems Joint Program Office Research and Innovative Technology Administration, USDOT Brian.Cronin@DOT.GOV
2	Fully Connected Vehicle
3	Moving towards Infrastructure Deployment
4	Application Development
5	V2I Reference Implementation – Concept A system of specifications and requirements that allow the various components of V2I hardware, software and firmware to work together. An agency will be able to select the capabilities and applications desired at a given installation.
6	V2I Communications for Safety
7	Mobility, Weather, and AERIS
8	Analyzed BSM for DMA, Weather and AERIS Background Connected V2V safety applications are built around the SAE J2735 BSM, which has two parts BSM Part 1: Contains the core data elements (vehicle size, position, speed, heading acceleration, brake system status) Transmitted approximately 10x per second BSM Part 2: Added to part 1 depending upon events (e.g., ABS activated) Contains a variable set of data elements drawn from many optional data elements (availability by vehicle model varies) Transmitted less frequently No on-vehicle BSM storage of BSM data The BSM is transmitted over DSRC (range ~300 meters) The BSM is tailored for low latency, localized broadcast required by V2V safety applications
9	BSM Analysis Results DMA The data is the right set of data. Some Applications will work (spot specific). Need storage capabilities and likely other communication mechanisms to truly gain value. Possible approach: Vehicles transmit BSM Part 1 plus key Part 2 elements less frequently Transmit via DSRC when available, Cellular otherwise Weather The Data in BSM is sufficient. Possible approach: “Black Ice” warning requires near-instantaneous information while other algorithms operate with data rates from once per second to once every 30 seconds 15 observations per segment (e.g., 1 mile) per time step (e.g., 15 min) should be sufficient for confidence in the application outputs Bandwidth required for data transmission is minimal (85-365 bytes)
10	BSM Analysis Results AERIS The BSM Part I satisfies the major part of several AERIS applications that compute eco-trajectories for vehicles. Additional environmental information can improve eco-trajectory computations, but is not required. Many applications do not require low latency. There are two approaches for collecting emissions data: Estimate emissions using BSM Part I data Collect emissions data from the vehicle (requires additions to J2735) Need additional data not in BSM for some apps, such as emissions, fuel type, fuel consumption, road grade, road type, engine temperature
11	Deployment Scenario
12	Research Data Exchange
13	Affiliated Connected Vehicle Test Beds
14	To Do in 2013 Partner with NHTSA on the V2V Safety Decision Understand the Market Potential for New Vehicle Based Data Enabled by Connected Vehicles Partner with the Community to Define and Test Applications based on additional SAE J2735 Messages (Probe Data, Environment …) Understand the landscape for Data Aggregation in a Connected Vehicle World
15	What’s New? New Strategic Plan Offer your input at: http://itsstrategicplan.ideascale.com/
16	For More Information www.ITS.DOT.GOV Brian Cronin, Team Leader, Research RITA, ITS Joint Program Office (JPO) Brian.Cronin@dot.gov