ISO/IEC 23917:2005

Information technology — Telecommunications and information exchange between systems — NFCIP-1 — Protocol Test Methods

ISO/IEC 23917:2005 specifies protocol test methods for ISO/IEC 18092 in addition to those specified in ISO/IEC 22536.

Technologies de l'information — Télécommunications et échange d'information entre systèmes — NFCIP-1 — Méthodes d'essai du protocole

General Information

• Status: Withdrawn
• Publication Date: 02-Nov-2005
• ICS: 35.100.10 - Physical layer
• Technical Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Drafting Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 08-Dec-2023
• Completion Date: 30-Oct-2025

Relations

• Revised: ISO/IEC 23917:2023 - Telecommunications and information exchange between systems — Near Field Communication Interface and Protocol 1 (NFCIP-1) — Protocol test methods
• Effective Date: 23-Apr-2020

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 23917
First edition
2005-11-01
Information technology —
Telecommunications and information
exchange between systems — NFCIP-1 —
Protocol Test Methods
Technologies de l'information — Télécommunications et échange
d'information entre systèmes — NFCIP-1 — Méthodes d'essai du
protocole
Reference number
©
ISO/IEC 2005
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.

©  ISO/IEC 2005
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2005 – All rights reserved

Contents Page
Foreword.v
Introduction .vi
1 Scope.1
2 Conformance.1
3 Normative references.1
4 Notational conventions.1
4.1 Representation of numbers.1
4.2 Names.1
4.3 Test report.2
5 Terms and definitions .2
5.1 Activation in Active communication Mode.2
5.2 Activation in Passive communication Mode .2
5.3 Active communication Mode.2
5.4 Operating volume.2
5.5 Passive communication Mode .2
5.6 Single Device Detection (SDD).2
5.7 Scenario.2
5.8 Test commands .2
6 Acronyms and abbreviations .3
7 General description.5
7.1 Apparatus for Testing .5
7.1.1 Generating the I/O character timing in reception mode.5
7.1.2 Measuring and monitoring the RF I/O protocol.5
7.1.3 Test scenario and report.5
7.1.4 RFU bits.5
7.1.5 General rules.5
8 Target test methods .5
8.1 Apparatus for testing the Target (Target-test-apparatus).5
8.2 List of protocol test methods related to ISO/IEC 18092 .6
8.3 Activation in Passive communication Mode at 212 and 424 kbps .7
8.3.1 Activation time.7
8.3.2 Frame format.8
8.3.3 SDD at 212 and 424 kbps.8
8.4 Activation in Active communication Mode.9
8.4.1 RF Collision Avoidance .9
8.5 Logical operation of the Target Transport Protocol .10
8.5.1 Handling of ATR_REQ.10
8.5.2 Handling of PSL_REQ.11
8.5.3 Handling of DEP_REQ Information PDUs.13
8.5.4 Handling of DEP_REQ Information PDUs with the "more information" bit set to ONE .14
8.5.5 Handling of DEP_REQ supervisory PDU's with timeout bit set to ONE .19
8.5.6 Handling of DEP_REQ supervisory PDUs with timeout bit set to ZERO.20
8.5.7 Handling of DSL_REQ.21
8.5.8 Handling of RLS_REQ.22
8.5.9 Handling of WUP_REQ (Active communication Mode Only).24
9 Initiator test methods.26
9.1 Apparatus for testing the Initiator (Initiator-test-apparatus).26
9.1.1 Initiator test apparatus concept.26
© ISO/IEC 2005 – All rights reserved iii

9.1.2 Protocol activation procedure for Passive communication Mode at 106 kbps .26
9.1.3 Protocol activation procedures for Passive communication Mode at 212 and 424 kbps.27
9.1.4 Protocol activation procedures for Active communication Mode. 27
9.2 List of protocol test methods for Initiators . 27
9.3 Activation in Passive communication Mode at 212 and 424 kbps . 28
9.3.1 Frame format. 28
9.3.2 SDD at 212 and 424 kbps . 28
9.4 Activation in Active communication Mode . 29
9.4.1 Initial RF Collision Avoidance . 29
9.4.2 Response RF Collision Avoidance with time jitter n=0 . 29
9.5 Logical operation of the Transport Protocol . 30
9.5.1 Handling of ATR_RES . 30
9.5.2 Handling of PSL_RES. 31
9.5.3 Handling of DEP_RES Information PDUs. 32
9.5.4 Handling of DEP_RES Information PDU's with more information bit set to ONE. 34
9.5.5 Handling of DEP_RES supervisory PDU's with timeout bit set to ONE. 37
9.5.6 Handling of DEP_RES supervisory PDUs with timeout bit set to ZERO. 39
9.5.7 Handling of DSL_RES . 40
9.5.8 Handling of RLS_RES . 41
Annex A (normative) Test report template for Target tests. 43
Annex B (normative) Test report template for Initiator tests. 48
iv © ISO/IEC 2005 – All rights reserved

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.
ISO/IEC 23917 was prepared by Ecma International (as ECMA-362) and was adopted, under a special “fast-
track procedure”, by Joint Technical Committee ISO/IEC JTC 1, Information technology, in parallel with its
approval by national bodies of ISO and IEC.
© ISO/IEC 2005 – All rights reserved v

Introduction
In 2002, Ecma International formed Task Group 19 of Technical Committee 32 to specify Near Field
Communication (NFC) signal interfaces and protocols. The NFC devices are wireless closely coupled
devices communicating at 13,56 MHz.
The General Assembly of December 2002 adopted Near Field Communication Interface and Protocol-1
(NFCIP-1) as Standard ECMA-340 (ISO/IEC 18092).
This International Standard specifies protocol tests for ECMA-340 (ISO/IEC 18092) and complements
ECMA-356 (ISO/IEC 22536), which specifies the RF interface tests for ECMA-340 (ISO/IEC 18092).
vi © ISO/IEC 2005 – All rights reserved

INTERNATIONAL STANDARD ISO/IEC 23917:2005(E)
Information technology — Telecommunications and information
exchange between systems — NFCIP-1 — Protocol Test
Methods
1 Scope
This International Standard specifies protocol test methods for ISO/IEC 18092 in addition to those specified in
ISO/IEC 22536.
2 Conformance
In addition to conforming to ISO/IEC 22536, implementations of ISO/IEC 18092 shall pass all normative tests
and requirements specified herein; test results shall be recorded using Annex A and Annex B of this
International Standard.
3 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO/IEC 10373-6:2001, Identification cards — Test methods — Part 6: Proximity cards
ISO/IEC 18092:2004, Information technology — Telecommunications and information exchange between
systems — Near Field Communication — Interface and Protocol (NFCIP-1)
ISO/IEC 22536:2005, Information technology — Telecommunications and information exchange between
systems — NFCIP-1 - RF interface test methods
4 Notational conventions
4.1  Representation of numbers
The following conventions and notations apply in this document unless otherwise stated.
x Letters and digits in parentheses represent numbers in hexadecimal notation.
x The setting of bits is denoted by ZERO or ONE.
x Numbers in binary notation and bit patterns are represented by strings of digits 0 and 1 shown with the
most significant bit to the left. Within such strings, X may be used to indicate that the setting of a bit is not
specified within the string.
4.2  Names
The names of basic elements, e.g. specific fields, are written with a capital initial letter.
© ISO/IEC 2005 – All rights reserved 1

4.3  Test report
The test report includes the number of passed tests versus the total number of tests, the number of different
samples and the date of the tests, see Annexes A and B.
5 Terms and definitions
For the purposes of this document, the following terms and definitions apply
5.1
Activation in Active communication Mode
flow to activate the DUT in Active communication Mode as defined in ISO/IEC 18092, which includes
initialisation and protocol activation.
5.2
Activation in Passive communication Mode
flow to activate the DUT in Passive communication Mode as defined in ISO/IEC 18092, which includes
initialisation and protocol activation.
5.3
Active communication Mode
in the Active communication Mode scheme, as defined in ISO/IEC 18092, both the Initiator and the Target use
their own RF field to enable the communication.
5.4
Operating volume
a volume with a field strength of at least H and not exceeding H generated by a NFC device at
min max
manufacturer specified positions.
5.5
Passive communication Mode
the Initiator is generating the RF field and the Target responds to an Initiator command in a load modulation
scheme as defined in ISO/IEC 18092.
5.6
Single Device Detection (SDD)
SDD is an algorithm used by the initiator to detect one out of several Targets in its RF field.
5.7
Scenario
a scenario is a protocol and application specific sequence test operations. Scenario description tables list all
individual test operations.
A horizontal line in a scenario description table indicates that the device shall be reset to initial conditions.
5.8
Test commands
Commands defined for dedicated functional behaviour on an implemented system according to
ISO/IEC 18092. The PDUs that are actually used in these commands shall be recorded in the test report (see
Annex A and Annex B).
Definitions valid for all test commands:
xx PNI
2 © ISO/IEC 2005 – All rights reserved

The following test commands are specified based on PDUs specified in ISO/IEC 18092:
A(ACK) DEP_REQ or DEP_RES PDU coded as ACK/NACK PDU with ACK/NACK bit set to
xx
ZERO and PNI set to xx.
A(NACK) DEP_REQ or DEP_RES PDU coded as ACK/NACK PDU with ACK/NACK bit set to
xx
ONE and PNI set to xx.
S(A) DEP_REQ or DEP_RES PDU coded as Supervisory PDU (as defined in
ISO/IEC 18092) with the Timeout bit set to ZERO. No PNI is used for this command.
S(TO) DEP_REQ or DEP_RES PDU coded as Supervisory PDU (as defined in
ISO/IEC 18092) with the Timeout bit set to ONE. No PNI is used for this command.
TEST_COMMAND1 Default Test command, it is a DEP_REQ frame coded as information PDU with
xx
"More Information" bit set to ZERO (no chaining) and the PNI set to xx. The Initiator
or the target-test-apparatus sends this PDU.
TEST_RESPONSE1 Response to TEST_COMMAND1 (DEP_RES) with the PNI set to xx.
xx
TEST_COMMAND2 Test command used for tests of the chaining procedure. This command forces the
xx
counterpart (either Initiator or Target) to use chaining in the next DEP_REQ. This
command is a DEP_REQ or DEP_RES frame, for an Initiator or Target respectively,
with its "More Information" bit set to ZERO and it uses the same PDU as
TEST_COMMAND1, but this PDU has different data.
TEST_COMMAND3B This command marks the beginning of a DEP_REQ or DEP_RES frame, for an
xx
Initiator or Target respectively, with its "More Information" bit set to ONE and the PNI
set to xx.
TEST_COMMAND3n This command is sent after TEST_COMMAND3B and before TEST_COMMAND3E.
xx
The lower case n represents a number ranging from 0 to 9. This command has the
"More Information" bit set to ONE and the PNI set to xx.
TEST_COMMAND3E This command marks the end of the chaining procedure and is a DEP_REQ or
xx
DEP_RES frame, for an Initiator or Target respectively, with the "More Information"
bit set to ZERO and the PNI set to xx.
TEST_RESPONSE3 is the response to the chaining command. Shall be a DEP_REQ or DEP_RES frame,
xx
for an Initiator or Target respectively, with the "More Information" bit set to ZERO
and the PNI set to xx.
TEST_COMMAND4 Test command used for tests dealing with frame waiting time. The Initiator sends
xx
this command and forces the Target to use a Supervisory PDU with the timeout bit
set to ONE and the PNI set to xx.
TEST_RESPONSE4 is the response to TEST_COMMAND4. It is a DEP_RES with the "More Information"
xx
bit set to ZERO and the PNI set to xx. It may be the same as TEST_RESPONSE1.
6 Acronyms and abbreviations
ATR_REQ ATtribute Request command as defined in ISO/IEC 18092
ATR_RES Response to the ATR_REQ
CRC Cyclic Redundancy Check as defined in Annex A of ISO/IEC 18092
~CRC CRC as defined above with all bits inverted
© ISO/IEC 2005 – All rights reserved 3

DEP_REQ Data Exchange Protocol Request as defined in ISO/IEC 18092
DEP_RES Response to the Data Exchange Protocol Request
DID Device ID as defined in ISO/IEC 18092
DSL_REQ DeSeLect Request command as defined in ISO/IEC 18092
DSL_RES Response to the DSL_REQ
DUT Device Under Test
fc Frequency of operating field (carrier frequency) as defined in ISO/IEC 18092
Hmax Maximum field strength of the Initiator antenna field as defined in ISO/IEC 18092
Hmin Minimum field strength of the Initiator antenna field as defined in ISO/IEC 18092
HThreshold Defined in ISO/IEC 18092
ID Identification number
LT Lower Tester the Target-emulation part of the Initiator-Test-apparatus
Mute No response within a specified timeout
PDU Protocol Data Unit as defined in ISO/IEC 18092
PNI Package Number Information as defined in ISO/IEC 18092
POL_REQ POlling Request command as defined in ISO/IEC 18092
POL_RES Response to the Polling Request
PSL_REQ Parameter SeLect Request command as defined in ISO/IEC 18092
PSL_RES Response to the PSL_REQ
RF Radio Frequency
RFU Reserved for Future Use
RLS_REQ ReLease Request command as defined in ISO/IEC 18092
RLS_RES Response to the RLS_REQ
RTO PDU Response TimeOut extension as specified in ISO/IEC 18092 clause 12.6.1.3.3 and 12.6.2
SDD Single Device Detection as defined in ISO/IEC 18092
Td The delay between the end of the Request frame and the start of the first time slot for SDD
at 212 and 424 kbps (equals 512 × 64/fc)
Ts The period of one time slot (equals 256 × 64/fc)
TCM Test controlmessage
UT Upper Tester, the master part of the Initiator-Test-apparatus
4 © ISO/IEC 2005 – All rights reserved

