Identification cards — Contactless integrated circuit cards — Proximity cards — Part 4: Transmission protocol

ISO/IEC 14443 is one of a series of International Standards describing the parameters for identification cards as defined in ISO/IEC 7810, and the use of such cards for international interchange. ISO/IEC 14443-4:2008 specifies a half-duplex block transmission protocol featuring the special needs of a contactless environment and defines the activation and deactivation sequence of the protocol. ISO/IEC 14443-4:2008 is intended to be used in conjunction with other parts of ISO/IEC 14443 and is applicable to proximity cards or objects of Type A and Type B.

Cartes d'identification — Cartes à circuit(s) intégré(s) sans contact — Cartes de proximité — Partie 4: Protocole de transmission

General Information

Status
Withdrawn
Publication Date
06-Jul-2008
Withdrawal Date
06-Jul-2008
Current Stage
9599 - Withdrawal of International Standard
Completion Date
27-May-2016
Ref Project

Relations

Buy Standard

Standard
ISO/IEC 14443-4:2008 - Identification cards -- Contactless integrated circuit cards -- Proximity cards
English language
37 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 14443-4
Second edition
2008-07-15

Identification cards — Contactless
integrated circuit cards — Proximity
cards —
Part 4:
Transmission protocol
Cartes d'identification — Cartes à circuit(s) intégré(s) sans contact —
Cartes de proximité —
Partie 4: Protocole de transmission




Reference number
ISO/IEC 14443-4:2008(E)
©
ISO/IEC 2008

---------------------- Page: 1 ----------------------
ISO/IEC 14443-4:2008(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.


COPYRIGHT PROTECTED DOCUMENT


©  ISO/IEC 2008
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 2008 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 14443-4:2008(E)
Contents Page
Foreword. v
Introduction . vi
1 Scope. 1
2 Normative references. 1
3 Terms and definitions. 1
4 Symbols and abbreviated terms . 2
5 Protocol activation of PICC Type A . 4
5.1 Request for answer to select. 5
5.2 Answer to select . 6
5.2.1 Structure of the bytes. 7
5.2.2 Length byte. 7
5.2.3 Format byte . 7
5.2.4 Interface byte TA(1) . 8
5.2.5 Interface byte TB(1) . 9
5.2.6 Interface byte TC(1) . 9
5.2.7 Historical bytes. 10
5.3 Protocol and parameter selection request. 10
5.3.1 Start byte. 10
5.3.2 Parameter 0. 11
5.3.3 Parameter 1. 11
5.4 Protocol and parameter selection response. 12
5.5 Activation frame waiting time. 12
5.6 Error detection and recovery. 12
5.6.1 Handling of RATS and ATS. 12
5.6.2 Handling of PPS request and PPS response . 13
5.6.3 Handling of the CID during activation . 13
6 Protocol activation of PICC Type B . 14
7 Half-duplex block transmission protocol. 14
7.1 Block format. 14
7.1.1 Prologue field . 15
7.1.2 Information field. 18
7.1.3 Epilogue field. 18
7.2 Frame waiting time . 18
7.3 Frame waiting time extension . 18
7.4 Power level indication . 19
7.5 Protocol operation. 20
7.5.1 Multi-Activation. 20
7.5.2 Chaining. 20
7.5.3 Block numbering rules. 21
7.5.4 Block handling rules. 22
7.5.5 PICC presence check. 23
7.5.6 Error detection and recovery. 23
8 Protocol deactivation of PICC Type A and Type B. 24
8.1 Deactivation frame waiting time. 24
8.2 Error detection and recovery. 24
Annex A (informative) Multi-Activation example. 25
© ISO/IEC 2008 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 14443-4:2008(E)
Annex B (informative) Protocol scenarios . 26
B.1 Notation. 26
B.2 Error-free operation. 26
B.2.1 Exchange of I-blocks . 26
B.2.2 Request for waiting time extension . 27
B.2.3 DESELECT. 27
B.2.4 Chaining. 27
B.2.5 PICC Presence check . 28
B.3 Error handling. 29
B.3.1 Exchange of I-blocks . 29
B.3.2 Request for waiting time extension . 30
B.3.3 DESELECT. 32
B.3.4 Chaining. 32
Annex C (informative) Block and frame coding overview . 35
Bibliography . 37

iv © ISO/IEC 2008 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC 14443-4:2008(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.
ISO/IEC 14443-4 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 17, Cards and personal identification.
This second edition cancels and replaces the first edition (ISO/IEC 14443-4:2001). It also incorporates the
Amendment ISO/IEC 14443-4:2001/Amd.1:2006.
ISO/IEC 14443 consists of the following parts, under the general title Identification cards — Contactless
integrated circuit cards — Proximity cards:
⎯ Part 1: Physical characteristics
⎯ Part 2: Radio frequency power and signal interface
⎯ Part 3: Initialization and anticollision
⎯ Part 4: Transmission protocol

© ISO/IEC 2008 – All rights reserved v

---------------------- Page: 5 ----------------------
ISO/IEC 14443-4:2008(E)
Introduction
ISO/IEC 14443 is one of a series of International Standards describing the parameters for identification cards
as defined in ISO/IEC 7810, and the use of such cards for international interchange.
The protocol as defined in this part of ISO/IEC 14443 is capable of transferring the application protocol data
units as defined in ISO/IEC 7816-4. Thus, application protocol data units may be mapped as defined in
ISO/IEC 7816-4 and application selection may be used as defined ISO/IEC 7816-5.
ISO/IEC 14443 is intended to allow operation of proximity cards in the presence of other contactless cards
conforming to ISO/IEC 10536 and ISO/IEC 15693 and Near Field Communication (NFC) devices conforming
to ISO/IEC 18092 and ISO/IEC 21481.
The International Organization for Standardization (ISO) and International Electrotechnical Commission (IEC)
draw attention to the fact that it is claimed that compliance with this document may involve the use of patents.
ISO and IEC take no position concerning the evidence, validity and scope of these patent rights.
The holders of these patent rights have assured ISO and IEC that they are willing to negotiate licences under
reasonable and non-discriminatory terms and conditions with applicants throughout the world. In this respect,
the statements of the holders of these patent rights are registered with the ISO and IEC. Information may be
obtained from:
US Patent US5359323 FRANCE TELECOM
Centre National d’Études des Télécommunications
38-40 rue de Général Leclerc
92794 Issy-les-Moulineaux
Cedex 9
France
MOTOROLA
Motorola ESG
207 route de Ferney
P O Box 15
1218 Grand-Saconnex
Geneva
Switzerland
JP 2129209, JP 2561051, JP 2981517 OMRON
Intellectual Property Department
Law & Intellectual Property H.Q.
Contactless Responding Unit
20, Igadera Shimokaiinji
Nagaokakyo City
Kyoto 617-8510
Japan
Patent EP 0 492 569 B1 ON-TRACK INNOVATIONS
Z.H.R. Industrial Zone
P O Box 32
A system and method for the non-contact
Rosh-Pina 12000
transmission of data

Israel
vi © ISO/IEC 2008 – All rights reserved

---------------------- Page: 6 ----------------------
ISO/IEC 14443-4:2008(E)
The following companies may hold patents relating to this document but have not provided details of the
patents or agreed to provide licences.
US 4 650 981 WAYNE S FOLETTA
CA 95129, USA
4760 Castlewood Drive
San Jose, California CA 9512
USA
US Patent No. 4, 661,691 JOHN W HALPERN
C/O Vincent M DeLuca
Rothwell, Figg, Ernst & Kurz, p.c.
555 Thirteenth Street, N.W.
Suite 701 East Tower
Washington, D.C. 20004
WO 89 05549 A MAGELLAN CORPORATION
8717 Research Drive
Irvine
CA 92618
USA
Attention is drawn to the possibility that some of the elements of this part of ISO/IEC 14443 may be the
subject of patent rights other than those identified above. ISO and IEC shall not be held responsible for
identifying any or all such patent rights.

© ISO/IEC 2008 – All rights reserved vii

---------------------- Page: 7 ----------------------
INTERNATIONAL STANDARD ISO/IEC 14443-4:2008(E)

Identification cards — Contactless integrated circuit cards —
Proximity cards —
Part 4:
Transmission protocol
1 Scope
This part of ISO/IEC 14443 specifies a half-duplex block transmission protocol featuring the special needs of a
contactless environment and defines the activation and deactivation sequence of the protocol.
This part of ISO/IEC 14443 is intended to be used in conjunction with other parts of ISO/IEC 14443 and is
applicable to proximity cards or objects of Type A and Type B.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO/IEC 7816-3, Identification cards — Integrated circuit cards — Part 3: Cards with contacts — Electrical
interface and transmission protocols
ISO/IEC 7816-4, Identification cards — Integrated circuit cards — Part 4: Organization, security and commands
for interchange
ISO/IEC 14443-2, Identification cards — Contactless integrated circuit cards — Proximity cards — Part 2:
Radio frequency power and signal interface
ISO/IEC 14443-3, Identification cards — Contactless integrated circuit cards — Proximity cards — Part 3:
Initialization and anticollision
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
bit duration
one elementary time unit (etu), calculated by the following formula:
1 etu = 128 / (D x fc)
the initial value of the divisor D is 1, giving the initial etu as follows:
1 etu = 128 / fc
where fc is the carrier frequency as defined in ISO/IEC 14443-2.
© ISO/IEC 2008 – All rights reserved 1

---------------------- Page: 8 ----------------------
ISO/IEC 14443-4:2008(E)
3.2
block
special type of frame, which contains a valid protocol data format
NOTE A valid protocol data format includes I-blocks, R-blocks or S-blocks.
3.3
invalid block
type of frame, which contains an invalid protocol format
NOTE A time-out, when no frame has been received, is not interpreted as an invalid block.
3.4
frame
sequence of bits as defined in ISO/IEC 14443-3
NOTE The PICC Type A uses the standard frame defined for Type A and the PICC Type B uses the frame defined
for Type B.
4 Symbols and abbreviated terms
ACK positive ACKnowledgement
ATS  Answer To Select
ATQA Answer To reQuest, Type A
ATQB Answer To reQuest, Type B
CID  Card IDentifier
CRC Cyclic Redundancy Check, as defined for each PICC Type in ISO/IEC 14443-3
CRC1 most significant byte of CRC (b16 to b9)
CRC2 least significant byte of CRC (b8 to b1)
D  Divisor
DR  Divisor Receive (PCD to PICC)
DRI  Divisor Receive Integer (PCD to PICC)
DS  Divisor Send (PICC to PCD)
DSI  Divisor Send Integer (PICC to PCD)
EDC Error Detection Code
etu  elementary time unit
fc  carrier frequency
FSC Frame Size for proximity Card
FSCI Frame Size for proximity Card Integer
FSD Frame Size for proximity coupling Device
2 © ISO/IEC 2008 – All rights reserved

---------------------- Page: 9 ----------------------
ISO/IEC 14443-4:2008(E)
FSDI Frame Size for proximity coupling Device Integer
FWI  Frame Waiting time Integer
FWT Frame Waiting Time
FWT temporary Frame Waiting Time
TEMP
HLTA HALT command, Type A
I-block Information block
INF  INformation Field
MAX index to define a maximum value
MIN  index to define a minimum value
NAD Node ADdress
NAK Negative AcKnowledgement
OSI  Open Systems Interconnection
PCB Protocol Control Byte
PCD Proximity Coupling Device
PICC proximity card or object
PPS Protocol and Parameter Selection
PPSS Protocol and Parameter Selection Start
PPS0 Protocol and Parameter Selection parameter 0
PPS1 Protocol and Parameter Selection parameter 1
R-block Receive ready block
R(ACK) R-block containing a positive acknowledge
R(NAK) R-block containing a negative acknowledge
RATS Request for Answer To Select
REQA REQuest Command, Type A
RFU Reserved for Future Use by ISO/IEC
S-block Supervisory block
SAK Select AcKnowledge
SFGI Start-up Frame Guard time Integer
SFGT  Start-up Frame Guard Time
WUPA Wake-UP command, Type A
© ISO/IEC 2008 – All rights reserved 3

---------------------- Page: 10 ----------------------
ISO/IEC 14443-4:2008(E)
WTX Waiting Time eXtension
WTXM Waiting Time eXtension Multiplier
For the purposes of this document, the following notation applies:
⎯ (xxxxx)b Data bit representation;
⎯ ‘XY’ Hexadecimal notation, equal to XY to the base 16.
5 Protocol activation of PICC Type A
The following activation sequence shall be applied:
⎯ PICC activation sequence as defined in ISO/IEC 14443-3 (request, anticollision loop and select).
⎯ The SAK byte shall be checked for availability of an ATS. The SAK is defined in ISO/IEC 14443-3.
⎯ The PICC may be set to HALT state, using the HLTA Command as defined in ISO/IEC 14443-3, if no
ATS is available.
⎯ The RATS may be sent by the PCD as next command after receiving the SAK if an ATS is available.
⎯ The PICC shall send its ATS as answer to the RATS. The PICC shall only answer to the RATS if the
RATS is received directly after the selection.
⎯ If the PICC supports any changeable parameters in the ATS, a PPS request may be used by the PCD as
the next command after receiving the ATS to change parameters.
⎯ The PICC shall send a PPS Response as answer to the PPS request.
A PICC does not need to implement the PPS, if it does not support any changeable parameters in the ATS.
The PCD activation sequence for a PICC Type A is shown in Figure 1.
4 © ISO/IEC 2008 – All rights reserved

---------------------- Page: 11 ----------------------
ISO/IEC 14443-4:2008(E)

Field On
Send REQA
Receive ATQA Send WUPA
Send HLTA
Anticollision
loop
Non
ATS
no
ISO/IEC 14443-4
 available?
protocol
yes
Use
no
ISO/IEC14443-4
 protocol?
yes
Send RATS Receive DESELECT Response
Receive ATS Send DESELECT Request
yes
PPS
supported?
no
yes
Parameter
change?
Send PPS Request
no
Receive PPS Response
Exchange
Transparent Data

Figure 1 — Activation of a PICC Type A by a PCD
5.1 Request for answer to select
This clause defines the RATS with all its fields (see Figure 2).
Start byte
'E0'
Parameter byte
Parameter
. . . . codes FSDI and CID
CRC1
CRC2

Figure 2 — Request for answer to select
The parameter byte consists of two parts (see Figure 3):
⎯ The most significant half-byte b8 to b5 is called FSDI and codes FSD. The FSD defines the maximum
size of a frame the PCD is able to receive. The coding of FSD is given in Table 1.
© ISO/IEC 2008 – All rights reserved 5
ISO/IEC 14443-4 ISO/IEC 14443-3

---------------------- Page: 12 ----------------------
ISO/IEC 14443-4:2008(E)
⎯ 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).
⎯ The least significant half byte b4 to b1 is named CID and it defines the logical number of the addressed
PICC in the range from 0 to 14. The value 15 is RFU. The CID is specified by the PCD and shall be
unique for all PICCs, which are in the ACTIVE state at the same time. The CID is fixed for the time the
PICC is active and the PICC shall use the CID as its logical identifier, which is contained in the first error-
free RATS received.
⎯ A PCD setting CID = 15 is not compliant with this standard. For PICC behaviour see 5.6.1.2 (c).

b8 b7 b6 b5 b4 b3 b2 b1
CID
FSDI

Figure 3 — Coding of RATS parameter byte

Table 1 — FSDI to FSD conversion
FSDI ‘0’ ‘1’ ‘2’ ‘3’ ‘4’ ‘5’ ‘6’ ‘7’ ‘8’ ‘9’-‘F’
FSD 16 24 32 40 48 64 96 128 256 RFU
(bytes)

5.2 Answer to select
This clause defines the ATS with all its available fields (see Figure 4).
In the case that one of the defined fields is not present in an ATS sent by a PICC the default values for that
field shall apply.
6 © ISO/IEC 2008 – All rights reserved

---------------------- Page: 13 ----------------------
ISO/IEC 14443-4:2008(E)
Length byte

TL
Format byte
T0
. . . . codes Y(1) and FSCI
Interface bytes
TA(1)
. . . . codes DS and DR
TB(1)
. . . . codes FWI and SFGI
TC(1)
. . . . codes protocol options
Historical bytes
T1
Tk
CRC1
CRC2

Figure 4 — Structure of the ATS
5.2.1 Structure of the bytes
The length byte TL is followed by a variable number of optional subsequent bytes in the following order:
⎯ format byte T0,
⎯ interface bytes TA(1), TB(1), TC(1) and
⎯ historical bytes T1 to Tk.
5.2.2 Length byte
The length byte TL is mandatory and specifies the length of the transmitted ATS including itself. The two CRC
bytes are not included in TL. The maximum size of the ATS shall not exceed the indicated FSD. Therefore the
maximum value of TL shall not exceed FSD-2.
5.2.3 Format byte
The format byte T0 is optional and is present as soon as the length is greater than 1. The ATS can only
contain the following optional bytes when this format byte is present.
T0 consists of three parts (see Figure 5):
⎯ The most significant bit b8 shall be set to 0. The value 1 is RFU.
⎯ The bits b7 to b5 contain Y(1) indicating the presence of subsequent interface bytes TC(1), TB(1) and
TA(1).
⎯ The least significant half byte b4 to b1 is called FSCI and codes FSC. The FSC defines the maximum
size of a frame accepted by the PICC. The default value of FSCI is 2 and leads to a FSC of 32 bytes. The
coding of FSC is equal to the coding of FSD (see Table 1).
© ISO/IEC 2008 – All rights reserved 7

---------------------- Page: 14 ----------------------
ISO/IEC 14443-4:2008(E)
⎯ A PICC setting FSCI = '9'-'F' is not compliant with this standard. A received value of FSCI = '9'-'F' should
be interpreted 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.

b8 b7 b6 b5 b4 b3 b2 b1
0
FSCI
TA(1) is transmitted, if bit is set to 1
TB(1) is transmitted, if bit is set to 1 Y(1)
TC(1) is transmitted , if bit is set to 1
shall be set to 0, 1 is RFU

Figure 5 — Coding of format byte
5.2.4 Interface byte TA(1)
The interface byte TA(1) consists of four parts (see Figure 6):
⎯ The most significant bit b8 codes the possibility to handle different divisors for each direction. When this
bit is set to 1 the PICC is unable to handle different divisors for each direction.
⎯ The bits b7 to b5 code the bit rate capability of the PICC for the direction from PICC to PCD, called DS.
The default value shall be (000)b.
⎯ The bit b4 shall be set to (0)b and the other value is RFU.
⎯ The bits b3 to b1 code the bit rate capability of the PICC for the direction from PCD to PICC, called DR.
The default value shall be (000)b.

b8 b7 b6 b5 b4 b3 b2 b1
0
DR=2 supported, if bit is set to 1
DR=4 supported, if bit is set to 1
DR=8 supported, if bit is set to 1
shall be set to 0, 1 is RFU
DS=2 supported, if bit is set to 1
DS=4 supported, if bit is set to 1
DS=8 supported, if bit is set to 1
Only the same D for both directions supported , if
bit is set to 1
Different D for each direction
supported, if bit is set to 0

Figure 6 — Coding of interface byte TA(1)
The selection of a specific divisor D for each direction may be done by the PCD using a PPS.
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).
8 © ISO/IEC 2008 – All rights reserved

