• 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

payment transaction status Quintuple

Bidirectional?: False

payment transaction status (A-Interconnect): This CVRIA application interconnect encapsulates all of the Layer 2 information flows between the 'Roadway Payment Support' 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 'payment transaction status'. This application interconnect is uni-directional since the underlying layer 2 information flows go from 'ITS Roadway Payment Equipment' to 'Driver'.

ITS Roadway Payment Equipment (Source Physical Object): 'ITS Roadway Payment Equipment' represents the roadway components of a toll collection system. It provides the capability for vehicle operators to pay tolls without stopping their vehicles. It supports use of locally determined pricing structures and includes the capability to implement various variable pricing policies. Typically, transactions are accompanied by feedback to the customer and a record of the transactions is provided to a back office system (e.g., the Payment Administration Center).

Roadway Payment Support (Source Application Object): "Roadway Payment Support" represents the equipment that works in conjunction with the RSE to detect vehicles and identify and process violators when the RSE is used to support electronic payment. Various fee structures and payment strategies are supported including strategies that support reimbursements or credits that incentivize desired driving behavior.

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.