Type: Safety

Groups:

V2I Safety

Diagrams are based on the most recently available application concepts that the CVRIA team has access to, and do not necessarily reflect prototypes or other in-development activities.

Red Light Violation Warning

The Red Light Violation Warning (RLVW) application enables a connected vehicle approaching an instrumented signalized intersection to receive information from the infrastructure regarding the signal timing and the geometry of the intersection. The application in the vehicle uses its speed and acceleration profile, along with the signal timing and geometry information to determine if it appears likely that the vehicle will enter the intersection in violation of a traffic signal. If the violation seems likely to occur, a warning can be provided to the driver. Another usage of this application would be at a railroad crossing where the violation relates to railroad crossings gates that have been activated.

Enterprise
Functional
Physical
A-Interconnect
Communications
Requirements
Sources
Security

Enterprise

This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.

The enterprise diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagrams: Installation Operations Maintenance Certification
PNG Diagrams: Installation Operations Maintenance Certification

Display Legend in SVG or PNG

Business Interaction Matrix:

Red Light Violation Warning Operations Stage
	Vehicle Owner	Driver	Vehicle OBE Owner	Roadway Owner	RSE Owner	RSE Operator	ITS Roadway Equipment Owner	ITS Roadway Operator	Traffic Manager	RSE Intersection Safety Provider	Remote Vehicle OBE Owner	Vehicle Intersection Warning Provider
Vehicle Owner		Vehicle Usage Agreement	Vehicle OBE Usage Agreement									Application Usage Agreement
Driver	Vehicle Usage Agreement		Expectation of Information Provision					Expectation of Information Provision			Presumption of Correct Operation
Vehicle OBE Owner	Vehicle OBE Usage Agreement	Expectation of Information Provision			Expectation of Information Provision						Expectation of Data Provision
Roadway Owner					Service Delivery Agreement
RSE Owner			Expectation of Information Provision	Service Delivery Agreement		Operations Agreement	Information Exchange Agreement		Information Exchange Agreement	Application Usage Agreement
RSE Operator					Operations Agreement
ITS Roadway Equipment Owner					Information Exchange Agreement			Operations Agreement
ITS Roadway Operator		Expectation of Information Provision					Operations Agreement
Traffic Manager					Information Exchange Agreement
RSE Intersection Safety Provider					Application Usage Agreement
Remote Vehicle OBE Owner		Presumption of Correct Operation	Expectation of Data Provision
Vehicle Intersection Warning Provider	Application Usage Agreement

Includes Enterprise Objects:

Enterprise Object	Description
Application Certification Entity	The body that determines whether an application may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with application type. For example, applications with human safety component (crash avoidance, movement assistance etc.) may have stringent requirements and extensive testing in a variety of conditions, while applications that provide strictly mobility functionality may have far less testing requirements; possibly as little as just making sure the application doesn't interfere with any other applications.
Device Certification Entity	The body that determines whether a device may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with device type.
Driver	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.
Federal Regulatory	Federal regulatory bodies that have legal authority to control and/or provide input to policies regulating transportation infrastructure and operations. This includes entities such as the Federal Communications Commission and US Department of Transportation.
ITS Certification Entity	The body that determines whether an ITS device or application may be deployed and operated in the transportation environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with device and application type. Typically not a formal body, assigned on a project-by-project basis depending on the type of infrastructure involved. Since ITS projects are locally-focused (typically state or smaller), the entities that are part of this body are typically those with operational jurisdiction where the ITS is installed (e.g., state or local DOTs, state or local maintenance managers etc.)
ITS Roadway Equipment Owner	The entity that owns the Roadway ITS equipment.
ITS Roadway Operator	The entity that operates the Roadway ITS equipment.
Remote Vehicle OBE Owner	The owner of the Remote Vehicle OBE
Roadway Owner	The owner of the roadway proximate to which roadside equipment will be/is installed.
Roadway Signal Control Installer	Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Roadway Signal Control Maintainer	Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Roadway Signal Control Provider	Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
RSE Deployer	The entity responsible for the deployment, operations and maintenance of roadside equipment.
RSE Intersection Safety Installer	Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
RSE Intersection Safety Maintainer	Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
RSE Intersection Safety Provider	Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
RSE Maintainer	The entity that maintains the roadside equipment, including its hardware and operating system software, but not applications software.
RSE Operator	The entity that operates roadside equipment in the transportation environment.
RSE Owner	The owner of roadside equipment.
RSE Provider	The "RSE Provider" is the entity that develops and (presumably) sells roadside equipment to other entities for deployment and research.
State Regulatory	State regulatory bodies that have legal authority to control and/or provide input to policies regulating vehicles, transportation infrastructure and operations. This includes entities like Departments of Motor Vehicles, property tax authorities and tolling agencies.
TMC Intersection Safety Installer	Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TMC Intersection Safety Provider	Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
TMC Signal Control Installer	Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TMC Signal Control Maintainer	Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TMC Signal Control Provider	Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Traffic Manager	The entity responsible for the management of traffic, both freeway and arterial.
Vehicle Intersection Warning Installer	Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Vehicle Intersection Warning Maintainer	Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Vehicle Intersection Warning Provider	Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Vehicle Manufacturer	The entity that builds, assembles, verifies and validates the Vehicle in which the Vehicle OBE will eventually operate.
Vehicle OBE Manufacturer	The entity that builds, assembles, verifies and validates the Vehicle OBE. This can be an OEM-equipped OBE, retrofit or aftermarket equipment.
Vehicle OBE Owner	The entity, individual, group or corporation that owns the Vehicle On-Board equipment. This could be the same as the Vehicle Owner, but it could be a third part that licenses the use of the OBE to the Owner.
Vehicle Owner	The individual, group of individuals or corporate entity that is identified as the registered owner of the Vehicle under state law.

