Parent Service Package: PS03
< < PS03.5 : PS03.6 : PS03.7 > >

PS03.6: Wide Area Wireless Implementation

Signal Preemption is requested via wide-area wireless (e.g., cellular) to a third-party provider that coordinates with the Traffic Management Center to preempt the signal for the emergency vehicle.

Relevant Regions:

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
Emergency Vehicle OBE Developer	Emergency Vehicle OBE	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.
ITS Roadway Equipment Developer	ITS Roadway Equipment	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
Emergency Vehicle OBE Installer	Emergency Vehicle OBE	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.
Emergency Vehicle OBE Owner	Emergency Vehicle OBE Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Emergency Vehicle OBE Owner	Emergency Vehicle OBE 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.
ITS Roadway Equipment Installer	ITS Roadway Equipment	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.
ITS Roadway Equipment Owner	ITS Roadway Equipment Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
ITS Roadway Equipment Owner	ITS Roadway Equipment 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
Emergency Personnel	Emergency Vehicle OBE	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.
Emergency Personnel	ITS Roadway Equipment	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.
Emergency Vehicle OBE Maintainer	Emergency Vehicle OBE	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.
Emergency Vehicle OBE Manager	Emergency Personnel	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.
Emergency Vehicle OBE Manager	Emergency Vehicle OBE	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.
Emergency Vehicle OBE Owner	Emergency Vehicle OBE 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.
Emergency Vehicle OBE Owner	Emergency Vehicle OBE Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Emergency Vehicle OBE Supplier	Emergency Vehicle OBE Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
ITS Roadway Equipment Maintainer	ITS Roadway Equipment	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.
ITS Roadway Equipment Manager	Emergency Personnel	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.
ITS Roadway Equipment Manager	ITS Roadway Equipment	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.
ITS Roadway Equipment Owner	ITS Roadway Equipment 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.
ITS Roadway Equipment Owner	ITS Roadway Equipment Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
ITS Roadway Equipment Supplier	ITS Roadway Equipment 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 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
ITS Roadway Equipment	Roadway Signal Control	1.1.1.1	Process Traffic Sensor Data
		1.2.7.1	Process Indicator Output Data for Roads
		1.2.7.13	Provide Device Interface for Field Management Stations
		1.2.7.16	Process Signal Control Conflict Monitoring
		1.2.7.2	Monitor Roadside Equipment Operation
		1.2.7.8	Provide Device Interface to Other Roadway Devices
Traffic Management Center	TMC Signal Control	1.1.2.2	Process Traffic Data
		1.1.2.5	Process Vehicle Situation Data
		1.1.4.1	Retrieve Traffic Data
		1.1.4.4	Manage Traffic Archive Data
		1.1.5	Exchange Data with Other Traffic Centers
		1.2.1	Select Strategy
		1.2.2.2	Determine Indicator State for Road Management
		1.2.4.1	Output Control Data for Roads
		1.2.6.1	Maintain Traffic and Sensor Static Data
		1.2.8	Collect Traffic Field Equipment Fault Data
Transportation Information Center	TIC Traffic Control Dissemination	6.2.2	Collect Traffic Data
Transportation Information Center	TIC Traffic Control Dissemination	6.5.1	Provide Broadcast Data 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
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.
ITS Roadway Equipment	Field	'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway. This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.
Traffic Management Center	Center	The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.
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.

Includes Functional Objects:

Functional Object	Description	Physical Object
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
Roadway Signal Control	'Roadway Signal Control' includes the field elements that monitor and control signalized intersections. It includes the traffic signal controllers, detectors, conflict monitors, signal heads, and other ancillary equipment that supports traffic signal control. It also includes field masters, and equipment that supports communications with a central monitoring and/or control system, as applicable. The communications link supports upload and download of signal timings and other parameters and reporting of current intersection status. It represents the field equipment used in all levels of traffic signal control from basic actuated systems that operate on fixed timing plans through adaptive systems. It also supports all signalized intersection configurations, including those that accommodate pedestrians. In advanced, future implementations, environmental data may be monitored and used to support dilemma zone processing and other aspects of signal control that are sensitive to local environmental conditions.	ITS Roadway Equipment
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 Signal Control	'TMC Signal Control' provides the capability for traffic managers to monitor and manage the traffic flow at signalized intersections. This capability includes analyzing and reducing the collected data from traffic surveillance equipment and developing and implementing control plans for signalized intersections. Control plans may be developed and implemented that coordinate signals at many intersections under the domain of a single Traffic Management Center and are responsive to traffic conditions and adapt to support incidents, preemption and priority requests, pedestrian crossing calls, etc. This may include adaptive traffic control systems (ATCS) that adjust signal timings based on traffic conditions, demand, and system capacity. It also supports all signalized intersection configurations, including those that accommodate pedestrians.	Traffic Management Center

Includes Information Flows:

