< < TM01 : TM02 : TM03 > >

TM02: Vehicle-Based Traffic Surveillance

This service package uses probe data information obtained from vehicles in the network to support traffic operations, including incident detection and the implementation of localized operational strategies. Since traffic data is collected from vehicles, travel times and other related traffic performance measures are available. This service package includes the capability to collect data from Connected Vehicles so that "probe" data can be collected from all equipped vehicles, providing access to a large vehicle population as penetration increases. Incident detection enables transportation agencies to determine the location of potential incidents so the agencies can respond more quickly to the incident and mitigate any negative impacts to the transportation network. Vehicle data that can be used to detect potential incidents include changes in vehicle speeds indicating the disruption of traffic flow, when a vehicle's safety systems have been activated or deployed, or sudden vehicle turns or deceleration at a specific location (indicating a potential obstacle in the roadway).

Relevant Regions: Australia, Canada, European Union, and United States

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
Basic Vehicle Manager Basic Vehicle Manages
Basic Vehicle Owner Basic Vehicle Owns
Basic Vehicle Owner Basic Vehicle Manager Operations Agreement
Basic Vehicle Owner Vehicle OBE Owner Expectation of Data Provision
Basic Vehicle Supplier Basic Vehicle Owner Warranty
Connected Vehicle Roadside Equipment Manager Connected Vehicle Roadside Equipment Manages
Connected Vehicle Roadside Equipment Owner Connected Vehicle Roadside Equipment Owns
Connected Vehicle Roadside Equipment Owner Connected Vehicle Roadside Equipment Manager Operations Agreement
Connected Vehicle Roadside Equipment Owner Traffic Management Center Owner Information Exchange Agreement
Connected Vehicle Roadside Equipment Owner Transportation Information Center Owner Information Provision Agreement
Connected Vehicle Roadside Equipment Owner Vehicle OBE Owner Expectation of Information Provision
Connected Vehicle Roadside Equipment Supplier Connected Vehicle Roadside Equipment Owner Warranty
Payment Administration Center Manager Payment Administration Center Manages
Payment Administration Center Owner Payment Administration Center Owns
Payment Administration Center Owner Payment Administration Center Manager Operations Agreement
Payment Administration Center Owner Traffic Management Center Owner Information Provision Agreement
Payment Administration Center Owner Transportation Information Center Owner Information Provision Agreement
Payment Administration Center Supplier Payment Administration Center Owner Warranty
Traffic Management Center Manager Traffic Management Center Manages
Traffic Management Center Owner Connected Vehicle Roadside Equipment Owner Information Exchange Agreement
Traffic Management Center Owner Traffic Management Center Owns
Traffic Management Center Owner Traffic Management Center Manager Operations Agreement
Traffic Management Center Owner Transportation Information Center Owner Information Exchange Agreement
Traffic Management Center Supplier Traffic Management Center Owner Warranty
Transit Management Center Manager Transit Management Center Manages
Transit Management Center Owner Traffic Management Center Owner Information Provision Agreement
Transit Management Center Owner Transit Management Center Owns
Transit Management Center Owner Transit Management Center Manager Operations Agreement
Transit Management Center Owner Transportation Information Center Owner Information Provision Agreement
Transit Management Center Supplier Transit Management Center Owner Warranty
Transportation Information Center Manager Transportation Information Center Manages
Transportation Information Center Owner Traffic Management Center Owner Information Exchange Agreement
Transportation Information Center Owner Transportation Information Center Owns
Transportation Information Center Owner Transportation Information Center Manager Operations Agreement
Transportation Information Center Owner Vehicle OBE Owner Information Exchange Agreement
Transportation Information Center Supplier Transportation Information Center Owner Warranty
Vehicle OBE Manager Vehicle OBE Manages
Vehicle OBE Owner Transportation Information Center Owner Information Exchange Agreement
Vehicle OBE Owner Vehicle OBE Owns
Vehicle OBE Owner Vehicle OBE Manager Operations Agreement
Vehicle OBE Supplier Vehicle OBE Owner Warranty
Wireless Communications Provider System Manager Wireless Communications Provider System Manages
Wireless Communications Provider System Owner Traffic Management Center Owner Information Provision Agreement
Wireless Communications Provider System Owner Transportation Information Center Owner Information Provision Agreement
Wireless Communications Provider System Owner Wireless Communications Provider System Owns
Wireless Communications Provider System Owner Wireless Communications Provider System Manager Operations Agreement
Wireless Communications Provider System Supplier Wireless Communications Provider System Owner Warranty

Maintenance Stage Roles and Relationships

Functional

This service package includes the following Functional View PSpecs:

Physical Object Functional Object PSpec Number PSpec Name
Connected Vehicle Roadside Equipment RSE Situation Monitoring 1.1.1.6 Collect Vehicle Roadside Safety Data
1.1.6 Collect Vehicle Traffic Surveillance Data
1.1.7 Collect Vehicle Environmental Data
9.2.3.8 Collect Connected Vehicle Field Equipment Status
RSE Traffic Monitoring 1.1.2.6 Process Collected Vehicle Safety Data
1.1.6 Collect Vehicle Traffic Surveillance Data
1.1.7 Collect Vehicle Environmental Data
1.2.7.15 Process Intersection Safety Data
1.2.7.4 Process In-vehicle Signage Data
6.7.3.5 Provide Short Range Traveler Information
9.3.3.5 Manage Speeds at Roadside
Traffic Management Center TMC Situation Data Management 1.1.2.5 Process Vehicle Situation Data
Transportation Information Center TIC Situation Data Management 6.2.1 Collect Misc Traveler Information
6.2.2 Collect Traffic Data
6.2.5 Collect Situation and Sensor Data From Vehicles
6.5.8 Provide Operational Data for Other Centers
6.5.9 Provide Traveler Alert Interface
6.9 Manage Traveler Info Archive Data
Vehicle OBE Vehicle Basic Safety Communication 3.1.1 Produce Collision and Crash Avoidance Data
3.1.3 Process Vehicle On-board Data
3.1.4 Communicate with Remote Vehicles
3.1.6 Provide Vehicle Acceleration and Deceleration Inputs
3.2.3.2 Manage Platoon Following
3.2.3.3 Process Data for Vehicle Actuators
3.2.3.5 Process Vehicle Sensor Data
3.2.4 Process Sensor Data for Automatic Vehicle Operations
6.7.1.2 Provide Driver Guidance Interface
6.7.1.3 Process Vehicle Location Data
6.7.1.4 Update Vehicle Navigable Map Database
6.7.3.3 Provide Driver Information Interface
Vehicle Situation Data Monitoring 3.1.3 Process Vehicle On-board Data

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
Basic Vehicle Vehicle 'Basic Vehicle' represents a complete operating vehicle. It includes the vehicle platform that interfaces with and hosts ITS electronics and all of the driver convenience and entertainment systems, and other non-ITS electronics on-board the vehicle. Interfaces represent both internal on-board interfaces between ITS equipment and other vehicle systems and other passive and active external interfaces or views of the vehicle that support vehicle/traffic monitoring and management. External interfaces may also represent equipment that is carried into the vehicle (e.g., a smartphone that is brought into the vehicle). Internal interfaces are often implemented through a vehicle databus, which is also included in this object. Note that 'Vehicle' represents the general functions and interfaces that are associated with personal automobiles as well as commercial vehicles, emergency vehicles, transit vehicles, and other specialized vehicles.
Connected Vehicle Roadside Equipment Field '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.
Payment Administration Center Center The 'Payment Administration Center' provides general payment administration capabilities and supports the electronic transfer of funds from the customer to the transportation system operator or other service provider. Charges can be recorded for tolls, vehicle-mileage charging, congestion charging, or other goods and services. It supports traveler enrollment and collection of both pre-payment and post-payment transportation fees in coordination with the financial infrastructure supporting electronic payment transactions. The system may establish and administer escrow accounts depending on the clearinghouse scheme and the type of payments involved. It may post a transaction to the customer account, generate a bill (for post-payment accounts), debit an escrow account, or interface to a financial infrastructure to debit a customer designated account. It supports communications with the ITS Roadway Payment Equipment to support fee collection operations. As an alternative, a wide-area wireless interface can be used to communicate directly with vehicle equipment. It also sets and administers the pricing structures and may implement road pricing policies in coordination with the Traffic Management Center.
Traffic Management Center Center 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.
Transit Management Center Center The 'Transit Management Center' manages transit vehicle fleets and coordinates with other modes and transportation services. It provides operations, maintenance, customer information, planning and management functions for the transit property. It spans distinct central dispatch and garage management systems and supports the spectrum of fixed route, flexible route, paratransit services, transit rail, and bus rapid transit (BRT) service. The physical object's interfaces support communication between transit departments and with other operating entities such as emergency response services and traffic management systems.
Transportation Information Center Center 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.
Vehicle OBE Vehicle The Vehicle On-Board Equipment (OBE) provides the vehicle-based sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. The Vehicle OBE includes general capabilities that apply to passenger cars, trucks, and motorcycles. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle OBE includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle OBE. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Route guidance capabilities assist in formulation of an optimal route and step by step guidance along the travel route. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.
Wireless Communications Provider System Center The 'Wireless Communications Provider System' represents the systems used by wireless communications providers to provide data and voice services that collectively serve billions of mobile users around the world. As they serve their customers, these providers collect location information from their mobile customers as they use communications services while they traverse the transportation network. This information may be shared with transportation providers, in aggregate and without personal information, to provide a rich data source that may be used in conjunction with other data to monitor transportation network use and performance.

Use this physical object where the relationship with the communications provider is limited to use of service provider-derived transportation network performance data. Where wireless communications services are purchased and used to support wireless interfaces included in an ITS architecture, see 'ITS Communications Equipment', which can represent use of purchased communications services as part of an overall ITS communications network.

Includes Functional Objects:

Functional Object Description Physical Object
RSE Situation Monitoring 'RSE Situation Monitoring' is a general functional object that supports collection of traffic, environmental, and emissions data from passing vehicles. The data is collected, filtered, and forwarded based on parameters provided by the back office. Parameters are provided to passing vehicles that are equipped to collect and send situation data to the infrastructure in snapshots. In addition, this object collects current status information from local field devices including intersection status, sensor data, and signage data, providing complete, configurable monitoring of the situation for the local transportation system in the vicinity of the RSE. Connected Vehicle Roadside Equipment
RSE Traffic Monitoring 'RSE Traffic Monitoring' monitors the basic safety messages that are shared between connected vehicles and distills this data into traffic flow measures that can be used to manage the network in combination with or in lieu of traffic data collected by infrastructure-based sensors. As connected vehicle penetration rates increase, the measures provided by this application can expand beyond vehicle speeds that are directly reported by vehicles to include estimated volume, occupancy, and other measures. This object also supports incident detection by monitoring for changes in speed and vehicle control events that indicate a potential incident. Connected Vehicle Roadside Equipment
TIC Situation Data Management 'TIC Situation Data Management' manages connected vehicle situation data collection, quality controls, filtering, aggregation, and storage. Through this process, raw data reported by connected vehicles are transformed into information products that can be accessed and used to support transportation operations and traveler information. The distribution of the connected vehicle-derived information products is handled by other functional objects. Transportation Information Center
TMC Situation Data Management 'TMC Situation Data Management' collects, assimilates, and disseminates vehicle probe data collected from roadside short range communications equipment and centers controlling transit vehicles, toll collection points, and route-guided vehicles. It estimates traffic and road conditions based on the aggregated probe data and disseminates this information to other centers. Traffic Management Center
Vehicle Basic Safety Communication 'Vehicle Basic Safety Communication' exchanges current vehicle location and motion information with other vehicles in the vicinity, uses that information to calculate vehicle paths, and warns the driver when the potential for an impending collision is detected. If available, map data is used to filter and interpret the relative location and motion of vehicles in the vicinity. Information from on-board sensors (e.g., radars and image processing) are also used, if available, in combination with the V2V communications to detect non-equipped vehicles and corroborate connected vehicle data. Vehicle location and motion broadcasts are also received by the infrastructure and used by the infrastructure to support a wide range of roadside safety and mobility applications. This object represents a broad range of implementations ranging from basic Vehicle Awareness Devices that only broadcast vehicle location and motion and provide no driver warnings to advanced integrated safety systems that may, in addition to warning the driver, provide collision warning information to support automated control functions that can support control intervention. Vehicle OBE
Vehicle Situation Data Monitoring 'Vehicle Situation Data Monitoring' is the highest-level representation of the functionality required to collect traffic and environmental situation data by monitoring and storing the experience of the vehicle as it travels through the road network. Collected data is aggregated into snapshots that are reported when communications is available and with flow control based on parameters provided by the infrastructure. Note that this functional object supports collection of data for areas remote from RSEs or other communications infrastructure. Vehicle OBE

