The USDOT’s three Connected Vehicle Pilots successfully demonstrate cross-site over-the-air interoperability among six participating vendors.

Interoperability-related activities pave the way for roll-out of connected vehicle technologies, with devices and applications operating as designed across the nation.


Background (Show)

Lesson Learned

To pave the way for a nationwide deployment, a major long-term goal of the Connected Vehicle (CV) Pilot Deployment Program is for the connected vehicle devices and equipment to be interoperable, meaning that they would be able to operate as designed anywhere in the country, regardless of where they were built. The cooperative agreements between the United States Department of Transportation (USDOT) and the CV Pilot Deployment Sites (New York City, Tampa and Wyoming) included a requirement for the CV Pilot sites to perform an activity that showed the devices from the three sites being interoperable. Leveraging a series of technical roundtable meetings, the USDOT and the three CV Pilot sites settled on a definition of interoperability and an approach to conduct a limited test of interoperability. For purposes of the interoperability activity, the USDOT and CV Pilot sites defined interoperability as:

"A vehicle with an onboard unit (OBU) from one of the three CV Pilot sites is able to interact with OBUs and/or roadside units (RSUs) from the other sites in accordance with the key connected vehicle interfaces and standards."

Over a period of several months, the CV Pilot sites collaborated to harmonize the data elements that would make such interactions possible. The CV Pilot sites next worked with the USDOT and its support contractor to develop a plan to conduct an Interoperability Test that would take place at Turner-Fairbank Highway Research Center (TFHRC) in McLean, Virginia from June 26th-28th, 2018. In addition to testing interoperability among connected vehicle devices from the three sites, the testing also served to identify potential interoperability issues that may require resolution prior to the sites advancing to an operational phase of the CV Pilot Deployment Program later in 2018.

Planning for the testing event was jointly led by the CV Pilot sites in coordination with TFHRC and USDOT staff. TFHRC and its Saxton Transportation Operations Laboratory (STOL) contractor provided support to the CV Pilot sites as well as the facility and supporting equipment for the testing. This support included installing the same RSU models used by the sites to allow them to replicate their configurations, installing OBUs from the sites in vehicles and providing trained drivers to operate the vehicles during the interoperability test runs. In addition to the USDOT and sites, representatives of the CV Pilots’ Independent Evaluation (IE) team were present to observe in support of the broader independent evaluation effort. Six TFHRC-provided vehicles were used for the testing with each vehicle being outfitted with an OBU from one of the CV Pilot site’s OBU vendors – Tampa (3), New York City (2) and Wyoming (1). Additionally, the sites each loaded the TFHRC-supplied RSUs with their own software. A test of this nature involving three deployment sites, six device vendors and multiple communications media had never been done before – making the Interoperability Test a truly unicorn event.

The purpose of the Interoperability Test was to test: (1) interactions between different sites’ OBUs and (2) interactions between selected OBUs and RSUs. Specific objectives are summarized in the table below:
Interactions between different CV Pilot sites’ OBUOBUs from each site should be able to receive SAE J2735 Basic Safety Messages (BSMs) transmitted by each of the other site’s OBUs over-the-air, authenticate them, parse them and process them in accordance with SAE J2945/1.
The Forward Collision Warning (FCW) application – an application all three sites are utilizing in their Pilots – hosted by OBU-equipped vehicles from each site should be able to interact with equipped lead vehicles from each of the other sites in an open-sky environment, and demonstrate a response (e.g., alert). Additionally, the Electronic Emergency Brake Light (EEBL) and Intersection Movement Assist (IMA) applications on OBUs from Tampa and New York City should be able to interact with equipped vehicles from the other site in an open-sky environment.
Interactions between selected OBUs and RSUsOBUs from New York City and Tampa should be able to receive and parse SAE J2735 Signal Phase and Timing (SPaT) and MAP messages sent by RSUs. (Note: Wyoming’s Pilot does not involve intersections so Wyoming did not participate in the RSU testing).

