ANSI INCITS ISO IEC 14443-4 AMD 1-2006 Identification cards Contactless integrated circuit(s) cards Proximity cards Part 4 Transmission protocol Amendment 1 Handling of reserved fi.pdf

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

1、INCITS/ISO/IEC 14443-4:2001/Amd.1:20062008 (ISO/IEC 14443-4:2001/Amd.1:2006, IDT) Identification cards Contactless integrated circuit(s) cards Proximity cards Part 4: Transmission protocol Amendment 1: Handling of reservedfields and valuesINCITS/ISO/IEC 14443-4:2001/Amd.1:20062008(ISO/IEC 14443-4:20

2、01/Amd.1:2006, IDT)INCITS/ISO/IEC 14443-4:2001/Amd.1:20062008 ii 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 embedded a

3、re 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 Incorporated. Detai

4、ls 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 re

5、lating 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: 2/7/2008 Published by American National Standards Institute, 25 West 43rd

6、 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 Standards In

7、stitute (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 to ITI, 12

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

9、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 committee

10、s 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 St

11、andards 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. Publica

12、tion 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

13、patent rights. Amendment 1 to ISO/IEC 14443-4: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-4:2001, a need was raised to better clarify the handling of fields and value

14、s reserved by ISO/IEC for future use. This Amendment addresses the required document enhancements. ISO/IEC 14443-4: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 in

15、conformity with ISO/IEC 14443-4: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-4:2001, should assist with backward compatibility and interoperability for future defi

16、nition 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 of ISO/IEC 14443-4:2001; thus, it is recommended to implement them at this time. INCITS/ISO/IEC 14443-4:2001/Amd.1:20062008 ITIC 2008 All rights res

17、erved 1 Identification cards Contactless integrated circuit(s) cards Proximity cards Part 4: Transmission protocol AMENDMENT 1: Handling of reserved fields and values Page 3, Clause 4 “Symbols and abbreviated terms” Replace the definition of RFU with the following: “Reserved for Future Use by ISO/IE

18、C”. Page 6, Subclause 5.1 “Request for answer to select” Add the following paragraphs as the last paragraphs in the subclause: “A PCD setting FSDI = 9-F is not compliant with this standard. A received value of FSDI = 9-F should be interpreted by the PICC as FSDI = 8 (FSD = 256 bytes). A PCD setting

19、CID = 15 is not compliant with this standard. For PICC behaviour see 5.6.1.2 (c).” Page 7, Subclause 5.2.3 “Format byte” Add the following paragraphs as the last paragraphs in the subclause: “A PICC setting FSCI = 9-F is not compliant with this standard. A received value of FSCI = 9-F should be inte

20、rpreted by the PCD as FSCI = 8 (FSC = 256 bytes). A PICC not setting b8 to 0 is not compliant with this standard. The PCD should ignore b8 and its interpretation of any other field of the whole frame shall not change.” Page 8, Subclause 5.2.4 “Interface byte TA(1)” Add the following paragraphs as th

21、e last paragraphs in the subclause: “A PICC setting b4 = 1 is not compliant with this standard. A received value of TA(1) with b4 = 1 should be interpreted by the PCD as (b8 to b1) = (00000000)b (only 106 kbit/s in both directions).” Page 9, Subclause 5.2.5 “Interface byte TB(1)” INCITS/ISO/IEC 1444

22、3-4:2001/Amd.1:20062008 2 ITIC 2008 All rights reserved Add the following paragraphs as the last paragraphs in the subclause: “A PICC setting SFGI = 15 is not compliant with this standard. Until the RFU value 15 is assigned by ISO, a PCD receiving SFGI = 15 should interpret it as SFGI = 0. A PICC se

23、tting FWI = 15 is not compliant with this standard. Until the RFU value 15 is assigned by ISO, a PCD receiving FWI = 15 should interpret it as FWI = 4.” Page 9, Subclause 5.2.6 “Interface byte TC(1)” Add the following paragraphs as the last paragraphs in the subclause: “A PICC setting (b8 to b3) (00

24、01)b and/or setting (b8 to b6) (0001)b and/or receiving (b8 to b6) (0000)b is not compliant with this standard. A PICC receiving (b8 to b5) 0 of an I-block is not compliant with this standard. A PICC or PCD setting b2 (10)b of an S-block is not compliant with this standard.” Page 17, Subclause 7.1.1

25、.2 “Card identifier field” Add the following paragraphs as the last paragraphs in the second list item starting “The bits b6 and b5 .”: “A PICC or PCD setting (b6,b5) (00)b shall be treated as a protocol error.” INCITS/ISO/IEC 14443-4:2001/Amd.1:20062008 4 ITIC 2008 All rights reserved Page 17, Subc

26、lause 7.1.1.3 “Node address field” Add the following paragraphs after the first paragraph starting “The NAD in the prologue .”: “A PICC or PCD setting b8 0 is not compliant with this standard. b8 0 shall be treated as a protocol error.” Page 18, Subclause 7.2 “Frame waiting time” Add the following p

27、aragraphs as the last paragraphs in the subclause: “The PICC shall not set FWI to the RFU value of 15. Until the RFU value 15 is assigned by ISO, a PCD receiving FWI = 15 should interpret it as FWI = 4. NOTE This clause is added for PCDs compatibility with future PICCs when ISO defines the RFU value

28、 15.” Page 19, Subclause 7.3 “Frame waiting time extension” Add the following paragraphs as the last paragraphs in the first list item starting with “The most significant bits b8 and b7 ”: “A PCD not setting (b8,b7) = (00)b is not compliant with this standard. The PICC shall treat (b8,b7) (00)b as p

29、rotocol error.” Page 19, Subclause 7.3 “Frame waiting time extension” Add the following paragraphs as the last paragraphs in the second list item starting with “The least significant bits b6 to b1 ”: “A PICC setting WTXM = 0 or WTXM = 60-63 is not compliant with this standard. When receiving WTXM =

30、0 or WTXM = 60-63 the PCD shall treat it as a protocol error.” Page 21, Subclause 7.5.3.2 “PICC rules” Add a note after rule D: “NOTE In accordance with 7.5.5, the PICC neither toggles its internal block number nor sends a response block, when an error is detected.” Page 21, Subclause 7.5.3.2 “PICC

31、rules” Add a note after rule E: “NOTE There is no block number toggling when an R(NAK) block is received.” INCITS/ISO/IEC 14443-4:2001/Amd.1:20062008 ITIC 2008 All rights reserved 5 Page 22, Subclause 7.5.4.2 “PCD rules” Add a note after rule 5: “NOTE An R(ACK) block may be sent by the PCD only in c

32、ase of PICC chaining, as the PICC response when receiving an R(ACK) block in other cases is not defined.” Page 22, Subclause 7.5.4.2 “PCD rules” Add a note after rule 6: “NOTE The last I-block re-transmission is not required out of PCD chaining. The PCD may determine the presence of a PICC by sendin

33、g R(NAK) blocks at any time out of chaining (including before sending any I-block) and receiving R(ACK) from the PICC if present.” Page 22, Subclause 7.5.4.3 “PICC rules” Add a note after rule 10: “NOTE If the I-block received is empty then the mandatory I-block sent may either be empty or contain a

34、ny applicative information (e.g. error code).” Page 22, before Subclause 7.5.5 “Error detection and recovery” Add a new subclause: “ 7.5.5 PICC presence check The following methods may be used to check the presence of a PICC at any time out of chaining (including before any I-block exchange). 7.5.5.

35、1 Method 1 The PCD may send an empty I-block and expect to receive an I-block from the PICC. 7.5.5.2 Method 2 Before the first I-block exchange, the PCD may send an R(NAK) block (with block number 0) and expect to receive an R(ACK) block from the PICC (rule 12). After the first I-block exchange, the

36、 PCD may either a) send an R(NAK) block (with current block number) and expect to receive an R(ACK) block from the PICC (rule 12), in which case the PCD should not retransmit its last I-block as mentioned in the note in rule 6; or b) toggle its block number then send an R(NAK) block and expect to re