7 General description
7.1  Apparatus for Testing
NOTE The test-apparatus may require information about the implemented protocol and functionality. These
parameters shall be recorded in the test report.
This clause is valid for Initiator and Target tests.
Although this International Standard does not define dedicated test circuit for timing measurements and to
check the correctness of the framing, influence of such circuit shall be avoided.
7.1.1 Generating the I/O character timing in reception mode
The target-test-apparatus and the LT shall be able to generate the I/O bit stream according to ISO/IEC 18092.
All timing parameters (e.g. start bit length, guard time, bit width, request guard time, start of frame width, end
of frame width) shall be set to any value within the defined ranges of ISO/IEC 18092. The limits shall be tested
according ISO/IEC 22536.
7.1.2 Measuring and monitoring the RF I/O protocol
The targe-test-apparatus and the LT shall be able to measure the timing of the logical low and high states of
the incoming demodulated data.
7.1.3 Test scenario and report
Testing of the DUT as defined in this document and requires a test scenario to be executed. This test scenario
contains a protocol and application specific sequence.
The result of the test scenario shall be documented in a test report as defined in Annexes A and B.
7.1.4 RFU bits
A test shall fail and the DUT declared non-compliant in case an RFU field is not set to its default value.
7.1.5 General rules
The following rules apply:
An Initiator (Target test apparatus) always sends a request whereas a Target (LT) sends a response.
A response must follow a request.
If the PNIs for the TEST_RESPONSEn and TEST_COMMANDn are the same, then TEST_COMMANDn is
correct.
8 Target test methods
The DUT shall answer as specified in the scenarios, optionally inserting one or more RTO PDUs before
responding with the PDU as specified in the scenarios.
8.1  Apparatus for testing the Target (Target-test-apparatus)
The Target-test-apparatus tests the DUT by emulating an Initiator.
© ISO/IEC 2005 – All rights reserved 5

The Target-test-apparatus shall execute the initialisation and protocol activation and perform data exchange
commands.
8.2  List of protocol test methods related to ISO/IEC 18092
To test Targets performing initialisation and SDD in Passive communication Mode at 106 kbps the PICC test
methods of ISO/IEC 10373-6 must be executed.
To test Targets performing initialisation and SDD in Passive communication Mode at 212 and 424 kbps the
test methods listed in table 1 must be executed.
Table 1 — Activation in Passive communication Mode at 212 and 424 kbps
Test method Corresponding requirement
Clause Name Base standard Clause(s)
8.3.1 Activation time ISO/IEC 18092 11.2.2.3
8.3.2 Frame format ISO/IEC 18092 11.2.2.2
8.3.3 SDD at 212 and 424 kbps ISO/IEC 18092 11.2.2.3
11.2.2.4
To test Targets performing initialisation in Active communication Mode the test method in table 2 must be
executed.
Table 2 — Activation in Active communication Mode
Test method Corresponding requirement
Clause Name Base standard Clause(s)
8.4.1 RF Collision Avoidance ISO/IEC 18092 11.1.2
To test Targets using the transport protocol the test methods listed in table 3 must be executed.
6 © ISO/IEC 2005 – All rights reserved

Table 3 — Logical operation of the Transport Protocol
Test method Corresponding requirement
Clause Name Base standard Clause(s)
8.5.1 Handling of ATR_REQ ISO/IEC 18092 12.5.1.3
8.5.2 Handling of PSL_REQ ISO/IEC 18092 12.5.3.3
8.5.3 Handling of DEP_REQ Information PDUs ISO/IEC 18092 12.6.1.2
8.5.4 Handling of DEP_REQ Information PDUs ISO/IEC 18092 12.6.1.3
with the "more information" bit set to ONE
8.5.5 Handling of DEP_REQ supervisory PDUs ISO/IEC 18092 12.6.1.3
with timeout bit set to ONE
8.5.6 Handling of DEP_REQ supervisory PDU's ISO/IEC 18092 12.6.1.3
with timeout bit set to ZERO
8.5.7 Handling of DSL_REQ ISO/IEC 18092 12.7.1.3
8.5.8 Handling of RLS_REQ ISO/IEC 18092 12.7.2.3
8.3  Activation in Passive communication Mode at 212 and 424 kbps
8.3.1 Activation time
The purpose of this test is to verify that the Target responds with to a POL_REQ with a POL_RES within two
seconds after power up (see ISO/IEC 18092 clause 11.2.2.3).
8.3.1.1 Procedure
Repeat steps a) to e) for the data rates of 212 and 424 kbps.
a) Place the DUT into the operating volume.
b) Generate an RF-field between the limits H and H and verify that the field strength does not influence
min max
the test results.
c) Send a POL_REQ command frame with TSN is set to 0 at the selected data rate.
d) If there is no POL_RES received after T and T are passed send the POL_REQ again. Repeat this step
d s
until a response from the DUT is received.
st
e) Measure the timing between RF-on and the beginning of the 1 response of the DUT. If the DUT
responds in less than two seconds, the test is PASS otherwise it is FAIL.
8.3.1.2 Test report
The test report shall indicate whether the DUT behaves correctly for both data rates.
© ISO/IEC 2005 – All rights reserved 7

8.3.2 Frame format
The purpose of this test is to determine the frame formats at 212 and 424 kbps are correct (see
ISO/IEC 18092 clause 11.2.2.2).
8.3.2.1 Procedure
Repeat steps a) to d) for the data rates of 212 and 424 kbps.
a) Place the DUT into the operating volume.
b) Generate an RF-field between the limits H and H and verify that the field strength does not influence
min max
the test results.
c) Send the POL_REQ command frame at the selected data rate.
d) Verify the correct framing of the response from the DUT.
8.3.2.2 Test report
The test report shall indicate whether the DUT behaves correctly for both data rates and shall include results
for the following characteristics:
Characteristic Expected result
Preamble minimum 48 bits all
logical ZEROs
SYNC 1st byte is ´B2´
nd
2 byte is ´4D´
value of the length byte ´12´
CRC bytes according to ISO/IEC
18092, Annex A
8.3.3 SDD at 212 and 424 kbps
The purpose of this test is to determine the correct response to the POL_REQ (see ISO/IEC 18092 clause
11.2.2.4).
8.3.3.1 Procedure
Repeat steps a) to f) for the data rates of 212 and 424 kbps.
a) Place the DUT into the operating volume.
b) Generate an RF-field between the limits H and H and verify that the field strength does not influence
min max
the test results.
c) Send a POL_REQ command frame with TSN is set to 0 at the selected data rate.
d) Record the time between POL_REQ and POL_RES. If the DUT does not respond in the last time slot
available repeat step c).
8 © ISO/IEC 2005 – All rights reserved

e) Analyse the content of the response.
f) Increase the TSN to the next allowed value and repeat step a) to e) until the maximum TSN value is
reached.
8.3.3.2 Test report
The test report shall indicate whether the DUT behaves correctly for both data rates and shall include results
for the following characteristics:
Characteristic Expected result
1st byte of the payload ´01´
2nd byte of the payload ´01´
3rd byte of the payload ´FE´
time between end of POL_REQ T + (TSN + 1) * T
d s
and end of POL_RES
8.4  Activation in Active communication Mode
8.4.1 RF Collision Avoidance
The purpose of this test is to determine the behaviour of the DUT in Active communication Mode during RF
Collision Avoidance (see ISO/IEC 18092 clause 11.1.2).
8.4.1.1 Procedure
Repeat steps a) to e) for the data rates of 106, 212 and 424 kbps.
a) Place the DUT into the operating volume.
b) Generate an RF-field between the limits H and H and verify that the field strength does not influence
min max
the test results.
c) Send a valid ATR_REQ command frame at the selected data rate and switch off the RF afterwards.
d) Measure the time between RF-off of the Target test-apparatus and RF-on of the DUT.
e) Repeat steps a) to d) until all randomly generated number of time periods are met and count the number
of retries necessary.
8.4.1.2 Test report
The test report shall indicate whether the DUT behaves correctly for all data rates.
© ISO/IEC 2005 – All rights reserved 9

Characteristic Expected result
T minimum 768/f
ADT c
maximum 2559/f
c
T n times 512/f
RFW c
8.5  Logical operation of the Target Transport Protocol
8.5.1 Handling of ATR_REQ
The purpose of this test is to determine the correct handling of the ATR_REQ of the DUT (see ISO/IEC 18092
clause 12.5.1.3.2).
8.5.1.1 Procedure
Repeat steps a) to e) for the data rates of 106, 212 and 424 kbps and for both Active and Passive
communication Modes.
a) Place the DUT into the operating volume.
b) Generate an RF-field between the limits H and H and verify that the field strength does not influence
min max
the test results.
c) Perform activation selected according at the selected data rate and follow the rules for Collision avoidance
in Active communication mode.
d) Apply the test scenario T 1.
e) Analyse if the response from the DUT are according to scenario T 1.
10 © ISO/IEC 2005 – All rights reserved

