tech-invite   World Map     

IETF     RFCs     Groups     SIP     ABNFs    |    3GPP     Specs     Gloss.     Arch.     IMS     UICC    |    Misc.    |    search     info

3GPP Glossaries

 

 

SIM/UICC directories/files

X

Y

Z

 

 

 

Here          Top

EF IAP     # EF ICCID     # EF ICE_DN     # EF ICE_FF     # EF ICE_graphics     # EF ICI     # DF ICO     # EF ICON     # EF ICT     # EF IIDF     # EF IMG     # EF IMPI     # EF IMPU     # EF IMSI     # EF InvScan     # EF IPD     # EF IPS     # DF IRIDIUM     # DF ISIM     # EF IST     # EF IWL    

 

EF IAP  —  Index  Administration  Phone book


This file is present if Tag 'A9' is indicated in the reference file EF PBR.

The EF contains pointers to the different records in the files that are part of the phone book. The index administration file record number/ID is mapped one to one with the corresponding EF ADN (shall be record to record). The index administration file contains the same amount of records as EF ADN. The order of the pointers in an EF IAP shall be the same as the order of file IDs that appear in the TLV object indicated by Tag 'A9' in the reference file record. The amount of bytes in a record is equal to the number of files indicated in the EF PBR following tag 'A9'.

See it  under DF PHONEBOOK

Source:  TS 31.102 – Clause 4.4.2.2

Up       Top

EF ICCID  —  Integrated  Circuit  Card  IDentification


This EF provides the ICCID, a unique identification number for the UICC, according to ITU-T Recommendation E.118.

See it  under MF

Source:  ETSI (SCP) TS 102 221 – Clause 13.2

Up       Top

EF ICE_DN  —  In  Case of  Emergency    Dialling  Number


This EF contains one or more records containing number formatted ICE information, according to TS 22.101.

This file shall be deactivated if the user does not wish the ICE information contained in this file to be available and activated if the user wishes the ICE information in this file to be available.

See it  under DF TELECOM

Source:  TS 31.102 – Clause 4.5.6

Up       Top

EF ICE_FF  —  In  Case of  Emergency    Free  Format


This EF contains one or more records containing free formatted ICE information, according to TS 22.101.

This file shall be deactivated if the user does not wish the ICE information contained in this file to be available and activated if the user wishes the ICE information in this file to be available.

See it  under DF TELECOM

Source:  TS 31.102 – Clause 4.5.7

Up       Top

EF ICE_graphics  —  In  Case of  Emergency    Graphics


This EF contains ICE graphical information, according to TS 22.101.

This file shall be deactivated if the user does not wish the ICE information contained in this file to be available and activated if the user wishes the ICE information in this file to be available.

For this EF the Total File Size data object shall be present within the FCP template in order for the ME to fit the picture to the available memory.

See it  under DF GRAPHICS

Source:  TS 31.102 – Clause 4.6.1.3

Up       Top

EF ICI  —  Incoming  Call  Information


This EF is located within the USIM application. The incoming call information can be linked to the phone book stored under DF TELECOM or to the local phone book within the USIM. The EF ICI contains the information related to incoming calls.

The time of the call and duration of the call are stored in this EF. This EF can also contain associated alpha identifier that may be supplied with the incoming call. In addition it contains identifiers of associated network/bearer capabilities and identifiers of extension records at the USIM ADF level. The structure of this EF is cyclic, so the contents shall be updated only after a call is disconnected.

If CLI is supported and the incoming phone number matches a number stored in the phone book the incoming call information is linked to the corresponding information in the phone book. If the incoming call matches an entry but is indicated as hidden in the phone book the link is established but the information is not displayed by the ME if the code for the secret entry has not been verified. The ME shall not ask for the secret code to be entered at this point.

Optionally the ME may store the link to phone book entry in the file, so that it does not need to look again for a match in the phone book when it reuses the entry. But the ME will have to check that the incoming call number still exits in the linked phone book entry, as the link might be broken (entry modified). When not used by the ME or no link to the phone book has been found, this field shall be set to 'FFFFFF'.

The first byte of this link is used to identify clearly the phone book location either global (i.e. under DF TELECOM) or local (i.e. USIM specific). To allow the reuse of the referring mechanism in further implementation of the phonebook under discussion, this byte can be used to indicate those.

See it  under ADF USIM

Source:  TS 31.102 – Clause 4.2.33

Up       Top


Not defined in the 3GPP Specifications

See it  under DF GSM

Source:  TS 51.011 – Clause 10.2

Up       Top

EF ICON  —  LAUNCH  PAD


This EF contains the data for one icon.

See it  under DF CD

Source:  ETSI (SCP) TS 102 221 – Clause 13.5.2

Up       Top

EF ICT  —  Incoming  Call  Timer


This EF contains the accumulated incoming call timer duration value for the current call and previous calls. The EF is USIM specific and resides within the USIM application.

See it  under ADF USIM

Source:  TS 31.102 – Clause 4.2.35

Up       Top

EF IIDF  —  Image  Instance  Data  Files


There may be several image instance data files. Each Image Instance Data File contains data for one or more image instances.

See it  under DF GRAPHICS

Source:  TS 31.102 – Clause 4.6.1.2

Up       Top

EF IMG  —  IMaGe


Each record of this EF identifies instances of one particular graphical image, which graphical image is identified by this EF's record number.

Image instances may differ as to their size, having different resolutions, and the way they are coded, using one of several image coding schemes.

As an example, image k may represent a company logo, of which there are i instances in the UICC, of various resolutions and perhaps encoded in several image coding schemes. Then, the i instances of the company's logo are described in record k of this EF.

See it  under DF GRAPHICS

Source:  TS 31.102 – Clause 4.6.1.1

Up       Top

EF IMPI  —  IMS  Private


This EF contains the private user identity of the user, under the form of a NAI (Network Access Identifier) as defined in RFC 7542.

See it  under ADF ISIM

Source:  TS 31.103 – Clause 4.2.2

Up       Top

EF IMPU  —  IMS  PUblic


This EF contains one or more records, with each record able to hold a public SIP Identity (SIP URI) of the user. The first (or only) record in the EF shall be used when performing emergency registration.

See it  under ADF ISIM

Source:  TS 31.103 – Clause 4.2.4

Up       Top

EF IMSI  —  International  Mobile  Subscriber  Identity


This EF contains the IMSI.

See it  under DF GSM

Source:  TS 51.011 – Clause 10.3.2

See it  under ADF USIM

Source:  TS 31.102 – Clause 4.2.2

See it  under ADF HPSIM

Source:  TS 31.104 – Clause 4.2.2

Up       Top

EF InvScan  —  Investigation  Scan


This EF contains two flags used to control the investigation scan for higher prioritized PLMNs not offering voice services.

See it  under DF GSM

Source:  TS 51.011 – Clause 10.3.39

See it  under DF GSM-ACCESS

Source:  TS 31.102 – Clause 4.4.3.5

Up       Top

EF IPD  —  IMEI(SV) of  Pairing  Device


This EF contains the IMEI(SV) as defined in TS 23.003 that was used in the USAT Application Pairing procedure.

This file shall be present if USAT Application Pairing is supported as defined in this specification.

See it  under ADF USIM

Source:  TS 31.102 – Clause 4.2.102

Up       Top

EF IPS  —  IMEI(SV)  Pairing  Status


This EF stores the status of USAT Application Pairing checking.

This file shall be present if USAT Application Pairing is supported as defined in this specification.

The status flag of pairing check (with value "OK" or "KO") stored in the file EFIPS can be read by any terminal hosting the UICC. The information stored in the file EFIPS provides a mechanism to detect changes of association between a USIM and a MTC ME. The information stored in the file EFIPS can be read locally by e.g. the maintenance person.

See it  under ADF USIM

Source:  TS 31.102 – Clause 4.2.101

Up       Top


Not defined in the 3GPP Specifications

See it  under DF GSM

Source:  TS 51.011 – Clause 10.2

Up       Top

ADF ISIM  —  IMS  Subscriber  Identity  Module


Click   here   to see the file structure under ADF ISIM.

See it  under MF

Source:  TS 31.103

Up       Top

EF IST  —  ISIM  Service  Table


This EF indicates which optional services are available. If a service is not indicated as available in the ISIM, the ME shall not select this service. The presence of this file is mandatory if optional services are provided in the ISIM.
1   P-CSCF address
2   Generic Bootstrapping Architecture (GBA)
3   HTTP Digest
4   GBA-based Local Key Establishment Mechanism
5   Support of P-CSCF discovery for IMS Local Break Out
6   Short Message Storage (SMS)
7   Short Message Status Reports (SMSR)
8   Support for SM-over-IP including data download via SMS-PP as defined in TS 31.111
9   Communication Control for IMS by ISIM
10   Support of UICC access to IMS
11   URI support by UICC

See it  under ADF ISIM

Source:  TS 31.103 – Clause 4.2.7

Up       Top

EF IWL  —  IMEI(SV)  White  Lists


This EF stores ranges of values of IMEI(SV) to which the USIM is authorized to be paired as defined in TS 31.102. This file shall be present if USAT Application Pairing is supported as defined in this specification. This file shall contain at least one IMEI(SV) range of values to which the USIM is authorized to be paired.

See it  under ADF USIM

Source:  TS 31.102 – Clause 4.2.100

Up       Top