Transport Canada
www.tc.gc.ca
Home > Transport Canada > Innovation > Intelligent Transportation Systems > Architecture
> ITS Architecture for Canada Version 2.0
> Physical Architecture
> Entities
>Toll Administration
Innovation
Browse Resources
Innovation Contact Information
Browse By Mode
Browse By Subject
About Us
The Toll Administration Subsystem provides general payment administration capabilities and supports the electronic transfer of authenticated funds from the customer to the transportation system operator. This subsystem supports traveller enrollment and collection of both pre-payment and post-payment transportation fees in coordination with the existing, and evolving 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. This subsystem posts a transaction to the customer account and generates a bill (for post-payment accounts), debits an escrow account, or interfaces to the financial infrastructure to debit a customer designated account. It supports communications with the Toll Collection Subsystem to support fee collection operations. The subsystem also sets and administers the pricing structures and includes the capability to implement road pricing policies in coordination with the Traffic Management Subsystem. The electronic financial transactions in which this subsystem is an intermediary between the customer and the financial infrastructure shall be cryptographically protected and authenticated to preserve privacy and ensure authenticity and auditability.
Security Considerations
The primary security consideration for the Toll Administration Subsystem is related to the financial information collected from the field and exchanged between other agencies using common electronic payment media that 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 to the Toll Administration subsystem in order to ensure that tolls are properly accounted for. The integrity of the information is also important to consider in order to prevent disruption of toll fee collection operations.
Functionality: Equipment Packages and PSpecs
Inputs/Outputs: Architecture Flows and Data Flows
- archive requests - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows:
- archive status - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows:
- registration - Registered owner of vehicle and associated vehicle information.
Data Flows:
- alert notification - Notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public. The flow identifies the alert originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, and information and instructions necessary for the public to respond to the alert. This flow may also identify specific information that should not be released to the public.
Data Flows:
- toll service change request - Request to change pricing, modify restrictions, or modify operations of a toll road facility
Data Flows:
- transaction status - Response to transaction request. Normally dealing with a request for payment.
Data Flows:
- toll data request - Request made to obtain toll schedule information or pay a toll in advance. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information.
Data Flows:
- toll data request - Request made to obtain toll schedule information or pay a toll in advance. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information.
Data Flows:
- toll coordination - This flow supports reciprocity between toll agencies/service centres by exchanging information that supports reconciliation of toll charges by customers that are enrolled with other toll service centres. In addition to toll charge reconciliation, exchanged information may include toll schedule information, customer information and other toll service information that is coordinated between toll agencies or centres.
Data Flows:
- toll archive data - Data indicating toll facility usage and pricing schedules. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows:
- license request - Request supporting registration data based on license plate read during violation.
Data Flows:
- alert status - Information indicating the current status of the emergency alert including identification of the traveller and driver information systems that are being used to provide the alert.
Data Flows:
- toll service change response - Response to toll service change requests indicating level of compliance with request.
Data Flows:
- payment request - Request for payment from financial institution.
Data Flows:
- toll data - Current toll schedules for different types of vehicles as well as advanced toll payment information.
Data Flows:
- toll data - Current toll schedules for different types of vehicles as well as advanced toll payment information.
Data Flows:
- toll probe data - Aggregate probe data derived from electronic toll collection operations. Data collected could include vehicle speeds and travel times for a given link or collection of links.
Data Flows:
- toll coordination - This flow supports reciprocity between toll agencies/service centres by exchanging information that supports reconciliation of toll charges by customers that are enrolled with other toll service centres. In addition to toll charge reconciliation, exchanged information may include toll schedule information, customer information and other toll service information that is coordinated between toll agencies or centres.
Data Flows:
- toll information presentation - Presentation of information to toll centre personnel including toll revenues, toll-related reports, operational status information, and alert information.
Data Flows:
- toll advisories - 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:
- toll instructions - Information provided to configure and support toll plaza operations including toll pricing information.
Data Flows:
- toll probe data - Aggregate probe data derived from electronic toll collection operations. Data collected could include vehicle speeds and travel times for a given link or collection of links.
Data Flows:
- toll service change response - Response to toll service change requests indicating level of compliance with request.
Data Flows:
- toll administration requests - Personnel inputs that control system operations, including requests to change toll fees, confirmation that alerts should be provided to toll operators, etc.
Data Flows: