Gainesville Signal Phase and Timing (SPaT) Trapezium

Project Description: This project deployed connected vehicle (CV) technologies and applications along four roads forming a trapezium surrounding the University of Florida main campus. The routes are SR 121 (SW 34th St), SR 26 (W University Ave), US 441 (SW 13th St), and SR 24 (SW Archer Rd). The goal of the project is to improve travel time reliability, safety, throughput, and traveler information. This project also deployed and tested pedestrian and bicyclist safety CV and smartphone–based applications. The project covers 27 traffic signals equipped with 27 Roadside Units.

Project Status: Existing

Project Stakeholders:

Project Inventory:

Interconnect and Flow

Diagrams

Project Service Packages:

Project Information Flows:

Information Flow	Source Element	Destination Element	Status
conflict monitor status	City of Gainesville Field Equipment	City of Gainesville CAV Roadside Equipment	Existing
device enrollment information	City of Gainesville CAV Roadside Equipment	FDOT SCMS	Planned
device enrollment information	Private Travelers Personal Computing Devices	FDOT SCMS	Planned
device enrollment information	Vehicles	FDOT SCMS	Planned
enrollment credentials	FDOT SCMS	City of Gainesville CAV Roadside Equipment	Planned
enrollment credentials	FDOT SCMS	Private Travelers Personal Computing Devices	Planned
enrollment credentials	FDOT SCMS	Vehicles	Planned
intersection control status	City of Gainesville Field Equipment	City of Gainesville CAV Roadside Equipment	Existing
intersection geometry	CAV-ITS Map Update System	City of Gainesville CAV Roadside Equipment	Planned
intersection geometry	CAV-ITS Map Update System	Gainesville Smart Traffic TMC	Planned
intersection geometry	CAV-ITS Map Update System	Vehicles	Planned
intersection geometry	City of Gainesville CAV Roadside Equipment	Private Travelers Personal Computing Devices	Planned
intersection geometry	City of Gainesville CAV Roadside Equipment	Vehicles	Existing
intersection infringement info	City of Gainesville CAV Roadside Equipment	City of Gainesville Field Equipment	Existing
intersection infringement info	Vehicles	City of Gainesville CAV Roadside Equipment	Existing
intersection safety application info	Gainesville Smart Traffic TMC	City of Gainesville CAV Roadside Equipment	Existing
intersection safety application status	City of Gainesville CAV Roadside Equipment	Gainesville Smart Traffic TMC	Existing
intersection safety warning	City of Gainesville CAV Roadside Equipment	Vehicles	Existing
intersection status	City of Gainesville CAV Roadside Equipment	Private Travelers Personal Computing Devices	Planned
intersection status	City of Gainesville CAV Roadside Equipment	Vehicles	Existing
intersection status monitoring	City of Gainesville CAV Roadside Equipment	City of Gainesville Field Equipment	Existing
map update notification	Gainesville Smart Traffic TMC	CAV-ITS Map Update System	Planned
map updates	CAV-ITS Map Update System	City of Gainesville CAV Roadside Equipment	Planned
map updates	CAV-ITS Map Update System	Gainesville Smart Traffic TMC	Planned
map updates	CAV-ITS Map Update System	Vehicles	Planned
map updates	City of Gainesville CAV Roadside Equipment	Vehicles	Planned
misbehavior report	Private Travelers Personal Computing Devices	FDOT SCMS	Planned
misbehavior report	Vehicles	FDOT SCMS	Planned
mixed use crossing status	City of Gainesville Field Equipment	City of Gainesville CAV Roadside Equipment	Existing
mixed use safety warning control	Gainesville Smart Traffic TMC	City of Gainesville Field Equipment	Existing
mixed use safety warning status	City of Gainesville Field Equipment	Gainesville Smart Traffic TMC	Existing
personal crossing safety information	City of Gainesville CAV Roadside Equipment	Private Travelers Personal Computing Devices	Planned
personal location	Private Travelers Personal Computing Devices	City of Gainesville CAV Roadside Equipment	Planned
personal location	Private Travelers Personal Computing Devices	Vehicles	Planned
personal location information	City of Gainesville CAV Roadside Equipment	City of Gainesville Field Equipment	Existing
personal signal service request	Private Travelers Personal Computing Devices	City of Gainesville CAV Roadside Equipment	Planned
proxied personal location	City of Gainesville CAV Roadside Equipment	Vehicles	Existing
roadway geometry	CAV-ITS Map Update System	City of Gainesville CAV Roadside Equipment	Planned
roadway geometry	CAV-ITS Map Update System	Vehicles	Planned
roadway geometry	City of Gainesville CAV Roadside Equipment	Vehicles	Planned
security credential revocations	FDOT SCMS	Private Travelers Personal Computing Devices	Planned
security credential revocations	FDOT SCMS	Vehicles	Planned
security credentials	FDOT SCMS	Private Travelers Personal Computing Devices	Planned
security credentials	FDOT SCMS	Vehicles	Planned
security policy and networking information	FDOT SCMS	City of Gainesville CAV Roadside Equipment	Planned
security policy and networking information	FDOT SCMS	Private Travelers Personal Computing Devices	Planned
security policy and networking information	FDOT SCMS	Vehicles	Planned
signal control commands	Gainesville Smart Traffic TMC	City of Gainesville Field Equipment	Existing
signal control device configuration	Gainesville Smart Traffic TMC	City of Gainesville Field Equipment	Existing
signal control plans	Gainesville Smart Traffic TMC	City of Gainesville Field Equipment	Existing
signal control status	City of Gainesville Field Equipment	Gainesville Smart Traffic TMC	Existing
signal fault data	City of Gainesville Field Equipment	Gainesville Smart Traffic TMC	Existing
signal service request	City of Gainesville CAV Roadside Equipment	City of Gainesville Field Equipment	Existing
signal system configuration	Gainesville Smart Traffic TMC	City of Gainesville Field Equipment	Existing
traffic detector control	Gainesville Smart Traffic TMC	City of Gainesville Field Equipment	Existing
traffic detector data	City of Gainesville Field Equipment	Gainesville Smart Traffic TMC	Existing
traffic situation data	City of Gainesville CAV Roadside Equipment	City of Gainesville Field Equipment	Existing
traffic situation data	City of Gainesville CAV Roadside Equipment	Gainesville Smart Traffic TMC	Existing
vehicle location and motion	Vehicles	City of Gainesville CAV Roadside Equipment	Existing
vehicle location and motion	Vehicles	Private Travelers Personal Computing Devices	Planned
vehicle location and motion for mapping	Vehicles	CAV-ITS Map Update System	Planned
vehicle location and motion for surveillance	Vehicles	City of Gainesville CAV Roadside Equipment	Existing
vehicle location data for mapping	City of Gainesville CAV Roadside Equipment	CAV-ITS Map Update System	Planned
vehicle situation data	Vehicles	City of Gainesville CAV Roadside Equipment	Existing
vehicle situation data parameters	City of Gainesville CAV Roadside Equipment	Vehicles	Existing

