MEMBERSHIP OPPORTUNITIES & ENGAGEMENTS Working Groups - - PowerPoint PPT Presentation
MEMBERSHIP OPPORTUNITIES & ENGAGEMENTS Working Groups - - PowerPoint PPT Presentation
MEMBERSHIP OPPORTUNITIES & ENGAGEMENTS Working Groups Certification Policy Automotive Cybersecurity Connected Vehicle Certification Tolling Certification Emerging Technologies Events Plugfests
MEMBERSHIP OPPORTUNITIES & ENGAGEMENTS Working Groups
- Certification Policy
- Automotive Cybersecurity
- Connected Vehicle Certification
- Tolling Certification
- Emerging Technologies
Events
- Plugfests
- Roundtables
- Workshops
Policy
- NHTSA V2V NPRM
- FCC Spectrum Docket
- Briefings with key Government
Officials
- October 16 – 20, Industry Sponsored
- San Francisco Bay Area
- 1-day policy workshop
- 4 days Reserved Test Sessions with
Concurrent Educational Activities
- Security / Certificates / SCMS Focus
(Green Hills-ISS & OnBoardSecurity)
- Test Equipment Providers &
Introduction/Interface
- Conformance & interoperability
Release 1 Conformance using 2016 Standards:
- IEEE 802.11p Physical Layer
- IEEE 1609.2 Security/Certificates
- IEEE 1609.3 Network (including WSA)
- IEEE 1609.4 Multi-Channel Operations
- SAE J2945.1 V-V BSMs Minimum
Performance (laboratory setting)
- Message Interoperability (laboratory setting)
Agenda 11:00 a.m. Opening and logistics Jason Conley, OmniAir Consortium 11:05 a.m. Welcome to SF Bay Area Andrew Fremier, Metropolitan Transportation Commission 11:15 a.m. OmniAir & Interoperability Dave Kristick, E-470 Public Highway Authority 11: 35 a.m. Introduction of USDOT official James Hofmann, North Texas Tollway Authority 11:40 a.m. Keynote 1— USDOT Vision for CAVs Jonathan Walker, U.S. Department of Transportation (invited) 12:00 p.m. Keynote 2—Caltrans Vision for CAVs Malcolm Dougherty, California Department of Transportation
Monday, October 16 Connected Vehicle Workshop
1:00 p.m. Panel 1
- 2X Interoperability and Testing
Moderator: Michael Stelts, Panasonic Speakers: Shailen Bhatt, Colorado Department of Transportation (invited) Tom Rzeznik, Danlaw Fernando Rodriguez, 7Layers Kendra Pridemore, UL 2:15 p.m. Panel 2- Connected Vehicle Interoperability Around the World Moderator: PJ Wilkins, E-ZPass Speakers: Myoung Hwan, ITS Korea (invited) Roland Jonasch, Transport Canada (invited) ITS Japan Representative TBD European Representative TBD 3:30 p.m. Panel 3
- Automotive Cybersecurity and V2X
Moderator: Andrew Howell, Monument Policy Group Speakers: Peter Samson, OnBoard Security David Sequino, Integrity Security Systems Dean Therriault, General Motors (invited) National Highway Traffic Safety Administration Rep. (invited) 4:30 p.m. Panel 4- Future Trends in Connected and Automated Vehicles Moderator: Andy Fremier, Metropolitan Transportation Commission Speakers: James (Jim) Misener, Qualcomm Robert Schill, HERE Techonologies Randell Iwasaki, Contra Costa Transportation Authority John Kenney, Toyota Info Technology Center 5:25 p.m. Closing Remarks Jason Conley, OmniAir Consortium
Agenda - Activities Running Parallel to Test Sessions
Tuesday October 17 8:00 to 8:30 am Introductions UL 8:30 to 10:30 am Testing Overview OmniAir & 7Layers 10:30 to 12:00 pm Security 101 & Certificates INTEGRITY Security Services 1:00 to 2:00 pm Security 101 & Certificates OnboardSecurity 2:00 to 3:30 pm Standards IEEE & SAE Kevin Smith & David Kelley 4:00 to 5:30 pm Connected Vehicle Pilots Invitations Wednesday October 18 8:00 to 8:30 am Announcements UL / OmniAir 8:30 to 9:30 am Laboratory Spotlight 7Layers (Authorized DSRC V2X) 9:30 to 10:30 am Test Equipment Spotlight Spirent 10:30 to 11:30 am Test Equipment Spotlight Danlaw 1:00 to 2:00 pm Test Equipment Spotlight Anritsu 2:00 to 3:00 pm Test Equipment Spotlight Keysight 3:00 to 4:00 pm Test Equipment Spotlight 3M 4:00 to 5:00 pm Test Equipment Spotlight TBD Thursday October 19 8:00 to 8:30 am Announcements UL / OmniAir 8:30 to 10:00 am Security 101 & Certificates INTEGRITY Security Services 10:00 to 11:30am Security 101 & Certificates OnBoardSecurity 1:00 to 3:00 pm CV Technical Committee OmniAir & Dmitri Khijniak - 7Layers 3:00 to 4:00 pm Group Interoperability OmniAir 4:00 to 5:30 pm Emerging Technology Committee TBD Friday October 20 8:00 to 8:30 am Announcements UL / OmniAir 8:30 to 10:00 am Policy Committee Kendra Pridemore—UL 10:00 to 12:00 pm Spring 2018 Plugfest Info & Survey Jason Conley—OmniAir
1 What is the device type? □ OBU □ RSU □ Test Tool Other __________ 2 How many physical radios and modes? □ One □ Two □ Continuous □ Alternating 3 What are the external communication interfaces? □ Wired USB □ Wired Ethernet □ Bluetooth □ WiFi / □ 4G LTE 4 What are the antenna port interfaces? □ GPS-DSRC Integrated GPS - □ Fakra □ SMA □ N-Type □ DSRC - Fakra DSRC - □ SMA □ N-Type 5 If OBU, implementation type is? □ Embedded □ Aftermarket □ OEM Add-on □ CAN I/F 6 If RSU, installation type is? □ Networked □ Standalone □ Master/Client □ Other ___________ 7 Does device support WAVE Short Messages (WSM)? □ Transmit □ Receive □ Both 8 Does device support WAVE Service Advertisement (WSA) Messages? □ Transmit □ Receive □ Both 9 Does device support IPv6 from WSA/WRA? □ Transmit □ Receive □ Both 10 Does device use 1609.2 security headers for message types? □ Unsecured □ Signed □ Encrypted 11 Which Security Certificates will the device use during testing? □ Plugfest □ CAMP QA □ USDOT Production □ SSPs 12 Does device Interfaces with SCMS to obtain or refresh Security Credentials? □ CAMP □ Green Hills □ None 13 Device Supports Test Control Interface (TCI) Standard? □ 802.11 □ 1609 □ J2945/1 □ None Message Types 13 Does device support BSM messages defined in SAE J2735? □ Transmit □ Receive □ Both 14 Does device support BSM requirement defined in SAE J2945/1? □ Transmit □ Receive □ Both 15 Does device support MAP messages defined in SAE J2735? □ Transmit □ Receive □ Both 16 Does device support RTCM messages defined in SAE J2735? □ Transmit □ Receive □ Both 17 Does device support SPAT messages defined in SAE J2735? □ Transmit □ Receive □ Both 18 Does device support TIM messages defined in SAE J2735? □ Transmit □ Receive □ Both Standards 19 Device supports IEEE 802.11:2012 (802.11p)? □ 10 MHz CHs □ 20 MHz CHs □ Data Rates (all) □ Power Max ___ dBm 20 Device supports IEEE 802.11:2012 (802.11p) regarding Frequency Mask? □ Mask C (required) □ Mask A □ Mask B □ Mask D 21 Device supports IEEE 1609.2:2016 WSM message signatures? □ Certificate □ Digest □ Both 22 Device supports IEEE 1609.2:2016 Security Profiles? □ BSM □ WSA □ MAP/SPaT □ RTCM □ TIM □ Other ______ 23 Device Supports IEEE 1609.3:2016? □ WSM □ WSA □ IPv6 □ All 24 Device Supports IEEE 1609.4:2016? □ Continuous □ Alternating □ User Priorities □ EDCA 25 Device Supports IEEE 1609.12:2016? □ PSID Sizes (1-2) □ PSID Sizes (3-4) □ p-encoding 26 Device Supports SAE J2735:2016? □ BSM □ MAP / SPaT □ RTCM □ TIM □ Other _______ 27 Device Supports SAE J2945/1:201603? □ BSM □ MAP / SPaT □ RTCM □ TIM □ Other ______ 28 Device Supports RSU 4.1a Specification □ Store & Forward □ Immediate Frwd □ SNMP Management □ HSM Security
What device types can be tested at the Plugfest?
- Roadside equipment (RSE)
- On-board equipment (OBE)
- Wireless modules
- Test system or test equipment
Date: Manufacturer Name:
Profiles
Model Number: V2V V2V RSU (V2I) Module Deviation Test Tool 1 What is the device type? OBU-SC OBU-MC RSU Other Transmit Receive 2 How many physical radios and modes? 1C 1A or 2C/A 2 C/A Either 1 Continuous on Separate CHs 3 What are the external communication interfaces? Optional Optional Wired Ethernet SMA Ethernet 4 What are the antenna port interfaces? Fakra Fakra N-Type Other
- Mates
5 If OBU, implementation type is? Various Various
- Ethernet
Ethernet / OTA 6 If RSU, installation type is?
- Ethernet
- Ethernet
Ethernet / OTA 7 Does device support WAVE Short Messages (WSM)? Both Both Both Either Yes Yes 8 Does device support WAVE Service Advertisement (WSA) Messages? Optional Receive Both
- Yes
Yes 9 Does device support IPv6 from WSA/WRA? Optional Both Transmit
- Yes
Yes 10 Does device use 1609.2 security headers for message types? Signed Signed Signed
- Signed
Signed 11 Which Security Certificates will the device use during testing? Either Either Either None Both Yes 12 Does device Interfaces with SCMS to obtain or refresh Security Credentials? Recommend Recommend Recommend None No No 13 Device Supports Test Control Interface (TCI) Standard? All All All 802.11 Depends Depends Message Types 13 Does device support BSM messages defined in SAE J2735? Both Both Receive
- Yes
Yes 14 Does device support BSM requirement defined in SAE J2945/1? Both Both Receive
- Yes
Yes 15 Does device support MAP messages defined in SAE J2735? Receive Receive Transmit
- Yes
Yes 16 Does device support RTCM messages defined in SAE J2735? Optional Optional Transmit
- Yes
Yes 17 Does device support SPAT messages defined in SAE J2735? Receive Receive Transmit
- Yes
Yes 18 Does device support TIM messages defined in SAE J2735? Receive Receive Transmit
- Yes
Yes Standards 19 Device supports IEEE 802.11:2012 (802.11p)? 10 MHz/6 Mbps 10 MHz/6 Mbps 10 MHz/All DR All Both All 20 Device supports IEEE 802.11:2012 (802.11p) regarding Frequency Mask? Mask C Mask C Mask C / D Mark C Mask C DNA 21 Device supports IEEE 1609.2:2016 WSM message signatures? Both Both Both
- Depends
Yes 22 Device supports IEEE 1609.2:2016 Security Profiles? All All All None Depends Yes 23 Device Supports IEEE 1609.3:2016? All All All All All All 24 Device Supports IEEE 1609.4:2016? Continuous Alternating All All Yes Continous on Separate CHs 25 Device Supports IEEE 1609.12:2016? All All All
- All
All 26 Device Supports SAE J2735:2016? Optional Optional Depends
- UPER / bit
UPER / bit 27 Device Supports SAE J2945/1:201603? BSM All Receive
- BSM
Yes 28 Device Supports RSU 4.1a Specification
- All
- DNA
Yes
What device types can be tested at the Plugfest?
- Roadside equipment (RSE)
- On-board equipment (OBE)
- Wireless modules
- Test system or test equipment
Test Cases in Bench Setting to be Conducted:
- Validated:
802.11p, IEEE 1609.3 WSM/WSA, IEEE 1609.4 WSM/WSA
- Validated Message Decoding: BSM, MAP, SPAT, TIM & WSA per J2735
- Verifying:
IEEE 1609.2 /Certificates, IEEE 1609.3 & .4 IPv6 & J2945/1
- Device Profiles:
V2V & V2I
- Trial:
Group Interoperability (Transmit & Receive) and Group Field Vehicle Testing Interoperability (OBU & RSU) RSU 4.1a
Test Equipment per Standards / Requirements:
- IEEE 802.11p PHY:
Danlaw (TCI), Rhodes-Schwarz, Anritsu & Keysight
- IEEE 1609.2 Security/Certificate:
Danlaw (TCI), Spirent (TCI) & 3M
- IEEE 1609.3 Network:
Danlaw (TCI) & Spirent (TCI), Anritsu & Keysight
- IEEE 1609.4 Multi-Channels:
Danlaw (TCI) & Spirent (TCI), Anritsu & Keysight
- IEEE 1609.12 PSIDs & SAE J2735 Messages: 3M
- SAE J2945.1 (V2V):
Spirent & SwRI (pathHistory)
- SCMS Processing:
Green Hills Software / OnBoardSecurity
- RSU 4.1a (V2I):
TBD / CoC & Message Decoding Only
Device Requirements & Testing:
- Test Equipment Interface:
TCIs per 802.11p, 1609 and J2945/1
- Test Case & TCI Specifications:
https://github.com/certificationoperatingcouncil/COC_TestSpecs
- PSIDs: per Message Types:
0x7F (test) and specific for test cases
- Security Certificates:
Fall 2017 Plugfest or CAMP QA versions
- Bench Testing per Test Cases:
Wired (no Over-The-Air)
- Group Interoperability:
Wireless / Over-The-Air
Overall Testing Requirements
- Test Control Interfaces [TCI] is strongly recommended for bench conformance testing through
1609.2, 1609.3 and 1609.4.
- Most 1609 tests will be wired with device recommended in isolated box. Signal attenuators
are recommended.
- IEEE 802.11p testing service would require desired TCI interface or test equipment’s
proprietary chipset interfaces. 802.11p will be a wired test with the device in isolated box.
- Devices will require security header regardless if broadcasting unsecured or signed messages.
- All devices indoors will be operating at default parameters (Power 15 dBm, 6 Mbps, and PSID
0x7FFF - Test) for WSM except for individual parameter variable under test.
- TCI is recommended to conduct J2945/1 bench testing for 0x20 BSMs and 0x23 SCMS. Device
is expected to operate at default parameters.
- Each test session may be required to use different channels for 1609.3 / 1609.4 (WSM, WSA
and IPv6) testing at 10 & 20 Hz if interference occurs.
- All PCAP files represent over-the-air captures both externally and internally.
- USB sticks will be provided to capture internal PCAP files under recommended file naming
structure: “[Test Case Number]-[Device Type]-[Manufacturer]-[TestStation]-[Session#].pcap”
Overall Testing Requirements (continue)
- 1609.2 Security will use “QA &/or plugfest” certificates. Security will test on BSMs
(CH172). Certificate changing may require GPS simulator to show location movement.
- Each Test Equipment used will contain both Chained Root Certificates (provided).
- Each Test Equipment will default security profiles (provided) for each message type.
- PSIDs will be 0p7FFF (WSMs), 0p20 (BSMs), 0p23 (SCMS) 0p80 (RTCM), 0p8007
(SPaT/MAP), 0p8003 (TIM), 0p87 (WSA) and 0pEF-FF-FF-FE (IPv6) during test sessions.
- Two bytes of four byte tempID recommended to be fixed if configurable.
- While not in testing sessions, PSID 0x7F (even BSMs) will be used.
- Well-formed 0x20 BSMs Part I & II CH172 transmissions from OBUs are required for field
interoperability testing.
- Group and Field Interoperability testing for OBUs will use 0x20 BSMs (CH172).
- Group and Field Interoperability testing for RSUs will be transmitting on CH172 (WSA,
SPaT, MAP)/ CH178 (WSA, TIM, MAP) and CH 182 (IPv6).
- FCC compliance where not operating under USDOT Experimental License Domain and
device requires proper labeling.
INTEGRITY Security Services, Inc., is providing test Enrollment Certificates and Pseudonym Certificates to End Entity OBU and RSU devices participating in OmniAir’s PlugFest this October. A key objective of this PlugFest is to verify the ability of an End Entity (EE) to obtain these certificates from the SCMS using the CAMP-defined protocols. To obtain certificates for the OmniAir PlugFest, End Entity (EE) companies will need to
- Register on the ISS V2X website (www.ghsiss.com/v2x ) for test
certificates
- Implement the CAMP-specified EE to SCMS messages
- Handle the subsequent SCMS responses to obtain and Enrollment
Certificate
- Request Pseudonym Certificates and to download the Pseudonym
Once an Enrollment Certificate is obtained, a Pseudonym Certificate request can then be made directly of the ISS Test Certificate Management System. Details on this process may be found in the FAQ on the website once you have registered for PlugFest test certificates at www.ghsiss.com/v2x
UL Laboratory
47173 Benicia St, Fremont, CA 94538 (510) 771-1000
- Parking may be limited and request consolidation.
- Test Equipment Manufacturers can setup on Monday starting at
8:00am / 1:00pm. Contact is: XXXXXXXXXXXXXXXX
- Tables setup and GPS Repeater in Testing Area (30’x40’).
- Training Center (30’x35’x40’ Triangle) with 10’ Screen
Mobile Vehicle Interoperability Testing
- One vehicle with multi-channel packet capture tool, reference
OBU and 2-3 devices under test sending BSMs will drive proposed route under variety of speed conditions ~ 25-30 minutes to provide:
- Parameter Consistency among different device providers.
- Direction and Speed Unlatching and Latching
- Hard Braking Event Flag
- PathHistory Analysis
- Certificate Changing due to movement
- Few RSU opportunities to setup and transmit SPaT/MAP and
TIM messages.
- Group assignments based on product variations (certificate
source, security and etc.)
Next Steps
- Register (http://omniair.org/events/ or www.eventbrite.com/e/omniair-
consortiums-plugfest-by-the-bay-2017-tickets-36163330495) to participate in PlugFest and determine readiness. Few sponsorships still available. Current sponsors need to provide their allotted attendees list to Ryan Hall (rhall@omniair.org).
- Next Connected Vehicle’s technical committee meeting is scheduled for Tuesday
September 26 at 12:00pm EDT in plugfest preparation feedback.
- Is additional “Plugfest Technical Preparation Awareness” webinar needed? and
regional time zone?
- Device manufacturers can send message capture PCAP files before October 1 for
well-formed packet decoding feedback.
- Additional technical questions can be addressed to Dmitri Khijniak