ISO/IEC 23917:2023
(Main)Telecommunications and information exchange between systems — Near Field Communication Interface and Protocol 1 (NFCIP-1) — Protocol test methods
Telecommunications and information exchange between systems — Near Field Communication Interface and Protocol 1 (NFCIP-1) — Protocol test methods
This document specifies protocol test methods for Near Field Communication Interface and Protocol 1 (NFCIP-1), as defined in ISO/IEC 18092 (the base standard). The radio frequency (RF) test methods for NFCIP-1 (also defined in ISO/IEC 18092) are specified in ISO/IEC 22536.
Télécommunications et échange d'information entre systèmes — Interface et protocole 1 de communication en champ proche (NFCIP-1) — Méthodes d'essai du protocole
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 23917
Second edition
2023-12
Telecommunications and information
exchange between systems — Near
Field Communication Interface and
Protocol 1 (NFCIP-1) — Protocol test
methods
Télécommunications et échange d'information entre systèmes —
Interface et protocole 1 de communication en champ proche
(NFCIP-1) — Méthodes d'essai du protocole
Reference number
© ISO/IEC 2023
© ISO/IEC 2023
All rights reserved. Unless otherwise specified, or required in the context of its implementation, 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
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
© ISO/IEC 2023 – All rights reserved
Contents Page
Foreword .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Symbols and abbreviated terms.2
5 Notational conventions . 4
5.1 Representation of numbers . 4
5.2 Names . 4
5.3 Test report . 4
6 Conformance . 4
7 Apparatus for testing . 4
7.1 General . 4
7.2 Generating the I/O character timing in reception mode . 4
7.3 Measuring and monitoring the RF I/O protocol . 4
7.4 Test scenario and report . 5
7.5 RFU bits . 6
7.6 General rules . 6
8 Target test methods . .6
8.1 General . 6
8.2 Apparatus for testing the Target (Target-test-apparatus) . 6
8.3 List of protocol test methods related to ISO/IEC 18092. 6
8.4 Activation in Passive communication mode at f /128 . 7
c
8.4.1 SDD for transport protocol activation . 7
8.5 Activation in Passive communication mode at f /64 and f /32 . 8
c c
8.5.1 Activation time. 8
8.5.2 Frame format . 8
8.5.3 SDD timing . 9
8.5.4 SDD for transport protocol activation . 9
8.6 Activation in Active communication mode . 10
8.6.1 RFCA . 10
8.7 Logical operation of the Target Transport Protocol . 11
8.7.1 Handling of ATR_REQ . 11
8.7.2 Handling of PSL_REQ .12
8.7.3 Handling of DEP_REQ Information PDUs .13
8.7.4 Handling of DEP_REQ Information PDUs with chaining Initiator to Target
and Target to Initiator . 15
8.7.5 Handling of DEP_REQ supervisory PDUs with timeout bit set to ONE . 17
8.7.6 Handling of DEP_REQ supervisory PDUs with timeout bit set to ZERO . 19
8.7.7 Handling of DSL_REQ .20
8.7.8 Handling of RLS_REQ . 21
8.7.9 Handling of WUP_REQ (Active communication mode only) .22
9 Initiator test methods .23
9.1 Apparatus for testing the Initiator (Initiator-test-apparatus) . 23
9.1.1 Initiator-test-apparatus concept . 23
9.1.2 Protocol activation procedure for Passive communication mode at f /128 . 24
c
9.1.3 Protocol activation procedures for Passive communication mode at f /64
c
and f /32 . 24
c
9.1.4 Protocol activation procedures for Active communication mode . 24
9.2 List of protocol test methods for Initiators . 24
9.3 Activation in Passive communication mode at f /128 . 26
c
9.3.1 Initial RFCA .26
iii
© ISO/IEC 2023 – All rights reserved
9.3.2 SDD for transport protocol activation . 26
9.4 Activation in Passive communication mode at f /64 and f /32 . 27
c c
9.4.1 Initial RFCA . 27
9.4.2 Frame format . 27
9.4.3 SDD for transport protocol activation .28
9.5 Activation in Active communication mode .28
9.5.1 Initial RFCA .28
9.5.2 Response RFCA with time jitter n=0 .29
9.6 Logical operation of the Transport Protocol .29
9.6.1 Handling of ATR_RES .29
9.6.2 Handling of PSL_RES.30
9.6.3 Handling of DEP_RES Information PDUs . 31
9.6.4 Handling of DEP_RES Information PDUs with chaining Initiator to Target
and Target to Initiator . 32
9.6.5 Handling of DEP_RES supervisory PDUs with timeout bit set to ONE . 35
9.6.6 Handling of DEP_RES supervisory PDUs with timeout bit set to ZERO .36
9.6.7 Handling of DSL_RES . 37
9.6.8 Handling of RLS_RES .38
9.6.9 Handling of WUP_RES (Active communication mode only) .39
Annex A (normative) Test report template for Target tests.41
Annex B (normative) Test report template for Initiator tests .45
iv
© ISO/IEC 2023 – 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.
The procedures used to develop this document and those intended for its further maintenance
are described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria
needed for the different types of document should be noted. This document was drafted in
accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives or
www.iec.ch/members_experts/refdocs).
ISO and IEC draw attention to the possibility that the implementation of this document may involve the
use of (a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of
any claimed patent rights in respect thereof. As of the date of publication of this document, ISO and IEC
had not received notice of (a) patent(s) which may be required to implement this document. However,
implementers are cautioned that this may not represent the latest information, which may be obtained
from the patent database available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall
not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to
the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see
www.iso.org/iso/foreword.html. In the IEC, see www.iec.ch/understanding-standards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 6, Telecommunications and information exchange between systems.
This second edition cancels and replaces the first edition (ISO/IEC 23917:2005), which has been
technically revised.
The main changes are as follows:
— alignment with the latest edition of ISO/IEC 18092 (the base standard);
— improvement on descriptions of test procedures;
— correction of test scenarios.
Any feedback or questions on this document should be directed to the user’s national standards
body. A complete listing of these bodies can be found at www.iso.org/members.html and
www.iec.ch/national-committees.
v
© ISO/IEC 2023 – All rights reserved
INTERNATIONAL STANDARD ISO/IEC 23917:2023(E)
Telecommunications and information exchange between
systems — Near Field Communication Interface and
Protocol 1 (NFCIP-1) — Protocol test methods
1 Scope
This document specifies protocol test methods for Near Field Communication Interface and Protocol 1
(NFCIP-1), as defined in ISO/IEC 18092 (the base standard).
The radio frequency (RF) test methods for NFCIP-1 (also defined in ISO/IEC 18092) are specified in
ISO/IEC 22536.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements 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, Cards and security devices for personal identification — Test methods — Part 6:
Contactless proximity objects
ISO/IEC 18092:2023, Telecommunications and information exchange between systems — Near Field
Communication Interface and Protocol (NFCIP-1)
ISO/IEC 22536, Information technology — Telecommunications and information exchange between
systems — Near Field Communication Interface and Protocol (NFCIP-1) — RF interface test methods
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 18092 and the following
apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www. iso. org/o bp
— IEC Electropedia: available at https:// www.e lectropedia. org/
3.1
activation in active communication mode
flow to activate the device under test (DUT) in active communication mode (3.3), which includes
initialisation and protocol activation
3.2
activation in passive communication mode
flow to activate the device under test (DUT) in passive communication mode (3.5), which includes
initialisation and protocol activation
3.3
active communication mode
mode in which both the Initiator and the Target use their own radio frequency (RF) field to enable the
communication
[SOURCE: ISO/IEC 18092:2023, 3.1]
© ISO/IEC 2023 – All rights reserved
3.4
operating volume
volume with a field strength of at least H and not exceeding H generated by a near field
min max
communication (NFC) device at manufacturer specified positions
3.5
passive communication mode
mode in which the Initiator is generating the radio frequency (RF) field and the Target responds to an
Initiator command in a load modulation scheme
[SOURCE: ISO/IEC 18092:2023, 3.17]
3.6
Single Device Detection
SDD
algorithm used by the Initiator to detect one out of several Targets in its radio frequency (RF) field
[SOURCE: ISO/IEC 18092:2023, 3.20]
3.7
scenario
protocol and application-specific sequence of test commands
Note 1 to entry: Scenario description tables list all individual test commands (3.8).
3.8
test commands
commands defined for dedicated functional behaviour on a device under test (DUT)
Note 1 to entry: Table 1 lists test commands.
3.9
transport protocol
protocol for data exchange between Initiator and Target, consisting of activation, data exchange and
deactivation
Note 1 to entry: The transport protocol is defined in ISO/IEC 18092.
4 Symbols and abbreviated terms
The abbreviated terms in ISO/IEC 18092 and the following apply.
ATR_REQ ATtribute Request command
ATR_RES Response to the ATR_REQ
CRC Cyclic Redundancy Check
~CRC CRC as defined above with all bits inverted
DEP_REQ Data Exchange Protocol Request
DEP_RES Response to the Data Exchange Protocol Request
DID Device ID
DSL_REQ DeSeLect Request command
DSL_RES Response to the DSL_REQ
© ISO/IEC 2023 – All rights reserved
DUT Device Under Test
f Frequency of operating field (carrier frequency)
c
H Maximum field strength of the Initiator antenna field
max
H Minimum field strength of the Initiator antenna field
min
H Threshold value to detect an external RF field
Threshold
ID Identification number
I/O Input and Output
LT Lower Tester, the Target-emulation part of the Initiator-Test-apparatus
Mute No response within a specified timeout
NFCIP-1 Near field communication interface and protocol
PDU Protocol Data Unit
PNI Packet Number Information
POL_REQ POLling Request command
POL_RES Response to the POL_REQ
PSL_REQ Parameter SeLect Request command
PSL_RES Response to the PSL_REQ
RF Radio Frequency
RFU Reserved for Future Use
RLS_REQ ReLease Request command
RLS_RES Response to the RLS_REQ
RTO PDU Response TimeOut extension
SAK Select Acknowledge
SDD Single Device Detection
t The delay between the end of the Request frame and the start of the first time slot for
d
SDD at f /64 and f /32 (equals 512 × 64/f )
c c c
t The period of one time slot (equals 256 × 64/f )
s c
t Active delay time
ADT
t RW waiting time
RFW
t the time between the start of the rising edge of the last modulation and the start of
RF,OFF
falling edge when the device turns off the RF field
TSN Time Slot Number
UT Upper Tester, the master part of the Initiator-Test-apparatus
© ISO/IEC 2023 – All rights reserved
WUPA Wake-UP command, Type A
5 Notational conventions
5.1 Representation of numbers
The following conventions and notations apply in this document unless otherwise stated.
— Letters and digits in parentheses represent numbers in hexadecimal notation.
— The setting of bits is denoted by ZERO or ONE.
— 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 is used to indicate that the setting of a bit
is not specified within the string.
5.2 Names
The names of basic elements, e.g. specific fields, are written with a capital initial letter.
5.3 Test report
The test reports (Annexes A and B) include 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).
6 Conformance
A DUT conforms to the protocols specified in ISO/IEC 18092 when it meets the test requirements in this
document.
7 Apparatus for testing
7.1 General
This clause is valid for Initiator and Target tests.
The test-apparatus may require information about the implemented protocol and functionality. These
parameters shall be recorded in the test report.
Although this document does not define a dedicated test circuit for timing measurements and to check
the correctness of the framing, the influence of such a circuit shall be avoided.
7.2 Generating the I/O character timing in reception mode
The target-test-apparatus and the lower tester (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 to ISO/IEC 22536.
7.3 Measuring and monitoring the RF I/O protocol
The target-test-apparatus and the LT shall be able to measure the timing of the logical low and high
states of the incoming demodulated data.
© ISO/IEC 2023 – All rights reserved
7.4 Test scenario and report
Testing of the DUT as defined in this document requires a test scenario to be executed. A test scenario is
defined as a protocol and application specific sequence of test commands.
The test commands are listed in Table 1. The test commands are specified based on PDUs specified in
ISO/IEC 18092.
Table 1 — Test commands
Test command Description
A(ACK) DEP_REQ or DEP_RES PDU coded as ACK/NACK PDU with ACK/NACK bit set to ZERO
xx
and PNI set to xx.
A(NACK) DEP_REQ or DEP_RES PDU coded as ACK/NACK PDU with ACK/NACK bit set to ONE
xx
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 "More
xx
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_COM-
MAND1, but this PDU has different data.
TEST_COMMAND3B The first part of a chaining command. This command marks the beginning of a
xx
DEP_REQ or DEP_RES frame, for an Initiator or Target respectively, with its "More
Information" bit set to ONE and the PNI set to xx.
TEST_COMMAND3n The middle part of a chaining command. This command is sent after TEST_COMMAND3B
xx
and before TEST_COMMAND3E. The lowercase 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 The last part of a chaining command. This command marks the end of the chaining
xx
procedure and is a DEP_REQ or 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 Response to a chaining command, which can be a DEP_REQ or DEP_RES frame, for
xx
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 Response to TEST_COMMAND4. It is a DEP_RES with the "More Information" bit set
xx
to ZERO and the PNI set to xx. It may be the same as TEST_RESPONSE1.
TEST_COMMAND5 Test command used for tests of the deactivation. This command forces the Initiator
xx
to send a DSL_REQ. It is a DEP_RES with the "More Information" bit set to ZERO and
the PNI set to xx.
TEST_COMMAND6 Test command used for tests of the deactivation. This command forces the Initiator
xx
to send an RLS_REQ. It is a DEP_RES with the "More Information" bit set to ZERO
and the PNI set to xx.
The PDUs that are actually used in these commands shall be recorded in the test report templates in
Annexes A and B.
The result of the test scenario shall be documented in a test report as defined in Annexes A and B.
© ISO/IEC 2023 – All rights reserved
7.5 RFU bits
A test shall fail and the DUT shall be declared non-compliant in case an RFU field is not set to its defined
value.
7.6 General rules
The following rules apply:
— An Initiator (Target-test-apparatus) always sends a request, whereas a Target (LT) sends a response.
— A response shall 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
8.1 General
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.2 Apparatus for testing the Target (Target-test-apparatus)
The Target-test-apparatus tests the DUT by emulating an Initiator.
The Target-test-apparatus shall execute the initialisation and protocol activation and perform data
exchange commands.
8.3 List of protocol test methods related to ISO/IEC 18092
To test Targets performing initialisation and SDD in Passive communication mode at f /128, the PICC
c
test methods of ISO/IEC 10373-6 and the test methods listed in Table 1 shall be executed.
Table 2 — Activation in Passive communication mode at fc/128
Test method Corresponding requirement
Clause in this doc- Name Base standard Clause(s)
ument
8.4.1 SDD for transport protocol activation ISO/IEC 18092:2023 11.3.1
To test Targets performing initialisation and SDD in Passive communication mode at f /64 and f /32 the
c c
test methods listed in Table 2 shall be executed.
Table 3 — Activation in Passive communication mode at fc/64 and fc/32
Test method Corresponding requirement
Clause in this doc- Name Base standard Clause(s)
ument
8.5.1 Activation time ISO/IEC 18092:2023 11.3.2.3
8.5.2 Frame format ISO/IEC 18092: 2023 11.3.2.2
8.5.3 SDD timing ISO/IEC 18092: 2023 11.3.2.3
8.5.4 SDD for transport protocol activation ISO/IEC 18092: 2023 11.3.2.3
11.3.2.4
© ISO/IEC 2023 – All rights reserved
To test Targets performing initialisation in Active communication mode, the test method in Table 3
shall be executed.
Table 4 — Activation in Active communication mode
Test method Corresponding requirement
Clause in this doc- Name Base standard Clause(s)
ument
8.6.1 RFCA ISO/IEC 18092: 2023 11.2.3
To test Targets using the transport protocol, the test methods listed in Table 4 shall be executed.
Table 5 — Logical operation of the Transport Protocol
Test method Corresponding requirement
Clause in this doc- Name Base standard Clause(s)
ument
8.7.1 Handling of ATR_REQ ISO/IEC 18092: 2023 12.6.1.3
8.7.2 Handling of PSL_REQ ISO/IEC 18092: 2023 12.6.3.3
8.7.3 Handling of DEP_REQ Information PDUs ISO/IEC 18092: 2023 12.7.1.2
8.7.4 Handling of DEP_REQ Information PDUs with ISO/IEC 18092: 2023 12.7.1.3
the more information bit set to ONE
8.7.5 Handling of DEP_REQ supervisory PDUs with ISO/IEC 18092: 2023 12.7.1.3
timeout bit set to ONE
8.7.6 Handling of DEP_REQ supervisory PDUs with ISO/IEC 18092: 2023 12.7.1.3
timeout bit set to ZERO
8.7.7 Handling of DSL_REQ ISO/IEC 18092: 2023 12.8.2.3
8.7.8 Handling of RLS_REQ ISO/IEC 18092: 2023 12.8.3.3
8.7.9 Handling of WUP_REQ (Active communication ISO/IEC 18092: 2023 12.6.2.4
mode only)
8.4 Activation in Passive communication mode at f /128
c
8.4.1 SDD for transport protocol activation
8.4.1.1 Purpose
The purpose of this test is to determine the activation of transport protocol when the Target supports
the transport protocol (see ISO/IEC 18092: 2023, 11.3.1).
8.4.1.2 Procedure
Repeat steps a) to e) for the data rates of f /128.
c
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
min max
influence the test results.
c) Perform SDD and receive a valid SAK with support of transport protocol.
d) Send an ATR_REQ command frame.
e) Verify that a valid ATR_RES frame is sent by the DUT.
© ISO/IEC 2023 – All rights reserved
8.4.1.3 Test report
The test report shall indicate whether the DUT behaves correctly.
8.5 Activation in Passive communication mode at f /64 and f /32
c c
8.5.1 Activation time
8.5.1.1 Purpose
The purpose of this test is to verify that the Target responds to a POL_REQ with a POL_RES within two
seconds after power up (see ISO/IEC 18092: 2023, 11.3.2.3).
8.5.1.2 Procedure
Repeat steps a) to e) for the data rates of f /64 and f /32.
c c
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
min max
influence 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.
e) Measure the timing between RF-on and the beginning of the first response of the DUT. If the DUT
responds in less than 2 sec, the test is PASS, otherwise it is FAIL.
8.5.1.3 Test report
The test report shall indicate whether the DUT behaves correctly for both data rates.
8.5.2 Frame format
8.5.2.1 Purpose
The purpose of this test is to determine that the frame formats at f /64 and f /32 are correct (see
c c
ISO/IEC 18092: 2023, 11.3.2.2).
8.5.2.2 Procedure
Repeat steps a) to d) for the data rates of f /64 and f /32.
c c
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
min max
influence 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.5.2.3 Test report
The test report shall indicate whether the DUT behaves correctly for both data rates and shall include
results for the characteristics as shown in Table 6.
© ISO/IEC 2023 – All rights reserved
Table 6 — Expected results for characteristics of frame formats
Characteristic Expected result
Preamble minimum 48 bits all logical ZEROs
SYNC 1st byte is ´B2´
2nd byte is ´4D´
value of the length byte ´12´
CRC bytes according to ISO/IEC 18092: 2023, Annex A
8.5.3 SDD timing
8.5.3.1 Purpose
The purpose of this test is to determine the correct response to the POL_REQ (see ISO/IEC 18092: 2023,
11.3.2.3) in a timely manner.
8.5.3.2 Procedure
Repeat steps a) to f) for the data rates of f /64 and f /32. Initially TSN is set to 0.
c c
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
min max
influence the test results.
c) Send a POL_REQ command frame with TSN 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).
e) Analyse the content of the response.
f) Increase the TSN to the next allowed value and repeat steps a) to e) until the maximum TSN value is
reached.
8.5.3.3 Test report
The test report shall indicate whether the DUT behaves correctly for both data rates and shall include
results for the characteristics as shown in Table 7.
Table 7 — Expected result of characteristics of SDD timing
Characteristic Expected result
1st byte of the payload ´01´
time between end of POL_REQ and t + (TSN + 1) * t
d s
end of POL_RES
8.5.4 SDD for transport protocol activation
8.5.4.1 Purpose
The purpose of this test is to determine the activation of transport protocol when the Target supports
the transport protocol (see ISO/IEC 18092: 2023, 11.3.2.3 and 11.3.2.4).
© ISO/IEC 2023 – All rights reserved
8.5.4.2 Procedure
Repeat steps a) to g) for the data rates of f /64 and f /32. Initially TSN is set to 0.
c c
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
min max
influence the test results.
c) Send a POL_REQ command frame with TSN at the selected data rate.
d) Record the 6-byte number of POL_RES and the time between POL_REQ and POL_RES. If the DUT
does not respond in the last time slot available repeat step c).
e) Analyse the content of the response.
f) If the 6-byte number of POL_RES is identical to the 6-byte number of POL_RES previously received,
turn the RF field off and then repeat step a) to e).
g) Send an ATR_REQ command frame.
h) Verify that a valid ATR_RES frame is sent by the DUT.
8.5.4.3 Test report
The test report shall indicate whether the DUT behaves correctly for both data rates and shall include
results for the characteristics as shown in Table 8.
Table 8 — Expected result of characteristics of SDD for transport protocol
Characteristic Expected result
1st byte of the payload ´01´
2nd byte of the payload ´01´
3rd byte of the payload ´FE´
8.6 Activation in Active communication mode
8.6.1 RFCA
8.6.1.1 Purpose
The purpose of this test is to determine the behaviour of the DUT in Active communication mode during
RFCA (see ISO/IEC 18092: 2023, 11.2.3).
8.6.1.2 Procedure
Repeat steps a) to g) for the data rates of f /128, f /64 and f /32.
c c c
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
min max
influence the test results.
c) Send a valid ATR_REQ command frame at the selected data rate and switch off the RF afterwards.
d) Receive a valid ATR_RES frame at the selected data rate.
e) Measure the time between RF-off of the Target test-apparatus and RF-on of the DUT.
f) Measure the time between the start of the rising edge of the last modulation and RF-off of the DUT.
© ISO/IEC 2023 – All rights reserved
g) Repeat steps a) to f) until all randomly generated number of time periods are met and count the
number of retries necessary.
8.6.1.3 Test report
The test report shall indicate whether the DUT behaves correctly for all data rates as shown in Table 9.
Table 9 — Expected results for characteristics of RFCA
Characteristic Expected result
t minimum 768/f
ADT c
maximum 2559/f
c
t n times 512/f
RFW c
t minimum 350/f and maximum 2559/f for a bit rate of f /128
RF,OFF c c c
minimum 215/f and maximum 2559/f for a bit rate of f /64 or f /32
c c c c
8.7 Logical operation of the Target Transport Protocol
8.7.1 Handling of ATR_REQ
8.7.1.1 Purpose
The purpose of this test is to determine the correct handling of the ATR_REQ of the DUT (see
ISO/IEC 18092: 2023, 12.6.1.3).
8.7.1.2 Procedure
Repeat steps a) to e) for each of test scenario T 1, T 2 and T 3, for the data rates of f /128, f /64 and f /32
c c c
and for both Active and Passive communication modes. Test scenarios T 1, T 2 and T 3 are defined in
Table 10, Table 11 and Table 12, respectively.
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
min max
influence the test results.
c) Perform activation at the selected data rate and follow the rules for RFCA in Active communication
mode.
d) Apply the test scenario T 1, T 2 and T 3. T 3 is optional.
e) Check if the response and the PNIs from the DUT are according to the applied scenario.
Table 10 — Scenario T 1 — ATR_REQ with PPi:b8 set to ZERO, correct transaction
Target-test-apparatus DUT
ATR_REQ
ATR_RES
TEST_COMMAND1
TEST_RESPONSE1
© ISO/IEC 2023 – All rights reserved
Table 11 — Scenario T 2 — ATR_REQ with PPi:b8 set to ZERO, erroneous transaction
Target-test-apparatus DUT
TEST_COMMAND1
Mute
ATR_REQ (~CRC)
Mute
ATR_REQ
ATR_RES
TEST_COMMAND1
TEST_RESPONSE1
ATR_REQ
Mute
TEST_COMMAND1
TEST_RESPONSE1
Table 12 — Scenario T 3 — ATR_REQ with PPi:b8 set to ONE
Target-test-apparatus DUT
ATR_REQ
ATR_RES
TEST_COMMAND1
TEST_RESPONSE1
8.7.1.3 Test report
The test report shall indicate whether the DUT behaves correctly for all data rates and communication
modes.
8.7.2 Handling of PSL_REQ
8.7.2.1 Purpose
The purpose of this test is to determine the correct PSL handling of the DUT (see ISO/IEC 18092: 2023,
12.6.3.3).
8.7.2.2 Procedure
Repeat steps a) to f) for each test scenario T 4, T 5 and T 6, for the data rates of f /128, f /64 and f /32
c c c
and for both Active and Passive communication modes. Test scenarios T 4, T 5 and T 6 are defined in
Table 13, Table 14 and Table 15, respectively.
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
min max
influence the test results.
c) Perform initialisation and protocol activation in the selected communication mode and data rate.
d) Send an ATR_REQ and receive ATR_RES.
e) Apply the test scenario T 4, T 5 or T 6.
f) Check if the response and the PNIs from the DUT are according to the applied scenario.
© ISO/IEC 2023 – All rights reserved
Table 13 — Scenario T 4 — PSL_REQ
Target-test-apparatus DUT
PSL_REQ
PSL_RES
PSL_REQ
Mute
TEST_COMMAND1
TEST_RESPONSE1
Table 14 — Scenario T 5 — PSL_REQ
Target-test-apparatus DUT
PSL_REQ (~CRC)
Mute
PSL_REQ
Mute
TEST_COMMAND1
TEST_RESPONSE1
Table 15 — Scenario T 6 — PSL_REQ
Target-test-apparatus DUT
TEST_COMMAND1
TEST_RESPONSE1
PSL_REQ
Mute
TEST_COMMAND1
TEST_RESPONSE1
8.7.2.3 Test report
The test report shall indicate whether the DUT behaves correctly for all data rates and communication
modes.
8.7.3 Handling of DEP_REQ Information PDUs
8.7.3.1 Purpose
The purpose of this test is to determine the correct handling of the DEP_REQ information PDU of the
DUT (see ISO/IEC 18092: 2023, 12.7.1.3).
8.7.3.2 Procedure
Repeat steps a) to f) for each test scenario T 7, T 8, and T 9, for the data rates of f /128, f /64 and f /32
c c c
and for both Active and Passive communication modes. Test scenarios T 7, T 8 and T 9 are defined in
Table 16, Table 17 and Table 18, respectively.
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
min max
influence the test results.
c) Perform activation in the selected communication mode and data rate.
© ISO/IEC 2023 – All rights reserved
d) Send an ATR_REQ and receive the ATR_RES from the DUT.
e) Apply the test scenario T 7, T 8 or T 9.
f) Check if the response and the PNIs from the DUT are according to the scenarios.
Table 16 — Scenario T 7 — DEP_REQ information PDU, correct transaction
Target-test-apparatus DUT
TEST_COMMAND1
TEST_RESPONSE1
TEST_COMMAND1
TEST_RESPONSE1
TEST_COMMAND1
TEST_RESPONSE1
TEST_COMMAND1
TEST_RESPONSE1
TEST_COMMAND1
TEST_RESPONSE1
Table 17 — Scenario T 8 — DEP_REQ information PDU, erroneous transaction
Target-test-apparatus DUT
TEST_COMMAND1 (~CRC)
Mute
S(A)
S(A)
TEST_COMMAND1
TEST_RESPONSE1
TEST_COMMAND1
TEST_RESPONSE1
Table 18 — Scenario T 9 — DEP_REQ information PDU, erroneous transaction
Target-test-apparatus DUT
TEST_COMMAND1
TEST_RESPONSE1
TEST_COMMAND1 (~CRC)
Mute
S(A)
S(A)
TEST_COMMAND1
TEST_RESPONSE1
8.7.3.3 Test report
The test report shall indicate whether the DUT behaves correctly for all data rates and communication
modes for both scenarios.
© ISO/IEC 2023 – All rights reserved
8.7.4 Handling of DEP_REQ Information PDUs with chaining Initiator to Target and Target to
Initiator
8.7.4.1 Purpose
The purpose of this test is to determine the correct handling of the DEP_REQ information PDU
with chaining feature. The chaining feature is enabled by the more information bit set to ONE (see
ISO/IEC 18092: 2023, 12.7.1.3).
8.7.4.2 Procedure
Repeat steps a) to f) for each test scenario T 10, T 11, T 12, T 13, T 14 and T 15, for the data rates of
f /128, f /64 and f /32 and for both Active and Passive communication modes. Test scenarios T 10, T 11,
c c c
T 12, T 13, T 14 and T 15 are defined in Table 19, Table 20, Table 21, Table 22, Table 23 and Table 24,
respectively.
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
min max
influence the 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) Apply the test scenario T 10, T 11, T 12, T 13, T 14 or T 15. T 13 is optional.
f) Check if the response and the PNIs from the DUT are according to the test scenarios.
Table 19 — Scenario T 10 — DEP_REQ information PDU with more information bit set to ONE,
correct transaction
Target-test-apparatus DUT
TEST_COMMAND1
TEST_RESPONSE1
TEST_COMMAND3B
A(ACK)
TEST_COMMAND3E
TEST_RESPONSE3
TEST_COMMAND1
TES
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...