OmniAir Consortium 5.9 GHz DSRC Certification Update IEEE 1609 Working Group April 29 th 2008

1. OmniAir Consortium 5.9 GHz DSRC Certification Update IEEE 1609 Working Group April 29th 2008 Los Angeles, CA Tim McGuckin, OmniAir Randy Roebuck, SIRIT, Certification Committee Co-Chair William Wolf, SwRI, Test Method Writer

2. Certification Structure Presented Framework at VII WG Meeting 2/27 Completed surveys & are examining inputs Exploring Business Models Incorporating “Wi-Fi” testing concepts from UNH-IOL Introduced Certification & Interoperability to VOLPE Identifying tools Liability White Paper Completed & Ready for Review by VII WG 1609 Test Method Draft Completed & Ready for Selective Review Primer Available as Introduction Suggest Test Method Focus Session with Device Developers for testing feasibility and streamlining. Concept of Operations First Phase Completed – updating to reflect VTD approach VII Tactical Deployment Workshop Scheduled May 22 in McLean, VA DSRC Activities Status

3. Timing Initial outreach & education needed to get stakeholders predisposed to DSRC and certification elements. OmniAir waited to ramp up due to time-constraints of our audience – the technical experts busy developing the POC through 2007. Now is the right time to address certification, as many are still working cooperatively and evaluating RSE/OBE units through POC testing and second generation standards enhancements. Purpose Recommend a structure reflective of the stakeholders’ needs for compliant, interoperable DSRC systems. Address the ability to test and certify RSE/OBE implementations against current architecture and standards. Understand and track/address where changes need to occur in a context of ‘testability.’ Consider standards in terms of ensuring interoperability and open system deployment. Hi-Level Certification Status

4. For POC units, even using mostly common components, there was a challenge to get devices communicating. Underscores the essential necessity for compliance & interoperability testing. Surveys supported the need for: higher degree of unit definition more up-to-date standards and standards enhancements, and device/system testability Independent test method generation – to provide insight on the potential issues of hardware implementations of the standards. Hi-Level Certification Status

5. TBD Application Certification VII POC CICAS EPS TBD 1609.1 Virtual Device-to-Application Interface Architecture / Overall Unit Spec (i.e. 1609.0) J2735 Test Method (by OmniAir*) OmniAir Device Certification Program - the management entity 1609.2-4 Test Method (by OmniAir) Additional Test Methods (by OmniAir*) IEEE 1609.3 & .4 (Stack) & .2 (Blended) SAE J2735 Message Set 802.11p Test Method (by ASTM *) IEEE 802.11p Standard Message / Application Handler? SAE Device Certification Coverage ?+ * - Need / Desire

6. Auto OEMs • OBE V-V • OmniAir • Device Air I/F Certification • Future Application Certification Network Ethernet RSE OBE # B OBE # C OBE # A Golden Verification Units Certification Responsibilities Revised “Up-the-Stack plus Security and Over-the-Air” • Special / Regional / Opt-in Apps Packet Sniffer

7. ? Certification Flow (draft)

8. Phased Testing Approach • Note: • This structure option significantly limits OmniAir’s legal liability; only 3rd parties provide the approval that “this device will not fail”; OmniAir is simply verifying that a device has passed the requirements & processes of the Consortium’s defined test program as carried out. • Timelines are driven by device availability, released standards, regulations and market.

9. Test Method Development OmniAir’s Test Methods • WA-4: IEEE P1609.2-.4 Standards. • 1st Draft (280pgs) completed Nov 2007 • Reviewed with POC Hardware Tester December 2007 • Test Method Primer Available • Limited Distribution for Technical Comments ~Spring 2008 • Must be revised as Standards evolve. • Proposed WA-6: SAE J2735 • Proposed WA-11: Complete 802.11p Test Method (started for ASTM 2213) • Proposed WA-12: Integration of the 802.11p TM with the OmniAir TM for IEEE 1609.2-4 • Test Methods Based On: • IEEE STD 1609.2:2006 (06 Jul 06) • IEEE STD 1609.3:2007 (20 Apr 07) • IEEE STD 1609.4:2006 (29 Nov 06)

10. Test Methods Approach • Select conformance items from standards • Incorporate use-case structure as appropriate • Identify tester requirements • Describe test environment • No use of SAP’s, primitives in test methods • Monolithic black box testing of 1609 implementation • Develop cross-reference table for traceability • Develop generic draft test method

11. Testability Concerns Departures from Standards • As a result of comparing available DSRC units (developed to test DSRC requirements), OmniAir discovered that radio manufacturers’ implementations do not entirely conform to the standards as released for trial use. • Current devices thus do not comport well with test methods because implementations do not comport well with standards. • While some departure from a trial use standard is expected, it is unclear whether these non-standard changes have been: • thoroughly documented; • approved by the USDOT as the new de facto standard; or • whether there is a plan to update the IEEE 1609 set of standards to reflect these implementations. • We believe that failing to thoroughly document variants couldhave serious implications to the overall goal of a completely interoperable 5.9GHz DSRC deployment.

12. Certification Process needs to accommodate the OBE deployment stages: Carried-in (Standalone) Smaller in size, scope & cost No vehicle electrical connections (power & communication) RSE–OBE Services Limited Tolling, Parking, Point of Sale and Probe Data Applications Mildly Embedded RSEs being deployed more heavily Auto OEMs allocate small space (headliner) and power connection. May offer serial interface to the vehicle. Industry Standards push across all necessary peripherals RSE-OBE and OBE-OBE Functionality More complex applications Fully Embedded Warrants automotive investment for national deployment Fully integrated device with sophisticated comm. buss interface Basic safety applications with Driver interaction Working as communication gateway Tactical Deployment Stages

13. IEEE 802.11p released & its test method developed IEEE 1609 Trial Standards & their Test Method updated to reflect latest technical findings Peripheral standards identified & associated such as GPS Positioning, Data Encryption (IPv6 UDP) and etc. New standards developed for multiple-application / services management such as Message Handler Independent RSE/OBE units to reflect latest standards & long-term requirements used as “Golden Units” Test Tools enhanced to reflect “Up-the-Stack plus Security and Over-the-Air” direction. Regulatory rules (specification) defining overall 5.9GHz DSRC RSE & OBE minimum unit requirements to qualify as a VII system component. Verification/Certification of “Mandatory Active Safety” applications (as required on all candidate units) - must determine where this is addressed. Key Items to complete

14. Everyone’s participation is needed to develop certification process and cannot be isolated activity. Opportune time in current VII test beds to address testability which affects the architecture and implementation of radio functionality / modularity and total integration. Certification must evolve to address incremental deployment stages and its policies. Overall objective is to maintain a focus on system integrity & device interoperability to insure “open” system. Summary

15. VII is not a question! How we get there needn’t be either! Held at Booz Allen Conference Center, McLean, VA Thursday May 22, 2008 from 8:45am to 5:30pm plus reception Panels: Tactical Foundation Design Feasibility Data / Info Delivery Business Model See PDF Brochure for details, or visit www.omniair.org/vtd/workshop/ Tactical Deployment Workshop