SB nº 200: Transmission Error Timings

EMV^® Specification Bulletin No. 200 First Edition January 2018 Transmission Error Timings This Specification Bulletin changes the timing requirements for the exception processing of transmission errors primarily during the half-duplex block transmission protocol.

Applicability

This Specification Bulletin applies to:  EMV Contactless Specifications for Payment Systems, Book D – EMV Contactless Communication Protocol Specification, Version 2.6 – March 2016. Related Documents  None

Description

This bulletin changes the timing requirements for the exception processing of transmission errors primarily during the half-duplex block transmission protocol. The time within which a block must be retransmitted or a reset initiated is now defined from the end of the last block instead of from the beginning of the last block and the retransmission time limit has been reduced accordingly. This reduction in the retransmission time limit also applies whilst not in the half-duplex block transmission protocol.

countries.

Proposed Specification Change Change Requirement 10.3.5.3 as follows: PCD 10.3.5.3 If a block with a transmission error is received after receipt of a block not indicating chaining, then the PCD shall send an R(NAK) block. The PCD shall send the R(NAK) block no later than tRETRANSMISSION measured from the start after the end of the modulation of the block with the transmission error. The PCD shall send up to two consecutive R(NAK) blocks to ask for retransmission. If a block with a transmission error in response to the second R(NAK) block is received, then the PCD shall report a transmission error to the terminal and continue as specified in 10.3.5.9 no later than tRESETDELAY after the end of the modulation of the last block with the transmission error. measured from the start of the last invalid response (i.e. the start of SoF for Type A response and the start of SoS for a Type B response as defined in section 4.8). Note that the transmission error is suppressed by the EMD handling defined in section 4.9.2 if the transmission error is detected when less than 4 bytes have been received from the PICC. Change Requirement 10.3.5.4 as follows: PCD 10.3.5.4 If a block with a protocol error is received after receipt of a block not indicating chaining, then the PCD shall report a protocol error to the terminal and continue as specified in 10.3.5.9 no later than tRESETDELAY after the end of the modulation of the block measured from the start of the response block containing the protocol error (i.e. the start of SoF for Type A response and the start of SoS for a Type B response as defined in section 4.8).

countries.

Change Requirement 10.3.5.6 as follows: PCD 10.3.5.6 If a block with a transmission error is received after receipt of a block indicating chaining, then the last R(ACK) block sent by the PCD shall be retransmitted. The PCD shall send the R(ACK) block no later than tRETRANSMISSION measured from the start after the end of the modulation of the block with the transmission error. The PCD shall retransmit the R(ACK) block up to two consecutive times to ask for retransmission. If a block with a transmission error in response to the second R(ACK) block is received, then the PCD shall report a transmission error to the terminal and continue as specified in 10.3.5.9 no later than tRESETDELAY after the end of the modulation of the last block with the transmission error. measured from the start of the last invalid response (i.e. the start of SoF for Type A response and the start of SoS for a Type B response as defined in section 4.8). Note that the transmission error is suppressed by the EMD handling defined in section 4.9.2 if the transmission error is detected when less than 4 bytes have been received from the PICC. Change Requirement 10.3.5.7 as follows: PCD 10.3.5.7 If a block with a protocol error is received after receipt of a block indicating chaining, then the PCD shall report a protocol error to the terminal and continue as specified in 10.3.5.9 no later than tRESETDELAY after the end of the modulation of the block measured from the start of the response block containing the protocol error (i.e. the start of SoF for Type A response and the start of SoS for a Type B response as defined in section 4.8).

countries.

Change the value of tRETRANSMISSION in Table A.6 as follows: Table A.6: PCD Processing Parameter … tRETRANSMISSION … PCD Value Min Max PICC Value Units 3310 ms

countries.

Legal Notice

The EMV^® Specifications are provided "AS IS" without warranties of any kind, and EMVCo neither assumes nor accepts any liability for any errors or omissions contained in these Specifications. EMVCO DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT, AS TO THESE SPECIFICATIONS. EMVCo makes no representations or warranties with respect to intellectual property rights of any third parties in or in relation to the Specifications. EMVCo undertakes no responsibility to determine whether any implementation of the EMV^® Specifications may violate, infringe, or otherwise exercise the patent, copyright, trademark, trade secret, know-how, or other intellectual property rights of third parties, and thus any person who implements any part of the EMV^® Specifications should consult an intellectual property attorney before any such implementation. Without limiting the foregoing, the Specifications may provide for the use of public key encryption and other technology, which may be the subject matter of patents in several countries. Any party seeking to implement these Specifications is solely responsible for determining whether its activities require a license to any such technology, including for patents on public key encryption technology. EMVCo shall not be liable under any theory for any party’s infringement of any intellectual property rights in connection with the EMV^® Specifications

countries.