Connected Vehicle Environment System Requirements 1
This material is based upon work supported by the U.S. Department of Transportation under Agreement No. DTFH6116H00013. Any opinions, findings, and conclusions or recommendations expressed in this publication are those of the Author(s) and do not necessarily reflect the view of the U.S. Department of Transportation. 2
SPEAKERS RYAN BOLLO TOM TIMCHO CHRISTOPHER TOTH Project Manager, Technical Lead, CV Systems Engineer, City of Columbus WSP WSP rjbollo@columbus.gov tom.timcho@wsp.com christopher.toth@wsp.com 3
TODAY’S AGENDA 01 | PURPOSE OF THIS WEBINAR • Discuss System Requirements activities and get feedback from SMEs and public input. 02 | WEBINAR CONTENT • Smart Columbus Program Overview • Connected Vehicle Environment Project Overview • Smart Columbus Connected Vehicle Environment System Requirements • Subject Matter Experts Panel • Questions • How to Stay Connected 03 | WEBINAR PROTOCOL • All participant lines have been muted during the webinar in order to reduce background noise • Questions are welcome via chatbox during the Q&A Section • The webinar recording and presentation materials will be posted on the Smart Columbus website 4
$40 MILLION 78 APPLIED • COLUMBUS WON VISION: T o empower our residents to live their best lives through responsive, innovative and safe mobility solutions. MISSION: T o demonstrate how an intelligent transportation system and equitable access to transportation can have positive impacts on every day challenges faced by cities. OUTCOMES: 5
CONNECTED VEHICLE ENVIRONMENT 6
DEPLOYMENT AREA 7
ON-BOARD UNIT INSTALLATIONS Vehicle Type Quantity Private Vehicle 1019 Light-Duty Vehicle City Fleet Vehicle 200 COTA Supervisor Vehicle 25 Fire Truck/EMS 30 Emergency Vehicle Police Cruiser 80 Heavy-Duty Vehicle Platoon Truck 10 CEAV 6 COTA Transit Bus* Transit Vehicle 350 (fixed-route) COTA Paratransit Bus 80 Total 1,800 *Quantity may vary slightly depending on operational needs. Source: City of Columbus 8
APPLICATIONS Heavy-Duty Emergency Class Application Light-Duty Manager Manager Transit Transit Vehicle Vehicle Vehicle Vehicle Traffic V2V Emergency Electronic Brake Light X Safety Forward Collision Warning X Intersection Movement Assist X Lane Change Warning/ Blind Spot Warning X V2I TransitSignal Priority X X Mobility Freight Signal Priority/ Intent to Platoon Priority X Emergency Vehicle Preemption X Vehicle Data for Traffic Operations X TransitVehicle Interaction Event Recording X V2I Red Light Violation Warning X Safety Reduced Speed School Zone X For more information, please see the Connected Vehicle Environment Concept of Operations 9
SYSTEM REQUIREMENTS 10
SYSTEM REQUIREMENTS Development Process • Break down system into functional group categories. • Develop technical requirements for system sub-components. • Link requirements with user needs, constraints, and interfaces as described by the ConOps. 11
SYSTEM REQUIREMENTS System Boundary 27. Over-the-Air (Wi-Fi) 13. Satellite Transit CV Transit Vehicle 25. Backhaul Management 26. Local OBU (Internet) System Transit Traffic Signal Vehicle Human Interface 28. UI Smart Controller / (existing) Databus Columbus School Zone Transit CV 19. DSRC Signal Operating Mgmt. Staff Loc and Time System LDV 24. Backhaul Other OBU Data Source 23. Local Functional Group (Internet) Operator Traffic CV (GNSS) 18. DSRC Common 20. DSRC Management 8. UI RSU Network Time 12. Satellite System 16. Backhaul 15. Backhaul 9. DSRC DSRC Messages LDV OBU Source 7. Local 22. Backhaul Roadside Equipment LDV Databus Traffic Management Center 17. Backhaul Ohio CORS 3. UI (Internet) 10. Satellite Transit Management Center 2. DSRC Emergency Traffic CV 1. Local V2I Mobility Vehicle OBU Mgmt. Staff Security and 21. Backhaul Emergency Credentials 29. UI V2I Safety Vehicle Management Emergency Databus 14. Satellite V2V Safety System Vehicle Operator Location and Time Vehicle Onboard Equipment Source (GNSS) 11. Satellite Platooning 6. DSRC HDV OBU Provider 4. Local 5. Over-the-Air (TBD) Central Management HDV Databus System Boundary System Step 1: Break down system into functional group categories. 12
SYSTEM REQUIREMENTS System Boundary 27. Over-the-Air (Wi-Fi) 13. Satellite Transit CV Transit Vehicle 25. Backhaul Management 26. Local OBU (Internet) System Transit Traffic Signal Vehicle Human Interface 28. UI Smart Controller / (existing) Databus Columbus School Zone Transit CV 19. DSRC Signal Operating Mgmt. Staff Loc and Time System LDV 24. Backhaul Other OBU Data Source 23. Local Functional Group (Internet) Operator Traffic CV (GNSS) 18. DSRC Common 20. DSRC Management 8. UI RSU Network Time 12. Satellite System 16. Backhaul 15. Backhaul 9. DSRC DSRC Messages LDV OBU Source 7. Local 22. Backhaul Roadside Equipment LDV Databus Traffic Management Center 17. Backhaul Ohio CORS 3. UI (Internet) 10. Satellite Transit Management Center 2. DSRC Emergency Traffic CV 1. Local V2I Mobility Vehicle OBU Mgmt. Staff Security and 21. Backhaul Emergency Credentials 29. UI V2I Safety Vehicle Management Emergency Databus 14. Satellite V2V Safety System Vehicle Operator Location and Time Vehicle Onboard Equipment Source (GNSS) 11. Satellite Platooning 6. DSRC HDV OBU Provider 4. Local 5. Over-the-Air (TBD) Central Management HDV Databus System Boundary System Step 1: Break down system into functional group categories. 13
SYSTEM REQUIREMENTS Step 2: Develop technical requirements for system components 14
SYSTEM REQUIREMENTS Step 3: Link requirements with user needs, constraints, and interfaces as described by the ConOps 15
REQUIREMENTS BY THE NUMBERS 16
SUBJECT MATTER EXPERTS PANEL TONY ENGLISH JIAQI MA NICK HEGEMIER MIKE SCHULMAN Lead System Design for Assistant Professor, Managing Director of Program Manager, NEXT Mobility Lab Lead, Infrastructure, Wyoming CV Pilot Trihydro University of Cincinnati Ohio Department of Crash Avoidance Metrics Transportation Partnership 17
REQUIREMENTS DISCUSSION SUBJECT MATTER EXPERTS PANEL • Four categories of requirements are discussed • Interoperability • Applications • Human Machine Interface (HMI) • Operations • For each category: • Description • Example requirements • Questions and Discussion • Procurement 18
INTEROPERABILITY SYSTEM REQUIREMENTS Communication on specific interfaces (internal and external) are constrained to specific standards so that the CVE can be easily expanded and will be able to interact with external systems that use the same widely-accepted standards 19 19
INTEROPERABILITY SYSTEM REQUIREMENTS RequirementID Description CVE-CN1648-V01 All CVE components that utilize DSRC shall comply with all of the following: 1. SAE J2735_201603 - Dedicated Short Range Communications (DSRC) Message Set Dictionary. 2. SAE J 2945/1 - On-Board System Requirements for V2V Safety Communications 3. SAE J 2945/4 (draft) - DSRC Messages for Traveler Information and Basic Information Delivery 4. IEEE 802.11p - Wireless Access in Vehicular Environments. 5. IEEE 1609.2 - IEEE Standard for Wireless Access in Vehicular Environments -- Security Services for Applications and Management Messages 6. IEEE 1609.3 - IEEE Standard for Wireless Access in Vehicular Environments (WAVE) -- Networking Services. 7. IEEE 1609.4 - IEEE Standard for Wireless Access in Vehicular Environments (WAVE) -- Multi-Channel Operation. 8. NTCIP 1202 - NTCIP Object Definitions for Actuated Traffic Controllers. 9. NTCIP 1211 - NTCIP Objects for Signal Control and Prioritization (SCP) CVE-FN1308-V01 An RSU shall acquire time from the Location and Time Source (LTS) interface in accordance with J2945/1 section 6.2.4. CVE-FN1309-V01 An RSU shall acquire location from the LTS interface in accordance with J2945/1 section 6.2.1. CVE-FN1311-V01 An RSU shall use Coordinated Universal Time (UTC) time for all logged data (e.g., events logs, probe vehicle data) based on the format defined in J2735 section 6.19 and epoch of January 1st 1970. 20 20
INTEROPERABILITY QUESTIONS/FEEDBACK 1. Aside from adhering to existing communications and messaging standards, what other requirements should be included to maximize the likelihood of interoperability with other CV systems? 2. Are there certain data elements in standards that should be included or interpreted differently? For instance, are there optional field of J2735 that are critical to implement? 3. Are there any messages that are being considered for future standards that should be considered for the CV Environment? 21 21
CV APPLICATION SYSTEM REQUIREMENTS Requirements that describe and constrain the communications and functions that enable CV Applications V2V Safety V2I Safety V2I Mobility 22 22
Recommend
More recommend
