City of Orlando Bicycle and Pedestrian Innovative ITS (International Drive)

Project Description: This project would deploy innovative pedestrian and bicycle collision avoidance system in the City of Orlando on International Drive from Oakridge Rd. to Central Florida Pkwy. Utilizing connected vehicle technologies, the pedestrian and bicycle collision avoidance system reduces the occurrence of vehicular collisions with pedestrians and bicycles at an intersection.

Project Status: Planned

Project Stakeholders:

• City of Orlando
• FDOT CO
• FDOT District 5
• LYNX
• Travelers

Project Service Packages:

• SU04: Map Management (City of Orlando Bicycle and Pedestrian Innovative ITS)
• SU08: Security and Credentials Management (City of Orlando Bicycle and Pedestrian Innovative ITS)
• TM04: Connected Vehicle Traffic Signal System (City of Orlando Bicycle and Pedestrian Innovative ITS)
• VS12: Vulnerable Road User Safety (City of Orlando Bicycle and Pedestrian Innovative ITS)

Project Information Flows:

Information Flow	Source Element	Destination Element	Status
archived data products	SunStore	City of Orlando TMC	Planned
intersection geometry	City of Orlando Field Equipment	LYNX Transit Vehicles	Planned
intersection geometry	City of Orlando Field Equipment	Private Travelers Personal Computing Devices	Planned
intersection status	City of Orlando Field Equipment	LYNX Transit Vehicles	Planned
intersection status	City of Orlando Field Equipment	Private Travelers Personal Computing Devices	Planned
local traveler information	City of Orlando Field Equipment	Private Travelers Personal Computing Devices	Planned
map updates	CAV-ITS Map Update System	City of Orlando Field Equipment	Planned
misbehavior report	LYNX Transit Vehicles	FDOT SCMS	Planned
misbehavior report	Private Travelers Personal Computing Devices	FDOT SCMS	Planned
personal crossing safety information	City of Orlando Field Equipment	Private Travelers Personal Computing Devices	Planned
personal location	Private Travelers Personal Computing Devices	City of Orlando Field Equipment	Planned
personal location	Private Travelers Personal Computing Devices	LYNX Transit Vehicles	Planned
personal signal service request	Private Travelers Personal Computing Devices	City of Orlando Field Equipment	Planned
security credential revocations	FDOT SCMS	LYNX Transit Vehicles	Planned
security credential revocations	FDOT SCMS	Private Travelers Personal Computing Devices	Planned
security credentials	FDOT SCMS	LYNX Transit Vehicles	Planned
security credentials	FDOT SCMS	Private Travelers Personal Computing Devices	Planned
security policy and networking information	FDOT SCMS	LYNX Transit Vehicles	Planned
security policy and networking information	FDOT SCMS	Private Travelers Personal Computing Devices	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 system configuration	City of Orlando TMC	City of Orlando Field Equipment	Planned
traffic archive data	City of Orlando TMC	SunStore	Planned
vehicle location and motion	LYNX Transit Vehicles	City of Orlando Field Equipment	Planned
vehicle location and motion	LYNX Transit Vehicles	Private Travelers Personal Computing Devices	Planned
vehicle location and motion	Vehicle	City of Orlando Field Equipment	Planned
vehicle signage data	City of Orlando Field Equipment	Vehicle	Planned

Project Functional Requirements (Element - Functional Object):

• CAV-ITS Map Update System - 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.


• CAV-ITS Map Update System - 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.
• 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.


• CAV-ITS Map Update System - Map Management
• 1: The Center shall collect Vehicle location information from Vehicles.
• 2: The Center shall collect updates to roadway geometry from other Centers.
• 4: The Center shall collect updates to intersection geometry from other Centers.
• 5: The Center shall provide basemap updates to other Centers.


• City of Orlando 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.
• 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.


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


• City of Orlando Field Equipment - Roadway Mixed Use Crossing Safety
• 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.


