KDOT CAV Field Equipment represents the Connected and Autonomous Vehicle (CAV) field equipment in the KDOT WAMPO area. In addition to the KDOT Traffic Operations Center (Wichita Metro), this equipment will interface to statewide CAV systems that are required for administrative, security, credentialing, or other support purposes.
| Document Number | Title | Description |
|---|
| CTI 4001 | Roadside Unit (RSU) Standard | This document establishes a non–proprietary, communications–agnostic, industry consensus Roadside Unit (RSU) Standard. An RSU is a transportation infrastructure communications device that is a part of a Cooperative Intelligent Transportation Systems (C–ITS) transportation environment. The goal of such an environment is to reduce the number of fatalities and injuries on roadways, improve mobility, and reduce environmental impacts of transportation systems. Commonly known as the Connected Vehicle (CV) environment in the United States (US), it includes both connected human–driven vehicles and connected automated vehicles (CAVs). The terms Vehicle–to–Infrastructure (V2I) and Vehicle–to–Vehicle (V2V) are used to reflect the exchanges of messages within the CV environment. The vision for this technology has expanded to include all types of travelers including pedestrians, cyclists, multimodal travelers, and other vulnerable road users (VRUs), and is referred to as Vehicle–to–Everything (V2X) technology and V2X communications. |
|---|
| ISO 21217 | Intelligent transport systems –– Communications access for land mobiles (CALM) –– Architecture | ISO 21217 describes the communications reference architecture of nodes called "ITS station units" designed for deployment in ITS communication networks. While it describes a number of ITS station elements, whether or not a particular element is implemented in an ITS station unit depends on the specific communication requirements of the implementation. It also describes the various communication modes for peer–to–peer communications over various networks between ITS communication nodes. These nodes may be ITS station units as described in the document or any other reachable nodes. ISO 21217 specifies the minimum set of normative requirements for a physical instantiation of the ITS station based on the principles of a bounded secured managed domain. |
|---|
| ITE ATC 5201 | Advanced Transportation Controller | This standard defines the functionality and performance requirements for a modern ITS controller known as an ATC. It is similar to the NEMA TS–2 standard in that it defines basic capabilities but leaves hardware choices up to the manufacturer. |
|---|
| ITE ATC 5202 | Model 2070 Controller Standard | This standard specifies the hardware for a modern, open–architecture controller for ITS applications that can run Linux and is capable of executing advanced signal controller logic, among other things. |
|---|
| ITE ATC 5301 | Intelligent Transportation System Standard Specification for Roadside Cabinets | This standard specifies the characteristics of a modern controller cabinet for the ITS industry. |
|---|
| ITE ATC 5401 | Application Programming Interface Standard for the Advanced Transportation Controller | This standard defines the application programmers' interface (API) that should be supported by an ATC, which is an open–architecture controller that can host multiple ITS applications. |
|---|
| NEMA TS 8 | Cyber and Physical Security for Intelligent Transportation Systems | This specification describes how agencies and other transportation infrastructure owner/operators should implement cyber– and physical–security for ITS. |
|---|
| NEMA TS2 | Traffic Controller Assemblies with NTCIP Requirements | This specification covers traffic signaling equipment used to facilitate and expedite the safe movement of pedestrians and vehicular traffic. |
|---|
| NEMA TS4 | Hardware Standards for Dynamic Message Signs (DMS) With NTCIP Requirements | This standard provides hardware specifications for safe, dependable, functional, and easily maintained Dynamic Message Sign (DMS) equipment. |
|---|
| NIST FIPS PUB 140–2 | Security Requirements for Cryptographic Modules | This Federal Information Processing Standard (140–2) specifies the security requirements that will be satisfied by a cryptographic module, providing four increasing, qualitative levels intended to cover a wide range of potential applications and environments. The areas covered, related to the secure design and implementation of a cryptographic module, include specification; ports and interfaces; roles, services, and authentication; finite state model; physical security; operational environment; cryptographic key management; electromagnetic interference/electromagnetic compatibility (EMI/EMC); self–tests; design assurance; and mitigation of other attacks. |
|---|