• 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

vehicle control information Quintuple

Bidirectional?: False

vehicle control information (A-Interconnect): This CVRIA application interconnect encapsulates all of the Layer 2 information flows between the 'Vehicle Cooperative Cruise Control' application object and the '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 'vehicle control information'. This application interconnect is uni-directional since the underlying layer 2 information flows go from 'Vehicle OBE' to 'Vehicle Databus'.

Vehicle OBE (Source Physical Object): 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 Cooperative Cruise Control (Source Application Object): "Vehicle Cooperative Cruise Control" regulates vehicle speed using V2V communications to share speeds and coordinate maneuvers with other vehicles, maintaining vehicle speed and a safe headway. It also provides the capability for vehicles to operate in cooperative platoons with reduced headways in designated lanes. These capabilities are provided by systems on board the vehicle that coordinate with other vehicles and regulate acceleration and braking.

Vehicle Databus (Destination Physical Object): 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.