tech-invite   World Map     

IETF     RFCs     Groups     SIP     ABNFs    |    3GPP     Specs     Glossaries     Architecture     IMS     UICC    |    search     info

3GPP Glossaries

|   Features_Services   |   Network_Entities   |   Reference_Points   |   SIM_UICC_Dir_Files   |   Identifiers   |

 

SIM/UICC directories/files

X

Y

Z

 

 

 

Here          Top

|   EF PBC   |   EF PBR   |   EF P-CSCF   |   EF Phase   |   DF PHONEBOOK   |   EF PL   |   EF PLMNSEL   |   EF PLMNwAcT   |   EF PNN   |   EF PNNI   |   DF ProSe   |   EF PROSE_ANN   |   EF PROSE_FUNC   |   EF PROSE_GC   |   EF PROSE_GM_DISCOVERY   |   EF PROSE_MON   |   EF PROSE_PLMN   |   EF PROSE_POLICY   |   EF PROSE_RADIO_ANN   |   EF PROSE_RADIO_COM   |   EF PROSE_RADIO_MON   |   EF PROSE_RELAY   |   EF PROSE_RELAY_DISCOVERY   |   EF PROSE_UIRC   |   EF PSC   |   EF Pseudo   |   EF PSISMSC   |   EF PSLOCI   |   EF PST   |   EF PUCT   |   EF PUID   |   EF PURI   |   EF PWS   |

 


This EF contains control information related to each entry in the phone book. This EF contains as many records as the EF ADN associated with it (shall be record to record). Each record in EF PBC points to a record in its EF ADN. This file indicates the control information and the hidden information of each phone book entry.

The content of EF PBC is linked to the associated EF ADN record by means of the ADN record number/ID (there is a one to one mapping of record number/identifiers between EF PBC and EF ADN).

See it under DF PHONEBOOK

Source:  TS 31.102 – Clause 4.4.2.5

Up       Top


This file describes the structure of the phonebook. All EFs representing the phonebook are specified here (with the exception of EF PSC, EF PUID and EF CC), together with their file identifiers (FID) and their short file identifiers (SFI), if applicable.

Certain kinds of EFs can occur more than once in the phonebook, e.g. there may be two entities of Abbreviated Dialling Numbers, EF ADN and EF ADN1. For these kinds of EFs, no fixed FID values are specified. Instead, the value '4FXX' indicates that the value is to be assigned by the card issuer. These assigned values are then indicated in the associated TLV object in EF PBR.

See it under DF PHONEBOOK

Source:  TS 31.102 – Clause 4.4.2.1

Up       Top


This EF contains one or more Proxy Call Session Control Function addresses. The first record in the EF shall be considered to be of the highest priority.The last record in the EF shall be considered to be the lowest priority.

See it under ADF ISIM

Source:  TS 31.103 – Clause 4.2.8

Up       Top


This EF contains one or more Proxy Call Session Control Function addresses. The first record in the EF shall be considered to be of the highest priority.The last record in the EF shall be considered to be the lowest priority.
  • '00': phase 1
  • '02': phase 2
  • '03': phase 2 and PROFILE DOWNLOAD required (see TS 51.014).

See it under DF GSM

Source:  TS 51.011 – Clause 10.3.19

Up       Top


Click   here   to see the file structure under DF PHONEBOOK.

The EFs in the DF PHONEBOOK level contain phone book related features as required in TS 21.111.

The UICC may contain a global phonebook, or application specific phonebooks, or both in parallel. When both phonebook types co-exist, they are independent and no data is shared. In this case, it shall be possible for the user to select which phonebook the user would like to access. To achieve this, the terminal shall support the global and the application specific phonebooks.

It is recommended that the terminal searches for the global phonebook located under DF TELECOM as its presence is not indicated anywhere in the USIM application.

The global phonebook is located in DF PHONEBOOK under DF TELECOM. Each specific USIM application phonebook is located in DF PHONEBOOK of its respective Application ADF USIM. The organisation of files in DF PHONEBOOK under ADF USIM and under DF TELECOM follows the same rules. Yet DF PHONEBOOK under ADF USIM may contain a different set of files than DF PHONEBOOK under DF TELECOM. All phonebook related EFs are located under their respective DF PHONEBOOK. USIM specific phonebooks are dedicated to application specific entries. Each application specific phonebook is protected by the application PIN.

See it under DF TELECOM

Source:  TS 31.102 – Clause 4.6.2

Source:  TS 31.102 – Clause 4.4.2

Up       Top


This EF contains the codes for up to n languages. This information, determined by the user/operator, defines the preferred languages of the user, for the UICC, in order of priority.

