Toledo Regional ITS Architecture (2021)

US: SAE Signal Preemption - WAVE TCP

Description

This solution is used within the U.S.. It combines standards associated with US: SAE Signal Preemption with those for V–X: WAVE TCP. The US: SAE Signal Preemption standards include upper–layer standards required to implement signal preemption and priority information flows. The V–X: WAVE TCP standards include lower–layer standards that support connection–oriented vehicle–to–any communications within ~300m using the Transmission Control Protocol (TCP) over Internet Protocol version 6 (IPv6) over IEEE WAVE in the 5.9GHz spectrum.

Includes Standards

Level	DocNum	FullName	Description
Mgmt	Addressed Elsewhere	Addressed Elsewhere in Stack	The services related to this portion of the stack are defined in the other standards listed for this solution.
Security	IEEE 1609.2	IEEE Standard for Wireless Access in Vehicular Environments – Security Services for Applications and Management Messages	This standard defines secure message formats and processing for use by Wireless Access in Vehicular Environments (WAVE) devices, including methods to secure WAVE management messages and methods to secure application messages. It also describes administrative functions necessary to support the core security functions.
Security	IEEE 1609.2a	IEEE 1609.2a–2017 – IEEE Standard for Wireless Access in Vehicular Environments––Security Services for Applications and Management Messages – Amendment 1	This standard defines secure message formats and processing for use by Wireless Access in Vehicular Environments (WAVE) devices, including methods to secure WAVE management messages and methods to secure application messages. It also describes administrative functions necessary to support the core security functions.
Security	IEEE 1609.2b	IEEE Standard for Wireless Access in Vehicular Environments––Security Services for Applications and Management Messages – Amendment 2––PDU Functional Types and Encryption Key Management	This standard defines secure message formats and processing for use by Wireless Access in Vehicular Environments (WAVE) devices, including methods to secure WAVE management messages and methods to secure application messages. It also describes administrative functions necessary to support the core security functions.
ITS Application Entity	CEN ISO 19091	Intelligent transport systems –– Cooperative ITS –– Using V2I and I2V communications for applications related to signalized intersections	This technical specification defines messages and related data structures and data elements for the following exchanges between roadside equipment and vehicles: 1) Definition of the SPaT (signal phase and timing) message transmitted from a traffic controller that describes the state of the signals, signal timing as necessary to support the applications identified herein; 2) definition of the MAP message (which include the definition of motorized lane, vehicles, busses, trams, bicycle, pedestrian crosswalks, etc.); and 3) definition of the messages (SRM, SSM) to be exchanged between an intersection traffic controller and approaching vehicles to support priority treatment as might be expected for emergency response , freight transport, and public transport vehicles to improve safety.
ITS Application Entity	SAE J2735	Dedicated Short Range Communications (DSRC) Message Set Dictionary (TM)	This standard defines the data and messages for use in DSRC (i.e., V2V, V2I, and V2D) applications. The SAE J2945 series defines additional requirements on how to use these messages.
ITS Application Entity	SAE J2945/B	Recommended Practices for Signalized Intersection Applications	This document provides guidance on usage of SAE J2735 and other related information for signalized intersection applications. The document focuses on how to use SPaT and MAP messages to support signalized–intersection applications. In general, implementation guidance is necessary to achieve interoperability by addressing the requirements for the options for both over the air dialogs and message contents, and to support larger intersection maps This document also addresses using Signal Request & Signal Status messages corresponding to vehicle functionality and approaches to traffic signal priority/pre–emption (TSP), including three different methods for implementing TSP over the air. The project is complementary to the connected intersections project being performed by ITE.
Facilities	SAE J2735	Dedicated Short Range Communications (DSRC) Message Set Dictionary (TM)	This standard defines the data and messages for use in DSRC (i.e., V2V, V2I, and V2D) applications. The SAE J2945 series defines additional requirements on how to use these messages.
Facilities	SAE J2945	Dedicated Short Range Communication (DSRC) Systems Engineering Process Guidance for J2945/x Documents and Common Design Concepts	This standard defines cross–cutting material which applies to the J2945/x series including generic DSRC interface requirements and guidance on Systems Engineering (SE) content.
TransNet	IETF RFC 2460	Internet Protocol, Version 6 (IPv6) Specification	This standard (RFC) specifies version 6 of the Internet Protocol (IPv6), also sometimes referred to as IP Next Generation or IPng.
TransNet	IETF RFC 4291	IP Version 6 Addressing Architecture	This 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.
TransNet	IETF RFC 4861	Neighbor Discovery for IP version 6 (IPv6)	This standard (RFC) specifies the Neighbor Discovery protocol for IP Version 6. IPv6 nodes on the same link use Neighbor Discovery to discover each other's presence, to determine each other's link–layer addresses, to find routers, and to maintain reachability information about the paths to active neighbors.
TransNet	IETF RFC 4862	IPv6 Stateless Address Autoconfiguration	This standard (RFC) specifies the steps a host takes in deciding how to autoconfigure its interfaces in IP version 6. The autoconfiguration process includes generating a link–local address, generating global addresses via stateless address autoconfiguration, and the Duplicate Address Detection procedure to verify the uniqueness of the addresses on a link.
TransNet	IETF RFC 793	Transmission Control Protocol	This standard (RFC) defines the main connection–oriented Transport Layer protocol used on Internet–based networks.
TransNet	IEEE 1609.3	IEEE Standard for Wireless Access in Vehicular Environments (WAVE) – Networking Services	This standard defines the network and transport layer options for the WAVE environment. The standard defines three options: a bandwidth efficient single–hop solution known as WSMP, UDP/IP, and TCP/IP. It has been harmonized with ISO FNTP and FSAP – a common message format specified in ISO 16460.
Access	IEEE 1609.4	IEEE Draft Standard for Wireless Access in Vehicular Environments – Multi–Channel Operation	This standard primarily defines the data link layer of the WAVE communications stack.
Access	IEEE 802.11	IEEE Draft Standard for Information technology––Telecommunications and information exchange between systems Local and metropolitan area networks––Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specificatio	This standard defines the physical and data link layers for wireless Ethernet, including WiFi and DSRC.
Access	ISO/IEC 8802–2	IEEE Standard for Information technology –– Telecommunications and information exchange between systems––Local and metropolitan area networks –– Specific requirements –– Part 2: Logical Link Control	ISO/IEC 8802–2 describes the logical link control (LLC) sublayer, which constitutes the top sublayer in the data link layer of the ISO 8802 Local Area Network Protocol (also known as IEEE 802.2).

Readiness: Moderate

Readiness Description

Two significant or one significant and several minor issues. For existing deployments, the chosen solution is likely deficient in security or management capabilities and the issues should be reviewed and upgrades developed as needed. For new deployments, the solution may be viable for pilots when applied to the triples it supports; such pilot deployments should consider a path to addressing these issues as a part of their design activities. The solution does not provide sufficient interoperability, management, and security to enable proper, full–scale deployment without additional work.

Issues

Issue	Severity	Description	Associated Standard	Associated Triple
Overlap of standards	Medium	Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow.	Bundle: WAVE – Subnet	(All)
Uncertainty about trust revocation mechanism	Medium	The mechanisms used to prevent bad actors from sending authorized messages is unproven.	Bundle: IEEE 1609.2	(All)
Data not defined in standard format	Low	The definition of data concepts should conform to ISO 14817–1 to promote reuse among ITS.	SAE J2735 DSRC Message Set	(All)
Guidance document under development	Low	This recommended practice on how to use the related standards is still under development but is not seen as strictly necessary to begin deployment of equipment.	SAE J2945/B Signal Intersection Applications	(All)
Not a standard (minor)	Low	The document is publicly available and widely used but it is not currently a formal standard.	ISO 19091 V2I for signalized intersections	(All)

Supports Interfaces