Scenario T 1 — ATR_REQ
Target-test-apparatus DUT
TEST_COMMAND1
o
Mute
m
ATR_REQ
o
ATR_RES
m
ATR_REQ
o
ATR_RES
m
ATR_REQ (~CRC)
o
Mute
m
ATR_REQ
o
ATR_RES
m
TEST_COMMAND1
00 o
TEST_RESPONSE1
m 00
ATR_REQ
o
Mute
m
TEST_COMMAND1
01 o
TEST_RESPONSE1
m 01
8.5.1.2 Test report
The test report shall indicate whether the DUT behaves correctly for all data rates and communication modes.
8.5.2 Handling of PSL_REQ
The purpose of this test is to determine the correct PSL handling of the DUT (see ISO/IEC 18092 clause
12.5.3.3.2).
8.5.2.1 Procedure
Repeat steps a) to f) for the data rates of 106, 212 and 424 kbps and for both Active and Passive
communication Modes.
a) Place the DUT into the operating volume.
b) Turn on a field between the limits H and H and verify that the field strength does not influence the
min max
test results.
c) Perform initialisation and protocol activation in the selected communication mode and data rate.
© ISO/IEC 2005 – All rights reserved 11

d) Send an ATR_REQ and receive ATR_RES.
e) Apply the test scenario T 2.
f) Check the response from the DUT is according to scenario T 2.
Scenario T 2 — PSL_REQ
Target-test-apparatus DUT
PSL_REQ
o
PSL_RES
m
PSL_REQ
o
Mute
m
TEST_COMMAND1
00 o
TEST_RESPONSE1
m
PSL_REQ (~CRC)
o
Mute
m
PSL_REQ
o
Mute
m
TEST_COMMAND1
00 o
TEST_RESPONSE1
m 00
TEST_COMMAND1
00 o
TEST_RESPONSE1
m 00
PSL_REQ
o
Mute
m
TEST_COMMAND1
o
TEST_RESPONSE1
m 01
8.5.2.2 Test report
The test report shall indicate whether the DUT behaves correctly for all data rates and communication modes.
12 © ISO/IEC 2005 – All rights reserved

8.5.3 Handling of DEP_REQ Information PDUs
The purpose of this test is to determine the correct handling of the DEP_REQ information PDU of the DUT
(see ISO/IEC 18092 clause 12.6.1.3).
8.5.3.1 Procedure
Repeat steps a) to f) for the data rates of 106, 212 and 424 kbps and for both Active and Passive
communication Modes.
a) Place the DUT into the operating volume.
b) Turn on a field between the limits H and H and verify that the field strength does not influence the
min max
test results.
c) Perform activation in the selected communication mode and data rate.
d) Send an ATR_REQ and receive the ATR_RES from the DUT.
e) Execute scenario T 3 followed by scenario T 4.
f) Check if the response and the PNIs from the DUT are according to the scenarios.
Scenario T 3 — DEP_REQ information PDU, correct transaction
Target-test-apparatus DUT
TEST_COMMAND1
00 o
TEST_RESPONSE1
m 00
TEST_COMMAND1
01 o
TEST_RESPONSE1
m 01
TEST_COMMAND1
10 o
TEST_RESPONSE1
m 10
TEST_COMMAND1
o
TEST_RESPONSE1
m 11
© ISO/IEC 2005 – All rights reserved 13

Scenario T 4 — DEP_REQ information PDU, erroneous transaction
Target-test-apparatus DUT
TEST_COMMAND1 (~CRC)
o
Mute
m
S(A)
o
S(A)
m
TEST_COMMAND1
o
TEST_RESPONSE1
m 00
TEST_COMMAND1
o
TEST_RESPONSE1
m 01
TEST_COMMAND1
o
TEST_RESPONSE1
m 00
TEST_COMMAND1 (~CRC)
01 o
Mute
m
S(A)
o
S(A)
m
TEST_COMMAND1
01 o
TEST_RESPONSE1
m 01
8.5.3.2 Test report
The test report shall indicate whether the DUT behaves correctly for all data rates and communication modes
for both scenarios.
8.5.4 Handling of DEP_REQ Information PDUs with the "more information" bit set to ONE
The purpose of this test is to determine the correct handling of the DEP_REQ information PDU with the "more
information" bit set to ONE (see ISO/IEC 18092 clause 12.6.1.3).
8.5.4.1 Procedure
Repeat steps a) to f) for the data rates of 106, 212 and 424 kbps and for both Active and Passive
communication Modes.
a) Place the DUT into the operating volume.
b) Turn on a field between the limits H and H and verify that the field strength does not influence the
min max
test results.
14 © ISO/IEC 2005 – All rights reserved

c) Perform activation in the selected communication mode and data rate.
d) Send an ATR_REQ and receive the ATR_RES from the DUT.
e) Execute scenario T 5 followed scenario T 6.
f) Check if the response and the PNIs from the DUT are according to the test scenarios.
Scenario T 5 — DEP_REQ information PDU with more information bit set; correct transaction
Target-test-apparatus DUT
TEST_COMMAND1
o
TEST_RESPONSE1
m 00
TEST_COMMAND3B
o
A(ACK)
m 01
TEST_COMMAND3E
o
TEST_RESPONSE3
m 10
TEST_COMMAND1
o
TEST_RESPONSE1
m 11
© ISO/IEC 2005 – All rights reserved 15

TEST_COMMAND1
00 o
TEST_RESPONSE1
m 00
TEST_COMMAND3B
01 o
A(ACK)
m 01
TEST_COMMAND30
o
A(ACK)
m 10
TEST_COMMAND31
o
A(ACK)
m 11
TEST_COMMAND32
o
A(ACK)
m 00
TEST_COMMAND33
o
A(ACK)
m 01
TEST_COMMAND3E
10 o
TEST_RESPONSE3
m 10
TEST_COMMAND1
o
TEST_RESPONSE1
m 11
TEST_COMMAND1
o
TEST_RESPONSE1
m 00
TEST_COMMAND2
01 o
TEST_COMMAND3B
m
A(ACK)
10 o
TEST_ COMMAND3E
m
TEST_COMMAND1
11 o
TEST_RESPONSE1
m
The following test case depends on the behaviour of the DUT and is therefore optional.
16 © ISO/IEC 2005 – All rights reserved

TEST_COMMAND1
o
TEST_RESPONSE1
m 00
TEST_COMMAND2
01 o
TEST_COMMAND3B
m 01
A(ACK)
o
TEST_ COMMAND30
m 10
A(ACK)
o
TEST_ COMMAND31
m 11
A(ACK)
o
TEST_ COMMAND32
m 00
A(ACK)
o
TEST_ COMMAND33
m 01
A(ACK)
10 o
TEST_ COMMAND3E
m 10
TEST_COMMAND1
11 o
TEST_RESPONSE1
m 11
© ISO/IEC 2005 – All rights reserved 17

Scenario T 6 — DEP_REQ information PDU with more information bit set, erroneous transaction
Target-test-apparatus DUT
TEST_COMMAND1
o
TEST_RESPONSE1
m 00
TEST_COMMAND3B
o
A(ACK)
m 01
TEST_COMMAND30 (~CRC)
o
Mute
m
S(A)
o
S(A)
m
TEST_COMMAND30
o
A(ACK)
m 10
TEST_COMMAND3E
11 o
TEST_RESPONSE3
m 11
TEST_COMMAND1
o
TEST_RESPONSE1
m 00
TEST_COMMAND1
o
TEST_RESPONSE1
m 00
TEST_COMMAND2
01 o
TEST_COMMAND3B
m 01
A(ACK) (~CRC)
10 o
Mute
m
S(A)
o
S(A)
m
A(ACK)
10 o
TEST_RESPONSE3E
m
TEST_COMMAND1
11 o
TEST_RESPONSE1
m
18 © ISO/IEC 2005 – All rights reserved

8.5.4.2 Test report
The test report shall indicate whether the DUT behaves correctly for all data rates and communication modes.
8.5.5 Handling of DEP_REQ supervisory PDU's with timeout bit set to ONE
The purpose of this test is to determine the correct handling of the DEP_REQ with supervisory PDU with
timeout bit set to ONE (see ISO/IEC 18092 clause 12.6.1.3).
8.5.5.1 Procedure
Repeat steps a) to f) for the data rates of 106, 212 and 424 kbps and for both Active and Passive
communication Modes.
a) Place the DUT into the operating volume.
b) Turn on a field between the limits H and H and verify that the field strength does not influence the
min max
test results.
c) Perform activation in the selected communication mode and data rate.
d) Send an ATR_REQ and receive the ATR_RES from the DUT.
e) Execute scenario T 7 followed by scenario T 8.
f) Check if the response and the PNIs from the DUT are according to scenarios.
Scenario T 7 — DEP_REQ supervisory PDU with timeout bit set to ONE; correct transaction
Target-test-apparatus DUT
TEST_COMMAND1
o
TEST_RESPONSE1
m 00
TEST_COMMAND4
01 o
S(TO)
m
S(TO)
o
TEST_RESPONSE4
m 01
TEST_COMMAND1
o
TEST_RESPONSE1
m 10
© ISO/IEC 2005 – All rights reserved 19

Scenario T 8 — DEP_REQ supervisory PDU, timeout bit set, erroneous transaction
Target-test-apparatus DUT
TEST_COMMAND1
o
TEST_RESPONSE1
m 00
TEST_COMMAND4
o
S(TO)
m
S(TO) (~CRC)
o
Mute
m
S(A)
o
S(A)
m
S(TO)
o
TEST_RESPONSE4
m 01
TEST_COMMAND1
o
TEST_RESPONSE1
m 10
8.5.5.2 Test report
The test report shall indicate whether the DUT behaves correctly for all data rates and both communication
modes
8.5.6 Handling of DEP_REQ supervisory PDUs with timeout bit set to ZERO
The purpose of this test is to determine the correct handling of the DEP_REQ supervisory PDU with the
timeout bit set to ZERO (see ISO/IEC 18092 clause 12.6.1.3).
8.5.6.1 Procedure
Repeat steps a) to f) for the data rates of 106, 212 and 424 kbps and for both Active and Passive
communication Modes.
a) Place the DUT into the operating volume.
b) Turn on a field between the limits H and H and verify that the field strength does not influence the
min max
test results.
c) Perform activation in the selected communication mode and data rate.
d) Send an ATR_REQ and receive the ATR_RES from the DUT.
e) Execute scenario T 9 followed by scenario T 10.
f) Check if the response and the PNIs from the DUT are according to the scenarios.
20 © ISO/IEC 2005 – All rights reserved

Scenario T 9 — DEP_REQ supervisory PDU, timeout bit not set to ZERO, correct transaction
Target-test-apparatus DUT
TEST_COMMAND1
o
TEST_RESPONSE1
m 00
S(A)
o
S(A)
m
TEST_COMMAND1
o
TEST_RESPONSE1
m 01
Scenario T 10 — DEP_REQ supervisory PDU, timeout bit not set to ZERO, erroneous transaction
Target-test-apparatus DUT
TEST_COMMAND1
00 o
TEST_RESPONSE1
m 00
S(A) (~CRC)
o
Mute
m
S(A)
o
S(A)
m
TEST_COMMAND1
01 o
TEST_RESPONSE1
m 01
8.5.6.2 Test report
The test report shall indicate whether the DUT behaves correctly for all data rates and communication modes.
8.5.7 Handling of DSL_REQ
The purpose of this test is to determine the correct handling of the DSL_REQ (see ISO/IEC 18092 clause
12.7.1.3).
8.5.7.1 Procedure
Repeat steps a) to f) for the data rates of 106, 212 and 424 kbps and for both Active and Passive
communication Modes.
a) Place the DUT into the operating volume.
b) Turn on a field between the limits H and H and verify that the field strength does not influence the
min max
test results.
© ISO/IEC 2005 – All rights reserved 21

c) Perform activation in the selected communication mode and data rate.
d) Send an ATR_REQ and receive the ATR_RES from the DUT.
e) Execute scenario T 11 followed scenario T 12.
f) Check if the response and the PNIs from the DUT are according to the scenarios.
Scenario T 11 — DSL_REQ, correct transaction
Target-test-apparatus DUT
TEST_COMMAND1
o
TEST_RESPONSE1
m 00
DSL_REQ
o
DSL_RES
m
DSL_REQ
o
Mute
m
Scenario T 12 — DSL_REQ, erroneous transaction
Target-test-apparatus DUT
TEST_COMMAND1
00 o
TEST_RESPONSE1
m 00
DSL_REQ (~CRC)
o
Mute
m
DSL_REQ
o
DSL_RES
m
8.5.7.2 Test report
The test report shall indicate whether the DUT behaves correctly for all data rates and communication modes.
8.5.8 Handling of RLS_REQ
The purpose of this test is to determine the correct handling of the RLS_REQ of the DUT (see ISO/IEC 18092
clause 12.7.2.3).
8.5.8.1 Procedure
Repeat steps a) to h) for the data rates of 106, 212 and 424 kbps and for both Active and Passive
communication Modes.
22 © ISO/IEC 2005 – All rights reserved

a) Place the DUT into the operating volume.
b) Turn on a field between the limits H and H and verify that the field strength does not influence the
min max
test results.
c) Perform activation in the selected communication mode and data rate.
d) Send an ATR_REQ and receive the ATR_RES from the DUT.
e) Execute scenario T 13 followed scenario T 14.
f) Check if the response and the PNIs from the DUT are according to the scenarios.
...