The presence of this file is optional for a SIM, and it is called EF ELP from GSM Rel-97 up to GSM Rel-99.

See it under MF

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

Up       Top


This EF contains the coding for n PLMNs, where n is at least eight. This information determined by the user/operator defines the preferred PLMNs of the user in priority order.

See it under DF GSM

Source:  TS 51.011 – Clause 10.3.4

Up       Top


This EF contains the coding for n PLMNs, where n is at least eight. This information is determined by the user and defines the preferred PLMNs of the user in priority order. The first record indicates the highest priority and the nth record indicates the lowest. The EF also contains the Access Technologies for each PLMN in this list (see TS 23.122).

See it under DF GSM

Source:  TS 51.011 – Clause 10.3.35

Source:  TS 31.102 – Clause 4.2.5

Up       Top


This EF contains the full and short form versions of the network name for the registered PLMN. The ME shall use these versions in place of its own versions of the network name for the PLMN (stored in the ME's memory list), and also in place of the versions of the network name received when registered to the PLMN, as defined by TS 24.008.

This file may also contain PLMN additional information to be displayed to the user during the Manual Network Selection procedures as defined in TS 23.122.

If the EF OPL is not present, then the first record in this EF is used for the default network name when registered in the HPLMN (if the EHPLMN list is not present or is empty) or an EHPLMN (if the EHPLMN list is present).

See it under DF GSM

Source:  TS 51.011 – Clause 10.3.41

Source:  TS 31.102 – Clause 4.2.58

Up       Top


This EF contains one or several links to the PLMN network name icon. When more than one link is available in a record, it is up to the ME to choose the link type to be used (e.g. the link type that is supported by the ME).

See it under ADF USIM

Source:  TS 31.102 – Clause 4.2.89

Up       Top


Click   here   to see the file structure under DF ProSe.

See it under ADF USIM

Source:  TS 31.102 – Clause 4.4.8

Up       Top


This EF contains the authorized PLMNs for ProSe direct discovery for public safety as described in TS 24.334. This file shall be used only if the ME is authorized as per content of EF AD or received service authorization from the ProSe Function.

See it under DF ProSe

Source:  TS 31.102 – Clause 4.4.8.3

Up       Top


This EF contains the IP address of the HPLMN ProSe Function.

See it under DF ProSe

Source:  TS 31.102 – Clause 4.4.8.4

Up       Top


This EF contains the PTK ID and Counter associated with the PGK currently in use for a ProSe Group.

See it under DF ProSe

Source:  TS 31.102 – Clause 4.4.8.10

Up       Top


If service no. 10 is "available" in the ProSe Service Table, this file shall be present. This EF contains the ProSe discovery parameters for public safety, as described in TS 24.334. This file shall be used only if the ME is authorized as per content of EF AD or received service authorization from the ProSe Function.

See it under DF ProSe

Source:  TS 31.102 – Clause 4.4.8.12a

Up       Top


This EF contains the authorized PLMNs for ProSe direct discovery for public safety as described in TS 24.334. This file shall be used only if the ME is authorized as per content of EF AD or received service authorization from the ProSe Function.

See it under DF ProSe

Source:  TS 31.102 – Clause 4.4.8.2

Up       Top


This EF contains the authorized PLMNs for ProSe direct communication for public safety, as described in TS 24.334. This file shall be used only if the ME is authorized as per content of EF AD or received service authorization from the ProSe Function.

See it under DF ProSe

Source:  TS 31.102 – Clause 4.4.8.9

Up       Top


This EF contains the policy parameters to be used for ProSe direct communication for public safety when the UE is not served by E-UTRAN, as described in TS 24.334. This file shall be used only if the ME is authorized as per content of EF AD or received service authorization from the ProSe Function.

See it under DF ProSe

Source:  TS 31.102 – Clause 4.4.8.8

Up       Top


This EF contains the radio parameters to be used for ProSe direct communication for public safety when the UE is not served by E-UTRAN, as described in TS 24.334. This file shall be used only if the ME is authorized as per content of EF AD or received service authorization from the ProSe Function.

See it under DF ProSe

Source:  TS 31.102 – Clause 4.4.8.7

Up       Top


This EF contains the radio parameters to be used for ProSe direct communication for public safety when the UE is not served by E-UTRAN, as described in TS 24.334. This file shall be used only if the ME is authorized as per content of EF AD or received service authorization from the ProSe Function.

See it under DF ProSe

Source:  TS 31.102 – Clause 4.4.8.5

Up       Top


This EF contains the radio parameters to be used for ProSe direct communication for public safety when the UE is not served by E-UTRAN, as described in TS 24.334. This file shall be used only if the ME is authorized as per content of EF AD or received service authorization from the ProSe Function.

See it under DF ProSe

Source:  TS 31.102 – Clause 4.4.8.6

Up       Top


If service no. 11 is "available" in the ProSe Service Table, this file shall be present. This EF contains the authorized PLMNs for ProSe UE-to-network relay for public safety, as described in TS 24.334. This file shall be used only if the ME is authorized as per content of EF AD or received service authorization from the ProSe Function.

See it under DF ProSe

Source:  TS 31.102 – Clause 4.4.8.13

Up       Top


If service no. 11 is "available" in the ProSe Service Table, this file shall be present. This EF contains the ProSe direct discovery parameters when it is used for ProSe UE-to-network relay discovery for public safety, as described in TS 24.334. This file shall be used only if the ME is authorized as per content of EF AD or received service authorization from the ProSe Function.

See it under DF ProSe

Source:  TS 31.102 – Clause 4.4.8.14

Up       Top


If service no. 8 is "available" in the ProSe Service Table, this file shall be present. This EF contains the description of the configuration to be used by the UE for reporting the usage information for direct communication for public safety, as described in TS 24.334 and TS 32.277. This file shall be used only if the UE is authorized for direct communication as per content of EFAD or received service authorization from the ProSe Function.

See it under DF ProSe

Source:  TS 31.102 – Clause 4.4.8.12

Up       Top


The PSC is used by the ME to construct the phone book identifier (PBID) and to determine whether the accessed phone book is the same as the previously accessed phone book or if it is a new unknown phone book (might be the case that there is one phonebook under DF telecom and one phone book residing in a USIM-application). If the PSC is unknown, a full synchronisation of the phone book will follow.

The PSC is also used to regenerate the UIDs and reset the CC to prevent them from running out of range. When the UIDs or the CC has reached its maximum value, a new PSC is generated. This leads to a scenario where neither the CC nor the UIDs will run out of range.

The PSC shall be regenerated by the terminal if one of the following situation applies:
  • the values of the UIDs have run out of range;
  • the whole phone book has been reset/deleted;
  • the value of the CC has run out of range.

See it under DF PHONEBOOK

Source:  TS 31.102 – Clause 4.4.2.12.2

Up       Top


This EF contains a temporary user identifier (pseudonym) for subscriber identification. Pseudonyms may be provided as part of a previous authentication sequence. Pseudonyms are used as defined in TS 24.234

See it under DF WLAN

Source:  TS 31.102 – Clause 4.4.5.1

Up       Top


This EF contains the Public Service Identity of the SM-SC (either a SIP URI or tel URI) that the ME shall use to submit SMS over IP as defined in TS 24.341.

See it under DF TELECOM

Source:  TS 31.102 – Clause 4.5.9

Up       Top


This EF contains the following Location Information:
  • P-TMSI;
  • P-TMSI signature value;
  • Routing Area Information (RAI);
  • Routing Area update status.

See it under ADF USIM

Source:  TS 31.102 – Clause 4.2.23

Up       Top


If service no. 101 is "available" in the USIM Service Table, this file shall be present. This EF indicates which ProSe services are available. If a service is not indicated as available in the ProSe Service Table, the ME shall not select this service.

See it under DF ProSe

Source:  TS 31.102 – Clause 4.4.8.11

Up       Top


This EF contains the PUCT. The PUCT is Advice of Charge related information which may be used by the ME in conjunction with EF ACM to compute the cost of calls in the currency chosen by the subscriber, as specified in TS 22.024.

See it under DF GSM

Source:  TS 51.011 – Clause 10.3.12

Source:  TS 31.102 – Clause 4.2.13

Up       Top


The PUID is used to store the previously used unique identifier (UID). The purpose of this file is to allow the terminal to quickly generate a new UID, which shall then be stored in the EF UID.

See it under DF PHONEBOOK

Source:  TS 31.102 – Clause 4.4.2.12.4

Up       Top


This EF contains the URI address that may be linked to a phonebook entry. Several URI addresses can be attached to one EF-ADN record, using one or several EF-PURI. The number of URI addresses may be equal to or less than the amount of records in EF-ADN. Each record contains a URI address. The first part indicates the URI address, and the second part indicates the reference to the associated record in the EF-ADN file. This record cannot be shared between several phonebook entries.

See it under DF PHONEBOOK

Source:  TS 31.102 – Clause 4.4.2.15

Up       Top


This EF contains the configuration parameters for PWS, as defined in TS 22.268.

See it under ADF USIM

Source:  TS 31.102 – Clause 4.2.96

Up       Top