5 Application protocol

31.1023GPPCharacteristics of the Universal Subscriber Identity Module (USIM) applicationRelease 17TS

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

The requirements stated in the corresponding clause of TS 31.101 [11] 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 clause "EF_UST"). In all other cases the procedure shall not start.

5.1 USIM management procedures

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 Initialisation

5.1.1.1 USIM application selection

After UICC activation (see TS 31.101 [11]), the ME selects a USIM application. If no EF_DIR file is found or no USIM applications are listed in the EF_DIR file, the ME may then try to select the GSM application as specified in TS 51.011 [18].

NOTE: there may be cards that need to be reset before selecting the GSM application.

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 [11] 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.

5.1.1.2 USIM initialisation

The ME requests the emergency call codes. For service requirements, see TS 22.101 [24].

The ME requests the Language Indication. The preferred language selection shall always use the EF_LI in preference to the EF_PLat the MF unless any of the following conditions applies:

– if the EF_LI has the value ‘FFFF’ in its highest priority position, then the preferred language selection shall be the language preference in the EF_PLat the MF level according the procedure defined in TS 31.101 [11];

– if the ME does not support any of the language codes indicated in EF_LI, or if EF_LI is not present, then the language selection shall be as defined in EF_PL at the MF level according the procedure defined in TS 31.101 [11];

– if neither the languages of EF_LInor EF_PL 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:

‑ IMSI request if service n°130 is "not available";

‑ SUPI_NAI request if service n°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.

5.1.1.3 GSM related initialisation procedures

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 termination

5.1.2.1 3G session termination

NOTE 1: This procedure is not to be confused with the deactivation procedure in TS 31.101 [11].

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.

NOTE 2: If the ME has already updated any of the subscriber related information during the 3G session, and the value has not changed until 3G session termination, the ME may omit the respective update procedure.

To actually terminate the session, the ME shall then use one of the mechanisms described in TS 31.101 [11].

5.1.2.1.1 GSM termination procedures

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 reset

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 [11] instead of one of the mechanisms to terminate the session.

5.1.3 USIM application closure

After termination of the 3G session as defined in 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 codes

Request: The ME performs the reading procedure with EF_ECC. If EF_ECC 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 EF_ECC.

NOTE: The update procedure is only applicable when access conditions of ADM for update is set to ALW, PIN or PIN2.

5.1.5 Language indication

Request: The ME performs the reading procedure with EF_LI.

Update: The ME performs the updating procedure with EF_LI.

5.1.6 Administrative information request

The ME performs the reading procedure with EF_AD.

5.1.7 USIM service table request

The ME performs the reading procedure with EF_UST.

5.1.8 Void

5.1.9 UICC presence detection

The ME checks for the presence of the UICC according to TS 31.101 [11] within all 30s periods of inactivity on the UICC-ME interface during a call. If the presence detection according to TS 31.101 [11] 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.

5.1.10 UICC interface in PSM

As defined in 3GPP TS 23.682 [78], 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 3GPP TS 31.101 [11]) 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 3GPP TS 31.101 [11]),

– 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:

– EF_ICCID,

– EF_IMSI if Service n°130 is "not available",

– EF_{SUPI_NAI} if service n°130 is "available", and

– EF_LOCI and/or EF_PSLOCI and/or EF_EPSLOCI(depending on which of these specific EFs containing LOCI the ME used prior to entering PSM).

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.

5.1.11 UICC interface during eDRX

In order to reduce power consumption when the UE uses extended idle mode DRX cycle, as defined in 3GPP TS 24.301 [51], 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 EF_AD, the UE may optionally deactivate the UICC (as specified in clause 6A.1 of 3GPP TS 31.101 [11]) during the extended idle mode DRX cycle. In this case, the UE shall re-activate the UICC (as specified in clause 6A.1 of 3GPP TS 31.101 [11]), 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:

— EF_ICCID,

– EF_IMSI if Service n°130 is "not available",

– EF_{SUPI_NAI} if service n°130 is "available",

– EF_LOCI and/or EF_PSLOCI and/or EF_EPSLOCI(depending on which of these specific EFs containing LOCI the ME used prior to applying eDRX).

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.

5.1.12 UICC interface during MICO

As described in 3GPP TS 24.501 [104], 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 3GPP TS 31.101 [11]) 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 3GPP TS 31.101 [11]),

– 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:

– EF_ICCID,

— EF_IMSI if Service n°130 is "not available",

– EF_{SUPI_NAI} if service n°130 is "available", and

– EF_LOCI and/or EF_PSLOCI and/or EF_EPSLOCIand/or EF_5GS3GPPLOCI (depending on which of these specific EFs containing LOCI the ME used prior to entering MICO).

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.

5.2 USIM security related procedures

5.2.1 Authentication algorithms computation

The ME selects a USIM application and uses the AUTHENTICATE command (see 7.1.1). The response is sent to the ME (in case of the T=0 protocol when requested by a subsequent GET RESPONSE command).

After a successful AUTHENTICATE command, the ME shall perform cipher and integrity key update procedure.

5.2.2 IMSI request

Requirement: Service n°130 is "not available".

Request: The ME performs the reading procedure with EF_IMSI.

5.2.3 Access control information request

The ME performs the reading procedure with EF_ACC.

5.2.4 Higher Priority PLMN search period request

The ME performs the reading procedure with EF_HPPLMN.

5.2.5 Location information

Request: The ME performs the reading procedure with EF_LOCI.

Update: The ME performs the updating procedure with EF_LOCI.

In the case when updating EF_LOCI with data containing the TMSI value and the card reports the error ‘6581’ (Memory Problem), the ME shall terminate 2G or 3G operation.

5.2.6 Cipher and Integrity key

Request: The ME performs the reading procedure with EF_Keys.

Update: The ME performs the updating procedure with EF_Keys.

5.2.7 Forbidden PLMN

Request: The ME performs the reading procedure with EF_FPLMN.

Update: The ME performs the updating procedure with EF_FPLMN.

5.2.8 Void

5.2.9 User Identity Request

The ME selects a USIM and performs:

– If Service n°130 is "not available", the reading procedure with EF_IMSI.

– If Service n°130 is "available", the reading procedure with EF_{SUPI_NAI}.

5.2.10 GSM Cipher key

Requirement: Service n°27 "available".

Request: The ME performs the reading procedure with EF_Kc.

Update: The ME performs the updating procedure with EF_Kc.

5.2.11 GPRS Cipher key

Requirement: Service n°27 "available".

Request: The ME performs the reading procedure with EF_KcGPRS.

Update: The ME performs the updating procedure with EF_KcGPRS.

5.2.12 Initialisation value for Hyperframe number

Request: The ME performs the reading procedure with EF_START-HFN.

Update: The ME performs the updating procedure with EF_START-HFN.

5.2.13 Maximum value of START

Request: The ME performs the reading procedure with EF_THRESHOLD.

5.2.14 HPLMN selector with Access Technology request

Request: The ME performs the reading procedure with EF_HPLMNwAcT.

5.2.15 Packet Switched Location information

Request: The ME performs the reading procedure with EF_PSLOCI.

Update: The ME performs the updating procedure with EF_PSLOCI.

5.2.16 Cipher and Integrity key for Packet Switched domain

Request: The ME performs the reading procedure with EF_KeysPS.

Update: The ME performs the updating procedure with EF_KeysPS.

5.2.17 LSA information

Requirement: Service n°23 "available".

Request: The ME performs the reading procedure with EF_SAI, EF_SLL and its associated LSA Descriptor files.

Update: The ME performs the updating procedure with EF_SLL.

5.2.18 Voice Group Call Services

Requirement: Service n°57 "available".

Voice Group Call Service

Request: The ME performs the reading procedure with EFVGCS.

Voice Group Call Service Status

Request: The ME performs the reading procedure with EFVGCSS.

Update: The ME performs the updating procedure with EFVGCSS.

5.2.19 Voice Broadcast Services

Requirement: Service n°58 "available".

Voice Broadcast Service

Request: The ME performs the reading procedure with EF_VBS.

Voice Broadcast Service Status

Request: The ME performs the reading procedure with EF_VBSS.

