Type: Mobility

Groups:
  • Traffic Signals
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.

Intelligent Traffic Signal System

The Intelligent Traffic Signal System (ISIG) application uses both vehicle location and movement information from connected vehicles as well as infrastructure measurement of non-equipped vehicles to improve the operations of traffic signal control systems. The application utilizes the vehicle information to adjust signal timing for an intersection or group of intersections in order to improve traffic flow, including allowing platoon flow through the intersection. The application serves as an over-arching system optimization application, accommodating other mobility applications such as Transit Signal Priority, Freight Signal Priority, Emergency Vehicle Preemption, and Pedestrian Mobility to maximize overall arterial network performance. In addition, the application may consider additional inputs such as environmental situation information or the interface (i.e., traffic flow) between arterial signals and ramp meters.

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:

Intelligent Traffic Signal System Operations Stage
Vehicle OwnerDriverVehicle OBE OwnerRoadway OwnerRSE OwnerRSE OperatorITS Roadway Equipment OwnerITS Roadway OperatorTraffic ManagerTraffic Operations PersonnelPedestriansVehicle Basic Safety ProviderVehicle Intersection Warning ProviderRSE Environmental Monitoring ProviderVehicle Environmental Monitoring ProviderOther Traffic ManagerRSE Intersection Management ProviderOther ITS Roadway Equipment OwnerRSE Situation Monitoring ProviderRSE Traffic Monitoring Provider
Vehicle OwnerVehicle Usage AgreementVehicle OBE Usage AgreementApplication Usage AgreementApplication Usage AgreementApplication Usage Agreement
DriverVehicle Usage AgreementExpectation of Information ProvisionExpectation of Information Provision
Vehicle OBE OwnerVehicle OBE Usage AgreementExpectation of Information ProvisionExpectation of Data Provision
Roadway OwnerService Delivery Agreement
RSE OwnerExpectation of Data ProvisionService Delivery AgreementOperations AgreementInformation Exchange and Action AgreementInformation Exchange AgreementApplication Usage AgreementApplication Usage AgreementApplication Usage AgreementApplication Usage Agreement
RSE OperatorOperations Agreement
ITS Roadway Equipment OwnerInformation Exchange and Action AgreementOperations AgreementInformation Exchange and Action AgreementInformation Exchange and Action Agreement
ITS Roadway OperatorExpectation of Information ProvisionOperations AgreementExpectation of Safety Provision
Traffic ManagerInformation Exchange AgreementInformation Exchange and Action AgreementEmployment AgreementInformation Exchange Agreement
Traffic Operations PersonnelEmployment Agreement
PedestriansExpectation of Safety Provision
Vehicle Basic Safety ProviderApplication Usage Agreement
Vehicle Intersection Warning ProviderApplication Usage Agreement
RSE Environmental Monitoring ProviderApplication Usage Agreement
Vehicle Environmental Monitoring ProviderApplication Usage Agreement
Other Traffic ManagerInformation Exchange Agreement
RSE Intersection Management ProviderApplication Usage Agreement
Other ITS Roadway Equipment OwnerInformation Exchange and Action Agreement
RSE Situation Monitoring ProviderApplication Usage Agreement
RSE Traffic Monitoring 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.
Other ITS Roadway Equipment Owner Representing another ITS Roadway Equipment Owner, "Other ITS Roadway Equipment Owner" provides the source and destination for agreements and expectations between ITS Roadway Equipment Owners, enabling field ITS device management activities to be coordinated across jurisdictional boundaries.
Other Traffic Manager Representing another Traffic Manager, "Other Traffic Manager" provides the source and destination for agreements and expectations between Traffic Managers, enabling traffic management activities to be coordinated across jurisdictional boundaries.
Pedestrians 'Pedestrians' participate in connected vehicle applications that support safe, shared use of the transportation network by motorized and non-motorized transportation modes. Representing those using non-motorized travel modes, pedestrians provide input (e.g. a call signal requesting right of way at an intersection) and may be detected by connected vehicle applications to improve safety. Note that pedestrians represent all non-motorized users, including bicyclists.
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.
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 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 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 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 Situation 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 Situation 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 Situation 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 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 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 Regional Traffic 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.
TMC Regional Traffic 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.
TMC Regional Traffic 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.
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.
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 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 Intersection Warning Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Vehicle Intersection Warning Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Vehicle Intersection Warning Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Vehicle Manufacturer The entity that builds, assembles, verifies and validates the Vehicle in which the Vehicle OBE will eventually operate.
Vehicle OBE Manufacturer The entity that builds, assembles, verifies and validates the Vehicle OBE. This can be an OEM-equipped OBE, retrofit or aftermarket equipment.
Vehicle OBE Owner The entity, individual, group or corporation that owns the Vehicle On-Board equipment. This could be the same as the Vehicle Owner, but it could be a third part that licenses the use of the OBE to the Owner.
Vehicle Owner The individual, group of individuals or corporate entity that is identified as the registered owner of the Vehicle under state law.
Vehicle Roadside Information Reception 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 Situation Data 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 Situation Data 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 Situation Data 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 Speed Management 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.

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.
Other ITS Roadway Equipment Representing another set of ITS Roadway Equipment, 'Other ITS Roadway Equipment' supports 'field device' to 'field device' communication and coordination, and provides a source and destination for information that may be exchanged between ITS Roadway Equipment. The interface enables direct coordination between field equipment. Examples include the direct interface between sensors and other roadway devices (e.g., Dynamic Message Signs) and the direct interface between roadway devices (e.g., between a Signal System Master and Signal System Local equipment) or a connection between an arterial signal system master and a ramp meter controller.
Other Traffic Management Centers Representing another Traffic Management Center, 'Other Traffic Management Centers' is intended to provide a source and destination for information exchange between peer (e.g. inter-regional) traffic management functions. It enables traffic management activities to be coordinated across different jurisdictional areas.
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.
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 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 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 Situation Monitoring "RSE Situation Monitoring" is a general application object that supports collection of traffic, environmental, and emissions data from passing vehicles. The data is collected, filtered, and forwarded based on parameters provided by the back office. Parameters are provided to passing vehicles that are equipped to collect and send situation data to the infrastructure in snapshots. In addition, this object collects current status information from local field devices including intersection status, sensor data, and signage data, providing complete, configurable monitoring of the situation for the local transportation system in the vicinity of the RSE.
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 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 Regional Traffic Management "TMC Regional Traffic Management" supports coordination between traffic management centers in order to share traffic information between centers as well as control of traffic management field equipment. This coordination supports wide area optimization and regional coordination that spans jurisdictional boundaries; for example, coordinated signal control in a metropolitan area or coordination between freeway operations and arterial signal control within a corridor.
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.
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 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 Intersection Warning "Vehicle Intersection Warning" uses V2V and V2I communications to monitor other connected vehicles at intersections and support the safe movement of the vehicle through the intersection. Driver warnings are provided and the application may also optionally take control of the vehicle to avoid collisions. The application will also notify the infrastructure and other vehicles if it detects an unsafe infringement on the intersection.
Vehicle OBE The Vehicle On-Board Equipment (OBE) provides the vehicle-based processing, storage, and communications functions necessary to support connected vehicle operations. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle OBE. This communication platform is augmented with processing and data storage capability that supports the connected vehicle applications.

