Version 1.1

Proximity Communication Interface Implementation Specifications

Version 1.1

JULY 2001
New Media Development Association(foundational juridical person)

Version 1.1

Foreword
The New Media Development Association has developed a "Development of Platform for New
Generation Smart Card Systems" based on an innovative architecture that is able to accommodate newfunctional requirements and diverse security levels with the aim of systematically integrating the various
card specifications in existence at present as a part of the "Industrial and Social Information
Infrastructure Development Project" implemented by the Japan Information Processing Development
Corporation in accordance with the third supplementary budget for the 1998 fiscal year. Thisdevelopment was carried out with particular focus on contactless IC cards --- proximity cards (PICC) as
defined in ISO/IEC 14443 for which popularity is expected to grow in a wide range of IC card
applications in the future. The "Proximity Communications Interface Implementation Specification"(Version 1.0) were released in December 2000 in the form of a disclosed technical reference thatsummarized the results of studies for improving compatibility between PICC and proximity coupling
devices (PCD) based on experience acquired during the course of their development.
This specification is a revised version of the previous version 1.0. The following factors were taken
into consideration in the production of this revised edition.
- Although Version 1.0 was produced on the basis of the latest documents available relating to
ISO/IEC 14443 as of March 2000, since that time, work at ISO have progressed, and with some
exceptions, were released in the form of ISO standards. It was therefore necessary to achieve
compatibility with these ISO standards.
- Following the release of Version 1.0, requests were made from various fields asking for
implementation specifications for PCD (open PCD) that will enable the operation of placing or
holding up a card. Implementation specifications were therefore added or reviewed in order to
respond to these needs.
We hope that this specification will assist in the future proliferation of IC cards and IC card systems.
Furthermore, be aware of the following when referring to or using these specifications.
- The functions, testing methods and so forth specified in these specifications are subject to addition,
revision, alteration or deletion during the course of substantiative testing and other efforts scheduled
to be conducted in the future by this association.
- This association is not responsible in any way for the contents of these specifications or the resultsof their use, including industrial property rights and so forth.
In conclusion, the association would like to express its deep appreciation to the RW compatibility
verification work group (located within the New Media Development Association) for its numerous
contributions and constructive discussions, and to those persons at the Ministry of Economics, Trade andIndustry for their generous support of those efforts pertaining to the production of these specifications.
July 2001
New Media Development Association

Version 1.1

Table of contents

1.
2.

3.
4.

5.

6.

7.

8.

SYSTEM OVERVIEW ................................................................................................................... 1
DESIGN GUIDELINES .................................................................................................................. 2
2.1

INTRODUCTION ................................................................................................................ 2

2.2

CHARACTERISTICS OF ASSUMED PICC AND PCD............................................................ 3

2.3

CHARACTERISTICS OF THIS IMPLEMENTATION SPECIFICATION ...................................... 5

2.4

DOMESTIC RADIO LAW ..................................................................................................... 7

2.5

CITED STANDARDS ........................................................................................................... 8

2.6

OTHERS ............................................................................................................................ 9

COMPONENTS .......................................................................................................................... 10
USAGE CONDITIONS ................................................................................................................ 13
4.1

BASIC GUIDELINES ........................................................................................................ 13

4.2

BASIC CONDITIONS ........................................................................................................ 14

CARD ANTENNA CHARACTERISTICS ........................................................................................ 16
5.1

ANTENNA SHAPE ............................................................................................................ 16

5.2

ANTENNA RESISTANCE VALUE ....................................................................................... 17

5.3

INDUCTANCE .................................................................................................................. 18

5.4

RESONANCE FREQUENCY .............................................................................................. 19

5.5

MATERIAL AND PRODUCTION METHOD ......................................................................... 20

CARD IC CHARACTERISTICS.................................................................................................... 21
6.1

OPERATING POWER ........................................................................................................ 21

6.2

INPUT SIGNAL ................................................................................................................ 24

6.3

OUTPUT SIGNAL ............................................................................................................. 25

PCD ANTENNA CHARACTERISTICS .......................................................................................... 26
7.1

ANTENNA POSITION ....................................................................................................... 26

7.2

ANTENNA SHAPE ............................................................................................................ 27

7.3

ANTENNA RESISTANCE VALUE ....................................................................................... 28

7.4

INDUCTANCE .................................................................................................................. 29

7.5

RESONANCE FREQUENCY .............................................................................................. 30

7.6

MATERIAL AND PRODUCTION METHOD ......................................................................... 31

POWER TRANSMISSION ............................................................................................................ 32
8.1

FREQUENCY ................................................................................................................... 32

8.2
OPERATING MAGNETIC FIELD ....................................................................................... 33
8.2.1
PICC Operating Magnetic Field ........................................................................... 33
8.2.2
PCD Generated Magnetic Field ............................................................................ 34

9.

COMMUNICATION PCD TO PICC ............................................................................................. 35
9.1
COMMUNICATION SIGNAL INTERFACE TYPE A .............................................................. 35
9.1.1
Bit Rate .................................................................................................................. 35
9.1.2
Modulation ............................................................................................................. 36
9.1.3
Bit Representation and Coding............................................................................. 39iVersion 1.1

9.2
COMMUNICATION SIGNAL INTERFACE TYPE B .............................................................. 40
9.2.1
Bit Rate .................................................................................................................. 40
9.2.2
Modulation ............................................................................................................. 41
9.2.3
Bit Representation and Coding............................................................................. 42

10.

COMMUNICATION PICC TO PCD .......................................................................................... 43

10.1 COMMUNICATION SIGNAL INTERFACE TYPE A .............................................................. 43
10.1.1 Bit Rate .................................................................................................................. 43
10.1.2 Load Modulation.................................................................................................... 44
10.1.3 Subcarrier .............................................................................................................. 45
10.1.4 Subcarrier Modulation Method............................................................................. 46
10.1.5 Bit Representation and Coding............................................................................. 47
10.2 COMMUNICATION SIGNAL INTERFACE TYPE B .............................................................. 48
10.2.1 Bit Rate .................................................................................................................. 48
10.2.2 Load Modulation.................................................................................................... 49
10.2.3 Subcarrier .............................................................................................................. 50
10.2.4 Subcarrier Modulation .......................................................................................... 51
10.2.5 Bit Representation and Coding............................................................................. 52

11.
12.

POLLING ............................................................................................................................... 53
ANTICOLLISION .................................................................................................................... 55

12.1 TYPE A-INITIALIZATION AND ANTICOLLISION ................................................................ 59
12.1.1 Frame Format and Timing.................................................................................... 59
12.1.2 PICC States............................................................................................................ 70
12.1.3 Command Set......................................................................................................... 80
12.1.4 Select Sequence ..................................................................................................... 84
12.2 TYPE B - INITIALIZATION AND ANTICOLLISON ............................................................... 99
12.2.1 Character, Frame Format and Timing ................................................................. 99
12.2.2 Cyclic Redundancy Check Code (CRC_B) .......................................................... 107
12.2.3 Anticollision Sequence......................................................................................... 108
12.2.4 PICC States Description ..................................................................................... 109
12.2.5 Command Set....................................................................................................... 119
12.2.6 Anticollision Response Rules .............................................................................. 120
12.2.7 REQB/WUPB Command ..................................................................................... 122
12.2.8 Slot Marker Command (Slot_MARKER)............................................................ 129
12.2.9 Answer to Request (ATQB) ................................................................................. 132
12.2.10 ATTRIB Command........................................................................................... 140
12.2.11
Answer to ATTRIB Command ......................................................................... 149
12.2.12 HLTB Command and Answer.......................................................................... 151
12.3 COMMUNICATION EXAMPLE TYPE A ............................................................................ 152
12.3.1 Overview of Communication Example of Bit Frame Anticollision Processing 152
12.3.2 Explanation of Selection Processing of Bit Frame Anticollision ....................... 155
12.4 CRC_A AND CRC_B ENCODING .................................................................................. 158
12.4.1 CRC_A Encoding.................................................................................................. 158
12.4.2 CRC_B Encoding ................................................................................................. 161
12.4.3 Code Sample Written in C Language for CRC Calculation............................... 165
ii

Version 1.1

12.5 TYPE A TIMESLOT - INITIALIZATION AND ANTICOLLISION .......................................... 168
12.5.1 Bit, Byte and Frame Format............................................................................... 169
12.5.2 PICC States.......................................................................................................... 171
12.5.3 Command/Response Sets .................................................................................... 176
12.5.4 Time Slot Type Anticollision Processing............................................................. 179
12.6

13.

EXAMPLE OF ANTICOLLISION SEQUENCE FOR TYPE B ................................................ 182

TRANSMISSION PROTOCOL ................................................................................................. 187

13.1 PROTOCOL ACTIVATION OF PICC TYPE A .................................................................... 190
13.1.1 Request for Answer to Select .............................................................................. 193
13.1.2 Answer to Select (ATS)........................................................................................ 195
13.1.3 Protocol and Parameter Selection Request ........................................................ 203
13.1.4 Protocol and Parameter Selection Response...................................................... 207
13.1.5 Activation Frame Waiting Time ......................................................................... 208
13.1.6 Error Detection and Recovery............................................................................. 209
13.2

PROTOCOL ACTIVATION OF PICC TYPE B .................................................................... 212

13.3 HALF-DUPLEX BLOCK TRANSMISSION PROTOCOL ....................................................... 213
13.3.1 Block Format ....................................................................................................... 214
13.3.2 Frame Waiting Time (FWT) ................................................................................ 221
13.3.3 Power Level Indication........................................................................................ 224
13.3.4 Protocol Operation............................................................................................... 225
13.4 PROTOCOL DEACTIVATION OF PICC TYPE A AND TYPE B ........................................... 233
13.4.1 Deactivation Frame Waiting Time ..................................................................... 234
13.4.2 Error Detection and Recovery............................................................................. 235
13.5

MULTI-ACTIVATION EXAMPLE ..................................................................................... 236

13.6 PROTOCOL SCENARIOS ................................................................................................. 237
13.6.1 Error-free Operation............................................................................................ 239
13.6.2 Error handling ..................................................................................................... 243
13.7

BLOCK AND FRAME CODING OVERVIEW ...................................................................... 252

13.8 T=1 PROTOCOL USAGE SPECIFICATIONS ..................................................................... 254
13.8.1 PICC Activation ................................................................................................... 255
13.8.2 Protocol Processing.............................................................................................. 257
13.9

14.
14.1

TRANSMISSION CONTROL MATRIX OF T=CL PROTOCOL (REFERENCE) ...................... 263

CARD TEST METHODS ........................................................................................................ 267
TEST ENVIRONMENT .................................................................................................... 267

14.2 TEST APPARATUS.......................................................................................................... 268
14.2.1 Calibration Coil ................................................................................................... 269
14.2.2 Test PCD .............................................................................................................. 273
14.2.3 Test PCD-S ........................................................................................................... 285
14.2.4 Digital Sampling Oscilloscope............................................................................. 289
14.3 TEST METHODS ............................................................................................................ 290
14.3.1 Testing Using Test PCD ...................................................................................... 290
14.3.2 Testing Using Test PCD-S ................................................................................... 298

15.

PCD TEST METHODS .......................................................................................................... 299
iii

Version 1.1

15.1

TEST ENVIRONMENT .................................................................................................... 299

15.2 TEST APPARATUS.......................................................................................................... 300
15.2.1 Reference PICC.................................................................................................... 301
15.3 TEST METHODS ............................................................................................................ 312
15.3.1 Magnetic Field Strength ..................................................................................... 312
15.3.2 Power Transmission Test .................................................................................... 316
15.3.3 Modulation Waveform ......................................................................................... 318
15.3.4 Reception Ability of Load Modulation Signal..................................................... 320

16.
16.1

EXTERNAL COMMUNICATION PROTOCOL............................................................................ 322
PHYSICAL INTERFACE .................................................................................................. 322

16.2 BLOCK FORMAT ............................................................................................................ 324
16.2.1 RCB (Required).................................................................................................... 325
16.2.2 LEN (Required).................................................................................................... 326
16.2.3 DAT (Optional)..................................................................................................... 327
16.2.4 BCC (Required).................................................................................................... 328
16.3 COMMUNICATION TIME SPECIFICATIONS .................................................................... 329
16.3.1 Character Waiting Time (CWT) .......................................................................... 330
16.3.2 Block Guard Time (BGT)..................................................................................... 331
16.3.3 Block Waiting Time (BWT) ................................................................................. 332
16.4 COMMUNICATION ERROR PROCESSING ....................................................................... 333
16.4.1 PCD Communication Error Processing .............................................................. 333
16.4.2 Upper Device Communication Error Processing ............................................... 335
16.5 COMMANDS AND RESPONSES ....................................................................................... 337
16.5.1 Commands and Response for PICC .................................................................... 337
16.5.2 Summary of Commands and Responses for PCD .............................................. 340
16.5.3 Details of Commands and Responses for PCD................................................... 344
16.6 REFERENCE INFORMATION .......................................................................................... 377
16.6.1 Normal Communication Sequence Examples .................................................... 377
16.6.2 Abnormal Communication Sequence Example.................................................. 382

17.
COMPATIBILITY TEST METHOD ........................................................................................... 388[REFERENCE] EXAMPLE OF COMPATIBILITY VERIFICATION SHEET ................................................ 390

iv

Version 1.1

1.

System Overview

These proximity communication interface implementation specification define specifications andstandards that supplement ISO/IEC 14443-2, 3 and 4 with respect to functions pertaining to contactlesscommunication between the PICC and PCD. Therefore, these specifications attempt to ensureinteroperability and compatibility of various types of PICCs and PCDs of numerous manufacturers byserving to standardize antenna characteristics, resonance characteristics and various other parameters at
the production level not defined by ISO.
These implementation specifications apply to PICC based on the radio wave interface type of ASK 100%modulation type A or ASK 10% modulation type B as indicated in ISO/IEC 14443-2 as well as PCD
capable of operating both of these cards.
The range over which this implementation specification are applicable is shown in "Fig. 1-1 Target of
Proximity Communication Interface Implementation Specifications".

Target of Implementation Specifications

Card
platform

Fig. 1-1

Proximity

Proximity IC

coupling

cards

devices

IC cardsystemTarget of Proximity Communication Interface Implementation Specifications

1

Version 1.1

2.

Design Guidelines

2.1

Introduction
Proximity communication interface implementation standards are produced to ensureinteroperability and compatibility between PICC and PCD under specific usage conditions
indicated in "4. Usage Conditions". These are discussed in ISO/IEC specifications (ISO/IEC
14443 PICC Specifications) so as not to inhibit the extendability and diversity of usage conditions.
Accordingly, it is necessary to add to and alter ISO/IEC specifications in order to ensurecompatibility based on the premise of certain specific usage conditions.
To begin with, in this implementation specification, ISO/IEC specifications are defined anddescribed as "Basic Specifications" in the sense of serving as the basis of this implementation
specification.
Next, specifications that are added in the form of implementation specifications are defined anddescribed as "Extended Specifications" in the sense of being an extension to the basic
specifications.
Moreover, those specifications not included in "basic specifications" or "extended specifications"for which implementation is preferable but not required are defined and described as "References".

2

Version 1.1

2.2

Characteristics of Assumed PICC and PCD
The IC card systems assumed in these implementation specifications are characterized byenhanced security functions for which there are new needs with respect to PICC. Consequently, it
is necessary to consider the matters indicated below.

(1) PICC Equipped with an Encryption Coprocessor
When implementing encryption processing such as public key encryption (ex. RSA) within an IC
card, the current technology calls for an independent encryption coprocessor within the card IC forprocessing. This IC requires power consumption of roughly 50 mW or more. In this case, it isestimated that at least 100 mW will be required for the output of the PCD.
While a communication distance of about 10 cm is said to be required in the case of ticket gates oftransportation means, it is not easy to achieve this communication distance with a PICC having
power consumption of 50 mW or more. However, since there is a considerable likelihood that IC
power consumption will be reduced and revisions will be made to domestic the Radio related law
in the future, there is a possibility that communication distance will increase. Thus, it isnecessary to specify the antenna size of the PICC with the potential for future development in mind.
In order to achieve longer communication distances, it will be desirable to specify antenna sizes tobe as large as possible.
(2) Single Card Operation and Two Card Operation
In the case of PICC, there are two possible operating forms: namely, an operating form in which
only a single PICC communicates with a single PCD in the same manner as conventional contact
IC cards (single card operation), and an operating form in which multiple PICCs establish links
with a single PCD to communicate with that device (multiple card operation). Specifically, when
the number of cards in multiple card operation is limited to two cards, it is referred to as a two card
operation.
Single card operation is used in systems premised on processing with a single specific card. Twocard operation is used in systems in which a PCD simultaneously establishes a link with two
PICCs and uses each card for different roles, such as using the first PICC for a specific application,and the second PICC for payment for instance.
Caution is required in that, depending on which of these operation forms is assumed, the resonancefrequency of the PICC and other design conditions vary. Although a PICC inherently premisedon two card operation can also be used for single card operation enabling it to cover both forms ofoperation, since a system with the longest communication distance as possible may be
implemented on the premise of single card operation, this implementation specification allows
both PICC premised on single card operation and PICC premised on two card operation.

3

Version 1.1(3) Open PCD
In the case of contactless applications, received power basically decreases the farther away fromthe antenna. If an encryption coprocessors requiring large power consumption is loaded, with thepresent level of technology, it is necessary to bring the card close to the PCD. In such cases as
well, from the viewpoint of ease of operation and ease of maintenance of the PCD, there is a desire
to simply place or hold the card near the PCD without actually inserting the card into the slot of the
PCD. A system mounted with an open PCD is preferable for such needs.
It is necessary for the PCD to comply with the existing domestic Radio laws for each of its antenna
outputs (see "2.4 Domestic Radio Law"). Assuming the power consumption of a card IC to beabout 50 mW, the PCD is assumed to be a premises radio station or convenience radio station.
If reductions in power consumption of card ICs progress and the output of PCD falls below 50 mW
in the future, it may be possible to realize PCD that function as radio stations that do not require alicense as with extremely low power radio stations.
(4) Slot-In Type PCD
Even with PICCs, in cases in which card processing requires a relatively long period of time atgovernment offices and financial institutions, for example, in order to perform processing reliably,
there have been requests from users indicating the desire to perform card processing with the card
slipped into the PCD. In such cases, a system implemented with a slot-in type of PCD will be
reguired.
When considering the convenience of performing official clerical procedures by users, it isdesirable to suppress the antenna output to the range of extremely low power radio and use as anextremely low power radio station. However, with the slot-in type PCD, while supplying therequired power to the card inside the PCD, the entire PCD is shielded thereby avoiding radiation
outside the PCD and making it possible to suppress the output of radio waves to the outside for theentire PCD to within the range of an extremely low power radio station.

4

Version 1.1

2.3

Characteristics of This Implementation Specification
The matters indicated below have been taken into consideration in this implementation
specification.

(1) Improvement of Compatibility of between PICCs and PCDs
This implementation specification were produced for the purpose of improving compatibility
between PICC and PCD as indicated in "2.2 Characteristics of Assumed PICC and PCD".
However, considerations have also been given to allow a certain degree of freedom in the design of
PICC and PCD. It should therefore be noted that this implementation specification does notunequivocally guarantee the compatibility of PICC and PCD. In order to guarantee compatibility,
users of this implementation specification expected to perform the PICC and PCD test methods
indicated in Chapters 14 and 15, along with the operation tests for PICC and PCD actually used in
the IC card system to be applied.
(2) Need for Specifications other than ISO/IEC Standards
ISO/IEC standards specify specifications oriented toward maintaining higher levels ofextendability (or diversity). In addition, discussions are presented focusing mainly on remotefunctions. Consequently, the operating specifications of a PICC are specified as, for example,"Shall operate as intended in a magnetic field from 1.5 A/m to 7.5 A/m". The antenna diameter of
the test PCD is 15 cm and also is premised to a certain extent on remote functions. In addition,
the fact that specifications are basically based on magnetic field strength suggests that thesestandards are premised on that the PICC and PCD being arranged at a distance at which they do
not exert mutual effects, and that a uniform magnetic field be formed.
In contrast, since this project assumes power consumption of the card IC to be around 50 mW, the
PICC and PCD are arranged in a relationship such that they are in close physical proximity andthat they mutually affect the physical and electrical characteristics of the antenna. It is extremely
unlikely that the measuring instrument with a uniform magnetic field is identical to the actual
magnetic field detected by the PICC. This point is not specified in ISO/IEC standards, and is themost characteristic point of this implementation specification.

5

Version 1.1(3) Required Specifications other than ISO/IEC Standards
It is necessary to add the matters indicated below not described in ISO/IEC standards for thereasons described in the previous section. In other words, these are the important points of this
implementation specification.
(a) PICC specifications (antenna shape, etc.)
See "5. Card Antenna Characteristics".
(b) Reference (surface reading type) PCD specifications for evaluation of PICC
See "14. Card Test Methods".
(c) PCD specifications (antenna shape, etc.)
See "7. PCD Antenna Characteristics ".
(d) Reference PICC specifications for evaluation of PCD
See "15. PCD Test Methods ".
(e) Protocol between external devices and PCD (reference specifications)
See "16. External Communication Protocol".

6

Version 1.1

2.4

Domestic Radio Law
For reference purposes, the relationship between radio stations and power consumption for afrequency of 13.56 MHz in Japan is shown in "Table 2.4-1 References: Domestic Radio Stations(13.56 MHz ± 7 KHz) Rules and Power Consumption ".

Table 2.4-1

References: Domestic Radio Stations (13.56 MHz ± 7 KHz) Rules and Power
Consumption
Extremely low power
radio stations

Premise radio stations orSpecified low power
convenience radio stations

54 dBmV/m or less(at 3 m)(Antenna output about
50 mW or less*1)

Antenna output 1 W or less(equal to extremely low
power radio stations
outside the 13.56 MHz ± 7
KHz band)Antenna output
10 mW

Power
consumption

Radio license notrequiredTechnical competence
required, radio station
application required

Technical
competence required,radio station license
not required

Current example: No CPU
Power consumption: 2-5 mW

About several cm

About 10 cm

About 5 mm

About 5 mm
(surface reading)About several cm

Not possible

About 5 mm
(surface reading)shielded-

Not possible

Rule

PICC
Power consumption: 10-20
mW
New generation IC card
CPU + encryption coprocessor
Power consumption: 25 mW or
more*1: Reference value assuming an antenna diameter of 30 mm

7Version 1.1

2.5

Cited Standards
The standards cited in these implementation specifications are indicated in "Table 2.5-1 Cited
Standards".
Table 2.5-1

Cited Standards

Standard number
ISO/IEC 14443-1

ISO/IEC 14443-2

ISO/IEC 14443-3

ISO/IEC 14443-4

ISO/IEC 10373-6
ISO/IEC 7810
ISO/IEC 7816-2

Title
Identification cards-Contactless
integrated circuit (s) cards- Proximity cards Part1Physical characteristics
Identification cards-Contactless
integrated circuit (s) cards- Proximity cards - Part2Radio
frequency power and signal interface
Identification cards-Contactless
integrated circuit (s) cards- Proximity cards
Part3Initialization and anticollision
Identification cards-Contactless
integrated circuit (s) cards- Proximity cards
Part4Transmission protocol
Identification cards - Test methods Part4Proximity cards
Identification cards - Physicalcharacteristics
Identification cards - Integrated circuit(s)cards with contacts - Part2Dimensions
and location of the contacts

8

Publication
First edition
2000-04-15

FDIS
2000-05-02

First edition
2001-02-01

First edition
2001-02-01

FDIS
2001-01-18
2nd edition
1995-08-15
First edition
1999-03-01

Version 1.1

2.6

OthersDimensions and values not having tolerances described in this implementation specification aretreated as reference dimensions or reference values, and refer to the target central dimension andcentral value.

9Version 1.1

3.

Components

This Proximity Communication Interface Implementation Specification stipulate specifications andstandards that supplement ISO/IEC 14443-2, 3 and 4 with respect to functions relating to contactlesscommunications in PICC and external nodes.
This implementation specification applies to PICC based on the radio wave interface type of ASK 100%modulation type A or ASK 10% modulation type B indicated in ISO/IEC 14443-2, as well as PCD
capable of operating both of these cards.
The components of this proximity communication interface implementation specification is indicated in"Fig. 3-1 Components of the Proximity Communication Interface Implementation Specification".

Power Transmission

IC card antennacharacteristics

Proximity coupling
device antennacharacteristics

Card IC
characteristics

Polling

Transmission
protocol

Anticollision

External device

Usage conditions

External node
Proximity coupling device

Proximity IC card

Proximity Communication Interface
Implementation Specification

Signal transmission from proximity
coupling device to card
Signal transmission from card to proximity
coupling device

Fig. 3-1

Proximity coupling
device test methods

Card test
methods

Compatibility test
methods

External
Communication
protocolComponents of the Proximity Communication Interface Implementation Specification

The sub-categories in the main category of "Proximity Communication Interface Implementation
Specification" are specified in "Table 3-1 Functional Components".

10Version 1.1

Table 3-1 Functional Components
Chapter Title
Usage Conditions

Card Antenna Characteristics

Card IC Characteristics

PCD Antenna Characteristics

Power Transmission

Signal Transmission from
PCD to Card

Signal Transmission from
Card to PCD

Polling

Description
Specifies the usage conditions of the proximity communicationinterface assumed in applications. The specified usage conditions
include communication range, number of cards used, type of card
used and applicable radio law.
Antenna shape, antenna resistance value and other characteristics
are specified as PICC antenna characteristics.
Antennacharacteristics are to be specified with difference in characteristics
due to antenna material and production method in mind.
Characteristic values including IC power consumption and operating
voltage are specified as IC characteristics for PICC.
IC
characteristics are to be specified with difference in characteristics
due to IC function and production method in mind.
Antenna position, shape and other characteristics are specified as
PCD antenna characteristics. Antenna characteristics are to be
specified with differences in characteristics due to communication
performance and production method in mind.
In addition to specifying power transmission characteristics of the
PCD based on ISO/IEC 14443-2, power transmission characteristicsof the PCD are specified in consideration of the PCD characteristics
and card characteristics as specified in these implementation
specifications.
The modulation method, modulation waveform and encoding
method of signal transmission from the PCD to the PICC are
specified on the basis of ISO/IEC 14443-2. Type A and Type B
communication methods are specified.
The modulation method and encoding method of signal transmission
from the PICC to the PCD are specified on the basis of ISO/IEC
14443-2. Type A and Type B communication methods are
specified.
Polling is specified based on ISO/IEC 14443-3 as a method for
detecting whether or not a PICC capable of communicating with the
PCD is present . Polling methods are specified that are compatible
with both type A and type B communication methods.

11Version 1.1

Table 3-1 Functional Components (continued)
Chapter Title
Anticollision

Transmission Protocol

Card Test Methods

PCD Test Methods

External Communication
ProtocolCompatibility Test Methods

