< < ST03 : ST04 : ST05 > >

ST04: Roadside Lighting

The Roadside Lighting service package is a connected vehicle version of the automated roadside lighting systems that uses the presence of vehicles based on V2I communications as an input to control of roadside lighting systems. The service package can use the presence of vehicles to alter roadside lighting levels, and can use environmental data obtained from the vehicles as an input to support adjustment of the lighting based on adverse weather conditions such as fog, rain, or snow.

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
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 ITS Roadway Equipment Owner Information Exchange and Action Agreement
Connected Vehicle Roadside Equipment Owner Traffic Management Center Owner Information Exchange Agreement
Connected Vehicle Roadside Equipment Supplier Connected Vehicle Roadside Equipment Owner Warranty
ITS Roadway Equipment Manager ITS Roadway Equipment Manages
ITS Roadway Equipment Owner ITS Roadway Equipment Owns
ITS Roadway Equipment Owner ITS Roadway Equipment Manager Operations Agreement
ITS Roadway Equipment Owner Traffic Management Center Owner Information Exchange Agreement
ITS Roadway Equipment Supplier ITS Roadway Equipment Owner Warranty
Traffic Management Center Manager Traffic Management Center Manages
Traffic Management Center Manager Traffic Operations Personnel System Usage Agreement
Traffic Management Center Owner Connected Vehicle Roadside Equipment Owner Information Exchange Agreement
Traffic Management Center Owner ITS Roadway 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 Supplier Traffic Management Center Owner Warranty
Traffic Operations Personnel Traffic Management Center Operates
Vehicle OBE Manager Vehicle OBE Manages
Vehicle OBE Owner Vehicle OBE Owns
Vehicle OBE Owner Vehicle OBE Manager Operations Agreement
Vehicle OBE Supplier Vehicle OBE 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 Lighting System Support 1.1.2.6 Process Collected Vehicle Safety Data
1.1.7 Collect Vehicle Environmental Data
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
ITS Roadway Equipment Roadway Basic Surveillance 1.1.1.1 Process Traffic Sensor Data
1.1.1.7 Process Road User Protection
1.1.2.11 Control Dynamic Lanes
1.2.7.16 Process Signal Control Conflict Monitoring
1.2.7.2 Monitor Roadside Equipment Operation
1.2.7.8 Provide Device Interface to Other Roadway Devices
1.3.1.3 Process Traffic Images
9.2.3.6 Collect Field Equipment Status for Repair
9.3.3.1 Collect Vehicle Speed
Roadway Lighting System Control 1.2.7.11 Control Lighting System
Traffic Management Center TMC Basic Surveillance 1.1.2.1 Process Traffic Data for Storage
1.1.2.2 Process Traffic Data
1.1.2.3 Update Data Source Static Data
1.1.2.5 Process Vehicle Situation Data
1.1.2.8 Process Roadway Environmental Data
1.1.3 Generate Predictive Traffic Model
1.1.4.1 Retrieve Traffic Data
1.1.4.2 Provide Traffic Operations Personnel Traffic Data Interface
1.1.5 Exchange Data with Other Traffic Centers
1.2.6.1 Maintain Traffic and Sensor Static Data
1.2.8 Collect Traffic Field Equipment Fault Data
1.3.1.1 Analyze Traffic Data for Incidents
1.3.2.1 Store Possible Incident Data
1.3.2.5 Provide Current Incidents Store Interface
1.3.2.6 Manage Traffic Routing
1.3.4.2 Provide Traffic Operations Personnel Incident Interface
1.3.4.5 Process Video Data
TMC Environmental Monitoring 1.1.2.5 Process Vehicle Situation Data
1.1.2.8 Process Roadway Environmental Data
1.1.4.1 Retrieve Traffic Data
1.1.4.2 Provide Traffic Operations Personnel Traffic Data Interface
1.1.4.4 Manage Traffic Archive Data
1.1.5 Exchange Data with Other Traffic Centers
1.2.4.3 Output In-vehicle Signage Data
1.2.4.7 Manage Roadway Warning System
1.2.8 Collect Traffic Field Equipment Fault Data
TMC Lighting System Control 1.1.4.2 Provide Traffic Operations Personnel Traffic Data Interface
1.2.4.6 Manage Lighting System
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 Environmental Monitoring 3.1.3 Process Vehicle On-board Data
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.3 Process Vehicle Location Data
6.7.1.4 Update Vehicle Navigable Map Database
6.7.3.1 Get Driver Personal Request
6.7.3.2 Provide Driver with Personal Travel Information
6.7.3.3 Provide Driver Information Interface

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
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.
ITS Roadway Equipment Field '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.
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.
Traffic Operations Personnel Center 'Traffic Operations Personnel' represents the people that operate a traffic management center. These personnel interact with traffic control systems, traffic surveillance systems, incident management systems, work zone management systems, and travel demand management systems. They provide operator data and command inputs to direct system operations to varying degrees depending on the type of system and the deployment scenario.
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.

Includes Functional Objects:

Functional Object Description Physical Object
Roadway Basic Surveillance 'Roadway Basic Surveillance' monitors traffic conditions using fixed equipment such as loop detectors and CCTV cameras. ITS Roadway Equipment
Roadway Lighting System Control 'Roadway Lighting System Control' includes field equipment that controls lighting systems for transportation facilities and infrastructure. It includes the sensors, lighting controllers, and supporting field equipment that monitors and controls lighting systems. The equipment supports control based on sensed local conditions, stored timing plans, and remote commands from a center. It monitors lighting system status and reports status to the controlling center. ITS Roadway Equipment
RSE Lighting System Support 'RSE Lighting System Support' uses V2I communications to monitor vehicle presence and collect environmental information from passing connected vehicles. The collected data is processed and filtered and provided as an input to support adjustment of roadside lighting systems. 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
TMC Basic Surveillance 'TMC Basic Surveillance' remotely monitors and controls traffic sensor systems and surveillance (e.g., CCTV) equipment, and collects, processes and stores the collected traffic data. Current traffic information and other real-time transportation information is also collected from other centers. The collected information is provided to traffic operations personnel and made available to other centers. Traffic Management Center
TMC Environmental Monitoring 'TMC Environmental Monitoring' assimilates current and forecast road conditions and surface weather information using a combination of weather service provider information, information collected by other centers such as the Maintenance and Construction Management Center, data collected from environmental sensors deployed on and about the roadway, and information collected from connected vehicles. The collected environmental information is monitored and presented to the operator. This information can be used to issue general traveler advisories and support location specific warnings to drivers. Traffic Management Center
TMC Lighting System Control 'TMC Lighting System Control' provides the capability for traffic managers to monitor and manage the electrical lighting systems along the roadside. This capability includes implementing control plans for lighting systems that may be activated by time-of-day plans or by activating changes to the lighting based on traffic or incidents. 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 Environmental Monitoring 'Vehicle Environmental Monitoring' collects data from on-board sensors and systems related to environmental conditions and sends the collected data to the infrastructure as the vehicle travels. The collected data is a byproduct of vehicle safety and convenience systems and includes ambient air temperature and precipitation measures and status of the wipers, lights, ABS, and traction control systems. Vehicle OBE

Includes Information Flows:

Information Flow Description
environmental situation data Aggregated and filtered vehicle environmental data collected from vehicle safety and convenience systems including 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. This information flow represents the aggregated and filtered environmental data sets that are provided by the RSE to the back office center. Depending on the RSE configuration and implementation, the data set may also include environmental sensor station data collected by the RSE.
lighting management application info Application parameters and thresholds. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted.
lighting management application status Lighting management application status reported by the RSE. This includes current operational state and status of the RSE and a record of system operation.
lighting system control data Information used to configure and control roadside lighting systems.
lighting system status Status of roadside lighting controls including operating condition and current operational state.
traffic detector control Information used to configure and control traffic detector systems such as inductive loop detectors and machine vision sensors.
traffic detector data Raw and/or processed traffic detector data which allows derivation of traffic flow variables (e.g., speed, volume, and density measures) and associated information (e.g., congestion, potential incidents). This flow includes the traffic data and the operational status of the traffic detectors
traffic operator data Presentation of traffic operations data to the operator including traffic conditions, current operating status of field equipment, maintenance activity status, incident status, video images, security alerts, emergency response plan updates and other information. This data keeps the operator appraised of current road network status, provides feedback to the operator as traffic control actions are implemented, provides transportation security inputs, and supports review of historical data and preparation for future traffic operations activities.
traffic operator input User input from traffic operations personnel including requests for information, configuration changes, commands to adjust current traffic control strategies (e.g., adjust signal timing plans, change DMS messages), and other traffic operations data entry.
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.
vehicle environmental data Data from vehicle safety and convenience systems that can be used to estimate environmental and infrastructure conditions, including measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, anti-lock brake status, vertical acceleration 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. Both current data and snapshots of recent events (e.g., traction control or anti-lock brake system activations) may be reported.
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.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal
B. Increase the safety of the transportation system for motorized and nonmotorized users; Achieve a significant reduction in traffic fatalities and serious injuries on all public roads

