Atr For Contactless Smart Cards - Gemalto Prox-DU Reference Manual

ATR for contactless smart cards

The Answer To Request (ATR) returned by an ISO14443-A or ISO14443-B smart card is
compliant with the PC/SC V2.0 Part 3 Revision 2.01.09 specifications.
The ATR is as follows:
Byte
Value
Number
0 3Bh
1 8Nh
2 80h
3 01h
XX
XX
4 to 3+N
XX
4 + N UU
The contactless smart card exposes its ATS or information bytes not directly, but via a
specific ATR mapping. For those cards that provide such information, optionally with
Historical Bytes (or Application Information respectively), the mapping in the table above
applies.
•
The ATR returned by a DESFire smart card is:
3Bh 8Fh 80h 01h 80h 80h 65h B0h 07h 02h 02h 89h 83h 00h 90h 00h 00h 00h 00h
46h
With:
n = Fh (15 historical bytes)
www.gemalto.com
DOC118569A
Reference Manual
Prox–DU & Prox–SU
Designation
Initial
header
• Higher nibble 8 means no TA1, TB1, TC1
only TD1 is following.
• Lower nibble N is the number of historical
T0
bytes (HistByte 0 to HistByte N-1).
• Higher nibble 8 means no TA2, TB2, TC2
only TD2 is following.
TD1
• Lower nibble 0 means T = 0.
• Higher nibble 0 means no TA3, TB3, TC3,
TD3 following.
TD2
• Lower nibble 1 means T = 1.
Historical bytes:
• ISO14443A:
T1
The historical bytes from ATS response.
Refer to the ISO14443-4 specification
...
• ISO14443B:
Byte 1-4: Application Data from ATQB
..
Byte 5-7: Protocol Info Byte from ATQB
Byte 8: Higher nibble = MBLI from ATTRIB
Tk
command. Lower nibble (RFU) = 0
Refer to the ISO14443-3 specification
TCK Exclusive-OR of bytes T0 to Tk
Table 13 – ATR for contactless Smart cards
Release for first samples
Public Use
Preliminary
Description
Do not use for final design
Page 44/134