Description
Anticollision avoidance is specified on the basis of ISO/IEC
14443-3 for acquiring identification information of PICC even when
multiple PICCs capable of communicating with the PCD arepresent. Communication methods are specified for both type A andtype B. The method for type A is to be the time slot method.
Communication frames and the basic communication sequence are
specified with the transmission protocol of the PICC and PCD on
the basis of ISO/IEC 14443-4. Type A and Type B communication
formats are specified.
Specifies the PICC test methods specified with ISO/IEC 10373-6,
while also specifying the test method of PICC in consideration of
the characteristics and so forth of the PCD as specified in this
implementation specification for the purpose of evaluating PICC.
In addition to specifying test methods of the PCD based on ISO/IEC
10373-6, test methods of the PCD are specified in consideration of
PICC characteristics specified in this implementation specification
for the purpose of evaluating the PCD.
Commands and responses required for realizing a proximity
communication interface in the communication protocol between
the PCD and an external device are specified. Type A and type B
communication formats are specified. The method for type A is tobe the time slot method.
The test method is specified for evaluating interoperability andcompatibility of a PICC and PCD. The contents of evaluation bycross-testing the PICC and PCD are also specified.

12

Version 1.1

4.

Usage Conditions

The following specifies the usage conditions of the proximity communication interface assumed in this
implementation specification. The specified usage conditions include communication range, number ofcards used, type of card used and applicable radio telegraphy law.
4.1

Basic Guidelines

Basic guidelines for drafting the usage conditions are indicated below.
(1) Basic conditions are assumed with the focus on ensuring the safety of personal authorization such as
issuing/confirmation of certificates and reserving/using public facilities as examples of applications inpublic fields.
(2) PICC are assumed to be proximity contactless type cards that comply with ISO/IEC 14443 and whichhave a built-in chip containing a CPU and encryption coprocessor.
(3) The electromagnetic waves generated from the PCD are assumed to be within the range of extremely
low power radio waves in the case of slot-in PCD. In the case of open PCD, considering the current
level of technology, the electromagnetic waves generated from the PCD are assumed to constitute an
output that exceeds extremely low power radio waves.

13

Version 1.1

4.2

Basic Conditions
Basic conditions relating to usage conditions are indicated in "Table 4.2-1 Basic Conditions".
Table 4.2-1

No.

Item

1

Usage form

2

Type of PICC

3

No. of cards
operated

4

Applicableradio law

Basic Conditions
Description

The following two usage forms are assumed.
(1) Card is placed or held over the PCD (in the case of an open PCD).
(2) Card is inserted into a slot or box equipped on the PCD (in the case ofa slot-in PCD).
In either case, the direction of card insertion or orientation of the card is
not significant.
The following two types are assumed.
(1) Type A specified in ISO/IEC 14443-2(2) Type B specified in ISO/IEC 14443-2
Only one card is assumed in the case of PICC premised on single card
operation. One to two cards are assumed in the case of PICC premisedon two card operation. However, the operated PICCs working in
combination are assumed to be of the same type (type A cards or type B
cards), and operation of combinations of different types of cards is not
specified in this implementation specification.
Shall be based on the Radio Law applied in Japan.

14

Version 1.1

Table 4.2-1

Basic Conditions (continued)

No.

Item

Description

5

Communication
range

A distance of 0-5 mm (*1) and dislocation diameter of about 5 mm (*2)
are assumed in the case of slot-in PCD, while a distance of 0-20 mm anddislocation diameter of about 20 mm are assumed in the case of open
PCD. However, this does not exclude communication outside this range.
Furthermore, if held within holders (or other containers that hold the card),
the range shall be within such holder.
*1: Distance refers to the distance to the surface opposing the PCD side of
the PICC assuming the surface of the PCD casing to be 0 mm (origin) andthe antenna of the PICC and the PCD are held horizontally.

6

PICC physicalspecifications*2 Dislocation refers to the amount of dislocation in the horizontal
direction of the PICC assuming the reading center of the PCD and centerof the outer diameter of the PICC are aligned to be 0 mm (origin) and theantenna of the PICC and the PCD are held horizontally.
Shall be ID-1 specified in ISO/IEC 14443-1. However, thickness lessthan or equal to ID-1 are also allowed.

15

Version 1.1

5.

Card Antenna Characteristics

Antenna shape, antenna resistance value and other characteristics are specified as PICC antennacharacteristics. Antenna characteristics shall be specified with consideration to differences incharacteristics due to antenna material and production methods.
5.1

Antenna Shape(1) Basic Specifications
Although there are basically no particular restrictions on the shape and position of the antenna
allocation in PICC, the position indicated in "Fig. 5.1-1 Minimum Coupling Area of PICC" shallbe included.
Center of pin as specified inY

ISO/IEC 7816-2
Y=23.89mm
X

X=15.06mm
Fig. 5.1-1

Minimum Coupling Area of PICC

(2) Extended Specifications
In order to operate the PICC in four direction (front, back, up, down), the antenna mounting area
shall be where the coupling area will be minimum with respect to all directions. The antenna
allcation renge is shown with diagonal lines in "Fig. 5.1-2 Antenna Mounting Range".

 Fig. 5.1-2

Antenna Mounting Range(3) References
None

16

Version 1.1

5.2

Antenna Resistance Value(1) Basic Specifications
None(2) Extended Specifications
Although resistance values are not particularly specified in this specification, the resistance value
shall at least satisfy the specifications specified in the following:"8. Power Transmission""9. Communication PCD to PICC""10. Communication PICC to PCD"
"14. Card Test Methods"(3) References
None

17

Version 1.1

5.3

Inductance(1) Basic Specifications
None(2) Extended Specifications
Although inductance are not particularly specified in this specification, the inductance value shallat least satisfy the specifications specified in the following:"8. Power Transmission""9. Communication PCD to PICC""10. Communication PICC to PCD"
"14. Card Test Methods"(3) References
None

18

Version 1.1

5.4

Resonance Frequency(1) Basic Specifications
None(2) Extended Specifications
The resonance frequencies when using a single PICC and when superimposing two cards are
specified.
(a) When Using a Single Card
The resonance frequency is preferably 19 MHz or higher, and shall at least satisfy the
specifications specified in the following:"8. Power Transfer""9. Communication PCD to PICC""10. Communication PICC to PCD"
"14. Card Test Methods"
Furthermore, in the case of card premised on single card operation, the resonance frequency may
be 19 MHz or lower, but considerations must be given to the effects when bringing the card inclose proximity of a PCD.
In addition, in the case of using superimposed cards, a resonance frequency that satisfies the
specification in "5.4 (2) (b) When Superimposing Two Cards" shall be selected.
Resonance frequency shall be measured using the method specified in the "NOTE" of section"15.3.1 (1) (a) a) 2)".
(b) When Superimposing Two Cards
The resonance frequency is preferably 13 MHz or higher, and shall at least satisfy the
specifications specified in the following:"8. Power Transmission""9. Communication PCD to PICC""10. Communication PICC to PCD"
"14. Card Test Methods"
Resonance frequency shall be measured using the method specified in the "NOTE" of section"15.3.1 (1) (a) a) 2)".
(3) References
None

19

Version 1.1

5.5

Material and Production Method(1) Basic Specifications
None(2) Extended Specifications
Although materials and production methods are not particularly specified in this specification,materials and production methods shall at least satisfy the specifications specified in the following:"8. Power Transmission""9. Communication PCD to PICC""10. Communication PICC to PCD"
"14. Card Test Methods"(3) References
None

20

Version 1.1

6.

Card IC Characteristics

Characteristic values including IC power consumption and operating voltage are specified as IC
characteristics for PICC. IC characteristics shall be specified with consideration to differences incharacteristics due to IC function and production methods.
6.1

Operating Power(1) Basic Specifications
None(2) Extended Specifications
The power supply method, minimum operating power, maximum operating power, maximum input
power and input capacity of card ICs are specified.
(a) Power Supply Method
The card IC shall operate by receiving power supplied from the PCD through an antenna.
(b) Minimum Operating Power
There are no particular specifications for the value of minimum power consumption at which thecard IC functions normally. However, the power shall be appropriate for the card IC to operate at
the minimum operating magnetic field specified in "14. Card Test Methods".
Section "6.1 (2) (e) Definition of Power Consumption" is applied for the power consumption of thecard IC.
(c) Maximum Operating Power
There are no particular specifications for the maximum power consumption at which the card ID
functions normally. However, the power shall be appropriate for the card IC to operate at the
maximum operating magnetic field specified in "14. Card Test Methods".
Section "6.1 (2) (e) Definition of Power Consumption" is applied for the power consumption of thecard IC.
(d) Maximum Input Power
There are no particular specifications for the value of maximum input power at which the card IC
is not destroyed. However, the power shall be that at which the card IC is not destroyed at the
maximum applied magnetic field specified in "14. Card Test Methods".

21Version 1.1(e) Definition of Power Consumption
The card IC equivalent circuit and its components are shown in "Fig. 6.1-1 Card IC Equivalent
Circuit 1" and "Table 6.1-1 Equivalent Circuit Composition". Card IC power consumption shallbe the power that is consumed by load resistor R1 in order to correspond to the Reference PICC
circuit drawing specified in Annex D of ISO/IEC 10373-6.
If the rectifier characteristics differ between the card IC and card IC equivalent circuit 1, the power
shall be that resulting from converting the card IC rectifier characteristics to the rectifiercharacteristics of card IC equivalent circuit 1.

Rectifier

P1

Card ICIC

D1

D2

D3

D4

C1

L1

C2

R1

P2

SymbolFig. 6.1-1

Card IC Equivalent Circuit 1

Table 6.1-1

Equivalent Circuit Composition

Components

P1, P2
C1
D1, D2, D3, D4

Coil connection pad
Input capacity
Full wave rectifier diodeC2

Smoothing capacitor

R1

Load resistor

VDC

Receiving voltage

L1

Antenna22

Part constant and type

As per "(f) Input Capacity"
Schottky diode(equivalent to BAR43)
Determined by producing
manufacturer
Determined by producing
manufacturer
Determined by producing
manufacturer-

VDC

Version 1.1(f) Input Capacity
There are no particular specifications for card IC input capacity. However, capacity shall satisfy"5.4 Resonance Frequency" with the antenna connected.
(3) References
None

23

Version 1.1

6.2

Input Signal(1) Basic Specifications
None(2) Extended Specifications
The input signal that can be processed normally by the card IC is specified.
The card IC shall be able to normally process the signal specified in "9. Communication PCD to
PICC" with the antenna connected. In addition, the tests specified in "14. Card Test Methods"
shall be satisfied. However, the antenna connected to the card IC shall satisfy "5. Card Antenna
Characteristics".
(3) References
None

24

Version 1.1

6.3

Output Signal(1) Basic Specifications
None(2) Extended Specifications
The output signal generated by the card IC is specified.
The card IC shall generate the signal specified in "10. Communication PICC to PCD" with theantenna connected. In addition, the tests specified in "14. Card Test Methods" shall be satisfied.
However, the antenna connected to the card IC shall satisfy "5. Card Antenna Characteristics".
(3) References
None

25

Version 1.1

7.

PCD Antenna Characteristics

Antenna position, shape and other characteristics are specified as PCD antenna characteristics. Antennacharacteristics are to be specified with consideration to differences in characteristics due tocommunication performance and production methods.
7.1

Antenna Position(1) Basic Specifications
None(2) Extended Specifications
Although there are no particular specifications for antenna position, antenna position shall bedecided so as to satisfy communication performance independent of the operating direction (front,
back, up, down) of the PICC within the communication range or the coil position. In addition,
the antenna shall be aligned in a direction such that the antenna of the PCD and the antenna of the
PICC face each other in parallel.
An example of an antenna position of a PCD where the center of the antenna is aligned with thecenter of the PICC is shown in "Fig. 7.1-1 Antenna Position".

Center of theproximity
IC cardIC

Centerof the antenna of the
proximity
coupling device





Antennaof theIC
proximity
IC card
Parallel

Antennaof the proximity
coupling
 deviceFig. 7.1-1

Antenna Position(3) References
None

26

Version 1.1

7.2

Antenna Shape(1) Basic Specifications
None(2) Extended Specifications
The PCD antenna preferably has a symmetrical shape in order to prevent significant changes incommunication performance caused by the direction of operation (front, back, up, down) of the
PICC or by the coil position. An example of the antenna shape of a PCD is shown in "Fig. 7.2-1
Antenna Shape".

Verticaldirection<Legend>

Horizontal
direction  Antenna centerFig. 7.2-1

Antenna Shape(3) References
None

27

Version 1.1

7.3

Antenna Resistance Value(1) Basic Specifications
None(2) Extended Specifications
Although resistance values are not particularly specified in this specification, the resistance value
shall at least satisfy the specifications specified in the following:"8. Power Transmission""9. Communication PCD to PICC""10. Communication PICC to PCD"
"15. PCD Test Methods"(3) References
None

28

Version 1.1

7.4

Inductance(1) Basic Specifications
None(2) Extended Specifications
Although inductance are not particularly specified in this specification, inductance shall at leastsatisfy the specifications specified in the following:"8. Power Transmission""9. Communication PCD to PICC""10. Communication PICC to PCD"
"15. PCD Test Methods"(3) References
None

29

Version 1.1

7.5

Resonance Frequency(1) Basic Specifications
None(2) Extended Specifications
Although resonance frequency are not particularly specified in this specification, resonancefrequency shall at least satisfy the specifications specified in the following:"8. Power Transfer""9. Communication PCD to PICC""10. Communication PICC to PCD"
"15. PCD Test Methods"(3) References
None

30

Version 1.1

7.6

Material and Production Method(1) Basic Specifications
None(2) Extended Specifications
Although materials and production method are not particularly specified in this specification,materials and production methods shall at least satisfy the specifications specified in the following:"8. Power Transmission""9. Communication PCD to PICC""10. Communication PICC to PCD"
"15. PCD Test Methods"(3) References
None

31

Version 1.1

8.

Power Transmission

In addition to specifying power transmission characteristics of the PCD based on ISO/IEC 14443-2,
power transmission characteristics of the PCD are specified with consideration to the PCD characteristics
and card characteristics as specified in this implementation specification.
8.1

Frequency(1) Basic Specifications
The frequency fc of the RF operating field shall be 13.56 MHz ±7kHz.
(2) Extended Specifications
None(3) References
None

32

Version 1.1

8.2

Operating Magnetic Field

8.2.1

PICC Operating Magnetic Field(1) Basic Specifications(a) Minimum Operating Magnetic Field (Hmin)
The minimum unmodulated operating field shall be Hmin and has a value of 1.5 A/m (rms).
(b) Maximum Operating Magnetic Field (Hmax)
The maximum unmodulated operating field shall be Hmax and has a value of 7.5 A/m (rms).
(c) Operating Conditions
A PICC shall operate as intended continually between Hmin and Hmax.
(d) Maximum Applied Magnetic Field
The PICC must operate normally even after being continuously exposed to a magnetic fieldstrength of an average magnetic field of 10 A/m (rms) at 13.56 MHz. In addition, it must also
operate normally even after being exposed for 30 seconds on average to a magnetic field strengthof a maximum magnetic field of 12 A/m (rms).
(2) Extended Specifications(a) Minimum Operating Magnetic Field (Hmin)
The strength of the minimum operating magnetic field of the PICC is to be 4 A/m (rms) in the
non-modulated state.
(3) References
None

33

Version 1.1

8.2.2

PCD Generated Magnetic Field(1) Basic Specifications
A PCD shall generate a field of at least Hmin and not exceeding Hmax at manufacturer specified
positions (operating volume). In addition the PCD shall be capable of powering any signal
reference PICC (specified in "15. PCD Test Methods") at manufacuturer specified positions(operating volume).
The PCD shall not generate a field higher than the value specified in section "8.2.1 (d) Maximum
Applied Magnetic Field" in any possible PICC position.
Test methods for the PCD operating field are defined in "15. PCD Test Methods".
(2) Extended Specifications
None(3) References
None

34

Version 1.1

9.

Communication PCD to PICC

The modulation method, modulation waveform and encoding method of signal transmission from the
PCD to the PICC are specified on the basis of ISO/IEC 14443-2. Type A and Type B

communication methods are specified.
--

fc: frequency of operating field (carrier frequency).
Manchester: method of bit coding whereby a logic level during a bit duration is represented by asequence of two defined physical state of a communication medium. The order of the physicalstates within the sequence defines the logical state.
NRZ-L (Non-Return to Zero, L for level): method of bit coding whereby a logic level during a bit
duration is represented by one of two defined physical states of a communication medium.

9.1

Communication Signal Interface Type A

9.1.1

Bit Rate(1) Basic Specifications
The bit rate for the transmission during initialization and anticollision shall be fc/128(~106 kbit/s).
(2) Extended Specifications
None(3) References
None

35

Version 1.1

9.1.2

Modulation(1) Basic Specifications
Communication from PCD to PICC for a bit rate of fc/128 shall use the modulation principle of
ASK 100% of the RF operating field to create a "Pause" as shown in "Fig. 9.1-1 Pause".
The envelope of the PCD field shall decrease monotonically to less than 5% of its initial value
HINITIAL and remain less than 5% for more than t2. This envelope shall comply to "Fig. 9.1-1
Pause".
If the envelope of the PCD field does not decrease monotonically, the time between a local
maximum and the time of passing the same value before the local maximum shall not exceed 0.5µs. This shall only apply if the local maximum is greater than 5% of HINITIAL.
Overshoots shall remain within 90% and 110% of HINITIAL.
The PICC shall detect the “End of Pause” after the field exceeds 5% of HINITIAL and before it
exceeds 60% of HINITIAL.
However, in systems designed to handle only one card at a time, t4 need not be respected.
The waveform of end of pause is shown in "Fig. 9.1-2 Definition of "End of Pause"".

36

Version 1.1

Envelope ofCarrier Amplitude
H/M INITIAL
110%
100%
90%
60%

5%
t

5%

60%
90%
100%
110%

t4

Condition
t1

t2
t1

t2

t3

t3
t4

Fig. 9.1-1

37

Pause

t1>2.5µs
t1≤2.5µs

Min.
2.0µs
0.5µs
0.7µs
0
0

Max.
3.0µs
t1
1.5µs
0.4µs

Version 1.1

Carrier
Amplitude
100%
60%

5%
t

5%

60%
t4

t4 < 0.4µs

100%Fig. 9.1-2

Definition of "End of Pause"(2) Extended Specifications
None(3) References
None

38

Version 1.1

9.1.3

Bit Representation and Coding(1) Basic Specifications
The following sequences are defined:- sequence X: after a time of half the bit duration a "Pause" shall occur.
- sequence Y: for the full bit duration no modulation shall occur.
- sequence Z: at the beginning of the bit duration a "Pause" shall occur.
The above sequences shall be used to code the following information:- logic "1": sequence X- logic "0": sequence Y with the following two exceptions:- If there are two or more contiguous "0"s, sequence Z shall be used from the second "0" on.
- If the first bit after a "start of frame" is "0", sequence Z shall be used to represent this andany "0"s which follow directly thereafter.
start of comunication: sequence Z
end of communication: logic "0" followed by sequence Y.
no information: at least two sequneces Y.

(2) Extended Specifications
None(3) References
None

39

Version 1.1

9.2

Communication Signal Interface Type B

9.2.1

Bit Rate(1) Basic Specifications
The bit rate for the transmission during initialization and anticollision shall be nominallyfc/128(~106 kbit/s). Tolerance and bit boundaries are defined in "12. Anticollision".
(2) Extended Specifications
None(3) References
None

40

Version 1.1

9.2.2

Modulation(1) Basic Specifications
Communication from PCD to PICC shall use the modulation principle of ASK 10% of the RF
operating field. The modulation index shall be between 8% and 14%. The modulation
waveform shall comply to "Fig. 9.2-1 Type B Modulation Waveform". The rising and fallingedges of the modulation shall be monotonic.

hfya=
carrier
amplitude

y

hr
tr

Fig. 9.2-1

b

tf

tr
tf
y

2µs max
2µs max
0.1(a-b)

hfhr

0.1(a-b)max

Type B Modulation Waveform(2) Extended Specifications
None(3) References
None

41

Version 1.1

9.2.3

Bit Representation and Coding(1) Basic Specifications
Bit coding format shall be NRZ-L with logic levels defined as follows:- Logic "1": carrier high field amplitude(no modulation applied).
- Logic "0": carrier low field amplitude.
(2) Extended Specifications
None(3) References
None

42

Version 1.1

10. Communication PICC to PCD
The modulation method and encoding method of signal transmission from the PICC to the PCD are
specified on the basis of ISO/IEC 14443-2. Type A and Type B communication methods are specified.
The following indicates the terms and abbreviations used in this chapter.
- Subcarrier: signal of frequency fs used to modulate a carrier of frequency fc.
- Bit duration: time during which a logical level is defined, at the end of which a new bit starts.
- Manchester: method of bit coding whereby a logic level during a bit duration is represented by asequence of two defined physical state of a communication medium. The order of the physicalstates within the sequence defines the logical state.
- BPSK (Binary Phase Shift Keying): Binary phase shift keying- fs: Frequency of the subcarrier modulation.
- NRZ-L (Non-Return to Zero. L for level): method of bit coding whereby a logic level during a bit
duration is represented by one of two defined physical states of a communication medium.
10.1 Communication Signal Interface Type A
10.1.1 Bit Rate
(1) Basic Specifications
The bit rate for the transmission during initialization and anticollision shall be fc/128(~106 kbit/s).
(2) Extended Specifications
None(3) References
None

43

Version 1.1

10.1.2 Load Modulation(1) Basic Specifications
The PICC shall be capable of communication to the PCD via a inductive coupling area where thecarrier frequency is loaded to generate a subcarrier with frequency fs. The subcarrier shall be
generated by switching a load in the PICC. The load modulation amplitude shall be at least 30/H1,
2(mVpeak) when measured as described in ISO/IEC 10373-6, where H is the (rms) value ofmagnetic field strength in A/m.
(2) Extended Specifications
None(3) References
None

44

Version 1.1

10.1.3 Subcarrier(1) Basic Specifications
The frequency fs of the subcarrier shall be fc/16 (~847kHz). Consequently, during initialization
and anticollision, one bit period is equivalent to 8 periods of the subcarrier.
(2) Extended Specifications
None(3) References
None

45

Version 1.1

10.1.4 Subcarrier Modulation Method(1) Basic Specifications
Every bit period shall start with a defined phase relation to the subcarrier.
start with the loaded state of the subcarrier.

The bit period shall

The subcarrier is modulated using On/Off keying with the sequence defined in "10.1.5 Bit
Representation and Coding".
(2) Extended Specifications
None(3) References
None

46

Version 1.1

10.1.5 Bit Representation and Coding(1) Basic Specifications
The following sequences are defined:- sequence D: the carrier shall be modulated with the subcarrier for the first half (50%) of the bit
duration.
- sequence E: the carrier shall be modulated with the subcarrier for the second half (50%) of the
bit duration.
- Sequence F: the carrier is not modulated with the subcarrier for one bit duration.
Bit coding shall be Manchester with the following definitions:- logic"1": sequence D- logic"0": sequence E- start of communication: sequence D- end of communication: sequnece F- no information: no subcarrier (Sequence F)(2) Extended Specifications
None(3) References
None

47

Version 1.1

10.2 Communication Signal Interface Type B
10.2.1 Bit Rate
(1) Basic Specifications
The bit rate for the transmission during initialization and anticollision shall be nominallyfc/128(~106 kbit/s).
(2) Extended Specifications
None(3) References
None

48

Version 1.1

10.2.2 Load Modulation(1) Basic Specifications
The PICC shall be capable of communication to the PCD via a inductive coupling area where thecarrier frequency is loaded to generate a subcarrier with frequency fs. The subcarrier shall be
generated by switching a load in the PICC.
The load modulation amplitude shall be at least 30/H1, 2 (mVpeak) when measured as described in
ISO/IEC10373-6, where H is the (rms) value of magnetic field strenfh in A/m.
(2) Extended Specifications
None(3) References
None

49

Version 1.1

10.2.3 Subcarrier(1) Basic Specifications
The frequency fs of the subcarrier shall be fc/16 (~847kHz). Consequently, during initialization
and anticollision, one bit period is equivalent to 8 periods of the subcarrier. The PICC shallgenerate a subcarrier only when data is to be transmitted.
(2) Extended Specifications
None(3) References
None

50

Version 1.1

10.2.4 Subcarrier Modulation(1) Basic Specifications
The subcarrier shall be BPSK modulated, see example in "Fig. 10.2-1 Allowed phase shifts" withBPSK modulation. Phase shifts shall only occur at nominal position of rising or falling edges ofthe subcarrier.
Bit period

Phase change point

Next phase change point
Fig. 10.2-1

Allowed Phase Shifts(2) Extended Specifications
None(3) References
None

51

Version 1.1

10.2.5 Bit Representation and Coding(1) Basic Specifications
Bit coding shall be NRZ-L where a change of logic level shall be denoted be a phase shift (180°) of
the subcarrier.
The initial logic level for NRZ-L at the start of a PICC frame shall be established by the following
sequence:
After any command from the PCD a guard time TR0 shall apply in which the PICC shall notgenerate a subcarrier. TR0 shall be greater than 64/fs.
The PICC shall then generate a subcarrier with no phase tradition for a synchronization time TR1.
This establishes a subcarrier phase reference Φ0. TR1shall be greater than 80/fs.
This initial phase state Φ0 of the subcarrier shall be defined as logic "1" so that the first phasetransition represents a change from logic "1" to logic "0".
Subsequently the logic level is defined according to the subcarrier phase reference Φ0:
Φ0: represents logic"1".
Φ0 + 180°: reperesents logic "0".
(2) Extended Specifications
None(3) References
None

52

Version 1.1

11. Polling
Polling for detecting existence of a PICC capable of communicating with the PCD is specified based on
ISO/IEC 14443-3. Polling methods compatible with both type A and type B communication methods
are specified.
The following indicates the terms and abbreviations used in this chapter.
- REQA (Request Command, Type A): Request command for a Type A PICC
- REQA (Request Command, Type B): Request command for a Type B PICC
- ATQ (Answer To Read): Response signal from PICC.
Furthermore, the PCD described in this chapter includes external devices.

53Version 1.1(1) Basic Specifications
In order to detect PICCs which are in the operating field, a PCD shall send repeated Request
commands. The PCD shall send REQA and REQB described in "12. Anticollision" and in adtion
may send other commands described in "12.5 Type A Timeslot - Initialization and Anticollision".
When a PICC is exposed to an unmodulated operating field it shall be able to accept within 5ms(see "8. Power Transfer").
More specifically:- EXAMPLE 1
When a PICC Type A receives and Type B command it shall be able to accept
a REQA within 5ms of unmodulated operating field.
- EXAMPLE 2
When a PICC Type B receives any Type A command it shall be able to accept
a REQB within 5ms of unmodulated operating field.
(2) Extended Specifications
None(3) References
The request commands used for polling may use the encoding system described in "12.5 Type A
Timeslot - Initialization and Anticollision" and REQB having an optional method. (For further
details, refer to References of section "12.2.4(3)" of "12.2 Type B Initialization and Anticollision
Processing".)54

Version 1.1

12. Anticollision
Anticollision is specified on the basis of ISO/IEC 14443-3 for acquiring identification information of
PICC where multiple PICCs capable of communicating with the PCD are present. Communication
methods are specified for both type A and type B.
(1) Terms Used in this Section- Anticollision Loopalgorithm used to prepare for dialogue between PCD and one or more PICCs out of the total
number of PICCs responding to a request command- Bit Collision Detection Protocol
Processing method which gives significance to bit units within a frame. Collision occurs when
two or more PICCs send complementary bit patterns to the PCD. In the case of type A PICCs, thebit pattern overlaps and the carrier is modulated with the subcarrier for the entire bit period (100%).
PCD recognizes the IDs of all PICCs in order while detecting colliding bits.
- Byte8 bits of data designated b8 to b1, from the most significant bit (MSB, b8) to the least significant
bit (LSB, b1)- Collisiontransmission by two PICCs in the same PCD energizing field and during the same time period,
such that the PCD is unable to distinguish from which PICC the data originated.
- elementary time unit
etu
for "12. Anticollision", one etu is defined as 1 etu=128/fc (i.e. 9.4 µs nominal)- Framesequence of data bits and optional error detection bits, with frame delimiters at start and end

55

Version 1.1- Higher layer protocol
protocol layer ( not described in that makes use of the protocol layer defined in to transfer
information belonging to the application or higher layers of protocol that is not described in "12.
Anticollision".
- Timeslot protocol
method whereby a PCD establishes logical channels with one or more PICCs of Type B, whichmakes use of timeslot allocation for PICC response- Unique Identifier
UID is the number used for anticollision processing of type A cards.

56

Version 1.1(2) Symbols Used in this Section- AFI Application field identifier
Preliminary card screening standard according to the application field.
- APa
Parameter used with ATQB
- APc
Parameter used with ATTRIB- APfAnticollosion Prefix f, used in REQB
- APn
Anticollision Prefix n, used in Slot-MARKER Command- ATA
Response to ATTRIB- ATQRequest acknowledgment signal- ATQA
Answer To Request, Type A- ATQB
Answer To Request, Type B- ATTRIB PICC selection command- BCC
UID CLn check byte, calculated as exclusive-or over the 4 previous bytes- CLn
Cascade Level n (3 ≥ n ≥ 1)
- CT
Cascade Tag (value is '88')- CRC_A Cyclic Redundancy Check error detection code A- CRC_B Cyclic Redundancy Check error detection code B- DESEL Deselect command-E
End of communication, Type A- EGT
Extra Guard Time
- EOF
End Of Frame- etu
Elementary time unit
- FGT
Frame guard time
- fc
Carrier frequency (13.56 MHz)
- fs
Subcarrier frequency (fc/16)- ID
IDentification number- INF
INFormation field belonging to higher layer- LSB
Least significant bit- MSB
Most significant bit-N
Number of anticollision slots or PICC response probability in each slot-nVariable integer value as defined in the specific clause- NAD
Node address- NVB
Number of Valid Bits-P
Odd Parity bit

57

Version 1.1- PARAM Attribute information parameter- PCD
Proximity coupling device for proximity IC card (including upper devices)- PICC
Proximity Card
- PUPI
Pseudo-Unique PICC Identifier-R
Slot number chosen by the PICC during the anticollision sequence- REQA
Request Command, Type A- REQB
Request Command, Type B- RFU
Reserved for Future Use-SStart of communication, Type A- SAK
Select AcKnowledge- SEL
Select code
- SOF
Start of frame- T0
Minimum time from completion of transmission by PCD to start of generation of
subcarrier by PICC
- T1
Minimum time from start of generation of subcarrier to its stable generation before
start of data transmission by PICC
- UID
Unique identifier- UIDnByte number n of Unique Identifier, n ≥ 0(3) For the purposes of this section, then following notation applies:- (xxxx)b- 'XX'

Data bit representation
Hexadecimal

58

Version 1.1

12.1 Type A-Initialization and AnticollisionThis section describes the initialization and collision detection protocol applicable for PICCs of
Type A.
12.1.1 Frame Format and TimingThis section defines the frame format and timing used during communication initialization andanticollision. For bit representation and coding refer to "9. Communication PCD to PICC" and"10. Communication PICC to PCD".
12.1.1.1 Frame Delay Time
(1) Basic Specifications
The frame delay FDT is defined as the time between two frames transmitted in opposite directions.
(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

59Version 1.1

12.1.1.2 Frame Delay Time PCD to PICC
(1) Basic Specifications
This is the time between the end of the last pause transmitted by the PCD and the first modulationedge within the start bit transmitted by the PICC and shall respect the timing defined in "Fig.
12.1-1 Frame Delay Time PCD to PICC", where n is an integer value.

Last data bit transmitted by PCD

First modulation of PICC

FDT=(n×128+84) / fc

128/fc256/fc128/fclogic "1"End of communication (E)Start ofcommunication (S)FDT=(n×128+20) / fc

128/fc256/fc128/fclogic "0"End of communication (E)Start ofcommunication (S)Fig. 12.1-1

Frame Delay Time PCD to PICC

60

Version 1.1"Table 12.1-1 Frame Delay Time PCD to PICC" defines values for n and FDT depending on thecommand type and the logic state of the last transmitted data bit in this command.
Table 12.1-1 Frame Delay Time PCD to PICC
command type
REQA Command
WUPA Command
ANTICOLLISION Command
SELECT Command
All other commandsn(Integer value)
9

last bit = (1)b
1236 / fc

last bit = (0)b1172 / fc≥9(n×128+84) / fc

(n×128+20) / fc

FDT

The value n=9 means that all PICCs in the field shall respond in a synchronous way which isneeded for anticollision.
For all other commands the PICC shall ensure that the first modulation edge within the start bit isaligned to the bit grid defined in "Fig. 12.1-1 Frame Delay Time PCD to PICC".
(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

61Version 1.1

12.1.1.3 Frame Delay Time PICC to PCD(1) Basic Specifications
This is the time between the last modulation transmitted by the PICC and the first pausetransmitted by the PCD and shall be at least 1172/fc.
(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

62Version 1.1

12.1.1.4 Request Guard Time
(1) Basic Specifications
Request Guard Time is defined as the minimum time between the start bits of two consecutive
REQA commands. It has the value 7000/fc.
(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

63Version 1.1

12.1.1.5 Frame Formats(1) Basic Specifications
The following frame types are defined:- short frames for commands defined in "Fig. 12.1-2 Short Frame"- standard frames for regular commands;- bit oriented anticollision frame for anticollision command.
(a) Short Frame
A short frame is used to initiate communication and consists of, in the following order:- start of communication;- 7 data bits transmitted LSB first (for coding see "Fig. 12-1-2 Short Frame").
- end of communication
No parity bit us added.
LSB
b1

S
b2
b3
↑
First bit transmitted
Fig. 12.1-2

b4

b5

b6

Short Frame

64

MSB
b7

E

Version 1.1(b) Standard Frame
Standard frames are used for data exchange and consist of :- start of communication;n x (8 data bits+odd parity bit), with n≥1. The LSB of each byte is transmitted first. Eachbyte is followed by and odd parity bit. The parity bit P is set such that the number of 1s is oddin (b1 to b8, P);- Frame end bit- end of communication.
The composition of standard frames is shown in "Fig. 12.1-3 Standard Frame".

SLSB
n x (8 data bits + odd-number parity bit)
b1 b2 b3 b4 b5 b6 b7 b8 P b1 b2 b3
b6 b7 b8
1st byte

First bit transmitted

2nd byte
ParityFig. 12.1-3

P

b1

b8

P

E

nth byte
End of communication

Standard Frame65

Version 1.1(c) Bit oriented anticollision frame
A collision is detected when at least two PICCs transmit different bit patterns to the PCD. In thiscase the carrier is modulated with the subcarrier for the whole bit duration for at least one bit.
Bit oriented anticollision frames shall only be used during bit frame anticollision loops and arestandard frames with a length of 7 bytes, split into two parts:
part 1 for transmission from PCD to PICC;
part 2 for transmission from PICC to PCD.
- For the length of part1 and part2, the following rules shall apply:- rule1: The sum of data bits shall be 56;- rule 2: The minimum length of part 1 shall be 16 data bits;- rule 3: The maximum length of part 1 shall be 55 data bits.
Consequently, the minimum length of part 2 shall be 1 data bit and the maximum length shall be 40
data bits.
Since the split can occur at any bit position within a byte, two cases are defined:- case FULL BYTE: Split after a complete byte. A parity bit is added after the last data bit of part1;
- case SPLIT BYTE: split within a byte. No parity bit is added after the last data bit of part 1.
The following examples for case FULL BYTE (Fig. 12.1-4 "Bit organization and transmission of
bit oriented anticollision frame, case FULL BYTE") and case SPLIT BYTE (Fig. 12.1-5 "Bitorganization and transmission of bit oriented anticollision frame, case SPLIT BYTE") define thebit organization and order of bit transmission.

66Version 1.1

Standard frame, split after 4th complete data byte
SEL

NVB

UID0

UID1

UID2

UID3

BCC

S 11001001 1 00000010 0 01001100 0 00001000 0 11010101 0 10110011 0 00100010 1 E

'93'

'40'

'32'

'10'

'AB'

'CD'

'44'

anticollision frame, part1: PCD to PICC)
S 11001001 1 00000010 0 01001100 0 00001000 0 E

anticollision frame, part 2: PICC to PCDFirst bit transmitted
S 11010101 0 10110011 0 00100010 1 E

First bit transmitted
Fig. 12.1-4

Bit organization and transmission of bit oriented anticollision frame, case FULL
BYTE

67

Version 1.1

Standard frame, split after 2 data bytes + 5 bits
SEL

NVB

UID0

UID1

UID2

UID3

BCC

S 11001001 1 10100100 0 01001 100 0 00001000 0 11010101 0 10110011 0 00100010 1 E

'93'

'25'

'32'

'10'

'AB'

'CD'

'44'

antiollision frame, part 1: PCD to PICC
S 11001001 1 10100100 0 01001 E

anticollision frame, part 2: PICC to PCDFirst bit transmitted
S 100 x 00001000 0 11010101 0 10110011 0 00100010 1 E

First bit transmitted

Fig. 12.1-5

Bit organization and transmission of bit oriented anticollision frame,case SPLIT BYTE

For a SPLIT BYTE, the first parity bit of part 2 shall be ignored by the PCD.
(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

68Version 1.1

12.1.1.6 CRC_A(1) Basic Specifications
The frame CRC_A is a function of k data bits, which consist of all the data bits in the frame,
excluding parity bits, S and E, and the CRC_A itself. Since data is encoded in bytes, the numberof bits k is a multiple of 8. For error checking, the two CRC_A bytes are sent in the standard frame,
after the bytes and before the E. The CRC_A is as defined in ISO/IEC 13239, but the initial
register content register content shall be '6363' and the register content shall not be invented after
calculation.
For example refer to "12.4 CRC_A and CRC_B Encoding".
(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

69Version 1.1

12.1.2 PICC States(1) Basic Specifications
The following sections provide descriptions of the states for a PICC of Type A specific to the bit
collision detection protocol.
"Fig. 12.1-6 PICC Type A state diagram" takes all possible state transitions caused by commandsof this chapter into account.
PICCs react to valid received frames only. No response is sent when transmission errors aredetected.
The following symbols apply for the state diagram shown in "Fig. 12.1-6 PICC Type A state
diagram".
-

REQA REQA command
WUPA WUPA command
AC ANTICOLLISION Command (match UID)nAC ANTICOLLISION Command (not matched UID)SEL SELECT Command (matched UID)nSEL SELECT Command (not matched UID)HLTA HLTA command
DESEL DESELCT Command, defined in "13. Transmission Protocol".
Error Transmission error detected70

Version 1.1

Power off
state
Reset
HALT
state
REQA
WUPA
nAC
nSEL
NSEL
HLTA
Error

WUPA

READY*
state
REQA
WUPA
AC
nAC
SEL
NSEL
Error

REQA
AC
nAC
SEL
nSEL
HLTA
Error

IDLE
state
REQA
WUPA
SEL
nSEL
HLTA
Error

REQAWUPA

READY
state

AC
REQA
WUPA
AC
nAC
SEL
NSEL
Error

SEL

AC
nAC
SEL
nSEL
HLTA
Error

AC

SEL

ACTIVE
state

ACTIVE*
state

ISO/IEC
14443-4

HLTA

Fig. 12.1-6

DESEL

HLTA

PICC Type A State Diagram

PICCs being compliant with the specifications of this chapter but not using the specifications of"13. Transmission Protocol" may leave the ACTIVE or ACTIVE* State by proprietary commands.

71

Version 1.1(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

72Version 1.1

12.1.2.1 Power-OFF State(1) Basic Specifications- Description:
In the POWER-OFF State, the PICC is not powered due to a lack of carrier energy.
- State exit conditions and transitions:
If the PICC is in an energizing magnetic field greater than Hmin (see "8. Power Transfer"), it
shall enter is IDLE State within a delay not greater than defined in "11. Polling").
(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

73Version 1.1

12.1.2.2 IDLE State(1) Basic Specifications- Description
In the IDLE State, the PICC is powered. It listens for commands and shall recognized request
commands (REQA) and wakeup commands (WUPA).
- State exit conditions and transitions:
The PICC enters the Ready State after it has received a valid REQA or WUPA Command andtransmitted its response (ATQA).
(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

74Version 1.1

12.1.2.3 READY State(1) Basic Specifications- Description
In the READY State, either the bit frame anticollision or a proprietary anticollision method canbe applied (see "12.5 Type A Timeslot - Initialization and Anticollision"). Cascade levels arehandled inside this state to get the complete UID.
- State exit conditions and transitions:
The PICC enters the ACTIVE State when it is selected with its complete UID.
(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

75

Version 1.1

12.1.2.4 ACTIVE State(1) Basic Specifications- Description
In the ACTIVE State, the PICC listens to any higher layer message.
- State exit conditions and transitions:
The PICC enters the HALT State when a valid halt command (HLTA) is received.
- NOTEIn the higher layer protocol, specific commands may be defined to return the PICC to its HALTState.
(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

76Version 1.1

12.1.2.5 HALT State(1) Basic Specifications- Description:
In the HALT State, the PICC shall respond only to a WUPA Command that will make enter into
the READY* state.
- State exit conditions and transitions:
The PICC enters the READY* State after it has received a valid WUPA Command andtransmitted its ATQA.
(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

77Version 1.1

12.1.2.6 READY* State(1) Basic Specifications- Description
The READY* State is similar to the READY State, either the bit frame anticollision or a
proprietary anticollision method can be applied (see "12.5 Type A Timeslot - Initialization andAnticollision"). Cascade levels are handled inside this state to get complete UID.
- State exit conditions and transitions:
The PICC enters the ACTIVE *State when it is selected with its complete UID.
(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

78

Version 1.1

12.1.2.7 ACTIVE* State(1) Basic Specifications- Description
The ACTIVE* State is similar to the ACTIVE State, the PICC is selected and listens to any
higher layer message.
- State exit conditions and transitions:
The PICC enters the HALT State when a valid halt command (HLTA) is received.
(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

79

Version 1.1

12.1.3 Command Set(1) Basic Specifications
The Commands used by the PCD to manage communication with several PICCs are:- Request command (REQA)- Wakeup command (WUPA)- Anticollision command (ANTICOLLISION)- Select command (SELECT)- Halt command (HLTA)
The commands use the byte and frame formats described in "12.1.1 Frame Formats and Timing".
(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

80Version 1.1

12.1.3.1 REQA and WUPA Command(1) Basic Specifications
The request (REQA) and wakeup (WUPA) Commands are sent by the PCD to probe the field for
PICCs of Type A. They are transmitted within a short frame.
See "Fig. 12.1-6 PICC Type A State Diagram" to check in which cases PICC actually have toanswer to these respective commands. Particularly the WUPA Command is sent by the the PCD
to put PICCs which have entered the HALT State back into the READY* State. They shall thenparticipate in furture anticollision and selection procedures.
"Table 12.1-2 Coding of Short Frame" shows the coding of REQA and WUPA Commands which
use the Short frame format.
Table 12.1-2
b7
0
1
0

b6
1
0
1

b5
0
1
1

b4
0
0
0

b3
1
0
1

b2
1
1
0

1
1

0
1

0
x
x
x
1
1
x
x
all other values

Coding of Short Frameb1
Description
0 '26' = REQA command
0 '52' = WUPA command
1 '35' = Time slot type
(See "12.5 Type A Timeslot - Initialization andAnticollision")x '40' to '4F' = Proprietary
x '78' to '7F' = Proprietary
RFU(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

81Version 1.1

12.1.3.2 ANTICOLLISION and SELECT Command(1) Basic Specifications
These commands are used during and anticollission loop (see "Fig. 12.1-4 Bit organization andtransmission of bit oriented anticollision frame, case FULL BYTE" and "Fig. 12.1-5 Bit
organization and transmission of bit oriented anticollision frame, case SPLIT BYTE").
The ANTICOLLISION and SELCT Command consists of:- select code SEL (1 byte);- number of valid bits NVB (1 byte, for coding see Table 7);- 0 to 40 data bits of UID CLn according to the value of NVB.
SEL specifies the cascade level CLn. Refer to "12.1.4.3 (c) Coding of NVB (Number of Valid
Bits)" for information of encoding of NVB.
The ANTICOLLISION Command is transmitted within bit oriented anticollision frame.
SELECT Command is transmitted within standard frameThe

As long as NVB does not specify 40 valid bits, the command is called ANTICOLLISION
Command, where the PICC remains in READY or READY* State.
If NVB specifies 40 data bits of UID CLn (NVB='70'), a CRC_A shall be appended. This
command is called SELECT Command. If the PICC has transmitted the complete UID, it transits
from READY State to ACTIVE State or from READY* State to ACTIVE* State and indicates in
its SAK response that UID is complete. Otherwise, the PICC remains in READY or
READY*State and the PCD shall initiate a new anticollision loop with increased cascade level.
(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

82Version 1.1

12.1.3.3 Halt Command(1) Basic Specifications
The HLTA Command consists of two bytes followed by CRC_A and shall be transmitted withinStandard Frame.
The details of the frame of the halt command are shown in "Fig. 12.1-7 Standard Frame Containing
HLTA Command".
First bit transmitted
↓
S

'50'

Fig. 12.1-7

'00'

CRC_A

E

Standard Frame Containing HLTA Command

If the PICC responds with any modulation during a period of 1ms after the end of the frame
containing the HLTA Command, this response shall be interpreted as 'not acknowledge'.
(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

83Version 1.1

12.1.4 Select Sequence
The purpose of the select sequence is to get the UID from one PICC and to select this PICC for
further communication.
12.1.4.1 Select Sequence Flowchart(1) Basic Specifications
A select sequence flowchart is shown in "Fig. 12.1-8 Initialization and Anticollision Flowchart for
PCD".

84

Version 1.1

ISO/IEC 14443-3
Start

Send REQA

Receive ATQA

proprietary anticollision

Check
ATQA

bit frame anticollision

Select cascadelevel 1

Increase cascadelevel

Perform bit frame
anticollision loop••

UID not
complete••

Proprietary
frames andprotocols

Check
SAK

UID complete
PICC compliant toISO/IEC 14443-4

ISO/IEC 14443-4

Proceeds with commands and protocols
defined in ISO/IEC 14443-4

Fig. 12.1-8

UID complete
PICC not compliant toISO/IEC 14443-4

Proprietarycommands
and protocols

Initialization and Anticollision Flowchart for PCD

85

Version 1.1(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

86Version 1.1

12.1.4.2 ATQA-Answer To Request(1) Basic Specifications
After a REQA Command is transmitted by the PCD, all PICCs in the IDLE State shall respondsynchronously with answer to request signal (ATQA).
After a WUPA Command is transmitted by the PCD, all PICCs in the IDLE or HALT State shall
respond synchronously with answer to request signal (ATQA).
The PCD shall detect any collision that may occur when multiple PICCs respond.
An example is given in "12.3 Communication Example Type A".
(a) Coding of ATQA
Encoding of an answer to request signal (ATQA) is shown in "Table 12.1-3 Coding of ATQA".

Table 12.1-3
MSB
b16 b15 b14 b13(0000)bOther values are RFU

Coding of ATQA

b7
b8
UID size
bit frame

b12 b11 b10 b9
Proprietary coding

87

b6
R
F
U

b5

LSB
b4
b3
b2
b1
Bit frame anticollision

Version 1.1(b) Coding rules for bit frame anticollision- Rule 1: Rule 1: Bits b7 and b8 ode the UID size (single, double or triple, see "Table 12.1-4
Coding of b7, b8 for Bit Frame Anticollision").
- Rule 2: One out of the five bits b1, b2, b3, b4 or b5 shall be set to (1)b to indicate bit frame
anticollision (see "Table 12.1-5 Coding of b1-b5 for Bit Frame Anticollision").
NOTE

Bit9 to bit 12 indicate additional and proprietary methods.

Table 12.1-4
b8
0
0
1
1

Table 12.1-5
b5
1
0
0
0
0

Coding of b7, b8 for Bit Frame Anticollision
b7
0
1
0
1

Meaning
UID size: Single
UID size: Double
UID size: Triple
RFU

Coding of b1-b5 for Bit Frame Anticollision

b4
b3
b2
0
0
0
1
0
0
0
1
0
0
0
1
0
0
0
Other values

b1
0
0
0
0
1

Meaning
Bit frame anticollision
Bit frame anticollision
Bit frame anticollision
Bit frame anticollision
Bit frame anticollision
RFU(0) Extended Specifications
None(1) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

88Version 1.1

12.1.4.3 Anticollision and Select(1) Basic Specifications(a) Anticollision loop within each cascade level
The following algorithm shall apply to the anticollision loop:
1)

The PCD shall assign SEL with the code for the selected anticollision type and cascade level.

2)

The PCD shall assign NVB with the value of '20'.
Note: This value defines that the PCD will transmit no part of UID CLn. Consequently thiscommand forces all PICCs in the field to respond with their complete UID CLn.

3)

The PCD shall transmit SEL and NVB.

4)All PICCs in the field shall respond with their complete UID CLn.

5)

Assuming the PICCs in the field have unique serial numbers, then if more than one PICC
responds, a collision occurs. If no collision occurs, steps 6) to 10) shall be skipped.

6)

The PCD shall recognize the position of the first collision.

7)

The PCD shall assign NVB with a value that specifies the number of valid bits of UID CLn.
The valid bits shall be part of the UID CLn that was received before a collision occurredfollowed by a (0)b or (1)b, decided by the PCD. A typical implementation adds a (1)b.

8)

The PCD shall transmit SEL and NVB, followed by the valid bits.

9)

Only PICCs of which the part of UID CLn is equal to the Valid bits transmitted by the PCD
shall transmit their remaining bits of the UID CLn.

10) If further collisions occur, steps 6) to 9) shall be repeated.
will be 32.

89

The maximum number of loops

Version 1.1

11) If no further collision occurs, the PCD shall assign NVB with the value of '70'.
Note: This value defines that the PCD will transmit the complete UID CLn.
12) The PCD shall transmit SEL and NVB, followed by all 40 bits of UID CLn, followed by
CRC_A checksum.
13) The PICC which UID CLn matches the 40 bits shall respond with its SAK.
14) If the UID is complete, the PICC shall transmit SAK with cleared cascade bit and shalltransit from READY State to ACTIVE State to ACTIVE* State..
15) The PCD shall check if the cascade bit of SAK is set to decide whether further anticollision
loops with increased cascade level shall follow.
If the UID of a PICC is complete and known by the PCD, the PCD may skip step 2- step 10 toselect this PICC without performing the anticollision loop.
The above procedure from 1) to 13) is illustrated in "Fig. 12.1-9 Anticollision Loop, Frowchart for
PCD".

90

Version 1.1

Start ofanticollision loop

1)

SEL: = code (cascade level)2)

NVB= '20'

7)

NVB= '20'+coll

3)

TransitANTICOLLISION command

8)

TransitANTICOLLISION command

SEL

SEL

NVB

4)

UID CLn

9)

Receive UID CLn
10)
Yes
6)

Collision?

5)

NVB

coll:
= Position of first collision

No
11)

12)

NVB= '70'

Transit Select command
SEL

NVB

13)

UID CLn

CRCA

Receive SAK

End ofanticollision loop

Fig. 12.1-9

Anticollision Loop, Flowchart for PCD

91

Version 1.1(b) Coding of SEL (Select code)- Length: 1 byte
- Possible values: '93', '95', '97'
Details are shown in "Table 12.1-6 Coding of SEL ".

Table 12.1-6
b8
1
1
1
1

b7
0
0
0
0

b6
0
0
0
0

b5
1
1
1
1

b4
0
0
0

b3 b2 b1
0
1
1
1
0
1
1
1
1
Other values

Coding of SEL

Meaning'93': Select cascade level 1'95': Select cascade level 2'97': Select cascade level 3
RFU

92

Version 1.1(c) Coding of NVB (Number of Valid Bits)- Length: 1 byte
The upper 4 bits are called "Byte count" and specify the integer part of the number of all valid databits transmitted by the PCD (including SEL and NVB) divided by 8. Consequently, the minimum
value of "Byte count" is 2 and the maximum value is 7.
The lower 4 bits are called "bit count" and specify the number of all valid data bits transmitted by
the PCD (including SEL and NVB) modulo 8.
The details are shown in "Table 12.1-7 Coding of NVB ".

Table 12.1-7

Coding of NVB

b8

b7

b6

b5

Meaning

b4

b3

b2

b1

Meaning

0

0

1

0

Byte count = 2

0

0

0

0

bit count = 0

0

0

1

1

Byte count = 3

0

0

0

1

bit count = 1

0

1

0

0

Byte count = 4

0

0

1

0

bit count = 2

0

1

0

1

Byte count = 5

0

0

1

1

bit count = 3

0

1

1

0

Byte count = 6

0

1

0

0

bit count = 4

0

1

1

1

Byte count = 7

0

1

0

1

bit count = 5

0

1

1

0

bit count = 6

0

1

1

1

bit count = 7

93Version 1.1(d) Coding of SAK (Select acknowledge)
SAK is transmitted by the PICC when NVB has specified 40 valid data bits and when all these databits math with UID CLn. The composition of SAK is shown in "Fig. 12.1-10 Select acknowledge(SAK) ".
1st byte

2nd and 3rd bytes

SAK

CRC_A

MSB     LSB

MSB           LSB

Fig. 12.1-10

Select Acknowledge (SAK)PCD checks b3 in order to investigate whether or not the UID is complete.
(cascade bit) and b6 is given in "Table 12.1-8 Coding of SAK ".
Table 12.1-8

The coding of bits b3

Coding of SAK

b8

b7

b6

b5

b4

b3

b2

b1

x

x

x

x

x

1

x

x

x

x

1

x

x

0

x

x

x

x

0

x

x

0

x

x

Meaning
Cascade bit set: UID not complete
UID complete.
PICC compliant with ISO/IEC 14443-4
UID complete.
PICC not compliant with ISO/IEC 14443-4

If the UID is not complete, the PICC remains in the READY state or READY* state. The PCD
advances the cascade level by 1 and repeats the anticollision loop.
In the case of the UID is complete, the PICC clears the cascade bit, returns SAK and changes fromthe READY state to the ACTIVE state or from the READY* state to the ACTIVE* state. If the
PICC complies with ISO/IEC 14443-4, the PICC sets b6 of SAK.

94

Version 1.1(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

95Version 1.1

12.1.4.4 UID Contents and Cascade Levels(1) Basic Specifications
The UID consists of 4, 7 or 10 UID bytes. Consequently, the PICC shall handle up to 3 cascadelevels to get all UID bytes. Within each cascade level, a part of UID shall be transmitted to the
PCD. According to the cascade level, three types of UID size are defined. This UID size shallbe consistent with "Table 12.1-9 UID size ".
Table 12.1-9
Cascade level1
2
3

UID size
SingleDoubleTripleUID Size
Number of UID bytes
47
10The contents of the UID are specified as shown below.
- UID CLn UID portion at cascade level n (3 ≥ n ≥ 1)
- UIDnnth (n ≥ 0) byte of UID- BCC Exclusive OR of first 4 bytes among checked bytes of UID CLn- CT
Cascade tag (value is '88')
The UID is a fixed unique number or a random number which is dynamically generated by the
PICC. The first byte (uid0) of the UID assigns the content of the following bytes of the UID.
The contents of UID during single operation are shown in "Table 12.1-10 Single size of UIDs ".

Table 12.1-10
uid0
'08'
'x0' - 'x7''x9' - 'xE'
'18' - 'F8'
'xF'

Single Size of UIDs

Description
uid1 to uid3 is a random number which is dynamically generated
proprietary fixed number
RFU

The value '88' of the cascade tag CT shall not be used for uid0 in single size UID

96

Version 1.1

The contents of double size and triple size UIDs are shown in "Table 12.1-11 Double and triple
size UIDs ".
Table 12.1-11

Double and Triple Size UIDs

uid0
Description
Manufacturer ID according to Each manufacturer is responsible for making characteristic
ISO/IEC 7816-6/AM1 (*)
values other than uid0 characteristic.
(*) The value '81' to 'FE', which are marked for 'Private use' in ISO/IEC 7816-6/AM1 shall not beallowed in this context.
The method of using the cascade levels is shown in "Fig. 12.1-11 Usage of Cascade Levels".

UID
size
single

PCD

UID
size
double

PCD

UID
size
triple

PCD

'93'

PICC

uid0 uid1 uid2 uid3 BCC'93'

CT uid0 uid1 uid2 BCC

PICC

PICC

'95'

'93'

uid3 uid4 uid5 uid6 BCC

'95'

'97'

CT uid0 uid1 uid2 BCC

CT uid4 uid5 uid6 BCC

uid6 uid7 uid8 uid9 BCC

Cascade level 1

Cascade level 2

Cascade level 3

Fig. 12.1-11

Usage of Cascade Levels

NOTE: The purpose of the cascade tag is to force a collision with PICCs that have a smaller UID
size. Consequently, UID0 and UID3 must not have the same values as the value of the cascade
tag.

97

Version 1.1

The procedure by which the PCD obtains a complete UID is as shown below.
- Step 1: The PCD selects cascade level1- Step 2: The anticollison loop shall be performed- Step 3: The PCD shall check the cascade bit of SAK- Step 4: If the cascade bit is set, the PCD shall increase the cascade level and initiate a new
anticollision loop
(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

98Version 1.1

12.2Type B - Initialization and Anticollison
This section describes the initialization and collision detection protocol application for PICCs of
Type B.
12.2.1 Character, Frame Format and Timing(1) Basic Specifications
This section defines the character, frame format and timing used during communication
initialization and anticlossion for PISSs of Type B. For bit representation and coding refer to
ISO/IEC 14443-2.
(2) Extended Specifications
None(3) References
None

99

Version 1.1

12.2.1.1 Character Transmission Format(1) Basic Specifications
Bytes are transmitted and received between PICCs and a PCD by characters, the format of which
during the Anticollision sequence is as follows:- 1 start bit at logic "0";- 8 data bits transmitted, LSB first;- 1 stop bit at logic "1";
The transmission of one byte is performed with a character requiring 10 etu as illustrated in "Fig.
12.2-1 Character Format".
Start

LSB
b1

MSB
b2

b3

b4

b5

b6

b7

Stop

EGT

b8

10etu
Fig. 12.2-1

Character Format

Bit boundaries within a character shall occur between (n-0.125) etu and (n+0.125)etu where n is
the number of bit boundaries after the start bit falling edge (1 ≤ n ≤ 9)(2) Extended Specifications
None(3) References
None

100

Version 1.1

12.2.1.2 Character Separation(1) Basic Specifications
A character is separated from the next one by the extra guard time EGT.
The EGT between 2 consecutive characters sent by the PCD to the PICC shall be between 0 and 57µs.
The EGT between 2 consecutive characters sent by the PCD to the PICC shall be between 0 and 19µs.
(2) Extended Specifications
None(3) References
None

101

Version 1.1

12.2.1.3 Frame Format(1) Basic Specifications
PCDs and PICCs shall send characters as frames.
by EOF.

The frame is normally delimited by SOF and

The frame organization used by PCD and PICC is shown in "Fig. 12.2-2 Frame Format".

SOF

CharacterFig. 12.2-2

Frame Format(2) Extended Specifications
None(3) References
None

102

EOF

Version 1.1

12.2.1.4 Start Of Frame (SOF)(1) Basic Specifications
SOF is composed of:- one falling edge;- followed by 10 etu with a logic "0";- followed by one single rising edge located anywhere within the following etu;
- followed by at least 2 etu (but no more than 3 etu) with logic "1".
The composition of SOF is shown in "Fig. 12.2-3 SOF".

No (sub) carrier
modulation≥10 etu, ≤ 11 etu≥2etu, ≤3etu(2) Extended Specifications
None(3) References
None

103

b1

1st character≥12 etu, ≤14 etu

Fig. 12.2-3

Start

SOF

b2

Version 1.1

12.2.1.5 End Of Frame (EOF)(1) Basic Specifications
EOF is composed of:- one falling edge;- followed by10 etu with a logical "0";- followed by one single rising edge located anywhere within the following etu.
The composition of EOF is shown in "Fig. 12.2-4 EOF".

EOF

Last character≥10 etu, ≤11 etu

No (Sub)carrier

Transition
Fig. 12.2-4

modulation

EOF

Note: The probability of receiving a false EOF is low and corresponds to the transmission of a '00'
character with a wrong reception of the stop bit.
(2) Extended Specifications
None(3) References
None

104

Version 1.1

12.2.1.6 Subcarrier from PICC to PCD and SOF(1) Basic Specifications
PICC start of communication after a PCD data transmission shall respect the timing defined in "Fig.
12.2-5 PICC subcarrier SOF ".
The default minimum values of TR0 and TR1 are defined in ISO/IEC 14443-2 and may be reducedby the PCD, (see "12.2.10 ATTRIB Command").
The maximum value of TR0 is 256/fs for ATQB only and (256/fs)*2FWI for all other frames.
maximum value of TR1 is 200/fs.

PCD

Last character

Unmodulated carrier

EOF
T0

T1

Unmodulated
carrier ON

PICC
Subcarrier OFF

SOF

Fig. 12.2-5 PICC subcarrier SOF
A PICC may turn on the subcarrier only if it intends to begin transmitting information.
(2) Extended Specifications
None(3) References
None

105

The

Version 1.1

12.2.1.7 Subcarrier from PICC to PCD and EOF(1) Basic Specifications
PCD start of communication after a PICC data transmission and EOF shall EOF shall respect thetiming defined in "Fig. 12.2-6 PICC to PCD EOF".
The PICC shall turn off its subcarrier after the transmission of the EOF.
shall:- not be stopped before the end of the EOF;
- be stopped no later than etu after the end of the EOF.

The subcarrier signal

The minimum delay between the PICC EOF start (falling edge) and the PCD SOF start (fallingedge) is 10 etu + 32/fs.

PICC
subcarrier
PICC
data

fs ON

fs to OFF

Last character≤2etu

fs OFF

Undefined

EOF
PCD≥10etu+32/fs

Fig. 12.2-6

PICC to PCD EOF(2) Extended Specifications
None(3) References
None

106

SOF

Version 1.1

12.2.2 Cyclic Redundancy Check Code (CRC_B)(1) Basic Specifications
The frame insertion position of CRC_B is shown in "Fig. 12.2-7 Frame Insertion Position of
CRC_B".

1st byte………nth byte
Data byte(n bytes)
MSB

CRC_B
(2 bytes)
LSB

Fig. 12.2-7

MSB

LSB

Frame Insertion Position of CRC_B

The frame CRC_B is a function of k data bits, which consist of all the data bits in the frame,
excluding start bits, stop bits, delays between bytes, SOF and EOF, and the CRC_B itself. Sincedata is encoded in bytes, the number of bits k is a multiple of 8.
For error checking, the two CRC_B bytes are included in the frame, after the data bits and before
the EOF. The CRC_B is as defined in ISO/IEC 13239. The initial register content shall be all
ones: 'FFFF'.
Encoding examples of CRC_A and CRC_B are shown in "12.4 CRC_A and CRC_B Encoding".
(2) Extended Specifications
None(3) References
None

107

Version 1.1

12.2.3 Anticollision Sequence(1) Basic Specifications
An anticollision sequence is managed by the PCD through a set of commands detailed in thischapter. The PCD is the master of the communication with one or more PICCs. It initiates
PICC communication activity by issuing a REQB Command to prompt for PICCs to respond.
During the anticollsioin sequence it may happen that two or more PICCs respond simultaneously:
this is a collision. The command set allows the PCD to handle sequences to separate PICC
transmissions in time. The PCD may repeat its anticollision procedure until it finds all PICCs in
the operating volume.
Having completed the anticollision sequence, PICC communication will be under control of the
PCD, allowing only one PICC to talk at a time.
The collision scheme is based on definition of timeslots in which PICCs are invited to answer withminimum identification data. The number of slots is parameterized in the REQB/WUPB and canvary from one to some integer number. PICC response probability in each timeslot is also
controllable. PICCs are allowed to answer only once in the anticollosion sequence.
Consequently, even in case of multiple PICCs present in the PCD filed, there will probably be aslot in which only one PICC answers and where the PCD is able to capture the identification data.
Based on the identification data the PCD is able to establish a communication channel with theidentified PICC.
An anticollision sequence allows selection of one or more PICCs for further communication at any
time.
The set of commands allows implementation of different anticollision management strategies at the
PCD level. This strategy is under the control of the application designer and can include:- probabilistic (repetitive single slot prompt with response probability less than or equal to 1);- pseudo-deterministic (multiple slots with scanning of them during the anticollision sequence tohave the maximum probability that all present PICCs answer);(2) Extended Specifications
None(3) References
None

108

Version 1.1

12.2.4 PICC States Description(1) Basic Specifications
An example of a flow chart of the Different states and transition conditions between states isshown in "Fig. 12.2-8 PICC state transition flowchart example".

109

Version 1.1

Power OFFPower OFF

Idle

Wait for REQB
or WAKE_UP

Else

REQB or WUPB
Yes

No

Matched AFI

Yes

No

N=1?

Option 2

Wait for MatchedElseslot markers

REQB or
WUPB

Matched Slot Marker

Else

Wait for Matched ATRIBor HALTB

Matched HALTB

Matched ATTRIB
Send answer toATTRIBElseREQB or WUPB

Send answer to HALTACTIVE

Ready declared

ATQB sent

ActiveDESELECT
Else

Halt

HALT
WUPB

Fig. 12.2-8

PICC state transition flowchart example

110

Anticollision

R=1

Ready

R>1

Select R

Ready Requested

Option 1

Version 1.1- Note 1:
In the Figure, R is a random number chosen by the PICC in the range from 1 to N (refer to"12.2.7.4 Encoding of PARAM" for information on encoding of N).
- Note 2:
In the Figure, OPTION 1: For PICCs not supporting Slot-MARKER Command (Probabilistic
approach). OPTION 2: For PICC supporting Slot-MARKER Command (Timeslot approach).
(2) Extended Specifications
None(3) References
In the case of not using Slot_MARKER commands, namely in the case of using the Timeslot
approach, processing is performed as shown below. However, since this type of processing is notdefined in the specifications of ISO/IEC 14443, adequate considerations are to be given to thesystem when using this type of processing.
In "Fig. 12.2-8 PICC State Transition Flowchart Example", processing to evaluate b5 of the
PARAM portion of REQB after evaluating whether or not AFI match, is added.
If b5 = (0)b, processing proceeds to evaluating whether or not N = 1. Subsequent processing is
the same as in "Fig. 12.2-8 PICC State Transition Flowchart Example ".
If case b5 = (1)b, processing is performed in the order shown below.
1) R select2) Wait until slot timing agree
3) Send ATQB (subsequent processing is the same as in "Fig. 12.2-8 PICC State Transition
Flowchart Example ")The PCD sends a command in which b5 of the PARAM portion of REQB is set to (1)b.

111

Version 1.1

12.2.4.1 General Statement for State Description and Transitions(1) Basic Specifications
To any state the following shall apply:- the PICC shall return to POWER_OFF State if the RF field disappears.
To any state specific to the anticollision sequence (except ACTIVE State) the following shallapply:- Default communication parameters as defined in "12.2.1 Character, Frame Format and Timing"
shall be used.
- The PICC shall not emit subcarrier except to transmit response frames as specified in theprevious sections.
- The PICC will become able to receive commands from the PCD when power is transmitted to
the PICC and reset is released.
- If a frame from the PCD is valid (correct CRC_B), the PICC shall perform the required action
and/or response depending on its state as in anticollision commands the first 3 bits of the data ina frame are (101)b (3 first bits of anticollision Prefix byte)- The PICC shall not answer to any command frame not stating with (101)b.
- The PICC shall only react to valid frames received (no response sent when transmission errors
are detected).
(2) Extended Specifications
None(3) References
None

112

Version 1.1

12.2.4.2 Power OFF State(1) Basic Specifications- Definition of StateIn the POWER-OFF State, the PICC is not powered due to a lack of carrier energy.
State exit conditions and transitions:- Conditions for State Transition and Transition Destination
If the PICC is in an energizing magnetic field greater than Hmin (see "8. Power Transfer"), it shallenter its IDLE State within a delay not greater than defined in "11. Polling").
(2) Extended Specifications
None(3) References
None

113

Version 1.1

12.2.4.3 IDLE State(1) Basic Specifications- Definition of StateIn the IDLE State, the PICC is powered.
WUPB messages.

It listens for frames and shall recognize REQB and- State exit conditions and transitions:
On reception of valid REQB or WUPB Command frames the PICC moves onto the READY
REQUESTED sub-state. (Valid REQB/WUPB means valid with REQB/WUPB Command andmatched AFI. See "12.2.7 REQB/WUPB Commands" for details.
(2) Extended Specifications
None(3) References
None

114

Version 1.1

12.2.4.4 READY-REQUESTED Sub-state(1) Basic Specifications- Definition of StateIn the READY-REQUIRED sub-state, the PICC is powered and has received a valid REQB or
WUPB Commands with a control parameter N. The PICC calculate a random number R which isused to control its subsequent operation as described in "12.2.6 Anticollision Response Rules".
- State exit conditions and transitions:
Refer to "12.2.6 Anticollision Response Rules.
(2) Extended Specifications
None(3) References
None

115

Version 1.1

12.2.4.5 READY-DECLARED Sub-state(1) Basic Specifications- Definition of StateIn the READY-DECLARED sub-state, the PICC is powered and has sent its ATQB corresponding
to the last valid REQB/WUPB message received. It listens to frames and shall recognize
REQB/WUPB ATTRIB and HLTB commands.
- State exit conditions and transitions:
On reception of a valid ATTRIB Command the PICC shall enter the ACTIVE State if the PUPI in
the ATTRIB Command matches the PICC PUPI.
If the PUPI in the ATTRIB Command does not match the PICC PUPI the PICC remains in the
READY-DECLARED sub-state.
On reception of a valid REQB/WUPB Command frame the same conditions and transitions apply
as on reception of a valid REQB/WUPB Command in the IDLE State.
On reception of a matched HLTB Command the PICC shall enter the HALT State.
(2) Extended Specifications
None(3) References
None

116

Version 1.1

12.2.4.6 ACTIVE State(1) Basic Specifications- Definition of StateThe PICC is powered and has entered a higher layer mode since a Card Identifier (CID) has been
assigned to this PICC through the ATTRIB Command.
The PICC listens to any higher layer message properly formatted (proper CID and valid CRC_B)
The PICC shall not emit subcarrier following any frame with invalid CRC_B or with another CID
than the one assigned.
- State exit conditions and transitions:
The PICC enters the HALT State when a valid DESELECT Command frame is received(DESELECT Command is defined in ISO/IEC 14443-4).
- Specific remarks:
Valid REQB/WUPB or Slot-MARKER frames shall not be answered. A valid frame with an
ATTRIB Command shall not be answered.
In the higher layer protocol, specific commands may be defined to return the PICC to other states(IDLE or HALT). The PICC may return to these states only following reception of suchcommands.
(2) Extended Specifications
None(3) References
None

117

Version 1.1

12.2.4.7 HALT State(1) Basic Specifications- Definition of StateThe PICC shall respond only to a WUPB Command which brings it back to the IDLE State.
- State exit conditions and transitions:
The PICC returns to the POWER_OFF State if the RF field disappears.
(2) Extended Specifications
None(3) References
None

118

Version 1.1

12.2.5 Command Set(1) Basic Specifications
Four primitive commands are used to manage multi-node communication channels:- REQB/WUPB- Slot_MARKER- ATTRIB- HLTB
These four commands use the bit and byte formats described in detail in "12.2.1 Character andFrame Formats and Time Specifications".
The commands and the response of the PICC to these commands are described in the following
sections. Any frame received with a wrong format (wrong frame identifiers or invalid CRC_B)
shall be ignored.
(2) Extended Specifications
None(3) References
The PCD does not send Slot_MARKER command.

119Version 1.1

12.2.6 Anticollision Response Rules(1) Basic Specifications
A PICC which is in the READY-REQUESTED sub-state, after receiving a valid REQB/WUPB
Command (Requested AFI=0 or AFI matched with an internal application), shall respond according
to the following the rules, where the parameter N has been given in the REQB/WUPB Commands:a) If N= the PICC shall send an ATQB and shall move to the READY-DECLATED sub-stateb) If N>1 the PICC shall internally generate a random number R which shall be evenly distributed
between 1 to N
1) If R=1 the PICC shall send am ATQB and shall move to the READY-DECLARED sub-state.
2) If R>1 PICCs employing the probabilistic approach shall return to IDLE State; PICCs
employing the slot marker approach shall wait until they have received a Slot-MARKER
Command with a matched slot number (slot number=R) before sending the ATQB andmoving to the READY-DECLARED sub-state.

120

Version 1.1(2) Extended Specifications
None(3) References
If b5 of the PARAM portion of REQB/WUPB is (0)b, basic specifications are applied, and if it is(1)b, processing is performed as described below.
a) When N = 1: The PICC sends ATQB.
b) When N > 1: The PICC internally generates a random number R (1 ≤ R ≤ N).
The PICC then sends ATQB after waiting for a period corresponding to the value of R.
The relationship between random number R (= slot number) and the timing by which ATQB is sent
is as shown below.
1) When R = 1:
The period of 32 etu following completion of EOF of the REQB/WUPB command sent by
the PCD shall be the guard time tA. Following completion of tA, a period of 240 etu (tB)shall be the first slot. The PICC may send ATQB at any arbitrary timing of the first slot.
However, the period of the final 10 etu (tC) in tB shall be the inter-slot guard time, and the
PICC must not send out a subcarrier during this time.
2) When R > 1:
The period of 240 etu following completion of the (R-1)st slot shall be the Rth slot. The
PICC may send ATQB at any arbitrary timing of the Rth slot. However, the period of the
final 10 etu (tC) in tB shall be the inter-slot guard time, and the PICC must not send out asubcarrier during this time.

121

Version 1.1

12.2.7 REQB/WUPB Command(1) Basic Specifications
The REQB and WUPB Commands sent by the PCD are used to probe the field for PICCs of TypeB.
In addition WUPB is particularly used to also wake up PICCs which are in HALT Sate.
The number of slots N is included in the command as a parameter to optimize the anti-collisionalgorithm for a given application. See "Fig. 12.2-8 PICC state Transition Flowchart Example" fordetailed description of when the PICC shall respond to these respective commands.
(2) Extended Specifications
None(3) References
None

122

Version 1.1

12.2.7.1 REQB/WUPB Command Format(1) Basic Specifications
These commands are send out in the form of 5 bytes by the PCD.
REQB/WUPB Command Format" for details.
APf(1 byte)MSB

AFI(1 byte)LSB

MSB

Fig. 12.2-9

PARAM(1 byte)

LSB

MSB

LSB

CRC_B
(2 bytes)
MSB

REQB/WUPB Command Format(2) Extended Specifications
None(3) References
None

123

Refer to "Fig. 12.2-9

LSB

Version 1.1

12.2.7.2 Coding of Anticollision Prefix byte APf(1) Basic Specifications
The Anticollision Prefix byte is APf = '05' = (0000 0101)b.
(2) Extended Specifications
None(3) References
None

124

Version 1.1

12.2.7.3 Coding of AFI(1) Basic Specifications
AFI (Application Family Identifier) represents the type of application targeted by the PCD and isused to preselect PICCs before the ATQB. Only PICCs with applications of the type indicated by
the AFI may answer to a REQB/WUPB Command with AFI different to '00'.
When AFI is '00', all PICCs shall process the REQB/WUPB.
The most significant half byte of AFI is used to code one specific or all application families, as
defined in "Table 12.2-1 Coding of AFI". The least significant half byte of AFI is used to code
one specific or all application sub-families. Sub-family codes different from 0 are proprietary.
Table 12.2-1

Coding of AFI

AFI
AFI
Meaning upper 4 bits lower 4 bits
PICCs respond from'0'
'0'
All families and sub-families
X'0'
All sub-families of family X
XY
Only the Yth sub-family and family X'0'Y
Proprietary sub-family Y only
'1''0' , Y
Transport'2''0' , Y
Financial'3''0' , Y
Identification'4''0' , Y
Telecommunication'5''0' , Y
Medical'6''0' , YMultimedia'7''0' , Y
Gaming'8''0' , Y
Data storage'9' - 'F''0' , Y
RFU
- Remarks: X = '1' to 'F', Y = '1' to 'F'

125

Example/Note
No application preselection
Wide application preselection

Mass transit, Bus, Airline, ...
IEP, Banking, Retail, ...
Access Control, ...
Public Telephony, GSM, ...
Internet services....
Portable Files, ....

Version 1.1(2) Extended Specifications
None(3) References
The AFI set for the PICC shall be '00'.
AFI is not '00'.

The PICC shall not to respond to REQB/WUPB for which

In addition, the PCD shall set AFI = '00' and sends an REQB/WUPB command.

126

Version 1.1

12.2.7.4 Coding of PARAM(1) Basic Specifications
Details of encoding of the PARAM byte in the REQB/WUPB commands are shown in "Fig.
12.2-10 Coding of PARAM" and "Table 12.2-2 Encoding of N".
b8 = 0b7 = 0 b6 = 0 b5 = 0
RFU
All RFU bits shall be set to 0
Fig. 12.2-10

b4
REQB / WUPB

b3
b2
b1
N(Number of slots)

Coding of PARAM

b4 = 0 defines REQB: PICCs in IDLE State or READY State shall process this command
b4 = 1 defines WUPB: PICCs in IDLE State or READY State or HALT State shall process thiscommandb1, b2 and b3 are used to code the number of slots N according to "Table 12.2-2 Coding of N".

Table 12.2-2
b3
0
0
0
0
1
1
1

b2
0
0
1
1
0
0
1

Coding of N

b1
0
1
0
1
0
1
x

N
1 = 202 = 21
4 = 22
8 = 2316 = 24
RFU
RFU

NOTE: For each PICC, the probability of response (ATQB) in the first slot is 1/N. Thus, if theprobabilistic approach is used in the PCD, N is not used to adjust the number of slots but theprobability for the PICC to return its ATQB in this unique slot.

127

Version 1.1(2) Extended Specifications
None(3) References
The PICC supports time slot type anticollision processing.
The PCD sends a command by setting b5 = 1.

128

Version 1.1

12.2.8 Slot Marker Command (Slot_MARKER)(1) Basic Specifications
After a REQB/WUPB Command, the PCD may send up to (N-1) Slot_MARKER Commands todefine the start of each timeslot.
Slot_MARKER Commands can be sent:- after the end of an ATQB message received by the PCD to make the start of the next slot;- or earlier if no ATQB is received (no need to wait until the end of a slot, if this slot is known tobe empty).
It is not mandatory for PICC to support this command. In this case, the PICC shall ignore any
Slot_MARKER Command. The PICC may only send its ATQB after REQB (in the first slot) in aprobabilistic approach.
(2) Extended Specifications
None(3) References
The PCD does not send a Slot_MARKER command.

129

Version 1.1

12.2.8.1 Slot Marker Command (Slot_MARKER) Format(1) Basic Specifications
The slot marker command (Slot_MARKER) is send out using 3 bytes by the PCD.
shown in "Fig. 12.2-11 Slot Marker Command (Slot_MARKER) Format".
APn(1 byte)

CRC_B(2 bytes)

MSB     LSB

MSB           LSB

Fig. 12.2-11

Slot Marker Command (Slot_MARKER) Format(2) Extended Specifications
None(3) References
The PCD does not send a Slot_MARKER command.

130

The format is

Version 1.1

12.2.8.2 Coding of Anticollision Prefix byte APn(1) Basic Specifications
The value of the anticollision prefix byte (APn) is APn = (nnnn0101)b. Here, (nnnn)b is the slot
number. The relationship between nnnn and slot number is specified in "Table 12.2-3 Coding of
Slot Number".

Table 12.2-3

Coding of Slot Number

Nnnn
Slot nubmer
0001
2
0010
3
0011
4
..........
..........
1110
15
1111
16
NOTE: It is not mandatory that the Slot_MARKER Commands are sent sequentially withincremental slot numbers.
(2) Extended Specifications
None(3) References
The PCD does not send a Slot_MARKER command.

131

Version 1.1

12.2.9 Answer to Request (ATQB)(1) Basic Specifications
The response to both REQB/WUPB and Slot_MARKER Commands is named ATQB.
(2) Extended Specifications
None(3) References
None

132

Version 1.1

12.2.9.1 ATQB Format(1) Basic Specifications
The format of ATQB send out from a PICC is shown in "Fig. 12.2-12 ATQB Format".
1st byte'50'(1 byte)

2nd to 5th bytes
PUPI(4 bytes)

6th to 9th bytes
Application data
(4 bytes)Fig. 12.2-12

10th to 12th bytes
Protocol information(3 bytes)

ATQB Format(2) Extended Specifications
None(3) References
None

133

13th and 14th bytes
CRC_B(2 bytes)

Version 1.1

12.2.9.2 Pseudo Unique PICC Identifier (PUPI)(1) Basic Specifications
A Pseudo-Unique PICC Identifier (PUPI) is used to differentiate PICCs during anticollision. This
4-byte number maybe either a number dynamically generated by the PICC or a diversified fixed
number. The PUPI may only change in the IDLE State.
(2) Extended Specifications
None(3) References
None

134

Version 1.1

12.2.9.3 Application Data
(1) Basic Specifications
The Application date field is used to inform the PCD which applications are currently installed in
the PICC. This information allows the PCD to select the desired PICC in the presence of morethan one PICC.
The application data is defined dependent upon the ADC (Application Data Coding) field in the
Protocol Info, which defines if either the CRC_B compressing method described below or
proprietary coding is used.
When the CRC_B compressing coding is used, Application Data field contains the following:
1st byte
AFI(1 byte)2nd and 3rd bytes
CRC_B (AID)(2 bytes)Fig. 12.2-13

4th byte
No. of applications(1 byte)Applicatino Data Format(a) AFIFor mono application PICCs AFI gives the family of the application (see Table 12.2-1).
For multi application PICCs AFI gives the family of the application described in CRC_B (AID).
(b) CRC_B (AID)
CRB_B (AID) is the result of calculation of CRC_B of the AID of an application in the PICC
matching the AFI given the REQB/WUPB Command.
(c) Number of Applications
Indicates on significant half byte value gives the number of application in the PICC.
The most significant half byte value gives the number of applications corresponding to the AFI
given in Application Data with '0' meaning no application and 'F' meaning 15 applications or more.
The least significant half byte value gives the total number of applications in the PICC with '0'
meaning no application and 'F' meaning 15 application or more.

135

Version 1.1(2) Extended Specifications
None(3) References
The following values are set for application data.
- 1st to 2nd bytes: Arbitrary value for each IC manufacturer- 3rd byte: IC manufacturer code specified in ISO/IEC 7816-6 Amendment 1- 4th byte: 'E0'136

Version 1.1

12.2.9.4 Protocol Info
(1) Basic Specifications
The Protocol Info field indicates the parameters supported by the PICC.
detailed in "Fig. 12-2-14 Protocol Info Format".
1st byte
Bit_Rate_
capability(8 bits)
MSB LSB

2nd byte
Max_Frame_
Protpcol_TypeSize(4 bits)(4 bits)
MSB
LSB

3rd byte
ADC

FWI(4 bits)
MSB(2 bits)

It is formatted asFO(2 bits)
LSB

Fig. 12-2-14 Protocol Info Format(a) Communication Speed Capability (8 bits)
The capability to support the communication speed of the PICC is shown in "Table 12.2-4 Bit
Rates Supported by the PICC".

Table 12.2-4 Bit Rates Supported by the PICC
b8

b7

b6

b5

b4

b3

b2

b1

0

0

0

0

0

0

0

0

PICC supports only 106 kbit/s in both directions

1

-

-

-

0

-

-

-

Same bit rate from PCD to PICC and from PICC to PCD compulsory.

-

-

-

1

0

-

-

-

PICC to PCD, 1etu=64 / fc, bit rate supported is 212 kbit/s

-

-

1

-

0

-

-

-

PICC to PCD, 1etu=32 / fc, bit rate supported is 424 kbit/s

-

1

-

-

0

-

-

-

PICC to PCD, 1etu=16 / fc, bit rate supported is 847 kbit/s

-

-

-

-

0

-

-

1

PCD to PICC, 1etu=64 / fc, bit rate supported is 212 kbit/s

-

-

-

-

0

-

1

-

PCD to PICC, 1etu=32 / fc, bit rate supported is 424 kbit/s

-

-

-

-

0

1

-

-

PCD to PICC, 1etu=16 / fc, bit rate supported is 847 kbit/s

Other values (b4 = 1)

Meaning

PFU

137

Version 1.1(b) Maximum Frame Sizes
The maximum frame sizes able to be received by the PICC are shown in "Table 12.2-5 Maximum
Frame Sizes".

Table 12.2-5 Maximum Frame Sizes
Maximum Frame Size
Code in ATQB
Maximum Frame
Size(byte)

0

1

2

3

4

5

6

7

8

9-F

16

24

32

40

48

64

96

128

256

RFU > 256(c) Protocol Type (4 bits)
Protocol types supported by the PICC are defined in "Table 12.2-6 Protocol Types Supported by
PICC".

Table 12.2-6

Protocol Types Supported by PICC

b4

b3

b2

b1

0

0

0

1

PICC compliant with ISO/IEC 14443-4

0

0

0

0

PICC not compliant with ISO/IEC 14443-4
RFU

Other values

Meaning(d) Frame Waiting Time Integer (FWI) (4 bits)
FWI codes an integer value used to define the frame waiting time (FWT).
The FWT defines the maximum time for a PICC to start its response after the end of a PCD frame.
FWT is calculated by the formula:
FWT = (256 × 16/fc) × 2FWI
where the value of FWI has the range from 0 to 14 and the value of 15 is RFU.
For FWI = 0, FWI is mininal (~ 302 µs)
For FWI = 14, FWI is maximal (~ 4949 ms)

138

Version 1.1(e) Application Data Coding (2 bits)
The details of application data coding (ADC) are shown in "Table 12-2-7 Application Data Coding
Supported by PICC".

Table 12-2-7

Application Data Coding Supported by PICC

b4

b3

Meaning

00

Arbitrary application

0

1

Coding shown in "12.2.9.3 Application Data"

Other values

RFU(f) Frame Option (2 bits)
Details of the frame options supported by the PICC are shown in "Table 12-2-8 Frame Options
Supported by PICC".

Table 12-2-8

Frame Options Supported by PICC

b2

b1

Meaning

1

x

PICC supports NAD.

x

1

PICC supports CID.

(2) Extended Specifications
None(3) References
The value of application data coding (ADC) shall be (00)b.
Frame option (FO) shall support CID.

139

Version 1.1

12.2.10 ATTRIB Command(1) Basic Specifications
The ATTRIB Command sent by the PCD shall include information required to select a single
PICC.
A PICC receiving an ATTRIB Command with its identifier becomes selected and assigned to a
dedicated channel. After being selected, this PICC only response to commands in ISO/IEC
14443-4 which include its unique CID.
(2) Extended Specifications
None(3) References
None

140

Version 1.1

12.2.10.1 ATTRIB Command Format(1) Basic Specifications
ATTRIB Command has the following format: "Fig. 12-2-15 ATTRIB Command format"'1D'

Identifier

Param1

Param2

Param3

Param4(1 byte)(4 byte)(1 byte)(1 byte)(1 byte)(1 byte)Fig. 12-2-15 ATTRIB Command Format
A CID value of '00' is returned if the PICC does not support CID.
(2) Extended Specifications
None(3) References
None

141

Higher layer INF(Option: 0
byte or more)

CRC_B(2 byte)Version 1.1

12.2.10.2 Identifier(1) Basic Specifications
This identifier is the value of the PUPI sent by PICC in the ATQB.
(2) Extended Specifications
None(3) References
None

142

Version 1.1

12.2.10.3 Coding of Param 1(1) Basic Specifications
Encoding of PARAM1 within an ATTRIB sent by the PCD is shown in "Fig. 12-2-16 Coding of
Param1". All RFU bits shall be set to 0 if not otherwise specified.

Minimum TR0

Minimum TR1

EOF

SOF

b8

b6

b4

b3

b7

b5

Fig. 12-2-16

RFU
b2

b1

Coding of Param 1(a) EOF/SOF
b3 and b4 indicate the PCD capability to support suppression of the EOF and/or SOF from PICC to
PCD, which may reduce communication overhead. The suppression of EOF and/or SOF is
optional for the PICC. The coding of b3 and b4 is shown in "Table 12-2-9 Handling of
SOF/EOF":
Table 12-2-9b301

Handling of SOF/EOF

Request to send SOF
Request
Not requested(may be omitted)

b4
0
1

143

Request to send EOF
Request
Not requested(may be omitted)

Version 1.1(b) Minimum TRO
Minimum TRO indicates to the PICC the minimum delay before responding after the end of acommand sent by a PCD. The default value has been defined in ISO/IEC 14443-2, 9.2.5..
Encoding of T0 is shown in "Table 12-2-10 Minimum TRO coding".

Table 12-2-10

Minimum TRO coding

b8-b7
00
01
10
11

Minimum TRO
default value
48/fs
16/fs
RFU

NOTE: Minimum TRO is required by the PCD when switching from transmit to receive and its
value depends on the PCD performance.
(c) Minimum TR1
Minimum TR1 indicates to the PICC the minimum delay between subcarrier modulation start andbeginning of data transmission. The default value has been defined in ISO/IEC 14443-2, 9.2.5.
Encoding of T1 is shown in "Table 12-2-11Minimum TR1".

Table 12-2-11
b6-b5
00
01
10
11

Minimum TR1
Minimum TR1
default value
64/fs
16/fs
RFU

NOTE: Minimum TR1 is required by the PCD for synchronization with the PICC and its value
depends on the PCD performance.
(2) Extended Specifications
None(3) References
None

144

Version 1.1

12.2.10.4 Coding of Param2(1) Basic Specifications
The least significant half byte (b4 to b1) is used to code the maximum frame size that can bereceived by the PCD as specified in "Table 12-2-12 Coding of b4 to b1 of Param2".

Table 12-2-12

Coding of b4 to b1 of Param2

Maximum Frame Size
0
1
2
3
4
5
6
7
Code in ATTRIB
Maximum Frame
16
24
32
40
48
64
96
128
Size(byte)
NOTE: RFU is retained for the case in which the value is larger than 256.

8

9-F

256

RFU

The most significant half byte (b8 to b5) is used for bit rate selection, as specified in "Table
12-2-13 Coding of b5 to b8 of Param2".

Table 12-2-13

Coding of b5 to b8 of Param2

b6 b5
00
01
10
11

Meaning
PCD to PICC, 1etu = 128 / fc, bit rate is 106 kbit/s
PCD to PICC, 1etu = 64 / fc, bit rate is 212 kbit/s
PCD to PICC, 1etu = 32 / fc, bit rate is 424 kbit/s
PCD to PICC, 1etu = 16 / fc, bit rate is 847 kbit/s

b8 b7
00
01
10
11

Meaning
PICC to PCD, 1etu = 128 / fc, bit rate is 106 kbit/s
PICC to PCD, 1etu = 64 / fc, bit rate is 212 kbit/s
PICC to PCD, 1etu = 32 / fc, bit rate is 424 kbit/s
PICC to PCD, 1etu = 16 / fc, bit rate is 847 kbit/s(2) Extended Specifications
None(3) References
None

145

Version 1.1

12.2.10.5 Coding of Param3(1) Basic Specifications
The least significant half byte (b4 to b1) is used for confirmation of the protocol type as specified
in "Table 12.2-6 Protocol Types Supported by PICC". The most significant half byte (b8 to b5) is
set to (0000)b, all other value are RFU.
Coding of Param3 is shown in "Table 12-2-17 Coding of Param3 ".
RFU
b8 = 0b7 = 0b6 = 0b5 = 0

Table 12-2-17

b4

Protocol typeb3
b2

Coding of Param3(2) Extended Specifications
None(3) References
None

146

b1

Version 1.1

12.2.10.6 Coding of Param4(1) Basic Specifications
The Param 4 byte consists of two parts:- the least significant half byte (b4 to b1) is named Card Identifier (CID) and defines the logicalnumber 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 each active PICC. If the PICC dose not support
CID, code value (0000)b shall be used;- the most significant half byte (b8 to b5) is set to (0000)b, all other value are RFU.
(2) Extended Specifications
None(3) References
None

147

Version 1.1

12.2.10.7 Higher layer INF(1) Basic Specifications
Any higher layer command transferable as the INF field of ISO/IEC 14443-4 may be included.
It is not mandatory for the PICC to process successfully ant command in this context.
The PICC shall however process successfully such message if no application command isincluded.
(2) Extended Specifications
None(3) References
The following specifications are added to the basic specifications.
Upper layer information: 'F4 XX XX XX XX'- 1st byte:
Indicates that a matching check is performed on 4 application data bytes (and other values aredesignated as RFU).
- 2nd to 5th bytes:
Data is the same as application data in ATQB.
If the upper layer information is as described above, when application data in ATQB is identical to
the 4 bytes following 'F4' of the upper layer information, a response to ATTRIB is returned and the
PICC changes to the ACTIVE state. If they do not match, a response is not returned and the
PICC remains in the READY-DECLARED state.
An upper layer response does not exist for the 'F4' command.
Accordingly, a summary of card operation when an ATTRIB command is received for which the
PUPI matchs is as shown below.
- If upper layer information does not exist, a response is returned and the PICC changes to the
ACTIVE state.
- If upper layer information is 'F4 XX XX XX XX' and 'XX XX XX XX' matches with theapplication data of ATQB, a response is returned and the PICC changes to the ACTIVE state.
- If upper layer information is 'F4 XX XX XX XX' and 'XX XX XX XX' does not match with theapplication data of ATQB, a response is not returned and the PICC remains in the
READY-DECLARED state.
If upper layer information is not 'F4 XX XX XX XX', a response is not returned and the PICC
remains in the READY-DECLARED state.

148

Version 1.1

12.2.11 Answer to ATTRIB Command(1) Basic Specifications
The PICC shall answer to any valid ATTRIB Command (correct PUPI and valid CRC_B) with theformat described in "Fig. 12-2-18 Format of the Answer to an ATTRIB Command".
MBLI(1 byte)CID

Fig. 12-2-18

Higher layer Response(Optional 0 or more bytes)

CRC_B(2 bytes)

Format of the Answer to an ATTRIB Command

The first byte consists of two parts:
1) The most significant half byte (b8 to b5) is called the Maximum Buffer Length Index(MBLI). It is used by the PICC to let the PCD know the limit of its internal buffer toreceived chained frames. The coding of MBLI is as follows:- MBLI = 0:means that the PICC provides no information on its internal input buffer size;- MBLI > 0:is used to calculate the actual internal maximum buffer length (MBL) according to thefollowing formula:
MBL = (PICC Maximum Frame Size)*2(MBLI-1)
where the PICC maximum frame size is returned accumulated length is never grater
than MBL.
2) The least significant half byte (b4 to b1) contains the returned CID.
support CID, code value (0000)b is returned.

149

If the PICC dose notVersion 1.1

As indicated in "Fig. 12-2-19 PICC Answer to ATTRIB Format without Higher Layer Response", a
PICC shall the answer the empty (no higher layer INF filed) ATTRIB Command with an empty
higher layer response:
MBLI
CID(1 byte)Fig. 12-2-19

CRC_B(2 bytes)

PICC Answer to ATTRIB Format without Higher Layer Response

NOTE: A suitably formatted ATTRIB response command (for which CID and CRD_B are set)
indicates that the PICC has been selected by the PCD.
(2) Extended Specifications
None(3) References
If the upper layer information satisfies the conditions specified in "12.2.10.7 (3) References", a
response is returned in the format specified in "Fig. 12.2-19 PICC Answer to ATTRIB Format
without Higher Layer Response".

150

Version 1.1

12.2.12 HLTB Command and Answer(1) Basic Specifications
The HLTB Command is used to set a PICC in HALT State and stop responding to a REQB. Afteranswering to this command the PICC shall ignore any commands except the WUPB Command(see "12.2.7 REQB/WUPB Command").
The format of a halt command sent out by the PCD is shown in "Fig. 12-2-20 Format of the
HLTB Command".
'50'(1 byte)Identifier(4 bytes)Fig. 12-2-20

CRC_B(2 bytes)

Format of the HLTB Command

The 4 byte identifier is the value of the PUPI sent by the PICC in the ATQB.
The format of Answer to a HLTB Command from the PICC is shown in "Fig. 12-2-21 Format of
PICC Answer to HLTB Command".
'00'(1 byte)

CRC_B(2 bytes)Fig. 12-2-21 Format of PICC Answer to HLTB Command(2) Extended Specifications
None(3) References
None

151

Version 1.1

12.3Communication Example Type A
12.3.1 Overview of Communication Example of Bit Frame Anticollision Processing(1) Basic Specifications
This example illustrated in "Fig. 12.3-1 Select sequence with bit frame anticollision" shows theselect sequence with 2 PICCs in the field on the assumption of:- PICC #1 with UID size : single, Value of uid0 '10';- PICC #2 with UID size : double.

152

Version 1.1

Request
REQA
ATQA

'26'

PICC#1(10000000 00000000)b

ATQA

PICC#2(10000010 00000000)b

Anticollision loop, cascade level 1
SEL

NVB

'93'

'20'

UID0

UID1

UID2

UID3

BCC

PICC#1

UID1

UID2

BCC

PICC#2(00001000)b

CT

UID0

(00010001)b

The first collision occurs at the 4th bit.
SEL

NVB

'93'

'24'

(0001)b

UID0

UID1

UID2

BCC

PICC#2(0001)b

SEL

NVB

CT

UID0

'93'

'70'

(00010001)b

UID1

UID2

BCC

CRC_A
SAK CRC_A(xx1xxxxx)b

Anticollision loop, cascade level 2
SEL

NVB

'95'

'20'

SEL

NVB

'93'

'70'

UID3

UID3

UID4

UID5

UID6

BCC

UID4

UID5

UID6

BCC

CRC_A
SAK CRC_A(xx0xxxxx)b

Note: start of communication, end of communication and parity bits are not shown for the sake ofsimplicity.
Representation:

PCD to PICC

PCD to PICC
(xxx....x)bFirst bit transmitted (LSB)
Fig. 12.3-1

Select Sequence with Bit Frame Anticollision

153

Version 1.1(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

154

Version 1.1

12.3.2 Explanation of Selection Processing of Bit Frame Anticollision
12.3.2.1 Request Processing(1) Basic Specifications
The contents of the request portion of "Fig. 12.3-1 Select Sequence with Bit Frame Anticollision"
are as shown below.
- PCD transmits the REQA Command.
- All PICCs respond with their ATQA.
PICC #1 indicates bit frame anticollision and UID size : single.
PICC #2 indicates bit frame anticollision and UID size : double.
(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

155

Version 1.1

12.3.2.2 Anticollision Loop, Cascade Level 1(1) Basic Specifications
The contents of the anticollision loop portion of cascade level 1 of "Fig. 12.3-1 Select Sequencewith Bit Frame Anticollision" are as shown below.
- PCD transmits an ANTICOLLISION Command:- SEL specifies bit frame anticollision and cascade level 1;- the value '20' of NVB specifies that the PCD will transmit no part of UID CL1;- consequently all PICCs in the field respond with their complete UID CL1;- due to the value '88' of the cascade tag, the first collection occurs at bit position #4;- PCD transmits another ANTICOLLISION Command that includes the first 3 bits of UID CL1
that were received before the collision occurs, follow by a (1)b. Consequently the PCD assigns
NVB with the value '24';- these 4bits correspond to the first bits of UID CL1 of PICC #2;- PICC #2 responds with its 36 remaining bits of UID CL1. Since PICC #1 dose not respond, no
collision occurs;- since the PCD "knows" all bits of UID CL1 of PICC #2, it transmits a SELECT Command for
PICC #2;- PICC #2 responds with SAK, indicating that UID is not complete;- consequently, the PCD increases the cascade level.
(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

156

Version 1.1

12.3.2.3 Anticollision Loop, Cascade Level 2(1) Basic Specifications
The contents of the anticollision loop portion of cascade level 2 of "Fig. 12.3-1 Select Sequencewith Bit Frame Anticollision" are as shown below.
- PCD transmits another ANTICOLLISION Command:
SEL specifies bit frame anticollision and cascade level 2;
NVB is reset to '20' to force PICC #2 to respond with its complete UID CL2;
- PICC #2 responds with all 40 bits of its UID CL2;
- PCD transmits the SELECT Command for PICC #2, cascade level 2;- PICC #2 responds with SAK indicating that the UID is complete, and switches from the
READY state to the ACTIVE state.
(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

157

Version 1.1

12.4CRC_A and CRC_B Encoding
12.4.1 CRC_A Encoding(1) Basic Specifications
This section is provided for explanatory purposes and indicates the bit patterns that will exist in thephysical layer. It is included for the purpose of checking an ISO/IEC 14443-3 Type A
implementation of CRC_A encoding.
The process of encoding and decoding may be conveniently carried out by a 16-stage cyclic shift
register with appropriate feedback gates. According to ITU-T Recommendation V.41, ANNEX I,
figures I-1/V.41, and 1-2/V.41 the flip-flops of the register shall be numbered from FFO to FF15.
FFO shall be the leftmost flip-flop where data is shifted in. FF15 shall be the rightmost flip-flopwhere data is shifted out..
The initial value of the register is shown in "Table 12.4-1 Initial Content of 16-Stage Shift Register
According to Value '6363'".

Table 12.4-1

Initial Content of 16-Stage Shift Register According to Value '6363'

FF0

FF1

FF2

FF3

FF4

FF5

FF6

FF7

FF8

FF9 FF10 FF11 FF12 FF13 FF14 FF15

0

1

1

0

0

0

1

1

0

1

The initial value is set to '6363' in hexadecimal.
FF15 to the LSB.

1

0

0

1

1

Consequently, FFO corresponds to the MSB and(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

1580Version 1.1

12.4.1.1 CRC_A Example 1(1) Basic Specifications
The following conditions are used for CRC_A example 1.
- Transmission of data, first byte = '00', second byte = '00', CRC_A appended.
According to the calculation result of this example, CRC_A = '1EA0'. The frame organization inthis case is shown in "Fig. 12.4-1 Example 1 for CRC_A Encoding". In addition, the finalcontents of the shift register during encoding are shown in "Table 12.4-2 Content of 16-stage Shift
Register According to Value '1EA0'".
First bit transmitted↓

S

0000 0000

10000 0000

10000 0101

1

0111 1000

1

'00'

P

'00'

P

'A0'

P

'1E'

P

E

Fig. 12.4-1 Example 1 for CRC_A Encoding
Table 12.4-2

Content of 16-stage Shift Register According to Value '1EA0'

FF0

FF1

FF2

FF3

FF4

FF5

FF6

FF7

FF8

FF9 FF10 FF11 FF12 FF13 FF14 FF15

0

0

0

1

1

1

1

0

1

0

1

0

(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

159

0

0

0

0

Version 1.1

12.4.1.2 CRC_A Example 2(1) Basic Specifications
The following conditions are used for CRC_A example 2.
- Transmission of data block, first byte = '12', second byte = '34', CRC_A appended.
According to the calculation result of this example, CRC_A = 'CF26'. The frame organization inthis case is shown in "Fig. 12.4-2 Example 2 for CRC_A encoding". In addition, the finalcontents of the shift register during encoding are shown in "Table 12.4-3 Content of 16-stage shift
register according to value 'CF26'".
First bit transmitted↓

S

0100 1000

10010 1100

00110 0100

01111 0011

1

'12'

P

'34'

P

'26'

P

'CF'

P

Fig. 12.4-2
Table 12.4-3

E

Example 2 for CRC_A Encoding

Content of 16-stage Shift Register According to Value 'CF26'

FF0

FF1

FF2

FF3

FF4

FF5

FF6

FF7

FF8

FF9 FF10 FF11 FF12 FF13 FF14 FF15

1

1

0

0

1

1

1

1

0

0

1

0

(2) Extended Specifications
None(3) References"12.5 Type A Timeslot - Initialization and Anticollision" is employed.

160

0

1

1

0

Version 1.1

12.4.2 CRC_B Encoding(1) Basic Specifications
This section is provided for explanatory purpose and indicates the bit patterns that will exist in thephysical layer. It is included for the purpose of checking an ISO/IEC 14443-3 Type B
implementation of CRC_B encoding.
Refer to ISO/IEC 13239 and CCITT X.25 #2.2.7 and V.42 #8.1.1.6.1 for further details.
Initial Value = 'FFFF'(2) Extended Specifications
None(3) References
None

161

Version 1.1

12.4.2.1 CRC_B Example 1(1) Basic Specifications
The following conditions are used for CRC_B example 1.
- Transmission of first byte = '00', second byte = '00', third byte = '00', CRC_B appended.
According to the calculation result of this example, CRC_B = 'C6CC'.
this case is shown in "Fig. 12.4-3 Example 1 for CRC_B encoding".

SOF

1st byte

2nd byte

3rd byte

'00'

'00'

'00'

Fig. 12.4-3

CRC_B
'CC'

Example 1 for CRC_B encoding(2) Extended Specifications
None(3) References
None

162

The frame organization in

'C6'

EOF

Version 1.1

12.4.2.2 CRC_B Example 1(1) Basic Specifications
The following conditions are used for CRC_B example 2.
- Transmission of first byte = '0F', second byte = 'AA', third byte = 'FF', CRC_B appended.
According to the calculation result of this example, CRC_B = 'D1FC'.
this case is shown in "Fig. 12.4-4 Example 2 for CRC_B Encoding".

SOF

1st byte

2nd byte

3rd byte

'0F'

'AA'

'FF'

Fig. 12.4-4

CRC_B
'FC'

Example 2 for CRC_B Encoding(2) Extended Specifications
None(3) References
None

163

The frame organization in

'D1'

EOF

Version 1.1

12.4.2.3 CRC_B Example 3(1) Basic Specifications
The following conditions are used for CRC_B example 3.
- Transmission of first byte = '0A', second byte = '12', third byte = '34', fourth byte = '56', CRC_B
appended.
According to the calculation result of this example, CRC_B = 'F62C'.
this case is shown in "Fig. 12.4-5 Example 3 for CRC_B Encoding".

1st byte

2nd byte

3rd byte

4th byte

'0A'

'12'

'34'

'56'

SOF

Fig. 12.4-5

Example 3 for CRC_B Encoding(2) Extended Specifications
None(3) References
None

164

The frame organization in

2nd byte
'2C'

'F6'

3rd byte
EOF

Version 1.1

12.4.3 Code Sample Written in C Language for CRC Calculation(1) Basic Specifications#include <stdio.h>#include <stdlib.h>#include <string.h>#include <ctype.h>#define CRC_A 1#define CRC_B 2#define BYTE unsigned char
unsigned short UpdateCrc(unsigned char ch, unsigned short *lpwCrc){
ch = (ch^(unsigned char)((*lpwCrc) & 0x00FF));ch = (ch^(ch<<4));*lpwCrc = (*lpwCrc >> 8)^((unsigned short)ch << 8)^((unsigned short)ch<<3)^((unsigned
short)ch>>4);
return(*lpwCrc);}
void ComputeCrc(int CRCType, char *Data, int Length,
BYTE *TransmitFirst, BYTE *TransmitSecond){
unsigned char chBlock;unsigned short wCrc;
switch(CRCType) {case CRC_A:
wCrc = 0x6363;// ITU-V.41

break;
case CRC_B:
wCrc = 0xFFFF;// ISO 13239

break;
default:

165

Version 1.1

return;}do {chBlock = *Data++;UpdateCrc(chBlock, &wCrc);} while (--Length);
if (CRCType == CRC_B)
wCrc = ~wCrc;// ISO 13239*TransmitFirst = (BYTE) (wCrc & 0xFF);*TransmitSecond = (BYTE) ((wCrc >> 8) & 0xFF);
return;}BYTE BuffCRC_A[10] = {0x12, 0x34};
BYTE BuffCRC_B[10] = {0x0A, 0x12, 0x34, 0x56};
unsigned short Crc;
BYTE First, Second;
FILE *OutFd;
int i;
int main(void){
printf("CRC-16 reference results 3-Jun-1999¥n");printf("by Mickey Cohen - mickey@softchip.com¥n¥n");printf("Crc-16 G(x) = x^16 + x^12 + x^5 + 1¥n¥n");printf("CRC_A of [ ");for(i=0; i<2; i++) printf("%02X ",BuffCRC_A[i]);ComputeCrc(CRC_A, BuffCRC_A, 2, &First, &Second);
printf("] Transmitted: %02X then %02X.¥n", First, Second);
printf("CRC_B of [ ");for(i=0; i<4; i++) printf("%02X ",BuffCRC_B[i]);ComputeCrc(CRC_B, BuffCRC_B, 4, &First, &Second);
printf("] Transmitted: %02X then %02X.¥n", First, Second);
166

Version 1.1

return(0);}(2) Extended Specifications
None(3) References
None

167

Version 1.1

12.5Type A Timeslot - Initialization and AnticollisionThis section specifies initialization and anticollision processing for the type A timeslot type PICCs.
The symbols used in this section are indicated below.
- ATH_t
Answer To Halt of type A_timeslot- ATQA_t Answer To reQuest of Type A_timeslot- ATQ-ID
Answer To REQ-ID- CID_t
Card Identifier of Type A_timeslot- HLTA_t
HALT Command of Type A_timeslot- REQA_t REQuest Command of Type A_timeslot- REQ-ID
REQuest-ID Command- SAK_t
Select AKnowledge of Type A_timeslot- SEL_t
SELect Command of Type A_timeslot

168

Version 1.1

12.5.1 Bit, Byte and Frame Format
12.5.1.1 Timing Definitions(1) Basic Specifications(a) Polling reset time
Polling reset times of Type A_timeslot are equal to those of Type A in "11. Polling".
(b) Time interval from REQA_t to ATQA_t
PICC returns ATQA_t after waiting for 32+/-2 etu upon receiving REQA_t.
recognize the coding of the ATQA_t.

The PCD may not(c) Request Guard TimeThe Request Guard Time is defined as the minimum time between the start of bits of twoconsecutive Request commands. Its values shall be 0.5 ms.
(d) Frame Guard TimeThe Fame Guard Time is defined as the minimum time between the rising edge of the last bit andthe falling edge of the start bit of two consecutive frames in opposite direction. Its value shall be
10 etu.
(e) Timeslot length
The first timeslot starts in 32 etu after REQ-ID. Each timeslot length is 104 etu consisting of 94
etu for ATQ-ID reception and 10 etu frame guard time succeeding.
(2) Extended Specifications
None(3) References
None

169

Version 1.1

12.5.1.2 Frame Format(1) Basic Specifications(a) REQA_t Frames
Refer to "12.1.1.5(1)(a) Short Frame" and "Table 12.1-2 Short Frame" for information on the frame
format of REQA_t. The data content is '35' for a REQA_t.
(b) Standard Frames
The LSB of each byte is transmitted first. Each byte has no parity. CRC_B defined in "12.2.2
Cyclic Redundancy Check Code (CRC_B)" is added to the end of the frame data. The format ofstandard frames is shown in "Fig. 12.5-1 Standard Frames of Type A Timeslot Type".

S

1 byteCommand/response

Data: n × (8 data bits + no parity)(0 or 1 byte)(0 or1 byte)(Parameter 1)(Parameter 2)

Fig. 12.5-1(0 or 8 bytes)(UID)

Standard Frames of Type A Timeslot Type(2) Extended Specifications
None(3) References
None

170

CRC_B
2 bytes

EVersion 1.1

12.5.2 PICC States
The following sections provide the states for PICC, Type A_timeslot.
12.5.2.1 Power Off State(1) Basic Specifications
In the POWER-OFF State, the PICC is not energized due to lack of carrier and shall not emit
subcarrier.
(2) Extended Specifications
None(3) References
None

171

Version 1.1

12.5.2.2 IDLE State(1) Basic Specifications
This state is entered after the field has been active within a 5 ms delay. The PICC recognize
REQA_t .
(2) Extended Specifications
None(3) References
None

172

Version 1.1

12.5.2.3 READY State(1) Basic Specifications
This state is entered by REQA_t.

The PICC recognizes REQA_t, REQ-ID and SEL_t.

(2) Extended Specifications
None(3) References
None

173

Version 1.1

12.5.2.4 ACTIVE State(1) Basic Specifications
This state has two substates.
The first sub-state is entered by SEL_t with its complete UID and CID_t.
PICC recognizes HLTA_t and proprietary higher layer commands.

In this sub-state, theThe second sub-state is a state where commands defined in "13.3 Half-duplex Block Transmission
Protocol" can be executed, and is entered from the first sub-state by a command defined in "13.1
Protocol Activation of PICC Type A".
(2) Extended Specifications
None(3) References
None

174

Version 1.1

12.5.2.5 HALT State(1) Basic Specifications
This state is entered by HLTA_t from ACTIVE State.
(2) Extended Specifications
None(3) Refrences
None

175

In this state, the PICC is mute.

Version 1.1

12.5.3 Command/Response Sets
(1) Basic Specifications
Four commands and their response are used.
Commands/Responses of Type A Timeslot Type".

176

Details are shown in "Table 12.5-1

Version 1.1

Table 12.5-1

Commands/Responses of Type A Timeslot Type

Type
Name
Encoding (b8-b1)
Command REQA_t (b7-b1)(0110101)b(='35')
Response ATQA_t Any value from '00' to 'FF'

Command REQ-ID

Response ATQ-ID

Command SEL_t

Response SAK_t

Command HLTA_t

Response ATH_t(00001000)b(='08')
Refer to "Table 12.5-2 Parameters of
REQ-ID Command" for informationon the parameters.
(00000110)b(='06')(01000NNN)b: NNN is CID_t from 0
to 7(01100NNN)b: NNN+8 is CID_t from
8 to 15b8-b5(1000)b: Able to acquire
additional information with upper
layer protocol
b8-b5(1100)b: Initial value of protocol
b4-b1(0000)b:
Other than ISO/IEC 14443-4
b4-b1(0001)b:
ISO/IEC14443-4(00011NNN)b: NNN is CID_t from 0
to 7(00111NNN)b: NNN+8 is CID_t from
8 to 15(00000110)b(='06')

177

Meaning
Request PICC Type A timeslot toanswer ATQA_t.
Answer to REQA_t. PCD canrecognize the existence of Type A
timeslot PICC. However, the PCD is
not required to recognize the coding of
the ATQA_t.
Request the PICC to answer its UID to
one to timeslots. REQ-ID is followedby two parameters.
Answer 8-byte UID to one of 4
timeslots. ATQ-ID is followed by its
8-byte UID.
Select the PICC with its UID and set
the CID_t. SEL_t is followed by 8
byte UID.
Acknowledgment of SEL_t

Halt command for PICC of CID_t

Acknowledgment of HLTA_t

Version 1.1

Coding of parameters in the REQ-ID command is shown in "Table 12.5-2 Parameters of REQ-ID
Command".

Table 12.5-2

P1

Parameter
b8 -b7b6 - b1

P2

Parameters of REQ-ID Command

Meaning
Timeslot length, b7=1: for 8-byte UID, b8=0
Number of timeslots, b3=1: for 4 timeslots, Others=0'00'(2) Extended Specifications
None(3) References
None

178

Version 1.1

12.5.4 Time Slot Type Anticollision Processing(1) Basic Specifications
The flow chart of PICC anticollision sequence is shown as below in "Fig. 12.5-2 Flowchart of
PICC Anticollision Sequence".

179

Version 1.1

Power
OFF

Power OFF

Wait for REQA_t
IDLE

REQA_tSend ATQA_t

Wait for REQ-ID
REQ-IDREADY

Wait for Slot R

Send ATQ-ID
REQA_tWait for Matched
SEL_t agree

REQ-ID

Matched EL_t
Send SAK_t
Matched HLTA_t

Enter ISO/IEC 14443-4
Else

ACTIVE
ISO/IEC 14443-4

Send Answer to
HLTA_tHALT

DESELECT
HALT
Fig. 12.5-2

ACTIVE

ACTIVE
1st substate

Else

FlowChart of PICC Anticollision Sequence

180

ANTI-COLLISION

Select R

Version 1.1(2) Extended Specifications
None(3) References
None

181

Version 1.1

12.6Example of Anticollision Sequence for Type B(1) Basic Specifications
An example of an anticollision sequence for Type B is shown in "Fig. 12.6-1 Type B Anticollision
Sequence Example".
PCD

PICCs

PCD
Start of anticollision Sequence
Transport Application, AFI = '10'
Number of slot, N = 1
Transmit 'REQB'
ApF

AFI

Param

CRC

CRC

PICC1

05

10

00

xx

xx

Transport PICC
Matched AFI
N=1
Transmit 'ATQB'

PICC2Medical PICC
Not Matched AFI
Wait for next REQB/WUPB

PICC3
Multi application PICC
Matched AFI
N=1
Transmit 'ATQB'

PCD
Collision detected
Change Number of slots, N = 4
Fig. 12.6-1

Type B Anticollision Sequence Example

182

Version 1.1

PCD

PICCs

Transmit 'REQB'
ApF

AFI

Param

CRC

CRC

PICC1

05

10

02

xx

xx

Transport PICC
Matched AFI
Randomly selects R between 1 to N
R = 2, so waits for slot marker for slot 2

PICC2
Medical PICC
Not Matched AFI
Wait for next REQB/WUPB

PICC3
Multi application PICC
Matched AFI
Randomly selects R between 1 to N
R = 1, so transmit in slot 1

PCD

Transmit 'ATQB'PCD has now a choice depending on its
application…select the PICC3 and send no
more slot marker, continue sending slot
markers, or other possibilities.
For this example the PCD will continue tosend slot markers.
Fig. 12.6-1

Type B Anticollision Sequence Example (continued)

183

Version 1.1

PCD

PICCs

Transmit slot marker for slot 2
APn

CRC

CRC

PICC1

15

xx

xx

Transport PICC
Matched AFI
R = 2, so transmit in slot 2
Transmit 'ATQB'

PICC2Medical PICC
Waiting for next REQB/WUPB

PICC3
Multi application PICC

PCD

Waiting for HLTB or ATTRIB

The PCD has two PICC responses
For this example the PCD will continue tosend slot markers.
Transmit slot marker for slot 3, No response.
Transmit slot marker for slot 4, No response.

PCD
PCD application decides to select thetransport PICC1 with the ATTRIB
Command and may stop PICC3 with a
HLTB Command.
Fig. 12.6-1

Type B Anticollision Sequence Example (continued)

184

Version 1.1(2) Extended Specifications
None(3) References
An example of the procedure in the case b5 of the PARAM portion of REQB/WUPB is 1 is shownin "Fig. 12.6-2 Type B Anticollision Sequence Example".
PCD

PICCs

PCD
Start of anticollision sequence
Transport Application, AFI = '10'
Number of slots, N = 1
Transmit 'REQB/WUPB'
ApF

AFI

Param

CRC

CRC

PICC1

05

10

10

xx

xx

Transport PICC
Matched AFI
N=1
Transmit 'ATQB'

PICC2Medical PICC
Matched AFI
Wait for next REQB/WUPB

PICC3
Multi application PICC
Matched AFI
N=1'ATQB' sent

PCD
Collision detected
Change in number of slots, N=4
Fig. 12.6-2Type B Anticollision Sequence Example
185

Version 1.1

PCD

PICCs

Transmit 'REQB/WUPB'
ApF

AFI

Param

CRC

CRC

PICC1

05

10

12

xx

xx

Transport PICC
Matched AFI
Randomly selects R between 1 to N
R = 2, so waits for slot marker for slot 2'ATQB' sent

PICC2
Medical PICC
Not Matched AFI
Wait for next REQB/WUPB

PICC3
Multi application PICC
Matched AFI
Randomly selects R between 1 to N
R = 1, so transmit in slot 1

PCD'ATQB' sent

PCD has now a choice depending on its
application…select the PICC3 and send no
more slot marker, continue sending slot
markers, or other possibilities.
For this example the PCD will continue tosend slot markers
Fig. 12.6-2Type B Anticollision Sequence Example (continued)

186

Version 1.1

13. Transmission Protocol
Communication frames and the basic communication sequence are specified with the transmission
protocol of the PICC and PCD on the basis of ISO/IEC 14443-4. Type A and Type B communication
formats are specified.
(1) Terms Used in this Chapter- Bit duration
one elementary time unit (etu), calculated by the following formula.
- 1 etu = 128 / (D x fc)
Since the initial value of divisor D is 1, the initial value of etu is as shown below.
- 1etu = 128 f/c
fc is specified in "8. Power Transfer".
- Block
special type of frame, which contains a valid protocol data format. A valid protocol data
format includes I-Blocks, R-Blocks or S-Blocks.
- Invalid block
A type of frame with an invalid protocol format. A time-out, when no frame has been received,
is not interpreted as an invalid block.
- Framesequence of bits as defined in "12. Anticollision". The PICC Type A uses the standard frame
defined for Type A and the PICC Type B uses the frame defined for Type B.

187

Version 1.1(2) Symbols and Abbreviations Used in this Chapter-

ACK positive ACKnowledgement
ATS Answer To Select
ATQB Answer To reQuest, Type B
CID Card IDentifier
CRC Cyclic Redundancy Check, as defined for each PICC Type in ISO/IEC 14443-3
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 Codeetu 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
FSDI Frame Size for proximity coupling Device Integer
FWI Frame Waiting time Integer
FWT Frame Waiting Time
FWTTEMP temporary Frame Waiting Time
HLTA HALT Command, Type A
I-Block Information block
INF INformation Field
NAD Node ADdress
OSI Open Systems Interconnection
PCB Protocol Control Byte
PCD Proximity Coupling Device
PICC Proximity Card
PPS Protocol and Parameter Selection

188

Version 1.1-

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 SelectRFU Reserved for Future Use
S-Block Supervisory block
SAK Select AcKnowledge
SFGI Start-up Frame Guard time Integer
SFGT Start-up Frame Guard TimeWUPA Wake-Up Command, Type A
WTX Waiting Time eXtension
WTXM Waiting Time eXtension Multiplier(3) Methods Used to Represent Data Values Used in this Chapter- (xx)b: Binary xx- 'xx': Hexadecimal xx

189Version 1.1

13.1Protocol Activation of PICC Type A(1) Basic Specifications
The following activation sequence shall be applied:- PICC activation sequence as defined in "12. Anticollision" (request, anticollision loop andselect).
- At the beginning the SAK byte shall be checked for availability of an ATS. The SAK is
defined in "12. Anticollision".
- The PICC may be set to HALT state, using the HLTA Command as defined in "12.
Anticollision", if no ATS is available.
- The RATS may be sent by the PCD as next command after receiving the SAK if an ATS isavailable.
- 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 parametersin the ATS.
The PCD activation sequence for a PICC Type A is shown in "Fig. 13.1-1 Activation of a PICC
Type A by a PCD".

190

Version 1.1

ISO/IEC 14443-3

Field ON

Send REQ
Receive ATQA

Send WUPA

Anticollision
loop

HALT
state

Send HLTA

no

ATSavailable?

Non ISO/IEC

Activation

Send RATSDESELECT response
Receive ATS
DESELECT request
PPS
supported?

yesnoParameterchange?
noyes

Send PPS request

Receive PPS response

Exchange
Transparent
Data

Fig. 13.1-1

Activation of a PICC Type A by a PCD

191

ISO/IEC 14443-4

yesDeactivation processing

14443-4 protocol

Version 1.1(2) Extended Specifications
None(3) References
None

192

Version 1.1

13.1.1 Request for Answer to Select(1) Basic Specifications
The specifications of request for ATS (RATS) and its contents are as follows.
RATS is shown in "Fig. 13.1-2 Request for answer to select".

'E0'

ParameterCRC

1 byte1 byte2 bytesFig. 13.1-2

The structure ofRequest for answer to selectThe parameter byte consists of two parts as shown in "Fig. 13.1-3 Coding of RATS parameterbyte".
- 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
13.1-1 FSDI to FSD conversion".
The least significant half byte b4 to b1 is named CID and it defines the logical number of theaddressed 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 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.
b8

b7

b6

b5

b4

b3

b2

b1

CID
FSDI
Fig. 13.1-3 Coding of RATS Parameter Byte
Table 13.1-1 FSDI to FSD Conversion
FSDI
FSD

'0'
16

'1'
24

'2'
32

'3'
40

'4'
48

193

'5'
64

'6'
96

'7'
128

'8'
256

'9' to 'F'
RFU

Version 1.1(2) Extended Specifications
None(3) References
None

194

Version 1.1

13.1.2 Answer to Select (ATS)(1) Basic Specifications
This clause defines the ATS with all its available fields "Fig. 13.1-4 Structure of the ATS".
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.

TL

Length byte

T0

Format byte….. codes Y(1) and FSCITAInterface bytes…..codes DS and DR

TB…..codes FWI and SFGI…..codes protocol options

TC
Historical bytes
T1

Tk
CRC1
CRC2
Fig. 13.1-4 Structure of the ATS(2) Extended Specifications
None(3) References
None

195

Version 1.1

13.1.2.1 Structure of the Bytes(1) Basic Specifications
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.
(2) Extended Specifications
None(3) References
None

196

Version 1.1

13.1.2.2 Length Byte
(1) Basic Specifications
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 theindicated FSD. Therefore the maximum value of TL shall not exceed FSD-2.
(2) Extended Specifications
None(3) References
None

197

Version 1.1

13.1.2.3 Format Byte
(1) Basic Specifications
The format byte T0 is optional and is present as soon as the length is greater than 1.
only contain the following optional bytes when this format byte is present.

The ATS can

To consists of three parts (see "Fig. 13.1-5 Coding of Format Byte"):- 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 13.1-1 FSDI to
FSD Conversion").
b8
0

b7

b6

b5

b4

b3

b2

b1

FSCI
TA(1) is transmitted, if bit is set to 1
TB(1) is transmitted, if bit is set to 1
TC(1) is transmitted, if bit is set to 1
shall be set to 0, 1 is RFU
Fig. 13.1-5

Coding of Format Byte

(2) Extended Specifications
None(3) References
None

198

Y(1)

Version 1.1

13.1.2.4 Interface Byte TA(1)(1) Basic Specifications
The interface byte TA(1) consists of four parts (see "Fig. 13.1-6 Codig of Interface byte TA (1)"):- 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
0

b3

b2

b1

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
Fig. 13.1-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.
(2) Extended Specifications
None(3) References
None

199

Version 1.1

13.1.2.5 Interface Byte TB(1)(1) Basic Specifications
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 "Fig. 13.1-7 Coding of interface byte TB(1)"):- The most significant half-byte b8 to b5 is called FWI and codes FWT (see "13.3.2 Frame
Waiting Time (FWT)"). The value of FWI may be from 0 to 14, and a value of 15 indicates
RFU. The initial value of FWI is to be 4.
- The least significant half byte b4 to b1 is called SFGI and codes a multiplier value used todefine the SFGT. The SFGT defines a specific guard time needed by the PICC before it isready 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 indicates no SFGT needed and the values in therange 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
Fig. 13.1-7

Coding of Interface Byte TB(1)SFGT is calculated by the following formula:
SFGT = (256 x 16 / fc) x 2SFGISFGTMIN = minimum value of the frame delay time as defined in "12.Anticollision"
SFGTDEFAULT = SFGTMINSFGTMAX = approx. 4949 ms(2) Extended Specifications
None(3) References
None

200

Version 1.1

13.1.2.6 Interface Byte TC(1)(1) Basic Specifications
The interface byte TC(1) specifies a parameter of the protocol.
The specific interface byte TC(1) consists of two parts (see "Fig. 13.1-8 Coding of interface byte
TC(1)"):- The most significant bits b8 to b3 shall be (000000)b and all other values are RFU.
- The bits b2 and b1 define which optional fields in the prologue field a PICC does support. The
PCD is allowed to skip fields, which are supported by the PICC, but a field not supported by the
PICC shall never be transmitted by the PCD. The default value shall be (10)b indicating CID
supported and NAD not supported.
b8
0

b7
0

b6
0

b5
0

b4
0

b3
0

b2

b1

NAD supported, if bit is set to 1
CID supported, if bit is set to 1
shall be set to (000000)b, all other values
are RFU
Fig. 13.1-8

Coding of Interface Byte TC(1)(2) Extended Specifications
None(3) References
None

201

Version 1.1

13.1.2.7 Historical Bytes(1) Basic Specifications
The historical bytes A1 to Ak are optional and designate general information. The maximum
length of the ATS gives the maximum possible number of historical bytes. ISO/IEC 7816-4
specifies the content of the historical bytes.
(2) Extended Specifications
None(3) References
None

202

Version 1.1

13.1.3 Protocol and Parameter Selection Request(1) Basic Specifications
PPS request contains the start byte that is followed by the format byte and parameter byte (see "Fig.
13.1-9 Protocol and parameter selection request").
PPSSStart byte

PPS0

Format bytes

PPS1

Parameter bytes

CRC1
CRC2
Fig. 13.1-9

Protocol and Parameter Selection Request(2) Extended Specifications
None(3) References
None

203

Version 1.1

13.1.3.1 Protocol and Parameter Selection (PPS) Start(1) Basic Specifications
The first byte of PPS is the start byte, and is called PPSS. PPSS consists of two parts (see "Fig.
13.1-10 Coding of PPSS"):- The most significant half byte b8 to b5 shall be set to 'D' and identifies the PPS.
- The least significant half byte b4 to b1 is named CID and it defines the logical number of theaddressed PICC.
b8
1

b7
1

b6
0

b5
1

b4

b3

b2

b1

CID
shall be set to 1, 0 is RFU
shall be set to 0, 1 is RFU
shall be set to (11)b, all other values are RFU
Fig. 13.1-10

Coding of PPSS

(2) Extended Specifications
None(3) References
None

204

Version 1.1

13.1.3.2 PPS0
(1) Basic Specifications
PPS0 indicates the presence of the optional byte PPS1 (see "Fig. 13.1-11 PPS0").
b8
0

b7
0

b6
0

b5

b4
0

b3
0

b2
0

b1
1
shall be set to 1, 0 is RFU
shall be set to (000)b, all other values are RFU
PPS1 is transmitted, if bit is set to 1
shall be set to (000)b, all other values are RFU

Fig. 13.1-11

Coding of PPSS0(2) Extended Specifications
None(3) References
None

205

Version 1.1

13.1.3.3 PPS1
(1) Basic Specifications
PPPS1 consists of three parts (see "Fig. 13.1-12 Coding of PPS1"):- The most significant half byte b8 to b5 shall be (0000)b and all other values are RFU.
- The bits b4 to b3 are called DSI and code the selected divisor integer from PICC to PCD.
- The bits b2 and b1 are called DRI and code the selected divisor integer from PCD to PICC.
b8
0

b7
0

b6
0

b5
0

b4

b3

b2

b1

DRI
DSI
shall be set (0000)b, all other values are RFU
Fig. 13.1-12

Coding of PPS1

For the definition of DS and DR, see "13.1.2.4 Interface Byte TA(1)".
The coding of D is given in "Table 13.1-2 DRI, DSI to D conversion".
Table 13.1-2
DI
D

(00)b
1

DRI, DSI to D conversion(01)b2(2) Extended Specifications
None(3) References
None

206

(10)b
4

(11)b
8

Version 1.1

13.1.4 Protocol and Parameter Selection Response(1) Basic Specifications
The PPS response acknowledges the received PPS request and it contains only the start byte
specified in "13.1.3.1 Protocol and Parameter Selection (PPS) Start". This structure of the PPS
response is shown in "Fig. 13.1-13 Protocol and Parameter Selection Response".
PPSS

CRC1

CRC2

Fig. 13.1-13

Protocol and Parameter Selection Response(2) Extended Specifications
None(3) References
None

207

Version 1.1

13.1.5 Activation Frame Waiting Time
(1) Basic Specifications
The activation frame waiting time defines the maximum time for a PICC to start sending its
response frame after the end of a frame received from the PCD and has a value of 65536/fc (~4833µs).
NOTE The minimum time between frames in any direction (from PCD to PICC and from PICC
to PCD) is defined in "12. Anticollision".
(2) Extended Specifications
None(3) References
None

208

Version 1.1

13.1.6 Error Detection and Recovery
13.1.6.1 Handling of RATS and ATS(1) Basic Specifications(a) PCD rules
When the PCD has sent the RATS and receives a valid ATS the PCD shall continue operation.
In any other case the PCD may retransmit the RATS or it shall use the deactivation sequence as
defined in "13.4 Protocol Deactivation of PICC Type A and Type B".
(b) PICC rules
When the PICC has been selected with the last command and1) receives a valid RATS, the PICC
- shall send back its ATS and- shall disable the RATS (stop responding to received RATS).
2) receives any other block valid or invalid, except a HLTA Command, the PICC
- shall ignore the block and- shall remain in receive mode.
(2) Extended Specifications
None(3) References
None

209

Version 1.1

13.1.6.2 Handling of PPS Request and PPS Response(1) Basic Specifications(a) PCD rules
When the PCD has sent a PPS request and received a valid PPS response the PCD shall activate
the selected parameters and continue operation.
In any other case the PCD may retransmit a PPS request and continue operation.
(b) PICC rules
When the PICC has received a RATS, sent its ATS and1) received a valid PPS request, the PICC
- shall send the PPS response,- shall disable the PPS request (stop responding to received PPS requests) and- shall activate the received parameter.
2) received an invalid block, the PICC
- shall disable the PPS request (stop responding to received PPS requests) and- shall remain in receive mode.
3) received a valid block, except a PPS request, the PICC
- shall disable the PPS request (stop responding to received PPS requests) and- shall continue operation.
(2) Extended Specifications
None(3) References
None

210

Version 1.1

13.1.6.3 Handling of the CID During Activation(1) Basic Specifications
When the PCD has sent a RATS containing a CID not equal to 0 and
1) received an ATS indicating CID is supported, the PCD- shall send blocks containing CID=n to this PICC and- shall not use the CID=n for further RATS while this PICC is in ACTIVE state.
2) received an ATS indicating CID is not supported, the PCD- shall send blocks containing no CID to this PICC and- shall not activate any other PICC while this PICC is in ACTIVE state.
When the PCD has sent a RATS containing a CID equal to 0 and
1) received an ATS indicating CID is supported, the PCD- may send blocks containing CID equal to 0 to this PICC and- shall not activate any other PICC while this PICC is in ACTIVE state.
2) received an ATS indicating CID is not supported, the PCD shall- send blocks containing no CID to this PICC and- not activate any other PICC while this PICC is in ACTIVE state.
(2) Extended Specifications
None(3) References
None

211

Version 1.1

13.2Protocol Activation of PICC Type B(1) Basic Specifications
The activation sequence for a PICC Type B is described in "12. Anticollision".
(2) Extended Specifications
None(3) References
None

212

Version 1.1

13.3Half-duplex Block Transmission Protocol(1) Basic Specifications
The half-duplex block transmission protocol addresses the special needs of contactless card
environments and uses the frame format as defined in "12. Anticollision". Here, the following
frame structures are specified.
- Data block
In addition, the following codings are specified.
- Flow control, block chaining and transmission control including error recovery, etc.
- Special interface control- This protocol is designed according to the principle layering of the OSI reference model, withparticular attention to the minimization of interactions across boundaries. Four layers aredefined:- Physical layer exchanges bytes according to "12. Anticollision".
- Data link layer exchanges blocks as defined in this clause.
- Session layer combined with the data link layer for a minimum overhead.
- Application layer processing commands, which involve the exchange of at least one block or
chain of blocks in either direction.
(2) Extended Specifications
None(3) References
None

213

Version 1.1

13.3.1 Block Format(1) Basic Specifications
The block format (see "Fig. 13.3-1 Block Format") consists of a prologue field (mandatory), an
information field (optional) and an epilogue field (mandatory).
Prologue field
PCB

[CID]

[NAD]

1 byte1 byte1 byteInformation field

Epilogue field

[INF]

EDC
2 bytes

Error detection code
FSD/FSC

Fig. 13.3-1

Block Format(2) Extended Specifications
None(3) References
None

214

Version 1.1

13.3.1.1 Prologue Field(1) Basic Specifications
The prologue field is mandatory and consists of up to three bytes:- Protocol Control Byte (mandatory),- Card IDentifier (optional),- Node ADdress (optional).
(a) Protocol Control Byte Field
The PCB is used to convey the information required to control the data transmission.
The protocol defines three fundamental types of blocks:- I-Block used to convey information for use by the application layer.
- R-Block used to convey positive or negative acknowledgements. An R-Block never contains
an INF field. The acknowledgement relates to the last received block.
- S-Block used to exchange control information between the PCD and the PICC.
Two different types of S-Blocks are defined:
1) Waiting time extension containing a 1 byte long INF field and2) DESELECT containing no INF field
The coding of the PCB depends on its type and is defined by the following figures. PCB coding
not defined here are either used in ISO/IEC 14443 or are RFU. The coding of I-Blocks, R-Blocks
and S-Blocks are shown in "Fig. 13.3-2 Coding of I-Block PCB", "Fig. 13.3-3 Coding of R-Block
PCB" and "Fig. 13.3-4 Coding of S-Block PCB".

215

Version 1.1

b8
0

b7
0

b6
0

b5

b4

b3

b2
1

b1

Block number
RFU
NAD following, if bit is set to 1
CID following, if bit is set to 1
Chaining, if bit is set to 1
shall be set to 0, 1 is RFU
Coding of I-Block PCB
Fig. 13.3-2

b8
1

b7
0

b6
1

b5

b4

b3
0

b2
1

Coding of I-Block PCB

b1

Block number
shall be set to 1, 0 is RFU
shall be set to 0
CID following, if bit is set to 1
ACK, if bit is set to 0, NAK, if bit is set to 1
shall be set to 1
R-BlockFig. 13.3-3

b8
1

b7
1

b6

b5

b4

b3
0

b2
1

Coding of R-Block PCB

b1
0
shall be set to 0, 1 is RFU
shall be set to 1, 0 is RFU
shall be set to 0
CID following, if bit is set to 1(00)b DESELECT or (11)b WTX
S-BlockFig. 13.3-4

Coding of S-Block PCB

216

Version 1.1(b) Card Identifier Field
The CID field is used to identify a specific PICC and consists of three parts (see "Fig. 13.3-5
Coding of card identifier"):- The two most significant bits b8 and b7 are used to indicate the power level indication received
by a PICC from a PCD. There two bits shall be set to (00)b for PCD to PICC communication.
- The bits b6 and b5 are used to convey additional information, which are not defined and shall be
set to (00)b and all other values are RFU.
- The bits b4 to b1 code the CID.
b8

b7

b6
0

b5
0

b4

b3

b2

b1

CID
shall be set to (00)b, all other values are RFU
Power level indication

Fig. 13.3-5

Coding of Card IdentifierSee"13.3.3 Power Level Indication" for specifications regarding power level indication. The
coding of CID is given in "13.1.1 Request for Answer To Select" for Type A and "12.
Anticollision" for Type B.
The handling of the CID by a PICC is described below:
A PICC, which does not support a CID- shall ignore any block containing a CID.
A PICC, which does support a CID- shall respond to blocks containing its CID by using its CID,
- shall ignore blocks containing other CIDs and- shall, incase its CID is 0, respond also to blocks containing no CID by using no CID.

217

Version 1.1(c) Node Address Field
The NAD in the prologue field is reserved to build up and address different logical connections.
The usage of the NAD shall be compliant with the definition from ISO/IEC 7816-3, when the bits
b8 and b4 are both set to 0. All other values are RFU.
The following definitions shall apply for the usage of the NAD:a) The NAD field shall only be used for I-Blocks.
b) When the PCD uses the NAD, the PICC shall also use the NAD,c) During chaining the NAD shall only be transmitted in the first block of chain,d) The PCD shall never use the NAD to address different PICCs (The CID shall be used to address
different PICCs).
e) When the PICC does not support the NAD, it shall ignore any block containing the NAD.
(2) Extended Specifications
None(3) References
None

218

Version 1.1

13.3.1.2 Information Field (INF)(1) Basic Specifications
The INF field is optional. When present, the INF field conveys either application data in I-Blocks
or non-application data and status information in S-Blocks. The length of the information field is
calculated by counting the number of bytes of the whole block minus length of prologue andepilogue field.
(2) Extended Specifications
None(3) References
None

219

Version 1.1

13.3.1.3 Epilogue Field(1) Basic Specifications
The epilogue field contains the EDC of the transmitted block, which is the CRC defined in "12.
Anticollision".
(2) Extended Specifications
None(3) References
None

220

Version 1.1

13.3.2 Frame Waiting Time (FWT)(1) Basic Specifications
The FWT defines the maximum time within which a PICC shall start its response frame after theend of a PCD frame (see "Fig. 13.3-6 Frame Waiting Time").
Sent by the PCD

Sent by the PICC
T < FWT

Fig. 13.3-6
NOTE

Frame Waiting TimeThe minimum time between frames in any direction is defined in "12. Anticollision".

FWT is calculated by the following formula:
FWT = (256 x 16 / fc) x 2FWI
FWTMIN = approx. 302 µs
FWTDEFAULT = approx. 4833 µs
FWTMAX = approx. 4949 ms
The FWT value shall be used by the PCD to detect a protocol error or an unresponsive PICC.
The PCD obtains the right to re-transmit if the start of a response from the PICC is not received
within FWT.
When the PICC needs more time than the defined FWT to process the received block it shall usean S(WTX) request for a waiting time extension. An S(WTX) request contains a 1 byte long INF
field that consists of two parts (see "Fig. 13.3-7 Coding of INF field of an S(WTX) Request"):- The two most significant bits b8 and b7 code the power level indication (see "13.3.3 PowerLevel Indication").
- The least significant bits b6 to b1 code the WTXM. The WTXM is coded in the range from 1
to 59. The values 0 and 60 to 63 are RFU.

221

Version 1.1

b8

b7

b6

b5

b4

b3

b2

b1

WTXM
Power level indication
Fig. 13.3-7

Coding of INF Field of an S(WTX) Request

The PCD shall acknowledge by sending an S(WTX) response containing also a 1 byte long INF
field that consists of two parts (see "Fig. 13.3-8 Coding of INF Field of an S(WTX) Response")and contains the same WTXM as received in the request:- The most significant bits b8 and b7 shall be (00)b and all other values are RFU.
- The least significant bits b6 to b1 codes the acknowledged WTXM value used to define a
temporary FWT.
b8
0

b7
0

b6

b5

b4

b3

b2

b1

WTXM
shall be set to (00)b, all other values are RFU
Fig. 13.3-8

Coding of INF Field of an S(WTX) Response

The corresponding temporary value of FWT is calculated by the following formula:
FWTTEMP = FWT x WTXM
The time FWTTEMP requested by the PICC, starts after the PCD has sent the S(WTX) response.
FWTMAX shall be used, when the formula results in a value higher than FWTMAX.
The temporary FWT applies only until the next block has been received by the PCD.

222

Version 1.1

Type B FWI are included in ATQB (specified in "12. Anticollision").
In addition, type A FWI are included in ATS (specified in "13.1.2.5 Interface Byte TB(1))".
(2) Extended Specifications
None(3) References
None

223

Version 1.1

13.3.3 Power Level Indication(1) Basic Specifications
The power level indication is coded as shown in "Table 13.3-1 Coding of Power Level Indication"using two bits embedded in the CID field (when present) and in the S-Block sent by the PICC (see"13.3.1.1(b) Card Identifier Field" and "13.3.2 Frame Waiting Time (FWT)"). When coding thepower level, the two bits contained in the CID (when present) and S-Block returned by the PICC
are used.

Table 13.3-1
(00)b
(01)b
(10)b
(11)b

Coding of Power Level Indication

PICC does not support the power level indication
Insufficient power for full functionality
Sufficient power for full functionality
More than sufficient power for full functionality(2) Extended Specifications
None(3) References
Even if the PICC indicates a value other than (00)b, the PCD may ignore that indication.

224

Version 1.1

13.3.4 Protocol Operation(1) Basic Specifications
After the activation sequence the PICC shall wait for a block as only the PCD has the right to send.
After sending a block, the PCD shall switch to receive mode and wait for a block before switchingback to transmit mode.
The PICC may transmit blocks only in response to received blocks (it is insensitive to time delays).
After responding, the PICC shall return to the receive mode.
The PCD shall not initiate a new pair of command / response until the current pair of command /response has been completed or if the frame waiting time is exceeded with no response.
(2) Extended Specifications
None(3) References
None

225

Version 1.1

13.3.4.1 Multi-Activation(1) Basic Specifications
The Multi-Activation feature allows the PCD to hold several PICCs in the ACTIVE state
simultaneously. It allows switching directly between several PICCs without needingadditionaltime for deactivation of a PICC and activation of another PICC.
For an example of Multi-Activation, see "13.5 Multi-Activation Example".
NOTE

The PCD needs to handle a separate block number for each activated PICC.

(2) Extended Specifications
None(3) References
None

226

Version 1.1

13.3.4.2 Chaining(1) Basic Specifications
The chaining feature allows the PCD or PICC to transmit information that does not fit in a single
block as defined by FSC or FSD respectively, by dividing the information into several blocks.
Each of those blocks shall have a length less than or equal to FSC or FSD respectively.
The chaining bit in the PCB of an I-Block controls the chaining of blocks.
chaining bit set shall be acknowledged by an R-Block.

Each I-Block with the

The chaining feature is shown in "Fig. 13.3-9 Chaining" using a 16 bytes long string transmitted inthree blocks.
Notation:
I(1)x
I(0)x
R(ACK)x

I-Block with chaining bit set and block number x
I-Block with chaining bit not set (last block of chain) and block number x
R-Block that indicates a positive acknowledge.

227

Version 1.1

Receive

Send

0123456 789ABCD

EF

INF

PCB

INF

EDC

PCB

'12'

0123456'XX' 'XX'

'13'

I(1)0

Application
layer

Answer

EDC

789ABCD 'XX' 'XX'

I(1)1

Data link
layer

PCB

INF

EDC

'02'

EF

'XX' 'XX'

I(0)0

Physical
layer
PCB

EDC

'A2'

'XX' 'XX'

R(ACK)0

PCB

EDC

PCB

'A3'

'XX' 'XX'

'02'

R(ACK)1

0123456 789ABCD

INF

EDC

Answer 'XX' 'XX'

I(0)0

EF

Data linklayer

AnswerSend

Receive
Fig. 13.3-9

Chaining

Note: This example does not use the optional fields NAD and CID.
(2) Extended Specifications
None(3) References
None

228

Application
layer

Version 1.1

13.3.4.3 Error Detection and Recovery(1) Basic Specifications
The definitions made in clause overrule the block numbering rules (see "13.3.4.4 Block Number
Rules").
The following errors shall be detected by the PCD:
1) 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:- Resends block (optional),- Use of S(DESELECT) request,- Ignore the PICC.
2) Protocol error (infringement of PCB coding or infringement of protocol rules)
The PCD shall attempt error recovery by the following techniques in the order shown:- Use of S(DESELECT) request,- Ignore the PICC.
The following errors shall be detected by the PICC:- Transmission error (Frame error or EDC error),- Protocol error (infringement of the protocol rules).
The PICC shall attempt no error recovery. The PICC shall always return to receive mode, when atransmission error or a protocol error occurs and it shall accept an S(DESELECT) request at any
time.
NOTE

An R(NAK) block is never sent by the PICC.

(2) Extended Specifications
None(3) References
None

229

Version 1.1

13.3.4.4 Block Number Rules(1) Basic Specifications(a) PCD Rules
Rule A: The PCD block number shall be initialized to 0 for each activated PICC.
Rule B: When an I-Block or an R(ACK) block with a block number equal to the current blocknumber is received, the PCD shall toggle the current block number for that PICC before
optionally sending a block.
(b) PICC Rules
Rule C: The PICC block number shall be initialized to 1 at activation.
Rule D: When an I-Block is received (independent of its block number), the PICC shall toggle its
block number before sending a block.
Rule E: When an R(ACD) block with a block number not equal to the current PICC's blocknumber is received, the PICC shall toggle its block number before sending a block.
(2) Extended Specifications
None(3) References
None

230

Version 1.1

13.3.4.5 Block Handling Rules(1) Basic Specifications(a) General Rules
Rule 1: The first block shall be sent by the PCD.
Rule 2: When an I-Block indicating chaining is received, the block shall be acknowledged by an
R(ACK) block.
Rule 3: S-Blocks are only used in pairs. An S(...) request block shall always be followed by anS(...) response block (see "13.3.2 Frame Waiting Time (FWT)" and "13.4 Protocol
Deactivation of PICC Type A and Type B").
(b) PCD Rules
Rule 4: When an invalid block is received or a FWT time-out occurs, an R(NAK) block shall besent (except in the case of PICC chaining or S(DESELECT)).
Rule 5: In the case of PICC chaining, when an invalid block is received or a FWT time-out
occurs, an R(ACK) block shall be sent.
Rule 6: When an R(ACK) block is received, if its block number is not equal to the PCD's current
block number, the last I-Block shall be re-transmitted.
Rule 7: When an R(ACK) block is received, if its block number is equal to the PCD's current
block number, chaining shall be continued.
Rule 8: If the S(Deselect) request is not answered by an error-free S(DESELECT) response theS(DESELECT) request may be re-transmitted or the PICC may be ignored.
(c) PICC Rules
Rule 9: The PICC is allowed to send an S(WTX) block instead of an I-Block or an R(ACK)block.
Rule 10: When an I-Block not indicating chaining is received, the block shall be acknowledged by
an I-Block.
Rule 11: When an R(ACK) or an R(NAK) block is received, if its block number is equal to the
PICC's current block number, the last block shall be re-transmitted.

231

Version 1.1

Rule 12: When an R(NAK) block is received, if its block number is not equal to the PICC's current
block number, an R(ACK) block shall be sent.
Rule 13: When an R(ACK) block is received, if its block number is not equal to the PICC's current
block number, and the PICC is in chaining, chaining shall be continued.
(2) Extended Specifications
None(3) References
None

232

Version 1.1

13.4Protocol Deactivation of PICC Type A and Type B(1) Basic Specifications
The PICC shall be set to the HALT state, after the transactions between PCD and PICC have been
completed.
The deactivation of a PICC is done by using a DESELECT Command.
The DESELECT Command is coded as an S-Block of the protocol and consists of an
S(DESELECT) request block sent by the PCD and an S(DESELECT) response sent as
acknowledge by the PICC.
(2) Extended Specifications
None(3) References
None

233

Version 1.1

13.4.1 Deactivation Frame Waiting Time
(1) Basic Specifications
The deactivation frame waiting time defines the maximum time for a PICC to start sending its
S(DESELECT) response frame after the end of the S(DESELECT) request frame received fromthe PCD and has a value of 65536/fc (= approx. 4833 µs).
Note: The minimum time between frames in any direction is defined in "12. Anticollision".
(2) Extended Specifications
None(3) References
None

234

Version 1.1

13.4.2 Error Detection and Recovery(1) Basic Specifications
When the PCD has sent an S(DESELECT) request and has received an S(DESELECT) response,
the PICC has been set successfully to the HALT state and the CID assigned to it is released.
When the PCD fails to receive an S(DESELECT) response the PCD may retry the deactivation
sequence.
(2) Extended Specifications
None(3) References
None

235

Version 1.1

13.5Multi-Activation Example(1) Basic Specifications
The following table describes an example of the usage of Multi-Activation for three PICCs.

Table 13.5-1
PCD Action
Power On field
Three PICC enter the field
Activate PICC with CID=1
Any data transmission with CID=1...
Activate PICC with CID=2
Any data transmission with CID=1,2...
Activate PICC with CID=3
Any data transmission with
CID=1,2,3...
S(DESELECT) Command with
CID=3
S(DESELECT) Command with
CID=2
S(DESELECT) Command with
CID=1 HALT...

Multi-Activation

Status PICC 1IDLE
ACTIVE(1)ACTIVE(1)ACTIVE(1)ACTIVE(1)Status PICC 2
IDLE
IDLE
IDLE
ACTIVE(2)ACTIVE(2)Status PICC 3
IDLE
IDLE
IDLE
IDLE
IDLE

ACTIVE(1)ACTIVE(1)ACTIVE(2)ACTIVE(2)ACTIVE(3)ACTIVE(3)ACTIVE(1)ACTIVE(2)HALT

ACTIVE(1)

HALT

HALT

HALT

HALT

HALT

-

-

-

(2) Extended Specifications
None(3) References
None

236

Version 1.1

13.6Protocol Scenarios(1) Basic Specifications
This annex gives some scenarios for an error-free operation as well as for error handling.
scenarios may be used to build test cases for compliance tests.

These

The following symbols are used.
All block===> correctly received
All block=≠=> erroneously received
All block===> nothing received (FWT time-out)
Separation line ___ end of the smallest protocol operation
I(1)x
I-Block with chaining bit set and block number x
I(0)x
I-Block with chaining bit not set (last block of chain) and block number x
R(ACK)x
R-Block indicating a positive acknowledge
R(NAK)x
R-Block indicating a negative acknowledge
S(…)
S-Block
The block numbering in a scenario always starts with the PCD's current block number for thedestination PICC. For ease of presentation, scenarios start after the PICC activation sequence andhence the current block numbers start with 0 for the PCD and with 1 for the PICC.

237

Version 1.1"Fig. 13.6-1 Exchange of I-Blocks""Fig. 13.6-2 Request for Waiting Time Extension""Fig. 13.6-3 DESELECT""Fig. 13.6-4 Chaining (Part 1)""Fig. 13.6-5 Chaining (Part 2)""Fig. 13.6-6 Exchange of I-Blocks (Part 1)""Fig. 13.6-7 Exchange of I-Blocks (Part 2)""Fig. 13.6-8 Exchange of I-Blocks (Part 3)""Fig. 13.6-9 Exchange of I-Blocks (Part 4)""Fig. 13.6-10 Request for Waiting Time Extension (Part 1)""Fig. 13.6-11 Request for Waiting Time Extension (Part 2)""Fig. 13.6-12 Request for Waiting Time Extension (Part 3)""Fig. 13.6-13 Request for Waiting Time Extension (Part 4)""Fig. 13.6-14 Request for Waiting Time Extension (Part 5)""Fig. 13.6-15 DESELECT""Fig. 13.6-16 Chaining (Part 1)""Fig. 13.6-17 Chaining (Part 2)""Fig. 13.6-18 Chaining (Part 3)""Fig. 13.6-19 Chaining (Part 4)""Fig. 13.6-20 Chaining (Part 5)"
The scenario examples are shown above.
(2) Extended Specifications
None(3) References
None

238

Version 1.1

13.6.1 Error-free Operation
13.6.1.1 Exchange of I-Blocks(1) Basic Specifications
Scenario 1: Exchange of I-Blocks
Block no.
Comment(0)
Rule 1
1Rule B
1
2
3

PCD
I(0)0
I(0)1

Rule B0

Fig. 13.6-1

PICC
===>
<===

I(0)0

===>
<===

I(0)1

0
1

Exchange of I-Blocks(2) Extended Specifications
None(3) References
None

239

Block no.
(1)

Comment
Rule D
Rule 10
Rule D
Rule 10

Version 1.1

13.6.1.2 Request for Waiting Time Extension(1) Basic Specifications
Scemario 2: Waiting time extension
Block no.
Comment
PCD(0)
1
Rule 1
I(0)0
2
3
4
5
6

S(WTX) response

Rule B1
I(0)1

Rule B0

Fig. 13.6-2

PICC
===>
<===
===>
<===
===>
<===

0
S(WTX) request
I(0)0
1
I(0)1

Request for Waiting Time Extension(2) Extended Specifications
None(3) References
None

240

Block no.
(1)

Comment
Rule D
Rule 9Rule 10
Rule D
Rule 10

Version 1.1

13.6.1.3 DESELECT(1) Basic Specifications
Scenario 3: DESELECT
Block no.
Comment(0)7
Rule 18
Rule B
1
9

PCD

PICC

I(0)0

===>
<===

S(DESELECT)
request

0
I(0)0

===>

10

<===

Fig. 13.6-3

1
S(DESELECT)
response

DESELECT(2) Extended Specifications
None(3) References
None

241

Block no.
(1)

Comment
Rule D
Rule 10
Rule D
Rule 3

Version 1.1

13.6.1.4 Chaining(1) Basic Specifications
Scenario 4: PCD uses chaining
Block no.
Comment(0)1
Rule 1
2
Rule B
1
3
Rule 7
4
Rule B
0
5
6

PCD
I(1)0
I(0)1
I(0)0

Rule B

1

Fig. 13.6-4

Scenario 5: PICC uses chaining
Block no.
Comment(0)1
Rule 1
2
Rule B
1
3
Rule 2
4
Rule B
0
5
6

===>
<===
===>
<===
===>
<===

I(0)0
R(ACK)110
R(ACK)0
1
I(0)1
0
I(0)0

PICC
===>
<===
===>
<===

0
1
I(0)1
0
I(0)0

Chaining (Part 2)(2) Extended Specifications
None(3) References
None

242

Block no.
(1)

I(1)0

===>
<===

Fig. 13.6-5

Block no.
(1)

Comment
Rule D
Rule 2Rule D
Rule 10
Rule D
Rule 10Chaining (Part 1)

PCD

I(0)0

Rule B

PICC

Comment
Rule D
Rule 10
Rule E
Rule 12Rule D
Rule 10

Version 1.1

13.6.2 Error handling13.6.2.1 Exchange of I-Blocks(1) Basic Specifications
Scenario 6: Start of Protocol
Block no.
Comment(0)1
Rule 1
2
Time out
3
Rule 4
4
No change
5
Rule 6
6
Rule B
1
7
8

PCD
I(0)0
R(NAK)0
I(0)0
I(0)1

Rule B

Scenario 7: Exchange of I-Blocks
Block no.
Comment(0)1
Rule 1
2
Rule B
1
3
4
5
6
7
8
9
10

Time out
Rule 4

===>
<===

I(0)1

=≠=>

R(NAK)1
I(0)1
I(0)0

Rule B

1

Fig. 13.6-7

R(ACK)1
0
I(0)0
1
I(0)1

PICC

I(0)0

0

Block no.
(1)

Comment

Rule 12Rule D
Rule 10
Rule D
Rule 10

Exchange of I-Blocks (Part 1)

PCD

No change
Rule 6
Rule B

=≠=>
<===
===>
<===
===>
<===
===>
<===

0

Fig. 13.6-6

PICC

<===
===>
<===
===>
<===
===>
<===

0
I(0)0

R(ACK)0
1
I(0)1
0
I(0)0

Exchange of I-Blocks (Part 2)

243

Block no.
(1)

Comment
Rule D
Rule 10

Rule 12Rule D
Rule 10
Rule D
Rule 10

Version 1.1

Scenario 8: Exchange of I-Blocks
Block no.
Comment
PCD(0)
1
Rule 1
I(0)0
2
3
4
5
6

Rule 4Rule B

PICC

R(NAK)01
I(0)1

Rule B

===>
<===

0

Fig. 13.6-8

Rule 4
Time out
Rule 4Rule B

R(NAK)0

7
8

I(0)1

Rule B

0

===>
<=≠=
===>
<===
===>
<===

Rule D
Rule 10

1

Rule 11
Rule D
Rule 10Block no.
(1)

Comment

I(0)0
I(0)1

0
I(0)0

I(0)0
1
I(0)1

Exchange of I-Blocks (Part 4)(2) Extended Specifications
None(3) References
None

244

Rule D
Rule 10

-

===>
<===

Fig. 13.6-9

I(0)0

PICC

R(NAK)01

0Comment

Exchange of I-Blocks (Part 3)

Scenario 9: Exchange of I-Blocks
Block no.
Comment
PCD(0)
1
Rule 1
I(0)0
2
3
4
5
6

===>
<=≠=
===>
<===

Block no.
(1)

Rule 11
Rule D
Rule 10

Version 1.1

13.6.2.2 Waiting Time Extension(1) Basic Specifications
Scenario 10: Request for waiting time extension
Block no.
Comment
PCD(0)
1
Rule 1
I(0)0
2
3
4
5
6
7
8

Rule 4Rule 3Rule B

R(NAK)0S(WTX) response1
I(0)1

Rule B

Rule 4
Time out
Rule 4R(NAK)0R(NAK)0

Rule 3Rule B

1

Rule B

0

S(WTX) response

9
10

I(0)1

Fig. 13.6-11

Block no.
(1)

Comment

S(WTX) request

Rule D
Rule 9S(WTX) request

Rule 11I(0)01

Rule 10
Rule D
Rule 10Block no.
(1)

Comment0I(0)1

Waiting Time Extension (Part 1)

Scenario 11: Request for waiting time extension
Block no.
Comment
PCD(0)
1
Rule 1
I(0)0
2
3
4
5
6
7
8

===>
<=≠=
===>
<===
===>
<===
===>
<===

0

Fig. 13.6-10

PICC

PICC
===>
<=≠=
=≠=>
<===
===>
<===
===>
<===

0
S(WTX) request
S(WTX) request

Rule 11I(0)0Rule 10
Rule D
Rule 10

===>
<===

1
I(0)1

Request for Waiting Time Extension (Part 2)

245

Rule D
Rule 9

Version 1.1

Scenario 12: Request for Waiting Time Extension
Block no.
Comment
PCD(0)
1
Rule 1
I(0)0
===>
2
3
4
5
6
7
8
9
10

Rule 3Time out
Rule 4S(WTX) response
R(NAK)0

Rule 3Rule B

1

Rule B

0

S(WTX) response
I(0)1

Fig. 13.6-12

<===
=≠=>
<===
===>
<===
===>
<===
===>
<===

Rule 3S(WTX) response

Rule 4Rule B

R(NAK)0
1

7
8

I(0)1

Rule B

0

<===
===>
<=≠=
===>
<===

9
10

Rule 3Rule 4
Time out
Rule 4Rule B

S(WTX) response
R(NAK)0R(NAK)01
0Rule B
Fig. 13.6-14

Comment
Rule D
Rule 9S(WTX) request

Rule 11I(0)01

Rule 10
Rule D
Rule 10Block no.
(1)

Comment

I(0)1

PICC

S(WTX) request

Rule D
Rule 9I(0)0Rule 10I(0)01Rule 11
Rule D
Rule 10Block no.
(1)

Comment0

I(0)1

Request for Waiting Time Extension (Part 4)

Scenario 14: Request for Waiting Time Extension
Block no.
PCD
Comment(0)1
Rule 1
I(0)0
===>
2
3
4
5
6
7
8

0
S(WTX) request

===>
<===

Fig. 13.6-13

Block no.
(1)

Request for Waiting Time Extension (Part 3)

Scenario 13: Request for Waiting Time Extension
Block no.
PCD
Comment(0)1
Rule 1
I(0)0
===>
2
3
4
5
6

PICC

I(0)1

<===
===>
<=≠=
=≠=>
<===
===>
<===
===>
<===

PICC

S(WTX) request

Rule D
Rule 9I(0)0Rule 10

0

I(0)0
1
I(0)1

Request for Waiting Time Extension (Part 5)

246

Rule 11
Rule D
Rule 10

Version 1.1(2) Extended Specifications
None(3) References
None

247

Version 1.1

13.6.2.3 DESELECT(1) Basic Specifications
Scenario 15: DESELECT
Block no.
Comment(0)11
Rule 1
12
Rule B
13
14
15

PCD
I(0)0
S(DESELECT)
requestTime out
Rule 816

S(DESELECT)
request

PICC
===>
<===

I(0)0

Block
no. (1)

Comment
Rule D
Rule 10

=≠=>
<===
===>

-

<===

S(DESELECT)
response

Fig. 13.6-15 DESELECT(2) Extended Specifications
None(3) References
None

248

Rule 3

Version 1.1

13.6.2.4 Chaining(1) Basic Specifications
Scenario 16: PCD uses chaining
Block no.
Comment(0)1
Rule 1
2
3
4
5
6
7
8

Rule 4Rule B
Rule 7Rule B
Rule 7Rule B

9
10Rule B

PCD
I(1)0
R(NAK)0

1
I(1)1
0
I(0)0
1
I(0)1
0

Fig. 13.6-16

Scenario 17: PCD uses chaining
Block no.
Comment(0)1
Rule 1
2
Rule B
1
3
Rule 7
4
Time-out
5
Rule 4
6
No change
7
Rule 6
8
Rule B
0
9Rule 7
10
Rule B
1
11
12

===>
<=≠=
===>
<===
===>
<===
===>
<===
===>
<===

I(1)0
I(1)1
R(NAK)1
I(1)1
I(0)0

0
R(ACK) 0
R(ACK) 0
1
R(ACK)1
0
I(0)0
1
I(0)1

PICC
===>
<===
=≠=>
<===
===>
<===
===>
<===
===>
<===

R(ACK)0

Comment
Rule D
Rule 2Rule 11
Rule D
Rule 2Rule D
Rule 10
Rule D
Rule 10

Comment
Rule D
Rule 2

R(ACK)01
R(ACK)1
0
I(0)0
1
I(0)1

Chaining (Part 2)

249

Block no.
(1)
0

===>

0

Fig. 13.6-17

Block no.
(1)

Chaining (Part 1)

PCD

I(0)1

Rule B

PICC

Rule 12Rule D
Rule 2Rule D
Rule 10
Rule D
Rule 10

Version 1.1

Scenario 18: PCD uses chaining
Block no.
Comment(0)1
Rule 1
2
3
4
5
6
7
8
9
10

Rule 4Time-out
Rule 4Rule B
Rule 7Rule B
Rule 7Rule B

11
12

Rule B

PCD
I(1)0
R(NAK)0R(NAK)0

1
I(1)1
0
I(0)0
1
I(0)1
0

Fig. 13.6-18

PICC
===>
<=≠=
=≠=>
<===
===>
<===
===>
<===
===>
<===
===>
<===

===>
<===
=≠=>
<===
===>
<===
===>
<===

9

===>

10

Rule B

0

R(ACK) 0

Rule D
Rule 2

R(ACK) 0
1
R(ACK)1
0
I(0)0
1
I(0)1

PICC

<===

Fig. 13.6-19

0Comment

Rule D
Rule 11
Rule D
Rule 2Rule D
Rule 10
Rule D
Rule 10Chaining (Part 3)

Scenario 19: PCD uses chaining
Block no.
PCD
Comment(0)1
Rule 1I(0)02
Rule B
1
3
Rule 2
R(ACK)1
4
Time-out
5
Rule 5
R(ACK)1
6
Rule B
0
7
Rule 2
R(ACK)08
Rule B1
I(0)1

Block no.
(1)

Comment

0

Rule D
Rule 10

1

Rule E
Rule 13Rule E
Rule 13Rule D
Rule 10

I(1)0
I(1)1
0
I(0)0
1
I(0)1

Chaining (Part 4)

250

Block no.
(1)

Version 1.1

Scenario 20: PCD uses chaining
Block no.
PCD
Comment(0)1
Rule 1I(0)02
Rule B
1
3
Rule 2
R(ACK)1
4
5
6
7
8
9
10

Rule 5Rule B
Rule 2Rule B

R(ACK)10
R(ACK)01
I(0)1

Rule B0

Fig. 13.6-20

PICC
===>
<===
===>
<=≠=
===>
<===
===>
<===
===>
<===

0
I(1)0
1
I(1)1

None
(3) References
None

251

Comment
Rule D
Rule 10
Rule D
Rule 12

No change
I(1)1
0
I(0)0
1
I(0)1

Chaining (Part 5)(2) Extended Specifications

Block no.
(1)

Rule 11
Rule D
Rule 12Rule D
Rule 10

Version 1.1

13.7Block and Frame Coding Overview(1) Basic Specifications"Table 13.7-1 Block and Frame Coding" gives an overview of the different block and frame coding
sent by the PCD.
The type of a block respectively frame is indicated by the first byte.
(a) Definitions made in "12. Anticollision":
REQA(0100110)b (7 bit)
WUPA
(1010010)b (7 bit)
REQB/WUPB(00000101)b
SLOT MARKER (Type B only)(xxxx0101)b
Select (Type A only)(1001xxxx)b
ATTRIB (Type B only)(00011101)b
HLTA(01010000)b
HLTB(01010000)b(b) Definitions made in "13. Transmission Protocol":RATS(11100000)b
PPS(1101xxxx)b
I-Block(00xxxxxx)b(not (00xxx101)b)
R-Block(10xxxxxx)b(not (1001xxx)b)
S-Block(11xxxxxx)b(not (1110xxxx)b or (1101xxxx)b)

252

Version 1.1

Block and Frame Coding

SLOT MARKER

SELECTATTRIB

HLTA

HLTB

RATS

PPS

0

1

1

0

X

1

0

0

0

1

1

b7

0

0

1

0

X

0

0

1

1

1

1

b6

0 (RFU)

1

0

1

X

X

0

0

0

0

1

0

b5

Chaining

ACK/NAK

0

1

X

X

1

1

1

1

0

1

b4

CID

CID

CID

0

X

X

1

0

0

0

X

b3

NAD

0 (no NAD)0 (no NAD)

1

1

X

1

0

0

0

X

b2

1

1 (RFU)

1 (RFU)

0

0

X

0

0

0

0

X

b1

Block No.

Block No.

0 (RFU)

1

1

X

1

0

0

0

X

I-Block PCB

WTX

b8

Bit

R-Block PCB

REQB / WUPBDESELECT S-Block
PCB

Table 13.7-1(2) Extended Specifications
None(3) References
None

253

Version 1.1

13.8T=1 Protocol Usage Specifications
These specifications stipulate usage specifications in the case of applying the T=1 protocol
specified in ISO/IEC 7816-3 to proximity contactless IC cards. The contents described in "13.8
T=1 Protocol Usage Specifications" are all "reference specifications".
In the past, although the T=1 protocol was used in PICC provided with pins, it has been requested
that they would also like to be used in proximity contactless IC cards. However, since the T=1
protocol is targeted at a single PICC connected with a wire, it cannot be applied directly tomultiple PICC. In addition, since the communication protocol employed in ISO/IEC has adifferent T=1 protocol and block format, in environments in which both PICC employing thisprotocol and PICC employing the T=1 protocol are present, there is the potential for interference.
Therefore, the following stipulates usage specifications of a T=1 protocol that solves these
problems and can be applied to contactless IC cards (hereafter, to be referred to as the T=1'
protocol).

254

Version 1.1

13.8.1 PICC Activation
The procedure for PICC activation shall follow the procedures described in "12. Anticollision" and"13. Transmission Protocol". However, some responses from the PICC are changed in order toindicate differences in the protocol.
(a) Changes in Type A Time Slot Activation
In the case of using the T=1' protocol, the response (SAK_t) to an SEL_t command is changed tothat shown in "Fig. 13.8-1 SAK_t Response Format during T=1 Protocol" (equivalent to ATR of
ISO/IEC 7816-3). The PICC switches to the T=1' protocol after sending SAK_t.
In the case a PICC is present that returns a response other than SAK_t specified here or SAK_t
specified in "12. Anticollision", since this is not a PICC eligible for this standardization, a HALT_t
command is issued and the PICC is deactivated.

TS

T0

TA1 TB1 TC1 TD1 TA2 TB2 TC2 TD2 TA3

Fig. 13.8-1

...

T1

...

Tk

SAK_t Response Format during T=1 Protocol

TS: '3B' is to be fixed (LSB first, positive logic)
T0, Tai, Tbi, Tci, Tdi, T1…Tk: Same as ISO/IEC 7816-3 except for the following items:
T: Valid only when T=1, other values are taken to indicate RFU.
FI: FI = 128 regardless of value.
N, CWT: 8 etu regardless of value.
P, I, X, C: Values are invalid since this function does not exist.
Indication of protocol options: CRC is used regardless of value.
CRC: CRC of ISO/IEC 3309 is used (CRC initial value: 'FFFF').

255

CRC

Version 1.1(b) Changes in Type B Activation
In the case of using the T=1' protocol, some of the coding of the ATQB response and ATTRIB
command is changed, and information equivalent to ATR is returned with an Answer to ATTRIB
response. The PICC switches to the T=1' protocol after sending the Answer to ATTRIB response.
Changes during T=1 protocol:- ATQB response
Application Data (4 bytes): "T=1" is used as the code indicating the T=1' protocol.
Protocol_Type (4 bits): (0000)b since the protocol is not specified in ISO/IEC.
- ATTRIB command
Parameter 3 (b4 b3 b2 b1): (0000)b since the protocol is not specified in ISO/IEC.
Higher layer INF: Not used
- Answer to ATTRIB response
Equivalent to ATR (details are the same as those for the Type A time slot type).

256

Version 1.1

13.8.2 Protocol Processing
Protocol processing shall follow the specifications in ISO/IEC 7816-3. However, some of theprocessing is changed due to differences in the communication method and to prevent interference.
(a) Communication Format
The communication format of the PICC shall follow the specifications in "11. Polling" and "12.
Anticollision". However, a portion of the communication format is changed due to differences in
the communication method and to prevent interference, and these changes are shown in "Table
13.8-1 Communication Format". In addition, the EDC is taken to be CRC (ISO/IEC 3309) toensure the reliability of communications.

Table 13.8-1
ProtocolItem
Modulation/
demodulation

ISO/IEC 7816-3
T=1 protocol
None

Encoding

NRZ

Frame format

None

Synchronization
methodCharacterformatStart-stop
synchronization
Start: 1 bit
Data: 8 bits
Parity: Even
Stop: 1 bit

Communication Format
Type ATime slot
T=1' protocol
ISO/IEC 14443-2
Type A
ISO/IEC 14443-2
Type A
ISO/IEC 14443-3
Appendix C(Clock synchronization)

Data: 8 bits

257

Type B
T=1' protocol
ISO/IEC 14443-2
Type B
ISO/IEC 14443-2
Type B
ISO/IEC 14443-3
Type B
Start-stop
synchronization
Start: 1 bit
Data: 8 bits
Stop: 1 bit

Version 1.1(b) NAD Coding
Although NAD is inherently a byte that represents the node address of communication, it is usedhere as a PICC identifier (CID) and PCD identifier to prevent interference. In addition, since a
Vpp pin is not present on proximity contactless IC cards, the control bit of the Vpp pin is alsochanged so as to be used as an identifier. The coding of NAD is shown in "Fig. 13.8-2 NAD
Coding".
b8
b7
b6
b5
DAD (Destination Identifier)Fig. 13.8-2

b4
b3
b2
b1
SAD (Sender Identifier)
NAD Coding

The PICC identifier (CID) is to be the CID designated during PICC activation.
The PCD identifier is to be the SAD present in a command received error-free by the PICC during
the start of the protocol.
(c) Operational NAD Assignment Restrictions
According to ISO/IEC 7816-3, NAD is able to assume any value other than the same DAD and
SAD (excluding '0'). However, during application to proximity contactless IC cards, operational
restrictions are placed on the assignment of NAD in consideration of the possibility of the presenceof both a PICC before activation and a PICC complying with the protocol described in "13.
Transmission Protocol".
However, these restrictions do not restrict the functions of the PICC, but rather only restrict the
PICC with respect to system operation.

258

Version 1.1a) NAD Restrictions of the Type A Time Slot Type
Coding of the first byte of commands used with the type A time slot type is shown in "Fig.
13.8-3 NAD Restrictions of Type A Time Slot Type".
Lower 4 bits
Upper 4 bits

0

1

2

3

4

5

6

7

8
ID

0

I-Block

I-Block

1

I-Block

I-Block

9

A

B

C

D

I-Block

E

F

I-Block

HALT_t

(0~7)

2
3

(REQ)

4

HALT_t(8~F)

SEL_t (0~7)

56SEL_t (8~F)

7
8
9
A

R-Block

R-Block

B

R-Block

R-BlockC

S(DESEL)

S(DESEL)

D
E
F

PPS
RATS

S(WTX)S(WTX)

Commands specified in "12. Anticollision"Commands specified in "13. Transmission Protocol"
Collision of commands (but able to be distinguished due to different command sizes)

Fig. 13.8-3

NAD Restrictions of Type A Time Slot TypeAs a general rule, although NAD can be assigned to the empty spaces of the above "Fig. 13.8-3
NAD Restrictions of Type A Time Slot Type", in order to ensure future expandability, the PCD
identifier and PICC identifier shall assume the values shown below.
- PCD identifier: 'D'- PICC identifier (CID): Value other than 'D' (and '5' is also preferably not used)
Here, the HALT command for a PICC in which CID = '5' and the T=1 protocol command for a
PICC in which CID = '5' have the same first byte. Although they can be distinguished since
the frame sizes of both are clearly different, it is preferable not to use CID = '5' in considerationof the possibility of a PICC being present that responds incorrectly.

259

Version 1.1b) NAD Restrictions of the Type B Type
Coding of the first byte of commands used with the type B type is shown in "Fig. 13.8-4 NAD
Restrictions of Type B Type".
Lower 4 bits
1

2

3

1

I-Block

2

I-Block

4

5
REQB

6

7

8

9

A

B

I-Block

I-Block

I-Block

I-Block

C

D

E

ATTR

I-Block

4
5

HALT

6
7
8
9
A

R-Block

B

R-Block

R-BlockC

S(DESEL)

S(DESEL)

R-Block

S(WTX)S(WTX)

DE
F

Commands specified in "12. Anticollision"Commands specified in "13. Transmission Protocol"

Fig. 13.8-4

NAD Restrictions of Type B TypeIn accordance with the above "Fig. 13.8-4 NAD Restrictions of Type B Type", the PCD
identifier and PICC identifier shall assume the values shown below.
- PCD identifier: Value of '1', '4', '8', '9' or 'C'- PICC identifier (CID): Value other than identifier used by PCD

260

F

I-Block

3

Slot marker

Upper 4 bits

0

Version 1.1

13.8.2.1 PICC Receive Error Processing
According to ISO/IEC 7816-3, an R-Block is to be sent during an IC card receive error. In thecase of PICC, however, since there is the possibility of judging a command to another PICC asbeing a receive error, it is necessary to prevent the PICC from returning a response during a PICC
receive error.
At this time, communication sequence management of the PICC performs processing by assumingthat there has been no reception.

261

Version 1.1

13.8.2.2 Card Deactivation
The procedure for PICC deactivation shall follow the procedure described in "12. Anticollision".
Consequently, the HALT (HALT_t) command can still be recognized even after the PICC has
switched to the T=1 protocol.

262

Version 1.1

13.9Transmission Control Matrix of T=CL Protocol (Reference)
A transmission control matrix is shown in "Table 13.9-1 PICC Transmission Control Matrix (for Upper Device)" and "Table 13.9-2 PCD (Upper Device) Transmission Control Matrix (for PICC)" to facilitate understanding.
These are only shown for reference purposes, however.

Table 13.9-1
Event

PICC Transmission Control Matrix (for Upper Device)

Receive I-Block (from PCD)

Receive R-Block (from PCD)

A

B

C

D

E

F

G

H

No chaining
I(0)0
received

No chaining
I(0)1
received

Chaining
I(1)0
received

Chaining
I(1)1
received

R(ACK)0
received

R(ACK)1
received

R(NAK)0
received

R(NAK)1
received

–
→*

–
→*

Rule 12 → 6
Send R(ACK)1–→*Rule 11 → 1
Resend final block
I(0)0

–
→*

Rule 11 → 1
Resend final block
I(0)0

Rule 12 → 5
Send R(ACK)0–→*

Rule 11 → 2
Resend final
block I(0)1

Rule 12 → 6
Send R(ACK)1Rule 11 → 2
Resend final block
I(0)1

Rule 11 → 3
Resend final block
I(1)0

Internal bn
updatedRule 13
Send I(0)1 → 2
Send I(1)1 → 4

Rule 11 → 3
Resend final block
I(1)0

–
→*

Internal bn
updatedRule 13
Send I(0)0 → 1
Send I(1)0 → 3

Rule 11 → 4
Resend final
block I(1)1–→*

Rule 11 → 4
Resend final block
I(1)1

Receive S-Block(from PCD)
J
I
Response
S(WTK)
received

Request
S(DESELECT)
received–→*

Send response
S(DESELECT)→ End of current
protocolprocessing

Receive error message
K

L

Error message(PCB error)

Error
message(CRC error,
EGT time
out)

–
→*

–
→*

Status0: Protocol
start state

1: Receive waitstate after sending
I(0)0 (no chaining)
2: Receive waitstate after sending
I(0)1 (no chaining)

Internal bn updated
Rule 10 → 1 Send I(0)0
Rule 10 → 3 Send I(1)0
Send S(WTX) → 7
Internal bn updated
Rule 10 → 2 Send I(0)1
Rule 10 → 4 Send I(1)1
Send S(WTX) → 7
Internal bn updated
Rule 10 → 1 Send I(0)0
Rule 10 → 3 Send I(1)0
Send S(WTX)7

Internal bn updated
Rule 2
Send R(ACK)0 → 5
Send S(WTX) → 7
Internal bn updated
Rule 2
Send R(ACK)1 → 6
Send S(WTX) → 7
Internal bn updated
Rule 2
Send R(ACK)0 → 5
Send S(WTX) → 7

3: Receive waitstate after sending
I(1)0 (chaining)

4: Receive waitstate after sending
I(1)1 (chaining)

–
→*

–
→*

263

Version 1.1

Table 13.9-1

Event

PICC Transmission Control Matrix (for Upper Device) (continued)

Receive I-Block (from PCD)

Receive S-Block(from PCD)

Receive R-Block (from PCD)

Receive error message

A

B

C

D

E

F

G

H

I

J

K

L

No chaining
I(0)0
received

No chaining
I(0)1
received

Chaining
I(1)0
received

Chaining
I(1)1
received

R(ACK)0
received

R(ACK)1
received

R(NAK)0
received

R(NAK)1
received

Response S(WTK)
received

Request
S(DESELECT)
received

Error message(PCB error)

Error
message(CRC error,
EGT time
out)

Rule 11 → 5
Resend final
block
R(ACK)0

Rule 12 → 5
Send
R(ACK)0

–
→*

–
*

Status5: Receive waitstate after sending
R(ACK)0
6: Receive waitstate after sending
R(ACK)1
7: Receive waitstate after
sending S(WTX)
requestInternal bn updated
Rule 10 → 2 Send I(0)1
Rule 10 → 4 Send I(1)1
Send S(WTX) → 7
Internal bn updated
Rule 10 → 1 Send I(0)0
Rule 10 → 3 Send I(1)0
Send S(WTX) → 7

Internal bn updated
Rule 2
Send R(ACK)1 → 6
Send S(WTX) → 7
Internal bn updated
Rule 2
Send R(ACK) 0 → 5
Send S(WTX) → 7

–
→*

–
→*

–
→*

Rule 12 → 6
Send
R(ACK)1

Rule 11 → 6
Resend final
block
R(ACK)1

Send request S(WTX) → 7(Resend)

–
→*

–
→*

Command to besent prior tochanging to thisstate are sent
followed byproceeding to its
status

Note 1: The number retained internally by the PICC for imparting a block number to the block to be sent next is to be referred to as the internal block number (internal bn).
Note 2: *: Returns to immediately previous transmission status

264

Send response
S(DESELECT) →end of current
protocol processing

Version 1.1

Table 13.9-2
EventA

Status0: Waiting for
instructions fromupper layer
1: Receive waitstate after sending
I(0)0 (no chaining)
Expecting I-Block

2: Receive waitstate after sending
I(0)1 (no chaining)
Expecting I-Block

Receive I-Block (from PCD)C
B

PCD (Upper Device) Transmission Control Matrix (for PICC)

D

Receive R-Block (from PCD)F
E

Receive S-Block (from PCD)
H
G

I

Receive error message
J

K

No chaining
I(0)0 received

No chaining
I(0)1 received

Chaining
I(1)0 received

Chaining
I(1)1 received

R(ACK)0
received

R(ACK)1
received

RequestS(WTK)
received

Response
S(DESELEC
T) received

Error
message(PCB error)

Error message(CRC error, EGT
time out)

FWT time out

–

–

–

–

–

–

–

–

–

–

–

Normaltermination(n clear) → 0
Waiting for
upper layer
instructions
Block number
violation → 0

Block number
violation → 0

Normalreceiving(n clear)
Rule 2→6

Block number
violation → 0

Transmission error
n+1
N = n-1: Retry out →0
N > n-1: Rule 4 → 7

Transmission error
n+1
N = n-1: Retry out →0
N > n-1: Rule 4 → 7

Normaltermination(n clear) → 0
Waiting for
upper layer
instructions

Block number
violation → 0

Normaltermination(n clear)
Rule 2→5Transmission error
n+1
N = n-1: Retry out →0
N > n-1: Rule 4 → 8

Transmission error
n+1
N = n-1: Retry out →0
N > n-1: Rule 4 → 8

Transmission error
n+1
N = n-1: Retry out →0
N > n-1: Rule 4 → 8

Transmission error
n+1
N = n-1: Retry out →0
N > n-1: Rule 4 → 8

Transmission error
n+1
N = n-1: Retry out →0
N > n-1: Rule 4 → 8

Transmission error
n+1
N = n-1: Retry out →0
N > n-1: Rule 4 → 8

Transmission error
n+1
N = n-1: Retry out →0
N > n-1: Rule 5 → 5Transmission error
n+1
N = n-1: Retry out →0
N > n-1: Rule 5 → 5

Protocol error → 0

Chaining
continued(n clear)
Rule 7
Send I(0)1 → 2
Send I(1)1 → 4

3: Receive waitstate after sending
I(1)0 (chaining)
Expecting I-Block
ExpectingR(ACK)

Block number
violation → 0
Send response
S(WTX)

Protocol error→0Format error→0

Protocol error → 0
4: Receive waitstate after sending
I(1)1 (chaining)
Expecting I-Block
ExpectingR(ACK)
5: Receive waitstate after sending
R(ACK)0
Expecting I-Block

Block number
violation → 0

Block number
Chaining
Normalviolation → 0
continued
termination(n clear)(n clear) → 0
Rule 2 → 6
Chaining
Send R(ACK)1
completed,waiting for upper
layer instructions

Chaining
continued(n clear)
Rule 7
Send I(0)1 → 1
Send I(1)1 → 3

Block number
violation → 0
Protocol error → 0

265Version 1.1

Table 13.9-2
EventA

Status
6: Receive waitstate after sending
R(ACK)1
Expecting I-Block

7: Receive waitstate after sending
R(NAK)0

8: Receive waitstate after sending
R(NAK)1

9: Receive waitstate after sending
S(DESELECT)
requestPCD (Upper Device) Transmission Control Matrix (for PICC) (continued)

Receive I-Block (from PCD)C
B
Chaining
I(1)0 received

No chaining
I(0)0 received

No chaining
I(0)1 received

Block number
violation → 0

Normaltermination(n clear) → 0
PICC chaining
completed,waiting for
upper layer
instructions

Block number
violation → 0

Normaltermination(n clear) → 0
Waiting for
upper layer
instructions

Block number
violation → 0

Chaining
continued(n clear)
Rule 2 → 6
Send R(ACK)1Block number
violation → 0

Normaltermination(n clear) → 0
Waiting for
upper layer
instructions

Block number
violation → 0

DChaining
I(1)1 received

Chaining continued(n clear)
Rule 2 → 5
Send R(ACK)0

Receive R-Block (from PCD)F
E
R(ACK)0
received

R(ACK)1
received

Receive S-Block (from PCD)H
G
RequestS(WTK)
received

I

Error
Response
message
S(DESELECT)(PCB error)
received

Block number
violation → 0

Resend final I
block (n clear)
Rule 6
Send I(0)0 → 1
Send I(1)0 → 3

Chaining continued(n clear)
Rule 2 → 5
Send R(ACK)0

Resend final I
block (n clear)
Rule 6
Send I(0)1 → 2
Send I(1)1 → 4

Chaining
continued(n clear)
Rule 7
Send I(0)0 → 1
Send I(1)0 → 3

Send
response
S(WTX)

Protocol error→0Note 1: n: Error counter (initial value: 0), N: upper limit value of requests for resending
In the case event J or K occurs after requesting resending N times, the protocol ends and returns to status 0.

266

FWT time out

Formaterror → 0

Transmission error
Transmission error
n+1
n+1
N = n-1: Retry out → N = n-1: Retry out →00
N > n-1: Rule 4 → 7 N > n-1: Rule 4 → 7
Transmission error
Transmission error
n+1
n+1
N = n-1: Retry out → N = n-1: Retry out →00
N > n-1: Rule 4 → 8 N > n-1: Rule 4 → 8→ End ofcurrent
protocolprocessing

Rule 8 → 0

Error message (CRC
error, EGT time out)

K

Transmission error
Transmission error
n+1
n+1
N = n-1: Retry out → N = n-1: Retry out →00
N > n-1: Rule 5 → 6 N > n-1: Rule 5 → 6

Protocol error → 0

Chaining
continued(n clear)
Rule 7
Send I(0)1 → 2
Send (1)1 → 4

Receive error message
J

Rule 8 → 0