The capabilities listed in the table above were demonstrated in staged scenarios on TFHRC’s closed road course. In total, 102 interoperability test runs were conducted for four test cases – FCW, IMA, EEBL and reception of SPaT/MAP messages. Data was downloaded off of the OBUs immediately following each test run, with nearly 5 GB worth of data being generated over the test period. This data will be uploaded to the USDOT’s Secure Data Commons (SDC) for further analysis to help identify lessons learned that can be gleaned for future testing.
Overall, the three-day testing event was a major success that went above and beyond the event’s original testing objectives, with time allotted on the last day for some impromptu tests by the sites. Results of the testing indicated successful transfer of messages between the six vehicles fit with devices from five different OBU vendors. Out of the five vendors, four utilized DSRC and one used both DSRC and SiriusXM Radio. Additionally, equipment from New York City and Tampa’s vendors demonstrated the successful transfer of messages between the site-configured RSUs and the sites’ OBUs. The event was lauded by many for being well-planned, well-organized, and well-executed, with some attendees reporting that it was the most successful connected vehicle testing event they had ever participated in. The Interoperability Test was a watershed moment for connected vehicle technology, and an important milestone in the maturation of these technologies for operational deployment.

A Final Test Report documenting the results of the Interoperability Test is expected to be made available in Fall 2018.

Lesson Comments

No comments posted to date

Comment on this Lesson

To comment on this lesson, fill in the information below and click on submit. An asterisk (*) indicates a required field. Your name and email address, if provided, will not be posted, but are to contact you, if needed to clarify your comments.


Connected Vehicle Pilot Deployment Program: Success Stories

Author: Glassco, Rick; James O'Hara; Barbara Staples; Kathy Thompson; and Peiwei Wang

Published By: USDOT Office of the Secretary for Research and Deployment

Source Date: 11/01/2017

URL: https://www.its.dot.gov/pilots/success_lessonslearned.htm

Other Lessons From this Source

Lesson Contacts

Lesson Analyst:

Kathy Thompson


Average User Rating

0 ( ratings)

Rate this Lesson

(click stars to rate)

Lessons From This Source

Allow for increased coordination with the Interdepartmental Radio Advisory Committee (IRAC) early on in the DSRC licensing process to help reduce what is traditionally a very lengthy process.

Connected Vehicle Pilot Deployment Program yields program management best practices for integrating and testing large disparate systems.

Connected vehicles should rely on more than one data feed to determine accurate location and speed

Consider installing additional vehicle detection equipment if it is determined that there is not sufficient market penetration for CV traffic signal control applications to work at their full potential

Facing a gap in standards interpretation, the Tampa and New York City Connected Vehicle Pilot Sites worked together to harmonize message structure for pedestrian safety applications.

For pedestrian safety warning applications, opt to collect pedestrian location data from LIDAR sensors instead of pedestrian mobile devices that often have insufficient accuracy.

Incentivize participation in CV deployments through benefits such as toll discounts

Include technical, operations, and legal personnel in stakeholder meetings to address the requirements of the CV deployment and ensure that participants' privacy is being maintained

Incorporate standardized over-the-air update procedures to permit efficient firmware updates for connected vehicle devices.

Obtain working prototypes of CV applications from the USDOT’s Open Source Application Data Portal (OSADP) to prevent time spent doing duplicative software development

Prevent the need for channel switching (a safety hazard) by designing CV communications to include dual radios in each vehicle

Publish all CV planning documentation to serve as an example for other early deployers to follow

The Tampa Connected Vehicle Pilot Program investigates damage to roadside units (RSUs) near lightning strikes and improves transient surge immunity by verifying nearby support structures are properly grounded.

The USDOT’s three Connected Vehicle Pilots successfully demonstrate cross-site over-the-air interoperability among six participating vendors.

Use local student mechanics where possible to perform CV equipment installations to provide students with required trainee experience and to contain costs

Use on-board connected vehicle (CV) technology and SPaT / MAP infrastructure messages to prevent wrong way entries on reversible express lanes.

When installing antennas on streetcars to support wireless connected vehicle applications, verify that radio performance is not compromised by interference from high-voltage power lines.


None defined


None defined

Systems Engineering

Show the V

Unit / Device Testing

Focus Areas

None defined

Goal Areas



None defined

Lesson ID: 2018-00831