Light Vehicle OBE --> ITS Roadway Payment Equipment:
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.
ITS Roadway Payment Equipment (Destination Physical Object): 'ITS Roadway Payment Equipment' represents the roadway components of a toll collection system. It provides the capability for vehicle operators to pay tolls without stopping their vehicles. It supports use of locally determined pricing structures and includes the capability to implement various variable pricing policies. Typically, transactions are accompanied by feedback to the customer and a record of the transactions is provided to a back office system (e.g., the Payment Administration 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_location_for_road_use_payment
- vehicle_road_use_history_data
- vehicle_speed_and_distance_for_road_use_payment
This Triple has the following triple relationships:
None |
Communication Solutions
- US: SAE Other J2735 - Local Unicast Wireless (1609.2) (20)
- (None-Data) - Local Unicast Wireless (EU) (54)
Selected Solution
Solution Description
ITS Application Entity
SAE J2735 |
Click gap icons for more info.
|
||
Mgmt
Addressed Elsewhere |
Facilities
SAE J2735 |
Security
|
|
TransNet
IEEE 1609.3 |
|||
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 | Regional |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Destination |
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 |