• About
  • Connected Vehicle
  • Architecture
  • Approach
  • Viewpoints
  • Security
• Applications
• Views
  • Enterprise
  • Functional
  • Physical
  • Communications
• Standards
  • CV Standards
  • CV Standards Plan
• Resources
  • Databases
  • Diagrams
  • Documents
  • Presentations
  • Tools
  • Training
• Glossary
  • Acronyms
• Contact Us

Eco-Approach and Departure at Signalized Intersections

The Eco-Approach and Departure at Signalized Intersections application uses wireless data communications sent from a roadside equipment (RSE) unit to connected vehicles to encourage "green" approaches to and departures from signalized intersections. The application, located in a vehicle, collects intersection geometry information and signal phase movement information using V2I communications and data from nearby vehicles using V2V communications. Upon receiving this information, the application performs calculations to provide speed advice to the driver of the vehicle allowing the driver to adapt the vehicle's speed to pass the next traffic signal on green or to decelerate to a stop in the most eco-friendly manner. The application also considers a vehicle's acceleration as it departs from a signalized intersection. Finally, the application may perform engine adjustments that provide increased fuel efficiency.

• 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

Hide Legend

Business Interaction Matrix:

Eco-Approach and Departure at Signalized Intersections Operations Stage
	Vehicle Owner	Driver	Vehicle OBE Owner	Roadway Owner	RSE Owner	RSE Operator	ITS Roadway Equipment Owner	ITS Roadway Operator	Traffic Manager	Vehicle Basic Safety Provider	Remote Vehicle OBE Owner	Vehicle Eco-Driving Assist Provider	RSE Intersection Management Provider
Vehicle Owner		Vehicle Usage Agreement	Vehicle OBE Usage Agreement							Application 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				Application Usage Agreement
RSE Operator					Operations Agreement
ITS Roadway Equipment Owner								Operations Agreement	Information Exchange and Action Agreement
ITS Roadway Operator		Expectation of Information Provision					Operations Agreement
Traffic Manager					Information Exchange Agreement		Information Exchange and Action Agreement
Vehicle Basic Safety Provider	Application Usage Agreement
Remote Vehicle OBE Owner		Presumption of Correct Operation	Expectation of Data Provision
Vehicle Eco-Driving Assist Provider	Application Usage Agreement
RSE Intersection Management Provider					Application Usage Agreement

Eco-Approach and Departure at Signalized Intersections Maintenance Stage
	Vehicle Owner	Vehicle OBE Manufacturer	Vehicle Manufacturer	RSE Deployer	RSE Owner	ITS Roadway Equipment Owner	Traffic Manager	RSE Provider	Vehicle Basic Safety Provider	Vehicle Basic Safety Maintainer	TMC Signal Control Maintainer	TMC Signal Control Provider	RSE Traffic Monitoring Provider	RSE Traffic Monitoring Maintainer	Vehicle Eco-Driving Assist Provider	Vehicle Eco-Driving Assist Maintainer	Roadway Signal Control Provider	Roadway Signal Control Maintainer	RSE Intersection Management Provider	RSE Intersection Management Maintainer	Roadway Owner
Vehicle Owner		Warranty	Warranty						Warranty						Warranty
Vehicle OBE Manufacturer	Warranty		Vehicle Data Access Agreement							Mobile Component Maintenance Agreement						Mobile Component Maintenance Agreement
Vehicle Manufacturer	Warranty	Vehicle Data Access Agreement
RSE Deployer					RSE Deployment Agreement									Field Component Maintenance Agreement						Field Component Maintenance Agreement
RSE Owner				RSE Deployment Agreement				RSE Procurement Agreement					Warranty						Warranty		Device Placement and Operations Agreement
ITS Roadway Equipment Owner																	Warranty	Maintenance Agreement
Traffic Manager											Backoffice Component Maintenance Agreement	Warranty
RSE Provider					RSE Procurement Agreement
Vehicle Basic Safety Provider	Warranty												Application Interface Specification						Application Interface Specification
Vehicle Basic Safety Maintainer		Mobile Component Maintenance Agreement
TMC Signal Control Maintainer							Backoffice Component Maintenance Agreement
TMC Signal Control Provider							Warranty										Application Interface Specification		Application Interface Specification
RSE Traffic Monitoring Provider					Warranty				Application Interface Specification
RSE Traffic Monitoring Maintainer				Field Component Maintenance Agreement
Vehicle Eco-Driving Assist Provider	Warranty
Vehicle Eco-Driving Assist Maintainer		Mobile Component Maintenance Agreement
Roadway Signal Control Provider						Warranty						Application Interface Specification							Application Interface Specification
Roadway Signal Control Maintainer						Maintenance Agreement
RSE Intersection Management Provider					Warranty				Application Interface Specification			Application Interface Specification					Application Interface Specification
RSE Intersection Management Maintainer				Field Component Maintenance Agreement
Roadway Owner					Device Placement and Operations Agreement

Eco-Approach and Departure at Signalized Intersections Installation Stage
	Vehicle Owner	Vehicle OBE Manufacturer	Vehicle Manufacturer	RSE Deployer	RSE Owner	ITS Roadway Equipment Owner	Traffic Manager	RSE Provider	Vehicle Basic Safety Provider	Vehicle Basic Safety Installer	TMC Signal Control Installer	TMC Signal Control Provider	RSE Traffic Monitoring Provider	RSE Traffic Monitoring Installer	Vehicle Eco-Driving Assist Provider	Vehicle Eco-Driving Assist Installer	Roadway Signal Control Provider	Roadway Signal Control Installer	RSE Intersection Management Provider	RSE Intersection Management Installer	Roadway Owner
Vehicle Owner		Mobile Component License Agreement	Vehicle Procurement Agreement
Vehicle OBE Manufacturer	Mobile Component License Agreement		Vehicle Data Access Agreement						Application Procurement Agreement	Mobile Component Installation Agreement					Application Procurement Agreement	Mobile Component Installation Agreement
Vehicle Manufacturer	Vehicle Procurement Agreement	Vehicle Data Access Agreement							Interface Description						Interface Description
RSE Deployer					RSE Deployment Agreement															Field Component Installation Agreement
RSE Owner				RSE Deployment Agreement				RSE Procurement Agreement					Application Procurement Agreement						Application Procurement Agreement		Device Placement and Operations Agreement
ITS Roadway Equipment Owner																	Application Procurement Agreement	Installation Agreement
Traffic Manager											Backoffice Component Installation Agreement	Application Procurement Agreement
RSE Provider					RSE Procurement Agreement
Vehicle Basic Safety Provider		Application Procurement Agreement	Interface Description										Application Interface Specification						Application Interface Specification
Vehicle Basic Safety Installer		Mobile Component Installation Agreement
TMC Signal Control Installer							Backoffice Component Installation Agreement
TMC Signal Control Provider							Application Procurement Agreement										Application Interface Specification		Application Interface Specification
RSE Traffic Monitoring Provider					Application Procurement Agreement				Application Interface Specification
RSE Traffic Monitoring Installer
Vehicle Eco-Driving Assist Provider		Application Procurement Agreement	Interface Description
Vehicle Eco-Driving Assist Installer		Mobile Component Installation Agreement
Roadway Signal Control Provider						Application Procurement Agreement						Application Interface Specification							Application Interface Specification
Roadway Signal Control Installer						Installation Agreement
RSE Intersection Management Provider					Application Procurement Agreement				Application Interface Specification			Application Interface Specification					Application Interface Specification
RSE Intersection Management Installer				Field Component Installation Agreement
Roadway Owner					Device Placement and Operations Agreement

Eco-Approach and Departure at Signalized Intersections Certification Stage
	Vehicle OBE Manufacturer	Application Certification Entity	Federal Regulatory	State Regulatory	Traffic Manager	RSE Provider	Device Certification Entity	ITS Certification Entity
Vehicle OBE Manufacturer		Member					Member
Application Certification Entity	Member		Member	Member	Member
Federal Regulatory		Member					Member
State Regulatory		Member					Member
Traffic Manager		Member						Member
RSE Provider							Member
Device Certification Entity	Member		Member	Member		Member
ITS Certification Entity					Member

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 Management 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 Management 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 Management 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 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.
RSE Traffic Monitoring 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 Traffic Monitoring 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 Traffic Monitoring 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.
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 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 Basic 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.
Vehicle Basic 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.
Vehicle Basic 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.
Vehicle Eco-Driving Assist 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 Eco-Driving Assist 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 Eco-Driving Assist 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 Management	"RSE Intersection Management" uses short range communications to support connected vehicle applications that manage signalized intersections. It communicates with approaching vehicles and ITS infrastructure (e.g., the traffic signal controller) to enhance traffic signal operations. Coordination with the ITS infrastructure also supports conflict monitoring to ensure the RSE output and traffic signal control output are consistent and degrade in a fail safe manner.
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.
RSE Traffic Monitoring	"RSE Traffic Monitoring" monitors the basic safety messages that are shared between connected vehicles and distills this data into traffic flow measures that can be used to manage the network in combination with or in lieu of traffic data collected by infrastructure-based sensors. As connected vehicle penetration rates increase, the measures provided by this application can expand beyond vehicle speeds that are directly reported by vehicles to include estimated volume, occupancy, and other measures. This object also supports incident detection by monitoring for changes in speed and vehicle control events that indicate a potential incident.
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 Basic Safety	"Vehicle Basic Safety" exchanges current vehicle location and motion information with other vehicles in the vicinity, uses that information to calculate vehicle paths, and warns the driver when the potential for an impending collision is detected. If available, map data is used to filter and interpret the relative location and motion of vehicles in the vicinity. Information from on-board sensors (e.g., radars and image processing) are also used, if available, in combination with the V2V communications to detect non-equipped vehicles and corroborate connected vehicle data. Vehicle location and motion broadcasts are also received by the infrastructure and used by the infrastructure to support a wide range of roadside safety and mobility applications. This object represents a broad range of implementations ranging from basic Vehicle Awareness Devices that only broadcast vehicle location and motion and provide no driver warnings to advanced integrated safety systems that may, in addition to warning the driver, provide collision warning information to support automated control functions that can support control intervention.
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 Eco-Driving Assist	"Vehicle Eco-Driving Assist" provides customized real-time driving advice to drivers, allowing them to adjust behaviors to save fuel and reduce emissions. This advice includes recommended driving speeds, optimal acceleration and deceleration profiles based on prevailing traffic conditions, and local interactions with nearby vehicles, i.e., processing Basic Safety Messages (BSMs) to determine position and speed of vehicles that are between the host vehicle and the intersection. When approaching and departing signalized intersections, it uses intersection geometry information, the relative position and speed of vehicles ahead of it, and signal phase movement information to provide speed advice to the driver so that the driver can adapt the vehicle's speed to pass the next traffic signal on green, decelerate to a stop in the most eco-friendly manner, or manage acceleration as the vehicle departs from a signalized intersection. It also provides feedback to drivers on their driving behavior to encourage them to drive in a more environmentally efficient manner. It may also support vehicle-assisted strategies, where the vehicle automatically implements the eco-driving strategy (e.g., changes gears, switches power sources, or reduces its speed in an eco-friendly manner as the vehicle approaches a traffic signal or queue).
Vehicle Environmental Monitoring	"Vehicle Environmental Monitoring" collects data from on-board sensors and systems related to environmental conditions and sends the collected data to the infrastructure as the vehicle travels. The collected data is a byproduct of vehicle safety and convenience systems and includes ambient air temperature and precipitation measures and status of the wipers, lights, ABS, and traction control systems.
Vehicle 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.
Backoffice Component Maintenance Agreement	Agreement	An agreement in which one entity maintains the operational status of the backoffice 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.
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.
Information Exchange and Action 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. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
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.
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.2	Process and Store Traffic Data	Collection
1.1.2.6	Process Collected Vehicle Safety Data	Pspec	- RSE Intersection Management - RSE Traffic Monitoring
1.1.6	Collect Vehicle Traffic Surveillance Data	Pspec	- RSE Intersection Management - RSE Traffic Monitoring
1.2	Provide Device Control	Collection
1.2.1	Select Strategy	Pspec	- TMC Signal Control
1.2.4	Output Control Data	Collection
1.2.4.1	Output Control Data for Roads	Pspec	- TMC Signal Control
1.2.4.3	Output In-vehicle Signage Data	Pspec	- 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 Management - RSE Traffic Monitoring
1.2.7.7	Process Vehicle Safety and Environmental Data for Output	Pspec	- RSE Intersection Management
1.2.7.15	Process Intersection Safety Data	Pspec	- RSE Intersection Management - RSE Traffic Monitoring
1.2.7.16	Process Signal Control Conflict Monitoring	Pspec	- Roadway Signal Control
1.2.8	Collect Traffic Field Equipment Fault Data	Pspec	- TMC Signal Control
3.1	Monitor Vehicle Status	Collection
3.1.1	Produce Collision and Crash Avoidance Data	Pspec	- Vehicle Basic Safety
3.1.3	Process Vehicle On-board Data	Pspec	- Vehicle Basic Safety - Vehicle Eco-Driving Assist
3.1.4	Communicate with Remote Vehicles	Pspec	- Vehicle Basic Safety
3.1.6	Provide Vehicle Acceleration and Deceleration Inputs	Pspec	- Vehicle Basic Safety - Vehicle Eco-Driving Assist
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 Basic Safety
6.7.1.4	Update Vehicle Navigable Map Database	Pspec	- Vehicle Basic Safety
6.7.3	Provide Traveler Services in Vehicle	Collection
6.7.3.2	Provide Driver with Personal Travel Information	Pspec	- Vehicle Eco-Driving Assist
6.7.3.3	Provide Driver Information Interface	Pspec	- Vehicle Basic Safety - Vehicle Eco-Driving Assist

