Light Vehicle OBE --> Parking Area Equipment:
vehicle payment information

Definitions

vehicle payment information (Information Flow): Information provided for payment of tolls, parking, and other transportation fees including identification that can be used to identify the payment account or source and related vehicle and service information that are used to determine the type and price of service requested. This flow supports one-time payments that may not be associated with a service account. See also 'actuate secure payment'. The information exchange normally supports an account debit to pay fees, but an account credit may be initiated where pricing strategies include incentives.

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.

Parking Area Equipment (Destination 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.

Included In

This Triple is in the following Service Packages:

• PM03: Parking Electronic Payment

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_confirmation
• parking_lot_vehicle_payment_data_collect
• parking_lot_vehicle_payment_data_collected

This Triple has the following triple relationships:

Communication Solutions

• US: WAVE Tolling - Local Unicast Wireless (1609.2) (13)
• (None-Data) - Local Unicast Wireless (EU) (38)

Selected Solution

US: WAVE Tolling - Local Unicast Wireless (1609.2)

Solution Description

ITS Application Entity ISO 14906			Click gap icons for more info.
Mgmt Addressed Elsewhere	Facilities IEEE 1609.11 ISO 15628	Security Bundle: IEEE 1609.2
	TransNet IEEE 1609.3
	Access Bundle: Local Unicast Wireless SubNet (US)

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

Security