Type: Environmental

Groups:
  • AERIS/ Sustainable Travel
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.

Eco-Cooperative Adaptive Cruise Control

The Eco-Cooperative Adaptive Cruise Control (Eco-CACC) application is an extension to the adaptive cruise control (ACC) concept. Eco-Cooperative Adaptive Cruise Control includes longitudinal automated vehicle control while considering eco-driving strategies. In addition to on-board sensors used in ACC, the application makes use of V2V communications to determine the preceding vehicle's speed, acceleration, and location. This application allows following vehicles to use CACC aimed at relieving a driver from manually adjusting his or her speed to maintain a constant speed and a safe time gap from the lead vehicle. The Eco-Cooperative Adaptive Cruise Control application incorporates other information, such as road grade, roadway geometry, and road weather information, to determine the most environmentally efficient trajectory for the following vehicle. In the long term, the application may also consider vehicle platooning, where two or more vehicles travel with small gaps, reducing aerodynamic drag. Platooning relies on V2V communication that allows vehicles to accelerate or brake with minimal lag to maintain the platoon with the lead vehicle. The reduction in drag results in reduced fuel consumption, greater fuel efficiency, and less pollution for vehicles. This application is applicable to all vehicle classes and is similar to the Cooperative Adaptive Cruise Control application.

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:

Eco-Cooperative Adaptive Cruise Control Operations Stage
Vehicle OwnerDriverVehicle OBE OwnerRoadway OwnerRSE OwnerRSE OperatorITS Roadway Equipment OwnerITS Roadway OperatorTraffic ManagerTraffic Operations PersonnelRSE Environmental Monitoring ProviderRemote Vehicle OBE OwnerRSE Traffic Monitoring ProviderRSE Automated Vehicle Operations ProviderVehicle Basic Safety ProviderVehicle Environmental Monitoring ProviderVehicle Cooperative Cruise Control Provider
Vehicle OwnerVehicle Usage AgreementVehicle OBE Usage AgreementApplication Usage AgreementApplication Usage AgreementApplication Usage Agreement
DriverVehicle Usage AgreementExpectation of Information ProvisionPresumption of Correct Operation
Vehicle OBE OwnerVehicle OBE Usage AgreementExpectation of Information ProvisionExpectation of Information ProvisionExpectation of Data Provision
Roadway OwnerService Delivery Agreement
RSE OwnerExpectation of Information ProvisionService Delivery AgreementOperations AgreementInformation Exchange AgreementInformation Exchange and Action AgreementApplication Usage AgreementApplication Usage AgreementApplication Usage Agreement
RSE OperatorOperations Agreement
ITS Roadway Equipment OwnerInformation Exchange AgreementOperations AgreementInformation Exchange and Action Agreement
ITS Roadway OperatorOperations Agreement
Traffic ManagerInformation Exchange and Action AgreementInformation Exchange and Action AgreementEmployment Agreement
Traffic Operations PersonnelEmployment Agreement
RSE Environmental Monitoring ProviderApplication Usage Agreement
Remote Vehicle OBE OwnerPresumption of Correct OperationExpectation of Data Provision
RSE Traffic Monitoring ProviderApplication Usage Agreement
RSE Automated Vehicle Operations ProviderApplication Usage Agreement
Vehicle Basic Safety ProviderApplication Usage Agreement
Vehicle Environmental Monitoring ProviderApplication Usage Agreement
Vehicle Cooperative Cruise Control ProviderApplication 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 Basic Surveillance 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 Basic Surveillance 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 Basic Surveillance 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.
Roadway Environmental 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.
Roadway Environmental 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.
Roadway Environmental 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.
Roadway Owner The owner of the roadway proximate to which roadside equipment will be/is installed.
RSE Automated Vehicle Operations 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 Automated Vehicle Operations 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 Automated Vehicle Operations 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 Environmental 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 Environmental 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 Environmental 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.
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.
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 Automated Vehicle Operations 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 Automated Vehicle Operations 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 Automated Vehicle Operations 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 Environmental 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.
TMC Environmental 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.
TMC Environmental 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.
TMC Traffic Surveillance 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 Traffic Surveillance 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 Traffic Surveillance 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.
Traffic Operations Personnel 'Traffic Operations Personnel' represents the people that operate a traffic management center. These personnel interact with traffic control systems, traffic surveillance systems, incident management systems, work zone management systems, and travel demand management systems. They provide operator data and command inputs to direct system operations to varying degrees depending on the type of system and the deployment scenario.
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 Cooperative Cruise 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.
Vehicle Cooperative Cruise 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.
Vehicle Cooperative Cruise 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.
Vehicle Environmental 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.
Vehicle Environmental 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.
Vehicle Environmental 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.
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 Basic Surveillance "Roadway Basic Surveillance" monitors traffic conditions using fixed equipment such as loop detectors and CCTV cameras.
Roadway Environmental Monitoring "Roadway Environmental Monitoring" measures environmental conditions and communicates the collected information back to a center where it can be monitored and analyzed. A broad array of general weather and road surface information may be collected. Weather conditions that may be measured include temperature, wind, humidity, precipitation, and visibility. Surface and sub-surface sensors can measure road surface temperature, moisture, icing, salinity, and other measures.
RSE Automated Vehicle Operations "RSE Automated Vehicle Operations" includes the field elements that monitor and control access to and egress from automated lanes. It monitors and coordinates automated vehicle operations within the lanes. These lanes support vehicles operating in platoons with short headways.
RSE Development System The system used in a backoffice environment to develop and test the roadside equipment.
RSE Environmental Monitoring "RSE Environmental Monitoring" collects environmental situation (probe) data from passing vehicles that are equipped with short range communications capability. The collected data includes current environmental conditions as measured by on-board sensors (e.g., ambient temperature and precipitation measures), current status of vehicle systems that can be used to infer environmental conditions (e.g., status of lights, wipers, ABS, and traction control systems), and emissions measures reported by the vehicle. The application object collects the provided data, aggregates and filters the data based on provided configuration parameters, and sends the collected information back to a center for processing and distribution. This application object may also process the collected data locally and issue short-term road weather advisories for the road segment using short range communications.
RSE Installation System The system used to install and configure the roadside equipment.
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 Automated Vehicle Operations "TMC Automated Vehicle Operations" remotely monitors and controls automated lanes. It monitors system operation and provides parameters that control system operation including system parameters that govern vehicle platoon formation, speeds, and gaps or headways.
TMC Environmental Monitoring "TMC Environmental Monitoring" assimilates current and forecast road conditions and surface weather information using a combination of weather service provider information, information collected by other centers such as the Maintenance and Construction Management Center, and data collected from environmental sensors deployed on and about the roadway. The collected environmental information is monitored and presented to the operator. This information can be used to issue general traveler advisories and support location specific warnings to drivers.
TMC Traffic Surveillance "TMC Traffic Surveillance" remotely monitors and controls traffic sensors and surveillance (e.g., CCTV) equipment, and collects, processes and stores the collected traffic data. Current traffic information and other real-time transportation information is also collected from other centers. The collected information is provided to traffic operations personnel and made available to other centers.
Traffic Management Center 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 Cooperative Cruise Control "Vehicle Cooperative Cruise Control" regulates vehicle speed using V2V communications to share speeds and coordinate maneuvers with other vehicles, maintaining vehicle speed and a safe headway. It also provides the capability for vehicles to operate in cooperative platoons with reduced headways in designated lanes. These capabilities are provided by systems on board the vehicle that coordinate with other vehicles and regulate acceleration and braking.
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 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.
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.
Employment Agreement Agreement An agreement between an individual and a corporation or government entity, whereupon the individual agrees to provide labor to the corporation/agency, which in turn compensates the employee. Stipulates level of compensation, working conditions, necessary equipment and training and expectations of employee performance.
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.
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.
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.1 Process Traffic Sensor Data Pspec - Roadway Basic Surveillance
1.1.1.3 Process Environmental Sensor Data Pspec - Roadway Environmental Monitoring
1.1.2 Process and Store Traffic Data Collection
1.1.2.2 Process Traffic Data Pspec - TMC Traffic Surveillance
1.1.2.5 Process Traffic Situation and Sensor Data Pspec - TMC Traffic Surveillance
- TMC Environmental Monitoring
1.1.2.6 Process Collected Vehicle Safety Data Pspec - RSE Environmental Monitoring
- RSE Traffic Monitoring
1.1.2.8 Process Roadway Environmental Data Pspec - TMC Traffic Surveillance
- TMC Environmental Monitoring
1.1.2.11 Control Dynamic Lanes Pspec - Roadway Basic Surveillance
1.1.4 Display and Output Traffic Data Collection
1.1.4.2 Provide Traffic Operations Personnel Traffic Data Interface Pspec - TMC Traffic Surveillance
- TMC Environmental Monitoring
1.1.6 Collect Vehicle Traffic Surveillance Data Pspec - RSE Environmental Monitoring
- RSE Traffic Monitoring
1.1.7 Collect Vehicle Environmental Data Pspec - RSE Environmental Monitoring
- RSE Traffic Monitoring
1.2 Provide Device Control Collection
1.2.8 Collect Traffic Field Equipment Fault Data Pspec - TMC Traffic Surveillance
- TMC Environmental Monitoring
1.3 Manage Incidents Collection
1.3.1 Traffic Data Analysis for Incidents Collection
1.3.1.1 Analyze Traffic Data for Incidents Pspec - TMC Traffic Surveillance
1.3.1.3 Process Traffic Images Pspec - Roadway Basic Surveillance
3.1 Monitor Vehicle Status Collection
3.1.3 Process Vehicle On-board Data Pspec - Vehicle Environmental Monitoring
- Vehicle Basic Safety
- Vehicle Cooperative Cruise Control
3.1.4 Communicate with Remote Vehicles Pspec - Vehicle Basic Safety
3.1.6 Provide Vehicle Acceleration and Deceleration Inputs Pspec - Vehicle Basic Safety
3.2 Provide Automatic Vehicle Operation Collection
3.2.1 Provide Driver Interface Pspec
3.2.2 Provide Automatic Vehicle Operations Control Pspec - Vehicle Cooperative Cruise Control
3.2.3 Provide Vehicle Control Collection
3.2.3.1 Provide Command Interface Pspec
3.2.3.2 Manage Platoon Following Pspec - Vehicle Environmental Monitoring
- Vehicle Basic Safety
- Vehicle Cooperative Cruise Control
3.2.3.3 Process Data for Vehicle Actuators Pspec - Vehicle Environmental Monitoring
- Vehicle Basic Safety
- Vehicle Cooperative Cruise Control
3.2.3.5 Process Vehicle Sensor Data Pspec - Vehicle Environmental Monitoring
- Vehicle Basic Safety
- Vehicle Cooperative Cruise Control
3.2.4 Process Sensor Data for Automatic Vehicle Operations Pspec - Vehicle Environmental Monitoring
- Vehicle Basic Safety
- Vehicle Cooperative Cruise Control
3.2.5 Check Vehicle for Automated Operations Eligibility Pspec - RSE Automated Vehicle Operations
3.2.6 Manage Check-in and Check-out Pspec - RSE Automated Vehicle Operations
3.2.7 Manage Automatic Vehicle Operations Pspec - TMC Automated Vehicle Operations
3.2.8 Provide Automated Lane Changing Pspec - RSE Automated Vehicle Operations
6.7 Provide Driver Personal Services Collection
6.7.1 Provide On-line Vehicle Guidance Collection
6.7.1.4 Update Vehicle Navigable Map Database Pspec - Vehicle Environmental Monitoring
- Vehicle Basic Safety
6.7.3 Provide Traveler Services in Vehicle Collection
6.7.3.3 Provide Driver Information Interface Pspec - Vehicle Environmental Monitoring
- Vehicle Basic Safety
9.2 Manage Roadway M&C Activities Collection
9.2.3 Determine M&C Needs Collection
9.2.3.6 Collect Field Equipment Status for Repair Pspec - Roadway Basic Surveillance
- Roadway Environmental Monitoring

