hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 4.4.2.2 Status of UICC interfaces | Void. |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 4.4.3 Minimum/maximum conditions for DUT operation | Void. |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 4.4.4 Conventions | Unless otherwise specified, ADM_CREATE_PIPE is sent by the test equipment with source HID = HID of host simulator and destination HID = HID of host controller. 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 command was sent. |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 4.5 Test execution | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 4.5.1 Parameter variations | Unless otherwise specified, all test cases shall be carried out in full power mode only, and for the parameter variations specified individually for each test case. ETSI ETSI TS 102 695-1 V13.0.0 (2019-04) 22 Release 13 |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 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. Some sample scenarios of te... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 4.6 Pass criterion | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 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... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 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 ... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5 Test cases | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1 HCI architecture | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.1 Overview | Reference: ETSI TS 102 622 [1], clause 4.1. There are no conformance requirements for the terminal for the referenced clause. |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.2 Hosts | Reference: ETSI TS 102 622 [1], clause 4.2. RQ4.1 The host controller shall not use host identifiers which are RFU. RQ4.2 The host controller shall reject received host identifiers which are RFU. RQ4.28 Rel-12 upwards The dynamically allocated range of values shall be used by the host controller to assign a host identi... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.3 Gates | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.3.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 4.3. RQ4.3 The host controller shall have one administration gate. RQ4.4 The host controller shall have one link management gate. RQ4.5 The host controller shall have one identity management gate. RQ4.6 The host controller shall have one loop back gate. RQ4.7 The host controller s... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.3.2.1 Test execution | There are no test case-specific parameters for this test case. |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.3.2.2 Initial conditions | • The HCI interface is idle; i.e. no further communication is expected. • PIPE0 is open. ETSI ETSI TS 102 695-1 V13.0.0 (2019-04) 24 Release 13 • PIPE1 is open. |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.3.2.3 Test procedure | Step Direction Description RQ 1 HS HCUT Send ANY_GET_PARAMETER(REC_ERROR) on PIPE0. 2 HCUT HS Send ANY_OK (parameters are not checked). RQ4.4 3 HS HCUT Send ADM_CREATE_PIPE on PIPE1, with source and destination GID = GID of identity management gate. 4 HCUT HS Send ANY_OK (parameters are not checked); designate ... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.3.3 Void | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.4 Pipes | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.4.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 4.4. RQ4.11 The host controller shall not attempt to delete a static pipe. RQ4.12 The host controller shall reject any attempts to delete a static pipe. RQ4.13 The state of a pipe (i.e. open or closed) shall remain persistent if the hosts are powered down and up again. RQ4.14 The ... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.4.2.1 Test execution | The test procedure shall be executed once for each of following parameters: • PIPE0. • PIPE1. |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.4.2.2 Initial conditions | • The HCI interface is idle; i.e. no further communication is expected. • PIPE1 is open. |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.4.2.3 Test procedure | Step Direction Description RQ 1 HS HCUT Send ADM_DELETE_PIPE containing the pipe indicated in the test execution clause, on PIPE1. 2 HCUT HS Send response containing an allowed error response code for the command. RQ4.12 |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.4.3 Test case 2: initial pipe state and persistence of pipe state and registry value | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.4.3.1 Test execution | There are no test case-specific parameters for this test case. |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.4.3.2 Initial conditions | • The HCI interface is idle; i.e. no further communication is expected. • PIPE1 is open. • The value of SESSION_IDENTITY in the registry is not 'FFFFFFFFFFFFFFFF'. |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.4.3.3 Test procedure | Step Direction Description RQ 1 HS HCUT Send ADM_CREATE_PIPE on PIPE1, with source GID = 'EE' and destination GID = GID of the loop back gate. 2 HCUT HS Send ANY_OK (parameters are not checked); designate the created pipe PIPE_LOOP_BACK. 3 HS HCUT Open PIPE on PIPE_LOOP_BACK. 4 HCUT HS Send ANY_OK. 5 HS HCUT ... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.5 Registries | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.5.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 4.5. RQ4.21 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]. RQ4.22 A new instance of the registry is created for every pipe that connects to the gate. RQ4.23 Upon pipe creation all regist... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.5.2.1 Test execution | Assignment of terms to entities referenced in SR1: GID of gate = GATE_X, registry parameter identifier = REG_PARAM. There are no test case-specific parameters for this test case. |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.5.2.2 Initial conditions | • The HCI interface is idle; i.e. no further communication is expected. • PIPE1 is open. ETSI ETSI TS 102 695-1 V13.0.0 (2019-04) 27 Release 13 |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.1.5.2.3 Test procedure | Step Direction Description RQ 1 HS HCUT Send ADM_CREATE_PIPE on PIPE1, with source GID = 'EE' and destination GID = GATE_X. 2 HCUT HS Send ANY_OK (parameters are not checked); designate the created pipe PIPEa. 3 HS HCUT Send ANY_OPEN_PIPE on PIPEa. 4 HCUT HS Send ANY_OK. 5 HS HCUT Send ANY_SET_PARAMETER(REG_P... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.2 HCP | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.2.1 HCP packets | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.2.1.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 5.1. RQ5.1 The host controller shall use the correct structure for transmitted HCP packets. RQ5.2 The host controller shall recognize correctly structured received HCP packets. RQ5.3 When receiving a packet, the host controller as destination host forwards the packet to the destin... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.2.2 HCP message structure | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.2.2.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 5.2. RQ5.6 The host controller shall use the correct structure for transmitted HCP messages. RQ5.7 Type value 3 shall not be used. RQ5.8 The host controller shall recognize correctly structured received HCP messages. RQ5.9 A gate shall only accept a command or an event on a pipe w... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.2.2.2 Test case 1: commands/events on pipe which is not open | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.2.2.2.1 Test execution | There are no test case-specific parameters for this test case. |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.2.2.2.2 Initial conditions | • The HCI interface is idle; i.e. no further communication is expected. • PIPE1 is open. |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.2.2.2.3 Test procedure | Step Direction Description RQ 1 HS HCUT Send ADM_CREATE_PIPE on PIPE1, with source and destination GID = GID of identity management gate. 2 HCUT HS Send ANY_OK (parameters are not checked); designate the created pipe PIPE_ID_MAN. 3 HS HCUT Send ANY_OPEN_PIPE on PIPE_ID_MAN. 4 HCUT HS Send ANY_OK. 5 HS HCUT Se... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.2.3 Message fragmentation | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.2.3.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 5.3. RQ5.11 Message fragmentation shall be used when the size of the message is larger than supported by the underlying data link layer. RQ5.12 Messages shall be fragmented according to the rules specified in ETSI TS 102 622 [1]. RQ5.13 The destination gate is responsible for rebu... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.3 Instructions | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.3.1 Commands | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.3.1.1 Overview | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.3.1.1.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 6.1.1. RQ6.1 For all gates, the host controller shall not use RFU instruction values ('05' to '0F') in commands. RQ6.2 For administration gates, the host controller shall not use RFU instruction values ('16' to '3F') in commands. RQ6.3 For gates defined in ETSI TS 102 622 [1], the... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.3.1.2 Generic commands | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 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. RQ6.4 The host controller shall reject an incorrectly formatted ANY_SET_PARAMETER command with an allowed error response code. RQ6.5 The host controller shall reject an ANY_SET_PARAMETER command if the access right for the parameter do... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 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. RQ6.9 The host controller shall reject an incorrectly formatted ANY_GET_PARAMETER command with an allowed error response code. RQ6.10 The host controller shall reject an ANY_GET_PARAMETER command if the access right for the parameter d... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 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. RQ6.14 The host controller shall reject an incorrectly formatted ANY_OPEN_PIPE command. RQ6.15 When the host controller receives a valid ANY_OPEN_PIPE command on a closed pipe, it shall open the pipe and return ANY_OK without any param... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 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. RQ6.18 The host controller shall reject an incorrectly formatted ANY_CLOSE_PIPE command. RQ6.19 When the host controller receives a valid ANY_CLOSE_PIPE on an open pipe, it shall close the pipe and respond with ANY_OK and no parameters... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.3.1.3 Administration commands | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 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. RQ6.22 When the host controller receives an ADM_CREATE_PIPE command, it shall use the WHITELIST defined by the destination host in order to verify that the source host is authorized to create a pipe. RQ6.23 When the pipe was successful... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 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. RQ6.24 When the host controller sends an ADM_NOTIFY_PIPE_CREATED command, the command parameters shall be 5 bytes long. RQ6.25 When the host controller sends an ADM_NOTIFY_PIPE_CREATED command as a result of an ADM_CREATE_PIPE command ... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 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. RQ6.26 The host that requested the deletion of the pipe can only be the source host or destination host. RQ6.27 When the pipe is successfully deleted, the host controller shall send the response ANY_OK without parameters. NOTE: All con... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 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. RQ6.28 When the host controller sends an ADM_NOTIFY_PIPE_DELETED command, the command parameters shall be 1 byte long. NOTE: All conformance requirements for the referenced clause are included in clause 5.5.1.2 of the present document.... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 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. RQ6.29 When the host controller receives a valid ADM_CLEAR_ALL_PIPE command and the data link layer specified in ETSI TS 102 613 [2] is used, it shall interpret the two bytes in the command parameters as the identity reference data, an... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 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. RQ6.32 When the host controller receives a valid ADM_CLEAR_ALL_PIPE command from a requesting host, it shall send ADM_NOTIFY_ALL_PIPE_CLEARED to every host with at least one pipe to the requesting host. RQ6.33 When the host controller ... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.3.2 Responses | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.3.2.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 6.2. RQ6.35 A response shall be sent to all commands received even to those unknown to the receiving gate. RQ6.36 Responses received out of order (i.e. if no command was sent previously) shall be discarded. RQ6.37 For a received command which is defined in table 16 in ETSI TS 102 ... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.3.2.2.1 Test execution | There are no test case-specific parameters for this test case. ETSI ETSI TS 102 695-1 V13.0.0 (2019-04) 34 Release 13 |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.3.2.2.2 Initial conditions | • The HCI interface is idle; i.e. no further communication is expected. • PIPE1 is open. |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.3.2.2.3 Test procedure | Step Direction Description RQ 1 HS HCUT Send command with an RFU instruction value on PIPE1. 2 HCUT HS Send response (contents are not checked). RQ6.35 |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.3.3 Events | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.3.3.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 6.3. RQ6.38 Unknown events received shall be discarded. RQ6.39 EVT_HOT_PLUG shall be sent by the host controller to any other connected host to notify the connection or disconnection of a host to the host controller. RQ6.40 Rel-7 to Rel-12 When the host controller send EVT_HOT_PLU... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.3.3.2.1 Test execution | There are no test case-specific parameters for this test case. ETSI ETSI TS 102 695-1 V13.0.0 (2019-04) 35 Release 13 |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.3.3.2.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 controller's identity management gate, and is open. |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.3.3.2.3 Test procedure | Step Direction Description RQ 1 HS HCUT Send event with an RFU instruction value on PIPE_ID_MAN. 2 HS HCUT Send ANY_GET_PARAMETER(GATES_LIST) on PIPE_ID_MAN. 3 HCUT HS Send response with ANY_OK and value of GATES_LIST. RQ6.38 |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.4 GATES and subclauses | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.4.1 GATES | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.4.1.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 7. RQ7.1 Gates shall support the commands and events specified for them in tables 18 and 19 of ETSI TS 102 622 [1]. NOTE 1: RQ1 is not tested in this clause, as it is effectively tested in other clauses of the present document. NOTE 2: ANY_GET_PARAMETER and ANY_SET_PARAMETER are n... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.4.2 Management gates | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.4.2.1 Administration gates | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.4.2.1.1 Host controller administration gate | 5.4.2.1.1.1 Conformance requirements Reference: ETSI TS 102 622 [1], clauses 7.1.1.1 and 4.5. RQ4.26 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. RQ6.32 When the host controller receives a vali... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.4.2.1.2 Host administration gate | 5.4.2.1.2.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 7.1.1.2. There are no conformance requirements for the terminal for the referenced clause. |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.4.2.2 Link management gate | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.4.2.2.1 Host controller link management gate | 5.4.2.2.1.1 Conformance requirements Reference: ETSI TS 102 622 [1], clauses 7.1.2.1 and 4.5. RQ4.26 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. RQ7.15 The host controller shall use a default ... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.4.2.2.2 Host link management gate | 5.4.2.2.2.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 7.1.2.2. RQ7.18 The host controller shall only set values of REC_ERROR with length 2 bytes. NOTE: Test cases for RQ7.18 are presented in ETSI TS 102 695-3 [10]. ETSI ETSI TS 102 695-1 V13.0.0 (2019-04) 41 Release 13 |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.4.2.3 Identity management gate | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.4.2.3.1 Local registry | 5.4.2.3.1.1 Conformance requirements Reference: ETSI TS 102 622 [1], clauses 7.1.3 and 4.5. NOTE: This clause covers the conformance requirements contained within ETSI TS 102 622 [1], clause 7.1.3 for the local registry. The requirements for the remote registry are contained in clause 5.4.2.3.2. RQ4.26 Registry paramet... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.4.2.3.2 Remote registry | 5.4.2.3.2.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 7.1.3. NOTE: This clause covers the conformance requirements contained within ETSI TS 102 622 [1], clause 7.1.3 for the remote registry. The requirements for the local registry are contained in clause 5.4.2.3.1. RQ7.33 The host controller shall... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.4.2.4 Loop back gate | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.4.2.4.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clauses 7.1.4 and 4.5. RQ4.26 Registry parameters which are in the range of '00' to 'EF' but which are not allocated in ETSI TS 102 622 [1] shall not be present in the registry. RQ4.27 Rel-11 upwards As destination gate, the loop back gate in the host controller shall accept at least one... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.4.3 Generic gates | Reference: ETSI TS 102 622 [1], clause 7.2. There are no conformance requirements for the terminal for the referenced clause. ETSI ETSI TS 102 695-1 V13.0.0 (2019-04) 44 Release 13 |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.5 HCI procedures | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.5.1 Pipe management | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.5.1.1 Pipe creation | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.5.1.1.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clauses 8.1.1, 5.1,6.1.3.1 and 6.1.3.2. RQ6.22 When the host controller receives an ADM_CREATE_PIPE command, it shall use the WHITELIST defined by the destination host in order to verify that the source host is authorized to create a pipe. RQ8.1 The host controller shall verify that the ... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.5.1.2 Pipe deletion | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.5.1.2.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clauses 8.1.2, 6.1.3.3 and 6.1.3.4. RQ8.9 After receiving a valid ADM_DELETE PIPE command from a host, the host controller notifies the destination host (with an ADM_NOTIFY_PIPE_DELETED command). RQ6.28 When the host controller sends an ADM_NOTIFY_PIPE_DELETED command, the command parame... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.5.1.2.2 Test case 1: valid pipe deletion from host to host controller | 5.5.1.2.2.1 Test execution There are no test case-specific parameters for this test case. 5.5.1.2.2.2 Initial conditions • The HCI interface is idle; i.e. no further communication is expected. • PIPE1 is open. • A dynamic pipe (PIPE_X) has been created from a gate on the host simulator to a gate on the host controller,... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.5.1.3 Clear all Pipes | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.5.1.3.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clauses 8.1.3, 6.1.3.5 and 6.1.3.6. RQ6.29 When the host controller receives a valid ADM_CLEAR_ALL_PIPE command and the data link layer specified in ETSI TS 102 613 [2] is used, it shall interpret the two bytes in the command parameters as the identity reference data, and shall use the i... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.5.1.3.2 Test case 1: identity reference data when ETSI TS 102 613 is used | 5.5.1.3.2.1 Test execution There are no test case-specific parameters for this test case. 5.5.1.3.2.2 Initial conditions • The HCI interface is idle; i.e. no further communication is expected. • SYNC ID needs to match. ETSI ETSI TS 102 695-1 V13.0.0 (2019-04) 46 Release 13 5.5.1.3.2.3 Test procedure Step Direction Desc... |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.5.2 Registry access | Reference: ETSI TS 102 622 [1], clause 8.2. There are no new conformance requirements for the terminal for the referenced clause. |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.5.3 Host and Gate discovery | Reference: ETSI TS 102 622 [1], clause 8.3. There are no conformance requirements for the terminal for the referenced clause. |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.5.4 Session initialization | |
92ea1f0bb3b750219f3775a220a38c6d | 102 695-1 | 5.5.4.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clauses 6.2 and 8.4. RQ8.12 8.4 In case the lower layer identity check fails, the host controller shall execute only the following commands: ANY_OPEN_PIPE, ADM_CLEAR_ALL_PIPE, ANY_GET_PARAMETER, and only if these are sent on PIPE1. RQ8.13 8.4 In case the lower layer identity check fails,... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.