Parent Service Package: VS04
< < VS04.1 : VS04.2 : VS04.3 > >

VS04.2: Commercial WAW Emergency Vehicle Alert Implementation

The special vehicle alerts are provided by a third party provider that uses wide-area wireless communication to provide special vehicle alerts to vehicles in the vicinity.

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
(hide)

Source	Destination	Role/Relationship
Basic Vehicle Developer	Basic Vehicle	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Vehicle Developer	Basic Vehicle Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Vehicle Developer	Vehicle	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.

Installation Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Basic Vehicle Installer	Basic Vehicle	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Basic Vehicle Owner	Basic Vehicle Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Basic Vehicle Owner	Basic Vehicle Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Vehicle Installer	Vehicle	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Vehicle Owner	Vehicle Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Vehicle Owner	Vehicle Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.

Operations and Maintenance Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Basic Vehicle Maintainer	Basic Vehicle	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Basic Vehicle Manager	Basic Vehicle	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Basic Vehicle Manager	Driver	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Basic Vehicle Owner	Basic Vehicle Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Basic Vehicle Owner	Basic Vehicle Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Basic Vehicle Supplier	Basic Vehicle Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Driver	Basic Vehicle	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Driver	Vehicle	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Vehicle Maintainer	Vehicle	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Vehicle Manager	Driver	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Vehicle Manager	Vehicle	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Vehicle Owner	Basic Vehicle Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Vehicle Owner	Basic Vehicle Owner	Expectation of Data Provision (hide) An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data.
Vehicle Owner	Basic Vehicle User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Vehicle Owner	Driver	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Vehicle Owner	Driver	Vehicle Operating Agreement (hide) An agreement whereupon the controller of a vehicle grants another entity permission and rights to operate the vehicle.
Vehicle Owner	Vehicle Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Vehicle Owner	Vehicle Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Vehicle Supplier	Vehicle Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.

Functional

This service package includes the following Functional View PSpecs:

Physical Object	Functional Object	PSpec Number	PSpec Name
Emergency Management Center	Emergency Routing	5.2	Provide Operator Interface for Emergency Data
		5.3.6	Maintain Vehicle Status
		5.3.7	Provide Emergency Vehicle Route
		5.5	Update Emergency Display Map Data
		5.7.1	Assess System Status For Disasters
		5.7.3	Assess System Status For Evacuation
Emergency Vehicle OBE	EV On-Board En Route Support	5.3.3	Provide Emergency Vehicle Location
		5.3.5	Provide Emergency Personnel Interface
		5.3.9	Process Mobile Emergency Requests
Transportation Information Center	TIC Traffic Control Dissemination	6.2.2	Collect Traffic Data
		6.5.1	Provide Broadcast Data Interface
		6.5.2	Provide Interactive 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 Control Automation	3.2.3.3	Process Data for Vehicle Actuators
		3.2.3.4.1	Provide Servo Control
		3.2.3.4.2	Provide Vehicle Control Data Interface
	Vehicle Control 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.2.3.5.1	Process General Vehicle Sensor Data
		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.
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.
Emergency Management Center	Center	The 'Emergency Management Center' represents systems that support incident management, disaster response and evacuation, security monitoring, and other security and public safety-oriented ITS applications. It includes the functions associated with fixed and mobile public safety communications centers including public safety call taker and dispatch centers operated by police (including transit police), fire, and emergency medical services. It includes the functions associated with Emergency Operations Centers that are activated at local, regional, state, and federal levels for emergencies and the portable and transportable systems that support Incident Command System operations at an incident. This Center also represents systems associated with towing and recovery, freeway service patrols, HAZMAT response teams, and mayday service providers. It manages sensor and surveillance equipment used to enhance transportation security of the roadway infrastructure (including bridges, tunnels, interchanges, and other key roadway segments) and the public transportation system (including transit vehicles, public areas such as transit stops and stations, facilities such as transit yards, and transit infrastructure such as rail, bridges, tunnels, or bus guideways). It provides security/surveillance services to improve traveler security in public areas not a part of the public transportation system. It monitors alerts, advisories, and other threat information and prepares for and responds to identified emergencies. It coordinates emergency response involving multiple agencies with peer centers. It stores, coordinates, and utilizes emergency response and evacuation plans to facilitate this coordinated response. Emergency situation information including damage assessments, response status, evacuation information, and resource information are shared The Emergency Management Center also provides a focal point for coordination of the emergency and evacuation information that is provided to the traveling public, including wide-area alerts when immediate public notification is warranted. It tracks and manages emergency vehicle fleets using real-time road network status and routing information from the other centers to aid in selecting the emergency vehicle(s) and routes, and works with other relevant centers to tailor traffic control to support emergency vehicle ingress and egress, implementation of special traffic restrictions and closures, evacuation traffic control plans, and other special strategies that adapt the transportation system to better meet the unique demands of an emergency.
Emergency Personnel	Vehicle	'Emergency Personnel' represents personnel that are responsible for police, fire, emergency medical services, towing, service patrols, and other special response team (e.g., hazardous material clean-up) activities at an incident site. These personnel are associated with the Emergency Vehicle during dispatch to the incident site, but often work independently of the Emergency Vehicle while providing their incident response services.
Emergency Vehicle OBE	Vehicle	The 'Emergency Vehicle On-Board Equipment' (OBE) resides in an emergency vehicle and provides the processing, storage, and communications functions that support public safety-related connected vehicle applications. It represents a range of vehicles including those operated by police, fire, and emergency medical services. In addition, it represents other incident response vehicles including towing and recovery vehicles and freeway service patrols. It includes two-way communications to support coordinated response to emergencies. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including emergency vehicles. The Emergency Vehicle OBE supplements these general capabilities with capabilities that are specific to emergency vehicles.
Other Transportation Information Centers	Center	Representing another Transportation Information Center, this object is intended to provide a source and destination for ITS information flows between peer information and service provider functions. It enables cooperative information sharing between providers as conditions warrant.
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.