Includes Data Flows:

Source Pspec	Data Flow	Destination Pspec
Collect Traffic Field Equipment Fault Data	indicator_fault_state	Select Strategy
Collect Vehicle Traffic Surveillance Data	vehicle_traffic_roadside_equip_status	Collect Traffic Field Equipment Fault Data
Collect Vehicle Traffic Surveillance Data	vehicle_situation_data_raw	Process Collected Vehicle Safety Data
Collect Vehicle Traffic Surveillance Data	vehicle_traffic_situation_data_configuration	Process Vehicle On-board 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
Communicate with Remote Vehicles	remote_vehicle_status_for_eco_drive	Provide Vehicle Acceleration and Deceleration Inputs
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	vehicle_sign_data_for_roads	Output In-vehicle Signage Data
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
Output In-vehicle Signage Data	infrastructure_warning_signage	Process In-vehicle Signage Data
Output In-vehicle Signage Data	vehicle_sign_data	Process In-vehicle Signage Data
Output In-vehicle Signage Data	vehicle_signage_reduced_speed_zone_data	Process In-vehicle Signage Data
Output In-vehicle Signage Data	vehicle_signage_stop_sign_gap_data	Process In-vehicle Signage Data
Output In-vehicle Signage Data	vehicle_signage_configuration	Process In-vehicle Signage Data
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	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	reduced_speed_signage_message_output	Output In-vehicle Signage Data
Process In-vehicle Signage Data	infrastructure_restriction_signage_message_output	Output In-vehicle Signage Data
Process In-vehicle Signage Data	vehicle_sign_status	Output In-vehicle Signage Data
Process In-vehicle Signage Data	speed_vehicle_sign_status	Output In-vehicle Signage Data
Process In-vehicle Signage Data	infrastructure_vehicle_sign_status	Output In-vehicle Signage Data
Process In-vehicle Signage Data	stop_sign_gap_signage_message_output	Output In-vehicle Signage Data
Process In-vehicle Signage Data	stop_sign_gap_sign_status	Output In-vehicle Signage 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_traffic_situation_data	Collect Vehicle Traffic Surveillance Data
Process Vehicle On-board Data	vehicle_traffic_probe_data_for_archive	Collect Vehicle Traffic Surveillance Data
Process Vehicle On-board Data	vehicle_characteristics_for_roadside	Collect Vehicle Traffic Surveillance Data
Process Vehicle On-board Data	vehicle_system_characteristics_for_roadside	Collect Vehicle Traffic Surveillance Data
Process Vehicle On-board Data	vehicle_roadside_surveillance_status_data	Collect Vehicle Traffic Surveillance Data
Process Vehicle On-board Data	vehicle_roadside_surveillance_location_data	Collect Vehicle Traffic Surveillance Data
Process Vehicle On-board Data	vehicle_roadside_surveillance_size_data	Collect Vehicle Traffic Surveillance Data
Process Vehicle On-board Data	vehicle_roadside_surveillance_speed_data	Collect Vehicle Traffic Surveillance 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 On-board Data	host_vehicle_status_for_eco_drive	Provide Vehicle Acceleration and Deceleration Inputs
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	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 Information Interface	vehicle_control_request	Provide Vehicle Acceleration and Deceleration Inputs
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	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