Includes Information Flows:

Information Flow Description
comm-derived travel performance data Data that can be used to derive travel time data and other transportation performance measures. Data provided may be raw IDs, locations, and timestamps, derived link travel times, speeds, or other data that has been collected and derived by a communications provider from its mobile customers.
host vehicle status Information provided to the ITS on-board equipment from other systems on the vehicle platform. This includes the current status of the powertrain, steering, and braking systems, and status of other safety and convenience systems. In implementations where GPS is not integrated into the Vehicle On-Board Equipment, the host vehicle is also the source for data describing the vehicle's location in three dimensions (latitude, longitude, elevation) and accurate time that can be used for time synchronization across the ITS environment.
road network conditions Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included.
road network traffic situation data Aggregated route usage, travel times, and other aggregated data collected from probe vehicles that can be used to estimate current traffic conditions.
situation data collection parameters The parameters that are used to control the flow of situation data from the RSE. This flow identifies the type of data/snapshots that are requested from passing vehicles and reporting parameters such as snapshot frequency, filtering criteria (data thresholds for reporting), and reporting interval that control the type and volume of data reported to the back office center.
toll probe data Aggregate probe data derived from electronic toll collection operations. Data collected could include vehicle speeds and travel times for a given link or collection of links.
traffic monitoring application info Traffic monitoring application parameters and thresholds that control the filtering, aggregation, and range of measures that are collected, derived, and reported. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted.
traffic monitoring application status Traffic monitoring application status reported by the RSE. This includes current operational state and status of the RSE and a record of system operation.
traffic situation data 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.
transit probe data Aggregate probe data derived from tracking transit vehicles. Data collected could include transit vehicle speeds and travel times for a given link or collection of links.
vehicle location and motion for surveillance Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size. This flow represents monitoring of basic safety data ('vehicle location and motion') broadcast by passing connected vehicles for use in vehicle detection and traffic monitoring applications.
vehicle situation data This flow represents vehicle snapshots that may be provided by the vehicle to support traffic and environmental conditions monitoring. Snapshots are collected by the vehicle for specific events (e.g., when a sensor exceeds a threshold) or periodically and reported based on control parameters when communications is available. Traffic-related data includes snapshots of measured speed and heading and events including starts and stops, speed changes, and other vehicle control events. Environmental data may include measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, anti-lock brake status, and other collected vehicle system status and sensor information. The collected data is reported along with the location, heading, and time that the data was collected.
vehicle situation data parameters A request for vehicle situation data that includes parameters used to control the data that is reported and the flow of data reported by the vehicle. This flow identifies the type of data/snapshots that are requested and reporting parameters such as snapshot frequency, filtering criteria (data thresholds for reporting), and reporting interval.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal
G. Promote efficient system management and operation; Improve the efficiency of the surface transportation system

Associated Objective Categories

Objective Category
Arterial Management: Traffic Monitoring and Data Collection
Freeway Management: Transportation Management Centers
Special Event Management: Use of Technology
Traveler Information: Data Collection and Sharing on Travel Conditions

Associated Objectives and Performance Measures

Objective Performance Measure
Field data collection is conducted either through floating car studies or other methods at least once every Y years on major signalized arterials and X years on minor signalized arterials. Number of field data collection studies performed every Y and X years on major and minor signalized arterials, respectively.
Increase the percent of regional transportation system monitored by the TMC for real-time performance. Percent of regional transportation system monitored by the TMC for real-time performance.


 
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Needs and Requirements

Need Functional Object Requirement
01 Traffic Operations and Traveler Information Providers need to be able to monitor the road network using information from connected vehicles in order to detect and verify incidents. RSE Situation Monitoring 01 The field element shall collect traffic-related data including snapshots of measured speed and heading and events including starts and stops, speed changes, and other vehicle control from vehicles.
03 The field element shall provide data collection parameters to vehicles.
RSE Traffic Monitoring 01 The field element shall communicate with on-board equipment on passing vehicles to collect current vehicle position, speed, and heading and a record of previous events (e.g., starts and stops, link travel times) that can be used to determine current traffic conditions.
TMC Situation Data Management 01 The center shall collect traffic probe data from vehicles via roadside field equipment.
03 The center shall collect traffic data from traveler information centers based on data from their subscriber vehicles; the data may be aggregated and initial link time calculations performed at the sending center.
Vehicle Basic Safety Communication 05 The vehicle shall exchange location and motion information with roadside equipment and nearby vehicles.
Vehicle Situation Data Monitoring 01 The Vehicle shall obtain data collection parameters from Connected Vehicle Roadside Equipment.
02 The Vehicle shall collect data collection parameters from Centers.
03 The vehicle shall provide traffic-related data including snapshots of measured speed and heading and events including starts and stops, speed changes, and other vehicle control from vehicle.
04 The Vehicle shall provide data to Centers in accordance with data collection parameters provided by Centers/Connected Vehicle Roadside Equipment.
05 The Vehicle shall provide data to Connected Vehicle Roadside Equipment. in accordance with data collection parameters provided by Centers/Connected Vehicle Roadside Equipment.
02 Traffic Operations need to be able to monitor the roadside equipment in order to detect faults in equipment or communications. TMC Situation Data Management 05 The center shall collect operational status for the roadside probe data collection equipment.
06 The center shall collect fault data for the roadside probe data collection equipment for repair.
03 Traffic Operations need to be able to monitor the road network using probe data from connected vehicles in order to support traveler information. TIC Situation Data Management 01 The center shall collect traffic probe data (speeds, travel times, etc.) from appropriately equipped vehicles and short range communications equipment.
05 The center shall aggregate collected traffic probe data, calculate route segment travel times, route segment speeds, route usage, and road weather information for dissemination to other centers.
04 Traffic Operations need to be able to monitor the road network using probe data from toll or transit systems. TIC Situation Data Management 03 The center shall collect road condition data from probe-equipped transit vehicles via transit management centers.
04 The center shall collect probe data from toll administrative centers containing travel times between toll collection points for those vehicles equipped for electronic toll collection; the data may be aggregated and processed at the sending center.
TMC Situation Data Management 02 The center shall collect road condition data from probe-equipped transit vehicles via transit management centers; the data may be aggregated and preliminarily processed at the sending center.
04 The center shall collect probe data from payment administrative centers containing travel times between toll collection points for those vehicles equipped for electronic toll collection; the data may be aggregated and processed at the sending center.

Related Sources

Document Name Version Publication Date
CO-UMP Probe Vehicle Data 5/31/2021
ITS User Services Document 1/1/2005
SAE J3067- Candidate Improvements to Dedicated Short Range Communications (DSRC) Message Set Dictionary (SAE J2735)Using Systems Engineering Methods 8/15/2014


Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
Basic Vehicle  
Connected Vehicle Roadside Equipment Moderate Moderate Moderate Class 2
Payment Administration Center Low Moderate Low Class 1
Traffic Management Center Moderate Moderate Moderate Class 2
Transit Management Center Low Moderate Low Class 1
Transportation Information Center Moderate Moderate Moderate Class 2
Vehicle OBE Moderate Moderate Moderate Class 2
Wireless Communications Provider System Not Applicable Moderate Low Class 1



In order to participate in this service package, each information flow triple should meet or exceed the following security levels.

