Type: Mobility
Groups:- Traffic Network
Queue Warning
The Queue Warning (Q-WARN) application utilizes connected vehicle technologies, including vehicle-to-infrastructure (V2I) and vehicle-to-vehicle (V2V) communications, to enable vehicles within the queue event to automatically broadcast their queued status information (e.g., rapid deceleration, disabled status, lane location) to nearby upstream vehicles and to infrastructure-based central entities (such as the TMC). The infrastructure will broadcast queue warnings to vehicles in order to minimize or prevent rear-end or other secondary collisions. The Q-WARN application is not intended to operate as a crash avoidance system (e.g., like the forward collision warning [FCW] safety application). In contrast to such systems, Q-WARN will engage well in advance of any potential crash situation, providing messages and information to the driver in order to minimize the likelihood of his needing to take crash avoidance or mitigation actions later. The Q-WARN application performs two essential tasks: queue determination (detection and/or prediction) and queue information dissemination. In order to perform these tasks, Q-WARN solutions can be vehicle-based or infrastructure-based or utilize a combination of each.
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
Business Interaction Matrix:
| Queue Warning Operations Stage | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Vehicle Owner | Driver | Vehicle OBE Owner | Roadway Owner | RSE Owner | RSE Operator | ITS Roadway Equipment Owner | ITS Roadway Operator | Traffic Manager | Information Service Provider | Traffic Operations Personnel | Vehicle Basic Safety Provider | RSE Environmental Monitoring Provider | Vehicle Environmental Monitoring Provider | Remote Vehicle OBE Owner | Other Traffic Manager | RSE Traffic Monitoring Provider | RSE Queue Warning Provider | Vehicle Queue Warning Provider | Vehicle Roadside Information Reception Provider | |
| Vehicle Owner | Vehicle Usage Agreement | Vehicle OBE Usage Agreement | Application Usage Agreement | Application Usage Agreement | Application Usage Agreement | Application Usage Agreement | ||||||||||||||
| Driver | Vehicle Usage Agreement | Expectation of Information Provision | Expectation of Information Provision | Presumption of Correct Operation | ||||||||||||||||
| Vehicle OBE Owner | Vehicle OBE Usage Agreement | Expectation of Information Provision | Expectation of Information Provision | Expectation of Data Provision | ||||||||||||||||
| Roadway Owner | Service Delivery Agreement | |||||||||||||||||||
| RSE Owner | Expectation of Information Provision | Service Delivery Agreement | Operations Agreement | Information Exchange and Action Agreement | Information Exchange Agreement | Application Usage Agreement | Application Usage Agreement | Application Usage Agreement | ||||||||||||
| RSE Operator | Operations Agreement | |||||||||||||||||||
| ITS Roadway Equipment Owner | Information Exchange and Action Agreement | Operations Agreement | Information Exchange and Action Agreement | |||||||||||||||||
| ITS Roadway Operator | Expectation of Information Provision | Operations Agreement | ||||||||||||||||||
| Traffic Manager | Information Exchange Agreement | Information Exchange and Action Agreement | Information Provision Agreement | Employment Agreement | Information Exchange Agreement | |||||||||||||||
| Information Service Provider | Information Provision Agreement | |||||||||||||||||||
| Traffic Operations Personnel | Employment Agreement | |||||||||||||||||||
| Vehicle Basic Safety Provider | Application Usage Agreement | |||||||||||||||||||
| RSE Environmental Monitoring Provider | Application Usage Agreement | |||||||||||||||||||
| Vehicle Environmental Monitoring Provider | Application Usage Agreement | |||||||||||||||||||
| Remote Vehicle OBE Owner | Presumption of Correct Operation | Expectation of Data Provision | ||||||||||||||||||
| Other Traffic Manager | Information Exchange Agreement | |||||||||||||||||||
| RSE Traffic Monitoring Provider | Application Usage Agreement | |||||||||||||||||||
| RSE Queue Warning Provider | Application Usage Agreement | |||||||||||||||||||
| Vehicle Queue Warning Provider | Application Usage Agreement | |||||||||||||||||||
| Vehicle Roadside Information Reception Provider | Application Usage Agreement | |||||||||||||||||||
Includes Enterprise Objects:
| Enterprise Object | Description |
|---|---|
| Application Certification Entity | The body that determines whether an application may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with application type. For example, applications with human safety component (crash avoidance, movement assistance etc.) may have stringent requirements and extensive testing in a variety of conditions, while applications that provide strictly mobility functionality may have far less testing requirements; possibly as little as just making sure the application doesn't interfere with any other applications. |
| Device Certification Entity | The body that determines whether a device may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with device type. |
| Driver | The 'Driver' represents the person that operates a vehicle on the roadway. Included are operators of private, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The Driver originates driver requests and receives driver information that reflects the interactions which might be useful to all drivers, regardless of vehicle classification. Information and interactions which are unique to drivers of a specific vehicle type (e.g., fleet interactions with transit, commercial, or emergency vehicle drivers) are covered by separate objects. |
| Federal Regulatory | Federal regulatory bodies that have legal authority to control and/or provide input to policies regulating transportation infrastructure and operations. This includes entities such as the Federal Communications Commission and US Department of Transportation. |
| Information Service Provider | The "Information Service Provider" represents the owner of the Transportation Information Center. The Information Service Provider is responsible for collecting and disseminating information relevant to the traveling public. |
| 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 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. |
| Remote Vehicle OBE Owner | The owner of the Remote Vehicle OBE |
| Roadway Basic Surveillance Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Roadway Basic Surveillance Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Roadway Basic Surveillance Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
| Roadway Environmental Monitoring Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Roadway Environmental Monitoring Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| Roadway Environmental Monitoring Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
| Roadway Owner | The owner of the roadway proximate to which roadside equipment will be/is installed. |
| Roadway 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. |
| Roadway 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. |
| Roadway 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. |
| RSE Deployer | The entity responsible for the deployment, operations and maintenance of roadside equipment. |
| RSE Environmental Monitoring Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| RSE Environmental Monitoring Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
| RSE Environmental Monitoring Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
| RSE Maintainer | The entity that maintains the roadside equipment, including its hardware and operating system software, but not applications software. |
| RSE Operator | The entity that operates roadside equipment in the transportation environment. |
| RSE Owner | The owner of roadside equipment. |
| RSE Provider | The "RSE Provider" is the entity that develops and (presumably) sells roadside equipment to other entities for deployment and research. |
| RSE Queue 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. |
| RSE Queue 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. |
| RSE Queue 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. |
| 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 Roadway 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. |
| TMC Roadway 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. |
| TMC Roadway 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. |
| 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 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 Queue 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 Queue 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 Queue 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 Roadside Information Reception 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 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 Roadside Information Reception 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. |
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 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. |
| Remote Vehicle OBEs | 'Remote Vehicle OBEs' represents other connected vehicles that are communicating with the host vehicle. This includes all connected motorized vehicles including passenger cars, trucks, and motorcycles and specialty vehicles (e.g., maintenance vehicles, transit vehicles) that also include the basic 'Vehicle OBE' functionality that supports V2V communications. In CVRIA, this object provides a source and destination for information transfers between connected vehicles. The host vehicle on-board equipment, represented by the Vehicle OBE physical object, sends information to, and receives information from the Remote Vehicle OBEs to model all connected vehicle V2V communications in CVRIA. |
| Roadside Equipment | 'Roadside Equipment' (RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers. |
| Roadway Basic Surveillance | "Roadway Basic Surveillance" monitors traffic conditions using fixed equipment such as loop detectors and CCTV cameras. |
| Roadway Environmental Monitoring | "Roadway Environmental Monitoring" measures environmental conditions and communicates the collected information back to a center where it can be monitored and analyzed. A broad array of general weather and road surface information may be collected. Weather conditions that may be measured include temperature, wind, humidity, precipitation, and visibility. Surface and sub-surface sensors can measure road surface temperature, moisture, icing, salinity, and other measures. |
| Roadway Warning | "Roadway Warning" includes the field equipment used to warn drivers approaching hazards on a roadway. Warnings may be generated in response to roadway weather conditions, road surface conditions, traffic conditions including queues, obstacles or animals in the roadway, and any other transient events that can be sensed. The equipment monitors traffic and roadway conditions and may send data to a traffic management center for processing or may process it to determine when a warning should be issued. When it is determined that a warning should be issued, the equipment is used to alert approaching drivers via dynamic warning signs, flashing lights, in-vehicle messages, etc. |
| RSE Development System | The system used in a backoffice environment to develop and test the roadside equipment. |
| RSE Environmental Monitoring | "RSE Environmental Monitoring" collects environmental situation (probe) data from passing vehicles that are equipped with short range communications capability. The collected data includes current environmental conditions as measured by on-board sensors (e.g., ambient temperature and precipitation measures), current status of vehicle systems that can be used to infer environmental conditions (e.g., status of lights, wipers, ABS, and traction control systems), and emissions measures reported by the vehicle. The application object collects the provided data, aggregates and filters the data based on provided configuration parameters, and sends the collected information back to a center for processing and distribution. This application object may also process the collected data locally and issue short-term road weather advisories for the road segment using short range communications. |
| RSE Installation System | The system used to install and configure the roadside equipment. |
| RSE Maintenance System | The system used to configure changes and updates to the roadside equipment. This system is capable of acquiring and reporting diagnostic information about the RSE's configuration and performance. |
| RSE Queue Warning | "RSE Queue Warning" provides V2I communications to support queue warning systems. It monitors connected vehicles to identify and monitor queues in real-time and provides information to vehicles about upcoming queues, including downstream queues that are reported by the Traffic Management Center. |
| 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 Roadway Warning | "TMC Roadway Warning" remotely monitors and controls the systems used to warn drivers approaching hazards on a roadway. It monitors data on roadway conditions from sensors in the field and generates warnings in response to roadway weather conditions, road surface conditions, traffic conditions including queues, obstacles or animals in the roadway, and any other transient events that can be sensed. |
| 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. |
| Transportation Information Center | The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service. |
| 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 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 Queue Warning | "Vehicle Queue Warning" detects vehicle queues and reports queues to other vehicles using V2V communications and to the infrastructure using V2I communications. Vehicle-based queue warning builds on the exchange of vehicle location and motion and maneuvers that supports connected vehicle safety applications. This application also receives information about downstream queues using I2V communications. Individualized queue warnings and queue characteristics relevant to the vehicle are provided to the driver. |
| Vehicle Roadside Information Reception | "Vehicle Roadside Information Reception" receives advisories, vehicle signage data, and other driver information and presents this information to the driver using in-vehicle equipment. Information presented may include fixed sign information, traffic control device status (e.g., signal phase and timing data), advisory and detour information, warnings of adverse road and weather conditions, travel times, and other driver information. |
Includes Roles:
| Role | Description |
|---|---|
| Certifies | An Enterprise verifies that a target Resource meets relevant performance, functional, environmental and quality requirements. |
| Constrains | A Resource or Enterprise applies requirements, constraints and associated tests to another Resource. |
| Installs | An Enterprise performs the initial delivery, integration and configuration of the target Resource. |
| Maintains | An Enterprise administers the hardware and software that comprise the target Resource. |
| Member | An Enterprise is part of another larger, target Enterprise. |
| Operates | An Enterprise controls the functionality and state of the target Resource. An Enterprise that Operates a resource is considered Responsible. |
| Owns | An Enterprise has financial ownership and control over the Resource. An Enterprise that Owns a resource is considered Accountable. |
Includes Coordination:
| Coordination | Type | Description |
|---|---|---|
| Application Installation Data | Information Sharing | Data needed to install the application, including the application executable code and any configuration data. Unidirectional flow. |
| Application Interface Specification | Agreement | The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question. |
| Application Maintenance Data | Information Sharing | Data used to facilitate the upgrade, patching and general health maintenance of an application component. |
| Application Performance Data | Information Sharing | Data used to characterize application performance, including such measures as availability, known errors and known uses. |
| Application Procurement Agreement | Agreement | An agreement whereupon one entity provides a copy of an application component to another entity. This component is capable of being installed and functioning, according to its requirements that passed through the application's certification process. |
| Application Usage Agreement | Agreement | An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component. |
| Backoffice Component Installation Agreement | Agreement | An agreement that grants one party permission to install a backoffice application component on a center-based device controlled by the other party. |
| Device Placement and Operations Agreement | Agreement | An agreement that enables the controller of a physical device to install it (so as to make it operational) at a fixed location controlled by another entity. |
| Employment Agreement | Agreement | An agreement between an individual and a corporation or government entity, whereupon the individual agrees to provide labor to the corporation/agency, which in turn compensates the employee. Stipulates level of compensation, working conditions, necessary equipment and training and expectations of employee performance. |
| Expectation of Data Provision | Expectation | An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data. |
| Expectation of Information Provision | Expectation | An expectation where one party believes another party will provide it information whenever such information is likely relevant to the recipient. |
| Field Component Installation Agreement | Agreement | An agreement that grants one party permission to install a field application component on a roadside device controlled by the other party. |
| 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. |
| Information Provision Agreement | Agreement | An agreement where one party agrees to provide information to another party. This is a unidirectional agreement. |
| Installation Agreement | Agreement | An agreement whereupon one entity installs an application component on a device controlled by another entity. |
| Interface Description | Agreement | Documentation of the interface between two systems, where one system does not have an application component that is part of the application, but does provide and/or receive data and/or information that is used by or sourced from the application. In many cases this is an existing interface used by the application, so the description of the interface already exists and is imposed by the terminator. |
| Maintenance Agreement | Agreement | An agreement in which one entity maintains the operational status of a system under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities. |
| Maintenance Data Exchange Agreement | Agreement | An agreement that states one entity will provide data related to maintenance of an application component to the other entity. |
| Mobile Component Installation Agreement | Agreement | An agreement whereupon the controller of OBE gives another party permission to install, configure and make operational a component that enables the mobile portion of an application. |
| Mobile Component License Agreement | Agreement | An end-user license agreement allowing the operator of the mobile device to use the mobile application component that is part of the application in question. |
| Operations Agreement | Agreement | An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity. |
| Presumption of Correct Operation | Expectation | The assumption made by one party that another party operates their device in a similar and correct fashion. Specific to devices in the transportation environment, this assumption is relevant when devices interact, where one party's device receives information from another's. The operator of the device implicitly trusts that the other device is operating according to a similar set of governing rules as its device. |
| RSE Deployment Agreement | Agreement | Agreement to install, configure and make operational roadside equipment, between the provider of that equipment and the entity that controls access to the roadside. May define locations, expectation of power provision, backhaul responsibility and installation restrictions. |
| RSE Installation Data | Information Sharing | Data necessary to configure and make RSE operational. Uni-directional. |
| RSE Maintenance Data | Information Sharing | Data necessary to modify the operational configuration of RSE; assumes RSE is already configured. Uni-directional. |
| RSE Performance Data | Information Sharing | Data that includes metrics of RSE performance. Could include fields such as uptime, packets received/transmitted, distance vector from which packets received, as well as application-specific performance measures. |
| RSE Procurement Agreement | Agreement | An agreement whereupon one entity provides roadside equipment to another entity. The RSE is capable of being installed and functioning, according to its requirements that passed through the device's certification process. |
| Service Delivery Agreement | Agreement | A relationship where one party agrees to provide a service to the other party. This agreement may specify the expected performance of this service in terms of availability and/or actions/time-type performance specifications. |
| Vehicle Data Access Agreement | Agreement | An agreement whereby the party that controls access to on-board vehicle data grants another party the right and ability to access that data. Includes the conditions under which data may be accessed, and specifies the mechanisms, including physical and functional access methods, data formats and any other considerations necessary for the accessing party to acquire data. May also include caveats regarding responsibility for data quality and responsibility for use of the data. |
| Vehicle OBE Usage Agreement | Agreement | An agreement that grants one entity permission to use a Vehicle OBE that the other party controls. |
| Vehicle Procurement Agreement | Agreement | The exchange of a vehicle for compensation. One entity purchases the vehicle from the other. |
| Vehicle Usage Agreement | Agreement | An agreement between the owner of a vehicle and a prospective operator, whereupon the owner allows the operator to use the vehicle. |
| Warranty | Agreement | A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance over time of an application component. |
Functional
Includes Processes:
Includes Data Flows:
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
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 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. |
| Remote Vehicle OBEs | Vehicle | 'Remote Vehicle OBEs' represents other connected vehicles that are communicating with the host vehicle. This includes all connected motorized vehicles including passenger cars, trucks, and motorcycles and specialty vehicles (e.g., maintenance vehicles, transit vehicles) that also include the basic 'Vehicle OBE' functionality that supports V2V communications. In CVRIA, this object provides a source and destination for information transfers between connected vehicles. The host vehicle on-board equipment, represented by the Vehicle OBE physical object, sends information to, and receives information from the Remote Vehicle OBEs to model all connected vehicle V2V communications in CVRIA. |
| Roadside Equipment | Field | 'Roadside Equipment' (RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers. |
| Traffic Management Center | Center | The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters. |
| Traffic Operations Personnel | Center | 'Traffic Operations Personnel' represents the people that operate a traffic management center. These personnel interact with traffic control systems, traffic surveillance systems, incident management systems, work zone management systems, and travel demand management systems. They provide operator data and command inputs to direct system operations to varying degrees depending on the type of system and the deployment scenario. |
| Transportation Information Center | Center | The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service. |
| 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 Warning | "Roadway Warning" includes the field equipment used to warn drivers approaching hazards on a roadway. Warnings may be generated in response to roadway weather conditions, road surface conditions, traffic conditions including queues, obstacles or animals in the roadway, and any other transient events that can be sensed. The equipment monitors traffic and roadway conditions and may send data to a traffic management center for processing or may process it to determine when a warning should be issued. When it is determined that a warning should be issued, the equipment is used to alert approaching drivers via dynamic warning signs, flashing lights, in-vehicle messages, etc. | 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 Queue Warning | "RSE Queue Warning" provides V2I communications to support queue warning systems. It monitors connected vehicles to identify and monitor queues in real-time and provides information to vehicles about upcoming queues, including downstream queues that are reported by the Traffic Management Center. | 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 Roadway Warning | "TMC Roadway Warning" remotely monitors and controls the systems used to warn drivers approaching hazards on a roadway. It monitors data on roadway conditions from sensors in the field and generates warnings in response to roadway weather conditions, road surface conditions, traffic conditions including queues, obstacles or animals in the roadway, and any other transient events that can be sensed. | 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 Queue Warning | "Vehicle Queue Warning" detects vehicle queues and reports queues to other vehicles using V2V communications and to the infrastructure using V2I communications. Vehicle-based queue warning builds on the exchange of vehicle location and motion and maneuvers that supports connected vehicle safety applications. This application also receives information about downstream queues using I2V communications. Individualized queue warnings and queue characteristics relevant to the vehicle are provided to the driver. | Vehicle OBE |
| Vehicle Roadside Information Reception | "Vehicle Roadside Information Reception" receives advisories, vehicle signage data, and other driver information and presents this information to the driver using in-vehicle equipment. Information presented may include fixed sign information, traffic control device status (e.g., signal phase and timing data), advisory and detour information, warnings of adverse road and weather conditions, travel times, and other driver information. | Vehicle OBE |
Includes Information Flows:
| Information Flow | Description |
|---|---|
| collision warning information | Information provided to support computer-based intervention of vehicle controls. Analogous to driver warnings, these are warnings issued to on-board control systems of an impending collision or other situation detected by the Vehicle OBE that may require control intervention. |
| 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. |
| queue warning application information | Information regarding formed or impending queues (location of the end of queue, estimated duration of the queue, and other descriptions of the queue condition) and recommendations for upstream vehicles including speed reduction, lane change, or diversion recommendations. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted. |
| queue warning application status | Queue warning application status reported by the RSE. This includes current operational state and status of the RSE and a record of measured vehicle speeds and identified queues. |
| queue warning information | Information regarding formed or impending queues (location of the end of queue, estimated duration of the queue, and other descriptions of the queue condition) and recommendations for upstream vehicles including speed reduction, lane change, or diversion recommendations. |
| 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. |
| roadway warning system control | Information used to configure and control roadway warning systems. |
| roadway warning system status | Current operating status of roadway warning systems. |
| 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 images | High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications. This flow includes the images and meta data that describes the images. |
| traffic operator data | Presentation of traffic operations data to the operator including traffic conditions, current operating status of field equipment, maintenance activity status, incident status, video images, security alerts, emergency response plan updates and other information. This data keeps the operator appraised of current road network status, provides feedback to the operator as traffic control actions are implemented, provides transportation security inputs, and supports review of historical data and preparation for future traffic operations activities. |
| traffic operator input | User input from traffic operations personnel including requests for information, configuration changes, commands to adjust current traffic control strategies (e.g., adjust signal timing plans, change DMS messages), and other traffic operations data entry. |
| traffic sensor control | Information used to configure and control traffic sensor systems. |
| traffic situation data | Current, aggregate traffic data collected from connected vehicles that can be used to supplement or replace information collected by roadside traffic detectors. It includes raw and/or processed reported vehicle speeds, counts, and other derived measures. Raw and/or filtered vehicle control events may also be included to support incident detection. |
| vehicle control event | Notification that the vehicle has performed an emergency maneuver that could impact the safety of surrounding vehicles. This includes hard braking and activation of traction/stability control systems or other maneuvers that warrant immediate notification of surrounding vehicles. The information flow conveys the current vehicle location, path, and current control actions. |
| vehicle environmental data | Data from vehicle safety and convenience systems that can be used to estimate environmental conditions, including measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, anti-lock brake status, and other collected vehicle system status and sensor information. The collected data is reported along with the location, heading, and time that the data was collected. Both current data and snapshots of recent events (e.g., traction control or anti-lock brake system activations) may be reported. |
| vehicle location and motion | Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size. |
| vehicle location and motion for surveillance | Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size. This flow represents monitoring of basic safety data ('vehicle location and motion') broadcast by passing connected vehicles for use in vehicle detection and traffic monitoring applications. |
| vehicle signage data | In-vehicle signing data that augments regulatory, warning, and informational road signs and signals. The information provided would include static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal states, grade crossing information, local traffic and road conditions, detours, advisories, and warnings). |
| vehicle signage local data | Information provided by adjacent field equipment to support in-vehicle signing of dynamic information that is currently being displayed to passing drivers. This includes the dynamic information (e.g., current signal states, grade crossing information, local traffic and road conditions, detours, advisories, parking availability, etc.) and control parameters that identify the desired timing, duration, and priority of the signage data. |
| video surveillance control | Information used to configure and control video surveillance systems. |
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
Requirements
| Need | Requirement | ||
|---|---|---|---|
| N2.111 | The Queue Warning (Q-WARN) System needs to inform the Driver of a downstream traffic queue in sufficient time to react safely. | 2.233 | The Queue Warning (Q-WARN) System shall communicate queue warnings and queue characteristic information based on vehicle's distance to end of queue, (length of queue, lane(s) impacted, other descriptions of the queue condition) to the driver. |
| N2.112 | The Q-WARN System needs to inform the Driver of a downstream traffic queue in sufficient time to react safely. | 2.234 | The Q-WARN System shall communicate queue warnings and queue information to the driver utilizing auditory, visual, or haptic alerts and auditory or visual (on-screen) messages. |
| N2.113 | The Q-WARN System needs to inform the driver of what actions to take to respond to the impending queue including speed reduction, lane change, or diversion. | 2.235 | The Q-WARN System shall communicate queue response strategies (speed reduction, lane change, diversion recommendations) to the driver. |
| 2.236 | The Q-WARN System shall communicate queue response strategies to the driver utilizing auditory or visual (on-screen) messages. | ||
| N2.114 | The Q-WARN System needs to detect a queue formation | 2.237 | The Q-WARN System shall communicate with the connected vehicles to gather real-time vehicle-collected data including vehicle speed, location and localized weather condition from the vehicle network. |
| 2.238 | The Q-WARN System shall detect the location, duration, and length of queue propagation, as a result of significant downstream speed reductions or stopped traffic. | ||
| N2.115 | The Q-WARN System needs to disseminate queued status alert to upstream vehicles and other systems | 2.239 | The Q-WARN System shall disseminate a queued status alert to other connected vehicles via V2V communication. |
| 2.240 | The Q-WARN System shall disseminate a queued status alert to infrastructure systems via V2I communication. | ||
| N2.116 | The Q-WARN System needs to receive queue information from other vehicles or systems. | 2.241 | The Q-WARN System shall receive queue warning messages from infrastructure systems via I2V communication channels. |
| 2.242 | The Q-WARN System shall receive queue warning messages from other vehicles via V2V communication channels. | ||
| N2.117 | The Q-WARN System needs to generate queue warning response strategies, including speed reduction, lane change, or diversion. | 2.243 | The Q-WARN system shall individualize generic queue warning message based on vehicle's position and distance to the end of the queue. |
| 2.244 | The Q-WARN system shall generate appropriate queue response strategies that include speed reduction, lane change, or diversion recommendations based on local traffic, weather, and roadway conditions. | ||
| 2.245 | The Q-WARN system shall send queue warning status to the SPD-HARM application to generate appropriate speed reduction and lane change messages. | ||
| 2.246 | The Q-WARN system shall interface with the Connected Vehicle-based EnableATIS and/or Freight Drayage Optimization applications to generate appropriate route diversion recommendations. | ||
| N2.118 | The Q-WARN System needs to collect traffic, road condition, and weather data from other systems to provide a complete picture of the conditions that are contributing to the queue and to support the generation of warning/recommendations. | 2.247 | The Q-WARN system shall have a data collection capability for receiving real-time traffic, road conditions, and weather data from multiple sources. |
| 2.248 | The Q-WARN system shall have a data collection capability for receiving real-time traffic, road conditions, and weather data from infrastructure-based systems. | ||
| 2.249 | The Q-WARN system shall have the capability to receive real-time traffic (including location and speed), road conditions (e.g. ice, wet, etc.), and weather data (clear, rainy and snowy) from connected vehicles. | ||
| N2.119 | The Q-WARN System needs to quickly and reliably detect a formed queue, from traffic information received from fixed infrastructures where vehicle-based communication and detection is not available. | 2.250 | The Q-WARN system shall have a queue detection capability for known fixed queue generation locations. |
| 2.251 | The Q-WARN system shall determine the lane(s) impacted by the formed queue. | ||
| 2.252 | The Q-WARN system shall determine the length of the formed queue. | ||
| 2.253 | The Q-WARN system shall determine the number of vehicles in the formed queue. | ||
| 2.254 | The Q-WARN system shall determine the traveling speed and direction of the formed queue. | ||
| N2.120 | The Q-WARN System needs to predict impending queues. | 2.255 | The Q-WARN system shall utilize current, predicted, and historical traffic data, and real-time and predicted weather data, road surface data in queue prediction algorithms. |
| 2.256 | The Q-WARN system shall have a queue prediction capability for known fixed queue generation locations. | ||
| 2.257 | The Q-WARN system shall determine the time of formation of the predicted queue. | ||
| 2.258 | The Q-WARN system determine the lane(s) impacted by the predicted queue. | ||
| 2.259 | The Q-WARN system shall determine the length of the predicted queue. | ||
| 2.260 | The Q-WARN system determine the expected duration of the predicted queue. | ||
| 2.261 | The Q-WARN system shall determine the number of vehicles in the predicted queue. | ||
| 2.262 | The Q-WARN system shall determine the traveling speed and direction of the predicted queue. | ||
| N2.121 | The Q-WARN System needs to generate queue warning response strategies for upstream vehicles | 2.263 | The Q-WARN system shall have a queue warning response strategy generation capability. |
| 2.264 | The Q-WARN system shall generate target speed strategies that consider estimated duration of the queue, other descriptions of the queue condition, downstream traffic conditions, predicted future traffic conditions, weather, and local roadway surface conditions. | ||
| N2.122 | The Q-WARN System needs to disseminate recommended queue warning strategies to upstream vehicles. | 2.265 | The Q-WARN system shall have a queue warning and queue information dissemination capability. |
| 2.266 | The Q-WARN system shall disseminate queue warnings and queue information to DMS locations. | ||
| 2.267 | The Q-WARN system shall disseminate queue warnings and queue information to connected vehicles. | ||
| N2.123 | The Q-WARN System needs to analyze performance of the Q-WARN system in order to make changes to the algorithms or software to improve the performance of the system. | 2.268 | The Q-WARN system shall have the capability to conduct segment-specific and network-wide operational performance analysis. |
| 2.269 | The Q-WARN system shall conduct operational performance analysis in terms of travel time reliability, travel delay, and capacity drop. | ||
| 2.270 | The Q-WARN system shall provide a means to compare predicted versus actual queue occurrences and characteristics. | ||
| 2.271 | The Q-WARN system shall be able to modify the algorithms and software performance to improve the performance of the system. | ||
| N2.124 | The Q-WARN System needs to disseminate Q-WARN information to other dynamic mobility applications | 2.272 | The Q-WARN system shall send queue warning information (queue location and characteristics, recommended responses provided, user messages provided) to other dynamic mobility applications. |
| N2.125 | The Q-WARN System needs to disseminate Q-WARN data information to freeway and arterial traffic management entities and other dynamic mobility applications through standardized interfaces, including a Data Capture and Management (DCM) system. | 2.273 | The Q-WARN system shall send queue warning related data to freeway and arterial traffic management entities. |
Related Sources
- Concept Development and Needs Identification for INFLO: Functional and Performance Requirements, and High-Level Data and Communication Needs, Final, 11/1/2012
- Concept Development and Needs Identification for Intelligent Network Flow Optimization (INFLO), Functional and Performance Requirements, and High-Level Data and Communication Needs, Draft v5.0, 11/1/2012
- Report on Detailed Requirements for the INFLO Prototype, Final, 12/27/2013
- Report on Dynamic Speed Harmonization and Queue Warning Algorithm Design, Final, 2/28/2014
- System Design Document for the INFLO Prototype, Final, 3/28/2014
Security
In order to participate in this application, each physical object should meet or exceed the following security levels.
| Physical Object Security | ||||
|---|---|---|---|---|
| Physical Object | Confidentiality | Integrity | Availability | Security Class |
| Security levels have not been defined yet. | ||||
In order to participate in this application, each information flow triple should meet or exceed the following security levels.
| Information Flow Security | |||||
|---|---|---|---|---|---|
| Source | Destination | Information Flow | Confidentiality | Integrity | Availability |
| Basis | Basis | Basis | |||
| Security levels have not been defined yet. | |||||