hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.4 Type F RF technology | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.4.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 9.4.4. RQ1 9.4.4 In the context of a valid contactless card application sequence as specified in ETSI TS 102 622 [1], and In case SWP as defined in ETSI TS 102 613 [2] is used as a data link layer, the initialization data exchange is performed using CLT as defined in ETSI TS 102 6... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.4.6 Test case 5: EVT_FIELD_OFF after EVT_FIELD_ON / SWP interface activation | 5.6.4.4.6.1 Test execution Void. 5.6.4.4.6.2 Initial conditions • The host controller simulator is configured to support only the Type F RF gate. • For full power mode execution: HCI session initialization has been performed, the HCI interface is idle and the SWP interface is not DEACTIVATED. • For low power mode execu... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.5 Update RF technology settings | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.5.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 9.4.5. There are no conformance requirements for the UICC for the referenced clause. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.6 Identity check | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.6.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 9.4.6. There are no conformance requirements for the UICC for the referenced clause. ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 80 Release 11 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7 Contactless reader | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.1 Overview | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.1.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 10.1. RQ1 For each reader RF gate it wants to use, the host has one reader application gate. RQ2 The host shall not create more than one pipe to each reader RF gate. RQ3 Rel-11 upwards If MAX_CURRENT present in the host, the host is allowed to consume a current up to the maximum d... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.2 Reader RF gates | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.2.1 Overview | Reference: ETSI TS 102 622 [1], clause 10.2.1. There are no conformance requirements for the UICC for the referenced clause. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.2.2 Command | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.2.2.1 WR_XCHG_DATA | 5.7.2.2.1.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 10.2.2.1. RQ1 The host shall have at least one byte in parameter of WR_XCHG_DATA. RQ2 In the CTR field of WR_XCHG_DATA, bit b8 to b6 shall set to 0. RQ3 In the CTR field of WR_XCHG_DATA, if bit b5 is set to one, the host shall use timeout value... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.2.3 Registries | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.2.3.1 Type A reader RF gate | 5.7.2.3.1.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 10.2.3.1. ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 81 Release 11 RQ1 The host shall adhere to the access condition of RO for UID. RQ2 The host shall adhere to the access condition of RO for ATQA. RQ3 The host shall adhere to the access conditio... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.2.3.2 Type B reader RF gate | 5.7.2.3.2.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 10.2.3.2. RQ1 The host shall adhere to the access condition of RO for PUPI. RQ2 The host shall adhere to the access condition of RO for APPICATION_DATA. RQ3 The host shall adhere to the access condition of RO for HIGHER_LAYER_RESPONSE. RQ4 Rel-... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.2.4 Events and subclauses | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.2.4.1 Events | 5.7.2.4.1.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 10.2.4. There are no conformance requirements for the UICC for the referenced clause. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.2.4.2 EVT_READER_REQUESTED | 5.7.2.4.2.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 10.2.4.1. RQ1 When the host sends EVT_READER_REQUESTED, it shall contain no parameters. NOTE: Development of test cases for above listed RQs is FFS. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.2.4.3 EVT_END_OPERATION | 5.7.2.4.3.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 10.2.4.2. There are no conformance requirements for the UICC for the referenced clause. ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 82 Release 11 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.2.5 Responses | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.2.5.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 10.2.5. There are no conformance requirements for the UICC for the referenced clause. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.3 Reader application gates | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.3.1 Overview | Reference: ETSI TS 102 622 [1], clause 10.3.1. There are no conformance requirements for the UICC for the referenced clause. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.3.2 Command | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.3.2.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 10.3.2. There are no conformance requirements for the UICC for the referenced clause. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.3.3 Registry | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.3.3.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 10.3.3. RQ1 Registry parameters which are in the range reserved for usage by ETSI TS 102 622 [1] but which are not defined in ETSI TS 102 622 [1] shall not be present in the registry. NOTE: Development of test cases for above listed RQs is FFS. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.3.4 Events and subclauses | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.3.4.1 Events | 5.7.3.4.1.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 10.3.4. RQ1 The reader application gates support the event name EVT_TARGET_DISCOVERED. RQ2 Rel-11 upwards The reader application gates support the event name EVT_READER_STATUS. NOTE: Development of test cases for above listed RQs is FFS. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.3.4.2 EVT_TARGET_DISCOVERED | 5.7.3.4.2.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 10.3.4.1. There are no conformance requirements for the UICC for the referenced clause. ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 83 Release 11 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.3.4.3 EVT_READER_STATUS | 5.7.3.4.3.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 10.3.4.2. There are no conformance requirements for the UICC for the referenced clause. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.4 Procedures | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.4.1 Use of contactless reader application | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.4.1.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 10.4.1. RQ1 The host shall send the EVT_READER_REQUESTED event on a single pipe only. RQ2 In the context of a valid contactless reader application sequence as specified in ETSI TS 102 622 [1], the host shall only send WR_XCHG_DATA commands after receiving an EVT_TARGET_DISCOVERED ... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.4.2 Contactless reader not available | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.4.2.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 10.4.2. There are no conformance requirements for the UICC for the referenced clause. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.4.3 Error management | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.7.4.3.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 10.4.3. There are no conformance requirements for the UICC for the referenced clause. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8 Connectivity | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.1 Overview | Reference: ETSI TS 102 622 [1], clause 11.1. There are no conformance requirements for the Host for the referenced clause. ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 84 Release 11 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.2 Connectivity gate and subclauses | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.2.1 Connectivity gate | Reference: ETSI TS 102 622 [1], clause 11.2. There are no conformance requirements for the Host for the referenced clause. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.2.2 Commands | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.2.2.1 PRO_HOST_REQUEST | 5.8.2.2.1.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 11.2.1.1. RQ1 The Host shall not try to interact with any other host except the host controller before receiving the response of PRO_HOST_REQUEST. RQ2 The Host shall not try to interact with another host if the response of PRO_HOST_REQUEST is n... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.2.3 Events and subclauses | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.2.3.1 Events | Reference: ETSI TS 102 622 [1], clause 11.2.2. There are no conformance requirements for the Host for the referenced clause. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.2.3.2 EVT_CONNECTIVITY | 5.8.2.3.2.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 11.2.2.1. RQ1 When the Host sends EVT_CONNECTIVITY, it shall contain no parameters. NOTE: Development of test cases for above listed RQs is FFS. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.2.3.3 Void | Reference: ETSI TS 102 622 [1], clause 11.2.2.2. There are no conformance requirements for the Host for the referenced clause. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.2.3.4 EVT_OPERATION_ENDED | 5.8.2.3.4.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 11.2.2.3. RQ1 When the Host send EVT_OPERATION_ENDED, it shall not contain parameters. RQ2 The Host shall only EVT_OPERATION_ENDED in the context of a PRO_HOST_REQUEST command. NOTE: Development of test cases for above listed RQs is FFS. ETSI E... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.2.3.5 EVT_TRANSACTION | 5.8.2.3.5.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 11.2.2.4. RQ1 When the Host sends the EVT_TRANSACTION, it shall use BER-TLV parameters as defined in ETSI TS 102 622 [1]. NOTE: Development of test cases for above listed RQs is FFS. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.2.4 Registry | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.2.4.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 11.2.3. RQ1 Registry parameters which are in the range reserved for usage by ETSI TS 102 622 [1] but which are not defined in ETSI TS 102 622 [1] shall not be present in the registry. NOTE: Development of test cases for above listed RQs is FFS. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.3 Connectivity application gate and subclauses | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.3.1 Connectivity application gate | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.3.1.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 11.3. There are no conformance requirements for the Host for the referenced clause. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.3.2 Commands | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.3.2.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 11.3.1. There are no conformance requirements for the Host for the referenced clause. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.3.3 Events and subclauses | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.3.3.1 Events | 5.8.3.3.1.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 11.3.2. There are no conformance requirements for the Host for the referenced clause. ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 86 Release 11 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.3.3.2 EVT_STANDBY | 5.8.3.3.2.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 11.3.2.1. RQ1 When the Host receives the EVT_STANDBY, it shall stop any ongoing communication with the other hosts and the host controller within 100 ms. NOTE: Development of test cases for above listed RQs is FFS. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.3.4 Registry | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.3.4.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 11.3.3. There are no conformance requirements for the Host for the referenced clause. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.4 Procedures | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.8.4.1 Use of connectivity gate | Reference: ETSI TS 102 622 [1], clause 11.4.1. There are no conformance requirements for the Host for the referenced clause. ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 87 Release 11 Annex A (normative): Additional test cases A.1 Overview The annex provides test cases that can only be implemented in a standardized way if ... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-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) Application Layer. The objective of the present document is to provide a basis for conformance tests for DSRC-HDR equipment specified in ETSI ES 200 674-1 [1] g... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 2 References | |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 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. Referenced documents which a... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 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. NOTE: While any hyperlinks i... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 3 Definitions and abbreviations | |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI ES 200 674-1 [1] and ISO/IEC 9646-1 [3] apply. |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI ES 200 674-1 [1] and ISO/IEC 9646-1 [3] apply. |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 4 Test Suite Structure | |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 4.1 Structure | Table 1 shows the application layer test suite structure (TSS) including its groups defined for the conformance testing. Table 1: Test suite structure for DSRC-HDR application layer Group Type of system under test (SUT) Behaviour Kernel unit On Board Unit Valid behaviour Invalid behaviour Road Side Unit Valid behaviour... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 4.2 Test groups | There are six test groups defined for the application layer of DSRC-HDR as presented in table 1. |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-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). ETSI ETSI TS 102 708-2-2 V1.5.1 (2018-08) 7 |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 4.4 Behaviour test groups | |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-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. |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-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). |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5 Test purposes | |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.1 Introduction | |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-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 ... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.1.2 Naming conventions | The identifier of the TP is built according to table 3. ETSI ETSI TS 102 708-2-2 V1.5.1 (2018-08) 8 Table 3: TP naming convention Identifier TP/<sut>/<layer>/<group>/<x>/<n> <sut> = Type of SUT OBU On Board Unit RSU Road Side Unit <layer> AL Application Layer <group> KU Kernel Unit RA Read Access WA Write Access OF Opt... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.1.3 Sources of TP definitions | All TPs are specified according to the base standard ETSI ES 200 674-1 [1]. |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.1.4 General reference | All references in the test purposes, if not stated differently, are indicating clauses of the base standard ETSI ES 200 674-1 [1]. All references to PICS are indicating tables in ETSI TS 102 708-2-1 [2]. |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-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 SUT (OBU) shall be ready for communication, i.e. it shall not be in sleep mode and all boot processes shall be finalized. • The "AP Invocation Identifier" used in the SUT shall be as defined by the ... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-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, A.3, A.5/1, A.5/2, A5/3 and A.5/7 of the PICS [2] shall be implicitly selected for all TPs. ETSI ETSI TS 102 708-2-2 V1.5.1 (2018-08) 9 For all TPs related to RSUs the following PICS sel... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.1.7 Presentation conventions | Concatenation of directives in a single frame shall be indicated with the symbol |. EXAMPLE: Concatenation of Open-Rq with Close-Rq is presented as Open-Rq | Close-Rq, with Open-Rq sent first. |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.2 Test purposes for on-board units | |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.2.1 Kernel Unit | |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.2.1.1 Valid behaviour | TP/OBU/AL/KU/BV/01 Verify that the IUT can handle Open-Rq Reference: Clauses 11.5.2, 11.5.3, 11.6.1, 11.6.2, 11.6.3 and 11.6.4 PICS Selection: Table A.4/1 AND Table A.4/2 AND 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 rece... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.2.1.2 Invalid behaviour | TP/OBU/AL/KU/BI/01 Verify that the IUT can manage Select-TBA-Id-Rq with an invalid length Reference: Clauses 11.5.4, 11.6.1, 11.6.2 and 11.6.5 PICS Selection: Table A.4/5 AND Table A.4/6 Initial conditions with { the IUT being in the "initial state" and the IUT having received a valid Open-Rq | Close-Rq with new privat... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.2.2 Read access | |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.2.2.1 Valid behaviour | TP/OBU/AL/RA/BV/01 Verify that the IUT can manage Open-Rq | Read-Master-Core-Rq | Close-Rq Reference: Clauses 11.5.6, 11.6.2 and 11.6.7 PICS Selection: Table A.4/9 AND Table A.4/10 Initial conditions with { the IUT being in the "initial state" } Expected behaviour ensure that { repeat with different private LinkID and ... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.2.2.2 Invalid behaviour | TP/OBU/AL/RA/BI/01 Verify that the IUT can manage reception of Get-Master-Record-Rq outside a session Reference: Clauses 11.5.7, 11.6.2 and 11.6.8 PICS Selection: Table A.4/11 AND Table A.4/12 Initial conditions with { the IUT being in the "initial state" } Expected behaviour ensure that { when { the IUT receives a val... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.2.3 Write Access | |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.2.3.1 Valid behaviour | TP/OBU/AL/WA/BV/01 Verify that the IUT can manage Open-Rq | Select-TBA-Id-Rq | Write-Appl-Core-Rq | Close- Rq with no restrictions due to EETS profile and with no support for security level 1 Reference: Clauses 11.5.9, 11.6.2, 11.6.10 PICS Selection: Table A.4/15 AND Table A.4/16 AND NOT (Table A.2/1 OR Table A.2/3) In... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.2.3.2 Invalid behaviour | TP/OBU/AL/WA/BI/01 Verify that the IUT can manage a sequence Open-Rq | Select-TBA-Id-Rq | Write-Appl-Core- Rq | Close-Rq that violates the restrictions due to EETS profile and no support for security level 1 Reference: Clauses 11.5.9, 11.6.2, 11.6.10 and D.2.2 PICS Selection: Table A.4/15 AND Table A.4/16 AND Table A.2... |
b88c487d5ab776ee8c1bab8ab9a53d7a | 102 708-2-2 | 5.2.4 Optional functionality |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.