Extension of PICC and PCD test methods

Extension des méthodes de test PICC et PCD

General Information

Status
Published
Current Stage
4098 - Project deleted
Start Date
03-Aug-2017
Ref Project

RELATIONS

Buy Standard

Draft
ISO/IEC 10373-6:2016/DAmd 2 - Extension of PICC and PCD test methods
English language
38 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (sample)

DRAFT AMENDMENT ISO/IEC 10373-6/DAmd 2
ISO/IEC JTC 1/SC 17 Secretariat: ANSI
Voting begins on Voting terminates on
2014-06-30 2014-09-30

INTERNATIONAL ORGANIZATION FOR STANDARDIZATION • МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ • ORGANISATION INTERNATIONALE DE NORMALISATION

INTERNATIONAL ELECTROTECHNICAL COMMISSION • МЕЖДУНАРОДНАЯ ЭЛЕКТРОТЕХНИЧЕСКАЯ КОММИСИЯ • COMMISSION ÉLECTROTECHNIQUE INTERNATIONALE

Identification cards — Test methods
Part 6:
Proximity cards
AMENDMENT 2 Extension of PICC and PCD test methods
Cartes d'identification — Méthodes d'essai
Partie 6: Cartes de proximité
AMENDEMENT 2 Extension des méthodes de test PICC et PCD
ICS 35.240.15

To expedite distribution, this document is circulated as received from the committee

secretariat. ISO Central Secretariat work of editing and text composition will be undertaken at

publication stage.

Pour accélérer la distribution, le présent document est distribué tel qu'il est parvenu du

secrétariat du comité. Le travail de rédaction et de composition de texte sera effectué au

Secrétariat central de l'ISO au stade de publication.

THIS DOCUMENT IS A DRAFT CIRCULATED FOR COMMENT AND APPROVAL. IT IS THEREFORE SUBJECT TO CHANGE AND MAY NOT BE

REFERRED TO AS AN INTERNATIONAL STANDARD UNTIL PUBLISHED AS SUCH.
R PURPOSES,

IN ADDITION TO THEIR EVALUATION AS BEING ACCEPTABLE FOR INDUSTRIAL, TECHNOLOGICAL, COMMERCIAL AND USE

DRAFT INTERNATIONAL STANDARDS MAY ON OCCASION HAVE TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL TO BECOME

STANDARDS TO WHICH REFERENCE MAY BE MADE IN NATIONAL REGULATIONS.

RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT, WITH THEIR COMMENTS, NOTIFICATION OF ANY RELEVANT PATENT RIGHTS OF WHICH

THEY ARE AWARE AND TO PROVIDE SUPPORTING DOCUMENTATION.
International Organization for Standardization, 2014
International Electrotechnical Commission, 2014
---------------------- Page: 1 ----------------------
ISO/IEC 10373-6/DAmd 2
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2014

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any

means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission.

Permission can be requested from either ISO at the address below or ISO’s member body in the country of the requester.

ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2014 — All rights reserved
---------------------- Page: 2 ----------------------
DRAFT AMENDMENT ISO/IEC 10373-6:2011/FPDAM 8
Copyright notice

This ISO document is a Draft International Standard and is copyright-protected by ISO. Except as permitted

under the applicable laws of the user's country, neither this ISO draft nor any extract from it may be

reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic,

photocopying, recording or otherwise, without prior written permission being secured.

Requests for permission to reproduce should be addressed to either ISO at the address below or ISO's

member body in the country of the requester.
ISO copyright office
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Reproduction may be subject to royalty payments or a licensing agreement.
Violators may be prosecuted.
© ISO/IEC 2014 – All rights reserved 1
---------------------- Page: 3 ----------------------
Foreword

ISO (the International Organization for Standardization) and IEC (the International Electrotechnical

Commission) form the specialized system for worldwide standardization. National bodies that are members of

ISO or IEC participate in the development of International Standards through technical committees

established by the respective organization to deal with particular fields of technical activity. ISO and IEC

technical committees collaborate in fields of mutual interest. Other international organizations, governmental

and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information

technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.

International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.

The main task of the joint technical committee is to prepare International Standards. Draft International

Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as

an International Standard requires approval by at least 75 % of the national bodies casting a vote.

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent

rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.

Amendment 8 to ISO/IEC 10373-6:2011 was prepared by Joint Technical Committee ISO/IEC JTC 1,

Information technology, Subcommittee SC 17, Cards and personal identification.
2 © ISO/IEC 2014 – All rights reserved
---------------------- Page: 4 ----------------------
Identification cards — Test methods — Part 6: Proximity cards
AMENDEMENT 8: EXTENSION OF PICC AND PCD TEST METHODS
Page 6, 4.3
Add the following text at the beginning of 4.3:

"The following absolute tolerances shall be applied when adjusting test conditions in 7.2.2:

 for timings (t , t , t , t , t , t , t ): ± 1/fc
1 2 3 5 6 r f
 for envelope overshoot, Type A: ± 0,01 × (1-a)
 for envelope overshoot and undershoot, Type B: ± 0,01 × (1-b)
 for the modulation index m: ± 0,5 %
 for the pulse shape factor a: ± 0,02"
Editor's note: For highest bit rates, the timing tolerance may be too high
Page 6, Clause 4
Add the following subclause at the end of the clause 4:
"4.6 DUT position

The PICC and Reference PICC antennas shall be centered on the sense coil a of the test PCD assembly."

Page 12, 6.1.1.1
Replace:
"the average value specified in ISO/IEC 14443-1:2008"
with:

"the average values specified in ISO/IEC 14443-1:2008/Amd.1:2012, 4.4 for each class"

© ISO/IEC 2014 – All rights reserved 3
---------------------- Page: 5 ----------------------
Page 12, 6.1.1.2
Add the following sentence at the beginning:
"Apply the following procedure with each Reference PICC."
Replace:
WARNING - R2 value should be between 55 and 65 Ω.
with the following text:
WARNING - R2 value for Reference PICC 1 should be between 55 and 65 Ω.

Editor's note: the warning needs to be updated with the missing R2 values for Reference PICCs 2 to 6.

Page 13, 6.2.1.2
Replace existing step g):
"g) Check that the PICC operates as intended."
with the modified steps g) and h):
"g) Wait for 30 s at 0 A/m (rms).
h) Check that the PICC operates as intended."
Page 14, 7.1 (amended by ISO/IEC 10373-6:2011/Amd.1:2012)
Replace existing Table 3 with the following Table:
Class Reference H test H test Test PCD assembly
min max
PICC
V R2 R2 R2 R2
load min max min max
1 1 6 V 870 Ω 1070 Ω 85 Ω – 10% 85 Ω + 10% Test PCD assembly 1
2 2 4,5 V 1030 Ω 1260 Ω 125 Ω – 10% 125 Ω + 10% Test PCD assembly 1
3 3 4,5 V 1080 Ω 1320 Ω 130 Ω – 10% 130 Ω + 10% Test PCD assembly 1
4 4 4,5 V 990 Ω 1210 Ω 110 Ω – 10% 110 Ω + 10% Test PCD assembly 2
5 5 4,5 V 960 Ω 1170 Ω 115 Ω – 10% 115 Ω + 10% Test PCD assembly 2
6 6 4,5 V 900 Ω 1100 Ω 130 Ω – 10% 130 Ω + 10% Test PCD assembly 2
Page 15, 7.1.1.2 (amended by ISO/IEC 10373-6:2011/Amd.1:2012)

Replace the existing warning of step b) in the procedure for H test with the following:

max

"WARNING — R2 value should be between R2 and R2 as defined in H test columns in Table 3.

min max max
Check this range at least once before using the alternative method."
4 © ISO/IEC 2014 – All rights reserved
---------------------- Page: 6 ----------------------

Replace the existing warning of step b) in the procedure for H test with the following:

min

"WARNING — R2 value should be between R2 and R2 as defined in H test columns in Table 3.

min max min
Check this range at least once before using the alternative method."
Page 19, 7.2.2
Add a new subclause and renumber following subclauses:
"7.2.2.2 General conditions

The test conditions shall be checked using the analysis tool defined in Annex E with the PICC under test in the

DUT position. If at least a parameter is not within the tolerances defined in 4.3, the test conditions shall be

readjusted."
Page 89, G.3.3.2.1
Add the following table footnote a in line IDLE of Table G.5:
IDLE state may be reached from ACTIVE state
Replace the original table footnote a in Table G.6:

Any SELECT command may be preceded with an anticollision command to retrieve the PICC UID, especially for

random UID.
with the modified table footnote a:

If the PICC UID is unknown, SELECT command may be preceded with an anticollision command to retrieve the PICC

UID.
Add the following row at the end of Table G.6:
REQA 
ACTIVE  IDLE
 Mute
Page 90, G.3.3.2.2

Delete the table footnote a from Table G.7 on States "READY(I), I < CascadeLevels" and "READY(I),

I = CascadeLevels".
Add a table footnote a on received ATQA in Table G.7 on states IDLE and HALT:

If PICC UID is known , send an anticollision command to retrieve the PICC UID. Check that UID has not changed.

© ISO/IEC 2014 – All rights reserved 5
---------------------- Page: 7 ----------------------
Page 91, G.3.3.3.2
Replace the original step a):
"a) Put the PICC into IDLE state."
with the modified step a):

"a) Put the PICC into IDLE state. If the UID is unknown, put the PICC in ACTIVE state to retrieve its UID and

then put it in IDLE state. Check that the value '88' of the cascade tag CT is not used for uid0 in single size

UID. "
Add the following row at the end of Table G.8:
Transition PICC-test-apparatus PICC FDT TTS
('93 20')  IDLE
 Mute
Remove the table footnotes c and d from Table G.8
Page 93, G.3.3.4.2
Add the following rows at the end of Table G.10:
Transition PICC-test-apparatus PICC FDT TTS
('93 20', wrong parity bit)  IDLE
(wrong parity bit)
 Mute
SELECT(1) with wrong parity  IDLE
SELECT g
bit
(wrong parity bit) h
 Mute
('93 20')  1172/fc READY(1)

UIDTX1[[1..32]] BCC
Replace the original table footnote g in Table G.10:

Any SELECT command may be preceded with an anticollision command to retrieve the PICC UID, especially for

random UID.
with the modified table footnote g:

If the PICC UID is unknown, SELECT command may be preceded with an anticollision command to retrieve the PICC

UID, especially for random UID.
Add the following table footnote h in Table G.10:

The parity error is simulated on the first transmitted byte of the frame by reversing the parity bit.

6 © ISO/IEC 2014 – All rights reserved
---------------------- Page: 8 ----------------------
Page 95, G.3.3.5.2
Add the following rows at the end of Table G.12:
Transition PICC-test-apparatus PICC FDT TTS
('95 20', wrong parity bit)  IDLE
(wrong parity bit)
 Mute
SELECT(2) with wrong parity  IDLE
SELECT
bit
(wrong parity bit)
 Mute
('95 20')  1172/fc READY(2)
 UIDTX1[[1..32]] BCC
Replace the original table footnote g in Table G.12:

Any SELECT command may be preceded with an anticollision command to retrieve the PICC UID, especially for

random UID.
with the modified table footnote g:

If the PICC UID is unknown, SELECT command may be preceded with an anticollision command to retrieve the PICC

UID.
Add the following table footnote h in Table G.12:

The parity error is simulated on the first transmitted byte of the frame by reversing the parity bit.

Page 97, G.3.3.6.2
Add the following rows at the end of Table G.14:
Transition PICC-test-apparatus PICC FDT TTS
('97 20', wrong parity bit)  IDLE
(wrong parity bit)
 Mute
SELECT(3) with wrong parity  IDLE
SELECT
bit
(wrong parity bit)
 Mute
('97 20')  1172/fc READY(3)
 UIDTX1[[1..32]] BCC
Replace the original table footnote e in Table G.14:

Any SELECT command may be preceded with an anticollision command to retrieve the PICC UID, especially for

random UID.
© ISO/IEC 2014 – All rights reserved 7
---------------------- Page: 9 ----------------------
with the modified table footnote e:

If the PICC UID is unknown, SELECT command may be preceded with an anticollision command to retrieve the PICC

UID.
Add the following table footnote f in Table G.14:

The parity error is simulated on the first transmitted byte of the frame by reversing the parity bit.

Page 98, G.3.3.7.2
Add the following rows at the end of Table G.16:
Transition PICC-test-apparatus PICC FDT TTS
RATS(0,0) with wrong parity bit  IDLE
RATS
(wrong parity bit) b
 Mute
REQB  IDLE or ACTIVE
Type B command
 Mute
('93 20')  IDLE
 Mute
Add the following table footnotes c and d in Table G.16:

The parity error is simulated on the first transmitted byte of the frame by reversing the parity bit.

Check first IDLE state as TTS. If TTS is not IDLE state, rerun the test a second time to check ACTIVE state.

Page 100, G.3.3.8.2
Add the following row at the end of Table G.18:
Transition PICC-test-apparatus PICC FDT TTS
('93 20')  HALT
 Mute
8 © ISO/IEC 2014 – All rights reserved
---------------------- Page: 10 ----------------------
Page 101, G.3.3.9.2
Add the following rows at the end of Table G.20:
Transition PICC-test-apparatus PICC FDT TTS
('93 20', wrong parity bit)  HALT
(wrong parity bit)
 Mute
SELECT(1) with wrong parity  HALT
SELECT
bit
(wrong parity bit)
 Mute
 READY*(1) or
REQB
HALT
Type B command
 Mute
('93 20')  HALT
 Mute
Add the following table footnotes g and h in Table G.20:

The parity error is simulated on the first transmitted byte of the frame by reversing the parity bit.

Check first HALT state as TTS. If TTS is not HALT state, rerun the test a second time to check READY*(1) state.

Page 103, G.3.3.10.2
Add the following rows at the end of Table G.22:
Transition PICC-test-apparatus PICC FDT TTS
('95 20', wrong parity bit)  HALT
(wrong parity bit)
 Mute
SELECT(2) with wrong parity  HALT
SELECT
bit
(wrong parity bit)
 Mute
 READY*(2) or
REQB
HALT
Type B command
 Mute
('95 20')  HALT
 Mute
Add the following table footnotes g and h in Table G.22:

The parity error is simulated on the first transmitted byte of the frame by reversing the parity bit.

Check first HALT state as TTS. If TTS is not HALT state, rerun the test a second time to check READY*(2) state.

© ISO/IEC 2014 – All rights reserved 9
---------------------- Page: 11 ----------------------
Page 105, G.3.3.11.2
Add the following rows at the end of Table G.24:
Transition PICC-test-apparatus PICC FDT TTS
('97 20', wrong parity bit)  HALT
(wrong parity bit)
 Mute
SELECT(3) with wrong parity  HALT
SELECT
bit
(wrong parity bit)
 Mute
 READY*(3) or
REQB
HALT
Type B command
 Mute
('97 20')  HALT
 Mute
Add the following table footnotes e and f in Table G.24:

The parity error is simulated on the first transmitted byte of the frame by reversing the parity bit.

Check first HALT state as TTS. If TTS is not HALT state, rerun the test a second time to check READY*(3) state.

Page 107, G.3.3.12.2
Add the following rows at the end of Table G.26:
Transition PICC-test-apparatus PICC FDT TTS
RATS(0,0) with wrong parity bit  HALT
RATS
(wrong parity bit) b
 Mute
REQB  HALT or
Type B command
ACTIVE*
 Mute
('93 20')  HALT
 Mute
Add the following table footnotes c and d in Table G.26:

The parity error is simulated on the first transmitted byte of the frame by reversing the parity bit.

Check first HALT state as TTS. If TTS is not HALT state, rerun the test a second time to check ACTIVE* state.

10 © ISO/IEC 2014 – All rights reserved
---------------------- Page: 12 ----------------------
Page 108, G.3.3.13.2
Add the following rows at the end of Table G.28:
Transition PICC-test-apparatus PICC FDT TTS
S(DESELECT) with wrong parity bit  PROTOCOL
DESELECT
(wrong parity bit)
 Mute
ISO/IEC 14443-4 I(0)0(TEST_COMMAND1(1))  PROTOCOL
command with wrong parity bit
(wrong parity bit)
 Mute
REQB  IDLE or
Type B command
PROTOCOL
 Mute
('93 20')  PROTOCOL
 Mute
Add the following table footnotes c and d in Table G.28:

The parity error is simulated on the first transmitted byte of the frame by reversing the parity bit.

Check first IDLE state as TTS. If TTS is not IDLE state, rerun the test a second time to check PROTOCOL state.

Page 109, G.3.4.2, Pseudocode
Add after line 5:
TPDUSend (SEL(c) 20)
if TPDURecv() ≠ (UIDTXc[[1..32]] BCC) then return FAIL
Page 112, G.3
Add the following subclauses:
"G.3.8 Handling of Frame Delay Time PICC to PCD
G.3.8.1 Scope

This test is to determine if the PICC Type A respects the minimum FDT according ISO/IEC14443-3:2011,

6.2.1 and SFGT according to ISO/IEC 14443-4:2008, 5.2.5.
G.3.8.2 Procedure

This procedure shall be repeated for two combinations of bit rates as described below:

 at a bit rate of fc/128 in both direction;
 at the maximum bit rates supported by PICC in each direction.
Perform the following steps for Scenario G.71 listed below:
a) Put the PICC into IDLE state.
b) For each step in the Scenario do:
© ISO/IEC 2014 – All rights reserved 11
---------------------- Page: 13 ----------------------

1) Send the command as described in the PICC-test-apparatus column respecting the timing condition

described in the Frame Delay Time PICC to PCD column.
2) Check that the PICC response matches the one of the PICC column.
c) End for.
12 © ISO/IEC 2014 – All rights reserved
---------------------- Page: 14 ----------------------
Scenario G.71: Handling of FDT and SFGT
Step Frame Delay Time PICC-test-apparatus PICC
PICC to PCD
- REQA 
 ATQA
(Minimum Frame 
Delay Time PICC to AC(1)
PCD + 50)/fc
 UIDTX BCC
SELECT(1) 
(1172 + 50)/fc
 SAK (cascade) or SAK
(complete)
(1172 + 50)/fc AC(2) 
 UIDTX BCC
SELECT(2) 
(1172 + 50)/fc
 SAK (cascade) or SAK
(complete)
AC(3) 
(1172 + 50)/fc
 UIDTX BCC
SELECT (3) 
(1172 + 50)/fc
 SAK (complete)
(1172 + 50)/fc RATS(0,0) 
 ATS
(1172 + 50)/fc if 
PPS(0,dri,dsi)
SFGI=0
 PPS response
SFGT+ 50/fc
I(0) (TEST_COMMAND1(1)) 
(1172 + 50)/fc 0

I(0) (TEST_RESPONSE1(1))
(1172 + 50)/fc I(0)1(TEST_COMMAND3) 
 S(WTX) (WTXM)
S(WTX) (WTXM) 
(1172 + 50)/fc

I(0)1(TEST_RESPONSE3)

The applied Frame Delay Time PICC to PCD between shall have a maximum tolerance of ± 25/fc

This step is sent only for PICC with UID size 2 and 3.
This step is sent only for PICC with UID size 3.

PPS request is sent for bit rate > fc/128. Configure PPS command with appropriate dsi and dri values.

S(WTX) request may be sent by the PICC. PICC-test-apparatus shall send acknowledge until receiving

the response with no specific requirement on Frame Delay Time PICC to PCD.

Additional S(WTX) request may be sent by the PICC. PICC-test-apparatus shall send acknowledge until receiving

the response with no specific requirement on Frame Delay Time PICC to PCD.
G.3.8.3 Test report
Fill the appropriate row in Table G.61 according to Table G.64.
© ISO/IEC 2014 – All rights reserved 13
---------------------- Page: 15 ----------------------
Table G.64 — Result criteria for handling of Frame Delay Time PICC to PCD
Explanation Test result
Only when the PICC responded as indicated in PASS
the procedure
Any other case FAIL
G.3.9 Scenario G.72: PICC bit rates capability
G.3.9.1 Scope

This test is to determine the behavior of a Type A PICC when receiving PCD messages according to ISO/IEC

14443-3:2011, 6.1 and 6.2.
G.3.9.2 Procedure

This procedure shall be repeated for combinations of PCD to PICC and PICC to PCD bit rates supported by

the PICC, so that all supported bit rates in each direction are used at least once during the tests.

a) Put the PICC into IDLE state.
b) Put the PICC in PROTOCOL state
c) Send the appropriate PPS command and check the PPS response.

d) Check that the PICC responses are valid. Record the presence, content and timing of the PICC

responses.

e) Send the I-block I(0)0(TEST_COMMAND1(1)). Record the presence, frame format, content and timing of

the PICC response.
f) Send the S(DESELECT) command.

g) Check that the PICC response is a valid S(DESELECT). Record the presence, frame format, content and

timing of the PICC response.
h) Send a WUPA command.

i) Check that the PICC response is a valid ATQA. Record the presence, frame format, content and timing of

the PICC response.
G.3.9.3 Test report

Report the measured timings in Table G.59 and fill the appropriate row in Table G.62 according to Table G.65.

Table G.65 — Result criteria for Scenario G.72: PICC Reception
Explanation Test result
Only when the PICC responded as indicated in PASS
the procedure
Any other case FAIL
14 © ISO/IEC 2014 – All rights reserved
---------------------- Page: 16 ----------------------
Page 113, G.4.3
Replace the original title:
G.4.3 Scenario G.22: PICC Reception
with the following modified title:
G.4.3 Scenario G.22: PICC framing and bit rates capability
Page 113, G.4.3.1
Replace the entire original Scope with the modified text:

This test is to determine the behavior of a Type B PICC when receiving PCD messages according to ISO/IEC

14443-3:2011, 7.1.
Page 113, G.4.3.2
Replace the entire original procedure with the modified text:
"G.4.3.2 Procedure

This procedure shall be repeated for combinations of PCD to PICC and PICC to PCD bit rates supported by

the PICC, so that all supported bit rates in each direction are used at least once during the tests.

Perform the following steps for each row of Table G.34:
a) Put the PICC into IDLE state.
b) Set the frame parameters of the PICC-test-apparatus according to Table G.34.
c) Send a REQB command

d) Check that the PICC response is a valid ATQB. Record the presence, frame format, content and timing of

the PICC response.
e) Send the ATTRIB(0, 0)

f) Check that the PICC response is a valid ATA. Record the presence, frame format, content and timing of

the PICC response.

g) Send the I-block I(0)0(TEST_COMMAND1(1)). Record the presence, frame format, content and timing of

the PICC response.
h) Send the S(DESELECT) command.

i) Check that the PICC response is a valid S(DESELECT). Record the presence, frame format, content and

timing of the PICC response.
j) Send a WUPB command.

k) Check that the PICC response is a valid ATQB. Record the presence, frame format, content and timing of

the PICC response."
© ISO/IEC 2014 – All rights reserved 15
---------------------- Page: 17 ----------------------
Page 114, G.4.3.3
Replace the existing Table G.34 with the modified table:
EGT SOF SOF EOF Minimum Minimum EOF SOF Framing Bit boundaries
low high TR0 TR1 handling handling options
Rising Falling
coding coding coding coding
edge edge
[etu] [etu] [etu] [etu]
[1/fc] [1/fc]
0 10,5 2,5 10,5 (00)b (00)b (0)b (0)b (00)b 0 0
0 10-1/16 2-1/8 10-1/16 (00)b (00)b (0)b (0)b (00)b 0 0
6 10-1/16 2-1/8 10-1/16 (00)b (00)b (0)b (0)b (00)b 0 0
0 11+1/8 2-1/8 10-1/16 (00)b (00)b (0)b (0)b (00)b 0 0
0 10-1/16 3+1/8 10-1/16 (00)b (00)b (0)b (0)b (00)b 0 0
6 11+1/8 3+1/8 11+1/8 (00)b (00)b (0)b (0)b (00)b 0 0
d e
0 10-1/16 2-1/8 10-1/16 (00)b (00)b (0)b (0)b (00)b -8 -8
f g
0 10-1/16 2-1/8 10-1/16 (00)b (00)b (0)b (0)b (00)b +8 +8
d g
0 10-1/16 2-1/8 10-1/16 (00)b (00)b (0)b (0)b (00)b -8 +8
f e
0 10-1/16 2-1/8 10-1/16 (00)b (00)b (0)b (0)b (00)b +8 -8
0 10,5 2,5 10,5 (00)b (01)b (0)b (0)b (00)b 0 0
0 10,5 2,5 10,5 (00)b (10)b (0)b (0)b (00)b 0 0
0 10,5 2,5 10,5 (01)b (00)b (0)b (0)b (00)b 0 0
0 10,5 2,5 10,5 (01)b (01)b (0)b (0)b (00)b 0 0
0 10,5 2,5 10,5 (01)b (10)b (0)b (0)b (00)b 0 0
0 10,5 2,5 10,5 (10)b (00)b (0)b (0)b (00)b 0 0
0 10,5 2,5 10,5 (10)b (01)b (0)b (0)b (00)b 0 0
0 10,5 2,5 10,5 (10)b (10)b (0)b (0)b (00)b 0 0
0 10,5 2,5 10,5 (00)b (00)b (0)b (1)b (00)b 0 0
0 10,5 2,5 10,5 (00)b (00)b (1)b (0)b (00)b 0 0
0 10,5 2,5 10,5 (00)b (00)b (1)b (1)b (00)b 0 0
0 10,5 2,5 10,5 (00)b (00)b (0)b (0)b (01)b 0 0
0 10,5 2,5 10,5 (00)b (00)b (0)b (0)b (10)b 0 0
Only applicable for bit rates fc/8, fc/4 and fc/2.

Bit boundaries is applied on b2 of the first byte of I-block I(0)0(TEST_COMMAND1(1)). For bit rates higher than fc/16

bit boundaries shall occur at nominal bit positions.
condition 1 defined in (to complete)
Not applicable for bit rate higher that fc/16
Apply -4 for fc/64, -2 for fc/32 and -1 for fc/16
Apply -1 for fc/6, fc/32 and for fc/16
Apply +4 for fc/64, +2 for fc/32 and +1 for fc/16
Apply +1 for fc/6, fc/32 and for fc/16
16 © ISO/IEC 2014 – All rights reserved
---------------------- Page: 18 ----------------------
Replace the original text:
"Fill the appropriate row in Table G.62 according to Table G.35."
with the modified text:

"Report the measured timings in Table G.60 and fill the appropriate row in Table G.62 according to Table

G.35"
Page 115, G.4.4.1.1
Add the following footnote a in line IDLE of table G.36:
IDLE state may be reached from READY-DECLARED state
Add the following row at the end of Table G.37:
REQB(1,nAFI) 
READY-DECLARED  IDLE
 Mute
Page 115, G.4.4.1.2
Add the following table footnote b on received ATQB in Table G.38:
if the PUPI is known, check that PUPI has not changed
Page 116, G.4.4.2.2
Replace the original step a):
"a) Put the PICC into IDLE state."
with the modified step a):

"a) Put the PICC into IDLE state. If the PUPI is unknown, put the PICC in READY-DECLARED state to

retrieve the PICC PUPI and put it in IDLE state."

Remove the table footnote b from Table G.39 and rename all other table footnotes.

© ISO/IEC 2014 – All rights reserved 17
---------------------- Page: 19 ----------------------
Page 118, G.4.4.3.2
Replace the original step a):
"a) Put the PICC into READY-REQUESTED state."
with the modified step a):

"a) Put the PICC into READY-REQUESTED state. If the PUPI is unknown, put the PICC in READY-

DECLARED state to retrieve the PICC PUPI and put it in IDLE state before performing the step a)."

Remove the table footnote b from Table G.41 and rename all other table footnotes.

Page 123, G.4.4.6.2
Add the following row at the end of Table G.47:
Transition PICC-test-apparatus PICC FDT TTS
 IDLE or
REQA
PROTOCOL
Type A command
 Mute
Add the following table footnote b in Table G.47:

Check first IDLE state as TTS. If TTS is not IDLE state, rerun the test a second time to check PROTOCOL state.

Page 127, G.4
Add the following subclauses:
"G.4.8 Handling of TR2
G.4.8.1 Scope

This test is to determine if the PICC Type B respects the minimum TR2 according ISO/IEC 14443-3:2011,

7.9.4.4.
G.4.8.2 Procedure

This procedure shall be repeated for two combinations of bit rates as described below:

 at a bit rate of fc/128 in both direction
 at the maximum bit rates supported by PICC in each direction
Perform the following steps of Scenario G.73 listed below:
a) Put the PICC into IDLE state.
b) For each step in the Scenario do:
18 © ISO/IEC 2014 – All rights reserved
---------------------- Page: 20 ----------------------

1) Send the command as described in the PICC-test-apparatus column respecting the timing condition

described in the TR2 column.
2) Check that the PICC response matches the one of the PICC column.
c) End for.
Scenario G.73: Handling of TR2
Step TR2 to apply PICC-test-apparatus PICC
- 
REQB(1)
 ATQB or Extended ATQB
Minimum ATTRIB(0,0) 
2 b,c
TR2+ 50/fc
 ATA(0)
Minimum I(0) (TEST_COMMAND1(1)) 
b,c
TR2+ 50/fc
SFGT+50/fc

I(0) (TEST_RESPONSE1(1))
Minimum I(0)1(TEST_COMMAND3) 
b,c
TR2+ 50/fc
 S(WTX) (WTXM)
Minimum S(WTX) (WTXM) 
b,c
TR2+ 50/fc

I(0)1(TEST_RESPONSE3)
bit 5 of PARAM is set to 1. PICC-test-apparatus supports the extended ATQB.
Minimum TR2 is set as given in the ATQB
The applied TR2 shall have a maximum tolerance of ± 25/fc
If the PICC has responded with extended ATQB

S(WTX) request may be sent by the PICC. PICC-test-apparatus shall send acknowledge until receiving

the response with no specific requirement on TR2.

Additional S(WTX) request may be sent by the PICC. PICC-test-apparatus shall send acknowledge until receiving

the response with no specific requirement on TR2
G.4.8.3 Test report
Fill the appropriate row in Table G.62 according to Table G.66.
Table G.66 — Result criteria for handling of TR2
Explanation Test result
Only when the PICC responded as indicated in PASS
the procedure
Any other case FAIL
© ISO/IEC 2014 – All rights reserved 19
---------------------- Page: 21 ----------------------
Page 132, G.5.2.2
Add the following text scenario G.74 after Scenario G.43 and before Scenario G
...

Questions, Comments and Discussion

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