ITS Roadway Payment Equipment --> Light Vehicle OBE:
road use charges
Definitions
road use charges (Information Flow): Road use charges per link.
ITS Roadway Payment Equipment (Source 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).
Light Vehicle OBE (Destination 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.
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:
Relationship | Source | Destination | Flow |
---|---|---|---|
Interactive | Light Vehicle OBE | ITS Roadway Payment Equipment | road use history |
Depends On | Payment Administration Center | ITS Roadway Payment Equipment | road use charges |
Communication Solutions
- (None-Data) - Local Unicast Wireless (1609.2) (35)
- (None-Data) - Local Unicast Wireless (EU) (38)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
Addressed Elsewhere |
Facilities
Development needed |
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 | Recent |
Spatial Context | Adjacent |
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 | Intended for the end user, so does not generally need to be concealed based on its content. However, could reasonably include localized information which if intercepted implies location of the end user, which is personal and should be protected. | This material is used to support end user routing with an understanding of travel times and costs. Loss, corruption or forgery are likely to implact small numbers of users and have a moderate impact on revenues. | This material is used to support end user routing with an understanding of travel times and costs. Loss, corruption or forgery are likely to implact small numbers of users and have a moderate impact on revenues. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |