Identification cards — Contactless integrated circuit(s) cards — Proximity cards — Part 3: Initialization and anticollision — Amendment 1: Bit rates of fc/64, fc/32 and fc/16

Cartes d'identification — Cartes à circuit(s) intégré(s) sans contact — Cartes de proximité — Partie 3: Initialisation et anticollision — Amendement 1: Débit binaires de fc/64, fc/32 et fc/16

General Information

Status
Withdrawn
Publication Date
14-Jun-2005
Withdrawal Date
14-Jun-2005
Current Stage
9599 - Withdrawal of International Standard
Completion Date
12-Apr-2011
Ref Project

Relations

Buy Standard

Standard
ISO/IEC 14443-3:2001/Amd 1:2005 - Bit rates of fc/64, fc/32 and fc/16
English language
9 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 14443-3
First edition
2001-02-01
AMENDMENT 1
2005-06-01


Identification cards — Contactless
integrated circuit(s) cards — Proximity
cards —
Part 3:
Initialization and anticollision —
AMENDMENT 1: Bit rates of fc/64, fc/32 and
fc/16
Cartes d´identification — Cartes à circuit(s) intégré(s) sans contact —
Cartes de proximité —
Partie 3: Initialisation et anticollision
AMENDEMENT 1: Débits binaires de fc/64, fc/32 et fc/16




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

---------------------- Page: 1 ----------------------
ISO/IEC 14443-3:2001/Amd.1:2005(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 2005
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 copyright@iso.org
Web www.iso.org
Published in Switzerland

ii © ISO/IEC 2005 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 14443-3:2001/Amd.1:2005(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 1 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.

© ISO/IEC 2005 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 14443-3:2001/Amd.1:2005(E)

Identification cards — Contactless integrated circuit(s) cards —
Proximity cards —
Part 3:
Initialization and anticollision
AMENDMENT 1: Bit rates of fc/64, fc/32 and fc/16
Page 2, term number 3.5
Replace the existing definition with the following:
"elementary time unit
etu
time unit calculated by the following formula:
1 etu = 128 / (D x fc)
where
D∈ {1,2,4,8}
fc is the carrier frequency as defined in ISO/IEC 14443-2.
The initial value of the divisor D is 1, giving the initial etu as follows: 1 etu = 128 / fc.
Page 3, Clause 4
Add the following new abbreviations:
"D Divisor
TR2 Frame delay Time PICC to PCD, Type B”
Page 5, Clause 5
Replace the existing Clause 5 title with the following:
"
5 Alternating between Type A and Type B commands,
5.1 Polling
"
© ISO/IEC 2005 – All rights reserved 1

---------------------- Page: 4 ----------------------
ISO/IEC 14443-3:2001/Amd.1:2005(E)
Add the following at the end of the new subclause 5.1:
"EXAMPLE 3 When a PICC Type A is exposed to field activation it shall be able to accept a REQA within 5 ms of
unmodulated operating field.
EXAMPLE 4 When a PICC Type B is exposed to field activation it shall be able to accept a REQB within 5 ms of
unmodulated operating field.
5.2 Influence of Type A commands on PICC Type B operation
A PICC Type B should either go to IDLE state (be able to accept a REQB) or be able to continue a transaction
in progress after receiving any Type A command.
5.3 Influence of Type B commands on PICC Type A operation
A PICC Type A should either go to IDLE state (be able to accept a REQA) or be able to continue a transaction
in progress after receiving any Type B command.
5.4 Transition to Power OFF state
The PICC shall be in the Power OFF state no later than 5 ms after the operating field is switched off."
Page 5, Clause 6
Insert the following new subclause before the existing subclause 6.1 and renumber all subsequent subclauses.
"6.1 Bit rates
Communication between PCD and PICC can be achieved with four different bit rates (see Table Amd.1-1).
Bit rates of fc/64, fc/32 and fc/16 are optional and may be independently supported by PCD and PICC.
Table Amd.1-1 — Bit rates
Divisor D etu Bit rate
128/fc  (~9,4 µs) fc/128 (~106 kbit/s)
1
2 (optional) 128/(2fc)  (~4,7 µs) fc/64 (~212 kbit/s)
128/(4fc)  (~2,4 µs) fc/32 (~424 kbit/s)
4 (optional)
8 (optional) 128/(8fc)  (~1,2 µs) fc/16 (~847 kbit/s)

NOTE The initial bit rate is fc/128. This applies for the whole initialization and anticollision sequence."
2 © ISO/IEC 2005 – All rights reserved

---------------------- Page: 5 ----------------------
ISO/IEC 14443-3:2001/Amd.1:2005(E)
Page 6, subclause 6.1.2 (renumbered to 6.2.2)
Replace Figure 1 with the following:
"
Last data bit transmitted by PCD First modulation of PICC
FDT
1 etu 2 etu
logic "1" End of communication Start of
(E) communication (S)
FDT
1 etu 2 etu
Start of
logic "0" End of communication
communication (S)
(E)

Figure 1 — Frame delay time PCD to PICC"
Replace Table 1 and the last two sentences of subclause 6.1.2 (renumbered to 6.2.2) with the following:
"Table 1 — Frame delay time PCD to PICC
Command type n (integer value) FDT
last bit = (1)b last bit = (0)b

REQA Command 9 (n*128+84)/fc (n*128+20)/fc
WUPA Command
[ = 1236/fc ] [ = 1172/fc ]
ANTICOLLISION Command
SELECT Command
All other commands at bit rates
PCD to PICC PICC to PCD
fc/128 (n*128+84)/fc (n*128+20)/fc
≥ 9
fc/128
fc/64 (n*128+148)/fc (n*128+116)/fc
≥ 8
fc/32 (n*128+116)/fc (n*128+100)/fc
≥ 8
fc/16 (n*128+100)/fc (n*128+92)/fc
≥ 8
fc/128 or fc/64 or fc/32 fc/64 or fc/32 or fc/
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.