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

Success Stories from the USDOT’s Connected Vehicle Pilot Program

Tampa; Florida; United States

Background (Show)

Lesson Learned

All of the connected vehicle applications being implemented and evaluated in the Connected Vehicle Pilot Deployment Program did not need to be developed from scratch. Software developers for the three CV Pilot sites have been able to take advantage of software prototyped by many programs, including the USDOT’s Dynamic Mobility Applications (DMA) program and the Safety Pilot Model Demonstration project in Ann Arbor, MI.

One of THEA’s six use cases is to prevent the entry of vehicles going the wrong way (against the permitted flow of traffic for Traffic Signal the given time of day) onto the Reversible Express Lanes (REL) of the Lee Roy Selmon Expressway. Entry into the REL is governed by a traffic signal so THEA started by using existing Red Light Violation Warning (RLVW) software. The plan was to treat the traffic signal as if it changed only twice per day (i.e., at the times the directionality of the REL was reversed) and that a vehicle trying to enter the REL the wrong way could be detected as if it were trying to run a red light.

However, the complexity of the intersection (cars could enter the REL from three intersection approach directions, and could go in legal directions as well as the illegal direction) made this approach unworkable. THEA evolved the RLVW application into a Wrong Way Entry (WWE) application. The key change was to adapt the Signal Phase and Timing (SPaT) and MAP (intersection geometry) messages broadcast by the traffic signal to include a bit for each approach lane indicating whether the direction for that lane is "revocable", i.e. changeable. By examining the "revocable" bit for the lane of an approaching vehicle and the time of day, the vehicle’s Onboard Unit (OBU) can determine whether it is going the wrong way. If so, it will send a warning message to the vehicle’s driver and broadcast a warning message to the drivers of approaching vehicles.

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.

Lesson ID: 2018-00812