ANSI INCITS ISO IEC 14443-3 AMD 3-2006 Identification cards Contactless integrated circuit(s) cards Proximity cards Part 3 Initialization and anticollision Amendment 3 Handling of .pdf

《ANSI INCITS ISO IEC 14443-3 AMD 3-2006 Identification cards Contactless integrated circuit(s) cards Proximity cards Part 3 Initialization and anticollision Amendment 3 Handling of .pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS ISO IEC 14443-3 AMD 3-2006 Identification cards Contactless integrated circuit(s) cards Proximity cards Part 3 Initialization and anticollision Amendment 3 Handling of .pdf（12页珍藏版）》请在麦多课文档分享上搜索。

1、INCITS/ISO/IEC 14443-3:2001/Amd.3:20062008 (ISO/IEC 14443-3:2001/Amd.3:2006, IDT) Identification cards Contactless integrated circuit(s) cards Proximity cards Part 3: Initialization and anticollision Amendment 3: Handling of reserved fields and valuesINCITS/ISO/IEC 14443-3:2001/Amd.3:20062008(ISO/IE

2、C 14443-3:2001/Amd.3:2006, IDT)INCITS/ISO/IEC 14443-3:2001/Amd.3:20062008ii ITIC 2008 All rights reserved PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are

3、 embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorpor

4、ated. 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

5、 problem relating to it is found, please inform the Central Secretariat at the address given below. Adopted by INCITS (InterNational Committee for Information Technology Standards) as an American National Standard. Date of ANSI Approval: 7/2/2008 Published by American National Standards Institute, 2

6、5 West 43rd Street, New York, New York 10036 Copyright 2008 by Information Technology Industry Council (ITI). All rights reserved. These materials are subject to copyright claims of International Standardization Organization (ISO), International Electrotechnical Commission (IEC), American National S

7、tandards Institute (ANSI), and Information Technology Industry Council (ITI). Not for resale. No part of this publication may be reproduced in any form, including an electronic retrieval system, without the prior written permission of ITI. All requests pertaining to this standard should be submitted

8、 to ITI, 1250 Eye Street NW, Washington, DC 20005. Printed in the United States of America INCITS/ISO/IEC 14443-3:2001/Amd.3:20062008 ITIC 2008 All rights reserved iii Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the s

9、pecialized 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 technica

10、l 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. Inter

11、national 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 voti

12、ng. 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 o

13、r 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 field

14、s 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 p

15、roducts 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 futu

16、re 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. INCITS/ISO/IEC 14443-3:2001/Amd.3:20062008 ITIC 2008 All rights reserved 1 Identific

17、ation 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 Int

18、eger 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

19、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 th

20、e 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 pa

21、ragraphs in the subclause: “A PICC sending an ATQA with (b8,b7) = (11)b or (b16 to b13) (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). INCITS/ISO/IEC 14443-3:2001/Am

22、d.3:20062008 2 ITIC 2008 All rights reserved 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) (0)b should ignore the values and should commence with the first step of the a

23、nticollision 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 t

24、hat 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 by

25、te 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 p

26、aragraphs in the subclause: “NOTE x in this table means a dont 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, Su

27、bclause 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 antic

28、ollision 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.” INCITS/ISO/I

29、EC 14443-3:2001/Amd.3:20062008 ITIC 2008 All rights reserved 3 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 Travel Documents (MRTDs) Y=1 Passport Y=2 Visa Other Y values RFU F 0,Y RFU ” Add the followi

30、ng 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 standard. The PICC shall not respond when the AFI field is set to a value which is RFU.” Page 29, Subclause 7.7.4 “Coding of PARAM” Replace Figure

31、21 with the following figure: “ b8 b7 b6 b5 b4 b3 b2 b1 RFU Extended ATQB supported REQB / WUPB N (Number of slots) All RFU bits shall be set to 0. Figure 21 Coding of PARAM ” Replace definition before Table 13 with the following: “b4 = 0 defines REQB: PICCs in IDLE state or READY state shall proces

32、s this command. b4 = 1 defines WUPB: PICCs in IDLE state or READY state or HALT state shall process this command. b1, b2 and b3 are used to code the number of slots N according to Table 13. b5 indicates the PCD capability to support extended ATQB response from the PICC. The use of extended ATQB is o

33、ptional for the PICC. The coding of b5 is as follows: b5 = 0 defines: extended ATQB defined in subclause 7.9.4.7 is not supported by the PCD. b5 = 1 defines: extended ATQB defined in subclause 7.9.4.7 is supported by the PCD.” Add the following paragraphs as the last paragraphs in the subclause befo

34、re Table 13: “A PCD sending a REQB/WUPB command with (b8 to b6) (0000)b is not compliant with this standard. The PCD shall ignore (b4 to b1) and its interpretation of any other field of the whole frame shall not change. A PCD changing its interpretation of any other field of the whole frame when (b4

35、 to b1) (00)b is not compliant with this standard. The PICC should ignore any value (b2,b1) and its interpretation of any other field of the whole frame shall not change.” Page 34, Subclause 7.10.3.1 “Minimum TR0” Add the following paragraphs as the last paragraphs in the subclause: “A PCD setting (

36、b8,b7) = (11)b is not compliant with this standard. Until the RFU value (11)b is assigned by ISO, a PICC receiving (b8,b7) = (11)b should interpret it as (b8,b7) = (00)b, the default value.” Page 34, Subclause 7.10.3.2 “Minimum TR1” Add the following paragraphs as the last paragraphs in the subclaus

37、e: “A PCD setting (b6,b5) = (11)b is not compliant with this standard. Until the RFU value (11)b is assigned by ISO, a PICC receiving (b6,b5) = (11)b should interpret it as (b6,b5) = (00)b, the default value.” Page 35, Subclause 7.10.3.3 “EOF/SOF” Add the following paragraph as the last paragraph in

38、 the subclause after Table 23: “SOF/EOF suppression applies only for communications at fc/128 (106 kbit/s). For bit rates higher than fc/128 (106 kbit/s) the PICC shall always provide SOF and EOF.” Page 35, Subclause 7.10.4 “Coding of Param 2” Add the following paragraphs as the last paragraphs in t

39、he subclause: “A PCD setting Maximum Frame Size Code = 9-F is not compliant with this standard. Until the RFU values 9-F are assigned by ISO, a PICC receiving Maximum Frame Size Code = 9-F should interpret it as Maximum_Frame_Size Code = 8 (256 bytes).” INCITS/ISO/IEC 14443-3:2001/Amd.3:20062008 ITI

40、C 2008 All rights reserved 7 Page 35, Subclause 7.10.5 “Coding of Param 3” Add the following paragraphs as the last paragraphs in the subclause: “A PCD setting (b8 to b5) (0000)b.” Page 36, Subclause 7.10.6 “Coding of Param 4” Add the following paragraphs as the last paragraphs in the subclause: “A

41、PCD setting CID = 15 is not compliant with this standard. The PICC should ignore and not answer the ATTRIB command when received value of CID = 15, as any action in the PICC for CID = 15 may be decided in the future by ISO. A PCD setting (b8 to b5) (0000)b is not compliant with this standard. The PICC should ignore (b8 to b5) and its interpretation of any other field of the whole frame shall not change.” INCITS/ISO/IEC 14443-3:2001/Amd.3:20062008 ICS 35.240.15 Price based on 7 pages ITIC 2008 All rights reserved