Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 31.127  Word version:  17.0.0

Top   Top   None   None   Next
0…   2…   5…   6…   7…   8…   9…   10…   11…   12…   13…   14…   15…   16…

 

0  Introductionp. 23

The present document defines application behavioural tests for a UE with a non-removable UICC/USIM where no access to the physical UICC-Terminal interface can be granted when interacting with a 3GPP network.
The aim of the present document is to ensure the correct behaviour of a UE interfacing with a 3GPP network whilst it is proved that card specific data and functionality is used wherever indicated, similar to application tests defined in TS 31.121 but without direct access to the UICC-Terminal interface.
The present document does not define any aspects related to the administrative management phase of the UICC. Any internal technical realisation of either the UICC or the ME is only specified where these are important for the verification of specific behaviour. Application specific details for applications residing on an UICC are specified in the respective application specific documents.
Up

1  Scopep. 24

The present document provides application behavioural tests for a UE to interoperability with dedicated 3GPP network operations. Where there shall be a description for each compliant implementation including the:
  • the test case specific setting of the USIM;
  • the applicability of each test case;
  • the test configurations;
  • the conformance requirement(s) and reference(s) to the related core specifications;
  • the test purposes; and
  • a brief description of the test procedure and the specific acceptance criteria.
The present document is applicable for MEs supporting a non-removable UICC only. MEs that allow access to the physical card interface as defined in ETSI TS 102 221 [8] or ETSI TS 102 671 [29] shall be tested in accordance to TS 31.121.
This document shall provide alternative verification and testing approaches for test cases initially defined in TS 31.121. If no ETSI or 3GPP defined alternative method to verify an existing requirement is available or if the result generated by the proposed verification method is less reliable, this has to be clearly stated in the test description.
Due to possible limitations in profile handling and updating it is not intended to use the test case defined within this document with 2G only MEs or MEs implemented in accordance to Rel-12 or earlier.
A 3GPP ME may support functionality that is not required by 3GPP, but the requirements to do so are outside of the scope of 3GPP. The present document does not contain tests for features that are out of scope of 3GPP.
In the present document, unless explicitly stated otherwise, for Rel-13 onwards the term E-UTRAN implicitly refers to E-UTRAN in WB-S1 mode. E-UTRAN in NB-S1 mode is always explicitly referred to as NB-IoT.
Up

Up   Top   ToC