In CVRIA, the Vehicle OBE includes the functions and interfaces that support connected vehicle applications for passenger cars, trucks, and motorcycles. Many of these applications (e.g., V2V Safety applications) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle OBE includes the common interfaces and functions that apply to all motorized vehicles.
Vehicle Situation Data Monitoring "Vehicle Situation Data Monitoring" is the highest-level representation of the functionality required to collect traffic and environmental situation data by monitoring and storing the experience of the vehicle as it travels through the road network. Collected data is aggregated into snapshots that are reported when communications is available and with flow control based on parameters provided by the infrastructure. Note that this application object supports collection of data for areas remote from RSEs or other communications infrastructure.

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.
Expectation of Safety Provision Expectation Users of the transportation environment expect that the entities that operate the environment do so in such a way as to preserve and enhance users' safety. This is inherent to current operations, and is an underlying assumption of drivers and pedestrians when accepting information from ITS. This expectation is explicitly noted for connected vehicle applications where this is a new relationship, whereupon the transportation system user expects a transportation service provider to do something (i.e., actuate a system or deliver information) that will protect and/or enhance the user's safety.
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.
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 Specification Agreement The definition of interface between two hardware components that must share data.
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.
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
- Roadway Signal Control
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
- TMC Signal Control
1.1.2.5 Process Traffic Situation and Sensor Data Pspec - TMC Traffic Surveillance
- TMC Environmental Monitoring
- TMC Signal Control
1.1.2.6 Process Collected Vehicle Safety Data Pspec - RSE Environmental Monitoring
- RSE Intersection Management
- RSE Traffic Monitoring
1.1.2.8 Process Roadway Environmental Data Pspec - TMC Traffic Surveillance
- TMC Environmental Monitoring
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.5 Exchange Data with Other Traffic Centers Pspec - TMC Traffic Surveillance
- TMC Environmental Monitoring
- TMC Signal Control
- TMC Regional Traffic Management
1.1.6 Collect Vehicle Traffic Surveillance Data Pspec - RSE Environmental Monitoring
- RSE Intersection Management
- RSE Traffic Monitoring
- RSE Situation Monitoring
1.1.7 Collect Vehicle Environmental Data Pspec - RSE Environmental Monitoring
- RSE Traffic Monitoring
- RSE Situation Monitoring
1.2 Provide Device Control Collection
1.2.1 Select Strategy Pspec - TMC Traffic Surveillance
- TMC Environmental Monitoring
- 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 Traffic Surveillance
- TMC Environmental Monitoring
- TMC Signal Control
1.2.4.7 Manage Roadway Warning System Pspec - TMC Traffic Surveillance
- TMC Environmental Monitoring
- TMC Signal Control
1.2.7 Provide Roadside Control Facilities Collection
1.2.7.1 Process Indicator Output Data for Roads Pspec - Roadway Environmental Monitoring
- Roadway Signal Control
1.2.7.2 Monitor Roadside Equipment Operation Pspec - Roadway Basic Surveillance
- Roadway Environmental Monitoring
- Roadway Signal Control
1.2.7.4 Process In-vehicle Signage Data Pspec - RSE Environmental Monitoring
- RSE Intersection Management
- RSE Traffic Monitoring
1.2.7.7 Process Vehicle Safety and Environmental Data for Output Pspec - RSE Environmental Monitoring
- RSE Intersection Management
1.2.7.13 Provide Device Interface for Field Management Stations Pspec - Roadway Signal Control
1.2.7.15 Process Intersection Safety Data Pspec - RSE Environmental Monitoring
- RSE Intersection Management
- RSE Traffic Monitoring
1.2.7.16 Process Signal Control Conflict Monitoring Pspec - Roadway Basic Surveillance
- Roadway Environmental Monitoring
- Roadway Signal Control
1.2.8 Collect Traffic Field Equipment Fault Data Pspec - TMC Traffic Surveillance
- TMC Environmental Monitoring
- TMC Signal Control
3.1 Monitor Vehicle Status Collection
3.1.1 Produce Collision and Crash Avoidance Data Pspec - Vehicle Intersection Warning
- Vehicle Basic Safety
3.1.3 Process Vehicle On-board Data Pspec - Vehicle Intersection Warning
- Vehicle Environmental Monitoring
- Vehicle Basic Safety
- Vehicle Situation Data Monitoring
6.7 Provide Driver Personal Services Collection
6.7.1 Provide On-line Vehicle Guidance Collection
6.7.1.3 Process Vehicle Location Data Pspec - Vehicle Intersection Warning
- Vehicle Environmental Monitoring
- Vehicle Basic Safety
6.7.1.4 Update Vehicle Navigable Map Database Pspec - Vehicle Intersection Warning
- Vehicle Environmental Monitoring
- Vehicle Basic Safety
6.7.3 Provide Traveler Services in Vehicle Collection
6.7.3.2 Provide Driver with Personal Travel Information Pspec - Vehicle Intersection Warning
- Vehicle Environmental Monitoring
6.7.3.3 Provide Driver Information Interface Pspec - Vehicle Intersection Warning
- Vehicle Environmental Monitoring
- Vehicle Basic Safety

Includes Data Flows:

Source Pspec Data Flow Destination Pspec
Collect Traffic Field Equipment Fault Data indicator_fault_state Select Strategy
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
Exchange Data with Other Traffic Centers other_control_data_for_roads Output Control Data for Roads
Exchange Data with Other Traffic Centers status_data_for_roads Output Control Data for Roads
Exchange Data with Other Traffic Centers env_sensor_control_from_other_center Process Roadway Environmental Data
Exchange Data with Other Traffic Centers env_sensor_status_from_other_center Process Roadway Environmental Data
Exchange Data with Other Traffic Centers device_control_request_from_other_center Provide Traffic Operations Personnel Traffic Data Interface
Exchange Data with Other Traffic Centers other_TMC_cv_incidents Select Strategy
Exchange Data with Other Traffic Centers other_TMC_emergency_data Select Strategy
Exchange Data with Other Traffic Centers other_TMC_strategy_data Select Strategy
Manage Roadway Warning System vehicle_sign_data_for_warning Output In-vehicle Signage Data
Manage Roadway Warning System pedestrian_roadside_warning_system_control Process Intersection Safety Data
Manage Roadway Warning System intersection_safety_system_controls Process Intersection Safety Data
Manage Roadway Warning System stop_sign_gap_roadside_control Process Intersection Safety Data
Manage Roadway Warning System queue_warning_roadside_configuration Process Vehicle Safety and Environmental Data for Output
Manage Roadway Warning System roadway_warning_system_status_to_operator Provide Traffic Operations Personnel Traffic Data Interface
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 control_data_for_roads Exchange Data with Other Traffic Centers
Output Control Data for Roads other_status_for_roads Exchange Data with Other Traffic Centers
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
Output In-vehicle Signage Data vehicle_signage_operator_status Provide Traffic Operations Personnel Traffic Data Interface
Process Collected Vehicle Safety Data vehicle_env_sensor_data_for_roadside Process Environmental Sensor Data
Process Collected Vehicle Safety Data vehicle_traffic_data_for_roads Process Indicator Output Data for Roads
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 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 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 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 t_other_rw_ic_to_ic Provide Device Interface for Field Management Stations
Process Indicator Output Data for Roads signal_preemption_override Select Strategy
Process Indicator Output Data for Roads signal_priority_override Select Strategy
Process Intersection Safety Data roadside_intersection_safety_status Collect Traffic Field Equipment Fault Data
Process Intersection Safety Data roadside_pedestrian_safety_status Manage Roadway Warning System
Process Intersection Safety Data roadside_intersection_safety_status Manage Roadway Warning System
Process Intersection Safety Data intersection_infringement_for_indicators Process Indicator Output Data for Roads
Process Intersection Safety Data local_traffic_signal_service_request Process Indicator Output Data for Roads
Process Intersection Safety Data intersection_warning_for_signage Process In-vehicle Signage Data
Process Intersection Safety Data intersection_data_for_signage Process In-vehicle Signage Data
Process Intersection Safety Data intersection_status_data_for_vehicle Process Vehicle On-board Data
Process Intersection Safety Data intersection_collision_avoidance_data Produce Collision and Crash Avoidance Data
Process Intersection Safety Data stop_sign_gap_data_to_vehicle Produce Collision and Crash Avoidance Data
Process In-vehicle Signage Data vehicle_sign_status Collect Traffic Field Equipment Fault Data
Process In-vehicle Signage Data speed_vehicle_sign_status Collect Traffic Field Equipment Fault Data
Process In-vehicle Signage Data infrastructure_vehicle_sign_status Collect Traffic Field Equipment Fault Data
Process In-vehicle Signage Data stop_sign_gap_sign_status Collect Traffic Field Equipment Fault Data
Process In-vehicle Signage Data 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 Roadway Environmental Data env_sensor_control_to_other_center Exchange Data with Other Traffic Centers
Process Roadway Environmental Data env_sensor_status_to_other_center Exchange Data with Other Traffic Centers
Process Roadway Environmental Data environmental_data_for_signage Output In-vehicle Signage 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 Signal Control Conflict Monitoring conflict_monitor_detection Process Indicator Output Data for Roads
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 local_sensor_data_for_roads Process Indicator Output Data for Roads
Process Traffic Sensor Data pedestrian_demand_for_roadside Process Intersection Safety Data
Process Traffic Sensor Data pedestrian_sensor_status_for_roadside Process Intersection Safety Data
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_video_image_for_display Provide Traffic Operations Personnel Traffic Data Interface
Process Traffic Situation and Sensor Data probe_data_for_strategy Select Strategy
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_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 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 vehicle_occupants_detected Process Traffic Sensor Data
Process Vehicle On-board Data collision_data Produce Collision and Crash Avoidance Data
Process Vehicle On-board Data vehicle_status_details_for_broadcast Provide Driver with Personal Travel Information
Process Vehicle Safety and Environmental Data for Output queue_warning_system_status Collect Traffic Field Equipment Fault Data
Process Vehicle Safety and Environmental Data for Output queue_warning_system_status Manage Roadway Warning System
Process Vehicle Safety and Environmental Data for Output env_sensor_data_for_advisory_message Process In-vehicle Signage Data
Process Vehicle Safety and Environmental Data for Output vehicle_safety_and_roadway_data Process In-vehicle Signage Data
Process Vehicle Safety and Environmental Data for Output roadside_signal_monitoring Process Signal Control Conflict Monitoring
Process Vehicle Safety and Environmental Data for Output position_correction_to_vehicle Process Vehicle Location Data
Process Vehicle Safety and Environmental Data for Output roadside_safety_data_to_vehicle Process Vehicle On-board Data
Process Vehicle Safety and Environmental Data for Output signal_phase_indication_to_vehicle Produce Collision and Crash Avoidance Data
Process Vehicle Safety and Environmental Data for Output signal_phase_timing_to_vehicle Produce Collision and Crash Avoidance Data
Process Vehicle Safety and Environmental Data for Output signal_phase_response_state_to_vehicle Produce Collision and Crash Avoidance Data
Process Vehicle Safety and Environmental Data for Output queue_warning_from_roadside Produce Collision and Crash Avoidance Data
Process Vehicle Safety and Environmental Data for Output vehicle_env_sensor_data_output Provide Driver with Personal Travel Information
Process Vehicle Safety and Environmental Data for Output roadway_geometry_to_vehicle Update Vehicle Navigable Map Database
Process Vehicle Safety and Environmental Data for Output roadside_intersection_details_to_vehicle Update Vehicle Navigable Map Database
Process Vehicle Safety and Environmental Data for Output roadside_intersection_lanes_to_vehicle Update Vehicle Navigable Map Database
Process Vehicle Safety and Environmental Data for Output roadside_map_update_to_vehicle Update Vehicle Navigable Map Database
Produce Collision and Crash Avoidance Data vehicle_intersection_infringement Process Intersection Safety Data
Produce Collision and Crash Avoidance Data position_warnings Provide Driver with Personal Travel Information
Provide Device Interface for Field Management Stations field_management_station_fault_indication Collect Traffic Field Equipment Fault Data
Provide Device Interface for Field Management Stations field_management_station_status Monitor Roadside Equipment Operation
Provide Device Interface for Field Management Stations f_other_rw_ic_to_ic Process Indicator Output Data for Roads
Provide Driver Information Interface vehicle_display_type Provide Driver with Personal Travel Information
Provide Driver with Personal Travel Information vehicle_advisory_information Provide Driver Information Interface
Provide Driver with Personal Travel Information vehicle_traveler_information Provide Driver Information Interface
Provide Driver with Personal Travel Information vehicle_trip_planning_responses Provide Driver Information Interface
Provide Traffic Operations Personnel Traffic Data Interface roadside_data_collection_configuration_data Collect Vehicle Traffic Surveillance Data
Provide Traffic Operations Personnel Traffic Data Interface device_control_request_to_other_center Exchange Data with Other Traffic Centers
Provide Traffic Operations Personnel Traffic Data Interface roadway_warning_system_control_from_operator Manage Roadway Warning System
Provide Traffic Operations Personnel Traffic Data Interface vehicle_signage_operator_input Output In-vehicle Signage 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
Select Strategy request_other_TMC_data Exchange Data with Other Traffic Centers
Select Strategy cv_incidents_for_other_TMC Exchange Data with Other Traffic Centers
Select Strategy emergency_data_for_other_TMC Exchange Data with Other Traffic Centers
Select Strategy signal_override_status Exchange Data with Other Traffic Centers
Select Strategy signal_system_timing_plan Process Indicator Output Data for Roads
Select Strategy signal_system_configuration Process Indicator Output Data for Roads
Select Strategy intersection_roadside_configuration Process Intersection Safety Data
Select Strategy intersection_roadside_sensor_configuration Process Vehicle Safety and Environmental Data for Output

Physical

This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.
The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
Driver Vehicle The 'Driver' represents the person that operates a vehicle on the roadway. Included are operators of private, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The Driver originates driver requests and receives driver information that reflects the interactions which might be useful to all drivers, regardless of vehicle classification. Information and interactions which are unique to drivers of a specific vehicle type (e.g., fleet interactions with transit, commercial, or emergency vehicle drivers) are covered by separate objects.
ITS Roadway Equipment Field 'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway itself. In CVRIA, this physical object represents all of the other ITS field equipment that interfaces with and supports the Connected Vehicle Roadside Equipment (RSE). This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.
Other ITS Roadway Equipment Field Representing another set of ITS Roadway Equipment, 'Other ITS Roadway Equipment' supports 'field device' to 'field device' communication and coordination, and provides a source and destination for information that may be exchanged between ITS Roadway Equipment. The interface enables direct coordination between field equipment. Examples include the direct interface between sensors and other roadway devices (e.g., Dynamic Message Signs) and the direct interface between roadway devices (e.g., between a Signal System Master and Signal System Local equipment) or a connection between an arterial signal system master and a ramp meter controller.
Other Traffic Management Centers Center Representing another Traffic Management Center, 'Other Traffic Management Centers' is intended to provide a source and destination for information exchange between peer (e.g. inter-regional) traffic management functions. It enables traffic management activities to be coordinated across different jurisdictional areas.
Pedestrians Traveler 'Pedestrians' participate in connected vehicle applications that support safe, shared use of the transportation network by motorized and non-motorized transportation modes. Representing those using non-motorized travel modes, pedestrians provide input (e.g. a call signal requesting right of way at an intersection) and may be detected by connected vehicle applications to improve safety. Note that pedestrians represent all non-motorized users, including bicyclists.
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
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 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 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 Situation Monitoring "RSE Situation Monitoring" is a general application object that supports collection of traffic, environmental, and emissions data from passing vehicles. The data is collected, filtered, and forwarded based on parameters provided by the back office. Parameters are provided to passing vehicles that are equipped to collect and send situation data to the infrastructure in snapshots. In addition, this object collects current status information from local field devices including intersection status, sensor data, and signage data, providing complete, configurable monitoring of the situation for the local transportation system in the vicinity of the RSE. 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 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 Regional Traffic Management "TMC Regional Traffic Management" supports coordination between traffic management centers in order to share traffic information between centers as well as control of traffic management field equipment. This coordination supports wide area optimization and regional coordination that spans jurisdictional boundaries; for example, coordinated signal control in a metropolitan area or coordination between freeway operations and arterial signal control within a corridor. Traffic Management Center
TMC Signal Control "TMC Signal Control" provides the capability for traffic managers to monitor and manage the traffic flow at signalized intersections. This capability includes analyzing and reducing the collected data from traffic surveillance equipment and developing and implementing control plans for signalized intersections. Control plans may be developed and implemented that coordinate signals at many intersections under the domain of a single traffic management center and are responsive to traffic conditions and adapt to support incidents, preemption and priority requests, pedestrian crossing calls, etc. Traffic Management Center
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 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
Vehicle Intersection Warning "Vehicle Intersection Warning" uses V2V and V2I communications to monitor other connected vehicles at intersections and support the safe movement of the vehicle through the intersection. Driver warnings are provided and the application may also optionally take control of the vehicle to avoid collisions. The application will also notify the infrastructure and other vehicles if it detects an unsafe infringement on the intersection. Vehicle OBE
Vehicle Situation Data Monitoring "Vehicle Situation Data Monitoring" is the highest-level representation of the functionality required to collect traffic and environmental situation data by monitoring and storing the experience of the vehicle as it travels through the road network. Collected data is aggregated into snapshots that are reported when communications is available and with flow control based on parameters provided by the infrastructure. Note that this application object supports collection of data for areas remote from RSEs or other communications infrastructure. 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.
crossing permission Information provided to guide and warn pedestrians at crossings including crossing permission, crossing time remaining, and real-time warnings of safety threats.
device data Data from detectors, environmental sensor stations, and traffic control devices including device inventory information.
device status Status information from devices
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.
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.
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.
pedestrian detection Pedestrian request to cross the roadway. This may be an overt (e.g., push button) request from a pedestrian or the physical presence of a pedestrian that can be detected by sensors or surveillance systems.
road network conditions Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included.
signal control commands Control of traffic signal controllers or field masters including clock synchronization.
signal control data Information used to configure local traffic signal controllers.
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 service request A call for service or extension for a signal control phase that is issued by the RSE for connected vehicles approaching an intersection and/or pedestrians at a crosswalk. This flow identifies the desired phase and service time.
signal system configuration Data used to configure traffic signal systems including configuring control sections and mode of operation (time based or traffic responsive).
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 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 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 situation data This flow represents vehicle snapshots that may be provided by the vehicle to support traffic and environmental conditions monitoring. Snapshots are collected by the vehicle for specific events (e.g., when a sensor exceeds a threshold) or periodically and reported based on control parameters when communications is available. Traffic-related data includes snapshots of measured speed and heading and events including starts and stops, speed changes, and other vehicle control events. Environmental data may include 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.
vehicle situation data parameters A request for vehicle situation data that includes parameters used to control the data that is reported and the flow of data reported by the vehicle. This flow identifies the type of data/snapshots that are requested and reporting parameters such as snapshot frequency, filtering criteria (data thresholds for reporting), and reporting interval.

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 Pedestrians crossing permission
None: Human interface ITS Roadway Equipment Driver driver information
ITS Roadway Equipment Traffic Management Center environmental sensor data
ITS Roadway Equipment Roadside Equipment intersection control status
ITS Roadway Equipment Other ITS Roadway Equipment signal control data
ITS Roadway Equipment Traffic Management Center signal control status
ITS Roadway Equipment Traffic Management Center traffic flow
Other ITS Roadway Equipment ITS Roadway Equipment signal control data
Other Traffic Management Centers Traffic Management Center device data
Other Traffic Management Centers Traffic Management Center device status
Other Traffic Management Centers Traffic Management Center road network conditions
None: Human interface Pedestrians ITS Roadway Equipment pedestrian detection
Roadside Equipment ITS Roadway Equipment environmental situation data
Roadside Equipment Traffic Management Center environmental situation data
Roadside Equipment Traffic Management Center intersection management application status
Roadside Equipment Vehicle OBE intersection status
Roadside Equipment ITS Roadway Equipment intersection status monitoring
Roadside Equipment ITS Roadway Equipment signal service request
Roadside Equipment Traffic Management Center traffic situation data
Roadside Equipment ITS Roadway Equipment traffic situation data
Roadside Equipment Vehicle OBE vehicle situation data parameters
Traffic Management Center Other Traffic Management Centers device data
Traffic Management Center Other Traffic Management Centers device status
Traffic Management Center ITS Roadway Equipment environmental sensors control
Traffic Management Center Roadside Equipment intersection management application info
Traffic Management Center Other Traffic Management Centers road network conditions
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
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 Vehicle Databus driver update information
None: Human interface Vehicle OBE Driver driver updates
Vehicle OBE Roadside Equipment vehicle environmental data
Vehicle OBE Roadside Equipment vehicle location and motion for surveillance
Vehicle OBE Roadside Equipment vehicle situation data

