Connected Vehicle Roadside Equipment --> Transportation Information 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 that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. 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.

Transportation Information Center (Destination Physical Object): The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.

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:

This Triple has the following triple relationships:

Relationship	Source	Destination	Flow
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 (8)
(None-Data) - Secure Internet (ITS) (32)
Data for Distribution (TBD) - Apache Kafka (36)
Data for Distribution (TBD) - OMG DDS (36)
(None-Data) - OASIS MQTT (42)
Data for Distribution (TBD) - OASIS MQTT (42)
(None-Data) - OASIS AMQP (45)
Data for Distribution (TBD) - OASIS AMQP (45)

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 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
	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	Moderate
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.	This information is used to help with incident detection. It should be verified to ensure that it is not incorrectly influencing this.THEA: only limited adverse effect if raw/processed connected vehicle data is bad/compromised; could be LOW for ISIG	This information is used as supplemental information. It should operate correctly if not every single message is received.

Security Characteristics	Value
Authenticable	True
Encrypt	True

Connected Vehicle Roadside Equipment --> Transportation Information Center:traffic situation data