Includes Data Flows:

Source Pspec Data Flow Destination Pspec
Check Vehicle for Automated Operations Eligibility avo_checking_data Manage Check-in and Check-out
Check Vehicle for Automated Operations Eligibility avo_check_response Provide Automatic Vehicle Operations Control
Collect Vehicle Environmental Data vehicle_env_sensor_status_for_traffic Collect Traffic Field Equipment Fault Data
Collect Vehicle Environmental Data vehicle_env_probe_input_data Process Collected Vehicle Safety Data
Collect Vehicle Environmental Data vehicle_env_sensor_data_for_traffic Process Roadway Environmental Data
Collect Vehicle Environmental Data vehicle_env_sensor_status_for_traffic Process Roadway Environmental Data
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_situation_data_for_traffic Process Traffic Situation and Sensor Data
Collect Vehicle Traffic Surveillance Data vehicle_situation_data_at_border Process Traffic Situation and Sensor 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 remote_vehicle_status_for_eco_drive Provide Vehicle Acceleration and Deceleration Inputs
Control Dynamic Lanes shoulder_management_equip_status_for_m_and_c Collect Field Equipment Status for Repair
Control Dynamic Lanes lane_management_equip_status_for_m_and_c Collect Field Equipment Status for Repair
Control Dynamic Lanes shoulder_management_device_status Collect Traffic Field Equipment Fault Data
Control Dynamic Lanes lane_management_device_status Collect Traffic Field Equipment Fault Data
Manage Automatic Vehicle Operations avo_control_data_changes Manage Check-in and Check-out
Manage Automatic Vehicle Operations automated_lane_changing_control_data Provide Automated Lane Changing
Manage Check-in and Check-out avo_control_information Check Vehicle for Automated Operations Eligibility
Manage Check-in and Check-out avo_equip_status_for_m_and_c Collect Field Equipment Status for Repair
Manage Check-in and Check-out avo_device_status Collect Traffic Field Equipment Fault Data
Manage Check-in and Check-out automated_lane_movement_data Control Dynamic Lanes
Manage Check-in and Check-out avo_checking_details Manage Automatic Vehicle Operations
Manage Platoon Following platooning_selected Process Data for Vehicle Actuators
Manage Platoon Following platoon_status Provide Automatic Vehicle Operations Control
Manage Platoon Following feedback_platoon_status Provide Command Interface
Process Collected Vehicle Safety Data vehicle_traffic_data_for_lanes Control Dynamic Lanes
Process Collected Vehicle Safety Data vehicle_env_sensor_data_for_roadside Process Environmental Sensor Data
Process Collected Vehicle Safety Data vehicle_env_data_for_center Process Roadway Environmental Data
Process Collected Vehicle Safety Data vehicle_traffic_data_for_center Process Traffic Situation and Sensor Data
Process Collected Vehicle Safety Data local_travel_times_data_for_traffic Process Traffic Situation and Sensor Data
Process Data for Vehicle Actuators manual_input_received Manage Platoon Following
Process Data for Vehicle Actuators feedback_actuator_status Provide Command Interface
Process Environmental Sensor Data environmental_sensor_equip_status_for_m_and_c Collect Field Equipment Status for Repair
Process Environmental Sensor Data environmental_sensor_status Collect Traffic Field Equipment Fault Data
Process Environmental Sensor Data environmental_sensor_data_for_roadside_safety Process Collected Vehicle Safety Data
Process Environmental Sensor Data environment_sensor_data Process Roadway Environmental Data
Process Environmental Sensor Data environmental_sensor_status Process Roadway Environmental Data
Process Roadway Environmental Data env_sensor_control_to_roadway Process Environmental Sensor Data
Process Roadway Environmental Data env_sensor_status_for_traffic_operator Provide Traffic Operations Personnel Traffic Data Interface
Process Sensor Data for Automatic Vehicle Operations avo_vehicle_data Provide Automatic Vehicle Operations Control
Process Traffic Data unusual_data Analyze Traffic Data for Incidents
Process Traffic Images traffic_image_data Analyze Traffic Data for Incidents
Process Traffic Images video_device_equip_status_for_m_and_c Collect Field Equipment Status for Repair
Process Traffic Images video_device_status Collect Traffic Field Equipment Fault Data
Process Traffic Sensor Data incident_analysis_data Analyze Traffic Data for Incidents
Process Traffic Sensor Data hov_sensor_equip_status_for_m_and_c Collect Field Equipment Status for Repair
Process Traffic Sensor Data multimodal_crossing_sensor_equip_status_for_m_and_c Collect Field Equipment Status for Repair
Process Traffic Sensor Data pedestrian_sensor_equip_status_for_m_and_c Collect Field Equipment Status for Repair
Process Traffic Sensor Data reversible_lane_sensor_equip_status_for_m_and_c Collect Field Equipment Status for Repair
Process Traffic Sensor Data traffic_sensor_equip_status_for_m_and_c Collect Field Equipment Status for Repair
Process Traffic Sensor Data hov_sensor_status Collect Traffic Field Equipment Fault Data
Process Traffic Sensor Data multimodal_crossing_sensor_status Collect Traffic Field Equipment Fault Data
Process Traffic Sensor Data pedestrian_sensor_status Collect Traffic Field Equipment Fault Data
Process Traffic Sensor Data reversible_lane_sensor_status Collect Traffic Field Equipment Fault Data
Process Traffic Sensor Data traffic_sensor_status Collect Traffic Field Equipment Fault Data
Process Traffic Sensor Data dynamic_lane_sensor_data_to_roadway Control Dynamic Lanes
Process Traffic Sensor Data traffic_video_image Process Traffic Data
Process Traffic Sensor Data hov_sensor_data Process Traffic Data
Process Traffic Sensor Data multimodal_crossing_sensor_data Process Traffic Data
Process Traffic Sensor Data pedestrian_sensor_data Process Traffic Data
Process Traffic Sensor Data traffic_sensor_data Process Traffic Data
Process Traffic Sensor Data vehicle_characteristics_data Process Traffic Data
Process Traffic Sensor Data traffic_sensor_data_for_automated_lane_changing Provide Automated Lane Changing
Process Traffic Sensor Data traffic_video_image_for_display Provide Traffic Operations Personnel Traffic Data Interface
Process Vehicle On-board Data vehicle_env_sensor_data Collect Vehicle Environmental 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_occupants_detected Process Traffic Sensor Data
Process Vehicle On-board Data host_vehicle_status_for_eco_drive Provide Vehicle Acceleration and Deceleration Inputs
Process Vehicle Sensor Data feedback_sensor_status Provide Command Interface
Provide Automated Lane Changing lane_change_details Provide Automatic Vehicle Operations Control
Provide Automated Lane Changing lane_change_strategy Provide Automatic Vehicle Operations Control
Provide Automatic Vehicle Operations Control avo_vehicle_condition Check Vehicle for Automated Operations Eligibility
Provide Automatic Vehicle Operations Control platoon_status_for_roadside Check Vehicle for Automated Operations Eligibility
Provide Automatic Vehicle Operations Control avo_route_data Manage Check-in and Check-out
Provide Automatic Vehicle Operations Control platoon_action Manage Platoon Following
Provide Automatic Vehicle Operations Control avo_status Provide Driver Interface
Provide Command Interface driver_selection Manage Platoon Following
Provide Command Interface driver_manual_input Process Data for Vehicle Actuators
Provide Command Interface control_status Provide Driver Interface
Provide Driver Information Interface vehicle_control_request Provide Vehicle Acceleration and Deceleration Inputs
Provide Driver Interface driver_avo_input Provide Automatic Vehicle Operations Control
Provide Driver Interface driver_input Provide Command Interface
Provide Traffic Operations Personnel Traffic Data Interface roadside_data_collection_configuration_data Collect Vehicle Traffic Surveillance Data
Provide Traffic Operations Personnel Traffic Data Interface env_sensor_control_by_traffic_operator Process Roadway Environmental Data
Provide Traffic Operations Personnel Traffic Data Interface sensor_configuration_data Process Traffic Sensor Data
Provide Traffic Operations Personnel Traffic Data Interface infrastructure_sensor_control Process Traffic Sensor Data

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.
Traffic Operations Personnel Center 'Traffic Operations Personnel' represents the people that operate a traffic management center. These personnel interact with traffic control systems, traffic surveillance systems, incident management systems, work zone management systems, and travel demand management systems. They provide operator data and command inputs to direct system operations to varying degrees depending on the type of system and the deployment scenario.
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 Basic Surveillance "Roadway Basic Surveillance" monitors traffic conditions using fixed equipment such as loop detectors and CCTV cameras. ITS Roadway Equipment
Roadway Environmental Monitoring "Roadway Environmental Monitoring" measures environmental conditions and communicates the collected information back to a center where it can be monitored and analyzed. A broad array of general weather and road surface information may be collected. Weather conditions that may be measured include temperature, wind, humidity, precipitation, and visibility. Surface and sub-surface sensors can measure road surface temperature, moisture, icing, salinity, and other measures. ITS Roadway Equipment
RSE Automated Vehicle Operations "RSE Automated Vehicle Operations" includes the field elements that monitor and control access to and egress from automated lanes. It monitors and coordinates automated vehicle operations within the lanes. These lanes support vehicles operating in platoons with short headways. Roadside Equipment
RSE Environmental Monitoring "RSE Environmental Monitoring" collects environmental situation (probe) data from passing vehicles that are equipped with short range communications capability. The collected data includes current environmental conditions as measured by on-board sensors (e.g., ambient temperature and precipitation measures), current status of vehicle systems that can be used to infer environmental conditions (e.g., status of lights, wipers, ABS, and traction control systems), and emissions measures reported by the vehicle. The application object collects the provided data, aggregates and filters the data based on provided configuration parameters, and sends the collected information back to a center for processing and distribution. This application object may also process the collected data locally and issue short-term road weather advisories for the road segment using short range communications. 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 Automated Vehicle Operations "TMC Automated Vehicle Operations" remotely monitors and controls automated lanes. It monitors system operation and provides parameters that control system operation including system parameters that govern vehicle platoon formation, speeds, and gaps or headways. Traffic Management Center
TMC Environmental Monitoring "TMC Environmental Monitoring" assimilates current and forecast road conditions and surface weather information using a combination of weather service provider information, information collected by other centers such as the Maintenance and Construction Management Center, and data collected from environmental sensors deployed on and about the roadway. The collected environmental information is monitored and presented to the operator. This information can be used to issue general traveler advisories and support location specific warnings to drivers. Traffic Management Center
TMC Traffic Surveillance "TMC Traffic Surveillance" remotely monitors and controls traffic sensors and surveillance (e.g., CCTV) equipment, and collects, processes and stores the collected traffic data. Current traffic information and other real-time transportation information is also collected from other centers. The collected information is provided to traffic operations personnel and made available to other centers. Traffic Management Center
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 Cooperative Cruise Control "Vehicle Cooperative Cruise Control" regulates vehicle speed using V2V communications to share speeds and coordinate maneuvers with other vehicles, maintaining vehicle speed and a safe headway. It also provides the capability for vehicles to operate in cooperative platoons with reduced headways in designated lanes. These capabilities are provided by systems on board the vehicle that coordinate with other vehicles and regulate acceleration and braking. Vehicle OBE
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

Includes Information Flows:

Information Flow Description
automated lane control data Control commands and operating parameters provided to RSEs that control and monitor automated vehicle operations, including platooned vehicles using cooperative adaptive cruise control. This flow includes platoon parameters including maximum platoon size, target speeds and headways, and vehicle restrictions.
automated lane status Current operational status of lanes supporting automated vehicle operations including cooperative adaptive cruise control. The flow includes the status of the RSEs, associated field equipment, and vehicles using the facility.
cooperative adaptive cruise control parameters Information, instructions, and control parameters for cooperative cruise control including current system conditions and advisories, control parameters (e.g., speed, required vehicle performance profiles, gaps or headways) and check in/checkout instructions.
cooperative adaptive cruise control status Data provided by a connected vehicle identifying it's current mode and operational status and information provided to support checkin/checkout of the lane and coordinated maneuvers while on the automated facility.
driver input Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands.
driver input information Driver input received from the driver-vehicle interface equipment via the vehicle bus. It includes configuration data, settings and preferences, interactive requests, and control commands for the connected vehicle on-board equipment.
driver update information Information provided to the driver-vehicle interface to inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment. The flow includes the information to be presented to the driver and associated metadata that supports processing, prioritization, and presentation by the DVI as visual displays, audible information and warnings, and/or haptic feedback.
driver updates Information provided to the driver including visual displays, audible information and warnings, and haptic feedback. The updates inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment.
environmental sensor data Current road conditions (e.g., surface temperature, subsurface temperature, moisture, icing, treatment status) and surface weather conditions (e.g., air temperature, wind speed, precipitation, visibility) as measured and reported by fixed and/or mobile environmental sensors. Operational status of the sensors is also included.
environmental sensors control Data used to configure and control environmental sensors.
environmental situation data Aggregated and filtered vehicle environmental data collected from vehicle safety and convenience systems including measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, anti-lock brake status, and other collected vehicle system status and sensor information. This information flow represents the aggregated and filtered environmental data sets that are provided by the RSE to the back office center. Depending on the RSE configuration and implementation, the data set may also include environmental sensor station data collected by the RSE.
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.
traffic flow Raw and/or processed traffic detector data which allows derivation of traffic flow variables (e.g., speed, volume, and density measures) and associated information (e.g., congestion, potential incidents). This flow includes the traffic data and the operational status of the traffic detectors.
traffic operator data Presentation of traffic operations data to the operator including traffic conditions, current operating status of field equipment, maintenance activity status, incident status, video images, security alerts, emergency response plan updates and other information. This data keeps the operator appraised of current road network status, provides feedback to the operator as traffic control actions are implemented, provides transportation security inputs, and supports review of historical data and preparation for future traffic operations activities.
traffic operator input User input from traffic operations personnel including requests for information, configuration changes, commands to adjust current traffic control strategies (e.g., adjust signal timing plans, change DMS messages), and other traffic operations data entry.
traffic sensor control Information used to configure and control traffic sensor systems.
traffic situation data Current, aggregate traffic data collected from connected vehicles that can be used to supplement or replace information collected by roadside traffic detectors. It includes raw and/or processed reported vehicle speeds, counts, and other derived measures. Raw and/or filtered vehicle control events may also be included to support incident detection.
vehicle control information Information provided to support computer-controlled intervention of vehicle throttle and braking to support adaptive coordinated cruise control and other applications that include automated vehicle control.
vehicle entries and exits Information exchanged between an RSE and ITS Roadway Equipment that supports detection of non-equipped vehicles in an automated lane, low emissions zone, or other facility where V2I communications is used to monitor vehicles at entry or exit points. This exchange also supports identification of non-equipped vehicles where an RSE is used for payment collection. This generic exchange can be implemented by any approach that compares vehicle detections with V2I communications by the RSE to identify vehicles that are not equipped or are otherwise unable to communicate with the RSE.
vehicle environmental data Data from vehicle safety and convenience systems that can be used to estimate environmental conditions, including measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, anti-lock brake status, and other collected vehicle system status and sensor information. The collected data is reported along with the location, heading, and time that the data was collected. Both current data and snapshots of recent events (e.g., traction control or anti-lock brake system activations) may be reported.
vehicle location and motion Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size.
vehicle 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.
vehicle platoon coordination Coordination of control commands between leader and follower vehicles allowing vehicles to join, coordinate with, and separate from platoons of cooperative vehicles. This flow shares platoon size, location, and performance parameters (e.g., platoon speed and spacing) between platooned vehicles. It also coordinates maneuvers between platooned vehicles, including maneuvers as vehicles join and leave the platoon.
vehicle profile Information about a vehicle such as vehicle make and model, fuel type, engine type, average emissions, average fuel consumption, passenger occupancy, or other data that can be used to classify vehicle eligibility for access to specific lanes, road segments, or regions.

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 Traffic Management Center environmental sensor data
ITS Roadway Equipment Traffic Management Center traffic flow
ITS Roadway Equipment Roadside Equipment vehicle entries and exits
Remote Vehicle OBEs Vehicle OBE vehicle location and motion
Remote Vehicle OBEs Vehicle OBE vehicle platoon coordination
Roadside Equipment Traffic Management Center automated lane status
Roadside Equipment Vehicle OBE cooperative adaptive cruise control parameters
Roadside Equipment Traffic Management Center environmental situation data
Roadside Equipment ITS Roadway Equipment environmental situation data
Roadside Equipment ITS Roadway Equipment traffic situation data
Roadside Equipment Traffic Management Center traffic situation data
Roadside Equipment ITS Roadway Equipment vehicle entries and exits
Traffic Management Center Roadside Equipment automated lane control data
Traffic Management Center ITS Roadway Equipment environmental sensors control
None: Human interface Traffic Management Center Traffic Operations Personnel traffic operator data
Traffic Management Center ITS Roadway Equipment traffic sensor control
None: Human interface Traffic Operations Personnel Traffic Management Center traffic operator input
Vehicle Databus Vehicle OBE driver input information
Vehicle Databus Vehicle OBE host vehicle status
Vehicle OBE Roadside Equipment cooperative adaptive cruise control status
Vehicle OBE Vehicle Databus driver update information
None: Human interface Vehicle OBE Driver driver updates
Vehicle OBE Vehicle Databus vehicle control information
Vehicle OBE Roadside Equipment vehicle environmental data
Vehicle OBE Remote Vehicle OBEs vehicle location and motion
Vehicle OBE Roadside Equipment vehicle location and motion for surveillance
Vehicle OBE Remote Vehicle OBEs vehicle platoon coordination
Vehicle OBE Roadside Equipment vehicle platoon coordination
Vehicle OBE Roadside Equipment vehicle profile

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.098 Eco-Cooperative Adaptive Cruise Control (ECACC) needs to accept vehicles into a platoon and inform drivers of how, when, and where to safely join a ECACC platoon 1.203 Eco-Cooperative Adaptive Cruise Control (ECACC) shall determine recommended platoon entry location and timing for vehicle entering a platoon.
N1.099 When a driver decides to leave the platoon ECACC needs to be able to allow her to regain manual throttle control and change lanes safely. 1.204 ECACC shall allow the vehicle to leave the platoon when driver decides.
N1.100 ECACC needs to provide an interface for the driver to accept a recommended speed and gap policy for his connected vehicle to implement. 1.207 ECACC shall have a speed and gap strategy generation capability.
1.208 ECACC shall provide a speed and gap strategy to the vehicle driver for acceptance by the driver
N1.101 ECACC needs to receive vehicle operational information from other vehicles or systems. 1.206 ECACC shall collect location and movement data from other connected vehicles.
N1.102 ECACC needs to automatically engage vehicle throttle to enact cruise control strategies. 1.209 ECACC shall automatically engage vehicle throttle to enact cruise control strategies.
N1.103 ECACC needs to needs to receive and process data from multiple sources in order to make the recommendations for eco-driving strategies. 1.205 ECACC shall incorporate infrastructure information, such as road grade, roadway geometry, and road weather information, to determine the most environmentally efficient trajectory for the following vehicle.

Related Sources

  • AERIS Transformative Concepts and Applications Descriptions, Final, 8/1/2012

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.