There are two possible implementations for control transfers, version A and version B. The least significant bit reports: These requests provide the same services to the application layer as bulk transfers. USB electrical interface and operating procedures 1. The parameters of the class specific request shall be set as follows: P1, P2 INS parameter of a command header. It may return less.

Uploader: Kazizil
Date Added: 1 September 2015
File Size: 54.7 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 88260
Price: Free* [*Free Regsitration Required]

This section defines the class specific requests for control transfers.

The second condition ensures that the interrupt message “virtually not present” is an asynchronous event caused by the USB-ICC. Its size is 0, 1, 2, or 3 bytes.

The driver in combination with the operating system shall provide means to recognize properly card removal. It may return less. Size of expected data to be returned by the bulk-IN endpoint.

It may have the values in Table 6. The following two tables give the values for the status and the error codes. The term “virtual” is used to express that the USB-ICC may be envisaged as removed from the interface device although it is still powered.

Used interchangeably with ICCD. For the correct transmission of data, the following general rules shall apply to the state diagram: This address is an endpoint number between 1 and The value for bReserved is given in the tables. Not relevant, fixed for legacy reason 6 bSeq 1 FFh Sequence number for icd.


For example, a bit integer stored iccf little endian format places the least significant byte at the lower address and the most significant byte at the next address.

BIFIT BIFIT ICCD Smart Card Reader how to download and install the driver

For the parameters, the following general rules shall apply: The maximum number of bytes present in this body. The maximum number of bytes expected in the data field of the response APDU. The following clauses give the values and the parameters for each of the class specific requests and describe the data that is transferred between host and USB-ICC.

Therefore, these two requests are always represented by two arrowed boxes: Indicates if the response is complete, to be continued or if the command APDU can continue Size of abData field of this message 00h: Polling the abData field contains the delay time wDelayTime until the host waits to send out the next request.

The wValue field specifies bLevelParameter in the high byte and bReserved in the low byte.


Smart Card ICCD version 1.0

For control transfers two implementations are possible version A and version B. Its size is 0, 1 or 3 bytes. This specification uses the following typographic conventions: The time interval is driver dependent. The response APDU begins with this command and is to continue 02h: Also returns information created by the preceding request.

In addition, sequence numbering assigns command messages with their corresponding response messages. The following values are assigned: Zero-based value identifying the index in icccd array of concurrent interfaces supported by this configuration.

Smart Card ICCD version |

Instead, it uses class-specific protocols on the interface level. Shall be in the range from 1 to In order to save bandwidth, the time interval should not be less than 10ms. The value is given in units of 10ms e.

For correct operation of the interrupt request, the following conditions shall apply: