City of Orlando Smart Corridor Technologies

Project Description: This project would install intelligent sensor based infrastructures – RSU, ATSPM, SPaT, CCTV, Bluetooth Detectors, EVP, TSP, Passive pedestraian etc. along the International Drive from World Center Drive to Oak Ridge Drive.

Project Status: Planned

Project Stakeholders:

Project Inventory:

Interconnect and Flow

Diagrams

Project Service Packages:

TM03: Traffic Signal Control (City of Orlando Smart Corridor Technologies)
TM06: Traffic Information Dissemination (City of Orlando Smart Corridor Technologies)
SU04: Map Management (City of Orlando Smart Corridor Technologies)
SU08: Security and Credentials Management (City of Orlando Smart Corridor Technologies)
TM04: Connected Vehicle Traffic Signal System (City of Orlando Smart Corridor Technologies)
VS12: Vulnerable Road User Safety (City of Orlando Smart Corridor Technologies)
TM01: Infrastructure-Based Traffic Surveillance (City of Orlando Smart Corridor Technologies)
PM01: Parking Space Management (City of Orlando Smart Corridor Technologies)
PT09: Transit Signal Priority (City of Orlando Smart Corridor Technologies)
TM02: Vehicle-Based Traffic Surveillance (City of Orlando Smart Corridor Technologies)
SU01: Connected Vehicle System Monitoring and Management (City of Orlando Smart Corridor Technologies)
PS03: Emergency Vehicle Preemption (City of Orlando Smart Corridor Technologies)

Project Information Flows:

Information Flow	Source Element	Destination Element	Status
communications signature	Vehicle	City of Orlando Field Equipment	Planned
equipment control commands	CAV Authorizing Center	City of Orlando CAV Field Equipment	Planned
equipment control commands	City of Orlando TMC	City of Orlando CAV Field Equipment	Planned
high resolution signal controller data_ud	City of Orlando Field Equipment	City of Orlando TMC	Planned
intersection geometry	CAV-ITS Map Update System	City of Orlando CAV Field Equipment	Planned
intersection geometry	CAV-ITS Map Update System	City of Orlando TMC	Planned
intersection geometry	City of Orlando CAV Field Equipment	City of Orlando Fire Vehicles	Planned
intersection geometry	City of Orlando CAV Field Equipment	Private Travelers Personal Computing Devices	Planned
intersection management application info	City of Orlando TMC	City of Orlando CAV Field Equipment	Planned
intersection management application status	City of Orlando CAV Field Equipment	City of Orlando TMC	Planned
intersection safety application info	City of Orlando TMC	City of Orlando CAV Field Equipment	Planned
intersection safety application status	City of Orlando CAV Field Equipment	City of Orlando TMC	Planned
intersection status	City of Orlando CAV Field Equipment	City of Orlando Fire Vehicles	Planned
intersection status	City of Orlando CAV Field Equipment	Private Travelers Personal Computing Devices	Planned
local signal preemption request	City of Orlando Fire Vehicles	City of Orlando CAV Field Equipment	Planned
local signal preemption request	City of Orlando Fire Vehicles	City of Orlando Field Equipment	Planned
local signal priority request	LYNX Transit Vehicles	City of Orlando CAV Field Equipment	Planned
local signal priority request	LYNX Transit Vehicles	City of Orlando Field Equipment	Planned
map update notification	City of Orlando TMC	CAV-ITS Map Update System	Planned
map updates	CAV-ITS Map Update System	City of Orlando CAV Field Equipment	Planned
map updates	CAV-ITS Map Update System	City of Orlando TMC	Planned
misbehavior report	City of Orlando CAV Field Equipment	FDOT SCMS	Planned
misbehavior report	City of Orlando Fire Vehicles	FDOT SCMS	Planned
misbehavior report	City of Orlando TMC	FDOT SCMS	Planned
misbehavior report	LYNX Transit Vehicles	FDOT SCMS	Planned
parking area information	City of Orlando Parking Equipment	City of Orlando Parking	Planned
parking area management information	City of Orlando Parking	City of Orlando Parking Equipment	Planned
parking information	City of Orlando Parking	City of Orlando TMC	Planned
passive vehicle monitoring control	City of Orlando TMC	City of Orlando Field Equipment	Planned
passive vehicle monitoring data	City of Orlando Field Equipment	City of Orlando TMC	Planned
personal crossing safety information	City of Orlando CAV Field Equipment	Private Travelers Personal Computing Devices	Planned
personal location	Private Travelers Personal Computing Devices	City of Orlando CAV Field Equipment	Planned
personal signal service request	Private Travelers Personal Computing Devices	City of Orlando CAV Field Equipment	Planned
right-of-way request notification	City of Orlando Field Equipment	City of Orlando TMC	Planned
roadway dynamic signage data	City of Orlando TMC	City of Orlando Field Equipment	Planned
roadway dynamic signage status	City of Orlando Field Equipment	City of Orlando TMC	Planned
roadway geometry	CAV-ITS Map Update System	City of Orlando CAV Field Equipment	Planned
RSE application information	CAV Authorizing Center	City of Orlando CAV Field Equipment	Planned
RSE application install/upgrade	CAV Authorizing Center	City of Orlando CAV Field Equipment	Planned
RSE application status	City of Orlando CAV Field Equipment	City of Orlando TMC	Planned
security credential revocations	FDOT SCMS	City of Orlando CAV Field Equipment	Planned
security credential revocations	FDOT SCMS	City of Orlando Fire Vehicles	Planned
security credential revocations	FDOT SCMS	City of Orlando TMC	Planned
security credential revocations	FDOT SCMS	LYNX Transit Vehicles	Planned
security credentials	FDOT SCMS	City of Orlando CAV Field Equipment	Planned
security credentials	FDOT SCMS	City of Orlando Fire Vehicles	Planned
security credentials	FDOT SCMS	City of Orlando TMC	Planned
security credentials	FDOT SCMS	LYNX Transit Vehicles	Planned
security policy and networking information	FDOT SCMS	City of Orlando CAV Field Equipment	Planned
security policy and networking information	FDOT SCMS	City of Orlando Fire Vehicles	Planned
security policy and networking information	FDOT SCMS	City of Orlando TMC	Planned
security policy and networking information	FDOT SCMS	LYNX Transit Vehicles	Planned
signal control commands	City of Orlando TMC	City of Orlando Field Equipment	Planned
signal control device configuration	City of Orlando TMC	City of Orlando Field Equipment	Planned
signal control plans	City of Orlando TMC	City of Orlando Field Equipment	Planned
signal control status	City of Orlando Field Equipment	City of Orlando TMC	Planned
signal fault data	City of Orlando Field Equipment	City of Orlando TMC	Planned
signal preemption request	City of Orlando CAV Field Equipment	City of Orlando Field Equipment	Planned
signal preemption request	City of Orlando Field Equipment	City of Orlando CAV Field Equipment	Planned
signal priority status	City of Orlando CAV Field Equipment	City of Orlando Fire Vehicles	Planned
signal priority status	City of Orlando CAV Field Equipment	LYNX Transit Vehicles	Planned
traffic detector control	City of Orlando TMC	City of Orlando Field Equipment	Planned
traffic detector data	City of Orlando Field Equipment	City of Orlando TMC	Planned
traffic images	City of Orlando Field Equipment	City of Orlando TMC	Planned
traffic monitoring application status	City of Orlando CAV Field Equipment	City of Orlando TMC	Planned
traffic situation data	City of Orlando CAV Field Equipment	City of Orlando TMC	Planned
vehicle location and motion	City of Orlando Fire Vehicles	City of Orlando CAV Field Equipment	Planned
vehicle location and motion	LYNX Transit Vehicles	City of Orlando CAV Field Equipment	Planned
vehicle location and motion	LYNX Transit Vehicles	City of Orlando Field Equipment	Planned
vehicle location and motion	Vehicle	City of Orlando CAV Field Equipment	Planned
vehicle location data for mapping	City of Orlando CAV Field Equipment	CAV-ITS Map Update System	Planned
video surveillance control	City of Orlando TMC	City of Orlando Field Equipment	Planned

Project Functional Requirements (Element - Functional Object):

CAV Authorizing Center - Center Connected Vehicle Infrastructure Management

1: The Center shall be capable of monitoring the operational status of Connected Vehicle Roadside Equipment applications.
2: The Center shall be capable of modifying the operational status of Connected Vehicle Roadside Equipment applications.
3: The Center shall request Connected Vehicle Roadside Equipment maintenance actions from other responsible centers.
4: The Center shall be capable of modifying the operational status of Connected Vehicle Roadside Equipment.
5: The Center shall track the status of Connected Vehicle Roadside Equipment maintenance actions.
6: The Center shall be capable of installing software applications on Connected Vehicle Roadside Equipment.
7: The Center shall accept information from other Centers that indicates which Connected Vehicle Roadside Equipment needs maintenance.

CAV-ITS Map Update System - Map Management

20: The Center shall provide basemap updates to Personal devices.
21: The Center shall provide intersection geometry updates to Vehicles.
22: The Center shall provide basemap updates to Vehicles.
24: The Center shall provide intersection geometry updates to Personal Devices.
27: The Center shall provide basemap updates to Connected Vehicle Roadside Equipment.
5: The Center shall provide basemap updates to other Centers.

City of Orlando CAV Field Equipment - ITS Management Support

1: The ITS Object shall provide its network address, service offerings and metrics characterizing those services to vehicles within the broadcast range of the ITS Object's short range communications equipment.
2: The ITS Object shall provide its network address, service offerings and metrics characterizing those services to the Object Registration and Discovery Service.
3: The ITS Object shall obtain network addresses from the Object Registration and Discovery Service.
4: The ITS Object shall make network address information available to onboard applications.
5: The ITS Object shall provide its configuration and operational status information to the Service Monitor
6: The ITS Object shall acquire regulatory information relevant to the operation of the ITS Object from the CCMS.

City of Orlando CAV Field Equipment - ITS Security Support

1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
10: The ITS Object shall maintain cryptographic secret information so that those secrets are accessible only to ITS Security Support, and not to any other Functional Object.
11: The ITS Object shall request pseudonymous credentials from the CCMS.
12: The ITS Object shall provide messages (that it receives) that indicate potential misbehavior/malfunction to the CCMS.
13: The ITS Object shall request permissions from the Center that manages permissions requests.
2: The ITS Object shall request enrollment credentials from the CCMS.
3: The ITS Object shall obtain the CCMS' trust credentials.
4: The ITS Object shall provide a mechanism for on-board applications to digitally sign messages using keys secured by the CCMS' trust authority.
5: The ITS Object shall provide a mechanism for on-board applications to authenticate messages secured by the CCMS' trust authority.
6: The ITS Object shall provide a mechanism for on-board applications to encrypt messages using keys secured by the CCMS' trust authority.
7: The ITS Object shall provide a mechanism for on-board applications to decrypt messages using keys secured by the CCMS' trust authority.
8: The ITS Object shall obtain a list of revoked credentials from the CCMS.
9: The ITS Object shall make the list of revoked credentials available to on-board applications.

City of Orlando CAV Field Equipment - RSE Device Management

1: The field element shall monitor the operational status (state of the device, configuration, and fault data) of connected sensors (such as traffic, infrastructure, environmental, security, speed) and devices (such as highway advisory radio, dynamic message signs, automated roadway treatment systems, barrier and safeguard systems, cameras, traffic signals, ramp meters, short range communications equipment, security surveillance equipment).
10: The field element shall implement configuration commands received from authorized Field Support Equipment.
2: The field element shall send operational status of connected field equipment to the maintenance center.
3: The field element shall send collected fault data to the maintenance center for repair.
4: The field element shall include a local interface that provides operational status and fault data for connected field equipment to field personnel.
5: The field element shall include a local interface that allows field personnel to command diagnostic tests on connected field equipment.
6: The field element shall provide operational status information to the Service Monitor.
7: The field element shall implement configuration commands received from an authorized Center.
8: The field element shall implement operational status commands received from an authorized Center.
9: The field element shall implement operational status commands received from authorized Field Support Equipment.

City of Orlando CAV Field Equipment - RSE Intersection Management

1: The field element shall communicate with passing vehicles to provide the current signal phase and timing information for all lanes and approaches at a signalized intersection.
2: The field element shall send the request for emergency vehicle preemption to a traffic signal controller that results in preemption of the current control plan and grants right-of-way to the requesting vehicle.
5: The field element shall receive transit signal priority requests from transit vehicles and forward to the traffic signal controller.
6: The field element shall receive emergency vehicle preemption requests from emergency vehicles and forward to the traffic signal controller.

City of Orlando CAV Field Equipment - RSE Intersection Safety

3: The roadway equipment shall collect vehicle path information sent by a vehicle.
5: The roadway equipment shall send to Connected Vehicles intersection signal timing information in order for the vehicle to determine if it will safely cross the intersection given its current speed and location.
6: The roadway equipment shall send to connected vehicles a warning if an intersection violation appears to be imminent.

City of Orlando CAV Field Equipment - RSE Map Management

1: The field element shall collect broadcasted vehicle location and motion information.
10: The field element shall provide intersection geometry updates to proximate Vehicles.
11: The field element shall provide parking facility geometry information to proximate Personal devices.
12: The field element shall provide roadway geometry updates to proximate Vehicles.
2: The field element shall aggregate vehicle location data.
3: The field element shall provide roadway geometry update information to proximate Vehicles.
4: The field element shall provide parking facility geometry information to proximate Vehicles.
5: The field element shall provide intersection geometry update information to proximate Vehicles.
6: The field element shall provide basemap update information to proximate Vehicles.
7: The field element shall provide intersection geometry update information to proximate Personal devices.
8: The field element shall provide vehicle location data to Centers.
9: The field element shall provide basemap updates to proximate Vehicles.

City of Orlando CAV Field Equipment - RSE Situation Monitoring

1: The field element shall collect traffic-related data including snapshots of measured speed and heading and events including starts and stops, speed changes, and other vehicle control from vehicles.

City of Orlando CAV Field Equipment - RSE Traffic Monitoring

1: The field element shall communicate with on-board equipment on passing vehicles to collect current vehicle position, speed, and heading and a record of previous events (e.g., starts and stops, link travel times) that can be used to determine current traffic conditions.

City of Orlando Field Equipment - Roadway Basic Surveillance

1: The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the center for further analysis and storage, under center control.
2: The field element shall collect, process, and send traffic images to the center for further analysis and distribution.
4: The field element shall return sensor and CCTV system operational status to the controlling center.
5: The field element shall return sensor and CCTV system fault data to the controlling center for repair.

City of Orlando Field Equipment - Roadway Passive Monitoring

1: The field element shall collect, process, and send data to the center to uniquely identify passing vehicles in order to support travel time measurement

City of Orlando Field Equipment - Roadway Signal Control

1: The field element shall control traffic signals under center control.
10: The field element shall receive request for transit vehicle signal priority.
15: The field element shall provide to roadside equipment the intersection geometry and signal phase movement information including phase and timing information, alarm status, and priority/preempt status.
17: The field element shall receive requests for signal preemption.
2: The field element shall respond to pedestrian crossing requests by accommodating the pedestrian crossing.
5: The field element shall report current preemption status to the center.
6: The field element shall return traffic signal controller operational status to the center.
7: The field element shall return traffic signal controller fault data to the center.
8: The field element shall report current transit priority status to the center.

City of Orlando Field Equipment - Roadway Traffic Information Dissemination

1: The field element shall include dynamic message signs for dissemination of traffic and other information to drivers, under center control; the DMS may be either those that display variable text messages, or those that have fixed format display(s) (e.g. vehicle restrictions, or lane open/close).
3: The field element shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the center.

City of Orlando Fire Vehicles - EV On-Board En Route Support

1: The emergency vehicle, including roadway service patrols, shall track its current location.
5: The emergency vehicle shall send requests to traffic signal control equipment at the roadside to preempt the signal.

City of Orlando Parking - Parking Coordination

3: The parking element shall distribute parking lot information to traffic management centers upon request to support integrated regional traffic control and parking management. This could include information on facility hours of operation and current parking availability.
7: The parking facility shall determine availability of parking spaces.

City of Orlando Parking - Parking Management

1: The center shall monitor parking area current operational status including current parking occupancy and rates.

City of Orlando Parking Equipment - Parking Area Management

1: The parking element shall maintain static parking lot information including hours of operation, rates, location, entrance locations, capacity, type, and constraints.
3: The parking element shall determine and maintain the number and availability of parking spaces.

City of Orlando TMC - Center Connected Vehicle Infrastructure Management

1: The Center shall be capable of monitoring the operational status of Connected Vehicle Roadside Equipment applications.
2: The Center shall be capable of modifying the operational status of Connected Vehicle Roadside Equipment applications.
4: The Center shall be capable of modifying the operational status of Connected Vehicle Roadside Equipment.

City of Orlando TMC - Center Map Management

1: The Center shall collect updates to basemaps from Map Update Systems .
2: The Center shall collect updates to intersection geometry from Map Update Systems.
3: The Center shall provide roadway geometry updates to Map Update Systems.
4: The Center shall provide intersection geometry updates to Map Update Systems.

City of Orlando TMC - ITS Management Support

1: The ITS Object shall provide its network address, service offerings and metrics characterizing those services to vehicles within the broadcast range of the ITS Object's short range communications equipment.
2: The ITS Object shall provide its network address, service offerings and metrics characterizing those services to the Object Registration and Discovery Service.
3: The ITS Object shall obtain network addresses from the Object Registration and Discovery Service.
4: The ITS Object shall make network address information available to onboard applications.
5: The ITS Object shall provide its configuration and operational status information to the Service Monitor
6: The ITS Object shall acquire regulatory information relevant to the operation of the ITS Object from the CCMS.

City of Orlando TMC - ITS Security Support

1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
10: The ITS Object shall maintain cryptographic secret information so that those secrets are accessible only to ITS Security Support, and not to any other Functional Object.
11: The ITS Object shall request pseudonymous credentials from the CCMS.
12: The ITS Object shall provide messages (that it receives) that indicate potential misbehavior/malfunction to the CCMS.
13: The ITS Object shall request permissions from the Center that manages permissions requests.
2: The ITS Object shall request enrollment credentials from the CCMS.
3: The ITS Object shall obtain the CCMS' trust credentials.
4: The ITS Object shall provide a mechanism for on-board applications to digitally sign messages using keys secured by the CCMS' trust authority.
5: The ITS Object shall provide a mechanism for on-board applications to authenticate messages secured by the CCMS' trust authority.
6: The ITS Object shall provide a mechanism for on-board applications to encrypt messages using keys secured by the CCMS' trust authority.
7: The ITS Object shall provide a mechanism for on-board applications to decrypt messages using keys secured by the CCMS' trust authority.
8: The ITS Object shall obtain a list of revoked credentials from the CCMS.
9: The ITS Object shall make the list of revoked credentials available to on-board applications.

City of Orlando TMC - TMC Basic Surveillance

1: The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements under remote control of the center.
2: The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.
7: The center shall remotely control devices to detect traffic.

City of Orlando TMC - TMC Passive Surveillance

1: The center shall collect time stamped vehicle identities from field equipment.
2: The center shall correlate the time stamped vehicle identities in order to calculate link travel times and derive other traffic measures.

City of Orlando TMC - TMC Roadway Equipment Monitoring

1: The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) operational status.
2: The center shall collect and store CCTV surveillance system (traffic, pedestrian) operational status.
4: The center shall collect and store CCTV surveillance system (traffic, pedestrian) fault data send to the maintenance center for repair.

City of Orlando TMC - TMC Signal Control

1: The center shall remotely control traffic signal controllers.
10: The center shall adjust signal timing in response to a signal prioritization, signal preemption, pedestrian call, multi-modal crossing activation, or other requests for right-of-way.
14: The center shall support requests from emergency management centers to provide responding emergency vehicles with signal preemption.
3: The center shall collect traffic signal controller operational status and compare against the control information sent by the center.
4: The center shall collect traffic signal controller fault data from the field.
6: The center shall implement control plans to coordinate signalized intersections based on data from sensors.

City of Orlando TMC - TMC Traffic Information Dissemination

1: The center shall remotely control dynamic messages signs for dissemination of traffic and other information to drivers.
19: The center shall collect general parking information and status, including current parking availability, parking pricing, and parking space availability information.
3: The center shall collect operational status for the driver information systems equipment (DMS, HAR, etc.).

FDOT SCMS - CCMS Authorization

1: The Center shall generate credential identifiers using facilities that are independently owned and operated from one another.

FDOT SCMS - CCMS Misbehavior Reporting and Action

1: The Center shall accept misbehavior reports from ITS Objects.

FDOT SCMS - CCMS Provisioning

1: The Center shall provide security and regulatory policy information to ITS Objects.

FDOT SCMS - CCMS Revocation

1: The Center shall place certificates on the revocation list of those certificates that are associated with misbehavior.

FDOT SCMS - ITS Security Support

1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).

LYNX Transit Vehicles - Transit Vehicle Signal Priority

1: The transit vehicle shall determine the schedule deviation and estimated times of arrival (ETA) at transit stops.
2: The transit vehicle shall send priority requests to traffic signal controllers at intersections, pedestrian crossings, and multimodal crossings on the roads (surface streets) and freeway (ramp controls) network that enable a transit vehicle schedule deviation to be corrected.

LYNX Transit Vehicles - Vehicle Basic Safety Communication

2: The vehicle shall provide its location with lane-level accuracy to on-board applications.

LYNX Transit Vehicles - Vehicle Control Automation

1: The vehicle shall monitor the area behind and in front of the vehicle to determine the proximity of other objects to the vehicle.

LYNX Transit Vehicles - Vehicle Intersection Warning

1: Vehicle shall provide vehicle path information to identify if vehicle is performing an unpermitted movement at an intersection such as a stop sign violation or running a red light.

Private Travelers Personal Computing Devices - ITS Management Support

6: The ITS Object shall acquire regulatory information relevant to the operation of the ITS Object from the CCMS.

Private Travelers Personal Computing Devices - ITS Security Support

1: The ITS Object shall obtain security policy information from the Cooperative Intelligent Transportation System Credentials Management System (CCMS).
2: The ITS Object shall request enrollment credentials from the CCMS.
3: The ITS Object shall obtain the CCMS' trust credentials.

Private Travelers Personal Computing Devices - Personal Pedestrian Safety

1: The personal information device shall provide the current location (latitude, longitude, and elevation) of the non-motorized travelers.
5: The personal traveler interface shall provide the traveler with warnings about approaching vehicles.

Vehicle - Vehicle Basic Safety Communication

2: The vehicle shall provide its location with lane-level accuracy to on-board applications.

Vehicle - Vehicle Control Automation

1: The vehicle shall monitor the area behind and in front of the vehicle to determine the proximity of other objects to the vehicle.

Vehicle - Vehicle Intersection Warning

1: Vehicle shall provide vehicle path information to identify if vehicle is performing an unpermitted movement at an intersection such as a stop sign violation or running a red light.

Vehicle - Vehicle Location Determination

1: The vehicle shall provide the vehicle's current location to other in-vehicle functions.
2: The vehicle shall calculate the location from one or more data sources including positioning systems such as GPS, sensors that track vehicle movement, and maps used to determine the likely vehicle route.

Vehicle - Vehicle Map Management

1: The Vehicle shall make basemap, roadway geometry, intersection geometry and parking facility geometry information available to other onboard vehicle applications.

Vehicle - Vehicle Situation Data Monitoring

1: The Vehicle shall obtain data collection parameters from Connected Vehicle Roadside Equipment.

Standards:

Project Operational Concepts:

Roles and Responsibilities

Travelers

Load intersection safety application on mobile device.

FDOT CO

Provide CAV secure infrastructure for vehicle safety.
Provide connected vehicle security, map and monitoring services.

LYNX

Communicate with the FDOT SCMS regarding CAV security.
Provide transit signal priority services.

City of Orlando

Collect vehicle probe data using roadside equipment, and calculate travel times.
Obtain traffic images and traffic flow data from CCTVs and field sensors, and maintain operational control of its own field equipment.
Operate traffic signal systems, including CCTVs, signals, and sensors, for the City of Orlando.
Provide emergency signal preemption for county and local fire/EMS agencies.
Provide traffic information to travelers using City of Orlando DMS devices.
Provide transit signal priority for regional transit providers using roadside devices.

Last Updated 2/5/2025