Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 31.102  Word version:  17.8.0

Top   Top   Up   Prev   Next
0…   3…   4…   4.2.9…   4.2.17…   4.2.26…   4.2.34…   4.2.44…   4.2.52…   4.2.60…   4.2.68…   4.2.76…   4.2.85…   4.2.93…   4.2.101…   4.2.107…   4.3…   4.4.2…   4.4.2.4…   4.4.3…   4.4.4…   4.4.5…   4.4.6…   4.4.8…   4.4.8.7…   4.4.9…   4.4.11…   4.4.11.7…   4.4.11.17…   4.4.12…   4.5…   4.6…   4.7   5…   5.2…   5.3…   5.4…   5.9…   6…   7…   7.1.2…   7.3…   A   B…   D   E…   G   H…   I…   L…   M…

 

5  Application protocolp. 258

The requirements stated in the corresponding clause of TS 31.101 apply to the USIM application.
The procedures listed in clause "USIM management procedures" are required for execution of the procedures in the subsequent clauses "USIM security related procedures" and "Subscription related procedures". The procedures listed in clauses "USIM security related procedures" are mandatory. The procedures listed in "Subscription related procedures" are only executable if the associated services, which are optional, are provided in the USIM. However, if the procedures are implemented, it shall be in accordance with clause "Subscription related procedures".
If a procedure is related to a specific service indicated in the USIM Service Table, it shall only be executed if the corresponding bits denote this service as "service available" (see EFUST). In all other cases the procedure shall not start.
Up

5.1  USIM management proceduresp. 258

If a USIM application is present on the UICC, a 3GPP ME shall only use the USIM application regardless of the radio access technology in use. In this case, a possibly existing SIM application shall never be used by a 3GPP ME.

5.1.1  Initialisationp. 259

5.1.1.1  USIM application selectionp. 259

After UICC activation (see TS 31.101), the ME selects a USIM application. If no EFDIR file is found or no USIM applications are listed in the EFDIR file, the ME may then try to select the GSM application as specified in TS 51.011.
After a successful USIM application selection, the selected USIM (AID) is stored on the UICC. This application is referred to as the last selected USIM application. The last selected USIM application shall be available on the UICC after a deactivation followed by an activation of the UICC.
If a USIM application is selected using partial DF name, the partial DF name supplied in the command shall uniquely identify a USIM application. Furthermore if a USIM application is selected using a partial DF name as specified in TS 31.101 indicating in the SELECT command the last occurrence the UICC shall select the USIM application stored as the last USIM application. If, in the SELECT command, the options first, next/previous are indicated, they have no meaning if an application has not been previously selected in the same session and shall return an appropriate error code.
Up

5.1.1.2  USIM initialisationp. 259

The ME requests the emergency call codes. For service requirements, see TS 22.101.
The ME requests the Language Indication. The preferred language selection shall always use the EFLI in preference to the EFPL at the MF unless any of the following conditions applies:
  • if the EFLI has the value 'FFFF' in its highest priority position, then the preferred language selection shall be the language preference in the EFPL at the MF level according the procedure defined in TS 31.101;
  • if the ME does not support any of the language codes indicated in EFLI, or if EFLI is not present, then the language selection shall be as defined in EFPL at the MF level according the procedure defined in TS 31.101;
  • if neither the languages of EFLI nor EFPL are supported by the terminal, then the terminal shall use its own internal default selection.
The ME then runs the user verification procedure. If the procedure is not performed successfully, the USIM initialisation stops.
The ME performs the administrative information request.
The ME performs the USIM Service Table request.
The ME performs the Enabled Services Table Request.
In case FDN is enabled, an ME which does not support FDN shall allow emergency calls but shall not allow MO calls and MO-SMS.
If BDN is enabled, an ME which does not support Call Control shall allow emergency calls but shall not allow MO calls.
If ACL is enabled, an ME which does not support ACL shall not send any APN to the network.
If all these procedures have been performed successfully then 3G session shall start. In all other cases 3G session shall not start.
Afterwards, the ME runs the following procedures if the ME and the USIM support the related services:
  • SUPI_NAI request if service No. 130 is "available";
  • Access control information request and/or UAC Access Identities Configuration procedure;
  • Higher Priority PLMN search period request;
  • EHPLMN request
  • HPLMN selector with Access Technology request;
  • User controlled PLMN selector with Access Technology request;
  • Operator controlled PLMN selector with Access Technology request;
  • GSM initialisation requests;
  • Location Information request for CS-and/or PS-mode and/or EPS and/or 5GS;
  • Cipher key and integrity key request for CS- and/or PS-mode;
  • EPS NAS Security Context request for EPS
  • 5GS NAS Security Context request for 5GS;;
  • Forbidden PLMN request;
  • Initialisation value for hyperframe number request;
  • Maximum value of START request;
  • CBMID request;
  • Depending on the further services that are supported by both the ME and the USIM the corresponding EFs have to be read.
After the USIM initialisation has been completed successfully, the ME is ready for a 3G session and shall indicate this to the USIM by sending a particular STATUS command.
Up

5.1.1.3  GSM related initialisation proceduresp. 260

If GSM access is enabled the following procedures shall be performed if the applicable service is enabled and if the ME supports the GSM compact access technology.
  • Investigation Scan request;
  • CPBCCH information request.

5.1.2  Session terminationp. 260

5.1.2.1  3G session terminationp. 260

The 3G session is terminated by the ME as follows.
The ME shall indicate to the USIM by sending a particular STATUS command that the termination procedure is starting.
The ME then runs all the procedures which are necessary to transfer the following subscriber related information to the USIM, if the ME and the USIM support the related services:
  • Location Information update for CS-and/or PS-domain and/or EPS and/or 5GS.
  • Cipher Key and Integrity Key update for CS-and/or PS-domain.
  • EPS NAS Security Context update for EPS domain.
  • 5GS NAS Security Context update for 5GS domain.
  • Advice of Charge increase.
  • Forbidden PLMN update.
  • GSM Termination procedures.
Finally, the ME deletes all these subscriber related information elements from its memory.
To actually terminate the session, the ME shall then use one of the mechanisms described in TS 31.101.
Up
5.1.2.1.1  GSM termination procedures |R6|p. 261
If GSM access is enabled the following termination procedures shall be performed if the applicable service is enabled.
  • CPBCCH information update (if the ME supports the GSM compact access technology);

5.1.2.2  3G session resetp. 261

The ME shall follow the 3G session termination procedure defined above except that the ME shall use the Application session reset procedure as described in TS 31.101 instead of one of the mechanisms to terminate the session.

5.1.3  USIM application closurep. 261

After termination of the 3G session as defined in clause 5.1.2 the USIM application may be closed by closing the logical channels that are used to communicate with this particular USIM application.

5.1.4  Emergency call codesp. 261

Request:
The ME performs the reading procedure with EFECC. If EFECC does not contain any valid number, the ME shall use the emergency numbers it stores for use in setting up an emergency call without a USIM.
Update:
The ME performs the updating procedure with EFECC.

5.1.5  Language indicationp. 261

Request:
The ME performs the reading procedure with EFLI.
Update:
The ME performs the updating procedure with EFLI.

5.1.6  Administrative information requestp. 261

The ME performs the reading procedure with EFAD.

5.1.7  USIM service table requestp. 261

The ME performs the reading procedure with EFUST.

5.1.8Void

5.1.9  UICC presence detectionp. 261

The ME checks for the presence of the UICC according to TS 31.101 within all 30s periods of inactivity on the UICC-ME interface during a call. If the presence detection according to TS 31.101 fails the call shall be terminated as soon as possible but at least within 5s after the presence detection has failed. Here a call covers a circuit switched call, and/or an active PDP context, and/ or an active EPS bearer context and/or an active 5GS PDU session.
The ME may suspend the UICC presence detection based on STATUS commands in case it has an active PDP context, an active EPS bearer context or an active 5GS PDU session, but has not exchanged any data with the network within a 30s period of inactivity on the UICC-ME interface, and resume it as soon as data is exchanged with the network, sending immediately a new STATUS command. For emergency services, if UICC presence detection fails during a call the service may not be terminated.
Up

5.1.10  UICC interface in PSM |R13|p. 262

As defined in TS 23.682, PSM is intended for UEs that are expecting only infrequent mobile originating and terminating services and that can accept a corresponding latency in the mobile terminating communication. The following procedures may be used by the ME in order to reduce power consumption while in PSM.
If the UICC supports the UICC suspension mechanism (SUSPEND UICC command), the ME may suspend the UICC after entering the PSM. In this case, the ME shall successfully resume the UICC before it can leave the PSM.
If the UICC does not support the UICC suspension mechanism, and only in case the PIN of the USIM is disabled, the ME may optionally deactivate the UICC (as specified in clause 6A.1 of TS 31.101) after entering the PSM. In this case, the ME shall perform these steps before it can leave the PSM:
  • re-activate the UICC (as specified in clause 6A.1 of TS 31.101),
  • re-initialize the USIM (as specified in clause 5.1.1), with the exception of re-reading EFs that are not required for the verification of the USIM,
  • take appropriate steps to verify that the same USIM is used.
Verification shall include at least the check of the content of the following EFs:
When the UE is in PSM and in case the ME wants to deactivate the UICC, it shall wait until the current proactive UICC session, if any, is terminated and/or any currently open BIP session is closed.
Up

5.1.11  UICC interface during eDRX |R13|p. 262

In order to reduce power consumption when the UE uses extended idle mode DRX cycle, as defined in TS 24.301, in case the UICC supports the UICC suspension mechanism (SUSPEND UICC command), the ME may suspend the UICC during the extended idle mode DRX cycle. In this case, the ME shall resume the UICC successfully before the end of the extended idle mode DRX cycle or before any other transmission to the network.
In case the UICC does not support the UICC suspension mechanism, the PIN of the USIM is disabled and deactivation of UICC is authorized in EFAD, the UE may optionally deactivate the UICC (as specified in clause 6A.1 of TS 31.101) during the extended idle mode DRX cycle. In this case, the UE shall re-activate the UICC (as specified in clause 6A.1 of TS 31.101), re-initialize the USIM (as specified in clause 5.1.1) and take appropriate steps to verify that the same USIM is used, before the end of the extended idle mode DRX cycle or before any other transmission to the network.
Verification shall include at least the check of the content of the following EFs:
When the UE is in extended idle mode DRX cycle and in case the ME wants to deactivate the UICC, it shall wait until the current proactive UICC session, if any, is terminated and/or any currently open BIP session is closed
Up

5.1.12  UICC interface during MICO |R15|p. 263

As described in TS 24.501, the UE can make use of MICO in order to optimize power consumption and signalling efficiency. The following procedures may be used by the ME in order to reduce power consumption and signalling while in MICO.
If the UICC supports the UICC suspension mechanism (SUSPEND UICC command), the ME may suspend the UICC after entering MICO. In this case, the ME shall successfully resume the UICC before it can leave MICO.
If the UICC does not support the UICC suspension mechanism, and only in case the PIN of the USIM is disabled, the ME may optionally deactivate the UICC (as specified in clause 6A.1 of TS 31.101) after entering MICO. In this case, the ME shall perform these steps before it can leave the MICO:
  • re-activate the UICC (as specified in clause 6A.1 of TS 31.101),
  • re-initialize the USIM (as specified in clause 5.1.1), with the exception of re-reading EFs that are not required for the verification of the USIM,
  • take appropriate steps to verify that the same USIM is used.
Verification shall include at least the check of the content of the following EFs:
When the UE is in MICO and in case the ME wants to deactivate the UICC, it shall wait until the current proactive UICC session, if any, is terminated and/or any currently open BIP session is closed.
Up

Up   Top   ToC