---------------------- Page: 15 ----------------------
ISO/IEC 14443-4:2008(E)
5.2.5 Interface byte TB(1)
The interface byte TB(1) conveys information to define the frame waiting time and the start-up frame guard
time.
The interface byte TB(1) consists of two parts (see Figure 7):
⎯ The most significant half-byte b8 to b5 is called FWI and codes FWT (see 7.2).
⎯ The least significant half byte b4 to b1 is called SFGI and codes a multiplier value used to define the
SFGT. The SFGT defines a specific guard time needed by the PICC before it is ready to receive the next
frame after it has sent the ATS. SFGI is coded in the range from 0 to 14. The value of 15 is RFU. The
value of 0 indicates no SFGT needed and the values in the range from 1 to 14 are used to calculate the
SFGT with the formula given below. The default value of SFGI is 0.
b8 b7 b6 b5 b4 b3 b2 b1
SFGI
FWI

Figure 7 — Coding of interface byte TB(1)
SFGT is calculated by the following formula:
SFGI
SFGT = (256 x 16 / fc) x 2
SFGT = minimum value of the frame delay time as defined in ISO/IEC 14443-3
MIN
SFGT = minimum value of the frame delay time as defined in ISO/IEC 14443-3
DEFAULT
14
SFGT = (256 x 16 / fc) x 2 (~4949 ms)
MAX
A PICC setting SFGI = 15 is not compliant with this standard. Until the RFU value 15 is assigned by ISO/IEC,
a PCD receiving SFGI = 15 should interpret it as SFGI = 0.
A PICC setting FWI = 15 is not compliant with this standard. Until the RFU value 15 is assigned by ISO/IEC, a
PCD receiving FWI = 15 should interpret it as FWI = 4.
5.2.6 Interface byte TC(1)
The interface byte TC(1) specifies a parameter of the protocol.
The specific interface byte TC(1) consists of two parts (see Figure 8):
⎯ The most
...

Questions, Comments and Discussion

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