Connected Vehicle Roadside Equipment --> ITS Roadway Equipment:
traffic situation data
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.
ITS Roadway Equipment (Destination Physical Object): 'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway. This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.
Included In
This Triple is in the following Service Packages:
- MC07: Work Zone Safety Monitoring
- PS07: Incident Scene Safety Monitoring
- ST02: Eco-Traffic Signal Timing
- ST03: Eco-Traffic Metering
- ST04: Roadside Lighting
- TM04: Connected Vehicle Traffic Signal System
- TM21: Speed Harmonization
- VS06: Stop Sign Gap Assist
- VS08: Queue Warning
- VS15: Infrastructure Enhanced Cooperative Adaptive Cruise Control
- VS16: Automated Vehicle Operations
This triple is associated with the following Functional Objects:
- Roadway Basic Surveillance
- Roadway Incident Scene Safety
- Roadway Lighting System Control
- Roadway Traffic Gap Assist
- Roadway Work Zone Safety
- RSE Incident Scene Safety
- RSE Traffic Gap Assist
- RSE Traffic Monitoring
- RSE Work Zone Safety
This Triple is described by the following Functional View Data Flows:
- vehicle_speed_data_from_roadside
- vehicle_traffic_data_for_freeways
- vehicle_traffic_data_for_lanes
- vehicle_traffic_data_for_lighting
- vehicle_traffic_data_for_roads
- vehicle_traffic_data_from_roadside
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 (11)
-
(None-Data) - Secure Internet (ITS) (32)
-
Data for Distribution (TBD) - Apache Kafka (36)
-
Data for Distribution (TBD) - OMG DDS (36)
-
Data for Distribution (TBD) - OASIS MQTT (42)
-
Data for Distribution (TBD) - OASIS AMQP (45)
Selected Solution
US: NTCIP Transportation Sensors - SNMPv3/TLSSolution Description
|
ITS Application Entity
NTCIP 1209  |
Click gap icons for more info.
|
||
|
Mgmt
|
Facilities
|
Security
IETF RFC 6353 |
|
|
TransNet
|
|||
|
Access
|
|||
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 | Adjacent |
| Acknowledgement | False |
| 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. THEA: only limited adverse effect if info is not timely/readily available, could be LOW for ISIG | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | True |