Project Functional Requirements (Element - Functional Object):

CAV-ITS Map Update System - Map Management

2: The Center shall collect updates to roadway geometry from other Centers.
3: The Center shall collect road infrastructure restriction information from other Centers.
4: The Center shall collect updates to intersection geometry from other Centers.
7: The Center shall collect vehicle location information from the Connected Vehicle Roadside Equipment.
8: The Center shall coordinate the contents of map data for distribution with other Centers.
13: The Center shall provide intersection geometry updates to other Centers.
18: The Center shall provide intersection geometry updates to Connected Vehicle Roadside Equipment.
19: The Center shall provide roadway geometry updates to Connected Vehicle Roadside Equipment.
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.
25: The Center shall provide roadway geometry updates to Vehicles.
27: The Center shall provide basemap updates to Connected Vehicle Roadside Equipment.

City of Gainesville CAV Roadside Equipment - 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.

City of Gainesville CAV Roadside 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.
3: The field element shall send the infrastructure application status to the operations center.
4: The field element shall receive signal prioity requests from commercial vehicles and forward to the traffic signal controller.
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.
7: The field element shall determine when special vehicles requesting preemption or priority at a signal are authorized to do so based on their digital credentials.
8: The field element shall send a signal service request to the traffic signal controller when its application status determines the need for a signal change.
9: The field element shall collect current signal phase and timing data from the traffic signal controller.

City of Gainesville CAV Roadside Equipment - RSE Intersection Safety

1: The roadway equipment shall collect the current location (latitude, longitude, and elevation) from personal information devices.
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.
7: The field element shall collect current conflict monitor and intersection control data from the traffic signal controller.

City of Gainesville CAV Roadside Equipment - RSE Map Management

3: The field element shall provide roadway geometry update 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.
9: The field element shall provide basemap updates to proximate Vehicles.
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.

City of Gainesville Field Equipment - Roadway Signal Control

1: The field element shall control traffic signals under center control.
4: The field element shall report the current signal control information to the center.
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.
9: The field element shall report current intersection signal timing information to roadside equipment for transmission to connected vehicles.
10: The field element shall receive request for transit vehicle signal priority.
12: The field element shall report current commercial vehicle priority status to the center.
13: 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.
14: The field element shall provide data to the Connected Vehicle Roadside Equipment.
15: The field element shall receive requests for emergency vehicle signal preemption.

