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

host transit vehicle status Quintuple

Bidirectional?: False

host transit vehicle status (A-Interconnect): This CVRIA application interconnect encapsulates all of the Layer 2 information flows between the 'Transit Vehicle Schedule Management' application object and the 'Transit Vehicle Databus' physical object. In this case, there is only a single Layer 2 flow associated with this interconnect, so the Layer 1 application interconnect name and the Layer 2 information flow name are both 'host transit vehicle status'. This application interconnect is uni-directional since the underlying layer 2 information flows go from 'Transit Vehicle Databus' to 'Transit Vehicle OBE'.

Transit Vehicle Databus (Source Physical Object): The 'Transit Vehicle Databus' represents the vehicle databus that interfaces with on-board equipment on a transit vehicle. It is a specialized and extended form of the Vehicle Databus that is subject to different vehicle databus standards and hosts a broad range of components that are unique to a transit vehicle including the farebox and associated electronics, passenger counters, and transit security systems. As a specialized form of the Vehicle Databus, it also provides access to the general-purpose sensors (e.g., radars, cameras), GPS, drive train monitoring and control systems, and vehicle safety features that support connected vehicle applications. The Transit Vehicle may represent a bus, paratransit vehicle, light rail vehicle, or other vehicle designed to carry passengers. In CVRIA, the 'Transit Vehicle Databus' is used to represent the onboard interactions between the Transit Vehicle OBE and the other systems included in a host transit vehicle.

Transit Vehicle OBE (Destination Physical Object): The Transit Vehicle On-Board equipment (OBE) resides in a transit vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient movement of passengers. The types of transit vehicles containing this physical object include buses, paratransit vehicles, light rail vehicles, other vehicles designed to carry passengers, and supervisory vehicles. It collects ridership levels and supports electronic fare collection. It supports a traffic signal prioritization function that communicates with the roadside physical object to improve on-schedule performance. Automated vehicle location enhances the information available to the transit operator enabling more efficient operations. On-board sensors support transit vehicle maintenance. The physical object supports on-board security and safety monitoring. This monitoring includes transit user or vehicle operator activated alarms (silent or audible), as well as surveillance and sensor equipment. The surveillance equipment includes video (e.g. CCTV cameras), audio systems and/or event recorder systems. It also furnishes travelers with real-time travel information, continuously updated schedules, transfer options, routes, and fares. In CVRIA, a separate 'Vehicle OBE' physical object supports the general V2V and V2I safety applications and other applications that apply to all vehicles, including transit vehicles. The Transit Vehicle OBE supplements these general capabilities with capabilities that are specific to transit vehicles.

Transit Vehicle Schedule Management (Destination Application Object): "Transit Vehicle Schedule Management" monitors schedule performance and identifies corrective actions when a deviation is detected. It provides two-way communication between the transit vehicle and center, enabling the center to communicate with the vehicle operator and monitor on-board systems.