Hide Legend

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 Management	"RSE Intersection Management" uses short range communications to support connected vehicle applications that manage signalized intersections. It communicates with approaching vehicles and ITS infrastructure (e.g., the traffic signal controller) to enhance traffic signal operations. Coordination with the ITS infrastructure also supports conflict monitoring to ensure the RSE output and traffic signal control output are consistent and degrade in a fail safe manner.	Roadside Equipment
RSE Traffic Monitoring	"RSE Traffic Monitoring" monitors the basic safety messages that are shared between connected vehicles and distills this data into traffic flow measures that can be used to manage the network in combination with or in lieu of traffic data collected by infrastructure-based sensors. As connected vehicle penetration rates increase, the measures provided by this application can expand beyond vehicle speeds that are directly reported by vehicles to include estimated volume, occupancy, and other measures. This object also supports incident detection by monitoring for changes in speed and vehicle control events that indicate a potential incident.	Roadside Equipment
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 Basic Safety	"Vehicle Basic Safety" exchanges current vehicle location and motion information with other vehicles in the vicinity, uses that information to calculate vehicle paths, and warns the driver when the potential for an impending collision is detected. If available, map data is used to filter and interpret the relative location and motion of vehicles in the vicinity. Information from on-board sensors (e.g., radars and image processing) are also used, if available, in combination with the V2V communications to detect non-equipped vehicles and corroborate connected vehicle data. Vehicle location and motion broadcasts are also received by the infrastructure and used by the infrastructure to support a wide range of roadside safety and mobility applications. This object represents a broad range of implementations ranging from basic Vehicle Awareness Devices that only broadcast vehicle location and motion and provide no driver warnings to advanced integrated safety systems that may, in addition to warning the driver, provide collision warning information to support automated control functions that can support control intervention.	Vehicle OBE
Vehicle Eco-Driving Assist	"Vehicle Eco-Driving Assist" provides customized real-time driving advice to drivers, allowing them to adjust behaviors to save fuel and reduce emissions. This advice includes recommended driving speeds, optimal acceleration and deceleration profiles based on prevailing traffic conditions, and local interactions with nearby vehicles, i.e., processing Basic Safety Messages (BSMs) to determine position and speed of vehicles that are between the host vehicle and the intersection. When approaching and departing signalized intersections, it uses intersection geometry information, the relative position and speed of vehicles ahead of it, and signal phase movement information to provide speed advice to the driver so that the driver can adapt the vehicle's speed to pass the next traffic signal on green, decelerate to a stop in the most eco-friendly manner, or manage acceleration as the vehicle departs from a signalized intersection. It also provides feedback to drivers on their driving behavior to encourage them to drive in a more environmentally efficient manner. It may also support vehicle-assisted strategies, where the vehicle automatically implements the eco-driving strategy (e.g., changes gears, switches power sources, or reduces its speed in an eco-friendly manner as the vehicle approaches a traffic signal or queue).	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 input	Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands.
driver input information	Driver input received from the driver-vehicle interface equipment via the vehicle bus. It includes configuration data, settings and preferences, interactive requests, and control commands for the connected vehicle on-board equipment.
driver update information	Information provided to the driver-vehicle interface to inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment. The flow includes the information to be presented to the driver and associated metadata that supports processing, prioritization, and presentation by the DVI as visual displays, audible information and warnings, and/or haptic feedback.
driver updates	Information provided to the driver including visual displays, audible information and warnings, and haptic feedback. The updates inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment.
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 management 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 management application status	Infrastructure application status reported by the RSE. This includes current operational state and status of the RSE and a log of operations.
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 device configuration	Data used to configure traffic signal control equipment including local controllers and system masters.
signal control plans	Traffic signal timing parameters including minimum green time and interval durations for basic operation and cycle length, splits, offset, phase sequence, etc. for coordinated systems.
signal control status	Operational and status data of traffic signal control equipment including operating condition and current indications.
signal system configuration	Data used to configure traffic signal systems including configuring control sections and mode of operation (time based or traffic responsive).
vehicle control optimization information	Information provided to the vehicle control system that supports efficient vehicle operation. The flow includes recommended speeds, acceleration, and deceleration profiles optimized for current conditions.
vehicle location and motion	Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size.
vehicle location and motion for surveillance	Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size. This flow represents monitoring of basic safety data ('vehicle location and motion') broadcast by passing connected vehicles for use in vehicle detection and traffic monitoring applications.

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
None: Human interface	Driver	Vehicle OBE	driver input
	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	vehicle location and motion
	Roadside Equipment	Traffic Management Center	intersection management application status
	Roadside Equipment	Vehicle OBE	intersection status
	Roadside Equipment	ITS Roadway Equipment	intersection status monitoring
	Traffic Management Center	Roadside Equipment	intersection management application info
	Traffic Management Center	ITS Roadway Equipment	signal control commands
	Traffic Management Center	ITS Roadway Equipment	signal control device configuration
	Traffic Management Center	ITS Roadway Equipment	signal control plans
	Traffic Management Center	ITS Roadway Equipment	signal system configuration
	Vehicle Databus	Vehicle OBE	driver input information
	Vehicle Databus	Vehicle OBE	host vehicle status
	Vehicle OBE	Vehicle Databus	driver update information
