User's Manual

SCL010/01X REFERENCE MANUAL 22
5.3.3. PC/SC 2.0 compliant ATR
When a user token is placed on the reader, initialization and anti-collision is performed. The user
token is automatically activated and an ATR is built as defined in the PC/SC specification. For
NFC Forum tag types 1 and 3, there is no definition in PC/SC.
5.3.3.1. Determining the technology of the user credential
The ScardControl method of PC/SC should be used to send the 0x900 IOCTL to SCL010/01X in
order to determine what type of technology is the user token based on
(see http://msdn.microsoft.com/enus/ Library/aa379474(VS.85).aspx
. The output buffer is a BYTE
with the following meaning:
Tec
Technology Value
MIFARE1K
0x01
MIFARE4K
0x02
MIFARE Ultralight 0x03
ISO14443-4 or
Mifare DESFire
0x04
FeliCa
0x05
Jewel or Topaz
0x06
ISO14443-4B
0x07
Value
Once a user credential is selected the driver constructs an ATR from the fixed elements that identify the
token.
Depending on the user technology this ATR can be analyzed as described below.
5.3.3.2. ATR for contactless storage user tokens
The ATR of the user token is composed as described in the table below. In order to allow the
application to identify the storage card properly, it’s Standard and Card name describing bytes
must be interpreted according to the Part 3 Supplemental Document, maintained by PC/SC.
Tokens using technology like MIFARE are examples of such user tokens.
Byte# Value Designation Description
0 0x3B Initial header
1 0x8n T0 n indicates the number of historical bytes in
following ATR
2 0x80 TD1 Nibble 8 indicates no TA2, TB2, TC2
Nibble 0 means T=0
3 0x01 TD2 Nibble 8 indicates no TA3, TB3, TC3
Nibble 1 means T=1
0x80 A status indicator may be present in an
optional TLV data object
0x4F Tag: Application identifier
Lentgh 1 byte
RID Registered identifier on 5 bytes
4...3+n
PIX
Optional TLV
data object
Proprietary identifier extension on 3 bytes