Payment Administration Center --> DMV:
license request
Definitions
license request (Information Flow): Request supporting registration data based on license plate read during violation or at the scene of an incident.
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.
DMV (Destination Physical Object): The 'DMV' is a specific (state) public organization responsible for registering vehicles, e.g., the Department of Motor Vehicles.
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:
- tdmv-road_use_payment_identity_code
- tdmv-road_use_payment_vehicle_license
- tdmv-toll_violation_identity_code
- tdmv-toll_violation_vehicle_license
This Triple has the following triple relationships:
| Relationship | Source | Destination | Flow |
|---|---|---|---|
| Request-Response | DMV | Payment Administration Center | registration |
Communication Solutions
No communications solutions identified.Characteristics
| Characteristic | Value |
|---|---|
| Time Context | Recent |
| Spatial Context | Regional |
| Acknowledgement | True |
| Cardinality | Unicast |
| Initiator | Source |
| Authenticable | True |
| Encrypt | True |
| Interoperability | Description |
|---|---|
| National | This triple should be implemented consistently within the geopolitical region through which movement is essentially free (e.g., the United States, the European Union). |
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | High | Moderate | Low | |
| Basis | Contains PII and an indication that the person(s) identified in this flow has violated a toll. Release of this information would compromise the personal privacy of those involved. | Inaccurate or corrupted information in this flow could lead to a mistaken understanding of the toll violator's identity. | Real-time response may be required to deal with tolling and similar violations. The number of people affected is probably quite small, but if the load becomes great the availability may need to be raised to MODERATE. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | True |