hash
stringlengths
32
32
doc_id
stringlengths
7
13
section
stringlengths
3
121
content
stringlengths
0
2.2M
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.3.2.4 Void
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.3.3 Events
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.3.3.1 Conformance requirements
Reference: ETSI TS 102 622 [1], clause 6.3. RQ1 Unknown events received shall be discarded. RQ2 When the host sends EVT_HCI_END_OF_OPERATION, it shall contain no parameters. RQ3 For gates defined in ETSI TS 102 622 [1], hosts shall not use event values which are not allocated in ETSI TS 102 622 [1]. NOTE 1: No RQs are ...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.3.3.2.1 Test execution
Void. ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 37 Release 11
915d49d66cb16af028532c3330e1bdcb
102 695-2
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's identity management gate, and is open.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.3.3.2.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 event with an RFU instruction value on PIPE_ID_MAN. 4 HCS  HUT Send ANY_GET_PARAMETER(GATES_LIST) on PIPE_ID_MAN. 5 HUT  HCS Send ...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.4 GATES and subclauses
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.4.1 GATES
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.4.1.1 Conformance requirements
Reference: ETSI TS 102 622 [1], clause 7. RQ1 Gates shall support the commands and events specified for them in tables 18 and 19 of ETSI TS 102 622 [1]. NOTE 1: In this clause, RQ1 is only tested for the management gates. Other clauses may test RQ1 for other gates as applicable. NOTE 2: ANY_GET_PARAMETER and ANY_SET_PA...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.4.1.2.1 Test execution
Void.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.4.1.2.2 Initial conditions
• The HCI interface is idle; i.e. no further communication is expected. • PIPE0 is open.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.4.1.2.3 Test procedure
Step Direction Description RQ 1 HCS  HUT Send ANY_CLOSE_PIPE on PIPE0. 2 HUT  HCS Send ANY_OK (parameters are not checked). RQ1 3 HCS  HUT Send ANY_OPEN_PIPE on PIPE0. 4 HUT  HCS Send ANY_OK (parameters are not checked). RQ1 ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 38 Release 11 5.4.1.3 Test case 2: command and eve...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.4.1.3.1 Test execution
The test procedure shall be executed once for each of following parameters, indicating the pipe to be used in the test procedure: • PIPE1; • a pipe which has been created from the host controller's identity management gate to the host's identity management; • a pipe which has been created from gate with GID = '01' on t...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.4.1.3.2 Initial conditions
• The HCI interface is idle; i.e. no further communication is expected. • The pipe indicated in the test execution clause is open.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.4.1.3.3 Test procedure
Step Direction Description RQ 1 HCS  HUT Send ANY_CLOSE_PIPE on the pipe indicated in the test execution clause. 2 HUT  HCS Send ANY_OK (parameters are not checked). RQ1 3 HCS  HUT Send ANY_OPEN_PIPE on the pipe indicated in the test execution clause. 4 HUT  HCS Send ANY_OK (parameters are not checked). RQ1
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.4.2 Management gates
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.4.2.1 Administration gates
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.4.2.1.1 Host controller administration gate
5.4.2.1.1.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 7.1.1.1. RQ1 The host shall only set values of SESSION_IDENTITY with length 8 bytes. RQ2 The session identity shall be modified by the host whenever a modification of the configuration is performed by the host. RQ3 The default value of the sess...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.4.2.1.2 Host administration gate
5.4.2.1.2.1 Conformance requirements Reference: ETSI TS 102 622 [1], clauses 7.1.1.2 and 4.5. RQ1 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. NOTE: Development of test cases for RQ1 is FFS.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.4.2.2 Link management gate
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.4.2.2.1 Host controller link management gate
5.4.2.2.1.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 7.1.2.1. RQ1 The host shall only set values of REC_ERROR with length 2 bytes. NOTE: RQ1 is not testable in a standardized manner. See Annex A for test cases which could be used in a non-standardized manner. ETSI ETSI TS 102 695-2 V11.0.0 (2019-...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.4.2.2.2 Host link management gate
5.4.2.2.2.1 Conformance requirements Reference: ETSI TS 102 622 [1], clauses 7.1.2.2 and 4.5. RQ1 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. RQ2 7.1.2.2 The host shall use a default value for REC_ERROR of '0000'...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.4.2.3 Identity management gate
915d49d66cb16af028532c3330e1bdcb
102 695-2
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. RQ1 4.5 Registry parame...
915d49d66cb16af028532c3330e1bdcb
102 695-2
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. RQ1 The host shall adhere to the...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.4.2.4 Loop back gate
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.4.2.4.1 Conformance requirements
Reference: ETSI TS 102 622 [1], clauses 7.1.4 and 4.5. RQ1 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. RQ2 7.1.4 Rel-11 upwards As destination gate, the loop back gate in the host controller shall accept at least...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.4.3 Generic gates
Reference: ETSI TS 102 622 [1], clause 7.2. There are no conformance requirements for the UICC for the referenced clause. ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 43 Release 11
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5 HCI procedures
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.1 Pipe management
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.1.1 Pipe creation
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.1.1.1 Conformance requirements
Reference: ETSI TS 102 622 [1], clauses 8.1.1, 6.1.3.1 and 6.1.3.2. RQ1 6.1.3.1 When a host sends an ADM_CREATE_PIPE command, the command parameters shall be 3 bytes long, and contain valid GIDs and HID. RQ2 6.1.3.2 When a host receives an ADM_NOTIFY_PIPE_CREATED command, it shall respond with ANY_OK with no parameters...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.1.1.2 Void
5.5.1.1.3 Test case 2: ADM_NOTIFY_PIPE_CREATED from host controller 5.5.1.1.3.1 Test execution Void. 5.5.1.1.3.2 Initial conditions • The HCI interface is idle; i.e. no further communication is expected. • PIPE1 is open. 5.5.1.1.3.3 Test procedure Step Direction Description RQ 1 HCS  HUT Send ADM_NOTIFY_PIPE_CREATED o...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.1.2 Pipe deletion
915d49d66cb16af028532c3330e1bdcb
102 695-2
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. RQ1 6.1.3.3 When a host sends an ADM_DELETE_PIPE command, the command parameters shall be 1 byte long. RQ2 6.1.3.3 When a host sends an ADM_DELETE_PIPE command, the host that requested the deletion of the pipe shall be the source host or destination ho...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.1.2.2 Void
5.5.1.2.3 Test case 2: receiving ADM_NOTIFY_PIPE_DELETED 5.5.1.2.3.1 Test execution Void. 5.5.1.2.3.2 Initial conditions • The HCI interface is idle; i.e. no further communication is expected. • PIPE1 is open. • A pipe (PIPE_LOOP_BACK) has been created to the host's loop back gate, and is open. 5.5.1.2.3.3 Test procedu...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.1.3 Clear all Pipes
915d49d66cb16af028532c3330e1bdcb
102 695-2
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. ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 46 Release 11 RQ1 6.1.3.5 When the host sends an ADM_CLEAR_ALL_PIPE command and the data link layer specified in ETSI TS 102 613 [2] is used, the command parameters are the identity reference data and shall be t...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.1.3.5 Void
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.2 Registry access
Reference: ETSI TS 102 622 [1], clause 8.2. There are no new conformance requirements for the UICC for the referenced clause.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.3 Host and Gate discovery
Reference: ETSI TS 102 622 [1], clause 8.3. There are no conformance requirements for the UICC for the referenced clause.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.4 Session initialization
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.4.1 Conformance requirements
Reference: ETSI TS 102 622 [1], clause 8.4. RQ1 Up to Rel-9 The Host shall perform session initialization only if no contactless transaction is pending at startup (e.g. after power up in full-power mode as defined in ETSI TS 102 613 [2]). RQ2 Up to Rel-9 If the data link layer specified in ETSI TS 102 613 [2] is being ...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.4.2.1 Test execution
Run this test procedure in full power mode only.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.4.2.2 Initial conditions
• The host is not powered up.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.4.2.3 Test procedure
Step Direction Description RQ 1 HCS  HUT Power up host. 2 HUT  HCS Send ANY_SET_PARAMETER(SESSION_IDENTITY) on PIPE1 (see note 1). 3 HCS  HUT Send ANY_OK with no parameters. 4 HUT  HCS Wait for any the HCI interface to be idle. 5 HCS  HUT Power down host. 6 HCS  HUT Power up host. 7 HUT  HCS Send ANY_GET_PARAME...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.4.3.1 Test execution
Run this test procedure in full power mode only.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.4.3.2 Initial conditions
• The host is not powered up.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.4.3.3 Test procedure
Step Direction Description RQ 1 HCS  HUT Power up host; behave as if lower layer identity check has failed (i.e. enter inhibited state). 2 HUT  HCS Send ANY_GET_PARAMETER(SESSION_IDENTITY) on PIPE1 (see note 1). RQ2/ RQ7 3 HCS  HUT Send an allowed response code for the command. 4 HUT  HCS Send ADM_CLEAR_ALL_PIPE on...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.4.4.1 Test execution
Run this test procedure in low power mode only.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.4.4.2 Initial conditions
• The Host is not powered up. • At the end of the previous full power mode activation, the state of at least one card emulation pipe was open, and the MODE parameter was '02' (as set by the UICC).
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.4.4.3 Test procedure
Step Direction Description RQ 1 HCS  HUT Power up host in low power mode. 2 HUT  HCS Do not send ANY_GET_PARAMETER(SESSION_IDENTITY), ADM_CLEAR_ALL_PIPE or ANY_SET_PARAMETER(SESSION_IDENTITY). RQ7 5.5.4.5 Test case 4: subsequent activation, no session initialization
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.4.5.1 Test execution
Run this test procedure in full power mode only.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.4.5.2 Initial conditions
• HCI session initialization has been performed and the SWP interface is DEACTIVATED. • The UICC has opened at least one card emulation pipe and set the MODE parameter to '02'.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.4.5.3 Test procedure
Step Direction Description RQ 1 HCS  HUT Perform subsequent interface activation. 2 HUT  HCS Do not send ANY_GET_PARAMETER(SESSION_IDENTITY), ADM_CLEAR_ALL_PIPE or ANY_SET_PARAMETER(SESSION_IDENTITY). RQ7 5.5.4.6 Test case 5: activation in low power mode, ACT_POWER_MODE with FR=1, no session initialization
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.4.6.1 Test execution
Run this test procedure in low power mode only.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.4.6.2 Initial conditions
• The Host is not powered up. • At the end of the previous full power mode activation, the state of at least one card emulation pipe was open, and the MODE parameter was '02' (as set by the UICC). ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 51 Release 11
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.4.6.3 Test procedure
Step Direction Description RQ 1 HCS  HUT Activate Vcc and SWIO. 2 HUT  HCS Send ACT_SYNC frame. 3 HCS  HUT Send ACT_POWER_MODE frame with FR=1 and low power mode indication. 4 HUT  HCS Send ACT_SYNC frame. 5 HCS  HUT Perform SHDLC link establishment. 6 HUT  HCS Do not send ANY_GET_PARAMETER(SESSION_IDENTITY), ADM...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.4.7.1 Test execution
Run this test procedure in full power mode only.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.4.7.2 Initial conditions
• HCI session initialization has been performed and the SWP interface is DEACTIVATED. • The UICC has opened at least one card emulation pipe and set the MODE parameter to '02'.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.4.7.3 Test procedure
Step Direction Description RQ 1 HCS  HUT Activate SWIO. 2 HUT  HCS Send ACT_SYNC frame. 3 HCS  HUT Send ACT_POWER_MODE frame with FR=1 and full power mode indication. 4 HUT  HCS Send ACT_SYNC frame. 5 HCS  HUT Perform SHDLC link establishment. 6 HUT  HCS Do not send ANY_GET_PARAMETER(SESSION_IDENTITY), ADM_CLEAR_...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.5 Loop back testing
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.5.1 Conformance requirements
Reference: ETSI TS 102 622 [1], clause 8.5. RQ1 A host shall accept the creation of a pipe to its loop back gate from any gate in another host. RQ2 When a host 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 data as received in the receive...
915d49d66cb16af028532c3330e1bdcb
102 695-2
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'. ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 52 Release 11
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.5.2.2 Initial conditions
• The HCI interface is idle; i.e. no further communication is expected. • PIPE1 is open.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.5.2.3 Test procedure
Step Direction Description RQ 1 HCS  HUT Send ADM_NOTIFY_PIPE_CREATED on PIPE1, with source GID as specified and destination GID = GID of loop back gate. 2 HUT  HCS Send ANY_OK (parameters are not checked). RQ1 5.5.5.3 Test case 2: pipe creation from another host
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.5.3.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'.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.5.3.2 Initial conditions
• The HCI interface is idle; i.e. no further communication is expected. • PIPE1 is open.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.5.3.3 Test procedure
Step Direction Description RQ 1 HCS  HUT Send ADM_NOTIFY_PIPE_CREATED on PIPE1, with source HID equal to the HID contained in the host's WHITELIST, source GID as specified and destination GID = GID of loop back gate. 2 HUT  HCS Send ANY_OK (parameters are not checked). RQ1 5.5.5.4 Test case 3: processing of EVT_POST_...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.5.4.1 Test execution
The test procedure shall be executed once for each of following parameters: • EVT_POST_DATA data sizes of: 1 byte, 100 bytes, 250 bytes.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.5.4.2 Initial conditions
• The HCI interface is idle; i.e. no further communication is expected. • A pipe (PIPE_LOOP_BACK) has been created to the host's loop back gate, and is open.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.5.5.4.3 Test procedure
Step Direction Description RQ 1 HCS  HUT Send EVT_POST_DATA on PIPE_LOOP_BACK containing data of the specified size. 2 HUT  HCS Send EVT_POST_DATA on PIPE_LOOP_BACK containing the same data as in step 1. RQ2, RQ3 ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 53 Release 11
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6 Contactless card emulation
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.1 Overview
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.1.1 Conformance requirements
Reference: ETSI TS 102 622 [1], clause 9.1. RQ1 For each card RF gate it wants to use, the host has one card application gate. RQ2 For the contactless platform for card emulation mode the pipes to card RF gates shall be created, opened, closed and deleted by the host. RQ3 The host shall not create more than one pipe to...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.2 Void
Reference: ETSI TS 102 622 [1], clause 9.2. There are no conformance requirements for the UICC for the referenced clause.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.3 Gates
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.3.1 Void
Reference: ETSI TS 102 622 [1], clause 9.3.1. There are no conformance requirements for the UICC for the referenced clause.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.3.2 Identity management gate
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.3.2.1 Conformance requirements
Reference: ETSI TS 102 622 [1], clause 9.3.2. RQ1 The host shall adhere to the access condition of RO for LOW_POWER_SUPPORT. NOTE: RQ1 is a non-occurrence RQ.
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.3.3 Card RF gates
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.3.3.1 Overview
Reference: ETSI TS 102 622 [1], clause 9.3.3.1. There are no conformance requirements for the UICC for the referenced clause.
915d49d66cb16af028532c3330e1bdcb
102 695-2
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. ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 54 Release 11 There are no conformance requirements for the UICC for the referenced clause.
915d49d66cb16af028532c3330e1bdcb
102 695-2
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. There are no conformance requirements for the UICC for the referenced clause. 5.6.3.3.3.2 EVT_SEND_DATA Reference: ETSI TS 102 622 [1], clause 9.3.3.3.1. There are no conformance requirements for the UICC for the r...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.3.3.4 Registry and subclauses
5.6.3.3.4.1 Registry Void. 5.6.3.3.4.1.1 Conformance requirements Reference: ETSI TS 102 622 [1], clause 9.3.3.4. There are no conformance requirements for the UICC for the referenced clause. 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], clause 9.3.3.4.1. RQ1 Th...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.3.4 Card application gates
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.3.4.1 Overview
Reference: ETSI TS 102 622 [1], clause 9.3.4.1. There are no conformance requirements for the UICC for the referenced clause.
915d49d66cb16af028532c3330e1bdcb
102 695-2
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 UICC for the referenced clause. ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 57 Release 11
915d49d66cb16af028532c3330e1bdcb
102 695-2
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. RQ1 Each card application gate shall support all events as listed. NOTE: This RQ is not tested in this clause, as it is tested in clause 5.6.4. 5.6.3.4.3.2 EVT_FIELD_ON 5.6.3.4.3.2.1 Conformance requirements Refere...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.3.4.4 Registry
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.3.4.4.1 Conformance requirements
Reference: ETSI TS 102 622 [1], clause 9.3.4.4. 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.6.4 Procedures
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.4.1 Use of contactless card application
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.4.1.1 Conformance requirements
Reference: ETSI TS 102 622 [1], clauses 9.4.1, 9.3.4.3 and 9.3.4.3.5. RQ1 9.4.1 In the context of a valid contactless card application sequence as specified in ETSI TS 102 622 [1], the host shall reply to received C-APDUs contained in EVT_SEND_DATAs by sending the R-APDUs contained in EVT_SEND_DATAs to the card RF gate...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.4.1.7 Test case 6: EVT_FIELD_OFF after EVT_FIELD_ON / SWP interface activation
5.6.4.1.7.1 Test execution The test procedure shall be executed once for each of following parameters. • Type A (if supported, and the UICC sets a value of SAK indicating support of ISO/IEC 14443-4 [5]). • Type B (if supported). 5.6.4.1.7.2 Initial conditions • The host controller simulator is configured to support onl...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.4.2 Non ISO/IEC 14443-4 type A
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.4.2.1 Conformance requirements
Reference: ETSI TS 102 622 [1], clauses 9.4.2 and clause 9.3.4.3. RQ1 9.4.2 In the context of a valid contactless card application sequence as specified in ETSI TS 102 622 [1], the host shall support communications using the CLT mode as defined in ETSI TS 102 613 [2]. RQ2 9.4.2 The host shall accept an EVT_FIELD_OFF wh...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.4.2.5 Test case 4: EVT_FIELD_OFF after EVT_FIELD_ON / SWP interface activation
5.6.4.2.5.1 Test execution Void. 5.6.4.2.5.2 Initial conditions • The host controller simulator is configured to support only the Type A card RF gate, with CLT_SUPPORT set to '01' (CLT supported). • For full power mode execution: HCI session initialization has been performed and the HCI interface is idle. • For low pow...
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.4.3 Type B' RF technology
915d49d66cb16af028532c3330e1bdcb
102 695-2
5.6.4.3.1 Conformance requirements
Reference: ETSI TS 102 622 [1], clause 9.4.3. NOTE: Since this technology is not publicly disclosed, no conformance requirements have been established. ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 71 Release 11