PCI Watch

Tracking changes across the Payment Card Industry

SB nº 121: Alignment (Spec Change)

v1.0 Specification Bulletins
Contactless

Specification Bulletin No. 121 First Edition April 2013 Alignment This Specification Bulletin aligns a number of parameters and functional behaviours with ISO/IEC 14443 and the NFC Forum Digital Protocol Specification.

Effective Date

This specification bulletin is effective from November 2013 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 – June 2013. Related Documents
  • None

Description

This Specification Bulletin aligns a number of parameters and functional behaviours with ISO/IEC 14443 and NFC Forum Digital Protocol Specification.

http://www.emvco.com.

Specification Change Notice 1. In Section 4.8.2 change FDTPCD,MIN requirements as follows: FDTPCD,MIN FDTPCD,MIN is the minimum time the PCD must wait before sending the start of a new PCD command after the end of the PICC response (except after the RATS and ATTRIB response when a guard time (SFGT) is requested by the PICC). FDTPCD,MIN is common for Type A and Type B and defines the minimum value for FDTA,PCD and FDTB,PCD and is FDTA,PCD,MIN for a Type A PICC and FDTB,PCD,MIN for a Type B PICC. PCD 4.8.2.1 Requirements 4.27: FDTPCD,MIN PICC Following the end of a PICC response, the PCD shall wait at least a time FDTA,PCD,MIN before transmitting the start of a new Type A PCD command and at least FDTB,PCD,MIN before transmitting the start of a new Type B PCD command. Refer to Annex A.4 for the values of FDTA,PCD,MIN and FDTB,PCD,MIN.

4.8.2.2 Following the end of a PICC response, the PICC shall be able to receive the start of a new PCD command with a minimum interval between the end of the PICC response and the start of the new PCD command of FDTA,PCD,MIN for a Type A command and FDTB,PCD,MIN for a Type B command. If the start of a new Type A PCD command is received before FDTA,PCD,MIN, or a new Type B PCD command before FDTB,PCD,MIN, then the PICC may consider this as a transmission error.

http://www.emvco.com.

In Annex A.4 Sequences and Frames, insert FDTA,PCD,MIN and FDTB,PCD,MIN into Table A.5 and delete FDTPCD,MIN as follows: Table A.5: Sequences and Frames Topic Parameter Type A Type B Common FWTACTIVATION FDTA,PCD,MIN … FWTATQB FDTB,PCD,MIN … FWT FDTPCD,MIN FSDMIN … PCD Value Min Max 71680 6780 7680 6780 384 x 2FWI 6780 256 PICC Value Min Max 65536 1172 Units 1/fc 1/fc 7296 1/fc 1792 1/fc 1/fc 5376 1/fc 256 - In Section 4.8.3 update Table 4.4 and Table 4.5 as follows: Table 4.4: Type A – Timings FDTA Minimum FDTA,PCD FDTA,PCD,MIN n.a. Maximum Table 4.5: Type B – Timings FDTB Minimum FDTB,PCD FDTB,PCD,MIN n.a. Maximum

http://www.emvco.com.

2. In Section 5.7.2, RATS Response (

Answer

To Select), add new PCD requirements related to the handling of FWI values. Requirements 5.17: Interface Byte TB(1) of the ATS PCD PICC 5.7.2.10a The PCD shall accept FWI less than or equal to FWIMAX. Refer to Annex A.4 for the value of FWIMAX.

5.7.2.10 The PICC shall set FWI less than or equal to FWIMAX

Refer to Annex A.4 for the value of FWIMAX. 5.7.2.10b A received value of FWI = 15 shall be treated by the PCD as FWI = 4. 3. In Section 5.7.2, RATS Response (Answer To Select), modify PCD requirements related to the handling of SFGI. Requirements 5.18: Interface Byte TB(1) of the ATS PCD PICC 5.7.2.11 The PCD shall be capable of supporting a PICC returning an ATS with TB(1) indicating an SFGI less than or equal to SFGIMAX. The PCD may support a PICC with an SFGI greater than SFGIMAX.

5.7.2.12 The PICC shall set SFGI less than or equal to SFGIMAX

Refer to Annex A.4 for the value of SFGIMAX. 5.7.2.11a A received value of SFGI = 15 shall be treated by the PCD as SFGI = 0.

http://www.emvco.com.

Topic Table A.5: Sequences and Frames Parameter … PCD Value Min Max PICC Value Min Max SFGIMAX 814 8 … Units - 4. In Section 6.3.2, WUPB and REQB Response (ATQB), add new PCD requirements related to the handling of Protocol_Type values. Requirements 6.11: Type B Protocol Type supported by the PICC PCD PICC 6.3.2.8 The PCD shall be capable of supporting a PICC indicating conformity to ISO/IEC 14443‐4. The PCD may support a PICC not indicating conformity to ISO/IEC 14443‐4.

6.3.2.9 The PICC shall announce that it supports ISO/IEC 14443‐4

This means that the PICC shall set b1 to (1)b. 6.3.2.8a The PCD shall resort to exception processing (protocol error) on reception of an ATQB with b4 of Protocol_Type set to (1)b. Alternatively, legacy PCDs may optionally ignore bit b4 of Protocol Type. Future versions of this specification may not support this option. As described in section 9 the ATQB coding is only considered during Collision Detection. The ATQB coding is ignored during Polling and Removal.