Update: The ME performs the updating procedure with EF_VBSS.

5.2.20 Generic Bootstrapping architecture (Bootstrap)

The ME uses the AUTHENTICATE command in GBA security context (Bootstrapping Mode) (see 7.1.1). The response is sent to the ME.

After a successful GBA_U Procedure, the ME shall update the B-TID field and the Key Life Time field in EF_GBABP

5.2.21 Generic Bootstrapping architecture (NAF Derivation)

The ME shall first read EF_GBABP. The ME then uses the AUTHENTICATE command in GBA security context (NAF Derviation Mode) (see 7.1.1). The response is sent to the ME.

5.2.22 MSK MIKEY Message Reception

The ME performs the reading of EF_MUK and retrieves the Time Stamp Counter Value associated with the involved MUK. Then it proceeds with Timestamp Payload checking as described in TS 33.246 [43].

5.2.23 MTK MIKEY Message Reception

The ME performs the reading of EF_MSK and retrieves the Time Stamp Counter Value associated with the involved MSK. Then it proceeds with Timestamp Payload checking as described in TS 33.246 [43].

5.2.24 Void

5.2.25 EHPLMN request

Requirement: Service n°71 "available".

Request: The ME performs the reading procedure with EF_EHPLMN.

5.2.26 Last RPLMN Selection Indication request

Requirement: Service n°74 "available".

Request: The ME performs the reading procedure with EF_LRPLMNSI.

5.2.27 EPS Location Information

Requirement: Service n°85 "available".

Request: The ME performs the reading procedure with EF_EPSLOCI.

Update: The ME performs the updating procedure with EF_EPSLOCI.

5.2.28 EPS NAS Security Context

Requirement: Service n°85 "available".

Request: The ME performs the reading procedure with EF_EPSNSC.

Update: The ME performs the updating procedure with EF_EPSNSC.

In order to prevent UICC memory wear out due to excessive writing, the update of EPS NAS security context shall be according to the rules and procedures specified in TS 33.401 [52].

5.2.29 Non Access Stratum Configuration

Requirement: Service n°96 "available".

Request: The ME performs the reading procedure with EF_NASCONFIG.

For each NAS configuration parameter, a parameter provided in EF_NASCONFIG shall take precedence over the corresponding parameter stored in the ME’s non-volatile memory.

5.2.30 PWS Configuration

Requirement: Service n°97 "available".

Request: The ME performs the reading procedure with EF_PWS.

5.2.31 5GS Location Information

Requirement: Service n°122 "available".

Request: The ME performs the reading procedure with EF_5GS3GPPLOCI or with EF_5GSN3GPPLOCI.

Update: The ME performs the updating procedure with EF_5GS3GPPLOCI or with EF_{5GSN3GPPLOCI.}

5.2.32 5GS NAS Security Context

Requirement: Service n°122 "available".

Request: The ME performs the reading procedure with EF5GS3GPPNSC and EF5GSN3GPPNSC.

If service n°136 is "available" in addition, the ME shall associate the NAS security context to the appropriate PLMN by parsing the two records and by retrieving the matching PLMN identifier of the second record.

5GS NAS Security Context in the first record shall be associated with 5G GUTI in the 5G LOCI file for the same access type (e.g. EF5GS3GPPNSC) and the 5GS NAS Security Context in the second record shall be associated with the 5G GUTI as indicated in the PLMN Identifier.

Update: The ME performs the updating procedure with EF5GS3GPPNSC and EF5GSN3GPPNSC as described in TS 24.501 clauses 4.4.2.1 and C.1 in Annex C.

In order to prevent UICC memory wear out due to excessive writing, the update of 5GS NAS security context shall be according to the rules and procedures specified in TS 33.501 [104].

5.2.33 SUPI_NAI request

Requirement: Service n°130 is "available".

Request: The ME performs the reading procedure with EF_{SUPI_NAI}.

5.2.34 URSP request

Requirement: Service n°132 is "available".

Request: The ME performs the reading procedure with EF_URSP.

How the ME uses the URSP rules defined in EF_URSP is specified in 3GPP TS 24.526 [109] clause 4.2.2.2.

5.2.35 Trusted non-3GPP Serving network name list request

Requirement: Service n°135 is "available".

Request: The ME performs the reading procedure with EF_TN3GPPSNN.

5.2.36 Steering of roaming connected mode control information request

Requirement: Service n°138 is "available".

Request: The ME performs the reading procedure with EF_SOR-CMCI as specified in 3GPP TS 23.122 [31].

5.3 Subscription related procedures

5.3.1 Phone book procedures

5.3.1.1 Initialisation

The ME first reads the content of EF_PBRto determine the configuration phonebook. If the EF_IAP file is indicated in EF_PBRfollowing tag ‘A8’ the ME reads the content of EF_IAP in order to establish the relation ship between the content in the files indicated using tag ‘A9’ and files indicated by tag ‘A8’. The ME may read the contents of the phone book related files in any order.

5.3.1.2 Creation/Deletion of information

In order to avoid unlinked data to introduce fragmentation of the files containing phone book data the following procedures shall be followed when creating a new entry in the phone book. The data related to EF_ADN is first stored in the relevant record. As the record number is used as a pointer the reference pointer is now defined for the entry. The rule for storing additional information for an entry is that the reference pointer shall be created before the actual data is written to the location.

In case of deletion of a complete or part of an entry the data shall be deleted first followed by the reference pointer for that data element. In case of deletion of a complete entry the contents of EF_ADN is the last to be deleted.

5.3.1.3 Hidden phone book entries

If a phone book entry is marked as hidden by means of EF_PBCthe ME first prompts the user to enter the ‘Hidden Key’. The key presented by the user is compared against the value that is stored in the corresponding EF_Hiddenkey. Only if the presented and stored hidden key are identical the ME displays the data stored in this phone book entry. Otherwise the content of this phone book entry is not displayed by the ME.

Even if the terminal does not support the Hidden Key Procedures, a hidden phone book entry shall not be displayed by the terminal.

Request: The ME performs the reading procedure with EF_Hiddenkey.

Update: The ME performs the updating procedure with EF_Hiddenkey.

5.3.2 Dialling numbers

Requirements:

– Service n°1 "available" for ADN located under the local phonebook;

– Presence of EF_ADN in EF_PBR for ADN located under the global phonebook;

– Presence of EF_ANR in EF_PBR for ANR;

– Service n°2 "available" for FDN;

– Service n°21 "available" for MSISDN;

– Service n°4 "available" for SDN;

– Service n°6 "available" for BDN;

– Service n°8 "available" for EFOCI;

– Service n°9 "available" for EFICI.

The following procedures may not only be applied to EF_ADN and its associated extension files EF_CCP1 and EF_EXT1 as described in the procedures below, but also to EF_ANR, EF_FDN, EF_MSISDN, EF_BDN, EF_SDN, EF_OCI,EF_ICI, and EF_MBDNand their associated extension files. If these files are not "available", as denoted in the USIM service table, the current procedure shall be aborted and the appropriate Efs shall remain unchanged.

As an example, the following procedures are described as applied to ADN.

Update: The ME analyses and assembles the information to be stored as follows (the byte identifiers used below correspond to those in the definition of the relevant Efs in the present document):

i) The ME identifies the Alpha‑tagging, Capability/Configuration1 Record Identifier and Extension1 Record Identifier.

ii) The dialling number/SSC string shall be analysed and allocated to the bytes of the EF as follows:

‑ if a "+" is found, the TON identifier is set to "International";

‑ if 20 or less "digits" remain, they shall form the dialling number/SSC string;

‑ if more than 20 "digits" remain, the procedure shall be as follows:

– The ME seeks for a free record in EF_EXT1. If an Extension1 record is not marked as "free", the ME runs the Purge procedure. If an Extension1 record is still unavailable, the procedure is aborted.

– The first 20 "digits" are stored in the dialling number/SSC string. The value of the length of BCD number/SSC contents is set to the maximum value, which is 11. The Extension1 record identifier is coded with the associated record number in the EF_EXT1. The remaining digits are stored in the selected Extension1 record where the type of the record is set to "additional data". The first byte of the Extension1 record is set with the number of bytes of the remaining additional data. The number of bytes containing digit information is the sum of the length of BCD number/SSC contents of EF_ADN and byte 2 of all associated chained Extension1 records containing additional data.

iii) If a called party subaddress is associated to the ADN/SSC the procedure shall proceed as follows:

– If the length of the called party subaddress is less than or equal to 11 bytes (see TS 24.008 [9] for coding):

– The ME stores the called party subaddress in the Extension1 record, and sets the Extension1 record type to "called party subaddress".

– If the length of the called party subaddress is greater than 11 bytes (see TS 24.008 [9] for coding):

– The ME seeks for two free records in EF_EXT1. If no such two records are found, the ME runs the Purge procedure. If two Extension1 records are still unavailable, the procedure is aborted.

– The ME stores the called party subaddress in the two Extension1 records. The identifier field in the Extension1 record containing the first part of the subaddress data is coded with the associated EF_EXT1 record number containing the second part of the subaddress data. Both Extension1 record types are set to "called party subaddress".

Once i), ii), and iii) have been considered the ME performs the updating procedure with EF_ADN. If the USIM has no available empty space to store the received ADN/SSC, or if the procedure has been aborted, the ME advises the user.

For reasons of memory efficiency, the ME may analyse all Extension1 records to recognise if the additional or subaddress data to be stored is already existing in EF_EXT1. In this case, the ME may use the existing chain or the last part of the existing chain from more than one ADN. The ME is only allowed to store extension data in unused records. If existing records are used for multiple access, the ME shall not change any data in those records to prevent corruption of existing chains.

Erasure: The ME sends the identification of the information to be erased. The content of the identified record in EF_ADN is marked as "free".

Request: The ME sends the identification of the information to be read. The ME shall analyse the data of EF_ADNto ascertain, whether additional data is associated in EF_EXT1 or EF_CCP1. If necessary, then the ME performs the reading procedure on these Efs to assemble the complete ADN/SSC.

Purge: The ME shall access each EF which references EF_EXT1 (EF_EXT2, EF_EXT6) for storage and shall identify records in these files using extension data (additional data or called party subaddress). Note that existing chains have to be followed to the end. All referred Extension1 (Extension2, Extension6) records are noted by the ME. All Extension1 (Extension2, Extension6) records not noted are then marked by the ME as "free" by setting the whole record to ‘FF’.

The following three procedures are only applicable to service n°2 (FDN).

FDN capability request. The ME shall check the state of service n°2, i.e. if FDN is "enabled" or "disabled". If FDN is enabled, the ME shall only allow outgoing calls as defined in the fixed number dialling description in TS 22.101 [24]. To ascertain the state of FDN, the ME shall check in EFUST and EFEST if FDN is enabled (service activated and available). In all other cases service n°2 is disabled.

FDN enabling is done by activating the FDN service in EFEST.

FDN disabling is done by deactivating the FDN service in EFEST.

The following three procedures are only applicable to service n°6 (BDN).

– BDN capability request. The ME shall check the state of service n°6, i.e. if BDN is "enabled" or "disabled". To ascertain the state of BDN, the ME shall check in EFUST and EFEST if BDN is "enabled" (service available and activated). In all other cases, the BDN service is "disabled".

– BDN enabling is done by activating the BDN service in EFEST.

– BDN disabling is done by deactivating the BDN service in EFEST.

5.3.3 Short messages

Requirement: Service n°10 "available".

Request: The USIM seeks for the identified short message. If this message is found, the ME performs the reading procedure with EF_SMS.

If service n°10 is "available" and the status of the SMS is ‘1D’ (status report requested, received and stored in EF_SMSR), the ME performs the reading procedure with the corresponding record in EF_SMSR. If the ME does not find a corresponding record in EF_SMSR, then the ME shall update the status of the SMS with ’15’ (status report requested, received but not stored in EF_SMSR).

If the short message is not found within the USIM memory, the USIM indicates that to the ME.

Update: The ME looks for the next available area to store the short message. If such an area is available, it performs the updating procedure with EF_SMS.

If there is no available empty space in the USIM to store the received short message, a specific MMI will have to take place in order not to loose the message.

Erasure: The ME will select in the USIM the message area to be erased. Depending on the MMI, the message may be read before the area is marked as "free". After performing the updating procedure with EF_SMS, the memory allocated to this short message in the USIM is made available for a new incoming message. The memory of the USIM may still contain the old message until a new message is stored in this area.

If service n°11 is "available" and the status of the SMS is ‘1D’ (status report requested, received and stored in EF_SMSR), the ME performs the erasure procedure for EF_SMSR with the corresponding record in EF_SMSR.

5.3.4 Advice of charge

Requirement: Service n°13 "available".

Accumulated Call Meter.

Request: The ME performs the reading procedure with EF_ACM. The USIM returns the last updated value of the ACM.

Initialisation: The ME performs the updating procedure with EF_ACM using the new initial value.

Increasing: The ME performs the increasing procedure with EF_ACMsending the value which has to be added.

Accumulated Call Meter Maximum Value.

Request: The ME performs the reading procedure with EF_ACMmax.

Initialisation: The ME performs the updating procedure with EF_ACMmax using the new initial maximum value.

Price per Unit and Currency Table (PUCT).

Request: The ME performs the reading procedure with EF_PUCT.

Update: The ME performs the updating procedure with EF_PUCT.

5.3.5 Capability configuration parameters

Requirement: Service n°14 "available".

Request: The ME performs the reading procedure with EF_CCP2.

Update: The ME performs the updating procedure with EF_CCP2.

Erasure: The ME sends the identification of the requested information to be erased. The content of the identified record in EF_CCP2 is marked as "free".

5.3.6 User controlled PLMN selector with Access Technology

Requirement: Service n°20 "available".

Request: The ME performs the reading procedure with EF_PLMNwACT.

Update: The ME performs the updating procedure with EF_PLMNwACT.

5.3.7 Cell broadcast message identifier

Requirement: Service n°15 "available".

Request: The ME performs the reading procedure with EF_CBMI.

Update: The ME performs the updating procedure with EF_CBMI.

5.3.8 Group identifier level 1

Requirement: Service n°17 "available".

Request: The ME performs the reading procedure with EF_GID1.

5.3.9 Group identifier level 2

Requirement: Service n°18 "available".

Request: The ME performs the reading procedure with EF_GID2.

5.3.10 Service provider name

Requirement: Service n°19 "available".

Request: The ME performs the reading procedure with EF_SPN.

5.3.11 Enhanced multi level precedence and pre-emption service

Requirement: Service n°24 "available".

Request: The ME performs the reading procedure with EF_eMLPP.

5.3.12 Cell broadcast message identifier ranges

Requirement: Service n°16 "available".

Request: The ME performs the reading procedure with EF_CBMIR.

Update: The ME performs the updating procedure with EF_CBMIR.

5.3.13 Short message status report

Requirement: Service n°11 "available".

Request: If the status of a stored short message indicates that there is a corresponding status report, the ME performs the reading procedure on the records of EF_SMSR and identifies the record containing the appropriate status report.

Update: If a status report is received, the ME first seeks within the SMS record identifiers of EF_SMSR for the same record number it used for the short message in EF_SMS. If such a record identifier is found in EF_SMSR, it is used for storage. If such a record identifier is not found, then the ME seeks for a free entry in EF_SMSR for storage. If no free entry is found the ME runs the Purge procedure with EF_SMSR. If there is still no free entry, the status report is not stored.

If the ME found an appropriate record in EF_SMSR for storage, it updates the record with the status report setting the record identifier in EF_SMSR to the appropriate record number of the short message in EF_SMS.

The status in EF_SMS is updated accordingly by performing the update procedure with EF_SMS.

Erasure: The ME runs the update procedure with EF_SMSR by at least storing ’00’ in the first byte of the record. The ME may optionally update the following bytes with ‘FF’.

Purge: The ME shall read the SMS record identifier (byte 1) of each record of EF_SMSR. With each record the ME checks the corresponding short messages in EF_SMS. If the status (byte 1) of the corresponding SMS is not equal ‘1D’ (status report requested, received and stored in EF_SMSR), the ME shall perform the erasure procedure with the appropriate record in EF_SMSR.

5.3.14 APN Control List

Requirement: Service n°35 "available".

Request: The ME performs the reading procedure with EF_ACL.

Update: The ME performs the updating procedure with EF_ACL.

Enabling: The ME activates service n°3 in EF_EST (bit n°3 set to "1").

Disabling: The ME deactivates service n°3 in EF_EST (bit n°3 set to "0").

When the APN Control List service is enabled, the ME shall check that the entire APN of any PDP context is listed in EF_ACL before requesting this PDP context activation from the network. If the APN is not present in EF_ACL, the ME shall not request the corresponding PDP context activation from the network.

In the case that the APN Control List is enabled and no APN is indicated in the PDP context request, indicating that a network provided APN is to be used, then the ME shall only request the PDP context activation if "network provided APN" is contained within EF_ACL.

If the APN Control List service is enabled and the ME is to provide an APN as part of attach for PDN connectivity, then the ME shall verify that the APN value is present in the EF_ACL and if it is not the ME shall not proceed with the attach procedure. If the APN Control List service is enabled and the ME does not indend to provide an APN as part of the attach for PDN connectivity and use a network provided APN, the ME shall not check if "network provided APN" is contained within EF_ACL.

If the APN Control List service is enabled and the ME is to provide a DNN as part of PDU session establishment, then the ME shall verify that the DNN value is present in the EF_ACL and if it is not the ME shall not proceed with the PDU session establishment procedure. If the APN Control List service is enabled and the ME does not intend to provide a DNN as part of the PDU session establishment and use a network provided DNN, the ME shall not check if "network provided DNN" is contained within EF_ACL.

5.3.15 Depersonalisation Control Keys

Requirement: Service n°36 "available".

Request: The ME performs the reading procedure with EF_DCK.

5.3.16 Co-operative Network List

Requirement: Service n°37 "available".

Request: The ME performs the reading procedure with EF_CNL.

5.3.17 CPBCCH information

Requirement: Service n°39 "available".

Request: The ME performs the reading procedure with EF_CPBCCH.

Update: The ME performs the updating procedure with EF_CPBCCH.

5.3.18 Investigation Scan

Requirement: Service n°40 "available".

Request: The ME performs the reading procedure with EF_InvScan.

5.3.19 Enabled Services Table Request

Requirement: Service n°2, 6, 34 or 35 "available".

Request: The ME performs the reading procedure with EF_EST.

Update: The ME performs the updating procedure with EF_EST.

5.3.20 Operator controlled PLMN selector with Access Technology

Requirement: Service n°42 "available".

Request: The ME performs the reading procedure with EF_OPLMNwACT

5.3.21 HPLMN selector with Access Technology

Requirement: Service n°43 "available".

Request: The ME performs the reading procedure with EFHPLMNwACT

5.3.22 Automatic Answer on eMLPP service

Requirement: Service n°25 "available"

Request: The ME performs the reading procedure with EF_AaeM.

Update: The ME performs the updating procedure with EF_AaeM.

5.3.23 Network Parameter information

Request: The ME performs the reading procedure with EF_NETPAR.

Update: The ME performs the updating procedure with EF_NETPAR.

5.3.24 PLMN network name

Requirement: Service n°45 "available".

Request: The ME performs the reading procedure with EF_PNN.

5.3.25 Operator PLMN List

Requirement: Service n°46 "available".

Request: The ME performs the reading procedure with EF_OPL

5.3.26 Message Waiting Indication

Requirement: Service n°48 "available".

Request: The ME performs the reading procedure with EF_MWIS.

Update: The ME performs the updating procedure with EF_MWIS.

5.3.27 Call Forwarding Indication Status

Requirement: Service n°49 "available".

Request: The ME performs the reading procedure with EF_CFIS.

Update: The ME performs the updating procedure with EF_CFIS.

5.3.28 Service Provider Display Information

Requirement: Service n°19 and 51 are "available".

Request: The ME performs the reading procedure with EF_SPDI.

Update: The ME performs the updating procedure with EF_SPDI.

5.3.29 MMS Notifications

Requirement: Service n°52 "available".

Request: The ME sends the identification of the information to be read, then the ME performs the reading procedure with EF_MMSN. If Service n°53 is available the ME shall analyse the data of EF_MMSN to ascertain, whether additional data is associated in EF_EXT8. If necessary, then the ME performs the reading procedure on EF_EXT8to assemble the complete MMS notification.

Update: The ME analyses and assembles the MMS notification to be stored as follows:

– if the MMS notification contains not more bytes than the maximum possible number for EF_MMSN then the ME looks for the next available area to store the MMS notification. If such an area is available, it performs the updating procedure with EF_MMSN.

– if the MMS notification contains more bytes than the maximum possible number for EF_MMSN then the ME seeks for a sufficient number of free records in EF_EXT8 to store the complete MMS notification.

– If there is not a sufficient number of EF_EXT8records marked as "free" to store the complete MMS notification, the procedure is aborted.

– Otherwise, the ME performs the updating procedure and stores as many bytes as possible in EF_MMSN. The Extension file record number of EF_MMSN is coded with the associated record number in the EF_EXT8. The remaining bytes are stored in the selected EF_EXT8record where the type of the record is then set to "additional data". The second byte of the EF_EXT8record is set with the number of bytes of the remaining additional data. It is possible, if the number of additional digits exceeds the capacity of the additional record, to chain another record inside the EF_EXT8by the identifier in the last byte of the record. In this case byte 2 of each record for additional data within the same chain indicates the number of bytes within the same record.

The ME is only allowed to store extension data in unused records of EF_EXT8

If there is no available empty space in the USIM to store the MMS notification, it is up to ME implementation how the notification is handled.

Erasure: The ME will select in the USIM the MMS notification to be erased. Depending on the MMI, the MMS notification may be read before the area is marked as "free". The memory of the USIM may still contain the old MMS notification until a new message is stored. If Service n°53 is available all associated records in EF_EXT8 are then marked by the ME as "free" by setting them to ‘FF’.

5.3.30 MMS Issuer Connectivity Parameters

Requirement: Service n°52 "available".

Request: the ME performs the reading procedure with EF_MMSICP.

Update: The ME performs the updating procedure with EF_MMSICP.

5.3.31 MMS User Preferences

Requirement: Service n°52 "available".

Request: the ME performs the reading procedure with EF_MMSUP.

Update: The ME performs the updating procedure with EF_MMSUP.

5.3.32 MMS User Connectivity Parameters

Requirement: Service n°52 and n°55 "available".

Request: the ME performs the reading procedure with EF_MMSUCP.

Update: The ME performs the updating procedure with EF_MMSUCP.

5.3.33 Network’s indication of alerting

Requirement: Service n°56 "available".

Request: The ME performs the reading procedure with EF_NIA.

5.3.34 Multimedia Messages Storage

If the terminal supports Multimedia Message Storage on the USIM, then the following procedures apply.

As defined in TS 23.140 [38] a Multimedia Message consists of content, or multimedia objects, and headers to describe various properties of that content. An MM is stored in EF_MMDF, a BER-TLV structured file.

A list of multimedia messages is stored in the BER-TLV file EF_MMLwhere each data object identifies one Multimedia Message stored in EF_MMDF.

Prerequisite: Service n°67 "available".

Request: The ME performs the reading procedures on EF_MML to verify the presence and to get the location information of the targeted MM. Then the ME performs the reading procedure of the EF_MMDF file to get the MM.

Update: The ME chooses a free identity (i.e. not listed in EF_MML) for the multimedia message and check for available space in the EF_MMDF file. This procedure could be done for each update or once at the startup of the UE and after a REFRESH command involving one of the DF_MULTIMEDIA files. Then the ME performs the following procedures:

If there is no available empty space in the EF_MMDF file to store the MM, the procedure is aborted and the user is notified.

Else, the ME stores the MM in EF_MMDF, then updates the information in EF_MML accordingly.

Erasure: After a successful deletion of an MM in EF_MMDF the terminal updates the information in EF_MML accordingly.

5.3.35 Equivalent HPLMN Presentation Indication request

Requirement: Service n°73 "available".

