Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 31.102  Word version:  17.1.0

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

 

4  Contents of the Files

This clause specifies the EFs for the 3GPP session defining access conditions, data items and coding. A data item is a part of an EF which represents a complete logical entity, e.g. the alpha tag in an EFADN record.
A file is associated with attributes that depending of the file type indicates how data is to be accessed e.g. file size, record length etc. Although in the present document some files and data items stored in a file are indicated as having a fixed length; when reading such structures the terminal shall derive the length of the data item from the attributes provided in the file information i.e. not use the fixed value specified for the file in the present document. Although the terminal is able to read the entire structure it should only use those elements in the data item which is recognised by the terminal.
For any EF, when the SFI is not indicated in the description of the file it is not allowed to assign an SFI. If in the description of the file an SFI value is indicated the file shall support SFI. The SFI value shall be assigned by the card issuer. It is mandatory for EFs stating an SFI value ('YY') in the description of their structure to provide an SFI. For files where in the file description the SFI is indicated as 'Optional' the file may support an SFI.
For an overview containing all files see Figure 4.1 and Figure 4.2.
Up

4.1  Contents of the EFs at the MF levelWord‑p. 23
The EFs at the Master File (MF) level are specified in TS 31.101.
The information in EFPL may be used by the ME for MMI purposes.
This information may also be used for the screening of Cell Broadcast messages in a preferred language, as follows.
When the CB Message Identifier capability is available, the ME selects only those CB messages the language of which corresponds to an entry in this EF or in EFLI, whichever of these EFs is used (see clause 5.1.1). The CB message language is defined by the Data Coding Scheme (see TS 23.038) received with the CB message. The ME shall be responsible for translating the language coding indicated in the Data Coding Scheme for the Cell Broadcast Service (as defined in TS 23.038) to the language coding as defined in ISO 639 [19] if it is necessary to check the language coding in EFPL.
Up

4.2  Contents of files at the USIM ADF (Application DF) level

The EFs in the USIM ADF contain service and network related information.
The File IDs '6F1X' (for EFs), '5F1X' and '5F2X' (for DFs) with X ranging from '0' to 'F' are reserved under the USIM ADF for administrative use by the card issuer.
UICC File Structure: EFs under USIM (LI, IMSI, Keys, KeysPS, PLMNwAct, HPPLMN, ACMmax, UST)

4.2.1  EFLI (Language Indication)

This EF contains the codes for one or more languages. This information, determined by the user/operator, defines the preferred languages of the user in order of priority. This information may be used by the ME for MMI purposes. This information may also be used for the screening of Cell Broadcast messages in a preferred language, as follows.
When the CB Message Identifier capability is available, the ME selects only those CB messages the language of which corresponds to an entry in this EF or in EFPL, whichever of these EFs is used (see clause 5.1.1). The CB message language is defined by the Data Coding Scheme (DCS: see TS 23.038) received with the CB message. The ME shall be responsible for translating the language coding indicated in the Data Coding Scheme for the Cell Broadcast Service (as defined in TS 23.038) to the language coding as defined in ISO 639 [19] if it is necessary to check the language coding in EF PL.
Identifier: '6F 05'Structure: transparentOptional
SFI: '02'
File size: 2n bytes, (n ≥ 1)Update activity: low
Access Conditions:
READALW
UPDATEPIN
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to 21st language code (highest priority)M2 bytes
3 to 42nd language codeO2 bytes
 
2n-1 to 2nNth language code (lowest priority)O2 bytes
Coding:
each language code is a pair of alpha-numeric characters, defined in ISO 639 [19]. Each alpha-numeric character shall be coded on one byte using the SMS default 7-bit coded alphabet as defined in TS 23.038 with bit 8 set to 0.
Unused language entries shall be set to 'FF FF'.
Up

4.2.2  EFIMSI (IMSI)Word‑p. 24
If service No. 130 is "available", this file shall not be available.
This EF contains the International Mobile Subscriber Identity (IMSI).
Identifier: '6F 07'Structure: transparentOptional
SFI: '07'
File size: 9 bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1Length of IMSIM1 byte
2 to 9IMSIM8 bytes
Length of IMSI
Contents:
  • the length indicator refers to the number of significant bytes, not including this length byte, required for the IMSI.
Coding:
IMSI
Contents:
  • International Mobile Subscriber Identity.
Coding:
  • this information element is of variable length. If a network operator chooses an IMSI of less than 15 digits, unused nibbles shall be set to 'F'.
     
    Byte 2:
    b8 b7 b6 b5 b4 b3 b2 b1
    MSB of Digit 1 LSB of Digit 1 Parity 0 0 1
    For the parity bit, see TS 24.008.
     
    Byte 3:
    b8 b7 b6 b5 b4 b3 b2 b1
    MSB of Digit 3 LSB of Digit 3 MSB of Digit 2 LSB of Digit 2
     
    etc.
Up

4.2.3  EFKeys (Ciphering and Integrity Keys)Word‑p. 25
This EF contains the ciphering key CK, the integrity key IK and the key set identifier KSI.
Identifier: '6F08'Structure: transparentMandatory
SFI: '08'
File size: 33 bytesUpdate activity: high
Access Conditions:
READPIN
UPDATEPIN
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1Key set identifier KSIM1 byte
2 to 17Ciphering key CKM16 bytes
18 to 33Integrity key IKM16 bytes
Key Set Identifier KSI
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
bits b4 to b8 are coded 0 KSI
Ciphering key CK
Coding:
  • the least significant bit of CK is the least significant bit of the 17th byte. The most significant bit of CK is the most significant bit of the 2nd byte.
Integrity key IK
Coding:
  • the least significant bit of IK is the least significant bit of the 33rd byte. The most significant bit of IK is the most significant bit of the 18th byte.
Up

4.2.4  EFKeysPS (Ciphering and Integrity Keys for Packet Switched domain)Word‑p. 26
This EF contains the ciphering key CKPS, the integrity key IKPS and the key set identifier KSIPS for the packet switched (PS) domain.
Identifier: '6F09'Structure: transparentMandatory
SFI: '09'
File size: 33 bytesUpdate activity: high
Access Conditions:
READPIN
UPDATEPIN
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1Key set identifier KSIPSM1 byte
2 to 17Ciphering key CKPSM16 bytes
18 to 33Integrity key IKPSM16 bytes
Key Set Identifier KSIPS
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
bits b4 to b8 are coded 0 KSIPS
Ciphering key CKPS
Coding:
  • the least significant bit of CKPS is the least significant bit of the 17th byte. The most significant bit of CKPS is the most significant bit of the 2nd byte.
Integrity key IKPS
Coding:
  • the least significant bit of IKPS is the least significant bit of the 33rd byte. The most significant bit of IKPS is the most significant bit of the 18th byte.
Up

4.2.5  EFPLMNwAcT (User controlled PLMN selector with Access Technology)

If service No. 20 is "available", this file shall be present.
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)
Identifier: '6F60'Structure: transparentOptional
SFI: '0A'
File size: 5n (where n ≥8 bytes)Update activity: low
Access Conditions:
READPIN
UPDATEPIN
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to 31st PLMN (highest priority)M3 bytes
4 to 51st PLMN Access Technology IdentifierM2 bytes
6 to 82nd PLMNM3 bytes
9 to 102nd PLMN Access Technology IdentifierM2 bytes
::
36 to 388th PLMNM3 bytes
39 to 408th PLMN Access Technology IdentifierM2 bytes
41 to 439th PLMNO3 bytes
44 to 459th PLMN Access Technology IdentifierO2 bytes
::
(5n-4) to (5n-2)Nth PLMN (lowest priority)O3 bytes
(5n-1) to 5nNth PLMN Access Technology IdentifierO2 bytes
PLMN
Contents:
  • Mobile Country Code (MCC) followed by the Mobile Network Code (MNC).
