< < VS07 : VS08 : VS09 > >

VS08: Queue Warning

This service package utilizes connected vehicle technologies, including vehicle-to-infrastructure (V2I) and vehicle-to-vehicle (V2V) communications, to enable vehicles within the queue event to automatically broadcast their queued status information (e.g., rapid deceleration, disabled status, lane location) to nearby upstream vehicles and to centers (such as the TMC). The infrastructure will broadcast queue warnings to vehicles in order to minimize or prevent rear-end or other secondary collisions. This service package is not intended to operate as a crash avoidance system. In contrast to such systems, this service package will engage well in advance of any potential crash situation, providing messages and information to the driver in order to minimize the likelihood of his needing to take crash avoidance or mitigation actions later. It performs two essential tasks: queue determination (detection and/or prediction) and queue information dissemination using vehicle-based, infrastructure-based, or hybrid solutions.

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

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations and Maintenance Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
Basic Vehicle Maintainer Basic Vehicle Maintains
Basic Vehicle Manager Basic Vehicle Manages
Basic Vehicle Manager Driver System Usage Agreement
Basic Vehicle Owner Basic Vehicle Maintainer System Maintenance Agreement
Basic Vehicle Owner Basic Vehicle Manager Operations Agreement
Basic Vehicle Owner Driver Application Usage Agreement
Basic Vehicle Owner Driver Vehicle Operating Agreement
Basic Vehicle Owner Vehicle Maintainer Maintenance Data Exchange Agreement
Basic Vehicle Owner Vehicle Owner Expectation of Data Provision
Basic Vehicle Owner Vehicle User Service Usage Agreement
Basic Vehicle Supplier Basic Vehicle Owner Warranty
Connected Vehicle Roadside Equipment Maintainer Connected Vehicle Roadside Equipment Maintains
Connected Vehicle Roadside Equipment Manager Connected Vehicle Roadside Equipment Manages
Connected Vehicle Roadside Equipment Owner Connected Vehicle Roadside Equipment Maintainer System Maintenance Agreement
Connected Vehicle Roadside Equipment Owner Connected Vehicle Roadside Equipment Manager Operations Agreement
Connected Vehicle Roadside Equipment Owner Driver Application Usage Agreement
Connected Vehicle Roadside Equipment Owner ITS Roadway Equipment Maintainer Maintenance Data Exchange Agreement
Connected Vehicle Roadside Equipment Owner ITS Roadway Equipment Owner Information Exchange and Action Agreement
Connected Vehicle Roadside Equipment Owner ITS Roadway Equipment User Service Usage Agreement
Connected Vehicle Roadside Equipment Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Connected Vehicle Roadside Equipment Owner Traffic Management Center Owner Information Exchange and Action Agreement
Connected Vehicle Roadside Equipment Owner Traffic Management Center User Service Usage Agreement
Connected Vehicle Roadside Equipment Owner Traffic Operations Personnel Application Usage Agreement
Connected Vehicle Roadside Equipment Owner Vehicle Maintainer Maintenance Data Exchange Agreement
Connected Vehicle Roadside Equipment Owner Vehicle Owner Information Exchange and Action Agreement
Connected Vehicle Roadside Equipment Owner Vehicle User Service Usage Agreement
Connected Vehicle Roadside Equipment Supplier Connected Vehicle Roadside Equipment Owner Warranty
Driver Basic Vehicle Operates
Driver Roadway Owner Expectation of Roadway Condition Management
Driver Vehicle Operates
ITS Roadway Equipment Maintainer ITS Roadway Equipment Maintains
ITS Roadway Equipment Manager ITS Roadway Equipment Manages
ITS Roadway Equipment Owner Connected Vehicle Roadside Equipment Maintainer Maintenance Data Exchange Agreement
ITS Roadway Equipment Owner Connected Vehicle Roadside Equipment Owner Information Exchange and Action Agreement
ITS Roadway Equipment Owner Connected Vehicle Roadside Equipment User Service 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 and Action 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
Other Traffic Management Centers Maintainer Other Traffic Management Centers Maintains
Other Traffic Management Centers Manager Other Traffic Management Centers Manages
Other Traffic Management Centers Owner Other Traffic Management Centers Maintainer System Maintenance Agreement
Other Traffic Management Centers Owner Other Traffic Management Centers Manager Operations Agreement
Other Traffic Management Centers Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Other Traffic Management Centers Owner Traffic Management Center Owner Information Exchange Agreement
Other Traffic Management Centers Owner Traffic Management Center User Service Usage Agreement
Other Traffic Management Centers Owner Traffic Operations Personnel Application Usage Agreement
Other Traffic Management Centers Supplier Other Traffic Management Centers Owner Warranty
Other Vehicles Maintainer Other Vehicles Maintains
Other Vehicles Manager Other Vehicles Manages
Other Vehicles Owner Driver Application Usage Agreement
Other Vehicles Owner Driver Vehicle Operating Agreement
Other Vehicles Owner Other Vehicles Maintainer System Maintenance Agreement
Other Vehicles Owner Other Vehicles Manager Operations Agreement
Other Vehicles Owner Vehicle Maintainer Maintenance Data Exchange Agreement
Other Vehicles Owner Vehicle Owner Expectation of Data Provision
Other Vehicles Owner Vehicle User Service Usage Agreement
Other Vehicles Supplier Other Vehicles Owner Warranty
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 Connected Vehicle Roadside Equipment Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Connected Vehicle Roadside Equipment Owner Information Provision Agreement
Traffic Management Center Owner Connected Vehicle Roadside Equipment User Service Usage Agreement
Traffic Management Center Owner ITS Roadway Equipment Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner ITS Roadway Equipment Owner Information Provision Agreement
Traffic Management Center Owner ITS Roadway Equipment User Service Usage Agreement
Traffic Management Center Owner Other Traffic Management Centers Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Other Traffic Management Centers Owner Information Exchange Agreement
Traffic Management Center Owner Other Traffic Management Centers User Service 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 Owner Transportation Information Center Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Transportation Information Center Owner Information Provision Agreement
Traffic Management Center Owner Transportation Information Center User Service Usage Agreement
Traffic Management Center Supplier Traffic Management Center Owner Warranty
Traffic Operations Personnel Traffic Management Center Operates
Transportation Information Center Maintainer Transportation Information Center Maintains
Transportation Information Center Manager Transportation Information Center Manages
Transportation Information Center Owner Driver Application Usage Agreement
Transportation Information Center Owner Transportation Information Center Maintainer System Maintenance Agreement
Transportation Information Center Owner Transportation Information Center Manager Operations Agreement
Transportation Information Center Owner Vehicle Maintainer Maintenance Data Exchange Agreement
Transportation Information Center Owner Vehicle Owner Information Provision Agreement
Transportation Information Center Owner Vehicle User Service Usage Agreement
Transportation Information Center Supplier Transportation Information Center Owner Warranty
Vehicle Characteristics Maintainer Vehicle Characteristics Maintains
Vehicle Characteristics Manager Vehicle Characteristics Manages
Vehicle Characteristics Owner Vehicle Characteristics Maintainer System Maintenance Agreement
Vehicle Characteristics Owner Vehicle Characteristics Manager Operations Agreement
Vehicle Characteristics Supplier Vehicle Characteristics Owner Warranty
Vehicle Maintainer Vehicle Maintains
Vehicle Manager Driver System Usage Agreement
Vehicle Manager Vehicle Manages
Vehicle Owner Basic Vehicle Maintainer Maintenance Data Exchange Agreement
Vehicle Owner Basic Vehicle Owner Expectation of Data Provision
Vehicle Owner Basic Vehicle User Service Usage Agreement
Vehicle Owner Connected Vehicle Roadside Equipment Maintainer Maintenance Data Exchange Agreement
Vehicle Owner Connected Vehicle Roadside Equipment Owner Expectation of Data Provision
Vehicle Owner Connected Vehicle Roadside Equipment User Service Usage Agreement
Vehicle Owner Driver Application Usage Agreement
Vehicle Owner Driver Vehicle Operating Agreement
Vehicle Owner Other Vehicles Maintainer Maintenance Data Exchange Agreement
Vehicle Owner Other Vehicles Owner Expectation of Data Provision
Vehicle Owner Other Vehicles User Service Usage Agreement
Vehicle Owner Transportation Information Center Maintainer Maintenance Data Exchange Agreement
Vehicle Owner Transportation Information Center Owner Expectation of Data Provision
Vehicle Owner Transportation Information Center User Service Usage Agreement
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 Object Functional Object PSpec Number PSpec Name
Connected Vehicle Roadside Equipment RSE Environmental Monitoring 1.1.1.6 Collect Vehicle Roadside Safety Data
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
1.2.7.7 Process Vehicle Safety and Environmental Data for Output
1.5.10 Collect Vehicle Emissions Messages
1.5.12 Manage Eco Roadway Usage in Roadway
6.7.3.3 Provide Short Range Traveler Information
RSE Queue Warning 1.1.2.6 Process Collected Vehicle Safety Data
1.2.7.4 Process In-vehicle Signage Data
1.2.7.7 Process Vehicle Safety and Environmental Data for Output
6.7.3.3 Provide Short Range Traveler Information
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.3 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 Environmental Monitoring 1.1.1.3 Process Environmental Sensor Data
1.2.7.1 Process Indicator Output Data for Roads
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.2.7.9 Process Roadway Information Data
9.2.3.6 Collect Field Equipment Status for Repair
9.3.3.1 Collect Vehicle Speed
Roadway Warning 1.2.7.12 Control Roadway Warning 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 Roadway Warning 1.1.4.2 Provide Traffic Operations Personnel Traffic Data Interface
1.2.4.7 Manage Roadway Warning System
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
TIC Traffic Control Dissemination 6.2.2 Collect Traffic Data
6.5.1 Provide Broadcast Data Interface
Vehicle 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.1 Process General 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.2 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.1 Process General 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 Provide Driver with Personal Travel Information
6.7.3.2 Provide Driver Information Interface
Vehicle Queue Warning 3.1.1 Produce Collision and Crash Avoidance Data
3.1.3 Process Vehicle On-board Data
3.2.3.3 Process Data for Vehicle Actuators
3.3.1 Provide Communications Function
6.7.3.2 Provide Driver Information Interface
Vehicle Situation Data Monitoring 3.1.3 Process Vehicle On-board Data
Vehicle Traveler Information Reception 3.1.3 Process Vehicle On-board Data
3.1.4 Communicate with Remote Vehicles
3.2.3.3 Process Data for Vehicle Actuators
6.7.1.3 Process Vehicle Location Data
6.7.1.4 Update Vehicle Navigable Map Database
6.7.3.1 Provide Driver with Personal Travel Information
6.7.3.2 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
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 (i.e., Roadside Units (RSUs)) equipped with short range wireless (SRW) communications technology, as well as any other supporting equipment that leverage the RSU and are not described by other objects (e.g., a local roadside processor). CVRSE are used to send messages to, and receive messages from, nearby vehicles and personal devices equipped with compatible communications technology. 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.
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.
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.
Other Traffic Management Centers Center Representing another Traffic Management Center, 'Other Traffic Management Centers' is intended to provide a source and destination for information exchange between peer (e.g. inter-regional) traffic management functions. It enables traffic management activities to be coordinated across different jurisdictional areas.
Other Vehicles Vehicle 'Other Vehicle OBEs' represents other connected vehicles that are communicating with the host vehicle. This includes all connected motorized vehicles including passenger cars, trucks, and motorcycles and specialty vehicles (e.g., maintenance vehicles, transit vehicles) that also include the basic 'Vehicle OBE' functionality that supports V2V communications. This object provides a source and destination for information transfers between connected vehicles. The host vehicle on-board equipment, represented by the Vehicle OBE physical object, sends information to, and receives information from the Other Vehicle OBEs to model all connected vehicle V2V communications in ARC-IT.
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.
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 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, 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) 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
Roadway Basic Surveillance 'Roadway Basic Surveillance' monitors traffic conditions using fixed equipment such as loop detectors and CCTV cameras. 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 Warning 'Roadway Warning' includes the field equipment used to warn drivers approaching hazards on a roadway. Warnings may be generated in response to roadway weather conditions, road surface conditions, traffic conditions including queues, obstacles or animals in the roadway, and any other transient events that can be sensed. The equipment monitors traffic and roadway conditions and may send data to a Traffic Management Center for processing or may process it to determine when a warning should be issued. When it is determined that a warning should be issued, the equipment is used to alert approaching drivers via dynamic warning signs, flashing lights, in-vehicle messages, etc. ITS Roadway Equipment
RSE Environmental Monitoring 'RSE Environmental Monitoring' collects environmental situation (probe) data from passing vehicles that are equipped with short range communications capability. The collected data includes current environmental conditions as measured by on-board sensors (e.g., ambient temperature and precipitation measures), current status of vehicle systems that can be used to infer environmental conditions (e.g., status of lights, wipers, ABS, and traction control systems), and emissions measures reported by the vehicle. The functional object collects the provided data, aggregates and filters the data based on provided configuration parameters, and sends the collected information back to a center for processing and distribution. This functional object may also process the collected data locally and issue short-term road weather advisories for the road segment using short range communications. Connected Vehicle Roadside Equipment
RSE Queue Warning 'RSE Queue Warning' provides V2I communications to support queue warning systems. It monitors connected vehicles to identify and monitor queues in real-time and provides information to vehicles about upcoming queues, including downstream queues that are reported by the Traffic Management Center. 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
TIC Traffic Control Dissemination 'TIC Traffic Control Dissemination' disseminates intersection status, lane control information, special vehicle alerts, and other traffic control related information that is real-time or near real-time in nature and relevant to vehicles in a relatively local area on the road network. It collects traffic control information from Traffic Management and other Center(s) and disseminates the relevant information to vehicles and other mobile devices. Transportation Information Center
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 Warning 'TMC Roadway Warning' remotely monitors and controls the systems used to warn drivers approaching hazards on a roadway. It monitors data on roadway conditions from sensors in the field and generates warnings in response to roadway weather conditions, road surface conditions, traffic conditions including queues, obstacles or animals in the roadway, and any other transient events that can be sensed. 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, 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. Vehicle
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
Vehicle Queue Warning 'Vehicle Queue Warning' detects vehicle queues and reports queues to other vehicles using V2V communications and to the infrastructure using V2I communications. Vehicle-based queue warning builds on the exchange of vehicle location and motion and maneuvers that supports connected vehicle safety applications. This application also receives information about downstream queues using I2V communications. Individualized queue warnings and queue characteristics relevant to the vehicle are provided to the driver. Vehicle
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
Vehicle Traveler Information Reception 'Vehicle Traveler Information Reception' receives advisories, vehicle signage data, and other driver information of use to all types of vehicles and drivers and presents this information to the driver using in-vehicle equipment. Information presented may include fixed sign information, traffic control device status (e.g., signal phase and timing data), advisory and detour information, warnings of adverse road and weather conditions, travel times, and other driver information. Vehicle

Includes Information Flows:

Information Flow Description
collision warning information Information provided to support computer-based intervention of vehicle controls. Analogous to driver warnings, these are warnings issued to on-board control systems of an impending collision or other situation detected by the Vehicle OBE that may require control intervention.
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 update information Information provided to the driver-vehicle interface to inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment. The flow includes the information to be presented to the driver and associated metadata that supports processing, prioritization, and presentation by the DVI as visual displays, audible information and warnings, and/or haptic feedback.
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.
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.
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.
queue warning application information Information regarding formed or impending queues (location of the end of queue, estimated duration of the queue, and other descriptions of the queue condition) and recommendations for upstream vehicles including speed reduction, lane change, or diversion recommendations. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted.
queue warning application status Queue warning application status reported by the RSE. This includes current operational state and status of the RSE and a record of measured vehicle speeds and identified queues.
queue warning information Information regarding formed or impending queues (location of the end of queue, estimated duration of the queue, and other descriptions of the queue condition) and recommendations for upstream vehicles including speed reduction, lane change, or diversion recommendations.
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.
roadway characteristics Detectable or measurable road characteristics such as friction coefficient and general surface conditions, road geometry and markings, etc. These characteristics are monitored or measured by ITS sensors and used to support advanced vehicle safety and control and road maintenance capabilities.
roadway warning system control Information used to configure and control roadway warning systems.
roadway warning system status Current operating status of roadway warning systems.
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 image meta data Meta data that describes traffic images. Traffic images (video) are in another flow.
traffic images High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications. This flow includes the images. Meta data that describes the images is contained in another flow.
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 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.
vehicle control event Notification that the vehicle has performed an emergency maneuver or action that could impact the safety of surrounding vehicles. This includes hard braking and activation of traction/stability control systems or other actions that warrant immediate notification of surrounding vehicles. The information flow conveys the current vehicle location, path, and current control actions. This may also include the list of maneuvers includes lane changes/departures and overtaking/passing maneuvers.
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 Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size.
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 signage data In-vehicle signing data that augments regulatory, warning, and informational road signs and signals. The information provided would include static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., local traffic and road conditions, restrictions, vehicle requirements, work zones, detours, closures, advisories, and warnings).
vehicle signage local data Information provided by adjacent field equipment to support in-vehicle signing of dynamic information that is currently being displayed to passing drivers. This includes the dynamic information (e.g., local traffic and road conditions, work zone information, lane restrictions, detours, closures, advisories, parking availability, etc.) and control parameters that identify the desired timing, duration, and priority of the signage data.
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.
video surveillance control Information used to configure and control video surveillance systems.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal
A. Support the economic vitality of the metropolitan area, especially by enabling global competitiveness, productivity, and efficiency; Improve freight network
B. Increase the safety of the transportation system for motorized and nonmotorized users; Reduce fatalities and injuries
D. Increase the accessibility and mobility of people and for freight; Reduce congestion
E. Protect and enhance the environment, promote energy conservation, improve the quality of life, and promote consistency between transportation improvements and State and local planned growth and economic development patterns; Protect/Enhance the Environment
F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight; Enhance integration and connectivity
G. Promote efficient system management and operation; Improve efficiency
I. Improve the resiliency and reliability of the transportation system and reduce or mitigate stormwater impacts of surface transportation; Improve resiliency and reliability
J. Enhance travel and tourism. Support travel and tourism

Associated Objective Categories

Objective Category
Emergency/Incident Management: Person Hours of Delay
Emergency/Incident Management: Traveler Information
Freeway Management: Efficiency
Freeway Management: Reliability
System Efficiency: Delay
System Efficiency: Energy Consumption
System Efficiency: Intensity of Congestion (Travel Time Index)
System Efficiency: Travel Time
System Reliability: Non-Recurring Delay
System Reliability: Travel Time 90th/95th Percentile
System Reliability: Travel Time Buffer Index
System Reliability: Variability
Travel Weather Management: Disseminating Information
Traveler Information: Trip Planning Tools

Associated Objectives and Performance Measures

Objective Performance Measure
Annual rate of change in regional average commute travel time will not exceed regional rate of population growth through the year Y. Average commute trip travel time (minutes).
Decrease the average buffer index for (multiple routes or trips) by X percent over Y years. The buffer index represents the extra time (buffer) most travelers add to their average travel time when planning trips. This is the extra time between the average travel time and near-worst case travel time (95th percentile). The buffer index is stated as a percentage of the average travel time. Average buffer index or buffer time can be calculated using miles traveled as a weighting factor. Buffer time = 95th percentile travel time (min) – average travel time (min).
Decrease the buffer index for (specific travel routes) by X percent over the next Y years. The buffer index represents the extra time (buffer) most travelers add to their average travel time when planning trips. This is the extra time between the average travel time and near-worst case travel time (95th percentile). The buffer index is stated as a percentage of the average travel time. Average buffer index or buffer time can be calculated using miles traveled as a weighting factor. Buffer time = 95th percentile travel time (min) – average travel time (min).
Enhance regional multimodal trip planning tools to X data sources by year Y. The number of data sources providing information for multi-modal trip planning tools.
Improve average travel time during peak periods by X percent by year Y. Average travel time during peak periods (minutes).
Reduce buffer index on the freeway system during peak and off-peak periods by X percent in Y years. The buffer index (represents the extra time (buffer) travelers add to their average travel time when planning trips in order to arrive on-time 95 percent of the time).
Reduce delay associated with incidents on the freeway system by X percent by year Y. Hours of delay associated with incidents.
Reduce excess fuel consumed due to congestion by X percent by year Y. Excess fuel consumed (total or per capita).
Reduce hours of delay per capita by X percent by year Y. Hours of delay (person-hours).
Reduce hours of delay per capita by X percent by year Y. Hours of delay per capita.
Reduce hours of delay per driver by X percent by year Y. Hours of delay (person-hours).
Reduce hours of delay per driver by X percent by year Y. Hours of delay per driver.
Reduce the 90th (or 95th) percentile travel times for each route selected by X percent over Y years. 95th or 90th percentile travel times for selected routes.
Reduce the average buffer time needed to arrive on-time for 95 percent of trips on (specified routes) by X minutes over Y years. The buffer index represents the extra time (buffer) most travelers add to their average travel time when planning trips. This is the extra time between the average travel time and near-worst case travel time (95th percentile). The buffer index is stated as a percentage of the average travel time. Average buffer index or buffer time can be calculated using miles traveled as a weighting factor. Buffer time = 95th percentile travel time (min) – average travel time (min).
Reduce the average of the 90th (or 95th) percentile travel times for (a group of specific travel routes or trips in the region) by X minutes in Y years. 95th or 90th percentile travel times for selected routes.
Reduce the number of person hours (or vehicle hours) of delay experienced by travelers on the freeway system. Hours of delay (vehicle-hours or person-hours).
Reduce the number of person hours (or vehicle hours) of delay experienced by travelers on the freeway system. Hours of delay per capita or driver.
Reduce the person hours (or vehicle hours) of total delay associated with traffic incidents by X percent over Y years. Person hours (or vehicle hours) of delay associated with traffic incidents.
Reduce the regional average travel time index by X percent per year. Travel time index (the average travel time during the peak period, using congested speeds, divided by the off-peak period travel time, using posted or free-flow speeds).
Reduce the share of freeway miles at Level of Service (LOS) X by Y by year Z. Miles at LOS X or V/C > 1.0 (or other threshold).
Reduce the variability of travel time on specified routes by X percent during peak and off-peak periods by year Y. Variance of travel time. Variance is the sum of the squared deviations from the mean. This can also be calculated as the standard deviation of travel time. Standard deviation is the square root of variance.
Reduce time between incident/emergency verification and posting a traveler alert to traveler information outlets (e.g., variable message signs, agency website, 511 system) by X minutes in Y years. Time to alert motorists of an incident/emergency.
Reduce time to alert travelers of travel weather impacts (using variable message signs, 511, road weather information systems, public information broadcasts, the agency's website, Web 2.0 technologies, etc.) by X (time period or percent) in Y years. Time from beginning of weather event to posting of traveler information on (variable message signs, 511, Road Weather Information Systems, public information broadcasts etc.).
Reduce time to alert travelers of travel weather impacts (using variable message signs, 511, road weather information systems, public information broadcasts, the agency's website, Web 2.0 technologies, etc.) by X (time period or percent) in Y years. Time from beginning of weather event to posting of traveler information on agency website.
Reduce total energy consumption per capita for transportation by X percent by year Y. Total energy consumed per capita for transportation.
Reduce total fuel consumption per capita for transportation by X percent by year Y. Total fuel consumed per capita for transportation.
Reduce total person hours of delay (or travel-time delay per capita) by time period (peak, off-peak) caused by all transient events such as traffic incidents, special events, and work zones. Total person hours of delay during scheduled and/or unscheduled disruptions to travel.
Reduce total person hours of delay (or travel-time delay per capita) by time period (peak, off-peak) caused by scheduled events, work zones, or system maintenance by x hours in y years. Travel time delay during scheduled and/or unscheduled disruptions to travel.
Reduce total person hours of delay (or travel-time delay per capita) by time period (peak, off-peak) caused by unscheduled disruptions to travel. Total person hours of delay during scheduled and/or unscheduled disruptions to travel.

 
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 needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information. 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.
02 The field element shall collect, process, and send traffic images to the center for further analysis and distribution.
04 The field element shall return sensor and CCTV system operational status to the controlling center.
Roadway Warning 01 The field element shall monitor for hazardous traffic conditions, including queues.
05 The field element shall autonomously identify potentially hazardous conditions and activate warning signs to approaching motorists.
07 The field element shall collect operational status of the warning system field equipment and report the operational status to the controlling center.
RSE Environmental Monitoring 04 The field element shall provide application status to the center for monitoring.
RSE Queue Warning 01 The field equipment shall communicate with the connected vehicles to gather real-time vehicle-collected data including vehicle speed, location and localized weather condition from the vehicle network.
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.
02 The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.
04 The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic sensor and surveillance data to other centers.
05 The center shall respond to control data from center personnel regarding sensor and surveillance data collection, analysis, storage, and distribution.
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 01 The traffic center shall remotely control environmental sensors that measure road surface conditions including temperature, moisture, icing, salinity, and other measures.
02 The traffic center shall remotely control environmental sensors that measure weather conditions including temperature, wind, humidity, precipitation, and visibility.
03 The traffic center shall assimilate current and forecast road conditions and surface weather information using a combination of weather service provider information (such as the National Weather Service and value-added sector specific meteorological services), data from roadway maintenance operations, and environmental data collected from sensors deployed on and about the roadway.
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 Roadway Warning 01 The center shall monitor data on traffic, environmental conditions, and other hazards collected from sensors along the roadway.
07 The center shall have the capability to receive real-time traffic (including location and speed), road conditions (e.g. ice, wet, etc.), and weather data (clear, rainy and snowy) from connected vehicles.
Vehicle Basic Safety Communication 02 The vehicle shall provide its location with lane-level accuracy to on-board applications.
06 The vehicle shall exchange location and motion information with roadside equipment and nearby vehicles.
Vehicle Environmental Monitoring 01 The vehicle shall collect and process environmental sensor data, including air temperature and rain sensors.
02 The vehicle shall monitor the status of vehicle convenience and safety systems (wiper status, headlight status, traction control system status) that can be used to measure environmental conditions and record snapshots of significant events in these systems.
04 The vehicle shall transmit environmental probe data to field equipment located along the roadway using short range communications.
Vehicle Situation Data Monitoring 02 The Vehicle shall collect data collection parameters from Centers.
03 The vehicle shall collect location and motion data from the vehicle platform.
05 The Vehicle shall provide data to Centers in accordance with data collection parameters provided by Centers/Connected Vehicle Roadside Equipment.
02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information. 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.
02 The field element shall collect, process, and send traffic images to the center for further analysis and distribution.
04 The field element shall return sensor and CCTV system operational status to the controlling center.
Roadway Environmental Monitoring 01 The field element shall include surface and sub-surface environmental sensors that measure road surface temperature, moisture, icing, salinity, and other measures.
02 The field element shall include environmental sensors that measure weather conditions including temperature, wind, humidity, precipitation, and visibility.
04 The field element's environmental sensors shall be remotely controlled by a traffic management center.
07 The field element shall provide environmental sensor equipment operational status to the controlling center or maintenance vehicle.
10 The field element shall provide weather and road surface condition data to centers.
RSE Environmental Monitoring 01 The field element shall communicate with passing vehicles to collect environmental monitoring data, including ambient air quality, emissions, temperature, precipitation, and other road weather information.
02 The field element shall aggregate and forward collected environmental probe information to the center.
04 The field element shall provide application status to the center for monitoring.
05 The field element shall aggregate and filter the collected environmental data based on configuration parameters received from the controlling center.
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.
02 The center shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center.
04 The center shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic sensor and surveillance data to other centers.
05 The center shall respond to control data from center personnel regarding sensor and surveillance data collection, analysis, storage, and distribution.
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 01 The traffic center shall remotely control environmental sensors that measure road surface conditions including temperature, moisture, icing, salinity, and other measures.
02 The traffic center shall remotely control environmental sensors that measure weather conditions including temperature, wind, humidity, precipitation, and visibility.
03 The traffic center shall assimilate current and forecast road conditions and surface weather information using a combination of weather service provider information (such as the National Weather Service and value-added sector specific meteorological services), data from roadway maintenance operations, and environmental data collected from sensors deployed on and about the roadway.
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 Roadway Warning 09 The center shall use collected data to detect the location, duration, and length of queue propagation, as a result of significant downstream speed reductions or stopped traffic.
Vehicle Environmental Monitoring 01 The vehicle shall collect and process environmental sensor data, including air temperature and rain sensors.
02 The vehicle shall monitor the status of vehicle convenience and safety systems (wiper status, headlight status, traction control system status) that can be used to measure environmental conditions and record snapshots of significant events in these systems.
04 The vehicle shall transmit environmental probe data to field equipment located along the roadway using short range communications.
Vehicle Situation Data Monitoring 02 The Vehicle shall collect data collection parameters from Centers.
03 The vehicle shall collect location and motion data from the vehicle platform.
05 The Vehicle shall provide data to Centers in accordance with data collection parameters provided by Centers/Connected Vehicle Roadside Equipment.
03 Traffic Operations needs to be able to generate queue warning response strategies, including speed reduction, lane change, or diversion. TIC Traffic Control Dissemination 06 The center shall provide queue information to vehicles.
TMC Roadway Warning 08 The center shall generate appropriate queue response strategies that include speed reduction, lane change, or diversion recommendations based on local traffic, weather, and roadway conditions.
04 The Driver needs to be able to send queue information and response strategies to upstream vehicles. Vehicle Queue Warning 01 The vehicle shall disseminate a queued status alert to other connected vehicles.
03 The vehicle shall receive queue warning messages from other vehicles.
05 The Driver needs to be able to receive queue information and queue response strategies based on information received from the infrastructure or other connected vehicles Roadway Warning 05 The field element shall autonomously identify potentially hazardous conditions and activate warning signs to approaching motorists.
06 The field element shall receive commands from the controlling center that activate warning signs to approaching motorists.
RSE Queue Warning 02 The field equipment shall communicate queue response strategies (speed reduction, lane change, diversion recommendations) to the vehicle.
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.
Vehicle Queue Warning 02 The vehicle shall receive queue warning messages from infrastructure systems.
04 The vehicle shall communicate queue warnings and queue characteristic information based on vehicle's distance to end of queue, (length of queue, lane(s) impacted, other descriptions of the queue condition) to the driver.
05 The vehicle shall communicate queue warnings and queue information to the driver utilizing auditory, visual, or haptic alerts and auditory or visual (on-screen) messages.
Vehicle Traveler Information Reception 01 The vehicle shall receive traveler information including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, border crossing information, and weather information.
02 The vehicle shall receive advisory information, such as evacuation information, proximity to a maintenance and construction vehicle, wide-area alerts, work zone intrusion information, variable speed limits, tunnel entrance restrictions, border crossing advisories, and other special information.
03 The vehicle shall receive indicator and fixed sign information including static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal and traffic meter states and local conditions warnings identified by local environmental sensors).
04 The vehicle shall store a translation table for road sign and message templates used for in-vehicle display.
05 The vehicle shall present the received information to the driver in audible or visual forms without impairing the driver's ability to control the vehicle in a safe manner.
06 The vehicle shall present to the driver a visual display of static sign information or dynamic roadway conditions information
07 The vehicle shall be capable of providing to the driver an audible presentation of static sign information or dynamic roadway conditions information

Related Sources

Document Name Version Publication Date
CO-UMP Road Hazard Warning 5/31/2021
Concept Development and Needs Identification for INFLO: Functional and Performance Requirements, and High-Level Data and Communication Needs Final 11/1/2012
Concept Development and Needs Identification for Intelligent Network Flow Optimization (INFLO), Functional and Performance Requirements, and High-Level Data and Communication Needs Draft v5.0 11/1/2012
Report on Detailed Requirements for the INFLO Prototype Final 12/27/2013
Report on Dynamic Speed Harmonization and Queue Warning Algorithm Design Final 2/28/2014
System Design Document for the INFLO Prototype Final 3/28/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
ITS Roadway Equipment Moderate Moderate Moderate Class 2
Other Traffic Management Centers Low Moderate Moderate Class 1
Other Vehicles Low High Moderate Class 3
Roadway Environment Not Applicable Low Low Class 1
Traffic Management Center Moderate High Moderate Class 3
Transportation Information Center Moderate Moderate Moderate Class 2
Vehicle Moderate High Moderate Class 3
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
Basic Vehicle Vehicle 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 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 queue warning 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 Vehicle queue warning information Not Applicable Moderate Low
Broadcast and intended for public use. Performance data that is compromised may result in incorrect actions taken by drivers, impacting their mobility and overall mobility throughout the transportation network. Lack of this flow will have a slight negative impact on potential recipients, but there are other mechanisms to learn of traffic delays. Only in circumstances where queue states directly drive decisions with signficant time impacts would this rise to MODERATE.
Connected Vehicle Roadside Equipment Vehicle vehicle signage data Low Moderate Moderate
This data is intentionally transmitted to everyone via a broadcast. It is meant to augment other signage data, and by definition is meant to be shared with everyone. These signs are meant to augment other visual cues to the driver. They should be accurate, but any inaccuracies should be corrected for by other means. These notifications are helpful to a driver, but if the driver does not receive this notification immediately, there should still be other visual cues.
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.
ITS Roadway Equipment Connected Vehicle Roadside Equipment vehicle signage local data Low Moderate Moderate
This data is intentionally transmitted to everyone via a broadcast. It is meant to augment other signage data, and by definition is meant to be shared with everyone. This information impacts the vehicle signage data sent to neighboring ASDs and should be trusted to avoid sending wrong information. DISC: WYO believes this to be HIGH. The system should know if these messages are not received.
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 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 roadway warning system status Moderate Moderate Moderate
Device status information should not be available, as those with criminal intent may use this information toward their own ends. Inaccurate or unavailable information may suggest inappropriate maintenance actions, costing time and money. Inaccurate or unavailable information may suggest inappropriate maintenance actions, 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.
ITS Roadway Equipment Traffic Management Center traffic image meta data Low Moderate Moderate
Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW. While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. While accuracy of this data is important for decision making purposes, applications should be able to function without it. Thus MODERATE generally.
ITS Roadway Equipment Traffic Management Center traffic images Low Moderate Low
Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW. Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. While useful, there is no signficant impact if this flow is not available.
Other Traffic Management Centers Traffic Management 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.
Other Vehicles Vehicle vehicle control event Low Moderate Moderate
This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators. This message is an indication of a potential hazard and should not be easy to forge. False messages here may lead to confusion that causes a traffic accident. From NYC: Integrity would need to be high if there were no mitigations against bad data in incoming BSMs. In fact, there are two mitigations: plausibility checking, and misbehavior reporting plus revocation. Taking these into account we believe, with [18], that the security requirements are met by requiring an integrity level of MODERATE on these information flows. RES: Sided with NYC due to mitigation documentation. This message is an indication of a potential hazard. If it isn't received it increases the risk to other road users. If a vehicle is infringing on an intersection, it must report this. From NYC: Even moderate availability of BSMs will enable a large majority of collisions between equipped vehicles to be avoided.
Other Vehicles Vehicle vehicle location and motion Not Applicable High Moderate
This data is intentionally transmitted to everyone via a broadcast. Much of its information content can also be determined via other visual indicators BSM info needs to be accurate and should not be tampered with BSM must be broadcast regularly to make data available for other vehicle OBEs, but availability cannot be guaranteed over a wireless medium
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.
Roadway Environment Vehicle 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.
Roadway Environment Vehicle roadway characteristics 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 Connected Vehicle Roadside Equipment queue warning application information Moderate Moderate Low
While the performance information included in this flow is not terribly sensitive, the application configuration information is: it could be used to determine an attack vector on the roadside equipment, so needs to be protected. Performance data that is compromised may result in incorrect actions taken by system operators or maintenance personnel, impacting mobility and operating costs. A delay in reporting this may impact mobility or maintenance, but there should be other mechanisms by which this information is learned.
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 roadway warning system control 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. 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 ITS Roadway Equipment video surveillance control Moderate Moderate 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. 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 Other Traffic Management Centers road network conditions Low Moderate Moderate
encrypted; but no harm should come from seeing this data info needs to be accurate and should not be tampered but should be able to cope with some bad data; should be able to confirm conditions by other mechanisms condition info should be timely and readily available so that TMCs are aware of current traffic info, conditions, restrictions, etc. but should not have severe/catastrophic consequences if not
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 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.
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.
Transportation Information Center Vehicle queue warning information Low Moderate Low
Intended for public use, but could indicate location of the recipient. Thus LOW and not N/A. Performance data that is compromised may result in incorrect actions taken by drivers, impacting their mobility and overall mobility throughout the transportation network. Lack of this flow will have a slight negative impact on potential recipients, but there are other mechanisms to learn of traffic delays. Only in circumstances where queue states directly drive decisions with signficant time impacts would this rise to MODERATE.
Transportation Information Center Vehicle 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 Basic Vehicle collision warning information Low Moderate Moderate
The information described in this message is the result of an analysis on broadcast data. It would not be difficult for a third party to produce the same message by listening to the broadcast information. This information is used by automated control systems on the vehicle platform to decide whether to react automatically, for example by braking. We assume that the vehicle platform uses this as only one input to the decision and will also take input from front-facing sensors (for pedestrian detection), rear-facing sensors (to detect possible rear-ending), etc. We strongly recommend that this message is not used as the sole basis for action; if it were to be so used, the integrity requirement might need to be HIGH, but we do not consider this case in detail here.DISC: THEA believes this should be HIGH: "information that provides warnings must be accurate and cannot be tampered with." This information is just one of a number of inputs to the vehicle platform that may be used to determine whether or not to take evasive action. DISC: THEA believes this should be HIGH: "information that provides warnings must be immediately available for the driver/control systems to react."
Vehicle Basic Vehicle driver update information Low Moderate Moderate
This information is all presented to the vehicle operator. Encrypting this information may make it harder to reverse engineer vehicle systems, and may defeat criminal tracking tools when the vehicle has already been compromised. Unless those scenarios are of concern to the operator or manufacturer, this can safely be set LOW. Any information presented to the operator of a vehicle should be both accurate and timely. By definition this includes safety information, but given that the driver has other means of learning about most threats, it seems difficult to justify HIGH. If HIGH is warranted, it should apply to both availability and integrity. Any information presented to the operator of a vehicle should be both accurate and timely. By definition this includes safety information, but given that the driver has other means of learning about most threats, it seems difficult to justify HIGH. If HIGH is warranted, it should apply to both availability and integrity.
Vehicle Connected Vehicle Roadside Equipment vehicle control event Low Moderate Moderate
This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators. This message is an indication of a potential hazard and should not be easy to forge. False messages here may lead to confusion that causes a traffic accident. This message is an indication of a potential hazard. If it isn't received it increases the risk to other road users. If a vehicle is infringing on an intersection, it must report this.
Vehicle 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 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 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 Other Vehicles vehicle control event Low Moderate Moderate
This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators. BSM info needs to be accurate and should not be tampered with, suggesting HIGH. From NYC: Integrity would need to be high if there were no mitigations against bad data in incoming BSMs. In fact, there are two mitigations: plausibility checking, and misbehavior reporting plus revocation. Taking these into account we believe, with [18], that the security requirements are met by requiring an integrity level of MODERATE on these information flows. RES: Sided with NYC due to mitigation documentation. BSM must be broadcast regularly to make data available for other vehicle OBEs, but cannot guarantee wireless communication
Vehicle Other Vehicles vehicle location and motion Not Applicable High Moderate
This data is intentionally transmitted to everyone via a broadcast. Much of its information content can also be determined via other visual indicators BSM info needs to be accurate and should not be tampered with BSM must be broadcast regularly to make data available for other vehicle OBEs, but availability cannot be guaranteed over a wireless medium
Vehicle 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.

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
CTI 4001 RSU Roadside Unit (RSU) Standard Connected Vehicle Roadside Equipment
ITE 5301 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




System Requirements

System Requirement Need
001 The system shall collect traffic probe data (speeds, travel times, etc.) from appropriately equipped vehicles and short range communications equipment. 05 The Driver needs to be able to receive queue information and queue response strategies based on information received from the infrastructure or other connected vehicles
002 The system shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements under remote control of the center. 02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
003 The system shall provide queue information to vehicles. 03 Traffic Operations needs to be able to generate queue warning response strategies, including speed reduction, lane change, or diversion.
004 The system shall monitor, analyze, and distribute traffic images from CCTV systems under remote control of the center. 02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
005 The system shall distribute road network conditions data (raw or processed) based on collected and analyzed traffic sensor and surveillance data to other centers. 02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
006 The system shall respond to control data from center personnel regarding sensor and surveillance data collection, analysis, storage, and distribution. 01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
007 The system 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). 01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
008 The system shall remotely control devices to detect traffic. 02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
009 The system shall remotely control environmental sensors that measure road surface conditions including temperature, moisture, icing, salinity, and other measures. 02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
010 The system shall assimilate current and forecast road conditions and surface weather information using a combination of weather service provider information (such as the National Weather Service and value-added sector specific meteorological services), data from roadway maintenance operations, and environmental data collected from sensors deployed on and about the roadway. 02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
011 The system shall receive aggregated and processed vehicle environmental data collected from vehicle safety and convenience systems through the connected vehicle roadside equipment. 01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
012 The system shall monitor data on traffic, environmental conditions, and other hazards collected from sensors along the roadway. 01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
013 The system shall have the capability to receive real-time traffic (including location and speed), road conditions (e.g. ice, wet, etc.), and weather data (clear, rainy and snowy) from connected vehicles. 01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
014 The system shall generate appropriate queue response strategies that include speed reduction, lane change, or diversion recommendations based on local traffic, weather, and roadway conditions. 03 Traffic Operations needs to be able to generate queue warning response strategies, including speed reduction, lane change, or diversion.
015 The system shall use collected data to detect the location, duration, and length of queue propagation, as a result of significant downstream speed reductions or stopped traffic. 02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
016 The system shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the center for further analysis and storage, under center control. 02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
017 The system shall collect, process, and send traffic images to the center for further analysis and distribution. 02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
018 The system shall collect, process, and send traffic images to the center for further analysis and distribution. 01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
019 The system shall return sensor and CCTV system operational status to the controlling center. 01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
020 The system shall return sensor and CCTV system operational status to the controlling center. 01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
021 The system shall include surface and sub-surface environmental sensors that measure road surface temperature, moisture, icing, salinity, and other measures. 02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
022 The system shall include environmental sensors that measure weather conditions including temperature, wind, humidity, precipitation, and visibility. 02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
023 The system shall provide environmental sensor equipment operational status to the controlling center or maintenance vehicle. 02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
024 The system shall provide weather and road surface condition data to centers. 02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
025 The system shall monitor for hazardous traffic conditions, including queues. 01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
026 The system shall autonomously identify potentially hazardous conditions and activate warning signs to approaching motorists. 05 The Driver needs to be able to receive queue information and queue response strategies based on information received from the infrastructure or other connected vehicles
01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
027 The system shall receive commands from the controlling center that activate warning signs to approaching motorists. 05 The Driver needs to be able to receive queue information and queue response strategies based on information received from the infrastructure or other connected vehicles
028 The system shall collect operational status of the warning system field equipment and report the operational status to the controlling center. 01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
029 The system shall communicate with passing vehicles to collect environmental monitoring data, including ambient air quality, emissions, temperature, precipitation, and other road weather information. 02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
030 The system shall aggregate and forward collected environmental probe information to the center. 02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
031 The system shall provide application status to the center for monitoring. 01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
032 The system shall aggregate and filter the collected environmental data based on configuration parameters received from the controlling center. 02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
033 The system shall communicate with the connected vehicles to gather real-time vehicle-collected data including vehicle speed, location and localized weather condition from the vehicle network. 01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
034 The system shall communicate queue response strategies (speed reduction, lane change, diversion recommendations) to the vehicle. 05 The Driver needs to be able to receive queue information and queue response strategies based on information received from the infrastructure or other connected vehicles
035 The system 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. 01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
036 The system shall provide its location with lane-level accuracy to on-board applications. 01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
037 The system shall exchange location and motion information with roadside equipment and nearby vehicles. 01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
038 The system shall collect and process environmental sensor data, including air temperature and rain sensors. 01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
039 The system shall monitor the status of vehicle convenience and safety systems (wiper status, headlight status, traction control system status) that can be used to measure environmental conditions and record snapshots of significant events in these systems. 01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
040 The system shall transmit environmental probe data to field equipment located along the roadway using short range communications. 02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
041 The system shall disseminate a queued status alert to other connected vehicles. 04 The Driver needs to be able to send queue information and response strategies to upstream vehicles.
042 The system shall receive queue warning messages from infrastructure systems. 05 The Driver needs to be able to receive queue information and queue response strategies based on information received from the infrastructure or other connected vehicles
043 The system shall receive queue warning messages from other vehicles. 04 The Driver needs to be able to send queue information and response strategies to upstream vehicles.
044 The system shall communicate queue warnings and queue characteristic information based on vehicle's distance to end of queue, (length of queue, lane(s) impacted, other descriptions of the queue condition) to the driver. 05 The Driver needs to be able to receive queue information and queue response strategies based on information received from the infrastructure or other connected vehicles
045 The system shall communicate queue warnings and queue information to the driver utilizing auditory, visual, or haptic alerts and auditory or visual (on-screen) messages. 05 The Driver needs to be able to receive queue information and queue response strategies based on information received from the infrastructure or other connected vehicles
046 The system shall receive traveler information including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, and weather information. 05 The Driver needs to be able to receive queue information and queue response strategies based on information received from the infrastructure or other connected vehicles
047 The system shall collect data collection parameters from Centers. 02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
048 The system shall receive advisory information, such as evacuation information, proximity to a maintenance and construction vehicle, wide-area alerts, work zone intrusion information, variable speed limits, tunnel entrance restrictions, and other special information. 05 The Driver needs to be able to receive queue information and queue response strategies based on information received from the infrastructure or other connected vehicles
049 The system shall provide data to Centers in accordance with data collection parameters provided by Centers/Connected Vehicle Roadside Equipment. 02 Traffic Operations needs to be able to develop predicted queue formation using both infrastructure and connected vehicle sources of information.
01 Traffic Operations needs to be able to detect a queue formation using both infrastructure and connected vehicle sources of information.
050 The system shall receive indicator and fixed sign information including static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal and traffic meter states and local conditions warnings identified by local environmental sensors). 05 The Driver needs to be able to receive queue information and queue response strategies based on information received from the infrastructure or other connected vehicles
051 The system shall store a translation table for road sign and message templates used for in-vehicle display. 05 The Driver needs to be able to receive queue information and queue response strategies based on information received from the infrastructure or other connected vehicles
052 The system shall present the received information to the driver in audible or visual forms without impairing the driver's ability to control the vehicle in a safe manner. 05 The Driver needs to be able to receive queue information and queue response strategies based on information received from the infrastructure or other connected vehicles
053 The system shall present to the driver a visual display of static sign information or dynamic roadway conditions information 05 The Driver needs to be able to receive queue information and queue response strategies based on information received from the infrastructure or other connected vehicles
054 The system shall provide to the driver an audible presentation of static sign information or dynamic roadway conditions information 05 The Driver needs to be able to receive queue information and queue response strategies based on information received from the infrastructure or other connected vehicles
 

Implementations


VS08.1 Traditional ITS Queue Warning Implementation

Traffic detectors/speed sensors in the infrastructure measure vehicle speeds and traditional ITS assets like DMS are used to provide driver warnings. This basic implementation does not include the CVRSE and does not include any direct OBE interface. (Alternatively, we could call this the WAW alternative and also include a new-for-the-SP triple between TIC and OBE that conveys queue warning info to vehicles.)

Traditional ITS Queue Warning Implementation Flows

Information FlowDescriptionInclusion Status
driver information Regulatory, warning, guidance, and other information provided to the driver to support safe and efficient vehicle operation. Fundamental
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. Optional
environmental sensor control Data used to configure and control environmental sensors. Optional
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. Optional
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. Optional
roadway warning system control Information used to configure and control roadway warning systems. Fundamental
roadway warning system status Current operating status of roadway warning systems. Fundamental
traffic detector control Information used to configure and control traffic detector systems such as inductive loop detectors and machine vision sensors. Fundamental
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 Fundamental
traffic image meta data Meta data that describes traffic images. Traffic images (video) are in another flow. Optional
traffic images High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications. This flow includes the images. Meta data that describes the images is contained in another flow. Optional
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. Optional
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. Optional
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. Fundamental
video surveillance control Information used to configure and control video surveillance systems. Optional


Traditional ITS Queue Warning Implementation Functional Objects

Functional Object
Roadway Basic Surveillance
Roadway Environmental Monitoring
Roadway Warning
TIC Situation Data Management
TMC Basic Surveillance
TMC Environmental Monitoring
TMC Roadway Warning


Back to Implementation List

VS08.2 WAW Queue Warning Implementation

In this alternative, wide-area wireless (WAW) communications is used to communicate queue warning information to equipped vehicles, replacing or augmenting traditional ITS assets like DMS for communicating warnings to approaching vehicles. This implementation relies on some combination of WAW situation-reporting by vehicles and infrastructure-based sensors to detect queues.

WAW Queue Warning Implementation Flows

Information FlowDescriptionInclusion Status
driver information Regulatory, warning, guidance, and other information provided to the driver to support safe and efficient vehicle operation. Optional
driver input Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands. Optional
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. Fundamental
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. Optional
environmental sensor control Data used to configure and control environmental sensors. Optional
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. Optional
queue warning information Information regarding formed or impending queues (location of the end of queue, estimated duration of the queue, and other descriptions of the queue condition) and recommendations for upstream vehicles including speed reduction, lane change, or diversion recommendations. Fundamental
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. Optional
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. At Least One
roadway characteristics Detectable or measurable road characteristics such as friction coefficient and general surface conditions, road geometry and markings, etc. These characteristics are monitored or measured by ITS sensors and used to support advanced vehicle safety and control and road maintenance capabilities. Optional
traffic detector control Information used to configure and control traffic detector systems such as inductive loop detectors and machine vision sensors. At Least One
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 At Least One
traffic image meta data Meta data that describes traffic images. Traffic images (video) are in another flow. At Least One
traffic images High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications. This flow includes the images. Meta data that describes the images is contained in another flow. At Least One
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. Optional
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. Optional
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. At Least One
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. At Least One
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. Optional
video surveillance control Information used to configure and control video surveillance systems. At Least One


WAW Queue Warning Implementation Functional Objects

Functional Object
Roadway Basic Surveillance
Roadway Environmental Monitoring
TIC Situation Data Management
TIC Traffic Control Dissemination
TMC Basic Surveillance
TMC Environmental Monitoring
TMC Roadway Warning
Vehicle Environmental Monitoring
Vehicle Queue Warning
Vehicle Situation Data Monitoring


Back to Implementation List

VS08.3 C-ITS Queue Warning Implementation

Short range communications supports direct V2I and V2V sharing of queue warning information for vehicles in and approaching traffic queues. The infrastructure monitors the short range communications and uses this to monitor and manage the queue. This implementation Includes the CVRSE interfaces as mandatory and many of the alternative ITSRE interfaces become optional, but they are still included as optional to support a real-world mix of equipped and unequipped vehicles.

C-ITS Queue Warning Implementation Flows

Information FlowDescriptionInclusion Status
collision warning information Information provided to support computer-based intervention of vehicle controls. Analogous to driver warnings, these are warnings issued to on-board control systems of an impending collision or other situation detected by the Vehicle OBE that may require control intervention. Optional
driver information Regulatory, warning, guidance, and other information provided to the driver to support safe and efficient vehicle operation. Optional
driver input Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands. Optional
driver update information Information provided to the driver-vehicle interface to inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment. The flow includes the information to be presented to the driver and associated metadata that supports processing, prioritization, and presentation by the DVI as visual displays, audible information and warnings, and/or haptic feedback. Optional
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. Fundamental
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. Optional
environmental sensor control Data used to configure and control environmental sensors. Optional
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. Optional
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. Optional
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. Optional
queue warning application information Information regarding formed or impending queues (location of the end of queue, estimated duration of the queue, and other descriptions of the queue condition) and recommendations for upstream vehicles including speed reduction, lane change, or diversion recommendations. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted. Fundamental
queue warning application status Queue warning application status reported by the RSE. This includes current operational state and status of the RSE and a record of measured vehicle speeds and identified queues. Fundamental
queue warning information Information regarding formed or impending queues (location of the end of queue, estimated duration of the queue, and other descriptions of the queue condition) and recommendations for upstream vehicles including speed reduction, lane change, or diversion recommendations. Fundamental
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. Optional
roadway characteristics Detectable or measurable road characteristics such as friction coefficient and general surface conditions, road geometry and markings, etc. These characteristics are monitored or measured by ITS sensors and used to support advanced vehicle safety and control and road maintenance capabilities. Optional
roadway warning system control Information used to configure and control roadway warning systems. Optional
roadway warning system status Current operating status of roadway warning systems. Optional
traffic detector control Information used to configure and control traffic detector systems such as inductive loop detectors and machine vision sensors. Optional
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 Optional
traffic image meta data Meta data that describes traffic images. Traffic images (video) are in another flow. Optional
traffic images High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications. This flow includes the images. Meta data that describes the images is contained in another flow. Optional
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. Optional
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. Optional
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. Optional
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. Optional
vehicle control event Notification that the vehicle has performed an emergency maneuver or action that could impact the safety of surrounding vehicles. This includes hard braking and activation of traction/stability control systems or other actions that warrant immediate notification of surrounding vehicles. The information flow conveys the current vehicle location, path, and current control actions. This may also include the list of maneuvers includes lane changes/departures and overtaking/passing maneuvers. Optional
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. Optional
vehicle location and motion Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size. Fundamental
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. Fundamental
vehicle signage data In-vehicle signing data that augments regulatory, warning, and informational road signs and signals. The information provided would include static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., local traffic and road conditions, restrictions, vehicle requirements, work zones, detours, closures, advisories, and warnings). Optional
vehicle signage local data Information provided by adjacent field equipment to support in-vehicle signing of dynamic information that is currently being displayed to passing drivers. This includes the dynamic information (e.g., local traffic and road conditions, work zone information, lane restrictions, detours, closures, advisories, parking availability, etc.) and control parameters that identify the desired timing, duration, and priority of the signage data. Optional
video surveillance control Information used to configure and control video surveillance systems. Optional


C-ITS Queue Warning Implementation Functional Objects

Functional Object
Roadway Basic Surveillance
Roadway Environmental Monitoring
Roadway Warning
RSE Environmental Monitoring
RSE Queue Warning
RSE Traffic Monitoring
TIC Situation Data Management
TMC Basic Surveillance
TMC Environmental Monitoring
TMC Roadway Warning
Vehicle Basic Safety Communication
Vehicle Environmental Monitoring
Vehicle Queue Warning
Vehicle Traveler Information Reception


Back to Implementation List