SB nº 186: PPS Command

EMV^® Specification Bulletin No. 186 First Edition November 2017 PPS Command This Specification Bulletin defines the PPS command for Type A.

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 specification bulletin introduces the Type A PPS command for the PICC to enable proprietary implementations. A PCD compliant with the specification continues not to use the PPS command. Requirement 5.1.1.2 requires the PICC to consider any PCD command with a coding not compliant to the specification as a protocol error. As the PPS command was not defined in the specification, the PICC was required to consider a PPS command as a protocol error.

countries.

Proposed Specification Change Add PPS and PPSR to Table 1.1: Abbreviations as follows: Table 1.1: Abbreviations Abbreviation … PPS PPSR PPSS PPS0 PPS1... Description Protocol and Parameter Selection Protocol and Parameter Selection Response Protocol and Parameter Selection Start Protocol and Parameter Selection parameter 0 Protocol and Parameter Selection parameter 1 Add PPS command to section 5 as follows: PCD Command WUPA REQA ANTICOLLISION CL1 ANTICOLLISION CL2 ANTICOLLISION CL3 SELECT CL1 SELECT CL2 SELECT CL3 HLTA RATS PPS Table 5.1: Type A – Command Set PICC Response ATQA ATQA UID CL1 UID CL2 UID CL3 SAK SAK SAK – ATS PPSR 5.8 Protocol Parameter Selection (PPS)

countries.

The PPS command contains the start byte that is followed by two parameter bytes (see Table 5.21). The PPS response acknowledges the received PPS command and it contains only the start byte. A PCD compliant with this specification does not use the PPS command. A PICC compliant with this specification which supports PPS is required to respond correctly to a valid PPS command when it is received as the first block after the PICC has sent the RATS response.

5.8.1 PPS Command The PPS command is transmitted with CRC_A within a standard frame. The format of the PPS command is defined in Table 5.21. Byte 1 PPSS Byte 2 PPS0 Table 5.21: Coding of PPS Command Byte 3 PPS1 Requirements 5.22: PPS Command PCD 5.8.1.1 The PCD shall not send a PPS command. PICC 5.8.1.2 If the PPS command is not the first block received after the PICC has sent the RATS response, the PICC shall ignore the PPS command. The components of this command are defined as follows: Coding of PPSS PPSS consists of two parts. b8 to b5 identify the PPS and b4 to b1 include the CID. Table 5.22: Coding of PPSS b8 b7 b6 b5 b4 b3 b2 b1 1 1 0 1 x x x x CID Meaning PPS0 Coding PPS0 indicates the presence of the optional byte PPS1

countries.

Table 5.23: Coding of PPS0 b8 b7 b6 b5 b4 b3 b2 b1 Meaning 0 0 0 Other values are RFU x PPS1 is transmitted if set to (1)b 0 0 0 1 Other values are RFU PPS1 Coding PPS1 conveys information to define the bit rate selection of the PCD compliant with the bit rate capabilities of the PICC indicated in the interface byte TA(1) of the RATS response. Table 5.24: Coding of PPS1 b8 b7 b6 b5 b4 b3 b2 b1 0 RFU Meaning 0 RFU 0 RFU 0 RFU x x DSI (selected divisor PICC to PCD) x x DRI (selected divisor PCD to PICC) The coding of the selected divisor integer D in terms of DSI and DRI is given in Table 5.25. DSI, DRI D Table 5.25: Coding of Selected Divisor Integer (00)b 1 (01)b 2 (10)b 4 (11)b 8 Requirements 5.23: PPS1 PICC 5.8.1.3 The PICC shall implement the bit rates requested by the PCD in the PPS command provided they comply with those proposed by the PICC in TA(1) of the RATS response.

5.8.2 PPS Response

countries.

The length of the PPS response is one byte and transmitted with CRC_A within a standard frame. The format of the PPS response is defined in Table 5.26. Byte 1 PPSS Table 5.26: Coding of PPS Response Requirements 5.24: PPS Response PICC 5.8.2.1 If the bit rates requested by the PCD in the PPS command do not comply with those proposed by the PICC in TA(1) of the RATS response, the PICC shall not send a PPS response (i.e. ignore the PPS command).

5.8.2.2 If the bit rates requested by the PCD in the PPS command comply with those proposed by the PICC in TA(1) of the RATS response the PICC shall send a PPS response with PPSS set to the same value as the PPSS byte of the PPS command.

countries.

Change Figure 7.1 as follows: Figure 7.1: PICC Type A State Diagram HALT HLTA REQA WUPA RATS HLTA PPS AC CL2 WUPA REQA AC CL3 WUPA SELECT CL2 RATS SELECT CL3 PPS ERROR AC CL1 AC CL3 READY * SELECT CL1 SELECT CL3 ERROR SELECT CL1 HLTA REQA WUPA RATS PPS AC CL1 AC CL2 SELECT CL1 SELECT CL2 ERROR READY' * SELECT CL2 HLTA REQA WUPA AC SELECT PPS ERROR READY" * SELECT CL3 AC SELECT HLTA REQA RATS PPS ERROR AC CL1 AC CL2 AC CL3 DESELECT ACTIVE * RATS PROTOCOL HLTA REQA WUPA RATS PPS AC SELECT ERROR POWER-OFF POWER-ON IDLE HLTA REQA WUPA RATS PPS AC CL1 AC CL3 SELECT SELECT ERROR HLTA REQA WUPA RATS PPS AC CL2 AC CL3 SELECT SELECT ERROR CL1 CL3 REQA, WUPA CL2 CL3 READY SELECT CL1 HLTA REQA WUPA RATS PPS AC CL1 AC CL2 SELECT CL1 SELECT CL2 ERROR READY' SELECT CL2 REQA WUPA AC SELECT PPS ERROR READY" SELECT CL3 AC SELECT HLTA RATS PPS ERROR AC CL1 AC CL2 AC CL3 ACTIVE RATS HLTA

countries.

Change requirement 7.2.7.1 as follows: Requirements 7.7: Type A – PROTOCOL State PICC 7.2.7.1 The PICC shall only reply to valid blocks as defined in Chapter 10 and optionally to the PPS command as defined in Chapter 5. All other Type A commands (i.e. WUPA, REQA, HLTA, AC, SELECT, and RATS) and errors shall be ignored. As described in section 7.1, if a command of another technology is received, the resulting state of the PICC is undefined. Add new requirement 7.2.7.3 as follows: PICC 7.2.7.3 The PICC shall remain in the PROTOCOL state when a PPS command is received and either:

• respond to the PPS command if allowed by the requirements specified in Chapter 5
• ignore the PPS command 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.