The difference between NFC and RFID
Industry News

The difference between NFC and RFID

PublishedShanghai Zejie Smart Technology Co., Ltd.

NFC's relationship with RFID is appropriate to be understood in terms of “different scope”: RFID covers multiple types of wireless recognition achieved, and NFC's focus compatible devices interact closely.

NFC is not a technology that is completely parallel to RFID.

The ability to read NFC labels, read commonly used UHF storage tags and complete door-to-door operations is different.

NFC is in close contact and does not mean that content will not be copied; general UHF tags are read more distant and do not mean continuous positioning capability.

NFC is a specific interactive program in the technical system of RFID, and it should be limited to function. Read labels, inter-device interaction and card simulations are not the same. Cell phones have NFC, and do not mean that they can read any RFID tag or directly access all protected data.

Situations requiring early verification

For example, a cell phone can open a page with a NFC tag without reading the storage UHF tag, which is different from the hardware range and does not mean that one of the labels is broken. The compatibility test should answer "what mission to do," instead of "Does the phone react when it approaches?"

It's recommended that this be verified.

Validates the read, write and permission requirements with target mobile phones and actual labels, and checks user tips in different system versions.

It is proposed that Andre, iOS and field dedicated terminals be included in the compatibility test, with a double validation of metal backboards, shell and actual adhesion. Clear permission for rewriting content should be set and service addresses should expire in a maintenanceable way.

The advantage of close interaction is clear at the border.

NFC uses compatible terminals to interact with labels at close range, often for service access, reading information or authentication. Not all RFID tags are read on the phone, and mobile phone capabilities are affected by protocols, systems and application privileges; a label that opens web pages does not automatically have a copyproof capability.

The credibility of the service entrance does not equal the readability of labels.

The label is read by a mobile phone, indicating that part of the interactive link is in place; whether or not the user enters the correct service depends on content, address and back-office privileges. Open access is not appropriate to take on the sensitive operations directly, and business actions should be properly validated and verified.

From demonstration to delivery, what evidence is needed

Observation dimensions Evidence to be retained
Interoperating Validation of terminals and label types by live machine
Entry maintenance Invalid links and content updates to process
Visit to the border Separate open information from sensitive operations
This is the key trade-off. Does business require an intentional touch or a collection without a case-by-case approach?

It's worth asking.

Does business require an intentional touch or a collection without a case-by-case approach?

Technical and factual references