Roadway Payment (Subsystem*)

The Roadway Payment Subsystem (RPS) represents the roadway components of a toll collection, vehicle miles traveled (VMT), congestion charging, and other systems that support payment from a vehicle. As a toll collection system, this subsystem 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 road pricing policies. Each transaction is accompanied by feedback to the customer indicating the general status of the customer account. A record of the transactions is provided to the Payment Administration Subsystem for reconciliation and so that the customer can periodically receive a detailed record of the transactions.

The RPS can represent equipment at fixed locations or mobile equipment that supports spot inspection to verify the vehicle equipment is configured correctly and operational. Fixed roadway equipment supports relay of VMT data and equipment status to the Payment Administration Subsystem. RPS elements can be located at traditional toll collection locations (i.e. toll plazas) to support traditional roadway toll functions, as well as at gas stations or public or privately operated auto mechanic shops or vehicle inspection stations) for relaying VMT data.

Functionality
Inputs/Outputs
Security
Subsystem Interfaces Diagram
Terminator Interfaces Diagram

Subsystem Interfaces Diagram

This is a context diagram for the entity Roadway Payment Subsystem that shows the interfaces to subsystems and every architecture flow that this entity sends or receives, as defined in the National ITS Architecture. A complete list of all architecture flows shown on this diagram, is available under the Inputs/Outputs section on this page.

Get the Source Graphic, a Enhanced Windows Metafile (EMF), in ZIP format.

Terminator Interfaces Diagram

Get the Source Graphic, a Windows Metafile (WMF), in ZIP format.

Security Considerations:

The primary security consideration for the Roadway Payment Subsystem relates to the financial information collected in the field that is sent to the Payment Administration Subsystem, and to any personal information associated with the financial transactions. Electronic payment needs to have a relatively high degree of confidentiality in order to safeguard the information. Additional security sensitivity is for the personal information associated with electronic accounts. In addition, it is important that the information is available from the Roadway Payment Subsystem to the Payment Administration Subsystem in order to ensure that payments are properly accounted for. The integrity of the information is also important to consider in order to prevent disruption of fee collection operations.

Functionality: Equipment Packages* and PSpecs*

Roadway VMT Payment (Equipment Package*)
PSpecs:
- 7.6.1.1-Collect VMT Data
- 7.6.1.3-Bill Driver for VMT
- 7.6.2-Obtain VMT Vehicle Image
- 7.6.7-Collect VMT Equipment Status
Toll Plaza Toll Collection (Equipment Package*)
PSpecs:
- 7.1.1.1-Read Vehicle Payment Data for Tolls
- 7.1.1.10-Determine Advanced Toll Bill
- 7.1.1.2-Calculate Vehicle Toll
- 7.1.1.4-Check for Advanced Tolls Payment
- 7.1.1.5-Bill Driver for Tolls
- 7.1.2-Produce Roadside Displays
- 7.1.3-Obtain Toll Violator Image
- 7.1.5-Detect Vehicle for Tolls

Inputs/Outputs: Architecture Flows* and Data Flows*

Payment Administration Roadway Payment

toll advisories (Architecture Flow*) - Alerts and advisories provided to toll plazas to keep toll operators informed of identified threats that may impact toll operations or public safety on a toll facility.
Data Flows*:
- alert_notification_for_toll_operator
toll instructions (Architecture Flow*) - Information provided to configure and support toll plaza operations including toll pricing information.
Data Flows*:
vehicle payment request (Architecture Flow*) - Request for information supporting toll and parking payments.
Data Flows*:
- vmt_payment_request_to_field
- vmt_vehicle_payment_data_clear_to_field

Roadway Payment Driver

roadside transaction status (Architecture Flow*) - The status of an electronic payment transaction provided directly to the driver via sign or other roadside infrastructure.
Data Flows*:
- td-toll_payment_confirmed
- td-toll_payment_invalid

Roadway Payment Payment Administration

toll transactions (Architecture Flow*) - Detailed list of transactions from a toll station.
Data Flows*:
vehicle payment information (Architecture Flow*) - Information provided for payment of tolls and parking fees including identification that can be used to identify the payment account or source and related vehicle and service information that are used to determine the type and price of service requested.
Data Flows*:
- vmt_payment_collected_from_field
- vmt_payment_confirmation_from_field
VMT data (Architecture Flow*) - A vehicle’s road use history that records where the vehicle has traveled over time. Optionally includes vehicle speeds as well as distance traveled for some applications. Information is accurate enough to distinguish between adjacent roads, adjacent lanes, and identify direction of travel on the roads.
Data Flows*:
- vehicle_identity_for_vmt_from_roadway
- vehicle_location_for_vmt_from_roadway
VMT equipment fault (Architecture Flow*) - Provides fault status of the VMT data collection equipment in a vehicle and vehicle image and other characteristics to allow independent identification of the vehicle and its owner.
Data Flows*:

Roadway Payment Toll Operator

toll operator information presentation (Architecture Flow*) - Information presented to the toll collection point operator, including toll transaction information, alerts, and advisories.
Data Flows*:
- tto-alert_notification
- tto-transaction_reports

Roadway Payment Vehicle

vehicle payment request (Architecture Flow*) - Request for information supporting toll and parking payments.
Data Flows*:
vehicle payment update (Architecture Flow*) - Data written to vehicle equipment to support electronic toll collection or parking payment.
Data Flows*:

Toll Operator Roadway Payment

toll operator requests (Architecture Flow*) - User input from the toll operator to request information at the toll collection site.
Data Flows*:
- fto-local_toll_price_variations

Vehicle Roadway Payment

vehicle payment information (Architecture Flow*) - Information provided for payment of tolls and parking fees including identification that can be used to identify the payment account or source and related vehicle and service information that are used to determine the type and price of service requested.
Data Flows*:
VMT data (Architecture Flow*) - A vehicle’s road use history that records where the vehicle has traveled over time. Optionally includes vehicle speeds as well as distance traveled for some applications. Information is accurate enough to distinguish between adjacent roads, adjacent lanes, and identify direction of travel on the roads.
Data Flows*:
VMT equipment status (Architecture Flow*) - Provides an indication of the operational status of the VMT data collection equipment in a vehicle. Also indicates vehicle ID (VIN) so that the registration of the equipment to a specific vehicle can be verified and confirmed by comparison with vehicle characteristics.
Data Flows*:
- vmt_equipment_status

Vehicle Characteristics Roadway Payment

vehicle characteristics (Architecture Flow*) - The physical or visible characteristics of an individual vehicle that can be measured to classify a vehicle and imaged to uniquely identify a vehicle.
Data Flows*:
- From_Vehicle_Characteristics