< < VS16.3 : VS17.1 : VS17.2 > >
VS17.1: Wide Area Wireless Communications Implementation
Wide-area wireless communications is used to provide information from the infrastructure to support automated vehicle operations.
Relevant Regions: Australia, Canada, European Union, and United States
- Enterprise
- Functional
- Physical
- Goals and Objectives
- Needs and Requirements
- Sources
- Security
- Standards
- System Requirements
Enterprise
Development Stage Roles and Relationships
Installation Stage Roles and Relationships
Operations and Maintenance Stage Roles and Relationships
(hide)
| Source | Destination | Role/Relationship |
|---|---|---|
| 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 |
| 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 Manager | Maint and Constr Field Personnel | System Usage Agreement |
| ITS Roadway Equipment Owner | ITS Roadway Equipment Maintainer | System Maintenance Agreement |
| ITS Roadway Equipment Owner | ITS Roadway Equipment Manager | Operations Agreement |
| ITS Roadway Equipment Owner | Traffic Management Center Maintainer | Maintenance Data Exchange Agreement |
| ITS Roadway Equipment Owner | Traffic Management Center Owner | Information Exchange Agreement |
| ITS Roadway Equipment Owner | Traffic Management Center User | Service Usage Agreement |
| ITS Roadway Equipment Owner | Traffic Operations Personnel | Application Usage Agreement |
| ITS Roadway Equipment Supplier | ITS Roadway Equipment Owner | Warranty |
| Maint and Constr Field Personnel | ITS Roadway Equipment | Operates |
| Other Vehicle OBEs Operator | Other Vehicles | Operates |
| Other Vehicles Maintainer | Other Vehicles | Maintains |
| Other Vehicles Manager | Other Vehicle OBEs Operator | System Usage Agreement |
| 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 |
| TIC Operator | Transportation Information Center | Operates |
| Traffic Management Center Maintainer | Traffic Management Center | Maintains |
| Traffic Management Center Manager | Traffic Management Center | Manages |
| Traffic Management Center Manager | Traffic Operations Personnel | System Usage Agreement |
| Traffic Management Center Owner | ITS Roadway Equipment Maintainer | Maintenance Data Exchange Agreement |
| Traffic Management Center Owner | ITS Roadway Equipment Owner | Information Exchange Agreement |
| Traffic Management Center Owner | ITS Roadway Equipment User | Service Usage Agreement |
| Traffic Management Center Owner | Maint and Constr Field Personnel | Application Usage Agreement |
| Traffic Management Center Owner | TIC Operator | Application Usage Agreement |
| Traffic Management Center Owner | Traffic Management Center Maintainer | System Maintenance Agreement |
| Traffic Management Center Owner | Traffic Management Center Manager | Operations Agreement |
| Traffic Management Center 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 | TIC Operator | System Usage Agreement |
| 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 Exchange Agreement |
| Transportation Information Center Owner | Vehicle User | Service Usage Agreement |
| Transportation Information Center Supplier | Transportation Information Center 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 | Driver | Application Usage Agreement |
| Vehicle Owner | Driver | Vehicle Operating Agreement |
| Vehicle Owner | Other Vehicle OBEs Operator | Application Usage Agreement |
| Vehicle Owner | Other Vehicle OBEs Operator | 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 | TIC Operator | Application Usage Agreement |
| Vehicle Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
| Vehicle Owner | Transportation Information Center Owner | Information Exchange Agreement |
| 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
The physical diagram can be viewed in SVG or PNG format and the current format is SVG.SVG Diagram
PNG Diagram
Includes Physical Objects:
| Physical Object | Class | Description |
|---|---|---|
| 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. |
| 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 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. |
| Potential Obstacles | Field | 'Potential Obstacles' represents any object that possesses the potential of being sensed and struck and thus also possesses physical attributes. Potential Obstacles include roadside obstructions, debris, animals, infrastructure elements (barrels, cones, barriers, etc.) or any other element that is in a potential path of the vehicle. Note that roadside objects and pieces of equipment that can become obstacles in a vehicle’s path can include materials, coatings, or labels (e.g., barcodes) that will improve the performance of the vehicle-based sensors that must detect and avoid these obstacles. See also 'Vulnerable Road Users' that more specifically represents the physical properties of shared users of the roadway that must also be detected. |
| 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 (including motorcycles), commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems. |
| Vehicle Characteristics | Vehicle | 'Vehicle Characteristics' represents the external view of individual vehicles of any class from cars and light trucks up to large commercial vehicles and down to micromobility vehicles (MMVs). It includes vehicle physical characteristics such as height, width, length, weight, and other properties (e.g., magnetic properties, number of axles, occupants, emissions) of individual vehicles that can be sensed and measured or classified. This physical object represents the physical properties of vehicles that can be sensed by vehicle-based or infrastructure-based sensors to support vehicle automation and traffic sensor systems. The analog properties provided by this terminator represent the sensor inputs that are used to detect and assess vehicle(s) within the sensor's range to support safe AV operation and/or responsive and safe traffic management. |
| Vulnerable Road Users | Personal | 'Vulnerable Road Users' represents any roadway user not in a motorized vehicle capable of operating at the posted speed for the roadway in question, and also any roadway user in a vehicle not designed to encase (and thus protect) its occupants. This includes pedestrians, cyclists, wheelchair users, two-wheeled scooter micromobility users, as well as powered scooters and motorcycles. Note that this terminator represents the physical properties of vulnerable road users and their conveyance that may be sensed to support safe vehicle automation and traffic management in mixed mode applications where a variety of road users share the right-of-way. See also 'Pedestrian' and 'MMV User' Physical Objects that represent the human interface to these vulnerable road users. |
Includes Functional Objects:
| Functional Object | Description | Physical Object |
|---|---|---|
| Roadway Barrier System Control | 'Roadway Barrier System Control' includes the field equipment that controls barrier systems used to control access to transportation facilities and infrastructure. Barrier systems include automatic or remotely controlled gates, barriers and other access control systems. | 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 Surveillance | 'Roadway Basic Surveillance' monitors traffic conditions using fixed equipment such as loop detectors, CCTV cameras, , RADARs and LIDARs. | ITS Roadway Equipment |
| TIC Traffic Control Dissemination | 'TIC Traffic Control Dissemination' serves as intermediary between transportation operations centers (e.g., TMC, Transit MC) and transportation users (e.g., vehicles, personal devices). It collects and 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 Automated Vehicle Operations | 'TMC Automated Vehicle Operations' remotely monitors and controls automated lanes. It monitors system operation and provides parameters that control system operation including system parameters that govern vehicle platoon formation, speeds, and gaps or headways. | Traffic Management Center |
| TMC Barrier System Management | 'TMC Barrier System Management' remotely monitors and controls barrier systems for transportation facilities and infrastructure under control of center personnel. Barrier systems include automatic or remotely controlled gates, barriers and other access control systems. It also provides an interface to other centers to allow monitoring and control of the barriers from other centers (e.g., public safety or emergency operations centers). | Traffic Management 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 |
| Vehicle Basic Safety Communication | 'Vehicle Basic Safety Communication' exchanges current vehicle characteristics, location, and motion (including past and intended maneuver) information with other vehicles in the vicinity and the infrastructure, uses that information to calculate vehicle paths, and warns the driver when the potential for an impending collision is detected. If available, map data is used to filter and interpret the relative location and motion of vehicles in the vicinity. Information from on-board sensors (e.g., radars and image processing) are also used, if available, in combination with the V2V communications to detect non-equipped vehicles and corroborate connected vehicle data. This object represents a broad range of implementations ranging from basic Vehicle Awareness Devices that only broadcast vehicle location and motion and provide no driver warnings to advanced integrated safety systems that coordinate maneuvers and may, in addition to warning the driver, provide collision warning information to support automated control functions that can support control intervention. This object can also support broadcasting other vehicle information required for passing through a specific roadway segment such as variables that describe vehicle's characteristics and parameters, driver's preferences in terms of vehicle motion and behavior, etc. | Vehicle |
| Vehicle Control Automation | 'Vehicle Control Automation' provides lateral and/or longitudinal control of a vehicle to allow 'hands off' and/or 'feet off' driving, automating the steering, accelerator, and brake control functions. It builds on the sensors included in 'Vehicle Safety Monitoring' and 'Vehicle Control Warning', receives warnings from 'Vehicle Intersection Movement', and uses the information about the area surrounding the vehicle to safely control the vehicle. It covers the range of incremental control capabilities from driver assistance systems that take over steering or acceleration/deceleration in limited scenarios with direct monitoring by the driver to full automation where all aspects of driving are automated under all roadway and environmental conditions, including providing, receiving, and acting on cooperation-related messaging. | Vehicle |
| Vehicle Control Warning | 'Vehicle Control Warning' monitors areas around the vehicle and provides warnings to a driver so the driver can take action to recover and maintain safe control of the vehicle. It includes lateral warning systems that warn of lane departures and obstacles or vehicles to the sides of the vehicle and longitudinal warning systems that monitor areas in the vehicle path and provide warnings when headways are insufficient or obstacles are detected in front of or behind the vehicle. It includes on-board sensors, including radars and imaging systems, and the driver information system that provides the visual, audible, and/or haptic warnings to the driver. | 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 Platoon Operations | 'Vehicle Platoon Operations' provides the capability for vehicles to operate in cooperative platoons with short fixed gaps and a designated lead vehicle. These capabilities are provided by systems on board the vehicle that coordinate with other vehicles and regulate acceleration and braking and provide higher-level functions that enable vehicles to join and depart from vehicle platoons. | Vehicle |
Includes Information Flows:
| Information Flow | Description |
|---|---|
| automated lane control data | Control commands and operating parameters for automated vehicle operations, including tightly coupled platooned groups of vehicles operating in dedicated or mixed-mode lanes. This flow includes platoon parameters including maximum platoon size, target speeds and gaps, and vehicle restrictions. |
| automated vehicle control parameters | Information, instructions, and control parameters for automated vehicle operations including current system conditions and advisories, control parameters (e.g., speed, required vehicle performance profiles, gaps or headways) and check in/checkout instructions. |
| automated vehicle control status | Data provided by a connected vehicle identifying it's current mode and operational status and information provided to support check-in/checkout of the lane and coordinated maneuvers while on the automated facility. |
| barrier system control | Information used to configure and control barrier systems that are represented by gates, barriers and other automated or remotely controlled systems used to manage entry to roadways. |
| barrier system status | Current operating status of barrier systems. Barrier systems represent gates, barriers and other automated or remotely controlled systems used to manage entry to roadways. Status of the systems includes operating condition and current operational state. |
| driver input | Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands. |
| driver input information | Driver input received from the driver-vehicle interface equipment via the vehicle bus. It includes configuration data, settings and preferences, interactive requests, and control commands for the connected vehicle on-board equipment. |
| 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. |
| 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. |
| physical presence | Detection of an obstacle. Obstacle could include animals, incident management and construction elements such as cones, barrels and barriers, internal structures such as pillars and poles, rocks in roadway, etc. |
| roadway characteristics | Detectable or measurable road characteristics such as friction coefficient and general surface conditions, road geometry, signs and indicators (e.g., speed limits, parking availability) and markings, etc. These characteristics are monitored or measured by ITS sensors and used to support advanced vehicle safety, parking, turning and lane change maneuvers and road maintenance capabilities. |
| traffic detector control | Information used to configure and control traffic detector systems such as inductive loop detectors and machine vision sensors. |
| traffic detector data | Raw and/or processed traffic detector data which allows derivation of traffic flow variables (e.g., speed, volume, and density measures) and associated information (e.g., congestion, potential incidents). This flow includes the traffic data and the operational status of the traffic detectors |
| traffic operator data | Presentation of traffic operations data to the operator including traffic conditions, current operating status of field equipment, maintenance activity status, incident status, video images, security alerts, emergency response plan updates and other information. This data keeps the operator appraised of current road network status, provides feedback to the operator as traffic control actions are implemented, provides transportation security inputs, and supports review of historical data and preparation for future traffic operations activities. |
| traffic operator input | User input from traffic operations personnel including requests for information, configuration changes, commands to adjust current traffic control strategies (e.g., adjust signal timing plans, change DMS messages), and other traffic operations data entry. |
| vehicle characteristics | The physical or visible characteristics of individual vehicles that can be used to detect, classify, and monitor vehicles and imaged to uniquely identify vehicles and characterize their performance (e.g., speed, occupants, emissions). |
| vehicle control | Control commands issued to vehicle actuators that control steering, throttle, and braking and other related commands that support safe transition between manual and automated vehicle control. This flow can also deploy restraints and other safety systems when a collision is unavoidable. |
| 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 maneuver coordination | Statements of intent, permission and status of a lane change or merge operation by a connected vehicle |
| vehicle platoon coordination | Coordination of control commands between leader and follower vehicles allowing vehicles to join, coordinate with, and separate from platoons of cooperative vehicles. This flow shares platoon size, location, and performance parameters (e.g., platoon speed and spacing) between platooned vehicles. |
| vehicle profile | Information about a vehicle such as vehicle make and model, fuel type, engine type, size and weight, vehicle performance and level of control automation, average emissions, average fuel consumption, passenger occupancy, or other data that can be used to classify vehicle eligibility for access to specific lanes, road segments, or regions or participation in cooperative vehicle control applications. |
| vulnerable road user presence | Detection of pedestrians, cyclists, and other vulnerable road users. This detection is based on physical characteristics of the user and their conveyance, which may be enhanced by design and materials that facilitate sensor-based detection and tracking of vulnerable road users. |
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 |
| G. Promote efficient system management and operation; | Improve efficiency |
Associated Objective Categories 
Associated Objectives and Performance Measures
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 | The Connected Vehicle needs to be able to perform lateral and longitudinal control actions in order to operate the vehicle without direct driver intervention either independently or as part of a platoon. | 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. | |||
| 18 | The vehicle shall provide measured and derived environmental conditions data to other vehicles and roadside equipment. | |||
| Vehicle Control Automation | 01 | The vehicle shall monitor the area behind and in front of the vehicle to determine the proximity of other objects to the vehicle. | ||
| 02 | The vehicle shall monitor the area to the sides of the vehicle to determine the proximity of other objects to the vehicle to determine if a control adjustment is needed. | |||
| 03 | The vehicle shall evaluate the likelihood of a collision between two vehicles or a vehicle and another objects, based on the proximity and vectors of other objects relative to the vehicle and the current speed and direction of the vehicle. | |||
| 04 | The vehicle shall collect location and motion data from the vehicle platform. | |||
| 05 | The Vehicle shall provide its location with lane-level accuracy to on-board control automation applications. | |||
| 09 | The vehicle shall send appropriate control actions to the vehicle's steering actuators. | |||
| 17 | The vehicle shall send appropriate control actions to the vehicle's speed control systems (e.g., throttle, brakes). | |||
| Vehicle Control Warning | 01 | The vehicle shall monitor the area to the sides of the vehicle to determine the proximity of other objects to the vehicle and if a warning is needed. | ||
| 02 | The vehicle shall evaluate the likelihood of a collision between two vehicles or a vehicle and another object to warn the driver, based on the proximity and vectors of other objects to the vehicle, roadway characteristics, and the current speed and direction of the vehicle. | |||
| 09 | The vehicle shall collect location and motion data from the vehicle platform. | |||
| Vehicle Platoon Operations | 03 | The vehicle shall collect and monitor data concerning the safety of the vehicle while on automated lanes including conditions of the brakes, drive train, forward/rear/side sensors, steering condition, fuel level, tire wear and pressure, and the status of vehicle processors and communications. | ||
| 04 | The vehicle shall monitor the area surrounding vehicle in an automated lane to determine the proximity of other objects to the vehicle. Obstacles could include animals, other vehicles, pedestrians, debris in roadway etc. | |||
| 05 | The vehicle shall evaluate the likelihood of a collision between two vehicles or a vehicle and a stationary object, based on the proximity of other objects to the vehicle, conditions of the roadway and environment, and the current speed and direction of the vehicle. | |||
| 02 | The Connected Vehicle needs to be able to perform actions that transition the vehicle from driver operation to autonomous operation and back to driver operation when the automated portion of the drive is completed. | Vehicle Basic Safety Communication | 12 | The vehicle shall analyze its own applications' performance and enter fail-safe mode (a mode such that the application cannot provide information or perform actions that affect its host) when critical components fail. |
| 13 | The vehicle shall notify the driver when onboard components or safety applications are offline. | |||
| Vehicle Control Automation | 08 | The vehicle shall provide an interface through which a vehicle driver can initiate, monitor and terminate automatic control of the vehicle. | ||
| 10 | The vehicle shall present vehicle control information to the driver in audible or visual forms without impairing the driver's ability to control the vehicle in a safe manner. | |||
| Vehicle Platoon Operations | 01 | The vehicle shall provide the capability for a driver to request access to automated vehicle lanes. | ||
| 02 | The vehicle shall request usage of automated lanes for all or part of an overall route; including sending vehicle conditions to the roadside to determine eligibility. | |||
| 06 | The vehicle shall provide warnings to the driver of potential dangers based on sensor input and analysis concerning the safety of the vehicle operating in an automated lane. | |||
| 07 | The vehicle shall present platoon information to the driver in audible or visual forms without impairing the driver's ability to control the vehicle in a safe manner. | |||
| 03 | Traffic Operations needs to be able to manage the operation of automated lanes on highways or roadways. | Roadway Barrier System Control | 01 | The field element shall activate barrier systems for transportation facilities and infrastructure under center control. Barrier systems include automated or remotely controlled gates, barriers and other systems that manage entry to roadways. |
| 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. | |||
| 13 | The field element shall collect environmental data from connected vehicle roadside equipment. | |||
| 14 | The field element shall provide access to remotely collected environmental data (i.e., from connected vehicle sources) in the same manner is it provides access to locally collected environmental data (typically by providing it to various centers). | |||
| Roadway 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. | ||
| 04 | The field element shall return sensor and CCTV system operational status to the controlling center. | |||
| TIC Traffic Control Dissemination | 01 | The center shall provide intersection status, lane control information, and other real time traffic control related information to vehicles. | ||
| TMC Automated Vehicle Operations | 01 | The center shall remotely control automated vehicle system field elements, by providing lane changing parameters, parameters for determination of vehicle suitability for particular automated lanes, and other control information required for automated highway operation. | ||
| 02 | The center shall maintain a log of all automated vehicle check-in and check-out transactions received from the field elements regardless of whether they are successful or not. | |||
| TMC Barrier System Management | 01 | The center shall remotely control barrier systems for transportation facilities and infrastructure. Barrier systems include automated or remotely controlled gates, barriers and other systems that manage entry to roadways. | ||
| 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. | |||
| 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. | |||
| Vehicle Basic Safety Communication | 02 | The vehicle shall provide its location with lane-level accuracy to on-board applications. | ||
| 07 | The vehicle shall receive warnings, informational road signs, traffic meters, and signals provided by infrastructure devices. | |||
| 18 | The vehicle shall provide measured and derived environmental conditions data to other vehicles and roadside equipment. | |||
| 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. | |||
Related Sources
| Document Name | Version | Publication Date |
|---|---|---|
| None |
Security
In order to participate in this service package, each physical object should meet or exceed the following security levels.
| Physical Object Security | ||||
|---|---|---|---|---|
| Physical Object | Confidentiality | Integrity | Availability | Security Class |
| Basic Vehicle | ||||
| ITS Roadway Equipment | Moderate | High | Moderate | Class 3 |
| Other Vehicles | Low | High | Moderate | Class 3 |
| Potential Obstacles | ||||
| Roadway Environment | Not Applicable | Low | Low | Class 1 |
| Traffic Management Center | Moderate | High | Moderate | Class 3 |
| Transportation Information Center | Moderate | High | Moderate | Class 3 |
| Vehicle | Moderate | High | Moderate | Class 3 |
| Vehicle Characteristics | ||||
| Vulnerable Road Users | ||||
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 | driver input information | Moderate | High | High |
| Internal vehicle flow that if reverse engineered could enable third party vehicle control. Largely a competitive question, could be set LOW if manufacturer and operator are not concerned with this type of compromise. | Includes vehicle control commands, which must be timely and accurate to support safe vehicle operation. | Includes vehicle control commands, which must be timely and accurate to support safe vehicle operation. | |||
| 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. | |||
| 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 | Traffic Management Center | barrier system status | Moderate | High | Moderate |
| Related to the control flow, however the data is directly observable and generally widely known. Difficult to justify obfuscation. | Status of barrier systems has direct human-safety related impact, that if performed incorrectly could lead to catastrophic incidents. | These systems need to operated when demanded or mobility will be restricted. However, manual processes should always be in place to compensate for a loss in connectivity, and to provide a secondary check for safety purposes anyway. | |||
| 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 | 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. | |||
| Other Vehicles | Vehicle | vehicle environmental data | Low | Moderate | Moderate |
| 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. | This could be used for safety applications, and in areas of severe weather a corrupted field could have significant consequences; however, any vehicle will use other inputs before triggering automatic safety facilities, so MODERATE should be sufficient. DISC: WYO believes this to be HIGH. | This data is required for the system to operate properly. If this data is not available, the system cannot give accurate warning information. | |||
| 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 | |||
| Other Vehicles | Vehicle | vehicle maneuver coordination | Low | High | Low |
| Data contained within this flow is intended to alert other nearby vehicles to a desired or impending movement by the source vehicle. The data does include identifiers indicating the sending vehicle, which needs to be recognized and protected as appropriate. It may be impractical to encrypt this data to meet performance requirements, and in any event no more than one vehicle would be identified and only in the field environment, so mass collection of this information would be difficult. | This flow is core to automated vehicle merge and lane change operations; flaws in the data could result in a crash, and so integrity should be ensured to the highest practical level. | L4/5 ADS will operate more smoothly if this flow works, but as the vehicle fleet will include L0 vehicles for the foreseeable future, any ADS must use other methods to ensure safe operation anyway. May be MODERATE in ADS-dedicated facilities. | |||
| Other Vehicles | Vehicle | vehicle platoon coordination | Low | High | Moderate |
| Includes the identity of the lead vehicle but no PII. Intended for vehicles to coordinate tightly, and with no previous relationship so likely open to other vehicles monitoring. | Platooning coordination data must be correct or potentially severe consequences can result, particularly if data relevant to high speed operations is corrupted. | Platooning will not fully function without this flow; the worst case is that vehicles drop from the platoon however; lack of this flow is unlikely to generate a severe incident on its own. | |||
| Potential Obstacles | Vehicle | physical presence | |||
| 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 | ITS Roadway Equipment | barrier system control | Moderate | High | Moderate |
| Control flows need to be obfuscated, lest a hostile individual learn how to control these systems. Barrier systems in particular present a safety risk if compromised, and could have a significant safety and mobility impact. | Control of barrier systems has direct human-safety related impact, that if performed incorrectly could lead to catastrophic incidents. | These systems need to operated when demanded or mobility will be restricted. However, manual processes should always be in place to compensate for a loss in connectivity, and to provide a secondary check for safety purposes anyway. | |||
| 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 | traffic detector control | Moderate | Moderate | Low |
| Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. DISC: THEA, WYO believe this to be LOW: encrypted, authenticated, proprietary; but should not cause severe damage if seen | Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH.. From THEA: should be accurate and not be tampered with; could enable outside control of traffic sensors but should not cause severe harm, but could cause issues with traffic sensor data received and be detrimental to operations | Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH.. From THEA: want updates but delayed information will not be severe; should be able to operate from a previous/default control/config. DISC: WYO believes this to be MODERATE | |||
| Traffic Management Center | Traffic Operations Personnel | traffic operator data | Moderate | Moderate | Moderate |
| Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. | Information presented to backoffice system operators must be consistent or the operator may perform actions that are not appropriate to the real situation. | The backoffice system operator should have access to system operation. If this interface is down then control is effectively lost, as without feedback from the system the operator has no way of knowing what is the correct action to take. | |||
| Traffic Management Center | Transportation Information Center | automated lane control data | 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 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 | automated vehicle control parameters | Low | High | Moderate |
| Intended for all vehicles participating in automated CACC scenario. | HIGH because lane change parameters could impact the safety of the vehicle network, particularly for vehicles that do not have CACC and are not aware of CACC behaviors, | There should be a back up or default mechanism in case this information cannot be exchanged. | |||
| 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 | Basic Vehicle | vehicle control | Moderate | High | High |
| Internal vehicle flow that if reverse engineered could enable third party vehicle control. Largely a competitive question, could be set LOW if manufacturer and operator are not concerned with this type of compromise. | Includes vehicle control commands, which must be timely and accurate to support safe vehicle operation. | Includes vehicle control commands, which must be timely and accurate to support safe vehicle operation. | |||
| 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 environmental data | Low | Moderate | Moderate |
| 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. | This could be used for safety applications, and in areas of severe weather a corrupted field could have significant consequences; however, any vehicle will use other inputs before triggering automatic safety facilities, so MODERATE should be sufficient. DISC: WYO believes this to be HIGH. | This data is required for the system to operate properly. If this data is not available, the system cannot give accurate warning information. | |||
| 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 | Other Vehicles | vehicle maneuver coordination | Low | High | Low |
| Data contained within this flow is intended to alert other nearby vehicles to a desired or impending movement by the source vehicle. The data does include identifiers indicating the sending vehicle, which needs to be recognized and protected as appropriate. It may be impractical to encrypt this data to meet performance requirements, and in any event no more than one vehicle would be identified and only in the field environment, so mass collection of this information would be difficult. | This flow is core to automated vehicle merge and lane change operations; flaws in the data could result in a crash, and so integrity should be ensured to the highest practical level. | L4/5 ADS will operate more smoothly if this flow works, but as the vehicle fleet will include L0 vehicles for the foreseeable future, any ADS must use other methods to ensure safe operation anyway. May be MODERATE in ADS-dedicated facilities. | |||
| Vehicle | Other Vehicles | vehicle platoon coordination | Low | High | Moderate |
| Includes the identity of the lead vehicle but no PII. Intended for vehicles to coordinate tightly, and with no previous relationship so likely open to other vehicles monitoring. | Platooning coordination data must be correct or potentially severe consequences can result, particularly if data relevant to high speed operations is corrupted. | Platooning will not fully function without this flow; the worst case is that vehicles drop from the platoon however; lack of this flow is unlikely to generate a severe incident on its own. | |||
| Vehicle | Transportation Information Center | automated vehicle control status | Moderate | Moderate | Moderate |
| Automated vehicle operating conditions could imply PII, and as they are internal measures should be provided only to intended recipients. | Automated vehicle operating conditions, if reported incorrectly, could result in warnings or operations responses that are inappropriate. | Other mechanisms for determining this information are unlikely, but given compettive concerns, applications will have to be designed to work without this data. | |||
| Vehicle | Transportation Information Center | vehicle environmental data | Low | Moderate | Moderate |
| 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. | This could be used for safety applications, and in areas of severe weather a corrupted field could have significant consequences; however, any vehicle will use other inputs before triggering automatic safety facilities, so MODERATE should be sufficient. DISC: WYO believes this to be HIGH. | This data is required for the system to operate properly. If this data is not available, the system cannot give accurate warning information. | |||
| Vehicle | Transportation Information Center | vehicle profile | Low | High | Moderate |
| Includes no PII and probably includes information that could be observed, so no need for obfuscation. | As this information will be used to determine the vehicle's ability to access services or be charged usage fees, it must be correct and not easily forgeable. | This flow enables various services; if the flow is not available the vehicle may not be able to use those services, and also may be charged incorrectly. | |||
| Vehicle Characteristics | ITS Roadway Equipment | vehicle characteristics | |||
| Vehicle Characteristics | Vehicle | vehicle characteristics | |||
| Vulnerable Road Users | Vehicle | vulnerable road user presence | |||
Standards
The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages. These pages can be accessed directly from the SVG diagram(s) located on the Physical tab, by clicking on each information flow line on the diagram.
| Name | Title | Known Issues | Physical Object |
|---|---|---|---|
| ISO 15623 Fwd Collision Performance | Intelligent transport systems -- Forward vehicle collision warning systems -- Performance requirements and test procedures | Vehicle | |
| ISO 24100 Probe Vehicle Data Protection | Intelligent transport systems -- Basic principles for personal data protection in probe vehicle information services | Traffic Management Center | |
| Transportation Information Center | |||
| ISO/SAE PAS 22736 Automation Taxonomy | Taxonomy and Definitions for Terms Related to Driving Automation Systems for On-Road Motor Vehicles | Vehicle | |
| 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 | |||
| SAE J3016 Automation Taxonomy | Taxonomy and Definitions for Terms Related to Driving Automation Systems for On-Road Motor Vehicles | Vehicle | |
| SAE J3251 CDA Pedestrian Collision Avoidance | Cooperative Driving Automation (CDA) Feature: Perception Status Sharing for Occluded Pedestrian Collision Avoidance | Vehicle | |
| SAE J3316 CDA Reference Architecture | Draft not available (Critical): under development | Vehicle | |
| SAE J3361 Antenna requirements | V2X Antenna Coverage and Test Requirements for US FHWA Class 1 and Class 3-13 Class Vehicles | Draft not available (Critical): under development | Vehicle |
| SAE J5001 OBU Standard | Onboard Unit Standard for Connected Vehicles | Draft not available (Critical): under development | Vehicle |
System Requirements
| No System Requirements |