• City of Orlando Field Equipment - Roadway Signal Control
• 1: The field element shall control traffic signals under center control.
• 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.
• 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.
• 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.


• City of Orlando 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.
• 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 Orlando Field 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.
• 6: The roadway equipment shall send to connected vehicles a warning if an intersection violation appears to be imminent.


• City of Orlando Field Equipment - RSE Map Management
• 10: The field element shall provide intersection geometry updates to proximate Vehicles.
• 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.


• City of Orlando 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.
• 2: The field element shall provide vehicle situation data to a center for archival.
• 5: The field element shall provide collected vehicle situation and local sensor data to data distribution centers.


• City of Orlando 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 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 - 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.
• 5: The center shall respond to control data from center personnel regarding sensor and surveillance data collection, analysis, storage, and distribution.


• City of Orlando TMC - TMC Intersection Safety
• 1: The center shall provide current intersection safety status information.
• 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.
• 4: The field element shall be capable of providing intersection priority for pedestrians or bicyclists based upon requests from the pedestrians or bicyclists
• 5: The field element shall be capable of configuring roadside equipment to perform the collection and transmission of information to support intersection safety.


• City of Orlando TMC - TMC Roadway Equipment Monitoring
• 3: The center shall collect and store sensor (traffic, pedestrian, multimodal crossing) fault data and send to the maintenance center for repair.


• City of Orlando TMC - TMC Signal Control
• 1: The center shall remotely control traffic signal controllers.
• 2: The center shall accept notifications of pedestrian calls.
• 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.


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


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


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


• LYNX Transit Vehicles - 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.


• LYNX Transit Vehicles - Transit Vehicle Pedestrian Safety
• 1: The transit vehicle shall determine if pedestrians are near a transit vehicle.
• 2: The transit vehicle shall determine if pedestrians are at risk of crash due to proximity of transit vehicle.
• 3: The transit vehicle shall notify the Transit Vehicle Operator of pedestrians that are in a position that is likely to result in a collision with the transit vehicle.
• 4: The transit vehicle shall collect pedestrian presence information from equipped personal devices.


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


• Private Travelers Personal Computing Devices - Personal Map Management
• 1: The Personal Device shall obtain basemap updates from Centers.


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


• SunStore - Archive Data Repository
• 1: The center shall collect data from centers.
• 11: The center shall respond to requests for archive data from archive data users (centers, field devices).


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


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

• (None-Data) - Secure Internet (ITS)
• (None-Data) - Secure Wireless Internet (ITS)
• (None-Data) - WAVE WSMP
• US: ADMS - Secure Internet (ITS)
• US: Misbehavior reporting - Secure Internet (ITS)
• US: NTCIP Signal System Masters - 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 TCP
• US: SAE Other J2735 - WAVE WSMP
• US: SAE Signal Control Messages - WAVE WSMP
• US: SAE Traveler Info - WAVE WSMP
• US: SAE VRU Messages - WAVE WSMP
• US: Security Credentials - Secure Internet (ITS)

Project Operational Concepts:

Roles and Responsibilities

• Travelers
• Load intersection safety application on mobile device.


• FDOT CO
• Provide Authorization, SCMS and Map services to Cities and Counties in the FDOT District 5 region.
• Provide CAV secure infrastructure for vehicle safety.
• Provide CAV secure infrastructure.


• FDOT District 5
• Coordinate the archival of information with the SunStore Data Warehouse.


• LYNX
• Communicate with the CAV-ITS Map Update System to obtain up-to-date maps.
• Communicate with the FDOT SCMS regarding CAV security.
• Provide awareness of surrounding connected and autonomous vehicles.


• City of Orlando
• Coordinate CAV capabilities with private vehicles using City of Orlando field equipment.
• Operate traffic signal systems, including CCTVs, signals, and sensors, for the City of Orlando.
• Provide vehicles with intersection information in support of vehicle safety.