37、ceive the last I-block from the PICC (rule 11). ” INCITS/ISO/IEC 14443-4:2001/Amd.1:20062008 6 ITIC 2008 All rights reserved Page 22, Subclause 7.5.5 “Error detection and recovery” Renumber the clause to 7.5.6. Add the following subclause title above the line “The following errors shall be detected

38、by the PCD:”: “7.5.6.1 Errors detected by the PCD” Change item a) text as follows: “ a) Transmission error (Frame error or EDC error) or FWT time-out The PCD shall attempt error recovery by the following techniques in the order shown: Application of PCD rules (see 7.5.4.2), Optionally apply PCD rule

39、s (see 7.5.4.2) once more, Use of S(DESELECT) request, Optionally use of S(DESELECT) request once more (as specified in Clause 8.2), Ignore the PICC. ” Page 23, Subclause 7.5.5 “Error detection and recovery” Add the following subclause title above the line “The following errors shall be detected by

40、the PICC:”: “7.5.6.2 Errors detected by the PICC” Page 27, Just before Clause B.3 Add a new subclause: “ B.2.5 PICC Presence check PICC presence check, method 1 Comment Block No. (0) PCD PICC Block No. (1) Comment 1. rule 1, method 1 I(0)0 0 rule D 2. rule B 1 I(0)0 rule 10 note INCITS/ISO/IEC 14443

41、-4:2001/Amd.1:20062008 ITIC 2008 All rights reserved 7 PICC presence check, method 2-a (before first I-block exchange) Comment Block No. (0) PCD PICC Block No. (1) Comment 1. rule 1, method 2-a R(NACK)0 rule E note 2. R(ACK)1 rule 12 3. rule 6 note, method 2-a R(NACK)0 rule E note 4. rule 6 note R(A

42、CK)1 rule 12 5. I(0)0 0 rule D 6. rule B 1 I(0)0 rule 10 PICC presence check, method 2-a Comment Block No. (0) PCD PICC Block No. (1) Comment 1. rule 1 I(0)0 0 rule D 2. rule B 1 I(0)0 rule 10 3. method 2-a R(NACK)1 rule E note 4. rule 6 note R(ACK)0 rule 12 5. I(0)1 1 rule D 6. 0 I(0)1 rule 10 PICC

43、 presence check, method 2-b Comment Block No. (0) PCD PICC Block No. (1) Comment 1. rule 1 I(0)0 0 rule D 2. rule B 1 I(0)0 rule 10 3. method 2-b 0 R(NACK)0 4. rule B 1 I(0)0 rule 11 5. I(0)1 1 rule D 6. rule B 0 I(0)1 rule 10 ” INCITS/ISO/IEC 14443-4:2001/Amd.1:20062008 ICS 35.240.15 Price based on 7 pages ITIC 2008 All rights reserved