Information Flow	Description
driver information	Regulatory, warning, guidance, and other information provided to the driver to support safe and efficient vehicle operation.
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 traffic control information	Status of a special traffic control strategy or system activation implemented in response to an emergency traffic control request, a request for emergency access routes, a request for evacuation, a request to activate closure systems, a request to employ driver information systems to support public safety objectives, or other special requests. Identifies the selected traffic control strategy and system control status.
emergency traffic control request	Special request to preempt the current traffic control strategy in effect at one or more signalized intersections or highway segments, activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver information systems. For example, this flow can request all signals to red-flash, request a progression of traffic control preemptions along an emergency vehicle route, request a specific evacuation traffic control plan, request activation of a road closure barrier system, or place a public safety or emergency-related message on a dynamic message sign.
intersection status	Current signal phase and timing information for all lanes at a signalized intersection. This flow identifies active lanes and lanes that are being stopped and specifies the length of time that the current state will persist for each lane. It also identifies signal priority and preemption status and pedestrian crossing status information where applicable. It may also include future signal phase and timing information.
signal preemption request	Direct request for preemption to a traffic signal controller that results in preemption of the current control plan and grants right-of-way to the requesting vehicle. This flow identifies the required phase and timing of the preemption. This flow may also cancel the preemption request (e.g., when the requesting vehicle clears the intersection).
signal priority status	In response to a request for signal priority, this flow indicates the status of the priority or preemption request.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor	Goal

Associated Objective Categories

Objective Category

Associated Objectives and Performance Measures

Objective	Performance Measure

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

Needs and Requirements

Need		Functional Object	Requirement

Related Sources

Document Name	Version	Publication Date
None

Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object	Confidentiality	Integrity	Availability	Security Class
Emergency Vehicle OBE
ITS Roadway Equipment
Traffic Management Center
Transportation Information Center

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
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 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	signal preemption request	Not Applicable	High	Moderate
Emergency Vehicle OBE	Transportation Information Center	signal preemption request	It does not matter if someone is able to eavesdrop on this request. There will be many other more obvious indicators that the request was made, such as sirens and flashing lights on the emergency vehicle.	The system must be able to trust these requests. Emergency Vehicles should be able to send these requests and know that they are being operated on by the receiving system. Additionally, if an unauthorized vehicle is able to send these requests it could bring traffic to a standstill by disrupting signal coordination citywide.	The alternative to this request is existing mechanisms – such as using the sirens to stop traffic. The difference between the emergency signal preemption application and existing practice is not significant enough to justify a HIGH availability requirement.
ITS Roadway Equipment	Emergency Personnel	driver information	Not Applicable	High	High
ITS Roadway Equipment	Emergency Personnel	driver information	This data is sent to all drivers and is also directly observable, by design.	This is the primary signal trusted by the driver to decide whether to go through the intersection and what speed to go through the intersection at; if it’s wrong, accidents could happen.	If the lights are out you have to get a policeman to direct traffic – expensive and inefficient and may cause a cascading effect due to lack of coordination with other intersections.
Traffic Management Center	Transportation Information Center	emergency traffic control information	Moderate	High	Moderate
Traffic Management Center	Transportation Information Center	emergency traffic control information	This can potentially include sensitive information, such as response information to emergencies.	Invalid messages could lead to an unauthorized user gaining transit signal priority at an intersection. This could also be used to bring traffic to a standstill, which could lead to a large financial impact on the community.	These messages are important to help with the transit signal priority application. Without them, it will not work. However, if these signals are not received, the Emergency Vehicle can still navigate through the intersection using Lights and Sirens. The TMC should have an acknowledgement of the receipt of a message.
Traffic Management Center	Transportation Information Center	intersection status	Not Applicable	High	Moderate
Traffic Management Center	Transportation Information Center	intersection status	This data is distributed using a variety of mechanisms, some of which are localized broadcast; it is desireable that all potential users get this information.	If this flow is not accurate or delivered in a timely fashion then a large variety of mobility and safety services that depend on it will not work properly.	If this flow is not accurate or delivered in a timely fashion then a large variety of mobility and safety services that depend on it will not work properly.
Transportation Information Center	Emergency Vehicle OBE	signal priority status	Low	Moderate	Low
Transportation Information Center	Emergency Vehicle OBE	signal priority status	Not much could be learned by observing this flow, just the state of the priority request and the identity of the requester. Both of those are information that can be gleaned by physical observation, and give little advantage to an observer.	Signal priority status information enables the receiving vehicle to proceed with more surety toward's its next stop; while there are obvious redundancies, a degree of confidence in the state of the message is required for user acceptance if nothing else.	The most important aspect of this flow is the initiating request and hopefull success of that priority message; if that succeeds then the signal will turn in the vehicle's favor, making this flow a 'nice-to-have' that should be correct if it arrives, but is not necessary for the priority application to function.
Transportation Information Center	Traffic Management Center	emergency traffic control request	Moderate	High	Moderate
Transportation Information Center	Traffic Management Center	emergency traffic control request	These requests could be used to track the specific route that an emergency vehicle is planning on taking.	False requests here could bring the traffic system to a standstill by making all of the lights red. Additionally, the system must be able to trust these requests, and know that they came from an authorized source.	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.

Standards

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

Name	Title	Physical Object
ITE 5201 ATC	Advanced Transportation Controller	ITS Roadway Equipment
ITE 5202 ATC Model 2070	Model 2070 Controller Standard	ITS Roadway Equipment
ITE 5301 ATC ITS Cabinet	Intelligent Transportation System Standard Specification for Roadside Cabinets	ITS Roadway Equipment
ITE 5401 ATC API	Application Programming Interface Standard for the Advanced Transportation Controller	ITS Roadway Equipment
NEMA TS 8 Cyber and Physical Security	Cyber and Physical Security for Intelligent Transportation Systems	ITS Roadway Equipment
NEMA TS 8 Cyber and Physical Security		Traffic Management Center
NEMA TS2 Traffic Controller Assemblies	Traffic Controller Assemblies with NTCIP Requirements	ITS Roadway Equipment

System Requirements

No System Requirements