《未来基于DSR的智能交通研讨会.pptx》由会员分享，可在线阅读，更多相关《未来基于DSR的智能交通研讨会.pptx（32页珍藏版）》请在taowenge.com淘文阁网|工程机械CAD图纸|机械工程制图|CAD装配图下载|SolidWorks_CaTia_CAD_UG_PROE_设计图分享下载上搜索。
1、,IntelliDrive Connectivity and the Future of Surface Transportation,Workshop Agenda,Background Goal of IntelliDrive Evolution from VII to IntelliDrive V2V & Safety Pilot programs Discussion on Inclusion of DSRC in Nomadic Devices Key questions/hurdles in moving towards deployment What can the federa
2、l government do to help? Summary of Results from Interviews Facilitated Discussion,The Problem!,Probe Data,E-payment Transactions,Signal Phase and Timing Information,Real Time Network Data,Situation Relevant Information,Infrastructure Communications,Opportunity for Innovation,Its All About Connectiv
3、ity,V2V Safety Messages,“The Network”,Evolution of IntelliDrive,Original VII Deployment Model DSRC based for all applications Infrastructure intensive using new DSRC technology Vehicle turnover for embedded DSRC technology Start with V2I (for all application types) and evolve into V2V (safety) US DO
4、Ts Current Perspective on IntelliDrive Deployment Non-safety (mobility, environment) Leverage existing data sources leverage vehicle capability for V2I spot safety Can leveraging of nomadic devices & retrofitting accelerate benefits? Infrastructure requirement is still a TBD (security),4,Latency vs.
5、 Communications Technologies For IntelliDriveSM,Latency (in seconds),Most Stringent latency requirement for Active Safety (.02 sec),Note: Y-axis not to scale for illustration purposes,Least stringent latency requirement for Active Safety ( 1 sec),Data source: Vehicle Safety Communications Project Fi
6、nal Report,Intersection Collision Avoidance,Opportunity for Safer Driving,Greater situational awareness Your vehicle can “see” nearby vehicles and knows roadway conditions you cant see Reduce or even eliminate crashes thru: Driver Advisories Driver Warnings Vehicle Control,Work Zone Notification,Int
7、elliDrive has the potential to address 82% of the vehicle crash scenarios involving unimpaired drivers,TRACK 5 Driver Issues,TRACK 4 Application Development,TRACK 3 Benefits Assessment,TRACK 2 Interoperability,TRACK 1 Crash Scenario Frame Work,TRACK 0 Current Activities,Select Applications,Complete
8、CAMP-V SC-A,Update Crash Scenarios,Define Initial Performance Requirements,Develop & Build Prototype Safety Application Vehicles,DVI Effectiveness Multiple Warnings,Driver Workload Issues,Complete Message and Communication Standards,Security & Privacy (Certificate Authority),Define Performance Measu
9、res,Develop Objective Tests,Adapt ACAT Methodology,Conduct Objective Tests,Safety Benefits Estimate,Regulation or NCAP Decision,Vehicle to Vehicle Safety Application Research Plan,Data Authentication,Track 6 IntelliDriveSM Policy Issues,Development Tests,Final Standards & Protocols,Field Trails,Secu
10、rity & Privacy Policy (V2V),5.9 Enforcement,Retrofit & Aftermarket Reqts,Business Models,Driver Acceptance,Performance Requirements,Governance (V2V),IntelliDriveSM System Engineering,IntelliDriveSM Principles,Track 7 Commercial Vehicle,Update Crash Scenarios,Define Initial Performance Reqs and Measu
11、res,Develop and Conduct Objective Tests,Driver Workload Issues and Acceptance,Field Tests,CVO Regulation Decision,Track 8 Transit Vehicle,Update Crash Scenarios,Define Initial Performance Reqs and Measures,Develop and Conduct Objective Tests,Driver Workload Issues and Acceptance,Field Tests,FTA Impl
12、ementation Decision,(TBD),(TBD),Technical and Policy Interactions,Technical Issues & Constraints,Policy Issues & Constraints,Trade-offs,Options & Recommendations,Deployment Model(s),(For Example: Security vs Privacy Trade-offs),Policy trade-offs will require senior level decisions.,Outstanding Techn
13、ical Issues,Addressed under current CAMP Agreement Independent technical peer review Safety Pilot provides real-world implementation Penetration vs. Effectiveness Driver Acceptance Data Security Positioning Scalability Channel Switching,Outstanding Policy Issues,Critical V2V Policy Issues Being Defi
14、ned V2V Policy White Paper /Roadmaps Being Developed Internal and External Stakeholder Engagement Being Defined How will tradeoffs between security, privacy and functionality be managed? Operations Who will monitor for misbehavior? Who will operate the Security Certificate Authority? Compliance & En
15、forcement Who will enforce DSRC standards? How will the rules of operation be developed and enforced? How and who will certify DSRC devices?,Safety Pilot Goals: - Support the 2013 Regulatory V2V Decision with Field Data- Public Awareness & Acceptance,Primary Objectives Demonstrate V2V real world imp
16、lementation Multiple vehicle types (cars, trucks, buses, rail, etc) Obtain substantial empirical data Assess driver acceptance of vehicle based safety systems Explore opportunities for accelerating safety benefits through aftermarket devices and retrofit systems Secondary Objectives Enable vehicle-i
17、nfrastructure (V2I) safety applications Leverage data for non-safety applications such as mobility, environment, and weather,Safety Pilot Activities,Driver Clinics Driver acceptance data from light vehicle driver clinics at various locations Explore similar opportunities for other vehicle types Perf
18、ormance testing in multiple geographic environments using small numbers of light vehicles and nomadic devices at same locations Model Deployment Critical Mass/Exposure testing large number of vehicles and devices creating a “highly saturated” operating environment Mixture of integrated safety system
19、s with nomadic devices Cars, trucks, buses, fleets, rail crossings Lots of vehicles, limited infrastructure,Safety Pilot Roadmap (rev 14),CY 2010,CY 2011,CY 2012,Q1,Independent Evaluation of Testing Activities,CY 2013,Q2,Q3,Q4,Q1,Q2,Q3,Q4,Q1,Q2,Q3,Q4,Q1,Q2,Q3,Q4,V2V Regulatory Decision Point,Model D
20、eployment Ramp-up and Preliminary Testing,Input to Industry standards based upon test results,Device Updates,Light Vehicle Driver Clinics & Performance Testing,Driver Clinics,Model Deployment,Evaluation,V2V Benefits Assessment,Initial Integrated Safety System Light Vehicle Builds,Vehicle Updates,Mod
21、el Deployment Full Scale Testing,Aftermarket Device Development,Transit Vehicle Roadeo,Heavy Vehicle,Sources Sought Notice (SSN) DTFH61-10-R-00026,SSN issued on April 29, 2010 in Fed Biz Opps: www.fbo.gov Market research on potential 5.9 GHz device suppliers Open for 30 days Next Steps: Issue solici
22、tation for device procurements for testing and qualification against acceptance requirements Issued to respondents from SSN and others who are known potential sources Small number of units to be used for qualification testing Would require devices by late 2010/early 2011 Critical factor is that resp
23、ondents are already well underway with product development Establish qualified products list (QPL) Procurement of devices for supporting larger Safety Pilot model deployment Vendors listed on QPL will be considered for future procurement under Safety Pilot Larger volume deliveries starting middle of
24、 2011 Procurement from multiple vendors,DTFH61-10-R-00026, Appendix A,Production of Dedicated Short Range Communications at 5.9 GHz Here I Am Nomadic Devices Here I Am Device General Needs,Basic Safety Message,Each class of device must be capable of transmitting a valid, signed Basic Safety Message
25、(BSM) and receiving BSMs. The “Here I Am” message is the BSM (subset) of SAE J2735 conveyed in the 5.9GHz DSRC medium according to IEEE 802.11p and 1609.2 - 1609.4. The primary information conveyed in the message is the location of a vehicle at a particular time. Other data items are included as wel
26、l. The message is properly signed so that receivers can check authenticity.,Provisioning/Test Interface,Each class of device must have a provisioning/test interface that enables the device to receive and load new versions of software, new configurations and credentials, and instructions to perform l
27、ogging functions and download log messages to an external device. This interface is intended to be used at time of manufacture, installation, and update. The interface may be used during operation if data logging is needed.,Vehicle/Device Interface,Each class of device may be physically mounted in a
28、 vehicle, although mounting methods will vary by device. The main purpose of the device is to transmit information about a vehicles operation. Since the main information transmitted is the location of the vehicle, the device will have to know the relationship between it and the center of the vehicle
29、. In some cases, the device may obtain power from the vehicle.,Device Classes,Class 1 This is a consumer grade device (such as a smart cell phone or personal navigation device) that can be carried into a vehicle by one or more of that vehicles occupants. To function properly, the device need not be
30、physically attached to the vehicle, but must be kept in a stable position relative to the vehicles center, varying no more than 5 centimeters in any direction (laterally, longitudinally, or vertically) while in use. Class 2 this is a purpose-designed device intended for temporary installation in a v
31、ehicle. The device must be physically attached to the vehicle during its temporary installation. It may use the vehicles power couplers for its operation. Class 3 this is a purpose-designed device intended for permanent installation in a vehicle. The device must be physically attached to the vehicle
32、 during its installation. It may use the vehicles power for its operation.,Standards References,Each class of device must be capable of transmitting J2735 (version 2009-11)-conformant Basic Safety Messages (BSMs) over a Dedicated Short Range Communications (DSRC) 5.9 Gigahertz (GHz) wireless network
33、 using the protocol stack and other standards associated with DSRC for vehicular communications. These include: IEEE 802.11p, IEEE 1609-1 through 1609-4, and J2735 (2009-11 version) and a performance standard under development by the automobile industry. SAE www.sae.org http:/www.sae.org/technical/s
34、tandards/J2735_200911 http:/www.sae.org/standardsdev/dsrc/DSRCImplementationGuide.pdf IEEE www.ieee.org Supplemental information will be provided in the solicitation,Engagement of Industry to Accelerate Market Summary of Input to Date,Goal: Discuss ways to accelerate the market for DSRC-enabled devi
35、ces for V2V Began input in early April 2010 still collecting input and seeking input today,Technology Issues and Challenges Existing, proven communications technologies are available Why DSRC when other communications exist (4G, Wi-Max, Wi-Fi, etc)? Frequency issues What is capacity in large scale s
36、ituations? What is probability for interference? Security issues Time to authenticate users needs to be shorter and data overhead smaller What is proposed for oversight? Does this level of security and authentication create cost-prohibitive elements for mobile devices and products? Interoperability
37、What are the issues for device manufacturers? We need to better understand.,Summary of Input to Date (continued),Summary of Input to Date (continued),Business Challenges Compelling business case for private sector not there Public wont pay for safety Most enthusiastic companies interested in mobilit
38、y data can sell the public on faster, cheaper, and convenience Production timing for enabling devices Typical business process to modify device is between 2-5 years Limited DSRC chip manufacturers worldwide More than one what is issue that needs to be resolved? We need to better understand.,Cultural
39、 Challenges Dialogue about the technology, business model, and standards felt closed under the VII process Some stakeholders have expressed negative experience with VII. Want to see the process more open, in particular with standards development Pace of deployment has been too slow Too much research
40、 Serious cultural differences among each of the entities involved Companies would like Federal government to require OEMs to provide data Major questions around liability What data do device manufacturers want (specifically)? We need to understand.,Summary of Input to Date (continued),Biggest Issue,
41、Need to see Federal government commitment to DSRC! Are the messages provided this week statement of commitment by Administrators, SSN, upcoming tests and model deployment the right signs of commitment?,DOT Actions and Responses to Challenges,Technical Challenges,Business Challenges,Cultural Challeng
42、es,Questions,Are these appropriate actions for Federal government to take? We are not going to develop business models for you.what information or input do you need to develop business models that are viable? Are there other areas of research, testing, and demonstration that are needed beyond the Sa
43、fety Pilot? Are there other actions that are needed to explore and develop policy recommendations? Who are other stakeholders that need to be involved in order to accelerate DSRC into the market?,Further Information,Mike.Schagrindot.gov 202-366-2180 Walton.Fehrdot.gov 202-366-0278 Suzanne.Sloandot.gov 617-494-3282,