Request: The ME performs the reading procedure with EF_EHPLMNPI.

5.3.36 NAF Key Centre Address request

Requirement: Service n°68 and service n°76 "available".

Request: The ME performs the reading procedure with EF_NAFKCA.

5.3.37 Service provider name Icon

Requirement: Service n°19 and service n°78 "available".

Request: The ME performs the reading procedure with EF_SPNand EF_SPNI.

5.3.38 PLMN network name Icon

Requirement: Service n°45 and service n°79 "available".

Request: The ME performs the reading procedure with EF_PNNand EF_PNNI.

5.3.39 ICE Information request

The ICE information shall be accessible even when the security features of the UE or UICC have been enabled. The ICE access procedure is described in TS 22.030 [4]. The terminal shall discover that the ICE feature is supported by the ability to select one of the ICE files i.e. EF_{ICE_DN}, EF_{ICE_FF} or EF_{ICE_graphics}.

Request: The terminal performs the read procedure with EF_{ICE_DN} and/or EF_{ICE_FF} and/or EF_{ICE_graphics}.

Update: The terminal performs the update procedure with EF_{ICE_DN} and/or EF_{ICE_FF} and/or EF_{ICE_graphics}.

Disable ICE display: The terminal performs the deactivate procedure consecutively on all the supported files (EF_{ICE_DN}, EF_{ICE_FF} and EF_{ICE_graphics}).

Enable ICE display: The terminal performs the activate procedure consecutively on all the supported files (EF_{ICE_DN}, EF_{ICE_FF} and EF_{ICE_graphics} ).

The content of the EF_{ICE_DN}, EF_{ICE_FF} and EF_{ICE_graphics} shall be preserved when enabling and disabling the ICE display.

5.3.40 eCall Related Procedures

The eCall feature on the USIM provides two numbers or URIs, a test number or URI and a reconfiguration number or URI, to the terminal to be used with the eCall. eCall support on the USIM is indicated in the service table when Service n° 89 or Service n° 112 is "available".

Depending on the type of eCall support and the domain, EF_FDN or EF_SDN or EF_FDNURI or EF_SDNURI is used to provide the eCall functionality.

5.3.40.1 eCall Only support

Requirement: Service n° 89 is "available" and FDN is enabled (Service n° 2 is "available" and FDN service is enabled in EF_EST).

Request: The ME performs the reading procedure with EF_FDN.

If eCall only calls are supported, then EF_FDN shall only contain two entries. The first entry shall contain the eCall test number and the second entry shall contain the eCall reconfiguration number. These numbers are used for eCall over CS domain. If Service n° 112 or Service n° 99 are not available, these numbers are used also for eCall over IMS Emergency Services using the PS domain in E-UTRAN or in NG-RAN, after being converted into tel URIs. A terminal in eCall only mode performs the FDN related procedures.

Requirement: Service n° 112 and Service n° 99 are "available" and FDN is enabled (Service n° 2 is "available" and FDN service is enabled in EF_EST).

Request: The ME performs the reading procedure with EF_FDNURI.

If eCall only calls are supported, then EF_FDNURI shall only contain two entries. The first entry shall contain the eCall test URI and the second entry shall contain the eCall reconfiguration URI. These URIs are used for eCall over IMS Emergency Services using the PS domain in E-UTRAN or in NG-RAN. A terminal in eCall only mode performs the FDN related procedures.

NOTE: These URIs can contain MSISDNs encoded as tel URIs.

5.3.40.2 eCall and Normal call support

Requirement: Service n° 89 and Service n° 4 are "available" and FDN is disabled (either Service n°2 is not "available" or FDN service is disabled in EF_EST).

Request: The ME performs the reading procedure with EF_SDN.

If eCall and normal calls are supported, then the last two entries of EF_SDN shall contain the eCall test number and the eCall reconfiguration number respectively. These numbers are used for eCalls over CS domain. If Service n° 112 or Service n° 99 are not available, these numbers are used also for eCall over IMS Emergency Services using the PS domain in E-UTRAN or in NG-RAN, after being converted into tel URIs. A terminal in eCall and normal mode performs the SDN related procedures.

Requirement: Service n° 112 and Service n° 99 and Service n° 4 are "available" and FDN is disabled (either Service n°2 is not "available" or FDN service is disabled in EF_EST).

Request: The ME performs the reading procedure with EF_SDNURI.

If eCall and normal calls are supported, then the last two entries of EF_SDNURI shall contain the eCall test URI and the eCall reconfiguration URI respectively. These URIs are used for eCall over IMS Emergency Services using the PS domain in E-UTRAN or in NG-RAN. A terminal in eCall and normal mode performs the SDN related procedures.

NOTE: These URIs can contain MSISDNs encoded as tel URIs.

5.3.40.3 Change of eCall mode

It is possible to re-configure the USIM from eCall only support to eCall and Normal call support, or vice versa, either by changing the content of the USIM Service Table, and/or by changing the content of the EF_EST. The terminal shall be notified of the changes by using the REFRESH proactive command, defined in TS 31.111 [12], using one of the following modes:

– USIM Initialization and File Change Notification

– USIM Initialization and Full File Change Notification

– UICC Reset

– USIM Application Reset

– 3G Session Reset

5.3.41 SM-over-IP

Requirement: Service n°12 and n°91 "available".

Request: the ME performs the reading procedure with EF_PSISMSC.

Update: The ME performs the updating procedure with EF_PSISMSC.

5.3.42 UICC access to IMS

Requirement: Service n°95 is "available" and the ISIM application defined in TS 31.103 [64] is not present on the UICC.

Request: The terminal performs the reading procedure with EF_UICCIARI.

The procedures and command for "UICC access to IMS" are defined in TS 31.111 [12]. An ME supporting UICC access to IMS shall perform the reading procedure with EF_UICCIARI prior to sending a registration to the IMS.

5.3.43 TV Configuration

Requirement: Service n°116 "available".

Request: The ME performs the reading procedure with EF_TVCONFIG.

5.3.44 3GPP PS Data Off related procedures

Requirement: service n°117 is "available" in the USIM Service Table.

Request: If the ME supports 3GPP PS Data Off the ME shall perform the reading procedure with EF_{3GPPPSDataOff.}

5.3.45 3GPP PS Data Off service list related procedures

Requirement: service n°118 is "available" in the USIM Service Table.

Request: If the ME supports 3GPP PS Data Off the ME shall perform the reading procedure with EF_{3GPPPSDATAOFFservicelist}. If the ME performs the reading procedure with EF_{3GPPPSDATAOFFservicelist}, the UE shall use the 3GPP PS Data Off Service list in the EF_{3GPPPSDATAOFFservicelist}as described in TS 24.229 [63] clauses 4.17, B.3.1.5 and L.3.1.5.

5.3.46 EARFCN list for MTC/NB-IOT UEs

Requirement: Service n°121 "available".

Request: The ME performs the reading procedure with EF_EARFCNList.

5.3.47 SUCI Calculation information procedure

Requirement: "SUCI calculation is to be performed by the ME" (i.e. Service n°124 is "available"and Service n°125 is not "available").

Request: As part of the SUCI calculation performed by the ME, the ME performs the reading procedure with EF_{SUCI_Calc_Info}.

5.3.48 SUCI Calculation by the USIM procedure

Requirement: "SUCI calculation is performed by the USIM" (i.e. Service n°124 and Service n°125 are "available").

Request: The ME uses the GET IDENTITY command in SUCI context to retrieve the SUCI calculated by the USIM

Following procedures apply for 5G NSWO authentication.

– If "5G NSWO support" is activated (i.e. Service nº142 is "available"), the ME shall use the GET IDENTITY command in the SUCI 5G NSWO context to retrieve the SUCI calculated by the USIM.

– if USIM service 142 is not available and if the SUPI type is IMSI, the ME shall use the GET IDENTITY command in the SUCI context to retrieve the SUCI calculated by the USIM and contruct the SUCI in the NAI format as below.

– The ME shall construct the realm part of the SUCI using the Home Network Identifier in the SUCI retrieved from the USIM as specified in TS 23.003 [25].

– The ME shall construct the username part of the SUCI using the complete SUCI excluding the Home Network Identifier received from the USIM.

