Identive CLOUD 47x0 F, Справочное руководство

Страница: 29 / 98

CLOUD 47
X
0 F R
EFERENCE
M
ANUAL
29
6. Commands description
6.1. Generic APDU
6.1.1. Working with DESFire and MIFARE Plus tokens
To work with DESFire EV1 and MIFARE Plus tokens, please refer to the according application
notes [AN337] and [AN338], respectively.
Please note that, since these application notes contain information available only under NDA
with NXP, you’d need to sign an NDA with NXP to be allowed to receive them.
6.1.2. PAPDU_GET_UID
GET UID will retrieve the UID or SNR or PUPI of the user token. This command can be used
for all supported technologies.
Command APDU
:
CLA INS P1 P2 Lc Data in Le
0xFF 0xCA 0x00 0x00 - - XX
Setting Le = 0x00 can be used to request the full UID or PUPI is sent back.(e.g. for ISO14443A
single 4 bytes, double 7 bytes, triple 10 bytes, for ISO14443B 4 bytes PUPI).
Response APDU:
Data Status Word
Requested bytes of UID SW1, SW2
6.1.3. PAPDU_ESCAPE_CMD
Usually escape commands are transmitted through SCardControl as defined in PCSC API
using IOCTL_CCID_ESCAPE. But on some environments, the driver will block this IOCTL
unless the registry has been edited to allow it. Hence this vendor specific APDU was defined to
transmit Escape commands to the reader as below
Command APDU
:
CLA INS P1 P2 Lc Data in Le
0xFF 0xCC 0x00 0x00 Length
of data Escape
Command
Buffer XX
Response APDU:
Data Status Word
Reader Response SW1, SW2