4 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.1 Test environment description

4.1.1 General test environment

Without having the UICC-terminal interface accessible a direct verification of APDU/data timing and contents is not possible. Thus, alternative implementations and methods will be used to provide sufficient confidence in the result obtained. The present document will not specify an authoritative test environment. The following figure shows a test environment that allows the verification of test results for UEs with an integrated and not removable UICC/USIM (nrUSIM).

Without having the UICC-terminal interface accessible, a direct verification of APDU or data contents is not possible. The present document shall provide a test environment and test methods that allow the verification of test results for UEs with an integrated and not removable UICC/USIM (nrUSIM).

Figure 4.1: General test environment

Figure 4.1 gives an overview on how a test case shall be executed.

Based on the identified test purpose and the related conformance requirements an appropriate test sequence is defined. The test itself can be split into three phases:

In the preparation phase the initial set-up for the test case is performed. Test specific data is transferred to the nrUSIM. E.g. by provisioning a test specific profile.
In the execution phase the test procedure is performed. It has to be ensured that all steps defined in the test procedure are executed and that they are executed in order. The data generated during this execution is stored in the TT and/or test EFs in the file system within the nrUICC.
In the verification phase the data, procedures and processes identified and stored during execution are checked against given conformance requirements. A final verification of specific EF/DF contents might be required. The exchange of required data has to be ensured, even though the required data transfer is not necessarily listed in the test procedure.

4.1.2 Example – test environment for implicit testing

Implicit testing within the scope of the present document describes an end-to-end test method where the UICC/USIM file system of the DUT is prepared to contain specific data. During test execution the data transferred from the DUT to the TT is checked and compared to the expected result or value respectively.

Example:

– During preparation phase specific content for the EF_IMSI is updated in the nrUSIM;

– A registration to the network shall be executed using this value;

– The TT compares the initial value sent with the value returned during registration.

To ensure that no pre-configured value is used, the values to be verified in such a test procedure shall be generated as described in clause 4.3 of the present document.

NOTE: A test toolkit applet can be used for testing USAT specific test cases in TS 31.117 [35].

Figure 4.2: Test environment for implicit testing

4.1.3 Example – test environment for contents verification

Contents verification within the scope of the present document describes a procedure that allows the TT to compare contents of EFs/DFs available on the EUT with expected values defined in the present document.

Example:

– During preparation phase specific content for the EF_FPLMN is updated in the nrUSIM;

– During execution of the test the FPLMN value is modified;

– As the FPLMN value stored in EF_FPLMN is not transferred to the TT during test execution;

– The TT performs a read procedure on EF_FPLMN at test case end (not necessarily part of the test procedure);

– The TT compares the value read with the expected value stored in the TT.

The contents verification method described here is not applicable when a verification of EF/DF contents needs to be performed at a time other than the preparation or the verification phase.

NOTE: It is not expected that a reading procedure on EF contents can be performed whilst the test procedure is executed.

The test environment needed to perform contents verification is identical to the test environment shown for implicit testing.

4.1.4 Example – test environment for seamless testing

Seamless testing within the scope of the present document relies on monitoring of data transfer between ME and nrUSIM traced by a software interface between nrUSIM and baseband implemented by the ME vendor.

The logged communication can be transferred to the TT and will be used to determine if conformance requirements are met.

NOTE: A test toolkit applet can be used for testing USAT specific test cases in TS 31.117 [35].

Figure 4.3: Test environment for seamless testing

4.1.5 Example – test environment for test toolkit events based testing

Test toolkit events based testing within the scope of the present document is applicable for UEs supporting the required USIM application toolkit functionality. A toolkit applet is installed onto the nrUSIM, capable of handling test events internal to the card runtime environment and the applets to monitor APDUs received at the nrUICC.

NOTE: The same test toolkit applet can be used for testing USAT specific test cases in TS 31.117[x].

The logged events can be stored in a test EF during the test execution phase and transferred to the TT during the verification phase to determine if conformance requirements are met.

Figure 4.4: Test environment for test toolkit events based testing

4.1.6 Example – test environment for UEs with ETSI eSSP/iSSP

For testing UEs with an USIM functionality provided by an eSSP/iSSP as defined in ETSI TS 103 666‑x specifications a test tool interface as defined in ETSI TS 103 834 has to be supported. Adaption needed to operate tests on UEs with an eSSP/iSSP, like e.g., an APDU gate are out of scope of the present document.

Figure 4.5: Test environment for UEs with ETSI eSSP/iSSP