I-75 Floridas Regional Advanced Mobility Elements (FRAME)

Project Description: This project deployed emerging technologies to better manage, operate, and maintain the multi–modal transportation system and create an Integrated Corridor Management solution on I–75 and state highway systems in the Cities of Gainesville and Ocala. The emerging technologies used in this project are Automated Traffic Signal Performance Measures and Connected Vehicle technologies such as Roadside Units and On Board Units for effective traffic operations; Transit Signal Priority and Freight Signal Priority. The goal of the project is to disseminate real–time information to the motorists during freeway incidents.
Project limit: I–75 and US 441/US 301 from Wildwood to Alachua

Project Status: Existing

Project Stakeholders:

• County Public Safety Agencies
• FDOT CO
• FDOT District 2
• Gainesville Regional Transit System
• Gainesville Traffic Operations Division
• Private Commercial Vehicle and Fleet Operators
• Travelers

Project Service Packages:

• VS13: Intersection Safety Warning and Collision Avoidance (City of Gainesville)
• PT09: Transit Signal Priority (Gainesville CV Priority)
• TM02: Vehicle-Based Traffic Surveillance (FDOT District 2 Traffic Management Center)
• DM02: Performance Monitoring (Gainesville ATSPM)
• PS03: Emergency Vehicle Preemption (Gainesville CV Preemption)
• CVO06: Freight Signal Priority (Gainesville CV Priority)
• SU08: Security and Credentials Management (I-75 FRAME)
• SU09: Device Certification and Enrollment (I-75 FRAME)

Project Information Flows:

