hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.2.4.1 Valid behaviour | TP/OBU/AL/OF/BV/01 Verify that the IUT can manage the Read-Display-Type-Rq Reference: Clauses 11.5.5, 11.6.2 and 11.6.6 PICS Selection: Table A.4/7 AND Table A.4/8 AND Table A.5/6 Initial conditions with { the IUT being in the "initial state" } Expected behaviour ensure that { when { the IUT receives a valid Open-Rq | ... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.2.4.2 Invalid behaviour | TP/OBU/AL/OF/BI/01 Verify that the IUT can manage an invalid Action-Rq (covers also Write-Data-To-External-Rq and Read-Data_from-External-Rq) Reference: Clauses 11.5.11, 11.5.12, 11.5.19, 11.6.2, 11.6.12, 11.6.13, 11.6.20 PICS Selection: Table A.4/19 AND Table A.4/20 AND Table A.4/21 AND Table A.4/22 AND Table A.4/35 A... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.2.5 Security | |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.2.5.1 Valid behaviour | TP/OBU/AL/SC/BV/01 Verify that the IUT can manage Set-Password-Rq Reference: Clauses 11.5.20, 11.6.2 and 11.6.21 PICS Selection: Table A.4/37 AND Table A.4/38 Initial conditions with { the IUT being in the "initial state" AND the password to be used in the OBU is accessed according to the applicant specifications, and ... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.2.5.2 Invalid behaviour | TP/OBU/AL/SC/BI/01 Verify that the IUT can manage Set-Password-Rq with invalid length Reference: Clauses 11.5.20, 11.6.2 and 11.6.21 PICS Selection: Table A.4/37 AND Table A.4/38 Initial conditions with { the IUT being in the "initial state" AND the password to be used in the OBU is accessed according to the applicant ... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.2.6 Integrity constraints | |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.2.6.1 Invalid behaviour | TP/OBU/AL/IC/BI/01 Verify that the IUT correctly identifies an invalid termination request Reference: Clauses 11.6.2 and 11.6.4 PICS Selection: Table A.4/3 AND Table A.4/4 Initial conditions with { the IUT being in the "initial state" } Expected behaviour ensure that { when { the IUT receives a valid Close-Rq with new ... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.3 Test purposes for road side units | |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.3.1 Kernel Unit | TP/RSU/AL/KU/BV/01 Verify that the IUT can establish a connection with an OBU Reference: Clauses 11.5.2, 11.5.3, 11.6.3 and 11.6.4 PICS Selection: Table B.4/1 AND Table B.4/2 AND Table B.4/3 AND Table B.4/4 Initial conditions with { the IUT being in the "initial state" and the IUT is stimulated to send the sequence Ope... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.3.2 Read access | TP/RSU/AL/RA/BV/01 Verify that the IUT can read specific fields of the master core Reference: Clauses 11.5.6 and 11.6.7 PICS Selection: Table B.4/9 AND Table B.4/10 Initial conditions with { the IUT being in the "initial state" and the IUT is stimulated to send the sequence Open-Rq | Read-Master-Core-Rq | Close-Rq with... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.3.3 Write access | TP/RSU/AL/WA/BV/01 Verify that the IUT can write specific fields of the application core and no support of security level 1 Reference: Clauses 11.5.9 and 11.6.10 PICS Selection: Table B.4/15 AND Table B.4/16 AND NOT Table B.2/3 Initial conditions with { the IUT being in the "initial state" and the IUT knows the value o... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.3.4 Optional functionality | TP/RSU/AL/OF/BV/01 Verify that the IUT can issue a Read-Display-Type-Rq Reference: Clauses 11.5.5 and 11.6.6 PICS Selection: Table B.4/7 AND Table B.4/8 AND Table B.9/6 Initial conditions with { the IUT being in the "initial state" and the IUT is stimulated to send the sequence Open-Rq | Read-Display-Type-Rq | Close-Rq... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.3.5 Security | TP/RSU/AL/SC/BV/01 Verify that the IUT can issue a Set-Password-Rq Reference: Clauses 11.5.20 and 11.6.21 PICS Selection: Table B.4/37 AND Table B.4/38 Initial conditions with { the IUT being in the "initial state" and the IUT is stimulated to send the sequence Open-Rq | Set-Password-Rq with new private LinkID and with... |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 1 Scope | The present document contains the Abstract Test Suite (ATS) and partial PIXIT proforma to test the "Dedicated Short Range Communication" (DSRC) "High Data Rate" (HDR) data link layer [1]. The objective of this abstract test specification is to provide test scripts for testing conformance of DSRC-HDR equipment specified... |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI ES 200 674-1: "Electromagnetic compatibility and... |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ETSI TS 102 708-2-3: "Intelligent Transport Syst... |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 3 Definitions and abbreviations | |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ES 200 674-1 [1], ISO/IEC 9646-1 [4], ISO/IEC 9646-2 [5], ES 201 873-1 [8] and the following apply: abstract test case: Refer to ISO/IEC 9646-1 [4]. Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 [4]. Abstract Test Suite (ATS): Refer to I... |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ES 200 674-1 [1], ISO/IEC 9646-1 [4], ISO/IEC 9646-2 [5], ES 201 873-1 [8] and the following apply: ATS Abstract Test Suite IUT Implementation Under Test OBU On Board Unit PDU Protocol Data Unit PICS Protocol Implementation Conformance Statement PIXIT... |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 4 Abstract Test Method (ATM) | This clause describes the ATM used to test TS 102 708-1-2 [3]. |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 4.1 Protocol layer architecture | The implementation under test is the LLC layer of ES 200 674-1 [1]. The System under test comprises also the PHY layer and the application layer, whixh are necessary to perform the IUT tests. The tester executes the TTCN-3 scripts of the present Test Specification, running on an emulated PHY layer. Figure 1: Protocol l... |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 4.2 Test system architecture | |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 4.2.1 The TTCN-3 test architecture | An abstract architecture for a test system (TS) implementing a TTCN-3 ATS is displayed in figure 2 and also stated in ES 201 873-5 [9]. Test Management (TM) Test Control (TC) Test Logging (TL) TCI TTCN-3 Executable (TE) TTCN-3 Runtime System (T3RTS) Executable Test Suite (ETS) Encoding/Decoding System TRI SUT Adapter (... |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 4.2.2 The HDR LLC test architecture | TTCN-3 Test Case _ MTC (TE + TM) Component type: LLC_simu SUT Adapter TRI PHY testing controller HDR LLC SUT (OBU or RSU) HDR LLC Test System PHY layer emulation llc port ctrl port AL (Application Layer) IUT = LLC Layer PHY Layer Client Application TTCN-3 action operation Figure 3: The HDR LLC Test System Architecture ... |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 4.2.3 Port mapping | |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 4.2.3.1 Mapping rules for the llc port | Two TTCN-3 types are sent and received over the llc port: • the Lpdu type; • the LpduExceedN2 type. ETSI ETSI TS 102 708-1-3 V1.1.1 (2010-03) 10 Table 2: Lpdu type mapping TTCN-3 type LLC frame field LlcAddressField LLC Address Field of the LPDU InformationField (octetstring, length = 0 .. 56) Information Field of the ... |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 4.2.3.2 Mapping rules for the ctrl port | Table 4: CtrlMessages type mapping TTCN-3 type Description, CtrlMsg Enumerated type, each enumerated value representing a specific test adapter function (request/response). ctrlValue (16 bits integer) This parameter is used as necessary for sending or receiving values (eg timing value as response to a request for measu... |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 4.3 Type of SUT | Two types of systems under test (SUT) are distinguished, i.e. on board units (OBUs) and road side units (RSUs). |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 5 Untestable test purposes | This clause gives a list of TP, which are not implemented in the ATS due to the chosen ATM or other restrictions. Table 5: Untestable TP Test Case Name Reason void |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 6 The ATS development process | |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 6.1 Requirements and Test Purposes | For each test purpose there is a table defined in clause 5 of TS 102 708-1-2 [3]. The requirements applicable to this TP are given by a reference to ES 200 674-1 [1]. There are no explicit formulations of requirements. |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 6.2 Test case grouping | The ATS structure is based on the structuring of Test Purposes in clause 4 of TS 102 708-1-2 [3]. ETSI ETSI TS 102 708-1-3 V1.1.1 (2010-03) 11 |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 6.3 Test case identifier | The test case names are built up according to the following scheme. Table 6: TC identifier naming convention scheme TC_<st>_<pl_<x>_<nn> <st> = side type OBU On Boad Unit RSU Road Side Unit <pl> = protocol layer DLL DLL AL Application Layer (see note) <x> = type of testing BV Valid Behaviour Tests BI Invalid Syntax or ... |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 6.4 ATS Library | For this ATS the TTCN-3 library modules are basically organized as: 1) LibCommon modules (only a sub-part of the modules of this library is used); 2) DLL test suite modules. The following table shows the organisation of the ATS as library of modules. Table 7: Library of modules Module Class Module Id Description LibCom... |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 6.5 TTCN-3 naming conventions | Like in other software projects using a programming language, the use of naming conventions supports or increases: a) the readability; b) the detection of semantic errors; c) the shared work of several developers; d) the maintainability. The naming conventions applied to the ATS are based on the following underlying pr... |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 6.6 PICS information | Test purposes, which form the base test specification for this ATS, contain selection criteria using PICS parameters. Actually a major part of the features described in the PICS are likely to be supported, even if the PICS status is "optional". Thus the selection criteria will not be applied as a condition for the exec... |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 6.7 Test Suite documentation | In order to allow browsing of the ITS_L2 ATS without the use of a specific TTCN-3 test development environment, the TTCN ATS is made available in HTML format with hyperlinks between entities in the ATS. The documentation in the ATS makes use of special comment tags used by the tool that converts the ATS to the HTML for... |
9a33fd5eaf4d7ae68bf727ac22d4ab29 | 102 708-1-3 | 6.8 ATS archive | ATS archive is contained in archive ts_1027080103v010101p0.zip which accompanies the present document. ETSI ETSI TS 102 708-1-3 V1.1.1 (2010-03) 14 Annex A (normative): Partial PIXIT proforma Notwithstanding the provisions of the copyright clause related to the text of the present document, grants that users of the pre... |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 1 Scope | The present document contains the Test Suite Structure (TSS) and Test Purposes (TP) to test the "Dedicated Short Range Communication" (DSRC) "High Data Rate" (HDR) data link layer [1]. The objective of this test specification is to provide a basis for conformance tests for DSRC-HDR equipment specified in [1] giving a h... |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI ES 200 674-1: "Electromagnetic compatibility and... |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. ETSI ETSI TS 102 708-1-2 V1.1.1 (2010-... |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 3 Definitions and abbreviations | |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in [1] and [3] apply. |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in [1] and [3] apply. |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 4 Test Suite Structure | |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 4.1 Structure | Table 1 shows the DLL Test Suite Structure (TSS) including its subgroups defined for the conformance testing. Table 1: Test suite structure for DSRC-HDR data link layer Group Type of system under test (SUT) Behaviour Data link layer On Board Unit Valid behaviour Invalid behaviour Road Side Unit Valid behaviour Invalid ... |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 4.2 Test groups | There is a single test group for the data link layer of DSRC-HDR. |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 4.3 Type of SUT | Two types of systems under test (SUT) are distinguished, i.e. on board units (OBUs) and road side units (RSUs). |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 4.4 Behaviour test groups | |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 4.4.1 Valid behaviour tests | Valid behaviour tests shall verify that the IUT reacts in conformity with the base standard [1], after receipt or exchange of valid protocol data units (PDUs). "Valid PDU" means that the exchange of messages and the content of the exchanged messages are considered as valid, i.e compliant with the base standard. |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 4.4.2 Invalid behaviour tests | Invalid behaviour tests shall verify that the IUT reacts in conformity with the base standard [1], after receipt of a syntactically invalid protocol data unit (PDU). ETSI ETSI TS 102 708-1-2 V1.1.1 (2010-03) 7 |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 5 Test purposes | |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 5.1 Introduction | |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 5.1.1 Definition conventions | Test purposes (TPs) are defined following particular rules as presented in table 2. Table 2: TP definition rules TP ID Title: Reference: PICS Selection: TC Reference Initial condition: Stimulus and Expected behaviour: TP ID The TP ID is a unique identifier. It shall be specified according to the TP naming conventions d... |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 5.1.2 Naming conventions | The identifier of the TP is built according to table . Table 3: TP naming convention Identifier TP/<sut>/<layer>/<x>/<n> <sut> = Type of SUT OBU On Board Unit RSU Road Side Unit <layer> DLL Data Link Layer x = Type of testing BV Valid Behaviour Test BI Invalid Behaviour Test <n> = sequential number >0 <n> = sequential ... |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 5.1.3 Sources of TP definitions | All TPs are specified according to the base standard ES 200 674-1 [1]. |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 5.1.4 General reference | All references in the test purposes, if not stated differently, are indicating clauses of the base standard ES 200 674-1 [1]. All references to PICS are indicating tables in TS 102 708-1-1 [2]. ETSI ETSI TS 102 708-1-2 V1.1.1 (2010-03) 8 |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 5.1.5 General conditions | For all TPs related to OBUs the following pre-conditions shall apply, if not defined differently for a specific TP: • The OBU shall be ready for communication, i.e. it shall not be in sleep mode and all boot processes shall be finalized. Additional pre-conditions may apply for specific TPs. |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 5.1.6 Default PICS selection | For all TPs related to OBUs the following PICS selections shall apply in addition to those specified for a specific TP: • Tables A.1/1, A.4/3 and A.4/9 of the PICS [2] is implicitly selected for all TPs. For all TPs retaled to RSUs the following PICS selections shall apply in addition to those specified for a specific ... |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 5.2 Test purposes for on-board units | |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 5.2.1 Valid behaviour tests | TP/OBU/DLL/BV/01 Verify that the IUT can reply to requests providing proper values in the LLC address field Reference: Clauses 10.9.1, 10.4.1 and 10.4.2 PICS Selection: Table A.3/1 TC reference: Initial condition: Stimulus and Expected Behaviour: 1) Tester sends a frame to the IUT upon which a reply is expected. 2) Ver... |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 5.2.2 Invalid behaviour tests | TP/OBU/DLL/BI/01 Verify that the IUT ignores downlink frames with a length exceeding the maximum allowed length as defined by N2 Reference: Clauses 10.2.2.1 and 10.2.2.4 PICS Selection: Table A.4/1 AND Table A.5/4 TC reference: Initial condition: Stimulus and Expected Behaviour: 1) Tester sends downlink frame containin... |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 5.3 Test purposes for road side units | |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 5.3.1 Valid behaviour tests | TP/RSU/DLL/BV/01 Verify that the IUT correctly handles the abort sequence Reference: Clause 10.2.2.3 PICS Selection: Tables A.2/2 AND A.4/1 AND A.4/10 TC reference: Initial condition: Stimulus and Expected Behaviour: 1) Force the IUT to send a request to the tester upon which a reply is expected. 2) Tester sends uplink... |
56fcb18e9f90c0cca37ef6589ca5460d | 102 708-1-2 | 5.3.2 Invalid behaviour tests | TP/RSU/DLL/BI/01 Verify that the IUT ignores uplink frames with a length exceeding the maximum allowed length as defined by N3 Reference: Clause 10.2.2.1 and 10.2.2.4 PICS Selection: Tables A.5/1 AND A.5/5 TC reference: Initial condition: Stimulus and Expected Behaviour: 1) Force the IUT to send a request to the tester... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 1 Scope | The present document covers the minimum characteristics which are considered necessary for the terminal in order to provide compliance to ETSI TS 102 622 [1]. The present document specifies the test cases for: • the HCI core as described in the first part of ETSI TS 102 622 [1]; • the contactless platform as described ... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 2 References | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. • In the case of a reference... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. • In the case of a reference... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 3 Definition of terms, symbols and abbreviations | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 102 622 [1] and the following apply: allowed error response code: response code which is not ANY_OK and which is allowed for the referenced command as specified in ETSI TS 102 622 [1] non-occurrence RQ: RQ which has been extracted from ETSI TS 102 622... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 3.2 Symbols | For the purposes of the present document, the symbols given in ETSI TS 102 622 [1] and the following apply: PIPE0 the static pipe connected to the link management gate of the device under test PIPE1 the static pipe connected to the administration gate of the device under test ETSI ETSI TS 102 695-1 V13.0.0 (2019-04) 13... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 102 622 [1] and the following apply: (U)SIM (Universal) Subscriber Identity Module AC AntiCollision AFI Application Family Identifier AID Application IDentifier ATQA Answer To reQuest of type A ATQB Answer To reQuest of type B ATS Answer To Se... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 3.4 Void | Content of this clause has been moved to clause 3A. ETSI ETSI TS 102 695-1 V13.0.0 (2019-04) 14 Release 13 |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 3A Formats | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 3A.1 Format of the table of optional features | The columns in table 4.1 have the following meaning. Column Meaning Option The optional feature supported or not by the DUT. Status See clause 3A.3. Support The support columns shall be filled in by the supplier of the implementation. The following common notations, defined in ISO/IEC 9646-7 [9], are used for the suppo... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 3A.2 Format of the applicability table | The applicability of every test in table 4.2 is formally expressed by the use of Boolean expression defined in the following clause. The columns in table 4.2 have the following meaning. Column Meaning Clause The "Clause" column identifies the clause containing the test case referenced in the "Test case number and descr... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 3A.3 Status and Notations | The "Rel-x" columns show the status of the entries as follows: The following notations, defined in ISO/IEC 9646-7 [9], are used for the status column: M mandatory - the capability is required to be supported. O optional - the capability may be supported or not. N/A not applicable - in the given context, it is impossibl... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 3A.4 Format of the conformance requirements tables | The conformance requirements tables contained in the present document have the following format and meaning: Column Status Meaning Mandatory This mandatory column contains the conformance requirement number (e.g. RQ3). Optional This optional column is present when the containing clause sources conformance requirements ... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 4 Test environment | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 4.1 Table of optional features | The device supplier shall state the support of possible options in table 4.1. See clause 3A for the format of table 4.1. Table 4.1: Options Item Option Status Support Mnemonic 1 Data link layer specified in ETSI TS 102 613 [2] is used O O_102_613 2 Card RF gate for technology A is supported O O_CE_TypeA 3 Card RF gate ... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 4.2 Applicability table | Table 4.2 specifies the applicability of each test case to the device under test. See clause 3A for the format of table 4.2. Clause 4.5.2 should be referenced for usage of the execution requirements which are referenced in table 4.2 a) and described in table 4.2 c). Table 4.2 a): Applicability of tests Clause Test case... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.3.2 Test case 1: existence of gates | Rel-7 M M M M M M M |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.4.2 Test case 1: static pipe deletion | Rel-7 M M M M M M M 5.1.4.3 Test case 2: initial pipe state and persistence of pipe state and registry value Rel-7 TR1 M M M M M M M |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.5.2 Test case 1: registry deletion | Rel-7 SR1 M M M M M M M 5.2.2.2 Test case 1: commands/events on pipe which is not open Rel-7 M M M M M M M 5.3.1.2.3.2 Test case 1: ANY_OPEN_PIPE reception Rel-7 M M M M M M M 5.3.1.2.4.2 Test case 1: ANY_CLOSE_PIPE reception Rel-7 M M M M M M M |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.3.2.2 Test case 1: response to unknown command | Rel-7 M M M M M M M |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.3.3.2 Test case 1: reception of unknown events | Rel-7 M M M M M M M 5.4.2.1.1.2 Test case 1: SESSION_IDENTITY Rel-7 M M M M M M M 5.4.2.1.1.3 Test case 2: MAX_PIPE Rel-7 M M M M M M M 5.4.2.1.1.4 Test case 3: WHITELIST Rel-7 M M M M M M M 5.4.2.1.1.5 Test case 4: HOST_LIST Rel-7 M M M M M M M 5.4.2.1.1.6 Test case 5: EVT_HOT_PLUG - initial power- up Rel-12 N/A N/A N... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.5.4.2 Test case 1: inhibited state | Rel-7 M M M M M M M 5.5.4.3 Test case 2: inhibited state, followed by subsequent successful identity check Rel-7 M M M M M M M 5.5.4.4 Test case 3: initialization using all defined gates Rel-7 N/A N/A M M M M M |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.5.5.2 Test case 1: processing of EVT_POST_DATA | Rel-7 M M M M M M M ETSI ETSI TS 102 695-1 V13.0.0 (2019-04) 18 Release 13 Clause Test case number and description Release Execution requirements Rel-7 Terminal Rel-8 Terminal Rel-9 Terminal Rel-10 Terminal Rel-11 Terminal Rel-12 Terminal Rel-13 Terminal Support |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.6.1.2 Test case 1: RF gate of type A | Rel-7 TR2 C102 C102 C102 C102 C102 C102 C102 |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.6.1.3 Test case 2: RF gate of type B | Rel-7 TR2 C103 C103 C103 C103 C103 C103 C103 |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.6.1.4 Test case 3: RF gate of type F | Rel-7 TR2 N/A N/A C112 C112 C112 C112 C112 5.6.3.3.4.2.2 Test case 1: UID_REG - default Rel-7 TR2 C102 C102 C102 C102 C102 C102 C102 5.6.3.3.4.2.3 Test case 2: SAK Rel-7 TR2 C102 C102 C102 C102 C102 C102 C102 5.6.3.3.4.2.4 Test case 3: ATS - default parameters Rel-7 TR2 C102 C102 C102 C102 C102 C102 C102 5.6.3.3.4.2.5 ... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 4.3 Information to be provided by the device supplier | The device supplier shall provide the information indicated in table 4.3. Table 4.3: Default configuration Item Description Presence/Value Status Mnemonic 1 Void 2 Void 3 Void 4 Void 5 Void 6 Value of GATES_LIST M V_GATES_LIST 7 Value of MAX_PIPE M V_ MAX_PIPE 8 Value of HOST_LIST M V_ HOST_LIST 9 Maximum data rate sup... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 4.4 Test equipment | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 4.4.0 Base Requirements | The test equipment shall provide a host simulator which is connected to the DUT during test procedure execution, unless otherwise specified. With respect to the DUT, the host simulator shall act as a valid host according to ETSI TS 102 622 [1] unless otherwise specified. In particular, the host simulator shall ensure t... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 4.4.1 Measurement/setting uncertainties | Void. |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 4.4.2 Default conditions for DUT operation | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 4.4.2.1 General | Unless otherwise specified, the following applies during test procedure execution. The test equipment shall attempt to ensure that the identity check mechanism of the lower layer passes (see ETSI TS 102 622 [1], clause 8.4). If the test procedure indicates that the host simulator is to send ANY_OK in response to an ANY... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.