1	"Valerie Briggs" Valerie Briggs Team Lead, Knowledge Transfer and Policy ITS Joint Program Office Research and Innovative Technology Administration April 19, 2012
2	Today
3	Fully Connected Vehicle
4	ITS Research Program Components
5
6
7
8	Policy Research Focus Determine if V2V (and V2I/V2X) is feasible to implement Security Needs Functional Requirements Physical/Technical Requirements Operational & Organizational Requirements Financial Sustainability and Responsibility Challenges – unique – Potentially mandatory systems Trip anonymity Scalability, etc.
9	Security System: A “Must Have” for safety Clarifications Security Network – credentialing and certificate management Security Back Office – operational functions that apply across any type of Security Network Applications Infrastructure – Infrastructure specifically for V2I safety (DSRC) or V2I mobility (other options) All require sustainable funding
10	Security System
11	Security System & Applications Infrastructure
12	Security System & Security Infrastructure
13	Context and Trends Very fast moving Growth in consumer connectivity and the world of apps Emerging market “ecosystem” for apps, suppliers and, perhaps, OEMs Trend toward cell connection and apps in vehicles
14	Main things we need to do… Understand and document suitable security approaches Understand costs Identify potentially viable paths for implementation Identify potentially sustainable financial models for supporting needs Understand potential risks and ramifications Understand stakeholder impacts, roles and responsibilities and support needs
15	U.S. DOT Connected Vehicle Policy Program Organizational Structure 4/2012
16
17
18	Principles: Purpose Transportation safety is the DOT’s top priority. The principles require that the system: Prevent or mitigate the severity of crashes Minimize driver workload Ensure no increase to driver distraction Encompass all road users Ensure that mandatory safety applications cannot be turned off or overridden. Uses beyond safety applications are permissible and encouraged as long as they do not detract from safety.
19	Principles: Coverage/Scale The system is extensible to all types of connected vehicle systems and applications (safety, mobility, environmental, etc.). System implementation must be national in scale and extensible across North America. Implementation can start at discrete locations but is envisioned to include all major roadways with timing to coincide with the roll out of technology in vehicles.
20	Principles: User Protections DOT is committed to fostering a connected vehicle environment that ensures stakeholder and operational needs are met while at the same time protecting consumers appropriately from unwarranted privacy risks. The connected vehicle environment will incorporate appropriate privacy controls: transparency; individual participation and redress; purpose specification; limitations on use of information; data minimization and retention; data quality and integrity; security; and accountability and auditing. For example: The environment must provide consumers with appropriate advance notice of and, for opt-in systems, opportunity to provide consent for information collection, use, access, maintenance, security and disposal. The environment will limit the collection and retention of personally identifiable information to the minimum necessary to support stakeholder and operational needs.
21	Principles: User Protections (continued) As the federal role and other critical aspects of connected vehicle regulation and/or implementation are further defined, DOT will document publicly the privacy risks and controls applicable to the system and users. The system must be secure to an appropriate level. The system will: Ensure secure and trusted information exchange among users Provide protection from hacking and malicious behavior Maintain data integrity.
22
23
24
25	Principles: Technical Functionality Functionality of the system requires compliance with nationwide, universally accepted non-proprietary communication and performance standards Interoperability of equipment, vehicles, and other devices is necessary to enable mandatory safety applications as well as applications supporting mobility, economic competitiveness, and sustainability. Standards must be maintained to ensure technical viability. The system must be technically adaptable and viable over time Must be backward compatible. System must be able to evolve over time as new technologies become available.
26	Principles: Technical Functionality (continued) Communication technology for safety applications must be secure, low latency, mature, stable, and work at highway speeds. Currently DSRC is the only known viable technology for safety critical applications. DSRC or other communication technologies could be used for safety applications that are not for crash-imminent situations, mobility, and environmental applications. Use of the spectrum must comply with established requirements for non-interference. Safety applications take priority over non safety applications. Public sector applications take precedence over commercial applications.
27	For More Information