Editors note: CT1 needs to update TS 24.502 [117] on how the ME shall format the SUCI to include the realm part of the SUCI for 5G NSWO. Reference to the clause in 24.502 [117] shall be added here once it is updated.

5.3.49 Control plane-based Steering of Roaming related procedures

If service n°127 is "available" in the USIM Service Table, the Registration Accept shall contain control plane based Steering of Roaming information during the initial registration procedure in a VPLMN.

The control plane-based Steering of Roaming procedure and the related information from the HPLMN are specified in 3GPP TS 23.122 [31].

5.3.50 5GS Operator PLMN List

Requirement: Service n°129 "available".

Request: The ME performs the reading procedure with EF_OPL5G.

5.3.51 Routing Indicator procedure for ME

Requirement: Service n°124 is "available".

Request: As part of the SUCI calculation performed by the ME, the ME performs the reading procedure with EF_{Routing_Indicator}.

5.3.52 5GS eDRX procedure for ME

Requirement: Service n°141 "available".

Request: The ME performs the reading procedure with EF_5GSEDRX.

5.3.53 5G NSWO procedure

Requirement: Service n°142 is "available".

Request: If Non-seamless WLAN offload (NSWO) is supported by the ME, it shall perform the reading procedure with EF_{5GNSWO_CONF} and it shall follow the authentication procedure in 5G NSWO as defined in TS 33.501 [105] Annex S.

5.4 USAT related procedures

5.4.1 Data Download via SMS‑PP

Requirement: USIM Service n°28 "available".

The procedures and commands for Data Download via SMS‑PP are defined in TS 31.111 [12].

5.4.2 Image Request

The terminal sends the identification of the information to be read. The terminal shall analyse the data of EF_IMG to identify the files containing the instances of the image. If necessary, then the terminal performs READ BINARY commands on these files to assemble the complete image instance data.

5.4.3 Data Download via SMS‑CB

Requirement: USIM Service n°29 "available".

The ME shall perform the reading procedure with EF_CBMID, and add the message identifiers to the Cell Broadcast search list. On receiving a cell broadcast message the procedure defined in TS 31.111 [12] applies.

5.4.4 Call Control by USIM

Requirement: USIM Service n°30 "available".

The procedures and commands for Call Control by USIM are defined in TS 31.111 [12]. It is mandatory for the ME to perform the procedures if it has indicated that it supports Call Control by USIM in the TERMINAL PROFILE command.

5.4.5 MO-SMS control by USIM

Requirement: USIM Service n°31 "available".

The procedures and commands for MO-SMS control by USIM are defined in TS 31.111 [12]. It is mandatory for the ME to perform the procedures if it has indicated that it supports MO-SMS control by USIM in the TERMINAL PROFILE command.

5.4.6 Data Download via USSD and USSD application mode

Requirement: Service n°70 "available".

The procedures and commands for Data Download via USSD and USSD application mode are defined in TS 31.111 [12].

5.4.7 Additional TERMINAL PROFILE after UICC activation

Requirement: USIM Service n°72 "available".

The procedures and commands for Additional TERMINAL PROFILE after UICC activation are defined in TS 31.111 [12] and allow the ME to send multiple Terminal Profile downloads.

5.4.8 Terminal Applications

Requirement: Service n°77 "available"

The procedures and commands for "Terminal Applications" are defined in TS 31.111 [12]

5.4.9 Call control on EPS PDN connection by USIM

Requirement: USIM Service n°87 "available".

The procedures and commands for Call control on EPS PDN connection by USIM are defined in TS 31.111 [12].

5.4.10 Communication Control for IMS by USIM

Requirement: USIM Service n°93 "available".

The procedures and commands for Communication Control for IMS by USIM are defined in TS 31.111 [12]. It is mandatory for the ME to perform the procedures if it has indicated that it supports Communication Control for IMS by USIM in the TERMINAL PROFILE command.

5.4.11 USAT Facility Control

Requirement: The ME supports the USAT over AT feature specified in TS 31.111 [12].

Request: The ME performs the reading procedures of EF_UFC.

5.4.12 Extended Terminal Applications

Requirement: Service n°77 and n°94 "available"

The procedures and commands for "Extended Terminal Applications" are defined in TS 31.111 [12].

5.4.13 USAT application pairing procedure

The use of a USIM can be restricted to specific MEs using the USAT Application Pairing procedure and information stored in the USIM as specified in this specification and defined in 3GPP TS 33.187 [76].

To support the USAT Application Pairing procedure, the ME shall support USAT PROVIDE LOCAL INFORMATION command (IMEI or IMEISV), as specified in 3GPP TS 31.111 [12].

USAT Application Pairing is successful when the IMEI or IMEISV retrieved from the terminal belongs to a range of values the UICC is configured with in EF_IAL.

EF_IAL, EF_IPS, E_FIPD are defined in this document to support this procedure.

If the service n°102 is "available" in the USIM Service Table, the UICC shall start the UICC proactive session immediately after TERMINAL PROFILE and the first proactive command shall be PROVIDE LOCAL INFORMATION with IMEI or IMEISV. The ME shall respond with TERMINAL RESPONSE with IMEI or IMEISV before performing any AUTHENTICATE command.

The UICC shall respond to any AUTHENTICATE command with error status words SW1 SW2 = ’69 85′ if:

– IMEI or IMEISV provided by the ME is not in the corresponding allowed list configured in the USIM (EF_IAL)

– ME has not provided any IMEI

If the AUTHENTICATE command had been executed before the pairing procedure has been successfully performed (in the case of pre-Rel-12 MEs), the UICC may need to trigger a network attachment procedure by sending a proactive command REFRESH(3G SESSION RESET).

5.4.14 Call control on PDU Session by USIM

Requirement: USIM Service n°128 "available".

The procedures and commands for Call control on PDU Session by USIM are defined in TS 31.111 [12].

5.5 MexE related procedures

MexE is an optional feature. The higher level procedures, and contents and coding of the commands are given in TS 23.057 [30]. Procedures relating to the transmission of commands and responses across the USIM/ME interface are given in this clause. A USIM or ME supporting MexE shall conform to the requirements given in this clause.

5.5.1 MexE ST

Requirement: Service n°41 (MexE) "available".

Request: The ME performs the reading procedure with EF_MexE-ST

5.5.2 Operator root public key

Requirement: Service n°41 (MexE) "available" and MexE ST service n°1 (EF_ORPK) "available".

Request: The ME performs the reading procedure with EF_ORPK. The ME shall analyse the data of EF_ORPK (clause 4.4.1.4.2) to identify the files containing the certificate instances. If necessary, then the ME performs READ BINARY commands on these files to assemble the complete certificate instance data.

5.5.3 Administrator root public key

Requirement: Service n°41 (MexE) "available" and MexE ST service n°2 (EF_ARPK)"available".

Request: The ME performs the reading procedure with EF_ARPK.The ME shall analyse the data of EF_ARPK (clause 4.4.1.4.3) to identify the file containing the certificate instance. If necessary, then the ME performs READ BINARY commands on this file to assemble the complete certificate instance data.

5.5.4 Third Party root public key(s)

Requirement: Service n°41 (MexE) "available" and MexE ST service n°3 (EF_TPRPK)"available".

Request: The ME performs the reading procedure with EF_TPRPK.The ME shall analyse the data of EF_TPRPK (clause 4.4.1.4.4) to identify the files containing the certificate instances. If necessary, then the ME performs READ BINARY commands on these files to assemble the complete certificate instance data.

5.5.5 Trusted Key/Certificates Data Files

Requirement: Service n°41 (MexE) "available".

Request: The ME performs the reading procedure with EF_TKCDF.The ME shall analyse the data of EF_TKCDF and, if necessary, perform READ BINARY commands on these files

5.6 WLAN related procedures

5.6.1 WLAN Selection related Procedures

Requirement: service n°62 or n°63 or n°81 or n°82 or n°83 or n°84 or n°88 "available"

