ISO/IEC 7816-12:2005 pdf download – Identification cards — Integrated circuit cards — Part 12: Cards with contacts — USB electrical interface and operating procedures.
3 Terms and definitions For the purposes of this document, the following terms and definitions apply. 3.1 Device 3.1.1 interface device terminal communication device or machine to which the card is electrically connected during operation [ISO/IEC 7816-3] 3.1.2 USB connection device device providing an electrical connection path between a USB-ICC and a USB host or hub 3.2 Terms and definitions used in other specifications For the purposes of this document, the terms and definitions given in the USB specification and the CCID specification (see Clause 4) apply. NOTE The relevant terms used in this document are listed in informative Annexes C and D. 4 Abbreviations and notation For the purposes of this document, the following abbreviations apply. Protocol T=0, Protocol T=1 [ISO/IEC 7816-3] D+, D- [Universal Serial Bus Specification Revision 2.0] USB specification Referencing to Universal Serial Bus Specification Revision 2.0 (see clause 2). CCID Chip Card Interface Device. Designates an interface device controlled via USB.
5 Electrical characteristics of the contacts The assignment of the contacts for USB operating conditions is given in ISO/IEC 7816-2:1999 and ISO/IEC 7816-2:1999/Amd.1:2004. An interface device will provide a USB connection to a USB-ICC through VCC, GND, AUX1 and AUX2 respectively V BUS , GND, D+ and D- defined by the USB specification. Cards designed for ISO/IEC 7816-3 operating conditions shall not be damaged when activated under USB conditions. Conversely, cards designed for USB operation shall not be damaged when activated under ISO/IEC 7816-3 operating conditions (by definition, a damaged card no longer operates as specified or contains corrupt data). 6 USB-ICC operated by an interface device A USB-ICC that only provides a USB interface shall have electrically connected C1, C5, C4 and C8. All other contact fields shall be electrically isolated. This type of USB-ICC can be operated by a USB connection device. The USB connection device shall establish an electrical connection to C1, C5, C4 and C8 only, following the electrical characteristics and protocol given in the USB specification. An interface device that does not support a USB interface shall have AUX1 and AUX2 electrically isolated or ensure that the voltage applied at these contact fields shall remain between –0,3V and Vcc + 0,3V.
7 USB Descriptors 7.1 Standard Descriptors The standard descriptors described in the USB specification constitute a way for the host software to identify a new USB device attached, and to load one or more appropriate drivers for this new USB device. The standard descriptors are read by the host software during the enumeration process. In addition, the descriptors can also be retrieved by the host software using standard USB requests. NOTE This document uses for hexadecimal values the notation xxh as used in the USB specification. This is different from the notation ‘xx’ which is used in other parts of this standard series. The notation xxh is used here to avoid possible confusion when reading this document and the related USB documents. In the following tables of standard descriptors the character asteriks (*) in the column Value indicates that this value(s) is defined by ISO/IEC, taken from the set of possible values given in the USB specification. All other values are standard USB entries.
8 Data transfer between host and USB-ICC The exchange of data between host and USB-ICC may be done using bulk transfers or control transfers. For control transfer, two implementations are possible. They are named Version A and Version B. Bulk transfer mode is compliant to the CCID specification, e.g. it uses a subset of the messages/requests as defined in this specification. The notation for the state diagrams is given in the (informative) Annex A.
8.1.1 Bulk messages All messages transmitted over bulk endpoints start with a 10 byte header, optionally followed by data. The purpose of the header is to exchange control and status information between host and USB-ICC. In addition, sequence numbering assigns command messages with their corresponding response messages. The USB-ICC returns its status and error information in the fields bStatus and bError.