Associated Objective Categories

Objective Category
Safety: Vehicle Crashes and Fatalities
Safety: Worker Safety

Associated Objectives and Performance Measures

Objective Performance Measure
Enhance safety of workers Number of crashes and fatalities in work zones
Enhance safety of workers Number of workers injured by vehicles in work zones
Reduce crashes at intersections Number of crashes and fatalities at signalized intersections
Reduce crashes at intersections Number of crashes and fatalities at unsignalized intersections
Reduce crashes at intersections Number of crashes and fatalities related to red-light running
Reduce crashes due to driver errors and limitations Number of crashes and fatalities related to driver inattention and distraction
Reduce crashes due to driver errors and limitations Number of crashes and fatalities related to driving while intoxicated
Reduce crashes due to road weather conditions Number of crashes and fatalities related to weather conditions
Reduce crashes due to unexpected congestion Number of crashes and fatalities related to unexpected congestion
Reduce lane departure crashes Number of crashes and fatalities related to inappropriate lane departure, crossing or merging
Reduce secondary crashes Number of secondary crashes
Reduce the number of pedestrian fatalities by X percent by year Y. Number of pedestrian fatalities
Reduce the rate fatalities in the region by X percent by year Y. Rate of fatalities (rate per vehicle miles travelled (VMT))
Reduce the rate of severe injuries in the region by X percent by year Y. Rate of serious injuries (rate per VMT)
Reduce the total number of crashes in the region by X percent by year Y. Total crashes per X VMT.
Reduce the total number of crashes involving bicyclists and pedestrians in the region by X percent by year Y. Total crashes involving bicycles.
Reduce the total number of crashes involving bicyclists and pedestrians in the region by X percent by year Y. Total crashes involving pedestrians.
Reduce the total number of fatalities and severe injuries in the region by X percent by year Y. Total fatalities per X VMT.
Reduce the total number of fatalities and severe injuries in the region by X percent by year Y. Total severe injuries per X VMT.
Reduce the total number of fatalities in the region by X percent by year Y. Number of fatalities
Reduce the total number of severe injuries in the region by X percent by year Y. Number of serious injuries
Safeguard public safety personnel while they are at roadway incidents and emergencies Number of public safety personnel struck by vehicle at incident/emergency site
Safeguard public safety personnel while they are at roadway incidents and emergencies Number of public safety vehicles struck at incident/emergency site


 
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 need to be able to monitor operational conditions on the roadway including vehicle presence and weather conditions, in order to determine lighting strategies to implement. Roadway Basic Surveillance 01 The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the center for further analysis and storage, under center control.
RSE Lighting System Support 01 The field element shall monitor vehicle presence and collect environmental information from passing connected vehicles.
03 The field element shall transmit the collected aggregated and filtered environmental data from connected vehicle to the center.
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 Basic Surveillance 01 The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements under remote control of the center.
06 The center shall maintain a database of surveillance equipment and sensors and associated data (including the roadway on which they are located, the type of data collected, and the ownership of each).
07 The center shall remotely control devices to detect traffic.
TMC Environmental Monitoring 05 The traffic center shall receive aggregated and processed vehicle environmental data collected from vehicle safety and convenience systems through the connected vehicle roadside equipment.
TMC Lighting System Control 04 The traffic management center shall receive the environmental data collected from connected vehicle.
05 The traffic management center shall be able to monitor vehicle presence.
Vehicle Basic Safety Communication 05 The vehicle shall exchange location and motion information with roadside equipment and nearby vehicles.
Vehicle Environmental Monitoring 04 The vehicle shall transmit environmental probe data to field equipment located along the roadway using short range communications.
02 Traffic Operations need to be able to monitor and control roadway lighting systems in order to adjust lighting levels based on operational conditions. Roadway Lighting System Control 01 The field element shall control lighting systems along the roadside under center control.
02 The field element shall return operational status for the lighting system equipment to the center.
03 The field element shall return lighting system equipment fault data to the center for repair.
RSE Lighting System Support 02 The field element shall report the current operational state and status of the field element to the center.
TMC Lighting System Control 01 The traffic management center shall remotely control electrical lighting systems.
02 The traffic management center shall collect lighting system operational status from the field and compare against the control information sent by the center.
03 The traffic management center shall collect lighting system fault data from the field and send to the maintenance center for repair.
06 The traffic management center shall be able to adjust lighting level based on operational condition.

Related Sources

