Gainesville Bike and Pedestrian Safety Project

Project Description: Federal Accelerated Innovation Deployment (AID) program project to test and implement connected vehicle and pedestrian/bicyclist safety applications (active or passive) at 13 signalized intersections and 8 mid–block crossings within the core of the University of Florida (UF) campus. The goal of this project is to reduce pedestrian and bicycle crashes and conflicts with vehicles and transit. The routes are SR 26 (University Avenue), US 441 (SW 13th Street), Museum Road, and Gale Lemerand Drive. The project will install roadside units (RSUs), passive pedestrian detection systems, on–board units, and rectangular rapid flashing beacons.

The following will be tested during this project:
– Passive pedestrian/bicyclist detection at all locations via detection technologies.
– Real–time notification to transit, motorists, and pedestrians/bicyclists.
– Signal phase and timing data broadcasting with active pedestrian/bicyclist detection via RSUs.

Project Status: Planned

Project Stakeholders:

• FDOT CO
• Gainesville Traffic Operations Division
• Travelers

Project Service Packages:

• VS12: Vulnerable Road User Safety (City of Gainesville)
• SU08: Security and Credentials Management (Gainesville Bike and Pedestrian Safety)
• SU09: Device Certification and Enrollment (Gainesville Bike and Pedestrian Safety)

Project Information Flows:

Information Flow	Source Element	Destination Element	Status
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	Planned
intersection geometry	City of Gainesville CAV Roadside Equipment	Private Travelers Personal Computing Devices	Planned
intersection geometry	City of Gainesville CAV Roadside Equipment	Vehicles	Planned
intersection infringement info	Vehicles	City of Gainesville CAV Roadside Equipment	Planned
intersection safety application info	Gainesville Smart Traffic TMC	City of Gainesville CAV Roadside Equipment	Planned
intersection safety application status	City of Gainesville CAV Roadside Equipment	Gainesville Smart Traffic TMC	Planned
intersection safety warning	City of Gainesville CAV Roadside Equipment	Vehicles	Planned
intersection status	City of Gainesville CAV Roadside Equipment	Private Travelers Personal Computing Devices	Planned
intersection status	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	Planned
mixed use safety warning control	Gainesville Smart Traffic TMC	City of Gainesville Field Equipment	Planned
mixed use safety warning status	City of Gainesville Field Equipment	Gainesville Smart Traffic TMC	Planned
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	Planned
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	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 service request	City of Gainesville CAV Roadside Equipment	City of Gainesville Field Equipment	Planned
vehicle location and motion	Vehicles	City of Gainesville CAV Roadside Equipment	Planned
vehicle location and motion	Vehicles	Private Travelers Personal Computing Devices	Planned

Project Functional Requirements (Element - Functional Object):

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


• 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.
• 3: The roadway equipment shall collect vehicle path information sent by a vehicle.
• 4: The roadway equipment shall provide current crossing status including permission to cross, crossing time remaining.
• 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 Field Equipment - Roadway Mixed Use Crossing Safety
• 1: The field element shall collect images or sensor data for pedestrians or bicyclists and respond to pedestrian or bicyclist crossing requests via display, audio signal, or other manner.
• 2: The field element shall respond to pedestrian or bicyclist crossing requests via display, audio signal, or other manner.
• 3: The field element shall inform pedestrians and bicyclists of the status of the intersection including the amount of time left for crossing the intersection.


• 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
• 2: The center shall provide warnings to drivers when non-motorized users are occupying a cross walk or other mixed use path crossing.
• 3: The center shall provide warnings to pedestrians or bicyclists when vehicles are infringing on a cross walk or other mixed use path crossing.
• 5: The field element shall be capable of configuring roadside equipment to perform the collection and transmission of information to support intersection safety.


• 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.
• 3: The personal traveler interface shall provide traveler location information to transit vehicles.
• 4: The personal traveler interface shall provide to a transit vehicle the traveler's intent to board the transit vehicle including the transit stop at which the traveler would like to board.
• 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.
• 3: The vehicle shall evaluate the likelihood of a collision between two vehicles or a vehicle and a stationary object, based on the proximity of other objects to the vehicle and the current speed and direction of the vehicle.
• 6: The vehicle shall evaluate the likelihood of a collision between two vehicles or a vehicle and a stationary object, based on the proximity of other objects to the vehicle, roadway characteristics, and the current speed and direction of the vehicle.
• 7: The vehicle shall provide position control adjustments and warnings to the driver when an object gets close enough to the vehicle to become a hazard if no action is taken by the driver.
• 8: The vehicle shall provide an interface through which a vehicle driver can initiate, monitor and terminate automatic control of the vehicle.
• 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 Intersection Warning
• 2: Vehicle shall provide data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size.
• 4: The vehicle shall be capable of providing warnings to the driver based upon information received regarding pedestrians, cyclists, and other non-motorized users that are sharing the roadway with the vehicle.

Standards:

• (None-Data) - Secure Internet (ITS)
• (None-Data) - WAVE WSMP
• US: Device enrollment - Secure Internet (ITS)
• US: Misbehavior reporting - Secure Internet (ITS)
• US: NTCIP Signal Priority - SNMPv3/TLS
• US: NTCIP Traffic Signal - SNMPv3/TLS
• US: SAE Basic Safety Messages - WAVE WSMP
• US: SAE Other J2735 - Local Unicast Wireless (1609.2)
• US: SAE Other J2735 - WAVE WSMP
• US: SAE Signal Control Messages - WAVE WSMP
• US: SAE VRU Messages - WAVE WSMP
• US: Security Credentials - Secure Internet (ITS)

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 system to provide signal information to pedestrians and bicyclists.
• Operate connected vehicle equipment along roadway to provide alerts to vehicles and pedestrians


• University of Florida
• Collect information from the system for project evaluation.
• Conduct project evaluation.