Coding:
Access Technology Identifier:
Coding:
  • 2 bytes are used to select the access technology where the meaning of each bit is as follows:
    • bit = 1: access technology selected;
    • bit = 0: access technology not selected.
     
    Byte 5n-1:
    b8 b7 b6 b5 b4 b3 b2 b1
    UTRAN E-UTRAN (see table below) E-UTRAN in WB-S1 mode (see table below) E-UTRAN in NB-S1 mode (see table below) NG-RAN satellite NG-RAN RFU RFU
     
    Coding of the E-UTRAN
    b7 b6 b5 Description
    0xxE-UTRAN not selected
    100E-UTRAN in WB-S1 mode and NB-S1 mode
    101E-UTRAN in NB-S1 mode only
    110E-UTRAN in WB-S1 mode only
    111E-UTRAN in WB-S1 mode and NB-S1 mode
     
    Byte 5n:
    b8 b7 b6 b5 b4 b3 b2 b1
    GSM (see table below) GSM COMPACT cdma2000 HRPD cdma2000 1xRTT EC-GSM-IoT (see table below) GSM (see table below) RFU RFU
     
    Coding of the GSM
    b8 b4 b3
    0xxGSM and EC-GSM-IoT not selected
    100GSM and EC-GSM-IoT
    101GSM without EC-GSM-IoT
    110EC-GSM-IoT only
    111GSM and EC-GSM-IoT
Up

4.2.6  EFHPPLMN (Higher Priority PLMN search period)Word‑p. 28
This EF contains the interval of time between searches for a higher priority PLMN (see TS 23.122).
Identifier: '6F31'Structure: transparentMandatory
SFI: '12'
File size: 1 byteUpdate activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1Time intervalM1 byte
Time interval
Contents:
the time interval between two searches.
Coding:
For UEs not using any of the following at the time of starting the timer: NB-IoT, GERAN EC-GSM-IoT and Category M1 of E-UTRAN enhanced-MTC as specified in TS 36.306, the time interval is coded in integer multiples of n minutes. The range is from n minutes to a maximum value. The encoding is:
  • '00': No higher priority PLMN search attempts;
  • '01': n minutes;
  • '02': 2n minutes;
  • 'YZ': (16Y+Z)n minutes (maximum value).
For UEs using any of the following at the time of starting the timer: NB-IoT, GERAN EC-GSM-IoT and Category M1 of E-UTRAN enhanced-MTC as specified in TS 36.306, the time interval is coded as follows. The range is from n hours to a maximum value. The encoding is:
  • '00': No higher priority PLMN search attempts;
  • '01': n hours (2 hours);
  • '02' to '28': 2n hours (i.e. range from 4 hours to 80 hours with step of 2 hours);
  • '29' to '50': 4n-80 hours (i.e. range from 84 hours to 240 hours with step of 4 hours).
All other values shall be interpreted by the ME as a default period.
For specification of the integer timer interval n, the maximum value and the default period refer to TS 23.122.
Up

4.2.7  EFACMmax (ACM maximum value)Word‑p. 29
If service No. 13 is "available", this file shall be present.
This EF contains the maximum value of the accumulated call meter.
Identifier: '6F37'Structure: transparentOptional
File size: 3 bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEPIN/PIN2 (fixed during administrative management)
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to 3Maximum valueM3 bytes
Maximum value
Contents:
  • maximum value of the Accumulated Call Meter (ACM).
Coding:
First byte:
b8 b7 b6 b5 b4 b3 b2 b1
223 222 221 220 219 218 217 216
 
Second byte:
b8 b7 b6 b5 b4 b3 b2 b1
215 214 213 212 211 210 29 28
 
Third byte:
b8 b7 b6 b5 b4 b3 b2 b1
27 26 25 24 23 22 21 20
 
For instance, '00' '00' '30' represents 25+24.
All ACM data is stored in the USIM and transmitted over the USIM/ME interface as binary.
ACMmax is not valid, as defined in TS 22.024, if it is coded '000000'.
If a GSM application is present on the UICC and the ACMmax value is to be shared between the GSM and the USIM application this file shall be shared between the two applications.
Up