None: Human interface	Vehicle OBE	Driver	driver updates
	Vehicle OBE	Vehicle Databus	vehicle control optimization information
	Vehicle OBE	Remote Vehicle OBEs	vehicle location and motion
	Vehicle OBE	Roadside Equipment	vehicle location and motion for surveillance

Requirements

Need		Requirement
N1.001	Transportation agencies need to gather data from vehicles or infrastructure to support environmental monitoring.	1.001	All environmental applications shall collect data from mobile devices to support environmental monitoring, including ambient air quality, emissions, temperature, precipitation, and other road weather information.
		1.002	All environmental applications shall collect data from infrastructure devices to support environmental monitoring, including ambient air quality, emissions, temperature, precipitation, wind speed, and other road weather information.
N1.041	The Eco-Approach and Departure at Signalized Intersections Vehicle System needs to provide a user interface through which pertinent driver recommendations are provided to the driver.	1.138	The Eco-Approach and Departure at Signalized Intersections Vehicle System shall provide a user interface through which traffic conditions, environmental conditions, driving recommendations, and feedback on driving behavior can be provided to the driver.
N1.049	The Eco-Approach and Departure at Signalized Intersections Vehicle System needs to process current and forecasted conditions data, data from surrounding vehicles, data from the vehicle itself and driver inputs in order to allow the driver to make improved eco-driving decisions.	1.130	The Eco-Approach and Departure at Signalized Intersections Vehicle System shall determine driving recommendations with the objective of promoting a driving style that lowers vehicle emissions.
		1.131	The Eco-Approach and Departure at Signalized Intersections Vehicle System shall use signal phase and timing data, intersection geometry data, traffic data, vehicle sensor data, and vehicle status data from other vehicles to encourage "green" approaches to and departures from signalized intersections.
N1.089	The Eco-Approach and Departure at Signalized Intersections (EADSI) needs to know vehicle status, location, and motion information from both on-board equipment and from remote vehicles.	1.125	The Eco-Approach and Departure at Signalized Intersections Vehicle System shall collect vehicle location and motion data from other vehicles.
		1.126	The Eco-Approach and Departure at Signalized Intersections Vehicle System shall collect data from onboard systems and onboard sensors to obtain vehicle status and vehicle emissions data.
		1.192	EADSI shall collect vehicle characteristics.
N1.090	EADSI needs to know signal states.	1.193	EADSI shall collect signal states.
N1.091	EADSI needs to determine the most economical speed to proceed based on nearby signal states and vehicle characteristics.	1.194	EADSI shall determine the most economical speed to proceed based on nearby signal states and vehicle characteristics.
N1.092	EADSI needs to provide both intersection geometry and signal phase and timing information to vehicles.	1.115	The Eco-Approach and Departure at Signalized Intersections System shall disseminate descriptions about the static physical geometry at intersections and arterial roadway segments.
		1.121	The Eco-Approach and Departure at Signalized Intersections system shall provide intersection geometry information to vehicles.
		1.195	EADSI shall provide signal phase and timing information to vehicles.
N1.093	EADSI needs to provide recommended vehicle speed	1.196	EADSI shall provide recommended vehicle speed to the driver.

Related Sources

• Eco-Signal Operations: Operational Concept, Final, 10/1/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
			Basis	Basis	Basis
Security levels have not been defined yet.