http://www.emvco.com.

5. In Section 6.3.2, WUPB and REQB Response (ATQB), add new PCD requirements related to the handling of FWI values. Requirements 6.13: Maximum Value of FWI for Type B PCD PICC 6.3.2.12a The PCD shall accept FWI less than or equal to FWIMAX. Refer to Annex A.4 for the value of FWIMAX.

6.3.2.12 The PICC shall set FWI less than or equal to FWIMAX

Refer to Annex A.4 for the value of FWIMAX. 6.3.2.12bA received value of FWI = 15 shall be treated by the PCD as FWI = 4.

http://www.emvco.com.

6. In Section 8.1, Sate Diagram, update Figure 8.1 as follows: Figure 8.1: PICC Type B State Diagram

http://www.emvco.com.

In Section 8.2.3, READY State, add new PICC requirement on handling of WUPB/REQB with AFI that does not match the PICC’s AFI. Requirements 8.3: Type B – READY State PICC … 8.2.3.3 The PICC shall remain in the READY state after it has received a valid WUPB or REQB command and transmitted its ATQB. 8.2.3.3a The PICC may enter the IDLE state and transmit no response after it has received a WUPB or REQB command containing an AFI different from ‘00’ that does not match the PICC’s AFI value.

8.2.3.4 The PICC shall enter the HALT state after it has received a valid HLTB command and transmitted its HLTB response. … In Section 8.2.5, HALT State, add new PICC requirement on handling of WUPB with AFI that does not match the PICC’s AFI. Requirements 8.5: Type B – HALT State PICC 8.2.5.1 The PICC shall enter the READY state after it has received a valid WUPB command and transmitted its ATQB. 8.2.5.1a The PICC may enter the IDLE state and transmit no response after it has received a WUPB command containing an AFI different from ‘00’ that does not match the PICC’s AFI value.

8.2.5.2 The PICC shall ignore all other Type B commands and errors and remain in the HALT state.

http://www.emvco.com.

7. In Section 10.2.2, WTXM, add new PICC requirement below Table 10.5 related to the handling of RFU values of b8-b7. Requirements 10.3a: RFU Handling of S(WTX) Response PICC 10.2.1.1a The PICC shall treat b8 to b7 different from (00)b as a protocol error. Alternatively, legacy PICCs may optionally ignore bits b8 to b7. Future versions of this specification may not support this option. 8. In Section 10.2.2, WTXM, change requirement 10.2.2.1 as follows: Requirements 10.4: Frame Waiting Time Extension PCD 10.2.2.1 The PCD shall accept an S(WTX) having a WTXM with a value in the range from 1 to 59. The PCD shall resort to exception processing (protocol error) on reception of an S(WTX) having a WTXM set to 0 or a value in the range from 60 to 63. A received WTXM with a value in the range from 60 to 63 shall be treated by the PCD as value 59. Alternatively, legacy PCDs may optionally treat a WTXM in the range from 60 to 63 as value 59. Future versions of this specification may not support this option.

http://www.emvco.com.

9. In Section 10.3, Protocol Operation, add new Section 10.3.6 DESELECT Processing.

10.3.6 DESELECT Processing The DESELECT command is coded as an S-block and consists of an S(DESELECT) request block sent by the PCD and an S(DESELECT) response sent as acknowledgement by the PICC. The coding of the S(DESELECT) block is as shown in Table 10.3. A PCD compliant with this specification does not use the S(DESELECT) request block. A PICC compliant with this specification must respond correctly to an S(DESELECT) request block. Requirements 10.14: S(DESELECT) Response PICC 10.3.6.1 The PICC shall acknowledge the S(DESELECT) request block by sending an S(DESELECT) response block. The S(DESELECT) response block shall be coded as an S‐block as specified in Table 10.3.

10.3.6.2 The PICC shall send an S(DESELECT) response block in response to an S(DESELECT) request block within FWTDESELECT (refer to Annex A.6 for the value of FWTDESELECT) In Annex A, add a new section with the following value for FWTDESELECT. A.6 Protocol Operation Parameter FWTDESELECT Table A.7: Protocol Operation PICC Value 512 Units etu

http://www.emvco.com.

10. In Annex A.4, Sequences and Frames, change Table A.5 as follows: Topic Type A Type B Common Table A.5: Sequences and Frames Parameter FWTACTIVATION tPCD,S,1 PCD Value Min Max 71680 1280 140816 PICC Value Min Max 65536 126472 1424 tPCD,S,2 25648 38492 240 400 tPCD,E 1280 140816 126472 1424 tPICC,S,1 1264 1424 128072 140816 tPICC,S,2 240 400 25648 38492 tPICC,E 1264 1424 128072 140816 TR0MIN TR1MIN TR1MAX … 10241008 11521264 33283216 11521024 1280 3200 … SFGIMAX 814 8 … Units 1/fc 1/fc 1/fc 1/fc 1/fc 1/fc 1/fc 1/fc 1/fc 1/fc -

http://www.emvco.com.