Light Vehicle OBE --> Payment Administration Center:
road use history
Definitions
road use history (Information Flow): A vehicle's road use history that records where the vehicle has traveled over time. Optionally includes vehicle speeds as well as distance traveled for some applications. Information is accurate enough to distinguish between adjacent roads, adjacent lanes, and identify direction of travel on the roads.
Light Vehicle OBE (Source Physical Object): The 'Light Vehicle OBE' includes traveler-oriented capabilities that apply to passenger cars, trucks, and motorcycles that are used for personal travel. The rules vary by jurisdiction, but generally light vehicles are restricted in their weight and the maximum number of passengers they can carry. In ARC-IT, the Light Vehicle OBE represents vehicles that are operated as personal vehicles that are not part of a vehicle fleet and are not used commercially; thus, the choice between the various vehicle subsystems should be based more on how the vehicle is used than how much the vehicle weighs. See also the 'Vehicle' subsystem that includes the general safety and information services that apply to all types of vehicles, including light vehicles.
Payment Administration Center (Destination 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.
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:
- vehicle_identity_for_central_payment_admin
- vehicle_road_use_history_data_for_central_payment_admin
- vehicle_speed_and_distance_for_central_payment_admin
This Triple has the following triple relationships:
None |
Communication Solutions
- US: SAE Other J2735 - Secure Wireless Internet (ITS) (9)
- (None-Data) - Secure Wireless Internet (EU) (32)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
Development needed |
Security
|
|
TransNet
|
|||
Access
|
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 | Historical |
Spatial Context | Local |
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 | High | Moderate | |
Basis | Contains vehicle identity, location and road use history. This is personal, tracking information that needs the highest levels of protection. | Used as the basis for charging, any changes will have a direct impact on fees imposed and revenue collected. | Inability to complete this flow will result in a failure of the road use charging system, which will require alternative mechanisms, or more likely delay payments. Payment delay is probably not a serious problem unless widespread and unable to be resolved. Could be LOW if alternative mechanisms for managing charges exist. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |