PCI Watch

Tracking changes across the Payment Card Industry

SB nº 122: Alignment 2 (Spec Change)

v1.0 Specification Bulletins
Contactless

Specification Bulletin No. 122 First Edition August 2013 Alignment 2 This Specification Bulletin aligns a number of parameters and functional behaviour with ISO/IEC 14443 and NFC Forum Digital Protocol Specification in addition to previously published alignment bulletins.

Effective Date

This Specification Bulletin is effective from November 2014 at which time any affected or new type approval testing will come into effect.

Applicability

This specification bulletin applies to: EMV Contactless Specifications for Payment Systems, Book D – EMV Contactless Communication Protocol Specification, Version 2.3 – February 2013.

Related Documents

None

Description

This specification bulletin aligns a number of parameters and functional behaviour with ISO/IEC 14443 and NFC Forum Digital Protocol Specification.

http://www.emvco.com.

Specification Change Notice 1. In Section 4.8.1, Frame Delay Time PCD → PICC, change FWTB,PICC,MAX for WUPB and REQB Commands as follows: TR0 For Type B, TR0 is measured from the EoS of the PCD command to the start of unmodulated subcarrier of the PICC response as shown in Figure 4.20 above and Figures 4.23, 4.24, and 4.25 below. Figure 4.23: Start of Unmodulated Subcarrier of PICC Response (Positive Modulation) Figure 4.24: Start of Unmodulated Subcarrier of PICC Response (Negative Modulation)

http://www.emvco.com.

Figure 4.25: Start of Unmodulated Subcarrier of PICC Response (Example of Mixed Modulation Starting with Positive Part Cycle) FDTB,PICC,MAX and TR0MAX for WUPB and REQB Commands For the Type B – WUPB and REQB commands (see section 6.3.1), the PICC must starts sending its response within FWTACTIVATION (activation frame waiting time) the unmodulated subcarrier within TR0MAX,ATQB. Requirements 4.25: FWTATQB and TR0MAX for WUPB and REQB Commands PCD 4.8.1.14 For the Type B – WUPB and REQB commands, the PCD shall wait FWTATQB for a response from the PICC. If the PCD does not receive a response from the PICC within FWTATQB, then the PCD shall consider this is as a time‐out error. PICC 4.8.1.15 For the Type B – WUPB and REQB commands, the PICC shall start the unmodulated subcarrier its response within TR0MAX,ATQBFWTATQB. Refer to Annex A.4 for the value of TR0MAX,ATQBFWTATQB.

http://www.emvco.com.

In Annex A.4 Sequences and Frames, add TR0MAX,ATQB for the PICC Value and delete the PICC Value for FWTATQB as follows: Topic Type B Table A.5: Sequences and Frames Parameter … FWTATQB TR0MAX,ATQB PCD Value Min Max PICC Value Min Max Units 7680 7296 1/fc 4096 1/fc … Change Table 4.5 as follows: FDTB FDTB,PCD FDTB,PICC Table 4.5: Type B – Timings Minimum Maximum FDTPCD,MIN n.a. TR0MIN + TR1MIN  FWTATQBTR0MAX,ATQB + TR1MAX for ATQB  FWT for all other commands

http://www.emvco.com.

2. In Section 10.3.2 Chaining, add a requirement that a PICC must be able to accept an empty I-block at the end of a chain. Requirements 10.8: Block Sizes during Chaining PCD 10.3.2.2 When the PCD sends a chain of I‐blocks, each block indicating chaining (i.e. all blocks of the chain except the last one) shall have a length equal to FSC. When the PCD sends a chain of I‐blocks, the INF field of the last block may have a length equal to zero. PICC 10.3.2.3 The PICC shall accept a chain of I‐blocks of which the INF field of the last block has a length equal to zero.

http://www.emvco.com.

3. Recommend in the specification that if optional functionality is supported by the PICC, it should be done according to ISO/IEC 14443. Table 5.3: Byte 1 of ATQA b8 b7 b6 b5 b4 b3 b2 b1 Meaning 0 0 UID size: single (4 bytes) 0 1 UID size: double (7 bytes) 1 0 UID size: triple (10 bytes) 1 1 Not allowed 0 RFU 1 0 0 0 0 Bit frame anticollision1 0 1 0 0 0 Bit frame anticollision 0 0 1 0 0 Bit frame anticollision 0 0 0 1 0 Bit frame anticollision 0 0 0 0 1 Bit frame anticollision All other values Not allowed PCD 5.3.2.2 Requirements 5.4: UID Length The PCD shall be capable of successfully recovering a UID of 4, 7, or 10 bytes. PICC 5.3.2.3 The PICC shall have a UID of 4, 7, or 10 bytes. The value of the UID shall be a fixed number or a random number which is dynamically generated by the PICC. The value of the UID should conform to the UID contents requirements of ISO/IEC 14443‐3. 1 If the PICC supports bit frame anticollision then it should do so according to ISO/IEC 14443-3 however this functionality is beyond the scope of this specification.

http://www.emvco.com.

Requirements 5.19: Interface Byte TC(1) of the ATS PCD 5.7.2.14 The PCD shall not use CID or NAD and shall disregard any value returned by the PICC in b1‐b2 of TC(1). PICC The PICC may support CID and NAD. In this case it should do so according to ISO/IEC 14443. Requirements 6.3: Application Family Indicator (AFI) PCD 6.3.1.1 The AFI shall be set to '00'. This selects all application families. PICC The PICC may support a WUPB command with AFI different from '00'. In this case it should do so according to ISO/IEC 14443. PCD 6.3.1.2 Requirements 6.4: Number of Slots (N) The Number of slots (N) shall always be set to (000)b to force all PICCs to respond with ATQB in the first time slot. PICC The PICC may support a WUPB and REQB command with Number of slots different from (000)b. In this case it should do so according to ISO/IEC 14443 including supporting the Slot‐MARKER command and anticollision sequence defined in ISO/IEC 14443‐3 however this functionality is beyond the scope of this specification. Requirements 6.15: Frame Options (FO) PCD 6.3.2.14 The PCD shall not use CID or NAD and shall disregard any value returned by the PICC in the FO field. PICC The PICC may support CID and NAD. In this case it should do so according to ISO/IEC 14443.

http://www.emvco.com.

Requirements 6.18: Coding of Param 1 of the ATTRIB command PCD 6.4.1.3 6.4.1.4 6.4.1.5 The PCD shall set b8 and b7 equal to (00)b indicating that the default minimum value of TR0 (TR0MIN) has to be used (see Annex A.4). The PCD shall set b6 and b5 equal to (00)b indicating that the default minimum value of TR1 (TR1MIN) has to be used (see Annex A.4). The PCD shall set b4 and b3 equal to (00)b indicating that it does not support suppression of SoS/EoS. PICC The PICC may support values different from (00)b for b8 and b7. In this case it should do so according to ISO/IEC 14443. The PICC may support values different from (00)b for b6 and b5. In this case it should do so according to ISO/IEC 14443. The PICC may support suppression of SoS/EoS. In this case it should do so according to ISO/IEC 14443.

http://www.emvco.com.