Transportation Information Center --> Financial Center:
payment request
Definitions
payment request (Information Flow): Request for payment from financial institution or related financial service requests (e.g., balance inquiry)
Transportation Information Center (Source Physical Object): The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.
Financial Center (Destination Physical Object): The 'Financial Center' represents the organization that handles electronic fund transfer requests to enable the transfer of funds from the user of the service to the provider of the service. The functions and activities of financial clearinghouses are covered by this physical object.
Included In
This Triple is in the following Service Packages:
- CVO09: Freight-Specific Dynamic Travel Planning
- TI06: Shared Use Mobility and Dynamic Ridesharing
- TI09: Travel Services Information and Reservation
This triple is associated with the following Functional Objects:
- TIC Dynamic Ridesharing
- TIC Interactive Traveler Information
- TIC Travel Services Information and Reservation
This Triple is described by the following Functional View Data Flows:
- tfc- traveler_shared_use_payment_information
- tfc-driver_display_payment_request
- tfc-driver_map_payment_request
- tfc-registration_payment_request
- tfc-traveler_display_payment_request
- tfc-traveler_map_payment_request
- tfc-traveler_other_services_payments_request
- tfc-traveler_rideshare_payment_request
This Triple has the following triple relationships:
| Relationship | Source | Destination | Flow |
|---|---|---|---|
| Request-Response | Financial Center | Transportation Information Center | settlement |
| Depends On | Light Vehicle OBE | Transportation Information Center | trip confirmation |
| Depends On | Personal Information Device | Transportation Information Center | trip confirmation |
| Depends On | Traveler Support Equipment | Transportation Information Center | trip confirmation |
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 | Moderate | Moderate | Moderate | |
| Basis | Contains account and related information that is personal and if compromised could financially impact the owner of the account. | Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. | Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | True |