RFID product application next to
Industry News

RFID product application next to

PublishedShanghai Zejie Smart Technology Co., Ltd.

Doors, traffic vouchers and commodity labels all appear to be “unidentified”, but their protocols, authorizations and data use may differ completely.

Identity, gathering events and operational facts to be separated

The RFID link involves at least labels, readers, antennas and operating systems. The tag returns the logo for the search of objects, which results in a wireless observation, which is then interpreted by the business software according to location, time and documentation.

The RFIID around us is often mistaken for the same card.

Also close to a card reader, one system may read only the number and another may perform certificate authentication and transactions.

A cell phone cannot be presumed to read all cards because it can read a certain type of label; nor can a device be considered to be legally able to duplicate the corresponding business because it can display a number.

A similar card may be agreed to differently or only valid for a specific terminal. Users should be informed about its use, loss and alternative process; buyers should be given the same compatibility into their specific operation. Only confirmation of the same frequency does not guarantee consistency in actual use.

Why isn't one success enough?

The same brushing action can trigger a query, authentication or transaction, but the user may not be able to distinguish. Service providers should use feedback and instructions to make it understandable. Hide all processes as "drops" -- although simple operations may make it more difficult to detect errors in deductions or authorization failures in time.

Why the number of times read does not represent the quality of information

One label stays in the reading area, which can generate many repetitions of observations; the other is always blocked and may not have any record. The original number increases, without representing a more complete object cover. The software needs to combine observations with mission-generated events and distinguish between non-observed objects that are not observed. If the binding relationship is wrong, even if wireless communication is fully normal, it stabilizes the wrong output. The quality of the system should therefore at least take into account the three layers of the chain, identity and event, so that one layer cannot be endorsed by another.

How many bases do you have to decide what's worth?

Observation dimensions Evidence to be retained
Object Identity Is the coding tied to the object?
Collection of evidence Keep reading points, times and original results
Closed business circle Whether anomalies can be reviewed, corrected and traced
This is the key trade-off. We used to say "brush it," but behind that, who was going to verify who?

It's recommended that this be verified.

Select the types of documents actually used, check their public agreements, equipment compatibility and back-office privileges, and draw up a separate operating chain of trust.

It is recommended to write how the object identifiers are allocated, who binds and how the labels are used to continue history, and then design a collection point.

It's worth asking.

We used to say "brush it," but behind that, who was going to verify who?

Technical and factual references