The ME shall read the User, Home and Operator controlled WSIDs, the I-WLAN Equivalent HPLMN Presentation Indication, I-WLAN HPLMN Priority Indication, the I-WLAN Last Registered PLMN and the HPLMN Direct Access Indicationfrom the corresponding list files (i.e. EF_UWSIDL, EF_HWSIDL, EF_OWSIDL, EF_WEHPLMNPI, EF_WLRPLMN, EF_WHPI and EF_HPLMDAI)to perform WLAN selection procedures as described in TS 24.234 [40].

The user may change the User controlled WSIDs.

5.6.2 WLAN PLMN Selection related procedures

Requirement: service n°60 or nº61 "available"

The ME shall read the User controlled PLMN selector and/or Operator controlled PLMN selector in EF_UPLMNWLAN and EF_OPLMNWLANrespectively for WLAN PLMN Selection procedures as described in TS 24.234 [40].

The user may change the User controlled PLMN selector for WLAN.

5.6.3 WLAN access authentication related procedures

Requirement: service n°59 "available"

When the ME tries a full authentication, it shall inspect if a valid Pseudonym is available in EF_Pseudo.and use it as the user name portion of the NAI for WLAN access authentication following the procedures described in TS 24.234 [40].

The ME shall manage pseudonyms as defined in TS 24.234 [40].

5.6.4 WLAN access re-authentication related procedures

Requirement: service n°66 "available"

When the ME tries a fast re-authentication, it shall inspect if a valid reauthentication identity is available in EF_WRI and use it as the user name portion of the NAI for WLAN access re-authentication following the procedures described in TS 24.234 [40].

The ME shall manage re-authentiction identities, Master Key and counter values as described in TS 24.234 [40].

5.7 Network Connectivity Parameters for UICC IP connections related procedures

The EF_NCP-IP access procedures are described in ETSI TS 102 483 [50].

Requirement: Service n°80 is "available"

Request: The terminal performs the read procedure with EF_NCP-IPbefore establishing a remote data link for UICC remote IP connectivity as described in ETSI TS 102 483 [50].

Refresh: The terminal performs the refresh procedure with EF_NCP-IP.

5.8 H(e)NB related procedures

5.8.1 CSG Access Control procedures

Requirement: Service n°86 is "available"

Request: The terminal performs the read procedure with EF_ACSGL.

Update: The terminal performs the updating procedure with EF_ACSGL

The ME shall read the allowed CSG Ids from EF_ACSGL in order to perform H(e)NB selection procedures. The lists in EF_ACSGL shall take precedence over the list stored in the ME non-volatile memory.

Requirement: Service n°90 is "available"

Request: The terminal performs the read procedure with with EF_OCSGL.

The ME shall read the Operator CSG Ids from EF_OCSGL in order to perform H(e)NB selection procedures. The list in EF_OCSGL shall take precedence over the list stored in the ME non-volatile memory.

Requirement: Service n°92 is "available"

In case of a manual CSG cell selection, the ME shall read EF_AD and CSG Lists Display Indicators from EF_OCSGLand display CSG Ids accordingly. The configuration in EF_OCSGLshall take precedence over the configuration stored in the ME non-volatile memory.

If service n°92 is not "available", in case of a manual CSG cell selection, all available CSGs may be displayed without any restriction.

5.8.2 CSG Type related procedures

Requirement: Service n°86 is "available"

Request: The terminal performs the read procedure with EF_ACSGLand EF_CSGT.

Update: The terminal performs the updating procedure with EF_ACSGL

The ME shall discover the association between the selected CSG ID and a CSG Type from EF_ACSGL. If this association exists, the provided CSG Type shall be displayed.

Requirement: Service n°90 is "available"

Request: The terminal performs the read procedure with EF_OCSGLand EF_OCSGT.

The ME shall discover the association between the selected CSG ID and either a CSG Type from EF_ACSGL or an Operator CSG Type from EF_OCSGL. The Operator CSG Type has precedence.

5.8.3 HNB name display related procedures

Requirement: Service n°86 is "available"

Request: The terminal performs the read procedure with EF_ACSGLand EF_HNBN.

Update: The terminal performs the updating procedure with EF_ACSGLand EF_HNBN.

The ME shall discover the association between the selected CSG ID and a HNB name from EF_ACSGL. If this association exists, the provided HNB name shall be displayed.

Requirement: Service n°90 is "available"

Request: The terminal performs the read procedure with EF_OCSGLand EF_OHNBN.

The ME shall discover the association between the selected CSG ID and either a HNB Name from EF_ACSGL or an Operator HNB from EF_OCSGL. The Operator HNB Name has precedence. If this association exists, the HNB Name shall be displayed.

Requirement: Service n°92 is "available"

In case of a manual CSG cell selection, the ME shall read EF_AD and the CSG Lists Display Indicators from EF_OCSGLand display HNB Name accordingly. The configuration in EF_OCSGLshall take precedence over the configuration stored in the ME non-volatile memory.

If service n°92 is not "available", in case of a manual CSG cell selection, all available CSGs may be displayed without any restriction.

5.9 ProSe related procedures

5.9.1 ProSe Direct Discovery Provisioning parameters

Requirement: service n°1 is "available" in the ProSe Service Table.

Request: The ME performs the reading procedure with EF_{PROSE_MON}. and EF_{PROSE_ANN}.

5.9.2 HPLMN ProSe Function address

Requirement: service n°2 is "available" in the ProSe Service Table.

Request: The ME performs the reading procedure with EF_PROSEFUNC.

5.9.3 ProSe direct communication related Procedures

Requirement: service n°3 is "available" in the ProSe Service Table and "Prose services for Public Safety" is enabled in EF_AD or the ME received service authorization from the ProSe Function.

Request: The ME performs the reading procedure with EF_{PROSE_RADIO_COM}.

5.9.4 ProSe direct discovery related Procedures

Requirement: service n°4 is "available" in the ProSe Service Table and "Prose services for Public Safety" is enabled in EF_AD or the ME received service authorization from the ProSe Function.

Request: The ME performs the reading procedure with EF_{PROSE_RADIO_MON}.

Requirement: service n°5 is "available" in the ProSe Service Table and "Prose services for Public Safety" is enabled in EF_AD or the ME received service authorization from the ProSe Function.

Request: The ME performs the reading procedure with EF_{PROSE_RADIO_ANN}.

5.9.5 ProSe direct communication related Procedures

Requirement: service n°6 is "available" in the ProSe Service Table and "Prose services for Public Safety" is enabled in EF_AD or the ME received service authorization from the ProSe Function.

Request: The ME performs the reading procedure with EF_{PROSE_POLICY}.

5.9.6 ProSe direct communication related Procedures

Requirement: service n°3 is "available" in the ProSe Service Table and "Prose services for Public Safety" is enabled in EF_AD or the ME received service authorization from the ProSe Function

Request: The ME performs the reading procedure with EF_{PROSE_PLMN}.

5.9.7 ProSe Group Counter related Procedures

Requirement: service n°7 is "available" in the ProSe Service Table.

Request: The ME performs the reading procedure with EF_{PROSE_GC}. The content from the USIM shall be combined with that one from the non-volatile memory on the ME, with USIM taking precedence in case the same group is available in both.

Update: The ME performs the updating procedure with EF_{PROSE_GC}. If the EF does not have free space, the ME shall use the non-volatile memory on the ME.

The ME is responsible to remove entries no longer used from the EF_{PROSE_GC} in order to guarantee that EF is not filled with unnecessary entries.

5.9.8 ProSe Usage Information Reporting Configuration related Procedures

Requirement: service n°8 is "available" in the ProSe Service Table.

Request: The ME performs the reading procedure with EF_{PROSE_UIRC}. The content from the USIM shall be used by the ME to construct the content of the usage information report according the procedures defined in TS 24.334[70], with the USIM configuration parameters taking precedence in case the usage information reporting configuration parameters have also been provisioned in the ME.

5.9.9 ProSe Group Member Discovery related Procedures

Requirement: service n°10 is "available" in the ProSe Service Table and "Prose services for Public Safety" is enabled in EF_AD or the ME received service authorization from the ProSe Function.

Request: The ME performs the reading procedure with EF_{PROSE_GM_DISCOVERY}.

5.9.10 ProSe Relay related Procedures