Includes Resources:

Resource	Description
Application Component Certification Requirements	The requirements that define the functionality, performance and operational environment of an application component. Certification Requirements must be met in order for an application to be installed in the CVE.
Backoffice Service Development System	The systems used to develop backoffice (center) hardware and software components of applications.
Backoffice Service Installation System	The systems used to install and configure backoffice (center) hardware and software components.
Backoffice Service Maintenance System	The systems used to maintain and upgrade backoffice (center) hardware and software components.
Device Certification Requirements	The requirements that define the functionality, performance and operational environment of a connected vehicle device. Certification Requirements must be met in order for the device to be granted the credentials necessary to operate in the Connected Vehicle Environment.
Field Component Development System	The system used in a backoffice environment to develop and test the field component of the application.
Field Component Installation System	The system used to install a field component of a connected vehicle application.
Field Component Maintenance System	The system used to install and configure changes and updates to the field component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance.
ITS Certification Requirements	The requirements that define the functionality, performance and operational environment of an ITS device or ITS application. Applicability varies with jurisdictions, but typically devices and applications must meet pre-defined acceptance criteria prior to usage in the transportation environment.
ITS Field Component Development System	The system used in a backoffice environment to develop and test the ITS field component of the application.
ITS Field Component Installation System	The system used to install a field component of a connected vehicle application.
ITS Field Component Maintenance System	The system used to install and configure changes and updates to the ITS field component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance.
ITS Roadway Equipment	'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 itself. In CVRIA, this physical object represents all of the other ITS field equipment that interfaces with and supports the Connected Vehicle Roadside Equipment (RSE). 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.
Mobile Component Development System	The system used in a backoffice environment to develop and test the mobile component of the application.
Mobile Component Installation System	The system that interacts with the Vehicle OBE other mobile device and installs the mobile component of the application.
Mobile Component Maintenance System	The system used to configure changes and updates to the mobile component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance.
Remote Vehicle OBEs	'Remote 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. In CVRIA, 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 Remote Vehicle OBEs to model all connected vehicle V2V communications in CVRIA.
Roadside Equipment	'Roadside Equipment' (RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.
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.
RSE Development System	The system used in a backoffice environment to develop and test the roadside equipment.
RSE Installation System	The system used to install and configure the roadside equipment.
RSE Intersection Safety	"RSE Intersection Safety" uses short range communications to support connected vehicle applications that improve intersection safety. It communicates with approaching vehicles and ITS infrastructure to alert and warn drivers of potential stop sign, red light, and pedestrian crossing conflicts or violations.
RSE Maintenance System	The system used to configure changes and updates to the roadside equipment. This system is capable of acquiring and reporting diagnostic information about the RSE's configuration and performance.
TMC Intersection Safety	"TMC Intersection Safety" controls and monitors RSEs that support stop sign, red light, and pedestrian crossing violations. It configures the RSEs for the current intersection geometry and traffic signal control equipment at the intersection. Information that is currently being communicated to passing vehicles and the operational status of the field equipment is monitored by this application. The operational status of the field equipment is reported to operations personnel.
TMC Signal Control	"TMC Signal Control" provides the capability for traffic managers to monitor and manage the traffic flow at signalized intersections. This capability includes analyzing and reducing the collected data from traffic surveillance equipment and developing and implementing control plans for signalized intersections. Control plans may be developed and implemented that coordinate signals at many intersections under the domain of a single traffic management center and are responsive to traffic conditions and adapt to support incidents, preemption and priority requests, pedestrian crossing calls, etc.
Traffic Management Center	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.
Vehicle	The conveyance that provides the sensory, processing, storage, and communications functions necessary to support efficient, safe, and convenient travel. These functions reside in general vehicles including personal automobiles, commercial vehicles, emergency vehicles, transit vehicles, or other vehicle types.
Vehicle Databus	The 'Vehicle Databus' represents the interface to the vehicle databus (e.g., CAN, LIN, Ethernet/IP, FlexRay, and MOST) that may enable communication between the Vehicle OBE and other vehicle systems to support connected vehicle applications. The vehicle system statuses and/or sensor outputs available on the databus will vary based on the equipment installed on the vehicle and availability on databus. System statuses and sensor outputs may include select vehicle systems and sensors such as accelerometers, yaw rate sensors, and GPS derived location and timing information. In CVRIA, this physical object is used to represent the onboard interactions between the Vehicle OBE and the other systems included in a host vehicle. Note that the vehicle databus interface is not standardized across all vehicle classes. Also, some Vehicle OBE implementations will not have access to the vehicle databus. See 'Vehicle OBE' for more information.
Vehicle Intersection Warning	"Vehicle Intersection Warning" uses V2V and V2I communications to monitor other connected vehicles at intersections and support the safe movement of the vehicle through the intersection. Driver warnings are provided and the application may also optionally take control of the vehicle to avoid collisions. The application will also notify the infrastructure and other vehicles if it detects an unsafe infringement on the intersection.
Vehicle OBE	The Vehicle On-Board Equipment (OBE) provides the vehicle-based processing, storage, and communications functions necessary to support connected vehicle operations. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle OBE. This communication platform is augmented with processing and data storage capability that supports the connected vehicle applications. In CVRIA, the Vehicle OBE includes the functions and interfaces that support connected vehicle applications for passenger cars, trucks, and motorcycles. Many of these applications (e.g., V2V Safety applications) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle OBE includes the common interfaces and functions that apply to all motorized vehicles.

Includes Roles:

Role	Description
Certifies	An Enterprise verifies that a target Resource meets relevant performance, functional, environmental and quality requirements.
Constrains	A Resource or Enterprise applies requirements, constraints and associated tests to another Resource.
Installs	An Enterprise performs the initial delivery, integration and configuration of the target Resource.
Maintains	An Enterprise administers the hardware and software that comprise the target Resource.
Member	An Enterprise is part of another larger, target Enterprise.
Operates	An Enterprise controls the functionality and state of the target Resource. An Enterprise that Operates a resource is considered Responsible.
Owns	An Enterprise has financial ownership and control over the Resource. An Enterprise that Owns a resource is considered Accountable.

Includes Coordination:

Coordination	Type	Description
Application Installation Data	Information Sharing	Data needed to install the application, including the application executable code and any configuration data. Unidirectional flow.
Application Interface Specification	Agreement	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.
Application Maintenance Data	Information Sharing	Data used to facilitate the upgrade, patching and general health maintenance of an application component.
Application Performance Data	Information Sharing	Data used to characterize application performance, including such measures as availability, known errors and known uses.
Application Procurement Agreement	Agreement	An agreement whereupon one entity provides a copy of an application component to another entity. This component is capable of being installed and functioning, according to its requirements that passed through the application's certification process.
Application Usage Agreement	Agreement	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.
Backoffice Component Installation Agreement	Agreement	An agreement that grants one party permission to install a backoffice application component on a center-based device controlled by the other party.
Device Placement and Operations Agreement	Agreement	An agreement that enables the controller of a physical device to install it (so as to make it operational) at a fixed location controlled by another entity.
Expectation of Data Provision	Expectation	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.
Expectation of Information Provision	Expectation	An expectation where one party believes another party will provide it information whenever such information is likely relevant to the recipient.
Field Component Installation Agreement	Agreement	An agreement that grants one party permission to install a field application component on a roadside device controlled by the other party.
Field Component Maintenance Agreement	Agreement	An agreement in which one entity maintains the operational status of the field component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities.
Includes	Includes	Indicates that one component is entirely contained within another component.
Information Exchange Agreement	Agreement	An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Installation Agreement	Agreement	An agreement whereupon one entity installs an application component on a device controlled by another entity.
Interface Description	Agreement	Documentation of the interface between two systems, where one system does not have an application component that is part of the application, but does provide and/or receive data and/or information that is used by or sourced from the application. In many cases this is an existing interface used by the application, so the description of the interface already exists and is imposed by the terminator.
Maintenance Agreement	Agreement	An agreement in which one entity maintains the operational status of a system under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities.
Maintenance Data Exchange Agreement	Agreement	An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Mobile Component Installation Agreement	Agreement	An agreement whereupon the controller of OBE gives another party permission to install, configure and make operational a component that enables the mobile portion of an application.
Mobile Component License Agreement	Agreement	An end-user license agreement allowing the operator of the mobile device to use the mobile application component that is part of the application in question.
Mobile Component Maintenance Agreement	Agreement	An agreement in which one entity maintains the operational status of the mobile component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities.
Operations Agreement	Agreement	An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Presumption of Correct Operation	Expectation	The assumption made by one party that another party operates their device in a similar and correct fashion. Specific to devices in the transportation environment, this assumption is relevant when devices interact, where one party's device receives information from another's. The operator of the device implicitly trusts that the other device is operating according to a similar set of governing rules as its device.
RSE Deployment Agreement	Agreement	Agreement to install, configure and make operational roadside equipment, between the provider of that equipment and the entity that controls access to the roadside. May define locations, expectation of power provision, backhaul responsibility and installation restrictions.
RSE Installation Data	Information Sharing	Data necessary to configure and make RSE operational. Uni-directional.
RSE Maintenance Data	Information Sharing	Data necessary to modify the operational configuration of RSE; assumes RSE is already configured. Uni-directional.
RSE Performance Data	Information Sharing	Data that includes metrics of RSE performance. Could include fields such as uptime, packets received/transmitted, distance vector from which packets received, as well as application-specific performance measures.
RSE Procurement Agreement	Agreement	An agreement whereupon one entity provides roadside equipment to another entity. The RSE is capable of being installed and functioning, according to its requirements that passed through the device's certification process.
Service Delivery Agreement	Agreement	A relationship where one party agrees to provide a service to the other party. This agreement may specify the expected performance of this service in terms of availability and/or actions/time-type performance specifications.
Vehicle Data Access Agreement	Agreement	An agreement whereby the party that controls access to on-board vehicle data grants another party the right and ability to access that data. Includes the conditions under which data may be accessed, and specifies the mechanisms, including physical and functional access methods, data formats and any other considerations necessary for the accessing party to acquire data. May also include caveats regarding responsibility for data quality and responsibility for use of the data.
Vehicle OBE Usage Agreement	Agreement	An agreement that grants one entity permission to use a Vehicle OBE that the other party controls.
Vehicle Procurement Agreement	Agreement	The exchange of a vehicle for compensation. One entity purchases the vehicle from the other.
Vehicle Usage Agreement	Agreement	An agreement between the owner of a vehicle and a prospective operator, whereupon the owner allows the operator to use the vehicle.
Warranty	Agreement	A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance over time of an application component.

Functional

Includes Processes:

Level	Name	Type	Allocated to Application Object
1.1	Provide Traffic Surveillance	Collection
1.1.1	Process Sensor Data	Collection
1.1.1.6	Collect Vehicle Roadside Safety Data	Pspec	- RSE Intersection Safety
1.1.2	Process and Store Traffic Data	Collection
1.1.2.6	Process Collected Vehicle Safety Data	Pspec	- RSE Intersection Safety
1.2	Provide Device Control	Collection
1.2.1	Select Strategy	Pspec	- TMC Signal Control
1.2.2	Determine Road and Freeway State	Collection
1.2.2.2	Determine Indicator State for Road Management	Pspec	- TMC Intersection Safety - TMC Signal Control
1.2.4	Output Control Data	Collection
1.2.4.1	Output Control Data for Roads	Pspec	- TMC Intersection Safety - TMC Signal Control
1.2.4.7	Manage Roadway Warning System	Pspec	- TMC Intersection Safety - TMC Signal Control
1.2.7	Provide Roadside Control Facilities	Collection
1.2.7.1	Process Indicator Output Data for Roads	Pspec	- Roadway Signal Control
1.2.7.2	Monitor Roadside Equipment Operation	Pspec	- Roadway Signal Control
1.2.7.4	Process In-vehicle Signage Data	Pspec	- RSE Intersection Safety
1.2.7.7	Process Vehicle Safety and Environmental Data for Output	Pspec	- RSE Intersection Safety
1.2.7.12	Control Roadway Warning System	Pspec
1.2.7.15	Process Intersection Safety Data	Pspec	- RSE Intersection Safety
1.2.7.16	Process Signal Control Conflict Monitoring	Pspec	- Roadway Signal Control
1.2.8	Collect Traffic Field Equipment Fault Data	Pspec	- TMC Intersection Safety - TMC Signal Control
3.1	Monitor Vehicle Status	Collection
3.1.1	Produce Collision and Crash Avoidance Data	Pspec	- Vehicle Intersection Warning
3.1.3	Process Vehicle On-board Data	Pspec	- Vehicle Intersection Warning
3.1.4	Communicate with Remote Vehicles	Pspec	- Vehicle Intersection Warning
6.7	Provide Driver Personal Services	Collection
6.7.1	Provide On-line Vehicle Guidance	Collection
6.7.1.3	Process Vehicle Location Data	Pspec	- Vehicle Intersection Warning
6.7.1.4	Update Vehicle Navigable Map Database	Pspec	- Vehicle Intersection Warning
6.7.3	Provide Traveler Services in Vehicle	Collection
6.7.3.2	Provide Driver with Personal Travel Information	Pspec	- Vehicle Intersection Warning
6.7.3.3	Provide Driver Information Interface	Pspec	- Vehicle Intersection Warning

Includes Data Flows:

Source Pspec	Data Flow	Destination Pspec
Collect Traffic Field Equipment Fault Data	indicator_fault_state	Select Strategy
Collect Vehicle Roadside Safety Data	vehicle_safety_input_data	Process Collected Vehicle Safety Data
Communicate with Remote Vehicles	safety_message_data_from_remote_vehicles	Process Vehicle On-board Data
Communicate with Remote Vehicles	intersection_infringement_from_remote_vehicle	Produce Collision and Crash Avoidance Data
Control Roadway Warning System	roadway_warning_device_status	Collect Traffic Field Equipment Fault Data
Control Roadway Warning System	infrastructure_warning_device_status	Collect Traffic Field Equipment Fault Data
Control Roadway Warning System	stop_sign_gap_device_status	Collect Traffic Field Equipment Fault Data
Control Roadway Warning System	roadway_warning_system_status	Manage Roadway Warning System
Control Roadway Warning System	infrastructure_warning_system_status	Manage Roadway Warning System
Control Roadway Warning System	stop_sign_gap_system_status	Manage Roadway Warning System
Control Roadway Warning System	stop_sign_intersection_traffic	Process Intersection Safety Data
Control Roadway Warning System	signage_roadway_warning_from_roadway	Process In-vehicle Signage Data
Control Roadway Warning System	signage_stop_sign_warning_from_roadway	Process In-vehicle Signage Data
Determine Indicator State for Road Management	indicator_road_requested_state	Output Control Data for Roads
Manage Roadway Warning System	roadway_warning_system_control	Control Roadway Warning System
Manage Roadway Warning System	infrastructure_warning_system_control	Control Roadway Warning System
Manage Roadway Warning System	stop_sign_gap_system_control	Control Roadway Warning System
Manage Roadway Warning System	pedestrian_roadside_warning_system_control	Process Intersection Safety Data
Manage Roadway Warning System	intersection_safety_system_controls	Process Intersection Safety Data
Manage Roadway Warning System	stop_sign_gap_roadside_control	Process Intersection Safety Data
Manage Roadway Warning System	queue_warning_roadside_configuration	Process Vehicle Safety and Environmental Data for Output
Monitor Roadside Equipment Operation	indicator_status_from_signals	Collect Traffic Field Equipment Fault Data
Monitor Roadside Equipment Operation	indicator_status_from_traffic_meters	Collect Traffic Field Equipment Fault Data
Monitor Roadside Equipment Operation	indicator_faults_from_signals	Collect Traffic Field Equipment Fault Data
Output Control Data for Roads	indicator_status_for_roads_from_center	Collect Traffic Field Equipment Fault Data
Output Control Data for Roads	indicator_control_configuration_data_for_signal_control	Monitor Roadside Equipment Operation
Output Control Data for Roads	reversible_lane_control_for_roads	Process Indicator Output Data for Roads
Output Control Data for Roads	indicator_control_data_for_signal_control	Process Indicator Output Data for Roads
Output Control Data for Roads	indicator_input_state_for_roads	Select Strategy
Process Collected Vehicle Safety Data	vehicle_traffic_data_from_roadside	Control Roadway Warning System
Process Collected Vehicle Safety Data	vehicle_traffic_data_for_roads	Process Indicator Output Data for Roads
Process Collected Vehicle Safety Data	vehicle_safety_data_indication	Process Vehicle Safety and Environmental Data for Output
Process Collected Vehicle Safety Data	roadway_geometry_location_data	Process Vehicle Safety and Environmental Data for Output
Process Collected Vehicle Safety Data	roadway_intersection_geometry_data	Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads	reversible_lane_control_device_status_from_roads	Collect Traffic Field Equipment Fault Data
Process Indicator Output Data for Roads	indicator_response_data_for_roads	Monitor Roadside Equipment Operation
Process Indicator Output Data for Roads	indicator_input_data_from_signals	Output Control Data for Roads
Process Indicator Output Data for Roads	pedestrian_crosswalk_indicator_for_roadside	Process Intersection Safety Data
Process Indicator Output Data for Roads	roadside_signal_phase_indication	Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads	roadside_signal_phase_timing	Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads	roadside_signal_phase_response_state	Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads	roadside_signal_priority_preempt	Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads	signal_preemption_override	Select Strategy
Process Indicator Output Data for Roads	signal_priority_override	Select Strategy
Process Intersection Safety Data	roadside_intersection_safety_status	Collect Traffic Field Equipment Fault Data
Process Intersection Safety Data	roadside_pedestrian_safety_status	Manage Roadway Warning System
Process Intersection Safety Data	roadside_intersection_safety_status	Manage Roadway Warning System
Process Intersection Safety Data	intersection_infringement_for_indicators	Process Indicator Output Data for Roads
Process Intersection Safety Data	local_traffic_signal_service_request	Process Indicator Output Data for Roads
Process Intersection Safety Data	intersection_warning_for_signage	Process In-vehicle Signage Data
Process Intersection Safety Data	intersection_data_for_signage	Process In-vehicle Signage Data
Process Intersection Safety Data	intersection_status_data_for_vehicle	Process Vehicle On-board Data
Process Intersection Safety Data	intersection_collision_avoidance_data	Produce Collision and Crash Avoidance Data
Process Intersection Safety Data	stop_sign_gap_data_to_vehicle	Produce Collision and Crash Avoidance Data
Process In-vehicle Signage Data	vehicle_sign_status	Collect Traffic Field Equipment Fault Data
Process In-vehicle Signage Data	speed_vehicle_sign_status	Collect Traffic Field Equipment Fault Data
Process In-vehicle Signage Data	infrastructure_vehicle_sign_status	Collect Traffic Field Equipment Fault Data
Process In-vehicle Signage Data	stop_sign_gap_sign_status	Collect Traffic Field Equipment Fault Data
Process In-vehicle Signage Data	vehicle_signage_hri_data	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_individual_vehicle_speed	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_roadway_warning	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_alert_data	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_evacuation_data	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_output_data	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_speed_warning	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_barrier_message	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_emissions_message	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_traffic_data_message	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_traffic_metering_message	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_variable_speed_limit_message	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_reduced_speed_message	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_reduced_speed_zone_definition	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_reduced_speed_zone_timing	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_road_weather_advisory	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_infrastructure_restriction_ahead	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_infrastructure_restriction_warning	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_pedestrian_presence	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_intersection_infringement	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_rail_crossing_warning	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_stop_sign_gap_assist	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_work_zone_intrusion	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_work_zone_information	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_intersection_message	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_queue_warning	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_incident_work_zone	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_dynamic_lane_configuration	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_lane_closure_data	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_road_configuration_data	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_road_closure_data	Provide Driver with Personal Travel Information
Process In-vehicle Signage Data	vehicle_signage_road_diversion_data	Provide Driver with Personal Travel Information
Process Signal Control Conflict Monitoring	conflict_monitor_detection	Process Indicator Output Data for Roads
Process Vehicle Location Data	vehicle_location_for_probe_data	Process Vehicle On-board Data
Process Vehicle Location Data	vehicle_location_in_roadway	Produce Collision and Crash Avoidance Data
Process Vehicle On-board Data	vehicle_roadside_location_data	Collect Vehicle Roadside Safety Data
Process Vehicle On-board Data	vehicle_roadside_speed_data	Collect Vehicle Roadside Safety Data
Process Vehicle On-board Data	vehicle_roadside_size_data	Collect Vehicle Roadside Safety Data
Process Vehicle On-board Data	vehicle_roadside_current_status_data	Collect Vehicle Roadside Safety Data
Process Vehicle On-board Data	safety_message_data_for_remote_vehicles	Communicate with Remote Vehicles
Process Vehicle On-board Data	vehicle_roadside_control_event_data	Process Collected Vehicle Safety Data
Process Vehicle On-board Data	vehicle_status_for_intersection	Process Intersection Safety Data
Process Vehicle On-board Data	collision_data	Produce Collision and Crash Avoidance Data
Process Vehicle On-board Data	vehicle_status_details_for_broadcast	Provide Driver with Personal Travel Information
Process Vehicle Safety and Environmental Data for Output	queue_warning_system_status	Collect Traffic Field Equipment Fault Data
Process Vehicle Safety and Environmental Data for Output	queue_warning_system_status	Manage Roadway Warning System
Process Vehicle Safety and Environmental Data for Output	env_sensor_data_for_advisory_message	Process In-vehicle Signage Data
Process Vehicle Safety and Environmental Data for Output	vehicle_safety_and_roadway_data	Process In-vehicle Signage Data
Process Vehicle Safety and Environmental Data for Output	roadside_signal_monitoring	Process Signal Control Conflict Monitoring
Process Vehicle Safety and Environmental Data for Output	position_correction_to_vehicle	Process Vehicle Location Data
Process Vehicle Safety and Environmental Data for Output	roadside_safety_data_to_vehicle	Process Vehicle On-board Data
Process Vehicle Safety and Environmental Data for Output	signal_phase_indication_to_vehicle	Produce Collision and Crash Avoidance Data
Process Vehicle Safety and Environmental Data for Output	signal_phase_timing_to_vehicle	Produce Collision and Crash Avoidance Data
Process Vehicle Safety and Environmental Data for Output	signal_phase_response_state_to_vehicle	Produce Collision and Crash Avoidance Data
Process Vehicle Safety and Environmental Data for Output	queue_warning_from_roadside	Produce Collision and Crash Avoidance Data
Process Vehicle Safety and Environmental Data for Output	vehicle_env_sensor_data_output	Provide Driver with Personal Travel Information
Process Vehicle Safety and Environmental Data for Output	roadway_geometry_to_vehicle	Update Vehicle Navigable Map Database
Process Vehicle Safety and Environmental Data for Output	roadside_intersection_details_to_vehicle	Update Vehicle Navigable Map Database
Process Vehicle Safety and Environmental Data for Output	roadside_intersection_lanes_to_vehicle	Update Vehicle Navigable Map Database
Process Vehicle Safety and Environmental Data for Output	roadside_map_update_to_vehicle	Update Vehicle Navigable Map Database
Produce Collision and Crash Avoidance Data	intersection_infringement_for_remote_vehicle	Communicate with Remote Vehicles
Produce Collision and Crash Avoidance Data	vehicle_intersection_infringement	Process Intersection Safety Data
Produce Collision and Crash Avoidance Data	position_warnings	Provide Driver with Personal Travel Information
Provide Driver Information Interface	vehicle_display_type	Provide Driver with Personal Travel Information
Provide Driver with Personal Travel Information	vehicle_advisory_information	Provide Driver Information Interface
Provide Driver with Personal Travel Information	vehicle_traveler_information	Provide Driver Information Interface
Provide Driver with Personal Travel Information	vehicle_trip_planning_responses	Provide Driver Information Interface
Select Strategy	selected_hri_control_strategy	Determine Indicator State for Road Management
Select Strategy	selected_road_control_strategy	Determine Indicator State for Road Management
Select Strategy	signal_system_timing_plan	Process Indicator Output Data for Roads
Select Strategy	signal_system_configuration	Process Indicator Output Data for Roads
Select Strategy	intersection_roadside_configuration	Process Intersection Safety Data
Select Strategy	intersection_roadside_sensor_configuration	Process Vehicle Safety and Environmental Data for Output

Physical

This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.

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
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 itself. In CVRIA, this physical object represents all of the other ITS field equipment that interfaces with and supports the Connected Vehicle Roadside Equipment (RSE). 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.
Remote Vehicle OBEs	Vehicle	'Remote 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. In CVRIA, 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 Remote Vehicle OBEs to model all connected vehicle V2V communications in CVRIA.
Roadside Equipment	Field	'Roadside Equipment' (RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.
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.
Vehicle Databus	Vehicle	The 'Vehicle Databus' represents the interface to the vehicle databus (e.g., CAN, LIN, Ethernet/IP, FlexRay, and MOST) that may enable communication between the Vehicle OBE and other vehicle systems to support connected vehicle applications. The vehicle system statuses and/or sensor outputs available on the databus will vary based on the equipment installed on the vehicle and availability on databus. System statuses and sensor outputs may include select vehicle systems and sensors such as accelerometers, yaw rate sensors, and GPS derived location and timing information. In CVRIA, this physical object is used to represent the onboard interactions between the Vehicle OBE and the other systems included in a host vehicle. Note that the vehicle databus interface is not standardized across all vehicle classes. Also, some Vehicle OBE implementations will not have access to the vehicle databus. See 'Vehicle OBE' for more information.
Vehicle OBE	Vehicle	The Vehicle On-Board Equipment (OBE) provides the vehicle-based processing, storage, and communications functions necessary to support connected vehicle operations. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle OBE. This communication platform is augmented with processing and data storage capability that supports the connected vehicle applications. In CVRIA, the Vehicle OBE includes the functions and interfaces that support connected vehicle applications for passenger cars, trucks, and motorcycles. Many of these applications (e.g., V2V Safety applications) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle OBE includes the common interfaces and functions that apply to all motorized vehicles.

Includes Application Objects:

Application Object	Description	Physical Object
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
RSE Intersection Safety	"RSE Intersection Safety" uses short range communications to support connected vehicle applications that improve intersection safety. It communicates with approaching vehicles and ITS infrastructure to alert and warn drivers of potential stop sign, red light, and pedestrian crossing conflicts or violations.	Roadside Equipment
TMC Intersection Safety	"TMC Intersection Safety" controls and monitors RSEs that support stop sign, red light, and pedestrian crossing violations. It configures the RSEs for the current intersection geometry and traffic signal control equipment at the intersection. Information that is currently being communicated to passing vehicles and the operational status of the field equipment is monitored by this application. The operational status of the field equipment is reported to operations personnel.	Traffic Management Center
TMC Signal Control	"TMC Signal Control" provides the capability for traffic managers to monitor and manage the traffic flow at signalized intersections. This capability includes analyzing and reducing the collected data from traffic surveillance equipment and developing and implementing control plans for signalized intersections. Control plans may be developed and implemented that coordinate signals at many intersections under the domain of a single traffic management center and are responsive to traffic conditions and adapt to support incidents, preemption and priority requests, pedestrian crossing calls, etc.	Traffic Management Center
Vehicle Intersection Warning	"Vehicle Intersection Warning" uses V2V and V2I communications to monitor other connected vehicles at intersections and support the safe movement of the vehicle through the intersection. Driver warnings are provided and the application may also optionally take control of the vehicle to avoid collisions. The application will also notify the infrastructure and other vehicles if it detects an unsafe infringement on the intersection.	Vehicle OBE

Includes Information Flows:

Information Flow	Description
conflict monitor status	A control flow that supports failsafe operation in the event that a conflict is detected that requires the RSE to enter a failsafe operating mode.
driver information	Regulatory, warning, and guidance information provided to the driver while en route to support safe and efficient vehicle operation.
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.
host vehicle status	Information provided to the connected vehicle on-board equipment from other systems on the vehicle platform. This includes data from on-board sensors, the current status of the powertrain, steering, and braking systems, and status of 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 Connected Vehicle environment.
intersection control status	Status data provided by the traffic signal controller including phase information, alarm status, and priority/preempt status.
intersection infringement info	Vehicle path information sent by a vehicle that is performing an unpermitted movement at an intersection such as a stop sign violation or running a red light.
intersection safety application info	Intersection and device configuration data and warning parameters and thresholds. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted.
intersection safety application status	Infrastructure safety application status reported by the RSE. This includes current operational state and status of the RSE and a record of intersection safety issues identified and alerts and warnings issued.
intersection safety warning	A warning of an imminent unsafe vehicle infringement at an intersection that may endanger other vehicles or pedestrians. This allows vehicles approaching the intersection to be warned in the event of an imminent red light or stop sign violation or potential infringement on an occupied crosswalk. All connected vehicles at the intersection receive the warning, including both the infringing vehicle and other vehicles at or near the intersection.
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.
intersection status monitoring	Current signal phase and timing information for all lanes at a signalized intersection. This flow represents monitoring of communications by a receiver at the intersection to support monitoring for conflicts between actual signal states and RSE communications about those states.
signal control commands	Control of traffic signal controllers or field masters including clock synchronization.
signal control status	Operational and status data of traffic signal control equipment including operating condition and current indications.
vehicle location and motion	Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size.

Application Interconnect Diagram

This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.

The application interconnect diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram

Application Triples

Communications Diagram(s)	Source	Destination	Information Flow
	ITS Roadway Equipment	Roadside Equipment	conflict monitor status
None: Human interface	ITS Roadway Equipment	Driver	driver information
	ITS Roadway Equipment	Roadside Equipment	intersection control status
	ITS Roadway Equipment	Traffic Management Center	signal control status
	Remote Vehicle OBEs	Vehicle OBE	intersection infringement info
	Remote Vehicle OBEs	Vehicle OBE	vehicle location and motion
	Roadside Equipment	ITS Roadway Equipment	intersection infringement info
	Roadside Equipment	Traffic Management Center	intersection safety application status
	Roadside Equipment	Vehicle OBE	intersection safety warning
	Roadside Equipment	Vehicle OBE	intersection status
	Roadside Equipment	ITS Roadway Equipment	intersection status monitoring
	Traffic Management Center	Roadside Equipment	intersection safety application info
	Traffic Management Center	ITS Roadway Equipment	signal control commands
	Vehicle Databus	Vehicle OBE	host vehicle status
	Vehicle OBE	Vehicle Databus	driver update information
None: Human interface	Vehicle OBE	Driver	driver updates
	Vehicle OBE	Roadside Equipment	intersection infringement info
	Vehicle OBE	Remote Vehicle OBEs	intersection infringement info
	Vehicle OBE	Roadside Equipment	vehicle location and motion
	Vehicle OBE	Remote Vehicle OBEs	vehicle location and motion

Requirements

Need		Requirement
N3.045	Red Light Violation Warning (RLVW) needs SPaT information from the intersection signal controller so that it can determine if the host vehicle is at risk of violating the signal.	3.099	Red Light Violation Warning (RLVW) shall acquire SPaT information from the intersection signal controller at a signalized intersection near to and in the vehicle's direction of travel.
N3.046	RLVW needs to warn potential violators of signal control status in time for the driver to take appropriate action.	3.100	RLVW shall warn the driver of a potential violation of a traffic signal.
N3.046		3.101	RLVW shall determine when the vehicle must begin slowing in order to safely avoid violating a signal.
N3.047	RLVW needs to know the location of stop bars at the intersection where RLVW is operating so that it can calculate when it needs to notify the driver to stop.	3.102	RLVW shall acquire the locations of stop bars at the intersections near and relevant to the direction of travel of the vehicle.
N3.065	Red Light Violation Warning (RLVW) needs to, as appropriate, alert or warn the driver to reduce speed in order to avoid violating a signal.	3.148	RLVW shall compute whether the vehicle is traveling at a velocity that indicates it is at risk of violating the signal.
N3.065		3.149	RLVW shall warn the driver to reduce speed when the host vehicle is traveling at a velocity that indicates it is at risk of violating the signal.
N3.066	Data to determine Red Light Violation Warning (RLVW) needs to include the location of the stop bars at signalized intersections at which it operates.	3.136	Red Light Violation Warning (RLVW) shall acquire the location of the stop bars at signalized intersections at which RLVW is operating.
N3.067	RLVW needs to know the location and velocity of vehicles approaching a signalized intersection at which it operates.	3.137	RLVW shall be able to collect vehicle location information from vehicles near the intersection at which RLVW is operating.
		3.138	RLVW shall be able to collect vehicle velocity information from vehicles near the intersection at which RLVW is operating.
		3.139	RLVW shall be able to collect vehicle heading information from vehicles near the intersection at which RLVW is operating.
N3.068	RLVW needs to determine if a vehicle may violate the stop bar at a signalized intersection.	3.140	RLVW shall calculate if a vehicle is likely to violate the stop bar at a signalized intersection based on its current speed, heading, acceleration, location and the location of stop bars.
N3.069	RLVW needs to know the current and short term future signal state at a signalized intersection.	3.141	RLVW shall acquire Signal Phase & Timing (SPaT) data for the intersection at which RLVW is operating.
N3.070	RLVW needs to know the location of the stop bars at railroad grade crossings.	3.142	RLVW shall acquire the location of the stop bars at railroad grade crossings at which RLVW is operating.
N3.071	RLVW needs to know the location and velocity of vehicles approaching a railroad grade crossing near intersections where RLVW operates.	3.143	RLVW shall be able to collect vehicle location information from vehicles near the crossing at which RLVW is operating.
		3.144	RLVW shall be able to collect vehicle velocity information from vehicles near the railroad grade crossing at which RLVW is operating.
		3.145	RLVW shall be able to collect vehicle location and heading information from vehicles near the railroad grade crossing at which RLVW is operating.
N3.072	RLVW needs to determine if a vehicle may violate the stop bar at a railroad grade crossing at which RLVW operates.	3.146	RLVW shall calculate if a vehicle is likely to violate the stop bar at a signalized intersection based on its current speed, heading, acceleration, location and the location of stop bars.
N3.073	RLVW needs to know the current and short term future signal state at a railroad grade crossing at which RLVW operates.	3.147	RLVW shall acquire SPaT data for the intersections that are near a railroad crossing at which RLVW is operating.
N3.104	Vehicle to Infrastructure (V2I) Safety applications need to assess their own performance, to determine errors and avoid failures when critical components fail.	3.207	Vehicle to Infrastructure (V2I) Safety applications shall analyze their own 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.
		3.208	V2I Safety applications shall notify the driver when onboard components are offline
		3.209	V2I Safety applications shall notify its owner/operator when onboard components are offline.
N3.105	V2I Safety applications need to broadcast the performance of their host vehicle, to enable V2I applications that rely on knowing the location and/or trajectories of other vehicles.	3.210	V2I Safety applications shall broadcast the location, speed, acceleration, heading, steering wheel angle, brake system status, vehicle size and path history of host vehicles.
N3.106	V2I Safety applications need to have a common time source so that location and projected positions may be synchronized.	3.211	V2I Safety applications shall have a common time source.
N3.107	V2I Safety applications need to have positioning accurate enough to create alerts and/or warnings when warranted.	3.212	V2I Safety applications shall provide a means for any System component to determine its geographic position, in three dimensions.
N3.108	V2I Safety applications need to have positioning accurate enough to avoid false positive alerts and/or warnings.	3.213	V2I Safety applications shall provide position data together with a measure of the accuracy of the geographic position.

Related Sources

Accelerated Vehicle to Infrastructure (V2I) Safety Applications Concept of Operations Document, B, 3/26/2013
SAE J3067- Candidate Improvements to Dedicated Short Range Communications (DSRC) Message Set Dictionary (SAE J2735)Using Systems Engineering Methods, 8/15/2014

Security

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

Physical Object Security
Physical Object	Confidentiality	Integrity	Availability	Security Class
Security levels have not been defined yet.

In order to participate in this application, 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
Security levels have not been defined yet.