Application of smart traffic charge RFID readers in ETC systems
Industry News

Application of smart traffic charge RFID readers in ETC systems

PublishedShanghai Zejie Smart Technology Co., Ltd.

Smart transport charges require a combination of vehicle identification, trade authorization, lane status and billing results.

The ETC process cannot be simplified to RFID to get a cut on reading.

A valid identification also requires the recognition of vehicles, transactions and physical traffic.

Wireless identification is not an alternative to crash and drive-by security.

The ETC transaction involves vehicles, the fact of passage, the many steps between billing and payment, which cannot be simplified to make a certificate available. Repeated observation should be made on the same transaction, and irregular re-routing should avoid double-counting. Identity gathering is only a chain entry, not all evidence of the transaction.

The key to access is the state of authorization.

After a valid reading of the card, you will need to judge the authority, time, area and current status.

Access records should start and end.

The authorization to pass, open a channel, enter an object and end the passage should not be reduced to a single moment of success. Any interruption in any one step may render the presence, billing or permissions incorrect. The system needs to be clear about how timeout, cancellation and duplicate operations are handled and distinguish between re-testing communications and real secondary traffic. The normal process can be mapped and article by article checked for exit from each state when there is an anomaly. This is closer to the reliability of the complete access service than if the single reading card is located.

Re-examine the programme from an exception

When a transaction is requested repeatedly, the system should be identified as the same business and not as a re-deductible charge; but the vehicle is passed again, and it should become a new event. Communication is not the same thing as duplication of business, and it needs to be handled separately from the traffic identity, and cannot be assumed by just time.

Put your judgment in the real situation.

Tests of multiple triggers, time overruns and pass failures, checking the matching of fees, release and replenishment records.

The decision to open the door or lift the pole should be traced back to a record of clear authorization and, once the network has been restored, it will also deal with requests for re-routing and duplication of offline events.

From demonstration to delivery, what evidence is needed

Observation dimensions Evidence to be retained
Release correctness Samples that should be released and rejected should be counted.
Passive experience. The queue time and the number of rejections are observed simultaneously.
Exception recovery Offline strategy and manual processing documented
This is the key trade-off. If communications have been successful and passage is incomplete, how should the system deal with this transaction to be fair to users?

It's worth asking.

If communications have been successful and passage is incomplete, how should the system deal with this transaction to be fair to users?

Technical and factual references