SB nº 155: Polling Loop – Reset (Spec Change)
Specification Bulletin No. 155 Second Edition March 2015 Polling Loop - Reset This Specification Bulletin clarifies the inclusion of resets within the polling loop if required by other technologies.
Applicability
This Specification Bulletin applies to: EMV Contactless Specifications for Payment Systems, Book D – EMV Contactless Communication Protocol Specification, Version 2.4 – February 2014. Related Documents None
Description
In Book D – requirement 9.2.1.6 allows for resets that may be needed by other technologies before or after the proprietary polling command. Clarification is required to ensure that the corresponding testing is aligned. The second edition of this Specification Bulletin improves the diagram and corrects an error in the definition of the proprietary polling commands ("different from WUPA/REQA and WUPB/REQB" instead of "different from WUPA and WUPB") which was an unintentional deviation from the original definition in Version 2.4.
http://www.emvco.com/specifications.aspx.
Specification Changes In Section 9.2 replace Figure 9.2 and change requirement 9.2.1.6 as follows: Replace Figure 9.2 with the following figure. 1 TYPE_A = 0 TYPE_B = 0 TYPE_1 = 0 … TYPE_n = 0 2 NO TYPE_A = 0 ? YES 3 WAIT tP 4 WUPA 5 RESPONSE? NO YES 6 TYPE_A = 1 7 HLTA NO Other Type(s) YES Supported? 8 NO TYPE_B = 0 ? YES 9 WAIT tP 10 WUPB 11 RESPONSE? NO YES 12 TYPE_B = 1 Type 1... NO TYPE_1 = 0 ? YES Optional RESET tRESET Optional RESET tRESET WAIT tP1 POLL 1 RESPONSE? NO YES TYPE_1 = 1 Type x... 13 NO TYPE_x = 0 ? YES 14 Optional RESET tRESET 15 WAIT tPx 16 POLL x 19 Optional RESET tRESET 17 RESPONSE? NO YES 18 TYPE_x = 1 Type n NO TYPE_n = 0? YES Optional RESET tRESET WAIT tPn POLL n RESPONSE? NO YES TYPE_n = 1 20 RESET tRESET
http://www.emvco.com/specifications.aspx.
Change requirement 9.2.1.6 as follows: PCD 9.2.1.6 If the PCD supports other technologies, then for each supported technology x, the PCD shall for each other technology X proceed as follows: The PCD shall check the value of TYPE_Ox (symbol 13 and symbol 18). If TYPE_Ox is different from zero, then the PCD shall conclude the polling procedure and continue with the collision detection procedure. Else if TYPE_Ox is equal to zero, then:
- If specifically required by the technology, the PCD shall reset the Operating Field (symbol 14).1
- If required by the technology, the PCD shall may wait tPOx before sending the proprietary polling command for technology X (symbol 154 and symbol 19). The value of tPOx is proprietary for technology x and may be zero. and It is not defined by this specification.
- If required by the technology, the PCD may reset the Operating Field before and after the proprietary polling command.
- The PCD shall send a proprietary polling command for technology x (symbol 16).
- If the PCD detects a PICC of other technology x, the PCD shall set TYPE_Ox equal to 1 (symbol 187 and symbol 22).
- If specifically required by the technology, the PCD shall may reset the Operating Field before moving to the next technology (symbol 19) and after the proprietary polling command. Proprietary polling commands shall be different from WUPA/REQA and WUPB/REQB as defined by this specification. from REQA and REQB as defined by ISO/IEC 14443 3. 1 Resets are not to be applied if not specifically required by the other technology. http://www.emvco.com/specifications.aspx. PCD Other technologies (if any) that do not require a reset of the Operating Field (before and/or after) the proprietary polling command, shall be polled before other technologies (if any) that require a reset(s) of the Operating Field. The PCD shall continue with 9.2.1.7. PCDs that implement other technologies that require a reset before/after the polling command are responsible for implementing a proprietary process to handle any resulting collisions. For example from PICCs that support the proprietary technology alongside another supported technology. http://www.emvco.com/specifications.aspx.