Information Flow	Source Element	Destination Element	Status
archive analysis requests	Gainesville Smart Traffic TMC	City of Gainesville ATSPM System	Existing
archive analysis results	City of Gainesville ATSPM System	Gainesville Smart Traffic TMC	Existing
archive request confirmation	City of Gainesville ATSPM System	Gainesville Smart Traffic TMC	Existing
archive status	City of Gainesville ATSPM System	Gainesville Smart Traffic TMC	Existing
archived data product requests	Gainesville Smart Traffic TMC	City of Gainesville ATSPM System	Existing
archived data products	City of Gainesville ATSPM System	Gainesville Smart Traffic TMC	Existing
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	Commercial Vehicle	FDOT SCMS	Planned
device enrollment information	County Fire EMS/Rescue Vehicles	FDOT SCMS	Planned
device enrollment information	FDOT District 2 CAV Field Equipment	FDOT SCMS	Planned
device enrollment information	Gainesville Regional Transit Vehicles	FDOT SCMS	Planned
device enrollment information	Vehicles	FDOT SCMS	Planned
emergency traffic control information	Gainesville Smart Traffic TMC	County Fire EMS/Rescue Dispatch	Existing
emergency traffic control request	County Fire EMS/Rescue Dispatch	Gainesville Smart Traffic TMC	Existing
emergency vehicle tracking data	County Fire EMS/Rescue Vehicles	County Fire EMS/Rescue Dispatch	Existing
enrollment credentials	FDOT SCMS	City of Gainesville CAV Roadside Equipment	Planned
enrollment credentials	FDOT SCMS	Commercial Vehicle	Planned
enrollment credentials	FDOT SCMS	County Fire EMS/Rescue Vehicles	Planned
enrollment credentials	FDOT SCMS	FDOT District 2 CAV Field Equipment	Planned
enrollment credentials	FDOT SCMS	Gainesville Regional Transit Vehicles	Planned
enrollment credentials	FDOT SCMS	Vehicles	Planned
intersection control status	City of Gainesville Field Equipment	City of Gainesville CAV Roadside Equipment	Planned
intersection geometry	City of Gainesville CAV Roadside Equipment	Commercial Vehicle	Planned
intersection geometry	City of Gainesville CAV Roadside Equipment	County Fire EMS/Rescue Vehicles	Existing
intersection geometry	City of Gainesville CAV Roadside Equipment	Gainesville Regional Transit Vehicles	Existing
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 management application info	Gainesville Smart Traffic TMC	City of Gainesville CAV Roadside Equipment	Planned
intersection management application status	City of Gainesville CAV Roadside Equipment	Gainesville Smart Traffic TMC	Planned
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	Commercial Vehicle	Planned
intersection status	City of Gainesville CAV Roadside Equipment	County Fire EMS/Rescue Vehicles	Existing
intersection status	City of Gainesville CAV Roadside Equipment	Gainesville Regional Transit Vehicles	Existing
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
local signal preemption request	County Fire EMS/Rescue Vehicles	City of Gainesville CAV Roadside Equipment	Existing
local signal priority request	Commercial Vehicle	City of Gainesville CAV Roadside Equipment	Planned
local signal priority request	Gainesville Regional Transit Vehicles	City of Gainesville CAV Roadside Equipment	Existing
misbehavior report	Commercial Vehicle	FDOT SCMS	Planned
misbehavior report	County Fire EMS/Rescue Vehicles	FDOT SCMS	Planned
misbehavior report	Gainesville Regional Transit Vehicles	FDOT SCMS	Planned
misbehavior report	Vehicles	FDOT SCMS	Planned
right-of-way request notification	City of Gainesville Field Equipment	Gainesville Smart Traffic TMC	Planned
road network conditions	FDOT District 2 RTMC	Florida 511	Existing
road network traffic situation data	Florida 511	FDOT District 2 RTMC	Existing
security credential revocations	FDOT SCMS	Commercial Vehicle	Planned
security credential revocations	FDOT SCMS	County Fire EMS/Rescue Vehicles	Planned
security credential revocations	FDOT SCMS	Gainesville Regional Transit Vehicles	Planned
security credential revocations	FDOT SCMS	Vehicles	Planned
security credentials	FDOT SCMS	Commercial Vehicle	Planned
security credentials	FDOT SCMS	County Fire EMS/Rescue Vehicles	Planned
security credentials	FDOT SCMS	Gainesville Regional Transit Vehicles	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	Commercial Vehicle	Planned
security policy and networking information	FDOT SCMS	County Fire EMS/Rescue Vehicles	Planned
security policy and networking information	FDOT SCMS	FDOT District 2 CAV Field Equipment	Planned
security policy and networking information	FDOT SCMS	Gainesville Regional Transit Vehicles	Planned
security policy and networking information	FDOT SCMS	Vehicles	Planned
signal control commands	Gainesville Smart Traffic TMC	City of Gainesville Field Equipment	Planned
signal control status	City of Gainesville Field Equipment	Gainesville Smart Traffic TMC	Planned
signal preemption request	City of Gainesville CAV Roadside Equipment	City of Gainesville Field Equipment	Existing
signal priority service request	City of Gainesville CAV Roadside Equipment	City of Gainesville Field Equipment	Planned
signal priority status	City of Gainesville CAV Roadside Equipment	Commercial Vehicle	Planned
signal priority status	City of Gainesville CAV Roadside Equipment	County Fire EMS/Rescue Vehicles	Existing
signal priority status	City of Gainesville CAV Roadside Equipment	Gainesville Regional Transit Vehicles	Existing
situation data collection parameters	FDOT District 2 RTMC	FDOT District 2 CAV Field Equipment	Existing
suggested route	County Fire EMS/Rescue Dispatch	County Fire EMS/Rescue Vehicles	Existing
traffic control priority request	City of Gainesville Regional Transit System	Gainesville Smart Traffic TMC	Existing
traffic control priority status	Gainesville Smart Traffic TMC	City of Gainesville Regional Transit System	Existing
traffic monitoring application info	FDOT District 2 RTMC	FDOT District 2 CAV Field Equipment	Existing
traffic monitoring application status	FDOT District 2 CAV Field Equipment	FDOT District 2 RTMC	Existing
traffic situation data	FDOT District 2 CAV Field Equipment	FDOT District 2 RTMC	Existing
traffic situation data	FDOT District 2 CAV Field Equipment	Florida 511	Existing
transit schedule information	City of Gainesville Regional Transit System	Gainesville Regional Transit Vehicles	Existing
transit vehicle schedule performance	Gainesville Regional Transit Vehicles	City of Gainesville Regional Transit System	Existing
vehicle location and motion	Commercial Vehicle	City of Gainesville CAV Roadside Equipment	Planned
vehicle location and motion	County Fire EMS/Rescue Vehicles	City of Gainesville CAV Roadside Equipment	Existing
vehicle location and motion	Gainesville Regional Transit Vehicles	City of Gainesville CAV Roadside Equipment	Existing
vehicle location and motion	Vehicles	City of Gainesville CAV Roadside Equipment	Existing
vehicle location and motion for surveillance	Vehicles	FDOT District 2 CAV Field Equipment	Existing
vehicle situation data	Vehicles	FDOT District 2 CAV Field Equipment	Existing
vehicle situation data	Vehicles	FDOT District 2 RTMC	Existing
vehicle situation data	Vehicles	Florida 511	Existing
vehicle situation data parameters	FDOT District 2 CAV Field Equipment	Vehicles	Existing
vehicle situation data parameters	FDOT District 2 RTMC	Vehicles	Existing
vehicle situation data parameters	Florida 511	Vehicles	Existing