Information Flow Security
Source Destination Information Flow Confidentiality Integrity Availability
Basis Basis Basis
Basic Vehicle Vehicle OBE host vehicle status Low Moderate High
Unlikely that this includes any information that could be used against the originator. This can be MODERATE or HIGH, depending on the application: This is used later on to determine whether a vehicle is likely going to violate a red light or infringe a work zone. This needs to be correct in order for the application to work correctly. Since this monitors the health and safety of the vehicle and that information is eventually reported to the driver, it should be available at all times as it directly affects vehicle and operator safety.
Connected Vehicle Roadside Equipment Traffic Management Center traffic monitoring application status Moderate Moderate Low
This information could be of interest to a malicious individual who is attempting to determine the best way to accomplish a crime. As such it would be best to not make it easily accessible. If this is compromised, it could send unnecessary maintenance workers, or cause the appearance of excessive traffic violations, leading to further unnecessary investigation. A delay in reporting this may cause a delay in necessary maintenance, but (a) this is not time-critical and (b) there are other channels for reporting malfunctioning. Additionally, there is a message received notification, which means that RSE can ensure that all intersection safety issues are delivered.
Connected Vehicle Roadside Equipment Traffic Management Center traffic situation data Moderate Moderate Low
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.
Connected Vehicle Roadside Equipment Transportation Information Center traffic situation data Moderate Moderate Moderate
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.
Connected Vehicle Roadside Equipment Vehicle OBE vehicle situation data parameters Low Moderate Moderate
This isn't exactly a control flow, more like a 'suggestion flow', as the vehicle will always decide what to send. Probably no need for obfuscation. Info should be accurate and should not be tampered so that the vehicle only discloses the correctly requested data Parameters should be timely and readily available, but would not have severe/catastrophic consequences if not
Payment Administration Center Traffic Management Center toll probe data Low Moderate Low
As this is aggregate information that will be used for a public information product, there is little reason to conceal it. This will eventually drive decisions made by travelers, so it does deserve some protection. If modified or corrupted, may lead to decisions wasting time and money. There are many sources of traffic data, it is unlikely that this is the only one. While loss of this flow would degrade overall travel time quality, it would not eliminate that metric and would have a widespread but minor effect.
Payment Administration Center Transportation Information Center toll probe data Low Moderate Low
As this is aggregate information that will be used for a public information product, there is little reason to conceal it. This will eventually drive decisions made by travelers, so it does deserve some protection. If modified or corrupted, may lead to decisions wasting time and money. There are many sources of traffic data, it is unlikely that this is the only one. While loss of this flow would degrade overall travel time quality, it would not eliminate that metric and would have a widespread but minor effect.
Traffic Management Center Connected Vehicle Roadside Equipment situation data collection parameters Moderate Moderate Low
This is a control flow, so should be obfuscated to make it more difficult for a 3rd party to manipulate the RSE. Control parameters need to be correct and not corrupted so that the owner of the RSE and the receiver of the RSE's data get what they need from it. This information probably does not need to be changed very often, and if it is not available then likely the flow it controls (situation data flows to the DDS/TMC) are down as well.
Traffic Management Center Connected Vehicle Roadside Equipment traffic monitoring application info Moderate Moderate Low
This information could be of interest to a malicious individual who is attempting to determine the best way to accomplish a crime. As such it would be best to not make it easily accessible. If this is compromised, it could send unnecessary maintenance workers, or cause the appearance of excessive traffic violations, leading to further unnecessary investigation. A delay in reporting this may cause a delay in necessary maintenance, but (a) this is not time-critical and (b) there are other channels for reporting malfunctioning. Additionally, there is a message received notification, which means that RSE can ensure that all intersection safety issues are delivered.
Traffic Management Center Transportation Information Center road network conditions Low Moderate Moderate
No harm should come from seeing this data, as it is eventually intended for public consumption. While accuracy of this data is important for decision making purposes, applications should be able to corroborate the data in many instances. Thus MODERATE generally. Depends on the application; if mobility decisions that affect large numbers of travelers are made based on this data, then it is MODERATE. In more modest circumstances, it may be LOW.
Transit Management Center Traffic Management Center transit probe data Low Moderate Low
As this is aggregate information that will be used for a public information product, there is little reason to conceal it. This will eventually drive decisions made by travelers, so it does deserve some protection. If modified or corrupted, may lead to decisions wasting time and money. There are many sources of traffic data, it is unlikely that this is the only one. Loss of this flow may degrade overall travel time quality (unclear, as transit travel times are notoriously different from passenger vehicle travel times), it would not eliminate that metric and would have a widespread but minor effect.
Transit Management Center Transportation Information Center transit probe data Low Moderate Low
As this is aggregate information that will be used for a public information product, there is little reason to conceal it. This will eventually drive decisions made by travelers, so it does deserve some protection. If modified or corrupted, may lead to decisions wasting time and money. There are many sources of traffic data, it is unlikely that this is the only one. Loss of this flow may degrade overall travel time quality (unclear, as transit travel times are notoriously different from passenger vehicle travel times), it would not eliminate that metric and would have a widespread but minor effect.
Transportation Information Center Traffic Management Center road network traffic situation data Moderate Moderate Moderate
The data this is based on is not encrypted, but aggregated messages may have more privacy implications than individual ones. Should be limited effect if this data is incorrect or compromised, as there should be other mechanisms in place to validate it. This information is used as supplemental information. It should operate correctly if not every single message is received.
Transportation Information Center Vehicle OBE vehicle situation data parameters Low Moderate Moderate
This isn't exactly a control flow, more like a 'suggestion flow', as the vehicle will always decide what to send. Probably no need for obfuscation. Info should be accurate and should not be tampered so that the vehicle only discloses the correctly requested data Parameters should be timely and readily available, but would not have severe/catastrophic consequences if not
Vehicle OBE Connected Vehicle Roadside Equipment vehicle location and motion for surveillance Not Applicable Moderate Moderate
This is directly observable data; DISC: WYO believes this to be MODERATE Incorrect information here could lead to the system not functioning properly. If they are unable to properly detect all vehicles crossing the border, it would lead to confusion. There are other factors, such as visual indicators, of vehicles crossing the border, which can be used to help mitigate contradicting information. DISC: THEA believes this should be HIGH: "BSM info needs to be accurate and should not be tampered with" WYO believes this to be HIGH This information must be available in a timely manner for the system to act upon it. The system can operate correctly if some messages are missed, but overall a majority of them should be received.; WYO believes this to be LOW
Vehicle OBE Connected Vehicle Roadside Equipment vehicle situation data Moderate Moderate Low
Might be able to link multiple snapshots together and compromise some element of driver/traveler privacy. Some minimal guarantee of data integrity is necessary for all C-ITS flows. DISC: THEA believes this to be LOW: data should be accurate and not tampered with but should be able to cope with some bad data in traffic/environmental condition monitoring; aggregate data data should be timely and readily available, but limited adverse effect; aggregate data
Vehicle OBE Transportation Information Center vehicle situation data Moderate Moderate Low
Might be able to link multiple snapshots together and compromise some element of driver/traveler privacy. Event driven data can be used for various mobility monitoring applications, and as operational decisions may be made based on mobility conditions, this data's accuracy should be preserved or decisions may not align with real situations. While desireable, in most application contexts the provision of a single vehicle's data through this flow is not critical.
Wireless Communications Provider System Traffic Management Center comm-derived travel performance data Not Applicable Moderate Low
This data is intended for public use and is presumed to already be sanitized. Data should be correct and available, but this is one of many sources of travel-time data. Installations not relying on this source as their primary means for acquiring travel time data could lower this to LOW. Data should be correct and available, but this is one of many sources of travel-time data. Installations relying on this source as their primary means for acquiring travel time data should elevate this to MODERATE.
Wireless Communications Provider System Transportation Information Center comm-derived travel performance data Not Applicable Moderate Low
This data is intended for public use and is presumed to already be sanitized. Data should be correct and available, but this is one of many sources of travel-time data. Installations not relying on this source as their primary means for acquiring travel time data could lower this to LOW. Data should be correct and available, but this is one of many sources of travel-time data. Installations relying on this source as their primary means for acquiring travel time data should elevate this to MODERATE.

Standards

The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.

Name Title Physical Object
USDOT RSU Dedicated Short-Range Communications Roadside Unit Specifications (FHWA-JPO-17-589) Connected Vehicle Roadside Equipment