A US Perspective on ETSI ITS Standards

Transcription

1 A US Perspective on ETSI ITS Standards John B. Kenney Toyota InfoTechnology Center, USA ETSI ITS Workshop February 6,

2 Toyota InfoTechnology Center Japan HQ Investors: Toyota, Denso, KDDI, Toyota Tsusho, Aisin, Kyocera, Toyoda Gosei, Toyota Industries Headquarter: Tokyo, Japan Location:6-6-20, Akasaka, Minato-ku Personnel: about 60 Established:January, 2001 US Center Wholly-owned subsidiary of Toyota InfoTechnology Center Co., Ltd. Base: Mountain View Research Park (Headquarters) Location: Mountain View, CA Personnel: about 40 Established:April, 2001 Location: New York City, NY Personnel: 4 2

3 A General Perspective Overall standards are in good shape Interesting split between CAM and DENM, joining DENM safety with DENM mobility Interesting to see differences in deployment model and Day 1 applications driving the process Interesting that GeoNetworking included right away Interesting that application level requirements included right away. Still some questions about how far this will go. Interesting to see a struggle between those who wish to define things more flexibly and those who seek a more definite standard. Ongoing. Interesting to see multi-layer approach to congestion control 3

4 A General Perspective (con t) Will there have been enough progress on non-technical issues to make deployment successful? Policies, Governance, Business Will there have been enough testing prior to deployment? VSC-A Prototype, Basis for Model Deployment Forward Looking Camera System (LDW) Relative Positioning Platform GPS unit OBE CAN ENET Serial CICAS-V Threat Arbitration DVI Notifier EEBL FCW IMA BSW+LCW DNPW Sensor Data Handler Target Classification Host Vehicle Path Prediction V-V Safety Applications A Path History Wireless Message Handler CLW [From other Modules] Data Logger Eng. GUI Security A ENET VGA DSRC Radios (2) Cameras / Audio in Data Logger & Visualization Tools Display OTA messages Vehicle Sensors (Non Production) CAN CAN Vehicle CAN to OBE Interface Vehicle Signals (Production) Engineering DVI Vehicle CAN ENET Legend Common blocks (minimum) Common blocks (additional) 4 OEM specific or proprietary blocks

5 A Toyota Perspective Critical to drive costs out where we can Pleased to see ITS WC demo with DENSO Harmonization has an high profile within Toyota, Including with Japan, where we (US and EU) have many things to learn 5

6 A Harmonization Perspective Willingness to cooperate and harmonize Among OEMs (CAMP-C2CCC) Among SDOs HTGs ETSI MOU with SAE, IEEE CEN/ISO and ETSI Excellent harmonization effort on CAM, Data Elements Eagerness to continue with DENM, Minimum Performance Requirements, Applications Openness to harmonizing on V2I/I2V messages (including CEN, ISO, Japan) Not yet clear what will happen with congestion control Recent dis-harmonization in Security area 6

7 Thinking Ahead: Life Cycle Management 2 Realities Continual Improvement 1) IT Lifecycle 1-3 years Vehicle Lifecycle years 2) We re not going to get this perfect the first time 7

8 Challenges/Opportunities PHY: DSRC uses a OFDM (1999) MAC: CSMA/CA saturates under high load BSM/CAM/DENM: New elements, higher precision expected Driven by or enabling applications not possible today Security: ECDSA won t last forever Portable Devices Spectrum-Sharing 8

9 Dependencies Depends on Application Characteristics Broadcast without advertisement Broadcast with advertisement (can direct to appropriate channel, can indicate capability) Unicast with advertisement (can negotiate) Depends on Layer PHY MAC (can use PHY indicator) Higher layer (can use lower layer indicators) Depends on V2V (peer-peer) vs V2I (client server) 9

10 Protocol Evolution Strategies Upgrade legacy equipment not desirable Backward compatibility Old New Protocol header assist and/or setup negotiation header Next Layer header Same channel co-existence New packet Old packet New packet time Migrate to new channel Use other technology (e.g. LTE, WiFi) as a bridge What can we learn from other technologies? Internet Cellular Digital TV New Ch. Old Ch. freq What can we do now to future-proof initially deployed devices? 10

11 John Kenney 11