SB n° SB-93 : Removal Procedure (Spec Change)
Specification Bulletin No. 93 First Edition September 2011 Removal Procedure This specification bulletin corrects the requirements related to the main loop.
Effective Date
This specification bulletin is effective from November 2011, at which time any affected or new type approval testing will also come into effect.
Applicability
This specification bulletin applies to: EMV Contactless Specifications for Payment Systems, Book D – EMV Contactless Communication Protocol Specification, Version 2.1 – March 2011.
Related Documents
None
Description
This specification bulletin solves an inconsistency around the removal procedure between EMV Contactless Specifications for Payment Systems, Book A and Book D. In the current version of EMV Contactless Specifications for Payment Systems, Book D it is not possible to separate the removal procedure from a field off request, which is contrary to EMV Contactless Specifications for Payment Systems, Book A where a removal procedure may not always be performed (depending on implementation).
http://www.emvco.com.
Specification Change Notice In Section 9.1.1 Main Loop – Informative, change point 5 as follows: 5. When the transaction is finished the PCD waits until the PICC is removed from the Operating Field. In some environments it is necessary to ensure that the PICC has left the field by employing a removal procedure. The removal procedure is specified in section 9.5. When the PICC is removed from the Operating Field, the PCD resets the Operating Field (as defined in section 3.2.6), waits during a time tPAUSE with unmodulated carrier (optional) and resumes with the polling and collision detection (optional). The value of tPAUSE is implementation specific. In other environments where the physical configuration and the way the transaction completes may be sufficient to ensure no overlapping transactions, the removal procedure may be skipped. Replace requirement 9.1.2.3 by the following: PCD 9.1.2.3 9.1.2.4 9.1.2.5 9.1.2.6 9.1.2.7 The PCD shall alternate between technologies as specified in section 9.2. Only if a single PICC is detected during the collision detection procedure (see section 9.3), the PCD shall activate the PICC (see section 9.4) to initiate the transaction process (i.e. half duplex block protocol as described in Chapter 10). During the transaction process, the PCD shall not initiate any communication with another PICC. When the transaction is finished, the PCD shall continue with the removal procedure (except in the case of unrecoverable error (see 10.3.5.9)). The PCD shall perform collision detection as specified in section 9.3. Only if a single PICC is detected during the collision detection procedure, the PCD shall activate the PICC as specified in section 9.4 to initiate the transaction process. During the transaction process the PCD shall use the half-duplex block protocol as specified in Chapter 10 and shall not initiate any communication with another PICC. The PCD shall perform the removal procedure as specified in section 9.5, when requested to do so by the terminal. In Section 9.5 Removal, change first paragraph as follows: This section specifies how the PCD must proceed after the transaction is completed when the removal procedure is requested by the terminal. Figure 9.5 shows that the PCD continues polling until the PICC is removed. The implementation of the removal procedure is mandatory for the PCD, but the removal procedure is only executed upon request from the terminal. <<< End of Bulletin >>>
http://www.emvco.com.