Historical development of RFID
RFID Knowledge

Historical development of RFID

PublishedShanghai Zejie Smart Technology Co., Ltd.

It is not appropriate for RFID to develop into a straight-line story that suddenly emerges in a given year and will inevitably become widespread. Wireless recognition is industrialized, relying on chips, antennas, protocols, codes and business systems to mature together.

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 history of technology should be based on how capacity changes in conjunction with cost.

Early identification needs are not the same as today’s task of tracking individual products. Standardization makes it easier for different participants to share identities and events, while manufacturing and integration costs determine which particles are worth tracing.

If you only talk about reading distance and price of labels down, the main data and liability issues that persist in implementation are ignored. Hardware advances do not automatically bring process synergies.

Technological history is not a single-line advance in which new technologies are necessary to replace old ones. Old solutions can be applied for long periods of time because of low cost and mature processes.

Put this in a specific process.

Looking back at a technological history, you can divide changes into the capacity of the device, interoperability and organizational use. Read more easily at some stage, but not as cross-business data. Using this stratification perspective, you can explain why hardware has matured over many years, and certain projects still fail repeatedly in process synergy.

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.

Let's look at the input and the results.

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. Will the next stage of progress come from wireless performance more or will it be possible to interpret the same data from different organizations?

It's recommended that this be verified.

To comb through the criteria that an existing system relies on from code to collection and then on data exchange, analyse whether replacement of a component requires a full re-engineering.

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.

Will the next stage of progress come from wireless performance more or will it be possible to interpret the same data from different organizations?

Technical and factual references