FDOT SCMS - CCMS Authorization

1: The Center shall generate credential identifiers using facilities that are independently owned and operated from one another.
2: The Center shall assign two or more non-unique identifiers, that when combined are unique, to each credential it distributes.
3: The Center shall verify information received in pseudonym requests.
4: The Center shall coordinate the distribution of credentials with other Centers.
5: The Center shall store credential identifiers using facilities that are independently owned and operated from one another.
6: The Center shall provide Vehicle pseudonymous credentials in response to valid Vehicle pseudonym requests.
7: The Center shall provide Personal Device pseudonymous credentials in response to valid Personal Device pseudonym requests.
8: The Center shall provide Center pseudonymous credentials in response to valid Center pseudonym requests.
9: The Center shall provide Connected Vehicle Roadside Equipment pseudonymous credentials in response to valid Connected Vehicle Roadside Equipment pseudonym requests.
10: The Center shall accept user permission information from Centers authorized to provide that information.
11: The Center shall acquire identifiers relevant to ITS services from the relevant registry of such identifiers

FDOT SCMS - CCMS Enrollment

1: The Center shall provide enrollment credentials in response to valid enrollment requests.
2: The Center shall coordinate the distribution of enrollment credentials with other Centers.
3: The Center shall verify information received in enrollment requests.

FDOT SCMS - CCMS Misbehavior Reporting and Action

1: The Center shall accept misbehavior reports from ITS Objects.
2: The Center shall analyze misbehavior reports.
3: The Center shall coordinate misbehavior analysis with other Centers.

FDOT SCMS - CCMS Provisioning

1: The Center shall provide security and regulatory policy information to ITS Objects.
2: The Center shall provide its credentials information to ITS Objects.
3: The Center shall provide the operator with mechanisms for monitoring the status of all credential-granting activities without compromising any other requirement.

FDOT SCMS - CCMS Revocation

1: The Center shall place certificates on the revocation list of those certificates that are associated with misbehavior.
2: The Center shall provide to ITS Objects a list of credentials whose trust as been revoked.

Gainesville Smart Traffic TMC - TMC Intersection Safety

1: The center shall provide current intersection safety status information.
5: The field element shall be capable of configuring roadside equipment to perform the collection and transmission of information to support intersection safety.

Gainesville Smart Traffic TMC - TMC Signal Control

1: The center shall remotely control traffic signal controllers.
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.
9: The center shall implement control plans to coordinate signalized intersections based on data from sensors and connected vehicles.
10: The center shall adjust signal timing in respond to a signal prioritization, signal preemption, pedestrian call, multi-modal crossing activation, or other requests for right-of-way.

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.
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.
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.

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.

Vehicles - 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.
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.
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.

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.
2: The vehicle shall monitor the area to the sides of the vehicle to determine the proximity of other objects to the vehicle to determine if a control adjustment is needed.
5: The Vehicle shall provide its location with lane-level accuracy to on-board control automation applications.
10: The vehicle shall present vehicle control information to the driver in audible or visual forms without impairing the driver's ability to control the vehicle in a safe manner.

Vehicles - Vehicle Control Warning

1: The vehicle shall monitor the area to the sides of the vehicle to determine the proximity of other objects to the vehicle and if a warning is needed.
4: The vehicle shall present vehicle control warnings information to the driver in audible or visual forms without impairing the driver's ability to control the vehicle in a safe manner.
10: The Vehicle shall provide its location with lane-level accuracy to on-board warning applications.

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.
2: Vehicle shall provide data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size.
3: The vehicle shall receive intersection signal timing information in order for the vehicle to determine if it will safely cross the intersection given its current location and speed.
6: The vehicle shall provide to the driver a warning if it looks like the vehicle will go through the intersection after the signal has turned red.

Vehicles - Vehicle Map Management

3: The Vehicle shall obtain roadway geometry update information from proximate Connected Vehicle Roadside Equipment.
4: The Vehicle shall obtain intersection geometry update information from proximate Connected Vehicle Roadside Equipment.
7: The Vehicle shall obtain basemap update information from proximate Connected Vehicle Roadside Equipment.
10: The Vehicle shall obtain intersection geometry information from Centers.

Standards:

Project Operational Concepts:

Roles and Responsibilities

Travelers

Load and operate project application on mobile device.

FDOT CO

Enables trusted communications between mobile devices and other mobile devices, roadside devices, and centers and protect data they handle from unauthorized access.
Supports connected and autonomous vehicle operations.
The SCMS provides secure certificates to users within the CAV environment.

Gainesville Traffic Operations Division

Operate and maintain connected vehicle equipment along roadway to provide signal information to vehicles.

University of Florida

Collect information from the system for project evaluation.
Conduct project evaluation.

Last Updated 5/6/2024