• 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

driver information Quintuple

Bidirectional?: False

driver information (A-Interconnect): This CVRIA application interconnect encapsulates all of the Layer 2 information flows between the 'Electric Charging Station Management' application object and the 'Driver' 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 'driver information'. This application interconnect is uni-directional since the underlying layer 2 information flows go from 'Electric Charging Station' to 'Driver'.

Electric Charging Station (Source Physical Object): The 'Electric Charging Station' provides access to electric vehicle supply equipment that is used to charge hybrid and all-electric vehicles. This includes public charging stations that support consumers, workplace charging stations, and fleet charging stations.

Electric Charging Station Management (Source Application Object): 'Electric Charging Station Management' manages vehicle charging. It communicates with the vehicle during charging and provides charge status information to the driver. A connection with Roadside Equipment provides the capability to integrate charging station coordination and communication into the broader Connected Vehicle Environment.

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