Payment Administration Center --> Other Payment Administration Centers:
toll coordination
This triple is bi-directional. See also
Other Payment Administration Centers --> Payment Administration Center: toll coordination
Definitions
toll coordination (Information Flow): This flow supports reciprocity between toll agencies/service centers by exchanging information that supports reconciliation of toll charges by customers that are enrolled with other toll service centers. 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 centers.
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.
Other Payment Administration Centers (Destination Physical Object): Representing another Payment Administration Center, 'Other Payment Administration Centers' is intended to provide a source and destination for ITS information flows between payment administration functions. This interface allows reconciliation of toll charges and other payments across different agencies by allowing the exchange of information about clients who have incurred charges in jurisdictions other than their own (billing) customer service center. This interface enables apportioning charges and 'reciprocity' between participating customer service centers.
Included In
This Triple is in the following Service Packages:
This triple is associated with the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
Relationship | Source | Destination | Flow |
---|---|---|---|
Request-Response | Other Payment Administration Centers | Payment Administration Center | toll coordination |
Communication Solutions
No communications solutions identified.Characteristics
Characteristic | Value |
---|---|
Time Context | Recent |
Spatial Context | Regional |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Destination |
Authenticable | True |
Encrypt | True |
Interoperability | Description |
---|---|
Regional | Interoperability throughout the geopolitical region is highly desirable, but if implemented differently in different transportation management jurisdictions, significant benefits will still accrue in each jurisdiction. Regardless, this Information Flow Triple should be implemented consistently within a transportation jurisdiction (i.e., the scope of a regional architecture). |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Moderate | Moderate | Moderate | |
Basis | Will include payment information, at least account IDs and road use instances if not times and actual charges. If observed, could be used to track individuals or compromise payment mechanisms. | If modified or corrupted could lead to incorrect charges, either to the wrong account, no account or differing amounts. Left at MODERATE because the impact should be limited to individual or at least a small number of accounts. | Availability will depend on the number of cross-use interactions and the scheme for sharing charges. Generally consider this to be an operational near-real time flow, so MODERATE. If strictly batched then LOW may be more appopriate. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |