The unique identifier of the target varies between different communication technologies. This appendix defines the rules that the API implementation must follow when constructing the UID for discovered target.
For those NDEF_TAG target types that support Canonical
Target ID String Presentation (CID) defined in the NFC Forum, that identifier
must be used. The targets that do not support
CID the return value must be according to the
following table.
Table C.1. UID generation rules
| Communication protocol | UID generation rule |
|---|---|
| ISO14443-3/4 type A card or tag (e.g. Mifare UltraLight or Mifare DesFire) | 4,7 or 10 UID bytes from the cascade anti-collision procedure |
| ISO14443-3/4 type B card or tag | 4 PUPI bytes (random) from the initialization procedure |
| NFCIP-1 212,424 kbits (e.g. FeliCa card) | 8 NFCID2 bytes (2 fixed + 6 random) from the initialization procedure |
| ISO144443-3 type A tag (e.g. Jewel tag) | 4 UID bytes (UID0 to UID3) from RID command |