Payment Administration Center --> Electric Charging Management Center:
payment methods
Definitions
payment methods (Information Flow): A list of valid payment methods.
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.
Electric Charging Management Center (Destination Physical Object): The 'Electric Charging Management Center' provides management services for one or more electric vehicle charging stations used to charge hybrid and all-electric vehicles. This includes public charging stations that support consumers, workplace charging stations, and fleet charging stations using plug in (level 1, 2, fast charge, etc.), or inductive charging methods. The center interfaces with traveler information providers to support payment of charging and to disseminate information about the availability and status of their chargers and to coordinate reservations by drivers for the use of a charger. The center also interfaces with the appropriate electric utility that supplies electricity for its chargers to coordinate demand on the power grid.
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:
None |
Communication Solutions
- (None-Data) - Secure Internet (ITS) (43)
- (None-Data) - Apache Kafka (44)
- (None-Data) - OMG DDS (44)
- (None-Data) - OASIS MQTT (50)
- (None-Data) - OASIS AMQP (61)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
OMG DDS |
Facilities
Development needed OMG DDS OMG DDS-RPC OMG DDSI-RTPS |
Security
OMG DDS-Security |
|
TransNet
|
|||
Access
Internet Subnet Alternatives |
Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.
Characteristics
Characteristic | Value |
---|---|
Time Context | Recent |
Spatial Context | National |
Acknowledgement | False |
Cardinality | Unicast |
Initiator | Source |
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 | Low | |
Basis | Payment methods should be widely disseminated and contain no information that could cause harm if exposed. | Payment methods need to be correct so payment information can be exchanged. Could be LOW, as this should have redundancies and be able to tolerate significant latency. | Payment methods need to be correct so payment information can be exchanged. Could be LOW, as this should have redundancies and be able to tolerate significant latency. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |