Reference Manual
Prox–DU & Prox–SU
www.gemalto.com
DOC118569D Public Use Page 89/145
dwFeature defines Extended APDU for the contactless interface.
Full Extended APDU command length is supported (7+65535+2 = 65544 bytes).
The Extended APDU command must be split into several PC_to_RDR_XfrBlock messages
according to the CCID specification (the PC_toRDR_XfrBlock message length is limited to
dwCCIDMessageLength).
For a Mifare cards the data must be a Short APDU command as defined in PC/SC
specification.
For ISO14443-4 cards the data are send “as it” using the T=CL protocol.
For other proprietary APDU commands, the data must be a Short APDU command.
Offset Field Size Value Description
0 bMessageType 1 6Fh PC_to_RDR_XfrBlock
1 bwLength 4 Size of the abData field
5 bSlot 1 00h Slot 0
6 bSeq 1 00-FFh Sequence number for the
command
7 bBWI 1 00-FFh Used to extend the CCIDs Block
Waiting Timeout for this current
transfer. The CCID will timeout the
block after “this number multiplied
by the block Waiting Time” has
expired
8 wLevelParameter 2 xxxxh Use changes depending of the
exchange level reported by the
class descriptor in dwFeature field
For the contactless interface:
Extended APDU level
Indicate if an APDU command
begins and ends with this
command
0000h :The APDU command
begins and ends with this
command
0001h :The APDU command
begins with this command and
continues in the next
PC_to_RDR_XfrBlock
0002h :This abData field continues
an APDU command and ends the
APDU command.
0003h :The abData field continues
an APDU command and another
block is to follow.
0010h :Empty abDatafield
continuation of response APDU is
expected in the next
RDR_to_PC_DataBlock
10 abData Byte
Array
4 to 502 Data block sent to the CCID.
For a T=CL card this data are send
“as it” using the T=CL protocol.
For a Mifare card: the data must be
a Short APDU command as
defined in PC/SC specification.
The command message length = 10 + Card command length.
To Next Page
Loading...
Need help?
General