Requirement: service n°11 is "available" in the ProSe Service Table and "Prose services for Public Safety" is enabled in EF_AD or the ME received service authorization from the ProSe Function.

Request: The ME performs the reading procedure with EF_{PROSE_RELAY} and EF_{PROSE_RELAY_DISCOVERY}.

5.10 ePDG Selection related procedures

5.10.1 Home ePDG Identifier

Requirement: service n°106 and n°107 are "available" in the USIM Service Table.

Request: The ME performs the reading procedure with EF_ePDGId. The UE then shall use the Home ePDG identifier(s) present in the EF_ePDGIdtoperform the ePDG selection procedure as defined in 3GPP TS 24.302 [79].

If EF_ePDGId and EF_{ePDGSelection} are empty, the UE shall consider "ePDG configuration information is configured but empty", then the UE shall follow the procedure specified in the "Selection of the ePDG" UE procedure as defined in 3GPP TS 24.302 [79].

5.10.2 ePDG Selection Information

Requirement: service n°106 and n°107 are "available" in the USIM Service Table.

Request: The ME performs the reading procedure with EF_{ePDGSelection}. The UE then shall use the ePDG selection information present in the EF_{ePDGSelection}toperform the ePDG selection procedure as defined in 3GPP TS 24.302 [79].

5.10.3 ePDG configuration information configured but empty

Requirement: service n°106 is "available" and service n°107 is not "available" in the USIM Service Table.

Request: The UE shall consider "ePDG configuration information is configured but empty", then the UE shall follow the procedure specified in the "Selection of the ePDG" UE procedure as defined in 3GPP TS 24.302 [79].

5.11 ACDC related procedures

5.11.1 ACDC Configuration

Requirement: service n°108 is "available".

Request: The ME performs the reading procedure with EF_ACDC.

5.12 MCS related procedures

5.12.1 MCS configuration

Requirement: At least one of the services is "available" in the MCS Service Table.

Request: The ME performs the reading procedure with EF_{MCS _CONFIG}.

5.12.2 Void

5.12.3 Void

5.12.4 Void

5.13 ePDG Selection for Emergency Services related procedures

5.13.1 Emergency ePDG Identifier

Requirement: service n°110 and n°111 are "available" in the USIM Service Table.

Request: The ME performs the reading procedure with EF_ePDGIdEm. The UE then shall use the Emergency ePDG identifier(s) present in the EF_ePDGIdEmtoperform the ePDG selection procedure.

If EF_ePDGIdEm and EF_{ePDGSelectionEm} are empty, the UE shall consider that the ePDG configuration information for Emergency Services is configured but empty.

5.13.2 ePDG Selection Information for Emergency Services

Requirement: service n°110 and n°111 are "available" in the USIM Service Table.

Request: The ME performs the reading procedure with EF_{ePDGSelectionEm}. The UE then shall use the ePDG selection information for Emergency Services present in the EF_{ePDGSelectionEm}toperform the ePDG selection procedure.

If EF_ePDGIdEm and EF_{ePDGSelectionEm} are empty, the UE shall consider that the ePDG configuration information for Emergency Services is configured but empty.

5.13.3 ePDG configuration information for Emergency Services configured but empty

Requirement: service n°111 is "available" and service n°110 is not "available" in the USIM Service Table.

Request: The UE shall consider the ePDG configuration information is configured but empty.

5.13.4 From Preferred related procedures

Requirement: service n°114 is "available" in the USIM Service Table.

Request: The ME performs the reading procedure with EF_{FromPreferred}. The UE then shall use the From Preferred value in the EF_{FromPreferred}as described in 3GPP TS 24.607 [86] clause 4.5.2.12.

5.13.5 IMS Configuration Data related procedures

Requirement: service n°115 is "available" in the USIM Service Table.

Request: The ME may perform the reading procedure with EF_{IMSConfigData}. If the ME performs the reading procedure with EF_{IMSConfigData}, the UE shall use the IMS Configuration Data in the EF_{IMSConfigData}as described in 3GPP TS 24.229 [63] clause L.2.2.5.1D and 3GPP TS 24.229 [63] clause 6.1.1.

5.13.6 XCAP Configuration Data related procedures

Requirement: service n°120 is "available" in the USIM Service Table.

Request: The ME may perform the reading procedure with EF_{XCAPConfigData}. If the ME performs the reading procedure with EF_{XCAPConfigData}, the UE shall use the EF_{XCAPConfigData} as described in TS 24.623 [102] clause 5.2.1.3 and TS 24.623 [102] clause B.2

5.13.7 Multi-device and multi-identity related procedures

Requirement: service n°134 is "available" in the USIM Service Table.

Request: The ME performs the reading procedure with EF_{MuDMiDConfigData}. The UE shall use the EF_{MuDMiDConfigData} as described in TS 24.174 [45] clauses 4.5.3.1 and 4.5.3.6.

5.14 V2X related procedures

5.14.1 V2X configuration

Requirement: service n°1 is "available" in the V2X Service Table.

Request: The ME performs the reading procedure with EF_{V2X_CONFIG}.

5.14.2 V2X data policy over PC5

Requirement: service n°2 is "available" in the V2X Service Table.

Request: The ME performs the reading procedure with EF_{V2X_PC5}.

5.14.3 V2X data policy over Uu

Requirement: service n°3 is "available" in the V2X Service Table.

Request: The ME performs the reading procedure with EF_{V2X_Uu}.

5.15 UAC Access Identities related procedures

5.15.1 UAC Access Identities Configuration

Requirement: Service n°126 is "available".

Request: The ME performs the reading procedure with EF_{UAC_AIC}.

5.16 CAG selection related procedures

5.16.1 Pre-configured CAG information list reading procedure for ME

Requirement: Service n°137 is "available".

Request: The ME performs the reading procedure with EF_CAG as specified in 3GPP TS 21.322 [31] clause 3.8.

5.17 5G ProSe related procedures

5.17.1 5G ProSe configuration data for direct discovery

Requirement: service n°139 is "available" in the USIM Service Table and service n°1 is "available" in the 5G ProSe Service Table.

Request: The ME performs the reading procedure with EF_{5G_PROSE_DD}.

5.17.2 5G ProSe configuration data for direct communication

Requirement: service n°139 is "available" in the USIM Service Table and service n°2 is "available" in the 5G ProSe Service Table.

Request: The ME performs the reading procedure with EF_{5G_PROSE_DC}.

5.17.3 5G ProSe configuration data for UE-to-network relay UE

Requirement: service n°139 is "available" in the USIM Service Table and service n°3 is "available" in the 5G ProSe Service Table.

Request: The ME performs the reading procedure with EF_{5G_PROSE_U2NRU}.

5.17.4 5G ProSe configuration data for remote UE

Requirement: service n°139 is "available" in the USIM Service Table and service n°4 is "available" in the 5G ProSe Service Table.

Request: The ME performs the reading procedure with EF_{5G_PROSE_RU}.

5.17.5 5G ProSe configuration data for usage information reporting

Requirement: service n°139 is "available" in the USIM Service Table and service n°5 is "available" in the 5G ProSe Service Table.

Request: The ME performs the reading procedure with EF_{5G_PROSE_UIR}.

5.18 Disaster roaming related procedures

5.18.1 Disaster roaming information reading procedure for ME

Requirement: Service n°140 is "available".

Request: If the ME supports MINT (see 3GPP TS 23,122 [31]), the ME performs the reading procedure with EF_DRI.

5.19 SNPN (Standalone NPN) related procedures

5.19.1 PWS configuration in SNPN.

Requirement: Service n°143 is "available".

Request: The ME performs the reading procedure with EF_{PWS_SNPN.}

5.19.2 K_AUSF derivation configuration

Requirement: Service n° 145 is "available".

Request: The ME performs the reading procedure with EF_{KAUSF_DERIVATION.}

5.20 NG-RAN satellite access related procedures

5.20.1 Multiplier coefficient for Higher Priority PLMN search via NG-RAN satellite access for ME

Requirement: Service n°144 is "available".

Request: If the ME supports the NG-RAN via satellite access (see 3GPP TS 23,122 [31]), the ME performs the reading procedure with EF_MCHPPLMN.