ISO/IEC 14443-3:2001/Amd 3:2006

Identification cards — Contactless integrated circuit(s) cards — Proximity cards — Part 3: Initialization and anticollision — Amendment 3: Handling of reserved fields and values

Cartes d'identification — Cartes à circuit(s) intégré(s) sans contact — Cartes de proximité — Partie 3: Initialisation et anticollision — Amendement 3: Maniement de champs et valeurs réservés

General Information

• Status: Withdrawn
• Publication Date: 21-Mar-2006
• Withdrawal Date: 21-Mar-2006
• ICS: 35.240.15 - Identification cards. Chip cards. Biometrics
• Technical Committee: ISO/IEC JTC 1/SC 17 - Cards and security devices for personal identification
• Drafting Committee: ISO/IEC JTC 1/SC 17/WG 8 - Integrated circuit cards without contacts
• Current Stage: 9599 - Withdrawal of International Standard
• Completion Date: 12-Apr-2011

Relations

• Revised: ISO/IEC 14443-3:2011 - Identification cards — Contactless integrated circuit cards — Proximity cards — Part 3: Initialization and anticollision
• Effective Date: 15-Apr-2008
• Amends: ISO/IEC 14443-3:2001 - Identification cards — Contactless integrated circuit(s) cards — Proximity cards — Part 3: Initialization and anticollision
• Effective Date: 06-Jun-2022
• Child: ISO/IEC 14443-3:2001 - Identification cards — Contactless integrated circuit(s) cards — Proximity cards — Part 3: Initialization and anticollision
• Effective Date: 15-Apr-2008

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 14443-3
First edition
2001-02-01
AMENDMENT 3
2006-03-15


Identification cards — Contactless
integrated circuit(s) cards — Proximity
cards —
Part 3:
Initialization and anticollision
AMENDMENT 3: Handling of reserved fields
and values
Cartes d'identification — Cartes à circuit(s) intégré(s) sans contact —
Cartes de proximité —
Partie 3: Initialisation et anticollision
AMENDEMENT 3: Maniement de champs et valeurs réservés




Reference number
ISO/IEC 14443-3:2001/Amd.3:2006(E)
©
ISO/IEC 2006

