• B5.6.4.1 Driver does not cause system to stop running if required resources are not available
  • B5.6.4.4.2 258 byte packets in T=0 and 259 byte packets in T=1.
  • B5.6.4.4.3 Smart card insertion/removal monitor.
  • B5.6.4.4.4 Reader must support negotiable and specific modes according to ISO/IEC 7816-3 (1997-12-15) Sections 5.4 and 7.
  • B5.6.4.4.5 Support 3.5795 MHz minimum clock frequency.
  • B5.6.4.5 Input device implementing a PIN data-entry keyboard complies with ISO 13491-1
  • B5.6.4.6 See B1.4.12; A1.1.4.13
  • B5.6.3 Smart Card - Quality




    Download 0,89 Mb.
    bet121/188
    Sana21.03.2017
    Hajmi0,89 Mb.
    #429
    1   ...   117   118   119   120   121   122   123   124   ...   188

    B5.6.3 Smart Card - Quality

    B5.6.3.1 - See B1.4.12; A1.1.4.13
    B5.6.3.2 Pass WHQL tests - See B1.3.

    See “Smart Card Readers” in HCT documentation.

    B5.6.4 Smart Card - Windows Experience


    Design Guideline References:
    Smart Card for Windows web site at http://www.microsoft.com/hwdev/tech/input/smartcard/
    B5.6.4.1 Driver does not cause system to stop running if required resources are not available
    B5.6.4.2 Driver supports multiple instances of the same device on system without problems
    B5.6.4.3 See B1.4.5
    B5.6.4.4 Reader supports required capabilities
    B5.6.4.4.1 Direct and Inverse-convention smart cards.

    A smart card reader must support both inverse and direct convention smart cards either in hardware or in the driver for the operating system.
    B5.6.4.4.2 258 byte packets in T=0 and 259 byte packets in T=1.

    A smart card reader must support the exchange of the following in a single transmission:

    • 258 byte packets in T=0—that is, 256 data bytes plus the two status words SW1 and SW2.

    • 259 byte packets in T=1—that is, 254 information bytes plus node address, packet control bytes, length, and two Error Detection Code bytes.
    B5.6.4.4.3 Smart card insertion/removal monitor.

    A smart card reader must be able to detect and report smart card insertions and removals without any user intervention other than removing or inserting the smart card itself. The reader must use an interrupt mechanism to report the smart card insertion or removal to the system. A driver polling method to detect smart card insertion and removals is not an acceptable method for meeting this requirement.
    B5.6.4.4.4 Reader must support negotiable and specific modes according to ISO/IEC 7816-3 (1997-12-15) Sections 5.4 and 7.

    To support multi-protocol smart cards and smart cards using higher data rates and higher clock frequencies, the reader must support negotiable and specific modes according to ISO/IEC 7816-3 (1997-12-15), Sections 5.4 and 7.

    Power Down command for ISO 7816-3 is optional.

    PTS is not required.

    B5.6.4.4.5 Support 3.5795 MHz minimum clock frequency.

    A smart card reader must support a minimum clock frequency of 3.5795 MHz.
    B5.6.4.4.6 Support minimum data rate of 9600 bps.
    B5.6.4.4.7 Reset command.

    A smart card reader must support the asynchronous protocols T=0 and T=1 as described in ISO/IEC 7816-3, either in hardware or in the driver. Both protocols must be supported fully. The smart card reader and the driver must support cards that can handle both protocols.

    The following protocol rules apply for the T=1 protocol:



    • A transmission is defined as sending a command to a smart card using one or more T=1 blocks and receiving the corresponding answer using one or more T=1 blocks as defined in ISO/IEC 7816-3.

    • For cards that support Information Field Size integrated circuit Card (IFSC) requests, the first transmission—after a reset of the smart card—must start with an Information Field Size Device (IFSD) request, as defined in ISO/IEC 7816-3, Amendment 1, Section 9.5.1.2.

    For cards that do not support an IFSD request (that is, the card replies with an R-Block indicating “Other error”), the transmission must continue with an I-Block.

    After a successful RESYNCH request, the transmission must restart from the beginning with the first block with which the transmission originally started.



    • Support for protocols other than T=0 and T=1 is not required.
    B5.6.4.5 Input device implementing a PIN data-entry keyboard complies with ISO 13491-1

    An input device that uses a keyboard for personal identification number (PIN) entry must comply with ISO 13491-1:1998 Banking—Secure cryptographic devices (retail)—Part 1: Concepts, requirements and evaluation methods.
    B5.6.4.6 See B1.4.12; A1.1.4.13

    Download 0,89 Mb.
    1   ...   117   118   119   120   121   122   123   124   ...   188




    Download 0,89 Mb.