Parking Area Equipment --> Light Vehicle OBE:
vehicle payment update
Definitions
vehicle payment update (Information Flow): Data written to vehicle equipment to support electronic toll collection or parking payment.
Parking Area Equipment (Source Physical Object): 'Parking Area Equipment' provides electronic monitoring and management of parking facilities. It supports an I2V link to the Vehicle that allows electronic collection of parking fees and monitors and controls parking meters that support conventional parking fee collection. It also includes the instrumentation, signs, and other infrastructure that monitors parking lot usage and provides local information about parking availability and other general parking information. The two primary approaches to monitoring parking area usage are sensing vehicles within parking spots or counting vehicles as they come in and as they leave the area. This portion of the functionality must be located in the parking area where it can monitor, classify, and share information with customers and their vehicles. See also the separate 'Parking Management Center' physical object that may be located in a back office, remote from the parking area, which interfaces with the financial infrastructure and broadly disseminates parking information to other operational centers in the region.
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:
- Light Vehicle Basic Toll/Parking Payment
- Light Vehicle Payment Service
- Parking Area Electronic Payment
This Triple is described by the following Functional View Data Flows:
- parking_lot_payment_debited
- parking_lot_vehicle_payment_data_clear
- parking_lot_vehicle_payment_data_update
This Triple has the following triple relationships:
None |
Communication Solutions
- US: WAVE Tolling - Local Unicast Wireless (1609.2) (13)
- (None-Data) - Local Unicast Wireless (EU) (38)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
ETSI 302 890-1 Addressed Elsewhere |
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 | 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 | Contains payment status update information intended for an individual, and thus should be concealed as it is personal information with no legitimate use by an unintended recipient. | Payment information should be correct and timely or the recipient may take action to correct, or may fail to take action he should take and be penalized. | Payment information should be correct and timely or the recipient may take action to correct, or may fail to take action he should take and be penalized. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |