Link Type: Contact or Proximity
Vehicle OBE --> Payment Device:
request for payment
Definitions
request for payment (Information Flow): Request to deduct cost of service from user's payment account.
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.
Payment Device (Destination Physical Object): The 'Payment Device' enables the electronic transfer of funds from the user of a service (I.e. a traveler) to the provider of the service. Potential implementations include smart cards that support payment for products and services, including transportation services and general purpose devices like smart phones that support a broad array of services, including electronic payment. In addition to user account information, the payment device may also hold and update associated user information such as personal profiles, preferences, and trip histories.
Included In
This Information Flow is in the following Applications:
- Advanced Traveler Information Systems
- Electronic Toll Collection
- Integrated Multi-Modal Electronic Payment
- Low Emissions Zone Management
- Road Use Charging
This Information Flow is in the following Application Objects:
Communication Diagrams
The communication diagram(s) can be viewed in SVG or PNG format and the current format is SVG. Switch to PNG format.
Characteristics
Architectural:
Characteristic | Value |
---|---|
Time Context | Now |
Spatial Context | Adjacent |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Source |
Security
This information flow triple is in the following applications with the following security levels.
Information Flow Security | |||||
---|---|---|---|---|---|
Application | Confidentiality | Integrity | Availability | ||
Basis | Basis | Basis | |||
Security levels have not been defined yet. |