Payment Administration Center --> Light Vehicle OBE:
vehicle payment update

Definitions

vehicle payment update (Information Flow): Data written to vehicle equipment to support electronic toll collection or parking payment.

Payment Administration Center (Source Physical Object): The 'Payment Administration Center' provides general payment administration capabilities and supports the electronic transfer of funds from the customer to the transportation system operator or other service provider. Charges can be recorded for tolls, vehicle-mileage charging, congestion charging, or other goods and services. It supports traveler enrollment and collection of both pre-payment and post-payment transportation fees in coordination with the financial infrastructure supporting electronic payment transactions. The system may establish and administer escrow accounts depending on the clearinghouse scheme and the type of payments involved. It may post a transaction to the customer account, generate a bill (for post-payment accounts), debit an escrow account, or interface to a financial infrastructure to debit a customer designated account. It supports communications with the ITS Roadway Payment Equipment to support fee collection operations. As an alternative, a wide-area wireless interface can be used to communicate directly with vehicle equipment. It also sets and administers the pricing structures and may implement road pricing policies in coordination with the Traffic Management Center.

Light Vehicle OBE (Destination Physical Object): The 'Light Vehicle OBE' includes traveler-oriented capabilities that apply to passenger cars, trucks, and motorcycles that are used for personal travel. The rules vary by jurisdiction, but generally light vehicles are restricted in their weight and the maximum number of passengers they can carry. In ARC-IT, the Light Vehicle OBE represents vehicles that are operated as personal vehicles that are not part of a vehicle fleet and are not used commercially; thus, the choice between the various vehicle subsystems should be based more on how the vehicle is used than how much the vehicle weighs. See also the 'Vehicle' subsystem that includes the general safety and information services that apply to all types of vehicles, including light vehicles.

Included In

This Triple is in the following Service Packages:

• TM11: Road Use Charging

This triple is associated with the following Functional Objects:

• Light Vehicle Payment Service
• PAC Road Pricing Administration

This Triple is described by the following Functional View Data Flows:

• road_use_payment_debited
• road_use_vehicle_payment_data_clear
• road_use_vehicle_payment_data_update

This Triple has the following triple relationships:

Communication Solutions

• (None-Data) - Secure Wireless Internet (EU) (43)
• (None-Data) - Secure Wireless Internet (ITS) (43)
• (None-Data) - Apache Kafka over Wireless (44)
• (None-Data) - OMG DDS over Wireless (44)
• (None-Data) - OASIS MQTT over Wireless (50)
• (None-Data) - OASIS AMQP over Wireless (61)

Selected Solution

(None-Data) - OASIS AMQP over Wireless

Solution Description

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt Development needed	Facilities Development needed OASIS AMQP	Security IP Security Alternatives
	TransNet IP Alternatives Internet Transport Alternatives
	Access Wireless Internet Alternatives (NA)

Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.

Characteristics

Security