ECMA 362-2005 NFCIP-1 - Protocol Test Methods (2nd Edition)《NFCIP-1协议试验方法 第2版》.pdf

《ECMA 362-2005 NFCIP-1 - Protocol Test Methods (2nd Edition)《NFCIP-1协议试验方法 第2版》.pdf》由会员分享，可在线阅读，更多相关《ECMA 362-2005 NFCIP-1 - Protocol Test Methods (2nd Edition)《NFCIP-1协议试验方法 第2版》.pdf（55页珍藏版）》请在麦多课文档分享上搜索。

1、 ECMA-362 2ndEdition / December 2005 NFCIP-1 - Protocol TestMethods Standard ECMA-362 2ndEdition / December 2005 NFCIP-1 - Protocol Test Methods Ecma International Rue du Rhne 114 CH-1204 Geneva T/F: +41 22 849 6000/01 www.ecma-international.org IW ECMA-362.doc 08/12/2005 15:08 . Brief history In 20

2、02, 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 Int

3、erface and Protocol-1 (NFCIP-1) as Standard ECMA-340. This Ecma standard specifies protocol tests for ECMA-340 and complements ECMA-356, which specifies the RF interface tests for ECMA-340. This 2ndEdition is completely aligned with ISO/IEC 23917:2005. This Ecma Standard has been adopted by the Gene

4、ral Assembly of December 2005. Table of contents1 Scope 1 2 Conformance 1 3 References 1 4 Notational conventions 4.1 Representation of numbers 4.2 Names 1 4.3 Test report 1 5 Terms and definitions 5.1 Activation in Active communication Mode 5.2 Activation in Passive communication Mode 5.3 Active co

5、mmunication Mode 5.4 Operating volume 2 5.5 Passive communication Mode 5.6 Single Device Detection (SDD) 5.7 Scenario 2 5.8 Test commands 2 6 Acronyms and abbreviations 3 7 General description 4 7.1 Apparatus for Testing 7.1.1 Generating the I/O character timing in reception mode 7.1.2 Measuring and

6、 monitoring the RF I/O protocol 7.1.3 Test scenario and report 7.1.4 RFU bits 4 7.1.5 General rules 4 8 Target test methods 5 8.1 Apparatus for testing the Target (Target-test-apparatus) 8.2 List of protocol test methods related to ECMA-340 8.3 Activation in Passive communication Mode at 212 and 424

7、 kbps 6 8.3.1 Activation time 6 8.3.2 Frame format 6 8.3.3 SDD at 212 and 424 kbps 7 - i - 8.4 Activation in Active communication Mode 7 8.4.1 RF Collision Avoidance 8.5 Logical operation of the Target Transport Protocol 8 8.5.1 Handling of ATR_REQ 8.5.2 Handling of PSL_REQ 9 8.5.3 Handling of DEP_R

8、EQ Information PDUs 10 8.5.4 Handling of DEP_REQ Information PDUs with the “more information“ bit set to ONE 12 8.5.5 Handling of DEP_REQ supervisory PDUs with timeout bit set to ONE 16 8.5.6 Handling of DEP_REQ supervisory PDUs with timeout bit set to ZERO 17 8.5.7 Handling of DSL_REQ 18 8.5.8 Hand

9、ling of RLS_REQ 19 8.5.9 Handling of WUP_REQ (Active communication Mode Only) 20 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 106 kbps

10、23 9.1.3 Protocol activation procedures for Passive communication Mode at 212 and 424 kbps 23 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 212 and 424 kbps 25 9.3.1 Frame form

11、at 25 9.3.2 SDD at 212 and 424 kbps 25 9.4 Activation in Active communication Mode 26 9.4.1 Initial RF Collision Avoidance 26 9.4.2 Response RF Collision Avoidance with time jitter n=0 26 9.5 Logical operation of the Transport Protocol 26 9.5.1 Handling of ATR_RES 26 9.5.2 Handling of PSL_RES 27 9.5