Document Name Version Publication Date
ITS User Services Document 1/1/2005
National ITS Architecture Services


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
Connected Vehicle Roadside Equipment Moderate Moderate Moderate Class 2
ITS Roadway Equipment Moderate Moderate Moderate Class 2
Traffic Management Center Moderate Moderate Moderate Class 2
Vehicle OBE Low Moderate Moderate 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
Connected Vehicle Roadside Equipment ITS Roadway Equipment environmental situation data Low Moderate Moderate
Little to no impact if this data is observed Some minimal guarantee of data integrity is necessary for all C-ITS flows. DISC: THEA believes this to be LOW: only limited adverse effect if environmental data from vehicle safety and convenience systems is bad/compromised; can cope with some bad data; DISC: WYO belives this to be MODERATE Only limited adverse effect of info is not timely/readily available. DISC: WYO believes this to be MODERATE. Changed from THEA's LOW inferring severity of weather data in Wyoming
Connected Vehicle Roadside Equipment ITS Roadway Equipment 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. THEA: only limited adverse effect if info is not timely/readily available, could be LOW for ISIG
Connected Vehicle Roadside Equipment Traffic Management Center environmental situation data Low Moderate Moderate
Little to no impact if this data is observed Only limited adverse effect if environmental data from vehicle safety and convenience systems is bad/compromised; can cope with some bad data; DISC: WYO believes this to be MODERATE HIGH. Changed from THEA's LOW inferring severity of weather data in Wyoming Only limited adverse effect of info is not timely/readily available. DISC: WYO believes this to be MODERATE. Changed from THEA's LOW inferring severity of weather data in Wyoming
Connected Vehicle Roadside Equipment Traffic Management Center lighting management 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.
ITS Roadway Equipment Traffic Management Center lighting system status Moderate Moderate Moderate
Device status information should be concealed, as an unauthorized observer could use this to reverse engineer device control systems. Device status information needs to be available and correct, or the controlling system may take inappropriate maintenance action, costing time and money. Device status information needs to be available and correct, or the controlling system may take inappropriate maintenance action, costing time and money.
ITS Roadway Equipment Traffic Management Center traffic detector data Low Moderate Moderate
No impact if someone sees the data Some minimal guarantee of data integrity is necessary for all C-ITS flows. THEA believes this to be LOW.only limited adverse effect if raw/processed traffic detector data is bad/compromised; DISC: WYO believes this to be HIGH Only limited adverse effect of info is not timely/readily available, however without this information it will be difficult to perform traffic management activities, thus MODERATE. If not used for management, may be LOW.
Traffic Management Center Connected Vehicle Roadside Equipment lighting management 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 ITS Roadway Equipment lighting system control data Moderate Moderate Low
Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH. Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH.
Traffic Management Center ITS Roadway Equipment traffic detector control Moderate Moderate Low
Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. DISC: THEA, WYO believe this to be LOW: encrypted, authenticated, proprietary; but should not cause severe damage if seen Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH.. From THEA: should be accurate and not be tampered with; could enable outside control of traffic sensors but should not cause severe harm, but could cause issues with traffic sensor data received and be detrimental to operations Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH.. From THEA: want updates but delayed information will not be severe; should be able to operate from a previous/default control/config. DISC: WYO believes this to be MODERATE
Traffic Management Center Traffic Operations Personnel traffic operator data Moderate Moderate Moderate
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Information presented to backoffice system operators must be consistent or the operator may perform actions that are not appropriate to the real situation. The backoffice system operator should have access to system operation. If this interface is down then control is effectively lost, as without feedback from the system the operator has no way of knowing what is the correct action to take.
Traffic Operations Personnel Traffic Management Center traffic operator input Moderate High High
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Vehicle OBE Connected Vehicle Roadside Equipment vehicle environmental data Low Moderate Low
Little abusive potential for capturing the information in this flow as designed. Could be moderate if this contains PII related information, but considered for now to not include any PII; DISC: WYO believes Vehicle to Center versions of this flow to be MODERATE as center penetrations could more easily garner aggregate user data that might be used for mischief. 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; can also receive data from ITS RE; DISC: WYO believes this to be MODERATE data should be timely and readily available, but limited adverse effect; aggregate data; can also receive data from ITS RE; DISC: WYO believes this to be MODERATE
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

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
ITE ATC ITS Cabinet Intelligent Transportation System Standard Specification for Roadside Cabinets ITS Roadway Equipment
NEMA TS 8 Cyber and Physical Security Cyber and Physical Security for Intelligent Transportation Systems ITS Roadway Equipment
Traffic Management Center
USDOT RSU Dedicated Short-Range Communications Roadside Unit Specifications (FHWA-JPO-17-589) Connected Vehicle Roadside Equipment