< < ST01.2 : ST02.1 : ST02.2 > >
ST02.1: Infrastructure-Based Monitoring
Traffic detectors, environmental sensors, and emissions monitors in the infrastructure collect data used to adapt traffic signal control to minimize environmental impact
Relevant Regions:
- Enterprise
- Functional
- Physical
- Goals and Objectives
- Needs and Requirements
- Sources
- Security
- Standards
- System Requirements
Enterprise
Development Stage Roles and Relationships
Installation Stage Roles and Relationships
Operations and Maintenance Stage Roles and Relationships
(hide)
| Source | Destination | Role/Relationship |
|---|---|---|
| Driver | Roadway Owner | Expectation of Roadway Condition Management |
| Driver | Vehicle | Operates |
| Emissions Management Center Maintainer | Emissions Management Center | Maintains |
| Emissions Management Center Manager | Emissions Management Center | Manages |
| Emissions Management Center Manager | Emissions Management Operator | System Usage Agreement |
| Emissions Management Center Owner | Emissions Management Center Maintainer | System Maintenance Agreement |
| Emissions Management Center Owner | Emissions Management Center Manager | Operations Agreement |
| Emissions Management Center Owner | Traffic Management Center Maintainer | Maintenance Data Exchange Agreement |
| Emissions Management Center Owner | Traffic Management Center Owner | Information Provision Agreement |
| Emissions Management Center Owner | Traffic Management Center User | Service Usage Agreement |
| Emissions Management Center Owner | Traffic Operations Personnel | Application Usage Agreement |
| Emissions Management Center Supplier | Emissions Management Center Owner | Warranty |
| Emissions Management Operator | Emissions Management Center | Operates |
| ITS Roadway Equipment Maintainer | ITS Roadway Equipment | Maintains |
| ITS Roadway Equipment Manager | ITS Roadway Equipment | Manages |
| ITS Roadway Equipment Manager | Maint and Constr Field Personnel | System Usage Agreement |
| ITS Roadway Equipment Owner | Emissions Management Center Maintainer | Maintenance Data Exchange Agreement |
| ITS Roadway Equipment Owner | Emissions Management Center Owner | Information Provision Agreement |
| ITS Roadway Equipment Owner | Emissions Management Center User | Service Usage Agreement |
| ITS Roadway Equipment Owner | Emissions Management Operator | Application Usage Agreement |
| ITS Roadway Equipment Owner | ITS Roadway Equipment Maintainer | System Maintenance Agreement |
| ITS Roadway Equipment Owner | ITS Roadway Equipment Manager | Operations Agreement |
| ITS Roadway Equipment Owner | Traffic Management Center Maintainer | Maintenance Data Exchange Agreement |
| ITS Roadway Equipment Owner | Traffic Management Center Owner | Information Exchange Agreement |
| ITS Roadway Equipment Owner | Traffic Management Center User | Service Usage Agreement |
| ITS Roadway Equipment Owner | Traffic Operations Personnel | Application Usage Agreement |
| ITS Roadway Equipment Supplier | ITS Roadway Equipment Owner | Warranty |
| Maint and Constr Field Personnel | ITS Roadway Equipment | Operates |
| Roadway Maintainer | Roadway Environment | Maintains |
| Roadway Manager | Roadway Environment | Manages |
| Roadway Owner | Roadway Maintainer | System Maintenance Agreement |
| Roadway Owner | Roadway Manager | Operations Agreement |
| Traffic Management Center Maintainer | Traffic Management Center | Maintains |
| Traffic Management Center Manager | Traffic Management Center | Manages |
| Traffic Management Center Manager | Traffic Operations Personnel | System Usage Agreement |
| Traffic Management Center Owner | ITS Roadway Equipment Maintainer | Maintenance Data Exchange Agreement |
| Traffic Management Center Owner | ITS Roadway Equipment Owner | Information Exchange Agreement |
| Traffic Management Center Owner | ITS Roadway Equipment User | Service Usage Agreement |
| Traffic Management Center Owner | Maint and Constr Field Personnel | Application Usage Agreement |
| Traffic Management Center Owner | Traffic Management Center Maintainer | System Maintenance Agreement |
| 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 Maintainer | Vehicle | Maintains |
| Vehicle Manager | Driver | System Usage Agreement |
| Vehicle Manager | Vehicle | Manages |
| Vehicle Owner | Vehicle Maintainer | System Maintenance Agreement |
| Vehicle Owner | Vehicle Manager | Operations Agreement |
| Vehicle Supplier | Vehicle Owner | Warranty |
Functional
This service package includes the following Functional View PSpecs:
Physical
The physical diagram can be viewed in SVG or PNG format and the current format is SVG.SVG Diagram
PNG Diagram
Includes Physical Objects:
| Physical Object | Class | Description |
|---|---|---|
| Driver | Vehicle | The 'Driver' represents the person that operates a vehicle on the roadway. Included are operators of private, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The Driver originates driver requests and receives driver information that reflects the interactions which might be useful to all drivers, regardless of vehicle classification. Information and interactions which are unique to drivers of a specific vehicle type (e.g., fleet interactions with transit, commercial, or emergency vehicle drivers) are covered by separate objects. |
| Emissions Management Center | Center | The 'Emissions Management Center' provides the capabilities for air quality managers to monitor and manage air quality. These capabilities include collecting emissions data from distributed emissions sensors (included in ITS Roadway Equipment) and directly from connected vehicles. The sensors monitor general air quality and also monitor the emissions of individual vehicles on the roadway. The measures are collected, processed, and used to support environmental monitoring applications. |
| 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. |
| MMV User | Personal | The 'MMV User' represents the person that operates a micromobility vehicle (MMV). Included are cyclists and operators of other low-powered mobility devices such as e-scooters, powered wheelchairs, and power assisted bicycles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The MMV User participates in ITS services that support safe, shared use of the transportation network by motorized and non-motorized transportation modes. Representing those using non-motorized travel modes, and in particular bicyclists that sometimes share motor vehicle lanes, these MMV users provide input (e.g. a call signal requesting right of way at an intersection) and may be detected by ITS services to improve safety. The MMV User originates requests and receives information that reflects the interactions which might be useful to all users, regardless of vehicle type. |
| Pedestrian | Personal | The 'Pedestrian' represents a person traveling on foot. Pedestrians participate in ITS services that support safe, shared use of the transportation network. Included are visually impaired travelers who travel through portions of the transportation network and interact with ITS systems. They provide input (e.g. a call signal requesting right of way at an intersection) and may be detected by ITS services to improve safety |
| Roadway Environment | Field | 'Roadway Environment' represents the physical condition and geometry of the road surface, markings, signs, and other objects on or near the road surface. It also represents the environmental conditions immediately surrounding the roadway. The roadway environment must be sensed and interpreted to support automated vehicle services. Surrounding conditions may include fog, ice, snow, rain, wind, etc. which will influence the way in which a vehicle can be safely operated on the roadway. The roadway environment must be monitored to enable corrective action and information dissemination regarding roadway conditions which may adversely affect travel. Infrastructure owner/operators can improve the roadway environment to improve the performance and accuracy of vehicle-based sensors that must sense and interpret this environment. Improvements could include changes in the shape, size, design, and materials used in signs, pavement markings, and other road features. |
| 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 | Vehicle | This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles (including motorcycles), commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle 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. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. 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. |
| Vehicle Characteristics | Vehicle | 'Vehicle Characteristics' represents the external view of individual vehicles of any class from cars and light trucks up to large commercial vehicles and down to micromobility vehicles (MMVs). It includes vehicle physical characteristics such as height, width, length, weight, and other properties (e.g., magnetic properties, number of axles, occupants, emissions) of individual vehicles that can be sensed and measured or classified. This physical object represents the physical properties of vehicles that can be sensed by vehicle-based or infrastructure-based sensors to support vehicle automation and traffic sensor systems. The analog properties provided by this terminator represent the sensor inputs that are used to detect and assess vehicle(s) within the sensor's range to support safe AV operation and/or responsive and safe traffic management. |
Includes Functional Objects:
| Functional Object | Description | Physical Object |
|---|---|---|
| Emissions Connected Vehicle Monitoring | 'Emissions Connected Vehicle Monitoring' collects emissions data reported by passing vehicles and uses this data to support air quality management and planning. Coordination with traffic management supports air quality-responsive management of traffic. | Emissions Management Center |
| Emissions Data Management | 'Emissions Data Management' collects and stores air quality and vehicle emissions information by remotely monitoring and controlling area wide and point sensors. General air quality measures are distributed as general traveler information and also may be used in demand management programs. Collected roadside emissions are analyzed and used to detect, identify, and notify concerned parties regarding vehicles that exceed emissions standards. | Emissions Management Center |
| Roadway Basic Surveillance | 'Roadway Basic Surveillance' monitors traffic conditions using fixed equipment such as loop detectors and CCTV cameras. | ITS Roadway Equipment |
| Roadway Emissions Monitoring | 'Roadway Emissions Monitoring' monitors emissions and general air quality and communicates the collected information back to the Emissions Management Center where it can be monitored, analyzed, and used. This functional object supports point monitoring of individual vehicle emissions as well as general monitoring of standard air quality measures. | ITS Roadway Equipment |
| Roadway Environmental Monitoring | 'Roadway Environmental Monitoring' measures environmental conditions and communicates the collected information back to a center where it can be monitored and analyzed or to other field devices to support communications to vehicles. A broad array of weather and road surface information may be collected. Weather conditions that may be measured include temperature, wind, humidity, precipitation, and visibility. Surface and sub-surface sensors can measure road surface temperature, moisture, icing, salinity, and other metrics. | ITS Roadway Equipment |
| Roadway Field Management Station Operation | 'Roadway Field Management Station Operation' supports direct communications between field management stations and the local field equipment under their control. | ITS Roadway Equipment |
| Roadway Signal Control | 'Roadway Signal Control' includes the field elements that monitor and control signalized intersections. It includes the traffic signal controllers, detectors, conflict monitors, signal heads, and other ancillary equipment that supports traffic signal control. It also includes field masters, and equipment that supports communications with a central monitoring and/or control system, as applicable. The communications link supports upload and download of signal timings and other parameters and reporting of current intersection status. It represents the field equipment used in all levels of traffic signal control from basic actuated systems that operate on fixed timing plans through adaptive systems. It also supports all signalized intersection configurations, including those that accommodate pedestrians. In advanced, future implementations, environmental data may be monitored and used to support dilemma zone processing and other aspects of signal control that are sensitive to local environmental conditions. | ITS Roadway 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 Roadway Equipment Monitoring | 'TMC Roadway Equipment Monitoring' monitors the operational status of field equipment and detects failures. It presents field equipment status to Traffic Operations Personnel and reports failures to the Maintenance and Construction Management Center. It tracks the repair or replacement of the failed equipment. The entire range of ITS field equipment may be monitored including sensors (traffic, infrastructure, environmental, security, speed, etc.) and devices (highway advisory radio, dynamic message signs, automated roadway treatment systems, barrier and safeguard systems, cameras, traffic signals and override equipment, ramp meters, beacons, security surveillance equipment, etc.). | Traffic Management Center |
| TMC Signal Control | 'TMC Signal Control' provides the capability for traffic managers to monitor and manage the traffic flow at signalized intersections. This capability includes analyzing and reducing the collected data from traffic surveillance equipment and developing and implementing control plans for signalized intersections. Control plans may be developed and implemented that coordinate signals at many intersections under the domain of a single Traffic Management Center and are responsive to traffic conditions and adapt to support incidents, preemption and priority requests, pedestrian crossing calls, etc. | Traffic Management Center |
| Vehicle Basic Safety Communication | 'Vehicle Basic Safety Communication' exchanges current vehicle characteristics, location, and motion (including past and intended maneuver) information with other vehicles in the vicinity and the infrastructure, 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. 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 coordinate maneuvers and may, in addition to warning the driver, provide collision warning information to support automated control functions that can support control intervention. This object can also support broadcasting other vehicle information required for passing through a specific roadway segment such as variables that describe vehicle's characteristics and parameters, driver's preferences in terms of vehicle motion and behavior, etc. | Vehicle |
Includes Information Flows:
| Information Flow | Description |
|---|---|
| crossing call | Non-motorized user request to cross the roadway. This is an overt request from a pedestrian, micromobility vehicle user (e.g., cyclist), or other vulnerable road user. This overt request may be a physical button push or hovering or gesturing in the vicinity of the button that supports contactless activation. |
| crossing permission | Information provided to guide and warn pedestrians, micromobility vehicle users (e.g., cyclists), and other crosswalk users. It includes crossing request acknowledgment, current crossing permission, crossing time remaining, and real-time warnings of safety threats. |
| driver information | Regulatory, warning, guidance, and other information provided to the driver to support safe and efficient vehicle operation. |
| driver input | Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands. |
| driver updates | Information provided to the driver including visual displays, audible information and warnings, and haptic feedback. The updates inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment. |
| environmental conditions | Current road conditions (e.g., surface temperature, subsurface temperature, moisture, icing, treatment status) and surface weather conditions (e.g., air temperature, wind speed, precipitation, visibility) that are measured by environmental sensors. |
| environmental sensor control | Data used to configure and control environmental sensors. |
| environmental sensor data | Current road conditions (e.g., surface temperature, subsurface temperature, moisture, icing, treatment status) and surface weather conditions (e.g., air temperature, wind speed, precipitation, visibility) as measured and reported by fixed and/or mobile environmental sensors. Operational status of the sensors is also included. |
| mobile source emissions data | Measured and/or estimated emissions at point locations from mobile sources including cars and light trucks, heavy trucks and buses. Where applicable, this flow may also include emissions measures or estimates from non-road engines and portable equipment at the location. |
| right-of-way request notification | Notice that a request has occurred for signal prioritization, signal preemption, pedestrian call, multi-modal crossing activation, or other source for right-of-way. |
| signal control commands | Control of traffic signal controllers or field masters including clock synchronization. |
| signal control device configuration | Data used to configure traffic signal control equipment including local controllers and system masters. |
| signal control plans | Traffic signal timing parameters including minimum green time and interval durations for basic operation and cycle length, splits, offset, phase sequence, etc. for coordinated systems. |
| signal control status | Operational and status data of traffic signal control equipment including operating condition and current indications. |
| signal fault data | Faults reported by traffic signal control equipment. |
| signal system configuration | Data used to configure traffic signal systems including configuring control sections and mode of operation (time based or traffic responsive). |
| 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. |
| vehicle characteristics | The physical or visible characteristics of individual vehicles that can be used to detect, classify, and monitor vehicles and imaged to uniquely identify vehicles and characterize their performance (e.g., speed, occupants, emissions). |
| vehicle emissions data | Measured emissions of specific vehicles comprised of exhaust pollutants including hydrocarbons, carbon monoxide, and nitrogen oxides. |
Goals and Objectives
Associated Planning Factors and Goals
| Planning Factor | Goal |
|---|
Associated Objective Categories 
| Objective Category |
|---|
Associated Objectives and Performance Measures
| Objective | Performance Measure |
|---|
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 | ||
|---|---|---|---|---|
Related Sources
| Document Name | Version | Publication Date |
|---|---|---|
| None |
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 |
| Emissions Management Center | ||||
| ITS Roadway Equipment | ||||
| Roadway Environment | ||||
| Traffic Management Center | ||||
| Vehicle | ||||
| Vehicle Characteristics | ||||
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 | |||
| Driver | Vehicle | driver input | Moderate | High | High |
| Data included in this flow may include origin and destination information, which should be protected from other's viewing as it may compromise the driver's privacy. | Commands from from the driver to the vehicle must be correct or the vehicle may behave in an unpredictable and possibly unsafe manner | Commands must always be able to be given or the driver has no control. | |||
| Emissions Management Center | Traffic Management Center | mobile source emissions data | Low | Moderate | Moderate |
| Probably not sensitive information, no harm in this data being captured by unintended party if this flow does not correlate specific vehicles with any emissions data. If specific vehicles are associated with data, this would be MODERATE. | At least some guarantee of correctness should be had with this data. It could be used to modify transit/traffic strategies over a large area ("its a code ORANGE day out there, don't run") that change behavior for a large number of people. | While the source flows from RSEs are considered LOW, this is an aggregated flow, so the impact of an outage is larger. If this flow exists, it is probably used for decision-making and any loss of this flow has an impact. | |||
| ITS Roadway Equipment | Driver | driver information | Not Applicable | High | Moderate |
| This data is sent to all drivers and is also directly observable, by design. | This is the primary signal trusted by the driver to decide whether to go through the intersection and what speed to go through the intersection at; if it’s wrong, accidents could happen. | If the lights are out you have to get a policeman to direct traffic – expensive and inefficient and may cause a cascading effect due to lack of coordination with other intersections. | |||
| ITS Roadway Equipment | Emissions Management Center | vehicle emissions data | Moderate | Moderate | Low |
| Contains vehicle identity, which should be protected from casual viewing, and maps that to various emissions parameters. As this may imply legal issues (over-emitting etc.), the data should be kept confidential to protect the vehicle owner. | As this contains information that could be used to grant permitting (emissions passing) or issue penalites (over-emitting), a corruption of this data could result in the wrong action being taken, revenue lost or inappropriately gained, permit incorrectly granted or denied. | Could be MODERATE for those areas where emissions are high priority items. Generally LOW given that most emissions testing is done in person now. As systems come to rely on remote sensing, this may become MODERATE. | |||
| ITS Roadway Equipment | MMV User | crossing permission | Not Applicable | High | Low |
| This data is intentionally transmitted to everyone via a broadcast. | Although pedestrians have a responsibility to make sure the road is safe before they cross, they may react instinctively to incorrect information and be led to cross at unsafe times if they get incorrect information. Also, if the traffic signals are wrong and an accident happens, the pedestrian involved could sue, causing financial loss and other undesirable outcomes. | It is easy to tell whether this information flow is available and pedestrians are used to using crosswalks that do not provide this service. | |||
| ITS Roadway Equipment | Pedestrian | crossing permission | Not Applicable | High | Low |
| This data is intentionally transmitted to everyone via a broadcast. | Although pedestrians have a responsibility to make sure the road is safe before they cross, they may react instinctively to incorrect information and be led to cross at unsafe times if they get incorrect information. Also, if the traffic signals are wrong and an accident happens, the pedestrian involved could sue, causing financial loss and other undesirable outcomes. | It is easy to tell whether this information flow is available and pedestrians are used to using crosswalks that do not provide this service. | |||
| ITS Roadway Equipment | Traffic Management Center | environmental sensor data | Low | Moderate | Moderate |
| Little to no impact if this data is observed | info should be correct to determine safe speeds etc.; DISC: WYO believes this to be HIGH | Updates are desireable but slightly outdated information will not be catastrophic. | |||
| ITS Roadway Equipment | Traffic Management Center | right-of-way request notification | Low | Moderate | Moderate |
| This can be reasonably guessed based on observing the ITS RE’s environment. It is obvious when a bus approaches an intersection. | Invalid messages could lead to an unauthorized user gaining signal priority at an intersection. This could also be used to delay traffic, which could lead to a financial impact on the community. However, the traffic signal will have controls in place to ensure that it does not display an illegal configuration (such as green in every direction). | Even if all of the Right-of-way Requests are not passed along from an ITS RE, the intersection will still operate as normal. There are other existing methods to assist a right-of-way requesting vehicle safely traveling through an intersection, such as lights and sirens, which prevent this from being a HIGH. DISC: THEA and NYC believe this to be LOW: "not necessary for the app to work; can cope with not having immediately available data" | |||
| ITS Roadway Equipment | Traffic Management Center | signal control status | Low | High | Moderate |
| The current conditions of an ITS RE are completely observable, by design. | This influences the TMC response to a right-of-way request. It should be as accurate as the right-of-way request themselves. For some applications (ISIG) this need only be moderate. Per THEA: info needs to be accurate and should not be tampered to enable effective monitoring and control by the TMC. DISC: THEA believes this to be MODERATE: "info needs to be accurate and should not be tampered to enable effective monitoring and control by the TMC; should be as accurate as the right of way request". NYC:TMC doesn’t play an active role in this application, i.e. even if the information contained in this flow were incorrect, it is unlikely to affect the outcome of this application one way or the other. On some applications NYC has this MODERATE though. RES: This value can obviously change a lot depending on the application context. | The TMC will need the current status of the ITS RE in order to make an educated decision. If it is unavailable, the system is unable to operate. However, a few missed messages will not have a catastrophic impact. From NYC: TMC doesn’t play an active role in this application, i.e. even if it is unavailable, it is unlikely to affect the outcome of this application one way or the other. RES: This value can change a lot depending on the application context. | |||
| ITS Roadway Equipment | Traffic Management Center | signal fault data | Low | High | Moderate |
| The current conditions of an ITS RE are completely observable, by design. | 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. | |||
| 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. | |||
| MMV User | ITS Roadway Equipment | crossing call | Not Applicable | High | Low |
| The "Not Applicable" group includes information flows that do not actually carry information; for example, flows that represent the physical environment. | Although pedestrians have a responsibility to make sure the road is safe before they cross, and should ensure that they are detected by pedestrian detection systems, they may not always be detected and be led to cross at unsafe times if the ITS RE obtains incorrect information. | It is easy to tell whether this information flow is available and pedestrians are used to using crosswalks that do not provide this service. | |||
| Pedestrian | ITS Roadway Equipment | crossing call | Not Applicable | High | Low |
| The "Not Applicable" group includes information flows that do not actually carry information; for example, flows that represent the physical environment. | Although pedestrians have a responsibility to make sure the road is safe before they cross, and should ensure that they are detected by pedestrian detection systems, they may not always be detected and be led to cross at unsafe times if the ITS RE obtains incorrect information. | It is easy to tell whether this information flow is available and pedestrians are used to using crosswalks that do not provide this service. | |||
| Roadway Environment | ITS Roadway Equipment | environmental conditions | Not Applicable | Low | Low |
| Sensor-based information flows by definition have no confidentiality concerns. | While typically security concerns related to sensing ignored, if considered this would be LOW, as the obfuscation or failure of any given environmental sensor is likely to be overcome by the mass of data necessary to draw environmental concluisions. | While typically security concerns related to sensing ignored, if considered this would be LOW, as the obfuscation or failure of any given environmental sensor is likely to be overcome by the mass of data necessary to draw environmental concluisions. | |||
| Traffic Management Center | ITS Roadway Equipment | environmental sensor 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 | 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 environmental sensor data received and be detrimental to operations; DISC: WYO believes this may be HIGH for some applications | 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 THEAwant 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 | ITS Roadway Equipment | signal control commands | Moderate | High | Moderate |
| 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: NYC believes this to be LOW: "The result of this will be directly observable." | Invalid messages could lead to an unauthorized user gaining control of an intersection. This could also be used to bring traffic to a standstill, which could lead to a large financial impact on the community. DISC: NYC believes this to be MODERATE: The signal timing is critical to the intersection operation; incorrect signal timing can lead to significant congestion and unreliable operation; while unsafe operation is controlled by the cabinet monitoring system, attackers could “freeze” the signal or call a preemption. RES: This will vary depending on the application and implementation. | These messages are important to help with preemption and signal priority applications. Without them, these applications mayl not work. However, if these signals are not received, the ITS RE will continue to function using its default configuration. The TMC should have an acknowledgement of the receipt of a message. DISC: NYC blieves this to be LOW: TMC doesn’t play an active role in this application, i.e. even if it is unavailable, it is unlikely to affect the outcome of this application one way or the other. RES: This will vary depending on the application and implementation. | |||
| Traffic Management Center | ITS Roadway Equipment | signal control device configuration | Moderate | High | Moderate |
| 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 believes this to be LOW: "encrypted, authenticated, proprietary; however will not cause harm if seen, traffic light information is visible." | 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: proprietary info that should not be tampered with; includes local controllers and system masters; tampering with configurations could cause delays along with major safety issues | 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: should be timely and readily available; however, should be able to function using a default configuration | |||
| Traffic Management Center | ITS Roadway Equipment | signal control plans | Moderate | High | Moderate |
| 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 believes this to be LOW: "encrypted, authenticated, proprietary; but the result is directly observable from traffic lights | 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: proprietary info that should not be tampered with; tampering with these plans could cause delays along with major safety issues | 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: should be timely and readily available; coordinated with other systems; however, should be able to function using a default configuration | |||
| Traffic Management Center | ITS Roadway Equipment | signal system configuration | Low | High | Moderate |
| encrypted, authenticated, proprietary; however, the result is directly observable from traffic lights | proprietary info that should not be tampered with; data used to configure traffic signal systems; could cause significant delays and traffic issues if compromised | should be readily available; configurations can be time | |||
| 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 | Driver | driver updates | Not Applicable | Moderate | Moderate |
| This data is informing the driver about the safety of a nearby area. It should not contain anything sensitive, and does not matter if another person can observe it. | This is the information that is presented to the driver. If they receive incorrect information, they may act in an unsafe manner. However, there are other indicators that would alert them to any hazards, such as an oncoming vehicle or crossing safety lights. | If this information is not made available to the driver, then the system has not operated correctly. | |||
| Vehicle Characteristics | ITS Roadway Equipment | vehicle characteristics | |||
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. These pages can be accessed directly from the SVG diagram(s) located on the Physical tab, by clicking on each information flow line on the diagram.
| Name | Title | Physical Object |
|---|---|---|
| ITE 5201 ATC | Advanced Transportation Controller | ITS Roadway Equipment |
| ITE 5202 ATC Model 2070 | Model 2070 Controller Standard | ITS Roadway Equipment |
| ITE 5301 ATC ITS Cabinet | Intelligent Transportation System Standard Specification for Roadside Cabinets | ITS Roadway Equipment |
| ITE 5401 ATC API | Application Programming Interface Standard for the Advanced Transportation Controller | ITS Roadway Equipment |
| NEMA TS 8 Cyber and Physical Security | Cyber and Physical Security for Intelligent Transportation Systems | Emissions Management Center |
| ITS Roadway Equipment | ||
| Traffic Management Center | ||
| NEMA TS2 Traffic Controller Assemblies | Traffic Controller Assemblies with NTCIP Requirements | ITS Roadway Equipment |
System Requirements
| No System Requirements |