---------------------- Page: 1 ----------------------
ISO/IEC 14443-3:2001/Amd.3:2006(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.


©  ISO/IEC 2006
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Published in Switzerland

ii © ISO/IEC 2006 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 14443-3:2001/Amd.3:2006(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
Amendment 3 to ISO/IEC 14443-3:2001 was prepared by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC 17, Cards and personal identification.
As part of maintaining ISO/IEC 14443-3:2001, a need was raised to better clarify the handling of fields and
values reserved by ISO/IEC for future use. This Amendment addresses the required document
enhancements.
ISO/IEC 14443-3:2001 defines certain fields and values as Reserved for Future Use (RFU) by new ISO/IEC
rules that may be added in later versions. This Amendment includes clarification that products that comply to
ISO/IEC 14443-3:2001 shall not improperly use RFU fields and values, plus documentation of product
behaviour, that when followed by PICC and PCD designs commenced after publication of
ISO/IEC 14443-3:2001, should assist with backward compatibility and interoperability for future definition by
ISO of RFU fields and values. Consequently, many of the references to “should” may be changed into a
definitive “shall” in the second edition; thus, it is recommended to implement them at this time.
© ISO/IEC 2006 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 14443-3:2001/Amd.3:2006(E)
Identification cards — Contactless integrated circuit(s) cards —
Proximity cards —
Part 3:
Initialization and anticollision
AMENDMENT 3: Handling of reserved fields and values
Page 4, Clause 4 “Symbols and abbreviated terms”
Add the following abbreviations after the SELECT line:
“SFGI  Start-up Frame Guard time Integer
SFGT  Start-up Frame Guard Time”
Page 11, Subclause 6.2.3 (renumbered to 6.3.3) “READY State”
Replace the first sentence with the following:
“In the READY State, the bit frame anticollision method shall be applied.”
Page 11, Subclause 6.2.6 (renumbered to 6.3.6) “READY* State”
Replace the first sentence with the following:
“The READY* State is similar to the READY State. The bit frame anticollision method shall be applied.”
Page 12, Subclause 6.3.1 (renumbered to 6.4.1) “REQA and WUPA commands”
Add the following paragraphs below Table 2 “Coding of Short Frame”, as the last paragraphs in the subclause:
“A PCD sending an RFU value is not compliant with this standard.
A PICC receiving an RFU value should consider the short frame as an error (see Figure 6) and should not
send a response.”
Page 15, Subclause 6.4.2.1 (renumbered to 6.5.2.1) “Coding of ATQA”
Add the following as the last paragraphs in the subclause:
“A PICC sending an ATQA with (b8,b7) = (11)b or (b16 to b13) <> (0000)b or b6 <> (0)b is not compliant with
this standard.
A PCD detecting a collision in any bit of (b16 to b1) shall commence with the first step of the anticollision loop
(see Subclause 6.5.3.1).
© ISO/IEC 2006 – All rights reserved 1

---------------------- Page: 4 ----------------------
ISO/IEC 14443-3:2001/Amd.3:2006(E)
The PCD shall commence with the first step of the anticollision loop regardless of any value in the proprietary
field b12 to b9.
A PCD receiving (b8,b7) = (11)b or (b16 to b13) <> (0000)b or b6 <> (0)b should ignore the values and should
commence with the first step of the anticollision loop (see Subclause 6.5.3.1).”
Page 18, Subclause 6.4.3.3 (renumbered to 6.5.3.3) “Coding of NVB (Number of Valid Bits)”
Add the following paragraphs below Table 7 “Coding of NVB”, as the last paragraphs in the subclause:
“The PCD shall set NVB only to values defined in Table 7 except that for byte counts 6 and 7 only bit count of
0 is allowed. A PCD setting NVB to any forbidden value is not compliant with this standard.
A PCD setting the byte count (b8 to b5) to any value outside the range 2 to 7 is not compliant with this
standard.
A PCD setting the bit count (b4 to b1) > 7 for byte count equal 2 to 5 or setting the bit count (b4 to b1) to any
value other than 0 for byte count equal 6 or 7 is not compliant with this standard.”
Page 19, Subclause 6.4.3.4 (renumbered to 6.5.3.4) “Coding of SAK (Select acknowledge)”
Add the following below Table 8 “Coding of SAK”, as the last paragraphs in the subclause:
“NOTE ‘x’ in this table means ‘a don't care value’.
For b3 = (1)b the PCD shall ignore any other bit of SAK. For b3 = (0)b the PCD shall interpret b6 and shall
ignore any of the remaining bits of SAK. A PCD behaving differently is not compliant with this standard.”
Page 20, Subclause 6.4.4 (renumbered to 6.5.4) “UID contents and cascade levels”
Add the following paragraphs as the last paragraphs in the subclause:
“A PICC sending uid0 with an RFU value is not compliant with this standard. A PICC sending a proprietary
number shall fulfil all other requirements of the anticollision sequence including CT, otherwise such a PICC is
not compliant with this standard.
During the anticollision, the PCD shall regard uid0 with RFU or proprietary values as a regular uid0.”
Page 21, Subclause 7.1.3 “Frame format”
Remove the last sentence “See 7.10.3 for exceptions.”
2 © ISO/IEC 2006 – All rights reserved

---------------------- Page: 5 ----------------------
ISO/IEC 14443-3:2001/Amd.3:2006(E)
Page 29, Subclause 7.7.3 “Coding of AFI”
Replace the last row in Table 12 “AFI coding” with the following:
“
'9'-'D' '0',Y RFU
'E' '0',Y Machine Readable Y=1 Passport
Travel Documents Y=2 Visa
(MRTDs) Other Y values RFU
'F' '0',Y RFU
”
Add the following paragraph as the last paragraph in the subclause:
“A PCD sending a REQB/WUPB command with an AFI field set to an RFU value is not compliant with this
standa
...