7.2.5: Provide Payment Device Interface for Parking

This process shall be responsible for providing the interface through which the payment information can be read from a vehicle payment device. The process shall enable the use of the data for the purposes of paying the current parking lot charge and if required, advanced payments for tolls and/or transit fares. It shall be possible for the process to collect either the credit identity or the stored credit value data and to update the stored credit value as a result of the parking lot charge and (possibly) advanced charges having been paid. The time at which the vehicle entered the parking lot shall also be collected from the vehicle payment device by the process so that the charge for the use of the lot can be calculated. The process shall support collection of data from on-board a range of vehicle types including private cars or vans, commercial vehicles, transit vehicles, including those used for demand responsive transit services. This process shall manage a store of parking lot vehicle payment data.

This process is associated with the Light Vehicle OBE physical object.

This process is associated with the following functional objects:

• Light Vehicle Interactive Traveler Information
• Light Vehicle Payment Service

This process is associated with the following data flows:

• fpd-confirm_payment_at_parking_lot
• tpd-debited_payment_at_parking_lot
• tpd-request_payment_at_parking_lot
• fpd-parking_vehicle_payment_data
• parking_vehicle_payment_number
• driver_advanced_payment_at_lot
• driver_parking_payment_credit_identity
• parking_lot_vehicle_payment_data_clear
• parking_lot_vehicle_payment_data_collect
• parking_lot_vehicle_payment_data_update
• parking_lot_payment_confirmation
• parking_lot_payment_debited
• parking_lot_payment_request
• secure_id_for_parking
• fpd-secure_id_for_parking