Includes Functional Objects:

Functional Object	Description	Physical Object
Emergency Routing	'Emergency Routing' supports routing of emergency vehicles and enlists support from the Traffic Management Center to facilitate travel along these routes. Routes may be determined based on real-time traffic information and road conditions or routes may be provided by the Traffic Management Center on request. Vehicles are tracked and routes are based on current vehicle location. It may coordinate with the Traffic Management Center to provide preemption or otherwise adapt the traffic control strategy along the selected route. It may also coordinate with Transportation Information Centers to notify other drivers of public safety vehicles that are enroute.	Emergency Management Center
EV On-Board En Route Support	'EV On-Board En Route Support' provides communications functions to responding emergency vehicles that reduce response times and improve safety of responding public safety personnel and the general public. It supports traffic signal preemption via short range communication directly with signal control equipment.	Emergency Vehicle OBE
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
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

Includes Information Flows:

Information Flow	Description
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.
emergency personnel information presentation	Presentation of information to emergency personnel in the field including dispatch information, incident information, current road network conditions, device status, and other supporting information.
emergency personnel input	User input from emergency personnel in the field including dispatch coordination, incident status information, and remote device control requests.
emergency vehicle tracking data	The current location and operating status of the emergency vehicle.
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.
special vehicle alert	Notification that a vehicle is in the vicinity that requires special attention from drivers. In this context, 'special vehicle' refers to any type of vehicle that uses lights or placards to alert drivers including public safety vehicles, oversize vehicles, slow vehicles, and service vehicles that stop and back up frequently.
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.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor	Goal

Associated Objective Categories

Objective Category

Associated Objectives and Performance Measures

Objective	Performance Measure

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

Needs and Requirements

Need		Functional Object	Requirement
01	The Driver needs to receive warnings of nearby special vehicles (which can include emergency vehicles, maintenance vehicles, or oversize commercial vehicles) if those special vehicles are approaching the Driver’s Vehicle in order to allow the driver to take appropriate actions.	Emergency Routing	16	The center shall provide special vehicle alert information to a third party provider so that vehicles can be warned that are in the vicinity of the dispatched emergency vehicle.
		EV On-Board En Route Support	09	The emergency vehicle shall send the vehicle's location, speed and direction to a third party provider for distribution to vehicles in the vicinity.
		TIC Traffic Control Dissemination	08	The center shall notify vehicles in the vicinity when an emergency vehicle issues a special vehicle alert
		Vehicle Basic Safety Communication	03	The vehicle shall provide its location with road-level accuracy to on-board applications.
		Vehicle Basic Safety Communication	06	The vehicle shall exchange location and motion information with roadside equipment and nearby vehicles.
		Vehicle Control Warning	06	The vehicle shall receive emergency vehicle location information.
		Vehicle Control Warning	07	The vehicle shall notify the Driver of the presence of emergency vehicles nearby that may affect the host vehicle.
02	The Connected Vehicle needs to be able to provide warnings to the driver or control actions to the vehicle based upon warnings received from nearby special vehicles.	Vehicle Basic Safety Communication	01	The vehicle shall collect location and motion data from the vehicle platform.
		Vehicle Control Automation	13	The vehicle shall be capable of performing control actions based upon warnings received from nearby special vehicles.
		Vehicle Control Warning	08	The vehicle shall provide warnings to the driver based upon warnings received from nearby special vehicles.
		Vehicle Control Warning	10	The Vehicle shall provide its location with lane-level accuracy to on-board warning applications.

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
Emergency Management Center	Moderate	High	Moderate	Class 3
Emergency Vehicle OBE	Moderate	High	Moderate	Class 3
Other Transportation Information Centers	Moderate	High	Moderate	Class 3
Transportation Information Center	Moderate	High	Moderate	Class 3
Vehicle	Not Applicable	Low	Moderate	Class 1
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
Source	Destination	Information Flow	Basis	Basis	Basis
Basic Vehicle	Vehicle	driver input information	Moderate	High	High
Basic Vehicle	Vehicle	driver input information	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
Basic Vehicle	Vehicle	host vehicle status	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
Driver	Vehicle	driver input	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.
Emergency Management Center	Transportation Information Center	special vehicle alert	Moderate	High	Moderate
Emergency Management Center	Transportation Information Center	special vehicle alert	This flow is related to a flow that is effectively broadcast and intended for all, but since this flow goes between centers, an observer could learn of the locations of emergency vehicles on a broad scale by monitoring, increasing the awareness of a potentially nefarious actor. Thus, should probably be protected at some level.	The recipient must be sure that the originator is legitimate, as many of these alerts demand action by the recipient (pull over, make way, etc.). Since this power could easily be abused, it should be difficult to forge. Since this power is also often tied to emergency vehicle (life-saving) activity, it should not be interfered with. Availability is MODERATE because other mechanism (sirens, flashing lights) exist to provide the same message.	The recipient must be sure that the originator is legitimate, as many of these alerts demand action by the recipient (pull over, make way, etc.). Since this power could easily be abused, it should be difficult to forge. Since this power is also often tied to emergency vehicle (life-saving) activity, it should not be interfered with. Availability is MODERATE because other mechanism (sirens, flashing lights) exist to provide the same message.
Emergency Personnel	Emergency Vehicle OBE	emergency personnel input	Moderate	Moderate	Moderate
Emergency Personnel	Emergency Vehicle OBE	emergency personnel input	Some of the information, such as incident status information, is sensitive, and should be protected.	The system must know that these requests came from actual Emergency Personal. Additionally, incorrect information here may lead to the system responding incorrectly to the incident	These messages are important for the system to operate properly. Additionally, the system must know if messages are not received so that it can act accordingly.
Emergency Vehicle OBE	Emergency Management Center	emergency vehicle tracking data	Moderate	Moderate	Moderate
Emergency Vehicle OBE	Emergency Management Center	emergency vehicle tracking data	Emergency Vehicles give obvious visual and audio indicators about their location and operating status. Knowing the location of every single emergency vehicle within a city could be extremely useful information to a criminal. Additionally, although this is observable data, it is transmitted on a regional level, which means that someone who is able to intercept it would be able to read the location of all emergency vehicles, not just the ones they could directly observed. A sufficiently motivated criminal can however get this information by other means.	Incorrect data here could lead to incorrect decisions being made about the closure of lanes, or incorrect information being shared with the emergency vehicles. There should be other indicators that would contradict incorrect information transmitted here.	This information may be used to determine which emergency vehicle is dispatched, and having this information available could lead to a quicker response from the emergency vehicle. However, the system would still be able to operate properly if only most messages make it through.
Emergency Vehicle OBE	Emergency Personnel	emergency personnel information presentation	Moderate	Moderate	Moderate
Emergency Vehicle OBE	Emergency Personnel	emergency personnel information presentation	Some of this information, such as incident information, is sensitive and should be protected.	This information could affect how the Emergency Personnel respond to the event, and should be as accurate as possible.	This information needs to be available for the Emergency Personnel in order for them to respond accurately to the system. If they do not acknowledge this information, dispatch needs to know, so they can attempt to contact the Emergency Personnel via another channel, such as radio.
Emergency Vehicle OBE	Transportation Information Center	special vehicle alert	Moderate	High	Moderate
Emergency Vehicle OBE	Transportation Information Center	special vehicle alert	This flow is related to a flow that is effectively broadcast and intended for all, but since this flow goes to a center, an observer could learn of the locations of the emergency vehicle acting as source from a remote location, which may contribute to a nefarious actor's situtational awareness. Thus, should probably be protected at some level.	The recipient must be sure that the originator is legitimate, as many of these alerts demand action by the recipient (pull over, make way, etc.). Since this power could easily be abused, it should be difficult to forge. Since this power is also often tied to emergency vehicle (life-saving) activity, it should not be interfered with. Availability is MODERATE because other mechanism (sirens, flashing lights) exist to provide the same message.	The recipient must be sure that the originator is legitimate, as many of these alerts demand action by the recipient (pull over, make way, etc.). Since this power could easily be abused, it should be difficult to forge. Since this power is also often tied to emergency vehicle (life-saving) activity, it should not be interfered with. Availability is MODERATE because other mechanism (sirens, flashing lights) exist to provide the same message.
Other Transportation Information Centers	Transportation Information Center	special vehicle alert	Moderate	High	Moderate
Other Transportation Information Centers	Transportation Information Center	special vehicle alert	This flow is related to a flow that is effectively broadcast and intended for all, but since this flow goes between centers, an observer could learn of the locations of emergency vehicles on a broad scale by monitoring, increasing the awareness of a potentially nefarious actor. Thus, should probably be protected at some level.	The recipient must be sure that the originator is legitimate, as many of these alerts demand action by the recipient (pull over, make way, etc.). Since this power could easily be abused, it should be difficult to forge. Since this power is also often tied to emergency vehicle (life-saving) activity, it should not be interfered with. Availability is MODERATE because other mechanism (sirens, flashing lights) exist to provide the same message.	The recipient must be sure that the originator is legitimate, as many of these alerts demand action by the recipient (pull over, make way, etc.). Since this power could easily be abused, it should be difficult to forge. Since this power is also often tied to emergency vehicle (life-saving) activity, it should not be interfered with. Availability is MODERATE because other mechanism (sirens, flashing lights) exist to provide the same message.
Transportation Information Center	Other Transportation Information Centers	special vehicle alert	Moderate	High	Moderate
Transportation Information Center	Other Transportation Information Centers	special vehicle alert	This flow is related to a flow that is effectively broadcast and intended for all, but since this flow goes between centers, an observer could learn of the locations of emergency vehicles on a broad scale by monitoring, increasing the awareness of a potentially nefarious actor. Thus, should probably be protected at some level.	The recipient must be sure that the originator is legitimate, as many of these alerts demand action by the recipient (pull over, make way, etc.). Since this power could easily be abused, it should be difficult to forge. Since this power is also often tied to emergency vehicle (life-saving) activity, it should not be interfered with. Availability is MODERATE because other mechanism (sirens, flashing lights) exist to provide the same message.	The recipient must be sure that the originator is legitimate, as many of these alerts demand action by the recipient (pull over, make way, etc.). Since this power could easily be abused, it should be difficult to forge. Since this power is also often tied to emergency vehicle (life-saving) activity, it should not be interfered with. Availability is MODERATE because other mechanism (sirens, flashing lights) exist to provide the same message.
Transportation Information Center	Vehicle	special vehicle alert	Not Applicable	High	Moderate
Transportation Information Center	Vehicle	special vehicle alert	This flow is effectively broadcast and intended for all, so no need to obfuscate its contents.	The recipient must be sure that the originator is legitimate, as many of these alerts demand action by the recipient (pull over, make way, etc.). Since this power could easily be abused, it should be difficult to forge. Since this power is also often tied to emergency vehicle (life-saving) activity, it should not be interfered with. Availability is MODERATE because other mechanism (sirens, flashing lights) exist to provide the same message.	The recipient must be sure that the originator is legitimate, as many of these alerts demand action by the recipient (pull over, make way, etc.). Since this power could easily be abused, it should be difficult to forge. Since this power is also often tied to emergency vehicle (life-saving) activity, it should not be interfered with. Availability is MODERATE because other mechanism (sirens, flashing lights) exist to provide the same message.
Vehicle	Basic Vehicle	driver update information	Low	Moderate	Moderate
Vehicle	Basic Vehicle	driver update information	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
Vehicle	Basic Vehicle	vehicle control	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
Vehicle	Driver	driver updates	This data is informing the driver about the safety of a nearby area. It should not contain anything sensitive, and does not matter if another person can observe it.	This is the information that is presented to the driver. If they receive incorrect information, they may act in an unsafe manner. However, there are other indicators that would alert them to any hazards, such as an oncoming vehicle or crossing safety lights.	If this information is not made available to the driver, then the system has not operated correctly.
Vehicle Characteristics	Vehicle	vehicle characteristics
Vehicle Characteristics	Vehicle	vehicle characteristics

Standards

The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages. These pages can be accessed directly from the SVG diagram(s) located on the Physical tab, by clicking on each information flow line on the diagram.

Name	Title	Physical Object
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	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
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		Vehicle
SAE J3361 Antenna requirements	V2X Antenna Coverage and Test Requirements for US FHWA Class 1 and Class 3-13 Class Vehicles	Emergency Vehicle OBE
SAE J3361 Antenna requirements		Vehicle
SAE J5001 OBU Standard	Onboard Unit Standard for Connected Vehicles	Emergency Vehicle OBE
SAE J5001 OBU Standard	Onboard Unit Standard for Connected Vehicles	Vehicle

System Requirements

No System Requirements