US: NTCIP Transportation Sensors - SNMPv3/TLS

Description

This solution is used within the U.S.. It combines standards associated with US: NTCIP Transportation Sensors with those for I–F: SNMPv3/TLS. The US: NTCIP Transportation Sensors standards include upper–layer standards required to implement center–to–field transportation sensors (e.g., vehicle detectors) communications (e.g., real–time). The I–F: SNMPv3/TLS standards include lower–layer standards that support secure center–to–field and field–to–field communications using simple network management protocol (SNMPv3); implementations are strongly encouraged to use the TLS for SNMP security option for this solution to ensure adequate security.

Includes Standards

LevelDocNumFullNameDescription
MgmtNTCIP 1201NTCIP Global Object (GO) DefinitionsThis standard defines SNMP objects (data elements) used by a wide range of field devices like time and versioning information.
MgmtIETF RFC 3411An Architecture for Describing Simple Network Management Protocol (SNMP) Management FrameworksThis standard (RFC) defines the basic architecture for SNMPv3 and includes the definition of information objects for managing the SNMP entity's architecture.
MgmtIETF RFC 3412Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)This standard (RFC) contains a MIB that assists in managing the message processing and dispatching subsystem of an SNMP entity.
MgmtIETF RFC 3413Simple Network Management Protocol (SNMP) ApplicationsThis standard (RFC) includes MIBs that allow for the configuration and management of remote Targets, Notifications, and Proxys.
MgmtIETF RFC 3414User–based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)This standard (RFC) contains a MIB that assists in configuring and managing the user–based security model.
MgmtIETF RFC 3415View–based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)This standard (RFC) contains a MIB that supports the configuration and management of the View–based access control model of SNMP.
MgmtIETF RFC 3416Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP)This standard (RFC) defines the message structure and protocol operations used by SNMPv3.
MgmtIETF RFC 3418Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)This standard (RFC) defines the MIB to configure and manage an SNMP entity.
MgmtIETF RFC 4293Management Information Base for the Internet Protocol (IP)This standard (RFC) defines the MIB that manages an IP entity.
SecurityIETF RFC 6353Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)This standard (RFC) defines how to use the TLS authentication service to provide authentication within the access control mechanism of SNMP.
ITS Application EntityNTCIP 1209NTCIP Object Definitions for Transportation Sensor Systems (TSS)This standard defines SNMP objects (data elements) to monitor and control transportation system sensors that measure real–time vehicular traffic information.
FacilitiesNTCIP 1209NTCIP Object Definitions for Transportation Sensor Systems (TSS)This standard defines SNMP objects (data elements) to monitor and control transportation system sensors that measure real–time vehicular traffic information.
FacilitiesIETF RFC 3411An Architecture for Describing Simple Network Management Protocol (SNMP) Management FrameworksThis standard (RFC) defines the basic architecture for SNMPv3 and includes the definition of information objects for managing the SNMP entity's architecture.
FacilitiesIETF RFC 3412Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)This standard (RFC) contains a MIB that assists in managing the message processing and dispatching subsystem of an SNMP entity.
FacilitiesIETF RFC 3413Simple Network Management Protocol (SNMP) ApplicationsThis standard (RFC) includes MIBs that allow for the configuration and management of remote Targets, Notifications, and Proxys.
FacilitiesIETF RFC 3414User–based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)This standard (RFC) contains a MIB that assists in configuring and managing the user–based security model.
FacilitiesIETF RFC 3415View–based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)This standard (RFC) contains a MIB that supports the configuration and management of the View–based access control model of SNMP.
FacilitiesIETF RFC 3416Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP)This standard (RFC) defines the message structure and protocol operations used by SNMPv3.
TransNetIETF RFC 4291IP Version 6 Addressing ArchitectureThis standard (RFC) defines the addressing architecture of the IP Version 6 (IPv6) protocol. It includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses.
TransNetIETF RFC 4443Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) SpecificationThis standard (RFC) defines the control messages to manage IPv6.
TransNetIETF RFC 8200Internet Protocol, Version 6This document specifies version 6 of the Internet Protocol (IPv6).
TransNetIETF RFC 9293Transmission Control ProtocolThis document specifies the Transmission Control Protocol (TCP). TCP is an important transport–layer protocol in the Internet protocol stack, and it has continuously evolved over decades of use and growth of the Internet. Over this time, a number of changes have been made to TCP as it was specified in RFC 793, though these have only been documented in a piecemeal fashion. This document collects and brings those changes together with the protocol specification from RFC 793. This document obsoletes RFC 793, as well as RFCs 879, 2873, 6093, 6429, 6528, and 6691 that updated parts of RFC 793. It updates RFCs 1011 and 1122, and it should be considered as a replacement for the portions of those documents dealing with TCP requirements. It also updates RFC 5961 by adding a small clarification in reset handling while in the SYN–RECEIVED state. The TCP header control bits from RFC 793 have also been updated based on RFC 3168.
AccessNTCIP 2104NTCIP SP–EthernetThis standard defines the Access Layer for center–to–field communications where the local connection is some variant of Ethernet.

Readiness: High–Moderate

Readiness Description

One significant or possibly a couple minor issues. For existing deployments, the chosen solution likely has identified security or management issues not addressed by the communications solution. Deployers should consider additional security measures, such as communications link and physical security as part of these solutions. They should also review the management issues to see if they are relevant to their deployment and would require mitigation. For new deployments, the deployment efforts should consider a path to addressing these issues as a part of their design activities. The solution does not by itself provide a fully secure implementation without additional work.

Issues

IssueSeverityDescriptionAssociated StandardAssociated Triple
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)TDOT Connected Vehicle Roadside Equipment=>traffic situation data=>TDOT Changeable Speed Limit Signs
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Millington Connected Vehicle Roadside Equipment=>traffic situation data=>City of Millington Traffic Signals
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Millington Connected Vehicle Roadside Equipment=>traffic situation data=>Shelby County Health Department Emissions Sensors
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Olive Branch Connected Vehicle Roadside Equipment=>traffic situation data=>City of Olive Branch TOC
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Olive Branch Connected Vehicle Roadside Equipment=>traffic situation data=>City of Olive Branch Field Sensors
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Olive Branch Connected Vehicle Roadside Equipment=>traffic situation data=>City of Olive Branch Traffic Signals
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)Municipal Connected Vehicle Roadside Equipment=>traffic situation data=>Municipal TOC
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)Municipal Connected Vehicle Roadside Equipment=>traffic situation data=>Municipal Field Sensors
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)Municipal Connected Vehicle Roadside Equipment=>traffic situation data=>Municipal Traffic Signals
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)TDOT Connected Vehicle Roadside Equipment=>traffic situation data=>TDOT Region 4 TMC – Memphis
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)TDOT Connected Vehicle Roadside Equipment=>traffic situation data=>TDOT Field Sensors
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)TDOT Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis TOC
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)TDOT Connected Vehicle Roadside Equipment=>traffic situation data=>TDOT Ramp Metering Equipment
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Millington Connected Vehicle Roadside Equipment=>traffic situation data=>City of Millington TOC
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)TDOT Connected Vehicle Roadside Equipment=>traffic situation data=>Shelby County Health Department Emissions Sensors
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Millington Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis TOC
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)TDOT Connected Vehicle Roadside Equipment=>traffic situation data=>TDOT Ramp Queue Detection System
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)Town of Collierville Connected Vehicle Roadside Equipment=>traffic situation data=>Town of Collierville TOC
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)Town of Collierville Connected Vehicle Roadside Equipment=>traffic situation data=>Town of Collierville Field Sensors
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)Town of Collierville Connected Vehicle Roadside Equipment=>traffic situation data=>Town of Collierville Traffic Signals
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)Town of Collierville Connected Vehicle Roadside Equipment=>traffic situation data=>Shelby County Health Department Emissions Sensors
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Southaven Connected Vehicle Roadside Equipment=>traffic situation data=>City of Southaven Traffic Signals
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Southaven Connected Vehicle Roadside Equipment=>traffic situation data=>CIty of Southaven TOC
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Southaven Connected Vehicle Roadside Equipment=>traffic situation data=>City of Southaven Field Sensors
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)Shelby County Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis TOC
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)Shelby County Connected Vehicle Roadside Equipment=>traffic situation data=>Shelby County TOC
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)Shelby County Connected Vehicle Roadside Equipment=>traffic situation data=>Shelby County Traffic Signals
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)Shelby County Connected Vehicle Roadside Equipment=>traffic situation data=>Shelby County Health Department Emissions Sensors
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)TDOT Connected Vehicle Roadside Equipment=>traffic situation data=>TDOT DMS
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Bartlett Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis TOC
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Memphis Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis TOC
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Memphis Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis Field Sensors
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Memphis Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis Traffic Signals
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Memphis Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis DMS
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Memphis Connected Vehicle Roadside Equipment=>traffic situation data=>Shelby County Health Department Emissions Sensors
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Memphis Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis Changeable Speed Limit Signs
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Memphis Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis Variable LED Streetlights
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)MDOT Connected Vehicle Roadside Equipment=>traffic situation data=>MDOT Northwest Regional TMC
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)MDOT Connected Vehicle Roadside Equipment=>traffic situation data=>MDOT Field Sensors
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)MDOT Connected Vehicle Roadside Equipment=>traffic situation data=>MDOT Traffic Signals
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)MDOT Connected Vehicle Roadside Equipment=>traffic situation data=>MDOT DMS
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)MDOT Connected Vehicle Roadside Equipment=>traffic situation data=>MDOT Portable DMS
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Millington Connected Vehicle Roadside Equipment=>traffic situation data=>City of Millington Field Sensors
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)MDOT Connected Vehicle Roadside Equipment=>traffic situation data=>MDOT Ramp Queue Detection System
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)Shelby County Connected Vehicle Roadside Equipment=>traffic situation data=>Shelby County Field Sensors
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Bartlett Connected Vehicle Roadside Equipment=>traffic situation data=>City of Bartlett TOC
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Bartlett Connected Vehicle Roadside Equipment=>traffic situation data=>City of Bartlett Field Sensors
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Bartlett Connected Vehicle Roadside Equipment=>traffic situation data=>City of Bartlett Traffic Signals
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Bartlett Connected Vehicle Roadside Equipment=>traffic situation data=>Shelby County Health Department Emissions Sensors
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Germantown Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis TOC
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Germantown Connected Vehicle Roadside Equipment=>traffic situation data=>City of Germantown TOC
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Germantown Connected Vehicle Roadside Equipment=>traffic situation data=>City of Germantown Field Sensors
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Germantown Connected Vehicle Roadside Equipment=>traffic situation data=>City of Germantown Traffic Signals
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Germantown Connected Vehicle Roadside Equipment=>traffic situation data=>Shelby County Health Department Emissions Sensors
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Horn Lake Connected Vehicle Roadside Equipment=>traffic situation data=>City of Horn Lake TOC
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Horn Lake Connected Vehicle Roadside Equipment=>traffic situation data=>City of Horn Lake Traffic Signals
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)City of Horn Lake Connected Vehicle Roadside Equipment=>traffic situation data=>City of Horn Lake Field Sensors
Data not fully defined (medium)MediumSome of the data elements for this information flow are not fully defined.(None)MDOT Connected Vehicle Roadside Equipment=>traffic situation data=>MDOT Changeable Speed Limit Signs
Out of date (medium)MediumThe standard includes normative references to other standards that have been subject to significant changes that can impact interoperability or security of systems and the industry has not specified if and how these updates should be implemented for deployments of this standard.IETF RFC 6353 TLS for SNMP(All)
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)TDOT Connected Vehicle Roadside Equipment=>traffic situation data=>TDOT Ramp Queue Detection System
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Memphis Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis TOC
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Olive Branch Connected Vehicle Roadside Equipment=>traffic situation data=>City of Olive Branch TOC
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Olive Branch Connected Vehicle Roadside Equipment=>traffic situation data=>City of Olive Branch Field Sensors
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Olive Branch Connected Vehicle Roadside Equipment=>traffic situation data=>City of Olive Branch Traffic Signals
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)Municipal Connected Vehicle Roadside Equipment=>traffic situation data=>Municipal TOC
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)Municipal Connected Vehicle Roadside Equipment=>traffic situation data=>Municipal Field Sensors
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)Municipal Connected Vehicle Roadside Equipment=>traffic situation data=>Municipal Traffic Signals
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)TDOT Connected Vehicle Roadside Equipment=>traffic situation data=>TDOT Region 4 TMC – Memphis
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)TDOT Connected Vehicle Roadside Equipment=>traffic situation data=>TDOT Field Sensors
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)TDOT Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis TOC
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)TDOT Connected Vehicle Roadside Equipment=>traffic situation data=>TDOT Ramp Metering Equipment
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)TDOT Connected Vehicle Roadside Equipment=>traffic situation data=>TDOT DMS
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Millington Connected Vehicle Roadside Equipment=>traffic situation data=>City of Millington Traffic Signals
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)TDOT Connected Vehicle Roadside Equipment=>traffic situation data=>TDOT Changeable Speed Limit Signs
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Millington Connected Vehicle Roadside Equipment=>traffic situation data=>City of Millington Field Sensors
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)Town of Collierville Connected Vehicle Roadside Equipment=>traffic situation data=>Town of Collierville TOC
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)Town of Collierville Connected Vehicle Roadside Equipment=>traffic situation data=>Town of Collierville Field Sensors
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)Town of Collierville Connected Vehicle Roadside Equipment=>traffic situation data=>Town of Collierville Traffic Signals
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)Town of Collierville Connected Vehicle Roadside Equipment=>traffic situation data=>Shelby County Health Department Emissions Sensors
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Southaven Connected Vehicle Roadside Equipment=>traffic situation data=>City of Southaven Traffic Signals
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Southaven Connected Vehicle Roadside Equipment=>traffic situation data=>CIty of Southaven TOC
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Southaven Connected Vehicle Roadside Equipment=>traffic situation data=>City of Southaven Field Sensors
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)Shelby County Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis TOC
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)Shelby County Connected Vehicle Roadside Equipment=>traffic situation data=>Shelby County TOC
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)Shelby County Connected Vehicle Roadside Equipment=>traffic situation data=>Shelby County Traffic Signals
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)Shelby County Connected Vehicle Roadside Equipment=>traffic situation data=>Shelby County Health Department Emissions Sensors
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)Shelby County Connected Vehicle Roadside Equipment=>traffic situation data=>Shelby County Field Sensors
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)TDOT Connected Vehicle Roadside Equipment=>traffic situation data=>Shelby County Health Department Emissions Sensors
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Bartlett Connected Vehicle Roadside Equipment=>traffic situation data=>City of Bartlett TOC
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Memphis Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis Traffic Signals
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Memphis Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis DMS
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Memphis Connected Vehicle Roadside Equipment=>traffic situation data=>Shelby County Health Department Emissions Sensors
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Memphis Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis Changeable Speed Limit Signs
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Memphis Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis Variable LED Streetlights
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)MDOT Connected Vehicle Roadside Equipment=>traffic situation data=>MDOT Northwest Regional TMC
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)MDOT Connected Vehicle Roadside Equipment=>traffic situation data=>MDOT Field Sensors
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)MDOT Connected Vehicle Roadside Equipment=>traffic situation data=>MDOT Traffic Signals
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)MDOT Connected Vehicle Roadside Equipment=>traffic situation data=>MDOT DMS
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)MDOT Connected Vehicle Roadside Equipment=>traffic situation data=>MDOT Portable DMS
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)MDOT Connected Vehicle Roadside Equipment=>traffic situation data=>MDOT Changeable Speed Limit Signs
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Millington Connected Vehicle Roadside Equipment=>traffic situation data=>Shelby County Health Department Emissions Sensors
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Bartlett Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis TOC
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Germantown Connected Vehicle Roadside Equipment=>traffic situation data=>City of Germantown Traffic Signals
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Millington Connected Vehicle Roadside Equipment=>traffic situation data=>City of Millington TOC
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Millington Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis TOC
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Horn Lake Connected Vehicle Roadside Equipment=>traffic situation data=>City of Horn Lake Field Sensors
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Horn Lake Connected Vehicle Roadside Equipment=>traffic situation data=>City of Horn Lake Traffic Signals
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)MDOT Connected Vehicle Roadside Equipment=>traffic situation data=>MDOT Ramp Queue Detection System
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Germantown Connected Vehicle Roadside Equipment=>traffic situation data=>Shelby County Health Department Emissions Sensors
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Memphis Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis Field Sensors
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Germantown Connected Vehicle Roadside Equipment=>traffic situation data=>City of Germantown Field Sensors
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Germantown Connected Vehicle Roadside Equipment=>traffic situation data=>City of Germantown TOC
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Germantown Connected Vehicle Roadside Equipment=>traffic situation data=>City of Memphis TOC
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Bartlett Connected Vehicle Roadside Equipment=>traffic situation data=>Shelby County Health Department Emissions Sensors
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Bartlett Connected Vehicle Roadside Equipment=>traffic situation data=>City of Bartlett Traffic Signals
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Bartlett Connected Vehicle Roadside Equipment=>traffic situation data=>City of Bartlett Field Sensors
Use case not considered in design (medium)MediumWhile the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort.(None)City of Horn Lake Connected Vehicle Roadside Equipment=>traffic situation data=>City of Horn Lake TOC
Update data to SNMPv3LowData has been defined for SNMPv1, but needs to be updated to SNMPv3 format.(None)(All)
Use TLS for SNMP OptionLowThe standard allows for multiple security mechanisms. The only defined mechanism that meets the requirements for C–ITS is the one based on TLS.(None)(All)

Supports Interfaces

SourceDestinationFlow
City of Bartlett Connected Vehicle Roadside EquipmentCity of Bartlett Field Sensorstraffic situation data
City of Bartlett Connected Vehicle Roadside EquipmentCity of Bartlett TOCtraffic situation data
City of Bartlett Connected Vehicle Roadside EquipmentCity of Bartlett Traffic Signalstraffic situation data
City of Bartlett Connected Vehicle Roadside EquipmentCity of Memphis TOCtraffic situation data
City of Bartlett Connected Vehicle Roadside EquipmentShelby County Health Department Emissions Sensorstraffic situation data
City of Bartlett Field SensorsCity of Bartlett TOCtraffic detector data
City of Bartlett TOCCity of Bartlett Field Sensorstraffic detector control
City of Bartlett TOCCity of Bartlett Traffic Signalstraffic detector control
City of Bartlett Traffic SignalsCity of Bartlett Rail Notification Systemtraffic detector coordination
City of Bartlett Traffic SignalsCity of Bartlett TOCtraffic detector data
City of Bartlett Traffic SignalsCity of Memphis TOCtraffic detector data
City of Germantown Connected Vehicle Roadside EquipmentCity of Germantown Field Sensorstraffic situation data
City of Germantown Connected Vehicle Roadside EquipmentCity of Germantown TOCtraffic situation data
City of Germantown Connected Vehicle Roadside EquipmentCity of Germantown Traffic Signalstraffic situation data
City of Germantown Connected Vehicle Roadside EquipmentCity of Memphis TOCtraffic situation data
City of Germantown Connected Vehicle Roadside EquipmentShelby County Health Department Emissions Sensorstraffic situation data
City of Germantown Field SensorsCity of Germantown TOCtraffic detector data
City of Germantown TOCCity of Germantown Field Sensorstraffic detector control
City of Germantown TOCCity of Germantown Traffic Signalstraffic detector control
City of Germantown Traffic SignalsCity of Germantown Rail Notification Systemtraffic detector coordination
City of Germantown Traffic SignalsCity of Germantown TOCtraffic detector data
City of Horn Lake Connected Vehicle Roadside EquipmentCity of Horn Lake Field Sensorstraffic situation data
City of Horn Lake Connected Vehicle Roadside EquipmentCity of Horn Lake TOCtraffic situation data
City of Horn Lake Connected Vehicle Roadside EquipmentCity of Horn Lake Traffic Signalstraffic situation data
City of Horn Lake Field SensorsCity of Horn Lake TOCtraffic detector data
City of Horn Lake TOCCity of Horn Lake Field Sensorstraffic detector control
City of Horn Lake TOCCity of Horn Lake Traffic Signalstraffic detector control
City of Horn Lake Traffic SignalsCity of Horn Lake Rail Notification Systemtraffic detector coordination
City of Horn Lake Traffic SignalsCity of Horn Lake TOCtraffic detector data
City of Memphis CCTV CamerasCity of Memphis DMStraffic detector coordination
City of Memphis CCTV CamerasCity of Memphis Dynamic Lane Assignment Signtraffic detector coordination
City of Memphis CCTV CamerasCity of Memphis Field Sensorstraffic detector coordination
City of Memphis CCTV CamerasCity of Memphis TOCtraffic detector data
City of Memphis Changeable Speed Limit SignsCity of Memphis TOCtraffic detector data
City of Memphis Connected Vehicle Roadside EquipmentCity of Memphis Changeable Speed Limit Signstraffic situation data
City of Memphis Connected Vehicle Roadside EquipmentCity of Memphis DMStraffic situation data
City of Memphis Connected Vehicle Roadside EquipmentCity of Memphis Field Sensorstraffic situation data
City of Memphis Connected Vehicle Roadside EquipmentCity of Memphis TOCtraffic situation data
City of Memphis Connected Vehicle Roadside EquipmentCity of Memphis Traffic Signalstraffic situation data
City of Memphis Connected Vehicle Roadside EquipmentCity of Memphis Variable LED Streetlightstraffic situation data
City of Memphis Connected Vehicle Roadside EquipmentShelby County Health Department Emissions Sensorstraffic situation data
City of Memphis DMSCity of Memphis CCTV Camerastraffic detector coordination
City of Memphis DMSCity of Memphis Dynamic Lane Assignment Signtraffic detector coordination
City of Memphis DMSCity of Memphis Field Sensorstraffic detector coordination
City of Memphis DMSCity of Memphis TOCtraffic detector data
City of Memphis Dynamic Lane Assignment SignCity of Memphis CCTV Camerastraffic detector coordination
City of Memphis Dynamic Lane Assignment SignCity of Memphis DMStraffic detector coordination
City of Memphis Dynamic Lane Assignment SignCity of Memphis Field Sensorstraffic detector coordination
City of Memphis Dynamic Lane Assignment SignCity of Memphis TOCtraffic detector data
City of Memphis Field SensorsCity of Memphis CCTV Camerastraffic detector coordination
City of Memphis Field SensorsCity of Memphis DMStraffic detector coordination
City of Memphis Field SensorsCity of Memphis Dynamic Lane Assignment Signtraffic detector coordination
City of Memphis Field SensorsCity of Memphis TOCtraffic detector data
City of Memphis TOCCity of Bartlett Traffic Signalstraffic detector control
City of Memphis TOCCity of Germantown Traffic Signalstraffic detector control
City of Memphis TOCCity of Memphis CCTV Camerastraffic detector control
City of Memphis TOCCity of Memphis Changeable Speed Limit Signstraffic detector control
City of Memphis TOCCity of Memphis DMStraffic detector control
City of Memphis TOCCity of Memphis Dynamic Lane Assignment Signtraffic detector control
City of Memphis TOCCity of Memphis Field Sensorstraffic detector control
City of Memphis TOCCity of Memphis Traffic Signalstraffic detector control
City of Memphis TOCCity of Memphis Variable LED Streetlightstraffic detector control
City of Memphis TOCCity of Millington Traffic Signalstraffic detector control
City of Memphis TOCShelby County Health Department Emissions Sensorstraffic detector control
City of Memphis TOCShelby County Traffic Signalstraffic detector control
City of Memphis TOCTown of Collierville Traffic Signalstraffic detector control
City of Memphis Traffic SignalsCity of Memphis Rail Notification Systemtraffic detector coordination
City of Memphis Traffic SignalsCity of Memphis TOCtraffic detector data
City of Memphis Variable LED StreetlightsCity of Memphis TOCtraffic detector data
City of Millington Connected Vehicle Roadside EquipmentCity of Memphis TOCtraffic situation data
City of Millington Connected Vehicle Roadside EquipmentCity of Millington Field Sensorstraffic situation data
City of Millington Connected Vehicle Roadside EquipmentCity of Millington TOCtraffic situation data
City of Millington Connected Vehicle Roadside EquipmentCity of Millington Traffic Signalstraffic situation data
City of Millington Connected Vehicle Roadside EquipmentShelby County Health Department Emissions Sensorstraffic situation data
City of Millington Field SensorsCity of Millington TOCtraffic detector data
City of Millington TOCCity of Millington Field Sensorstraffic detector control
City of Millington TOCCity of Millington Traffic Signalstraffic detector control
City of Millington Traffic SignalsCity of Memphis TOCtraffic detector data
City of Millington Traffic SignalsCity of Millington Rail Notification Systemtraffic detector coordination
City of Millington Traffic SignalsCity of Millington TOCtraffic detector data
City of Olive Branch Connected Vehicle Roadside EquipmentCity of Olive Branch Field Sensorstraffic situation data
City of Olive Branch Connected Vehicle Roadside EquipmentCity of Olive Branch TOCtraffic situation data
City of Olive Branch Connected Vehicle Roadside EquipmentCity of Olive Branch Traffic Signalstraffic situation data
City of Olive Branch Field SensorsCity of Olive Branch TOCtraffic detector data
City of Olive Branch TOCCity of Olive Branch Field Sensorstraffic detector control
City of Olive Branch TOCCity of Olive Branch Traffic Signalstraffic detector control
City of Olive Branch Traffic SignalsCity of Olive Branch Rail Notification Systemtraffic detector coordination
City of Olive Branch Traffic SignalsCity of Olive Branch TOCtraffic detector data
City of Southaven Connected Vehicle Roadside EquipmentCity of Southaven Field Sensorstraffic situation data
City of Southaven Connected Vehicle Roadside EquipmentCIty of Southaven TOCtraffic situation data
City of Southaven Connected Vehicle Roadside EquipmentCity of Southaven Traffic Signalstraffic situation data
City of Southaven Field SensorsCIty of Southaven TOCtraffic detector data
CIty of Southaven TOCCity of Southaven Field Sensorstraffic detector control
CIty of Southaven TOCCity of Southaven Traffic Signalstraffic detector control
City of Southaven Traffic SignalsCity of Southaven Rail Notification Systemtraffic detector coordination
City of Southaven Traffic SignalsCIty of Southaven TOCtraffic detector data
MDOT CCTV CamerasMDOT DMStraffic detector coordination
MDOT CCTV CamerasMDOT Field Sensorstraffic detector coordination
MDOT CCTV CamerasMDOT Lane Control DMStraffic detector coordination
MDOT CCTV CamerasMDOT Northwest Regional TMCtraffic detector data
MDOT Changeable Speed Limit SignsMDOT Northwest Regional TMCtraffic detector data
MDOT Connected Vehicle Roadside EquipmentMDOT Changeable Speed Limit Signstraffic situation data
MDOT Connected Vehicle Roadside EquipmentMDOT DMStraffic situation data
MDOT Connected Vehicle Roadside EquipmentMDOT Field Sensorstraffic situation data
MDOT Connected Vehicle Roadside EquipmentMDOT Field Sensorsvehicle entries and exits
MDOT Connected Vehicle Roadside EquipmentMDOT Northwest Regional TMCtraffic situation data
MDOT Connected Vehicle Roadside EquipmentMDOT Portable DMStraffic situation data
MDOT Connected Vehicle Roadside EquipmentMDOT Ramp Queue Detection Systemtraffic situation data
MDOT Connected Vehicle Roadside EquipmentMDOT Traffic Signalstraffic situation data
MDOT DMSMDOT CCTV Camerastraffic detector coordination
MDOT DMSMDOT Field Sensorstraffic detector coordination
MDOT DMSMDOT Lane Control DMStraffic detector coordination
MDOT DMSMDOT Northwest Regional TMCtraffic detector data
MDOT Dynamic Lane Assignment SignMDOT DMStraffic detector coordination
MDOT Dynamic Lane Assignment SignMDOT Field Sensorstraffic detector coordination
MDOT Dynamic Lane Assignment SignMDOT Lane Control DMStraffic detector coordination
MDOT Field SensorsMDOT CCTV Camerastraffic detector coordination
MDOT Field SensorsMDOT Connected Vehicle Roadside Equipmentvehicle entries and exits
MDOT Field SensorsMDOT DMStraffic detector coordination
MDOT Field SensorsMDOT Lane Control DMStraffic detector coordination
MDOT Field SensorsMDOT Northwest Regional TMCtraffic detector data
MDOT Lane Control DMSMDOT CCTV Camerastraffic detector coordination
MDOT Lane Control DMSMDOT DMStraffic detector coordination
MDOT Lane Control DMSMDOT Field Sensorstraffic detector coordination
MDOT Lane Control DMSMDOT Northwest Regional TMCtraffic detector data
MDOT Northwest Regional TMCMDOT CCTV Camerastraffic detector control
MDOT Northwest Regional TMCMDOT Changeable Speed Limit Signstraffic detector control
MDOT Northwest Regional TMCMDOT DMStraffic detector control
MDOT Northwest Regional TMCMDOT Field Sensorstraffic detector control
MDOT Northwest Regional TMCMDOT Lane Control DMStraffic detector control
MDOT Northwest Regional TMCMDOT Portable DMStraffic detector control
MDOT Northwest Regional TMCMDOT Ramp Queue Detection Systemtraffic detector control
MDOT Northwest Regional TMCMDOT Traffic Signalstraffic detector control
MDOT Portable DMSMDOT Northwest Regional TMCtraffic detector data
MDOT Ramp Queue Detection SystemMDOT Northwest Regional TMCtraffic detector data
MDOT Traffic SignalsCity of Southaven Rail Notification Systemtraffic detector coordination
MDOT Traffic SignalsMDOT Northwest Regional TMCtraffic detector data
Municipal Connected Vehicle Roadside EquipmentMunicipal Field Sensorstraffic situation data
Municipal Connected Vehicle Roadside EquipmentMunicipal TOCtraffic situation data
Municipal Connected Vehicle Roadside EquipmentMunicipal Traffic Signalstraffic situation data
Municipal Field SensorsMunicipal TOCtraffic detector data
Municipal TOCMunicipal Field Sensorstraffic detector control
Municipal TOCMunicipal Traffic Signalstraffic detector control
Municipal Traffic SignalsMunicipal Rail Notification Systemtraffic detector coordination
Municipal Traffic SignalsMunicipal TOCtraffic detector data
Shelby County Connected Vehicle Roadside EquipmentCity of Memphis TOCtraffic situation data
Shelby County Connected Vehicle Roadside EquipmentShelby County Field Sensorstraffic situation data
Shelby County Connected Vehicle Roadside EquipmentShelby County Health Department Emissions Sensorstraffic situation data
Shelby County Connected Vehicle Roadside EquipmentShelby County TOCtraffic situation data
Shelby County Connected Vehicle Roadside EquipmentShelby County Traffic Signalstraffic situation data
Shelby County Field SensorsShelby County TOCtraffic detector data
Shelby County Health Department Emissions SensorsCity of Memphis TOCtraffic detector data
Shelby County TOCShelby County Field Sensorstraffic detector control
Shelby County TOCShelby County Traffic Signalstraffic detector control
Shelby County Traffic SignalsCity of Memphis TOCtraffic detector data
Shelby County Traffic SignalsShelby County TOCtraffic detector data
TDOT CCTV CamerasTDOT DMStraffic detector coordination
TDOT CCTV CamerasTDOT Field Sensorstraffic detector coordination
TDOT CCTV CamerasTDOT Lane Control DMStraffic detector coordination
TDOT CCTV CamerasTDOT Region 4 TMC – Memphistraffic detector data
TDOT Changeable Speed Limit SignsTDOT Region 4 TMC – Memphistraffic detector data
TDOT Connected Vehicle Roadside EquipmentCity of Memphis TOCtraffic situation data
TDOT Connected Vehicle Roadside EquipmentShelby County Health Department Emissions Sensorstraffic situation data
TDOT Connected Vehicle Roadside EquipmentTDOT Changeable Speed Limit Signstraffic situation data
TDOT Connected Vehicle Roadside EquipmentTDOT DMStraffic situation data
TDOT Connected Vehicle Roadside EquipmentTDOT Field Sensorstraffic situation data
TDOT Connected Vehicle Roadside EquipmentTDOT Field Sensorsvehicle entries and exits
TDOT Connected Vehicle Roadside EquipmentTDOT Ramp Metering Equipmenttraffic situation data
TDOT Connected Vehicle Roadside EquipmentTDOT Ramp Queue Detection Systemtraffic situation data
TDOT Connected Vehicle Roadside EquipmentTDOT Region 4 TMC – Memphistraffic situation data
TDOT DMSTDOT CCTV Camerastraffic detector coordination
TDOT DMSTDOT Dynamic Lane Assignment Signtraffic detector coordination
TDOT DMSTDOT Field Sensorstraffic detector coordination
TDOT DMSTDOT Lane Control DMStraffic detector coordination
TDOT DMSTDOT Region 4 TMC – Memphistraffic detector data
TDOT Dynamic Lane Assignment SignTDOT DMStraffic detector coordination
TDOT Dynamic Lane Assignment SignTDOT Field Sensorstraffic detector coordination
TDOT Dynamic Lane Assignment SignTDOT Lane Control DMStraffic detector coordination
TDOT Field SensorsTDOT CCTV Camerastraffic detector coordination
TDOT Field SensorsTDOT Connected Vehicle Roadside Equipmentvehicle entries and exits
TDOT Field SensorsTDOT DMStraffic detector coordination
TDOT Field SensorsTDOT Dynamic Lane Assignment Signtraffic detector coordination
TDOT Field SensorsTDOT Lane Control DMStraffic detector coordination
TDOT Field SensorsTDOT Region 4 TMC – Memphistraffic detector data
TDOT Lane Control DMSTDOT CCTV Camerastraffic detector coordination
TDOT Lane Control DMSTDOT DMStraffic detector coordination
TDOT Lane Control DMSTDOT Dynamic Lane Assignment Signtraffic detector coordination
TDOT Lane Control DMSTDOT Field Sensorstraffic detector coordination
TDOT Lane Control DMSTDOT Region 4 TMC – Memphistraffic detector data
TDOT Ramp Metering EquipmentTDOT Region 4 TMC – Memphistraffic detector data
TDOT Ramp Queue Detection SystemTDOT Region 4 TMC – Memphistraffic detector data
TDOT Region 4 TMC – MemphisTDOT CCTV Camerastraffic detector control
TDOT Region 4 TMC – MemphisTDOT Changeable Speed Limit Signstraffic detector control
TDOT Region 4 TMC – MemphisTDOT DMStraffic detector control
TDOT Region 4 TMC – MemphisTDOT Field Sensorstraffic detector control
TDOT Region 4 TMC – MemphisTDOT Lane Control DMStraffic detector control
TDOT Region 4 TMC – MemphisTDOT Ramp Metering Equipmenttraffic detector control
TDOT Region 4 TMC – MemphisTDOT Ramp Queue Detection Systemtraffic detector control
Town of Collierville Connected Vehicle Roadside EquipmentShelby County Health Department Emissions Sensorstraffic situation data
Town of Collierville Connected Vehicle Roadside EquipmentTown of Collierville Field Sensorstraffic situation data
Town of Collierville Connected Vehicle Roadside EquipmentTown of Collierville TOCtraffic situation data
Town of Collierville Connected Vehicle Roadside EquipmentTown of Collierville Traffic Signalstraffic situation data
Town of Collierville Field SensorsTown of Collierville TOCtraffic detector data
Town of Collierville TOCTown of Collierville Field Sensorstraffic detector control
Town of Collierville TOCTown of Collierville Traffic Signalstraffic detector control
Town of Collierville Traffic SignalsCity of Memphis TOCtraffic detector data
Town of Collierville Traffic SignalsTown of Collierville Rail Notification Systemtraffic detector coordination
Town of Collierville Traffic SignalsTown of Collierville TOCtraffic detector data