How MIFARE Uses Cookies

[Liang]

Thank you very much, TapLinx Team:

Yes, we want to handle one tag at a time, but because there could be at least two tags in fixed position within very closed range (none of them will be moved away), could we use TapLinx SDK to get the first tag, handling it, and then get second tag, handling it, and then third tag...?
If we use TapLinx anti-collision API several times, and every time the API give us a different tag, we think it is possible to do so.
(Correct us, if we are wrong.)

If using high level TapLinx SDK could not achieve what we want, could the NFC Reader Library described in "NFC Activating multiple Tags using NFC Reader Library" article can be used with Android Phone to achieve what we want? If this Library can work well with Android Phone, we could invest resources to work on this.

The ISO14443A anti-collision method is Bit Collision, we think if the reader send the same bit pattern to search for the tag every time, the tag responses first at the first time will also response first at the next time, in this situation, other tags in the field will never be selected.
But the article ""NFC Activating multiple Tags using NFC Reader Library" tell us another story, it seems that the reader (or the application) after successfully get a tag's information (UID and type?), it will not stop and return, it can go on find another tags in the field, finally reader get all the tags' information in the field, reader (application) can decide which tag it wants to process.

We wonder if the only solution is to use NFC Reader Library?

We appreciate any help we can get. Thank you!

---

+ 0  |  - 0

[Liang]

Thanks for reply.

Can you suggest an irreversible way?

We have studied a lot, but didn't find a way to prevent to take out the chip (NTAG 213, NTAG 213TT) from the tag.

NTAG 213TT or NTAG 413 DNA will lose the function of "Brand Protection " due to take out the chip from tag is easy.

You said: "An unpowered device cannot detect changes on an interface pin. This is physically not possible."

Because the Physical properties of the passive tag, the hacker can destroy the tamper wire or antenna and re-wired it, before any reader or cellphone reading the tag, the hacker can then attach the modified tag to fake product and sell it, our background server will treat this tag as genuine tag from us.

Could you give us some suggestion to avoid this situation?

Thank you very much.

---

+ 0  |  - 0

[Author]

Posts