Connected Vehicle Roadside Equipment --> Traffic Management Center:
traffic situation data

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

traffic situation data (Information Flow): Current, aggregate traffic data collected from connected vehicles that can be used to supplement or replace information collected by roadside traffic detectors. It includes raw and/or processed reported vehicle speeds, counts, and other derived measures. Raw and/or filtered vehicle control events may also be included to support incident detection.

Connected Vehicle Roadside Equipment (Source Physical Object): 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices (i.e., Roadside Units (RSUs)) equipped with short range wireless (SRW) communications technology, as well as any other supporting equipment that leverage the RSU and are not described by other objects (e.g., a local roadside processor). CVRSE are used to send messages to, and receive messages from, nearby vehicles and personal devices equipped with compatible communications technology. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.

Traffic Management Center (Destination Physical Object): The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.

Included In

This Triple is in the following Service Packages:

This triple is associated with the following Functional Objects:

This Triple is described by the following Functional View Data Flows:

vehicle_traffic_data_for_center

This Triple has the following triple relationships:

Relationship	Source	Destination	Flow
Depends On	Vehicle	Connected Vehicle Roadside Equipment	vehicle location and motion
Depends On	Vehicle	Connected Vehicle Roadside Equipment	vehicle location and motion for surveillance
Depends On	Vehicle	Connected Vehicle Roadside Equipment	vehicle situation data

Communication Solutions

US: NTCIP Transportation Sensors - SNMPv3/TLS (14)
(None-Data) - Secure Internet (ITS) (43)
Data for Distribution (TBD) - Apache Kafka (44)
Data for Distribution (TBD) - OMG DDS (44)
(None-Data) - OASIS MQTT (50)
Data for Distribution (TBD) - OASIS MQTT (50)
(None-Data) - OASIS AMQP (61)
Data for Distribution (TBD) - OASIS AMQP (61)

Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

US: NTCIP Transportation Sensors - SNMPv3/TLS

Solution Description

This solution is used within Canada and 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.

ITS Application Entity NTCIP 1209			Click gap icons for more info.
Mgmt NTCIP 1201 Bundle: SNMPv3 MIB	Facilities NTCIP 1209 ISO 15784-2	Security IETF RFC 6353 IETF RFC 9456
	TransNet IP Alternatives Internet Transport Alternatives
	Access Field SubNet Alternatives

Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.

Characteristics

Characteristic	Value
Time Context	Recent
Spatial Context	Local
Acknowledgement	True
Cardinality	Unicast
Initiator	Source
Authenticable	True
Encrypt	True

Interoperability	Description
Local	In cases where an interface is normally encapsulated by a single stakeholder, interoperability is still desirable, but the motive is vendor independence and the efficiencies and choices that an open standards-based interface provides.

Security

Information Flow Security
	Confidentiality	Integrity	Availability
Rating	Moderate	Moderate	Low
Basis	Aggregated messages may have more privacy implications than individual ones, especially if an attacker can attack more than one RSE-to-TMC connection at once.	only limited adverse effect if raw/processed connected vehicle data is bad/compromised; DISC: NYC believes this to be MODERATE: As investigation might be triggered if RF quality is reported as low, this data should be trusted. RES: Agree wih NYC.	only limited adverse effect of info is not timely/readily available. NYC: This data is purely for statistical purposes so low availability does not harm the [RSE RF Monitoring] application.

Security Characteristics	Value
Authenticable	True
Encrypt	True

Connected Vehicle Roadside Equipment --> Traffic Management Center:traffic situation data