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.1.2 Test case 1: full power mode | Rel-7 SR6 C107 C107 C107 C107 C107 5.6.4.1.3 Test case 2: full power mode, no EVT_CARD_ACTIVATED and EVT_CARD_DEACTIVATED Rel-7 SR6 C107 C107 C107 C107 C107 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.1.4 Test case 3: sequence from DEACTIVATED state | Rel-7 SR6 C107 C107 C107 C107 C107 5.6.4.1.5 Test case 4: sequence from DEACTIVATED state, no EVT_CARD_ACTIVATED or EVT_CARD_DEACTIVATED Rel-7 SR6 C107 C107 C107 C107 C107 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.1.6 Test case 5: low power, power down instead of EVT_FIELD_OFF | Rel-7 SR6 C107 C107 C107 C107 C107 5.6.4.1.7 Test case 6: EVT_FIELD_OFF after EVT_FIELD_ON / SWP interface activation Rel-7 SR6 C107 C107 C107 C107 C107 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.1.8 Test case 7: EVT_FIELD_OFF after EVT_CARD_ACTIVATED | Rel-7 SR6 C107 C107 C107 C107 C107 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.1.9 Test case 8: EVT_FIELD_OFF after EVT_SEND_DATA | Rel-7 SR6 C107 C107 C107 C107 C107 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.1.10 Test case 9: multiple open card gates | Rel-7 SR6 C108 C108 C108 C108 C108 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.1.11 Test case 10: empty C-APDU | Rel-7 SR6 C107 C107 C107 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.2.2 Test case 1: full power mode | Rel-7 SR7 N/A N/A N/A C109 C109 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.2.3 Test case 2: sequence from DEACTIVATED state | Rel-7 SR7 N/A N/A N/A C109 C109 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.2.4 Test case 3: low power mode, power down instead EVT_FIELD_OFF | Rel-7 SR7 N/A N/A N/A C109 C109 5.6.4.2.5 Test case 4: EVT_FIELD_OFF after EVT_FIELD_ON / SWP interface activation Rel-7 SR7 N/A N/A N/A C109 C109 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.2.6 Test case 5: EVT_FIELD_OFF during CLT frames exchange | Rel-7 SR7 N/A N/A N/A C109 C109 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.2.7 Test case 6: multiple open card gates | Rel-7 SR7 N/A N/A N/A C110 C110 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.4.2 Test case 1: RF error indicator | Rel-7 SR9 C106 C106 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.4.3 Test case 2: full power mode | Rel-7 SR9 C106 C106 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.4.4 Test case 3: sequence from DEACTIVATED state | Rel-7 SR9 C106 C106 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.4.5 Test case 4: low power, power down instead of EVT_FIELD_OFF | Rel-7 SR9 C106 C106 5.6.4.4.6 Test case 5: EVT_FIELD_OFF after EVT_FIELD_ON / SWP interface activation Rel-7 SR9 C106 C106 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.4.7 Test case 6: EVT_FIELD_OFF after EVT_SEND_DATA | Rel-7 SR9 C106 C106 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.4.8 Test case 7: multiple open card gates | Rel-7 SR9 C111 C111 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.6.4.4.9 Test case 8: EVT_FIELD_OFF during CLT frames exchange | Rel-7 SR9 C106 C106 ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 19 Release 11 Table 4.2 b): Conditional items referenced by table 4.2 a) Conditional item Condition Description C101 IF 4.1/1 THEN M ELSE N/A O_LINK_MAN C102 IF 4.1/2 THEN M ELSE N/A O_WHITELIST_NON_EMPTY C103 IF 4.1/3 THEN M ELSE N/A O_102_613 C104 IF 4.1/5 ... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 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 Indication of presence of VERSION_SW, and value if supported. M V_VERSION_SW 2 Indication of presence of VERSION_HARD, and value if supported. M V_VERSION_HARD 3 I... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 4.4 Test equipment | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 4.4.0 Base Requirements | The test equipment shall provide a host controller simulator which is connected to the DUT during test procedure execution, unless otherwise specified. For test cases which require a further host to be present, the test equipment shall further provide a host simulator which is connected to the DUT via the host controll... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 4.4.1 Measurement/setting uncertainties | Void. ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 22 Release 11 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 4.4.2 Default conditions for DUT operation | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 4.4.2.1 General | Unless otherwise specified, the test equipment shall apply the default conditions described in the following clauses during test procedure execution. The test equipment shall treat the identity check mechanism of the lower layer as having passed (see ETSI TS 102 622 [1], clause 8.4). The test equipment shall use the sa... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 4.4.2.2 Status of UICC interfaces | If the data link layer in ETSI TS 102 613 [2] is used and the DUT is a UICC, the terminal simulator shall not activate the ETSI TS 102 221 [7] interface or the ETSI TS 102 600 [8] interface. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 4.4.3 Minimum/maximum conditions for DUT operation | Void. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 4.4.4 Conventions | Unless otherwise specified, ADM_NOTIFY_PIPE_CREATED is sent by the test equipment with source HID = HID of host controller, destination HID = HID of host and a currently unused PID. If the pipe for a response is not explicitly specified, then the pipe for the response is required to be the pipe on which the preceding c... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 4.5 Test execution | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 4.5.1 Parameter variations | Unless otherwise specified, when the data link layer in ETSI TS 102 613 [2] is used, all tests shall be carried out once for each of following parameter variations in addition to the parameter variations specified individually for each test case. Table 4.5.1: Global parameter variations Voltage class and power mode Vcc... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 4.5.2 Execution requirements | Table 4.2, "Applicability of tests", specifies "execution requirements" for several test cases. For these test cases, it has not been possible to specify the corresponding test procedure in such a way that it can be guaranteed that the test procedure can be executed against every possible DUT. ETSI ETSI TS 102 695-2 V1... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 4.6 Pass criterion | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 4.6.0 Principle | A test shall only be considered as successful, if the test procedure was carried out successfully under all parameter variations with the DUT respecting all conformance requirements referenced in the test procedure. This is subject to the additional qualifications described in clause 4.6.1. NOTE: Within the test proced... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 4.6.1 Unanticipated behaviour from the DUT | In the specification of the test procedures, every attempt has been made to ensure that the interface between the simulator and the DUT is in a known state before and during test procedure execution. However, as the DUT is an autonomous device, it is not possible to fully guarantee this. If the DUT unexpectedly closes ... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5 Test cases | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1 HCI architecture | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.1 Overview | Reference: ETSI TS 102 622 [1], clause 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) 24 Release 11 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.2 Hosts | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.2.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 4.2. RQ1 A host shall not use host identifiers which are RFU. RQ2 A host shall reject received host identifiers which are RFU. NOTE: RQ1 is a non-occurrence RQ. 5.1.2.2 Test case 1: processing of RFU host identifier |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.2.2.1 Test execution | The test procedure shall be executed once for each of following parameters: • Source HID values of: every HID value which is RFU as defined in ETSI TS 102 622 [1]. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.2.2.2 Initial conditions | • The HCI interface is idle; i.e. no further communication is expected. • PIPE1 is open. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.2.2.3 Test procedure | Step Direction Description RQ 1 HCS HUT Send ADM_NOTIFY_PIPE_CREATED on PIPE1, with the specified source HID, source GID = '01' and destination GID = GID of loop back gate. 2 HUT HCS Send response containing an allowed error response code for the command. RQ2 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.3 Gates | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.3.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 4.3. RQ1 All hosts shall have one administration gate. RQ2 All hosts shall have one identity management gate. RQ3 All hosts shall have one loop back gate. RQ4 A host shall not use gate identifiers which are RFU. RQ5 Void. RQ6 A host shall not use gate identifiers which are host sp... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.3.2.1 Test execution | Void. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.3.2.2 Initial conditions | • The HCI interface is idle; i.e. no further communication is expected. ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 25 Release 11 • PIPE1 is open. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.3.2.3 Test procedure | Step Direction Description RQ 1 HCS HUT Send ADM_NOTIFY_PIPE_CREATED on PIPE1, with source and destination GID = GID of identity management gate; designate the created pipe PIPE_ID_MAN. 2 HUT HCS Send ANY_OK (parameters are not checked). RQ1, RQ2 3 HCS HUT Send ANY_OPEN_PIPE on PIPE_ID_MAN. 4 HUT HCS Send ANY_O... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.3.3 Void | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.4 Pipes | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.4.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 4.4. RQ1 A host shall not attempt to delete a static pipe. RQ2 A host shall reject any attempts to delete a static pipe. RQ3 The state of a pipe (i.e. open or closed) shall remain persistent if the hosts are powered down and up again. RQ4 The state of a dynamic pipe after creation... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.4.2.1 Test execution | Void. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.4.2.2 Initial conditions | • The HCI interface is idle; i.e. no further communication is expected. • PIPE1 is open. ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 26 Release 11 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.4.2.3 Test procedure | Step Direction Description RQ 1 HCS HUT Send ADM_NOTIFY_PIPE_DELETED(PIPE1) on PIPE1. 2 HUT HCS Send response containing an allowed error response code for the command. RQ2 5.1.4.3 Test case 2: static pipe deletion - link management gate |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.4.3.1 Test execution | Void. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.4.3.2 Initial conditions | • The HCI interface is idle; i.e. no further communication is expected. • PIPE1 is open. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.4.3.3 Test procedure | Step Direction Description RQ 1 HCS HUT Send ADM_NOTIFY_PIPE_DELETED(PIPE0) on PIPE1. 2 HUT HCS Send response containing an allowed error response code for the command. RQ2 5.1.4.4 Test case 3: persistence of pipe state |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.4.4.1 Test execution | Void. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.4.4.2 Initial conditions | • The HCI interface is idle; i.e. no further communication is expected. • PIPE1 is open. • A pipe (PIPE_ID_MAN) has been created to the host's identity management gate, and is open. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.4.4.3 Test procedure | Step Direction Description RQ 1 HCS HUT Send ADM_NOTIFY_PIPE_CREATED on PIPE1, with source GID = '01' and destination GID = GID of the loop back gate; designate the created pipe PIPE_LOOP_BACK. 2 HUT HCS Send ANY_OK (parameters are not checked). 3 HCS HUT Power down host. 4 HCS HUT Power up host, and proceed un... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.4.5.1 Test execution | Void. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.4.5.2 Initial conditions | • The HCI interface is idle; i.e. no further communication is expected. • PIPE1 is open. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.4.5.3 Test procedure | Step Direction Description RQ 1 HCS HUT Send ADM_NOTIFY_PIPE_CREATED on PIPE1, with source GID = '00' and destination GID = GID of identity management gate; designate the created pipe PIPEx. 2 HUT HCS Send ANY_OK (parameters are not checked). 3 HCS HUT Send ANY_GET_PARAMETER(GATES_LIST) on PIPEx. 4 HUT HCS Send... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.5 Registries | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.5.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 4.5. RQ1 For all gates defined in ETSI TS 102 622 [1], parameter identifiers in the range of '00' to 'EF' are reserved for use in ETSI TS 102 622 [1]. RQ2 A new instance of the registry is created for every pipe that connects to the gate. RQ3 Upon pipe creation all registry parame... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.5.2 Void | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.5.3 Void | ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 28 Release 11 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.2 HCP | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.2.1 HCP packets | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.2.1.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 5.1. RQ1 All hosts shall use the correct structure for transmitted HCP packets. RQ2 All hosts shall recognize correctly structured received HCP packets. RQ3 The destination host forwards the packet to the destination gate. NOTE 1: RQ1 and RQ2 are implicitly tested by the testing o... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.2.2 HCP message structure | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.2.2.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 5.2. RQ1 All hosts shall use the correct structure for transmitted HCP messages. RQ2 Type value 3 shall not be used. RQ3 All hosts shall recognize correctly structured received HCP messages. RQ4 A gate shall only accept a command or an event on a pipe when the state of that pipe i... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.2.2.2.1 Test execution | Void. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.2.2.2.2 Initial conditions | • The HCI interface is idle; i.e. no further communication is expected. • PIPE1 is open. ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 29 Release 11 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.2.2.2.3 Test procedure | Step Direction Description RQ 1 HCS HUT Send ADM_NOTIFY_PIPE_CREATED on PIPE1, with source and destination GID = GID of identity management gate; designate the created pipe PIPE_ID_MAN. 2 HUT HCS Send ANY_OK (parameters are not checked). 3 HCS HUT Send ANY_GET_PARAMETER(GATES_LIST) on PIPE_ID_MAN. 4 HUT HCS Sen... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.2.3 Message fragmentation | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.2.3.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 5.3. RQ1 Message fragmentation shall be used when the size of the message is larger than supported by the underlying data link layer. RQ2 Messages shall be fragmented according to the rules specified in ETSI TS 102 622 [1]. RQ3 The destination gate is responsible for rebuilding th... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3 Instructions | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.1 Commands | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.1.1 Overview | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.1.1.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 6.1.1. RQ1 For all gates, hosts shall not use RFU instruction values ('05' to '0F') in commands. RQ2 For administration gates, hosts shall not use RFU instruction values ('16' to '3F') in commands. RQ3 For gates defined in ETSI TS 102 622 [1], hosts shall not use instruction value... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.1.2 Generic commands | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.1.2.1 ANY_SET_PARAMETER | 5.3.1.2.1.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 6.1.2.1. RQ1 A host shall reject an incorrectly formatted ANY_SET_PARAMETER command. RQ2 A host shall reject an ANY_SET_PARAMETER command if the access right for the parameter does not allowed writing (i.e. is not RW or WO). RQ3 A host shall no... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.1.2.2 ANY_GET_PARAMETER | 5.3.1.2.2.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 6.1.2.2. RQ1 A host shall reject an incorrectly formatted ANY_GET_PARAMETER command. RQ2 A host shall reject an ANY_GET_PARAMETER command if the access right for the parameter does not allowed reading (i.e. is not RW or RO). RQ3 A host shall no... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.1.2.3 ANY_OPEN_PIPE | 5.3.1.2.3.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 6.1.2.3. RQ1 A host shall reject an incorrectly formatted ANY_OPEN_PIPE command. RQ2 When a host other than the host controller receives a valid ANY_OPEN_PIPE command on a closed pipe, it shall open the pipe and return ANY_OK with a parameter c... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.1.2.4 ANY_CLOSE_PIPE | 5.3.1.2.4.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 6.1.2.4. RQ1 A host shall reject an incorrectly formatted ANY_CLOSE_PIPE command. RQ2 When a host receives a valid ANY_CLOSE_PIPE on an open pipe, it shall close the pipe and respond with ANY_OK and no parameters. RQ3 When a host sends an ANY_C... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.1.3 Administration commands | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.1.3.1 ADM_CREATE_PIPE | 5.3.1.3.1.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 6.1.3.1. NOTE: All conformance requirements for the referenced clause are included in clause 5.5.1.1 of the present document. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.1.3.2 ADM_NOTIFY_PIPE_CREATED | 5.3.1.3.2.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 6.1.3.2. NOTE: All conformance requirements for the referenced clause are included in clause 5.5.1.1 of the present document. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.1.3.3 ADM_DELETE_PIPE | 5.3.1.3.3.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 6.1.3.3. NOTE: All conformance requirements for the referenced clause are included in clause 5.5.1.2 of the present document. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.1.3.4 ADM_NOTIFY_PIPE_DELETED | 5.3.1.3.4.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 6.1.3.4. ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 35 Release 11 NOTE: All conformance requirements for the referenced clause are included in clause 5.5.1.2 of the present document. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.1.3.5 ADM_CLEAR_ALL_PIPE | 5.3.1.3.5.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 6.1.3.5. NOTE: All conformance requirements for the referenced clause are included in clause 5.5.1.3 of the present document. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.1.3.6 ADM_NOTIFY_ALL_PIPE_CLEARED | 5.3.1.3.6.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 6.1.3.6. NOTE: All conformance requirements for the referenced clause are included in clause 5.5.1.3 of the present document. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.2 Responses | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.2.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 6.2. RQ1 A response shall be sent to all commands received even to those unknown to the receiving gate. RQ2 Responses received out of order (i.e. if no command was sent previously) shall be discarded. RQ3 For a received command which is defined in table 16 in ETSI TS 102 622 [1], ... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.2.2.1 Test execution | Void. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.2.2.2 Initial conditions | • The HCI interface is idle; i.e. no further communication is expected. • PIPE1 is open. • A pipe (PIPE_ID_MAN) has been created to the host's identity management gate and is open. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.2.2.3 Test procedure | Step Direction Description RQ 1 HCS HUT Send command with an RFU instruction value on PIPE1. 2 HUT HCS Send response (contents are not checked). RQ1 3 HCS HUT Send command with an RFU instruction value on PIPE_ID_MAN. 4 HUT HCS Send response (contents are not checked). RQ1 ETSI ETSI TS 102 695-2 V11.0.0 (2019-0... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.2.3.1 Test execution | Void. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.2.3.2 Initial conditions | • The HCI interface is idle; i.e. no further communication is expected. • A pipe (PIPE_ID_MAN) has been created to the host's identity management gate and is open. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.2.3.3 Test procedure | Step Direction Description RQ 1 HCS HUT Send ANY_GET_PARAMETER(GATES_LIST) on PIPE_ID_MAN. 2 HUT HCS Send response with ANY_OK and value of GATES_LIST on PIPE_ID_MAN. 3 HCS HUT Send response with ANY_OK and no parameters on PIPE_ID_MAN. 4 HUT No message on PIPE_ID_MAN. RQ2 5 HCS HUT Send ANY_GET_PARAMETER(GATES... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.