ISO/IEC 14443 Type A

Also known as NFCA.

Based on ISO14443 standards.

Near Field Communication devices implement native support for ISO14443-A tags. The NFC Forum refers to these tags as Type 1, Type 2 and Type 4 tags. FIXME integrate this The Anti-Collision example describes the initialization messages used to set up a communication channel and to retrieve the identifier and supported features from a tag. During the anti-collision phase, three or four different frames are received from a tag (ATQA, UID, SAK and optional ATS).

The ATQA, SAK and ATS values can be used to identify the manufacturer, tag type and application. However, it’s not recommended to rely on ATQA due to potential collision when more than one target are in the field.

A recommended document to identify MIFARE tags: MIFARE Type Identification Procedure.

The following table shows a list of known tags and their anti-collision values (hexadecimal). Please contact us to help update and expand this list.

Manufacturer Product ATQA SAK ATS (called ATR for contact smartcards) UID length
NXP MIFARE Mini 00 04 09   4 bytes
NXP MIFARE Classic 1k 00 04 08   4 bytes
NXP MIFARE Classic 4k 00 02 18   4 bytes
NXP MIFARE Ultralight 00 44 00   7 bytes
NXP MIFARE DESFire 03 44 20 75 77 81 02 80 7 bytes
NXP MIFARE DESFire EV1 03 44 20 75 77 81 02 80 7 bytes
IBM JCOP31 03 04 28 38 77 b1 4a 43 4f 50 33 31 4 bytes
IBM JCOP31 v2.4.1 00 48 20 78 77 b1 02 4a 43 4f 50 76 32 34 31 7 bytes
IBM JCOP41 v2.2 00 48 20 38 33 b1 4a 43 4f 50 34 31 56 32 32 7 bytes
IBM JCOP41 v2.3.1 00 04 28 38 33 b1 4a 43 4f 50 34 31 56 32 33 31 4 bytes
Infineon MIFARE Classic 1k 00 04 88   4 bytes
Gemplus MPCOS 00 02 98    
Innovision R&T Jewel 0C 00      
Nokia MIFARE Classic 4k - emulated (6212 Classic) 00 02 38   4 bytes
Nokia MIFARE Classic 4k - emulated (6131 NFC) 00 08 38   4 bytes

MIFARE

FIXME: We used to link to a landing MIFARE page.

ISO 14443A-4

Protocol for smartcards is referred as T=CL and is basically the same as for T=1 (for contact smartcards).