4.2 Requirements to the EUT and the test environment

31.1273GPPnon-removable Universal Subscriber Identity Module (nrUSIM) application behavioural test specificationRelease 17TSUICC-terminal interaction

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

4.2.1 General Requirements

All tests defined in the subsequent clauses apply to UEs operating an nrUSIM, what implies that the UICC‑terminal interface cannot be exposed to a TT. Depending on the test method used, an explicit verification of APDUs or data sent via the UICC‑terminal interface might not be possible. If explicit verification of APDUs, data or file contents is needed to verify a conformance requirement the implementation and applicability has to be declared (see also clause 3.7.1).

The tests are not applicable for UEs providing a UICC‑terminal interface in accordance to interface form factors defined in ETSI TS 102 221 [28] or ETSI TS 102 671 [29].

The following sequence of tests confirms:

a) the usage of the test specific UICC/USIM data;

b) the correct interpretation of data read from the USIM (Universal Subscriber Identification Module) by the ME;

c) the correct writing of data to the USIM by the ME;

d) the initiation of appropriate procedures by the ME;

e) the correct execution of functions

All tests apply to the USIM application on the UICC or an equivalent application implemented in accordance to the ETSI SSP specifications ETSI TS 103 666-1 [10], ETSI TS 103 666-2 [11] and ETSI TS 103 666-3 [12]

4.2.2 Requirements to the UE (EUT) – supported interfaces

The EUT has to support interfaces and administration methods to allow the TT or the tester to set the initial conditions defined for the test cases. Where the EUT may be solely the UE or the UE connected to an interface device.

NOTE: The connection of the UE and an interface device is set up similar to what is described in the Companion Device scenario in GSMA SGP.22 [30], but not limited to remote SIM provisioning functionality.

Suggested interfaces:

• Wi-Fi (IEEE 802.11-2016 [13])

• USB (USB-IF, USB 2.0 or higher)

The UE has to support at least one of the following data transfer methods:

• RFM and OTA via ETSI TS 102 225 [14] and ETSI TS 102 226 [15]

• AT commands as defined in TS 27.007 [16]

• Java^TMCard as defined in TS 31.130 [17]

Even though the availability of at least one of the suggested interfaces and one of the suggested data transfer method is recommended, interfaces and methods for UICC/USIM preparation for testing purposes are to be provided by the UE vendor and are out of scope of the present document.

4.2.3 Supported RATs

UEs tested in accordance to the present document shall support any 3GPP defined RATs. Test cases defined in the present document may contain RAT or RAN specific conformance requirements and methods of test. The applicability of the individual test cases can be determined by using Table B.1.

Tests that would require 2G network access (GERAN) are out of scope of the present document.

4.2.4 Initial and final procedure steps

Initial and final procedure steps are out of scope of the current specification to not explicitly exclude methods that might be used to get a UE set up at test case start or to have it ‘cleaned up’ at the end of a test (if required).

The testing person has to ensure that the UE has installed test specific the UICC and USIM data in accordance to the definitions of the particular test(see note). The UE has to be accessible and is switched into a specific reception mode if required by the test case. It has to be ensured that interfaces that are used to verify file data or a specific functionality do not interfere or block the operation of the test procedure as defined within this specification.

For verification purposes an interaction with the UE is allowed even after ending the defined test procedure. If such interaction takes place it has to be reported to the TT. A verification of conformance requirements that is based on data or information that is generated during this post-procedure interaction has to be identifiable as a post process, but can be used for the result generation.

NOTE: For all EFs, DFs and ADFs building the UICC and USIM where no data is explicitly defined in the test or by reference, an appropriate test value can be used (e.g.: values from GSMA TS.48 [9]).