Project Functional Requirements (Element - Functional Object):

• City of Gainesville ATSPM System - Archive On-Line Analysis and Mining
• 1: The center shall respond to requests for archive data from center users.
• 2: The center shall provide the capability to perform activities such as data mining, data fusion, summarizations, aggregations, and recreation from archive data. This may include multidimensional analysis, selective summarization and expansion of data details, and many other advanced analysis services.


• City of Gainesville ATSPM System - Archive Situation Data Archival
• 1: The center shall collect data from roadside devices.
• 2: The center shall respond to requests from the administrator interface function to manage field-sourced data collection.
• 3: The center shall provide the capability to adjust the collection of field-sourced data based on the statistical measures.
• 6: The center shall provide the capability to execute methods on the incoming field data such as aggregation and statistical measures before the data is stored in the archive.
• 7: The center shall respond to requests from the administrator interface function to select and manage data stored in the archive.


• 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 send the request for commercial vehicle priority to a traffic signal controller that results in priority 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.
• 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.
• 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.
• 7: The field element shall collect current conflict monitor and intersection control data from the traffic signal controller.


• City of Gainesville Field Equipment - Roadway Signal Control
• 1: The field element shall control traffic signals under center control.
• 2: The field element shall respond to pedestrian crossing requests by accommodating the pedestrian crossing.
• 3: The field element shall provide the capability to notify the traffic management center of pedestrian calls and pedestrian accommodations.
• 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.
• 11: The field element shall receive request for commercial 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.


• City of Gainesville Field Equipment - Roadway Signal Preemption
• 1: The field element shall respond to signal preemption requests from emergency vehicles.
• 2: The field element shall inform the controlling center when preemption requests have been received.


• City of Gainesville Regional Transit System - Transit Center Priority Management
• 3: The center shall define business rules that govern use of transit vehicle signal priority, communicate these rules to the transit vehicle, and monitor transit vehicle requests for priority at signalized intersections.
• 4: The center shall provide transit operations personnel with the capability to control and monitor transit signal priority operations.


• Commercial Vehicle - CV On-Board Signal Priority
• 1: The commercial vehicle shall request priority at a signalized intersection, including signals at the entrance to or exit from an intermodal shipping facility.
• 2: The commercial vehicle shall provide vehicle location and motion information to local connected vehicle equipment near signalized intersections.


• Commercial Vehicle - 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.


• County Fire EMS/Rescue Dispatch - Emergency Routing
• 1: The center shall collect current traffic and road condition information for emergency vehicle route calculation.
• 6: The center shall track current emergency vehicle location and status along with other emergency vehicle characteristics.
• 12: The center shall collect road and traffic conditions information, including current traffic conditions en route, current traffic conditions on-scene, and road weather conditions (e.g. wet, icy, snow-covered).
• 13: The center shall collect road and traffic conditions information from multiple sources including: traffic management centers, probe vehicle data, including traffic data and environmental conditions, and other private traffic data sources, e.g. private distributors that integrate connected (probe) vehicle data with cellular or surveillance device inputs.
• 14: The center shall provide routing instructions for a dispatched emergency vehicle that may reflect current network conditions and the additional routing options available to en route emergency that are not available to the general public.
• 15: The emergency center shall collect location and situational information about the emergency vehicles responding to or on the scene of an incident.


• County Fire EMS/Rescue Vehicles - EV On-Board En Route Support
• 5: The emergency vehicle shall send requests to traffic signal control equipment at the roadside to preempt the signal.


• County Fire EMS/Rescue 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.


• FDOT District 2 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).
• 2: The ITS Object shall request enrollment credentials from the CCMS.


• FDOT District 2 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.
• 3: The field element shall provide data collection parameters to vehicles.


• FDOT District 2 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.
• 2: The field element shall aggregate and forward collected probe information to the center.
• 3: The field element shall aggregate and forward collected probe information to other field elements.


• FDOT District 2 RTMC - TIC Situation Data Management
• 1: The center shall collect traffic probe data (speeds, travel times, etc.) from appropriately equipped vehicles and short range communications equipment.


• FDOT District 2 RTMC - TMC Situation Data Management
• 1: The center shall collect traffic probe data from vehicles via roadside field equipment.
• 5: The center shall collect operational status for the roadside probe data collection equipment.
• 6: The center shall collect fault data for the roadside probe data collection equipment for repair.


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


• FDOT SCMS - 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.


• Florida 511 - TIC Situation Data Management
• 5: The center shall aggregate collected traffic probe data, calculate route segment travel times, route segment speeds, route usage, and road weather information for dissemination to other centers.


• Gainesville Regional Transit 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.


• Gainesville Regional 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.
• 4: The transit vehicle shall prevent a priority request from being sent when the transit vehicle cannot use the priority (e.g., when the transit vehicle makes a passenger stop on the approach to an intersection).


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


• 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 Basic Safety Communication
• 2: The vehicle shall provide its location with lane-level accuracy to on-board applications.
• 3: The vehicle shall provide its location with road-level accuracy to on-board applications.
• 4: The vehicle shall collect road condition data from other vehicles.
• 6: The vehicle shall exchange location and motion information with roadside equipment and nearby vehicles.
• 7: The vehicle shall receive warnings, informational road signs, traffic meters, and signals provided by infrastructure devices.
• 13: The vehicle shall notify the driver when onboard components or safety applications are offline.


• Vehicles - Vehicle Control Warning
• 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.
• 6: The vehicle shall receive emergency vehicle location information.
• 7: The vehicle shall notify the Driver of the presence of emergency vehicles nearby that may affect the host vehicle.
• 8: The vehicle shall provide warnings to the driver based upon warnings received from nearby special vehicles.


• Vehicles - Vehicle Intersection Warning
• 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.
• 5: The vehicle shall receive warning from the infrastructure if an intersection violation appears to be imminent.
• 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 Situation Data Monitoring
• 1: The Vehicle shall obtain data collection parameters from Connected Vehicle Roadside Equipment.
• 4: The vehicle shall provide traffic-related data including snapshots of measured speed and heading and events including starts and stops, speed changes, and other vehicle control from vehicle.
• 5: The Vehicle shall provide data to Centers in accordance with data collection parameters provided by Centers/Connected Vehicle Roadside Equipment.
• 6: The Vehicle shall provide data to Connected Vehicle Roadside Equipment. in accordance with data collection parameters provided by Centers/Connected Vehicle Roadside Equipment.

Standards:

• (None-Data) - Secure Internet (ITS)
• US: ADMS - Secure Internet (ITS)
• US: Device enrollment - Secure Internet (ITS)
• US: GTFS real-time - Secure Wireless Internet (ITS)
• US: GTFS static - Secure Wireless Internet (ITS)
• US: Misbehavior reporting - Secure Internet (ITS)
• US: NTCIP Signal Priority - SNMPv3/TLS
• US: NTCIP Signal System Masters - SNMPv3/TLS
• US: NTCIP Traffic Signal - SNMPv3/TLS
• US: NTCIP Transportation Sensors - SNMPv3/TLS
• US: SAE Basic Safety Messages - WAVE WSMP
• US: SAE Other J2735 - Secure Wireless Internet (ITS)
• US: SAE Other J2735 - WAVE TCP
• US: SAE Other J2735 - WAVE WSMP
• US: SAE Signal Control Messages - WAVE WSMP
• US: SAE Signal Preemption - WAVE TCP
• US: Security Credentials - Secure Internet (ITS)
• US: TCIP - Secure Internet (ITS)
• US: TMDD - NTCIP Messaging

Project Operational Concepts:

Roles and Responsibilities

• Private Commercial Vehicle and Fleet Operators
• Install and maintain connected vehicle on-board equipment.


• FDOT CO
• Distribute traffic information to traveling public via 511 system.
• 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.


• County Public Safety Agencies
• Maintain traffic signal preemption equipment on public safety vehicles.


• FDOT District 2
• Distribute traffic information to other systems to distribute to the traveling public.
• Operate and maintain connected vehicle equipment along roadway to provide traffic surveillance.


• Gainesville Traffic Operations Division
• Operate and maintain CAV Field Equipment.
• Operate and maintain connected vehicle equipment along roadway to provide signal preemption to public safety vehicles.
• Operate and maintain connected vehicle equipment along roadway to provide signal priority to commerical vehicles.
• Operate and maintain connected vehicle equipment along roadway to provide signal priority to public transportation vehicles.
• Operate and maintain equipment at traffic signals to provide automated traffic signal performance measures.
• Operate and maintain system to process and analyze automated traffic signal performance measures.
• Use automated traffic signal performance measures to manage traffic on roadways in City of Gainesville.


• Gainesville Regional Transit System
• Maintain traffic signal priority equipment on public transportation vehicles.
• Operate and maintain connected vehicle on-board equipment.