hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.1.3 Gates | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.1.4 Pipes | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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 ... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.1.5 Registries | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.2 HCP | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.2.1 HCP packets | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.2.2 HCP message structure | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.2.3 Message fragmentation | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.3 Instructions | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.3.1 Commands | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.3.1.1 Overview | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.3.1.2 Generic commands | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.3.1.3 Administration commands | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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 ... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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 ... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.3.2 Responses | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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 ... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.3.2.2.1 Test execution | There are no test case-specific parameters for this test case. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.3.2.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. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.3.2.2.3 Test procedure | Step Direction Description RQ 1 HS HCUT Send ANY_GET_PARAMETER(GATES_LIST) on PIPE_ID_MAN. 2 HCUT HS Send response with ANY_OK and value of GATES_LIST on PIPE_ID_MAN. 3 HS HCUT Send response with ANY_OK and no parameters on PIPE_ID_MAN. 4 HCUT No message on PIPE_ID_MAN. RQ6.36 5 HS HCUT Send ANY_GET_PARAMETER(G... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.3.2.3.1 Test execution | There are no test case-specific parameters for this test case. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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 controller's identity management gate, and is open. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.3.2.3.3 Test procedure | Step Direction Description RQ 1 HS HCUT Send ANY_CLOSE_PIPE on PIPE_ID_MAN. 2 HCUT HS Send ANY_OK. 3 User HCUT Trigger the host controller to open PIPE_ID_MAN. 4 HCUT HS Send ANY_OPEN_PIPE on PIPE_ID_MAN. 5 HS HCUT Send ANY_OK with valid response parameter on PIPE_ID_MAN. 6 HS HCUT Send ANY_E_NOK on PIPE_ID... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.3.3 Events | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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 When the host controller send EVT_HOT_PLUG, it shall cont... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.4 GATES and subclauses | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.4.1 GATES | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.4.2 Management gates | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.4.2.1 Administration gates | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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.28 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.2 The registry of the host controller admin... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.4.2.2 Link management gate | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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.28 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 ... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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. 5.4.2.2.2.2 Test case 1: REC_ERROR 5.4.2.2.2.2.1 Test execution There are no test case-specific parameters for this test case. 5.4.2.2.2.2.2 Initial con... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.4.2.3 Identity management gate | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.4.2.4 Loop back gate | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.4.2.4.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clauses 7.1.4 and 4.5. RQ4.26 4.5 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 7.1.4 Rel-11 upwards As destination gate, the loop back gate in the host controller shall accept at... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.5 HCI procedures | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.5.1 Pipe management | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.5.1.1 Pipe creation | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.5.1.2 Pipe deletion | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.5.1.3 Clear all Pipes | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 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. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.5.4 Session initialization | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.5.4.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 8.4. RQ6.29 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. RQ6.30 In case the lower layer identity check fails, the host control... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.5.5 Loop back testing | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.5.5.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 8.5. RQ8.18 The host controller shall accept the creation of a pipe to its loop back gate from any gate in another host. RQ8.19 When the host controller receives the event EVT_POST_DATA on a pipe connected to its loop back gate, it shall send back the event EVT_POST_DATA with same... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.5.5.2.1 Test execution | The test procedure shall be executed once for each of following parameters: • Source GID values of: '00', '03', '05', '10', 'AA', 'FF'. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.5.5.2.2 Initial conditions | • The HCI interface is idle; i.e. no further communication is expected. • PIPE1 is open. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.5.5.2.3 Test procedure | Step Direction Description RQ 1 HS HCUT Send ADM_CREATE_PIPE on PIPE1, with source GID as specified and destination GID = GID of loop back gate. 2 HCUT HS Send ANY_OK (parameters are not checked). RQ8.18 |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6 Contactless card emulation | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.1 Overview | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.1.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 9.1. RQ9.1 The CLF shall handle the RF communication layers to the external contactless reader. RQ9.2 The host controller has one card RF gate for each RF technology it supports. RQ9.3 For the contactless platform for card emulation mode the pipes to card RF gates shall be created... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.2 Void | Reference: ETSI TS 102 622 [1], clause 9.2. There are no conformance requirements for the terminal for the referenced clause. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.3 Gates | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.3.1 Void | Reference: ETSI TS 102 622 [1], clause 9.3.1. There are no conformance requirements for the terminal for the referenced clause. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.3.2 Identity management gate | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.3.2.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 9.3.2. RQ9.6 If low power mode is supported, the parameter LOW_POWER_SUPPORT of identity management gate shall be '01'. RQ9.7 If low power mode is not supported, the parameter LOW_POWER_SUPPORT of identity management gate shall be '00'. RQ9.8 The host controller shall apply the ac... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.3.3 Card RF gates | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.3.3.1 Overview | Reference: ETSI TS 102 622 [1], clause 9.3.3.1. There are no conformance requirements for the terminal for the referenced clause. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.3.3.2 Commands | 5.6.3.3.2.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 9.3.3.2. There are no conformance requirements for the terminal for the referenced clause. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.3.3.3 Events and subclauses | 5.6.3.3.3.1 Events 5.6.3.3.3.1.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 9.3.3.3. RQ9.10 The Card RF gates shall support the EVT_SEND_DATA event. NOTE: RQ9.10 is tested in clause 5.6.4. ETSI ETSI TS 102 695-3 V13.0.0 (2019-04) 43 Release 13 5.6.3.3.3.2 EVT_SEND_DATA Reference: ETSI TS 102 622 [1... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.3.3.4 Registry and subclauses | 5.6.3.3.4.1 Registry 5.6.3.3.4.1.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 9.3.3.4. RQ9.11 All registries shall be persistent. NOTE: Development of test cases for above listed RQs is FFS. 5.6.3.3.4.2 RF technology type A 5.6.3.3.4.2.1 Conformance requirements Reference: ETSI TS 102 622 [1], clau... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.3.4 Card application gates | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.3.4.1 Overview | Reference: ETSI TS 102 622 [1], clause 9.3.4.1. There are no conformance requirements for the terminal for the referenced clause. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.3.4.2 Commands | 5.6.3.4.2.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 9.3.4.2. There are no conformance requirements for the terminal for the referenced clause. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.3.4.3 Events and subclauses | 5.6.3.4.3.1 Events 5.6.3.4.3.1.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 9.3.4.3. RQ9.74 When sending to a card application gate, the CLF shall respect the values and events as listed. NOTE: Development of test cases for above listed RQs is FFS. ETSI ETSI TS 102 695-3 V13.0.0 (2019-04) 50 Releas... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.3.4.4 Registry | 5.6.3.4.4.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 9.3.4.4. There are no conformance requirements for the terminal for the referenced clause. ETSI ETSI TS 102 695-3 V13.0.0 (2019-04) 51 Release 13 |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.4 Procedures | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.4.1 Use of contactless card application | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.4.1.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clauses 9.4 and 9.4.1. NOTE: These requirements apply for usage of ISO/IEC 14443-4 [7]. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.4.2 Non ISO/IEC 14443-4 type A applications | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.4.2.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 9.4.2. RQ9.91 In full power mode, and if SWP is not in DEACTIVATED_state, when the CLF detects a RF field, the card RF gate shall send the event EVT_FIELD_ON to the card application gate. RQ9.92 When there are multiple open card RF gates the CLF shall send the EVT_FIELD_ON to the ... |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.4.3 Type B' RF technology | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.4.3.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 9.4.3. NOTE: Defining conformance requirements is out of scope of the present document. |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.4.4 Type F RF technology | |
6760801549fcce1efd9b24fa418f3463 | 102 695-3 | 5.6.4.4.1 Conformance requirements | Reference: ETSI TS 102 622 [1], clause 9.4.4. RQ9.98 In full power mode, and if SWP is not in DEACTIVATED state, when the CLF detects a RF field, the card RF gate shall send the event EVT_FIELD_ON to the card application gate. RQ9.99 When there are multiple open cards RF gates the CLF shall send the EVT_FIELD_ON to the... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.