Source	Destination	Flow
Bowling Green State University Shuttle Vehicles	City of Bowling Green ITS Field Devices	local signal priority request
Bowling Green State University Shuttle Vehicles	ODOT Connected Vehicles Roadside Equipment	local signal priority request
Bowling Green Transit Vehicles	City of Bowling Green ITS Field Devices	local signal priority request
Bowling Green Transit Vehicles	County and City Connected Vehicles Roadside Equipment	local signal priority request
Bowling Green Transit Vehicles	ODOT Connected Vehicles Roadside Equipment	local signal priority request
Bowling Green Transit Vehicles	ODOT District 2 Traffic Signal Roadway Equipment	local signal priority request
City of Bowling Green Emergency Vehicles	City of Bowling Green ITS Field Devices	local signal preemption request
City of Bowling Green Emergency Vehicles	County and City Connected Vehicles Roadside Equipment	local signal preemption request
City of Bowling Green Emergency Vehicles	ODOT Connected Vehicles Roadside Equipment	local signal preemption request
City of Toledo Emergency Vehicles	City of Toledo ITS Field Devices	local signal preemption request
City of Toledo Emergency Vehicles	County and City Connected Vehicles Roadside Equipment	local signal preemption request
City of Toledo Emergency Vehicles	ODOT Connected Vehicles Roadside Equipment	local signal preemption request
Commercial Vehicles	County and City Connected Vehicles Roadside Equipment	local signal priority request
Commercial Vehicles	ODOT Connected Vehicles Roadside Equipment	local signal priority request
County and City Connected Vehicles Roadside Equipment	Bowling Green Transit Vehicles	signal priority status
County and City Connected Vehicles Roadside Equipment	City of Bowling Green Emergency Vehicles	signal priority status
County and City Connected Vehicles Roadside Equipment	City of Toledo Emergency Vehicles	signal priority status
County and City Connected Vehicles Roadside Equipment	Commercial Vehicles	signal priority status
County and City Connected Vehicles Roadside Equipment	Lucas County EMS Vehicles	signal priority status
County and City Connected Vehicles Roadside Equipment	Lucas County Fire Vehicles	signal priority status
County and City Connected Vehicles Roadside Equipment	Lucas County Sheriff Vehicles	signal priority status
County and City Connected Vehicles Roadside Equipment	Municipal Emergency Vehicles	signal priority status
County and City Connected Vehicles Roadside Equipment	Wood County Emergency Vehicles	signal priority status
Lucas County EMS Vehicles	County and City Connected Vehicles Roadside Equipment	local signal preemption request
Lucas County EMS Vehicles	Lucas County ITS Field Devices	local signal preemption request
Lucas County EMS Vehicles	ODOT Connected Vehicles Roadside Equipment	local signal preemption request
Lucas County Fire Vehicles	County and City Connected Vehicles Roadside Equipment	local signal preemption request
Lucas County Fire Vehicles	Lucas County ITS Field Devices	local signal preemption request
Lucas County Fire Vehicles	ODOT Connected Vehicles Roadside Equipment	local signal preemption request
Lucas County Sheriff Vehicles	County and City Connected Vehicles Roadside Equipment	local signal preemption request
Lucas County Sheriff Vehicles	ODOT Connected Vehicles Roadside Equipment	local signal preemption request
Monroe County Sheriff Vehicles	Lucas County ITS Field Devices	local signal preemption request
Municipal Emergency Vehicles	County and City Connected Vehicles Roadside Equipment	local signal preemption request
Municipal Emergency Vehicles	ODOT Connected Vehicles Roadside Equipment	local signal preemption request
ODOT Connected Vehicles Roadside Equipment	Bowling Green State University Shuttle Vehicles	signal priority status
ODOT Connected Vehicles Roadside Equipment	Bowling Green Transit Vehicles	signal priority status
ODOT Connected Vehicles Roadside Equipment	City of Bowling Green Emergency Vehicles	signal priority status
ODOT Connected Vehicles Roadside Equipment	City of Toledo Emergency Vehicles	signal priority status
ODOT Connected Vehicles Roadside Equipment	Commercial Vehicles	signal priority status
ODOT Connected Vehicles Roadside Equipment	Lucas County EMS Vehicles	signal priority status
ODOT Connected Vehicles Roadside Equipment	Lucas County Fire Vehicles	signal priority status
ODOT Connected Vehicles Roadside Equipment	Lucas County Sheriff Vehicles	signal priority status
ODOT Connected Vehicles Roadside Equipment	Municipal Emergency Vehicles	signal priority status
ODOT Connected Vehicles Roadside Equipment	OSHP District 1 and 2 Vehicles	signal priority status
ODOT Connected Vehicles Roadside Equipment	OSHP District 10 Vehicles	signal priority status
ODOT Connected Vehicles Roadside Equipment	TARPS Paratransit Vehicles	signal priority status
ODOT Connected Vehicles Roadside Equipment	TARTA Fixed Route Vehicles	signal priority status
ODOT Connected Vehicles Roadside Equipment	Wood County Emergency Vehicles	signal priority status
OSHP District 1 and 2 Vehicles	ODOT Connected Vehicles Roadside Equipment	local signal preemption request
OSHP District 1 and 2 Vehicles	ODOT District 2 Traffic Signal Roadway Equipment	local signal preemption request
OSHP District 10 Vehicles	ODOT Connected Vehicles Roadside Equipment	local signal preemption request
OSHP District 10 Vehicles	ODOT District 2 Traffic Signal Roadway Equipment	local signal preemption request
TARPS Paratransit Vehicles	City of Toledo ITS Field Devices	local signal priority request
TARPS Paratransit Vehicles	Lucas County ITS Field Devices	local signal priority request
TARPS Paratransit Vehicles	Municipal ITS Field Devices	local signal priority request
TARPS Paratransit Vehicles	ODOT Connected Vehicles Roadside Equipment	local signal priority request
TARPS Paratransit Vehicles	ODOT District 2 Traffic Signal Roadway Equipment	local signal priority request
TARTA Fixed Route Vehicles	City of Toledo ITS Field Devices	local signal priority request
TARTA Fixed Route Vehicles	Lucas County ITS Field Devices	local signal priority request
TARTA Fixed Route Vehicles	Municipal ITS Field Devices	local signal priority request
TARTA Fixed Route Vehicles	ODOT Connected Vehicles Roadside Equipment	local signal priority request
TARTA Fixed Route Vehicles	ODOT District 2 Traffic Signal Roadway Equipment	local signal priority request
Wood County Emergency Vehicles	County and City Connected Vehicles Roadside Equipment	local signal preemption request
Wood County Emergency Vehicles	ODOT Connected Vehicles Roadside Equipment	local signal preemption request