4.2.8  EFUST (USIM Service Table)Word‑p. 30
This EF indicates which services are available. If a service is not indicated as available in the USIM, the ME shall not select this service.
Identifier: '6F38'Structure: transparentMandatory
SFI: '04'
File size: X bytes, (X ≥ 1)Update activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1Services No. 1 to No. 8M1 byte
2Services No. 9 to No. 16O1 byte
3Services No. 17 to No. 24O1 byte
4Services No. 25 to No. 32O1 byte
etc.
XServices No. (8X-7) to No. (8X)O1 byte
Services
Contents:
Service No. 1:Local Phone Book
Service No. 2:Fixed Dialling Numbers (FDN)
Service No. 3:Extension 2
Service No. 4:Service Dialling Numbers (SDN)
Service No. 5:Extension3
Service No. 6:Barred Dialling Numbers (BDN)
Service No. 7:Extension4
Service No. 8:Outgoing Call Information (OCI and OCT)
Service No. 9:Incoming Call Information (ICI and ICT)
Service No. 10:Short Message Storage (SMS)
Service No. 11:Short Message Status Reports (SMSR)
Service No. 12:Short Message Service Parameters (SMSP)
Service No. 13:Advice of Charge (AoC)
Service No. 14:Capability Configuration Parameters 2 (CCP2)
Service No. 15:Cell Broadcast Message Identifier
Service No. 16:Cell Broadcast Message Identifier Ranges
Service No. 17:Group Identifier Level 1
Service No. 18:Group Identifier Level 2
Service No. 19:Service Provider Name
Service No. 20:User controlled PLMN selector with Access Technology
Service No. 21:MSISDN
Service No. 22:Image (IMG)
Service No. 23:Support of Localised Service Areas (SoLSA)
Service No. 24:Enhanced Multi-Level Precedence and Pre-emption Service
Service No. 25:Automatic Answer for eMLPP
Service No. 26:RFU
Service No. 27:GSM Access
Service No. 28:Data download via SMS-PP
Service No. 29:Data download via SMS-CB
Service No. 30:Call Control by USIM
Service No. 31:MO-SMS Control by USIM
Service No. 32:RUN AT COMMAND command
Service No. 33:shall be set to '1'
Service No. 34:Enabled Services Table
Service No. 35:APN Control List (ACL)
Service No. 36:Depersonalisation Control Keys
Service No. 37:Co-operative Network List
Service No. 38:GSM security context
Service No. 39:CPBCCH Information
Service No. 40:Investigation Scan
Service No. 41:MexE
Service No. 42:Operator controlled PLMN selector with Access Technology
Service No. 43:HPLMN selector with Access Technology
Service No. 44:Extension 5
Service No. 45:PLMN Network Name
Service No. 46:Operator PLMN List
Service No. 47:Mailbox Dialling Numbers
Service No. 48:Message Waiting Indication Status
Service No. 49:Call Forwarding Indication Status
Service No. 50:Reserved and shall be ignored
Service No. 51:Service Provider Display Information
Service No. 52:Multimedia Messaging Service (MMS)
Service No. 53:Extension 8
Service No. 54:Call control on GPRS by USIM
Service No. 55:MMS User Connectivity Parameters
Service No. 56:Network's indication of alerting in the MS (EF NIA)
Service No. 57:VGCS Group Identifier List (EF VGCS and EF VGCSS)
Service No. 58:VBS Group Identifier List (EF VBS and EF VBSS)
Service No. 59:Pseudonym
Service No. 60:User Controlled PLMN selector for I-WLAN access
Service No. 61:Operator Controlled PLMN selector for I-WLAN access
Service No. 62:User controlled WSID list
Service No. 63:Operator controlled WSID list
Service No. 64:VGCS security
Service No. 65:VBS security
Service No. 66:WLAN Reauthentication Identity
Service No. 67:Multimedia Messages Storage
Service No. 68:Generic Bootstrapping Architecture (GBA)
Service No. 69:MBMS security
Service No. 70:Data download via USSD and USSD application mode
Service No. 71:Equivalent HPLMN
Service No. 72:Additional TERMINAL PROFILE after UICC activation
Service No. 73:Equivalent HPLMN Presentation Indication
Service No. 74:Last RPLMN Selection Indication
Service No. 75:OMA BCAST Smart Card Profile
Service No. 76:GBA-based Local Key Establishment Mechanism
Service No. 77:Terminal Applications
Service No. 78:Service Provider Name Icon
Service No. 79:PLMN Network Name Icon
Service No. 80:Connectivity Parameters for USIM IP connections
Service No. 81:Home I-WLAN Specific Identifier List
Service No. 82:I-WLAN Equivalent HPLMN Presentation Indication
Service No. 83:I-WLAN HPLMN Priority Indication
Service No. 84:I-WLAN Last Registered PLMN
Service No. 85:EPS Mobility Management Information
Service No. 86:Allowed CSG Lists and corresponding indications
Service No. 87:Call control on EPS PDN connection by USIM
Service No. 88:HPLMN Direct Access
Service No. 89:eCall Data
Service No. 90:Operator CSG Lists and corresponding indications
Service No. 91:Support for SM-over-IP
Service No. 92:Support of CSG Display Control
Service No. 93:Communication Control for IMS by USIM
Service No. 94:Extended Terminal Applications
Service No. 95:Support of UICC access to IMS
Service No. 96:Non-Access Stratum configuration by USIM
Service No. 97:PWS configuration by USIM
Service No. 98:RFU
Service No. 99:URI support by UICC
Service No. 100:Extended EARFCN support
Service No. 101:ProSe
Service No. 102:USAT Application Pairing
Service No. 103:Media Type support
Service No. 104:IMS call disconnection cause
Service No. 105:URI support for MO SHORT MESSAGE CONTROL
Service No. 106:ePDG configuration Information support
Service No. 107:ePDG configuration Information configured
Service No. 108:ACDC support
Service No. 109:Mission Critical Services
Service No. 110:ePDG configuration Information for Emergency Service support
Service No. 111:ePDG configuration Information for Emergency Service configured
Service No. 112:eCall Data over IMS
Service No. 113:URI support for SMS-PP DOWNLOAD as defined in TS 31.111
Service No. 114:From Preferred
Service No. 115:IMS configuration data
Service No. 116:TV configuration
Service No. 117:3GPP PS Data Off
Service No. 118:3GPP PS Data Off Service List
Service No. 119:V2X
Service No. 120:XCAP Configuration Data
Service No. 121:EARFCN list for MTC/NB-IOT UEs
Service No. 122:5GS Mobility Management Information
Service No. 123:5G Security Parameters
Service No. 124:Subscription identifier privacy support
Service No. 125:SUCI calculation by the USIM
Service No. 126:UAC Access Identities support
Service No. 127:Control plane-based steering of UE in VPLMN
Service No. 128:Call control on PDU Session by USIM
Service No. 129:5GS Operator PLMN List
Service No. 130:Support for SUPI of type NSI or GLI or GCI
Service No. 131:3GPP PS Data Off separate Home and Roaming lists
Service No. 132:Support for URSP by USIM
Service No. 133:5G Security Parameters extended
Service No. 134:MuD and MiD configuration data
Service No. 135:Support for Trusted non-3GPP access networks by USIM
Service No. 136:Pre-configured CAG information list
The EF shall contain at least one byte. Further bytes may be included, but if the EF includes an optional byte, then it is mandatory for the EF to also contain all bytes before that byte. Other services are possible in the future and will be coded on further bytes in the EF. The coding falls under the responsibility of the 3GPP.
Service No. 46 can only be declared "available" if service No. 45 is declared "available".
Service No. 95, No. 99 and No. 115 shall not be declared "available" if an ISIM application is present on the UICC.
Service No. 125 shall only be taken into account if Service No. 124 is declared "available". If Service No. 124 and Service No. 125 are declared "available", the "SUCI calculation is to be performed by the USIM". If Service No. 124 is declared "available" and Service No. 125 is not declared "available", the "SUCI calculation is to be performed by the ME".
Coding:
1 bit is used to code each service:
  • bit = 1: service available;
  • bit = 0: service not available.
Service available means that the USIM has the capability to support the service and that the service is available for the user of the USIM unless the service is identified as "disabled" in EF EST.
Service not available means that the service shall not be used by the USIM user, even if the USIM has the capability to support the service.
 
First byte:
b8 b7 b6 b5 b4 b3 b2 b1
Service No. 8 Service No. 7 Service No. 6 Service No. 5 Service No. 4 Service No. 3 Service No. 2 Service No. 1
 
Second byte:
b8 b7 b6 b5 b4 b3 b2 b1
Service No. 16 Service No. 15 Service No. 14 Service No. 13 Service No. 12 Service No. 11 Service No. 10 Service No. 9
 
etc.
Up


Up   Top   ToC