Type: Safety
Groups:- V2I Safety
Railroad Crossing Violation Warning
The Railroad Crossing Violation Warning (RCVW) application will alert and/or warn drivers who are approaching an at-grade railroad crossing if they are on a crash-imminent trajectory to collide with a crossing or approaching train. This will be achieved through the integration of both vehicle-based and infrastructure-based technologies. The RSE sends to the vehicle detailed geometric information about the intersection, as well as information about whether a train is approaching or blocking the intersection. The geometric information could be obtained from an RSE at the intersection, or obtained from an RSE at some earlier point in the vehicles trip. The information about the approach or presence of a train would be obtained from the infrastructure via a connection between the rail infrastructure and the RSE. The information received from the RSE at the intersection could also be augmented with road surface information or other weather-related data. A more advanced version of the application could provide train arrival information or information about the amount of time the Highway Rail Intersection (HRI) will be blocked by the train.
Enterprise
SVG Diagrams: Installation Operations Maintenance Certification
PNG Diagrams: Installation Operations Maintenance Certification
Business Interaction Matrix:
Railroad Crossing Violation Warning Operations Stage | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Vehicle Owner | Driver | Vehicle OBE Owner | Roadway Owner | RSE Owner | RSE Operator | ITS Roadway Equipment Owner | ITS Roadway Operator | Traffic Manager | RSE Rail Crossing Warning Provider | Rail Operator | RSE Environmental Monitoring Provider | Vehicle Rail Crossing Warning Provider | |
Vehicle Owner | Vehicle Usage Agreement | Vehicle OBE Usage Agreement | Application Usage Agreement | ||||||||||
Driver | Vehicle Usage Agreement | Expectation of Information Provision | Expectation of Information Provision | ||||||||||
Vehicle OBE Owner | Vehicle OBE Usage Agreement | Expectation of Information Provision | Expectation of Information Provision | ||||||||||
Roadway Owner | Service Delivery Agreement | ||||||||||||
RSE Owner | Expectation of Information Provision | Service Delivery Agreement | Operations Agreement | Information Exchange Agreement | Application Usage Agreement | Application Usage Agreement | |||||||
RSE Operator | Operations Agreement | Information Exchange Agreement | |||||||||||
ITS Roadway Equipment Owner | Information Exchange Agreement | Operations Agreement | Information Exchange Agreement | Information Exchange Agreement | |||||||||
ITS Roadway Operator | Expectation of Information Provision | Operations Agreement | |||||||||||
Traffic Manager | Information Exchange Agreement | ||||||||||||
RSE Rail Crossing Warning Provider | Application Usage Agreement | ||||||||||||
Rail Operator | Information Exchange Agreement | Information Exchange Agreement | |||||||||||
RSE Environmental Monitoring Provider | Application Usage Agreement | ||||||||||||
Vehicle Rail Crossing Warning Provider | Application Usage Agreement |
Includes Enterprise Objects:
Enterprise Object | Description |
---|---|
Application Certification Entity | The body that determines whether an application may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with application type. For example, applications with human safety component (crash avoidance, movement assistance etc.) may have stringent requirements and extensive testing in a variety of conditions, while applications that provide strictly mobility functionality may have far less testing requirements; possibly as little as just making sure the application doesn't interfere with any other applications. |
Device Certification Entity | The body that determines whether a device may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with device type. |
Driver | The 'Driver' represents the person that operates a vehicle on the roadway. Included are operators of private, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The Driver originates driver requests and receives driver information that reflects the interactions which might be useful to all drivers, regardless of vehicle classification. Information and interactions which are unique to drivers of a specific vehicle type (e.g., fleet interactions with transit, commercial, or emergency vehicle drivers) are covered by separate objects. |
Federal Regulatory | Federal regulatory bodies that have legal authority to control and/or provide input to policies regulating transportation infrastructure and operations. This includes entities such as the Federal Communications Commission and US Department of Transportation. |
ITS Certification Entity | The body that determines whether an ITS device or application may be deployed and operated in the transportation environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with device and application type. Typically not a formal body, assigned on a project-by-project basis depending on the type of infrastructure involved. Since ITS projects are locally-focused (typically state or smaller), the entities that are part of this body are typically those with operational jurisdiction where the ITS is installed (e.g., state or local DOTs, state or local maintenance managers etc.) |
ITS Roadway Equipment Owner | The entity that owns the Roadway ITS equipment. |
ITS Roadway Operator | The entity that operates the Roadway ITS equipment. |
Rail Operator | Operator and owner of railroad. |
Roadway Advanced Rail Crossing 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 Advanced Rail Crossing 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 Advanced Rail Crossing Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
Roadway Environmental Monitoring Installer | Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
Roadway Environmental Monitoring Maintainer | Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers. |
Roadway Environmental Monitoring Provider | Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles. |
Roadway Owner | The owner of the roadway proximate to which roadside equipment will be/is installed. |
RSE 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 Rail Crossing 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 Rail Crossing 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 Rail Crossing 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. |
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 Rail Crossing 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 Rail Crossing 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 Rail Crossing 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. |
Traffic Manager | The entity responsible for the management of traffic, both freeway and arterial. |
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 Rail Crossing 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 Rail Crossing 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 Rail Crossing 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. |
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. |
Personal Information Device | The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with connected vehicle on-board equipment. |
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 Advanced Rail Crossing | "Roadway Advanced Rail Crossing" manages highway traffic at highway-rail intersections (HRIs) where operational requirements demand advanced features (e.g., where rail operational speeds are greater than 80 miles per hour). The active warning systems supported by this application include positive barrier systems which preclude entrance into the intersection when the barriers are activated. This application is activated on notification by wayside interface equipment which detects, or communicates with the approaching train. In this application, additional information about the arriving train is also provided by the wayside interface equipment so that the train's direction of travel, its estimated time of arrival, and the estimated duration of closure may be derived. This enhanced information may be conveyed to the driver prior to, or in context with, warning system activation. This application also includes detection capabilities which enable it to detect an entrapped or otherwise immobilized vehicle on the grade crossing and provide an immediate notification to the wayside interface equipment and traffic management. |
Roadway Environmental Monitoring | "Roadway Environmental Monitoring" measures environmental conditions and communicates the collected information back to a center where it can be monitored and analyzed. A broad array of general weather and road surface information may be collected. Weather conditions that may be measured include temperature, wind, humidity, precipitation, and visibility. Surface and sub-surface sensors can measure road surface temperature, moisture, icing, salinity, and other measures. |
RSE 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 Rail Crossing Warning | "RSE Rail Crossing Warning" is a connected vehicle application that improves safety at rail crossings. It communicates with wayside equipment that detects or communicates with approaching trains. It provides rail crossing warnings and train arrival information to approaching vehicles and monitors connected vehicles that may intrude on the crossing. |
TMC Rail Crossing Management | "TMC Rail Crossing Management" monitors and controls rail crossing traffic control equipment. Various levels of roadside equipment may be interfaced including standard active warning systems and high speed systems that provide additional information on approaching trains and detect and report obstructions on the grade crossing. This application remotely monitors and reports the status of the rail crossing equipment and sends control plan updates to the equipment. |
Traffic Management Center | The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters. |
Vehicle | The conveyance that provides the sensory, processing, storage, and communications functions necessary to support efficient, safe, and convenient travel. These functions reside in general vehicles including personal automobiles, commercial vehicles, emergency vehicles, transit vehicles, or other vehicle types. |
Vehicle Databus | The 'Vehicle Databus' represents the interface to the vehicle databus (e.g., CAN, LIN, Ethernet/IP, FlexRay, and MOST) that may enable communication between the Vehicle OBE and other vehicle systems to support connected vehicle applications. The vehicle system statuses and/or sensor outputs available on the databus will vary based on the equipment installed on the vehicle and availability on databus. System statuses and sensor outputs may include select vehicle systems and sensors such as accelerometers, yaw rate sensors, and GPS derived location and timing information. In CVRIA, this physical object is used to represent the onboard interactions between the Vehicle OBE and the other systems included in a host vehicle. Note that the vehicle databus interface is not standardized across all vehicle classes. Also, some Vehicle OBE implementations will not have access to the vehicle databus. See 'Vehicle OBE' for more information. |
Vehicle 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 Rail Crossing Warning | "Vehicle Rail Crossing Warning " uses I2V communications to receive alerts of trains entering HRIs and to provide warnings to drivers regarding the trains. The warning can include second train warning (meaning the HRI gates are about to lower, or remain lowered due to the arrival of a second train). The application can also provide vehicle infringement warnings by using the alert information along with vehicle trajectory information to determine that the vehicle will infringe upon a crossing that is (or will be) occupied by a train. |
Wayside Equipment | 'Wayside Equipment' represents train interface equipment (usually) maintained and operated by the railroad and (usually) physically located at or near a grade crossing. It is a source and destination for information for, or about, approaching trains and their crews (e.g. the time at which the train will arrive and the time it will take to clear a crossing, crossing status or warnings, etc.). Generally one wayside equipment interface would be associated with one highway rail intersection. However, multiple crossings may be controlled using information based on data from one wayside equipment interface. |
Includes Roles:
Role | Description |
---|---|
Certifies | An Enterprise verifies that a target Resource meets relevant performance, functional, environmental and quality requirements. |
Constrains | A Resource or Enterprise applies requirements, constraints and associated tests to another Resource. |
Installs | An Enterprise performs the initial delivery, integration and configuration of the target Resource. |
Maintains | An Enterprise administers the hardware and software that comprise the target Resource. |
Member | An Enterprise is part of another larger, target Enterprise. |
Operates | An Enterprise controls the functionality and state of the target Resource. An Enterprise that Operates a resource is considered Responsible. |
Owns | An Enterprise has financial ownership and control over the Resource. An Enterprise that Owns a resource is considered Accountable. |
Includes Coordination:
Coordination | Type | Description |
---|---|---|
Application Installation Data | Information Sharing | Data needed to install the application, including the application executable code and any configuration data. Unidirectional flow. |
Application Interface Specification | Agreement | The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question. |
Application Maintenance Data | Information Sharing | Data used to facilitate the upgrade, patching and general health maintenance of an application component. |
Application Performance Data | Information Sharing | Data used to characterize application performance, including such measures as availability, known errors and known uses. |
Application Procurement Agreement | Agreement | An agreement whereupon one entity provides a copy of an application component to another entity. This component is capable of being installed and functioning, according to its requirements that passed through the application's certification process. |
Application Usage Agreement | Agreement | An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component. |
Backoffice Component Installation Agreement | Agreement | An agreement that grants one party permission to install a backoffice application component on a center-based device controlled by the other party. |
Backoffice Component Maintenance Agreement | Agreement | An agreement in which one entity maintains the operational status of the backoffice component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities. |
Device Placement and Operations Agreement | Agreement | An agreement that enables the controller of a physical device to install it (so as to make it operational) at a fixed location controlled by another entity. |
Expectation of Data Provision | Expectation | An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data. |
Expectation of Information Provision | Expectation | An expectation where one party believes another party will provide it information whenever such information is likely relevant to the recipient. |
Field Component Installation Agreement | Agreement | An agreement that grants one party permission to install a field application component on a roadside device controlled by the other party. |
Field Component Maintenance Agreement | Agreement | An agreement in which one entity maintains the operational status of the field component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities. |
Includes | Includes | Indicates that one component is entirely contained within another component. |
Information Exchange Agreement | Agreement | An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. |
Installation Agreement | Agreement | An agreement whereupon one entity installs an application component on a device controlled by another entity. |
Interface Description | Agreement | Documentation of the interface between two systems, where one system does not have an application component that is part of the application, but does provide and/or receive data and/or information that is used by or sourced from the application. In many cases this is an existing interface used by the application, so the description of the interface already exists and is imposed by the terminator. |
Maintenance Agreement | Agreement | An agreement in which one entity maintains the operational status of a system under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities. |
Maintenance Data Exchange Agreement | Agreement | An agreement that states one entity will provide data related to maintenance of an application component to the other entity. |
Mobile Component Installation Agreement | Agreement | An agreement whereupon the controller of OBE gives another party permission to install, configure and make operational a component that enables the mobile portion of an application. |
Mobile Component License Agreement | Agreement | An end-user license agreement allowing the operator of the mobile device to use the mobile application component that is part of the application in question. |
Mobile Component Maintenance Agreement | Agreement | An agreement in which one entity maintains the operational status of the mobile component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities. |
Operations Agreement | Agreement | An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity. |
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
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. |
Roadside Equipment | Field | 'Roadside Equipment' (RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers. |
Traffic Management Center | Center | The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters. |
Vehicle Databus | Vehicle | The 'Vehicle Databus' represents the interface to the vehicle databus (e.g., CAN, LIN, Ethernet/IP, FlexRay, and MOST) that may enable communication between the Vehicle OBE and other vehicle systems to support connected vehicle applications. The vehicle system statuses and/or sensor outputs available on the databus will vary based on the equipment installed on the vehicle and availability on databus. System statuses and sensor outputs may include select vehicle systems and sensors such as accelerometers, yaw rate sensors, and GPS derived location and timing information. In CVRIA, this physical object is used to represent the onboard interactions between the Vehicle OBE and the other systems included in a host vehicle. Note that the vehicle databus interface is not standardized across all vehicle classes. Also, some Vehicle OBE implementations will not have access to the vehicle databus. See 'Vehicle OBE' for more information. |
Vehicle OBE | Vehicle | The Vehicle On-Board Equipment (OBE) provides the vehicle-based processing, storage, and communications functions necessary to support connected vehicle operations. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle OBE. This communication platform is augmented with processing and data storage capability that supports the connected vehicle applications. In CVRIA, the Vehicle OBE includes the functions and interfaces that support connected vehicle applications for passenger cars, trucks, and motorcycles. Many of these applications (e.g., V2V Safety applications) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle OBE includes the common interfaces and functions that apply to all motorized vehicles. |
Wayside Equipment | Field | 'Wayside Equipment' represents train interface equipment (usually) maintained and operated by the railroad and (usually) physically located at or near a grade crossing. It is a source and destination for information for, or about, approaching trains and their crews (e.g. the time at which the train will arrive and the time it will take to clear a crossing, crossing status or warnings, etc.). Generally one wayside equipment interface would be associated with one highway rail intersection. However, multiple crossings may be controlled using information based on data from one wayside equipment interface. |
Includes Application Objects:
Application Object | Description | Physical Object |
---|---|---|
Roadway Advanced Rail Crossing | "Roadway Advanced Rail Crossing" manages highway traffic at highway-rail intersections (HRIs) where operational requirements demand advanced features (e.g., where rail operational speeds are greater than 80 miles per hour). The active warning systems supported by this application include positive barrier systems which preclude entrance into the intersection when the barriers are activated. This application is activated on notification by wayside interface equipment which detects, or communicates with the approaching train. In this application, additional information about the arriving train is also provided by the wayside interface equipment so that the train's direction of travel, its estimated time of arrival, and the estimated duration of closure may be derived. This enhanced information may be conveyed to the driver prior to, or in context with, warning system activation. This application also includes detection capabilities which enable it to detect an entrapped or otherwise immobilized vehicle on the grade crossing and provide an immediate notification to the wayside interface equipment and traffic management. | ITS Roadway Equipment |
Roadway Environmental Monitoring | "Roadway Environmental Monitoring" measures environmental conditions and communicates the collected information back to a center where it can be monitored and analyzed. A broad array of general weather and road surface information may be collected. Weather conditions that may be measured include temperature, wind, humidity, precipitation, and visibility. Surface and sub-surface sensors can measure road surface temperature, moisture, icing, salinity, and other measures. | ITS Roadway Equipment |
RSE 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 Rail Crossing Warning | "RSE Rail Crossing Warning" is a connected vehicle application that improves safety at rail crossings. It communicates with wayside equipment that detects or communicates with approaching trains. It provides rail crossing warnings and train arrival information to approaching vehicles and monitors connected vehicles that may intrude on the crossing. | Roadside Equipment |
TMC Rail Crossing Management | "TMC Rail Crossing Management" monitors and controls rail crossing traffic control equipment. Various levels of roadside equipment may be interfaced including standard active warning systems and high speed systems that provide additional information on approaching trains and detect and report obstructions on the grade crossing. This application remotely monitors and reports the status of the rail crossing equipment and sends control plan updates to the equipment. | Traffic Management Center |
Vehicle Rail Crossing Warning | "Vehicle Rail Crossing Warning " uses I2V communications to receive alerts of trains entering HRIs and to provide warnings to drivers regarding the trains. The warning can include second train warning (meaning the HRI gates are about to lower, or remain lowered due to the arrival of a second train). The application can also provide vehicle infringement warnings by using the alert information along with vehicle trajectory information to determine that the vehicle will infringe upon a crossing that is (or will be) occupied by a train. | Vehicle OBE |
Includes Information Flows:
Information Flow | Description |
---|---|
arriving train information | Information for a train approaching a highway-rail intersection that may include direction and allow calculation of approximate arrival time and closure duration. |
driver information | Regulatory, warning, and guidance information provided to the driver while en route to support safe and efficient vehicle operation. |
driver update information | Information provided to the driver-vehicle interface to inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment. The flow includes the information to be presented to the driver and associated metadata that supports processing, prioritization, and presentation by the DVI as visual displays, audible information and warnings, and/or haptic feedback. |
driver updates | Information provided to the driver including visual displays, audible information and warnings, and haptic feedback. The updates inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment. |
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. |
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 infringement info | Vehicle path information sent by a vehicle that is performing an unpermitted movement at an intersection such as a stop sign violation or running a red light. |
rail crossing application info | Rail crossing 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. |
rail crossing application status | Rail crossing application status reported by the RSE. This includes current operational state and status of the RSE and a record of rail crossing events and alerts and warnings issued. |
rail crossing blockage notification | Notification that a highway-rail intersection is obstructed and supporting information. |
rail crossing control data | Data required for HRI information transmitted at railroad grade crossings and within railroad operations. |
rail crossing operational status | Status of the highway-rail grade crossing equipment including both the current state or mode of operation and the current equipment condition. |
rail crossing request | A request for highway-rail intersection status or a specific control request intended to modify HRI operation. |
rail crossing status | Status of the highway-rail intersection equipment including both the current state or mode of operation and the current equipment condition. |
rail crossing warning | A warning of a train approaching or already in a highway rail intersection. |
road weather advisories | Segment-specific weather and road conditions including real-time advisories of deteriorating road and weather conditions, medium-term advisories for the next 2–12 hours, and long-term advisories more than 12 hours into the future. The advisories may include advisories that are issued by the RSE based on locally collected environmental data (e.g., an ice on bridge advisory). |
track status | Current status of the wayside equipment and notification of an arriving train. |
vehicle location and motion | Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size. |
Application Interconnect Diagram
SVG Diagram
PNG Diagram
Application Triples
Requirements
Need | Requirement | ||
---|---|---|---|
N3.037 | Railroad Crossing Violation Warning (RCVW) needs to warn drivers of crossing closures or potential crash-imminent situations with a crossing or oncoming train in time for the driver to take appropriate action. | 3.088 | Railroad Crossing Violation Warning (RCVW) shall warn the driver of a potential crash at a railroad grade crossing. |
3.089 | RCVW shall calculate whether the vehicle may approach the railroad intersection while a train is present in the intersection. | ||
3.089a | RCVW shall warn drivers of crossing closures due to oncoming trains. | ||
N3.038 | RCVW needs information describing railroad crossing intersection geometry. | 3.090 | RCVW shall acquire railroad crossing intersection geometry information. |
N3.039 | RCVW needs weather and road conditions in the intersection area. | 3.091 | RCVW shall acquire weather information for the area near the railroad grade crossing intersection, including dew point temperature, wind speed, wind direction and visibility. |
3.092 | RCVW shall acquire road surface condition information for the area near the railroad grade crossing intersection, including road surface temperature, roadway water depth, roadway ice depth, roadway snow depth, adjacent snow depth). | ||
N3.040 | RCVW needs dynamic vehicle telematics data and vehicle configuration data. | 3.086 | Railroad Crossing Violation Warning (RCVW) shall acquire dynamic vehicle telematics data, including vehicle position, speed, acceleration and heading (optionally, turn signal and steering angle). |
3.087 | RCVW shall acquire vehicle configuration data, including vehicle weight, dimensions, and whether the vehicle has a trailer. | ||
N3.041 | RCVW needs to know when an approaching or crossing train(s) will cross and is crossing the RCVW-equipped at-grade crossing. | 3.093 | RCVW shall be able to acquire approaching train location information. |
N3.042 | RCVW needs to calculate an appropriate deceleration required to stop at the intersection given a set of data elements: road geometry, environmental road conditions, vehicle configuration data, and available telematics. | 3.094 | RCVW shall calculate the necessary deceleration required for the vehicle to stop at the intersection. |
N3.104 | Vehicle to Infrastructure (V2I) Safety applications need to assess their own performance, to determine errors and avoid failures when critical components fail. | 3.207 | Vehicle to Infrastructure (V2I) Safety applications shall analyze their own performance and enter fail-safe mode (a mode such that the application cannot provide information or perform actions that affect its host) when critical components fail. |
3.208 | V2I Safety applications shall notify the driver when onboard components are offline | ||
3.209 | V2I Safety applications shall notify its owner/operator when onboard components are offline. | ||
N3.105 | V2I Safety applications need to broadcast the performance of their host vehicle, to enable V2I applications that rely on knowing the location and/or trajectories of other vehicles. | 3.210 | V2I Safety applications shall broadcast the location, speed, acceleration, heading, steering wheel angle, brake system status, vehicle size and path history of host vehicles. |
N3.106 | V2I Safety applications need to have a common time source so that location and projected positions may be synchronized. | 3.211 | V2I Safety applications shall have a common time source. |
N3.107 | V2I Safety applications need to have positioning accurate enough to create alerts and/or warnings when warranted. | 3.212 | V2I Safety applications shall provide a means for any System component to determine its geographic position, in three dimensions. |
N3.108 | V2I Safety applications need to have positioning accurate enough to avoid false positive alerts and/or warnings. | 3.213 | V2I Safety applications shall provide position data together with a measure of the accuracy of the geographic position. |
Related Sources
- Connected Vehicle Safety Applications for Highway Rail Intersections (HRI) ConOps, Draft, 9/21/2012
- Vehicle-to-Infrastructure (V2I) Safety Applications Concept of Operation Document, Draft, 8/10/2012
- Vehicle-to-Infrastructure (V2I) Safety Applications System Requirements Document, Final, 3/8/2013
- Vehicle-to-Infrastructure Rail Crossing Violation Warning Concept of Operations, Draft, 3/11/2015
- Vehicle-to-Infrastructure Rail Crossing Violation Warning System Requirements Specification, Draft, 3/11/2015
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. |