12、.3 Handling of DEP_RES Information PDUs 28 9.5.4 Handling of DEP_RES Information PDUs with more information bit set to ONE 30 9.5.5 Handling of DEP_RES supervisory PDUs with timeout bit set to ONE 33 9.5.6 Handling of DEP_RES supervisory PDUs with timeout bit set to ZERO 35 9.5.7 Handling of DSL_RES

13、 36 9.5.8 Handling of RLS_RES 37 Annex A (normative) Test report template for Target tests 39 Annex B (normative) Test report template for Initiator tests 43 - ii - 1 Scope This Standard specifies protocol test methods for ECMA-340 in addition to those specified in ECMA-356. 2 Conformance In additio

14、n to conforming to ECMA-356, implementations of ECMA-340 shall pass all normative tests and requirements specified herein; test results shall be recorded using Annex A and Annex B of this Standard. 3 References The following are normative references for the purpose of this Standard: ECMA-340 Near Fi

15、eld Communication - Interface and Protocol (NFCIP-1) ECMA-356 NFCIP-1 - RF Interface Test Methods ISO/IEC 10373-6 Identification cards - Test methods - Part 6: Proximity cards 4 Notational conventions 4.1 Representation of numbers The following conventions and notations apply in this document unless

16、 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

17、, 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. 4.3 Test report The test report includes the number of passed tests versus the total number of tests, the

18、number of different samples and the date of the tests, see Annexes A and B. 5 Terms and definitions 5.1 Activation in Active communication Mode Flow to activate the DUT in Active communication Mode as defined in ECMA-340, which includes initialisation and protocol activation. 5.2 Activation in Passi

19、ve communication Mode Flow to activate the DUT in Passive communication Mode as defined in ECMA-340, which includes initialisation and protocol activation. 5.3 Active communication Mode In the Active communication Mode scheme, as defined in ECMA-340, both the Initiator and the Target use their own R

20、F field to enable the communication. - 1 - 5.4 Operating volume A volume with a field strength of at least Hminand not exceeding Hmaxgenerated by a NFC device at manufacturer specified positions. 5.5 Passive communication Mode The Initiator is generating the RF field and the Target responds to an In

21、itiator command in a load modulation scheme as defined in ECMA-340. 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 desc

22、ription 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 ECMA-340. The PDUs that ar

23、e 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 The following test commands are specified based on PDUs specified in ECMA-340: A(ACK)xxDEP_REQ or DEP_RES PDU coded as ACK/NACK PDU with ACK/NACK bit set

24、to ZERO and PNI set to xx. A(NACK)xxDEP_REQ or DEP_RES PDU coded as ACK/NACK PDU with ACK/NACK bit set to ONE and PNI set to xx. S(A) DEP_REQ or DEP_RES PDU coded as Supervisory PDU (as defined in ECMA-340) with the Timeout bit set to ZERO. No PNI is used for this command. S(TO) DEP_REQ or DEP_RES P

25、DU coded as Supervisory PDU (as defined in ECMA-340) with the Timeout bit set to ONE. No PNI is used for this command. TEST_COMMAND1xxDefault Test command, it is a DEP_REQ frame coded as information PDU with “More Information“ bit set to ZERO (no chaining) and the PNI set to xx. The Initiator or the

26、 target-test-apparatus sends this PDU. TEST_RESPONSE1xxResponse to TEST_COMMAND1 (DEP_RES) with the PNI set to xx. TEST_COMMAND2xxTest command used for tests of the chaining procedure. This command forces the counterpart (either Initiator or Target) to use chaining in the next DEP_REQ. This command

27、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_COMMAND3BxxThis command marks the beginning of a DEP_REQ or DEP_RES frame, for an Initiator or Target r

28、espectively, with its “More Information“ bit set to ONE and the PNI set to xx. - 2 - TEST_COMMAND3nxxThis command is sent after TEST_COMMAND3B and before TEST_COMMAND3E. 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 t

29、o xx. TEST_COMMAND3ExxThis command marks the end of the chaining 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_RESPONSE3xxis the response to the chaining command. Shall be a DEP_REQ or DEP

30、_RES frame, for an Initiator or Target respectively, with the “More Information“ bit set to ZERO and the PNI set to xx. TEST_COMMAND4xxTest command used for tests dealing with frame waiting time. The Initiator sends this command and forces the Target to use a Supervisory PDU with the timeout bit set

31、 to ONE and the PNI set to xx. TEST_RESPONSE4xxis the response to TEST_COMMAND4. It is a DEP_RES with the “More Information“ 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 ECMA-340 ATR_RES Resp

32、onse to the ATR_REQ CRC Cyclic Redundancy Check as defined in Annex A of ECMA-340 CRC CRC as defined above with all bits inverted DEP_REQ Data Exchange Protocol Request as defined in ECMA-340 DEP_RES Response to the Data Exchange Protocol Request DID Device ID as defined in ECMA-340 DSL_REQ DeSeLect

33、 Request command as defined in ECMA-340 DSL_RES Response to the DSL_REQ DUT Device Under Test fc Frequency of operating field (carrier frequency) as defined in ECMA-340 Hmax Maximum field strength of the Initiator antenna field as defined in ECMA-340 Hmin Minimum field strength of the Initiator ante

34、nna field as defined in ECMA-340 HThreshold Defined in ECMA-340 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 ECMA-340 PNI Package Number Information as defined in EC

35、MA-340 POL_REQ POlling Request command as defined in ECMA-340 POL_RES Response to the Polling Request PSL_REQ Parameter SeLect Request command as defined in ECMA-340 PSL_RES Response to the PSL_REQ RF Radio Frequency - 3 - RFU Reserved for Future Use RLS_REQ ReLease Request command as defined in ECM

36、A-340 RLS_RES Response to the RLS_REQ RTO PDU Response TimeOut extension as specified in ECMA-340 clause 12.6.1.3.3 and 12.6.2 SDD Single Device Detection as defined in ECMA-340 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

37、 512 64/fc) Ts The period of one time slot (equals 256 64/fc) TCM Test control message UT Upper Tester, the master part of the Initiator-Test-apparatus 7 General description 7.1 Apparatus for Testing NOTE The test-apparatus may require information about the implemented protocol and functionality. Th

38、ese parameters shall be recorded in the test report. This clause is valid for Initiator and Target tests. Although this 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 th

39、e 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 ECMA-340. 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 val

40、ue within the defined ranges of ECMA-340. The limits shall be tested according ECMA-356. 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

41、 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

42、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

43、 TEST_RESPONSEn and TEST_COMMANDn are the same, then TEST_COMMANDn is correct. - 4 - 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

44、(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.2 List of protocol test methods related to ECMA-340 To test Targets performing initialis

45、ation 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 co

46、mmunication Mode at 212 and 424 kbps Test method Corresponding requirement Clause Name Base standard Clause(s) 8.3.1 Activation time ECMA-340 11.2.2.3 8.3.2 Frame format ECMA-340 11.2.2.2 8.3.3 SDD at 212 and 424 kbps ECMA-340 11.2.2.3 11.2.2.4 To test Targets performing initialisation in Active com

47、munication 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 ECMA-340 11.1.2 To test Targets using the transport protocol the test methods listed in

48、table 3 must be executed. - 5 - 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 ECMA-340 12.5.1.3 8.5.2 Handling of PSL_REQ ECMA-340 12.5.3.3 8.5.3 Handling of DEP_REQ Information PDUs ECMA-340 12

49、.6.1.2 8.5.4 Handling of DEP_REQ Information PDUs with the “more information“ bit set to ONE ECMA-340 12.6.1.3 8.5.5 Handling of DEP_REQ supervisory PDUs with timeout bit set to ONE ECMA-340 12.6.1.3 8.5.6 Handling of DEP_REQ supervisory PDUs with timeout bit set to ZERO ECMA-340 12.6.1.3 8.5.7 Handling of DSL_REQ ECMA-340 12.7.1.3 8.5.8 Handling of RLS_REQ ECMA-340 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 tw