1 Smart Columbus
2 System Requirements
3 for Connected Vehicle Environment
4 for the Smart Columbus
5 Demonstration Program
6 www.its.dot.gov/index.htm
7 Draft Report – October 24, 2018
8 9 Source: City of Columbus – November 2015
10
11 Produced by City of Columbus 12 U.S. Department of Transportation 13 Office of the Assistant Secretary for Research and Technology
14 Notice
15 This document is disseminated under the sponsorship of the Department of 16 Transportation in the interest of information exchange. The United States Government 17 assumes no liability for its contents or use thereof.
18 The U.S. Government is not endorsing any manufacturers, products, or services cited 19 herein and any trade name that may appear in the work has been included only because 20 it is essential to the contents of the work.
21 Acknowledgment of Support
22 This material is based upon work supported by the U.S. Department of Transportation 23 under Agreement No. DTFH6116H00013.
24 Disclaimer
25 Any opinions, findings, and conclusions or recommendations expressed in this 26 publication are those of the Author(s) and do not necessarily reflect the view of the U.S. 27 Department of Transportation.
28
Technical Report Documentation Page
1. Report No. 2. Government Accession No. 3. Recipient’s Catalog No.
4. Title and Subtitle 5. Report Date Smart Columbus October 24, 2018
Systems Requirements for Connected Vehicle Environment (CVE) for Smart 6. Performing Organization Code Columbus Demonstration Program
7. Author(s) 8. Performing Organization Report No. Ryan Bollo, City of Columbus; Dr. Christopher Toth, WSP; Thomas Timcho, WSP, Jessica Baker, HNTB, Robert James, HNTB
9. Performing Organization Name and Address 10. Work Unit No. (TRAIS) City of Columbus 90 West Broad Street Columbus, OH 43215-9004 11. Contract or Grant No. DTFH6116H00013
12. Sponsoring Agency Name and Address 13. Type of Report and Period Covered U.S. Department of Transportation (USDOT) Draft Report Federal Highway Administration (FHWA) Office of Acquisition and Grants Management 14. Sponsoring Agency Code 1200 New Jersey Avenue, SE HOIT-1 Mail Drop: E62-204 Washington, DC 20590
15. Supplementary Notes Kate Hartman, AOR; Sarah Tarpgarrd, AO
16. Abstract The Smart City Demonstration Program is intended to improve access through expanded mobility options in major job centers, enhance visitor experience by better connecting visitors to transportation options, stimulate regional economic prosperity and compete globally through smart logistics, better connect Columbus residents to safe, reliable transportation that can be accessed by all, and support the efficient movement of people and goods through environmentally sustainable practices. This System Requirement Specification (SyRS) serves as the second in a series of engineering documents intended to describe the CVE, building upon the Concept of Operations (ConOps) Document. The SyRS describes a set of requirements that, when realized, will satisfy the expressed needs of the CVE. This document includes the identification, organization, presentation, and modification of the requirements for the CVE. This SyRS addresses conditions for incorporating operational concepts, design constraints, and design configuration requirements as well as the necessary characteristics and qualities of individual requirements and the set of all requirements.
17. Keywords 18. Distribution Statement Smart city, system requirements. CVE, Connected Vehicle Environment
19. Security Classif. (of this report) 20. Security Classif. (of this page) 21. No. of Pages 22. Price
Unclassified Unclassified 297 N/A
Form DOT F 1700.7 (8-72) Reproduction of completed page authorized 29
30 Table of Contents
31 Chapter 1. Introduction ...... 1 32 Document Purpose ...... 1 33 Project Scope ...... 1 34 Requirements Process ...... 4 35 References ...... 5
36 Chapter 2. System Description ...... 7 37 System Context ...... 7 38 System Modes and States ...... 19 39 Major System Characteristics ...... 20 40 System Capabilities ...... 20 41 System Conditions ...... 21 42 System Constraints ...... 21 43 User Characteristics ...... 22 44 Light-Duty Vehicle Operator ...... 23 45 Emergency Vehicle Operator ...... 23 46 Heavy-Duty Vehicle Operator ...... 24 47 Traffic Manager ...... 24 48 Transit Vehicle Operator ...... 24 49 Transit Manager ...... 24 50 Network Manager ...... 24 51 Assumptions and Dependencies ...... 25 52 System Constraints ...... 25 53 Operational Scenarios ...... 30
54 Chapter 3. System Requirements ...... 31 55 Functional Requirements ...... 33 56 Performance Requirements ...... 77 57 Interface Requirements ...... 84 58 Data Requirements ...... 96 59 Security Requirements ...... 123 60 Non-Functional Requirements ...... 127 61 Physical Requirements ...... 127 62 Availability and Recoverability Requirements ...... 128 63 Maintainability Requirements ...... 128
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | i Table of Contents
64 Storage and Transport Requirements ...... 132 65 Disposal Requirements ...... 133 66 Enabling Requirements ...... 133 67 Information Management Requirements ...... 133 68 Life Cycle Sustainment Requirements ...... 134 69 Policy and Regulation Requirements ...... 134
70 Chapter 4. Engineering Principles ...... 137 71 Methods of Verification ...... 137 72 Reference Architecture ...... 138
73 Appendix A. Document Terminology and Conventions ...... 145 74 Reference Conventions ...... 145
75 Appendix B. Requirements by System Functional Groups ...... 149
76 Appendix C. Relationship Matrix ...... 185
77 Appendix D. Other Mapped Relations ...... 228
78 Appendix E. Data Matrix ...... 266
79 Appendix F. Requirements Verification Traceability Matrix ...... 277
80 Appendix G. Acronyms and Definitions ...... 279
81 Appendix H. Glossary ...... 283
82 Appendix I. Version History ...... 287 83
84
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
ii | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Table of Contents
85 List of Tables
86 Table 1: Connected Vehicle Environment Project Scope ...... 3 87 Table 2: References ...... 5 88 Table 3: Connected Vehicle Environment Proposed System Interfaces and Elements...... 10 89 Table 4: Connected Vehicle Environment System Functional Groups ...... 17 90 Table 5: Connected Vehicle Environment Stakeholders and User Classes ...... 22 91 Table 6: Assumptions and Dependencies ...... 25 92 Table 7: System Constraints ...... 26 93 Table 8: List of Requirement Types ...... 31 94 Table 9: Functional Requirements ...... 33 95 Table 10: Performance Requirements ...... 78 96 Table 11: Interface Requirements ...... 84 97 Table 12: Data Requirements ...... 96 98 Table 13: Security Requirements ...... 123 99 Table 14: Physical Requirements ...... 127 100 Table 15: Maintainability Requirements ...... 129 101 Table 16. Storage and Transport Requirements ...... 132 102 Table 17: Disposal Requirements ...... 133 103 Table 18: Policy and Regulation Requirements ...... 134 104 Table 19: Methods of Verification ...... 137 105 Table 20: Requirements Numbering Convention ...... 145 106 Table 21: Requirements Organized by Functional Groups ...... 149 107 Table 22: Established Relations per Requirements ...... 185 108 Table 23: Constraint Relations ...... 228 109 Table D-2 System Interface Relations ...... 230 110 Table D-3 Requirements Mapped to Requirements ...... 234 111 Table 24: Data Matrix ...... 266 112 Table 25: Acronym List ...... 279 113 Table 26: Glossary ...... 283 114 Table 27: Version History ...... 287 115
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | iii Table of Contents
116 List of Figures
117 Figure 1: Connected Vehicle Environment Stakeholder Requirements Definition Process ...... 4 118 Figure 2: Connected Vehicle Environment System Breakdown Diagram ...... 8 119 Figure 3: ARC-IT Representation of the Connected Vehicle Environment (Includes Support Systems) .. 139 120 Figure 4: ARC-IT Representation of V2V Safety Applications (EEBL, FCW, BSW/LCW, IMA) ...... 140 121 Figure 5: ARC-IT Representation of RLVW...... 141 122 Figure 6: ARC-IT Representation of RSSZ ...... 141 123 Figure 7: ARC-IT Representation of Signal Priority/Preemption Applications (TSP, FSP, EVP) ...... 142 124 Figure 8: ARC-IT Representation of VDTO ...... 142 125 Figure 9: ARC-IT Representation of TVIER ...... 143 126
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
iv | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
127 Chapter 1. Introduction
128 This Systems Requirements Specification (SyRS) is intended to provide the requirements that drive the 129 specification, design, development, implementation, integration and testing of the Smart Columbus 130 Connected Vehicle Environment (CVE). The SyRS is a “black-box” description of what the CVE must do, 131 but not how it will do it. The document contains descriptions of inputs, outputs, and required relationships 132 between inputs and outputs.
133 Document Purpose
134 This System Requirement Specification (SyRS) serves as the second in a series of engineering 135 documents intended to describe the CVE, building upon the Concept of Operations (ConOps) Document. 136 The SyRS describes a set of requirements that, when realized, will satisfy the expressed needs of the 137 CVE. This document includes the identification, organization and presentation of the requirements for the 138 CVE project, which is a system made up of Connected Vehicle (CV) infrastructure and applications. 139 These requirements are derived from the user needs, constraints and interfaces that the CVE is expected 140 to implement, and the work within leverages prior system requirements efforts for related projects and 141 applications. This SyRS addresses conditions for incorporating operational concepts, design constraints, 142 and design configuration requirements as well as the necessary characteristics and qualities of individual 143 requirements and the set of all requirements.
144 This document was developed based on IEEE 1233-1998 IEEE Guidance for Developing System 145 Requirements Specifications and contains the following chapters:
146 1. Chapter 1. Introduction provides an overview of the CVE project and key elements that guide the 147 development of this SyRS document, including an overview of the project, the stakeholders, 148 requirements development process, and referenced materials.
149 2. Chapter 2. System Description focuses on describing and extending the CVE system concepts 150 established in the Concept of Operations (ConOps), including system capabilities, conditions, 151 constraints, and decomposing the system into its functional groups for establishing requirements.
152 3. Chapter 3. System Requirements contains the requirements for each functional group that make up 153 the system.
154 4. Chapter 4. Engineering Principles provides a description of engineering principles applied to the 155 system and requirements definition process.
156 Project Scope
157 In 2016, the U.S. Department of Transportation (USDOT) awarded $40 million to the City of Columbus, 158 Ohio, as the winner of the Smart City Challenge. With this funding, Columbus intends to address the most 159 pressing community-centric transportation problems by integrating an ecosystem of advanced and
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 1 Chapter 1. Introduction
160 innovative technologies, applications, and services to bridge the sociotechnical gap and meet the needs 161 of residents of all ages and abilities. In conjunction with the Smart City Challenge, Columbus was also 162 awarded a $10 million grant from Paul G. Allen Philanthropies to accelerate the transition to an electrified, 163 low-emissions transportation system.
164 With the award, the city established a strategic Smart Columbus program with the following vision and 165 mission:
166 Smart Columbus Vision: Empower residents to live their best lives through responsive, 167 innovative, and safe mobility solutions
168 Smart Columbus Mission: Demonstrate how and ITS and equitable access to transportation can 169 have positive impacts on every day challenges faced by cities
170 To enable these new capabilities, the Smart Columbus program is organized into three focus areas 171 addressing unique user needs: enabling technologies, emerging technologies, and enhanced human 172 services. The CVE primarily addresses needs in the enabling technologies focus area. The CVE project is 173 one of the nine projects in the Smart Columbus program and is a significant enabler to other technologies 174 delivered through the other eight projects. The CVE project will integrate smart traveler applications, 175 automated vehicles, connected vehicles, and smart sensors into its transportation network by focusing on 176 deploying CV infrastructure and CV applications.
177 CV Infrastructure – The project will focus on building out the physical and logical CV 178 infrastructure, which will consist of CV hardware and software (e.g. roadside units (RSUs), on- 179 board equipment, front and backhaul communications, equipment interfaces, etc.). The CVE will 180 generate the needed transportation-related data that are used by applications.
181 CV Applications and Data – The project scope also consists of deploying CV-specific 182 applications that will leverage the data generated by the infrastructure to deliver real-time safety 183 and mobility services. Data will be collected, stored, and made available for use in other Smart 184 Columbus project applications.
185 The CVE is expected to enhance safety and mobility for vehicle operators and improve pedestrian safety 186 in school zones by deploying CV infrastructure on the roadside and CV equipment in vehicles. The CVE 187 will also provide sources of high-quality data for traffic management and safety purposes. The foundation 188 for the CVE is the Columbus Traffic Signal System (CTSS), which is a high-speed network backbone. 189 When complete, the CTSS will interconnect 1,250 traffic signals in the Columbus region and provide 190 uniform signal coordination capability throughout the system. CTSS Phase D, which will connect all CVE 191 corridors with the exception of Alum Creek Drive, is expected to be complete in December 2018. An 192 expansion of the CTSS to connect Alum Creek Drive will be included in the CVE project.
193 The CV infrastructure deployment will occur along seven major corridors/areas. The deployment of in- 194 vehicle devices will target populations that are located near or frequently used infrastructure deployment 195 corridors. Table 1: Connected Vehicle Environment Project Scope lists the improvements associated 196 with the CVE.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
2 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 1. Introduction
197 Table 1: Connected Vehicle Environment Project Scope
Infrastructure Applications and Data
113 RSUs 1,800 OBUs CV Applications Data Capture The project will install The project will install The project will deploy The project will RSUs and other CV- onboard units (OBUs) vehicle-to-vehicle capture, relate, store, compatible equipment on participating private, (V2V) safety, vehicle- and respond to data at signalized emergency, transit, and to-infrastructure (V2I) generated by the intersections in the freight vehicles. safety, and V2I mobility infrastructure, used by project areas. applications. the applications for traffic management.
198 Source: City of Columbus
199 The intent of the CVE project is to improve safety and mobility of travelers by deploying CV technology as 200 part of a larger initiative within the City to improve the overall transportation system. As noted previously, 201 CV will be deployed to support the City’s automated vehicle project and to support the improvement in 202 freight operations, another of the City’s goal. Collectively, CV is just one component, but if it proves to be 203 effective, other projects can also benefit from the positive outcomes. Because the CVE primarily intends 204 to deploy CV technology (not the development of new applications or functionality), it is important for the 205 reader to understand that the ability of the CVE to address the user needs captured in the ConOps 206 depends on the availability of deployment-ready hardware and software solutions. Thus, the design and 207 implementation of the CVE will draw on these previous development efforts. The Architecture Reference 208 for Cooperative and Intelligent Transportation (ARC-IT)1 and its predecessor, the Connected Vehicle 209 Reference Implementation Architecture (CVRIA)2, are resources that provide descriptions of CV 210 applications that have been researched in the context of the National ITS architecture. Furthermore, the 211 Open Source Application Development Portal (OSADP) contains software for applications that have been 212 developed.3 When possible, applications on the CVRIA and OSADP will be used as-is or will have 213 minimal modifications made to address user needs documented in the ConOps.
214 Given that the primary scope of the CVE is to realize the benefits of deploying CV technology into an 215 operational environment, only applications that have demonstrated sufficient levels of development and 216 testing are being considered for implementation. However, the CVE will be designed in such a way that 217 added functionality concepts (that need further development) can be integrated with the CVE once 218 development and testing have matured to a point where applications are deployment-ready. Additionally, 219 due to the networked nature of devices in the CVE, several policies and constraints related to information 220 technology (IT) and data security are expected to be developed as part of the deployment.
1 https://local.iteris.com/arc-it/ 2 https://local.iteris.com/cvria/ 3 Open Source Application Development Portal. https://www.itsforge.net/
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 3 Chapter 1. Introduction
221 Requirements Process
222 The requirements established for this project will govern the CVE system’s development cycle and are an 223 essential factor in further defining and clarifying the scope and feasibility of development for the system. 224 This process will also provide the basis for the technical description of deliverables in the form of a 225 system‐level specification and defined interfaces at the system boundaries. Figure 1: Connected 226 Vehicle Environment Stakeholder Requirements Definition Process provides a high-level view of the 227 project’s stakeholder requirements definition process. Once the project’s requirements are established 228 they will be formally placed under configuration control using the Helix software system.
229 Figure 1: Connected Vehicle Environment Stakeholder Requirements Definition Process
CONTROLS
USDOT and City of Columbus Laws and Regulations Smart Columbus Project Procedures, Standards, and Directives City Agreements ITS Industry Standards Concept of Operations Operational Constraints and Policies
INPUTS ACTIVITIES OUTPUTS
Smart Columbus Project Evaluate stakeholder Stakeholder Mgt Plan needs requirements SoS Documentation Elicit stakeholder Verification Plan Connected Vehicle requirements Initial RVTM Environment Concept of Establish and define System feasibility Operations system requirements findings Stakeholder Needs Evaluate distributed Concept of production Project Performance SoS architecture and with agreement on Plan feasibility of system system boundaries Constraints Map requirements to Measure of user needs in RTM tool Effectiveness (MOE) for development needs and data
ENABLERS
ITS and Technology Standards Smart Columbus Program Communications Plan
230 Source: City of Columbus
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
4 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 1. Introduction
231 References
232 Table 2: References contains documents, literature, and Working Group Sessions used to gather input 233 for this document.
234 Table 2: References
Document Number Title Rev Pub. Date
FHWA-JPO-17-518 Smart Columbus Systems Engineering – January 16, 2018 Management Plan (SEMP) for Smart Columbus Demonstration Program https://rosap.ntl.bts.gov/view/dot/34764
– Beyond Traffic: The Smart City Challenge – – May 24, 2016 Phase 2 – Volume 1: Technical Application https://www.columbus.gov/WorkArea/Downlo adAsset.aspx?id=2147487896
– Security Credential Management System – January 11, 2016 Proof–of–Concept Implementation – EE Requirements and Specifications Supporting SCMS Software Release 1.0 http://www.its.dot.gov/pilots/pdf/SCMS_POC _EE_Requirements20160111_1655.pdf
1233-1998 IEEE Guidance for Developing System – 1998 Requirements Specifications
INCOSE‐TP‐2003‐002‐ INCOSE Systems Engineering Handbook 3.2.2 2011 03.2.2
– Systems Engineering Guidebook for 3.0 2009 Intelligent Transportation Systems
FHWA-JPO-17-521 Concept of Operations for the Connected – June 8, 2018 Vehicle Environment for the Smart Columbus Demonstration Program
– SPaT Challenge Verification Document 1.2 October 30, 2017
FHWA-JPO-16-315 Connected Vehicle Pilot Deployment – August 2016 Program Phase 1, System Requirements Specification (SyRS) – Tampa (THEA)
FHWA-JPO-16-303 Connected Vehicle Pilot Deployment – July 2016 Program Phase 1 Systems Requirements Specification (SyRS) – New York City
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 5 Chapter 1. Introduction
Document Number Title Rev Pub. Date
SAE J2735 _201603 Dedicated Short Range Communications – March 2016 (DSRC) Message Set Dictionary
SAE J2945/1 _201603 On-Board System Requirements for V2V – March 2016 Safety Communications
SAE J2945/9 (draft) Performance Requirements for Safety – – Communications to Vulnerable Road Users
SAE J3067 _201408 Candidate Improvements to Dedicated Short – August 2014 Range Communications (DSRC) Message Set Dictionary (SAE J2735) Using Systems Engineering Methods
IEEE 802.3 IEEE Standard for Ethernet – 2015
IEEE 1609.2 IEEE Standard for Wireless Access in – 2016 Vehicular Environments – Security Services for Applications and Management Messages
IEEE 1609.3 IEEE Standard for Wireless Access in – 2016 Vehicular Environments (WAVE) – Networking Services
IEEE 1609.4 IEEE Standard for Wireless Access in – 2016 Vehicular Environments (WAVE) – Multi- Channel Operation
NTCIP 1202 NTCIP Object Definitions for Actuated Traffic 3 January 2005 Controllers
NTCIP 1211 NTCIP Objects for Signal Control and – October 2014 Prioritization (SCP)
235 Source: City of Columbus
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
6 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
236 Chapter 2. System Description
237 System Context
238 The CVE can be described as a combination of subsystems that work together: a system of roadside 239 equipment, a system of in-vehicle equipment, and a system of backhaul networks for agency data. On the 240 roadside, the fundamental functions of the RSUs are to obtain several types of status information from 241 roadside ITS devices and broadcast this information to vehicles in the vicinity. Intersections identified for 242 the deployment of roadside CV equipment presumably contain necessary physical cabinet and conduit 243 space for the proposed CV equipment, and that the distance between the cabinet equipment and 244 overhead RSU mounting locations conform to distance constraints for physical communication between 245 locally networked devices. Necessary remedies will be addressed upon completion of detailed installation 246 plans.
247 Subsequently, in a vehicle, the fundamental functions of OBUs are to obtain various types of status 248 information from the vehicle and broadcast this information to other vehicles and infrastructure in the 249 vicinity. The OBU may utilize status information from the vehicle (this includes interfaces with other in- 250 vehicle devices deployed as part of the Smart Columbus program), other vehicles, the roadside, and 251 location and time data (obtained from a location and time source, such as GNSS) to support safety and 252 mobility applications. Similarly, the RSU exchanges information with the roadside ITS equipment, 253 vehicles, and location and time data to support mobility applications. OBUs will be comprised of DSRC 254 radios, and depending on their applications, may include a Human Machine Interface (HMI) and/or 255 connect to vehicle data systems. Both the OBU and RSU utilize the Security and Credentials 256 Management System (SCMS) to make sure that it is working with data from trusted sources, and the 257 roadside device saves operational data on the Smart Columbus Operating System (OS).
258 Figure 2: Connected Vehicle Environment System Breakdown Diagram shows V2I communication 259 between vehicles and roadside devices (via DSRC); communication between roadside devices and data 260 management systems (via backhaul); and V2V communication between onboard devices (via DSRC). 261 Table 3: Connected Vehicle Environment Proposed System Interfaces and Elements summarizes 262 the interfaces, hardware, facilities, communications and messages used in the system. The reader should 263 reference these figures and table throughout this section to foster a better understanding of the system 264 concept.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 7 Chapter 2. System Description
265 Figure 2: Connected Vehicle Environment System Breakdown Diagram
Transit CV 27. Over-the-Air (Wi-Fi) Transit Vehicle OBU Management System Loc and Time Data Source (GNSS) 25. Backhaul Traffic Signal Controller / School Zone Signal Vehicle Location Vehicle Situation Transit Center Data (Internet) Determination Roadway Speed Data Monitoring Collection Roadway Signal 13. Satellite Monitoring and Control Transit Vehicle Signal Warning Human Interface Vehicle Trust Priority 26. Local 28. UI (existing) Management Smart Columbus Roadway Support Roadway Signal Operating System Services Preemption Transit CV Vehicle Basic Safety Transit Vehicle Communication Databus Management Staff Archive Data Repository Elements Flow Cardinality 19. DSRC Archive Situation Data Location and Time Unicast Archival 23. Local Source (GNSS) Other OBU Center LDV Operator Multicast 14. Satellite Traffic CV 24. Backhaul (Internet) Management System Broadcast RSU 8. UI 18. DSRC Vehicle RSE Intersection LDV OBU TMC Signal Control RSE Traffic Monitoring Backhaul (existing) Management 12. Satellite 20. DSRC Vehicle Intersection Vehicle Situation Data Flow Status Warning Monitoring TMC Intersection RSE Intersection RSE Situation Safety 17. Backhaul Ohio CORS (Internet) Safety Monitoring Support Existing Vehicle Location Vehicle Map 9. DSRC Determination Management Project Center Support RSE Position RSE Map Services Correction Support Management Vehicle Speed Vehicle Trust 7. Local Network Time Source Management Assist Management RSE Trust 2. DSRC Field TMC Speed Warning 16. Backhaul 15. Backhaul RSE Support Services Management Flow Security Vehicle Basic Safety TMC Multi-Modal Communication LDV Databus Clear text, No Auth. Coordination 22. Backhaul RSE Speed Warning 6. DSRC Traveler Clear text, Auth. TMC Situation Data Management Emergency Vehicle OBU 10. Satellite Encrypted, Auth. 21. Backhaul Center Map Management Security and Credentials Management Vehicle Location Vehicle Trust 1. Local People System Determination Management TMC Data Collection EV On-Board En Route CCMS Misbehavior Emergency CCMS Authorization Support Reporting and Action Vehicle 3. UI Databus Functional 29. UI Object Traffic CV CCMS Enrollment CCMS Revocation Management Staff Emergency Vehicle CCMS Provisioning Operator
HDV OBU 11. Satellite
Platooning Provider CV On-Board Signal Vehicle Trust Central Management Priority Management 4. Local System
Freight Administration 5. Over-the-Air (TBD) Vehicle Location HDV Databus and Management Determination 266
267 Source: City of Columbus as generated from ARC-IT
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
8 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 2. System Description
268
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 9 Chapter 2. System Description
269 Table 3: Connected Vehicle Environment Proposed System Interfaces and Elements Interface Communications ID Reference Source Element Destination Element Data Flow Media
CVE- Interface 1 Emergency Vehicle Emergency Vehicle CAN Bus Data Local IX1608-V01 Databus OBU
CVE- Interface 2.1 Emergency Vehicle RSU SRM, BSM, Device DSRC IX1609-V01 OBU Enrollment Information, Misbehavior Report
CVE- Interface 2.2 RSU Emergency Vehicle SPaT, MAP, SSM, RTCM, DSRC IX1610-V01 OBU Security Policy and Networking Information, Security Credentials, Credential Revocations
CVE- Interface 3 Traffic Management Traffic CV MAP data, RSM data UI IX1611-V01 Staff (GIS Staff) Management Center (school zone locations, (CV MAP Update speed, and active times) System)
CVE- Interface 4 HDV Databus HDV OBU CAN Bus Data Local IX1612-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
10 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 2. System Description
Interface Communications ID Reference Source Element Destination Element Data Flow Media
CVE- Interface 5.1 HDV OBU Platooning Provider Platoon Data Request Over-the-Air IX1613-V01 Central Management (TBD) System
CVE- Interface 5.2 Platooning Provider HDV OBU Platoon Data Over-the-Air IX1614-V01 Central Management (TBD) System
CVE- Interface 6.1 HDV OBU RSU SRM, BSM, Device DSRC IX1615-V01 Enrollment Information, Misbehavior Report
CVE- Interface 6.2 RSU HDV OBU SPaT, MAP, SSM, RTCM, DSRC IX1616-V01 Security Policy and Networking Information, Security Credentials, Credential Revocations
CVE- Interface 7 LDV Databus LDV OBU CAN Bus Data Local IX1617-V01
CVE- Interface 8 LDV OBU LDV Operator Alert UI IX1618-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 11 Chapter 2. System Description
Interface Communications ID Reference Source Element Destination Element Data Flow Media
CVE- Interface 9.1 LDV OBU RSU BSM, Device Enrollment DSRC IX1619-V01 Information, Misbehavior Report
CVE- Interface 9.2 RSU LDV OBU SPaT, MAP, RTCM, RSM, DSRC IX1620-V01 Security Policy and Networking Information, Security Credentials, Credential Revocations
CVE- Interface 10 Loc and Time Data Emergency Vehicle Location and Time Data Satellite IX1621-V01 Source (GNSS) OBU (GNSS Data)
CVE- Interface 11 Loc and Time Data HDV OBU Location and Time Data Satellite IX1622-V01 Source (GNSS) (GNSS Data)
CVE- Interface 12 Loc and Time Data LDV OBU Location and Time Data Satellite IX1623-V01 Source (GNSS) (GNSS Data)
CVE- Interface 13 Loc and Time Data Transit Vehicle OBU Location and Time Data Satellite IX1624-V01 Source (GNSS) (GNSS Data)
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
12 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 2. System Description
Interface Communications ID Reference Source Element Destination Element Data Flow Media
CVE- Interface 14 Location and Time RSU Location and Time Data Satellite IX1625-V01 Source (GNSS) (GNSS Data)
CVE- Interface 15 Network Time Source RSU Network Time Data Backhaul IX1626-V01
CVE- Interface 16 Network Time Source Traffic CV Network Time Data Backhaul IX1627-V01 Management System
CVE- Interface 17 Ohio CORS RSU RTCM data Backhaul IX1628-V01 (Internet)
CVE- Interface 18 Other OBU (LDV, LDV OBU BSM DSRC IX1629-V01 HDV, Emergency Vehicle, and Transit Vehicle OBU)
CVE- Interface 19 Other OBU (LDV, Transit Vehicle OBU BSM DSRC IX1630-V01 HDV, Emergency Vehicle, and Transit Vehicle OBU)
CVE- Interface 20.1 RSU Transit Vehicle OBU SPaT, MAP, SSM, RTCM, DSRC IX1631-V01 Security Policy and Networking Information,
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 13 Chapter 2. System Description
Interface Communications ID Reference Source Element Destination Element Data Flow Media
Security Credentials, Credential Revocations
CVE- Interface 20.2 Transit Vehicle OBU RSU SRM, BSM, Device DSRC IX1632-V01 Enrollment Information, Misbehavior Report
CVE- Interface 21.1 RSU Security and Device Enrollment Backhaul IX1633-V01 Credentials Information, Misbehavior Management System Report
CVE- Interface 21.2 Security and RSU Security Policy and Backhaul IX1634-V01 Credentials Networking Information, Management System Security Credentials, Credential Revocations
CVE- Interface 22.1 RSU Traffic CV BSM, SRM, SSM, SPaT Backhaul IX1635-V01 Management System
CVE- Interface 22.2 Traffic CV RSU RSM, Authorized OBU ID Backhaul IX1636-V01 Management System List
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
14 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 2. System Description
Interface Communications ID Reference Source Element Destination Element Data Flow Media
CVE- Interface 23.1 RSU Traffic Signal SRM data (signal Local IX1637-V01 Controller / School preemption request data) Zone Signal
CVE- Interface 23.2 Traffic Signal RSU SPaT data, School Zone Local IX1638-V01 Controller / School Flashing Light Indicator Zone Signal
CVE- Interface 24 Traffic CV Smart Columbus Performance measures, Backhaul IX1639-V01 Management System Operating System (processed and PII- (Internet) removed BSM, SRM, SSM, SPaT)
CVE- Interface 25 Transit CV Smart Columbus Performance measures, Backhaul IX1640-V01 Management System Operating System (processed and PII- (Internet) removed Transit Vehicle Interaction Events)
CVE- Interface 26 Transit Vehicle Transit Vehicle OBU CAN Bus Data Local IX1641-V01 Databus
CVE- Interface 27 Transit Vehicle OBU Transit CV Transit Vehicle Interaction Over-The-Air (Wi- IX1642-V01 Management System Data Fi)
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 15 Chapter 2. System Description
Interface Communications ID Reference Source Element Destination Element Data Flow Media
CVE- Interface 28 Transit CV Transit CV Transit Vehicle Interaction UI IX1643-V01 Management System Management Staff Data
CVE- Interface 29 Emergency Vehicle Emergency Vehicle Signal Preempt UI IX1644-V01 OBU Operator Notification
270 Source: City of Columbus
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
16 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 2. System Description
271 To establish an organizational framework for CVE requirements, the proposed system described in 272 Section 5 of the ConOps was further refined, decomposed, and classified according to its functionality 273 (i.e. functional groups) and its major system components, as illustrated on the context diagrams in Figure 274 2: Connected Vehicle Environment System Breakdown Diagram. Table 4: Connected Vehicle 275 Environment System Functional Groups details the list of the functional groups resulting from 276 decomposing the CVE.
277 Table 4: Connected Vehicle Environment System Functional Groups
Ref # Functional Group High-Level Functionality
RSU Roadside Unit Relays CV data to/from vehicles and infrastructure elements
OBU Onboard Unit In-vehicle equipment that relays CV data to/from other vehicles and infrastructure and provides alerts/warnings to drivers (as applicable)
TSC Traffic Signal Controller Manages timing of traffic signals at intersections, reacting to requests for pre-empt/priority, as applicable
OS Operating System Data repository for all CV data captured. Source for Performance Measure calculations
TMC Traffic Management Centralized Management of all traffic signals. To be Center expanded to included management of CVE
TrMC Transit Management Repository for all Transit-related CV data as captured by Center OBU on transit vehicles
SCMS Security Credential Manages Digital Certificates used to ensure authenticated Management System message exchange
CORS Continuously Operating Source of GPS position correction information used in Reference Station conjunction with following
GNSS Global Navigation Primary source of location services provided to CV- Satellite System equipped vehicles
MAP MapData Message SAE J2735 2016:03 standard message for describing the geometry and layout of an intersection. Sent from RSU to OBU
SPAT Signal Phase and SAE J2735 2016:03 standard message for conveying the Timing Message current state and time remaining in a traffic signal phase.
SRM Signal Request SAE J2735 2016:03 standard message used by a vehicle Message to request preempt or priority service at a traffic signal.
SSM Signal Status Message SAE J2735 2016:03 standard message to provide current status of signal requests active or pending at a signalized location.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 17 Chapter 2. System Description
Ref # Functional Group High-Level Functionality
RSM Roadside Safety SAE J2945/4 work-in-progress version of standard Message message for conveying travel and roadway information. This is the expected replacement for the SAE J2735 TIM message.
RTCM Radio Technical SAE J2735 2016:03 standard message for conveying Commission for position correction information used by an OBU. Maritime Services Corrections Message
BSM Basic Safety Message SAE J2735 2016:03 standard message for conveying vehicle position, speed and trajectory info data
BSW Blind Spot Warning One of the suite of CV Applications to be employed in the Application CVE
EEBL Emergency Electronic One of the suite of CV Applications to be employed in the Brake Light Application CVE
EVP Emergency Vehicle One of the suite of CV Applications to be employed in the Preemption Application CVE
FCW Forward Collision One of the suite of CV Applications to be employed in the Warning Application CVE
FSP Freight Signal Priority One of the suite of CV Applications to be employed in the Application CVE
IMA Intersection Movement One of the suite of CV Applications to be employed in the Assist Application CVE
ITP Freight Intent to One of the suite of CV Applications to be employed in the Platoon Application CVE
LCW Lane Change Warning One of the suite of CV Applications to be employed in the Application CVE
TSP Traffic Signal Priority One of the suite of CV Applications to be employed in the Applications CVE
TVIER Transit Vehicle One of the suite of CV Applications to be employed in the Interaction Event CVE Recording
VDTO Vehicle Data for Traffic One of the suite of CV Applications to be employed in the Operations CVE
FMC Freight Management Management Center for Freight movement activities Center
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
18 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 2. System Description
Ref # Functional Group High-Level Functionality
PPCM Platooning Provider Management Center for Platoon coordination activities Central Management
RLVW Red Light Violation One of the suite of CV Applications to be employed in the Warning Application CVE
RSSZ Reduced Speed School One of the suite of CV Applications to be employed in the Zone Application CVE
TCVMS Traffic CV Management Management Center for CV activities System
TrCVMS Transit CV Management Center for Transit activities Management System
TSC Traffic Signal Controller Source of Signal Phase and Timing Data
APPS CV Applications CV Applications that use data generated in the CVE
278 Source: City of Columbus
279 System Modes and States
280 Because it is composed of multiple devices and potentially hosting several applications, the system mode 281 is viewed at a micro level. With devices deployed across the deployment area and outside the 282 deployment area (i.e., vehicles), viewing the deployment as a single system is not considered for the 283 purpose of defining modes. The mode will be composed of the status of a device, its ability to 284 communicate, and the operational status of the installed applications.
285 Devices have three modes:
286 Normal mode: A device and its applications are operating as required
287 Degradation mode: Something unexpected occurred and part of the device may not be 288 functioning as required
289 Error mode: a complete failure of the device including communication failure
290 Each Roadside Unit (RSU) or Onboard Unit (OBU) (referred to simply as a device when considered 291 generically as a DSRC-based unit) is considered to be in normal mode when the device is operating as 292 designed and the applications are functioning as designed. A device enters Degradation mode when 293 there is failure of one or more of the applications or a portion of the hardware fails. When an application 294 fails, data is not being received, processed or transmitted for those application(s). The other applications 295 continue to function as designed receiving, processing and transmitting data. When a portion of the 296 device hardware fails, the application may or may not be able to perform its functions. When a device 297 completely fails or loses the ability to communicate, it enters Error mode. OBUs’ modes cannot be 298 determined in real time. Mode changes by these devices will be discovered only when the vehicle’s data 299 is downloaded and only for those OBUs that will capture data. If there is a complete failure of the device,
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 19 Chapter 2. System Description
300 then it will be apparent that the device is nonoperational. If the device is operating, but one of the 301 applications has failed, this will be determined after the data has been downloaded and analyzed. OBU 302 failures may be determined more efficiently as drivers may notice the OBU is not functioning properly and 303 bring the vehicle in for OBU maintenance.
304 When determining the system state, the focus will be on the RSUs. These devices can provide a 305 heartbeat to the TMC that can be monitored. The OBUs are not considered when modeling and 306 determining the system state, as there is no reliable means to know if these devices are always operating 307 as required.
308 The three RSU device states are: Operational, Partial Failure and Failed.
309 When the device is operational, an RSU is known to be up and operating and in communication with the 310 TrCVMS via the appropriate network. Partial failure of an RSU indicates that the RSU is not operating as 311 required. An RSU is considered nonoperational when the communications with the RSU is down 312 (interrupted) or the RSU itself has some failure preventing it from operating normally. The RSU is 313 considered to be in a failed state when an RSU is inoperative.
314 Major System Characteristics
315 System Capabilities
316 The primary outcome of the CVE is deployment of technology both roadside and in vehicles to enable 317 communication between vehicles and between vehicles and roadside ITS equipment. The CV technology 318 will provide information that will help to reduce crashes along the target corridors, improving safety for 319 light-duty vehicle operators, transit vehicle operators, passengers, and public safety personnel.
320 The CVE will further maintain the safe and efficient movement of transit, freight, and emergency vehicles. 321 Signal priority at intersections will allow a bus to receive early or extended green time to maintain its 322 schedule. A freight priority capability at select signalized intersections will improve freight mobility and 323 consequently deliver goods faster and more efficiently. With the new freight platoons that will be 324 introduced on the region’s roadways, it will be critical to implement a specialized version of this priority 325 capability that adjusts signal timing to improve platoon mobility and prevent vehicles intending to platoon 326 from being separated while on surface roads. Furthermore, a signal preemption strategy will provide right- 327 of-way to emergency vehicles and allow safe, efficient passage through intersections.
328 The final capability is to provide the mechanisms to improve traffic management throughout the City of 329 Columbus. Ideally, the CVE will enable state and local agencies to collect low-cost, comprehensive, high- 330 quality data that can be used in conjunction with data collected from traditional and third-party sources to 331 support enhanced traffic management activities. Archiving select data from the CVE into Operating 332 System will further enhance the integration of transportation data into network management and long- 333 term transportation planning.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
20 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 2. System Description
334 System Conditions
335 The CVE is generally expected to perform under most conditions, securely and timely delivering data 336 to/from and between vehicles, allowing for the stated objectives of the project to be met. Situations that 337 may result in degraded or no performance include:
338 Loss of Power: A power outage that impacts the infrastructure elements of the environment will 339 prohibit the V2I applications from performing as expected.
340 Loss of Communications: Localized communications will be employed to ensure that loss of 341 communications will not adversely affect the interaction between the vehicles and infrastructure, 342 albeit there may be conditions whereby data collected from the CVE will not be forwarded to the 343 OS.
344 Device Failure: Device failures fall into one of two classes, the roadside equipment, specifically 345 the RSU, and the OBU.
346 Management provisions will be made to monitor the operation of the system’s infrastructure devices to 347 identify failures and resolve them. When RSUs fail, vehicle operators will not be notified and will operate 348 their vehicles normally without alerts or alarms from the OBUs for V2I applications. In this state, the V2V 349 applications will continue to function and provide alerts or alarms in the presence of other CVs (if their 350 OBUs are also functioning properly). Such fail conditions in the CV devices may result in safety-related 351 implications such as inability to issue alerts. Furthermore, this may lead to insufficient or inaccurate data 352 and safety benefit analysis of the system.
353 Light-Duty Vehicle (LDV) Operators with HMIs need to be informed when vehicles start that their vehicle 354 resident OBU is operating properly. Failed OBUs will not prevent the safe operation of the vehicle by the 355 LDV Operator; the LDV operator will not receive alerts or alarms from the device when it has failed. 356 Support personnel will have to be notified by the LDV Operator to begin the repair process.
357 System Constraints
358 System Constraints of the CVE can be grouped in several distinct categories which include equipment 359 selection, network security and operations, user privacy and data collection, and impact to traffic 360 operations.
361 Smart Columbus and the CVE serves as a deployment of CV technology. Thus, the choice of devices to 362 be deployed and the configuration of these devices are limited versus what might be expected for the CV 363 Pilots. Specifically, and as noted in the ConOps, only applications which have met technology readiness 364 level 6, or for which there is invaluable need were selected for inclusion. It is fully expected that DSRC will 365 be deployed as the wireless interface. Roadside Units will support bi-directional communications with 366 vehicles via the DSRC interface, but are not required to include Wi-Fi, Bluetooth or any other wireless 367 technology. Likewise, OBUs will be limited in the data they collect and the methods for both disseminating 368 information to the LDV Operator, as well as capturing data from the Transit Vehicle On-board Unit (OBU). 369 Only LDVs are expected to have a human-machine interface (HMI). Only Transit Vehicles belonging to 370 the transit agency, COTA, are expected to log onboard events. All other data capture will be via the active 371 J2735 messages, such as BSM, SPaT, MAP, RSM, SSM, SRM and RTCM.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 21 Chapter 2. System Description
372 The City has deployed several hundred miles of fiber and is in the process of connecting nearly every 373 traffic signal controller in the Columbus region to this network. The CVE will be connected to many of 374 these same traffic signal controllers. Presently, the traffic signal controller network is a private, internal 375 DPS network. The CVE requires access to external, public resources, including SCMS, CORS and the 376 Smart Columbus Operating System. Connecting the existing controller network to CVE will potentially 377 expose the controller to security risks associated with a public facing interface. Thus, the CVE must 378 implement an architecture that isolates it from the existing network, providing a reasonable assurance 379 that the former will not compromise the latter. This may require upgrading field equipment, installing 380 additional and possibly redundant equipment, and using spare communications links.
381 Throughout all meetings with the project stakeholders, the stakeholders expressed that privacy must be 382 maintained. Time and location information constitutes potentially Personally Identifiable Information (PII) 383 because it could be merged with other records (e.g., police crash reports) and used in legal proceedings, 384 disciplinary proceedings, or insurance negotiations. Keeping data with this time/location information is a 385 potential infringement of an individual’s privacy. The Smart Columbus Data Privacy Plan and Data 386 Management Plan address specific methods to handle this, but given the limited data collection available, 387 all data generated will be captured and handled accordingly.
388 Signal preemption and priority have potential impact on traffic operations and as it is not the goal of Smart 389 Columbus to necessarily demonstrate that preempt or priority have an overall positive net effect to the 390 transportation network. The CVE is focused on demonstrating that the technology can support this 391 function. The City may decide to limit or eliminate specific locations or corridors planned to support 392 preempt/prioritization, it may also require additional, conditional elements not presently specified.
393 User Characteristics
394 This section defines the stakeholders, user classes, and their roles and responsibilities for the CVE. 395 Stakeholders refers to an individual or organization affected by the activities, inputs and outputs of the 396 system being developed. They may have a direct or indirect interest in the system and their level of 397 participation may vary. This includes public agencies, private organizations or the traveling public (end 398 users) with a vested interest or "stake" in one or more aspects of the CVE as identified in Table 5: 399 Connected Vehicle Environment Stakeholders and User Classes. User Classes are classified based 400 on their perception of the system and the needs identified. Note that some key personnel may serve in 401 multiple roles based on the user needs and functions.
402 Table 5: Connected Vehicle Environment Stakeholders and User Classes
User Classes
Target Stakeholders
Operator
Duty
Manager
-
Duty Vehicle
-
Light Operator EmergencyVehicle Operator Heavy Vehicle Traffic TransitVehicle Operator TransitManager NetworkManager
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
22 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 2. System Description
User Classes
Linden Private Vehicle Owners* X ------
City of Columbus Light-Duty Vehicle Operators, Car Share Vehicle X ------Operators**
Logistics Company #1, - - X - - - - Logistics Company #2
COTA (Fixed-Route and CEAV) - - - - X X -
COTA (Supervisor Vehicle) X ------
City of Columbus Fire, Emergency - X - - - - - Medical Services (EMS)
City of Columbus Police - X - - - - -
City of Columbus Dept. of Public - - - X - - - Service Traffic Managers
City of Columbus Department of ------X Technology (DoT)
403 *Note: Linden residents are the target audience for privately-owned vehicles. Outreach can be done for other residents near CV 404 corridors if additional participation is needed to satisfy in-vehicle installation objectives.
405 ** Note: Car2Go, the only car-share entity operating in Columbus ended its service in the area on May 31, 2018. Should other 406 carshare providers provide service in the area, they could be considered a potential stakeholder for the light-duty vehicle operator 407 user class.
408 Source: City of Columbus
409 Light-Duty Vehicle Operator
410 The Light-Duty Vehicle operator user class is comprised of Linden Private Vehicle Owners, City of 411 Columbus Light-Duty Vehicle Operators, Car Share Vehicle Operators, and COTA Supervisor Vehicle 412 Operators. City of Columbus light-duty fleet includes vehicles such as: construction inspection vehicles, 413 DPS pool vehicles, infrastructure management vehicles, building and zoning inspections vehicle, signage 414 and pavement supervisor vehicles, and traffic management vehicles. In the context of the CVE, light-duty 415 vehicle operators are expected to use the Cleveland Avenue, High Street, and Morse Road corridors as 416 part of their typical routines. As identified in Chapter 1, these three corridors are responsible for a large 417 number of crashes and contain several of the most dangerous intersections in the Columbus area. While 418 using these corridors, it is expected that light-duty vehicle operators are exercising awareness in the 419 roadway environment to avoid unsafe situations.
420 Emergency Vehicle Operator
421 The Emergency Vehicle Operator user class is comprised of City of Columbus Fire, EMS and Police, and 422 must navigate the roadway network to respond to emergencies throughout the city. When actively 423 responding to calls, these vehicle operators engage flashing lights and sirens to make their presence
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 23 Chapter 2. System Description
424 known to other vehicles on the roadway. In response to the lights and sirens, other drivers are expected 425 to yield to the emergency vehicles (and to provide a clear path by pulling over or stopping at 426 intersections) so that the emergency vehicle operator can reach the destination as quickly as possible.
427 Heavy-Duty Vehicle Operator
428 The Heavy-Duty Vehicle Operator user class is comprised of drivers that operate heavy-duty freight 429 vehicles for local freight companies. With regard to the current system, one of the logistics companies 430 moves freight along the Alum Creek Corridor, to I-270, to Morse Road, east of I-270. The other logistic 431 company moves freight from Trabue Road, to Wilson Road, to I-70, and SR-209 in Byesville. Moving 432 freight in an expedient and efficient manner is very important for heavy-duty vehicle operators and the 433 logistics companies they represent.
434 Traffic Manager
435 City of Columbus DPS Traffic Managers represents the Traffic Manager user class. The Traffic Manager is 436 responsible for actively managing the transportation devices which allows them to modify the operations 437 of traffic control devices (such as traffic signal timing) to improve network efficiency. DPS Traffic 438 Managers currently use CCTV cameras to monitor traffic conditions. Based on conditions that are 439 observed, one of several signal timing plans are implemented to alleviate the congestion that is occurring. 440 The Traffic Manager is also responsible for the operations and maintenance of transportation network- 441 connected devices. This includes, but is not limited to CCTVs, traffic signal controllers, and switches 442 located in traffic signal cabinets.
443 Transit Vehicle Operator
444 The Transit Vehicle Operator user class is comprised of COTA fixed-route and paratransit vehicle 445 operators. These operators are responsible for servicing COTA passengers along their designated routes.
446 Transit Manager
447 The Transit Manager user class is represented by COTA Transit Managers. The transit manager is 448 responsible for making sure that transit vehicles run on-schedule, and for evaluating systems currently 449 on-board transit vehicles and potential future on-board transit vehicle systems to determine if they can 450 provide a benefit to the transit vehicle operator or to passengers. Because the transit vehicle operator 451 must safely operate the vehicle, only a limited number of outputs from these systems can be provided to 452 the transit vehicle operator without causing a distraction and reducing safety. The transit manager can 453 evaluate the outputs that may be provided from a new system to determine if it should be implemented.
454 Network Manager
455 The Network Manager user class is represented by the City of Columbus DoT. They are responsible for 456 operating and maintaining the fiber-optic network that is used to transmit data between networked 457 devices. The current system uses fiber-optic backhaul to provide connectivity between the TMC and 458 traffic signal controllers. The TMC uses the network to remotely specify modifications to traffic signal 459 timing plans when congested conditions are noted. It is the responsibility of the Network Manager to
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
24 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 2. System Description
460 establish network security protocols, enforce those protocols, and preserve connectivity or restore 461 connectivity when outages are experienced.
462 Assumptions and Dependencies
463 Table 6: Assumptions and Dependencies lists the known assumptions and dependencies that 464 represent a risk to the CVE project or system and can affect the ability to meet the desired functionality, 465 maintain the project schedule or meet performance goals.
466 Table 6: Assumptions and Dependencies
ID Assumption Corresponding Risk Dependency Degree
01 DSRC will be the DSRC will be replaced Continued availability of Low medium for over-the-air by competing DSRC-based equipment message transmission. technology
02 Position Correction will RTCM may be Quality of OBU GNSS Med-High be facilitated using insufficient to meet hardware and use of RTCM v3.0 Type project needs RTCM 1001/1005 messages
03 The SPaT Message will TSC without capability in SPaT Message Low be generated by the introduced into the CVE broadcast TSC
04 SCMS will be available City may need to pivot SCMS is critical for Medium from DriveOhio to alternative source secure operation of CVE
05 CV Applications will be App selection was Selection criteria must Low-Med available from selected based, in part, on be clear with OBU vendor availability and vendors readiness level.
467 Source: City of Columbus
468 System Constraints
469 Table 7: System Constraints lists the constraints on the system as defined by the concept of operations, 470 the contract or city/state policy. Requirements have been developed to support these constraints.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 25 Chapter 2. System Description
471 Table 7: System Constraints Constraint ID Reference Constraint
CVE- Constraint 1 DPS will provide deployment support CN1645- V01
CVE- Constraint 2 Equipment, software, processes, and interfaces shall comply CN1646- with IEEE and SAE standards as prescribed by one of the V01 USDOT approved certification entities.
CVE- Constraint 3 Equipment, software, processes, and interfaces shall be CN1647- tested for interoperability before deployment to ensure they V01 meet those standards for interoperability.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
26 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 2. System Description
Constraint ID Reference Constraint
CVE- Constraint 4 All CVE components (devices?) that utilize DSRC shall CN1648- comply with all of the following: 1. SAE J2735_201603 - V01 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- Constraint 5 A DSRC-Enabled LDV OBU shall be installed in private CN1649- vehicles V01
CVE- Constraint 6 A DSRC-Enabled LDV OBU shall be installed in DPS fleet CN1650- vehicles V01
CVE- Constraint 7 A DSRC-Enabled LDV OBU shall be installed in COTA CN1651- Supervisor vehicles V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 27 Chapter 2. System Description
Constraint ID Reference Constraint
CVE- Constraint 8 A DSRC-Enabled HDV OBU shall be installed in (platooning) CN1652- HDVs V01
CVE- Constraint 9 A DSRC-Enabled Transit Vehicle OBU shall be installed in CN1653- Transit Vehicles V01
CVE- Constraint 10 A DSRC-Enabled Transit Vehicle OBU shall be installed in CN1654- Paratransit Vehicles V01
CVE- Constraint 11 A DSRC-Enabled Transit Vehicle OBU shall be installed on CN1655- CEAVs V01
CVE- Constraint 12 A DSRC-Enabled Public Safety Vehicle OBU shall be installed CN1656- in Police Vehicles V01
CVE- Constraint 13 A DSRC-Enabled Public Safety Vehicle OBU shall be installed CN1657- in Fire Vehicles V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
28 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 2. System Description
Constraint ID Reference Constraint
CVE- Constraint 14 A DSRC-Enabled Public Safety Vehicle OBU shall be installed CN1658- in EMC Vehicles V01
CVE- Constraint 15 A DSRC-Enabled RSU will be installed at CV Environment CN1659- intersections (identified in ConOps) V01
CVE- Constraint 16 Safety applications that output an alert from an OBU shall be CN1660- commercial off the shelf software V01
CVE- Constraint 17 DPS will adhere to internal policies and best practices for CN1661- executing signal priority and signal preemption strategies V01
CVE- Constraint 18 DPS will limit the ability to receive signal priority or preemption CN1662- to a select vehicles V01
CVE- Constraint 19 DPS will operate and maintain the CVE CN1663- V01
CVE- Constraint 20 Performance measures will be used to assess the CVE CN1664- V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 29 Chapter 2. System Description
Constraint ID Reference Constraint
CVE- Constraint 21 An RSU shall adhere to the DSRC Roadside Unit (RSU) CN1665- Specifications Document v4.1 (October 2016) V01
472 Source: City of Columbus
473 Operational Scenarios
474 Chapter 6 of the Concept of Operations for the Connected Vehicle Environment project for the Smart 475 Columbus Demonstration Program – City of Columbus, Ohio captures and documents the operational 476 scenarios.
477
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
30 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
478 Chapter 3. System Requirements
479 This section of the document lists the identified requirements for the Connected Vehicle Environment. The 480 requirements are organized first by requirement type, then by system and services (i.e. functional 481 requirements (FR) for functional group 1, then FR for functional group 2, etc.). The requirements tables in 482 this section include a column for the requirement identifier, description, a reference, and verification 483 method. Each requirement type has a requirement identifier - Appendix A. Document Terminology and 484 Conventions provides an overview of the method that is used to build the requirement identifier. The next 485 column provides the requirement description, which is intended to be well-formed as specified by the 486 Systems Engineering Guide for Intelligent Transportation Systems4: necessary, clear, complete, correct, 487 feasible, and verifiable. The reference number identifies traceability to user needs, user scenarios, other 488 (parent) requirements, and/or policies and constraints. The final column provides the verification method – 489 the four fundamental verification methods considered include: inspection, demonstration, test, and 490 analysis. Definitions of these methods are provided in Methods of Verification in Chapter 4. 491 Engineering Principles. Table 8: List of Requirement Types describes the classifications of the 492 requirements in this document.
493 Table 8: List of Requirement Types
Type Description
Functional (FN) The Functional requirements specify actionable and qualitative behaviors (e.g. functions, tasks) of the core system of interest, which in the case of CVE includes the roadside infrastructure, including RSUs; as well as in-vehicle units.
Performance (PR) The Performance requirements specify quantifiable characteristics of operations that define the extent, or how well, and under what conditions a function or task is to be performed (e.g. rates, velocities).
Interfaces (IF) The Interface requirements define how the system will interact, communicate, or exchange data with external systems (external interface) and how core system elements interact with other parts of the system (internal interface).
Data (DR) The Data requirements define the data collected, transformed, and stored from various sources as well as identifies new data that is expected to be generated.
Security (SR) The Security requirements specify what is necessary to protect the integrity and operability of the system, its microservices, connections, and data. This includes physical security as well as cyber prevention, detection, identification, response and recovery requirements.
4 https://ops.fhwa.dot.gov/publications/seitsguide/seguide.pdf
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 31 Chapter 3. System Requirements
Type Description
Policy and The Policy and Regulation requirements specify relevant and applicable Regulation (RG) organizational policies or regulations that affect the development, operation or performance of the system (e.g. IT and labor policies, reports to regulatory agencies, health or safety criteria, etc.). This section also includes new policy and regulation imposed to realize the system.
Non-Functional (NF) The Non-Functional requirements define the characteristics of the overall operation of the system, including the following: Physical (PY) – specifies the construction, durability, adaptability and environmental characteristics of the system Availability and Recovery (AR) – define the times of day, days of year, and overall percentage the system can be used and when it will not be available for use as well as recovery point and time objectives. Maintainability (MT) – specify the level of effort required to locate and correct an error during operation. Storage and Transport (ST) – specify the physical location and environment for the system, including designated storage facility, installation site, repair facility, requirements for transporting equipment, etc. Disposal (DP) – specify the items related to the disposal of project/system components, due to either failure replacements, removal, end-of-life upgrade, or retirement.
Enabling (EN) The Enabling requirements specify details concerning the management of information as well as the production of the system and its life cycle sustainment, including the following: Information Management (IM) – specify the acquisition, management, and ownership of information from one or more sources, the custodianship and the distribution of that information to those who need it. Life Cycle Sustainability (LC) – define what items the project or system will review, measure, and analyze as part of its commitment to quality during the life cycle of the system, including development, integration, verification, validation, and training.
494 Source: City of Columbus
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
32 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
495 Functional Requirements
496 This section provides the high-level requirements for the system of interest (i.e. what the system will do). The requirements in Table 9: Functional 497 Requirements are organized by the functional groups and are related to the user needs identified the project ConOps identified.
498 Table 9: Functional Requirements Verification ReqID Functional Group Sub-Component Description References Method CVE- Roadside Roadside Unit An RSU shall obtain position correction CVE-SN860-v02 Demonstration FN1113-V01 Equipment information from a Continuously Operating CVE-IX1628-V01 Reference Station (CORS) for packaging and broadcasting as the RTCM message. CVE- Roadside Roadside Unit An RSU shall acquire time from the LTS CVE-SN850-v02 Demonstration FN1308-V01 Equipment interface in accordance with J2945/1 CVE-IX1625-V01 section 6.2.4. CVE-CN1648-V01
CVE- Roadside Roadside Unit An RSU shall acquire location from the LTS CVE-SN860-v02 Demonstration FN1309-V01 Equipment interface in accordance with J2945/1 CVE-IX1625-V01 section 6.2.1. CVE-CN1648-V01 CVE- Roadside Roadside Unit An RSU shall broadcast (school zone) CVE-UN140-v02 Demonstration FN1310-V01 Equipment RSMs to an LDV OBU when configured to CVE-UN610-v02 perform this function. CVE-IX1620-V01 CVE-IX1620-V01
CVE- Roadside Roadside Unit An RSU shall use Coordinated Universal CVE-CN1648-V01 Demonstration FN1311-V01 Equipment 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.
CVE- Roadside Roadside Unit An RSU shall have access to a function that CVE-UN130-v02 Demonstration FN1312-V01 Equipment generates SPaT messages from SPaT data CVE-FN1557-V01 inputs CVE-FN1558-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 33 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Roadside Roadside Unit An RSU shall have access to a function that CVE-UN130-v02 Demonstration FN1313-V01 Equipment generates RTCM messages from RTCM CVE-UN220-v02 data inputs CVE-UN310-v02 CVE-UN320-v02 CVE-UN510-v02 CVE-UN610-v02 CVE-FN1560-V01 CVE- Roadside Roadside Unit An RSU shall have access to a function that CVE-UN220-v02 Demonstration FN1314-V01 Equipment generates SSM messages from SSM data CVE-UN310-v02 inputs CVE-UN320-v02 CVE-UN510-v02 CVE-FN1563-V01 CVE- Roadside Roadside Unit An RSU shall comply with IEEE 1609.2: CVE-CN1648-V01 Demonstration FN1315-V01 Equipment Standard for WAVE Security Services for Applications and Management Messages CVE- Roadside Roadside Unit Select RSUs in/around designated school CVE-UN610-v02 Demonstration FN1316-V01 Equipment zones (Linden STEM Academy and Our Lady of Peace School) shall broadcast RSMs received from the Traffic CV Management System. CVE- Roadside Roadside Unit RSU functionality failure shall not affect the CVE-CN1659-V01 Demonstration FN1317-V01 Equipment safe operation of the signal controller. CVE- Roadside Roadside Unit All roadside equipment (including RSUs) CVE-IX1635-V01 Demonstration FN1318-V01 Equipment shall support remote authenticated access. CVE- Roadside Roadside Unit An RSU shall broadcast the WSA for CVE-SN870-v02 Demonstration FN1319-V01 Equipment certificate download on control channel 178 CVE-IX1610-V01 and indicate IPv6 connectivity and the IP address on a service channel other than channel 172 or 178. CVE- Roadside Roadside Unit An RSU shall implement a firewall blocking CVE-UN710-v02 Demonstration FN1320-V01 Equipment all IP access from devices to any IP CVE-IX1626-V01 address other than those approved for CVE-IX1628-V01 specific applications.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
34 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Roadside Roadside Unit An RSU shall support IPv6 tunneling over CVE-UN710-v02 Demonstration FN1321-V01 Equipment IPv4. CVE-IX1626-V01 CVE-IX1628-V01 CVE- Roadside Roadside Unit An RSU shall report over a management CVE-UN710-v02 Demonstration FN1322-V01 Equipment interface if channel busy ratios go above a configurable threshold. CVE- Roadside Roadside Unit An RSU shall delete old certificates upon CVE-SN820-v02 Demonstration FN1323-V01 Equipment location change. CVE-CN1663-V01 CVE- Roadside Roadside Unit An RSU shall support setting the certificate CVE-SN820-v02 Demonstration FN1324-V01 Equipment geographic region to be requested for CVE-CN1663-V01 application certificates. CVE- Roadside Roadside Unit It shall be possible for a system CVE-SN820-v02 Demonstration FN1325-V01 Equipment administrator with the appropriate CVE-CN1663-V01 permissions to configure the RSU to request application certificates with only designated geographic locations. CVE- Roadside Roadside Unit The CVE shall provide an interface to allow CVE-IX1634-V01 Demonstration FN1327-V01 Equipment the system administrator to request new certificates bound to the new location if it moves from one location to another. (Note: its interface will allow requesting a new RSU application certificate with a site.) CVE- Roadside Roadside Unit An RSU shall communicate using SNMPv3 CVE-IX1635-V01 Demonstration FN1328-V01 Equipment with SNMP messages protected by being sent over TLS. CVE- Roadside Roadside Unit An RSU shall support establishment of a CVE-IX1635-V01 Demonstration FN1329-V01 Equipment standard TLS-based VPN with client authentication for communication to the Traffic CV Management System, with a long-term client cert and a single CA cert trusted to authorize connections from the Traffic CV Management System. CVE- Roadside Roadside Unit An RSU shall verify received messages per CVE-CN1648-V01 Demonstration FN1330-V01 Equipment IEEE 1609.2 and per the relevant security CVE-IX1609-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 35 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method profiles before using them for operations in CVE-IX1616-V01 any application. CVE-IX1619-V01 CVE- Roadside Roadside Unit An RSU shall provide tamper evidence to CVE-UN430-v02 Demonstration FN1331-V01 Equipment detect tampering of the device (e.g. opening of the case). CVE- Roadside Roadside Unit An RSU shall require that 1609.2 signed CVE-SN820-v02 Demonstration FN1332-V01 Equipment messages are signed by a certificate that is CVE-CN1648-V01 protected from modification by, or chains back to a certificate that is protected from modification by, the secure boot process. CVE- Roadside Roadside Unit An RSU shall not create or transmit CVE-SN820-v02 Demonstration FN1333-V01 Equipment messages for any usage scenario if the CVE-CN1648-V01 usage scenario requires it to use 1609.2 certificates and it does not currently have valid certificates for that usage scenario CVE- Roadside Roadside Unit An RSU shall verify a DSRC message if a CVE-SN820-v02 Demonstration FN1334-V01 Equipment device identifies the message as containing a new DE_TemporaryID value. CVE- Roadside Roadside Unit An RSU supplier shall provide the CVE-CN1645-V01 Demonstration FN1335-V01 Equipment enrollment certificate for each RSU. CVE- Roadside Roadside Unit An RSU shall verify a DSRC message if the CVE-SN820-v02 Demonstration FN1336-V01 Equipment message results in the issuance of issue either advisory, warning, or alert CVE- Roadside Roadside Unit An RSU shall verify a DSRC message if the CVE-SN820-v02 Demonstration FN1337-V01 Equipment remote vehicle constitutes a potential threat (define potential threat as a vehicle that may collide with the host vehicle based on the both vehicle's speeds and trajectories) CVE- Roadside Roadside Unit An RSU shall verify a DSRC message if CVE-SN820-v02 Demonstration FN1338-V01 Equipment other potential threat situations such as red- light violations, and other safety applications.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
36 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Roadside Roadside Unit An RSU shall broadcast (school zone) Demonstration FN2972-V01 Equipment RSMs to a Transit Vehicle OBU when configured to perform this function. CVE- Roadside Roadside Unit An RSU shall broadcast MAP messages Demonstration FN2973-V01 Equipment loaded on the RSU to an HDV OBU CVE- Roadside Roadside Unit An RSU shall send RTCM messages Demonstration FN2979-V01 Equipment received from the CORS or other source to an HDV OBU CVE- Roadside Roadside Unit An RSU shall send RTCM messages Demonstration FN2980-V01 Equipment received from the CORS or other source to a Transit Vehicle OBU CVE- Roadside Roadside Unit An RSU shall send RTCM messages Demonstration FN2981-V01 Equipment received from the CORS or other source to an EV OBU CVE- Roadside Roadside Unit An RSU shall send SPaT messages Demonstration FN2982-V01 Equipment generated from SPaT data output from the controller to an HDV OBU CVE- Roadside Roadside Unit An RSU shall send SPaT messages Demonstration FN2983-V01 Equipment generated from SPaT data output from the controller to a Transit Vehicle OBU CVE- Roadside Roadside Unit An RSU shall receive BSMs from an HDV Demonstration FN2987-V01 Equipment OBU CVE- Roadside Roadside Unit An RSU shall receive BSMs from a Transit Demonstration FN2988-V01 Equipment Vehicle OBU CVE- Roadside Roadside Unit An RSU shall receive BSMs from an Demonstration FN2989-V01 Equipment Emergency Vehicle OBU CVE- Roadside Roadside Unit An RSU shall receive SRMs from a Transit Demonstration FN2990-V01 Equipment Vehicle OBU CVE- Roadside Roadside Unit An RSU shall receive SRMs from an Demonstration FN2991-V01 Equipment Emergency Vehicle OBU CVE- Roadside Roadside Unit The RSU shall be able to send the SSM at Demonstration FN3000-V01 Equipment a configurable rate CVE- Traffic Management Traffic CV The Traffic CV Management System shall CVE-UN410-v02 Demonstration FN1437-V01 Center Management System transmit performance metrics (as defined in CVE-IX1639-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 37 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method the Performance Measurement Plan) CVE-SN810-v02 derived from BSMs to the Smart Columbus OS CVE- Traffic Management Traffic CV The Traffic CV Management System shall CVE-UN410-v02 Demonstration FN1438-V01 Center Management System send PII-removed RSMs to the Smart CVE-IX1639-V01 Columbus OS CVE-SN810-v02 CVE- Traffic Management Traffic CV The Traffic CV Management System shall CVE-UN410-v02 Demonstration FN1439-V01 Center Management System send MAP messages to the Smart CVE-IX1639-V01 Columbus OS CVE-SN810-v02 CVE- Traffic Management Traffic CV The Traffic CV Management System shall CVE-UN430-v02 Demonstration FN1440-V01 Center Management System enable loading of RSMs on the RSU CVE- Traffic Management Traffic CV The Traffic CV Management System shall CVE-UN430-v02 Demonstration FN1441-V01 Center Management System enable loading of MAP messages on the CVE-IX1636-V01 RSU CVE- Traffic Management Traffic CV The Traffic CV Management System shall CVE-UN430-v02 Demonstration FN1442-V01 Center Management System accept input for RSM messages from Traffic CVE-IX1611-V01 Management Staff CVE-UN420-v02 CVE- Traffic Management Traffic CV The Traffic CV Management System shall CVE-UN430-v02 Demonstration FN1443-V01 Center Management System accept input for MAP messages from Traffic CVE-IX1611-V01 Management Staff CVE-UN420-v02 CVE- Traffic Management Traffic CV The Traffic CV Management System shall CVE-UN430-v02 Demonstration FN1444-V01 Center Management System accept input for configurable parameters CVE-IX1611-V01 from Traffic Management Staff CVE-UN420-v02
CVE- Traffic Management Traffic CV The Traffic CV Management System shall CVE-UN430-v02 Demonstration FN1445-V01 Center Management System make the status of RSUs available to Traffic CVE-IX1611-V01 Management Staff
CVE- Traffic Management Traffic CV The Traffic CV Management System shall CVE-UN410-v02 Demonstration FN1446-V01 Center Management System provide the VISA' functions of Validation, Integration, Sanitization (De-identification), and Aggregation of CV Data as defined in the U.S DOT SEMI ODE requirements (Reference TBR)
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
38 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Traffic Management Traffic CV The Traffic CV Management System shall CVE-UN430-v02 Demonstration FN1447-V01 Center Management System have access to a function that generates CVE-UN420-v02 RSM messages from RSM data inputs CVE- Traffic Management Traffic CV The Traffic CV Management System shall CVE-UN430-v02 Demonstration FN1448-V01 Center Management System have access to a function that generates CVE-UN420-v02 MAP messages from MAP data inputs
CVE- Traffic Management Traffic CV The Traffic CV Management System shall CVE-UN430-v02 Demonstration FN1449-V01 Center Management System monitor the status of RSUs CVE- Traffic Management Traffic CV The Traffic CV Management System shall CVE-UN430-v02 Demonstration FN1450-V01 Center Management System alert the Traffic Manager if an RSU is offline CVE- Traffic Management Traffic CV The Traffic CV Management System shall CVE-UN430-v02 Demonstration FN1451-V01 Center Management System alert the Traffic Manager if an RSU is not running normally (off, not responding, in safe mode, etc.) CVE- Traffic Management Traffic CV The Traffic CV Management System shall CVE-UN430-v02 Demonstration FN1452-V01 Center Management System make the status of all RSUs available to the Traffic Manager CVE- Traffic Management Traffic CV The Traffic CV Management System should CVE-UN410-v02 Demonstration FN1453-V01 Center Management System automate the generation of performance metrics as defined in the Performance Management Plan (TBD) CVE- Traffic Management Traffic CV The Traffic CV Management System should CVE-UN410-v02 Demonstration FN1454-V01 Center Management System use CV data made available through the CV Environment to generate performance metrics as defined in the Performance Management Plan (TBD) CVE- Traffic Management Traffic CV The Traffic CV Management System shall CVE-UN410-v02 Demonstration FN1455-V01 Center Management System upload performance metrics to the Smart CVE-SN810-v02 Columbus OS CVE- Traffic Management Traffic CV The Traffic CV Management System shall CVE-IX1635-V01 Demonstration FN1456-V01 Center Management System receive BSMs from the RSU CVE- Traffic Management Traffic CV The Traffic CV Management System shall CVE-PR1105-V01 Demonstration FN1463-V01 Center Management System monitor tamper alert devices CVE-FN1503-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 39 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE-FN1504-V01 CVE-FN1505-V01 CVE-FN1506-V01 CVE-FN1508-V01 CVE-FN1566-V01 CVE-FN1480-V01 CVE-UN430-v02 CVE-PR1105-V01
CVE- Traffic Management Traffic CV The Traffic CV Management System shall CVE-UN430-v02 Demonstration FN1464-V01 Center Management System alert the Traffic Manager when a tamper alert device detects that a traffic signal controller cabinet has been opened (or disturbed?) CVE- Traffic Management Traffic CV The Traffic CV Management System shall Demonstration FN2909-V01 Center Management System generate performance metrics (as defined in the Performance Measurement Plan) from data contained in CV messages that are captured. CVE- Traffic Management Traffic CV The Traffic CV Management System shall Demonstration FN2911-V01 Center Management System remove PII from BSMs that are received before further processing CVE- Traffic Signal Intent to Platoon An RSU shall determine if SRMs received CVE-UN320-v02 Demonstration FN1485-V01 Priority Applications Priority from multiple freight vehicles are intending to form a platoon CVE- Traffic Signal Intent to Platoon An RSU should use data received from the CVE-UN320-v02 Demonstration FN1486-V01 Priority Applications Priority Platooning System to determine if the HDV OBUs sending SRMs intend to form a platoon CVE- Traffic Signal Intent to Platoon An RSU shall consider the priority requests CVE-UN320-v02 Demonstration FN1487-V01 Priority Applications Priority from both HDV OBUs as a single priority request that is able to accommodate priority for both vehicles through the intersection if it
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
40 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method is determined that the vehicles intend to platoon CVE- Transit Transit CV The Transit CV Management System shall CVE-CN1664-V01 Demonstration FN1466-V01 Management Management System collect interaction data to generate the TBD Center performance measure (for Transit Vehicle Interaction Event Recording) CVE- Transit Transit CV The Transit CV Management System shall CVE-CN1664-V01 Demonstration FN1467-V01 Management Management System collect data to generate the on-time CVE-DR1402-V01 Center performance measure (for Transit Signal CVE-DR1403-V01 Priority) CVE-DR1404-V01 CVE-DR1405-V01 CVE-DR1406-V01 CVE-DR1407-V01 CVE-DR1408-V01 CVE-DR1409-V01 CVE-DR1410-V01 CVE-DR1411-V01 CVE-DR1412-V01 CVE-DR1413-V01 CVE-DR1414-V01 CVE-DR1415-V01 CVE-DR1416-V01 CVE-DR1417-V01 CVE-DR1418-V01 CVE-DR1419-V01 CVE- Transit Transit CV The Transit CV Management System shall CVE-CN1664-V01 Demonstration FN1468-V01 Management Management System collect data to generate the running time Center performance measure (for Transit Signal Priority) CVE- Transit Transit CV The Transit CV Management System shall CVE-CN1664-V01 Demonstration FN1469-V01 Management Management System collect data to generate the headway Center reliability performance measure (for Transit Signal Priority)
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 41 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Transit Transit CV The Transit CV Management System may CVE-CN1664-V01 Demonstration FN1470-V01 Management Management System use COTA CAD/AVL data to generate CVE-DR1420-V01 Center performance measures CVE-DR1421-V01 CVE-DR1422-V01 CVE-DR1423-V01 CVE-DR1424-V01 CVE-DR1425-V01 CVE-DR1426-V01 CVE-DR1427-V01 CVE-DR1428-V01 CVE-DR1429-V01 CVE-DR1430-V01 CVE-DR1431-V01 CVE-DR1432-V01 CVE-DR1433-V01 CVE-DR1434-V01 CVE-DR1435-V01 CVE-DR1436-V01 CVE- Transit Transit CV The Transit CV Management System may CVE-CN1664-V01 Demonstration FN1471-V01 Management Management System use user surveys to generate performance Center measures CVE- V2I Mobility Emergency Vehicle An Emergency Vehicle OBU shall request CVE-UN220-v02 Demonstration FN1493-V01 Preemption to receive signal preemption at RSU- equipped intersections CVE- V2I Mobility Emergency Vehicle The EVP application (see Appendix B) CVE-UN220-v02 Demonstration FN1497-V01 Preemption should employ algorithms that are used in CVE-CN1660-V01 MMITSS to enable emergency vehicle preemption CVE- V2I Mobility Emergency Vehicle A request to receive signal preemption from CVE-UN220-v02 Demonstration FN1500-V01 Preemption a Public Safety Vehicle OBU shall be high priority CVE- V2I Mobility Freight Signal Priority An HDV OBU shall request to receive CVE-UN310-v02 Demonstration FN1479-V01 signal priority at RSU-equipped CVE-FN1484-V01 intersections
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
42 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- V2I Mobility Freight Signal Priority An HDV OBU shall broadcast a SRM when CVE-PR1105-V01 Demonstration FN1480-V01 approaching an RSU-equipped intersection CVE-FN1503-V01 CVE-FN1504-V01 CVE-FN1505-V01 CVE-FN1506-V01 CVE-FN1508-V01 CVE-FN1566-V01 CVE-FN1463-V01 CVE-UN310-v02 CVE-PR1105-V01 CVE- V2I Mobility Freight Signal Priority An HDV OBU shall broadcast a SRM when CVE-UN310-v02 Demonstration FN1481-V01 it is within a configurable distance of the intersection it intends to request priority for CVE- V2I Mobility Freight Signal Priority An HDV OBU shall only request priority for CVE-UN310-v02 Demonstration FN1482-V01 movements along the designated freight route CVE- V2I Mobility Freight Signal Priority An HDV OBU shall only request priority in a CVE-UN310-v02 Demonstration FN1483-V01 SRM CVE- V2I Mobility Freight Signal Priority An HDV OBU shall cease broadcasting CVE-FN1479-V01 Demonstration FN1484-V01 SRMs for priority at a given intersection for a configurable amount of time after it has received an SSM from that intersection that contains the HDV OBU ID CVE- V2I Mobility Freight Signal Priority A request to receive signal priority from an CVE-UN310-v02 Demonstration FN1502-V01 HDV Vehicle OBU shall be low priority CVE-UN320-v02
CVE- V2I Mobility General The SRM shall contain the intersection ID CVE-UN310-v02 Demonstration FN1498-V01 Priority/Preemption that is provided in the MAP message for the CVE-UN320-v02 priority requested intersection CVE-UN510-v02 CVE-UN220-v02 CVE-UN520-v02 CVE- V2I Mobility General The SRM shall contain information CVE-UN310-v02 Demonstration FN1499-V01 Priority/Preemption regarding the movement for which priority is CVE-UN320-v02 being requested CVE-UN510-v02
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 43 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE-UN220-v02 CVE- V2I Mobility General High priority requests to receive signal CVE-PR1105-V01 Demonstration FN1503-V01 Priority/Preemption priority shall be serviced before low priority CVE-FN1504-V01 requests to receive signal priority CVE-FN1505-V01 CVE-FN1506-V01 CVE-FN1508-V01 CVE-FN1566-V01 CVE-FN1463-V01 CVE-FN1480-V01 CVE-UN310-v02 CVE-PR1105-V01 CVE-UN320-v02 CVE-UN510-v02 CVE-UN220-v02 CVE- V2I Mobility General Multiple high priority requests shall be CVE-PR1105-V01 Demonstration FN1504-V01 Priority/Preemption serviced in the order in which they are CVE-FN1503-V01 received CVE-FN1505-V01 CVE-FN1506-V01 CVE-FN1508-V01 CVE-FN1566-V01 CVE-FN1463-V01 CVE-FN1480-V01 CVE-UN310-v02 CVE-PR1105-V01 CVE-UN320-v02 CVE-UN510-v02 CVE-UN220-v02 CVE- V2I Mobility General Multiple low priority requests shall be CVE-PR1105-V01 Demonstration FN1505-V01 Priority/Preemption serviced in the order in which they are CVE-FN1503-V01 received CVE-FN1504-V01 CVE-FN1506-V01 CVE-FN1508-V01 CVE-FN1566-V01 CVE-FN1463-V01 CVE-FN1480-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
44 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE-UN310-v02 CVE-UN320-v02 CVE-PR1105-V01 CVE-UN510-v02 CVE-UN220-v02 CVE- V2I Mobility General An RSU shall use a locally-stored list of CVE-PR1105-V01 Demonstration FN1506-V01 Priority/Preemption vehicle OBU IDs that are authorized to CVE-FN1503-V01 receive signal priority at the intersection to CVE-FN1504-V01 determine if a received SRM is sent from an CVE-FN1505-V01 OBU that is authorized to make priority CVE-FN1508-V01 requests at that intersection CVE-FN1566-V01 CVE-FN1463-V01 CVE-FN1480-V01 CVE-UN320-v02 CVE-UN220-v02 CVE-PR1105-V01 CVE-CN1662-V01 CVE-UN510-v02 CVE-UN520-v02 CVE- V2I Mobility General An RSU shall use a locally-stored list of CVE-CN1662-V01 Demonstration FN1507-V01 Priority/Preemption vehicle OBU IDs that are authorized to receive signal preemption at the intersection to determine if a received SRM is sent from an OBU that is authorized to make preemption requests at that intersection CVE- V2I Mobility General An RSU shall place a priority request or a CVE-PR1105-V01 Demonstration FN1508-V01 Priority/Preemption preemption request to the traffic signal CVE-FN1503-V01 controller for the movement specified in the CVE-FN1504-V01 SRM if the following conditions are CVE-FN1505-V01 concurrently met: 1. An OBU ID (from the CVE-FN1506-V01 received SRM) matches against the locally- CVE-FN1566-V01 stored list of vehicle OBU IDs that are CVE-FN1463-V01 authorized to receive signal priority. 2. The CVE-FN1480-V01 CVE-UN310-v02
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 45 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method intersection ID in the SRM matches the CVE-UN320-v02 intersection ID CVE-PR1105-V01 CVE-UN510-v02 CVE-UN220-v02 CVE- V2I Mobility General The Traffic Signal Controller shall grant an CVE-UN310-v02 Demonstration FN1509-V01 Priority/Preemption early green for a phase for a movement that CVE-DR1378-V01 is requested in a priority SRM when the CVE-DR1379-V01 approach for that movement is red or yellow CVE-DR1380-V01 CVE-DR1381-V01 CVE-DR1382-V01 CVE-DR1383-V01 CVE-DR1384-V01 CVE-DR1385-V01 CVE-DR1386-V01 CVE-DR1387-V01 CVE-DR1388-V01 CVE-DR1389-V01 CVE-DR1390-V01 CVE-DR1391-V01 CVE-DR1392-V01 CVE-DR1393-V01 CVE-DR1394-V01 CVE-DR1395-V01 CVE-DR1396-V01 CVE-DR1397-V01 CVE-DR1398-V01 CVE-PR1399-V01 CVE-PR1400-V01 CVE-PR1401-V01 CVE-UN510-v02 CVE- V2I Mobility General The Traffic Signal Controller shall grant an CVE-UN310-v02 Demonstration FN1510-V01 Priority/Preemption extended green for a phase for a movement CVE-DR1378-V01 that is requested in a priority SRM when the CVE-DR1379-V01 approach for the requested movement is CVE-DR1380-V01 green CVE-DR1381-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
46 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE-DR1382-V01 CVE-DR1383-V01 CVE-DR1384-V01 CVE-DR1385-V01 CVE-DR1386-V01 CVE-DR1387-V01 CVE-DR1388-V01 CVE-DR1389-V01 CVE-DR1390-V01 CVE-DR1391-V01 CVE-DR1392-V01 CVE-DR1393-V01 CVE-DR1394-V01 CVE-DR1395-V01 CVE-DR1396-V01 CVE-DR1397-V01 CVE-DR1398-V01 CVE-PR1399-V01 CVE-PR1400-V01 CVE-PR1401-V01 CVE-UN510-v02 CVE- V2I Mobility General The Traffic Signal Controller shall not adjust CVE-CN1661-V01 Demonstration FN1511-V01 Priority/Preemption the typical progression of phases to CVE-DR1378-V01 accommodate a priority request CVE-DR1379-V01 CVE-DR1380-V01 CVE-DR1381-V01 CVE-DR1382-V01 CVE-DR1383-V01 CVE-DR1384-V01 CVE-DR1385-V01 CVE-DR1386-V01 CVE-DR1387-V01 CVE-DR1388-V01 CVE-DR1389-V01 CVE-DR1390-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 47 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE-DR1391-V01 CVE-DR1392-V01 CVE-DR1393-V01 CVE-DR1394-V01 CVE-DR1395-V01 CVE-DR1396-V01 CVE-DR1397-V01 CVE-DR1398-V01 CVE-PR1399-V01 CVE-PR1400-V01 CVE-PR1401-V01 CVE- V2I Mobility General The Traffic Signal Controller should CVE-CN1661-V01 Demonstration FN1512-V01 Priority/Preemption minimize the length of preceding phases to CVE-DR1144-V01 accommodate a priority request CVE-DR1145-V01 CVE-DR1146-V01 CVE-DR1147-V01 CVE-DR1148-V01 CVE-DR1149-V01 CVE-DR1150-V01 CVE-DR1151-V01 CVE-DR1152-V01 CVE-DR1153-V01 CVE-DR1154-V01 CVE-DR1155-V01 CVE-DR1156-V01 CVE-DR1157-V01 CVE-DR1158-V01 CVE-DR1159-V01 CVE-DR1160-V01 CVE-DR1161-V01 CVE-DR1162-V01 CVE-DR1163-V01 CVE-DR1164-V01 CVE-DR1165-V01 CVE-DR1166-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
48 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE-DR1167-V01 CVE-DR1168-V01 CVE-DR1169-V01 CVE-DR1170-V01 CVE-DR1171-V01 CVE-DR1172-V01 CVE-DR1173-V01 CVE-DR1174-V01 CVE-DR1175-V01 CVE-DR1176-V01 CVE-DR1177-V01 CVE-DR1178-V01 CVE-DR1179-V01 CVE-DR1180-V01 CVE-DR1181-V01 CVE-DR1182-V01 CVE-PR1183-V01 CVE- V2I Mobility General The Traffic Signal Controller should CVE-CN1661-V01 Demonstration FN1513-V01 Priority/Preemption immediately proceed to a pedestrian CVE-DR1144-V01 clearance phase if an active pedestrian CVE-DR1145-V01 phase is ongoing when servicing a priority CVE-DR1146-V01 or preemption request CVE-DR1147-V01 CVE-DR1148-V01 CVE-DR1149-V01 CVE-DR1150-V01 CVE-DR1151-V01 CVE-DR1152-V01 CVE-DR1153-V01 CVE-DR1154-V01 CVE-DR1155-V01 CVE-DR1156-V01 CVE-DR1157-V01 CVE-DR1158-V01 CVE-DR1159-V01 CVE-DR1160-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 49 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE-DR1161-V01 CVE-DR1162-V01 CVE-DR1163-V01 CVE-DR1164-V01 CVE-DR1165-V01 CVE-DR1166-V01 CVE-DR1167-V01 CVE-DR1168-V01 CVE-DR1169-V01 CVE-DR1170-V01 CVE-DR1171-V01 CVE-DR1172-V01 CVE-DR1173-V01 CVE-DR1174-V01 CVE-DR1175-V01 CVE-DR1176-V01 CVE-DR1177-V01 CVE-DR1178-V01 CVE-DR1179-V01 CVE-DR1180-V01 CVE-DR1181-V01 CVE-DR1182-V01 CVE-PR1183-V01 CVE- V2I Mobility General The Traffic Signal Controller shall not CVE-CN1661-V01 Demonstration FN1514-V01 Priority/Preemption reduce the duration of a pedestrian CVE-DR1144-V01 clearance interval before progressing to the CVE-DR1145-V01 next phase when servicing a priority or CVE-DR1146-V01 preemption request CVE-DR1147-V01 CVE-DR1148-V01 CVE-DR1149-V01 CVE-DR1150-V01 CVE-DR1151-V01 CVE-DR1152-V01 CVE-DR1153-V01 CVE-DR1154-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
50 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE-DR1155-V01 CVE-DR1156-V01 CVE-DR1157-V01 CVE-DR1158-V01 CVE-DR1159-V01 CVE-DR1160-V01 CVE-DR1161-V01 CVE-DR1162-V01 CVE-DR1163-V01 CVE-DR1164-V01 CVE-DR1165-V01 CVE-DR1166-V01 CVE-DR1167-V01 CVE-DR1168-V01 CVE-DR1169-V01 CVE-DR1170-V01 CVE-DR1171-V01 CVE-DR1172-V01 CVE-DR1173-V01 CVE-DR1174-V01 CVE-DR1175-V01 CVE-DR1176-V01 CVE-DR1177-V01 CVE-DR1178-V01 CVE-DR1179-V01 CVE-DR1180-V01 CVE-DR1181-V01 CVE-DR1182-V01 CVE-PR1183-V01 CVE- V2I Mobility General The Traffic Signal Controller shall next CVE-UN220-v02 Demonstration FN1515-V01 Priority/Preemption service a phase for a movement that is CVE-DR1144-V01 requested in a preemption SRM when the CVE-DR1145-V01 approach for the requested movement is CVE-DR1146-V01 red CVE-DR1147-V01 CVE-DR1148-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 51 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE-DR1149-V01 CVE-DR1150-V01 CVE-DR1151-V01 CVE-DR1152-V01 CVE-DR1153-V01 CVE-DR1154-V01 CVE-DR1155-V01 CVE-DR1156-V01 CVE-DR1157-V01 CVE-DR1158-V01 CVE-DR1159-V01 CVE-DR1160-V01 CVE-DR1161-V01 CVE-DR1162-V01 CVE-DR1163-V01 CVE-DR1164-V01 CVE-DR1165-V01 CVE-DR1166-V01 CVE-DR1167-V01 CVE-DR1168-V01 CVE-DR1169-V01 CVE-DR1170-V01 CVE-DR1171-V01 CVE-DR1172-V01 CVE-DR1173-V01 CVE-DR1174-V01 CVE-DR1175-V01 CVE-DR1176-V01 CVE-DR1177-V01 CVE-DR1178-V01 CVE-DR1179-V01 CVE-DR1180-V01 CVE-DR1181-V01 CVE-DR1182-V01 CVE-PR1183-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
52 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- V2I Mobility General The Traffic Signal Controller shall wait for CVE-CN1661-V01 Demonstration FN1516-V01 Priority/Preemption the light to turn red before servicing a phase CVE-DR1374-V01 for a movement that is requested in a preemption SRM when the approach for the requested movement is yellow CVE- V2I Mobility General The Traffic Signal Controller shall extend CVE-CN1661-V01 Demonstration FN1517-V01 Priority/Preemption the current phase for a movement that is CVE-DR1374-V01 requested in a preemption SRM when the approach for the requested movement is green CVE- V2I Mobility General An RSU shall receive output from the Traffic CVE-UN310-v02 Demonstration FN1518-V01 Priority/Preemption Signal Controller regarding the status of a CVE-UN320-v02 priority request CVE-DR1374-V01 CVE-UN510-v02 CVE-UN220-v02
CVE- V2I Mobility General An RSU shall send a SSM to an HDV OBU CVE-UN310-v02 Demonstration FN1519-V01 Priority/Preemption containing the results of the requests made CVE-UN320-v02 by one or more vehicles for a configurable CVE-DR1374-V01 period of time CVE-UN510-v02 CVE-UN220-v02 CVE- V2I Mobility General The Traffic CV Management System shall CVE-UN310-v02 Demonstration FN1520-V01 Priority/Preemption maintain a modifiable list of OBU IDs CVE-DR1420-V01 authorized to send SRMs CVE-DR1421-V01 CVE-DR1422-V01 CVE-DR1423-V01 CVE-DR1424-V01 CVE-DR1425-V01 CVE-DR1426-V01 CVE-DR1427-V01 CVE-DR1428-V01 CVE-DR1429-V01 CVE-DR1430-V01 CVE-DR1431-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 53 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE-DR1432-V01 CVE-DR1433-V01 CVE-DR1434-V01 CVE-DR1435-V01 CVE-DR1436-V01 CVE-UN320-v02 CVE-UN510-v02 CVE-UN220-v02 CVE- V2I Mobility General The Traffic CV Management System shall CVE-UN430-v02 Demonstration FN1521-V01 Priority/Preemption maintain a modifiable list of intersections for CVE-DR1420-V01 which each authorized OBU is allowed to CVE-DR1421-V01 request priority or preemption at. CVE-DR1422-V01 CVE-DR1423-V01 CVE-DR1424-V01 CVE-DR1425-V01 CVE-DR1426-V01 CVE-DR1427-V01 CVE-DR1428-V01 CVE-DR1429-V01 CVE-DR1430-V01 CVE-DR1431-V01 CVE-DR1432-V01 CVE-DR1433-V01 CVE-DR1434-V01 CVE-DR1435-V01 CVE-DR1436-V01 CVE- V2I Mobility General The Traffic CV Management System shall CVE-CN1662-V01 Demonstration FN1522-V01 Priority/Preemption transmit a list of vehicle OBU IDs that are CVE-DR1420-V01 authorized to receive signal priority at a CVE-DR1421-V01 given intersection to the RSU at that CVE-DR1422-V01 intersection when a change in the list has CVE-DR1423-V01 been made. CVE-DR1424-V01 CVE-DR1425-V01 CVE-DR1426-V01 CVE-DR1427-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
54 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE-DR1428-V01 CVE-DR1429-V01 CVE-DR1430-V01 CVE-DR1431-V01 CVE-DR1432-V01 CVE-DR1433-V01 CVE-DR1434-V01 CVE-DR1435-V01 CVE-DR1436-V01 CVE- V2I Mobility General The Traffic CV Management System shall CVE-CN1662-V01 Demonstration FN1523-V01 Priority/Preemption transmit a list of vehicle OBU IDs that are CVE-DR1292-V01 authorized to receive signal preemption at a CVE-DR1293-V01 given intersection to the RSU at that CVE-DR1294-V01 intersection when a change in the list has CVE-DR1295-V01 been made. CVE-DR1296-V01 CVE- V2I Mobility General The RSU shall receive the list of vehicle CVE-CN1662-V01 Demonstration FN1524-V01 Priority/Preemption OBU IDs that are authorized to receive CVE-DR1292-V01 signal priority at the intersection it is located CVE-DR1293-V01 at CVE-DR1294-V01 CVE-DR1295-V01 CVE-DR1296-V01 CVE- V2I Mobility General The RSU shall receive the list of vehicle CVE-CN1662-V01 Demonstration FN1525-V01 Priority/Preemption OBU IDs that are authorized to receive signal preemption at the intersection it is located at CVE- V2I Mobility Transit Signal Priority A Transit Vehicle OBU shall request to CVE-UN510-v02 Demonstration FN1488-V01 receive signal priority at RSU-equipped CVE-UN520-v02 intersections CVE- V2I Mobility Transit Signal Priority A Transit Vehicle OBU shall send a SRM to CVE-UN510-v02 Demonstration FN1489-V01 an RSU when it is within a configurable CVE-UN520-v02 distance of the intersection it intends to request priority for CVE- V2I Mobility Transit Signal Priority A Transit Vehicle OBU shall only request CVE-UN510-v02 Demonstration FN1490-V01 priority in an SRM CVE-UN520-v02
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 55 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- V2I Mobility Transit Signal Priority A Transit Vehicle OBU shall only request CVE-UN510-v02 Demonstration FN1491-V01 priority for movements along the route CVE-UN520-v02 being traversed by that transit vehicle CVE- V2I Mobility Transit Signal Priority An Transit Vehicle OBU shall cease CVE-UN510-v02 Demonstration FN1492-V01 broadcasting SRMs for priority at a given intersection for a configurable amount of time after it has received an SSM from that intersection that contains the Transit Vehicle OBU ID CVE- V2I Mobility Transit Signal Priority A request to receive signal priority from a CVE-UN510-v02 Demonstration FN1501-V01 Transit Vehicle OBU shall be low priority CVE-UN520-v02 CVE- V2I Mobility Transit Vehicle A Transit Vehicle OBU shall determine CVE-UN530-v02 Demonstration FN1534-V01 Interaction Event when to record a Transit Vehicle Interaction CVE-UN540-v02 Recording Event. Note: A Transit Vehicle Interaction Event contains the type of event along with a log of BSMs sent/received before and after the event. CVE- V2I Mobility Transit Vehicle A Transit Vehicle OBU shall not issue alerts CVE-UN530-v02 Demonstration FN1535-V01 Interaction Event CVE-UN540-v02 Recording CVE- V2I Mobility Transit Vehicle A Transit Vehicle OBU shall log a Transit CVE-UN530-v02 Demonstration FN1536-V01 Interaction Event Vehicle Interaction Event when there is CVE-UN540-v02 Recording emergency braking ahead by an OBU- equipped (remote) vehicle CVE- V2I Mobility Transit Vehicle A Transit Vehicle OBU shall log a Transit CVE-UN530-v02 Demonstration FN1537-V01 Interaction Event Vehicle Interaction Event when a forward CVE-UN540-v02 Recording collision is imminent with another OBU- equipped (remote) vehicle CVE- V2I Mobility Transit Vehicle A Transit Vehicle OBU shall log a Transit CVE-UN530-v02 Demonstration FN1538-V01 Interaction Event Vehicle Interaction Event when there is an CVE-UN540-v02 Recording approaching OBU-equipped (remote) CVE-DR1145-V01 vehicle on a conflicting approach at an intersection
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
56 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- V2I Mobility Transit Vehicle A Transit Vehicle OBU shall log a Transit CVE-UN530-v02 Demonstration FN1539-V01 Interaction Event Vehicle Interaction Event when there is an CVE-UN540-v02 Recording OBU-equipped (remote) vehicle in the host CVE-FN1129-V01 vehicle's blind spot CVE- V2I Mobility Transit Vehicle A Transit Vehicle OBU shall log a Transit CVE-UN530-v02 Demonstration FN1540-V01 Interaction Event Vehicle Interaction Event when it is CVE-UN540-v02 Recording changing lanes into another OBU-equipped CVE-DR1149-V01 (remote) vehicle CVE- V2I Mobility Transit Vehicle A Transit Vehicle OBU shall log a Transit CVE-UN530-v02 Demonstration FN1541-V01 Interaction Event Vehicle Interaction Event when the vehicle CVE-UN540-v02 Recording will run a red light at an RSU-equipped CVE-IF1222-V01 intersection CVE- V2I Mobility Transit Vehicle A Transit Vehicle OBU shall log a Transit CVE-UN530-v02 Demonstration FN1542-V01 Interaction Event Vehicle Interaction Event when the vehicle CVE-UN540-v02 Recording will enter an RSU-equipped school zone CVE-IF1234-V01 over the active school zone speed limit CVE- V2I Mobility Transit Vehicle A Transit Vehicle OBU shall log a Transit CVE-UN530-v02 Demonstration FN1543-V01 Interaction Event Vehicle Interaction Event when the vehicle CVE-UN540-v02 Recording is inside of an RSU-equipped school zone CVE-FN1554-V01 over the active school zone speed limit CVE- V2I Mobility Transit Vehicle A Transit Vehicle OBU shall store any CVE-UN530-v02 Demonstration FN1544-V01 Interaction Event BSMs received in local memory for a CVE-UN540-v02 Recording configurable amount of time. CVE- V2I Mobility Transit Vehicle A Transit Vehicle OBU shall store any SPaT CVE-UN530-v02 Demonstration FN1545-V01 Interaction Event messages received in local memory for a CVE-UN540-v02 Recording configurable amount of time. CVE- V2I Mobility Transit Vehicle A Transit Vehicle OBU shall store any MAP CVE-UN530-v02 Demonstration FN1546-V01 Interaction Event messages received in local memory for a CVE-UN540-v02 Recording configurable amount of time. CVE- V2I Mobility Transit Vehicle A Transit Vehicle OBU shall store any CVE-UN530-v02 Demonstration FN1547-V01 Interaction Event BSMs broadcast in local memory for a CVE-UN540-v02 Recording configurable amount of time.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 57 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- V2I Mobility Transit Vehicle A Transit Vehicle OBU shall store any CVE-UN530-v02 Demonstration FN1548-V01 Interaction Event SRMs broadcast in local memory for a Recording configurable amount of time. CVE- V2I Mobility Transit Vehicle A Transit Vehicle OBU shall store any CVE-UN530-v02 Demonstration FN1549-V01 Interaction Event SSMs received in local memory for a Recording configurable amount of time. CVE- V2I Mobility Transit Vehicle A Transit Vehicle Interaction Event shall CVE-UN530-v02 Demonstration FN1550-V01 Interaction Event consist of the type of event (emergency CVE-UN540-v02 Recording braking ahead, forward collision imminent, intersection movement, blind spot, lane change, red light violation, school zone speed limit, priority request) CVE- V2I Mobility Transit Vehicle A Transit Vehicle OBU shall log a Transit CVE-UN530-v02 Demonstration FN1551-V01 Interaction Event Vehicle Interaction Event when the transit CVE-DR1391-V01 Recording vehicle OBU broadcasts an SRM CVE-DR1392-V01 CVE- V2I Mobility Transit Vehicle A Transit Vehicle OBU shall remove Transit CVE-UN530-v02 Demonstration FN1554-V01 Interaction Event Vehicle Interaction Event data with the CVE-UN540-v02 Recording oldest start times from memory until it is CVE-FN1543-V01 able to log a newly received interaction event CVE- V2I Mobility Transit Vehicle A Transit Vehicle OBU shall upload all CVE-UN530-v02 Demonstration FN1555-V01 Interaction Event Transit Vehicle Interaction Event data to the CVE-UN540-v02 Recording Transit CV Management System when it connects to the vehicle's regular data upload service. CVE- V2I Mobility Transit Vehicle A Transit Vehicle OBU shall remove all CVE-UN530-v02 Demonstration FN1556-V01 Interaction Event Transit Vehicle Interaction Event data from CVE-UN540-v02 Recording memory once uploaded to the Transit CV Management System. CVE- V2I Mobility Transit Vehicle A Transit Vehicle Interaction Event shall CVE-UN530-v02 Demonstration FN1557-V01 Interaction Event consist of the start time of the safety CVE-DR1378-V01 Recording interaction event (UTC) CVE-DR1379-V01 CVE-DR1380-V01 CVE-DR1381-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
58 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE-DR1382-V01 CVE-DR1383-V01 CVE-DR1384-V01 CVE-DR1385-V01 CVE-DR1386-V01 CVE-DR1387-V01 CVE-DR1388-V01 CVE-DR1389-V01 CVE-DR1390-V01 CVE-DR1391-V01 CVE-DR1392-V01 CVE-DR1393-V01 CVE-DR1394-V01 CVE-DR1395-V01 CVE-DR1396-V01 CVE-DR1397-V01 CVE-DR1398-V01 CVE-PR1399-V01 CVE-PR1400-V01 CVE-PR1401-V01 CVE-FN1312-V01 CVE- V2I Mobility Transit Vehicle A Transit Vehicle Interaction Event event CVE-UN530-v02 Demonstration FN1558-V01 Interaction Event shall consist of the end time of the event CVE-FN1312-V01 Recording (UTC) (in the case where multiple events of the same warning are issued based on messages received from the same vehicle or intersection within a configurable amount of time) CVE- V2I Mobility Transit Vehicle A Transit Vehicle Interaction Event shall CVE-UN530-v02 Demonstration FN1559-V01 Interaction Event consist of all locally stored messages CVE-DR1144-V01 Recording (SPaT, MAP, received BSMs, broadcast CVE-DR1145-V01 BSMs) from a configurable amount of time CVE-DR1146-V01 before the start time of the event CVE-DR1147-V01 CVE-DR1148-V01 CVE-DR1149-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 59 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE-DR1150-V01 CVE-DR1151-V01 CVE-DR1152-V01 CVE-DR1153-V01 CVE-DR1154-V01 CVE-DR1155-V01 CVE-DR1156-V01 CVE-DR1157-V01 CVE-DR1158-V01 CVE-DR1159-V01 CVE-DR1160-V01 CVE-DR1161-V01 CVE-DR1162-V01 CVE-DR1163-V01 CVE-DR1164-V01 CVE-DR1165-V01 CVE-DR1166-V01 CVE-DR1167-V01 CVE-DR1168-V01 CVE-DR1169-V01 CVE-DR1170-V01 CVE-DR1171-V01 CVE-DR1172-V01 CVE-DR1173-V01 CVE-DR1174-V01 CVE-DR1175-V01 CVE-DR1176-V01 CVE-DR1177-V01 CVE-DR1178-V01 CVE-DR1179-V01 CVE-DR1180-V01 CVE-DR1181-V01 CVE-DR1182-V01 CVE-PR1183-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
60 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- V2I Mobility Transit Vehicle A Transit Vehicle Interaction Event shall CVE-UN530-v02 Demonstration FN1560-V01 Interaction Event consist of all locally stored messages CVE-DR1374-V01 Recording (SPaT, MAP, received BSMs, broadcast CVE-FN1313-V01 BSMs) from a configurable amount of time after the end time of the event CVE- V2I Mobility Vehicle Data for Traffic The RSU shall delete logged BSMs once it CVE-UN410-v02 Demonstration FN1563-V01 Operations has verified that the logged BSMs have CVE-DR1420-V01 been received by the Traffic CV CVE-DR1421-V01 Management System CVE-DR1422-V01 CVE-DR1423-V01 CVE-DR1424-V01 CVE-DR1425-V01 CVE-DR1426-V01 CVE-DR1427-V01 CVE-DR1428-V01 CVE-DR1429-V01 CVE-DR1430-V01 CVE-DR1431-V01 CVE-DR1432-V01 CVE-DR1433-V01 CVE-DR1434-V01 CVE-DR1435-V01 CVE-DR1436-V01 CVE-FN1314-V01 CVE-IX1635-V01 CVE- V2I Mobility Vehicle Data for Traffic The RSU shall send logged BSMs to the CVE-UN410-v02 Demonstration FN1564-V01 Operations Traffic CV Management System at a configurable time interval CVE- V2I Mobility Vehicle Data for Traffic The RSU shall log BSMs received from a CVE-UN410-v02 Demonstration FN1565-V01 Operations given OBU at a configurable frequency (10 Hz max) CVE- V2I Mobility Vehicle Data for Traffic The RSU shall send logged SRMs to the CVE-PR1105-V01 Demonstration FN1566-V01 Operations Traffic CV Management System at a CVE-FN1503-V01 configurable time interval CVE-FN1504-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 61 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE-FN1505-V01 CVE-FN1506-V01 CVE-FN1508-V01 CVE-FN1463-V01 CVE-FN1480-V01 CVE-UN410-v02 CVE-PR1105-V01 CVE-IX1635-V01 CVE- V2I Mobility Vehicle Data for Traffic The RSU shall log SRMs received from a CVE-UN410-v02 Demonstration FN1567-V01 Operations given OBU at a configurable frequency CVE-DR1402-V01 CVE-DR1403-V01 CVE-DR1404-V01 CVE-DR1405-V01 CVE-DR1406-V01 CVE-DR1407-V01 CVE-DR1408-V01 CVE-DR1409-V01 CVE-DR1410-V01 CVE-DR1411-V01 CVE-DR1412-V01 CVE-DR1413-V01 CVE-DR1414-V01 CVE-DR1415-V01 CVE-DR1416-V01 CVE-DR1417-V01 CVE-DR1418-V01 CVE-DR1419-V01 CVE- V2I Mobility Vehicle Data for Traffic The RSU shall send logged SSMs to the CVE-UN410-v02 Demonstration FN1569-V01 Operations Traffic CV Management System at a CVE-IX1635-V01 configurable time interval. CVE- V2I Mobility Vehicle Data for Traffic The RSU shall log SSMs received from a CVE-UN410-v02 Demonstration FN1570-V01 Operations traffic signal controller at a configurable frequency
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
62 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- V2I Mobility Vehicle Data for Traffic The RSU should not log duplicate SSMs CVE-UN410-v02 Demonstration FN1571-V01 Operations during a configurable time interval CVE- V2I Mobility Vehicle Data for Traffic The RSU shall send logged SPaT CVE-UN410-v02 Demonstration FN1572-V01 Operations messages to the Traffic CV Management CVE-IX1635-V01 System at a configurable time interval CVE- V2I Mobility Vehicle Data for Traffic The RSU shall log SPaT messages at a CVE-UN410-v02 Demonstration FN1573-V01 Operations configurable frequency CVE- V2I Mobility Vehicle Data for Traffic The RSU shall not log a SPaT message CVE-UN410-v02 Demonstration FN1574-V01 Operations unless there is a change in configurable select data elements (e.g. minEndTime, maxEndTime, etc.) from the previously logged message CVE- V2I Mobility Vehicle Data for Traffic The RSU shall log MAP messages at a CVE-UN410-v02 Demonstration FN1575-V01 Operations configurable frequency CVE- V2I Mobility Vehicle Data for Traffic The RSU should not log duplicate MAP CVE-UN410-v02 Demonstration FN1576-V01 Operations messages during a configurable time interval CVE- V2I Mobility Vehicle Data for Traffic The RSU shall send logged RSMs to the CVE-UN410-v02 Demonstration FN1577-V01 Operations Traffic CV Management System at a CVE-IX1635-V01 configurable time interval CVE- V2I Mobility Vehicle Data for Traffic The RSU shall log RSMs at a configurable CVE-UN410-v02 Demonstration FN1578-V01 Operations frequency CVE- V2I Mobility Vehicle Data for Traffic The RSU should not log duplicate RSMs CVE-UN410-v02 Demonstration FN1579-V01 Operations during a configurable time interval CVE- V2I Mobility Vehicle Data for Traffic The Traffic CV Management System shall CVE-UN410-v02 Demonstration FN1580-V01 Operations receive all logged BSMs sent by the RSU CVE-IX1635-V01 CVE- V2I Mobility Vehicle Data for Traffic The Traffic CV Management System shall CVE-UN410-v02 Demonstration FN1581-V01 Operations receive all logged SRMs sent by the RSU CVE-DR1276-V01 CVE-IX1635-V01 CVE- V2I Mobility Vehicle Data for Traffic The Traffic CV Management System shall CVE-UN410-v02 Demonstration FN1582-V01 Operations receive all logged SSMs sent by the RSU CVE-DR1292-V01 CVE-DR1293-V01 CVE-DR1294-V01 CVE-DR1295-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 63 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE-DR1296-V01 CVE-IX1635-V01 CVE- V2I Mobility Vehicle Data for Traffic The Traffic CV Management System shall CVE-UN410-v02 Demonstration FN1583-V01 Operations receive all logged SPaT messages sent by the RSU CVE- V2I Mobility Vehicle Data for Traffic The Traffic CV Management System shall CVE-UN410-v02 Demonstration FN1584-V01 Operations receive all logged RSM messages sent by CVE-IX1635-V01 the RSU CVE- V2I Mobility Vehicle Data for Traffic The Traffic CV Management System shall CVE-UN410-v02 Demonstration FN1585-V01 Operations store all logged BSMs sent by the RSU CVE-UN440-v02 CVE- V2I Mobility Vehicle Data for Traffic The Traffic CV Management System shall CVE-UN410-v02 Demonstration FN1586-V01 Operations store all logged SRMs sent by the RSU CVE-UN440-v02 CVE- V2I Mobility Vehicle Data for Traffic The Traffic CV Management System shall CVE-UN410-v02 Demonstration FN1587-V01 Operations store all logged SSMs sent by the RSU CVE-UN440-v02 CVE- V2I Mobility Vehicle Data for Traffic The Traffic CV Management System shall CVE-UN410-v02 Demonstration FN1588-V01 Operations store all logged SPaT messages sent by CVE-UN440-v02 the RSU CVE- V2I Mobility Vehicle Data for Traffic The Traffic CV Management System shall CVE-UN410-v02 Inspection FN1589-V01 Operations store all logged RSM messages sent by the CVE-DR1402-V01 RSU CVE-DR1403-V01 CVE-DR1404-V01 CVE-DR1405-V01 CVE-DR1406-V01 CVE-DR1407-V01 CVE-DR1408-V01 CVE-DR1409-V01 CVE-DR1410-V01 CVE-DR1411-V01 CVE-DR1412-V01 CVE-DR1413-V01 CVE-DR1414-V01 CVE-DR1415-V01 CVE-DR1416-V01 CVE-DR1417-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
64 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE-DR1418-V01 CVE-DR1419-V01 CVE-UN440-v02 CVE- V2I Mobility Vehicle Data for Traffic The Traffic CV Management System shall CVE-UN410-v02 Inspection FN1590-V01 Operations store all MAP messages that are input by CVE-DR1402-V01 the Traffic Manager CVE-DR1403-V01 CVE-DR1404-V01 CVE-DR1405-V01 CVE-DR1406-V01 CVE-DR1407-V01 CVE-DR1408-V01 CVE-DR1409-V01 CVE-DR1410-V01 CVE-DR1411-V01 CVE-DR1412-V01 CVE-DR1413-V01 CVE-DR1414-V01 CVE-DR1415-V01 CVE-DR1416-V01 CVE-DR1417-V01 CVE-DR1418-V01 CVE-DR1419-V01 CVE-UN440-v02 CVE- V2I Mobility Vehicle Data for Traffic The Traffic CV Management System shall CVE-UN410-v02 Inspection FN1591-V01 Operations make all stored data available to the Traffic CVE-DR1402-V01 Manager CVE-DR1403-V01 CVE-DR1404-V01 CVE-DR1405-V01 CVE-DR1406-V01 CVE-DR1407-V01 CVE-DR1408-V01 CVE-DR1409-V01 CVE-DR1410-V01 CVE-DR1411-V01 CVE-DR1412-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 65 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE-DR1413-V01 CVE-DR1414-V01 CVE-DR1415-V01 CVE-DR1416-V01 CVE-DR1417-V01 CVE-DR1418-V01 CVE-DR1419-V01 CVE-UN440-v02 CVE- V2I Mobility Vehicle Data for Traffic The RSU shall delete logged SRMs once it Demonstration FN2914-V01 Operations has verified that the logged SRMs have been received by the Traffic CV Management System CVE- V2I Mobility Vehicle Data for Traffic The RSU shall delete logged SSMs once it Demonstration FN2915-V01 Operations has verified that the logged SSMs have been received by the Traffic CV Management System CVE- V2I Mobility Vehicle Data for Traffic The RSU shall delete logged SPaT Demonstration FN2916-V01 Operations Messages one it has verified that the logged SPaT messages have been received by the Traffic CV Management System. CVE- V2I Mobility Vehicle Data for Traffic The RSU shall send logged MAP Demonstration FN2917-V01 Operations messages to the Traffic CV Management Center at a configurable time interval CVE- V2I Mobility Vehicle Data for Traffic The RSU shall delete logged MAP Demonstration FN2918-V01 Operations message once it has verified that the logged MAP messages have been received by the Traffic CV Management System CVE- V2I Mobility Vehicle Data for Traffic The RSU should not log duplicate RSMs Demonstration FN2919-V01 Operations during a configurable time interval CVE- V2I Mobility Vehicle Data for Traffic The RSU shall delete logged RSMs once it Demonstration FN2920-V01 Operations has verified that the logged RSMs have been received by the Traffic CV Management System
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
66 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- V2I Safety Red Light Violation An LDV OBU (host) shall issue an alert to CVE-UN130-v02 Demonstration FN1286-V01 Application Warning the LDV Operator via the HMI when a red- light violation will occur at an RSU-equipped intersection CVE- V2I Safety Red Light Violation An LDV OBU (host) shall determine if the CVE-UN130-v02 Demonstration FN1287-V01 Application Warning OBU-equipped (host) vehicle will run a red light for each SPaT message it receives CVE- V2I Safety Red Light Violation A red-light violation shall be occurring if all CVE-UN130-v02 Demonstration FN1288-V01 Application Warning of the following conditions are concurrently met: 1. An OBU-equipped vehicle is approaching an RSU-equipped intersection. 2. The OBU-equipped vehicle's trajectory (based on location, speed, acceleration) will cross the stop bar when the light is red with a configurable amount of confidence (factors that affect confidence include positioning error and uncertainty in the change of signal state) CVE- V2I Safety Reduced Speed An LDV OBU (host) shall issue an alert to CVE-UN140-v02 Demonstration FN1298-V01 Application School Zone the LDV Operator via the HMI when the CVE-UN610-v02 OBU-equipped (host) vehicle will enter an RSU-equipped school zone over the active school zone speed limit� CVE- V2I Safety Reduced Speed An LDV OBU (host) shall issue an alert CVE-UN140-v02 Demonstration FN1299-V01 Application School Zone when the OBU-equipped (host) vehicle is CVE-UN610-v02 inside of an RSU-equipped school zone over the active school zone speed limit CVE- V2I Safety Reduced Speed The LDV OBU (host) shall parse received CVE-UN140-v02 Demonstration FN1300-V01 Application School Zone RSMs to identify the school zone speed CVE-UN610-v02 limit (J2945/4). CVE- V2I Safety Reduced Speed The LDV OBU (host) shall parse received CVE-UN140-v02 Demonstration FN1301-V01 Application School Zone RSMs to identify when the school zone CVE-UN610-v02 speed limit is active.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 67 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- V2I Safety Reduced Speed The LDV OBU (host) shall parse received CVE-UN140-v02 Demonstration FN1302-V01 Application School Zone RSMs to identify the applicable regions of CVE-UN610-v02 use geographical path (J2945/4). CVE- V2I Safety Reduced Speed The LDV OBU (host) shall issue a school CVE-UN140-v02 Demonstration FN1303-V01 Application School Zone zone alert when all of the following CVE-UN610-v02 conditions are concurrently met: 1. OBU- equipped (host) vehicle is traveling towards the segment where the situational awareness applies. 2. The OBU-equipped (host) vehicle is expected to enter the school zone but not below the school zone speed limit (given its current location, motion, and expected braking rate) . 3. During active school zone hours CVE- V2I Safety Reduced Speed The LDV OBU (host) shall issue a school CVE-UN140-v02 Demonstration FN1304-V01 Application School Zone zone alert when all of the following CVE-UN610-v02 conditions are concurrently met: 1. OBU- equipped (host) vehicle is within the segment where the situational awareness applies. 2. OBU-equipped (host) vehicle is traveling above the school zone speed limit. 3. During active school zone hours CVE- V2V Safety Lane Change Warning A lane change collision shall be imminent if CVE-UN114-v02 Demonstration FN1140-V01 all of the following conditions are concurrently met: 1. The OBU-equipped (host) vehicle has a trajectory (based on position, speed, acceleration) that may interfere with an OBU-equipped (remote) vehicle trajectory in a sideswipe fashion. CVE- V2V Safety Blind Spot Warning An LDV OBU (host) shall issue an alert to CVE-UN120-v02 Demonstration FN1107-V01 Application the LDV Operator via the HMI when there is an OBU-equipped (remote) vehicle in the host vehicle's blind spot
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
68 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- V2V Safety Blind Spot Warning An LDV OBU (host) shall determine if a CVE-UN120-v02 Demonstration FN1108-V01 Application vehicle is in its blind spot for each BSM it receives CVE- V2V Safety Blind Spot Warning A vehicle shall be in a blind spot if all of the CVE-UN120-v02 Demonstration FN1109-V01 Application following conditions are concurrently met: 1. The OBU-equipped (host) vehicle is traveling in the same direction as the OBU- equipped (remote) vehicle. 2. The OBU- equipped (remote) vehicle is located in a configurable zone (rear left and rear right of the OBU-equipped host vehicle) with a configurable amount of confidence (factors that affect confidence include positioning error for the host and remote vehicle) CVE- V2V Safety Emergency Electronic An LDV OBU (host) shall issue an alert to CVE-UN111-v02 Demonstration FN1115-V01 Application Brake Light Warning the LDV Operator via the HMI �when there is emergency braking ahead by an OBU- equipped (remote) vehicle CVE- V2V Safety Emergency Electronic An LDV OBU (host) shall determine if there CVE-UN111-v02 Demonstration FN1116-V01 Application Brake Light Warning is emergency braking ahead for each BSM it receives CVE- V2V Safety Emergency Electronic Emergency braking ahead shall be CVE-UN111-v02 Demonstration FN1117-V01 Application Brake Light Warning occurring if all of the following conditions are concurrently met: 1. An OBU-equipped (remote) vehicle is braking in an emergency fashion. 2. The distance between the OBU- equipped (host) vehicle and OBU-equipped (remote) vehicle is less than a distance threshold that is a function of the speed of the host vehicle. 3. The OBU-equipped (host) vehicle is approaching the OBU- equipped (remote) vehicle. 4. The OBU- equipped (host) vehicle is moving in the
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 69 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method same direction as the OBU-equipped (remote) vehicle. CVE- V2V Safety Forward Collision An LDV OBU (host) shall issue an alert to CVE-UN112-v02 Demonstration FN1122-V01 Application Warning the LDV Operator via the LDV HMI when a forward collision is imminent with another OBU-equipped (remote) vehicle CVE- V2V Safety Forward Collision An LDV OBU (host) shall determine if a CVE-UN112-v02 Demonstration FN1124-V01 Application Warning forward collision is imminent for each BSM it receives CVE- V2V Safety Forward Collision A forward collision shall be imminent if all of CVE-UN112-v02 Demonstration FN1125-V01 Application Warning the following conditions are concurrently met: 1. The distance between the OBU- equipped (host) vehicle and OBU-equipped (remote) vehicle is less than a distance threshold that is a function of the speed of the host vehicle and the remote vehicle.. 2. The OBU-equipped (host) vehicle is approaching the OBU-equipped (remote) vehicle. CVE- V2V Safety Forward Collision A forward collision shall be imminent if the Demonstration FN2462-V01 Application Warning distance between the OBU-equipped (host) vehicle and OBU-equipped (remote) vehicle is less than a distance threshold that is a function of the speed of the host vehicle and the remote vehicle.
CVE- V2V Safety Forward Collision A forward collision shall be imminent if the Demonstration FN2463-V01 Application Warning OBU-equipped (host) vehicle is approaching the OBU-equipped (remote) vehicle. CVE- V2V Safety Intersection Movement An LDV OBU (host) shall issue an alert to CVE-UN113-v02 Demonstration FN1131-V01 Application Assist the LDV Operator via the HMI when an intersection collision is imminent with another OBU-equipped (remote) vehicle
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
70 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- V2V Safety Intersection Movement An LDV OBU (host) shall determine if an CVE-UN113-v02 Demonstration FN1132-V01 Application Assist intersection collision is imminent for each BSM it receives CVE- V2V Safety Intersection Movement An intersection collision shall be imminent if CVE-UN113-v02 Demonstration FN1133-V01 Application Assist all of the following conditions are concurrently met: 1. The OBU-equipped (host) vehicle has a trajectory (based on position, speed, acceleration) that may interfere with an OBU-equipped (remote) vehicle trajectory in a side impact fashion. 2. The distance between the OBU-equipped (host) vehicle and OBU-equipped (remote) vehicle is less than a distance threshold that is a function of the speed of the host vehicle and the remote vehicle. CVE- V2V Safety Lane Change Warning An LDV OBU (host) shall issue an alert to CVE-UN114-v02 Demonstration FN1138-V01 Application the LDV Operator via the HMI when it is changing lanes into another OBU-equipped (remote) vehicle CVE- V2V Safety Lane Change Warning An LDV OBU (host) shall determine if a CVE-UN114-v02 Demonstration FN1139-V01 Application lane change collision is imminent for each BSM it receives CVE- Vehicle Onboard Emergency Vehicle An Emergency Vehicle OBU shall cease Demonstration FN1215-V01 Equipment OBU broadcasting messages when its lights are off and siren is off CVE- Vehicle Onboard Emergency Vehicle An Emergency Vehicle OBU shall Demonstration FN1216-V01 Equipment OBU broadcast messages when its lights are flashing CVE- Vehicle Onboard Emergency Vehicle An Emergency Vehicle OBU shall Demonstration FN1217-V01 Equipment OBU broadcast messages when its siren is on CVE- Vehicle Onboard Emergency Vehicle An Emergency Vehicle OBU shall only CVE-UN220-v02 Demonstration FN1495-V01 Equipment OBU request preemption in an SRM CVE- Vehicle Onboard Emergency Vehicle An Emergency Vehicle OBU shall CVE-UN220-v02 Demonstration FN1496-V01 Equipment OBU cease sending SRMs for preemption to an
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 71 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method RSU at a given intersection for a configurable amount of time after it has received an SSM from the RSU at that intersection that contains the Emergency Vehicle OBU ID CVE- Vehicle Onboard Emergency Vehicle An Emergency Vehicle OBU shall send Demonstration FN2957-V01 Equipment OBU BSMs (Part I) consistent with SAE J2735 to a Transit Vehicle OBU CVE- Vehicle Onboard Emergency Vehicle An Emergency Vehicle OBU shall send Demonstration FN2958-V01 Equipment OBU BSMs (Part I) consistent with SAE J2735 to an RSU CVE- Vehicle Onboard Emergency Vehicle An Emergency Vehicle OBU shall receive Demonstration FN2961-V01 Equipment OBU position data from GNSS satellites CVE- Vehicle Onboard Emergency Vehicle An Emergency Vehicle OBU shall receive Demonstration FN2964-V01 Equipment OBU security certificates from the SCMS via the RSU CVE- Vehicle Onboard Emergency Vehicle An RSU shall broadcast MAP messages Demonstration FN2975-V01 Equipment OBU loaded on the RSU to an Emergency Vehicle OBU CVE- Vehicle Onboard Emergency Vehicle An RSU shall send a SSM to an EV OBU Demonstration FN2977-V01 Equipment OBU containing the results of the requests made by one or more vehicles for a configurable period of time CVE- Vehicle Onboard Emergency Vehicle The Emergency Vehicle OBU shall be able Demonstration FN2998-V01 Equipment OBU to send the SRM at a configurable rate CVE- Vehicle Onboard General OBU An OBU shall be capable of being reset and CVE-CN1663-V01 Demonstration FN1184-V01 Equipment reconfigured so that it can be installed into another vehicle of the same type (e.g. LDV, HDV, etc.) CVE- Vehicle Onboard General OBU An OBU host processor shall perform CVE-CN1649-V01 Demonstration FN1185-V01 Equipment integrity checks on boot to ensure that it is CVE-CN1650-V01 in a known good software state. CVE-CN1651-V01 CVE-CN1652-V01 CVE-CN1653-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
72 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE-CN1654-V01 CVE-CN1655-V01 CVE-CN1656-V01 CVE-CN1657-V01 CVE-CN1658-V01
CVE- Vehicle Onboard General OBU An OBU shall not continue to start up and CVE-SN870-v02 Demonstration FN1186-V01 Equipment will log an error if the host processor determines it is not in a known good software state on boot up. CVE- Vehicle Onboard General OBU The OBU should notify the vehicle CVE-IX1618-V01 Demonstration FN1198-V01 Equipment operators of the power status of device (e.g., off, powering up and online). CVE- Vehicle Onboard General OBU The OBU shall allow all vehicle operators to CVE-IX1618-V01 Demonstration FN1199-V01 Equipment see the system settings of the device. (e.g., version, brightness, volume, font size). CVE- Vehicle Onboard General OBU The OBU shall allow all vehicle operators to CVE-IX1618-V01 Demonstration FN1200-V01 Equipment see application availability with screen graphics (e.g., failed, operating, disabled). CVE- Vehicle Onboard General OBU The OBU should allow all vehicle operators CVE-IX1618-V01 Demonstration FN1201-V01 Equipment to see pending updates for the device with screen graphics (e.g., applications, firmware, operating system). CVE- Vehicle Onboard General OBU An OBU shall acquire time from the CVE-FN1192-V01 Demonstration FN1204-V02 Equipment Location and Time Service (LTS) interface CVE-SN840-v02 in accordance with J2945/1 section 6.2.4. CVE-FN1193-V01 CVE-IX1621-V01 CVE-IX1622-V01 CVE-IX1623-V01 CVE-IX1624-V01 CVE- Vehicle Onboard General OBU An OBU shall acquire location from the LTS CVE-SN830-v02 Demonstration FN1205-V01 Equipment interface in accordance with J2945/1 CVE-IX1621-V01 section 6.2.1. CVE-IX1622-V01 CVE-IX1623-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 73 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE-IX1624-V01 CVE- Vehicle Onboard General OBU The OBU should capture vehicle brake CVE-UN110-v02 Demonstration FN1207-V01 Equipment status over the OBU-OBD-II interface to the CVE-UN111-v02 host vehicle CVE-IX1617-V01 CVE-IX1608-V01 CVE-IX1641-V01 CVE- Vehicle Onboard General OBU An OBU device shall comply with IEEE CVE-CN1648-V01 Demonstration FN1209-V01 Equipment 1609.2: Standard for WAVE Security Services for Applications and Management Messages CVE- Vehicle Onboard General OBU The OBU shall implement a download CVE-IX1609-V01 Demonstration FN1212-V01 Equipment protocol that permits resumption of CVE-IX1615-V01 incomplete downloads instead of requiring CVE-IX1619-V01 an incomplete download to be restarted. CVE- Vehicle Onboard Heavy-Duty Vehicle An HDV OBU shall receive position data Demonstration FN2959-V01 Equipment OBU from GNSS satellites CVE- Vehicle Onboard Heavy-Duty Vehicle An HDV OBU shall receive security Demonstration FN2962-V01 Equipment OBU certificates from the SCMS via the RSU CVE- Vehicle Onboard Heavy-Duty Vehicle An HDV OBU shall send BSMs (Part I and Demonstration FN2968-V01 Equipment OBU Part II) consistent with SAE J2735 to a Transit Vehicle OBU CVE- Vehicle Onboard Heavy-Duty Vehicle An HDV OBU shall send BSMs (Part I and Demonstration FN2969-V01 Equipment OBU Part II) consistent with SAE J2735 to an RSU CVE- Vehicle Onboard Heavy-Duty Vehicle The HDV OBU shall be able to send the Demonstration FN2996-V01 Equipment OBU SRM at a configurable rate CVE- Vehicle Onboard Light-Duty Vehicle An LDV OBU shall communicate with a CVE-IX1618-V01 Demonstration FN1187-V01 Equipment OBU LDV Operator via an HMI CVE- Vehicle Onboard Light-Duty Vehicle The LDV OBU shall have two levels of alert CVE-PR1530-V01 Demonstration FN1188-V01 Equipment OBU CVE- Vehicle Onboard Light-Duty Vehicle The LDV OBU shall have a low-level alert CVE-FN1195-V01 Demonstration FN1189-V01 Equipment OBU CVE- Vehicle Onboard Light-Duty Vehicle The low-level alert shall consist of a CVE-FN1196-V01 Demonstration FN1190-V01 Equipment OBU configurable audio/visual warning
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
74 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Vehicle Onboard Light-Duty Vehicle The LDV OBU shall have a high-level alert CVE-FN1195-V01 Demonstration FN1191-V01 Equipment OBU CVE- Vehicle Onboard Light-Duty Vehicle The high-level alert shall consist of a CVE-FN1204-V02 Demonstration FN1192-V01 Equipment OBU configurable audio/visual warning CVE- Vehicle Onboard Light-Duty Vehicle The high-level alert shall be louder and CVE-FN1196-V01 Demonstration FN1193-V01 Equipment OBU more visible compared to the low-level alert CVE-FN1204-V02 CVE- Vehicle Onboard Light-Duty Vehicle The LDV OBU shall not display more than CVE-PR1530-V01 Demonstration FN1194-V01 Equipment OBU one alert to the LDV Vehicle Operator at a time CVE- Vehicle Onboard Light-Duty Vehicle The LDV OBU shall contain a configurable CVE-FN1189-V01 Demonstration FN1195-V01 Equipment OBU priority order for displaying alerts CVE-FN1191-V01 CVE- Vehicle Onboard Light-Duty Vehicle The order of alerts shall be configurable so CVE-FN1190-V01 Demonstration FN1196-V01 Equipment OBU that the order of alerts can be modified CVE-FN1193-V01 once priority has been established. CVE- Vehicle Onboard Light-Duty Vehicle The LDV OBU shall provide system status CVE-IX1618-V01 Demonstration FN1197-V01 Equipment OBU information to LDV operators. Information included in the system status includes power status, system settings, status of applications availability, and pending update status CVE- Vehicle Onboard Light-Duty Vehicle The LDV OBU shall provide messages that CVE-IX1618-V01 Demonstration FN1202-V01 Equipment OBU can be seen and/or heard by the LDV Operator via the HMI from the LDV Vehicle Operator's normal seating position CVE- Vehicle Onboard Light-Duty Vehicle The LDV OBU shall provide only the Demonstration FN1203-V01 Equipment OBU highest priority alert to the LDV vehicle operator when more than one alert is currently active CVE- Vehicle Onboard Light-Duty Vehicle An LDV OBU shall determine when to issue CVE-PR1530-V01 Demonstration FN1210-V01 Equipment OBU an alert CVE- Vehicle Onboard Light-Duty Vehicle The LDV OBU shall provide a visual output CVE-IX1618-V01 Demonstration FN1213-V01 Equipment OBU that is similar in look and feel from various applications when presenting information to LDV Operators via the HMI
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 75 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Vehicle Onboard Light-Duty Vehicle The LDV OBU Auditory signals (via the CVE-IX1618-V01 Demonstration FN1214-V01 Equipment OBU HMI) shall be loud enough to overcome masking sounds from road noise, the cab environment, and other equipment. � CVE- Vehicle Onboard Light-Duty Vehicle An LDV OBU shall receive BSMs from an Demonstration FN2952-V01 Equipment OBU Transit Vehicle OBU CVE- Vehicle Onboard Light-Duty Vehicle An LDV OBU shall receive BSMs from an Demonstration FN2953-V01 Equipment OBU Emergency Vehicle OBU CVE- Vehicle Onboard Light-Duty Vehicle An LDV OBU shall broadcast BSMs (Part I) Demonstration FN2970-V01 Equipment OBU consistent with SAE J2735 to a Transit Vehicle OBU CVE- Vehicle Onboard Light-Duty Vehicle An LDV OBU shall broadcast BSMs (Part I) Demonstration FN2971-V01 Equipment OBU consistent with SAE J2735 to an RSU CVE- Vehicle Onboard Transit Vehicle OBU A Transit Vehicle OBU shall transmit CVE-IX1642-V01 Demonstration FN1206-V01 Equipment Interaction Data to the Transit CV Management System CVE- Vehicle Onboard Transit Vehicle OBU A Transit Vehicle OBU shall use CVE-CN1648-V01 Demonstration FN1208-V01 Equipment 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. CVE- Vehicle Onboard Transit Vehicle OBU A Transit Vehicle OBU shall receive BSMs Demonstration FN2954-V01 Equipment from an HDV OBU CVE- Vehicle Onboard Transit Vehicle OBU A Transit Vehicle OBU shall receive BSMs Demonstration FN2955-V01 Equipment from a Transit Vehicle OBU CVE- Vehicle Onboard Transit Vehicle OBU A Transit Vehicle OBU shall receive BSMs Demonstration FN2956-V01 Equipment from an Emergency Vehicle OBU CVE- Vehicle Onboard Transit Vehicle OBU A Transit Vehicle OBU shall receive position Demonstration FN2960-V01 Equipment data from GNSS satellites CVE- Vehicle Onboard Transit Vehicle OBU An Transit Vehicle OBU shall receive Demonstration FN2963-V01 Equipment security certificates from the SCMS via the RSU
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
76 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Vehicle Onboard Transit Vehicle OBU A Transit Vehicle OBU shall broadcast Demonstration FN2966-V01 Equipment BSMs (Part I) consistent with SAE J2735 to a Transit Vehicle OBU CVE- Vehicle Onboard Transit Vehicle OBU A Transit Vehicle OBU shall broadcast Demonstration FN2967-V01 Equipment BSMs (Part I) consistent with SAE J2735 to an RSU CVE- Vehicle Onboard Transit Vehicle OBU An RSU shall broadcast MAP messages Demonstration FN2974-V01 Equipment loaded on the RSU to a Transit Vehicle OBU CVE- Vehicle Onboard Transit Vehicle OBU An RSU shall send a SSM to a Transit Demonstration FN2976-V01 Equipment Vehicle OBU containing the results of the requests made by one or more vehicles for a configurable period of time CVE- Vehicle Onboard Transit Vehicle OBU The Transit Vehicle OBU shall be able to Demonstration FN2997-V01 Equipment send the SRM at a configurable rate CVE- Vehicle Onboard Vehicle Operator The HMI shall present alerts to drivers CVE-IX1618-V01 Demonstration FN1123-V01 Equipment Interface Display using a devise that drivers are familiar with and limits driver interaction. CVE- Vehicle Onboard Emergency Vehicle An Emergency Vehicle OBU shall send a CVE-UN220-v02 Demonstration FN1494-V01 Equipmnet OBU SRM to an RSU when it is less than a configurable amount of time away from arriving at the intersection it intends to request priority for 499 Source: City of Columbus
500 Performance Requirements
501 This section provides the performance requirements (PR) for the system of interest (i.e. what the system will do). The requirements in Table 10: 502 Performance Requirements are organized by the functional groups and are related to the user needs identified the project ConOps identified.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 77 Chapter 3. System Requirements
503 Table 10: Performance Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages Basic Safety Message The BSM shall be broadcast at a CVE-FN1503-V01 Test PR1105-V01 frequency of 10 Hz CVE-FN1504-V01 CVE-FN1505-V01 CVE-FN1506-V01 CVE-FN1508-V01 CVE-FN1566-V01 CVE-FN1463-V01 CVE-FN1480-V01 CVE-FN1503-V01 CVE-FN1504-V01 CVE-FN1505-V01 CVE-FN1506-V01 CVE-FN1508-V01 CVE-FN1566-V01 CVE-FN1463-V01 CVE-FN1480-V01 CVE- DSRC Messages MapData Message The MAP message shall be expressed CVE-FN1512-V01 Inspection PR1183-V01 with an accuracy of 0.5 m or less. CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP message shall be Demonstration PR2993- transmitted with a frequency of at least V01 1 Hz
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
78 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages Signal Phase and The SPaT messages shall be CVE-FN1509-V01 Test PR1399- Timing Message generated and transmitted by the RSU CVE-FN1510-V01 V01 with a minimum frequency of 10 Hz CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-IF1281-V01 CVE- DSRC Messages Signal Phase and The SPaT MsgCount data field shall CVE-FN1509-V01 Test PR1400- Timing Message be incremented with every update that CVE-FN1510-V01 V01 is made to the corresponding CVE-FN1511-V01 IntersectionState data frame CVE-FN1557-V01 CVE-DR1387-V01 CVE-IF1281-V01 CVE- DSRC Messages Signal Phase and The SPaT MovementStates shall be CVE-FN1509-V01 Test PR1401- Timing Message updated with at least the computation CVE-FN1510-V01 V01 frequency of the traffic signal CVE-FN1511-V01 controller. If the controller is operating CVE-FN1557-V01 at 1 Hz, it is permissible to repeat the CVE-DR1387-V01 same MovementState information in CVE-IF1281-V01 10 SPaT messages. However, if the controller is operating at 10 Hz or greater, the MovementStates needs to be updated for every message. CVE- DSRC Messages Signal Request The SRM shall be broadcast Demonstration PR2995- Message at the configured frequency (functional V01 reqs describe when to start/stop broadcasting) CVE- DSRC Messages Signal Status The SSM shall be broadcast Demonstration PR2999- Message at the configured frequency (functional V01 reqs describe when to start/stop broadcasting) CVE- Roadside Roadside Unit The system clock of the RSU shall be CVE-IF1240-V01 Inspection PR1365- Equipment accurate to within 10 ms of the UTC CVE-IF1241-V01 V01 reference CVE-IF1242-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 79 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Roadside Roadside Unit All absolute times in any message CVE-IF1240-V01 Demonstration PR1366- Equipment shall be determined based on the CVE-IF1241-V01 V01 RSU's system clock CVE-IF1242-V01 CVE- Roadside Roadside Unit The time difference between CVE-IF1240-V01 Test PR1367- Equipment minEndTime (in the UTC reference CVE-IF1241-V01 V01 system) and the earliest possible CVE-IF1242-V01 physical phase change shall be no larger than 100 ms CVE- Roadside Roadside Unit The time difference between CVE-IF1240-V01 Test PR1368- Equipment maxEndTime (in the UTC reference CVE-IF1241-V01 V01 system) and the earliest possible CVE-IF1242-V01 physical phase change shall be no larger than 100 ms CVE- Roadside Roadside Unit The data elements MinuteOfTheYear CVE-CN1648-V01 Test PR1369- Equipment and DSecond shall be present in each V01 transmitted message and accurate within 100 ms of UTC time CVE- Roadside Roadside Unit School Zone RSUs shall broadcast the Demonstration PR2994- Equipment RSM at a frequency of 1 Hz V01 CVE- Traffic Traffic CV The Traffic CV Management System CVE-UN430-v02 Test PR1457- Management Management System shall notify designated personnel V01 Center within five minutes of limited connectivity. Note: Limited connectivity refers to a state when the Traffic CV Management System is not able to communicate with the RSU CVE- Traffic Traffic CV The Traffic CV Management System CVE-UN430-v02 Test PR1458- Management Management System shall notify designated personnel V01 Center within five minutes of a monitored function becoming unavailable
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
80 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- V2I Mobility Emergency Vehicle The EVP application (see Appendix B) CVE-UN220-v02 Analysis PR1531- Preemption shall meet TRL 6 criteria (has been CVE-CN1660-V01 V01 tested in a realistic envrionment outside of a laboratory and satisfies operational requirements when confronted with realistic problems) CVE- V2I Mobility Emergency Vehicle An Emergency Vehicle OBU (host) CVE-UN220-v02 Demonstration PR1532- Preemption shall issue a signal preemption CVE-CN1660-V01 V01 notification to the Emergency Vehicle Operator via the HMI when preemption has been granted CVE- V2I Mobility Freight Signal Priority The FSP application (see Appendix B) CVE-UN310-v02 Analysis PR1527- should employ algorithms that are used in CVE-CN1660-V01 V01 MMITSS to enable freight signal priority CVE- V2I Mobility Freight Signal Priority The FSP application (see Appendix B) CVE-UN310-v02 Analysis PR1528- shall meet TRL 6 criteria (has been CVE-CN1660-V01 V01 tested in a realistic envrionment outside of a laboratory and satisfies operational requirements when confronted with realistic problems) CVE- V2I Mobility Transit Signal Priority The TSP application (see Appendix B) CVE-UN510-v02 Analysis PR1529- should employ algorithms that are used in CVE-UN520-v02 V01 MMITSS to enable transit signal priority CVE-CN1660-V01 CVE- V2I Mobility Transit Signal Priority The TSP application (see Appendix B) CVE-UN510-v02 Analysis PR1530- shall meet TRL 6 criteria (has been CVE-FN1188-V01 V01 tested in a realistic envrionment CVE-FN1194-V01 outside of a laboratory and satisfies CVE-FN1210-V01 operational requirements when CVE-CN1660-V01 confronted with realistic problems) CVE- V2I Safety Red Light Violation The RLVW application (see Appendix CVE-UN130-v02 Analysis PR1290- Application Warning B) should employ algorithms that are CVE-CN1660-V01 V01 used in applications verified by CAMP to issue an RLVW
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 81 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- V2I Safety Red Light Violation The RLVW application (see Appendix CVE-UN130-v02 Analysis PR1291- Application Warning B) shall meet TRL 6 criteria (has been CVE-CN1660-V01 V01 tested in a realistic environment outside of a laboratory and satisfies operational requirements when confronted with realistic problems) CVE- V2I Safety Reduced Speed The RSSZ application (see Appendix CVE-UN140-v02 Analysis PR1306- Application School Zone B) should employ algorithms that are CVE-UN610-v02 V01 used in applications verified by CAMP CVE-CN1660-V01 to issue an RSSZ warning CVE- V2I Safety Reduced Speed The RSSZ application (see Appendix CVE-UN140-v02 Analysis PR1307- Application School Zone B) shall meet TRL 6 criteria (has been CVE-UN610-v02 V01 tested in a realistic environment CVE-CN1660-V01 outside of a laboratory and satisfies operational requirements when confronted with realistic problems) CVE- V2V Safety Emergency Electronic The EEBL application (see Appendix CVE-UN111-v02 Analysis PR1119-V01 Brake Light Warning B) should employ algorithms that are CVE-CN1660-V01 used in applications verified by CAMP to issue an EEBL alert. CVE- V2V Safety Blind Spot Warning The BSW application (see Appendix CVE-UN120-v02 Analysis PR1111-V01 Application B) should employ algorithms that are CVE-CN1660-V01 used in MMITSS to issue a BSW alert. CVE- V2V Safety Blind Spot Warning The BSW application (see Appendix CVE-UN120-v02 Analysis PR1112-V01 Application B) shall meet TRL 6 criteria (has been CVE-CN1660-V01 tested in a realistic environment outside of a laboratory and satisfies operational requirements when confronted with realistic problems)
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
82 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- V2V Safety Emergency Electronic The EEBL application (see Appendix CVE-UN111-v02 Analysis PR1120-V01 Application Brake Light Warning B) shall meet TRL 6 criteria (has been CVE-CN1660-V01 tested in a realistic environment outside of a laboratory and satisfies operational requirements when confronted with realistic problems) CVE- V2V Safety Forward Collision The FCW application (see Appendix CVE-UN112-v02 Analysis PR1127-V01 Application Warning B) should employ algorithms that are CVE-CN1660-V01 used in applications verified by CAMP to issue a FCW alert CVE- V2V Safety Forward Collision The FCW application (see Appendix CVE-UN112-v02 Analysis PR1128-V01 Application Warning B) shall meet TRL 6 criteria (has been CVE-CN1660-V01 tested in a realistic environment outside of a laboratory and satisfies operational requirements when confronted with realistic problems) CVE- V2V Safety Intersection The IMA application (see Appendix B) CVE-UN113-v02 Analysis PR1135-V01 Application Movement Assist should employ algorithms that are CVE-CN1660-V01 used in applications verified by CAMP to issue an IMA alert CVE- V2V Safety Intersection The IMA application (see Appendix B) CVE-UN113-v02 Analysis PR1136-V01 Application Movement Assist shall meet TRL 6 criteria (has been CVE-CN1660-V01 tested in a realistic environment outside of a laboratory and satisfies operational requirements when confronted with realistic problems) CVE- V2V Safety Lane Change Warning The LCW application (see Appendix B) CVE-UN114-v02 Analysis PR1142-V01 Application should employ algorithms that are CVE-CN1660-V01 used in applications verified by CAMP to issue a LCW alert
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 83 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- V2V Safety Lane Change Warning The LCW application (see Appendix B) CVE-UN114-v02 Analysis PR1143-V01 Application shall meet TRL 6 criteria (has been CVE-CN1660-V01 tested in a realistic environment outside of a laboratory and satisfies operational requirements when confronted with realistic problems) CVE- Vehicle Onboard General OBU The OBU shall have a minimum Demonstration PR2907- Equipment reserve (processor, dynamic storage, V01 persistent storage) capacity of XX % for its current and new firmware images. CVE- Vehicle Onboard Transit Vehicle OBU A Transit Vehicle OBU shall be Inspection PR2913- Equipment capable of holding 4 GB of interaction V01 event data.
504
505 Source: City of Columbus
506 Interface Requirements
507 The CVE interfaces allow dynamic and configurable functionality between internal components of the Smart Columbus SoS and external systems 508 that provide data or some other stated functionality as per the user needs. The IF requirements in Table 11: Interface Requirements have been 509 categorized into these two groups, which will help further clarify system boundaries.
510 Table 11: Interface Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Roadside An RSU shall receive An RSU shall receive security CVE-IX1634-V01 Demonstration IF1344-V01 Equipment security certificates certificates from the SCMS from the SCMS
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
84 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Roadside Roadside Unit An RSU shall receive data to populate CVE-IX1628-V01 Demonstration IF1339-V01 Equipment RTCM message from the CORS CVE- Roadside Roadside Unit An RSU shall receive data to populate CVE-IX1638-V01 Demonstration IF1340-V01 Equipment a SSM from the Traffic Signal Controller or Other Roadside Computing Device CVE- Roadside Roadside Unit An RSU shall receive RSMs from the CVE-IX1636-V01 Demonstration IF1341-V01 Equipment Traffic CV Management System CVE- Roadside Roadside Unit An RSU shall receive MAP messages CVE-IX1636-V01 Demonstration IF1342-V01 Equipment from the Traffic CV Management System CVE- Roadside Roadside Unit An RSU shall receive position data CVE-IX1625-V01 Demonstration IF1343-V01 Equipment from the LTS CVE- Roadside Roadside Unit An RSU shall receive SPaT messages CVE-IX1638-V01 Demonstration IF1345-V01 Equipment from the Traffic Signal Controller CVE- Roadside Roadside Unit An RSU should receive SSMs from a CVE-IX1638-V01 Demonstration IF1346-V01 Equipment Traffic Signal Controller CVE- Roadside Roadside Unit An RSU shall send information to CVE-UN220-v02 Demonstration IF1347-V01 Equipment request signal priority to the Traffic CVE-UN310-v02 Signal Controller CVE-UN320-v02 CVE-UN510-v02 CVE- Roadside Roadside Unit An RSU shall be powered via power CVE-CN1659-V01 Demonstration IF1348-V01 Equipment over Ethernet CVE- Roadside Roadside Unit An RSU shall be grounded CVE-CN1659-V01 Demonstration IF1349-V01 Equipment CVE- Roadside Roadside Unit Ethernet cable that connects to CVE-IX1637-V01 Demonstration IF1350-V01 Equipment equipment located outside of the traffic signal controller cabinet shall be outfitted with an in-line grounding mechanism
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 85 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Roadside Roadside Unit Ethernet cable that connects to CVE-IX1637-V01 Demonstration IF1351-V01 Equipment equipment located outside of the traffic signal controller cabinet shall be weatherproof (outdoor rated) CVE- Roadside Roadside Unit Ethernet cable that connects to CVE-IX1637-V01 Demonstration IF1352-V01 Equipment equipment located outside of the traffic signal controller cabinet shall be shielded CVE- Roadside Roadside Unit The RSU-SCMS interface shall allow a CVE-SN820-v02 Demonstration IF1353-V01 Equipment RSU to request application certificates CVE-IX1634-V01 with different contents from the current ones during the lifetime of the current ones. CVE- Roadside Roadside Unit Communication between the RSU and CVE-SN820-v02 Demonstration IF1354-V01 Equipment the SCMS shall operate in an CVE-IX1633-V01 encrypted, end-to-end connection in CVE-IX1634-V01 accordance with the selected SCMS interface. (Note: The SCMS interface should not need any further security.) CVE- Roadside Roadside Unit An RSU shall send SPaT messages CVE-IX1610-V01 Demonstration IF1356-V01 Equipment generated from SPaT data output from CVE-IX1616-V01 the controller to an LDV OBU CVE-IX1620-V01 CVE- Roadside Roadside Unit An RSU shall send MAP messages CVE-IX1610-V01 Demonstration IF1357-V01 Equipment loaded on the RSU to an LDV OBU CVE-IX1616-V01 CVE-IX1620-V01 CVE- Roadside Roadside Unit An RSU shall send RTCM messages CVE-IX1610-V01 Demonstration IF1358-V01 Equipment received from the CORS or other CVE-IX1616-V01 source to an LDV OBU CVE-IX1620-V01 CVE- Roadside Roadside Unit An RSU shall send SSM messages CVE-IX1610-V01 Demonstration IF1359-V01 Equipment received from the Traffic Signal CVE-IX1616-V01 Controller to an HDV OBU CVE-IX1631-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
86 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Roadside Roadside Unit An RSU shall send RSM messages CVE-DR1292-V01 Demonstration IF1360-V01 Equipment loaded on the RSU to an LDV OBU CVE-DR1293-V01 CVE-DR1294-V01 CVE-DR1295-V01 CVE-DR1296-V01 CVE-IX1620-V01 CVE-IX1631-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 87 Chapter 3. System Requirements
CVE- Roadside Roadside Unit An RSU shall receive over the air CVE-DR1144-V01 Demonstration IF1361-V01 Equipment messages via DSRC CVE-DR1145-V01 CVE-DR1146-V01 CVE-DR1147-V01 CVE-DR1148-V01 CVE-DR1149-V01 CVE-DR1150-V01 CVE-DR1151-V01 CVE-DR1152-V01 CVE-DR1153-V01 CVE-DR1154-V01 CVE-DR1155-V01 CVE-DR1156-V01 CVE-DR1157-V01 CVE-DR1158-V01 CVE-DR1159-V01 CVE-DR1160-V01 CVE-DR1161-V01 CVE-DR1162-V01 CVE-DR1163-V01 CVE-DR1164-V01 CVE-DR1165-V01 CVE-DR1166-V01 CVE-DR1167-V01 CVE-DR1168-V01 CVE-DR1169-V01 CVE-DR1170-V01 CVE-DR1171-V01 CVE-DR1172-V01 CVE-DR1173-V01 CVE-DR1174-V01 CVE-DR1175-V01 CVE-DR1176-V01 CVE-DR1177-V01 CVE-DR1178-V01 CVE-DR1179-V01 CVE-DR1180-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
88 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE-DR1181-V01 CVE-DR1182-V01 CVE-PR1183-V01 CVE-IX1609-V01 CVE-IX1615-V01 CVE-IX1619-V01 CVE- Roadside Roadside Unit An RSU shall receive BSMs from an CVE-IX1609-V01 Demonstration IF1362-V01 Equipment LDV OBU CVE-IX1615-V01 CVE-IX1619-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 89 Chapter 3. System Requirements
CVE- Roadside Roadside Unit An RSU shall receive SRMs from an CVE-DR1144-V01 Demonstration IF1363-V01 Equipment HDV OBU CVE-DR1145-V01 CVE-DR1146-V01 CVE-DR1147-V01 CVE-DR1148-V01 CVE-DR1149-V01 CVE-DR1150-V01 CVE-DR1151-V01 CVE-DR1152-V01 CVE-DR1153-V01 CVE-DR1154-V01 CVE-DR1155-V01 CVE-DR1156-V01 CVE-DR1157-V01 CVE-DR1158-V01 CVE-DR1159-V01 CVE-DR1160-V01 CVE-DR1161-V01 CVE-DR1162-V01 CVE-DR1163-V01 CVE-DR1164-V01 CVE-DR1165-V01 CVE-DR1166-V01 CVE-DR1167-V01 CVE-DR1168-V01 CVE-DR1169-V01 CVE-DR1170-V01 CVE-DR1171-V01 CVE-DR1172-V01 CVE-DR1173-V01 CVE-DR1174-V01 CVE-DR1175-V01 CVE-DR1176-V01 CVE-DR1177-V01 CVE-DR1178-V01 CVE-DR1179-V01 CVE-DR1180-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
90 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE-DR1181-V01 CVE-DR1182-V01 CVE-PR1183-V01 CVE-IX1609-V01 CVE-IX1615-V01 CVE- Roadside Roadside Unit An RSU shall send RSM messages Demonstration IF2978-V01 Equipment loaded on the RSU to a Transit Vehicle OBU CVE- Roadside Roadside Unit An RSU shall send SSM messages Demonstration IF2985-V01 Equipment received from the Traffic Signal Controller to a Transit Vehicle OBU CVE- Roadside Roadside Unit An RSU shall send SSM messages Demonstration IF2986-V01 Equipment received from the Traffic Signal Controller to an Emergency Vehicle OBU CVE- Transit Transit CV The Transit CV Management System CVE-IX1640-V01 Demonstration IF1277-V01 Management Management System shall generate performance metrics Center (as defined in the Performance Measurement Plan derived from COTA operations data) CVE- Transit Transit CV The Transit CV Management System CVE-IX1640-V01 Demonstration IF1472-V01 Management Management System shall send interaction data to the CVE-SN810-v02 Center Smart Columbus OS CVE- Transit Transit CV The Transit CV Management System CVE-UN530-v02 Demonstration IF1473-V01 Management Management System shall make interaction data available CVE-UN540-v02 Center to Transit Management Staff CVE-IX1643-V01 CVE- V2I Mobility Transit Signal Priority The TSP Application shall transmit and CVE-UN310-v02 Demonstration IF1526-V01 receive data from the OBU's internal CVE-UN320-v02 processing functions. CVE-UN510-v02 CVE-UN220-v02 CVE- V2I Mobility Transit Vehicle The TIVER Application shall transmit CVE-UN310-v02 Demonstration IF1561-V01 Interaction Event and receive data from the OBU's CVE-UN320-v02 Recording internal processing functions. CVE-UN510-v02 CVE-UN220-v02
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 91 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- V2I Mobility Vehicle Data for The VDTO Application shall receive CVE-UN410-v02 Demonstration IF1592-V01 Traffic Operations data from the OBU's internal processing functions. CVE- V2I Safety Red Light Violation The RLVW Application shall receive CVE-UN130-v02 Demonstration IF1289-V01 Application Warning data from the OBU's internal processing functions. CVE- V2I Safety Reduced Speed The RSSZ Application shall receive CVE-UN140-v02 Demonstration IF1305-V01 Application School Zone data from the OBU's internal processing functions. CVE-IF1110- V2V Safety Blind Spot Warning The BSW Application shall receive CVE-UN120-v02 Demonstration V01 Application data from the OBU's internal processing functions. CVE-IF1118- V2V Safety Emergency Electronic The EEBL Application shall receive CVE-UN111-v02 Demonstration V01 Application Brake Light Warning data from the OBU's internal processing functions. CVE- V2V Safety Forward Collision The FCW Application shall receive CVE-UN112-v02 Demonstration IF1126-V01 Application Warning data from the OBU's internal processing functions. CVE- V2V Safety Intersection The IMA Application shall receive CVE-UN113-v02 Demonstration IF1134-V01 Application Movement Assist data from the OBU's internal processing functions. CVE- V2V Safety Lane Change Warning The LCW Application shall receive CVE-UN113-v02 Demonstration IF1141-V01 Application data from the OBU's internal processing functions. CVE- Vehicle Onboard Emergency Vehicle An Emergency Vehicle OBU CVE-IX1629-V01 Demonstration IF1221-V01 Equipment OBU shall send BSMs (Part I) consistent CVE-IX1630-V01 with SAE J2735 to an LDV OBU CVE-IX1609-V01 CVE- Vehicle Onboard Emergency Vehicle An Emergency Vehicle OBU shall CVE-IX1610-V01 Demonstration IF1228-V01 Equipment OBU receive SPaT messages from an RSU CVE- Vehicle Onboard Emergency Vehicle An Emergency Vehicle OBU shall CVE-IX1610-V01 Demonstration IF1232-V01 Equipment OBU receive MAP messages from an RSU
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
92 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Vehicle Onboard Emergency Vehicle An Emergency Vehicle OBU shall CVE-IX1610-V01 Demonstration IF1236-V01 Equipment OBU receive RTCM messages from an RSU CVE- Vehicle Onboard Emergency Vehicle An Emergency Vehicle OBU shall CVE-IX1610-V01 Demonstration IF1239-V01 Equipment OBU receive SSM messages from an RSU CVE- Vehicle Onboard Emergency Vehicle An Emergency Vehicle OBU shall CVE-UN220-v02 Demonstration IF1244-V01 Equipment OBU receive the flashing light status over CVE-IX1608-V01 the OBU-OBD-II interface CVE- Vehicle Onboard Emergency Vehicle An Emergency Vehicle OBU shall CVE-UN220-v02 Demonstration IF1245-V01 Equipment OBU receive the siren status over the OBU- CVE-IX1608-V01 OBD-II interface CVE- Vehicle Onboard Emergency Vehicle An Emergency Vehicle OBU shall CVE-UN220-v02 Demonstration IF1247-V01 Equipment OBU issue a signal priority notification to the CVE-IX1644-V01 Emergency Vehicle Operator CVE- Vehicle Onboard Emergency Vehicle An Emergency Vehicle OBU shall CVE-IX1644-V01 Demonstration IF1248-V01 Equipment OBU provide a means of ceasing the broadcast of DSRC messages CVE- Vehicle Onboard Emergency Vehicle An Emergency Vehicle OBU CVE-IX1609-V01 Demonstration IF1251-V01 Equipment OBU shall send SRMs to an RSU CVE- Vehicle Onboard General OBU An LDV OBU shall receive security CVE-IX1610-V01 Demonstration IF1243-V01 Equipment certificates from the SCMS via the CVE-IX1616-V01 RSU CVE-IX1620-V01 CVE- Vehicle Onboard Heavy-Duty Vehicle An HDV OBU shall send BSMs (Part I CVE-IX1629-V01 Demonstration IF1219-V01 Equipment OBU and Part II) consistent with SAE J2735 CVE-IX1630-V01 to an LDV OBU CVE-IX1615-V01 CVE- Vehicle Onboard Heavy-Duty Vehicle An HDV OBU shall receive SPaT CVE-IX1616-V01 Demonstration IF1226-V01 Equipment OBU messages from an RSU CVE- Vehicle Onboard Heavy-Duty Vehicle An HDV OBU shall receive MAP CVE-IX1616-V01 Demonstration IF1230-V01 Equipment OBU messages from an RSU CVE- Vehicle Onboard Heavy-Duty Vehicle An HDV OBU shall receive RTCM CVE-FN1542-V01 Demonstration IF1234-V01 Equipment OBU messages from an RSU CVE-IX1616-V01 CVE- Vehicle Onboard Heavy-Duty Vehicle An HDV OBU shall receive SSM CVE-IX1616-V01 Demonstration IF1237-V01 Equipment OBU messages from an RSU
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 93 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Vehicle Onboard Heavy-Duty Vehicle An HDV OBU shall send SRMs to an CVE-IX1615-V01 Demonstration IF1249-V01 Equipment OBU RSU CVE- Vehicle Onboard Light-Duty Vehicle An LDV OBU shall send BSMs (Part I) CVE-IX1629-V01 Demonstration IF1218-V01 Equipment OBU consistent with SAE J2735 to an LDV CVE-IX1630-V01 OBU CVE-IX1619-V01 CVE- Vehicle Onboard Light-Duty Vehicle An LDV OBU shall communicate alerts CVE-IX1618-V01 Demonstration IF1222-V01 Equipment OBU to an LDV Operator CVE-FN1541-V01 CVE- Vehicle Onboard Light-Duty Vehicle An LDV OBU shall receive BSMs from CVE-IX1629-V01 Demonstration IF1223-V01 Equipment OBU an LDV OBU CVE-IX1630-V01 CVE- Vehicle Onboard Light-Duty Vehicle An LDV OBU shall receive SPaT CVE-IX1620-V01 Demonstration IF1225-V01 Equipment OBU messages from an RSU CVE- Vehicle Onboard Light-Duty Vehicle An LDV OBU shall receive MAP CVE-IX1620-V01 Demonstration IF1229-V01 Equipment OBU messages from an RSU CVE- Vehicle Onboard Light-Duty Vehicle An LDV OBU shall receive RTCM CVE-IX1620-V01 Demonstration IF1233-V01 Equipment OBU messages from an RSU CVE- Vehicle Onboard Light-Duty Vehicle An LDV OBU shall receive RSM CVE-PR1365-V01 Demonstration IF1240-V01 Equipment OBU messages from an RSU CVE-PR1366-V01 CVE-PR1367-V01 CVE-PR1368-V01 CVE-IX1620-V01 CVE- Vehicle Onboard Light-Duty Vehicle An LDV OBU shall receive position CVE-IX1623-V01 Demonstration IF1242-V01 Equipment OBU data from GNSS satellites CVE-PR1365-V01 CVE-PR1366-V01 CVE-PR1367-V01 CVE-PR1368-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
94 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Vehicle Onboard Light-Duty Vehicle An LDV OBU shall issue alerts to the CVE-UN110-v02 Demonstration IF1246-V01 Equipment OBU LDV Operator via an HMI CVE-UN111-v02 CVE-UN112-v02 CVE-UN113-v02 CVE-UN114-v02 CVE-UN120-v02 CVE-UN140-v02 CVE-UN140-v02 CVE-UN140-v02 CVE-UN610-v02 CVE-IX1618-V01 CVE- Vehicle Onboard Transit Vehicle OBU A Transit Vehicle OBU shall broadcast CVE-IX1629-V01 Demonstration IF1220-V01 Equipment BSMs (Part I) consistent with SAE CVE-IX1630-V01 J2735 to an LDV OBU CVE-IX1632-V01 CVE- Vehicle Onboard Transit Vehicle OBU A Transit Vehicle OBU shall receive CVE-IX1629-V01 Demonstration IF1224-V01 Equipment BSMs from an LDV OBU CVE-IX1630-V01 CVE- Vehicle Onboard Transit Vehicle OBU A Transit Vehicle OBU shall receive CVE-IX1631-V01 Demonstration IF1227-V01 Equipment SPaT messages from an RSU CVE- Vehicle Onboard Transit Vehicle OBU A Transit Vehicle OBU shall receive CVE-IX1631-V01 Demonstration IF1231-V01 Equipment MAP messages from an RSU CVE- Vehicle Onboard Transit Vehicle OBU A Transit Vehicle OBU shall receive CVE-IX1631-V01 Demonstration IF1235-V01 Equipment RTCM messages from an RSU CVE- Vehicle Onboard Transit Vehicle OBU A Transit Vehicle OBU shall receive CVE-DR1292-V01 Demonstration IF1238-V01 Equipment SSM messages from an RSU CVE-DR1293-V01 CVE-DR1294-V01 CVE-DR1295-V01 CVE-DR1296-V01 CVE-IX1631-V01 CVE- Vehicle Onboard Transit Vehicle OBU A Transit Vehicle OBU shall receive CVE-PR1365-V01 Demonstration IF1241-V01 Equipment RSM messages from an RSU CVE-PR1366-V01 CVE-PR1367-V01 CVE-PR1368-V01 CVE-IX1631-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 95 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Vehicle Onboard Transit Vehicle OBU A Transit Vehicle OBU shall send CVE-IX1632-V01 Demonstration IF1250-V01 Equipment SRMs to an RSU
511
512 Source: City of Columbus
513 Data Requirements
514 The data requirements (DR) for the core system of interest defines the data collected, transformed, and stored from various sources as well as 515 identifies new data that is expected to be generated. The requirements in Table 12: Data Requirements are organized by the functional groups 516 and are related to the user needs identified the project ConOps identified.
517 Table 12: Data Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1144- (msgIssueRevision) MsgCount data CVE-FN1513-V01 V01 element CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
96 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1145- (intersections) CVE-FN1513-V01 V01 IntersectionGeometryList data frame CVE-FN1514-V01 (a sequence of IntersectionGeometry) CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-FN1538-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1146- IntersectionGeometry data frame CVE-FN1513-V01 V01 under the (intersections) CVE-FN1514-V01 IntersectionGeometryList data frame CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1147- (id) IntersectionReferenceID data CVE-FN1513-V01 V01 frame under the IntersectionGeometry CVE-FN1514-V01 data frame CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 97 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1148- (id) IntersectionID data element under CVE-FN1513-V01 V01 the (id) IntersectionReferenceID data CVE-FN1514-V01 frame CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1149- (revision) MsgCount data element CVE-FN1513-V01 V01 under the IntersectionGeometry data CVE-FN1514-V01 frame CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-FN1540-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP message shall contain the CVE-FN1512-V01 Demonstration DR1150- (refPoint) Position3D-2 data frame CVE-FN1513-V01 V01 under the IntersectionGeometry data CVE-FN1514-V01 frame CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
98 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1151- (lat) Latitude data element under the CVE-FN1513-V01 V01 (refPoint) Position3D-2 data frame CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1152- (long) Longitude data element under CVE-FN1513-V01 V01 the (refPoint) Position3D-2 data frame CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1153- (laneWidth) LaneWidth data element CVE-FN1513-V01 V01 under the IntersectionGeometry data CVE-FN1514-V01 frame CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 99 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1154- LaneList data frame (a sequence of CVE-FN1513-V01 V01 GenericLane) under the CVE-FN1514-V01 IntersectionGeometry data frame CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1155- GenericLane data frame under the CVE-FN1513-V01 V01 LaneList data frame CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1156- (laneID) LaneID data element under CVE-FN1513-V01 V01 the GenericLane data frame CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
100 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1157- (maneuvers) AllowedManeuvers data CVE-FN1513-V01 V01 element under the GenericLane data CVE-FN1514-V01 frame CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1158- NodeList data frame under the CVE-FN1513-V01 V01 GenericLane data frame CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1159- (nodes) NodeSet data frame (a CVE-FN1513-V01 V01 sequence of Node) under the NodeList CVE-FN1514-V01 data frame CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 101 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1160- Node data frame under the (nodes) CVE-FN1513-V01 V01 NodeSet data frame CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1161- (delta) NodeOffsetPointXY data CVE-FN1513-V01 V01 element under the Node data frame CVE-FN1514-V01 (Any representation Node-XY-20b CVE-FN1515-V01 through Node-XY-32b) CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1162- (connectsTo) ConnectsToList data CVE-FN1513-V01 V01 frame (a sequence of Connection) CVE-FN1514-V01 under the GenericLane data frame CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
102 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1163- Connection data frame under the CVE-FN1513-V01 V01 (connectsTo) ConnectsToList data CVE-FN1514-V01 frame CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1164- (connectingLane) ConnectingLane CVE-FN1513-V01 V01 data frame under the Connection data CVE-FN1514-V01 frame CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1165- (lane) LaneID data element under the CVE-FN1513-V01 V01 (connectingLane) ConnectingLane CVE-FN1514-V01 data frame CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 103 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1166- (maneuver) AllowedManeuvers data CVE-FN1513-V01 V01 element under the (connectingLane) CVE-FN1514-V01 ConnectingLane data frame CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP Message shall contain the CVE-FN1512-V01 Demonstration DR1167- (signalGroup) SignalGroupID data CVE-FN1513-V01 V01 element under the Connection data CVE-FN1514-V01 frame CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP Message should describe all CVE-FN1512-V01 Demonstration DR1168- egress lanes. This makes it possible to CVE-FN1513-V01 V01 connect each ingress lane to the CVE-FN1514-V01 corresponding egress lane and also to CVE-FN1515-V01 describe the allowed maneuvers on all CVE-FN1559-V01 ingress lanes. CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
104 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages MapData Message The MAP Message egress lanes (if CVE-FN1512-V01 Demonstration DR1169- included) may optionally contain a CVE-FN1513-V01 V01 maneuvers field or a connectsTo field CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP Message egress lanes (if CVE-FN1512-V01 Demonstration DR1170- included) may optionally contain the CVE-FN1513-V01 V01 nodes in the NodeSet sequenced such CVE-FN1514-V01 that the first node is the stop bar CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP Message Node points shall CVE-FN1512-V01 Demonstration DR1171- correspond to the center of the lane CVE-FN1513-V01 V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 105 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages MapData Message The MAP Message Node points CVE-FN1512-V01 Demonstration DR1172- should extend to a recommended CVE-FN1513-V01 V01 minimum of 300 m from the stop bar CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP Message shall include a CVE-FN1512-V01 Demonstration DR1173- minimum of two node points to define CVE-FN1513-V01 V01 the lane CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP Message shall define node CVE-FN1512-V01 Demonstration DR1174- points such that the perpendicular CVE-FN1513-V01 V01 distance between two node points and CVE-FN1514-V01 the center of the lane shall be less CVE-FN1515-V01 than 0.5 m CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
106 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages MapData Message The MAP Message nodes in NodeSet CVE-FN1512-V01 Demonstration DR1175- shall be sequenced, in the case of an CVE-FN1513-V01 V01 ingress lane, such that the first node is CVE-FN1514-V01 the stop bar CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP Message shall describe all CVE-FN1512-V01 Demonstration DR1176- ingress lanes CVE-FN1513-V01 V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP Message shall contain a CVE-FN1512-V01 Demonstration DR1177- maneuvers field and a connectsTo CVE-FN1513-V01 V01 field for each ingress lane. The CVE-FN1514-V01 connectsTo field describes one or CVE-FN1515-V01 more Connections to egress lanes. CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 107 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages MapData Message The MAP Message Connection field CVE-FN1512-V01 Demonstration DR1178- shall contain the lane, maneuver, and CVE-FN1513-V01 V01 signalGroup associated with the CVE-FN1514-V01 Connection. The signalGroup CVE-FN1515-V01 identifies which signal group in the CVE-FN1559-V01 SPaT controls the flow of traffic from CVE-DR1272-V01 the ingress lane to the egress lane. CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP message containing a single CVE-FN1512-V01 Demonstration DR1179- physical lane which has multiple CVE-FN1513-V01 V01 different signals assigned (e.g., for CVE-FN1514-V01 straight and for right-turn movement), CVE-FN1515-V01 shall be represented by a single CVE-FN1559-V01 ingress lane and multiple connections CVE-DR1272-V01 that specify the relevant movements CVE-FN1552-V01 and the associated signal groups CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages MapData Message The MAP message CVE-FN1512-V01 Demonstration DR1181- IntersectionGeometry revision shall be CVE-FN1513-V01 V01 changed only if the map information CVE-FN1514-V01 was updated. CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
108 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages MapData Message The MAP message shall contain a CVE-FN1512-V01 Demonstration DR1182- laneList. Each lane in the laneList CVE-FN1513-V01 V01 shall be identified as an ingress lane CVE-FN1514-V01 or an egress lane through the CVE-FN1515-V01 laneAttributes->directionalUse field. CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1552-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE- DSRC Messages Radio Technical The RTCM shall include message type CVE-FN1516-V01 Demonstration DR1374- Commission for 1001 � GPS L1 observations at 5 Hz CVE-FN1517-V01 V01 Maritime Services CVE-FN1518-V01 Corrections Message CVE-FN1519-V01 CVE-FN1560-V01 CVE- DSRC Messages Radio Technical The RTCM message shall include CVE-CN1648-V01 Demonstration DR1375- Commission for message type 1005 Antenna V01 Maritime Services Reference Point (ARP) coordinates at Corrections Message 2 Hz
CVE- DSRC Messages Roadside Safety The Traffic CV Management System CVE-IF1238-V01 Analysis DR1292- Message shall generate a RSM consistent with CVE-SR1271-V01 V01 J2945/4 CVE-IF1360-V01 CVE-FN1475-V01 CVE-FN1523-V01 CVE-FN1524-V01 CVE-FN1582-V01 CVE- DSRC Messages Roadside Safety The RSM shall contain the school CVE-IF1238-V01 Demonstration DR1294- Message zone speed limit (J2945/4) (specific CVE-SR1271-V01 V01 data frames/elements TBD) CVE-IF1360-V01 CVE-FN1475-V01 CVE-FN1523-V01 CVE-FN1524-V01 CVE-FN1582-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 109 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages Roadside Safety The RSM shall contain the time CVE-IF1238-V01 Demonstration DR1295- Message periods when the school zone speed CVE-SR1271-V01 V01 limit is active. (specific data CVE-IF1360-V01 frames/elements TBD) CVE-FN1475-V01 CVE-FN1523-V01 CVE-FN1524-V01 CVE-FN1582-V01 CVE- DSRC Messages Roadside Safety The RSM shall contain the applicable CVE-IF1238-V01 Demonstration DR1296- Message regions of use geographical path (Part CVE-SR1271-V01 V01 ? defined in J2945/4). (specific data CVE-IF1360-V01 frames/elements TBD) CVE-FN1475-V01 CVE-FN1523-V01 CVE-FN1524-V01 CVE-FN1582-V01 CVE- DSRC Messages Signal Phase and The SPaT Message shall contain the CVE-FN1509-V01 Demonstration DR1378- Timing Message (timeStamp) MinuteOfTheYear data CVE-FN1510-V01 V01 element CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-IF1281-V01 CVE- DSRC Messages Signal Phase and The SPaT Message shall contain the CVE-FN1509-V01 Demonstration DR1379- Timing Message (intersections) IntersectionStateList CVE-FN1510-V01 V01 data frame (a sequence of CVE-FN1511-V01 IntersectionState) CVE-FN1557-V01 CVE-DR1387-V01 CVE-IF1281-V01 CVE- DSRC Messages Signal Phase and The SPaT Message shall contain the CVE-FN1509-V01 Demonstration DR1380- Timing Message IntersectionState data frame under the CVE-FN1510-V01 V01 IntersectionStateList data frame CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-IF1281-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
110 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages Signal Phase and The SPaT Message shall contain the CVE-FN1509-V01 Demonstration DR1381- Timing Message (id) IntersectionReferenceID data CVE-FN1510-V01 V01 element under the IntersectionState CVE-FN1511-V01 data frame CVE-FN1557-V01 CVE-DR1387-V01 CVE-IF1281-V01 CVE- DSRC Messages Signal Phase and The SPaT Message shall contain the CVE-FN1509-V01 Demonstration DR1382- Timing Message (revision) MsgCount data element CVE-FN1510-V01 V01 under the IntersectionState data frame CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-IF1281-V01 CVE- DSRC Messages Signal Phase and The SPaT Message shall contain the CVE-FN1509-V01 Demonstration DR1383- Timing Message (status) IntersectionStatusObject data CVE-FN1510-V01 V01 element under the IntersectionState CVE-FN1511-V01 data frame CVE-FN1557-V01 CVE-DR1387-V01 CVE-IF1281-V01 CVE- DSRC Messages Signal Phase and The SPaT Message shall contain the CVE-FN1509-V01 Demonstration DR1384- Timing Message (timeStamp) Dsecond data element CVE-FN1510-V01 V01 under the IntersectionState data frame CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-IF1281-V01 CVE- DSRC Messages Signal Phase and The SPaT Message shall contain the CVE-FN1509-V01 Demonstration DR1385- Timing Message (states) MovementList data frame (a CVE-FN1510-V01 V01 sequence of MovementState) under CVE-FN1511-V01 the IntersectionState data frame CVE-FN1557-V01 CVE-DR1387-V01 CVE-IF1281-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 111 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages Signal Phase and The SPaT Message shall contain the CVE-FN1509-V01 Demonstration DR1386- Timing Message MovementState data frame under the CVE-FN1510-V01 V01 MovementList data frame CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-IF1281-V01 CVE- DSRC Messages Signal Phase and The SPaT Message shall contain the CVE-FN1509-V01 Demonstration DR1387- Timing Message (signalGroup) SignalGroupID data CVE-FN1510-V01 V01 element under the MovementState CVE-FN1511-V01 data frame CVE-FN1557-V01 CVE-DR1378-V01 CVE-DR1379-V01 CVE-DR1380-V01 CVE-DR1381-V01 CVE-DR1382-V01 CVE-DR1383-V01 CVE-DR1384-V01 CVE-DR1385-V01 CVE-DR1386-V01 CVE-DR1388-V01 CVE-DR1389-V01 CVE-DR1390-V01 CVE-DR1391-V01 CVE-DR1392-V01 CVE-DR1393-V01 CVE-DR1394-V01 CVE-DR1395-V01 CVE-DR1396-V01 CVE-DR1397-V01 CVE-DR1398-V01 CVE-PR1399-V01 CVE-PR1400-V01 CVE-PR1401-V01 CVE-IF1281-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
112 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages Signal Phase and The SPaT Message shall contain the CVE-FN1509-V01 Demonstration DR1388- Timing Message (state-time-speed) MovementEventList CVE-FN1510-V01 V01 data frame (a sequence of CVE-FN1511-V01 MovementEvent) under the CVE-FN1557-V01 MovementState data frame CVE-DR1387-V01 CVE-DR1420-V01 CVE-DR1421-V01 CVE-DR1422-V01 CVE-DR1423-V01 CVE-DR1424-V01 CVE-DR1425-V01 CVE-DR1426-V01 CVE-DR1427-V01 CVE-DR1428-V01 CVE-DR1429-V01 CVE-DR1430-V01 CVE-DR1431-V01 CVE-DR1432-V01 CVE-DR1433-V01 CVE-DR1434-V01 CVE-DR1435-V01 CVE-DR1436-V01 CVE-IF1281-V01 CVE- DSRC Messages Signal Phase and The SPaT Message shall contain the CVE-FN1509-V01 Demonstration DR1389- Timing Message MovementEvent data frame under the CVE-FN1510-V01 V01 MovementEventList data frame CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-IF1281-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 113 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages Signal Phase and The SPaT Message shall contain the CVE-FN1509-V01 Demonstration DR1390- Timing Message (eventState) MovementPhaseState CVE-FN1510-V01 V01 data element under the CVE-FN1511-V01 MovementEvent data frame CVE-FN1557-V01 CVE-DR1387-V01 CVE-IF1281-V01 CVE- DSRC Messages Signal Phase and The SPaT Message shall contain the CVE-FN1551-V01 Demonstration DR1391- Timing Message (timing) TimeChangeDetails data CVE-FN1509-V01 V01 frame under the MovementEvent data CVE-FN1510-V01 frame CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-IF1281-V01 CVE- DSRC Messages Signal Phase and The SPaT Message shall contain the CVE-FN1509-V01 Demonstration DR1392- Timing Message (minEndTime) TimeMark data element CVE-FN1510-V01 V01 under the TimeChangeDetails data CVE-FN1511-V01 frame CVE-FN1557-V01 CVE-DR1387-V01 CVE-FN1551-V01 CVE-IF1281-V01 CVE- DSRC Messages Signal Phase and The SPaT Message should contain CVE-FN1509-V01 Demonstration DR1393- Timing Message the (maxEndTime) TimeMark data CVE-FN1510-V01 V01 element under the TimeChangeDetails CVE-FN1511-V01 data frame CVE-FN1557-V01 CVE-DR1387-V01 CVE-IF1281-V01 CVE- DSRC Messages Signal Phase and The SPaT Message should contain CVE-FN1509-V01 Demonstration DR1394- Timing Message the (likelyTime) TimeMark data CVE-FN1510-V01 V01 element under the TimeChangeDetails CVE-FN1511-V01 data frame CVE-FN1557-V01 CVE-DR1387-V01 CVE-IF1281-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
114 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages Signal Phase and The SPaT Message shall contain a CVE-FN1509-V01 Demonstration DR1395- Timing Message 'states' field, which is a list of one or CVE-FN1510-V01 V01 more MovementStates. The number of CVE-FN1511-V01 MovementStates shall correspond to CVE-FN1557-V01 the number of controller traffic phases CVE-DR1387-V01 that are currently active at the CVE-IF1281-V01 intersection. CVE- DSRC Messages Signal Phase and The SPaT Message signalGroup shall CVE-FN1509-V01 Demonstration DR1396- Timing Message be assigned number and is not CVE-FN1510-V01 V01 necessarily based on the controller CVE-FN1511-V01 phase number CVE-FN1557-V01 CVE-DR1387-V01 CVE-IF1281-V01 CVE- DSRC Messages Signal Phase and The SPaT Message should provide CVE-FN1509-V01 Demonstration DR1397- Timing Message maxEndTime or likelyTime CVE-FN1510-V01 V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-IF1281-V01 CVE- DSRC Messages Signal Phase and The SPaT Message should provide CVE-FN1509-V01 Demonstration DR1398- Timing Message maxEndTime if the traffic signal CVE-FN1510-V01 V01 controller is running fixed-time, and if CVE-FN1511-V01 transmitted shall be equal to CVE-FN1557-V01 minEndTime CVE-DR1387-V01 CVE-IF1281-V01 CVE- DSRC Messages Signal Request The OBU shall generate a SRM CVE-FN1589-V01 Demonstration DR1402- Message consistent with J2735 CVE-FN1590-V01 V01 CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 115 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages Signal Request The SRM shall contain the (second) CVE-FN1589-V01 Demonstration DR1404- Message DSecond data element CVE-FN1590-V01 V01 CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE- DSRC Messages Signal Request The SRM shall contain the (requests) CVE-FN1589-V01 Demonstration DR1405- Message SignalRequestList (sequence of CVE-FN1590-V01 V01 SignalRequestPackage) data frame CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE- DSRC Messages Signal Request The SRM shall contain the CVE-FN1589-V01 Demonstration DR1406- Message SignalRequestPackage data frame CVE-FN1590-V01 V01 under the SignalRequestList data CVE-FN1591-V01 frame CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE- DSRC Messages Signal Request The SRM shall contain the (request) CVE-FN1589-V01 Demonstration DR1407- Message SignalRequest data frame under the CVE-FN1590-V01 V01 SignalRequestPackage data frame CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE- DSRC Messages Signal Request The SRM shall contain the (id) CVE-FN1589-V01 Demonstration DR1408- Message IntersectionReferenceID data frame CVE-FN1590-V01 V01 under the SignalRequest data frame CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
116 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages Signal Request The SRM shall contain the (id) CVE-FN1589-V01 Demonstration DR1409- Message IntersectionID data element under the CVE-FN1590-V01 V01 intersectionReferenceID data frame CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE- DSRC Messages Signal Request The SRM shall contain the (requestID) CVE-FN1589-V01 Demonstration DR1410- Message RequestID data element under the CVE-FN1590-V01 V01 SignalRequest data frame CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE- DSRC Messages Signal Request The SRM shall contain the CVE-FN1589-V01 Demonstration DR1411- Message (requestType) PriorityRequestType CVE-FN1590-V01 V01 data element under the SignalRequest CVE-FN1591-V01 data frame CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE- DSRC Messages Signal Request The SRM shall contain the CVE-FN1589-V01 Demonstration DR1412- Message (inBoundLane) CVE-FN1590-V01 V01 IntersectionAccessPoint data frame CVE-FN1591-V01 under the SignalRequest data frame CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE- DSRC Messages Signal Request The SRM shall contain the (lane) CVE-FN1589-V01 Demonstration DR1413- Message LaneID data element under the CVE-FN1590-V01 V01 IntersectionAccessPoint data frame CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 117 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages Signal Request The SRM shall contain the (approach) CVE-FN1589-V01 Demonstration DR1414- Message ApproachID data element under the CVE-FN1590-V01 V01 IntersectionAccessPoint data frame CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE- DSRC Messages Signal Request The SRM shall contain the CVE-FN1589-V01 Demonstration DR1415- Message (connection) LaneConnectionID data CVE-FN1590-V01 V01 element under the CVE-FN1591-V01 IntersectionAccessPoint data frame CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE- DSRC Messages Signal Request The SRM shall contain the (requestor) CVE-FN1589-V01 Demonstration DR1416- Message RequestorDescription data frame CVE-FN1590-V01 V01 CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE- DSRC Messages Signal Request The SRM shall contain the (id) CVE-FN1589-V01 Demonstration DR1417- Message VehicleID data frame under the CVE-FN1590-V01 V01 RequestroDescription data frame CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE- DSRC Messages Signal Request The SRM shall contain the (entityID) CVE-FN1589-V01 Demonstration DR1418- Message TemporaryID under the VehicleID data CVE-FN1590-V01 V01 frame CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
118 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages Signal Request The SRM shall contain the (stationID) CVE-FN1589-V01 Demonstration DR1419- Message StationID under the VehicleID data CVE-FN1590-V01 V01 frame CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE- DSRC Messages Signal Status The RSU shall generate a SSM CVE-FN1520-V01 Analysis DR1420- Message consistent with J2735 CVE-FN1521-V01 V01 CVE-FN1522-V01 CVE-FN1563-V01 CVE-FN1282-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE- DSRC Messages Signal Status The SSM shall contain the (second) CVE-FN1520-V01 Demonstration DR1422- Message DSecond data element CVE-FN1521-V01 V01 CVE-FN1522-V01 CVE-FN1563-V01 CVE-FN1282-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE- DSRC Messages Signal Status The SSM shall contain the (status) CVE-FN1520-V01 Demonstration DR1423- Message SignalStatus data frame CVE-FN1521-V01 V01 CVE-FN1522-V01 CVE-FN1563-V01 CVE-FN1282-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 119 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages Signal Status The SSM shall contain the (sequence) CVE-FN1520-V01 Demonstration DR1424- Message MsgCount data element under the CVE-FN1521-V01 V01 SignalStatus data frame CVE-FN1522-V01 CVE-FN1563-V01 CVE-FN1282-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE- DSRC Messages Signal Status The SSM shall contain the (id) CVE-FN1520-V01 Demonstration DR1425- Message IntersectionReferenceID data element CVE-FN1521-V01 V01 under the SignalStatus data frame CVE-FN1522-V01 CVE-FN1563-V01 CVE-FN1282-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE- DSRC Messages Signal Status The SSM shall contain the (sigStatus) CVE-FN1520-V01 Demonstration DR1426- Message SignalStatusPackageList data frame CVE-FN1521-V01 V01 (sequence of SignalStatusPackage) CVE-FN1522-V01 under the SignalStatus data frame CVE-FN1563-V01 CVE-FN1282-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE- DSRC Messages Signal Status The SSM shall contain the CVE-FN1520-V01 Demonstration DR1427- Message SignalStatusPackage data frame CVE-FN1521-V01 V01 under the SignalStatusPacakageList CVE-FN1522-V01 data frame CVE-FN1563-V01 CVE-FN1282-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
120 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages Signal Status The SSM shall contain the (requestor) CVE-FN1520-V01 Demonstration DR1428- Message SignalRequestorInfo data frame under CVE-FN1521-V01 V01 the SignalStatusPackage data frame CVE-FN1522-V01 CVE-FN1563-V01 CVE-FN1282-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE- DSRC Messages Signal Status The SSM shall contain the (id) CVE-FN1520-V01 Demonstration DR1429- Message VehicleID under the CVE-FN1521-V01 V01 SignalRequestorInfor data frame CVE-FN1522-V01 CVE-FN1563-V01 CVE-FN1282-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE- DSRC Messages Signal Status The SSM shall contain the (request) CVE-FN1520-V01 Demonstration DR1430- Message RequestID under the CVE-FN1521-V01 V01 SignalRequestorInfor data frame CVE-FN1522-V01 CVE-FN1563-V01 CVE-FN1282-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE- DSRC Messages Signal Status The SSM shall contain the CVE-FN1520-V01 Demonstration DR1431- Message (sequenceNumber) MsgCount under CVE-FN1521-V01 V01 the SignalRequestorInfor data frame CVE-FN1522-V01 CVE-FN1563-V01 CVE-FN1282-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 121 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages Signal Status The SSM shall contain the CVE-FN1520-V01 Demonstration DR1432- Message (inboundOn) IntersectionAccessPoint CVE-FN1521-V01 V01 data frame under the CVE-FN1522-V01 SignalStatusPackage data frame CVE-FN1563-V01 CVE-FN1282-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE- DSRC Messages Signal Status The SSM shall contain the (lane) CVE-FN1520-V01 Demonstration DR1433- Message LaneID data element under the CVE-FN1521-V01 V01 IntesectionAccessPoint data frame CVE-FN1522-V01 CVE-FN1563-V01 CVE-FN1282-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE- DSRC Messages Signal Status The SSM shall contain the (approach) CVE-FN1520-V01 Demonstration DR1434- Message ApproachID data element under the CVE-FN1521-V01 V01 IntesectionAccessPoint data frame CVE-FN1522-V01 CVE-FN1563-V01 CVE-FN1282-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE- DSRC Messages Signal Status The SSM shall contain the CVE-FN1520-V01 Demonstration DR1435- Message (connection) LaneConnectionID data CVE-FN1521-V01 V01 element under the CVE-FN1522-V01 IntesectionAccessPoint data frame CVE-FN1563-V01 CVE-FN1282-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
122 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- DSRC Messages Signal Status The SSM shall contain the (status) CVE-FN1520-V01 Demonstration DR1436- Message PrioritizationResponseStatus data CVE-FN1521-V01 V01 element under the CVE-FN1522-V01 SignalStatusPackage data frame CVE-FN1563-V01 CVE-FN1282-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01
518
519 Source: City of Columbus
520 Security Requirements
521 The security requirements (SR) for the core system of interest specifies what is necessary to protect the integrity and operability of the system, its 522 microservices, connections, and data. This includes physical security as well as cyber prevention, detection, identification, response and recovery 523 requirements. The requirements in Table 13: Security Requirements are organized by the functional groups and are related to the user needs 524 identified the project ConOps identified.
525 Table 13: Security Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Roadside Roadside Unit RSUs shall support role-based CVE-SN820-v02 Demonstration SR1373- Equipment authentication to enable physical V01 access. CVE- Traffic Traffic CV Monitoring systems shall be used to CVE-UN430-v02 Demonstration SR1459- Management Management System detect abnormal unauthorized activity V01 Center on an IP connection.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 123 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Traffic Traffic CV The Traffic CV Management System CVE-UN430-v02 Demonstration SR1460- Management Management System shall monitor the DSRC V01 Center communications performance to detect DoS attacks. CVE- Traffic Traffic CV The Traffic CV Management System CVE-UN430-v02 Demonstration SR1461- Management Management System should investigate and monitor the V01 Center data traffic usage to detect unapproved use of the IP connection. CVE- Vehicle Onboard General OBU The OBU shall cease transmission of CVE-SN870-v02 Demonstration SR1254- Equipment BSMs if the OBU determines that it V01 has been blacklisted. Note: Blacklists detail devices that should not be trusted in the system or network CVE- Vehicle Onboard General OBU The OBU shall prevent incoming CVE-SN870-v02 Demonstration SR1255- Equipment messages with invalid conditions per V01 criteria in the IEEE 1609.2 from being acted on. CVE- Vehicle Onboard General OBU The OBU Vehicle Communications link CVE-SN870-v02 Demonstration SR1256- Equipment shall have communications security to V01 ensure the authenticity of all its messages in accordance to the standards prescribed by the overall USDOT connected vehicle program. CVE- Vehicle Onboard General OBU The OBU shall carry out plausibility CVE-SN870-v02 Demonstration SR1257- Equipment checking on the remote vehicle BSM V01 data. CVE- Vehicle Onboard General OBU The OBU shall indicate successful CVE-SN870-v02 Demonstration SR1258- Equipment receipt of the pseudonym certificates. V01 CVE- Vehicle Onboard General OBU When the OBU has no valid BSM CVE-SN870-v02 Demonstration SR1259- Equipment signing certificates, it shall store the V01 log file entries as IEEE 1609.2 data of type unsecured.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
124 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Vehicle Onboard General OBU The OBU shall obtain certificates via CVE-SN870-v02 Demonstration SR1261- Equipment IPv6 connectivity through the RSU. V01 CVE- Vehicle Onboard General OBU An OBU shall communicate using CVE-SN870-v02 Demonstration SR1262- Equipment SNMPv3 with SNMP messages V01 protected by being sent over TLS. CVE- Vehicle Onboard General OBU An OBU shall support establishment of CVE-SN870-v02 Demonstration SR1263- Equipment a standard TLS-based VPN with client V01 authentication for communication to the Traffic CV Management System, with a long-term client cert and a single CA cert trusted to authorize connections from the Traffic CV Management System. CVE- Vehicle Onboard General OBU An OBU shall verify received CVE-SN870-v02 Demonstration SR1264- Equipment messages per IEEE 1609.2 and per V01 the relevant security profiles before using them for operations in any application. CVE- Vehicle Onboard General OBU An OBU shall provide real-time tamper CVE-SN870-v02 Demonstration SR1265- Equipment data which indicates that the device V01 has been tampered with (e.g. opening of the case). CVE- Vehicle Onboard General OBU An OBU shall require that 1609.2 CVE-SN870-v02 Demonstration SR1266- Equipment signed messages are signed by a V01 certificate that is protected from modification by, or chains back to a certificate that is protected from modification by, the secure boot process.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 125 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Vehicle Onboard General OBU An OBU shall only transmit messages CVE-SN870-v02 Demonstration SR1267- Equipment for any usage scenario if the usage V01 scenario requires it to use 1609.2 certificates and it currently has valid certificates for that usage scenario CVE- Vehicle Onboard General OBU An OBU shall verify a DSRC message CVE-SN870-v02 Demonstration SR1268- Equipment when a device identifies the message V01 as containing a new DE_TemporaryID value. CVE- Vehicle Onboard General OBU An OBU shall verify a DSRC message CVE-SN870-v02 Demonstration SR1269- Equipment when the message results in the V01 issuance of issue either advisory, warning, or alert CVE- Vehicle Onboard General OBU An OBU shall verify a DSRC message CVE-SN870-v02 Demonstration SR1270- Equipment when the remote vehicle constitutes a V01 potential threat (define potential threat as a vehicle that may collide with the host vehicle based on the both vehicle�s speeds and trajectories CVE- Vehicle Onboard General OBU An OBU shall verify a DSRC message CVE-SN870-v02 Demonstration SR1271- Equipment when other potential threat situations CVE-DR1292-V01 V01 such as red-light violations, and other CVE-DR1293-V01 safety applications. CVE-DR1294-V01 CVE-DR1295-V01 CVE-DR1296-V01
526
527 Source: City of Columbus
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
126 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
528 Non-Functional Requirements
529 The non-functional requirements (NF) for the core system of interest specifies define the characteristics of the overall operation of the system such 530 as availability, maintainability, reliability, safety, environmental, human factors, and ergonomics.
531 Physical Requirements
532 The physical requirements specify the construction, durability, adaptability and environmental characteristics of the system, such as installation 533 location, device weight limits, dimension and volume limitations, temperature regulations, layout, access for maintenance, growth and expansion 534 characteristics, etc. The requirements in Table 14: Physical Requirements are organized by the functional groups and are related to the user 535 needs identified the project ConOps identified.
536 Table 14: Physical Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Roadside Cabinet Physical Roadside Equipment shall be Demonstration PY2912-V01 Equipment Security contained in a traffic signal controller cabinet that is outfitted with tamper alert devices to prevent unauthorized access. CVE- Roadside Roadside Unit RSU DSRC antennas shall be located CVE-CN1659-V01 Inspection PY1370-V01 Equipment to maximize the DSRC range along the corridors of interest. CVE- Roadside Roadside Unit RSU GPS antennas shall be located CVE-CN1659-V01 Analysis PY1371-V01 Equipment to maximize the GPS reception CVE- Roadside Roadside Unit Ethernet cable spans shall not exceed CVE-CN1648-V01 Inspection PY1372-V01 Equipment 100 meters (328 feet) CVE- Roadside Roadside Unit An RSU supplier shall provide the Inspection PY2908-V01 Equipment serial number for each RSU.
537
538 Source: City of Columbus
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 127 Chapter 3. System Requirements
539 Availability and Recoverability Requirements
540 The availability requirements define the times of day, days of year, and overall percentage the system can be used and when it will not be 541 available for use. It also specifies the recovery time objective (RTO) of the system, which describes the time frame permitted for a system to 542 become operational, the recovery point objective (RPO), which specifies up to what point in time shall the data be restored, as well as how the 543 system is expected to restore services (e.g. failover, backups, etc.) in an event of a failure. The ability to recover quickly from a system failure or 544 disaster depends on a blend of technologies and having a predefined plan for recovering the data on new hardware, when appropriate.
545 Maintainability Requirements
546 The maintainability requirements for the system specify the level of effort required to locate and correct an error during operation, establishing a 547 quantitative requirement for planned and unplanned support (e.g. mean and maximum times to repair or resolve issues, number of people and skill 548 levels required, support equipment necessary, maintenance staff hours, time and frequency of preventative maintenance, etc.). The requirements 549 in Table 15: Maintainability Requirements are organized by the functional groups and are related to the user needs identified the project 550 ConOps identified.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
128 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
551 Table 15: Maintainability Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Common A participant shall be A participant shall be able to return the CVE-CN1645-V01 Demonstration MT1604- able to return the OBU OBU to DPS for any reason (OBU CVE-DR1420-V01 V01 to DPS for any reason malfunction, remove/uninstall OBU, CVE-DR1421-V01 (OBU malfunction, etc.) CVE-DR1422-V01 remove/uninstall OBU, CVE-DR1423-V01 etc.) CVE-DR1424-V01 CVE-DR1425-V01 CVE-DR1426-V01 CVE-DR1427-V01 CVE-DR1428-V01 CVE-DR1429-V01 CVE-DR1430-V01 CVE-DR1431-V01 CVE-DR1432-V01 CVE-DR1433-V01 CVE-DR1434-V01 CVE-DR1435-V01 CVE-DR1436-V01 CVE- Common A set of support, A set of support, diagnostic and CVE-CN1645-V01 Demonstration MT1594- diagnostic and troubleshooting procedures shall be V01 troubleshooting developed to guide the support staff. procedures shall be developed to guide the support staff. CVE- Common Department of Public Department of Public Service shall CVE-CN1645-V01 Demonstration MT1602- Service shall maintain maintain the RSUs installed along the V01 the RSUs installed roadside. along the roadside.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 129 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Common Department of Public Department of Public Service shall CVE-CN1645-V01 Demonstration MT1603- Service shall provide provide contact information for CVE-DR1402-V01 V01 contact information for participants inquire about OBUs. CVE-DR1403-V01 participants inquire CVE-DR1404-V01 about OBUs. CVE-DR1405-V01 CVE-DR1406-V01 CVE-DR1407-V01 CVE-DR1408-V01 CVE-DR1409-V01 CVE-DR1410-V01 CVE-DR1411-V01 CVE-DR1412-V01 CVE-DR1413-V01 CVE-DR1414-V01 CVE-DR1415-V01 CVE-DR1416-V01 CVE-DR1417-V01 CVE-DR1418-V01 CVE-DR1419-V01 CVE- Common DPS shall maintain a DPS shall maintain a list of OBU CVE-CN1645-V01 Demonstration MT1595- list of OBU equipment equipment and contact information for V01 and contact vehicle owners that have OBUs information for vehicle installed owners that have OBUs installed CVE- Common DPS shall retain DPS shall retain Support Staff to CVE-CN1645-V01 Demonstration MT1593- Support Staff to troubleshoot and diagnose RSU and V01 troubleshoot and OBU issues. diagnose RSU and OBU issues.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
130 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Common Support Staff Device Support Staff Device installers shall be CVE-CN1645-V01 Demonstration MT1596- installers shall be approved by DPS to install roadside V01 approved by DPS to equipment (including RSUs) in signal install roadside cabinets and along the roadside. equipment (including RSUs) in signal cabinets and along the roadside. CVE- Common Support Staff Device Support Staff Device installers shall be CVE-CN1645-V01 Demonstration MT1597- installers shall be approved by DPS to install OBUs in V01 approved by DPS to participant vehicles. install OBUs in participant vehicles. CVE- Common Support Staff Device Support Staff Device installers shall be CVE-CN1645-V01 Demonstration MT1600- installers shall be approved by DPS to install OBU V01 approved by DPS to devices in private light-duty vehicles, install OBU devices in city fleet vehicles, transit vehicles, private light-duty Public Safety Vehicles, freight vehicles, city fleet vehicles, and CEAVs. vehicles, transit vehicles, Public Safety Vehicles, freight vehicles, and CEAVs. CVE- Common Support Staff shall be Support Staff shall be trained by the CVE-CN1645-V01 Demonstration MT1599- trained by the OBU OBU vendor to install OBU Devices V01 vendor to install OBU Devices CVE- Common Support Staff shall be Support Staff shall be trained by the CVE-CN1645-V01 Demonstration MT1598- trained by the RSU RSU vendor to install RSU Devices V01 vendor to install RSU Devices
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 131 Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method CVE- Common The Department of The Department of Public Service CVE-CN1645-V01 Demonstration MT1601- Public Service shall shall collect data to generate the V01 collect data to emergency response time generate the performance measure (for Emergency emergency response Vehicle Preemption) time performance measure (for Public Safety Vehicle Preemption) CVE- Roadside Roadside Unit RSUs shall support physical access to CVE-CN1645-V01 Demonstration MT1364- Equipment support maintenance activities. CVE-CN1659-V01 V01 CVE- Vehicle Onboard General OBU An OBU shall support physical access CVE-CN1663-V01 Demonstration MT1252- Equipment to support maintenance activities. V01 CVE- Vehicle Onboard General OBU An OBU shall support role-based CVE-CN1663-V01 Demonstration MT1253- Equipment authentication to enable physical V01 access.
552 Source: City of Columbus
553 Storage and Transport Requirements
554 The storage and transport requirements (ST) specify the physical location and environment for the system including designated storage facility, 555 installation site, repair facility and requirements for transporting equipment.
556 Table 16. Storage and Transport Requirements
Verification ReqID Description Reference Method
CVE-OBU-ST1-v1 OBUs shall be installed by a firm qualified to install electronic devices in Analysis motor vehicles.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
132 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Description Reference Method
CVE-RSU-ST1-v1 RSUs shall be installed by a firm qualified by the City for Traffic Signal and Analysis other ITS systems
557 Disposal Requirements
558 The disposal requirements (DR) specify the items related to the disposal of project/system components, due to either failure replacements, 559 removal, end-of-life upgrade, or retirement. The requirements in Table 17: Disposal Requirements are organized by the functional groups and 560 are related to the user needs identified the project ConOps identified.
561 Table 17: Disposal Requirements Verification ReqID Functional Group Sub-Component Description References Method
CVE- Transit Transit CV The CVE should remain operational CVE-UN410-v02 Analysis DP1465- Management Management System after the completion of the deployment V01 Center period
562 Source: City of Columbus
563 Enabling Requirements
564 The enabling requirements specify details concerning the management of information as well as the production of the system and its lifecycle 565 sustainment, including development, integration, verification, validation, and training.
566 Information Management Requirements
567 The information management (IM) requirements specify the acquisition, management, and ownership of information from one or more sources, the 568 custodianship and the distribution of that information to those who need it, and its ultimate disposition through archiving or deletion.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 133 Chapter 3. System Requirements
569 < In the context of the CVE, the Operating System is the IM system . However, the CVE is not dependent on the Operating System for operational 570 needs. The CVE does write data to the OS for archival and performance measures purpose as reflected in appropriate requirements>
571 Life Cycle Sustainment Requirements
572 The life cycle sustainment (LC) requirements define what items the project or system will review, measure, and analyze as part of its commitment 573 to quality during the life cycle of the system. The capacity to change or enhance the product and life cycle processes can be designed into the 574 system architecture to enable the cost-effective sustainment of the system throughout its life cycle. This design attribute should be established 575 early in the system’s development to provide a basis for planning each incremental development effort.
576 < Life Cycle Sustainment Requirements have not been established for the CVE>
577 Policy and Regulation Requirements
578 The policy and regulation requirements (RG) for the system of interest specifies relevant and applicable organizational policies and regulations 579 that affect the development, operation or performance of the system (e.g. IT and labor policies, reports to regulatory agencies, health or safety 580 criteria, etc.). This section also includes new policy and regulation imposed to realize the system. The requirements in Table 18: Policy and 581 Regulation Requirements are organized by the functional groups and are related to the user needs identified the project ConOps identified.
582 Table 18: Policy and Regulation Requirements Verification ReqID Functional Group Sub-Component Description References Method
CVE- Common An OBU shall be An OBU shall be licensed (subpart L of CVE-CN1645-V01 Analysis RG1607- licensed (subpart L of Part 95 of FCC Rules) by the FCC V01 Part 95 of FCC Rules) by the FCC
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
134 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 3. System Requirements
Verification ReqID Functional Group Sub-Component Description References Method
CVE- Common An RSU shall be An RSU shall be licensed (subpart M CVE-CN1645-V01 Analysis RG1605- licensed (subpart M of of Part 90 of FCC Rules) by the FCC V01 Part 90 of FCC Rules) by the FCC
CVE- Common An RSU shall be An RSU shall be registered (RSU CVE-CN1645-V01 Analysis RG1606- registered (RSU sites, sites, channels, and other relevant V01 channels, and other data) by site and segment with the relevant data) by site FCC before operation and segment with the FCC before operation
583 Source: City of Columbus
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 135
584 Chapter 4. Engineering Principles
585 This section describes engineering principles that guide composition of the CVE project.
586 Methods of Verification
587 The software and hardware components that make up the CVE will be individually verified, then 588 integrated to produce top-level assemblies and microservices. These assemblies will also be individually 589 verified before being integrated with others to produce larger, evolving assemblies until the complete 590 system has been integrated and verified. Throughout this process, the Smart Columbus program will 591 utilize the Helix Requirements Management tool to capture, track and trace requirements starting with the 592 user needs defined in the ConOps, through development, testing and deployment. This approach and 593 software tool will be instrumental through the design and development phases of the project.
594 The requirements also maintain a verification method, which details the plan for verifying the requirement 595 based on its stated definition. One of the verification methods listed in Table 19: Methods of Verification 596 is assigned for each requirement. Using the requirements defined in the previous section,
597 Table 19: Methods of Verification
Type Description
Inspection Verification through a visual, auditory, olfactory, or tactile comparison
Demonstration Verification that exercises the system software or hardware as it is designed to be used, without external influence, to verify the results are specified by the requirement
Test Verification using controlled and predefined inputs and other external elements (e.g. data, triggers, etc.) that influence or induce the system to produce the output specified by the requirement
Analyze Verification through indirect and logical conclusion using mathematical analysis, models, calculations, testing equipment and derived outputs based on validated data sets
598 Source: City of Columbus
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 137 Chapter 4. Engineering Principles
599 Reference Architecture
600 Originating with the National ITS Architecture, the connected vehicle industry has developed and 601 supported the Architecture Reference for Cooperative and Intelligent Transportation (ARC-IT), which 602 defines the message flows and elements of the CVE. Figure 3: ARC-IT Representation of the 603 Connected Vehicle Environment (Includes Support Systems) illustrates the reference architecture for 604 the CVE. Figure 4, Figure 5, Figure 6, Figure 7, Figure 8 and Figure 9 show the decomposed (Level 2) 605 representation of the CVE Applications.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
138 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 4. Engineering Principles
606 Figure 3: ARC-IT Representation of the Connected Vehicle Environment (Includes Support Systems)
Transit CV 27. Over-the-Air (Wi-Fi) Transit Vehicle OBU Management System Loc and Time Data Source (GNSS) 25. Backhaul Traffic Signal Controller / School Zone Signal Vehicle Location Vehicle Situation Transit Center Data (Internet) Determination Roadway Speed Data Monitoring Collection Roadway Signal 13. Satellite Monitoring and Control Transit Vehicle Signal Warning Human Interface Vehicle Trust Priority 26. Local 28. UI (existing) Management Smart Columbus Roadway Support Roadway Signal Operating System Services Preemption Transit CV Vehicle Basic Safety Transit Vehicle Communication Databus Management Staff Archive Data Repository Elements Flow Cardinality 19. DSRC Archive Situation Data Location and Time Unicast Archival 23. Local Source (GNSS) Other OBU Center LDV Operator Multicast 14. Satellite Traffic CV 24. Backhaul (Internet) Management System Broadcast RSU 8. UI 18. DSRC Vehicle RSE Intersection LDV OBU TMC Signal Control RSE Traffic Monitoring Backhaul (existing) Management 12. Satellite 20. DSRC Vehicle Intersection Vehicle Situation Data Flow Status Warning Monitoring TMC Intersection RSE Intersection RSE Situation Safety 17. Backhaul Ohio CORS (Internet) Safety Monitoring Support Existing Vehicle Location Vehicle Map 9. DSRC Determination Management Project Center Support RSE Position RSE Map Services Correction Support Management Vehicle Speed Vehicle Trust 7. Local Network Time Source Management Assist Management RSE Trust 2. DSRC Field TMC Speed Warning 16. Backhaul 15. Backhaul RSE Support Services Management Flow Security Vehicle Basic Safety TMC Multi-Modal Communication LDV Databus Clear text, No Auth. Coordination 22. Backhaul RSE Speed Warning 6. DSRC Traveler Clear text, Auth. TMC Situation Data Management Emergency Vehicle OBU 10. Satellite Encrypted, Auth. 21. Backhaul Center Map Management Security and Credentials Management Vehicle Location Vehicle Trust 1. Local People System Determination Management TMC Data Collection EV On-Board En Route CCMS Misbehavior Emergency CCMS Authorization Support Reporting and Action Vehicle 3. UI Databus Functional 29. UI Object Traffic CV CCMS Enrollment CCMS Revocation Management Staff Emergency Vehicle CCMS Provisioning Operator
HDV OBU 11. Satellite
Platooning Provider CV On-Board Signal Vehicle Trust Central Management Priority Management 4. Local System
Freight Administration 5. Over-the-Air (TBD) Vehicle Location HDV Databus and Management Determination 607
608 Source: City of Columbus
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 139 Chapter 4. Engineering Principles
609 Figure 4: ARC-IT Representation of V2V Safety Applications (EEBL, FCW, BSW/LCW, IMA)
LDV Operator
Alert
LDV OBU CAN Bus Data Vehicle Basic Safety LDV Databus Communication
BSM
Other OBU
610
611 Source: City of Columbus
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
140 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 4. Engineering Principles
612 Figure 5: ARC-IT Representation of RLVW
Traffic Signal Controller / School Zone Signal driver information LDV Operator Roadway Signal Control
Alert SPaT data
LDV OBU RSU SPaT, MAP, RTCM CAN Bus Data Vehicle Intersection LDV Databus RSE Intersection Warning Safety 613
614 Source: City of Columbus
615 Figure 6: ARC-IT Representation of RSSZ
Traffic CV Management System
School Zone Flashing SIgn Control Traffic Signal TMC Speed Warning Controller / School Zone Signal School Zone Flashing Sign LDV Operator Roadway Speed Monitoring and Warning
School Zone Flashing Light Indicator Alert
RSU RSM LDV OBU RSM CAN Bus Data RSE Speed Warning Vehicle Speed LDV Databus Management Assist 616
617 Source: City of Columbus
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 141 Chapter 4. Engineering Principles
618 Figure 7: ARC-IT Representation of Signal Priority/Preemption Applications (TSP, FSP, EVP)
Traffic CV Traffic Signal RSU Management System Controller / School signal preemption request Zone Signal Roadway Signal Authorized OBU ID List Preemption
SPaT data RSE Intersection TMC Signal Control Roadway Signal Control Management SRM SSM, SPaT MAP
SSM, SPaT, MAP SRM SRM SSM, SPaT, MAP
Platooning Provider Emergency Vehicle Transit Vehicle OBU HDV OBU Central Management OBU Platoon Data System EV On-Board En Route Transit Vehicle Signal CV On-Board Signal Support Priority Priority Freight Administration Platoon Data Request and Management
CAN Bus Data CAN Bus Data CAN Bus Data
Emergency Vehicle Transit Vehicle HDV Databus Databus Databus 619
620 Source: City of Columbus
621 Figure 8: ARC-IT Representation of VDTO
Traffic CV Management System RSU LDV OBU Emergency Vehicle Transit Vehicle OBU HDV OBU BSM OBU Vehicle Basic Safety EV On-Board En Route TMC Situation Data RSE Traffic Monitoring Transit Vehicle Signal CV On-Board Signal Management BSM, SRM, SSM, SPaT Communication Support Priority Priority
CAN Bus Data CAN Bus Data CAN Bus Data CAN Bus Data
LDV Databus Emergency Vehicle Transit Vehicle HDV Databus Databus Databus 622
623 Source: City of Columbus
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
142 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Chapter 4. Engineering Principles
624 Figure 9: ARC-IT Representation of TVIER
Transit Vehicle OBU
Transit CV Management System (2B) transit vehicle warning data Vehicle Situation Data Monitoring Transit Center Data BSM Collection Vehicle Basic Safety Communication
CAN Bus Data Transit Vehicle Other OBU Databus 625
626 Source: City of Columbus
627
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 143
628 Appendix A. Document Terminology and
629 Conventions
630 Reference Conventions
631 The following conventions are used through this document:
632 Titles of externally referenced documents or sources are underlined.
633 Titles of internally referenced exhibits, sections, etc. are italicized.
634 Requirement Numbering Convention
635 Each requirement contains a unique ID for traceability and configuration management. Requirements for 636 all projects in the Smart Columbus program will follow the same convention. This identifier contains six 637 elements partitioned into four octets, each representing an identifiable attribute of the requirement. Table 638 20: Requirements Numbering Convention lists the naming convention of the requirements.
01 02 03 04
Project Subproject Requirement Requirement “v” Static Version Abbreviation Abbreviation Type Code Number Character Number
639 (a) (b) (c) (d) (e) (f)
640 Table 20: Requirements Numbering Convention
Data Type, # of Characters Description Casing and/or Digits
Project The designated Smart Columbus project String, upper Variable Abbreviation acronym (e.g. CVE, EPM, etc.) case
Subproject or The system, subsystem, microservice, String, upper Variable Function Group module or other package creating a feature case Abbreviation or service (e.g. CORE, WEB, MOBI, etc.)
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 145 Appendix A. Document Terminology and Conventions
Data Type, # of Characters Description Casing and/or Digits
Requirement Table 8: List of Requirement Types String, upper 2 Type Code FN: Functional case PR: Performance IF: Interface DR: Data SR: Security RG: Policy and Regulation PY: Physical AR: Availability and Recovery MT: Maintainability ST: Storage and Transport DP: Disposal IM: Information Management LC: Life Cycle Sustainability
Requirement An integer incrementing by one, indicating Integer 3 Number the number of requirements established
“v” Static Static letter “v” represents the requirement Character 1 Character version
Version Number An integer incrementing by one, indicating Integer 2 the number of revisions made to the requirement
641 Source: City of Columbus
642 An example of a Functional Requirement for the Transit Pedestrian Indicator application under the 643 Connected Vehicle Environment, would be “CVE-TPI-FN001-v01” in which the following applies:
644 “CVE” is the Project Abbreviation
645 “RSU” is the Subproject Abbreviation
646 “FN001” is the requirement type code coupled with the three-digit Requirement Number
647 “v01” is the static “v” coupled with the two-digit version number
648 Requirements Table Headings
649 The columns in the requirements tables throughout this document have the following definitions:
650 ReqID: a unique identifier providing a reference to a specific requirement, see section.Error! 651 Reference source not found.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
146 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report Appendix A. Document Terminology and Conventions
652 Description: Statement of the business function or conditions the system must meet.
653 Reference: Additional requirement(s), User Needs, Constraints or Interfaces that serve as the 654 source (reason) a requirement exists.
655 Verification Method: As detailed in Chapter 4, the method expected to verify that a requirement 656 has been met is assigned to each requirement.
657 Conformance
658 Requirements listed in this document use the following terminology:
659 SHALL indicates the definition is an absolute requirement of the specification.
660 SHALL NOT indicates the definition is an absolute prohibition of the specification.
661 SHOULD (RECOMMENDED) indicates there may exist valid reasons or circumstances to omit a 662 particular item, but the full implications must be understood and carefully weighed before 663 choosing a different course.
664 SHOULD NOT (NOT RECOMMENDED) indicates there may exist valid reasons or 665 circumstances when a particular function of condition is acceptable or even useful, but the full 666 implications should be understood, and the case carefully weighed before implementing any 667 function or condition described with this label.
668 MAY (OPTIONAL) indicates an item is truly optional. Some vendors may choose to include or 669 implement Optional Requirements to add value or enhance their overall product while other 670 vendors may omit the same Optional Requirement to reduce cost, increase time to market, etc. 671 An implementation which does not include an Optional Requirement SHALL be interoperable with 672 implementations which does include the Optional Requirement, though perhaps with reduced 673 functionality. In the same vein an implementation which does include an Optional Requirement 674 SHALL be interoperable with an implementation which does not include the Optional 675 Requirement (with the exception for the feature the option provides).
676
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 147
677 Appendix B. Requirements by System
678 Functional Groups
679 Table 21: Requirements Organized by Functional Groups organizes requirements defined in Chapter 680 3. System Requirements into its functional groups. This organization is intended for ease of use and 681 quick reference during system design.
682 Table 21: Requirements Organized by Functional Groups
Functional Group ReqID Description
DPS shall retain Support Staff to troubleshoot and Common CVE-MT1593-V01 diagnose RSU and OBU issues. Support Staff shall be trained by the OBU vendor to Common CVE-MT1599-V01 install OBU Devices An OBU shall be licensed (subpart L of Part 95 of FCC Common CVE-RG1607-V01 Rules) by the FCC An RSU shall be registered (RSU sites, channels, and Common CVE-RG1606-V01 other relevant data) by site and segment with the FCC before operation An RSU shall be licensed (subpart M of Part 90 of FCC Common CVE-RG1605-V01 Rules) by the FCC A participant shall be able to return the OBU to DPS for Common CVE-MT1604-V01 any reason (OBU malfunction, remove/uninstall OBU, etc.) Department of Public Service shall provide contact Common CVE-MT1603-V01 information for participants inquire about OBUs. Department of Public Service shall maintain the RSUs Common CVE-MT1602-V01 installed along the roadside. The Department of Public Service shall collect data to Common CVE-MT1601-V01 generate the emergency response time performance measure (for Emergency Vehicle Preemption) Support Staff Device installers shall be approved by DPS to install OBU devices in private light-duty Common CVE-MT1600-V01 vehicles, city fleet vehicles, transit vehicles, Public Safety Vehicles, freight vehicles, and CEAVs. Support Staff shall be trained by the RSU vendor to Common CVE-MT1598-V01 install RSU Devices Support Staff Device installers shall be approved by Common CVE-MT1597-V01 DPS to install OBUs in participant vehicles.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 149 Appendix B. Requirements by System Functional Groups
Functional Group ReqID Description
Support Staff Device installers shall be approved by Common CVE-MT1596-V01 DPS to install roadside equipment (including RSUs) in signal cabinets and along the roadside. DPS shall maintain a list of OBU equipment and Common CVE-MT1595-V01 contact information for vehicle owners that have OBUs installed A set of support, diagnostic and troubleshooting Common CVE-MT1594-V01 procedures shall be developed to guide the support staff. The MAP message shall be transmitted with a DSRC Messages CVE-PR2993-V01 frequency of at least 1 Hz The SRM shall be broadcast at the configured DSRC Messages CVE-PR2995-V01 frequency (functional reqs describe when to start/stop broadcasting) The SSM shall be broadcast at the configured DSRC Messages CVE-PR2999-V01 frequency (functional reqs describe when to start/stop broadcasting) DSRC Messages CVE-PR1105-V01 The BSM shall be broadcast at a frequency of 10 Hz The MAP Message shall contain the DSRC Messages CVE-DR1144-V01 (msgIssueRevision) MsgCount data element The MAP Message shall contain the (intersections) DSRC Messages CVE-DR1145-V01 IntersectionGeometryList data frame (a sequence of IntersectionGeometry) The MAP Message shall contain the DSRC Messages CVE-DR1146-V01 IntersectionGeometry data frame under the (intersections) IntersectionGeometryList data frame The MAP Message shall contain the (id) DSRC Messages CVE-DR1147-V01 IntersectionReferenceID data frame under the IntersectionGeometry data frame The MAP Message shall contain the (id) IntersectionID DSRC Messages CVE-DR1148-V01 data element under the (id) IntersectionReferenceID data frame The MAP Message shall contain the (revision) DSRC Messages CVE-DR1149-V01 MsgCount data element under the IntersectionGeometry data frame The MAP message shall contain the (refPoint) DSRC Messages CVE-DR1150-V01 Position3D-2 data frame under the IntersectionGeometry data frame The MAP Message shall contain the (lat) Latitude data DSRC Messages CVE-DR1151-V01 element under the (refPoint) Position3D-2 data frame The MAP Message shall contain the (long) Longitude DSRC Messages CVE-DR1152-V01 data element under the (refPoint) Position3D-2 data frame
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
150 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional Group ReqID Description
The MAP Message shall contain the (laneWidth) DSRC Messages CVE-DR1153-V01 LaneWidth data element under the IntersectionGeometry data frame The MAP Message shall contain the LaneList data DSRC Messages CVE-DR1154-V01 frame (a sequence of GenericLane) under the IntersectionGeometry data frame The MAP Message shall contain the GenericLane data DSRC Messages CVE-DR1155-V01 frame under the LaneList data frame The MAP Message shall contain the (laneID) LaneID DSRC Messages CVE-DR1156-V01 data element under the GenericLane data frame The MAP Message shall contain the (maneuvers) DSRC Messages CVE-DR1157-V01 AllowedManeuvers data element under the GenericLane data frame The MAP Message shall contain the NodeList data DSRC Messages CVE-DR1158-V01 frame under the GenericLane data frame The MAP Message shall contain the (nodes) NodeSet DSRC Messages CVE-DR1159-V01 data frame (a sequence of Node) under the NodeList data frame The MAP Message shall contain the Node data frame DSRC Messages CVE-DR1160-V01 under the (nodes) NodeSet data frame The MAP Message shall contain the (delta) NodeOffsetPointXY data element under the Node data DSRC Messages CVE-DR1161-V01 frame (Any representation Node-XY-20b through Node- XY-32b) The MAP Message shall contain the (connectsTo) DSRC Messages CVE-DR1162-V01 ConnectsToList data frame (a sequence of Connection) under the GenericLane data frame The MAP Message shall contain the Connection data DSRC Messages CVE-DR1163-V01 frame under the (connectsTo) ConnectsToList data frame The MAP Message shall contain the (lane) LaneID data DSRC Messages CVE-DR1165-V01 element under the (connectingLane) ConnectingLane data frame The MAP Message shall contain the (maneuver) DSRC Messages CVE-DR1166-V01 AllowedManeuvers data element under the (connectingLane) ConnectingLane data frame The MAP Message shall contain the (signalGroup) DSRC Messages CVE-DR1167-V01 SignalGroupID data element under the Connection data frame The MAP Message should describe all egress lanes. This makes it possible to connect each ingress lane to DSRC Messages CVE-DR1168-V01 the corresponding egress lane and also to describe the allowed maneuvers on all ingress lanes.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 151 Appendix B. Requirements by System Functional Groups
Functional Group ReqID Description The MAP Message egress lanes (if included) may DSRC Messages CVE-DR1169-V01 optionally contain a maneuvers field or a connectsTo field The MAP Message egress lanes (if included) may DSRC Messages CVE-DR1170-V01 optionally contain the nodes in the NodeSet sequenced such that the first node is the stop bar The MAP Message Node points shall correspond to the DSRC Messages CVE-DR1171-V01 center of the lane The MAP Message Node points should extend to a DSRC Messages CVE-DR1172-V01 recommended minimum of 300 m from the stop bar The MAP Message shall include a minimum of two DSRC Messages CVE-DR1173-V01 node points to define the lane The MAP Message shall define node points such that DSRC Messages CVE-DR1174-V01 the perpendicular distance between two node points and the center of the lane shall be less than 0.5 m The MAP Message nodes in NodeSet shall be DSRC Messages CVE-DR1175-V01 sequenced, in the case of an ingress lane, such that the first node is the stop bar DSRC Messages CVE-DR1176-V01 The MAP Message shall describe all ingress lanes The MAP Message shall contain a maneuvers field and a connectsTo field for each ingress lane. The DSRC Messages CVE-DR1177-V01 connectsTo field describes one or more Connections to egress lanes. The MAP Message Connection field shall contain the lane, maneuver, and signalGroup associated with the DSRC Messages CVE-DR1178-V01 Connection. The signalGroup identifies which signal group in the SPaT controls the flow of traffic from the ingress lane to the egress lane.
The MAP message containing a single physical lane which has multiple different signals assigned (e.g., for straight and for right-turn movement), shall be DSRC Messages CVE-DR1179-V01 represented by a single ingress lane and multiple connections that specify the relevant movements and the associated signal groups The MAP message IntersectionGeometry revision shall DSRC Messages CVE-DR1181-V01 be changed only if the map information was updated. The MAP message shall contain a laneList. Each lane in the laneList shall be identified as an ingress lane or DSRC Messages CVE-DR1182-V01 an egress lane through the laneAttributes- >directionalUse field. The MAP message shall be expressed with an DSRC Messages CVE-PR1183-V01 accuracy of 0.5 m or less.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
152 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional Group ReqID Description
The Traffic CV Management System shall generate a DSRC Messages CVE-DR1292-V01 RSM consistent with J2945/4 The RSM shall contain the school zone speed limit DSRC Messages CVE-DR1294-V01 (J2945/4) (specific data frames/elements TBD) The RSM shall contain the time periods when the DSRC Messages CVE-DR1295-V01 school zone speed limit is active. (specific data frames/elements TBD) The RSM shall contain the applicable regions of use DSRC Messages CVE-DR1296-V01 geographical path (Part ? defined in J2945/4). (specific data frames/elements TBD) The SSM shall contain the (status) DSRC Messages CVE-DR1436-V01 PrioritizationResponseStatus data element under the SignalStatusPackage data frame The SSM shall contain the (connection) DSRC Messages CVE-DR1435-V01 LaneConnectionID data element under the IntesectionAccessPoint data frame The SSM shall contain the (approach) ApproachID data DSRC Messages CVE-DR1434-V01 element under the IntesectionAccessPoint data frame The SSM shall contain the (lane) LaneID data element DSRC Messages CVE-DR1433-V01 under the IntesectionAccessPoint data frame The SSM shall contain the (inboundOn) DSRC Messages CVE-DR1432-V01 IntersectionAccessPoint data frame under the SignalStatusPackage data frame The SSM shall contain the (sequenceNumber) DSRC Messages CVE-DR1431-V01 MsgCount under the SignalRequestorInfor data frame The SSM shall contain the (request) RequestID under DSRC Messages CVE-DR1430-V01 the SignalRequestorInfor data frame The SSM shall contain the (id) VehicleID under the DSRC Messages CVE-DR1429-V01 SignalRequestorInfor data frame The SSM shall contain the (requestor) DSRC Messages CVE-DR1428-V01 SignalRequestorInfo data frame under the SignalStatusPackage data frame The SSM shall contain the SignalStatusPackage data DSRC Messages CVE-DR1427-V01 frame under the SignalStatusPacakageList data frame The SSM shall contain the (sigStatus) SignalStatusPackageList data frame (sequence of DSRC Messages CVE-DR1426-V01 SignalStatusPackage) under the SignalStatus data frame The SSM shall contain the (id) IntersectionReferenceID DSRC Messages CVE-DR1425-V01 data element under the SignalStatus data frame The SSM shall contain the (sequence) MsgCount data DSRC Messages CVE-DR1424-V01 element under the SignalStatus data frame
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 153 Appendix B. Requirements by System Functional Groups
Functional Group ReqID Description
The SSM shall contain the (status) SignalStatus data DSRC Messages CVE-DR1423-V01 frame The SSM shall contain the (second) DSecond data DSRC Messages CVE-DR1422-V01 element DSRC Messages CVE-DR1420-V01 The RSU shall generate a SSM consistent with J2735 The SRM shall contain the (stationID) StationID under DSRC Messages CVE-DR1419-V01 the VehicleID data frame The SRM shall contain the (entityID) TemporaryID DSRC Messages CVE-DR1418-V01 under the VehicleID data frame The SRM shall contain the (id) VehicleID data frame DSRC Messages CVE-DR1417-V01 under the RequestroDescription data frame The SRM shall contain the (requestor) DSRC Messages CVE-DR1416-V01 RequestorDescription data frame The SRM shall contain the (connection) DSRC Messages CVE-DR1415-V01 LaneConnectionID data element under the IntersectionAccessPoint data frame The SRM shall contain the (approach) ApproachID DSRC Messages CVE-DR1414-V01 data element under the IntersectionAccessPoint data frame The SRM shall contain the (lane) LaneID data element DSRC Messages CVE-DR1413-V01 under the IntersectionAccessPoint data frame The SRM shall contain the (inBoundLane) DSRC Messages CVE-DR1412-V01 IntersectionAccessPoint data frame under the SignalRequest data frame The SRM shall contain the (requestType) DSRC Messages CVE-DR1411-V01 PriorityRequestType data element under the SignalRequest data frame The SRM shall contain the (requestID) RequestID data DSRC Messages CVE-DR1410-V01 element under the SignalRequest data frame The SRM shall contain the (id) IntersectionID data DSRC Messages CVE-DR1409-V01 element under the intersectionReferenceID data frame The SRM shall contain the (id) IntersectionReferenceID DSRC Messages CVE-DR1408-V01 data frame under the SignalRequest data frame The SRM shall contain the (request) SignalRequest DSRC Messages CVE-DR1407-V01 data frame under the SignalRequestPackage data frame The SRM shall contain the SignalRequestPackage DSRC Messages CVE-DR1406-V01 data frame under the SignalRequestList data frame The SRM shall contain the (requests) DSRC Messages CVE-DR1405-V01 SignalRequestList (sequence of SignalRequestPackage) data frame The SRM shall contain the (second) DSecond data DSRC Messages CVE-DR1404-V01 element
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
154 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional Group ReqID Description
DSRC Messages CVE-DR1402-V01 The OBU shall generate a SRM consistent with J2735
The SPaT MovementStates shall be updated with at least the computation frequency of the traffic signal controller. If the controller is operating at 1 Hz, it is permissible to repeat the same MovementState DSRC Messages CVE-PR1401-V01 information in 10 SPaT messages. However, if the controller is operating at 10 Hz or greater, the MovementStates needs to be updated for every message.
The SPaT MsgCount data field shall be incremented DSRC Messages CVE-PR1400-V01 with every update that is made to the corresponding IntersectionState data frame The SPaT messages shall be generated and DSRC Messages CVE-PR1399-V01 transmitted by the RSU with a minimum frequency of 10 Hz The SPaT Message should provide maxEndTime if the DSRC Messages CVE-DR1398-V01 traffic signal controller is running fixed-time, and if transmitted shall be equal to minEndTime The SPaT Message should provide maxEndTime or DSRC Messages CVE-DR1397-V01 likelyTime The SPaT Message signalGroup shall be assigned DSRC Messages CVE-DR1396-V01 number and is not necessarily based on the controller phase number The SPaT Message shall contain a 'states' field, which is a list of one or more MovementStates. The number DSRC Messages CVE-DR1395-V01 of MovementStates shall correspond to the number of controller traffic phases that are currently active at the intersection. The SPaT Message should contain the (likelyTime) DSRC Messages CVE-DR1394-V01 TimeMark data element under the TimeChangeDetails data frame The SPaT Message should contain the (maxEndTime) DSRC Messages CVE-DR1393-V01 TimeMark data element under the TimeChangeDetails data frame The SPaT Message shall contain the (minEndTime) DSRC Messages CVE-DR1392-V01 TimeMark data element under the TimeChangeDetails data frame The SPaT Message shall contain the (timing) DSRC Messages CVE-DR1391-V01 TimeChangeDetails data frame under the MovementEvent data frame The SPaT Message shall contain the (eventState) DSRC Messages CVE-DR1390-V01 MovementPhaseState data element under the MovementEvent data frame
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 155 Appendix B. Requirements by System Functional Groups
Functional Group ReqID Description
The SPaT Message shall contain the MovementEvent DSRC Messages CVE-DR1389-V01 data frame under the MovementEventList data frame The SPaT Message shall contain the (state-time- DSRC Messages CVE-DR1388-V01 speed) MovementEventList data frame (a sequence of MovementEvent) under the MovementState data frame The SPaT Message shall contain the (signalGroup) DSRC Messages CVE-DR1387-V01 SignalGroupID data element under the MovementState data frame The SPaT Message shall contain the MovementState DSRC Messages CVE-DR1386-V01 data frame under the MovementList data frame The SPaT Message shall contain the (states) MovementList data frame (a sequence of DSRC Messages CVE-DR1385-V01 MovementState) under the IntersectionState data frame The SPaT Message shall contain the (timeStamp) DSRC Messages CVE-DR1384-V01 Dsecond data element under the IntersectionState data frame The SPaT Message shall contain the (status) DSRC Messages CVE-DR1383-V01 IntersectionStatusObject data element under the IntersectionState data frame The SPaT Message shall contain the (revision) DSRC Messages CVE-DR1382-V01 MsgCount data element under the IntersectionState data frame The SPaT Message shall contain the (id) DSRC Messages CVE-DR1381-V01 IntersectionReferenceID data element under the IntersectionState data frame The SPaT Message shall contain the IntersectionState DSRC Messages CVE-DR1380-V01 data frame under the IntersectionStateList data frame The SPaT Message shall contain the (intersections) DSRC Messages CVE-DR1379-V01 IntersectionStateList data frame (a sequence of IntersectionState) The SPaT Message shall contain the (timeStamp) DSRC Messages CVE-DR1378-V01 MinuteOfTheYear data element The RTCM message shall include message type 1005 DSRC Messages CVE-DR1375-V01 Antenna Reference Point (ARP) coordinates at 2 Hz The RTCM shall include message type 1001 � GPS DSRC Messages CVE-DR1374-V01 L1 observations at 5 Hz The MAP Message shall contain the (connectingLane) DSRC Messages CVE-DR1164-V01 ConnectingLane data frame under the Connection data frame Roadside An RSU supplier shall provide the serial number for CVE-PY2908-V01 Equipment each RSU.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
156 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional Group ReqID Description
Roadside Equipment shall be contained in a traffic Roadside CVE-PY2912-V01 signal controller cabinet that is outfitted with tamper Equipment alert devices to prevent unauthorized access. An RSU shall broadcast (school zone) RSMs to a Roadside CVE-FN2972-V01 Transit Vehicle OBU when configured to perform this Equipment function. Roadside An RSU shall broadcast MAP messages loaded on the CVE-FN2973-V01 Equipment RSU to an HDV OBU Roadside An RSU shall send RSM messages loaded on the RSU CVE-IF2978-V01 Equipment to a Transit Vehicle OBU Roadside An RSU shall send RTCM messages received from the CVE-FN2979-V01 Equipment CORS or other source to an HDV OBU Roadside An RSU shall send RTCM messages received from the CVE-FN2980-V01 Equipment CORS or other source to a Transit Vehicle OBU Roadside An RSU shall send RTCM messages received from the CVE-FN2981-V01 Equipment CORS or other source to an EV OBU Roadside An RSU shall send SPaT messages generated from CVE-FN2982-V01 Equipment SPaT data output from the controller to an HDV OBU An RSU shall send SPaT messages generated from Roadside CVE-FN2983-V01 SPaT data output from the controller to a Transit Equipment Vehicle OBU Roadside An RSU shall send SSM messages received from the CVE-IF2985-V01 Equipment Traffic Signal Controller to a Transit Vehicle OBU Roadside An RSU shall send SSM messages received from the CVE-IF2986-V01 Equipment Traffic Signal Controller to an Emergency Vehicle OBU Roadside CVE-FN2987-V01 An RSU shall receive BSMs from an HDV OBU Equipment Roadside An RSU shall receive BSMs from a Transit Vehicle CVE-FN2988-V01 Equipment OBU Roadside An RSU shall receive BSMs from an Emergency CVE-FN2989-V01 Equipment Vehicle OBU Roadside An RSU shall receive SRMs from a Transit Vehicle CVE-FN2990-V01 Equipment OBU Roadside An RSU shall receive SRMs from an Emergency CVE-FN2991-V01 Equipment Vehicle OBU Roadside School Zone RSUs shall broadcast the RSM at a CVE-PR2994-V01 Equipment frequency of 1 Hz An RSU shall obtain position correction information Roadside from a Continuously Operating Reference Station CVE-FN1113-V01 Equipment (CORS) for packaging and broadcasting as the RTCM message. Roadside The RSU shall be able to send the SSM at a CVE-FN3000-V01 Equipment configurable rate
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 157 Appendix B. Requirements by System Functional Groups
Functional Group ReqID Description
Roadside An RSU shall acquire time from the LTS interface in CVE-FN1308-V01 Equipment accordance with J2945/1 section 6.2.4. Roadside An RSU shall acquire location from the LTS interface in CVE-FN1309-V01 Equipment accordance with J2945/1 section 6.2.1. Roadside An RSU shall broadcast (school zone) RSMs to an CVE-FN1310-V01 Equipment LDV OBU when configured to perform this function. An RSU shall use Coordinated Universal Time (UTC) Roadside time for all logged data (e.g., events logs, probe vehicle CVE-FN1311-V01 Equipment data) based on the format defined in J2735 section 6.19 and epoch of January 1st 1970. Roadside An RSU shall have access to a function that generates CVE-FN1312-V01 Equipment SPaT messages from SPaT data inputs Roadside An RSU shall have access to a function that generates CVE-FN1313-V01 Equipment RTCM messages from RTCM data inputs Roadside An RSU shall have access to a function that generates CVE-FN1314-V01 Equipment SSM messages from SSM data inputs An RSU shall comply with IEEE 1609.2: Standard for Roadside CVE-FN1315-V01 WAVE Security Services for Applications and Equipment Management Messages Select RSUs in/around designated school zones Roadside (Linden STEM Academy and Our Lady of Peace CVE-FN1316-V01 Equipment School) shall broadcast RSMs received from the Traffic CV Management System. Roadside RSU functionality failure shall not affect the safe CVE-FN1317-V01 Equipment operation of the signal controller. Roadside All roadside equipment (including RSUs) shall support CVE-FN1318-V01 Equipment remote authenticated access. An RSU shall broadcast the WSA for certificate Roadside download on control channel 178 and indicate IPv6 CVE-FN1319-V01 Equipment connectivity and the IP address on a service channel other than channel 172 or 178. An RSU shall implement a firewall blocking all IP Roadside CVE-FN1320-V01 access from devices to any IP address other than Equipment those approved for specific applications. Roadside CVE-FN1321-V01 An RSU shall support IPv6 tunneling over IPv4. Equipment Roadside An RSU shall report over a management interface if CVE-FN1322-V01 Equipment channel busy ratios go above a configurable threshold. Roadside An RSU shall delete old certificates upon location CVE-FN1323-V01 Equipment change. Roadside An RSU shall support setting the certificate geographic CVE-FN1324-V01 Equipment region to be requested for application certificates.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
158 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional Group ReqID Description
It shall be possible for a system administrator with the Roadside appropriate permissions to configure the RSU to CVE-FN1325-V01 Equipment request application certificates with only designated geographic locations. The CVE shall provide an interface to allow the system administrator to request new certificates bound to the Roadside CVE-FN1327-V01 new location if it moves from one location to another. Equipment (Note: its interface will allow requesting a new RSU application certificate with a site.) Roadside An RSU shall communicate using SNMPv3 with SNMP CVE-FN1328-V01 Equipment messages protected by being sent over TLS. An RSU shall support establishment of a standard TLS- based VPN with client authentication for Roadside communication to the Traffic CV Management System, CVE-FN1329-V01 Equipment with a long-term client cert and a single CA cert trusted to authorize connections from the Traffic CV Management System. An RSU shall verify received messages per IEEE Roadside CVE-FN1330-V01 1609.2 and per the relevant security profiles before Equipment using them for operations in any application. Roadside An RSU shall provide tamper evidence to detect CVE-FN1331-V01 Equipment tampering of the device (e.g. opening of the case). An RSU shall require that 1609.2 signed messages are signed by a certificate that is protected from Roadside CVE-FN1332-V01 modification by, or chains back to a certificate that is Equipment protected from modification by, the secure boot process. An RSU shall not create or transmit messages for any Roadside usage scenario if the usage scenario requires it to use CVE-FN1333-V01 Equipment 1609.2 certificates and it does not currently have valid certificates for that usage scenario An RSU shall verify a DSRC message if a device Roadside CVE-FN1334-V01 identifies the message as containing a new Equipment DE_TemporaryID value. Roadside An RSU supplier shall provide the enrollment certificate CVE-FN1335-V01 Equipment for each RSU. An RSU shall verify a DSRC message if the message Roadside CVE-FN1336-V01 results in the issuance of issue either advisory, Equipment warning, or alert Roadside RSUs shall support role-based authentication to enable CVE-SR1373-V01 Equipment physical access. Roadside Ethernet cable spans shall not exceed 100 meters (328 CVE-PY1372-V01 Equipment feet)
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 159 Appendix B. Requirements by System Functional Groups
Functional Group ReqID Description
Roadside RSU GPS antennas shall be located to maximize the CVE-PY1371-V01 Equipment GPS reception Roadside RSU DSRC antennas shall be located to maximize the CVE-PY1370-V01 Equipment DSRC range along the corridors of interest. The data elements MinuteOfTheYear and DSecond Roadside CVE-PR1369-V01 shall be present in each transmitted message and Equipment accurate within 100 ms of UTC time The time difference between maxEndTime (in the UTC Roadside CVE-PR1368-V01 reference system) and the earliest possible physical Equipment phase change shall be no larger than 100 ms The time difference between minEndTime (in the UTC Roadside CVE-PR1367-V01 reference system) and the earliest possible physical Equipment phase change shall be no larger than 100 ms Roadside All absolute times in any message shall be determined CVE-PR1366-V01 Equipment based on the RSU's system clock Roadside The system clock of the RSU shall be accurate to CVE-PR1365-V01 Equipment within 10 ms of the UTC reference Roadside RSUs shall support physical access to support CVE-MT1364-V01 Equipment maintenance activities. Roadside CVE-IF1363-V01 An RSU shall receive SRMs from an HDV OBU Equipment Roadside CVE-IF1362-V01 An RSU shall receive BSMs from an LDV OBU Equipment Roadside CVE-IF1361-V01 An RSU shall receive over the air messages via DSRC Equipment Roadside An RSU shall send RSM messages loaded on the RSU CVE-IF1360-V01 Equipment to an LDV OBU Roadside An RSU shall send SSM messages received from the CVE-IF1359-V01 Equipment Traffic Signal Controller to an HDV OBU Roadside An RSU shall send RTCM messages received from the CVE-IF1358-V01 Equipment CORS or other source to an LDV OBU Roadside An RSU shall send MAP messages loaded on the RSU CVE-IF1357-V01 Equipment to an LDV OBU Roadside An RSU shall send SPaT messages generated from CVE-IF1356-V01 Equipment SPaT data output from the controller to an LDV OBU Communication between the RSU and the SCMS shall operate in an encrypted, end-to-end connection in Roadside CVE-IF1354-V01 accordance with the selected SCMS interface. (Note: Equipment The SCMS interface should not need any further security.) The RSU-SCMS interface shall allow a RSU to request Roadside CVE-IF1353-V01 application certificates with different contents from the Equipment current ones during the lifetime of the current ones.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
160 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional Group ReqID Description
Ethernet cable that connects to equipment located Roadside CVE-IF1352-V01 outside of the traffic signal controller cabinet shall be Equipment shielded Ethernet cable that connects to equipment located Roadside CVE-IF1351-V01 outside of the traffic signal controller cabinet shall be Equipment weatherproof (outdoor rated) Ethernet cable that connects to equipment located Roadside CVE-IF1350-V01 outside of the traffic signal controller cabinet shall be Equipment outfitted with an in-line grounding mechanism Roadside CVE-IF1349-V01 An RSU shall be grounded Equipment Roadside CVE-IF1348-V01 An RSU shall be powered via power over Ethernet Equipment Roadside An RSU shall send information to request signal priority CVE-IF1347-V01 Equipment to the Traffic Signal Controller Roadside An RSU should receive SSMs from a Traffic Signal CVE-IF1346-V01 Equipment Controller Roadside An RSU shall receive SPaT messages from the Traffic CVE-IF1345-V01 Equipment Signal Controller Roadside An RSU shall receive security certificates from the CVE-IF1344-V01 Equipment SCMS Roadside CVE-IF1343-V01 An RSU shall receive position data from the LTS Equipment Roadside An RSU shall receive MAP messages from the Traffic CVE-IF1342-V01 Equipment CV Management System Roadside An RSU shall receive RSMs from the Traffic CV CVE-IF1341-V01 Equipment Management System An RSU shall receive data to populate a SSM from the Roadside CVE-IF1340-V01 Traffic Signal Controller or Other Roadside Computing Equipment Device Roadside An RSU shall receive data to populate RTCM message CVE-IF1339-V01 Equipment from the CORS An RSU shall verify a DSRC message if other potential Roadside CVE-FN1338-V01 threat situations such as red-light violations, and other Equipment safety applications. An RSU shall verify a DSRC message if the remote vehicle constitutes a potential threat (define potential Roadside CVE-FN1337-V01 threat as a vehicle that may collide with the host Equipment vehicle based on the both vehicle's speeds and trajectories) The Traffic CV Management System shall Traffic Management generate performance metrics (as defined in the CVE-FN2909-V01 Center Performance Measurement Plan) from data contained in CV messages that are captured.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 161 Appendix B. Requirements by System Functional Groups
Functional Group ReqID Description
Traffic Management The Traffic CV Management System shall remove PII CVE-FN2911-V01 Center from BSMs that are received before further processing The Traffic CV Management System shall use BSM Traffic Management data, SPaT data, MAP data, and RTCM data to CVE-DR1272-V01 Center generate the performance measures regarding red light compliance The Traffic CV Management System shall use BSM Traffic Management data, RSM data, and RTCM data to generate the CVE-DR1273-V01 Center performance measures regarding school zone speed compliance The Traffic CV Management System shall use BSM Traffic Management CVE-DR1274-V01 data to generate the TBD performance measure for Center (Vehicle Data for Traffic Operations) The Traffic CV Management System shall use BSM Traffic Management data from HDV OBUs to generate the travel time CVE-DR1275-V01 Center through intersection performance measure (for Freight Signal Priority, and Intent to Platoon Priority) The Traffic CV Management System shall remove PII Traffic Management CVE-DR1276-V01 from data prior to sending it to the Smart Columbus OS Center where it is made publicly available. The Traffic CV Management System shall alert the Traffic Management Traffic Manager when a tamper alert device detects CVE-FN1464-V01 Center that a traffic signal controller cabinet has been opened (or disturbed?) Traffic Management The Traffic CV Management System shall monitor CVE-FN1463-V01 Center tamper alert devices The Traffic CV Management System should investigate Traffic Management CVE-SR1461-V01 and monitor the data traffic usage to detect Center unapproved use of the IP connection. The Traffic CV Management System shall monitor the Traffic Management CVE-SR1460-V01 DSRC communications performance to detect DoS Center attacks. Traffic Management Monitoring systems shall be used to detect abnormal CVE-SR1459-V01 Center unauthorized activity on an IP connection. The Traffic CV Management System shall notify Traffic Management CVE-PR1458-V01 designated personnel within five minutes of a Center monitored function becoming unavailable The Traffic CV Management System shall notify designated personnel within five minutes of limited Traffic Management CVE-PR1457-V01 connectivity. Note: Limited connectivity refers to a state Center when the Traffic CV Management System is not able to communicate with the RSU
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
162 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional Group ReqID Description
Traffic Management The Traffic CV Management System shall receive CVE-FN1456-V01 Center BSMs from the RSU Traffic Management The Traffic CV Management System shall upload CVE-FN1455-V01 Center performance metrics to the Smart Columbus OS The Traffic CV Management System should use CV Traffic Management data made available through the CV Environment to CVE-FN1454-V01 Center generate performance metrics as defined in the Performance Management Plan (TBD) The Traffic CV Management System should automate Traffic Management CVE-FN1453-V01 the generation of performance metrics as defined in the Center Performance Management Plan (TBD) Traffic Management The Traffic CV Management System shall make the CVE-FN1452-V01 Center status of all RSUs available to the Traffic Manager The Traffic CV Management System shall alert the Traffic Management CVE-FN1451-V01 Traffic Manager if an RSU is not running normally (off, Center not responding, in safe mode, etc.) Traffic Management The Traffic CV Management System shall alert the CVE-FN1450-V01 Center Traffic Manager if an RSU is offline Traffic Management The Traffic CV Management System shall monitor the CVE-FN1449-V01 Center status of RSUs The Traffic CV Management System shall have access Traffic Management CVE-FN1448-V01 to a function that generates MAP messages from MAP Center data inputs The Traffic CV Management System shall have access Traffic Management CVE-FN1447-V01 to a function that generates RSM messages from RSM Center data inputs The Traffic CV Management System shall provide the VISA' functions of Validation, Integration, Sanitization Traffic Management CVE-FN1446-V01 (De-identification), and Aggregation of CV Data as Center defined in the U.S DOT SEMI ODE requirements (Reference TBR) Traffic Management The Traffic CV Management System shall make the CVE-FN1445-V01 Center status of RSUs available to Traffic Management Staff The Traffic CV Management System shall accept input Traffic Management CVE-FN1444-V01 for configurable parameters from Traffic Management Center Staff Traffic Management The Traffic CV Management System shall accept input CVE-FN1443-V01 Center for MAP messages from Traffic Management Staff Traffic Management The Traffic CV Management System shall accept input CVE-FN1442-V01 Center for RSM messages from Traffic Management Staff Traffic Management The Traffic CV Management System shall enable CVE-FN1441-V01 Center loading of MAP messages on the RSU
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 163 Appendix B. Requirements by System Functional Groups
Functional Group ReqID Description
Traffic Management The Traffic CV Management System shall enable CVE-FN1440-V01 Center loading of RSMs on the RSU Traffic Management The Traffic CV Management System shall send MAP CVE-FN1439-V01 Center messages to the Smart Columbus OS Traffic Management The Traffic CV Management System shall send PII- CVE-FN1438-V01 Center removed RSMs to the Smart Columbus OS The Traffic CV Management System shall transmit Traffic Management performance metrics (as defined in the Performance CVE-FN1437-V01 Center Measurement Plan) derived from BSMs to the Smart Columbus OS An RSU shall consider the priority requests from both HDV OBUs as a single priority request that is able to Traffic Signal Priority CVE-FN1487-V01 accommodate priority for both vehicles through the Applications intersection if it is determined that the vehicles intend to platoon An RSU should use data received from the Platooning Traffic Signal Priority CVE-FN1486-V01 System to determine if the HDV OBUs sending SRMs Applications intend to form a platoon Traffic Signal Priority An RSU shall determine if SRMs received from multiple CVE-FN1485-V01 Applications freight vehicles are intending to form a platoon Traffic Signal Priority The TSP Application shall generate data for the SRM CVE-DR1478-V01 Applications Message Traffic Signal Priority The TSP Application shall require data from the SSM CVE-DR1477-V01 Applications Message The Transit CV Management System shall Transit Management generate performance metrics (as defined in the CVE-IF1277-V01 Center Performance Measurement Plan derived from COTA operations data) Transit Management The Transit CV Management System shall make CVE-IF1473-V01 Center interaction data available to Transit Management Staff Transit Management The Transit CV Management System shall send CVE-IF1472-V01 Center interaction data to the Smart Columbus OS Transit Management The Transit CV Management System may use user CVE-FN1471-V01 Center surveys to generate performance measures Transit Management The Transit CV Management System may use COTA CVE-FN1470-V01 Center CAD/AVL data to generate performance measures The Transit CV Management System shall collect data Transit Management CVE-FN1469-V01 to generate the headway reliability performance Center measure (for Transit Signal Priority) The Transit CV Management System shall collect data Transit Management CVE-FN1468-V01 to generate the running time performance measure (for Center Transit Signal Priority)
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
164 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional Group ReqID Description
The Transit CV Management System shall collect data Transit Management CVE-FN1467-V01 to generate the on-time performance measure (for Center Transit Signal Priority) The Transit CV Management System shall collect Transit Management interaction data to generate the TBD performance CVE-FN1466-V01 Center measure (for Transit Vehicle Interaction Event Recording) Transit Management The CVE should remain operational after the CVE-DP1465-V01 Center completion of the deployment period The VDTO Application shall receive data from the V2I Mobility CVE-IF1592-V01 OBU's internal processing functions. The Traffic CV Management System shall make all V2I Mobility CVE-FN1591-V01 stored data available to the Traffic Manager The Traffic CV Management System shall store all V2I Mobility CVE-FN1590-V01 MAP messages that are input by the Traffic Manager The Traffic CV Management System shall store all V2I Mobility CVE-FN1589-V01 logged RSM messages sent by the RSU The Traffic CV Management System shall store all V2I Mobility CVE-FN1588-V01 logged SPaT messages sent by the RSU The Traffic CV Management System shall store all V2I Mobility CVE-FN1587-V01 logged SSMs sent by the RSU The Traffic CV Management System shall store all V2I Mobility CVE-FN1586-V01 logged SRMs sent by the RSU The Traffic CV Management System shall store all V2I Mobility CVE-FN1585-V01 logged BSMs sent by the RSU The Traffic CV Management System shall receive all V2I Mobility CVE-FN1584-V01 logged RSM messages sent by the RSU The Traffic CV Management System shall receive all V2I Mobility CVE-FN1583-V01 logged SPaT messages sent by the RSU The Traffic CV Management System shall receive all V2I Mobility CVE-FN1582-V01 logged SSMs sent by the RSU The Traffic CV Management System shall receive all V2I Mobility CVE-FN1581-V01 logged SRMs sent by the RSU The Traffic CV Management System shall receive all V2I Mobility CVE-FN1580-V01 logged BSMs sent by the RSU The RSU should not log duplicate RSMs during a V2I Mobility CVE-FN1579-V01 configurable time interval V2I Mobility CVE-FN1578-V01 The RSU shall log RSMs at a configurable frequency The RSU shall send logged RSMs to the Traffic CV V2I Mobility CVE-FN1577-V01 Management System at a configurable time interval The RSU should not log duplicate MAP messages V2I Mobility CVE-FN1576-V01 during a configurable time interval
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 165 Appendix B. Requirements by System Functional Groups
Functional Group ReqID Description
The RSU shall log MAP messages at a configurable V2I Mobility CVE-FN1575-V01 frequency The RSU shall not log a SPaT message unless there is a change in configurable select data elements (e.g. V2I Mobility CVE-FN1574-V01 minEndTime, maxEndTime, etc.) from the previously logged message The RSU shall log SPaT messages at a configurable V2I Mobility CVE-FN1573-V01 frequency The RSU shall send logged SPaT messages to the V2I Mobility CVE-FN1572-V01 Traffic CV Management System at a configurable time interval The RSU should not log duplicate SSMs during a V2I Mobility CVE-FN1571-V01 configurable time interval The RSU shall log SSMs received from a traffic signal V2I Mobility CVE-FN1570-V01 controller at a configurable frequency The RSU shall send logged SSMs to the Traffic CV V2I Mobility CVE-FN1569-V01 Management System at a configurable time interval. The RSU shall log SRMs received from a given OBU at V2I Mobility CVE-FN1567-V01 a configurable frequency The RSU shall send logged SRMs to the Traffic CV V2I Mobility CVE-FN1566-V01 Management System at a configurable time interval The RSU shall log BSMs received from a given OBU at V2I Mobility CVE-FN1565-V01 a configurable frequency (10 Hz max) The RSU shall send logged BSMs to the Traffic CV V2I Mobility CVE-FN1564-V01 Management System at a configurable time interval The RSU shall delete logged BSMs once it has verified V2I Mobility CVE-FN1563-V01 that the logged BSMs have been received by the Traffic CV Management System The VDTO Application shall capture data from the all V2I Mobility CVE-DR1562-V01 messages transmitted or received by an RSU The TIVER Application shall transmit and receive data V2I Mobility CVE-IF1561-V01 from the OBU's internal processing functions. A Transit Vehicle Interaction Event shall consist of all locally stored messages (SPaT, MAP, received BSMs, V2I Mobility CVE-FN1560-V01 broadcast BSMs) from a configurable amount of time after the end time of the event A Transit Vehicle Interaction Event shall consist of all locally stored messages (SPaT, MAP, received BSMs, V2I Mobility CVE-FN1559-V01 broadcast BSMs) from a configurable amount of time before the start time of the event
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
166 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional Group ReqID Description
A Transit Vehicle Interaction Event event shall consist of the end time of the event (UTC) (in the case where V2I Mobility CVE-FN1558-V01 multiple events of the same warning are issued based on messages received from the same vehicle or intersection within a configurable amount of time) A Transit Vehicle Interaction Event shall consist of the V2I Mobility CVE-FN1557-V01 start time of the safety interaction event (UTC) A Transit Vehicle OBU shall remove all Transit Vehicle V2I Mobility CVE-FN1556-V01 Interaction Event data from memory once uploaded to the Transit CV Management System. A Transit Vehicle OBU shall upload all Transit Vehicle Interaction Event data to the Transit CV Management V2I Mobility CVE-FN1555-V01 System when it connects to the vehicle's regular data upload service. A Transit Vehicle OBU shall remove Transit Vehicle Interaction Event data with the oldest start times from V2I Mobility CVE-FN1554-V01 memory until it is able to log a newly received interaction event The RSU shall delete logged SRMs once it has verified V2I Mobility CVE-FN2914-V01 that the logged SRMs have been received by the Traffic CV Management System The RSU shall delete logged SSMs once it has verified V2I Mobility CVE-FN2915-V01 that the logged SSMs have been received by the Traffic CV Management System The RSU shall delete logged SPaT Messages one it V2I Mobility CVE-FN2916-V01 has verified that the logged SPaT messages have been received by the Traffic CV Management System. The RSU shall send logged MAP messages to the V2I Mobility CVE-FN2917-V01 Traffic CV Management Center at a configurable time interval The RSU shall delete logged MAP message once it V2I Mobility CVE-FN2918-V01 has verified that the logged MAP messages have been received by the Traffic CV Management System The RSU should not log duplicate RSMs during a V2I Mobility CVE-FN2919-V01 configurable time interval The RSU shall delete logged RSMs once it has verified V2I Mobility CVE-FN2920-V01 that the logged RSMs have been received by the Traffic CV Management System A Transit Vehicle OBU shall log a Transit Vehicle V2I Mobility CVE-FN1551-V01 Interaction Event when the transit vehicle OBU broadcasts an SRM
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 167 Appendix B. Requirements by System Functional Groups
Functional Group ReqID Description
A Transit Vehicle Interaction Event shall consist of the type of event (emergency braking ahead, forward V2I Mobility CVE-FN1550-V01 collision imminent, intersection movement, blind spot, lane change, red light violation, school zone speed limit, priority request) A Transit Vehicle OBU shall store any SSMs received V2I Mobility CVE-FN1549-V01 in local memory for a configurable amount of time. A Transit Vehicle OBU shall store any SRMs broadcast V2I Mobility CVE-FN1548-V01 in local memory for a configurable amount of time. A Transit Vehicle OBU shall store any BSMs broadcast V2I Mobility CVE-FN1547-V01 in local memory for a configurable amount of time. A Transit Vehicle OBU shall store any MAP messages V2I Mobility CVE-FN1546-V01 received in local memory for a configurable amount of time. A Transit Vehicle OBU shall store any SPaT messages V2I Mobility CVE-FN1545-V01 received in local memory for a configurable amount of time. A Transit Vehicle OBU shall store any BSMs received V2I Mobility CVE-FN1544-V01 in local memory for a configurable amount of time. A Transit Vehicle OBU shall log a Transit Vehicle Interaction Event when the vehicle is inside of an RSU- V2I Mobility CVE-FN1543-V01 equipped school zone over the active school zone speed limit A Transit Vehicle OBU shall log a Transit Vehicle Interaction Event when the vehicle will enter an RSU- V2I Mobility CVE-FN1542-V01 equipped school zone over the active school zone speed limit A Transit Vehicle OBU shall log a Transit Vehicle V2I Mobility CVE-FN1541-V01 Interaction Event when the vehicle will run a red light at an RSU-equipped intersection A Transit Vehicle OBU shall log a Transit Vehicle V2I Mobility CVE-FN1540-V01 Interaction Event when it is changing lanes into another OBU-equipped (remote) vehicle A Transit Vehicle OBU shall log a Transit Vehicle V2I Mobility CVE-FN1539-V01 Interaction Event when there is an OBU-equipped (remote) vehicle in the host vehicle's blind spot A Transit Vehicle OBU shall log a Transit Vehicle Interaction Event when there is an approaching OBU- V2I Mobility CVE-FN1538-V01 equipped (remote) vehicle on a conflicting approach at an intersection A Transit Vehicle OBU shall log a Transit Vehicle V2I Mobility CVE-FN1537-V01 Interaction Event when a forward collision is imminent with another OBU-equipped (remote) vehicle
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
168 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional Group ReqID Description
A Transit Vehicle OBU shall log a Transit Vehicle V2I Mobility CVE-FN1536-V01 Interaction Event when there is emergency braking ahead by an OBU-equipped (remote) vehicle V2I Mobility CVE-FN1535-V01 A Transit Vehicle OBU shall not issue alerts A Transit Vehicle OBU shall determine when to record a Transit Vehicle Interaction Event. Note: A Transit V2I Mobility CVE-FN1534-V01 Vehicle Interaction Event contains the type of event along with a log of BSMs sent/received before and after the event. The TVIER Application shall capture data from the all V2I Mobility CVE-DR1533-V01 applicatiosn deployed on the Transit Vehicle An Emergency Vehicle OBU (host) shall issue a signal preemption notification to the Emergency Vehicle V2I Mobility CVE-PR1532-V01 Operator via the HMI when preemption has been granted The EVP application (see Appendix B) shall meet TRL 6 criteria (has been tested in a realistic envrionment V2I Mobility CVE-PR1531-V01 outside of a laboratory and satisfies operational requirements when confronted with realistic problems) The TSP application (see Appendix B) shall meet TRL 6 criteria (has been tested in a realistic envrionment V2I Mobility CVE-PR1530-V01 outside of a laboratory and satisfies operational requirements when confronted with realistic problems) The TSP application (see Appendix B) should employ V2I Mobility CVE-PR1529-V01 algorithms that are used in MMITSS to enable transit signal priority The FSP application (see Appendix B) shall meet TRL 6 criteria (has been tested in a realistic envrionment V2I Mobility CVE-PR1528-V01 outside of a laboratory and satisfies operational requirements when confronted with realistic problems) The FSP application (see Appendix B) should employ V2I Mobility CVE-PR1527-V01 algorithms that are used in MMITSS to enable freight signal priority The TSP Application shall transmit and receive data V2I Mobility CVE-IF1526-V01 from the OBU's internal processing functions. The RSU shall receive the list of vehicle OBU IDs that V2I Mobility CVE-FN1525-V01 are authorized to receive signal preemption at the intersection it is located at The RSU shall receive the list of vehicle OBU IDs that V2I Mobility CVE-FN1524-V01 are authorized to receive signal priority at the intersection it is located at
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 169 Appendix B. Requirements by System Functional Groups
Functional Group ReqID Description The Traffic CV Management System shall transmit a list of vehicle OBU IDs that are authorized to receive V2I Mobility CVE-FN1523-V01 signal preemption at a given intersection to the RSU at that intersection when a change in the list has been made. The Traffic CV Management System shall transmit a list of vehicle OBU IDs that are authorized to receive V2I Mobility CVE-FN1522-V01 signal priority at a given intersection to the RSU at that intersection when a change in the list has been made. The Traffic CV Management System shall maintain a modifiable list of intersections for which each V2I Mobility CVE-FN1521-V01 authorized OBU is allowed to request priority or preemption at. The Traffic CV Management System shall maintain a V2I Mobility CVE-FN1520-V01 modifiable list of OBU IDs authorized to send SRMs An RSU shall send a SSM to an HDV OBU containing V2I Mobility CVE-FN1519-V01 the results of the requests made by one or more vehicles for a configurable period of time An RSU shall receive output from the Traffic Signal V2I Mobility CVE-FN1518-V01 Controller regarding the status of a priority request The Traffic Signal Controller shall extend the current phase for a movement that is requested in a V2I Mobility CVE-FN1517-V01 preemption SRM when the approach for the requested movement is green The Traffic Signal Controller shall wait for the light to turn red before servicing a phase for a movement that V2I Mobility CVE-FN1516-V01 is requested in a preemption SRM when the approach for the requested movement is yellow The Traffic Signal Controller shall next service a phase V2I Mobility CVE-FN1515-V01 for a movement that is requested in a preemption SRM when the approach for the requested movement is red The Traffic Signal Controller shall not reduce the duration of a pedestrian clearance interval before V2I Mobility CVE-FN1514-V01 progressing to the next phase when servicing a priority or preemption request The Traffic Signal Controller should immediately proceed to a pedestrian clearance phase if an active V2I Mobility CVE-FN1513-V01 pedestrian phase is ongoing when servicing a priority or preemption request The Traffic Signal Controller should minimize the length V2I Mobility CVE-FN1512-V01 of preceding phases to accommodate a priority request The Traffic Signal Controller shall not adjust the typical V2I Mobility CVE-FN1511-V01 progression of phases to accommodate a priority request
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
170 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional Group ReqID Description
The Traffic Signal Controller shall grant an extended green for a phase for a movement that is requested in V2I Mobility CVE-FN1510-V01 a priority SRM when the approach for the requested movement is green The Traffic Signal Controller shall grant an early green for a phase for a movement that is requested in a V2I Mobility CVE-FN1509-V01 priority SRM when the approach for that movement is red or yellow
An RSU shall place a priority request or a preemption request to the traffic signal controller for the movement specified in the SRM if the following conditions are concurrently met: 1. An OBU ID (from the received V2I Mobility CVE-FN1508-V01 SRM) matches against the locally-stored list of vehicle OBU IDs that are authorized to receive signal priority. 2. The intersection ID in the SRM matches the intersection ID
An RSU shall use a locally-stored list of vehicle OBU IDs that are authorized to receive signal preemption at V2I Mobility CVE-FN1507-V01 the intersection to determine if a received SRM is sent from an OBU that is authorized to make preemption requests at that intersection An RSU shall use a locally-stored list of vehicle OBU IDs that are authorized to receive signal priority at the V2I Mobility CVE-FN1506-V01 intersection to determine if a received SRM is sent from an OBU that is authorized to make priority requests at that intersection Multiple low priority requests shall be serviced in the V2I Mobility CVE-FN1505-V01 order in which they are received Multiple high priority requests shall be serviced in the V2I Mobility CVE-FN1504-V01 order in which they are received High priority requests to receive signal priority shall be V2I Mobility CVE-FN1503-V01 serviced before low priority requests to receive signal priority A request to receive signal priority from an HDV V2I Mobility CVE-FN1502-V01 Vehicle OBU shall be low priority A request to receive signal priority from a Transit V2I Mobility CVE-FN1501-V01 Vehicle OBU shall be low priority A request to receive signal preemption from a Public V2I Mobility CVE-FN1500-V01 Safety Vehicle OBU shall be high priority The SRM shall contain information regarding the V2I Mobility CVE-FN1499-V01 movement for which priority is being requested
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 171 Appendix B. Requirements by System Functional Groups
Functional Group ReqID Description
The SRM shall contain the intersection ID that is V2I Mobility CVE-FN1498-V01 provided in the MAP message for the priority requested intersection The EVP application (see Appendix B) should employ V2I Mobility CVE-FN1497-V01 algorithms that are used in MMITSS to enable emergency vehicle preemption An Emergency Vehicle OBU shall request to receive V2I Mobility CVE-FN1493-V01 signal preemption at RSU-equipped intersections An Transit Vehicle OBU shall cease broadcasting SRMs for priority at a given intersection for a V2I Mobility CVE-FN1492-V01 configurable amount of time after it has received an SSM from that intersection that contains the Transit Vehicle OBU ID A Transit Vehicle OBU shall only request priority for V2I Mobility CVE-FN1491-V01 movements along the route being traversed by that transit vehicle A Transit Vehicle OBU shall only request priority in an V2I Mobility CVE-FN1490-V01 SRM A Transit Vehicle OBU shall send a SRM to an RSU V2I Mobility CVE-FN1489-V01 when it is within a configurable distance of the intersection it intends to request priority for A Transit Vehicle OBU shall request to receive signal V2I Mobility CVE-FN1488-V01 priority at RSU-equipped intersections An HDV OBU shall cease broadcasting SRMs for priority at a given intersection for a configurable V2I Mobility CVE-FN1484-V01 amount of time after it has received an SSM from that intersection that contains the HDV OBU ID V2I Mobility CVE-FN1483-V01 An HDV OBU shall only request priority in a SRM An HDV OBU shall only request priority for movements V2I Mobility CVE-FN1482-V01 along the designated freight route An HDV OBU shall broadcast a SRM when it is within a V2I Mobility CVE-FN1481-V01 configurable distance of the intersection it intends to request priority for An HDV OBU shall broadcast a SRM when V2I Mobility CVE-FN1480-V01 approaching an RSU-equipped intersection An HDV OBU shall request to receive signal priority at V2I Mobility CVE-FN1479-V01 RSU-equipped intersections V2I Safety The RLVW Application shall require data from the CVE-DR1283-V01 Application SPAT Message V2I Safety The RLVW Application shall require data from the MAP CVE-DR1284-V01 Application Message V2I Safety The RLVW Application shall require data from the CVE-DR1285-V01 Application RTCM Message
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
172 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional Group ReqID Description
An LDV OBU (host) shall issue an alert to the LDV V2I Safety CVE-FN1286-V01 Operator via the HMI when a red-light violation will Application occur at an RSU-equipped intersection An LDV OBU (host) shall determine if the OBU- V2I Safety CVE-FN1287-V01 equipped (host) vehicle will run a red light for each Application SPaT message it receives
A red-light violation shall be occurring if all of the following conditions are concurrently met: 1. An OBU- equipped vehicle is approaching an RSU-equipped intersection. 2. The OBU-equipped vehicle's trajectory V2I Safety CVE-FN1288-V01 (based on location, speed, acceleration) will cross the Application stop bar when the light is red with a configurable amount of confidence (factors that affect confidence include positioning error and uncertainty in the change of signal state)
V2I Safety The RLVW Application shall receive data from the CVE-IF1289-V01 Application OBU's internal processing functions. The RLVW application (see Appendix B) should V2I Safety CVE-PR1290-V01 employ algorithms that are used in applications verified Application by CAMP to issue an RLVW The RLVW application (see Appendix B) shall meet TRL 6 criteria (has been tested in a realistic V2I Safety CVE-PR1291-V01 environment outside of a laboratory and satisfies Application operational requirements when confronted with realistic problems) V2I Safety The RSSZ Application shall require data from the RSM CVE-DR1297-V01 Application Message An LDV OBU (host) shall issue an alert to the LDV V2I Safety Operator via the HMI when the OBU-equipped (host) CVE-FN1298-V01 Application vehicle will enter an RSU-equipped school zone over the active school zone speed limit� An LDV OBU (host) shall issue an alert when the OBU- V2I Safety CVE-FN1299-V01 equipped (host) vehicle is inside of an RSU-equipped Application school zone over the active school zone speed limit V2I Safety The LDV OBU (host) shall parse received RSMs to CVE-FN1300-V01 Application identify the school zone speed limit (J2945/4). V2I Safety The LDV OBU (host) shall parse received RSMs to CVE-FN1301-V01 Application identify when the school zone speed limit is active. The LDV OBU (host) shall parse received RSMs to V2I Safety CVE-FN1302-V01 identify the applicable regions of use geographical path Application (J2945/4).
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 173 Appendix B. Requirements by System Functional Groups
Functional Group ReqID Description The LDV OBU (host) shall issue a school zone alert when all of the following conditions are concurrently met: 1. OBU-equipped (host) vehicle is traveling towards the segment where the situational awareness V2I Safety CVE-FN1303-V01 applies. 2. The OBU-equipped (host) vehicle is Application expected to enter the school zone but not below the school zone speed limit (given its current location, motion, and expected braking rate) . 3. During active school zone hours The LDV OBU (host) shall issue a school zone alert when all of the following conditions are concurrently met: 1. OBU-equipped (host) vehicle is within the V2I Safety CVE-FN1304-V01 segment where the situational awareness applies. 2. Application OBU-equipped (host) vehicle is traveling above the school zone speed limit. 3. During active school zone hours V2I Safety The RSSZ Application shall receive data from the CVE-IF1305-V01 Application OBU's internal processing functions. The RSSZ application (see Appendix B) should employ V2I Safety CVE-PR1306-V01 algorithms that are used in applications verified by Application CAMP to issue an RSSZ warning The RSSZ application (see Appendix B) shall meet TRL 6 criteria (has been tested in a realistic V2I Safety CVE-PR1307-V01 environment outside of a laboratory and satisfies Application operational requirements when confronted with realistic problems) The EEBL application (see Appendix B) should employ V2V Safety CVE-PR1119-V01 algorithms that are used in applications verified by CAMP to issue an EEBL alert. A lane change collision shall be imminent if all of the following conditions are concurrently met: 1. The OBU- equipped (host) vehicle has a trajectory (based on V2V Safety CVE-FN1140-V01 position, speed, acceleration) that may interfere with an OBU-equipped (remote) vehicle trajectory in a sideswipe fashion. The LCW application (see Appendix B) shall meet TRL V2V Safety 6 criteria (has been tested in a realistic environment CVE-PR1143-V01 Application outside of a laboratory and satisfies operational requirements when confronted with realistic problems) V2V Safety The BSW Application shall require data from the BSM CVE-DR1106-V01 Application Message An LDV OBU (host) shall issue an alert to the LDV V2V Safety CVE-FN1107-V01 Operator via the HMI when there is an OBU-equipped Application (remote) vehicle in the host vehicle's blind spot V2V Safety An LDV OBU (host) shall determine if a vehicle is in its CVE-FN1108-V01 Application blind spot for each BSM it receives
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
174 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional Group ReqID Description
A vehicle shall be in a blind spot if all of the following conditions are concurrently met: 1. The OBU-equipped (host) vehicle is traveling in the same direction as the OBU-equipped (remote) vehicle. 2. The OBU- V2V Safety CVE-FN1109-V01 equipped (remote) vehicle is located in a configurable Application zone (rear left and rear right of the OBU-equipped host vehicle) with a configurable amount of confidence (factors that affect confidence include positioning error for the host and remote vehicle)
V2V Safety The BSW Application shall receive data from the CVE-IF1110-V01 Application OBU's internal processing functions. The BSW application (see Appendix B) should employ V2V Safety CVE-PR1111-V01 algorithms that are used in MMITSS to issue a BSW Application alert. The BSW application (see Appendix B) shall meet TRL V2V Safety 6 criteria (has been tested in a realistic environment CVE-PR1112-V01 Application outside of a laboratory and satisfies operational requirements when confronted with realistic problems) V2V Safety The EEBL Application shall require data from the BSM CVE-DR1114-V01 Application Message An LDV OBU (host) shall issue an alert to the LDV V2V Safety CVE-FN1115-V01 Operator via the HMI �when there is emergency Application braking ahead by an OBU-equipped (remote) vehicle V2V Safety An LDV OBU (host) shall determine if there is CVE-FN1116-V01 Application emergency braking ahead for each BSM it receives Emergency braking ahead shall be occurring if all of the following conditions are concurrently met: 1. An OBU-equipped (remote) vehicle is braking in an emergency fashion. 2. The distance between the OBU-equipped (host) vehicle and OBU-equipped V2V Safety CVE-FN1117-V01 (remote) vehicle is less than a distance threshold that Application is a function of the speed of the host vehicle. 3. The OBU-equipped (host) vehicle is approaching the OBU- equipped (remote) vehicle. 4. The OBU-equipped (host) vehicle is moving in the same direction as the OBU-equipped (remote) vehicle. V2V Safety The EEBL Application shall receive data from the CVE-IF1118-V01 Application OBU's internal processing functions. The EEBL application (see Appendix B) shall meet TRL V2V Safety 6 criteria (has been tested in a realistic environment CVE-PR1120-V01 Application outside of a laboratory and satisfies operational requirements when confronted with realistic problems) V2V Safety The FCW Application shall require data from the BSM CVE-DR1121-V01 Application Message
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 175 Appendix B. Requirements by System Functional Groups
Functional Group ReqID Description
An LDV OBU (host) shall issue an alert to the LDV V2V Safety CVE-FN1122-V01 Operator via the LDV HMI when a forward collision is Application imminent with another OBU-equipped (remote) vehicle V2V Safety An LDV OBU (host) shall determine if a forward CVE-FN1124-V01 Application collision is imminent for each BSM it receives A forward collision shall be imminent if all of the following conditions are concurrently met: 1. The distance between the OBU-equipped (host) vehicle and V2V Safety OBU-equipped (remote) vehicle is less than a distance CVE-FN1125-V01 Application threshold that is a function of the speed of the host vehicle and the remote vehicle.. 2. The OBU-equipped (host) vehicle is approaching the OBU-equipped (remote) vehicle. V2V Safety The FCW Application shall receive data from the CVE-IF1126-V01 Application OBU's internal processing functions. The FCW application (see Appendix B) should employ V2V Safety CVE-PR1127-V01 algorithms that are used in applications verified by Application CAMP to issue a FCW alert The FCW application (see Appendix B) shall meet TRL V2V Safety 6 criteria (has been tested in a realistic environment CVE-PR1128-V01 Application outside of a laboratory and satisfies operational requirements when confronted with realistic problems) V2V Safety The IMA Application shall require data from the BSM CVE-DR1130-V01 Application Message An LDV OBU (host) shall issue an alert to the LDV V2V Safety CVE-FN1131-V01 Operator via the HMI when an intersection collision is Application imminent with another OBU-equipped (remote) vehicle V2V Safety An LDV OBU (host) shall determine if an intersection CVE-FN1132-V01 Application collision is imminent for each BSM it receives
An intersection collision shall be imminent if all of the following conditions are concurrently met: 1. The OBU- equipped (host) vehicle has a trajectory (based on position, speed, acceleration) that may interfere with an V2V Safety OBU-equipped (remote) vehicle trajectory in a side CVE-FN1133-V01 Application impact fashion. 2. The distance between the OBU- equipped (host) vehicle and OBU-equipped (remote) vehicle is less than a distance threshold that is a function of the speed of the host vehicle and the remote vehicle.
V2V Safety The IMA Application shall receive data from the OBU's CVE-IF1134-V01 Application internal processing functions.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
176 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional Group ReqID Description
The IMA application (see Appendix B) should employ V2V Safety CVE-PR1135-V01 algorithms that are used in applications verified by Application CAMP to issue an IMA alert The IMA application (see Appendix B) shall meet TRL V2V Safety 6 criteria (has been tested in a realistic environment CVE-PR1136-V01 Application outside of a laboratory and satisfies operational requirements when confronted with realistic problems) V2V Safety The LCW Application shall require data from the BSM CVE-DR1137-V01 Application Message An LDV OBU (host) shall issue an alert to the LDV V2V Safety CVE-FN1138-V01 Operator via the HMI when it is changing lanes into Application another OBU-equipped (remote) vehicle V2V Safety An LDV OBU (host) shall determine if a lane change CVE-FN1139-V01 Application collision is imminent for each BSM it receives V2V Safety The LCW Application shall receive data from the OBU's CVE-IF1141-V01 Application internal processing functions. The LCW application (see Appendix B) should employ V2V Safety CVE-PR1142-V01 algorithms that are used in applications verified by Application CAMP to issue a LCW alert A forward collision shall be imminent if the distance between the OBU-equipped (host) vehicle and OBU- V2V Safety CVE-FN2462-V01 equipped (remote) vehicle is less than a distance Application threshold that is a function of the speed of the host vehicle and the remote vehicle. A forward collision shall be imminent if the OBU- V2V Safety CVE-FN2463-V01 equipped (host) vehicle is approaching the OBU- Application equipped (remote) vehicle. The OBU shall have a minimum reserve (processor, Vehicle Onboard CVE-PR2907-V01 dynamic storage, persistent storage) capacity of XX % Equipment for its current and new firmware images. Vehicle Onboard A Transit Vehicle OBU shall be capable of holding 4 CVE-PR2913-V01 Equipment GB of interaction event data. Vehicle Onboard An LDV OBU shall receive BSMs from an Transit CVE-FN2952-V01 Equipment Vehicle OBU Vehicle Onboard An LDV OBU shall receive BSMs from an Emergency CVE-FN2953-V01 Equipment Vehicle OBU Vehicle Onboard A Transit Vehicle OBU shall receive BSMs from an CVE-FN2954-V01 Equipment HDV OBU Vehicle Onboard A Transit Vehicle OBU shall receive BSMs from a CVE-FN2955-V01 Equipment Transit Vehicle OBU Vehicle Onboard A Transit Vehicle OBU shall receive BSMs from an CVE-FN2956-V01 Equipment Emergency Vehicle OBU
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 177 Appendix B. Requirements by System Functional Groups
Functional Group ReqID Description
Vehicle Onboard An Emergency Vehicle OBU shall send BSMs (Part I) CVE-FN2957-V01 Equipment consistent with SAE J2735 to a Transit Vehicle OBU Vehicle Onboard An Emergency Vehicle OBU shall send BSMs (Part I) CVE-FN2958-V01 Equipment consistent with SAE J2735 to an RSU Vehicle Onboard An HDV OBU shall receive position data from GNSS CVE-FN2959-V01 Equipment satellites Vehicle Onboard A Transit Vehicle OBU shall receive position data from CVE-FN2960-V01 Equipment GNSS satellites Vehicle Onboard An Emergency Vehicle OBU shall receive position data CVE-FN2961-V01 Equipment from GNSS satellites Vehicle Onboard An HDV OBU shall receive security certificates from CVE-FN2962-V01 Equipment the SCMS via the RSU Vehicle Onboard An Transit Vehicle OBU shall receive security CVE-FN2963-V01 Equipment certificates from the SCMS via the RSU Vehicle Onboard An Emergency Vehicle OBU shall receive security CVE-FN2964-V01 Equipment certificates from the SCMS via the RSU Vehicle Onboard A Transit Vehicle OBU shall broadcast BSMs (Part I) CVE-FN2966-V01 Equipment consistent with SAE J2735 to a Transit Vehicle OBU Vehicle Onboard A Transit Vehicle OBU shall broadcast BSMs (Part I) CVE-FN2967-V01 Equipment consistent with SAE J2735 to an RSU Vehicle Onboard An HDV OBU shall send BSMs (Part I and Part II) CVE-FN2968-V01 Equipment consistent with SAE J2735 to a Transit Vehicle OBU Vehicle Onboard An HDV OBU shall send BSMs (Part I and Part II) CVE-FN2969-V01 Equipment consistent with SAE J2735 to an RSU Vehicle Onboard An LDV OBU shall broadcast BSMs (Part I) consistent CVE-FN2970-V01 Equipment with SAE J2735 to a Transit Vehicle OBU Vehicle Onboard An LDV OBU shall broadcast BSMs (Part I) consistent CVE-FN2971-V01 Equipment with SAE J2735 to an RSU Vehicle Onboard An RSU shall broadcast MAP messages loaded on the CVE-FN2974-V01 Equipment RSU to a Transit Vehicle OBU Vehicle Onboard An RSU shall broadcast MAP messages loaded on the CVE-FN2975-V01 Equipment RSU to an Emergency Vehicle OBU An RSU shall send a SSM to a Transit Vehicle OBU Vehicle Onboard CVE-FN2976-V01 containing the results of the requests made by one or Equipment more vehicles for a configurable period of time An RSU shall send a SSM to an EV OBU containing Vehicle Onboard CVE-FN2977-V01 the results of the requests made by one or more Equipment vehicles for a configurable period of time Vehicle Onboard The HDV OBU shall be able to send the SRM at a CVE-FN2996-V01 Equipment configurable rate Vehicle Onboard The Transit Vehicle OBU shall be able to send the CVE-FN2997-V01 Equipment SRM at a configurable rate
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
178 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional Group ReqID Description
Vehicle Onboard The Emergency Vehicle OBU shall be able to send the CVE-FN2998-V01 Equipment SRM at a configurable rate The HMI shall present alerts to drivers using a devise Vehicle Onboard CVE-FN1123-V01 that drivers are familiar with and limits driver Equipment interaction. An OBU shall be capable of being reset and Vehicle Onboard CVE-FN1184-V01 reconfigured so that it can be installed into another Equipment vehicle of the same type (e.g. LDV, HDV, etc.) An OBU host processor shall perform integrity checks Vehicle Onboard CVE-FN1185-V01 on boot to ensure that it is in a known good software Equipment state. An OBU shall not continue to start up and will log an Vehicle Onboard CVE-FN1186-V01 error if the host processor determines it is not in a Equipment known good software state on boot up. Vehicle Onboard An LDV OBU shall communicate with a LDV Operator CVE-FN1187-V01 Equipment via an HMI Vehicle Onboard CVE-FN1188-V01 The LDV OBU shall have two levels of alert Equipment Vehicle Onboard CVE-FN1189-V01 The LDV OBU shall have a low-level alert Equipment Vehicle Onboard The low-level alert shall consist of a configurable CVE-FN1190-V01 Equipment audio/visual warning Vehicle Onboard CVE-FN1191-V01 The LDV OBU shall have a high-level alert Equipment Vehicle Onboard The high-level alert shall consist of a configurable CVE-FN1192-V01 Equipment audio/visual warning Vehicle Onboard The high-level alert shall be louder and more visible CVE-FN1193-V01 Equipment compared to the low-level alert Vehicle Onboard The LDV OBU shall not display more than one alert to CVE-FN1194-V01 Equipment the LDV Vehicle Operator at a time Vehicle Onboard The LDV OBU shall contain a configurable priority CVE-FN1195-V01 Equipment order for displaying alerts The order of alerts shall be configurable so that the Vehicle Onboard CVE-FN1196-V01 order of alerts can be modified once priority has been Equipment established. The LDV OBU shall provide system status information Vehicle Onboard to LDV operators. Information included in the system CVE-FN1197-V01 Equipment status includes power status, system settings, status of applications availability, and pending update status The OBU should notify the vehicle operators of the Vehicle Onboard CVE-FN1198-V01 power status of device (e.g., off, powering up and Equipment online).
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 179 Appendix B. Requirements by System Functional Groups
Functional Group ReqID Description
The OBU shall allow all vehicle operators to see the Vehicle Onboard CVE-FN1199-V01 system settings of the device. (e.g., version, Equipment brightness, volume, font size). The OBU shall allow all vehicle operators to see Vehicle Onboard CVE-FN1200-V01 application availability with screen graphics (e.g., failed, Equipment operating, disabled). The OBU should allow all vehicle operators to see Vehicle Onboard CVE-FN1201-V01 pending updates for the device with screen graphics Equipment (e.g., applications, firmware, operating system). The LDV OBU shall provide messages that can be Vehicle Onboard seen and/or heard by the LDV Operator via the HMI CVE-FN1202-V01 Equipment from the LDV Vehicle Operator's normal seating position The LDV OBU shall provide only the highest priority Vehicle Onboard CVE-FN1203-V01 alert to the LDV vehicle operator when more than one Equipment alert is currently active An OBU shall acquire time from the Location and Time Vehicle Onboard CVE-FN1204-V02 Service (LTS) interface in accordance with J2945/1 Equipment section 6.2.4. Vehicle Onboard An OBU shall acquire location from the LTS interface in CVE-FN1205-V01 Equipment accordance with J2945/1 section 6.2.1. Vehicle Onboard A Transit Vehicle OBU shall transmit Interaction Data CVE-FN1206-V01 Equipment to the Transit CV Management System Vehicle Onboard The OBU should capture vehicle brake status over the CVE-FN1207-V01 Equipment OBU-OBD-II interface to the host vehicle A Transit Vehicle OBU shall use Coordinated Universal Vehicle Onboard Time (UTC) time for all logged data (e.g., events logs, CVE-FN1208-V01 Equipment probe vehicle data) based on the format defined in J2735 section 6.19 and epoch of January 1st 1970. An OBU device shall comply with IEEE 1609.2: Vehicle Onboard CVE-FN1209-V01 Standard for WAVE Security Services for Applications Equipment and Management Messages Vehicle Onboard CVE-FN1210-V01 An LDV OBU shall determine when to issue an alert Equipment The OBU shall implement a download protocol that Vehicle Onboard CVE-FN1212-V01 permits resumption of incomplete downloads instead of Equipment requiring an incomplete download to be restarted. The LDV OBU shall provide a visual output that is Vehicle Onboard CVE-FN1213-V01 similar in look and feel from various applications when Equipment presenting information to LDV Operators via the HMI The LDV OBU Auditory signals (via the HMI) shall be Vehicle Onboard CVE-FN1214-V01 loud enough to overcome masking sounds from road Equipment noise, the cab environment, and other equipment. �
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
180 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional Group ReqID Description
Vehicle Onboard An Emergency Vehicle OBU shall cease broadcasting CVE-FN1215-V01 Equipment messages when its lights are off and siren is off Vehicle Onboard An Emergency Vehicle OBU shall broadcast messages CVE-FN1216-V01 Equipment when its lights are flashing Vehicle Onboard An Emergency Vehicle OBU shall broadcast messages CVE-FN1217-V01 Equipment when its siren is on Vehicle Onboard An LDV OBU shall send BSMs (Part I) consistent with CVE-IF1218-V01 Equipment SAE J2735 to an LDV OBU Vehicle Onboard An HDV OBU shall send BSMs (Part I and Part II) CVE-IF1219-V01 Equipment consistent with SAE J2735 to an LDV OBU Vehicle Onboard A Transit Vehicle OBU shall broadcast BSMs (Part I) CVE-IF1220-V01 Equipment consistent with SAE J2735 to an LDV OBU Vehicle Onboard An Emergency Vehicle OBU shall send BSMs (Part I) CVE-IF1221-V01 Equipment consistent with SAE J2735 to an LDV OBU Vehicle Onboard An LDV OBU shall communicate alerts to an LDV CVE-IF1222-V01 Equipment Operator Vehicle Onboard CVE-IF1223-V01 An LDV OBU shall receive BSMs from an LDV OBU Equipment Vehicle Onboard A Transit Vehicle OBU shall receive BSMs from an CVE-IF1224-V01 Equipment LDV OBU Vehicle Onboard An LDV OBU shall receive SPaT messages from an CVE-IF1225-V01 Equipment RSU Vehicle Onboard An HDV OBU shall receive SPaT messages from an CVE-IF1226-V01 Equipment RSU Vehicle Onboard A Transit Vehicle OBU shall receive SPaT messages CVE-IF1227-V01 Equipment from an RSU Vehicle Onboard An Emergency Vehicle OBU shall receive SPaT CVE-IF1228-V01 Equipment messages from an RSU Vehicle Onboard An LDV OBU shall receive MAP messages from an CVE-IF1229-V01 Equipment RSU Vehicle Onboard An HDV OBU shall receive MAP messages from an CVE-IF1230-V01 Equipment RSU Vehicle Onboard A Transit Vehicle OBU shall receive MAP messages CVE-IF1231-V01 Equipment from an RSU Vehicle Onboard An Emergency Vehicle OBU shall receive MAP CVE-IF1232-V01 Equipment messages from an RSU Vehicle Onboard An LDV OBU shall receive RTCM messages from an CVE-IF1233-V01 Equipment RSU Vehicle Onboard An HDV OBU shall receive RTCM messages from an CVE-IF1234-V01 Equipment RSU Vehicle Onboard A Transit Vehicle OBU shall receive RTCM messages CVE-IF1235-V01 Equipment from an RSU
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 181 Appendix B. Requirements by System Functional Groups
Functional Group ReqID Description
Vehicle Onboard An Emergency Vehicle OBU shall receive RTCM CVE-IF1236-V01 Equipment messages from an RSU Vehicle Onboard An HDV OBU shall receive SSM messages from an CVE-IF1237-V01 Equipment RSU Vehicle Onboard A Transit Vehicle OBU shall receive SSM messages CVE-IF1238-V01 Equipment from an RSU Vehicle Onboard An Emergency Vehicle OBU shall receive SSM CVE-IF1239-V01 Equipment messages from an RSU Vehicle Onboard An LDV OBU shall receive RSM messages from an CVE-IF1240-V01 Equipment RSU Vehicle Onboard A Transit Vehicle OBU shall receive RSM messages CVE-IF1241-V01 Equipment from an RSU Vehicle Onboard An LDV OBU shall receive position data from GNSS CVE-IF1242-V01 Equipment satellites Vehicle Onboard An LDV OBU shall receive security certificates from the CVE-IF1243-V01 Equipment SCMS via the RSU Vehicle Onboard An Emergency Vehicle OBU shall receive the flashing CVE-IF1244-V01 Equipment light status over the OBU-OBD-II interface Vehicle Onboard An Emergency Vehicle OBU shall receive the siren CVE-IF1245-V01 Equipment status over the OBU-OBD-II interface Vehicle Onboard An LDV OBU shall issue alerts to the LDV Operator via CVE-IF1246-V01 Equipment an HMI Vehicle Onboard An Emergency Vehicle OBU shall issue a signal priority CVE-IF1247-V01 Equipment notification to the Emergency Vehicle Operator Vehicle Onboard An Emergency Vehicle OBU shall provide a means of CVE-IF1248-V01 Equipment ceasing the broadcast of DSRC messages Vehicle Onboard CVE-IF1249-V01 An HDV OBU shall send SRMs to an RSU Equipment Vehicle Onboard CVE-IF1250-V01 A Transit Vehicle OBU shall send SRMs to an RSU Equipment Vehicle Onboard An Emergency Vehicle OBU shall send SRMs to an CVE-IF1251-V01 Equipment RSU Vehicle Onboard An OBU shall support physical access to support CVE-MT1252-V01 Equipment maintenance activities. Vehicle Onboard An OBU shall support role-based authentication to CVE-MT1253-V01 Equipment enable physical access. The OBU shall cease transmission of BSMs if the OBU Vehicle Onboard determines that it has been blacklisted. Note: Blacklists CVE-SR1254-V01 Equipment detail devices that should not be trusted in the system or network
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
182 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional Group ReqID Description
The OBU shall prevent incoming messages with invalid Vehicle Onboard CVE-SR1255-V01 conditions per criteria in the IEEE 1609.2 from being Equipment acted on. The OBU Vehicle Communications link shall have communications security to ensure the authenticity of Vehicle Onboard CVE-SR1256-V01 all its messages in accordance to the standards Equipment prescribed by the overall USDOT connected vehicle program. Vehicle Onboard The OBU shall carry out plausibility checking on the CVE-SR1257-V01 Equipment remote vehicle BSM data. Vehicle Onboard The OBU shall indicate successful receipt of the CVE-SR1258-V01 Equipment pseudonym certificates. When the OBU has no valid BSM signing certificates, it Vehicle Onboard CVE-SR1259-V01 shall store the log file entries as IEEE 1609.2 data of Equipment type unsecured. Vehicle Onboard The OBU shall obtain certificates via IPv6 connectivity CVE-SR1261-V01 Equipment through the RSU. Vehicle Onboard An OBU shall communicate using SNMPv3 with SNMP CVE-SR1262-V01 Equipment messages protected by being sent over TLS. An OBU shall support establishment of a standard TLS-based VPN with client authentication for Vehicle Onboard communication to the Traffic CV Management System, CVE-SR1263-V01 Equipment with a long-term client cert and a single CA cert trusted to authorize connections from the Traffic CV Management System. An OBU shall verify received messages per IEEE Vehicle Onboard CVE-SR1264-V01 1609.2 and per the relevant security profiles before Equipment using them for operations in any application. An OBU shall provide real-time tamper data which Vehicle Onboard CVE-SR1265-V01 indicates that the device has been tampered with (e.g. Equipment opening of the case). An OBU shall require that 1609.2 signed messages are signed by a certificate that is protected from Vehicle Onboard CVE-SR1266-V01 modification by, or chains back to a certificate that is Equipment protected from modification by, the secure boot process. An OBU shall only transmit messages for any usage Vehicle Onboard scenario if the usage scenario requires it to use 1609.2 CVE-SR1267-V01 Equipment certificates and it currently has valid certificates for that usage scenario An OBU shall verify a DSRC message when a device Vehicle Onboard CVE-SR1268-V01 identifies the message as containing a new Equipment DE_TemporaryID value.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 183 Appendix B. Requirements by System Functional Groups
Functional Group ReqID Description
An OBU shall verify a DSRC message when the Vehicle Onboard CVE-SR1269-V01 message results in the issuance of issue either Equipment advisory, warning, or alert An OBU shall verify a DSRC message when the remote vehicle constitutes a potential threat (define Vehicle Onboard CVE-SR1270-V01 potential threat as a vehicle that may collide with the Equipment host vehicle based on the both vehicle�s speeds and trajectories An OBU shall verify a DSRC message when other Vehicle Onboard CVE-SR1271-V01 potential threat situations such as red-light violations, Equipment and other safety applications. An Emergency Vehicle OBU shall cease sending SRMs for preemption to an RSU at a given intersection Vehicle Onboard CVE-FN1496-V01 for a configurable amount of time after it has received Equipment an SSM from the RSU at that intersection that contains the Emergency Vehicle OBU ID Vehicle Onboard An Emergency Vehicle OBU shall only request CVE-FN1495-V01 Equipment preemption in an SRM An Emergency Vehicle OBU shall send a SRM to an Vehicle Onboard RSU when it is less than a configurable amount of time CVE-FN1494-V01 Equipmnet away from arriving at the intersection it intends to request priority for
683 Source: City of Columbus 684
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
184 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
685 Appendix C. Relationship Matrix
686 Table 22: Established Relations per Requirements provides a mapping of each User need established 687 in the ConOps with the requirements that were created based off that User defined in Chapter 3. This 688 organization is intended for ease of use and quick reference during system design.
689 NOTE: This section will be added once requirements are transferred to Helix ALM.
690 Table 22: Established Relations per Requirements
USER NEED: CVE-UN110-v02 USER: Light-Duty Vehicle Operator Title: Vehicle Collision Avoidance Description: A light-duty vehicle operator needs to know of an event that may lead to a crash with a CV-equipped vehicle. Priority: Essential
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Interface CVE-IF1246- Vehicle Light-Duty An LDV OBU shall issue alerts V01 Onboard Vehicle OBU to the LDV Operator via an HMI Equipment Functional CVE- Vehicle General OBU The OBU should capture FN1207-V01 Onboard vehicle brake status over the Equipment OBU-OBD-II interface to the host vehicle
USER NEED: CVE-UN111-v02 USER: Light-Duty Vehicle Operator Title: Emergency Braking Ahead Description: A light-duty vehicle operator needs to know when a CV-equipped vehicle in its path of travel is braking in an emergency fashion. Priority: Essential
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Performance CVE- V2V Safety Emergency The EEBL application (see PR1119-V01 Electronic Appendix B) should employ Brake Light algorithms that are used in Warning applications verified by CAMP to issue an EEBL alert.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 185 Appendix C. Relationship Matrix
Performance CVE- V2V Safety Emergency The EEBL application (see PR1120-V01 Application Electronic Appendix B) shall meet TRL 6 Brake Light criteria (has been tested in a Warning realistic environment outside of a laboratory and satisfies operational requirements when confronted with realistic problems) Functional CVE- V2V Safety Emergency An LDV OBU (host) shall issue FN1115-V01 Application Electronic an alert to the LDV Operator Brake Light via the HMI �when there is Warning emergency braking ahead by an OBU-equipped (remote) vehicle Data CVE- V2V Safety Emergency The EEBL Application shall DR1114-V01 Application Electronic require data from the BSM Brake Light Message Warning Functional CVE- V2V Safety Emergency An LDV OBU (host) shall FN1116-V01 Application Electronic determine if there is emergency Brake Light braking ahead for each BSM it Warning receives Functional CVE- V2V Safety Emergency Emergency braking ahead shall FN1117-V01 Application Electronic be occurring if all of the Brake Light following conditions are Warning concurrently met: 1. An OBU- equipped (remote) vehicle is braking in an emergency fashion. 2. The distance between the OBU-equipped (host) vehicle and OBU- equipped (remote) vehicle is less than a distance threshold that is a function of the speed of the host vehicle. 3. The OBU-equipped (host) vehicle is approaching the OBU- equipped (remote) vehicle. 4. The OBU-equipped (host) vehicle is moving in the same direction as the OBU-equipped (remote) vehicle. Interface CVE-IF1118- V2V Safety Emergency The EEBL Application shall V01 Application Electronic receive data from the OBU's Brake Light internal processing functions. Warning Interface CVE-IF1246- Vehicle Light-Duty An LDV OBU shall issue alerts V01 Onboard Vehicle OBU to the LDV Operator via an HMI Equipment Functional CVE- Vehicle General OBU The OBU should capture FN1207-V01 Onboard vehicle brake status over the Equipment
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
186 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
OBU-OBD-II interface to the host vehicle
USER NEED: CVE-UN112-v02 USER: Light-Duty Vehicle Operator Title: Safe Following Distance Description: A light-duty vehicle operator needs to be informed if their following distance is too close. Priority: Essential
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Performance CVE- V2V Safety Forward The FCW application (see PR1127-V01 Application Collision Appendix B) should employ Warning algorithms that are used in applications verified by CAMP to issue a FCW alert Performance CVE- V2V Safety Forward The FCW application (see PR1128-V01 Application Collision Appendix B) shall meet TRL 6 Warning criteria (has been tested in a realistic environment outside of a laboratory and satisfies operational requirements when confronted with realistic problems) Functional CVE- V2V Safety Forward An LDV OBU (host) shall issue FN1122-V01 Application Collision an alert to the LDV Operator Warning via the LDV HMI when a forward collision is imminent with another OBU-equipped (remote) vehicle
Data CVE- V2V Safety Forward The FCW Application shall DR1121-V01 Application Collision require data from the BSM Warning Message
Functional CVE- V2V Safety Forward An LDV OBU (host) shall FN1124-V01 Application Collision determine if a forward collision Warning is imminent for each BSM it receives Functional CVE- V2V Safety Forward A forward collision shall be FN1125-V01 Application Collision imminent if all of the following Warning conditions are concurrently met: 1. The distance between the OBU-equipped (host) vehicle and OBU-equipped (remote) vehicle is less than a distance threshold that is a function of the speed of the host vehicle and the remote vehicle.. 2. The OBU-equipped
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 187 Appendix C. Relationship Matrix
(host) vehicle is approaching the OBU-equipped (remote) vehicle. Interface CVE-IF1126- V2V Safety Forward The FCW Application shall V01 Application Collision receive data from the OBU's Warning internal processing functions.
Interface CVE-IF1246- Vehicle Light-Duty An LDV OBU shall issue alerts V01 Onboard Vehicle OBU to the LDV Operator via an HMI Equipment
USER NEED: CVE-UN113-v02 USER: Light-Duty Vehicle Operator Title: Monitor Vehicle Trajectories at Intersection Description: A light-duty vehicle operator approaching an intersection needs to be aware of CV-equipped vehicles on intersecting trajectories. Priority: Essential
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Performance CVE- V2V Safety Intersection The IMA application (see PR1135-V01 Application Movement Appendix B) should employ Assist algorithms that are used in applications verified by CAMP to issue an IMA alert Performance CVE- V2V Safety Intersection The IMA application (see PR1136-V01 Application Movement Appendix B) shall meet TRL 6 Assist criteria (has been tested in a realistic environment outside of a laboratory and satisfies operational requirements when confronted with realistic problems) Functional CVE- V2V Safety Intersection An LDV OBU (host) shall issue FN1131-V01 Application Movement an alert to the LDV Operator Assist via the HMI when an intersection collision is imminent with another OBU- equipped (remote) vehicle Data CVE- V2V Safety Intersection The IMA Application shall DR1130-V01 Application Movement require data from the BSM Assist Message Data CVE- V2V Safety Lane Change The LCW Application shall DR1137-V01 Application Warning require data from the BSM Message Functional CVE- V2V Safety Intersection An LDV OBU (host) shall FN1132-V01 Application Movement determine if an intersection Assist collision is imminent for each BSM it receives
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
188 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional CVE- V2V Safety Intersection An intersection collision shall FN1133-V01 Application Movement be imminent if all of the Assist following conditions are concurrently met: 1. The OBU- equipped (host) vehicle has a trajectory (based on position, speed, acceleration) that may interfere with an OBU-equipped (remote) vehicle trajectory in a side impact fashion. 2. The distance between the OBU- equipped (host) vehicle and OBU-equipped (remote) vehicle is less than a distance threshold that is a function of the speed of the host vehicle and the remote vehicle. Interface CVE-IF1134- V2V Safety Intersection The IMA Application shall V01 Application Movement receive data from the OBU's Assist internal processing functions. Interface CVE-IF1141- V2V Safety Lane Change The LCW Application shall V01 Application Warning receive data from the OBU's internal processing functions. Interface CVE-IF1246- Vehicle Light-Duty An LDV OBU shall issue alerts V01 Onboard Vehicle OBU to the LDV Operator via an HMI Equipment
USER NEED: CVE-UN114-v02 USER: Light-Duty Vehicle Operator Title: Lane Change Collision Warning Description: A light-duty vehicle operator needs to be warned if they are changing lanes into the path of another CV-equipped vehicle. Priority: Essential
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Performance CVE- V2V Safety Lane Change The LCW application (see PR1142-V01 Application Warning Appendix B) should employ algorithms that are used in applications verified by CAMP to issue a LCW alert Performance CVE- V2V Safety Lane Change The LCW application (see PR1143-V01 Application Warning Appendix B) shall meet TRL 6 criteria (has been tested in a realistic environment outside of a laboratory and satisfies operational requirements when confronted with realistic problems) Functional CVE- V2V Safety Lane Change An LDV OBU (host) shall issue FN1138-V01 Application Warning an alert to the LDV Operator
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 189 Appendix C. Relationship Matrix
via the HMI when it is changing lanes into another OBU- equipped (remote) vehicle Functional CVE- V2V Safety Lane Change An LDV OBU (host) shall FN1139-V01 Application Warning determine if a lane change collision is imminent for each BSM it receives Functional CVE- V2V Safety Lane Change A lane change collision shall be FN1140-V01 Warning imminent if all of the following conditions are concurrently met: 1. The OBU-equipped (host) vehicle has a trajectory (based on position, speed, acceleration) that may interfere with an OBU-equipped (remote) vehicle trajectory in a sideswipe fashion. Interface CVE-IF1246- Vehicle Light-Duty An LDV OBU shall issue alerts V01 Onboard Vehicle OBU to the LDV Operator via an HMI Equipment
USER NEED: CVE-UN120-v02 USER: Light-Duty Vehicle Operator Title: Vehicle in Blind Spot Description: A light-duty vehicle operator needs to be notified if another CV-equipped vehicle is in their blind spot. Priority: Desirable
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Performance CVE-PR1111- V2V Safety Blind Spot The BSW application (see V01 Application Warning Appendix B) should employ algorithms that are used in MMITSS to issue a BSW alert. Performance CVE- V2V Safety Blind Spot The BSW application (see PR1112-V01 Application Warning Appendix B) shall meet TRL 6 criteria (has been tested in a realistic environment outside of a laboratory and satisfies operational requirements when confronted with realistic problems) Functional CVE- V2V Safety Blind Spot An LDV OBU (host) shall issue FN1107-V01 Application Warning an alert to the LDV Operator via the HMI when there is an OBU-equipped (remote) vehicle in the host vehicle's blind spot Data CVE- V2V Safety Blind Spot The BSW Application shall DR1106-V01 Application Warning require data from the BSM Message
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
190 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional CVE- V2V Safety Blind Spot An LDV OBU (host) shall FN1108-V01 Application Warning determine if a vehicle is in its blind spot for each BSM it receives Functional CVE- V2V Safety Blind Spot A vehicle shall be in a blind FN1109-V01 Application Warning spot if all of the following conditions are concurrently met: 1. The OBU-equipped (host) vehicle is traveling in the same direction as the OBU- equipped (remote) vehicle. 2. The OBU-equipped (remote) vehicle is located in a configurable zone (rear left and rear right of the OBU-equipped host vehicle) with a configurable amount of confidence (factors that affect confidence include positioning error for the host and remote vehicle)
Interface CVE-IF1110- V2V Safety Blind Spot The BSW Application shall V01 Application Warning receive data from the OBU's internal processing functions. Interface CVE-IF1246- Vehicle Light-Duty An LDV OBU shall issue alerts V01 Onboard Vehicle OBU to the LDV Operator via an HMI Equipment
USER NEED: CVE-UN130-v02 USER: Light-Duty Vehicle Operator Title: Stop on Red Signal Description: A light-duty vehicle operator needs to know if a signal will be red when the vehicle is expected to enter a CV-equipped intersection. Priority: Essential
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Performance CVE- V2I Safety Red Light The RLVW application (see PR1290-V01 Application Violation Appendix B) should employ Warning algorithms that are used in applications verified by CAMP to issue an RLVW Performance CVE- V2I Safety Red Light The RLVW application (see PR1291-V01 Application Violation Appendix B) shall meet TRL 6 Warning criteria (has been tested in a realistic environment outside of a laboratory and satisfies operational requirements when confronted with realistic problems)
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 191 Appendix C. Relationship Matrix
Functional CVE- V2I Safety Red Light An LDV OBU (host) shall issue FN1286-V01 Application Violation an alert to the LDV Operator Warning via the HMI when a red-light violation will occur at an RSU- equipped intersection Functional CVE- Roadside Roadside An RSU shall have access to a FN1312-V01 Equipment Unit function that generates SPaT messages from SPaT data inputs Functional CVE- Roadside Roadside An RSU shall have access to a FN1313-V01 Equipment Unit function that generates RTCM messages from RTCM data inputs Data CVE- V2I Safety Red Light The RLVW Application shall DR1283-V01 Application Violation require data from the SPAT Warning Message Data CVE- V2I Safety Red Light The RLVW Application shall DR1284-V01 Application Violation require data from the MAP Warning Message Data CVE- V2I Safety Red Light The RLVW Application shall DR1285-V01 Application Violation require data from the RTCM Warning Message Functional CVE- V2I Safety Red Light An LDV OBU (host) shall FN1287-V01 Application Violation determine if the OBU-equipped Warning (host) vehicle will run a red light for each SPaT message it receives Functional CVE- V2I Safety Red Light A red-light violation shall be FN1288-V01 Application Violation occurring if all of the following Warning conditions are concurrently met: 1. An OBU-equipped vehicle is approaching an RSU- equipped intersection. 2. The OBU-equipped vehicle's trajectory (based on location, speed, acceleration) will cross the stop bar when the light is red with a configurable amount of confidence (factors that affect confidence include positioning error and uncertainty in the change of signal state) Interface CVE-IF1289- V2I Safety Red Light The RLVW Application shall V01 Application Violation receive data from the OBU's Warning internal processing functions.
USER NEED: CVE-UN140-v02 USER: Light-Duty Vehicle Operator Title: School Zone/ Decrease Speed Description: A light-duty vehicle operator needs to know when they are exceeding the school zone speed limit in an active school zone that is CV equipped.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
192 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Priority: Essential
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Performance CVE- V2I Safety Reduced The RSSZ application (see PR1306-V01 Application Speed Appendix B) should employ School Zone algorithms that are used in applications verified by CAMP to issue an RSSZ warning Performance CVE- V2I Safety Reduced The RSSZ application (see PR1307-V01 Application Speed Appendix B) shall meet TRL 6 School Zone criteria (has been tested in a realistic environment outside of a laboratory and satisfies operational requirements when confronted with realistic problems) Functional CVE- V2I Safety Reduced An LDV OBU (host) shall issue FN1298-V01 Application Speed an alert to the LDV Operator School Zone via the HMI when the OBU- equipped (host) vehicle will enter an RSU-equipped school zone over the active school zone speed limit Functional CVE- Roadside Roadside An RSU shall broadcast FN1310-V01 Equipment Unit (school zone) RSMs to an LDV OBU when configured to perform this function.
Functional CVE- V2I Safety Reduced An LDV OBU (host) shall issue FN1299-V01 Application Speed an alert when the OBU- School Zone equipped (host) vehicle is inside of an RSU-equipped school zone over the active school zone speed limit Functional CVE- V2I Safety Reduced The LDV OBU (host) shall FN1300-V01 Application Speed parse received RSMs to School Zone identify the school zone speed limit (J2945/4). Functional CVE- V2I Safety Reduced The LDV OBU (host) shall FN1301-V01 Application Speed parse received RSMs to School Zone identify when the school zone speed limit is active. Functional CVE- V2I Safety Reduced The LDV OBU (host) shall FN1302-V01 Application Speed parse received RSMs to School Zone identify the applicable regions of use geographical path (J2945/4). Functional CVE- V2I Safety Reduced The LDV OBU (host) shall FN1303-V01 Application Speed issue a school zone alert when School Zone all of the following conditions
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 193 Appendix C. Relationship Matrix
are concurrently met: 1. OBU- equipped (host) vehicle is traveling towards the segment where the situational awareness applies. 2. The OBU-equipped (host) vehicle is expected to enter the school zone but not below the school zone speed limit (given its current location, motion, and expected braking rate) . 3. During active school zone hours Functional CVE- V2I Safety Reduced The LDV OBU (host) shall FN1304-V01 Application Speed issue a school zone alert when School Zone all of the following conditions are concurrently met: 1. OBU- equipped (host) vehicle is within the segment where the situational awareness applies. 2. OBU-equipped (host) vehicle is traveling above the school zone speed limit. 3. During active school zone hours Data CVE- V2I Safety Reduced The RSSZ Application shall DR1297-V01 Application Speed require data from the RSM School Zone Message Interface CVE-IF1305- V2I Safety Reduced The RSSZ Application shall V01 Application Speed receive data from the OBU's School Zone internal processing functions. Interface CVE-IF1246- Vehicle Light-Duty An LDV OBU shall issue alerts V01 Onboard Vehicle OBU to the LDV Operator via an HMI Equipment Interface CVE-IF1246- Vehicle Light-Duty An LDV OBU shall issue alerts V01 Onboard Vehicle OBU to the LDV Operator via an HMI Equipment Interface CVE-IF1246- Vehicle Light-Duty An LDV OBU shall issue alerts V01 Onboard Vehicle OBU to the LDV Operator via an HMI Equipment
USER NEED: CVE-UN220-v02 USER: Emergency Vehicle Operator Title: Emergency Vehicle Intersection Priority Description: An emergency vehicle operator needs preemption service at CV-equipped signalized intersections. Priority: Essential
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
194 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional CVE- V2I Mobility Emergency The EVP application (see FN1497-V01 Vehicle Appendix B) should employ Preemption algorithms that are used in MMITSS to enable emergency vehicle preemption Performance CVE- V2I Mobility Emergency The EVP application (see PR1531-V01 Vehicle Appendix B) shall meet TRL 6 Preemption criteria (has been tested in a realistic envrionment outside of a laboratory and satisfies operational requirements when confronted with realistic problems) Performance CVE- V2I Mobility Emergency An Emergency Vehicle OBU PR1532-V01 Vehicle (host) shall issue a signal Preemption preemption notification to the Emergency Vehicle Operator via the HMI when preemption has been granted Functional CVE- Roadside Roadside An RSU shall have access to a FN1314-V01 Equipment Unit function that generates SSM messages from SSM data inputs Interface CVE-IF1347- Roadside Roadside An RSU shall send information V01 Equipment Unit to request signal priority to the Traffic Signal Controller Interface CVE-IF1244- Vehicle Emergency An Emergency Vehicle OBU V01 Onboard Vehicle OBU shall receive the flashing light Equipment status over the OBU-OBD-II interface Interface CVE-IF1245- Vehicle Emergency An Emergency Vehicle OBU V01 Onboard Vehicle OBU shall receive the siren status Equipment over the OBU-OBD-II interface Interface CVE-IF1247- Vehicle Emergency An Emergency Vehicle OBU V01 Onboard Vehicle OBU shall issue a signal priority Equipment notification to the Emergency Vehicle Operator Functional CVE- V2I Mobility Emergency An Emergency Vehicle OBU FN1493-V01 Vehicle shall request to receive signal Preemption preemption at RSU-equipped intersections Functional CVE- Vehicle Emergency An Emergency Vehicle OBU FN1494-V01 Onboard Vehicle OBU shall send a SRM to an RSU Equipmnet when it is less than a configurable amount of time away from arriving at the intersection it intends to request priority for Functional CVE- Vehicle Emergency An Emergency Vehicle OBU FN1495-V01 Onboard Vehicle OBU shall only request preemption Equipment in an SRM
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 195 Appendix C. Relationship Matrix
Functional CVE- Vehicle Emergency An Emergency Vehicle OBU FN1496-V01 Onboard Vehicle OBU shall cease sending SRMs for Equipment preemption to an RSU at a given intersection for a configurable amount of time after it has received an SSM from the RSU at that intersection that contains the Emergency Vehicle OBU ID Functional CVE- V2I Mobility Emergency A request to receive FN1500-V01 Vehicle signal preemption from a Public Preemption Safety Vehicle OBU shall be high priority Functional CVE- V2I Mobility General The Traffic Signal Controller FN1515-V01 Priority/Pree shall next service a phase for a mption movement that is requested in a preemption SRM when the approach for the requested movement is red Functional CVE- Roadside Roadside An RSU shall have access to a FN1313-V01 Equipment Unit function that generates RTCM messages from RTCM data inputs Functional CVE- V2I Mobility General An RSU shall use a locally- FN1506-V01 Priority/Pree stored list of vehicle OBU IDs mption that are authorized to receive signal priority at the intersection to determine if a received SRM is sent from an OBU that is authorized to make priority requests at that intersection Data CVE- Traffic Signal General The TSP Application shall DR1477-V01 Priority Priority/Pree require data from the SSM Applications mption Message Data CVE- Traffic Signal General The TSP Application shall DR1478-V01 Priority Priority/Pree generate data for the SRM Applications mption Message Data CVE- V2I Mobility Transit The TVIER Application shall DR1533-V01 Vehicle capture data from the all Interaction applicatiosn deployed on the Event Transit Vehicle Recording Functional CVE- V2I Mobility General The SRM shall contain the FN1498-V01 Priority/Pree intersection ID that is provided mption in the MAP message for the priority requested intersection Functional CVE- V2I Mobility General The SRM shall contain FN1499-V01 Priority/Pree information regarding the mption movement for which priority is being requested
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
196 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional CVE- V2I Mobility General High priority requests to FN1503-V01 Priority/Pree receive signal priority shall be mption serviced before low priority requests to receive signal priority Functional CVE- V2I Mobility General Multiple high priority requests FN1504-V01 Priority/Pree shall be serviced in the order in mption which they are received Functional CVE- V2I Mobility General Multiple low priority requests FN1505-V01 Priority/Pree shall be serviced in the order in mption which they are received Functional CVE- V2I Mobility General An RSU shall place a priority FN1508-V01 Priority/Pree request or a preemption mption request to the traffic signal controller for the movement specified in the SRM if the following conditions are concurrently met: 1. An OBU ID (from the received SRM) matches against the locally- stored list of vehicle OBU IDs that are authorized to receive signal priority. 2. The intersection ID in the SRM matches the intersection ID Functional CVE- V2I Mobility General An RSU shall receive output FN1518-V01 Priority/Pree from the Traffic Signal mption Controller regarding the status of a priority request Functional CVE- V2I Mobility General An RSU shall send a SSM to FN1519-V01 Priority/Pree an HDV OBU containing the mption results of the requests made by one or more vehicles for a configurable period of time Functional CVE- V2I Mobility General The Traffic CV Management FN1520-V01 Priority/Pree System shall maintain a mption modifiable list of OBU IDs authorized to send SRMs Interface CVE-IF1526- V2I Mobility Transit Signal The TSP Application shall V01 Priority transmit and receive data from the OBU's internal processing functions. Interface CVE-IF1561- V2I Mobility Transit The TIVER Application shall V01 Vehicle transmit and receive data from Interaction the OBU's internal processing Event functions. Recording
USER NEED: CVE-UN310-v02 USER: Heavy-Duty Vehicle Operator Title: Heavy-Duty Vehicle Intersection Priority
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 197 Appendix C. Relationship Matrix
Description: A heavy-duty vehicle operator needs priority service at CV-equipped signalized intersections. Priority: Desirable
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Performance CVE- V2I Mobility Freight The FSP application (see PR1527-V01 Signal Appendix B) should employ Priority algorithms that are used in MMITSS to enable freight signal priority Performance CVE- V2I Mobility Freight The FSP application (see PR1528-V01 Signal Appendix B) shall meet TRL 6 Priority criteria (has been tested in a realistic envrionment outside of a laboratory and satisfies operational requirements when confronted with realistic problems) Data CVE- Traffic Signal General The TSP Application shall DR1477-V01 Priority Priority/Pree require data from the SSM Applications mption Message Data CVE- Traffic Signal General The TSP Application shall DR1478-V01 Priority Priority/Pree generate data for the SRM Applications mption Message Data CVE- V2I Mobility Transit The TVIER Application shall DR1533-V01 Vehicle capture data from the all Interaction applicatiosn deployed on the Event Transit Vehicle Recording Functional CVE- V2I Mobility General The SRM shall contain the FN1498-V01 Priority/Pree intersection ID that is provided mption in the MAP message for the priority requested intersection Functional CVE- V2I Mobility General The SRM shall contain FN1499-V01 Priority/Pree information regarding the mption movement for which priority is being requested Functional CVE- V2I Mobility General High priority requests to FN1503-V01 Priority/Pree receive signal priority shall be mption serviced before low priority requests to receive signal priority Functional CVE- V2I Mobility General Multiple high priority requests FN1504-V01 Priority/Pree shall be serviced in the order in mption which they are received Functional CVE- V2I Mobility General Multiple low priority requests FN1505-V01 Priority/Pree shall be serviced in the order in mption which they are received
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
198 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional CVE- V2I Mobility General An RSU shall place a priority FN1508-V01 Priority/Pree request or a preemption mption request to the traffic signal controller for the movement specified in the SRM if the following conditions are concurrently met: 1. An OBU ID (from the received SRM) matches against the locally- stored list of vehicle OBU IDs that are authorized to receive signal priority. 2. The intersection ID in the SRM matches the intersection ID Functional CVE- V2I Mobility General An RSU shall receive output FN1518-V01 Priority/Pree from the Traffic Signal mption Controller regarding the status of a priority request Functional CVE- V2I Mobility General An RSU shall send a SSM to FN1519-V01 Priority/Pree an HDV OBU containing the mption results of the requests made by one or more vehicles for a configurable period of time Functional CVE- V2I Mobility General The Traffic CV Management FN1520-V01 Priority/Pree System shall maintain a mption modifiable list of OBU IDs authorized to send SRMs Interface CVE-IF1526- V2I Mobility Transit Signal The TSP Application shall V01 Priority transmit and receive data from the OBU's internal processing functions. Interface CVE-IF1561- V2I Mobility Transit The TIVER Application shall V01 Vehicle transmit and receive data from Interaction the OBU's internal processing Event functions. Recording Functional CVE- V2I Mobility Freight A request to receive signal FN1502-V01 Signal priority from an HDV Vehicle Priority OBU shall be low priority Functional CVE- V2I Mobility General The Traffic Signal Controller FN1509-V01 Priority/Pree shall grant an early green for a mption phase for a movement that is requested in a priority SRM when the approach for that movement is red or yellow Functional CVE- V2I Mobility General The Traffic Signal Controller FN1510-V01 Priority/Pree shall grant an extended green mption for a phase for a movement that is requested in a priority SRM when the approach for the requested movement is green
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 199 Appendix C. Relationship Matrix
Functional CVE- V2I Mobility Freight An HDV OBU shall request to FN1479-V01 Signal receive signal priority at RSU- Priority equipped intersections Functional CVE- V2I Mobility Freight An HDV OBU shall broadcast a FN1480-V01 Signal SRM when approaching an Priority RSU-equipped intersection Functional CVE- V2I Mobility Freight An HDV OBU shall broadcast a FN1481-V01 Signal SRM when it is within a Priority configurable distance of the intersection it intends to request priority for Functional CVE- V2I Mobility Freight An HDV OBU shall only FN1482-V01 Signal request priority for movements Priority along the designated freight route Functional CVE- V2I Mobility Freight An HDV OBU shall only FN1483-V01 Signal request priority in a SRM Priority Functional CVE- Roadside Roadside An RSU shall have access to a FN1313-V01 Equipment Unit function that generates RTCM messages from RTCM data inputs Functional CVE- Roadside Roadside An RSU shall have access to a FN1314-V01 Equipment Unit function that generates SSM messages from SSM data inputs Interface CVE-IF1347- Roadside Roadside An RSU shall send information V01 Equipment Unit to request signal priority to the Traffic Signal Controller
USER NEED: CVE-UN320-v02 USER: Heavy-Duty Vehicle Operator Title: Freight Signal Priority with Platoon Intent Description: A heavy-duty vehicle operator needs to follow (or be followed by) other CV- equipped heavy-duty vehicles that it intends to platoon with. Priority: Desirable
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Functional CVE- V2I Mobility General An RSU shall use a locally- FN1506-V01 Priority/Pree stored list of vehicle OBU IDs mption that are authorized to receive signal priority at the intersection to determine if a received SRM is sent from an OBU that is authorized to make priority requests at that intersection Functional CVE- Traffic Signal Intent to An RSU shall determine if FN1485-V01 Priority Platoon SRMs received from multiple Applications Priority
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
200 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
freight vehicles are intending to form a platoon Functional CVE- Traffic Signal Intent to An RSU should use data FN1486-V01 Priority Platoon received from the Platooning Applications Priority System to determine if the HDV OBUs sending SRMs intend to form a platoon Functional CVE- Traffic Signal Intent to An RSU shall consider the FN1487-V01 Priority Platoon priority requests from both HDV Applications Priority OBUs as a single priority request that is able to accommodate priority for both vehicles through the intersection if it is determined that the vehicles intend to platoon Functional CVE- Roadside Roadside An RSU shall have access to a FN1313-V01 Equipment Unit function that generates RTCM messages from RTCM data inputs Functional CVE- Roadside Roadside An RSU shall have access to a FN1314-V01 Equipment Unit function that generates SSM messages from SSM data inputs Interface CVE-IF1347- Roadside Roadside An RSU shall send information V01 Equipment Unit to request signal priority to the Traffic Signal Controller Data CVE- Traffic Signal General The TSP Application shall DR1477-V01 Priority Priority/Pree require data from the SSM Applications mption Message Data CVE- Traffic Signal General The TSP Application shall DR1478-V01 Priority Priority/Pree generate data for the SRM Applications mption Message Data CVE- V2I Mobility Transit The TVIER Application shall DR1533-V01 Vehicle capture data from the all Interaction applicatiosn deployed on the Event Transit Vehicle Recording Functional CVE- V2I Mobility General The SRM shall contain the FN1498-V01 Priority/Pree intersection ID that is provided mption in the MAP message for the priority requested intersection Functional CVE- V2I Mobility General The SRM shall contain FN1499-V01 Priority/Pree information regarding the mption movement for which priority is being requested Functional CVE- V2I Mobility General High priority requests to FN1503-V01 Priority/Pree receive signal priority shall be mption serviced before low priority requests to receive signal priority
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 201 Appendix C. Relationship Matrix
Functional CVE- V2I Mobility General Multiple high priority requests FN1504-V01 Priority/Pree shall be serviced in the order in mption which they are received Functional CVE- V2I Mobility General Multiple low priority requests FN1505-V01 Priority/Pree shall be serviced in the order in mption which they are received Functional CVE- V2I Mobility General An RSU shall place a priority FN1508-V01 Priority/Pree request or a preemption mption request to the traffic signal controller for the movement specified in the SRM if the following conditions are concurrently met: 1. An OBU ID (from the received SRM) matches against the locally- stored list of vehicle OBU IDs that are authorized to receive signal priority. 2. The intersection ID in the SRM matches the intersection ID Functional CVE- V2I Mobility General An RSU shall receive output FN1518-V01 Priority/Pree from the Traffic Signal mption Controller regarding the status of a priority request Functional CVE- V2I Mobility General An RSU shall send a SSM to FN1519-V01 Priority/Pree an HDV OBU containing the mption results of the requests made by one or more vehicles for a configurable period of time Functional CVE- V2I Mobility General The Traffic CV Management FN1520-V01 Priority/Pree System shall maintain a mption modifiable list of OBU IDs authorized to send SRMs Interface CVE-IF1526- V2I Mobility Transit Signal The TSP Application shall V01 Priority transmit and receive data from the OBU's internal processing functions. Functional CVE- V2I Mobility Freight A request to receive signal FN1502-V01 Signal priority from an HDV Vehicle Priority OBU shall be low priority Interface CVE-IF1561- V2I Mobility Transit The TIVER Application shall V01 Vehicle transmit and receive data from Interaction the OBU's internal processing Event functions. Recording
USER NEED: CVE-UN410-v02 USER: Traffic Manager Title: Monitor Performance Description: A traffic manager needs the ability to monitor the status of traffic by obtaining data from the CVE. Priority: Essential
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
202 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Functional CVE- V2I Mobility Vehicle Data The RSU shall delete logged FN1563-V01 for Traffic BSMs once it has verified that Operations the logged BSMs have been received by the Traffic CV Management System Functional CVE- V2I Mobility Vehicle Data The RSU shall send logged FN1566-V01 for Traffic SRMs to the Traffic CV Operations Management System at a configurable time interval Functional CVE- V2I Mobility Vehicle Data The RSU shall send logged FN1569-V01 for Traffic SSMs to the Traffic CV Operations Management System at a configurable time interval. Functional CVE- V2I Mobility Vehicle Data The RSU shall send logged FN1572-V01 for Traffic SPaT messages to the Traffic Operations CV Management System at a configurable time interval Functional CVE- V2I Mobility Vehicle Data The RSU shall send logged FN1577-V01 for Traffic RSMs to the Traffic CV Operations Management System at a configurable time interval Functional CVE- V2I Mobility Vehicle Data The Traffic CV Management FN1580-V01 for Traffic System shall receive all logged Operations BSMs sent by the RSU Functional CVE- V2I Mobility Vehicle Data The Traffic CV Management FN1581-V01 for Traffic System shall receive all logged Operations SRMs sent by the RSU Functional CVE- V2I Mobility Vehicle Data The Traffic CV Management FN1582-V01 for Traffic System shall receive all logged Operations SSMs sent by the RSU Functional CVE- V2I Mobility Vehicle Data The Traffic CV Management FN1584-V01 for Traffic System shall receive all logged Operations RSM messages sent by the RSU Functional CVE- Traffic Traffic CV The Traffic CV Management FN1437-V01 Management Management System shall transmit Center System performance metrics (as defined in the Performance Measurement Plan) derived from BSMs to the Smart Columbus OS Functional CVE- Traffic Traffic CV The Traffic CV Management FN1438-V01 Management Management System shall send PII-removed Center System RSMs to the Smart Columbus OS Functional CVE- Traffic Traffic CV The Traffic CV Management FN1439-V01 Management Management System shall send MAP Center System
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 203 Appendix C. Relationship Matrix
messages to the Smart Columbus OS Disposal CVE- Transit Transit CV The CVE should remain DP1465-V01 Management Management operational after the completion Center System of the deployment period Data CVE- Traffic Traffic CV The Traffic CV Management DR1272-V01 Management Management System shall use BSM data, Center System SPaT data, MAP data, and RTCM data to generate the performance measures regarding red light compliance Data CVE- Traffic Traffic CV The Traffic CV Management DR1273-V01 Management Management System shall use BSM data, Center System RSM data, and RTCM data to generate the performance measures regarding school zone speed compliance Data CVE- Traffic Traffic CV The Traffic CV Management DR1274-V01 Management Management System shall use BSM data to Center System generate the TBD performance measure for (Vehicle Data for Traffic Operations) Data CVE- Traffic Traffic CV The Traffic CV Management DR1275-V01 Management Management System shall use BSM data Center System from HDV OBUs to generate the travel time through intersection performance measure (for Freight Signal Priority, and Intent to Platoon Priority) Data CVE- V2I Mobility Vehicle Data The VDTO Application shall DR1562-V01 for Traffic capture data from the all Operations messages transmitted or received by an RSU Functional CVE- Traffic Traffic CV The Traffic CV Management FN1446-V01 Management Management System shall provide the VISA' Center System functions of Validation, Integration, Sanitization (De- identification), and Aggregation of CV Data as defined in the U.S DOT SEMI ODE requirements (Reference TBR) Functional CVE- Traffic Traffic CV The Traffic CV Management FN1453-V01 Management Management System should automate the Center System generation of performance metrics as defined in the Performance Management Plan (TBD) Functional CVE- Traffic Traffic CV The Traffic CV Management FN1454-V01 Management Management System should use CV data Center System made available through the CV Environment to generate
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
204 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
performance metrics as defined in the Performance Management Plan (TBD) Functional CVE- Traffic Traffic CV The Traffic CV Management FN1455-V01 Management Management System shall upload Center System performance metrics to the Smart Columbus OS Functional CVE- V2I Mobility Vehicle Data The RSU shall send logged FN1564-V01 for Traffic BSMs to the Traffic CV Operations Management System at a configurable time interval Functional CVE- V2I Mobility Vehicle Data The RSU shall log BSMs FN1565-V01 for Traffic received from a given OBU at a Operations configurable frequency (10 Hz max) Functional CVE- V2I Mobility Vehicle Data The RSU shall log SRMs FN1567-V01 for Traffic received from a given OBU at a Operations configurable frequency Functional CVE- V2I Mobility Vehicle Data The RSU shall log SSMs FN1570-V01 for Traffic received from a traffic signal Operations controller at a configurable frequency Functional CVE- V2I Mobility Vehicle Data The RSU should not log FN1571-V01 for Traffic duplicate SSMs during a Operations configurable time interval Functional CVE- V2I Mobility Vehicle Data The RSU shall log SPaT FN1573-V01 for Traffic messages at a configurable Operations frequency Functional CVE- V2I Mobility Vehicle Data The RSU shall not log a SPaT FN1574-V01 for Traffic message unless there is a Operations change in configurable select data elements (e.g. minEndTime, maxEndTime, etc.) from the previously logged message Functional CVE- V2I Mobility Vehicle Data The RSU shall log MAP FN1575-V01 for Traffic messages at a configurable Operations frequency Functional CVE- V2I Mobility Vehicle Data The RSU should not log FN1576-V01 for Traffic duplicate MAP messages Operations during a configurable time interval Functional CVE- V2I Mobility Vehicle Data The RSU shall log RSMs at a FN1578-V01 for Traffic configurable frequency Operations Functional CVE- V2I Mobility Vehicle Data The RSU should not log FN1579-V01 for Traffic duplicate RSMs during a Operations configurable time interval Functional CVE- V2I Mobility Vehicle Data The Traffic CV Management FN1583-V01 for Traffic System shall receive all logged Operations SPaT messages sent by the RSU
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 205 Appendix C. Relationship Matrix
Functional CVE- V2I Mobility Vehicle Data The Traffic CV Management FN1585-V01 for Traffic System shall store all logged Operations BSMs sent by the RSU Functional CVE- V2I Mobility Vehicle Data The Traffic CV Management FN1586-V01 for Traffic System shall store all logged Operations SRMs sent by the RSU Functional CVE- V2I Mobility Vehicle Data The Traffic CV Management FN1587-V01 for Traffic System shall store all logged Operations SSMs sent by the RSU Functional CVE- V2I Mobility Vehicle Data The Traffic CV Management FN1588-V01 for Traffic System shall store all logged Operations SPaT messages sent by the RSU Functional CVE- V2I Mobility Vehicle Data The Traffic CV Management FN1589-V01 for Traffic System shall store all logged Operations RSM messages sent by the RSU Functional CVE- V2I Mobility Vehicle Data The Traffic CV Management FN1590-V01 for Traffic System shall store all MAP Operations messages that are input by the Traffic Manager Functional CVE- V2I Mobility Vehicle Data The Traffic CV Management FN1591-V01 for Traffic System shall make all stored Operations data available to the Traffic Manager
Interface CVE-IF1592- V2I Mobility Vehicle Data The VDTO Application shall V01 for Traffic receive data from the OBU's Operations internal processing functions.
USER NEED: CVE-UN420-v02 USER: Traffic Manager Title: Update Static Messages Description: A traffic manager needs the ability to update static messages within the CVE. Priority: Essential
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Functional CVE- Traffic Traffic CV The Traffic CV Management FN1442-V01 Management Management System shall accept input for Center System RSM messages from Traffic Management Staff Functional CVE- Traffic Traffic CV The Traffic CV Management FN1443-V01 Management Management System shall accept input for Center System MAP messages from Traffic Management Staff Functional CVE- Traffic Traffic CV The Traffic CV Management FN1444-V01 Management Management System shall accept input for Center System configurable parameters from Traffic Management Staff
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
206 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional CVE- Traffic Traffic CV The Traffic CV Management FN1447-V01 Management Management System shall have access to a Center System function that generates RSM messages from RSM data inputs Functional CVE- Traffic Traffic CV The Traffic CV Management FN1448-V01 Management Management System shall have access to a Center System function that generates MAP messages from MAP data inputs
USER NEED: CVE-UN430-v02 USER: Traffic Manager Title: Configure and Monitor Roadside Devices Description: A traffic manager needs to configure and monitor the status of roadside devices for operation within the CVE. Priority: Essential
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Functional CVE- Traffic Traffic CV The Traffic CV Management FN1441-V01 Management Management System shall enable loading of Center System MAP messages on the RSU Functional CVE- Traffic Traffic CV The Traffic CV Management FN1442-V01 Management Management System shall accept input for Center System RSM messages from Traffic Management Staff Functional CVE- Traffic Traffic CV The Traffic CV Management FN1443-V01 Management Management System shall accept input for Center System MAP messages from Traffic Management Staff Functional CVE- Traffic Traffic CV The Traffic CV Management FN1444-V01 Management Management System shall accept input for Center System configurable parameters from Traffic Management Staff Functional CVE- Traffic Traffic CV The Traffic CV Management FN1445-V01 Management Management System shall make the status Center System of RSUs available to Traffic Management Staff Functional CVE- Roadside Roadside An RSU shall provide tamper FN1331-V01 Equipment Unit evidence to detect tampering of the device (e.g. opening of the case). Functional CVE- Traffic Traffic CV The Traffic CV Management FN1440-V01 Management Management System shall enable loading of Center System RSMs on the RSU Functional CVE- Traffic Traffic CV The Traffic CV Management FN1447-V01 Management Management System shall have access to a Center System function that generates RSM messages from RSM data inputs
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 207 Appendix C. Relationship Matrix
Functional CVE- Traffic Traffic CV The Traffic CV Management FN1448-V01 Management Management System shall have access to a Center System function that generates MAP messages from MAP data inputs Functional CVE- Traffic Traffic CV The Traffic CV Management FN1449-V01 Management Management System shall monitor the status Center System of RSUs Functional CVE- Traffic Traffic CV The Traffic CV Management FN1450-V01 Management Management System shall alert the Traffic Center System Manager if an RSU is offline Functional CVE- Traffic Traffic CV The Traffic CV Management FN1451-V01 Management Management System shall alert the Traffic Center System Manager if an RSU is not running normally (off, not responding, in safe mode, etc.) Functional CVE- Traffic Traffic CV The Traffic CV Management FN1452-V01 Management Management System shall make the status Center System of all RSUs available to the Traffic Manager Functional CVE- Traffic Traffic CV The Traffic CV Management FN1463-V01 Management Management System shall monitor tamper Center System alert devices Functional CVE- Traffic Traffic CV The Traffic CV Management FN1464-V01 Management Management System shall alert the Traffic Center System Manager when a tamper alert device detects that a traffic signal controller cabinet has been opened (or disturbed?) Functional CVE- V2I Mobility General The Traffic CV Management FN1521-V01 Priority/Pree System shall maintain a mption modifiable list of intersections for which each authorized OBU is allowed to request priority or preemption at. Performance CVE- Traffic Traffic CV The Traffic CV Management PR1457-V01 Management Management System shall notify designated Center System personnel within five minutes of limited connectivity. Note: Limited connectivity refers to a state when the Traffic CV Management System is not able to communicate with the RSU Performance CVE- Traffic Traffic CV The Traffic CV Management PR1458-V01 Management Management System shall notify designated Center System personnel within five minutes of a monitored function becoming unavailable Security CVE- Traffic Traffic CV Monitoring systems shall be SR1459-V01 Management Management used to detect abnormal Center System unauthorized activity on an IP connection.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
208 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Security CVE- Traffic Traffic CV The Traffic CV Management SR1460-V01 Management Management System shall monitor the Center System DSRC communications performance to detect DoS attacks. Security CVE- Traffic Traffic CV The Traffic CV Management SR1461-V01 Management Management System should investigate and Center System monitor the data traffic usage to detect unapproved use of the IP connection.
USER NEED: CVE-UN440-v02 USER: Traffic Manager Title: Data Archive Configuration Description: A traffic manager needs to configure the mechanism that is used to archive data. Priority: Essential
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Functional CVE- V2I Mobility Vehicle Data The Traffic CV Management FN1585-V01 for Traffic System shall store all logged Operations BSMs sent by the RSU Functional CVE- V2I Mobility Vehicle Data The Traffic CV Management FN1586-V01 for Traffic System shall store all logged Operations SRMs sent by the RSU Functional CVE- V2I Mobility Vehicle Data The Traffic CV Management FN1587-V01 for Traffic System shall store all logged Operations SSMs sent by the RSU Functional CVE- V2I Mobility Vehicle Data The Traffic CV Management FN1588-V01 for Traffic System shall store all logged Operations SPaT messages sent by the RSU Functional CVE- V2I Mobility Vehicle Data The Traffic CV Management FN1589-V01 for Traffic System shall store all logged Operations RSM messages sent by the RSU Functional CVE- V2I Mobility Vehicle Data The Traffic CV Management FN1590-V01 for Traffic System shall store all MAP Operations messages that are input by the Traffic Manager Functional CVE- V2I Mobility Vehicle Data The Traffic CV Management FN1591-V01 for Traffic System shall make all stored Operations data available to the Traffic Manager
USER NEED: CVE-UN510-v02 USER: Transit Manager Title: Service Management Description: A transit manager needs to keep buses on schedule by reducing delays experienced at signalized intersections.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 209 Appendix C. Relationship Matrix
Priority: Desirable
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Performance CVE- V2I Mobility Transit Signal The TSP application (see PR1530-V01 Priority Appendix B) shall meet TRL 6 criteria (has been tested in a realistic envrionment outside of a laboratory and satisfies operational requirements when confronted with realistic problems) Performance CVE- V2I Mobility Transit Signal The TSP application (see PR1529-V01 Priority Appendix B) should employ algorithms that are used in MMITSS to enable transit signal priority Functional CVE- V2I Mobility Transit Signal A Transit Vehicle OBU shall FN1488-V01 Priority request to receive signal priority at RSU-equipped intersections Functional CVE- V2I Mobility Transit Signal A Transit Vehicle OBU shall FN1489-V01 Priority send a SRM to an RSU when it is within a configurable distance of the intersection it intends to request priority for Functional CVE- V2I Mobility Transit Signal A Transit Vehicle OBU shall FN1490-V01 Priority only request priority in an SRM Functional CVE- V2I Mobility Transit Signal A Transit Vehicle OBU shall FN1491-V01 Priority only request priority for movements along the route being traversed by that transit vehicle Functional CVE- V2I Mobility Transit Signal A request to receive signal FN1501-V01 Priority priority from a Transit Vehicle OBU shall be low priority Functional CVE- V2I Mobility Transit Signal An Transit Vehicle OBU shall FN1492-V01 Priority cease broadcasting SRMs for priority at a given intersection for a configurable amount of time after it has received an SSM from that intersection that contains the Transit Vehicle OBU ID Functional CVE- V2I Mobility General The Traffic Signal Controller FN1509-V01 Priority/Pree shall grant an early green for a mption phase for a movement that is requested in a priority SRM when the approach for that movement is red or yellow
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
210 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional CVE- V2I Mobility General The Traffic Signal Controller FN1510-V01 Priority/Pree shall grant an extended green mption for a phase for a movement that is requested in a priority SRM when the approach for the requested movement is green Functional CVE- V2I Mobility General An RSU shall use a locally- FN1506-V01 Priority/Pree stored list of vehicle OBU IDs mption that are authorized to receive signal priority at the intersection to determine if a received SRM is sent from an OBU that is authorized to make priority requests at that intersection Functional CVE- Roadside Roadside An RSU shall have access to a FN1314-V01 Equipment Unit function that generates SSM messages from SSM data inputs Interface CVE-IF1347- Roadside Roadside An RSU shall send information V01 Equipment Unit to request signal priority to the Traffic Signal Controller Functional CVE- Roadside Roadside An RSU shall have access to a FN1313-V01 Equipment Unit function that generates RTCM messages from RTCM data inputs Data CVE- Traffic Signal General The TSP Application shall DR1477-V01 Priority Priority/Pree require data from the SSM Applications mption Message Data CVE- Traffic Signal General The TSP Application shall DR1478-V01 Priority Priority/Pree generate data for the SRM Applications mption Message Data CVE- V2I Mobility Transit The TVIER Application shall DR1533-V01 Vehicle capture data from the all Interaction applicatiosn deployed on the Event Transit Vehicle Recording Functional CVE- V2I Mobility General The SRM shall contain the FN1498-V01 Priority/Pree intersection ID that is provided mption in the MAP message for the priority requested intersection Functional CVE- V2I Mobility General The SRM shall contain FN1499-V01 Priority/Pree information regarding the mption movement for which priority is being requested Functional CVE- V2I Mobility General High priority requests to FN1503-V01 Priority/Pree receive signal priority shall be mption serviced before low priority requests to receive signal priority
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 211 Appendix C. Relationship Matrix
Functional CVE- V2I Mobility General Multiple high priority requests FN1504-V01 Priority/Pree shall be serviced in the order in mption which they are received Functional CVE- V2I Mobility General Multiple low priority requests FN1505-V01 Priority/Pree shall be serviced in the order in mption which they are received Functional CVE- V2I Mobility General An RSU shall place a priority FN1508-V01 Priority/Pree request or a preemption mption request to the traffic signal controller for the movement specified in the SRM if the following conditions are concurrently met: 1. An OBU ID (from the received SRM) matches against the locally- stored list of vehicle OBU IDs that are authorized to receive signal priority. 2. The intersection ID in the SRM matches the intersection ID Functional CVE- V2I Mobility General An RSU shall receive output FN1518-V01 Priority/Pree from the Traffic Signal mption Controller regarding the status of a priority request Functional CVE- V2I Mobility General An RSU shall send a SSM to FN1519-V01 Priority/Pree an HDV OBU containing the mption results of the requests made by one or more vehicles for a configurable period of time Functional CVE- V2I Mobility General The Traffic CV Management FN1520-V01 Priority/Pree System shall maintain a mption modifiable list of OBU IDs authorized to send SRMs Interface CVE-IF1526- V2I Mobility Transit Signal The TSP Application shall V01 Priority transmit and receive data from the OBU's internal processing functions. Interface CVE-IF1561- V2I Mobility Transit The TIVER Application shall V01 Vehicle transmit and receive data from Interaction the OBU's internal processing Event functions. Recording
USER NEED: CVE-UN520-v02 USER: Transit Manager Title: On Schedule Status Description: A transit manager needs to know if any of its fleet in operation is behind schedule resulting from heavy traffic or increased passenger loads. Priority: Desirable
Related Requirements, Constraints, and System Interfaces
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
212 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional Sub- Type Identifier Group Component Description Functional CVE- V2I Mobility Transit Signal A Transit Vehicle OBU shall FN1488-V01 Priority request to receive signal priority at RSU-equipped intersections Functional CVE- V2I Mobility Transit Signal A Transit Vehicle OBU shall FN1489-V01 Priority send a SRM to an RSU when it is within a configurable distance of the intersection it intends to request priority for Functional CVE- V2I Mobility Transit Signal A Transit Vehicle OBU shall FN1490-V01 Priority only request priority in an SRM Functional CVE- V2I Mobility Transit Signal A Transit Vehicle OBU shall FN1491-V01 Priority only request priority for movements along the route being traversed by that transit vehicle Functional CVE- V2I Mobility Transit Signal A request to receive signal FN1501-V01 Priority priority from a Transit Vehicle OBU shall be low priority Performance CVE- V2I Mobility Transit Signal The TSP application (see PR1529-V01 Priority Appendix B) should employ algorithms that are used in MMITSS to enable transit signal priority Functional CVE- V2I Mobility General An RSU shall use a locally- FN1506-V01 Priority/Pree stored list of vehicle OBU IDs mption that are authorized to receive signal priority at the intersection to determine if a received SRM is sent from an OBU that is authorized to make priority requests at that intersection Functional CVE- V2I Mobility General The SRM shall contain the FN1498-V01 Priority/Pree intersection ID that is provided mption in the MAP message for the priority requested intersection Data CVE- Traffic Signal General The TSP Application shall DR1478-V01 Priority Priority/Pree generate data for the SRM Applications mption Message Data CVE- Traffic Signal General The TSP Application shall DR1477-V01 Priority Priority/Pree require data from the SSM Applications mption Message Data CVE- V2I Mobility Transit The TVIER Application shall DR1533-V01 Vehicle capture data from the all Interaction applicatiosn deployed on the Event Transit Vehicle Recording
USER NEED: CVE-UN530-v02 USER: Transit Manager
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 213 Appendix C. Relationship Matrix
Title: Monitor Transit Vehicle Interactions Description: A transit manager needs to assess interactions between transit vehicles and other CV-equipped vehicles on the roadway. Priority: Desirable
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall log FN1551-V01 Vehicle a Transit Vehicle Interaction Interaction Event when the transit vehicle Event OBU broadcasts an SRM Recording Functional CVE- V2I Mobility Transit A Transit Vehicle Interaction FN1557-V01 Vehicle Event shall consist of the start Interaction time of the safety interaction Event event (UTC) Recording Functional CVE- V2I Mobility Transit A Transit Vehicle Interaction FN1558-V01 Vehicle Event event shall consist Interaction of the end time of the event Event (UTC) (in the case where Recording multiple events of the same warning are issued based on messages received from the same vehicle or intersection within a configurable amount of time) Functional CVE- V2I Mobility Transit A Transit Vehicle Interaction FN1559-V01 Vehicle Event shall consist of all locally Interaction stored messages (SPaT, MAP, Event received BSMs, broadcast Recording BSMs) from a configurable amount of time before the start time of the event Functional CVE- V2I Mobility Transit A Transit Vehicle Interaction FN1560-V01 Vehicle Event shall consist of all locally Interaction stored messages (SPaT, MAP, Event received BSMs, broadcast Recording BSMs) from a configurable amount of time after the end time of the event Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall log FN1539-V01 Vehicle a Transit Vehicle Interaction Interaction Event when there is an OBU- Event equipped (remote) vehicle in Recording the host vehicle's blind spot Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall log FN1536-V01 Vehicle a Transit Vehicle Interaction Interaction Event when there is emergency
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
214 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Event braking ahead by an OBU- Recording equipped (remote) vehicle Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall log FN1537-V01 Vehicle a Transit Vehicle Interaction Interaction Event when a forward collision Event is imminent with another OBU- Recording equipped (remote) vehicle Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall log FN1538-V01 Vehicle a Transit Vehicle Interaction Interaction Event when there is an Event approaching OBU-equipped Recording (remote) vehicle on a conflicting approach at an intersection Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall log FN1540-V01 Vehicle a Transit Vehicle Interaction Interaction Event when it is changing lanes Event into another OBU-equipped Recording (remote) vehicle Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall log FN1541-V01 Vehicle a Transit Vehicle Interaction Interaction Event when the vehicle will run Event a red light at an RSU-equipped Recording intersection Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall log FN1542-V01 Vehicle a Transit Vehicle Interaction Interaction Event when the vehicle will Event enter an RSU-equipped school Recording zone over the active school zone speed limit Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall log FN1543-V01 Vehicle a Transit Vehicle Interaction Interaction Event when the vehicle is Event inside of an RSU-equipped Recording school zone over the active school zone speed limit Interface CVE-IF1473- Transit Transit CV The Transit CV Management V01 Management Management System shall make interaction Center System data available to Transit Management Staff Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall FN1534-V01 Vehicle determine when to record a Interaction Transit Vehicle Interaction Event Event. Note: A Transit Vehicle Recording Interaction Event contains the type of event along with a log of BSMs sent/received before and after the event. Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall not FN1535-V01 Vehicle issue alerts Interaction
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 215 Appendix C. Relationship Matrix
Event Recording Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall FN1544-V01 Vehicle store any BSMs received in Interaction local memory for a configurable Event amount of time. Recording Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall FN1545-V01 Vehicle store any SPaT messages Interaction received in local memory for a Event configurable amount of time. Recording Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall FN1546-V01 Vehicle store any MAP messages Interaction received in local memory for a Event configurable amount of time. Recording Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall FN1547-V01 Vehicle store any BSMs broadcast in Interaction local memory for a configurable Event amount of time. Recording Functional CVE- V2I Mobility Transit A Transit Vehicle Interaction FN1550-V01 Vehicle Event shall consist of the type Interaction of event (emergency braking Event ahead, forward collision Recording imminent, intersection movement, blind spot, lane change, red light violation, school zone speed limit, priority request) Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall FN1554-V01 Vehicle remove Transit Vehicle Interaction Interaction Event data with the Event oldest start times from memory Recording until it is able to log a newly received interaction event Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall FN1555-V01 Vehicle upload all Transit Vehicle Interaction Interaction Event data to the Event Transit CV Management Recording System when it connects to the vehicle's regular data upload service. Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall FN1556-V01 Vehicle remove all Transit Vehicle Interaction Interaction Event data from Event memory once uploaded to the Recording Transit CV Management System. Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall FN1548-V01 Vehicle store any SRMs broadcast in
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
216 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Interaction local memory for a configurable Event amount of time. Recording Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall FN1549-V01 Vehicle store any SSMs received in Interaction local memory for a configurable Event amount of time. Recording
USER NEED: CVE-UN540-v02 USER: Transit Manager Title: Transit Vehicle Operator CVE Output Description: A Transit Manager needs to understand the number of alert and warnings that will be issued to Transit Vehicle Operators. Priority: Desirable
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall FN1534-V01 Vehicle determine when to record a Interaction Transit Vehicle Interaction Event Event. Note: A Transit Vehicle Recording Interaction Event contains the type of event along with a log of BSMs sent/received before and after the event. Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall not FN1535-V01 Vehicle issue alerts Interaction Event Recording Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall log FN1536-V01 Vehicle a Transit Vehicle Interaction Interaction Event when there is emergency Event braking ahead by an OBU- Recording equipped (remote) vehicle Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall log FN1537-V01 Vehicle a Transit Vehicle Interaction Interaction Event when a forward collision Event is imminent with another OBU- Recording equipped (remote) vehicle Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall log FN1538-V01 Vehicle a Transit Vehicle Interaction Interaction Event when there is an Event approaching OBU-equipped Recording (remote) vehicle on a conflicting approach at an intersection Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall log FN1539-V01 Vehicle a Transit Vehicle Interaction Interaction Event when there is an OBU-
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 217 Appendix C. Relationship Matrix
Event equipped (remote) vehicle in Recording the host vehicle's blind spot Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall log FN1540-V01 Vehicle a Transit Vehicle Interaction Interaction Event when it is changing lanes Event into another OBU-equipped Recording (remote) vehicle Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall log FN1541-V01 Vehicle a Transit Vehicle Interaction Interaction Event when the vehicle will run Event a red light at an RSU-equipped Recording intersection Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall log FN1542-V01 Vehicle a Transit Vehicle Interaction Interaction Event when the vehicle will Event enter an RSU-equipped school Recording zone over the active school zone speed limit Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall log FN1543-V01 Vehicle a Transit Vehicle Interaction Interaction Event when the vehicle is Event inside of an RSU-equipped Recording school zone over the active school zone speed limit Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall FN1544-V01 Vehicle store any BSMs received in Interaction local memory for a configurable Event amount of time. Recording Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall FN1545-V01 Vehicle store any SPaT messages Interaction received in local memory for a Event configurable amount of time. Recording Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall FN1546-V01 Vehicle store any MAP messages Interaction received in local memory for a Event configurable amount of time. Recording Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall FN1547-V01 Vehicle store any BSMs broadcast in Interaction local memory for a configurable Event amount of time. Recording Functional CVE- V2I Mobility Transit A Transit Vehicle Interaction FN1550-V01 Vehicle Event shall consist of the type Interaction of event (emergency braking Event ahead, forward collision Recording imminent, intersection movement, blind spot, lane change, red light violation,
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
218 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
school zone speed limit, priority request) Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall FN1554-V01 Vehicle remove Transit Vehicle Interaction Interaction Event data with the Event oldest start times from memory Recording until it is able to log a newly received interaction event Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall FN1555-V01 Vehicle upload all Transit Vehicle Interaction Interaction Event data to the Event Transit CV Management Recording System when it connects to the vehicle's regular data upload service. Functional CVE- V2I Mobility Transit A Transit Vehicle OBU shall FN1556-V01 Vehicle remove all Transit Vehicle Interaction Interaction Event data from Event memory once uploaded to the Recording Transit CV Management System. Interface CVE-IF1473- Transit Transit CV The Transit CV Management V01 Management Management System shall make interaction Center System data available to Transit Management Staff
USER NEED: CVE-UN610-v02 USER: Pedestrian Title: School Zone Pedestrian Safety Description: A pedestrian in a school zone needs vehicles to travel at or below the school zone speed limit during active school zone hours. Priority: Essential
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Functional CVE- Roadside Roadside Select RSUs in/around FN1316-V01 Equipment Unit designated school zones (Linden STEM Academy and Our Lady of Peace School) shall broadcast RSMs received from the Traffic CV Management System. Functional CVE- V2I Safety Reduced An LDV OBU (host) shall issue FN1298-V01 Application Speed an alert to the LDV Operator School Zone via the HMI when the OBU- equipped (host) vehicle will enter an RSU-equipped school zone over the active school zone speed limit
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 219 Appendix C. Relationship Matrix
Functional CVE- V2I Safety Reduced An LDV OBU (host) shall issue FN1299-V01 Application Speed an alert when the OBU- School Zone equipped (host) vehicle is inside of an RSU-equipped school zone over the active school zone speed limit Functional CVE- V2I Safety Reduced The LDV OBU (host) shall FN1300-V01 Application Speed parse received RSMs to School Zone identify the school zone speed limit (J2945/4). Functional CVE- V2I Safety Reduced The LDV OBU (host) shall FN1301-V01 Application Speed parse received RSMs to School Zone identify when the school zone speed limit is active. Functional CVE- V2I Safety Reduced The LDV OBU (host) shall FN1302-V01 Application Speed parse received RSMs to School Zone identify the applicable regions of use geographical path (J2945/4). Functional CVE- V2I Safety Reduced The LDV OBU (host) shall FN1303-V01 Application Speed issue a school zone alert when School Zone all of the following conditions are concurrently met: 1. OBU- equipped (host) vehicle is traveling towards the segment where the situational awareness applies. 2. The OBU-equipped (host) vehicle is expected to enter the school zone but not below the school zone speed limit (given its current location, motion, and expected braking rate) . 3. During active school zone hours Functional CVE- V2I Safety Reduced The LDV OBU (host) shall FN1304-V01 Application Speed issue a school zone alert when School Zone all of the following conditions are concurrently met: 1. OBU- equipped (host) vehicle is within the segment where the situational awareness applies. 2. OBU-equipped (host) vehicle is traveling above the school zone speed limit. 3. During active school zone hours Performance CVE- V2I Safety Reduced The RSSZ application (see PR1306-V01 Application Speed Appendix B) should employ School Zone algorithms that are used in applications verified by CAMP to issue an RSSZ warning
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
220 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Performance CVE- V2I Safety Reduced The RSSZ application (see PR1307-V01 Application Speed Appendix B) shall meet TRL 6 School Zone criteria (has been tested in a realistic environment outside of a laboratory and satisfies operational requirements when confronted with realistic problems) Functional CVE- Roadside Roadside An RSU shall broadcast FN1310-V01 Equipment Unit (school zone) RSMs to an LDV OBU when configured to perform this function. Functional CVE- Roadside Roadside An RSU shall have access to a FN1313-V01 Equipment Unit function that generates RTCM messages from RTCM data inputs Interface CVE-IF1246- Vehicle Light-Duty An LDV OBU shall issue alerts V01 Onboard Vehicle OBU to the LDV Operator via an HMI Equipment
USER NEED: CVE-UN710-v02 USER: Network Manager Title: Maintain Connectivity Description: A Network Manager needs to maintain connectivity between CVE devices that communicate via backhaul. Priority: Essential
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Functional CVE- Roadside Roadside An RSU shall implement a FN1320-V01 Equipment Unit firewall blocking all IP access from devices to any IP address other than those approved for specific applications.
Functional CVE- Roadside Roadside An RSU shall support IPv6 FN1321-V01 Equipment Unit tunneling over IPv4. Functional CVE- Roadside Roadside An RSU shall report over a FN1322-V01 Equipment Unit management interface if channel busy ratios go above a configurable threshold.
USER NEED: CVE-SN810-v02 USER: General System Title: Operating System Connectivity Description: A roadside device needs to be connected to the Operating System. Priority: Essential
Related Requirements, Constraints, and System Interfaces
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 221 Appendix C. Relationship Matrix
Functional Sub- Type Identifier Group Component Description Functional CVE- Traffic Traffic CV The Traffic CV Management FN1437-V01 Management Management System shall transmit Center System performance metrics (as defined in the Performance Measurement Plan) derived from BSMs to the Smart Columbus OS Functional CVE- Traffic Traffic CV The Traffic CV Management FN1438-V01 Management Management System shall send PII-removed Center System RSMs to the Smart Columbus OS Functional CVE- Traffic Traffic CV The Traffic CV Management FN1439-V01 Management Management System shall send MAP Center System messages to the Smart Columbus OS Functional CVE- Traffic Traffic CV The Traffic CV Management FN1455-V01 Management Management System shall upload Center System performance metrics to the Smart Columbus OS Interface CVE-IF1472- Transit Transit CV The Transit CV Management V01 Management Management System shall send interaction Center System data to the Smart Columbus OS
USER NEED: CVE-SN820-v02 USER: General System Title: Roadside Device Wireless Communications Security Description: A roadside device needs to be connected to the SCMS. Priority: Essential
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Functional CVE- Roadside Roadside An RSU shall delete old FN1323-V01 Equipment Unit certificates upon location change. Functional CVE- Roadside Roadside An RSU shall support setting FN1324-V01 Equipment Unit the certificate geographic region to be requested for application certificates. Functional CVE- Roadside Roadside It shall be possible for a system FN1325-V01 Equipment Unit administrator with the appropriate permissions to configure the RSU to request application certificates with only designated geographic locations. Functional CVE- Roadside Roadside An RSU shall require that FN1332-V01 Equipment Unit 1609.2 signed messages are signed by a certificate that is
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
222 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
protected from modification by, or chains back to a certificate that is protected from modification by, the secure boot process. Functional CVE- Roadside Roadside An RSU shall not create or FN1333-V01 Equipment Unit transmit messages for any usage scenario if the usage scenario requires it to use 1609.2 certificates and it does not currently have valid certificates for that usage scenario Interface CVE-IF1353- Roadside Roadside The RSU-SCMS interface shall V01 Equipment Unit allow a RSU to request application certificates with different contents from the current ones during the lifetime of the current ones. Interface CVE-IF1354- Roadside Roadside Communication between the V01 Equipment Unit RSU and the SCMS shall operate in an encrypted, end- to-end connection in accordance with the selected SCMS interface. (Note: The SCMS interface should not need any further security.) Functional CVE- Roadside Roadside An RSU shall verify a DSRC FN1334-V01 Equipment Unit message if a device identifies the message as containing a new DE_TemporaryID value. Functional CVE- Roadside Roadside An RSU shall verify a DSRC FN1336-V01 Equipment Unit message if the message results in the issuance of issue either advisory, warning, or alert Functional CVE- Roadside Roadside An RSU shall verify a DSRC FN1337-V01 Equipment Unit message if the remote vehicle constitutes a potential threat (define potential threat as a vehicle that may collide with the host vehicle based on the both vehicle's speeds and trajectories) Functional CVE- Roadside Roadside An RSU shall verify a DSRC FN1338-V01 Equipment Unit message if other potential threat situations such as red- light violations, and other safety applications. Security CVE- Roadside Roadside RSUs shall support role-based SR1373-V01 Equipment Unit authentication to enable physical access.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 223 Appendix C. Relationship Matrix
USER NEED: CVE-SN830-v02 USER: General System Title: In-Vehicle Positioning Description: An in-vehicle device needs to have available position information. Priority: Essential
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Functional CVE- Vehicle General OBU An OBU shall acquire location FN1205-V01 Onboard from the LTS interface in Equipment accordance with J2945/1 section 6.2.1.
USER NEED: CVE-SN840-v02 USER: General System Title: In-Vehicle Time Synchronization Description: An in-vehicle device needs to be synchronized with a common time source. Priority: Essential
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Functional CVE- Vehicle General OBU An OBU shall acquire time from FN1204-V02 Onboard the Location and Time Service Equipment (LTS) interface in accordance with J2945/1 section 6.2.4.
USER NEED: CVE-SN850-v02 USER: General System Title: Roadside Time Synchronization Description: A roadside device needs to be synchronized with a common time source. Priority: Essential
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Functional CVE- Roadside Roadside An RSU shall acquire time from FN1308-V01 Equipment Unit the LTS interface in accordance with J2945/1 section 6.2.4.
USER NEED: CVE-SN860-v02 USER: General System Title: Position Correction Description: A roadside device needs to have access to position correction information. Priority: Essential
Related Requirements, Constraints, and System Interfaces
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
224 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Functional Sub- Type Identifier Group Component Description Functional CVE- Roadside Roadside An RSU shall acquire location FN1309-V01 Equipment Unit from the LTS interface in accordance with J2945/1 section 6.2.1. Functional CVE- Roadside Roadside An RSU shall obtain position FN1113-V01 Equipment Unit correction information from a Continuously Operating Reference Station (CORS) for packaging and broadcasting as the RTCM message.
USER NEED: CVE-SN870-v02 USER: General System Title: In-Vehicle Device Wireless Communications Security Description: An in-vehicle device needs to be able to maintain access control lists and obtain new certificates when necessary. Priority: Essential
Related Requirements, Constraints, and System Interfaces Functional Sub- Type Identifier Group Component Description Functional CVE- Roadside Roadside An RSU shall broadcast the FN1319-V01 Equipment Unit WSA for certificate download on control channel 178 and indicate IPv6 connectivity and the IP address on a service channel other than channel 172 or 178. Functional CVE- Vehicle General OBU An OBU shall not continue to FN1186-V01 Onboard start up and will log an error if Equipment the host processor determines it is not in a known good software state on boot up. Security CVE- Vehicle General OBU The OBU shall cease SR1254-V01 Onboard transmission of BSMs if the Equipment OBU determines that it has been blacklisted. Note: Blacklists detail devices that should not be trusted in the system or network Security CVE- Vehicle General OBU The OBU shall prevent SR1255-V01 Onboard incoming messages with invalid Equipment conditions per criteria in the IEEE 1609.2 from being acted on. Security CVE- Vehicle General OBU The OBU Vehicle SR1256-V01 Onboard Communications link shall have Equipment communications security to ensure the authenticity of all its messages in accordance to the
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 225 Appendix C. Relationship Matrix
standards prescribed by the overall USDOT connected vehicle program. Security CVE- Vehicle General OBU The OBU shall carry out SR1257-V01 Onboard plausibility checking on the Equipment remote vehicle BSM data. Security CVE- Vehicle General OBU The OBU shall indicate SR1258-V01 Onboard successful receipt of the Equipment pseudonym certificates. Security CVE- Vehicle General OBU When the OBU has no valid SR1259-V01 Onboard BSM signing certificates, it Equipment shall store the log file entries as IEEE 1609.2 data of type unsecured. Security CVE- Vehicle General OBU The OBU shall obtain SR1261-V01 Onboard certificates via IPv6 Equipment connectivity through the RSU. Security CVE- Vehicle General OBU An OBU shall communicate SR1262-V01 Onboard using SNMPv3 with SNMP Equipment messages protected by being sent over TLS. Security CVE- Vehicle General OBU An OBU shall support SR1263-V01 Onboard establishment of a standard Equipment TLS-based VPN with client authentication for communication to the Traffic CV Management System, with a long-term client cert and a single CA cert trusted to authorize connections from the Traffic CV Management System. Security CVE- Vehicle General OBU An OBU shall verify received SR1264-V01 Onboard messages per IEEE 1609.2 Equipment and per the relevant security profiles before using them for operations in any application. Security CVE- Vehicle General OBU An OBU shall provide real-time SR1265-V01 Onboard tamper data which indicates Equipment that the device has been tampered with (e.g. opening of the case). Security CVE- Vehicle General OBU An OBU shall require that SR1266-V01 Onboard 1609.2 signed messages are Equipment signed by a certificate that is protected from modification by, or chains back to a certificate that is protected from modification by, the secure boot process.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
226 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Security CVE- Vehicle General OBU An OBU shall only transmit SR1267-V01 Onboard messages for any usage Equipment scenario if the usage scenario requires it to use 1609.2 certificates and it currently has valid certificates for that usage scenario Security CVE- Vehicle General OBU An OBU shall verify a DSRC SR1268-V01 Onboard message when a device Equipment identifies the message as containing a new DE_TemporaryID value. Security CVE- Vehicle General OBU An OBU shall verify a DSRC SR1269-V01 Onboard message when the message Equipment results in the issuance of issue either advisory, warning, or alert Security CVE- Vehicle General OBU An OBU shall verify a DSRC SR1270-V01 Onboard message when the remote Equipment vehicle constitutes a potential threat (define potential threat as a vehicle that may collide with the host vehicle based on the both vehicle’s speeds and trajectories Security CVE- Vehicle General OBU An OBU shall verify a DSRC SR1271-V01 Onboard message when other potential Equipment threat situations such as red- light violations, and other safety applications.
691 Source: City of Columbus
692 693
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 227 Appendix D. Other Mapped Relations
694 Appendix D. Other Mapped Relations
695 The list below provides a mapping of all the relations established for system constraints, system 696 interfaces along with a mapping of requirements related to other requirements. These relations were 697 created based off the user needs defined in Error! Reference source not found.. This organization is 698 intended for ease of use and quick reference during system design 699
700 Table 23: Constraint Relations
Constraint ID Reference Requirement ID CVE-CN1665- Constraint 21 V01 CVE-CN1664- Constraint 20 CVE-FN1466-V01 V01 CVE-FN1467-V01 CVE-FN1468-V01 CVE-FN1469-V01 CVE-FN1470-V01 CVE-FN1471-V01 CVE-CN1663- Constraint 19 CVE-FN1184-V01 V01 CVE-MT1252-V01 CVE-MT1253-V01 CVE-FN1323-V01 CVE-FN1324-V01 CVE-FN1325-V01 CVE-CN1662- Constraint 18 CVE-FN1507-V01 V01 CVE-FN1522-V01 CVE-FN1523-V01 CVE-FN1524-V01 CVE-FN1525-V01 CVE-FN1506-V01 CVE-CN1661- Constraint 17 CVE-FN1511-V01 V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1516-V01 CVE-FN1517-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
228 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Constraint ID Reference Requirement ID CVE-CN1660- Constraint 16 CVE-PR1119-V01 V01 CVE-PR1120-V01 CVE-PR1127-V01 CVE-PR1128-V01 CVE-PR1135-V01 CVE-PR1136-V01 CVE-PR1142-V01 CVE-PR1143-V01 CVE-PR1111-V01 CVE-PR1112-V01 CVE-PR1290-V01 CVE-PR1291-V01 CVE-FN1497-V01 CVE-PR1531-V01 CVE-PR1532-V01 CVE-PR1527-V01 CVE-PR1530-V01 CVE-PR1528-V01 CVE-PR1306-V01 CVE-PR1307-V01 CVE-PR1529-V01 CVE-CN1659- Constraint 15 CVE-FN1317-V01 V01 CVE-IF1348-V01 CVE-IF1349-V01 CVE-PY1370-V01 CVE-PY1371-V01 CVE-MT1364-V01 CVE-CN1658- Constraint 14 CVE-FN1185-V01 V01 CVE-CN1657- Constraint 13 CVE-FN1185-V01 V01 CVE-CN1656- Constraint 12 CVE-FN1185-V01 V01 CVE-CN1655- Constraint 11 CVE-FN1185-V01 V01 CVE-CN1654- Constraint 10 CVE-FN1185-V01 V01 CVE-CN1653- Constraint 9 CVE-FN1185-V01 V01 CVE-CN1652- Constraint 8 CVE-FN1185-V01 V01 CVE-CN1651- Constraint 7 CVE-FN1185-V01 V01 CVE-CN1650- Constraint 6 CVE-FN1185-V01 V01 CVE-CN1649- Constraint 5 CVE-FN1185-V01 V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 229 Appendix D. Other Mapped Relations
Constraint ID Reference Requirement ID CVE-CN1648- Constraint 4 CVE-DR1375-V01 V01 CVE-FN1208-V01 CVE-FN1209-V01 CVE-FN1311-V01 CVE-FN1315-V01 CVE-PR1369-V01 CVE-PY1372-V01 CVE-FN1332-V01 CVE-FN1333-V01 CVE-FN1308-V01 CVE-FN1309-V01 CVE-FN1330-V01 CVE-CN1647- Constraint 3 V01 CVE-CN1646- Constraint 2 V01 CVE-CN1645- Constraint 1 CVE-MT1364-V01 V01 CVE-FN1335-V01 CVE-MT1593-V01 CVE-MT1594-V01 CVE-MT1595-V01 CVE-MT1596-V01 CVE-MT1597-V01 CVE-MT1598-V01 CVE-MT1599-V01 CVE-MT1600-V01 CVE-MT1601-V01 CVE-MT1602-V01 CVE-MT1603-V01 CVE-MT1604-V01 CVE-RG1605-V01 CVE-RG1606-V01 CVE-RG1607-V01
701 Source: City of Columbus
702 Table D-24 System Interface Relations
Interface ID Reference Requirement ID CVE-IX1644- Interface 29 CVE-IF1248-V01 V01 CVE-IF1247-V01 CVE-IX1643- Interface 28 CVE-IF1473-V01 V01 CVE-IX1642- Interface 27 CVE-FN1206-V01 V01 CVE-IX1641- Interface 26 CVE-FN1207-V01 V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
230 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Interface ID Reference Requirement ID CVE-IX1640- Interface 25 CVE-IF1472-V01 V01 CVE-IF1277-V01 CVE-IX1639- Interface 24 CVE-FN1437-V01 V01 CVE-FN1438-V01 CVE-FN1439-V01 CVE-IX1638- Interface 23.2 CVE-IF1340-V01 V01 CVE-IF1345-V01 CVE-IF1346-V01 CVE-IX1637- Interface 23.1 CVE-IF1350-V01 V01 CVE-IF1351-V01 CVE-IF1352-V01 CVE-IX1636- Interface 22.2 CVE-IF1341-V01 V01 CVE-IF1342-V01 CVE-FN1441-V01 CVE-IX1635- Interface 22.1 CVE-FN1318-V01 V01 CVE-FN1328-V01 CVE-FN1329-V01 CVE-FN1456-V01 CVE-FN1563-V01 CVE-FN1566-V01 CVE-FN1569-V01 CVE-FN1572-V01 CVE-FN1577-V01 CVE-FN1580-V01 CVE-FN1581-V01 CVE-FN1582-V01 CVE-FN1584-V01 CVE-IX1634- Interface 21.2 CVE-FN1327-V01 V01 CVE-IF1344-V01 CVE-IF1354-V01 CVE-IF1353-V01 CVE-IX1633- Interface 21.1 CVE-IF1354-V01 V01 CVE-IX1632- Interface 20.2 CVE-IF1250-V01 V01 CVE-IF1220-V01 CVE-IX1631- Interface 20.1 CVE-IF1227-V01 V01 CVE-IF1231-V01 CVE-IF1235-V01 CVE-IF1238-V01 CVE-IF1241-V01 CVE-IF1360-V01 CVE-IF1359-V01 CVE-IX1630- Interface 19 CVE-IF1223-V01 V01 CVE-IF1224-V01 CVE-IF1218-V01 CVE-IF1219-V01 CVE-IF1220-V01 CVE-IF1221-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 231 Appendix D. Other Mapped Relations
Interface ID Reference Requirement ID CVE-IX1629- Interface 18 CVE-IF1223-V01 V01 CVE-IF1224-V01 CVE-IF1218-V01 CVE-IF1219-V01 CVE-IF1220-V01 CVE-IF1221-V01 CVE-IX1628- Interface 17 CVE-IF1339-V01 V01 CVE-FN1113-V01 CVE-FN1320-V01 CVE-FN1321-V01 CVE-IX1627- Interface 16 V01 CVE-IX1626- Interface 15 CVE-FN1320-V01 V01 CVE-FN1321-V01 CVE-IX1625- Interface 14 CVE-IF1343-V01 V01 CVE-FN1308-V01 CVE-FN1309-V01 CVE-IX1624- Interface 13 CVE-FN1204-V02 V01 CVE-FN1205-V01 CVE-IX1623- Interface 12 CVE-IF1242-V01 V01 CVE-FN1204-V02 CVE-FN1205-V01 CVE-IX1622- Interface 11 CVE-FN1204-V02 V01 CVE-FN1205-V01 CVE-IX1621- Interface 10 CVE-FN1205-V01 V01 CVE-FN1204-V02 CVE-IX1620- Interface 9.2 CVE-IF1225-V01 V01 CVE-IF1229-V01 CVE-IF1233-V01 CVE-IF1240-V01 CVE-IF1360-V01 CVE-FN1310-V01 CVE-IF1243-V01 CVE-IF1356-V01 CVE-IF1357-V01 CVE-IF1358-V01 CVE-FN1310-V01 CVE-IX1619- Interface 9.1 CVE-IF1218-V01 V01 CVE-FN1212-V01 CVE-FN1330-V01 CVE-IF1361-V01 CVE-IF1362-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
232 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Interface ID Reference Requirement ID CVE-IX1618- Interface 8 CVE-FN1187-V01 V01 CVE-FN1197-V01 CVE-FN1198-V01 CVE-FN1199-V01 CVE-FN1200-V01 CVE-FN1201-V01 CVE-FN1202-V01 CVE-FN1213-V01 CVE-FN1214-V01 CVE-IF1222-V01 CVE-IF1246-V01 CVE-FN1123-V01 CVE-IX1617- Interface 7 CVE-FN1207-V01 V01 CVE-IX1616- Interface 6.2 CVE-IF1226-V01 V01 CVE-IF1230-V01 CVE-IF1234-V01 CVE-IF1237-V01 CVE-FN1330-V01 CVE-IF1243-V01 CVE-IF1356-V01 CVE-IF1357-V01 CVE-IF1358-V01 CVE-IF1359-V01 CVE-IX1615- Interface 6.1 CVE-IF1249-V01 V01 CVE-IF1219-V01 CVE-FN1212-V01 CVE-IF1361-V01 CVE-IF1362-V01 CVE-IF1363-V01 CVE-IX1614- Interface 5.2 V01 CVE-IX1613- Interface 5.1 V01 CVE-IX1612- Interface 4 V01 CVE-IX1611- Interface 3 CVE-FN1442-V01 V01 CVE-FN1443-V01 CVE-FN1444-V01 CVE-FN1445-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 233 Appendix D. Other Mapped Relations
Interface ID Reference Requirement ID CVE-IX1610- Interface 2.2 CVE-IF1228-V01 V01 CVE-IF1232-V01 CVE-IF1236-V01 CVE-IF1239-V01 CVE-IF1243-V01 CVE-IF1356-V01 CVE-IF1357-V01 CVE-IF1358-V01 CVE-IF1359-V01 CVE-FN1319-V01 CVE-IX1609- Interface 2.1 CVE-IF1251-V01 V01 CVE-IF1362-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-FN1330-V01 CVE-FN1212-V01 CVE-IF1221-V01 CVE-IX1608- Interface 1 CVE-IF1244-V01 V01 CVE-IF1245-V01 CVE-FN1207-V01
703 Source: City of Columbus
704 Table D-25 Requirements Mapped to Requirements
Requirement ID Related Requirements CVE-FN1591-V01 CVE-DR1402-V01 CVE-DR1404-V01 CVE-DR1405-V01 CVE-DR1406-V01 CVE-DR1407-V01 CVE-DR1408-V01 CVE-DR1409-V01 CVE-DR1410-V01 CVE-DR1411-V01 CVE-DR1412-V01 CVE-DR1413-V01 CVE-DR1414-V01 CVE-DR1415-V01 CVE-DR1416-V01 CVE-DR1417-V01 CVE-DR1418-V01 CVE-DR1419-V01 CVE-FN1590-V01 CVE-DR1402-V01 CVE-DR1404-V01 CVE-DR1405-V01 CVE-DR1406-V01 CVE-DR1407-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
234 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Requirement ID Related Requirements CVE-DR1408-V01 CVE-DR1409-V01 CVE-DR1410-V01 CVE-DR1411-V01 CVE-DR1412-V01 CVE-DR1413-V01 CVE-DR1414-V01 CVE-DR1415-V01 CVE-DR1416-V01 CVE-DR1417-V01 CVE-DR1418-V01 CVE-DR1419-V01 CVE-FN1589-V01 CVE-DR1402-V01 CVE-DR1404-V01 CVE-DR1405-V01 CVE-DR1406-V01 CVE-DR1407-V01 CVE-DR1408-V01 CVE-DR1409-V01 CVE-DR1410-V01 CVE-DR1411-V01 CVE-DR1412-V01 CVE-DR1413-V01 CVE-DR1414-V01 CVE-DR1415-V01 CVE-DR1416-V01 CVE-DR1417-V01 CVE-DR1418-V01 CVE-DR1419-V01 CVE-FN1582-V01 CVE-DR1292-V01 CVE-DR1294-V01 CVE-DR1295-V01 CVE-DR1296-V01 CVE-FN1581-V01 CVE-DR1276-V01 CVE-FN1567-V01 CVE-DR1402-V01 CVE-DR1404-V01 CVE-DR1405-V01 CVE-DR1406-V01 CVE-DR1407-V01 CVE-DR1408-V01 CVE-DR1409-V01 CVE-DR1410-V01 CVE-DR1411-V01 CVE-DR1412-V01 CVE-DR1413-V01 CVE-DR1414-V01 CVE-DR1415-V01 CVE-DR1416-V01 CVE-DR1417-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 235 Appendix D. Other Mapped Relations
Requirement ID Related Requirements CVE-DR1418-V01 CVE-DR1419-V01 CVE-FN1566-V01 CVE-PR1105-V01 CVE-FN1503-V01 CVE-FN1504-V01 CVE-FN1505-V01 CVE-FN1506-V01 CVE-FN1508-V01 CVE-FN1463-V01 CVE-FN1480-V01 CVE-PR1105-V01 CVE-FN1563-V01 CVE-DR1420-V01 CVE-DR1422-V01 CVE-DR1423-V01 CVE-DR1424-V01 CVE-DR1425-V01 CVE-DR1426-V01 CVE-DR1427-V01 CVE-DR1428-V01 CVE-DR1429-V01 CVE-DR1430-V01 CVE-DR1431-V01 CVE-DR1432-V01 CVE-DR1433-V01 CVE-DR1434-V01 CVE-DR1435-V01 CVE-DR1436-V01 CVE-FN1314-V01 CVE-FN1560-V01 CVE-DR1374-V01 CVE-FN1313-V01 CVE-FN1559-V01 CVE-DR1144-V01 CVE-DR1145-V01 CVE-DR1146-V01 CVE-DR1147-V01 CVE-DR1148-V01 CVE-DR1149-V01 CVE-DR1150-V01 CVE-DR1151-V01 CVE-DR1152-V01 CVE-DR1153-V01 CVE-DR1154-V01 CVE-DR1155-V01 CVE-DR1156-V01 CVE-DR1157-V01 CVE-DR1158-V01 CVE-DR1159-V01 CVE-DR1160-V01 CVE-DR1161-V01 CVE-DR1162-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
236 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Requirement ID Related Requirements CVE-DR1163-V01 CVE-DR1164-V01 CVE-DR1165-V01 CVE-DR1166-V01 CVE-DR1167-V01 CVE-DR1168-V01 CVE-DR1169-V01 CVE-DR1170-V01 CVE-DR1171-V01 CVE-DR1172-V01 CVE-DR1173-V01 CVE-DR1174-V01 CVE-DR1175-V01 CVE-DR1176-V01 CVE-DR1177-V01 CVE-DR1178-V01 CVE-DR1179-V01 CVE-DR1181-V01 CVE-DR1182-V01 CVE-PR1183-V01 CVE-FN1557-V01 CVE-DR1378-V01 CVE-DR1379-V01 CVE-DR1380-V01 CVE-DR1381-V01 CVE-DR1382-V01 CVE-DR1383-V01 CVE-DR1384-V01 CVE-DR1385-V01 CVE-DR1386-V01 CVE-DR1387-V01 CVE-DR1388-V01 CVE-DR1389-V01 CVE-DR1390-V01 CVE-DR1391-V01 CVE-DR1392-V01 CVE-DR1393-V01 CVE-DR1394-V01 CVE-DR1395-V01 CVE-DR1396-V01 CVE-DR1397-V01 CVE-DR1398-V01 CVE-PR1399-V01 CVE-PR1400-V01 CVE-PR1401-V01 CVE-FN1312-V01 CVE-FN1551-V01 CVE-DR1391-V01 CVE-DR1392-V01 CVE-FN1542-V01 CVE-IF1234-V01 CVE-FN1541-V01 CVE-IF1222-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 237 Appendix D. Other Mapped Relations
Requirement ID Related Requirements CVE-FN1540-V01 CVE-DR1149-V01 CVE-FN1539-V01 CVE-FN1538-V01 CVE-DR1145-V01
CVE-PR1530-V01 CVE-FN1188-V01 CVE-FN1194-V01 CVE-FN1210-V01 CVE-FN1524-V01 CVE-DR1292-V01 CVE-DR1294-V01 CVE-DR1295-V01 CVE-DR1296-V01 CVE-PR1105-V01 CVE-FN1503-V01 CVE-FN1504-V01 CVE-FN1505-V01 CVE-FN1506-V01 CVE-FN1508-V01 CVE-FN1566-V01 CVE-FN1463-V01 CVE-FN1480-V01 CVE-FN1503-V01 CVE-FN1504-V01 CVE-FN1505-V01 CVE-FN1506-V01 CVE-FN1508-V01 CVE-FN1566-V01 CVE-FN1463-V01 CVE-FN1480-V01 CVE-DR1144-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1145-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1538-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1146-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
238 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Requirement ID Related Requirements CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1147-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1148-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1149-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-FN1540-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1150-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1151-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1152-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 239 Appendix D. Other Mapped Relations
Requirement ID Related Requirements CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1153-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1154-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1155-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1156-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1157-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1158-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
240 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Requirement ID Related Requirements CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1159-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1160-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1161-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1162-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1163-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1165-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 241 Appendix D. Other Mapped Relations
Requirement ID Related Requirements CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1166-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1167-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1168-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1169-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1170-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1171-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
242 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Requirement ID Related Requirements CVE-IF1363-V01 CVE-DR1172-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1173-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1174-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1175-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1176-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1177-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 243 Appendix D. Other Mapped Relations
Requirement ID Related Requirements CVE-DR1178-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1179-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1181-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-DR1182-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-PR1183-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-FN1188-V01 CVE-PR1530-V01 CVE-FN1189-V01 CVE-FN1195-V01 CVE-FN1190-V01 CVE-FN1196-V01 CVE-FN1191-V01 CVE-FN1195-V01 CVE-FN1192-V01 CVE-FN1204-V02 CVE-FN1193-V01 CVE-FN1196-V01 CVE-FN1204-V02
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
244 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Requirement ID Related Requirements CVE-FN1194-V01 CVE-PR1530-V01 CVE-FN1195-V01 CVE-FN1189-V01 CVE-FN1191-V01 CVE-FN1196-V01 CVE-FN1190-V01 CVE-FN1193-V01 CVE-FN1204-V02 CVE-FN1192-V01 CVE-FN1193-V01 CVE-FN1210-V01 CVE-PR1530-V01 CVE-IF1222-V01 CVE-FN1541-V01 CVE-IF1234-V01 CVE-FN1542-V01 CVE-IF1238-V01 CVE-DR1292-V01 CVE-DR1294-V01 CVE-DR1295-V01 CVE-DR1296-V01 CVE-IF1240-V01 CVE-PR1365-V01 CVE-PR1366-V01 CVE-PR1367-V01 CVE-PR1368-V01 CVE-IF1241-V01 CVE-PR1365-V01 CVE-PR1366-V01 CVE-PR1367-V01 CVE-PR1368-V01 CVE-IF1242-V01 CVE-PR1365-V01 CVE-PR1366-V01 CVE-PR1367-V01 CVE-PR1368-V01 CVE-SR1271-V01 CVE-DR1292-V01 CVE-DR1294-V01 CVE-DR1295-V01 CVE-DR1296-V01 CVE-DR1272-V01 CVE-DR1144-V01 CVE-DR1145-V01 CVE-DR1146-V01 CVE-DR1147-V01 CVE-DR1148-V01 CVE-DR1149-V01 CVE-DR1150-V01 CVE-DR1151-V01 CVE-DR1152-V01 CVE-DR1153-V01 CVE-DR1154-V01 CVE-DR1155-V01 CVE-DR1156-V01 CVE-DR1157-V01 CVE-DR1158-V01 CVE-DR1159-V01 CVE-DR1160-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 245 Appendix D. Other Mapped Relations
Requirement ID Related Requirements CVE-DR1161-V01 CVE-DR1162-V01 CVE-DR1163-V01 CVE-DR1164-V01 CVE-DR1165-V01 CVE-DR1166-V01 CVE-DR1167-V01 CVE-DR1168-V01 CVE-DR1169-V01 CVE-DR1170-V01 CVE-DR1171-V01 CVE-DR1172-V01 CVE-DR1173-V01 CVE-DR1174-V01 CVE-DR1175-V01 CVE-DR1176-V01 CVE-DR1177-V01 CVE-DR1178-V01 CVE-DR1179-V01 CVE-DR1181-V01 CVE-DR1182-V01 CVE-PR1183-V01 CVE-DR1276-V01 CVE-FN1581-V01 CVE-DR1292-V01 CVE-IF1238-V01 CVE-SR1271-V01 CVE-IF1360-V01 CVE-FN1523-V01 CVE-FN1524-V01 CVE-FN1582-V01 CVE-DR1294-V01 CVE-IF1238-V01 CVE-SR1271-V01 CVE-IF1360-V01 CVE-FN1523-V01 CVE-FN1524-V01 CVE-FN1582-V01 CVE-DR1295-V01 CVE-IF1238-V01 CVE-SR1271-V01 CVE-IF1360-V01 CVE-FN1523-V01 CVE-FN1524-V01 CVE-FN1582-V01 CVE-DR1296-V01 CVE-IF1238-V01 CVE-SR1271-V01 CVE-IF1360-V01 CVE-FN1523-V01 CVE-FN1524-V01 CVE-FN1582-V01 CVE-FN1312-V01 CVE-FN1557-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
246 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Requirement ID Related Requirements CVE-FN1313-V01 CVE-FN1560-V01 CVE-FN1314-V01 CVE-FN1563-V01 CVE-FN1523-V01 CVE-DR1292-V01 CVE-DR1294-V01 CVE-DR1295-V01 CVE-DR1296-V01 CVE-FN1522-V01 CVE-DR1420-V01 CVE-DR1422-V01 CVE-DR1423-V01 CVE-DR1424-V01 CVE-DR1425-V01 CVE-DR1426-V01 CVE-DR1427-V01 CVE-DR1428-V01 CVE-DR1429-V01 CVE-DR1430-V01 CVE-DR1431-V01 CVE-DR1432-V01 CVE-DR1433-V01 CVE-DR1434-V01 CVE-DR1435-V01 CVE-DR1436-V01 CVE-FN1521-V01 CVE-DR1420-V01 CVE-DR1422-V01 CVE-DR1423-V01 CVE-DR1424-V01 CVE-DR1425-V01 CVE-DR1426-V01 CVE-DR1427-V01 CVE-DR1428-V01 CVE-DR1429-V01 CVE-DR1430-V01 CVE-DR1431-V01 CVE-DR1432-V01 CVE-DR1433-V01 CVE-DR1434-V01 CVE-DR1435-V01 CVE-DR1436-V01 CVE-FN1520-V01 CVE-DR1420-V01 CVE-DR1422-V01 CVE-DR1423-V01 CVE-DR1424-V01 CVE-DR1425-V01 CVE-DR1426-V01 CVE-DR1427-V01 CVE-DR1428-V01 CVE-DR1429-V01 CVE-DR1430-V01 CVE-DR1431-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 247 Appendix D. Other Mapped Relations
Requirement ID Related Requirements CVE-DR1432-V01 CVE-DR1433-V01 CVE-DR1434-V01 CVE-DR1435-V01 CVE-DR1436-V01 CVE-FN1519-V01 CVE-DR1374-V01 CVE-FN1518-V01 CVE-DR1374-V01 CVE-FN1517-V01 CVE-DR1374-V01 CVE-FN1516-V01 CVE-DR1374-V01 CVE-FN1515-V01 CVE-DR1144-V01 CVE-DR1145-V01 CVE-DR1146-V01 CVE-DR1147-V01 CVE-DR1148-V01 CVE-DR1149-V01 CVE-DR1150-V01 CVE-DR1151-V01 CVE-DR1152-V01 CVE-DR1153-V01 CVE-DR1154-V01 CVE-DR1155-V01 CVE-DR1156-V01 CVE-DR1157-V01 CVE-DR1158-V01 CVE-DR1159-V01 CVE-DR1160-V01 CVE-DR1161-V01 CVE-DR1162-V01 CVE-DR1163-V01 CVE-DR1164-V01 CVE-DR1165-V01 CVE-DR1166-V01 CVE-DR1167-V01 CVE-DR1168-V01 CVE-DR1169-V01 CVE-DR1170-V01 CVE-DR1171-V01 CVE-DR1172-V01 CVE-DR1173-V01 CVE-DR1174-V01 CVE-DR1175-V01 CVE-DR1176-V01 CVE-DR1177-V01 CVE-DR1178-V01 CVE-DR1179-V01 CVE-DR1181-V01 CVE-DR1182-V01 CVE-PR1183-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
248 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Requirement ID Related Requirements CVE-FN1514-V01 CVE-DR1144-V01 CVE-DR1145-V01 CVE-DR1146-V01 CVE-DR1147-V01 CVE-DR1148-V01 CVE-DR1149-V01 CVE-DR1150-V01 CVE-DR1151-V01 CVE-DR1152-V01 CVE-DR1153-V01 CVE-DR1154-V01 CVE-DR1155-V01 CVE-DR1156-V01 CVE-DR1157-V01 CVE-DR1158-V01 CVE-DR1159-V01 CVE-DR1160-V01 CVE-DR1161-V01 CVE-DR1162-V01 CVE-DR1163-V01 CVE-DR1164-V01 CVE-DR1165-V01 CVE-DR1166-V01 CVE-DR1167-V01 CVE-DR1168-V01 CVE-DR1169-V01 CVE-DR1170-V01 CVE-DR1171-V01 CVE-DR1172-V01 CVE-DR1173-V01 CVE-DR1174-V01 CVE-DR1175-V01 CVE-DR1176-V01 CVE-DR1177-V01 CVE-DR1178-V01 CVE-DR1179-V01 CVE-DR1181-V01 CVE-DR1182-V01 CVE-PR1183-V01 CVE-FN1513-V01 CVE-DR1144-V01 CVE-DR1145-V01 CVE-DR1146-V01 CVE-DR1147-V01 CVE-DR1148-V01 CVE-DR1149-V01 CVE-DR1150-V01 CVE-DR1151-V01 CVE-DR1152-V01 CVE-DR1153-V01 CVE-DR1154-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 249 Appendix D. Other Mapped Relations
Requirement ID Related Requirements CVE-DR1155-V01 CVE-DR1156-V01 CVE-DR1157-V01 CVE-DR1158-V01 CVE-DR1159-V01 CVE-DR1160-V01 CVE-DR1161-V01 CVE-DR1162-V01 CVE-DR1163-V01 CVE-DR1164-V01 CVE-DR1165-V01 CVE-DR1166-V01 CVE-DR1167-V01 CVE-DR1168-V01 CVE-DR1169-V01 CVE-DR1170-V01 CVE-DR1171-V01 CVE-DR1172-V01 CVE-DR1173-V01 CVE-DR1174-V01 CVE-DR1175-V01 CVE-DR1176-V01 CVE-DR1177-V01 CVE-DR1178-V01 CVE-DR1179-V01 CVE-DR1181-V01 CVE-DR1182-V01 CVE-PR1183-V01 CVE-FN1512-V01 CVE-DR1144-V01 CVE-DR1145-V01 CVE-DR1146-V01 CVE-DR1147-V01 CVE-DR1148-V01 CVE-DR1149-V01 CVE-DR1150-V01 CVE-DR1151-V01 CVE-DR1152-V01 CVE-DR1153-V01 CVE-DR1154-V01 CVE-DR1155-V01 CVE-DR1156-V01 CVE-DR1157-V01 CVE-DR1158-V01 CVE-DR1159-V01 CVE-DR1160-V01 CVE-DR1161-V01 CVE-DR1162-V01 CVE-DR1163-V01 CVE-DR1164-V01 CVE-DR1165-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
250 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Requirement ID Related Requirements CVE-DR1166-V01 CVE-DR1167-V01 CVE-DR1168-V01 CVE-DR1169-V01 CVE-DR1170-V01 CVE-DR1171-V01 CVE-DR1172-V01 CVE-DR1173-V01 CVE-DR1174-V01 CVE-DR1175-V01 CVE-DR1176-V01 CVE-DR1177-V01 CVE-DR1178-V01 CVE-DR1179-V01 CVE-DR1181-V01 CVE-DR1182-V01 CVE-PR1183-V01 CVE-FN1511-V01 CVE-DR1378-V01 CVE-DR1379-V01 CVE-DR1380-V01 CVE-DR1381-V01 CVE-DR1382-V01 CVE-DR1383-V01 CVE-DR1384-V01 CVE-DR1385-V01 CVE-DR1386-V01 CVE-DR1387-V01 CVE-DR1388-V01 CVE-DR1389-V01 CVE-DR1390-V01 CVE-DR1391-V01 CVE-DR1392-V01 CVE-DR1393-V01 CVE-DR1394-V01 CVE-DR1395-V01 CVE-DR1396-V01 CVE-DR1397-V01 CVE-DR1398-V01 CVE-PR1399-V01 CVE-PR1400-V01 CVE-PR1401-V01 CVE-FN1510-V01 CVE-DR1378-V01 CVE-DR1379-V01 CVE-DR1380-V01 CVE-DR1381-V01 CVE-DR1382-V01 CVE-DR1383-V01 CVE-DR1384-V01 CVE-DR1385-V01 CVE-DR1386-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 251 Appendix D. Other Mapped Relations
Requirement ID Related Requirements CVE-DR1387-V01 CVE-DR1388-V01 CVE-DR1389-V01 CVE-DR1390-V01 CVE-DR1391-V01 CVE-DR1392-V01 CVE-DR1393-V01 CVE-DR1394-V01 CVE-DR1395-V01 CVE-DR1396-V01 CVE-DR1397-V01 CVE-DR1398-V01 CVE-PR1399-V01 CVE-PR1400-V01 CVE-PR1401-V01 CVE-FN1509-V01 CVE-DR1378-V01 CVE-DR1379-V01 CVE-DR1380-V01 CVE-DR1381-V01 CVE-DR1382-V01 CVE-DR1383-V01 CVE-DR1384-V01 CVE-DR1385-V01 CVE-DR1386-V01 CVE-DR1387-V01 CVE-DR1388-V01 CVE-DR1389-V01 CVE-DR1390-V01 CVE-DR1391-V01 CVE-DR1392-V01 CVE-DR1393-V01 CVE-DR1394-V01 CVE-DR1395-V01 CVE-DR1396-V01 CVE-DR1397-V01 CVE-DR1398-V01 CVE-PR1399-V01 CVE-PR1400-V01 CVE-PR1401-V01 CVE-FN1508-V01 CVE-PR1105-V01 CVE-FN1503-V01 CVE-FN1504-V01 CVE-FN1505-V01 CVE-FN1506-V01 CVE-FN1566-V01 CVE-FN1463-V01 CVE-FN1480-V01 CVE-PR1105-V01 CVE-FN1506-V01 CVE-PR1105-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
252 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Requirement ID Related Requirements CVE-FN1503-V01 CVE-FN1504-V01 CVE-FN1505-V01 CVE-FN1508-V01 CVE-FN1566-V01 CVE-FN1463-V01 CVE-FN1480-V01 CVE-PR1105-V01 CVE-FN1505-V01 CVE-PR1105-V01 CVE-FN1503-V01 CVE-FN1504-V01 CVE-FN1506-V01 CVE-FN1508-V01 CVE-FN1566-V01 CVE-FN1463-V01 CVE-FN1480-V01 CVE-PR1105-V01 CVE-FN1504-V01 CVE-PR1105-V01 CVE-FN1503-V01 CVE-FN1505-V01 CVE-FN1506-V01 CVE-FN1508-V01 CVE-FN1566-V01 CVE-FN1463-V01 CVE-FN1480-V01 CVE-PR1105-V01 CVE-FN1503-V01 CVE-PR1105-V01 CVE-FN1504-V01 CVE-FN1505-V01 CVE-FN1506-V01 CVE-FN1508-V01 CVE-FN1566-V01 CVE-FN1463-V01 CVE-FN1480-V01 CVE-PR1105-V01 CVE-FN1484-V01 CVE-FN1479-V01 CVE-FN1480-V01 CVE-PR1105-V01 CVE-FN1503-V01 CVE-FN1504-V01 CVE-FN1505-V01 CVE-FN1506-V01 CVE-FN1508-V01 CVE-FN1566-V01 CVE-FN1463-V01 CVE-PR1105-V01 CVE-FN1479-V01 CVE-FN1484-V01 CVE-FN1470-V01 CVE-DR1420-V01 CVE-DR1422-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 253 Appendix D. Other Mapped Relations
Requirement ID Related Requirements CVE-DR1423-V01 CVE-DR1424-V01 CVE-DR1425-V01 CVE-DR1426-V01 CVE-DR1427-V01 CVE-DR1428-V01 CVE-DR1429-V01 CVE-DR1430-V01 CVE-DR1431-V01 CVE-DR1432-V01 CVE-DR1433-V01 CVE-DR1434-V01 CVE-DR1435-V01 CVE-DR1436-V01 CVE-FN1467-V01 CVE-DR1402-V01 CVE-DR1404-V01 CVE-DR1405-V01 CVE-DR1406-V01 CVE-DR1407-V01 CVE-DR1408-V01 CVE-DR1409-V01 CVE-DR1410-V01 CVE-DR1411-V01 CVE-DR1412-V01 CVE-DR1413-V01 CVE-DR1414-V01 CVE-DR1415-V01 CVE-DR1416-V01 CVE-DR1417-V01 CVE-DR1418-V01 CVE-DR1419-V01 CVE-FN1463-V01 CVE-PR1105-V01 CVE-FN1503-V01 CVE-FN1504-V01 CVE-FN1505-V01 CVE-FN1506-V01 CVE-FN1508-V01 CVE-FN1566-V01 CVE-FN1480-V01 CVE-PR1105-V01 CVE-DR1436-V01 CVE-FN1520-V01 CVE-FN1521-V01 CVE-FN1522-V01 CVE-FN1563-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE-DR1435-V01 CVE-FN1520-V01 CVE-FN1521-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
254 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Requirement ID Related Requirements CVE-FN1522-V01 CVE-FN1563-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE-DR1434-V01 CVE-FN1520-V01 CVE-FN1521-V01 CVE-FN1522-V01 CVE-FN1563-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE-DR1433-V01 CVE-FN1520-V01 CVE-FN1521-V01 CVE-FN1522-V01 CVE-FN1563-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE-DR1432-V01 CVE-FN1520-V01 CVE-FN1521-V01 CVE-FN1522-V01 CVE-FN1563-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE-DR1431-V01 CVE-FN1520-V01 CVE-FN1521-V01 CVE-FN1522-V01 CVE-FN1563-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE-DR1430-V01 CVE-FN1520-V01 CVE-FN1521-V01 CVE-FN1522-V01 CVE-FN1563-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE-DR1429-V01 CVE-FN1520-V01 CVE-FN1521-V01 CVE-FN1522-V01 CVE-FN1563-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE-DR1428-V01 CVE-FN1520-V01 CVE-FN1521-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 255 Appendix D. Other Mapped Relations
Requirement ID Related Requirements CVE-FN1522-V01 CVE-FN1563-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE-DR1427-V01 CVE-FN1520-V01 CVE-FN1521-V01 CVE-FN1522-V01 CVE-FN1563-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE-DR1426-V01 CVE-FN1520-V01 CVE-FN1521-V01 CVE-FN1522-V01 CVE-FN1563-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE-DR1425-V01 CVE-FN1520-V01 CVE-FN1521-V01 CVE-FN1522-V01 CVE-FN1563-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE-DR1424-V01 CVE-FN1520-V01 CVE-FN1521-V01 CVE-FN1522-V01 CVE-FN1563-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE-DR1423-V01 CVE-FN1520-V01 CVE-FN1521-V01 CVE-FN1522-V01 CVE-FN1563-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE-DR1422-V01 CVE-FN1520-V01 CVE-FN1521-V01 CVE-FN1522-V01 CVE-FN1563-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE-DR1420-V01 CVE-FN1520-V01 CVE-FN1521-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
256 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Requirement ID Related Requirements CVE-FN1522-V01 CVE-FN1563-V01 CVE-DR1388-V01 CVE-FN1470-V01 CVE-MT1604-V01 CVE-DR1419-V01 CVE-FN1589-V01 CVE-FN1590-V01 CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE-DR1418-V01 CVE-FN1589-V01 CVE-FN1590-V01 CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE-DR1417-V01 CVE-FN1589-V01 CVE-FN1590-V01 CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE-DR1416-V01 CVE-FN1589-V01 CVE-FN1590-V01 CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE-DR1415-V01 CVE-FN1589-V01 CVE-FN1590-V01 CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE-DR1414-V01 CVE-FN1589-V01 CVE-FN1590-V01 CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE-DR1413-V01 CVE-FN1589-V01 CVE-FN1590-V01 CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE-DR1412-V01 CVE-FN1589-V01 CVE-FN1590-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 257 Appendix D. Other Mapped Relations
Requirement ID Related Requirements CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE-DR1411-V01 CVE-FN1589-V01 CVE-FN1590-V01 CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE-DR1410-V01 CVE-FN1589-V01 CVE-FN1590-V01 CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE-DR1409-V01 CVE-FN1589-V01 CVE-FN1590-V01 CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE-DR1408-V01 CVE-FN1589-V01 CVE-FN1590-V01 CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE-DR1407-V01 CVE-FN1589-V01 CVE-FN1590-V01 CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE-DR1406-V01 CVE-FN1589-V01 CVE-FN1590-V01 CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE-DR1405-V01 CVE-FN1589-V01 CVE-FN1590-V01 CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE-DR1404-V01 CVE-FN1589-V01 CVE-FN1590-V01 CVE-FN1591-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
258 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Requirement ID Related Requirements CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE-DR1402-V01 CVE-FN1589-V01 CVE-FN1590-V01 CVE-FN1591-V01 CVE-FN1567-V01 CVE-FN1467-V01 CVE-MT1603-V01 CVE-PR1401-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-PR1400-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-PR1399-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-DR1398-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-DR1397-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-DR1396-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-DR1395-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-DR1394-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 259 Appendix D. Other Mapped Relations
Requirement ID Related Requirements CVE-DR1387-V01 CVE-DR1393-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-DR1392-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-FN1551-V01 CVE-DR1391-V01 CVE-FN1551-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-DR1390-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-DR1389-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-DR1388-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-DR1420-V01 CVE-DR1422-V01 CVE-DR1423-V01 CVE-DR1424-V01 CVE-DR1425-V01 CVE-DR1426-V01 CVE-DR1427-V01 CVE-DR1428-V01 CVE-DR1429-V01 CVE-DR1430-V01 CVE-DR1431-V01 CVE-DR1432-V01 CVE-DR1433-V01 CVE-DR1434-V01 CVE-DR1435-V01 CVE-DR1436-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
260 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Requirement ID Related Requirements CVE-DR1387-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1378-V01 CVE-DR1379-V01 CVE-DR1380-V01 CVE-DR1381-V01 CVE-DR1382-V01 CVE-DR1383-V01 CVE-DR1384-V01 CVE-DR1385-V01 CVE-DR1386-V01 CVE-DR1388-V01 CVE-DR1389-V01 CVE-DR1390-V01 CVE-DR1391-V01 CVE-DR1392-V01 CVE-DR1393-V01 CVE-DR1394-V01 CVE-DR1395-V01 CVE-DR1396-V01 CVE-DR1397-V01 CVE-DR1398-V01 CVE-PR1399-V01 CVE-PR1400-V01 CVE-PR1401-V01 CVE-DR1386-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-DR1385-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-DR1384-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-DR1383-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-DR1382-V01 CVE-FN1509-V01 CVE-FN1510-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 261 Appendix D. Other Mapped Relations
Requirement ID Related Requirements CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-DR1381-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-DR1380-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-DR1379-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-DR1378-V01 CVE-FN1509-V01 CVE-FN1510-V01 CVE-FN1511-V01 CVE-FN1557-V01 CVE-DR1387-V01 CVE-DR1374-V01 CVE-FN1516-V01 CVE-FN1517-V01 CVE-FN1518-V01 CVE-FN1519-V01 CVE-FN1560-V01 CVE-PR1368-V01 CVE-IF1240-V01 CVE-IF1241-V01 CVE-IF1242-V01 CVE-PR1367-V01 CVE-IF1240-V01 CVE-IF1241-V01 CVE-IF1242-V01 CVE-PR1366-V01 CVE-IF1240-V01 CVE-IF1241-V01 CVE-IF1242-V01 CVE-PR1365-V01 CVE-IF1240-V01 CVE-IF1241-V01 CVE-IF1242-V01 CVE-IF1363-V01 CVE-DR1144-V01 CVE-DR1145-V01 CVE-DR1146-V01 CVE-DR1147-V01 CVE-DR1148-V01 CVE-DR1149-V01 CVE-DR1150-V01 CVE-DR1151-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
262 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Requirement ID Related Requirements CVE-DR1152-V01 CVE-DR1153-V01 CVE-DR1154-V01 CVE-DR1155-V01 CVE-DR1156-V01 CVE-DR1157-V01 CVE-DR1158-V01 CVE-DR1159-V01 CVE-DR1160-V01 CVE-DR1161-V01 CVE-DR1162-V01 CVE-DR1163-V01 CVE-DR1164-V01 CVE-DR1165-V01 CVE-DR1166-V01 CVE-DR1167-V01 CVE-DR1168-V01 CVE-DR1169-V01 CVE-DR1170-V01 CVE-DR1171-V01 CVE-DR1172-V01 CVE-DR1173-V01 CVE-DR1174-V01 CVE-DR1175-V01 CVE-DR1176-V01 CVE-DR1177-V01 CVE-DR1178-V01 CVE-DR1179-V01 CVE-DR1181-V01 CVE-DR1182-V01 CVE-PR1183-V01 CVE-IF1361-V01 CVE-DR1144-V01 CVE-DR1145-V01 CVE-DR1146-V01 CVE-DR1147-V01 CVE-DR1148-V01 CVE-DR1149-V01 CVE-DR1150-V01 CVE-DR1151-V01 CVE-DR1152-V01 CVE-DR1153-V01 CVE-DR1154-V01 CVE-DR1155-V01 CVE-DR1156-V01 CVE-DR1157-V01 CVE-DR1158-V01 CVE-DR1159-V01 CVE-DR1160-V01 CVE-DR1161-V01 CVE-DR1162-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 263 Appendix D. Other Mapped Relations
Requirement ID Related Requirements CVE-DR1163-V01 CVE-DR1164-V01 CVE-DR1165-V01 CVE-DR1166-V01 CVE-DR1167-V01 CVE-DR1168-V01 CVE-DR1169-V01 CVE-DR1170-V01 CVE-DR1171-V01 CVE-DR1172-V01 CVE-DR1173-V01 CVE-DR1174-V01 CVE-DR1175-V01 CVE-DR1176-V01 CVE-DR1177-V01 CVE-DR1178-V01 CVE-DR1179-V01 CVE-DR1181-V01 CVE-DR1182-V01 CVE-PR1183-V01 CVE-IF1360-V01 CVE-DR1292-V01 CVE-DR1294-V01 CVE-DR1295-V01 CVE-DR1296-V01 CVE-DR1164-V01 CVE-FN1512-V01 CVE-FN1513-V01 CVE-FN1514-V01 CVE-FN1515-V01 CVE-FN1559-V01 CVE-DR1272-V01 CVE-IF1361-V01 CVE-IF1363-V01 CVE-MT1604-V01 CVE-DR1420-V01 CVE-DR1422-V01 CVE-DR1423-V01 CVE-DR1424-V01 CVE-DR1425-V01 CVE-DR1426-V01 CVE-DR1427-V01 CVE-DR1428-V01 CVE-DR1429-V01 CVE-DR1430-V01 CVE-DR1431-V01 CVE-DR1432-V01 CVE-DR1433-V01 CVE-DR1434-V01 CVE-DR1435-V01 CVE-DR1436-V01 CVE-MT1603-V01 CVE-DR1402-V01
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
264 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Requirement ID Related Requirements CVE-DR1404-V01 CVE-DR1405-V01 CVE-DR1406-V01 CVE-DR1407-V01 CVE-DR1408-V01 CVE-DR1409-V01 CVE-DR1410-V01 CVE-DR1411-V01 CVE-DR1412-V01 CVE-DR1413-V01 CVE-DR1414-V01 CVE-DR1415-V01 CVE-DR1416-V01 CVE-DR1417-V01 CVE-DR1418-V01 CVE-DR1419-V01 705 706
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 265 Appendix E. Data Matrix
707 Appendix E. Data Matrix
708 Table 26: Data Matrix contains a preliminary list of project specific data elements identified as required 709 for the proper functionality of the system. The list is not meant to be exhaustive at this time given the 710 evolutionary nature of agile projects; instead, it provides insight into where the data may be retrieved.
711 Table 26: Data Matrix
Source Translation Derived From FG Data Element System(s) Rules (ReqID)
MAP (msgIssueRevision) RSU ASN.1 CVE-MAP-DR1-v1 MsgCount data element
MAP (intersections) RSU ASN.1 CVE-MAP-DR2-v1 IntersectionGeometryList data frame (a sequence of IntersectionGeometry)
MAP IntersectionGeometry data RSU ASN.1 CVE-MAP-DR3-v1 frame under the (intersections) IntersectionGeometryList data frame
MAP (id) IntersectionReferenceID RSU ASN.1 CVE-MAP-DR4-v1 data frame under the IntersectionGeometry data frame
MAP (id) IntersectionID data RSU ASN.1 CVE-MAP-DR5-v1 element under the (id) IntersectionReferenceID data frame
MAP (revision) MsgCount data RSU ASN.1 CVE-MAP-DR6-v1 element under the IntersectionGeometry data frame
MAP (refPoint) Position3D-2 data RSU ASN.1 CVE-MAP-DR7-v1 frame under the IntersectionGeometry data frame
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
266 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Source Translation Derived From FG Data Element System(s) Rules (ReqID)
MAP (lat) Latitude data element RSU ASN.1 CVE-MAP-DR8-v1 under the (refPoint) Position3D-2 data frame
MAP (long) Longitude data RSU ASN.1 CVE-MAP-DR9-v1 element under the (refPoint) Position3D-2 data frame
MAP (laneWidth) LaneWidth data RSU ASN.1 CVE-MAP-DR10-v1 element under the IntersectionGeometry data frame
MAP LaneList data frame (a RSU ASN.1 CVE-MAP-DR11-v1 sequence of GenericLane) under the IntersectionGeometry data frame
MAP GenericLane data frame RSU ASN.1 CVE-MAP-DR12-v1 under the LaneList data frame
MAP (laneID) LaneID data RSU ASN.1 CVE-MAP-DR13-v1 element under the GenericLane data frame
MAP (maneuvers) RSU ASN.1 CVE-MAP-DR14-v1 AllowedManeuvers data element under the GenericLane data frame
MAP NodeList data frame under RSU ASN.1 CVE-MAP-DR15-v1 the GenericLane data frame
MAP (nodes) NodeSet data RSU ASN.1 CVE-MAP-DR16-v1 frame (a sequence of Node) under the NodeList data frame
MAP Node data frame under the RSU ASN.1 CVE-MAP-DR17-v1 (nodes) NodeSet data frame
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 267 Appendix E. Data Matrix
Source Translation Derived From FG Data Element System(s) Rules (ReqID)
MAP (delta) NodeOffsetPointXY RSU ASN.1 CVE-MAP-DR18-v1 data element under the Node data frame (Any representation Node-XY- 20b through Node-XY-32b)
MAP (connectsTo) RSU ASN.1 CVE-MAP-DR19-v1 ConnectsToList data frame (a sequence of Connection) under the GenericLane data frame
MAP Connection data frame RSU ASN.1 CVE-MAP-DR20-v1 under the (connectsTo) ConnectsToList data frame
MAP (connectingLane) RSU ASN.1 CVE-MAP-DR21-v1 ConnectingLane data frame under the Connection data frame
MAP (lane) LaneID data element RSU ASN.1 CVE-MAP-DR22-v1 under the (connectingLane) ConnectingLane data frame
MAP (maneuver) RSU ASN.1 CVE-MAP-DR23-v1 AllowedManeuvers data element under the (connectingLane) ConnectingLane data frame
MAP (signalGroup) RSU ASN.1 CVE-MAP-DR24-v1 SignalGroupID data element under the Connection data frame
MAP egress lanes (if included) RSU ASN.1 CVE-MAP-DR26-v1 may optionally contain a maneuvers field or a connectsTo field
MAP egress lanes (if included) RSU ASN.1 CVE-MAP-DR27-v1 may optionally contain the nodes in the NodeSet sequenced such that the first node is the stop bar
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
268 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Source Translation Derived From FG Data Element System(s) Rules (ReqID)
MAP Connection field shall RSU ASN.1 CVE-MAP-DR35-v1 contain the lane, maneuver, and signalGroup associated with the Connection. The signalGroup identifies which signal group in the SPaT controls the flow of traffic from the ingress lane to the egress lane.
MAP IntersectionGeometry RSU ASN.1 CVE-MAP-DR38-v1 revision shall be changed only if the map information was updated.
MAP laneList. Each lane in the RSU ASN.1 CVE-MAP-DR39-v1 laneList shall be identified as an ingress lane or an egress lane through the laneAttributes- >directionalUse field.
RSM school zone speed limit RSU ASN.1 CVE-RSM-DR3-v2 (J2945/4) (specific data frames/elements TBD)
RSM time periods when the RSU ASN.1 CVE-RSM-DR4-v1 school zone speed limit is active. (specific data frames/elements TBD)
RSM applicable regions of use RSU ASN.1 CVE-RSM-DR5-v1 geographical path (J2945/4). (specific data frames/elements TBD)
RTCM message type 1001 – GPS RSU ASN.1 CVE-RTCM-DR1-v1 L1 observations at 5 Hz
RTCM message type 1005 – RSU ASN.1 CVE-RTCM-DR2-v1 Antenna Reference Point (ARP) coordinates at 2 Hz
SPAT (timeStamp) RSU ASN.1 CVE-SPAT-DR1-v1 MinuteOfTheYear data element
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 269 Appendix E. Data Matrix
Source Translation Derived From FG Data Element System(s) Rules (ReqID)
SPAT (intersections) RSU ASN.1 CVE-SPAT-DR2-v1 IntersectionStateList data frame (a sequence of IntersectionState)
SPAT IntersectionState data RSU ASN.1 CVE-SPAT-DR3-v1 frame under the IntersectionStateList data frame
SPAT (id) IntersectionReferenceID RSU ASN.1 CVE-SPAT-DR4-v1 data element under the IntersectionState data frame
SPAT (revision) MsgCount data RSU ASN.1 CVE-SPAT-DR5-v1 element under the IntersectionState data frame
SPAT (status) RSU ASN.1 CVE-SPAT-DR6-v1 IntersectionStatusObject data element under the IntersectionState data frame
SPAT (timeStamp) Dsecond data RSU ASN.1 CVE-SPAT-DR7-v1 element under the IntersectionState data frame
SPAT (states) MovementList data RSU ASN.1 CVE-SPAT-DR8-v1 frame (a sequence of MovementState) under the IntersectionState data frame
SPAT MovementState data frame RSU ASN.1 CVE-SPAT-DR9-v1 under the MovementList data frame
SPAT (signalGroup) RSU ASN.1 CVE-SPAT-DR10-v1 SignalGroupID data element under the MovementState data frame
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
270 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Source Translation Derived From FG Data Element System(s) Rules (ReqID)
SPAT (state-time-speed) RSU ASN.1 CVE-SPAT-DR11-v1 MovementEventList data frame (a sequence of MovementEvent) under the MovementState data frame
SPAT MovementEvent data frame RSU ASN.1 CVE-SPAT-DR12-v1 under the MovementEventList data frame
SPAT (eventState) RSU ASN.1 CVE-SPAT-DR13-v1 MovementPhaseState data element under the MovementEvent data frame
SPAT (timing) TimeChangeDetails RSU ASN.1 CVE-SPAT-DR14-v1 data frame under the MovementEvent data frame
SPAT (minEndTime) TimeMark RSU ASN.1 CVE-SPAT-DR15-v1 data element under the TimeChangeDetails data frame
SPAT (maxEndTime) TimeMark RSU ASN.1 CVE-SPAT-DR16-v1 data element under the TimeChangeDetails data frame
SPAT (likelyTime) TimeMark data RSU ASN.1 CVE-SPAT-DR17-v1 element under the TimeChangeDetails data frame
SPAT “states” field, which is a list RSU ASN.1 CVE-SPAT-DR18-v1 of one or more MovementStates. The number of MovementStates shall correspond to the number of controller traffic phases that are currently active at the intersection.
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 271 Appendix E. Data Matrix
Source Translation Derived From FG Data Element System(s) Rules (ReqID)
SPAT signalGroup shall be RSU ASN.1 CVE-SPAT-DR19-v1 assigned number and is not necessarily based on the controller phase number
SPAT maxEndTime or likelyTime RSU ASN.1 CVE-SPAT-DR20-v2
SPAT maxEndTime if the traffic RSU ASN.1 CVE-SPAT-DR21-v1 signal controller is running fixed-time, and if transmitted shall be equal to minEndTime
SRM (second) DSecond data RSU ASN.1 CVE-SRM-DR3-v1 element
SRM (requests) RSU ASN.1 CVE-SRM-DR4-v1 SignalRequestList (sequence of SignalRequestPackage) data frame
SRM SignalRequestPackage RSU ASN.1 CVE-SRM-DR5-v1 data frame under the SignalRequestList data frame
SRM (request) SignalRequest RSU ASN.1 CVE-SRM-DR6-v1 data frame under the SignalRequestPackage data frame
SRM (id) IntersectionReferenceID RSU ASN.1 CVE-SRM-DR7-v1 data frame under the SignalRequest data frame
SRM (id) IntersectionID data RSU ASN.1 CVE-SRM-DR8-v1 element under the intersectionReferenceID data frame
SRM (requestID) RequestID data RSU ASN.1 CVE-SRM-DR9-v1 element under the SignalRequest data frame
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
272 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Source Translation Derived From FG Data Element System(s) Rules (ReqID)
SRM (requestType) RSU ASN.1 CVE-SRM-DR10-v1 PriorityRequestType data element under the SignalRequest data frame
SRM (inBoundLane) RSU ASN.1 CVE-SRM-DR11-v1 IntersectionAccessPoint data frame under the SignalRequest data frame
SRM (lane) LaneID data element RSU ASN.1 CVE-SRM-DR12-v1 under the IntersectionAccessPoint data frame
SRM (approach) ApproachID RSU ASN.1 CVE-SRM-DR13-v1 data element under the IntersectionAccessPoint data frame
SRM (connection) RSU ASN.1 CVE-SRM-DR14-v1 LaneConnectionID data element under the IntersectionAccessPoint data frame
SRM (requestor) RSU ASN.1 CVE-SRM-DR15-v1 RequestorDescription data frame
SRM (id) VehicleID data frame RSU ASN.1 CVE-SRM-DR16-v1 under the RequestroDescription data frame
SRM (entityID) TemporaryID RSU ASN.1 CVE-SRM-DR17-v1 under the VehicleID data frame
SRM (stationID) StationID under RSU ASN.1 CVE-SRM-DR18-v1 the VehicleID data frame
SSM (second) DSecond data OBU ASN.1 CVE-SSM-DR3-v1 element
SSM (status) SignalStatus data OBU ASN.1 CVE-SSM-DR4-v1 frame
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 273 Appendix E. Data Matrix
Source Translation Derived From FG Data Element System(s) Rules (ReqID)
SSM (sequence) MsgCount data OBU ASN.1 CVE-SSM-DR5-v1 element under the SignalStatus data frame
SSM (id) IntersectionReferenceID OBU ASN.1 CVE-SSM-DR6-v1 data element under the SignalStatus data frame
SSM (sigStatus) OBU ASN.1 CVE-SSM-DR7-v1 SignalStatusPackageList data frame (sequence of SignalStatusPackage) under the SignalStatus data frame
SSM SignalStatusPackage data OBU ASN.1 CVE-SSM-DR8-v1 frame under the SignalStatusPacakageList data frame
SSM (requestor) OBU ASN.1 CVE-SSM-DR9-v1 SignalRequestorInfo data frame under the SignalStatusPackage data frame
SSM (id) VehicleID under the OBU ASN.1 CVE-SSM-DR10-v1 SignalRequestorInfor data frame
SSM (request) RequestID under OBU ASN.1 CVE-SSM-DR11-v1 the SignalRequestorInfor data frame
SSM (sequenceNumber) OBU ASN.1 CVE-SSM-DR12-v1 MsgCount under the SignalRequestorInfor data frame
SSM (inboundOn) OBU ASN.1 CVE-SSM-DR13-v1 IntersectionAccessPoint data frame under the SignalStatusPackage data frame
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
274 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Source Translation Derived From FG Data Element System(s) Rules (ReqID)
SSM (lane) LaneID data element OBU ASN.1 CVE-SSM-DR14-v1 under the IntesectionAccessPoint data frame
SSM (approach) ApproachID OBU ASN.1 CVE-SSM-DR15-v1 data element under the IntesectionAccessPoint data frame
SSM (connection) OBU ASN.1 CVE-SSM-DR16-v1 LaneConnectionID data element under the IntesectionAccessPoint data frame
SSM (status) OBU ASN.1 CVE-SSM-DR17-v1 PrioritizationResponseStatu s data element under the SignalStatusPackage data frame
712 Source: City of Columbus
713
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 275
714 Appendix F. Requirements Verification
715 Traceability Matrix
716 The Requirements Verification Traceability Matrix (RVTM) is expected to be software generated once the 717 initial draft of system requirements has been reviewed and captured in the selected requirement 718 management tool.
719
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 277
720 Appendix G. Acronyms and Definitions
721 Table 27: Acronym List contains project specific acronyms used throughout this document.
722 Table 27: Acronym List
Abbreviation/Acronym Definition
3PL Third-Party Logistics ABS Antilock Braking System AMT Automated Manual Transmission API Application Programming Interface ASD Aftermarket Safety Device BRT Bus Rapid Transit BSM Basic Safety Message CCTN Columbus Connected Transportation Network CDP Columbus Division of Police CEAV Connected Electric Automated Vehicle (Smart Columbus Project #9) CFR Code of Federal Regulations CMAX Brand for COTA Cleveland Avenue Bus Rapid Transit CMS Collision Mitigation System ConOps Concept of Operations COTA Central Ohio Transit Authority CPS Common Payment System (Smart Columbus Project #5) CTSS Columbus Traffic Signal System CV Connected Vehicle CVE Connected Vehicle Environment (Smart Columbus Project #1) CVRIA Connected Vehicle Reference Implementation Architecture DOT (City of Columbus) Department of Technology DPS Columbus Department of Public Service DSRC Dedicated Short Range Communications DZA Delivery Zone Availability (Smart Columbus Project #10) EAV Electric Autonomous Vehicle
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 279 Appendix G. Acronyms and Definitions
Abbreviation/Acronym Definition
EPM Event Parking Management (Smart Columbus Project #12) EPP Enhanced Permit Parking (Smart Columbus Project #11) ETA Estimated Time of Arrival ETSI European Telecommunications Standards Institute EV Electric Vehicle FHWA Federal Highway Administration FSP Freight Signal Priority GHz Gigahertz GTFS General Transit Feed Specification GTFS-RT General Transit Feed Specification Real-Time ICD Interface Control Document IDE Integrated Data Exchange (Smart Columbus Project #4) IEEE Institute of Electrical and Electronics Engineers INCOSE International Council on Systems Engineering IP Internet Protocol address ISO International Organization for Standardization ISP Internet Service Provider IT Information Technology ITE Institute of Transportation Engineers ITPA Interstate Truck Parking Availability (Smart Columbus Project #15) ITS Intelligent Transportation Systems JIT Just-in-Time LED Light-Emitting Diode LTE Long-Term Evolution Mobility Assistance for People with Cognitive Disabilities (Smart Columbus MAPCD Project #8) MMITSS Multimodal Intelligent Traffic Signal System MMTPA Multimodal Trip Planning Application (Smart Columbus Project #6) MOE Measure of Effectiveness MORPC Mid-Ohio Regional Planning Commission NEMA National Electrical Manufacturers Association NIST National Institute of Standards and Technology
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
280 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Abbreviation/Acronym Definition
NOC Network Operations Center NOFO Notice of Funding Opportunity O&M Operations and Maintenance OBE On-board Equipment (many or all on-board devices) OBU On-board Unit (one on-board device) ODOT Ohio Department of Transportation OVR Oversize Vehicle Routing (Smart Columbus Project #14) PEO Parking Enforcement Officer PII Personally Identifiable Information RDE Research Data Exchange RFID Radio Frequency Identification RFQ Request for Quote ROI Return on Investment RSE Roadside Equipment RSU Roadside Unit SAE Society of Automotive Engineers SBS System Breakdown Structure SC Smart Columbus SCC Smart City Challenge SDD System Design Document SE Systems Engineering SEMP Systems Engineering Management Plan SEMS Systems Engineering Master Schedule SEP Systems Engineering Process SET-IT Systems Engineering Tool for Intelligent Transportation SMH Smart Mobility Hubs (Smart Columbus Project #7) SPaT Signal Phase and Timing SRM Signal Request Message SSL Smart Street Lighting (Smart Columbus Project #2) SSM Signal Status Message SyRS System Requirements Specification
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 281 Appendix G. Acronyms and Definitions
Abbreviation/Acronym Definition
TNC Transportation Network Company TP Truck Platooning (Smart Columbus Project #13) Transit Pedestrian Collision Avoidance System (Smart Columbus Project TPCAS #3) USDOT United States Department of Transportation V2I Vehicle-to-Infrastructure V2V Vehicle-to-Vehicle VAD Vehicle Awareness Device VRU Vulnerable Road User
723 Source: City of Columbus 724
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
282 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
725 Appendix H. Glossary
726 Table 28: Glossary contains project specific terms used throughout this document.
727 Table 28: Glossary
Term Definition
The City of Columbus Service Center which is the single point of contact for 311 Columbus Call requesting all non-emergency City services and is available to residents, City Center businesses, and visitors
A method of project management that is characterized by the division of tasks Agile into short phases of work and frequent reassessment and adaptation of plans
COTA's AirConnect is a direct service connecting travelers to/from Downtown AirConnect and the John Glenn International Airport. Service comes to designated spots every 30 minutes, 6 a.m.-9 p.m., 7 days a week.
App Software application
COTA's CBUS is the city's free Downtown Circulator, traveling from the Brewery District through Downtown to the Short North and back again. CBUS CBUS runs every 10-15 minutes, 7 days a week with the exception of special holidays.
Commercial-off-the- Software or hardware product that are ready-made and available for sale to shelf system (COTS) the public
Data Management A secure, SaaS web-based application that allows management of an entire System (DMS) parking meter network
The reasonable expectation that data of a sensitive nature will be kept Data privacy confidential, sanitized and/or encrypted, and respectfully and responsibly maintained by all users, managers, and collectors of the data
Data retention The continued storage of data for compliance or business reasons
The tools, policies, practices, and procedures used to protect data from being accessed, manipulated or destroyed or being leveraged by those with a Data security malicious intent or without authorization, as well as the corrective actions taken when data breaches are suspected or have been identified.
Dedicated Short A two-way short- to medium-range wireless communications capability that Range permits very high data transmission critical in communications-based active Communications safety applications (DSRC)
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 283 Appendix H. Glossary
Term Definition
When one Project, agency, or entity requires data or functionality provided by Dependency another Project, agency, or entity to meet its objectives
Enabling An innovation that alone or paired with an existing solution produces a better Technologies end user solution at a rapid rate
An organization whose mission is to market and promote Columbus services, Experience attractions, and facilities to visitors, meeting planners, convention delegates, Columbus and residents
When a complete failure of the intersection occurs, primarily due to loss of Failure operations power or other malfunctions
Multimodal Travel that is performed with more than one mode of transportation transportation
When a signalized intersection is cycling through its pre-planned phases Normal operations correctly, servicing all approaches, including pedestrian phases
Information that is freely available for anyone to use and republish as they Open-data wish
Open-source The notion of open collaboration and voluntary contribution for software concepts development by writing and exchanging programming code
Parking facility Land or a structure used for light-duty vehicle parking
Parking management A system intended to aggregate location, availability, payment information, system and reservation capabilities across all public and private parking options
Personally Information used in security and privacy laws that can be used to identify an Identifiable individual, such as vehicle, traveler, and payment information Information (PII)
The act of obtaining or acquiring goods, services or works, from a competitive Procurement bidding process
Commonly referred to as a QR Code. A barcode that stores information that Quick Response can be used for marketing or sharing information and can be read using a barcode digital device such as a cell phone
Real-time data Information that is delivered immediately after collection
All equipment located on the roadside, including any or all of the following Roadside equipment items: traffic signal controllers, pedestrian detection equipment, GPS receiver, a DSRC radio, a processing unit, and an audio pedestrian interface
A parking meter equipped with technology to collect data and make Smart parking meter interactions easier for the end user
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
284 | Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report
Term Definition
A device that takes input from the physical environment and uses built-in Smart sensors technology to perform functions upon detection of specific input and then process data before passing it on
System analytics or The analysis of data, procedures or business practices to locate information data analytics which can be used to create more efficient solutions
A linear and sequential product or software development model that includes Systems Engineering Conception, Initiation, Analysis, Design, Construction, Testing, (waterfall) approach Production/Implementation, and Maintenance phases
Third-party Organizations not affiliated with the Smart Columbus Program
Transportation Private businesses, non-profits, and quasi-governmental agencies that offer Network Companies one or more types of transportation for use in exchange for payment (TNCs)
The Travelers (residents and visitors) in Columbus who will be interacting with Travelers (end users) the EPM system to view, plan, reserve, and navigate to desired parking
Unified parking One system that would allow parking availability information and reservations availability and for parking lots and garages without concern for lot or garage ownership reservation system
Vehicle Data for App that uses probe data obtained from vehicles in the network to support Traffic Operations traffic operations, including incident detection and the implementation of (VDTO) localized operational strategies
728 Source: City of Columbus
729
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 285
730 Appendix I. Version History
731 Table 29: Version History
Version Number Date Author(s), Agency Summary of Changes
0.1 08/22/2018 WSP Initial Version for CoC Review
1.0 09/05/2018 City of Columbus Draft USDOT Submittal
1.1 10/24/18 City of Columbus Revised Draft (released prior to Webinar on 11/5/18)
732
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 287
733
U.S. Department of Transportation Office of the Assistant Secretary for Research and Technology Intelligent Transportation Systems Joint Program Office
Connected Vehicle Environment SyRS for Smart Columbus Demonstration Program – Draft Report | 288
U.S. Department of Transportation ITS Joint Program Office – HOIT 1200 New Jersey Avenue, SE Washington, DC 20590
Toll-Free “Help Line” 866-367-7487
www.its.dot.gov