Requirements

Need Requirement
N2.096 The Intelligent Traffic Signal System (ISIG) needs to collect data for traffic signal system optimization accommodating transit or freight signal priority, emergency signal preemption and pedestrian movements. 2.209 The Intelligent Traffic Signal System (ISIG) shall collect traffic data (e.g., volume, speed, occupancy, vehicle classification, incidents) for signalized intersections.
2.210 The Intelligent Traffic Signal System (ISIG) shall collect traffic data (e.g., volume, speed, occupancy, vehicle classification, incidents) for freeway on-ramps.
2.210a ISIG shall collect intersection performance data (e.g., intersection delay, intersection delay variability, intersection travel time, intersection travel time variability, queue length, queue length variability)
N2.097 The Intelligent Traffic Signal System (ISIG) needs to process current and historical data from multiple sources in order to provide over-arching signal system optimization. 2.211 The Intelligent Traffic Signal System (ISIG) shall use historical and processed traffic data to predict traffic conditions for arterial signal optimization.
2.212 ISIG shall evaluate alternative signal control strategies including strategies for phase failure management
2.212a ISIG shall implement a selected signal control strategy, including actuation of traffic signal infrastructure and ancillary devices such as advance warning flashers.
2.212b ISIG shall monitor priority requests and determine signal timing parameters across a collection of intersections to accommodate priority, coordination, and congestion control.
N2.098 The Intelligent Traffic Signal System (ISIG) needs to disseminate data that improves the traffic signal system to end users. 2.213 The Intelligent Traffic Signal System (ISIG) shall disseminate traffic data and arterial traffic signal timing plans to other jurisdictions to enable coordination of timing plans and other operational strategies for a corridor or a region.
2.214 ISIG shall provide signal status information to equipped vehicles and mobile devices in the vicinity of the intersection

Related Sources

  • Multi-Modal Intelligent Traffic Signal System (MMITSS) ConOps, Draft v2.0, 9/14/2012
  • Multi-Modal Intelligent Traffic Signal System Final System Requirements Document, Final, 3/7/2013
  • Multi-Modal Intelligent Traffic Signal System- System Design, Fi nal, 6/26/2013

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.