Connected Devices & IoT
Smart Parking Terminal: Plate, RFID and Payment Architecture
Software design that combines camera, license plate recognition, RFID, barrier and payment services in an offline-resistant entry-exit terminal.
Short answer
Single transaction chain from entry to payment
The smart parking terminal recognizes the vehicle by license plate or RFID, checks the subscription and permit rules, opens the barrier and calculates the time and fee at the exit. Scenarios such as visitor, subscriber, lost ticket, and payment failure should be handled in the same state machine. The prototype can be demonstrated end-to-end with camera feed and barrier relay simulator.
Edge terminal and service architecture
The local terminal consists of Camera Adapter, Plate Recognition, Access Rules, Barrier Controller and Payment Adapter components. On the cloud side, Facility, Lane, Vehicle, Subscription, ParkingSession, Tariff and Payment entities are kept. The login event is recorded with photo evidence, license plate trust score and device ID. The barrier receives a controlled pulse command only when valid process and safety sensor conditions are met.
Offline work and incident reconciliation
In case of internet outage, local subscription cache and facility policy come into play. Input-output events are stored with an immutable sequence number; When the connection arrives, it is reconciled with the center. Situations such as open occupancy of the same vehicle, duplicate license plate readings and simultaneous crossing of two lanes are resolved with clear rules. Unique transaction ID in fee and payment transactions prevents double collection.
Camera, RFID and personal data security
The license plate image should cover only the required field of view, retention period and access roles should be defined. If possible, the RFID ID is processed as a secure token instead of a raw card number. Search, correction and manual barrier opening operations in the management panel create an audit record. Payment card data is not stored in the terminal application; certified provider and tokenized stream are used.
Demo software presentation
The demo can be prepared with two virtual lanes, camera view, RFID reader and barrier mock-up. Subscriber vehicle enters automatically; the visitor sees the fee at the exit and makes a test payment. Low-security license plate reading falls to operator inspection. When the network goes down, authorized subscribers go through the local list, then the events are synchronized on the panel. It is also shown who performed the manual opening process.
Pilot metrics and field tests
Pilot success metrics are correct license plate reading, processing time, incorrect barrier opening, payment completion and offline synchronization rate. Night, rain, dirty plate, tail, reversing, tail tracking and sensor failure scenarios are tested. Barrier safety and field electronics must be verified with relevant manufacturer standards.
Frequently asked questions
Should license plate recognition work in the cloud or on an edge device?
The edge approach is powerful for low latency and offline operation; Centralized model management and reporting can be maintained in the cloud.
Should parking stop when the internet goes out?
No. Controlled local handover should continue according to facility policy and events should be reconciled upon connection return.