3GPP TS 31.102

3rd Generation Partnership Project;
3GPP TS 31.102
Technical Specification Group Core Network and Terminals;
V15.21.0 (2018-0610)
Characteristics of the
Universal Subscriber Identity Module (USIM) application
Technical Specification
(Release 15)
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.
The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners' Publications Offices.
Release 15 2 3GPP TS 31.102 V15.21.0 (2018-0610)
Keywords
UMTS, SIM, card, LTE
3GPP
Postal address
3GPP support office address

650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
http://www.3gpp.org
Copyright Notification
No part may be reproduced except as authorized by written permission.

The copyright and the foregoing restriction extend to reproduction in all media.
© 2018, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
All rights reserved.
UMTS™ is a Trade Mark of ETSI registered for the benefit of its members
3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
GSM® and the GSM logo are registered and owned by the GSM Association
3GPP
Release 15 3 3GPP TS 31.102 V15.21.0 (2018-0610)
Contents
Foreword...................................................................................................................................................12
Introduction...............................................................................................................................................12
1 Scope...............................................................................................................................................13
2 References.......................................................................................................................................13
3 Definitions, symbols, abbreviations and coding conventions.........................................................17
3.1 Definitions.................................................................................................................................................17
3.2 Symbols.....................................................................................................................................................18
3.3 Abbreviations............................................................................................................................................18
3.4 Coding Conventions..................................................................................................................................20
4 Contents of the Files.......................................................................................................................20
4.1 Contents of the EFs at the MF level..........................................................................................................20
4.2 Contents of files at the USIM ADF (Application DF) level.....................................................................21
4.2.1 EFLI (Language Indication).................................................................................................................21
4.2.2 EFIMSI (IMSI).......................................................................................................................................22
4.2.3 EFKeys (Ciphering and Integrity Keys).................................................................................................23
4.2.4 EFKeysPS (Ciphering and Integrity Keys for Packet Switched domain)................................................23
4.2.5 EFPLMNwAcT (User controlled PLMN selector with Access Technology).............................................24
4.2.6 EFHPPLMN (Higher Priority PLMN search period)................................................................................25
4.2.7 EFACMmax (ACM maximum value).......................................................................................................26
4.2.8 EFUST (USIM Service Table)...............................................................................................................28
4.2.9 EFACM (Accumulated Call Meter)........................................................................................................31
4.2.10 EFGID1 (Group Identifier Level 1)........................................................................................................31
4.2.12 EFSPN (Service Provider Name)...........................................................................................................32
4.2.13 EFPUCT (Price per Unit and Currency Table).......................................................................................33
4.2.14 EFCBMI (Cell Broadcast Message identifier selection).........................................................................34
4.2.15 EFACC (Access Control Class)..............................................................................................................35
4.2.16 EFFPLMN (Forbidden PLMNs)...............................................................................................................35
4.2.17 EFLOCI (Location Information).............................................................................................................36
4.2.18 EFAD (Administrative Data).................................................................................................................37
4.2.19 Void.....................................................................................................................................................39
4.2.20 EFCBMID (Cell Broadcast Message Identifier for Data Download).......................................................39
4.2.21 EFECC (Emergency Call Codes)...........................................................................................................40
4.2.22 EFCBMIR (Cell Broadcast Message Identifier Range selection)............................................................41
4.2.23 EFPSLOCI (Packet Switched location information)................................................................................41
4.2.24 EFFDN (Fixed Dialling Numbers).........................................................................................................43
4.2.25 EFSMS (Short messages).......................................................................................................................43
4.2.26 EFMSISDN (MSISDN).............................................................................................................................45
4.2.27 EFSMSP (Short message service parameters).........................................................................................45
4.2.28 EFSMSS (SMS status).............................................................................................................................47
4.2.29 EFSDN (Service Dialling Numbers).......................................................................................................47
4.2.30 EFEXT2 (Extension2).............................................................................................................................48
4.2.31 EFEXT3 (Extension3).............................................................................................................................48
4.2.32 EFSMSR (Short message status reports).................................................................................................49
4.2.33 EFICI (Incoming Call Information)......................................................................................................49
4.2.34 EFOCI (Outgoing Call Information)......................................................................................................53
4.2.35 EFICT (Incoming Call Timer)...............................................................................................................54
4.2.36 EFOCT (Outgoing Call Timer)..............................................................................................................54
4.2.37 EFEXT5 (Extension5).............................................................................................................................55
4.2.38 EFCCP2 (Capability Configuration Parameters 2).................................................................................55
4.2.39 EFeMLPP (enhanced Multi Level Precedence and Pre-emption)............................................................56
4.2.40 EFAaeM (Automatic Answer for eMLPP Service).................................................................................57
4.2.41 Void.....................................................................................................................................................58
4.2.42 EFHiddenkey (Key for hidden phone book entries)...................................................................................58
3GPP
Release 15 4 3GPP TS 31.102 V15.21.0 (2018-0610)
4.2.43 Void.....................................................................................................................................................58
4.2.44 EFBDN (Barred Dialling Numbers).......................................................................................................58
4.2.45 EFEXT4 (Extension4).............................................................................................................................59
4.2.46 EFCMI (Comparison Method Information)...........................................................................................59
4.2.47 EFEST (Enabled Services Table)...........................................................................................................60
4.2.48 EFACL (Access Point Name Control List)............................................................................................60
4.2.49 EFDCK (Depersonalisation Control Keys)............................................................................................61
4.2.50 EFCNL (Co-operative Network List).....................................................................................................61
4.2.51 EFSTART-HFN (Initialisation values for Hyperframe number).................................................................63
4.2.52 EFTHRESHOLD (Maximum value of START)..........................................................................................63
4.2.53 EFOPLMNwACT (Operator controlled PLMN selector with Access Technology).....................................63
4.2.54 EFHPLMNwAcT (HPLMN selector with Access Technology)...................................................................64
4.2.55 EFARR (Access Rule Reference)...........................................................................................................65
4.2.56 Void.....................................................................................................................................................66
4.2.57 EFNETPAR (Network Parameters)...........................................................................................................66
4.2.58 EFPNN (PLMN Network Name)...........................................................................................................68
4.2.59 EFOPL (Operator PLMN List)...............................................................................................................69
4.2.60 EFMBDN (Mailbox Dialling Numbers)..................................................................................................70
4.2.61 EFEXT6 (Extension6).............................................................................................................................71
4.2.62 EFMBI (Mailbox Identifier)...................................................................................................................71
4.2.63 EFMWIS (Message Waiting Indication Status)......................................................................................71
4.2.64 EFCFIS (Call Forwarding Indication Status).........................................................................................73
4.2.65 EFEXT7 (Extension7).............................................................................................................................74
4.2.66 EFSPDI (Service Provider Display Information)...................................................................................74
4.2.67 EFMMSN (MMS Notification)................................................................................................................75
4.2.68 EFEXT8 (Extension 8)............................................................................................................................77
4.2.69 EFMMSICP (MMS Issuer Connectivity Parameters)................................................................................77
4.2.70 EFMMSUP (MMS User Preferences).......................................................................................................80
4.2.71 EFMMSUCP (MMS User Connectivity Parameters).................................................................................81
4.2.72 EFNIA (Network's Indication of Alerting)............................................................................................81
4.2.73 EFVGCS (Voice Group Call Service).....................................................................................................82
4.2.74 EFVGCSS (Voice Group Call Service Status).........................................................................................84
4.2.75 EFVBS (Voice Broadcast Service).........................................................................................................84
4.2.76 EFVBSS (Voice Broadcast Service Status)............................................................................................86
4.2.77 EFVGCSCA (Voice Group Call Service Ciphering Algorithm)...............................................................87
4.2.78 EFVBSCA (Voice Broadcast Service Ciphering Algorithm)...................................................................88
4.2.79 EFGBABP (GBA Bootstrapping parameters)..........................................................................................88
4.2.80 EFMSK (MBMS Service Keys List)......................................................................................................89
4.2.81 EFMUK (MBMS User Key)...................................................................................................................90
4.2.82 Void.....................................................................................................................................................91
4.2.83 EFGBANL (GBA NAF List)....................................................................................................................91
4.2.84 EFEHPLMN (Equivalent HPLMN)...........................................................................................................92
4.2.85 EFEHPLMNPI (Equivalent HPLMN Presentation Indication)...................................................................92
4.2.86 EFLRPLMNSI (Last RPLMN Selection Indication)..................................................................................93
4.2.87 EFNAFKCA (NAF Key Centre Address)..................................................................................................93
4.2.88 EFSPNI (Service Provider Name Icon)..................................................................................................94
4.2.89 EFPNNI (PLMN Network Name Icon)..................................................................................................95
4.2.90 EFNCP-IP (Network Connectivity Parameters for USIM IP connections).............................................95
4.2.91 EFEPSLOCI (EPS location information)...................................................................................................98
4.2.92 EFEPSNSC (EPS NAS Security Context)..............................................................................................100
4.2.93 EFUFC (USAT Facility Control)......................................................................................................102
4.2.94 EFNASCONFIG (Non Access Stratum Configuration).............................................................................102
4.2.95 EFUICCIARI (UICC IARI)......................................................................................................................106
4.2.96 EFPWS (Public Warning System)........................................................................................................107
4.2.97 EFFDNURI (Fixed Dialling Numbers URI)...........................................................................................107
4.2.98 EFBDNURI (Barred Dialling Numbers URI).........................................................................................108
4.2.99 EFSDNURI (Service Dialling Numbers URI)........................................................................................109
4.2.100 EFIWL (IMEI(SV) White Lists)..........................................................................................................110
4.2.101 EFIPS (IMEI(SV) Pairing Status).......................................................................................................111
4.2.102 EFIPD (IMEI(SV) of Pairing Device).................................................................................................112
4.2.103 EFePDGId (Home ePDG Identifier).......................................................................................................113
3GPP
Release 15 5 3GPP TS 31.102 V15.21.0 (2018-0610)
4.2.104 EFePDGSelection (ePDG Selection Information).......................................................................................114

4.2.104a EFePDGIdEm (Emergency ePDG Identifier)...........................................................................................116
4.2.105 EFePDGSelectionEm (ePDG Selection Information for Emergency Services)............................................116
4.2.106 EFFromPreferred (From Preferred)............................................................................................................116
4.2.107 EFIMSConfigData (IMS Configuration Data).............................................................................................117
4.2.108 EFTVCONFIG (TV Configuration)..........................................................................................................117
4.2.109 EF3GPPPSDATAOFF (3GPP PS Data Off)..................................................................................................119
4.2.110 EF3GPPPSDATAOFFservicelist (3GPP PS Data Off Service List)....................................................................120
4.2.111 EFXCAPConfigData (XCAP Configuration Data).......................................................................................120
4.2.112 EFEARFCNList (EARFCN list for MTC/NB-IOT UEs)..........................................................................120
4.3 DFs at the USIM ADF (Application DF) Level.....................................................................................121
4.4 Contents of DFs at the USIM ADF (Application DF) level...................................................................122
4.4.1 Contents of files at the DF SoLSA level...........................................................................................122
4.4.1.1 EFSAI (SoLSA Access Indicator)..................................................................................................122
4.4.1.2 EFSLL (SoLSA LSA List).............................................................................................................123
4.4.1.3 LSA Descriptor files....................................................................................................................125
4.4.2 Contents of files at the DF PHONEBOOK level..............................................................................126
4.4.2.1 EFPBR (Phone Book Reference file).............................................................................................127
4.4.2.2 EFIAP (Index Administration Phone book)...................................................................................129
4.4.2.3 EFADN (Abbreviated dialling numbers)........................................................................................129
4.4.2.4 EFEXT1 (Extension1).....................................................................................................................132
4.4.2.5 EFPBC (Phone Book Control)........................................................................................................134
4.4.2.6 EFGRP (Grouping file)...................................................................................................................135
4.4.2.7 EFAAS (Additional number Alpha String).....................................................................................135
4.4.2.8 EFGAS (Grouping information Alpha String)................................................................................136
4.4.2.9 EFANR (Additional Number).........................................................................................................136
4.4.2.10 EFSNE (Second Name Entry).........................................................................................................138
4.4.2.11 EFCCP1 (Capability Configuration Parameters 1)..........................................................................139
4.4.2.12 Phone Book Synchronisation.......................................................................................................139
4.4.2.12.1 EFUID (Unique Identifier).......................................................................................................139
4.4.2.12.2 EFPSC (Phone book Synchronisation Counter).......................................................................140
4.4.2.12.3 EFCC (Change Counter)..........................................................................................................141
4.4.2.12.4 EFPUID (Previous Unique Identifier).......................................................................................142
4.4.2.13 EFEMAIL (e-mail address)..............................................................................................................142
4.4.2.14 Phonebook restrictions................................................................................................................143
4.4.2.15 EFPURI (Phonebook URIs)............................................................................................................143
4.4.3 Contents of files at the DF GSM-ACCESS level (Files required for GSM Access).......................144
4.4.3.1 EFKc (GSM Ciphering key Kc)....................................................................................................145
4.4.3.2 EFKcGPRS (GPRS Ciphering key KcGPRS)...................................................................................145
4.4.3.3 Void.............................................................................................................................................146
4.4.3.4 EFCPBCCH (CPBCCH Information)................................................................................................146
4.4.3.5 EFInvScan (Investigation Scan)........................................................................................................147
4.4.4 Contents of files at the MexE level.............................................................................................147
4.4.4.1 EFMexE-ST (MexE Service table)...............................................................................................148
4.4.4.2 EFORPK (Operator Root Public Key).......................................................................................148
4.4.4.3 EFARPK (Administrator Root Public Key)...............................................................................150
4.4.4.4 EFTPRPK (Third Party Root Public Key)..................................................................................151
4.4.4.5 EFTKCDF (Trusted Key/Certificates Data Files).......................................................................151
4.4.5 Contents of files at the DF WLAN level...........................................................................................152
4.4.5.1 EFPseudo (Pseudonym)....................................................................................................................152
4.4.5.2 EFUPLMNWLAN (User controlled PLMN selector for I-WLAN Access)..........................................153
4.4.5.3 EFOPLMNWLAN (Operator controlled PLMN selector for I-WLAN Access).........................................153
4.4.5.4 EFUWSIDL (User controlled WLAN Specific Identifier List).........................................................154
4.4.5.5 EFOWSIDL (Operator controlled WLAN Specific IdentifierList)...................................................155
4.4.5.6 EFWRI (WLAN Reauthentication Identity)...................................................................................155
4.4.5.7 EFHWSIDL (Home I-WLAN Specific Identifier List).....................................................................156
4.4.5.8 EFWEHPLMNPI (I-WLAN Equivalent HPLMN Presentation Indication).........................................157
4.4.5.9 EFWHPI (I-WLAN HPLMN Priority Indication)...........................................................................157
4.4.5.10 EFWLRPLMN (I-WLAN Last Registered PLMN).............................................................................158
4.4.5.11 EFHPLMNDAI (HPLMN Direct Access Indicator)............................................................................158
4.4.6 Contents of files at the DF HNB level..............................................................................................159
3GPP
Release 15 6 3GPP TS 31.102 V15.21.0 (2018-0610)
4.4.6.1 Introduction.................................................................................................................................159
4.4.6.2 EFACSGL (Allowed CSG Lists)......................................................................................................159
4.4.6.3 EFCSGT (CSG Type)......................................................................................................................162
4.4.6.4 EFHNBN (Home NodeB Name)......................................................................................................164
4.4.6.5 EFOCSGL (Operator CSG Lists)......................................................................................................164
4.4.6.6 EFOCSGT (Operator CSG Type).....................................................................................................166
4.4.6.7 EFOHNBN (Operator Home NodeB Name).....................................................................................167
4.4.7 Void...................................................................................................................................................167
4.4.8 Contents of files at the DF ProSe level.............................................................................................167
4.4.8.1 Introduction.................................................................................................................................167
4.4.8.2 EFPROSE_MON (ProSe Monitoring Parameters)................................................................................167
4.4.8.3 EFPROSE_ANN (ProSe Announcing Parameters)..............................................................................168
4.4.8.4 EFPROSEFUNC (HPLMN ProSe Function)........................................................................................169
4.4.8.5 EFPROSE_RADIO_COM (ProSe Direct Communication Radio Parameters)..........................................170
4.4.8.6 EFPROSE_RADIO_MON (ProSe Direct Discovery Monitoring Radio Parameters)................................172
4.4.8.7 EFPROSE_RADIO_ANN (ProSe Direct Discovery Announcing Radio Parameters)...............................173
4.4.8.8 EFPROSE_POLICY (ProSe Policy Parameters).....................................................................................174
4.4.8.9 EFPROSE_PLMN (ProSe PLMN Parameters)......................................................................................176
4.4.8.10 EFPROSE_GC (ProSe Group Counter)...............................................................................................177
4.4.8.11 EFPST (ProSe Service Table)........................................................................................................179
4.4.8.12 EFPROSE_UIRC (ProSe UsageInformationReportingConfiguration).................................................179
4.4.8.12 EFPROSE_GM_DISCOVERY (ProSe Group Member Discovery Parameters)...........................................183
4.4.8.13 EFPROSE_RELAY (ProSe Relay Parameters)......................................................................................184
4.4.8.14 EFPROSE_RELAY_DISCOVERY (ProSe Relay Discovery Parameters)......................................................185
4.4.9 Contents of files at the DF ACDC level............................................................................................188
4.4.9.1 Introduction.................................................................................................................................188
4.4.9.2 EFACDC_LIST (ACDC List)..............................................................................................................188
4.4.9.3 EFACDC_OS_CONFIG (ACDC OS configuration).................................................................................189
4.4.10 Contents of files at the DF TV level.................................................................................................190
4.4.10.1 Introduction.................................................................................................................................190
4.4.10.2 EFTVUSD (TV User Service Description).......................................................................................190
4.4.11 Contents of files at the DF5GS level....................................................................................................191
4.4.11.1 Introduction.................................................................................................................................191
4.4.11.2 EF5GS3GPPLOCI (5GS 3GPP location information)...........................................................................191
4.4.11.3 EF5GSN3GPPLOCI (5GS non-3GPP location information)..................................................................193
4.4.11.4 EF5GS3GPPNSC (5GS 3GPP Access NAS Security Context)............................................................193
4.4.11.5 EF5GSN3GPPNSC (5GS non-3GPP Access NAS Security Context)...................................................195
4.4.11.6 EF5GAUTHKEYS (5G authentication keys).........................................................................................196
4.4.11.7 EFUAC_AIC (UAC Access Identities Configuration)............................................................................197
4.4.11.8 EFSUCI_Calc_Info (Subscription Concealed Identifier Calculation Information EF)................................197
4.4.11.9 EFSteering_of_UE_in_VPLMN (Steering of UE in VPLMN)............................................................................199
4.5 Contents of Efs at the TELECOM level.................................................................................................200
4.5.1 EFADN (Abbreviated dialling numbers)..............................................................................................200
4.5.2 EFEXT1 (Extension1)...........................................................................................................................200
4.5.3 EFECCP (Extended Capability Configuration Parameter)...................................................................200
4.5.4 EFSUME (SetUpMenu Elements).........................................................................................................201
4.5.5 EFARR (Access Rule Reference).........................................................................................................201
4.5.6 EFICE_DN (In Case of Emergency – Dialling Number).......................................................................201
4.5.7 EFICE_FF (In Case of Emergency – Free Format)................................................................................202
4.5.8 EFRMA (Remote Management Actions)..............................................................................................202
4.5.9 EFPSISMSC (Public Service Identity of the SM-SC).............................................................................203
4.6 Contents of DFs at the TELECOM level................................................................................................203
4.6.0 List of DFs at the TELECOM level..................................................................................................203
4.6.1 Contents of files at the DFGRAPHICS level............................................................................................203
4.6.1.1 EFIMG (Image)..............................................................................................................................203
4.6.1.2 EFIIDF (Image Instance Data Files)...............................................................................................205
4.6.1.3 EFICE_graphics (In Case of Emergency – Graphics).................................................................205
4.6.1.4 Void.............................................................................................................................................206
4.6.1.5 Void.............................................................................................................................................206
4.6.2 Contents of files at the DFPHONEBOOK under the DFTELECOM.................................................................206
4.6.3 Contents of files at the DFMULTIMEDIA level.........................................................................................206
3GPP
Release 15 7 3GPP TS 31.102 V15.21.0 (2018-0610)
4.6.3.1 EFMML (Multimedia Messages List).............................................................................................206

4.6.3.2 EFMMDF (Multimedia Messages Data File)...................................................................................209
4.6.4 Contents of files at the DFMCS level...................................................................................................210
4.6.4.1 EFMST (MCS Service Table).........................................................................................................210
4.6.4.2 EFMCS_ CONFIG (MCS configuration data).......................................................................................210
4.6.4.3 Void.............................................................................................................................................211
4.6.4.4 Void.............................................................................................................................................211
4.6.4.5 Void.............................................................................................................................................211
4.6.5 Contents of files at the DFV2X level...................................................................................................211
4.6.5.1 V2X configuration data related files...........................................................................................211
4.6.5.2 EFVST (V2X Service Table)..........................................................................................................212
4.6.5.3 EFV2X_CONFIG (V2X configuration data).........................................................................................212
4.7 Files of USIM.........................................................................................................................................214
5 Application protocol.....................................................................................................................219
5.1 USIM management procedures...............................................................................................................219
5.1.1 Initialisation.......................................................................................................................................219
5.1.1.1 USIM application selection.........................................................................................................219
5.1.1.2 USIM initialisation......................................................................................................................219
5.1.1.3 GSM related initialisation procedures.........................................................................................220
5.1.2 Session termination...........................................................................................................................221
5.1.2.1 3G session termination................................................................................................................221
5.1.2.1.1 GSM termination procedures.................................................................................................221
5.1.2.2 3G session reset...........................................................................................................................221
5.1.3 USIM application closure..................................................................................................................221
5.1.4 Emergency call codes........................................................................................................................221
5.1.5 Language indication..........................................................................................................................222
5.1.6 Administrative information request..................................................................................................222
5.1.7 USIM service table request...............................................................................................................222
5.1.8 Void...................................................................................................................................................222
5.1.9 UICC presence detection...................................................................................................................222
5.1.10 UICC interface in PSM.....................................................................................................................222
5.1.11 UICC interface during eDRX............................................................................................................222
5.2 USIM security related procedures..........................................................................................................223
5.2.1 Authentication algorithms computation............................................................................................223
5.2.2 IMSI request......................................................................................................................................223
5.2.3 Access control information request...................................................................................................223
5.2.4 Higher Priority PLMN search period request...................................................................................223
5.2.5 Location information.........................................................................................................................223
5.2.6 Cipher and Integrity key....................................................................................................................223
5.2.7 Forbidden PLMN..............................................................................................................................223
5.2.8 Void...................................................................................................................................................224
5.2.9 User Identity Request........................................................................................................................224
5.2.10 GSM Cipher key................................................................................................................................224
5.2.11 GPRS Cipher key..............................................................................................................................224
5.2.12 Initialisation value for Hyperframe number......................................................................................224
5.2.13 Maximum value of START...............................................................................................................224
5.2.14 HPLMN selector with Access Technology request..........................................................................224
5.2.15 Packet Switched Location information.............................................................................................224
5.2.16 Cipher and Integrity key for Packet Switched domain......................................................................224
5.2.17 LSA information...............................................................................................................................224
5.2.18 Voice Group Call Services................................................................................................................225
5.2.19 Voice Broadcast Services..................................................................................................................225
5.2.20 Generic Bootstrapping architecture (Bootstrap)................................................................................225
5.2.21 Generic Bootstrapping architecture (NAF Derivation).....................................................................225
5.2.22 MSK MIKEY Message Reception....................................................................................................225
5.2.23 MTK MIKEY Message Reception....................................................................................................225
5.2.24 Void...................................................................................................................................................225
5.2.25 EHPLMN request..............................................................................................................................225
5.2.26 Last RPLMN Selection Indication request........................................................................................226
5.2.29 Non Access Stratum Configuration...................................................................................................226
5.2.30 PWS Configuration...........................................................................................................................226
3GPP
Release 15 8 3GPP TS 31.102 V15.21.0 (2018-0610)
5.3 Subscription related procedures..............................................................................................................227

5.3.1 Phone book procedures.....................................................................................................................227
5.3.1.1 Initialisation.................................................................................................................................227
5.3.1.2 Creation/Deletion of information................................................................................................227
5.3.1.3 Hidden phone book entries..........................................................................................................227
5.3.2 Dialling numbers...............................................................................................................................227
5.3.3 Short messages..................................................................................................................................229
5.3.4 Advice of charge...............................................................................................................................229
5.3.5 Capability configuration parameters.................................................................................................230
5.3.6 User controlled PLMN selector with Access Technology................................................................230
5.3.7 Cell broadcast message identifier......................................................................................................230
5.3.8 Group identifier level 1.....................................................................................................................230
5.3.10 Service provider name.......................................................................................................................230
5.3.11 Enhanced multi level precedence and pre-emption service..............................................................231
5.3.12 Cell broadcast message identifier ranges..........................................................................................231
5.3.13 Short message status report...............................................................................................................231
5.3.14 APN Control List..............................................................................................................................231
5.3.15 Depersonalisation Control Keys........................................................................................................232
5.3.16 Co-operative Network List................................................................................................................232
5.3.17 CPBCCH information.......................................................................................................................232
5.3.18 Investigation Scan.............................................................................................................................232
5.3.19 Enabled Services Table Request.......................................................................................................232
5.3.20 Operator controlled PLMN selector with Access Technology.........................................................232
5.3.21 HPLMN selector with Access Technology.......................................................................................232
5.3.22 Automatic Answer on eMLPP service..............................................................................................233
5.3.23 Network Parameter information........................................................................................................233
5.3.24 PLMN network name........................................................................................................................233
5.3.25 Operator PLMN List.........................................................................................................................233
5.3.26 Message Waiting Indication..............................................................................................................233
5.3.27 Call Forwarding Indication Status.....................................................................................................233
5.3.28 Service Provider Display Information...............................................................................................233
5.3.29 MMS Notifications............................................................................................................................233
5.3.30 MMS Issuer Connectivity Parameters...............................................................................................234
5.3.31 MMS User Preferences.....................................................................................................................234
5.3.32 MMS User Connectivity Parameters.................................................................................................234
5.3.33 Network's indication of alerting........................................................................................................234
5.3.34 Multimedia Messages Storage..........................................................................................................234
5.3.35 Equivalent HPLMN Presentation Indication request........................................................................235
5.3.36 NAF Key Centre Address request.....................................................................................................235
5.3.37 Service provider name Icon...............................................................................................................235
5.3.38 PLMN network name Icon................................................................................................................235
5.3.39 ICE Information request....................................................................................................................235
5.3.40 eCall Related Procedures..................................................................................................................236
5.3.40.1 eCall Only support.......................................................................................................................236
5.3.40.2 eCall and Normal call support.....................................................................................................236
5.3.40.3 Change of eCall mode.................................................................................................................237
5.3.41 SM-over-IP........................................................................................................................................237
5.3.42 UICC access to IMS..........................................................................................................................237
5.3.43 TV Configuration..............................................................................................................................237
5.3.44 3GPP PS Data Off related procedures...............................................................................................237
5.3.45 3GPP PS Data Off service list related procedures............................................................................237
5.3.46 EARFCN list for MTC/NB-IOT UEs...............................................................................................238
5.3.47 SUCI Calculation information procedure.........................................................................................238
5.3.48 SUCI Calculation by the USIM procedure.......................................................................................238
5.3.49 Control plane-based Steering of Roaming related procedures..........................................................238
5.4 USAT related procedures........................................................................................................................238
5.4.1 Data Download via SMS-PP.............................................................................................................238
5.4.2 Image Request...................................................................................................................................238
5.4.3 Data Download via SMS-CB............................................................................................................238
5.4.4 Call Control by USIM.......................................................................................................................239
3GPP
Release 15 9 3GPP TS 31.102 V15.21.0 (2018-0610)
5.4.5 MO-SMS control by USIM...............................................................................................................239

5.4.6 Data Download via USSD and USSD application mode..................................................................239
5.4.7 Additional TERMINAL PROFILE after UICC activation...............................................................239
5.4.8 Terminal Applications.......................................................................................................................239
5.4.9 Call control on EPS PDN connection by USIM...............................................................................239
5.4.10 Communication Control for IMS by USIM......................................................................................239
5.4.11 USAT Facility Control......................................................................................................................239
5.4.12 Extended Terminal Applications.......................................................................................................239
5.4.13 USAT application pairing procedure................................................................................................240
5.4.14 Call control on PDU Session by USIM.............................................................................................240
5.5 MexE related procedures........................................................................................................................240
5.5.1 MexE ST...........................................................................................................................................240
5.5.2 Operator root public key...................................................................................................................240
5.5.3 Administrator root public key...........................................................................................................241
5.5.4 Third Party root public key(s)...........................................................................................................241
5.5.5 Trusted Key/Certificates Data Files..................................................................................................241
5.6 WLAN related procedures......................................................................................................................241
5.6.1 WLAN Selection related Procedures................................................................................................241
5.6.2 WLAN PLMN Selection related procedures....................................................................................241
5.6.3 WLAN access authentication related procedures..............................................................................241
5.6.4 WLAN access re-authentication related procedures.........................................................................241
5.7 Network Connectivity Parameters for UICC IP connections related procedures.............................242
5.8 H(e)NB related procedures.....................................................................................................................242
5.8.1 CSG Access Control procedures.......................................................................................................242
5.8.2 CSG Type related procedures...........................................................................................................242
5.8.3 HNB name display related procedures..............................................................................................243
5.9 ProSe related procedures.........................................................................................................................243
5.9.1 ProSe Direct Discovery Provisioning parameters.............................................................................243
5.9.2 HPLMN ProSe Function address......................................................................................................243
5.9.3 ProSe direct communication related Procedures...............................................................................243
5.9.4 ProSe direct discovery related Procedures........................................................................................243
5.9.7 ProSe Group Counter related Procedures..........................................................................................244
5.9.8 ProSe Usage Information Reporting Configuration related Procedures...........................................244
5.9.9 ProSe Group Member Discovery related Procedures.......................................................................244
5.9.10 ProSe Relay related Procedures........................................................................................................244
5.10 ePDG Selection related procedures........................................................................................................245
5.10.1 Home ePDG Identifier......................................................................................................................245
5.10.2 ePDG Selection Information.............................................................................................................245
5.10.3 ePDG configuration information configured but empty...................................................................245
5.11 ACDC related procedures.......................................................................................................................245
5.11.1 ACDC Configuration........................................................................................................................245
5.12 MCS related procedures..........................................................................................................................245
5.12.1 MCS configuration............................................................................................................................245
5.12.2 Void...................................................................................................................................................245
5.12.3 Void...................................................................................................................................................245
5.12.4 Void...................................................................................................................................................246
5.13 ePDG Selection for Emergency Services related procedures.................................................................246
5.13.1 Emergency ePDG Identifier..............................................................................................................246
5.13.2 ePDG Selection Information for Emergency Services......................................................................246
5.13.3 ePDG configuration information for Emergency Services configured but empty............................246
5.13.4 From Preferred related procedures....................................................................................................246
5.13.5 IMS Configuration Data related procedures.....................................................................................246
5.13.6 XCAP Configuration Data related procedures..................................................................................246
5.14 V2X related procedures..........................................................................................................................247
5.14.1 V2X configuration.............................................................................................................................247
5.15 UAC Access Identities related procedures.............................................................................................247
5.15.1 UAC Access Identities Configuration...............................................................................................247
6 Security features............................................................................................................................247
6.1 Authentication and key agreement procedure.........................................................................................247
3GPP
Release 15 10 3GPP TS 31.102 V15.21.0 (2018-0610)
6.2 Cryptographic Functions.........................................................................................................................248

6.3 GSM Conversion Functions....................................................................................................................248
6.4 User verification and file access conditions............................................................................................248
7 USIM Commands.........................................................................................................................248
7.1 AUTHENTICATE..................................................................................................................................248
7.1.1 Command description.......................................................................................................................248
7.1.1.1 3G security context......................................................................................................................249
7.1.1.2 GSM security context..................................................................................................................250
7.1.1.3 VGCS/VBS security context.......................................................................................................250
7.1.1.4 GBA security context (Bootstrapping Mode)..............................................................................251
7.1.1.5 GBA security context (NAF Derivation Mode)..........................................................................251
7.1.1.6 MBMS security context (MSK Update Mode)............................................................................252
7.1.1.7 Void.............................................................................................................................................254
7.1.1.8 MBMS security context (MTK Generation Mode).....................................................................254
7.1.1.9 MBMS security context (MSK Deletion Mode).........................................................................254
7.1.1.10 MBMS security context (MUK Deletion Mode).........................................................................254
7.1.1.11 Local Key Establishment security context (Key Derivation mode)............................................255
7.1.1.12 Local Key Establishment security context (Key Availability Check mode)...............................256
7.1.2 Command parameters and data.........................................................................................................256
7.1.2.1 GSM/3G security context............................................................................................................258
7.1.2.5 MBMS security context (All Modes)..........................................................................................260
7.1.2.6 Local Key Establishment security context (All Modes)..............................................................261
7.1.2.6.1 Local Key Establishment security context (Key Derivation mode)......................................261
7.1.2.6.2 Local Key Establishment security context (Key Availability Check mode).........................263
7.2 Void.........................................................................................................................................................264
7.3 Status Conditions Returned by the USIM...............................................................................................264
7.3.1 Security management........................................................................................................................264
7.3.2 Status Words of the Commands........................................................................................................265
7.4 Optional commands................................................................................................................................266
7.5 GET IDENTITY.....................................................................................................................................266
7.5.1.1 SUCI context...............................................................................................................................266
7.5.2.1 SUCI context...............................................................................................................................268
8 Void...............................................................................................................................................268
Annex A (informative): EF changes via Data Download or USAT applications............................269
Annex B (normative): Image Coding Schemes...................................................................................273
B.1 Basic Image Coding Scheme........................................................................................................273
B.2 Colour Image Coding Scheme......................................................................................................274
B.3 Colour Image Coding Scheme with Transparency.......................................................................275
Annex C (informative): Structure of the Network parameters TLV objects..................................276
Annex D (informative): Tags defined in 31.102..................................................................................277
Annex E (informative): Suggested contents of the EFs at pre-personalization...............................282
Annex F (informative): Examples of coding of LSA Descriptor files for SoLSA............................286
Annex G (informative): Phonebook Example....................................................................................287
Annex H (normative): List of SFI Values...........................................................................................291
H.1 List of SFI Values at the USIM ADF Level.................................................................................291
3GPP
Release 15 11 3GPP TS 31.102 V15.21.0 (2018-0610)
H.2 List of SFI Values at the DF GSM-ACCESS Level.....................................................................291

H.3 List of SFI Values at the DF WLAN Level..................................................................................292
H.4 List of SFI Values at the DF HNB Level......................................................................................292
H.5 List of SFI Values at the DF ProSe Level.....................................................................................292
H.6 List of SFI Values at the DF ACDC Level...................................................................................292
H.7 List of SFI Values at the DF MCS Level......................................................................................293
H.8 List of SFI Values at the DF V2X Level......................................................................................293
H.9 List of SFI Values at the DF 5GS Level.......................................................................................293
H.10 List of SFI Values at the DF 5GS Level.......................................................................................293
Annex I (informative): USIM Application Session Activation/Termination...................................294
Annex J (informative): Example of MMS coding..............................................................................295
J.1 Coding example for MMS User Preferences..........................................................................................295
J.2 Coding Example for MMS Issuer/User Connectivity Parameters..........................................................295
Annex K (informative): Examples of VService_Id coding................................................................297

Annex L (normative): USIM-INI and USIM-RN for Relay Nodes..................................................298
L.1 Introduction.............................................................................................................................................298
L.2 Application selection procedure.............................................................................................................298
L.3 Secure channel operation........................................................................................................................299
L.4 Support of commands.............................................................................................................................299
L.5 Storage of certificates.............................................................................................................................299
L.6 Relay Node files support.........................................................................................................................299
L.6.1 USIM-INI Files.................................................................................................................................299
L.6.1.1 EFCERT (UICC Certificate)............................................................................................................299
L.6.2 USIM-RN Files.................................................................................................................................300
L.6.2.1 eFRNid (Relay Node identifier)......................................................................................................300
L.6.2.2 EFSCCmax (maximum value of Secure Channel Counter)..............................................................301
Annex M (normative): USIM application dedicated for IOPS.........................................................302

M.1 Introduction.............................................................................................................................................302
M.2 Features of the USIM dedicated for IOPS..............................................................................................302
M.3 Selection mechanisms.......................................................................................................................302
Annex N (informative): Change history..............................................................................................303

Foreword...................................................................................................................................................12
Introduction...............................................................................................................................................12
1 Scope...............................................................................................................................................13
2 References.......................................................................................................................................13
3 Definitions, symbols, abbreviations and coding conventions.........................................................17
3.1 Definitions.................................................................................................................................................17
3.2 Symbols.....................................................................................................................................................18
3.3 Abbreviations............................................................................................................................................18
3.4 Coding Conventions..................................................................................................................................20
4 Contents of the Files.......................................................................................................................20
4.1 Contents of the EFs at the MF level..........................................................................................................20
4.2 Contents of files at the USIM ADF (Application DF) level.....................................................................21
4.2.1 EFLI (Language Indication).................................................................................................................21
4.2.2 EFIMSI (IMSI).......................................................................................................................................22
4.2.3 EFKeys (Ciphering and Integrity Keys).................................................................................................23
4.2.4 EFKeysPS (Ciphering and Integrity Keys for Packet Switched domain)................................................23
3GPP
Release 15 12 3GPP TS 31.102 V15.21.0 (2018-0610)
4.2.5 EFPLMNwAcT (User controlled PLMN selector with Access Technology).............................................24

4.2.6 EFHPPLMN (Higher Priority PLMN search period)................................................................................25
4.2.7 EFACMmax (ACM maximum value).......................................................................................................26
4.2.8 EFUST (USIM Service Table)...............................................................................................................28
4.2.9 EFACM (Accumulated Call Meter)........................................................................................................31
4.2.12 EFSPN (Service Provider Name)...........................................................................................................32
4.2.13 EFPUCT (Price per Unit and Currency Table).......................................................................................33
4.2.14 EFCBMI (Cell Broadcast Message identifier selection).........................................................................34
4.2.15 EFACC (Access Control Class)..............................................................................................................35
4.2.16 EFFPLMN (Forbidden PLMNs)...............................................................................................................35
4.2.17 EFLOCI (Location Information).............................................................................................................36
4.2.18 EFAD (Administrative Data).................................................................................................................37
4.2.19 Void.....................................................................................................................................................39
4.2.20 EFCBMID (Cell Broadcast Message Identifier for Data Download).......................................................39
4.2.21 EFECC (Emergency Call Codes)...........................................................................................................40
4.2.22 EFCBMIR (Cell Broadcast Message Identifier Range selection)............................................................41
4.2.23 EFPSLOCI (Packet Switched location information)................................................................................41
4.2.24 EFFDN (Fixed Dialling Numbers).........................................................................................................43
4.2.25 EFSMS (Short messages).......................................................................................................................43
4.2.26 EFMSISDN (MSISDN).............................................................................................................................45
4.2.27 EFSMSP (Short message service parameters).........................................................................................45
4.2.28 EFSMSS (SMS status).............................................................................................................................47
4.2.29 EFSDN (Service Dialling Numbers).......................................................................................................47
4.2.30 EFEXT2 (Extension2).............................................................................................................................48
4.2.31 EFEXT3 (Extension3).............................................................................................................................48
4.2.32 EFSMSR (Short message status reports).................................................................................................49
4.2.33 EFICI (Incoming Call Information)......................................................................................................49
4.2.34 EFOCI (Outgoing Call Information)......................................................................................................53
4.2.35 EFICT (Incoming Call Timer)...............................................................................................................54
4.2.36 EFOCT (Outgoing Call Timer)..............................................................................................................54
4.2.37 EFEXT5 (Extension5).............................................................................................................................55
4.2.38 EFCCP2 (Capability Configuration Parameters 2).................................................................................55
4.2.39 EFeMLPP (enhanced Multi Level Precedence and Pre-emption)............................................................56
4.2.40 EFAaeM (Automatic Answer for eMLPP Service).................................................................................57
4.2.41 Void.....................................................................................................................................................58
4.2.42 EFHiddenkey (Key for hidden phone book entries)...................................................................................58
4.2.43 Void.....................................................................................................................................................58
4.2.44 EFBDN (Barred Dialling Numbers).......................................................................................................58
4.2.45 EFEXT4 (Extension4).............................................................................................................................59
4.2.46 EFCMI (Comparison Method Information)...........................................................................................59
4.2.47 EFEST (Enabled Services Table)...........................................................................................................60
4.2.48 EFACL (Access Point Name Control List)............................................................................................60
4.2.49 EFDCK (Depersonalisation Control Keys)............................................................................................61
4.2.50 EFCNL (Co-operative Network List).....................................................................................................61
4.2.51 EFSTART-HFN (Initialisation values for Hyperframe number).................................................................63
4.2.52 EFTHRESHOLD (Maximum value of START)..........................................................................................63
4.2.53 EFOPLMNwACT (Operator controlled PLMN selector with Access Technology).....................................63
4.2.54 EFHPLMNwAcT (HPLMN selector with Access Technology)...................................................................64
4.2.55 EFARR (Access Rule Reference)...........................................................................................................65
4.2.56 Void.....................................................................................................................................................66
4.2.57 EFNETPAR (Network Parameters)...........................................................................................................66
4.2.58 EFPNN (PLMN Network Name)...........................................................................................................68
4.2.59 EFOPL (Operator PLMN List)...............................................................................................................69
4.2.60 EFMBDN (Mailbox Dialling Numbers)..................................................................................................70
4.2.61 EFEXT6 (Extension6).............................................................................................................................71
4.2.62 EFMBI (Mailbox Identifier)...................................................................................................................71
4.2.63 EFMWIS (Message Waiting Indication Status)......................................................................................71
4.2.64 EFCFIS (Call Forwarding Indication Status).........................................................................................73
4.2.65 EFEXT7 (Extension7).............................................................................................................................74
3GPP
Release 15 13 3GPP TS 31.102 V15.21.0 (2018-0610)
4.2.66 EFSPDI (Service Provider Display Information)...................................................................................74

4.2.67 EFMMSN (MMS Notification)................................................................................................................75
4.2.68 EFEXT8 (Extension 8)............................................................................................................................77
4.2.69 EFMMSICP (MMS Issuer Connectivity Parameters)................................................................................77
4.2.70 EFMMSUP (MMS User Preferences).......................................................................................................80
4.2.71 EFMMSUCP (MMS User Connectivity Parameters).................................................................................81
4.2.72 EFNIA (Network's Indication of Alerting)............................................................................................81
4.2.73 EFVGCS (Voice Group Call Service).....................................................................................................82
4.2.74 EFVGCSS (Voice Group Call Service Status).........................................................................................84
4.2.75 EFVBS (Voice Broadcast Service).........................................................................................................84
4.2.76 EFVBSS (Voice Broadcast Service Status)............................................................................................86
4.2.77 EFVGCSCA (Voice Group Call Service Ciphering Algorithm)...............................................................87
4.2.78 EFVBSCA (Voice Broadcast Service Ciphering Algorithm)...................................................................88
4.2.79 EFGBABP (GBA Bootstrapping parameters)..........................................................................................88
4.2.80 EFMSK (MBMS Service Keys List)......................................................................................................89
4.2.81 EFMUK (MBMS User Key)...................................................................................................................90
4.2.82 Void.....................................................................................................................................................91
4.2.83 EFGBANL (GBA NAF List)....................................................................................................................91
4.2.84 EFEHPLMN (Equivalent HPLMN)...........................................................................................................92
4.2.85 EFEHPLMNPI (Equivalent HPLMN Presentation Indication)...................................................................92
4.2.86 EFLRPLMNSI (Last RPLMN Selection Indication)..................................................................................93
4.2.87 EFNAFKCA (NAF Key Centre Address)..................................................................................................93
4.2.88 EFSPNI (Service Provider Name Icon)..................................................................................................94
4.2.89 EFPNNI (PLMN Network Name Icon)..................................................................................................95
4.2.90 EFNCP-IP (Network Connectivity Parameters for USIM IP connections).............................................95
4.2.91 EFEPSLOCI (EPS location information)...................................................................................................98
4.2.92 EFEPSNSC (EPS NAS Security Context)..............................................................................................100
4.2.93 EFUFC (USAT Facility Control)......................................................................................................102
4.2.94 EFNASCONFIG (Non Access Stratum Configuration).............................................................................102
4.2.95 EFUICCIARI (UICC IARI)......................................................................................................................106
4.2.96 EFPWS (Public Warning System)........................................................................................................107
4.2.97 EFFDNURI (Fixed Dialling Numbers URI)...........................................................................................107
4.2.98 EFBDNURI (Barred Dialling Numbers URI).........................................................................................108
4.2.99 EFSDNURI (Service Dialling Numbers URI)........................................................................................109
4.2.100 EFIWL (IMEI(SV) White Lists)..........................................................................................................110
4.2.101 EFIPS (IMEI(SV) Pairing Status).......................................................................................................111
4.2.102 EFIPD (IMEI(SV) of Pairing Device).................................................................................................112
4.2.103 EFePDGId (Home ePDG Identifier).......................................................................................................113
4.2.104 EFePDGSelection (ePDG Selection Information).......................................................................................114
4.2.104a EFePDGIdEm (Emergency ePDG Identifier)...........................................................................................116
4.2.105 EFePDGSelectionEm (ePDG Selection Information for Emergency Services)............................................116
4.2.106 EFFromPreferred (From Preferred)............................................................................................................116
4.2.107 EFIMSConfigData (IMS Configuration Data).............................................................................................117
4.2.108 EFTVCONFIG (TV Configuration)..........................................................................................................117
4.2.109 EF3GPPPSDATAOFF (3GPP PS Data Off)..................................................................................................119
4.2.110 EF3GPPPSDATAOFFservicelist (3GPP PS Data Off Service List)....................................................................120
4.2.111 EFXCAPConfigData (XCAP Configuration Data).......................................................................................120
4.2.112 EFEARFCNList (EARFCN list for MTC/NB-IOT UEs)..........................................................................120
4.2.113 EF5GS3GPPLOCI (5GS 3GPP location information)................................................................................121
4.2.114 EF5GAUTHKEYS (5G authentication keys)..............................................................................................123
4.2.115 EF5GS3GPPNSC (5GS 3GPP Access NAS Security Context)..................................................................123
4.2.116 EF5GS3GPPNSC (5GS non-3GPP Access NAS Security Context)..........................................................125
4.2.117 EFSUCI_Calc_Info (Subscription Concealed Identifier Calculation Information EF)................................126
4.2.118 EFUAC_AIC (UAC Access Identities Configuration)............................................................................128
4.2.119 EFSteering_of_UE_in_VPLMN (Steering of UE in VPLMN)............................................................................128
4.3 DFs at the USIM ADF (Application DF) Level.....................................................................................129
4.4 Contents of DFs at the USIM ADF (Application DF) level...................................................................129
4.4.1 Contents of files at the DF SoLSA level...........................................................................................129
4.4.1.1 EFSAI (SoLSA Access Indicator)..................................................................................................130
4.4.1.2 EFSLL (SoLSA LSA List).............................................................................................................130
4.4.1.3 LSA Descriptor files....................................................................................................................133
3GPP
Release 15 14 3GPP TS 31.102 V15.21.0 (2018-0610)
4.4.2 Contents of files at the DF PHONEBOOK level..............................................................................134

4.4.2.1 EFPBR (Phone Book Reference file).............................................................................................135
4.4.2.2 EFIAP (Index Administration Phone book)...................................................................................137
4.4.2.3 EFADN (Abbreviated dialling numbers)........................................................................................137
4.4.2.4 EFEXT1 (Extension1).....................................................................................................................140
4.4.2.5 EFPBC (Phone Book Control)........................................................................................................142
4.4.2.6 EFGRP (Grouping file)...................................................................................................................143
4.4.2.7 EFAAS (Additional number Alpha String).....................................................................................143
4.4.2.8 EFGAS (Grouping information Alpha String)................................................................................144
4.4.2.9 EFANR (Additional Number).........................................................................................................144
4.4.2.10 EFSNE (Second Name Entry).........................................................................................................146
4.4.2.11 EFCCP1 (Capability Configuration Parameters 1)..........................................................................147
4.4.2.12 Phone Book Synchronisation.......................................................................................................147
4.4.2.12.1 EFUID (Unique Identifier).......................................................................................................147
4.4.2.12.2 EFPSC (Phone book Synchronisation Counter).......................................................................148
4.4.2.12.3 EFCC (Change Counter)..........................................................................................................149
4.4.2.12.4 EFPUID (Previous Unique Identifier).......................................................................................150
4.4.2.13 EFEMAIL (e-mail address)..............................................................................................................150
4.4.2.14 Phonebook restrictions................................................................................................................151
4.4.2.15 EFPURI (Phonebook URIs)............................................................................................................151
4.4.3 Contents of files at the DF GSM-ACCESS level (Files required for GSM Access).......................152
4.4.3.1 EFKc (GSM Ciphering key Kc)....................................................................................................153
4.4.3.2 EFKcGPRS (GPRS Ciphering key KcGPRS)...................................................................................153
4.4.3.3 Void.............................................................................................................................................154
4.4.3.4 EFCPBCCH (CPBCCH Information)................................................................................................154
4.4.3.5 EFInvScan (Investigation Scan)........................................................................................................155
4.4.4 Contents of files at the MexE level.............................................................................................155
4.4.4.1 EFMexE-ST (MexE Service table)...............................................................................................156
4.4.4.2 EFORPK (Operator Root Public Key).......................................................................................156
4.4.4.3 EFARPK (Administrator Root Public Key)...............................................................................158
4.4.4.4 EFTPRPK (Third Party Root Public Key)..................................................................................159
4.4.4.5 EFTKCDF (Trusted Key/Certificates Data Files).......................................................................159
4.4.5 Contents of files at the DF WLAN level...........................................................................................160
4.4.5.1 EFPseudo (Pseudonym)....................................................................................................................160
4.4.5.2 EFUPLMNWLAN (User controlled PLMN selector for I-WLAN Access)..........................................161
4.4.5.3 EFOPLMNWLAN (Operator controlled PLMN selector for I-WLAN Access).........................................161
4.4.5.4 EFUWSIDL (User controlled WLAN Specific Identifier List).........................................................162
4.4.5.5 EFOWSIDL (Operator controlled WLAN Specific IdentifierList)...................................................163
4.4.5.6 EFWRI (WLAN Reauthentication Identity)...................................................................................163
4.4.5.7 EFHWSIDL (Home I-WLAN Specific Identifier List).....................................................................164
4.4.5.8 EFWEHPLMNPI (I-WLAN Equivalent HPLMN Presentation Indication).........................................165
4.4.5.9 EFWHPI (I-WLAN HPLMN Priority Indication)...........................................................................165
4.4.5.10 EFWLRPLMN (I-WLAN Last Registered PLMN).............................................................................166
4.4.5.11 EFHPLMNDAI (HPLMN Direct Access Indicator)............................................................................166
4.4.6 Contents of files at the DF HNB level..............................................................................................167
4.4.6.1 Introduction.................................................................................................................................167
4.4.6.2 EFACSGL (Allowed CSG Lists)......................................................................................................167
4.4.6.3 EFCSGT (CSG Type)......................................................................................................................170
4.4.6.4 EFHNBN (Home NodeB Name)......................................................................................................172
4.4.6.5 EFOCSGL (Operator CSG Lists)......................................................................................................172
4.4.6.6 EFOCSGT (Operator CSG Type).....................................................................................................174
4.4.6.7 EFOHNBN (Operator Home NodeB Name).....................................................................................175
4.4.7 Void...................................................................................................................................................175
4.4.8 Contents of files at the DF ProSe level.............................................................................................175
4.4.8.1 Introduction.................................................................................................................................175
4.4.8.2 EFPROSE_MON (ProSe Monitoring Parameters)................................................................................175
4.4.8.3 EFPROSE_ANN (ProSe Announcing Parameters)..............................................................................176
4.4.8.4 EFPROSEFUNC (HPLMN ProSe Function)........................................................................................177
4.4.8.5 EFPROSE_RADIO_COM (ProSe Direct Communication Radio Parameters)..........................................178
4.4.8.6 EFPROSE_RADIO_MON (ProSe Direct Discovery Monitoring Radio Parameters)................................180
4.4.8.7 EFPROSE_RADIO_ANN (ProSe Direct Discovery Announcing Radio Parameters)...............................181
3GPP
Release 15 15 3GPP TS 31.102 V15.21.0 (2018-0610)
4.4.8.8 EFPROSE_POLICY (ProSe Policy Parameters).....................................................................................182

4.4.8.9 EFPROSE_PLMN (ProSe PLMN Parameters)......................................................................................184
4.4.8.10 EFPROSE_GC (ProSe Group Counter)...............................................................................................185
4.4.8.11 EFPST (ProSe Service Table)........................................................................................................187
4.4.8.12 EFPROSE_UIRC (ProSe UsageInformationReportingConfiguration).................................................187
4.4.8.12 EFPROSE_GM_DISCOVERY (ProSe Group Member Discovery Parameters)...........................................191
4.4.8.13 EFPROSE_RELAY (ProSe Relay Parameters)......................................................................................192
4.4.8.14 EFPROSE_RELAY_DISCOVERY (ProSe Relay Discovery Parameters)......................................................193
4.4.9 Contents of files at the DF ACDC level............................................................................................196
4.4.9.1 Introduction.................................................................................................................................196
4.4.9.2 EFACDC_LIST (ACDC List)..............................................................................................................196
4.4.9.3 EFACDC_OS_CONFIG (ACDC OS configuration).................................................................................197
4.4.10 Contents of files at the DF TV level.................................................................................................198
4.4.10.1 Introduction.................................................................................................................................198
4.4.10.2 EFTVUSD (TV User Service Description).......................................................................................198
4.5 Contents of Efs at the TELECOM level.................................................................................................199
4.5.1 EFADN (Abbreviated dialling numbers)..............................................................................................199
4.5.2 EFEXT1 (Extension1)...........................................................................................................................199
4.5.3 EFECCP (Extended Capability Configuration Parameter)...................................................................199
4.5.4 EFSUME (SetUpMenu Elements).........................................................................................................200
4.5.5 EFARR (Access Rule Reference).........................................................................................................200
4.5.6 EFICE_DN (In Case of Emergency – Dialling Number).......................................................................200
4.5.7 EFICE_FF (In Case of Emergency – Free Format)................................................................................201
4.5.8 EFRMA (Remote Management Actions)..............................................................................................201
4.5.9 EFPSISMSC (Public Service Identity of the SM-SC).............................................................................202
4.6 Contents of DFs at the TELECOM level................................................................................................202
4.6.0 List of DFs at the TELECOM level..................................................................................................202
4.6.1 Contents of files at the DFGRAPHICS level............................................................................................202
4.6.1.1 EFIMG (Image)..............................................................................................................................202
4.6.1.2 EFIIDF (Image Instance Data Files)...............................................................................................204
4.6.1.3 EFICE_graphics (In Case of Emergency – Graphics).................................................................204
4.6.1.4 Void.............................................................................................................................................205
4.6.1.5 Void.............................................................................................................................................205
4.6.2 Contents of files at the DFPHONEBOOK under the DFTELECOM.................................................................205
4.6.3 Contents of files at the DFMULTIMEDIA level.........................................................................................205
4.6.3.1 EFMML (Multimedia Messages List).............................................................................................205
4.6.3.2 EFMMDF (Multimedia Messages Data File)...................................................................................208
4.6.4 Contents of files at the DFMCPTT level................................................................................................209
4.6.4.1 EFMST (MCPTT Service Table)....................................................................................................209
4.6.4.2 EFMCPTT_ CONFIG (MCPTT configuration data)...............................................................................209
4.6.4.3 Void.............................................................................................................................................210
4.6.4.4 Void.............................................................................................................................................210
4.6.4.5 Void.............................................................................................................................................210
4.6.5 Contents of files at the DFV2X level...................................................................................................210
4.6.5.1 V2X configuration data related files...........................................................................................210
4.6.5.2 EFVST (V2X Service Table)..........................................................................................................211
4.6.5.3 EFV2X_CONFIG (V2X configuration data).........................................................................................211
4.7 Files of USIM.........................................................................................................................................213
5 Application protocol.....................................................................................................................217
5.1 USIM management procedures...............................................................................................................218
5.1.1 Initialisation.......................................................................................................................................218
5.1.1.1 USIM application selection.........................................................................................................218
5.1.1.2 USIM initialisation......................................................................................................................218
5.1.1.3 GSM related initialisation procedures.........................................................................................219
5.1.2 Session termination...........................................................................................................................219
5.1.2.1 3G session termination................................................................................................................219
5.1.2.1.1 GSM termination procedures.................................................................................................220
5.1.2.2 3G session reset...........................................................................................................................220
5.1.3 USIM application closure..................................................................................................................220
5.1.4 Emergency call codes........................................................................................................................220
3GPP
Release 15 16 3GPP TS 31.102 V15.21.0 (2018-0610)
5.1.5 Language indication..........................................................................................................................220

5.1.6 Administrative information request..................................................................................................220
5.1.7 USIM service table request...............................................................................................................221
5.1.8 Void...................................................................................................................................................221
5.1.9 UICC presence detection...................................................................................................................221
5.1.10 UICC interface in PSM.....................................................................................................................221
5.1.11 UICC interface during eDRX............................................................................................................221
5.2 USIM security related procedures..........................................................................................................222
5.2.1 Authentication algorithms computation............................................................................................222
5.2.2 IMSI request......................................................................................................................................222
5.2.3 Access control information request...................................................................................................222
5.2.4 Higher Priority PLMN search period request...................................................................................222
5.2.5 Location information.........................................................................................................................222
5.2.6 Cipher and Integrity key....................................................................................................................222
5.2.7 Forbidden PLMN..............................................................................................................................222
5.2.8 Void...................................................................................................................................................222
5.2.9 User Identity Request........................................................................................................................222
5.2.10 GSM Cipher key................................................................................................................................222
5.2.11 GPRS Cipher key..............................................................................................................................223
5.2.12 Initialisation value for Hyperframe number......................................................................................223
5.2.13 Maximum value of START...............................................................................................................223
5.2.14 HPLMN selector with Access Technology request..........................................................................223
5.2.15 Packet Switched Location information.............................................................................................223
5.2.16 Cipher and Integrity key for Packet Switched domain......................................................................223
5.2.17 LSA information...............................................................................................................................223
5.2.18 Voice Group Call Services................................................................................................................223
5.2.19 Voice Broadcast Services..................................................................................................................224
5.2.20 Generic Bootstrapping architecture (Bootstrap)................................................................................224
5.2.21 Generic Bootstrapping architecture (NAF Derivation).....................................................................224
5.2.22 MSK MIKEY Message Reception....................................................................................................224
5.2.23 MTK MIKEY Message Reception....................................................................................................224
5.2.24 Void...................................................................................................................................................224
5.2.25 EHPLMN request..............................................................................................................................224
5.2.26 Last RPLMN Selection Indication request........................................................................................224
5.2.29 Non Access Stratum Configuration...................................................................................................225
5.2.30 PWS Configuration...........................................................................................................................225
5.3 Subscription related procedures..............................................................................................................225
5.3.1 Phone book procedures.....................................................................................................................225
5.3.1.1 Initialisation.................................................................................................................................225
5.3.1.2 Creation/Deletion of information................................................................................................226
5.3.1.3 Hidden phone book entries..........................................................................................................226
5.3.2 Dialling numbers...............................................................................................................................226
5.3.3 Short messages..................................................................................................................................228
5.3.4 Advice of charge...............................................................................................................................228
5.3.5 Capability configuration parameters.................................................................................................229
5.3.6 User controlled PLMN selector with Access Technology................................................................229
5.3.7 Cell broadcast message identifier......................................................................................................229
5.3.10 Service provider name.......................................................................................................................229
5.3.11 Enhanced multi level precedence and pre-emption service..............................................................229
5.3.12 Cell broadcast message identifier ranges..........................................................................................229
5.3.13 Short message status report...............................................................................................................230
5.3.14 APN Control List..............................................................................................................................230
5.3.15 Depersonalisation Control Keys........................................................................................................230
5.3.16 Co-operative Network List................................................................................................................230
5.3.17 CPBCCH information.......................................................................................................................231
5.3.18 Investigation Scan.............................................................................................................................231
5.3.19 Enabled Services Table Request.......................................................................................................231
5.3.20 Operator controlled PLMN selector with Access Technology.........................................................231
5.3.21 HPLMN selector with Access Technology.......................................................................................231
3GPP
Release 15 17 3GPP TS 31.102 V15.21.0 (2018-0610)
5.3.22 Automatic Answer on eMLPP service..............................................................................................231

5.3.23 Network Parameter information........................................................................................................231
5.3.24 PLMN network name........................................................................................................................231
5.3.25 Operator PLMN List.........................................................................................................................231
5.3.26 Message Waiting Indication..............................................................................................................232
5.3.27 Call Forwarding Indication Status.....................................................................................................232
5.3.28 Service Provider Display Information...............................................................................................232
5.3.29 MMS Notifications............................................................................................................................232
5.3.30 MMS Issuer Connectivity Parameters...............................................................................................233
5.3.31 MMS User Preferences.....................................................................................................................233
5.3.32 MMS User Connectivity Parameters.................................................................................................233
5.3.33 Network's indication of alerting........................................................................................................233
5.3.34 Multimedia Messages Storage..........................................................................................................233
5.3.35 Equivalent HPLMN Presentation Indication request........................................................................234
5.3.36 NAF Key Centre Address request.....................................................................................................234
5.3.37 Service provider name Icon...............................................................................................................234
5.3.38 PLMN network name Icon................................................................................................................234
5.3.39 ICE Information request....................................................................................................................234
5.3.40 eCall Related Procedures..................................................................................................................234
5.3.40.1 eCall Only support.......................................................................................................................234
5.3.40.2 eCall and Normal call support.....................................................................................................235
5.3.40.3 Change of eCall mode.................................................................................................................235
5.3.41 SM-over-IP........................................................................................................................................236
5.3.42 UICC access to IMS..........................................................................................................................236
5.3.43 TV Configuration..............................................................................................................................236
5.3.44 3GPP PS Data Off related procedures...............................................................................................236
5.3.45 3GPP PS Data Off service list related procedures............................................................................236
5.3.46 EARFCN list for MTC/NB-IOT UEs...............................................................................................236
5.3.47 SUCI Calculation information procedure.........................................................................................236
5.3.48 SUCI Calculation by the USIM procedure.......................................................................................236
5.3.49 Steering of UE in VPLMN related procedures.................................................................................237
5.4 USAT related procedures........................................................................................................................237
5.4.1 Data Download via SMS-PP.............................................................................................................237
5.4.2 Image Request...................................................................................................................................237
5.4.3 Data Download via SMS-CB............................................................................................................237
5.4.4 Call Control by USIM.......................................................................................................................237
5.4.5 MO-SMS control by USIM...............................................................................................................237
5.4.6 Data Download via USSD and USSD application mode..................................................................237
5.4.7 Additional TERMINAL PROFILE after UICC activation...............................................................238
5.4.8 Terminal Applications.......................................................................................................................238
5.4.9 Call control on EPS PDN connection by USIM...............................................................................238
5.4.10 Communication Control for IMS by USIM......................................................................................238
5.4.11 USAT Facility Control......................................................................................................................238
5.4.12 Extended Terminal Applications.......................................................................................................238
5.4.13 USAT application pairing procedure................................................................................................238
5.4.14 Call control on PDU Session by USIM.............................................................................................239
5.5 MexE related procedures........................................................................................................................239
5.5.1 MexE ST...........................................................................................................................................239
5.5.2 Operator root public key...................................................................................................................239
5.5.3 Administrator root public key...........................................................................................................239
5.5.4 Third Party root public key(s)...........................................................................................................239
5.5.5 Trusted Key/Certificates Data Files..................................................................................................239
5.6 WLAN related procedures......................................................................................................................240
5.6.1 WLAN Selection related Procedures................................................................................................240
5.6.2 WLAN PLMN Selection related procedures....................................................................................240
5.6.3 WLAN access authentication related procedures..............................................................................240
5.6.4 WLAN access re-authentication related procedures.........................................................................240
5.7 Network Connectivity Parameters for UICC IP connections related procedures.............................240
5.8 H(e)NB related procedures.....................................................................................................................240
5.8.1 CSG Access Control procedures.......................................................................................................240
5.8.2 CSG Type related procedures...........................................................................................................241
3GPP
Release 15 18 3GPP TS 31.102 V15.21.0 (2018-0610)
5.8.3 HNB name display related procedures..............................................................................................241

5.9 ProSe related procedures.........................................................................................................................242
5.9.1 ProSe Direct Discovery Provisioning parameters.............................................................................242
5.9.2 HPLMN ProSe Function address......................................................................................................242
5.9.4 ProSe direct discovery related Procedures........................................................................................242
5.9.7 ProSe Group Counter related Procedures..........................................................................................242
5.9.8 ProSe Usage Information Reporting Configuration related Procedures...........................................243
5.9.9 ProSe Group Member Discovery related Procedures.......................................................................243
5.9.10 ProSe Relay related Procedures........................................................................................................243
5.10 ePDG Selection related procedures........................................................................................................243
5.10.1 Home ePDG Identifier......................................................................................................................243
5.10.2 ePDG Selection Information.............................................................................................................243
5.10.3 ePDG configuration information configured but empty...................................................................243
5.11 ACDC related procedures.......................................................................................................................244
5.11.1 ACDC Configuration........................................................................................................................244
5.12 MCPTT related procedures.....................................................................................................................244
5.12.1 MCPTT configuration.......................................................................................................................244
5.12.2 Void...................................................................................................................................................244
5.12.3 Void...................................................................................................................................................244
5.12.4 Void...................................................................................................................................................244
5.13 ePDG Selection for Emergency Services related procedures.................................................................244
5.13.1 Emergency ePDG Identifier..............................................................................................................244
5.13.2 ePDG Selection Information for Emergency Services......................................................................244
5.13.3 ePDG configuration information for Emergency Services configured but empty............................245
5.13.4 From Preferred related procedures....................................................................................................245
5.13.5 IMS Configuration Data related procedures.....................................................................................245
5.13.6 XCAP Configuration Data related procedures..................................................................................245
5.14 V2X related procedures..........................................................................................................................245
5.14.1 V2X configuration.............................................................................................................................245
5.15 UAC Access Identities related procedures.............................................................................................245
5.15.1 UAC Access Identities Configuration...............................................................................................245
6 Security features............................................................................................................................245
6.1 Authentication and key agreement procedure.........................................................................................246
6.2 Cryptographic Functions.........................................................................................................................246
6.3 GSM Conversion Functions....................................................................................................................246
6.4 User verification and file access conditions............................................................................................247
7 USIM Commands.........................................................................................................................247
7.1 AUTHENTICATE..................................................................................................................................247
7.1.1.1 3G security context......................................................................................................................248
7.1.1.2 GSM security context..................................................................................................................248
7.1.1.6 MBMS security context (MSK Update Mode)............................................................................250
7.1.1.7 Void.............................................................................................................................................252
7.1.1.8 MBMS security context (MTK Generation Mode).....................................................................252
7.1.1.9 MBMS security context (MSK Deletion Mode).........................................................................253
7.1.1.10 MBMS security context (MUK Deletion Mode).........................................................................253
7.1.1.11 Local Key Establishment security context (Key Derivation mode)............................................253
7.1.1.12 Local Key Establishment security context (Key Availability Check mode)...............................254
7.1.2.1 GSM/3G security context............................................................................................................256
7.1.2.5 MBMS security context (All Modes)..........................................................................................258
3GPP
Release 15 19 3GPP TS 31.102 V15.21.0 (2018-0610)
7.1.2.6 Local Key Establishment security context (All Modes)..............................................................259

7.1.2.6.1 Local Key Establishment security context (Key Derivation mode)......................................259
7.1.2.6.2 Local Key Establishment security context (Key Availability Check mode).........................261
7.2 Void.........................................................................................................................................................262
7.3 Status Conditions Returned by the USIM...............................................................................................262
7.3.1 Security management........................................................................................................................262
7.3.2 Status Words of the Commands........................................................................................................263
7.4 Optional commands................................................................................................................................264
7.5 GET IDENTITY.....................................................................................................................................264
7.5.1.1 SUCI context...............................................................................................................................264
7.a.2 Command parameters and data.........................................................................................................265
7.5.2.1 SUCI context...............................................................................................................................265
8 Void...............................................................................................................................................266
Annex A (informative): EF changes via Data Download or USAT applications............................267
Annex B (normative): Image Coding Schemes...................................................................................271
B.1 Basic Image Coding Scheme........................................................................................................271
B.2 Colour Image Coding Scheme......................................................................................................272
B.3 Colour Image Coding Scheme with Transparency.......................................................................273
Annex C (informative): Structure of the Network parameters TLV objects..................................274
Annex D (informative): Tags defined in 31.102..................................................................................275
Annex E (informative): Suggested contents of the EFs at pre-personalization...............................280
Annex F (informative): Examples of coding of LSA Descriptor files for SoLSA............................284
Annex G (informative): Phonebook Example....................................................................................285
Annex H (normative): List of SFI Values...........................................................................................289
H.1 List of SFI Values at the USIM ADF Level.................................................................................289
H.2 List of SFI Values at the DF GSM-ACCESS Level.....................................................................289
H.3 List of SFI Values at the DF WLAN Level..................................................................................290
H.4 List of SFI Values at the DF HNB Level......................................................................................290
H.5 List of SFI Values at the DF ProSe Level.....................................................................................290
H.6 List of SFI Values at the DF ACDC Level...................................................................................290
H.7 List of SFI Values at the DF MCPTT Level.................................................................................291
H.8 List of SFI Values at the DF V2X Level......................................................................................291
Annex I (informative): USIM Application Session Activation/Termination...................................292
Annex J (informative): Example of MMS coding..............................................................................293
J.1 Coding example for MMS User Preferences..........................................................................................293
J.2 Coding Example for MMS Issuer/User Connectivity Parameters..........................................................293
Annex K (informative): Examples of VService_Id coding................................................................295

Annex L (normative): USIM-INI and USIM-RN for Relay Nodes..................................................296
L.1 Introduction.............................................................................................................................................296
L.2 Application selection procedure.............................................................................................................296
L.3 Secure channel operation........................................................................................................................297
L.4 Support of commands.............................................................................................................................297
3GPP
Release 15 20 3GPP TS 31.102 V15.21.0 (2018-0610)
L.5 Storage of certificates.............................................................................................................................297

L.6 Relay Node files support.........................................................................................................................297
L.6.1 USIM-INI Files.................................................................................................................................297
L.6.1.1 EFCERT (UICC Certificate)............................................................................................................297
L.6.2 USIM-RN Files.................................................................................................................................298
L.6.2.1 eFRNid (Relay Node identifier)......................................................................................................298
L.6.2.2 EFSCCmax (maximum value of Secure Channel Counter)..............................................................299
Annex M (normative): USIM application dedicated for IOPS.........................................................300

M.1 Introduction.............................................................................................................................................300
M.2 Features of the USIM dedicated for IOPS..............................................................................................300
M.3 Selection mechanisms.......................................................................................................................300
Annex N (informative): Change history..................................................................................................301
3GPP
Release 15 21 3GPP TS 31.102 V15.21.0 (2018-0610)
Foreword
This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
Y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
Z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
The present document defines the Universal Subscriber Identity Module (USIM) application. This application resides
on the UICC, an IC card specified in TS 31.101 [11]. In particular, TS 31.101 [11] specifies the application independent
properties of the UICC/terminal interface such as the physical characteristics and the logical structure.
TS 31.101 [11] is one of the core documents for this specification and is therefore referenced in many places in the
present document.
3GPP
Release 15 22 3GPP TS 31.102 V15.21.0 (2018-0610)
1 Scope
The present document defines the USIM application for 3G telecom network operation.
The present document specifies:
- specific command parameters;
- file structures;
- contents of Efs (Elementary Files);
- security functions;
- application protocol to be used on the interface between UICC (USIM) and ME.
This is to ensure interoperability between a USIM and an ME independently of the respective manufacturer, card issuer
or operator.
The present document does not define any aspects related to the administrative management phase of the USIM. Any
internal technical realisation of either the USIM or the ME is only specified where these are reflected over the interface.
The present document does not specify any of the security algorithms which may be used.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
 References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
 For a specific reference, subsequent revisions do not apply.
 For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TS 21.111: "USIM and IC Card Requirements".
[2] 3GPP TS 22.011: "Service accessibility".
[3] 3GPP TS 22.024: "Description of Charge Advice Information (CAI)".
[4] 3GPP TS 22.030: "Man-Machine Interface (MMI) of the User Equipment (UE)".
[5] 3GPP TS 23.038: "Alphabets and language".
[6] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".
[7] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[8] 3GPP TS 22.067: "enhanced Multi Level Precedence and Pre-emption service (eMLPP) -
Stage 1".
[9] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage
3".
[10] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio
interface".
[11] 3GPP TS 31.101: "UICC-Terminal Interface, Physical and Logical Characteristics".
[12] 3GPP TS 31.111: "USIM Application Toolkit (USAT)".
3GPP
Release 15 23 3GPP TS 31.102 V15.21.0 (2018-0610)
[13] 3GPP TS 33.102: "3GPP Security; Security Architecture".
[14] 3GPP TS 33.103: "3GPP Security; Integration Guidelines".
[15] 3GPP TS 22.086: "Advice of charge (AoC) Supplementary Services - Stage 1".
[16] 3GPP TS 23.041: "Technical realization of Cell Broadcast (CB)".
[17] 3GPP TS 02.07: "Mobile Stations (MS) features".
[18] 3GPP TS 51.011 Release 4: "Specification of the Subscriber Identity Module – Mobile Equipment
(SIM – ME) interface".
[19] ISO 639 (1988): "Code for the representation of names of languages".
[20] ISO/IEC 7816-4: "Integrated circuit cards, Part 4: Organization, security and commands for
interchange".
[21] Void.
[22] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
[23] 3GPP TS 23.073: "Support of Localised Service Area (SoLSA); Stage 2".
[24] 3GPP TS 22.101: "Service aspects; service principles".
[25] 3GPP TS 23.003: "Numbering, Addressing and Identification".
[26] Void.
[27] 3GPP TS 22.022: "Personalisation of Mobile Equipment (ME); Mobile functionality

specification".
[28] 3GPP TS 44.018 "Mobile Interface Layer3 Specification, Radio Resource control protocol".
[29] 3GPP TS 23.022: "Functions related to Mobile Station (MS) in idle mode and group receive
mode".
[30] 3GPP TS 23.057: "Mobile Execution Environment (MexE);Functional description; Stage 2".
[31] 3GPP TS 23.122: "NAS Functions related to Mobile Station (MS) in idle mode".
[32] Void.
[33] 3GPP TS 25.101: "UE Radio Transmission and Reception (FDD)".
[34] 3GPP TS 45.005: "Radio Transmission and Reception".
[35] ISO/IEC 8825-1 (2008): "Information technology – ASN.1 encoding rules : Specification of Basic
Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules
(DER)".
[36] 3GPP TS 23.097: "Multiple Subscriber Profile (MSP)".
[37] Void.
[38] 3GPP TS 23.140 Release 6: "Multimedia Messaging Service (MMS); Functional description; stage
2".
[39] ETSI TS 102 222 V7.1.0: "Administrative commands for telecommunications applications".
[40] 3GPP TS 24.234 Release 12: "3GPP System to WLAN Interworking; UE to Network
protocols;Stage 3".
[41] 3GPP TS 33.234 Release 12: "3G Security; Wireless Local Area Network (WLAN) interworking
security".
3GPP
Release 15 24 3GPP TS 31.102 V15.21.0 (2018-0610)
[42] 3GPP TS 33.220: "Generic Authentication Architecture (GAA); Generic bootstrapping

architecture".
[43] 3GPP TS 33.246: "Security of Multimedia Broadcast/Multicast Service".
[44] 3GPP TS 43.020: "Technical Specification Group Services and system Aspects; Security related
network functions"
[45] 3GPP2 X.S0016-000-A v1.0: "3GPP2 Multimedia Messaging System MMS Specification
Overview, Revision A"
[46] 3GPP TS 43.068: "Technical Specification Group Core Network; Voice Group Call Service
(VGCS); Stage 2".
[47] 3GPP TS 33.110: "Key establishment between a Universal Integrated Circuit Card (UICC) and a
terminal".
[48] IETF RFC 3629 (2003): "UTF-8, a transformation format of ISO 10646".
[49] Open Mobile Alliance; OMA-TS-BCAST_SvcCntProtection

URL: http://www.openmobilealliance.org/
[50] ETSI TS TS 102 483 V8.1.0: "UICC-Terminal interface; Internet Protocol connectivity between
UICC and Terminal".
[51] 3GPP TS 24.301: "Technical Specification Group Core Network and Terminals; Non-Access-
Stratum (NAS) protocol for Evolved Packet Systems (EPS): Stage 3".
[52] 3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture".
[53] 3GPP2 C.S0074-A v1.0: "UICC-Terminal Interface Physical and Logical Characteristics for
cdma2000 Spread Spectrum Systems"
[54] 3GPP TS 22.220: "Service requirements for Home NodeBs and Home eNodeBs ".
[55] 3GPP TS 24.341: "Support of SMS over IP networks; Stage 3"
[56] IETF RFC 3261: "SIP: Session Initiation Protocol".
[57] IETF RFC 3629 (2003): "UTF-8, a transformation format of ISO 10646".
[58] 3GPP TS 24.285: "Allowed Closed Subscriber Group (CSG) list; Management Object (MO)"
[59] OMA Smartcard-Web-Server Approved Version 1.1 - 12 May 2009

(OMA-TS-Smartcard_Web_Server-V1_1-20090512-A).[60] ISO/IEC 15948:2003:
"Information technology - Computer graphics and image processing - Portable Network Graphics
(PNG): Functional specification".
[61] IETF RFC 2046: "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types".
NOTE: Available from http://www.ietf.org/rfc/rfc2046.txt.
[62] ETSI TS 101 220 : "Smart Cards; ETSI numbering system for telecommunication application
providers".
[63] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP)
and Session Description Protocol (SDP); Stage 3"
[64] 3GPP TS 31.103: "Characteristics of the IP Multimedia Services Identity Module (ISIM)
application".
[65] 3GPP TS 24.368: "Non-Access Stratum (NAS) configuration Management Object (MO)".
[66] ETSI TS 102 484 V10.1.0: ''Smart Cards; Secure channel between a UICC and end-point
terminal"
3GPP
Release 15 25 3GPP TS 31.102 V15.21.0 (2018-0610)
[67] ISO/IEC 7816-15:2004: "Identification cards -- Integrated circuit cards -- Part 15: Cryptographic
information application"
[68] 3GPP TS 22.268: "Public Warning System (PWS) Requirements".
[69] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal
Terrestrial Radio Access Network (E-UTRAN) access".
[70] 3GPP TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to Proximity-services

(ProSe) Function Protocol aspects; Stage 3".
[71] 3GPP TS 24.333: "Proximity-services (ProSe) Management Objects (MO)"
[72] 3GPP TS 33.303: "Proximity-based Services (ProSe); Security aspects"
[73] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2"
[74] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource
Control (RRC); Protocol specification"
[75] 3GPP TS 23.032: " Technical Specification Group Services and System Aspects; Universal
Geographical Area Description (GAD)"
[76] 3GPP TS 33.187: "Security aspects of Machine-Type Communications (MTC) and other mobile
data applications communications enhancements"
[77] 3GPP TS 32.277: "Proximity-based Services (ProSe) charging"
[78] 3GPP TS 23.682: "Technical Specification Group Services and System Aspects; Architecture
enhancements to facilitate communications with packet data networks and applications"
[79] 3GPP TS 24.302: "Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access
networks".
[80] IETF RFC 4122: "A Universally Unique IDentifier (UUID) URN Namespace".
[81] 3GPP TS 24.105: "Application specific Congestion control for Data Communication (ACDC)
Management Object (MO)".
[82] Void
[83] Void
[84] GSMA: "IMEI Allocation and Approval Process Version 9.0"
[85] 3GPP TS 36.306: "Technical Specification Group Radio Access Network; Evolved Universal
Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities"
[86] 3GPP TS 24.607: "Originating Identification Presentation (OIP) and Originating Identification
Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol
specification"
[87] 3GPP TS 24.417: "Management Object (MO) for Originating Identification Presentation (OIP)
and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN)
subsystem; Stage 3".
[88] 3GPP TS 24.167: "3GPP IMS Management Object (MO); Stage 3".
[89] 3GPP TS 24.483: "Mission Critical Services(MCS) Management Object (MO)".
[90] 3GPP TS 23.379: "Functional architecture and information flows to support mission critical push
to talk (MCPTT); Stage 2".void
[91] 3GPP TS 24.117: "TV service configuration Management Object (MO)"
[92] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE)
radio transmission and reception".
3GPP
Release 15 26 3GPP TS 31.102 V15.21.0 (2018-0610)
[93] 3GPP TS 24.424: "Management Object (MO) for Extensible Markup Language (XML)
Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary
Services (SS)".
[94] 3GPP TS 24.391: "Unstructured Supplementary Service Data (USSD) using IP Multimedia (IM)
Core Network (CN) subsystem (IMS) Management Object (MO)".
[95] 3GPP TS 24.275: "Management Object (MO) for basic communication part of IMS multimedia
telephony (MMTEL) communication service".
[96] 3GPP TS 24.368: "Non-Access Stratum (NAS) configuration Management Object (MO)".
[97] 3GPP TS 24.385: "V2X services Management Object (MO)".
[98] 3GPP TS 24.386: "User Equipment (UE) to V2X control function; protocol aspects ".
[99] 3GPP TS 26.346: " Technical Specification Group Services and System Aspects; Multimedia
Broadcast/Multicast Service (MBMS); Protocols and codecs"[100] OMA-DDS-DM_ConnMO-
V1_0-20081107-A: " Standardized Connectivity Management Objects".
[101] 3GPP TS 24.424: "Management Object (MO) for Extensible Markup Language (XML)
Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary
Services (SS)".
[100] OMA-DDS-DM_ConnMO-V1_0-20081107-A: " Standardized Connectivity Management

Objects".
[102] 3GPP TS 24.623: "Extensible Markup Language (XML) Configuration Access Protocol (XCAP)
over the Ut interface for Manipulating Supplementary Services".
[103] OMA OMA-TS-XDM_Core-V1_1-20080627-A: "XML Document Management (XDM)

Specification".
[104] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[105] 3GPP TS 33.501: "Security architecture and procedures for 5G System".
[106] 3GPP TS 22.261: "Service requirements for the 5G system; Stage 1".
3 Definitions, symbols, abbreviations and coding

conventions
3.1 Definitions
For the purposes of the present document, the following definition applies.
ADM: access condition to an EF which is under the control of the authority which creates this file.
Allocation of these levels and the respective requirements for their fulfilment are the responsibility of the
appropriate administrative authority
The definition of access condition ADM does not preclude the administrative authority from using ALW, PIN,
PIN2 and NEV if required.
A terminal does not need to evaluate access conditions indicated as ADM in the present document.
PIN/ADM: A terminal is required to evaluate the access condition and verify it in order to access the EF if the access
condition is set to PIN or PIN2.
3GPP
Release 15 27 3GPP TS 31.102 V15.21.0 (2018-0610)
EHPLMN: represents the Equivalent HPLMNs for network selection purposes. The behaviour of EHPLMNs is defined
in TS 23.122 [31].
3.2 Symbols
For the purposes of the present document, the following symbols apply:
|| Concatenation
 Exclusive OR
f1 Message authentication function used to compute MAC
f1* A message authentication code (MAC) function with the property that no valuable information can
be inferred from the function values of f1* about those of f1, ..., f5 and vice versa
f2 Message authentication function used to compute RES and XRES
f3 Key generating function used to compute CK
f4 Key generating function used to compute IK
f5 Key generating function used to compute AK
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
3GPP 3rd Generation Partnership Project

5GCN 5G Core Network
AC Access Condition
ACDC Application specific Congestion control for Data Communication
ACL APN Control List
ADF Application Dedicated File
AID Application Identifier
AK Anonymity key
ALW ALWays
AMF Authentication Management Field
AoC Advice of Charge
APN Access Point Name
ASME Access Security Management Entity
ASN.1 Abstract Syntax Notation One
AuC Authentication Centre
AUTN Authentication token
BDN Barred Dialling Number
BER-TLV Basic Encoding Rule - TLV
B-TID Bootstrapping Transaction Identifier
CCP Capability Configuration Parameter
CK Cipher key
CLI Calling Line Identifier
CNL Co-operative Network List
CPBCCH COMPACT Packet BCCH
CS Circuit switched
DCK Depersonalisation Control Keys
DF Dedicated File
DO Data Object
EC-GSM-IoT Extended coverage in GSM for IoT
DUCK Discovery User Confidentiality Key
DUIK Discovery User Integrity Key
DUSK Discovery User Scrambling Key
eDRX Extended Discontinuous Reception
EARFCN Evolved Absolute Radio Frequency Channel Number
EF Elementary File
EPC Evolved Packet Core
ePDG Evolved Packet Data Gateway
EPS Evolved Packet System
FCP File Control Parameters
FFS For Further Study
3GPP
Release 15 28 3GPP TS 31.102 V15.21.0 (2018-0610)
FQDN Full Qualified Domain Name

GSM Global System for Mobile communications
HE Home Environment
HNB Home NodeB
HeNB Home eNodeB
IARI IMS Application Reference Identifier
ICC Integrated Circuit Card
ICE In Case of Emergency
ICI Incoming Call Information
ICT Incoming Call Timer
ID Identifier
Idi Identity of the initiator
Idr Identity of the responder
IEI Information Element Identifier
IK Integrity key
IMSI International Mobile Subscriber Identity
K USIM Individual key
KC Cryptographic key used by the cipher A5
KSI Key Set Identifier
LI Language Indication
LSB Least Significant Bit
MAC Message authentication code
MAC-A MAC used for authentication and key agreement
MAC-I MAC used for data integrity of signalling messages
MBMS Multimedia Broadcast/Multicast Service
MCC Mobile Country Code
MCData Mission Critical Data
MCPTT Mission Critical Push To Talk
MCS Mission Critical Services
MCVideo Mission Critical Video
MexE Mobile Execution Environment
MF Master File
MGV-F MTK Generation and Validation Function
MIKEY Multimedia Internet KEYing
MM Multimedia Message
MMI Man Machine Interface
MMS Multimedia Messaging Service
MMSS MultiMode System Selection
MNC Mobile Network Code
MODE Indication packet switched/circuit switched mode
MSB Most Significant Bit
MSK MBMS Service Key
MTC Machine Type Communications
MTK MBMS Traffic Key
MUK MBMS User Key
NB-IoT Narrowband IoT
NEV NEVer
ngKSI Key Set Identifier in 5G
NG-RAN Next Generation Radio Access Network
NPI Numbering Plan Identifier
OCI Outgoing Call Information
OCT Outgoing Call Timer
PBID Phonebook Identifier
PGK ProSe Group Key
PIN Personal Identification Number
PL Preferred Languages
PS Packet switched
PSDK Public Safety Discovery Key
PS_DO PIN Status Data Object
PSM Power Saving Mode
PTK ProSe Traffic Key
3GPP
Release 15 29 3GPP TS 31.102 V15.21.0 (2018-0610)
RAND Random challenge

RANDMS Random challenge stored in the USIM
RES User response
RFU Reserved for Future Use
RST Reset
SDN Service dialling number
SE Security Environment
SEQp Sequence number for MGV-F stored in the USIM
SFI Short EF Identifier
SGSN Serving GPRS Support Node
SN Serving Network
SQN Sequence number
SRES Signed RESponse calculated by a USIM
SUCI Subscription Concealed Identifier
SUPI Subscription Permanent Identifier
SW Status Word
TLV Tag Length Value
TMGI Temporary Mobile Group Identity
TV Television
UAC Unified Access Control
USAT USIM Application Toolkit
USD User Service Description
USIM Universal Subscriber Identity Module
V2X Vehicle-to-Everything
VLR Visitor Location Register
WLAN Wireless Local Area Network
WSID WLAN Specific Identifier
XRES Expected user RESponse
3.4 Coding Conventions

The following coding conventions apply to the present document.
All lengths are presented in bytes, unless otherwise stated. Each byte is represented by bits b8 to b1, where b8 is the
most significant bit (MSB) and b1 is the least significant bit (LSB). In each representation, the leftmost bit is the MSB.
The coding of Data Objects in the present document is according to TS 31.101 [11].
'XX': Single quotes indicate hexadecimal values. Valid elements for hexadecimal values are the numbers
'0' to '9' and 'A' to 'F'.
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 EF ADN 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 figures 4.1 and 4.2.
3GPP
Release 15 30 3GPP TS 31.102 V15.21.0 (2018-0610)
4.1 Contents of the EFs at the MF level

The EFs at the Master File (MF) level are specified in TS 31.101 [11].
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 [5]) 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 [5]) to the language coding as defined in ISO 639 [19] if it is necessary to check the language
coding in EFPL.
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.
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 [5]) 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 [5]) to the language coding as defined in ISO 639 [19] if it is necessary to check the language
coding in EFPL.
Identifier: '6F 05' Structure: transparent Optional

SFI: '02'
File size: 2n bytes, (n ≥ 1) Update activity: low
Access Conditions:
READ ALW
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM
Bytes Description M/O Length

1 to 2 1st language code (highest priority). M 2 bytes
3 to 4 2nd language code O 2 bytes
2n-1 to 2n Nth language code (lowest priority). O 2 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 [5] with bit 8 set
to 0.
Unused language entries shall be set to 'FF FF'.
3GPP
Release 15 31 3GPP TS 31.102 V15.21.0 (2018-0610)
4.2.2 EFIMSI (IMSI)

This EF contains the International Mobile Subscriber Identity (IMSI).
Identifier: '6F07' Structure: transparent Mandatory

SFI: '07'
File size: 9 bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 Length of IMSI M 1 byte
2 to 9 IMSI M 8 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:
- according to TS 24.008 [9].
- 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
1
0
0
Parity
LSB of Digit 1
:
:
MSB of Digit 1
For the parity bit, see TS 24.008 [9].
Byte 3:
b8 b7 b6 B5 b4 b3 b2 b1
LSB of Digit 2
:
:
MSB of Digit 2
LSB of Digit 3
:
:
MSB of Digit 3
etc.
3GPP
Release 15 32 3GPP TS 31.102 V15.21.0 (2018-0610)
4.2.3 EFKeys (Ciphering and Integrity Keys)

This EF contains the ciphering key CK, the integrity key IK and the key set identifier KSI.

SFI: '08'
File size: 33 bytes Update activity: high
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 Key set identifier KSI M 1 byte
2 to 17 Ciphering key CK M 16 bytes
18 to 33 Integrity key IK M 16 bytes
- Key Set Identifier KSI.

Coding:
b8 b7 b6 b5 b4 b3 b2 b1
KSI
bits b4 to b8 are coded 0
- 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.
4.2.4 EFKeysPS (Ciphering and Integrity Keys for Packet Switched domain)
This EF contains the ciphering key CKPS, the integrity key IKPS and the key set identifier KSIPS for the packet
switched (PS) domain.

SFI: '09'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 Key set identifier KSIPS M 1 byte
2 to 17 Ciphering key CKPS M 16 bytes
18 to 33 Integrity key IKPS M 16 bytes
- Key Set Identifier KSIPS.

Coding:
b8 b7 b6 b5 b4 b3 b2 b1
KSIPS
3GPP
Release 15 33 3GPP TS 31.102 V15.21.0 (2018-0610)
- 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.
4.2.5 EFPLMNwAcT (User controlled PLMN selector with Access Technology)

If service n° 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 n th
record indicates the lowest. The EF also contains the Access Technologies for each PLMN in this list. (see
TS 23.122 [31])
Identifier: '6F60' Structure: transparent Optional

SFI: '0A'
File size: 5n (where n 8 bytes) Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 3 1st PLMN (highest priority) M 3 bytes
4 to 5 1st PLMN Access Technology Identifier M 2 bytes
6 to 8 2nd PLMN M 3 bytes
9 to 10 2nd PLMN Access Technology Identifier M 2 bytes
: :
36 to 38 8th PLMN M 3 bytes
39 to 40 8th PLMN Access Technology Identifier M 2 bytes
41 to 43 9th PLMN O 3 bytes
44 to 45 9th PLMN Access Technology Identifier O 2 bytes
: :
(5n-4) to (5n-2) Nth PLMN (lowest priority) O 3 bytes
(5n-1) to 5n Nth PLMN Access Technology Identifier O 2 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.
3GPP
Release 15 34 3GPP TS 31.102 V15.21.0 (2018-0610)
Byte5n-1:
b8 b7 b6 b5 b4 b3 b2 b1
RFU
RFU
RFU
NG-RAN
E-UTRAN in NB-S1 mode (see table below)
E-UTRAN in WB-S1 mode (see table below)
E-UTRAN (see table below)
UTRAN
NOTE: NG-RAN refers to E-UTRA or NR connected to 5GCN.

Coding of the E-UTRAN
b7 b6 b5 Description
0 x x E-UTRAN not selected
1 0 0 E-UTRAN in WB-S1 mode and NB-S1 mode
1 0 1 E-UTRAN in NB-S1 mode only
1 1 0 E-UTRAN in WB-S1 mode only
1 1 1 E-UTRAN in WB-S1 mode and NB-S1 mode
NOTE: E-UTRAN refers to E-UTRA connected to EPC.
Byte 5n:
b8 b7 b6 b5 b4 b3 b2 b1
RFU
RFU
GSM (see table below)
EC-GSM-IoT (see table below)
cdma2000 1xRTT
cdma2000 HRPD
GSM COMPACT
GSM (see table below)
Coding of the GSM
b8 b4 b3 Description
0 x x GSM and EC-GSM-IoT not selected
1 0 0 GSM and EC-GSM-IoT
1 0 1 GSM without EC-GSM-IoT
1 1 0 EC-GSM-IoT only
1 1 1 GSM and EC-GSM-IoT
4.2.6 EFHPPLMN (Higher Priority PLMN search period)

This EF contains the interval of time between searches for a higher priority PLMN (see 3GPP TS 23.122 [31]).

SFI: '12'
File size: 1 byte Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 Time interval M 1 byte
3GPP
Release 15 35 3GPP TS 31.102 V15.21.0 (2018-0610)
- Time interval.
Contents:
the time interval between two searches.
Coding:
For all UEs except those only supportingnot using any of the following at the time of starting the timer, or a
combination of: NB-IoT, GERAN EC-GSM-IoT and Category M1 of E-UTRAN enhanced-MTC as specified in 3GPP
TS 36.306 [85], 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 only supporting any of the following at the time of starting the timer, or a combination of,: NB-IoT,
GERAN EC-GSM-IoT and Category M1 of E-UTRAN enhanced-MTC as specified in 3GPP TS 36.306 [85], 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 3GPP
TS 23.122 [31].
NOTE: Care should be taken in the configuration of this EF, as the value stored can be interpreted in different
ways depending on the type of device used.
4.2.7 EFACMmax (ACM maximum value)

This EF contains the maximum value of the accumulated call meter.

Access Conditions:
READ PIN
UPDATE PIN/PIN2
(fixed during administrative management)
DEACTIVATE ADM
ACTIVATE ADM

1 to 3 Maximum value M 3 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:
3GPP
Release 15 36 3GPP TS 31.102 V15.21.0 (2018-0610)
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 [3], 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.
4.2.8 EFUST (USIM Service Table)

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.

SFI: '04'
File size: X bytes, (X ≥ 1) Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 Services n°1 to n°8 M 1 byte
2 Services n°9 to n°16 O 1 byte
etc.
X Services n°(8X-7) to n°(8X) O 1 byte
3GPP
Release 15 37 3GPP TS 31.102 V15.21.0 (2018-0610)
3GPP
Release 15 38 3GPP TS 31.102 V15.21.0 (2018-0610)
-Services
Contents: Service n°1: Local Phone Book
Service n°2: Fixed Dialling Numbers (FDN)
Service n°3: Extension 2
Service n°4: Service Dialling Numbers (SDN)
Service n°5: Extension3
Service n°6: Barred Dialling Numbers (BDN)
Service n°7: Extension4
Service n°8: Outgoing Call Information (OCI and OCT)
Service n°9: Incoming Call Information (ICI and ICT)
Service n°10: Short Message Storage (SMS)
Service n°11: Short Message Status Reports (SMSR)
Service n°12: Short Message Service Parameters (SMSP)
Service n°13: Advice of Charge (AoC)
Service n°14: Capability Configuration Parameters 2 (CCP2)
Service n°15: Cell Broadcast Message Identifier
Service n°16: Cell Broadcast Message Identifier Ranges
Service n°17: Group Identifier Level 1
Service n°18: Group Identifier Level 2
Service n°19: Service Provider Name
Service n°20: User controlled PLMN selector with Access Technology
Service n°21: MSISDN
Service n°22: Image (IMG)
Service n°23: Support of Localised Service Areas (SoLSA)
Service n°24: Enhanced Multi-Level Precedence and Pre-emption Service
Service n°25: Automatic Answer for eMLPP
Service n°26: RFU
Service n°27: GSM Access
Service n°28: Data download via SMS-PP
Service n°29: Data download via SMS-CB
Service n°30: Call Control by USIM
Service n°31: MO-SMS Control by USIM
Service n°32: RUN AT COMMAND command
Service n°33: shall be set to '1'
Service n°34: Enabled Services Table
Service n°35: APN Control List (ACL)
Service n°36: Depersonalisation Control Keys
Service n°37: Co-operative Network List
Service n°38: GSM security context
Service n°39: CPBCCH Information
Service n°40: Investigation Scan
Service n°41: MexE
Service n°42: Operator controlled PLMN selector with Access Technology
Service n°43: HPLMN selector with Access Technology
Service n°44: Extension 5
Service n°45: PLMN Network Name
Service n°46: Operator PLMN List
Service n°47: Mailbox Dialling Numbers
Service n°48: Message Waiting Indication Status
Service n°49: Call Forwarding Indication Status
Service n°50: Reserved and shall be ignored
Service n°51: Service Provider Display Information
Service n°52 Multimedia Messaging Service (MMS)
Service n°53 Extension 8
Service n°54 Call control on GPRS by USIM
Service n°55 MMS User Connectivity Parameters
Service n°56 Network's indication of alerting in the MS (NIA)
Service n°57 VGCS Group Identifier List (EFVGCS and EFVGCSS)
Service n°58 VBS Group Identifier List (EFVBS and EFVBSS)
Service n°59 Pseudonym
Service n°60 User Controlled PLMN selector for I-WLAN access
Service n°61 Operator Controlled PLMN selector for I-WLAN access
Service n°62 User controlled WSID list
Service n°63 Operator controlled WSID list
Service n°64 VGCS security
Service n°65 VBS security
Service n°66 WLAN Reauthentication Identity
Service n°67 Multimedia Messages Storage
Service n°68 Generic Bootstrapping Architecture (GBA)
3GPP
Release 15 39 3GPP TS 31.102 V15.21.0 (2018-0610)
Service n°69 MBMS security

Service n°70 Data download via USSD and USSD application mode
Service n°71 Equivalent HPLMN
Service n°72 Additional TERMINAL PROFILE after UICC activation
Service n°73 Equivalent HPLMN Presentation Indication
Service n°74 Last RPLMN Selection Indication
Service n°75 OMA BCAST Smart Card Profile
Service n°76 GBA-based Local Key Establishment Mechanism
Service n°77 Terminal Applications
Service n°78 Service Provider Name Icon
Service n°79 PLMN Network Name Icon
Service n°80 Connectivity Parameters for USIM IP connections
Service n°81 Home I-WLAN Specific Identifier List
Service n°82 I-WLAN Equivalent HPLMN Presentation Indication
Service n°83 I-WLAN HPLMN Priority Indication
Service n°84 I-WLAN Last Registered PLMN
Service n°85 EPS Mobility Management Information
Service n°86 Allowed CSG Lists and corresponding indications
Service n°87 Call control on EPS PDN connection by USIM
Service n°88 HPLMN Direct Access
Service n°89 eCall Data
Service n°90 Operator CSG Lists and corresponding indications
Service n°91 Support for SM-over-IP
Service n°92 Support of CSG Display Control
Service n°93 Communication Control for IMS by USIM
Service n°94 Extended Terminal Applications
Service n°95 Support of UICC access to IMS
Service n°96 Non-Access Stratum configuration by USIM
Service n°97 PWS configuration by USIM
Service n°98 RFU
Service n°99 URI support by UICC
Service n°100 Extended EARFCN support
Service n°101 ProSe
Service n°102 USAT Application Pairing
Service n°103 Media Type support
Service n°104 IMS call disconnection cause
Service n°105 URI support for MO SHORT MESSAGE CONTROL
Service n°106 ePDG configuration Information support
Service n°107 ePDG configuration Information configured
Service n°108 ACDC support
Service n°109 Mission Critical ServicesMCPTT
Service n°110 ePDG configuration Information for Emergency Service support
Service n°111 ePDG configuration Information for Emergency Service configured
Service n°112 eCall Data over IMS
Service n°113 URI support for SMS-PP DOWNLOAD as defined in
3GPP TS 31.111 [12]
Service n°114 From Preferred
Service n°115 IMS configuration data
Service n°116 TV configuration
Service n°117 3GPP PS Data Off
Service n°118 3GPP PS Data Off Service List
Service n°119 V2X
Service n°120 XCAP Configuration Data
Service n°121 EARFCN list for MTC/NB-IOT UEs
Service n°122 5GS Mobility Management Information
Service n°123 5G Security Parameters
Service n°124 Subscription identifier privacy support
Service n°125 SUCI calculation by the USIM
Service n°126 UAC Access Identities support
Service n° 127 Expect control plane-based Steering of Roaming information during
initial registrationSteering of UE in VPLMN
Service n°128 Call control on PDU Session by USIM
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 n°46 can only be declared "available" if service n°45 is declared "available".
3GPP
Release 15 40 3GPP TS 31.102 V15.21.0 (2018-0610)
Service n°95, n°99 and n°115 shall not be declared "available" if an ISIM application is present on the UICC.
Service n°125 shall only be taken into account if Service n°xxx is declared "available". If Service n°124 and Service
n°125 are declared "available", the "SUCI calculation is to be performed by the USIM". If Service n°124 is declared
"available" and Service n°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 EFEST.
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 n°1
Service n°2
Service n°3
Service n°4
Service n°5
Service n°6
Service n°7
Service n°8
Second byte:
b8 b7 b6 B5 B4 b3 b2 b1
Service n°9
Service n°10
Service n°11
Service n°12
Service n°13
Service n°14
Service n°15
Service n°16
etc.
4.2.9 EFACM (Accumulated Call Meter)

This EF contains the total number of units for both the current call and the preceding calls.
NOTE: The information may be used to provide an indication to the user for advice or as a basis for the
calculation of the monetary cost of calls (see TS 22.086 [15]).
3GPP
Release 15 41 3GPP TS 31.102 V15.21.0 (2018-0610)
Identifier: '6F39' Structure: cyclic Optional

SFI: Optional
Record length: 3 bytes Update activity: high
Access Conditions:
READ PIN
UPDATE PIN/PIN2
INCREASE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 3 Accumulated count of units M 3 bytes
NOTE: If a SFI is assigned, the recommended value is ‘1C’. However cards may exist
that indicate another value. Therefore the terminal shall be able to handle other
values.
- Accumulated count of units

Contents:
value of the ACM.
Coding:
see the coding of EFACMmax.
If a GSM application is present on the UICC and the ACM value is to be shared between the GSM and the USIM
application this file shall be shared between the two applications.
4.2.10 EFGID1 (Group Identifier Level 1)

This EF contains identifiers for particular USIM-ME associations. It can be used to identify a group of USIMs for a
particular application.
Identifier: '6F3E' Structure: transparent Optional

File size: n bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to n USIM group identifier(s) O n bytes
4.2.11 EFGID2 (Group Identifier Level 2)

This EF contains identifiers for particular USIM-ME associations. It can be used to identify a group of USIMs for a
particular application.
Identifier: '6F3F' Structure: transparent Optional

File size: n bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to n USIM group identifier(s) O n bytes
3GPP
Release 15 42 3GPP TS 31.102 V15.21.0 (2018-0610)
NOTE: The structure of EFGID1 and EFGID2 is identical. They are provided to allow the network operator to enforce
different levels of security dependant on an application.
4.2.12 EFSPN (Service Provider Name)

This EF contains the service provider name in text format and appropriate requirements for the display by the ME. The
service provider name may also be provided in a graphical format in EFSPNI. The ME shall use the service provider
name in the text format or the graphical format or both to display the service provider name according to the rules
defined in section 4.2.88.

File Size: 17 bytes Update activity: low
Access Conditions:
READ ALWAYS
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 Display Condition M 1 byte
2 to 17 Service Provider Name M 16 bytes
- Display Condition
Contents: display condition for the service provider name in respect to the registered PLMN (see TS 22.101 [24]).
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
b1=0: display of registered PLMN name not required

when registered PLMN is either HPLMN or a PLMN in
the service provider PLMN list (see EFSPDI).
B1=1: display of registered PLMN name required when
registered PLMN is either HPLMN or a PLMN in the
service provider PLMN list(see EFSPDI).
B2=0: display of the service provider name is
required when registered PLMN is neither HPLMN nor a
PLMN in the service provider PLMN list(see EFSPDI).
B2=1: display of the service provider name is not
required when registered PLMN is neither HPLMN nor a
PLMN in the service provider PLMN list(see EFSPDI).
RFU (see TS 31.101)
- Service Provider Name

Contents:
service provider string
Coding:
the string shall use:
- either the SMS default 7-bit coded alphabet as defined in TS 23.038 [5] with bit 8 set to 0. The string
shall be left justified. Unused bytes shall be set to 'FF'.
- or one of the UCS2 code options defined in the annex of TS 31.101 [11].
4.2.13 EFPUCT (Price per Unit and Currency Table)

3GPP
Release 15 43 3GPP TS 31.102 V15.21.0 (2018-0610)
This EF contains the Price per Unit and Currency Table (PUCT). The PUCT is Advice of Charge related information
which may be used by the ME in conjunction with EFACM to compute the cost of calls in the currency chosen by the
subscriber, as specified in TS 22.024 [3].

Access Conditions:
READ PIN
UPDATE PIN/PIN2
DEACTIVATE ADM
ACTIVATE ADM

1 to 3 Currency code M 3 bytes
4 to 5 Price per unit M 2 bytes
- Currency code
Contents:
the alpha-identifier of the currency code.
Coding:
bytes 1, 2 and 3 are the respective first, second and third character of the alpha identifier. This alpha-tagging shall
use the SMS default 7-bit coded alphabet as defined in TS 23.038 [5] with bit 8 set to 0.
- Price per unit

Contents:
price per unit expressed in the currency coded by bytes 1 to 3.
Coding:
byte 4 and bits b1 to b4 of byte 5 represent the Elementary Price per Unit (EPPU) in the currency coded by bytes 1
to 3. Bits b5 to b8 of byte 5 are the decimal logarithm of the multiplicative factor represented by the absolute value of
its decimal logarithm (EX) and the sign of EX, which is coded 0 for a positive sign and 1 for a negative sign.
Byte 4:
b8 b7 b6 b5 b4 B3 b2 b1
211 210 29 28 27 26 25 24 of EPPU
Byte 5:
b8 b7 b6 b5 b4 b3 b2 b1
23 22 21 20 of EPPU
Sign of EX
20 of Abs(EX)
21 of Abs(EX)
22 of Abs(EX)
- The computation of the price per unit value is made by the ME in compliance with TS 22.024 [3] by the
following formula:
price per unit = EPPU * 10EX.
- The price has to be understood as expressed in the coded currency.
If a GSM application is present on the UICC and the PUCT information is to be shared between the GSM and the
USIM application, then this file shall be shared between the two applications.
3GPP
Release 15 44 3GPP TS 31.102 V15.21.0 (2018-0610)
4.2.14 EFCBMI (Cell Broadcast Message identifier selection)

This EF contains the Message Identifier Parameters which specify the type of content of the cell broadcast messages
that the subscriber wishes the UE to accept.
Any number of CB Message Identifier Parameters may be stored in the USIM. No order of priority is applicable.

File size: 2 n bytes Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 2 CB Message Identifier 1 O 2 bytes
: : : :
2n-1 to 2n CB Message Identifier n O 2 bytes
- Cell Broadcast Message Identifier

Coding:
- as in TS 23.041 [16], "Message Format on BTS-MS Interface - Message Identifier";
- values listed show the types of message which shall be accepted by the UE;
- unused entries shall be set to 'FF FF'.
4.2.15 EFACC (Access Control Class)

This EF contains the assigned access control class(es). The access control class is a parameter to control the access
attempts. 15 classes are split into 10 classes randomly allocated to normal subscribers and 5 classes allocated to specific
high priority users. For more information see TS 22.011 [2].

SFI: '06'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to 2 Access control classes M 2 bytes
- Access control classes

Coding:
- each ACC is coded on one bit. An ACC is "allocated" if the corresponding bit is set to 1 and "not allocated" if this
bit is set to 0. Bit b3 of byte 1 is set to 0.
Byte 1:
b8 b7 b6 b5 b4 b3 b2 b1
15 14 13 12 11 10 09 08 Number of the ACC (except for bit b3)
Byte 2:
3GPP
Release 15 45 3GPP TS 31.102 V15.21.0 (2018-0610)
b8 b7 b6 b5 b4 b3 b2 b1
07 06 05 04 03 02 01 00 Number of the ACC
4.2.16 EFFPLMN (Forbidden PLMNs)

This EF contains the coding for n Forbidden PLMNs (FPLMN). It is read by the ME as part of the USIM initialization
procedure and indicates PLMNs which the UE shall not automatically attempt to access.
A PLMN is written to the EF if a network rejects a Location Update with the cause "PLMN not allowed". The ME shall
manage the list as follows.
When n FPLMNs are held in the EF, and rejection of a further PLMN is received by the ME from the network, the ME
shall modify the EF using the UPDATE command. This new PLMN shall be stored in the nth position, and the existing
list "shifted" causing the previous contents of the first position to be lost.
When less than n FPLMNs exist in the EF, storage of an additional FPLMN shall not cause any existing FPLMN to be
lost.
Dependent upon procedures used to manage storage and deletion of FPLMNs in the EF, it is possible, when less than n
FPLMNs exist in the EF, for 'FFFFFF' to occur in any position. The ME shall analyse all the EF for FPLMNs in any
position, and not regard 'FFFFFF' as a termination of valid data.
Identifier: '6F7B' Structure: transparent Mandatory

SFI: '0D'
File size: 3n bytes, (n≥ 4) Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 3 PLMN 1 M 3 bytes
: : : :
(3n-2) to 3n PLMN n O 3 bytes
- PLMN
Contents:
Mobile Country Code (MCC) followed by the Mobile Network Code (MNC).
Coding:
according to TS 24.008 [9].
For instance, using 246 for the MCC and 81 for the MNC and if this is stored in PLMN 3 the contents is as follows:
Bytes 7 to 9: '42' 'F6' '18'.
If storage for fewer than n PLMNs is required, the unused bytes shall be set to 'FF'.
4.2.17 EFLOCI (Location Information)

This EF contains the following Location Information:
- Temporary Mobile Subscriber Identity (TMSI);

- Location Area Information (LAI);
- Location update status.
See clause 5.2.5 for special requirements when updating EFLOCI.
3GPP
Release 15 46 3GPP TS 31.102 V15.21.0 (2018-0610)
Identifier: '6F7E' Structure: transparent Mandatory

SFI: '0B'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 4 TMSI M 4 bytes
5 to 9 LAI M 5 bytes
10 RFU M 1 byte
11 Location update status M 1 byte
- TMSI
Contents:
Temporary Mobile Subscriber Identity.
Coding:
B8 b7 b6 b5 b4 B3 b2 b1
MSB
- LAI
Contents:
Location Area Information.
Coding:
Byte 5: first byte of LAI
b8 b7 b6 b5 b4 b3 b2 b1
MSB
- Location update status

Contents:
status of location update according to TS 24.008 [9].
Coding:
Byte 11:
Bits: b3 b2 b1
0 0 0 : updated.
0 0 1 : not updated.
0 1 0 : PLMN not allowed.
0 1 1 : Location Area not allowed.
1 1 1 : reserved.
Bits b4 to b8 are RFU (see TS 31.101 [11]).
4.2.18 EFAD (Administrative Data)

This EF contains information concerning the mode of operation according to the type of USIM, such as normal (to be
used by PLMN subscribers for 3G operations), type approval (to allow specific use of the ME during type approval
procedures of e.g. the radio equipment), cell testing (to allow testing of a cell before commercial use of this cell),
manufacturer specific (to allow the ME manufacturer to perform specific proprietary auto-test in its ME during e.g.
maintenance phases).
3GPP
Release 15 47 3GPP TS 31.102 V15.21.0 (2018-0610)
It also provides an indication about how some ME features shall work during normal operation as well as information
about the length of the MNC, which is part of the International Mobile Subscriber Identity (IMSI).
Identifier: '6FAD' Structure: transparent Mandatory

SFI: '03'
File size: 4+X bytes Update activity: low
Access Conditions:
READ ALW
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 UE operation mode M 1 byte
2 to 3 Additional information M 2 bytes
4 length of MNC in the IMSI M 1 byte
5 to 4+X RFU O X bytes
- UE operation mode:
Contents:
mode of operation for the UE
Coding:
Initial value
- '00' normal operation.
- '80' type approval operations.
- '01' normal operation + specific facilities.
- '81' type approval operations + specific facilities.
- '02' maintenance (off line).
- '04' cell test operation.
All other values are RFU
- Additional information:
Contents:
additional information depending on the UE operation mode
Coding:
- specific facilities (if b1=1 in byte 1):
Byte 2 (first byte of additional information):
b8 b7 b6 b5 b4 b3 b2 b1
RFU (see TS 31.101)
Byte 3 (second byte of additional information):
b8 b7 b6 b5 b4 b3 b2 b1
b1=0: ciphering indicator feature disabled

b1=1: ciphering indicator feature enabled
b2: CSG Display Control bit, see below
b3: ProSe services for Public Safety, see below
b4: extended DRX cycle
RFU (see TS 31.101)
b1 is used to control the ciphering indicator feature as specified in TS 22.101 [24].
b2 is used to indicate which CSGs the UE shall display during manual CSG selection. This bit
corresponds to the value of OperatorCSGEntries_Only leaf described in TS 24.285 [58]. This bit shall be
ignored when service n°92 is not "available".
- b2=0: for every PLMN not included in EF_OCSGL, or for which a CSG display indicator tag is not
present, all available CSGs can be displayed without any restriction.
3GPP
Release 15 48 3GPP TS 31.102 V15.21.0 (2018-0610)
- b2=1: for every PLMN not included in EF_OCSGL or any PLMN for which a CSG display indicator
tag is not present, only the available CSGs found in the Operator CSG list shall be displayed.
b3 is used to indicate whether the USIM enables the Public Safety UE to use the ME provisioning
parameters for Public Safety usage, in the cases described in TS 24.334 [70].
- b3=0: the ME is not authorized for ProSe services for Public Safety usage (i.e. Direct Discovery and
Direct Communication as per TS 24.334 [70]) without contacting the ProSe Function.
- b3=1: the ME is authorized to use the parameters stored in the USIM or in the ME for ProSe
services for Public Safety usage, as described in TS 24.334 [70] without contacting the ProSe
Function.
b4 is used to indicate whether the UICC polling interval to retrieve proactive commands can be modified
(as described in TS 31.101 [11]) or weather the UICC interface can be deactivated (as described in clause
5.1.11) during extended DRX cycle.
- b4=0: the ME is not authorized to modify the polling interval and/or disable the UICC interface
during extended DRX cycle.
- b4=1: the ME is authorized to modify the polling interval and/or disable the UICC interface during
extended DRX cycle.
- ME manufacturer specific information (if b2=1 in byte 1):
Byte 2 (first byte of additional information):
B8 b7 b6 B5 B4 b3 b2 b1
Any value
Byte 3 (second byte of additional information):
B8 b7 b6 b5 B4 b3 b2 b1
Any value
- Length of MNC in the IMSI:

Contents:
The length indicator refers to the number of digits, used for extracting the MNC from the IMSI
Coding:
Byte 4:
b8 b7 b6 b5 b4 b3 b2 b1
This value codes the number of digits of the MNC in

the IMSI. Only the values '0010' and '0011' are
currently specified, all other values are reserved
for future use.
RFU (see TS 31.101)
4.2.19 Void
4.2.20 EFCBMID (Cell Broadcast Message Identifier for Data Download)

This EF contains the message identifier parameters which specify the type of content of the cell broadcast messages
which are to be passed to the USIM.
Any number of CB message identifier parameters may be stored in the USIM. No order of priority is applicable.
3GPP
Release 15 49 3GPP TS 31.102 V15.21.0 (2018-0610)

SFI: '0E'
File size: 2n bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

: : : :
2n-1 to 2n CB Message Identifier n O 2 bytes
- Cell Broadcast Message Identifier.

Coding:
- as in TS 23.041 [16]. Values listed show the identifiers of messages which shall be accepted by the UE to be passed
to the USIM.
Unused entries shall be set to 'FF FF'.
4.2.21 EFECC (Emergency Call Codes)

This EF contains emergency call codes.
Identifier: '6FB7' Structure: linear fixed Mandatory

SFI: '01'
Record size: X+4 bytes Update activity: low
Access Conditions:
READ ALW
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to 3 Emergency Call Code M 3 bytes
4 to X+3 Emergency Call Code Alpha Identifier O X bytes
X+4 Emergency Service Category M 1 byte
- Emergency Call Code.

Contents:
- Emergency Call Code.
Coding:
- the emergency call code is of a variable length with a maximum length of 6 digits. Each emergency call code is
coded on three bytes, with each digit within the code being coded on four bits as shown below. If a code of less than 6
digits is chosen, then the unused nibbles shall be set to 'F'.
Byte 1:
b8 b7 b6 b5 b4 b3 b2 b1
LSB of Digit 1
::
::
MSB of Digit 1
LSB of Digit 2
:
:
MSB of Digit 2
Byte 2:
3GPP
Release 15 50 3GPP TS 31.102 V15.21.0 (2018-0610)
b8 b7 b6 b5 b4 b3 b2 b1
LSB of Digit 3
:
:
MSB of Digit 3
LSB of Digit 4
:
:
MSB of Digit 4
Byte 3:
b8 b7 b6 b5 b4 b3 b2 b1
LSB of Digit 5
:
:
MSB of Digit 5
LSB of Digit 6
:
:
MSB of Digit 6
- Emergency Call Code Alpha Identifier.

Contents:
Information about the dialled emergency number to be displayed to the user.
Coding:
this alpha-tagging shall use
either:
- the SMS default 7-bit coded alphabet as defined in TS 23.038 [5] with bit 8 set to 0. The alpha identifier shall
be left justified. Unused bytes shall be set to 'FF'.
Or
- one of the UCS2 coded options as defined in the annex of TS 31.101 [11].
- Emergency Service Category.

Contents:
Information to be sent to the network indicating the category of the emergency call.
Coding:
Coding according to TS 24.008 [9].
4.2.22 EFCBMIR (Cell Broadcast Message Identifier Range selection)

This EF contains ranges of cell broadcast message identifiers that the subscriber wishes the UE to accept.
Any number of CB Message Identifier Parameter ranges may be stored in the USIM. No order of priority is applicable.

File size: 4n bytes Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 4 CB Message Identifier Range 1 O 4 bytes
5 to 8 CB Message Identifier Range 2 O 4 bytes
: : : :
(4n-3) to 4n CB Message Identifier Range n O 4 bytes
3GPP
Release 15 51 3GPP TS 31.102 V15.21.0 (2018-0610)
- Cell Broadcast Message Identifier Ranges.

Contents:
- CB Message Identifier ranges:
Coding:
- bytes one and two of each range identifier equal the lower value of a cell broadcast range, bytes three and four equal
the upper value of a cell broadcast range, both values are coded as in TS 23.041 [16] "Message Format on BTS-MS
Interface - Message Identifier". Values listed show the ranges of messages which shall be accepted by the UE.
Unused entries shall be set to 'FF FF FF FF'.
4.2.23 EFPSLOCI (Packet Switched location information)

This EF contains the following Location Information:
- Packet Temporary Mobile Subscriber Identity (P-TMSI);

- Packet Temporary Mobile Subscriber Identity signature value (P-TMSI signature value);
- Routing Area Information (RAI);
- Routing Area update status.

SFI: '0C'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 4 P-TMSI M 4 bytes
5 to 7 P-TMSI signature value M 3 bytes
8 to13 RAI M 6 bytes
14 Routing Area update status M 1 byte
- P-TMSI.
Contents:
Packet Temporary Mobile Subscriber Identity.
Coding:
Byte 1: first byte of P-TMSI
b8 b7 B6 B5 B4 B3 b2 b1
MSB
- P-TMSI signature value.

Contents:
Packet Temporary Mobile Subscriber Identity signature value.
Coding:
Byte 5: first byte of P-TMSI signature value.
B8 b7 B6 B5 B4 B3 b2 b1
MSB
3GPP
Release 15 52 3GPP TS 31.102 V15.21.0 (2018-0610)
- RAI
Contents:
Routing Area Information.
Coding:
Byte 8: first byte of RAI
b8 b7 b6 b5 b4 b3 b2 b1
MSB
- Routing Area update status.

Contents:
status of routing area update according to TS 24.008 [9].
Coding:
byte 14:
Bits: b3 b2 b1.
0 0 0 : updated.
0 0 1 : not updated.
0 1 0 : PLMN not allowed.
0 1 1 : Routing Area not allowed.
1 1 1 : reserved.
4.2.24 EFFDN (Fixed Dialling Numbers)

If service n° 2 and/or service n° 89 is "available", this file shall be present.
This EF contains Fixed Dialling Numbers (FDN) and/or Supplementary Service Control strings (SSC). In addition it
contains identifiers of associated network/bearer capabilities and identifiers of extension records at the USIM ADF
level. It may also contain an associated alpha-tagging. If this file is present in the USIM, the Enabled Services
Table (EFEST) shall also be present.
Identifier: '6F3B' Structure: linear fixed Optional

Record length: X+14 bytes Update activity: low
Access Conditions:
READ PIN
UPDATE PIN2
DEACTIVATE ADM
ACTIVATE ADM

1 to X Alpha Identifier O X bytes
X+1 Length of BCD number/SSC contents M 1 byte
X+2 TON and NPI M 1 byte
X+3 to X+12 Dialling Number/SSC String M 10 bytes
X+13 Capability/Configuration2 Record Identifier M 1 byte
X+14 Extension2 Record Identifier M 1 byte
For contents and coding of all data items see the respective data items of the EF ADN (clause 4.4.2.3), with the exception
that extension records are stored in the EFEXT2.
By default, destination addresses which are not in EFFDN shall not be allowed on any CS bearer service/teleservice, or
IMS communication or SMS when FDN is enabled.
For the FDN procedures related to SMS see TS 22.101 [24] and TS 31.111 [12].
3GPP
Release 15 53 3GPP TS 31.102 V15.21.0 (2018-0610)
NOTE: The value of X (the number of bytes in the alpha-identifier) may be different to the length denoted X in
EFADN.
4.2.25 EFSMS (Short messages)

This EF contains information in accordance with TS 23.040 [6] comprising short messages (and associated parameters)
which have either been received by the UE from the network, or are to be used as an UE originated message.
Identifier: '6F3C' Structure: linear fixed Optional

Record length: 176 bytes Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 Status M 1 byte
2 to 176 Remainder M 175 bytes
- Status.
Contents:
Status byte of the record which can be used as a pattern in the SEARCH RECORD command. For UE originating
messages sent to the network, the status shall be updated when the UE receives a status report, or sends a successful
SMS Command relating to the status report.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
X X 0 free space
X X 1 used space
0 0 1 message received by UE from network; message read
0 1 1 message received by UE from network; message to be

read
1 1 1 UE originating message; message to be sent
RFU (see TS 31.101 [11])
b8 b7 b6 b5 b4 b3 b2 b1
X X 1 0 1 UE originating message; message sent to the network:

0 0 1 0 1 Status report not requested
0 1 1 0 1 Status report requested but not (yet) received;
1 0 1 0 1 Status report requested, received but not stored
in EF-SMSR;
1 1 1 0 1 Status report requested, received and stored
in EF-SMSR;
RFU (see TS 31.101 [11])
- Remainder.
Contents:
This data item commences with the TS-Service-Centre-Address as specified in TS 24.011 [10]. The bytes
immediately following the TS-Service-Centre-Address contain an appropriate short message TPDU as specified in
TS 23.040 [6], with identical coding and ordering of parameters.
3GPP
Release 15 54 3GPP TS 31.102 V15.21.0 (2018-0610)
Coding:
according to TS 23.040 [6] and TS 24.011 [10]. Any TP-message reference contained in an UE originated message
stored in the USIM, shall have a value as follows:
Value of the TP-message-reference:

message to be sent: 'FF'.
Message sent to the network: the value of TP-Message-Reference used in the
message sent to the network.
Any bytes in the record following the TPDU shall be filled with 'FF'.
It is possible for a TS-Service-Centre-Address of maximum permitted length, e.g. containing more than 18 address
digits, to be associated with a maximum length TPDU such that their combined length is 176 bytes. In this case the ME
shall store in the USIM the TS-Service-Centre-Address and the TPDU in bytes 2 to 176 without modification, except
for the last byte of the TPDU, which shall not be stored.
4.2.26 EFMSISDN (MSISDN)

This EF contains MSISDN(s) related to the subscriber. In addition it contains identifiers of associated network/bearer
capabilities and identifiers of extension records at the USIM ADF level. It may also contain an associated
alpha-tagging.
Identifier: '6F40' Structure: linear fixed Optional

Access Conditions:
READ PIN
UPDATE PIN/ADM
DEACTIVATE ADM
ACTIVATE ADM

For contents and coding of all data items see the respective data items of EF ADN.
If the USIM stores more than one MSISDN number and the ME displays the MSISDN number(s) within the
initialisation procedure then the one stored in the first record shall be displayed with priority.
EFADN.
4.2.27 EFSMSP (Short message service parameters)

This EF contains values for Short Message Service header Parameters (SMSP), which can be used by the ME for user
assistance in preparation of mobile originated short messages. For example, a service centre address will often be
common to many short messages sent by the subscriber.
The EF consists of one or more records, with each record able to hold a set of SMS parameters. The first (or only)
record in the EF shall be used as a default set of parameters, if no other record is selected.
To distinguish between records, an alpha-identifier may be included within each record, coded on Y bytes.
3GPP
Release 15 55 3GPP TS 31.102 V15.21.0 (2018-0610)
The SMS parameters stored within a record may be present or absent independently. When a short message is to be sent
from the UE, the parameter in the USIM record, if present, shall be used when a value is not supplied by the user.

Record length: 28+Y bytes Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to Y Alpha-Identifier O Y bytes
Y+1 Parameter Indicators M 1 byte
Y+2 to Y+13 TP-Destination Address M 12 bytes
Y+14 to Y+25 TS-Service Centre Address M 12 bytes
Y+26 TP-Protocol Identifier M 1 byte
Y+27 TP-Data Coding Scheme M 1 byte
Y+28 TP-Validity Period M 1 byte
Storage is allocated for all of the possible SMS parameters, regardless of whether they are present or absent. Any bytes
unused, due to parameters not requiring all of the bytes, or due to absent parameters, shall be set to 'FF'.
- Alpha-Identifier.
Contents:
Alpha Tag of the associated SMS-parameter.
Coding:
see clause 4.4.2.3 (EFADN).
NOTE: The value of Y may be zero, i.e. the alpha-identifier facility is not used. By using the command GET
RESPONSE the ME can determine the value of Y.
- Parameter Indicators.
Contents:
each of the default SMS parameters which can be stored in the remainder of the record are marked absent or present
by individual bits within this byte.
Coding:
allocation of bits:
bit number Parameter indicated.
1 TP-Destination Address.
2 TS-Service Centre Address.
3 TP-Protocol Identifier.
4 TP-Data Coding Scheme.
5 TP-Validity Period.
6 reserved, set to 1.
Bit value Meaning.

0 Parameter present.
1 Parameter absent.
- TP-Destination Address.
Contents and Coding:
as defined for SM-TL address fields in TS 23.040 [6].
- TP-Service Centre Address.

as defined for RP-Destination address Centre Address in TS 24.011 [10].
- TP-Protocol Identifier.
3GPP
Release 15 56 3GPP TS 31.102 V15.21.0 (2018-0610)

as defined in TS 23.040 [6].
- TP-Data Coding Scheme.

as defined in TS 23.038 [5].
- TP-Validity Period.
as defined in TS 23.040 [6] for the relative time format.
4.2.28 EFSMSS (SMS status)

This EF contains status information relating to the short message service.

File size: 2+X bytes Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 Last Used TP-MR M 1 byte
2 SMS "Memory Cap. Exceeded" Not. Flag M 1 byte
3 to 2+X RFU O X bytes
- Last Used TP-MR.

Contents:
- the value of the TP-Message-Reference parameter in the last mobile originated short message, as defined in
TS 23.040 [6].
Coding:
- as defined in TS 23.040 [6].
- SMS "Memory Capacity Exceeded" Notification Flag.

Contents:
- this flag is required to allow a process of flow control, so that as memory capacity in the UE becomes available, the
Network can be informed. The process for this is described in TS 23.040 [6].
Coding:
b1=1 means flag unset; memory capacity available;
b1=0 means flag set;
b2 to b8 are reserved and set to 1.
4.2.29 EFSDN (Service Dialling Numbers)

If service n° 4 and or service n° 89 is "available", this file shall be present.
This EF contains special service numbers (SDN) and/or the respective supplementary service control strings (SSC). In
addition it contains identifiers of associated network/bearer capabilities and identifiers of extension records at the USIM
ADF level. It may also contain associated alpha-tagging. If the service n° 89 is available this file will contain the eCall
test and reconfiguration numbers that are used by an UE in eCall and normal service mode.
3GPP
Release 15 57 3GPP TS 31.102 V15.21.0 (2018-0610)

Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1-X Alpha identifier O X bytes
X+1 Length of BCD number/SSC contents M 1 bytes
that extension records are stored in the EFEXT3 and capability/configuration parameters are stored in EFCCP2.
EFADN.
4.2.30 EFEXT2 (Extension2)

This EF contains extension data of an FDN (see FDN in 4.2.24).
Identifier: '6F4B' Structure: linear fixed Optional

Access Conditions:
READ PIN
UPDATE PIN2
DEACTIVATE ADM
ACTIVATE ADM

1 Record type M 1 byte
2 to 12 Extension data M 11 bytes
13 Identifier M 1 byte
For contents and coding see clause 4.4.2.4 (EFEXT1).

This EF contains extension data of an SDN (see SDN in 4.2.29).
Identifier: '6F4C' Structure: linear fixed Optional

Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

3GPP
Release 15 58 3GPP TS 31.102 V15.21.0 (2018-0610)
4.2.32 EFSMSR (Short message status reports)

This EF contains information in accordance with TS 23.040 [6] comprising short message status reports which have
been received by the UE from the network.
Each record is used to store the status report of a short message in a record of EFSMS. The first byte of each record is the
link between the status report and the corresponding short message in EFSMS.

Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 SMS record identifier M 1
2 to 30 SMS status report M 29 bytes
- SMS record identifier.

Contents:
- this data item identifies the corresponding SMS record in EFSMS, e.g. if this byte is coded '05' then this status report
corresponds to the short message in record #5 of EFSMS.
Coding:
- '00' - empty record;
- '01' to 'FF' - record number of the corresponding SMS in EFSMS.
- SMS status report:

Contents:
- this data item contains the SMS-STATUS-REPORT TPDU as specified in TS 23.040 [6], with identical coding and
ordering of parameters.
Coding:
- according to TS 23.040 [6]. Any bytes in the record following the TPDU shall be filled with 'FF'.
4.2.33 EFICI (Incoming Call Information)

If service n°9 is "available", this file shall be present.
This EF is located within the USIM application. The incoming call information can be linked to the phone book stored
under DFTELECOM or to the local phone book within the USIM. The EFICI 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
3GPP
Release 15 59 3GPP TS 31.102 V15.21.0 (2018-0610)
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.
For the current version of the phone book, the phone book entry is identified as follows:
- the record number in the EFPBR which indicates the EFADN containing the entry;
- the record number inside the indicated EFADN.
The structure of EFICI is shown below. Coding scheme is according to EFADN
Structure of EFICI
Identifier: '6F80' Structure: Cyclic Optional

SFI: '14'
Record length: X+28 bytes Update activity: high
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

X+1 Length of BCD number contents M 1 byte
X+3 to X+12 Incoming Call Number M 10 bytes
X+15 to X+21 Incoming call date and time (see detail 1) M 7 bytes
X+22 to X+24 Incoming call duration (see detail 2) M 3 bytes
X+25 Incoming call status (see detail 3) M 1 byte
X+26 to X+28 Link to phone book entry (see detail 4) M 3 bytes
NOTE: When the contents except incoming call status are invalid, they are filled with 'FF'.
Detail 1 Coding of date and time.
Content:
the date and time are defined by the ME.
Coding:
it is according to the extended BCD coding from Byte1 to Byte 7. The first 3 bytes show year, month and day
(yy.mm.dd). The next 3 bytes show hour, minute and second (hh.mm.ss). The last Byte 7 is Time Zone. The Time Zone
indicates the difference, expressed in quarters of an hour, between the local time and GMT. Bit 4 in Byte 7 represents
the algebraic sign of this difference (0: positive, 1: negative). If the terminal does not support the Time Zone, Byte 7
shall be "FF". Byte X+15: Year.
B8 b7 b6 b5 b4 b3 b2 b1
LSB of first digit year
MSB of first digit year

LSB of second digit year
MSB of second digit year
Byte X+16: Month
3GPP
Release 15 60 3GPP TS 31.102 V15.21.0 (2018-0610)
b8 b7 b6 b5 b4 b3 b2 b1
LSB of first digit month
MSB of first digit month

LSB of second digit month
MSB of second digit month
Byte X+17: Day
b8 b7 b6 b5 b4 b3 b2 b1
LSB of first digit day
MSB of first digit day

LSB of second digit day
MSB of second digit day
Byte X+18: Hour
b8 b7 b6 b5 b4 b3 b2 b1
LSB of first digit hour
MSB of first digit hour

LSB of second digit hour
MSB of second digit hour
Byte X+19: Minute
b8 b7 b6 b5 b4 b3 b2 b1
LSB of first digit minute
MSB of first digit minute

LSB of second digit minute
MSB of second digit minute
Byte X+20: Second
b8 b7 b6 b5 b4 b3 b2 b1
LSB of first digit second
MSB of first digit second

LSB of second digit second
MSB of second digit second
3GPP
Release 15 61 3GPP TS 31.102 V15.21.0 (2018-0610)
Byte X+21: Time Zone
b8 b7 b6 b5 b4 b3 b2 b1
LSB of first digit indicates by quarters an hour
MSB of first digit indicates by quarters an hour

the algebraic sign (0: positive, 1: negative)
LSB of second digit indicates by quarters an hour
MSB of second digit indicates by quarters an hour
Detail 2 Coding of call duration.
Call duration is indicated by second.
Byte X+22:
b8 b7 b6 b5 b4 b3 b2 b1
223 222 221 220 219 218 217 216
Byte X+23:
b8 b7 b6 b5 b4 b3 b2 b1
215 214 213 212 211 210 29 28
Byte X+24:
b8 b7 b6 b5 b4 b3 b2 b1
27 26 25 24 23 22 21 20
For instance, '00' '00' '30' represents 25+24.
Detail 3 Coding of Call status.
Byte X+25:
b8 b7 b6 b5 b4 b3 b2 b1
Answered='0'/ Not Answered='1'

RFU
Detail 4 Link to phone book entry
For the current implementation of the phone book the following coding applies:
Phone book reference.
Byte X+26:
3GPP
Release 15 62 3GPP TS 31.102 V15.21.0 (2018-0610)
b8 b7 b6 b5 b4 b3 b2 b1
0 Global Phone Book (DFTELECOM)

1 Local Phone Book (USIM Specific)
RFU
EFPBR record number:
- Byte X+27: Hexadecimal value.
EFADN record number:
- Byte X+28: Hexadecimal value.
4.2.34 EFOCI (Outgoing Call Information)

This EF is located within the USIM application. The outgoing call information can be linked to the phone book stored
under DFTELECOM or to the local phone book within the USIM. The EFOCI contains the information related to outgoing
calls.
The time of the call and duration of the call are stored in this EF. It may also contain associated alpha identifier. In
addition it contains identifiers of associated network/bearer capabilities and identifiers of extension records at the USIM
ADF level. The structure of this file is cyclic, so the contents shall be updated only after a call is disconnected.
If the dialled phone number matches a number stored in the phone book the outgoing call information might be linked
to the corresponding information in the phone book. The dialled number may match with a hidden entry in the phone
book. If the dialled number matches a hidden entry in the phone book the link is established but the information related
to the phone book entry is not displayed by the ME, if the hidden code has not been verified. The ME shall not perform
hidden code verification 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 outgoing call number still exists 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'.
Coding scheme is according to EFICI.
Structure of EFOCI
Identifier: '6F81' Structure: Cyclic Optional

SFI: '15'
Record length: X+27 bytes Update activity: high
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

X+3 to X+12 Outgoing Call Number/SSC String M 10 bytes
X+15 to X+21 Outgoing call date and time M 7 bytes
X+22 to X+24 Outgoing call duration M 3 bytes
X+25 to X+27 Link to Phone Book Entry M 3 bytes
NOTE: When the contents are invalid, they are filled with 'FF'.
3GPP
Release 15 63 3GPP TS 31.102 V15.21.0 (2018-0610)
4.2.35 EFICT (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.
This file should have only one entry.
Structure of EFICT

Access Conditions:
READ PIN
UPDATE PIN/PIN2
INCREASE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 3 Accumulated call timer value M 3 bytes
Coding:
Accumulated call timer value is indicated by second.
Byte 1:
b8 b7 b6 b5 b4 b3 b2 b1
223 222 221 220 219 218 217 216
Byte 2:
b8 b7 b6 b5 b4 b3 b2 b1
215 214 213 212 211 210 29 28
Byte 3:
b8 b7 b6 b5 b4 b3 b2 b1
27 26 25 24 23 22 21 20
For example, '00' '00' '30' represents 25+24.
4.2.36 EFOCT (Outgoing Call Timer)

This EF contains the accumulated outgoing call timer duration value for the current call and previous calls. The EF is
USIM specific and resides within the USIM application. The contents of this EF shall be updated only after a call is
disconnected. The coding of this EF is the same as EFICT.
This file should have only one entry.
3GPP
Release 15 64 3GPP TS 31.102 V15.21.0 (2018-0610)
Structure of EFOCT

Access Conditions:
READ PIN
UPDATE PIN/PIN2
INCREASE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 3 Accumulated call timer value M 3 bytes

This EF contains extension data of EFICI, EFOCI and EFMSISDN of the USIM application.
Identifier: '6F4E' Structure: linear fixed Optional

Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

For contents and coding see EFEXT1.
4.2.38 EFCCP2 (Capability Configuration Parameters 2)

This EF contains parameters of required network and bearer capabilities and terminal configurations associated with a
call established using a fixed dialling number, a barred dialling number, an MSISDN, a service dialling number, an
incoming call, an outgoing call or an MBDN. It is referred by EFFDN, EFBDN, EFMSISDN, EFSDN, EFICI, EFOCI, EFMBDN and
EFCFIS at USIM ADF level.
Identifier: '6F4F' Structure: linear fixed Optional

SFI: '16'
Record length: X bytes, X15 Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to X Bearer capability information element M X bytes
- Bearer capability information elements.
- Contents and Coding:

- see TS 24.008 [9]. The Information Element Identity (IEI) shall be excluded, i.e. the first byte of the EF CCP2 record
3GPP
Release 15 65 3GPP TS 31.102 V15.21.0 (2018-0610)
shall be Length of the bearer capability contents.

- unused bytes are filled with 'FF'.
4.2.39 EFeMLPP (enhanced Multi Level Precedence and Pre-emption)

This EF contains information about priority levels and fast call set-up conditions for the enhanced Multi Level
Precedence and Pre-emption service that can be used by the subscriber.
Identifier: '6FB5' Structure: transparent Optional

Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 Priority levels M 1 byte
2 Fast call set-up conditions M 1 byte
- Priority levels.
Contents:
- the eMLPP priority levels subscribed to.
Coding:
- each eMLPP priority level is coded on one bit. Priority levels subscribed to have their corresponding bits
set to 1. Priority levels not subscribed to have their corresponding bits set to 0. Bit b8 is reserved and set
to 0.
Byte 1:
b8 b7 b6 b5 b4 b3 b2 b1
priority level A
priority level B
priority level 0
priority level 1
priority level 2
priority level 3
priority level 4
0
NOTE: Priority levels A and B can not be subscribed to (see TS 22.067 [5] for details).
EXAMPLE 1: If priority levels 0, 1 and 2 are subscribed to, EFeMLPP shall be coded '1C'.
- Fast call set-up conditions.

Contents:
for each eMLPP priority level, the capability to use a fast call set-up procedure.
Coding:
each eMLPP priority level is coded on one bit. Priority levels for which fast call set-up is allowed have their
corresponding bits set to 1. Priority levels for which fast call set-up is not allowed have their corresponding bits set to 0.
Bit b8 is reserved and set to 0.
Byte 2: fast call set-up condition for:
3GPP
Release 15 66 3GPP TS 31.102 V15.21.0 (2018-0610)
b8 b7 b6 b5 b4 b3 b2 b1
fast call set-up condition for priority level A

` fast call set-up condition for priority level B
fast call set-up condition for priority level 0
0
EXAMPLE 2: If fast call set-up is allowed for priority levels 0, and 1, then byte 2 of EFeMLPP is coded '0C'.
4.2.40 EFAaeM (Automatic Answer for eMLPP Service)

This EF contains those priority levels (of the Multi Level Precedence and Pre-emption service) for which the ME shall
answer automatically to incoming calls.

Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 Automatic answer priority levels M 1 byte
- Automatic answer priority levels.

Contents:
- for each eMLPP priority level, the capability for the mobile station to answer automatically to incoming calls (with
the corresponding eMLPP priority level).
Coding:
- each eMLPP priority level is coded on one bit. Priority levels allowing an automatic answer from the mobile station
have their corresponding bits set to 1. Priority levels not allowing an automatic answer from the mobile station have
their corresponding bits set to 0. Bit b8 is reserved and set to 0.
Byte 1:
b8 b7 b6 b5 b4 b3 b2 b1
Automatic answer priority for priority level A

Automatic answer priority for priority level B
Automatic answer priority for priority level 0
0
EXAMPLE: If automatic answer is allowed for incoming calls with priority levels A, 0 and 1, then EF AaeM is
coded '0D'.
3GPP
Release 15 67 3GPP TS 31.102 V15.21.0 (2018-0610)
4.2.41 Void
4.2.42 EFHiddenkey (Key for hidden phone book entries)

This EF contains the hidden key that has to be verified by the ME in order to display the phone book entries that are
marked as hidden. The hidden key can consist of 4 to 8 digits.
Identifier: '6FC3' Structure: transparent Optional

Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 4 Hidden Key M 4 bytes
- Hidden Key.
Coding:
- the hidden key is coded on 4 bytes using BCD coding. The minimum number of digits is 4. Unused digits are
padded with 'F'.
NOTE 1: Digits are not swapped, i.e. for instance the key "1234" is coded as '12 34 FF FF'.
NOTE 2: The phone book entries marked as hidden are not scrambled by means of the hidden key. They are stored
in plain text in the phone book.
4.2.43 Void
4.2.44 EFBDN (Barred Dialling Numbers)

This EF contains Barred Dialling Numbers (BDN) and/or Supplementary Service Control strings (SSC). In addition it
contains identifiers of associated network/bearer capabilities and identifiers of extension records. It may also contain an
associated alpha-tagging. As the BDN service relies on the Call Control feature, BDN shall only be available if Call
Control is available. If this file is present in the USIM, the Enabled Services Table (EF EST) shall also be present.
Identifier: '6F4D' Structure: linear fixed Optional

Access Conditions:
READ PIN
UPDATE PIN2
DEACTIVATE ADM
ACTIVATE ADM

X+15 Comparison Method Pointer M 1 byte
For contents and coding of all data items, except for the Comparison Method Pointer, see the respective data items of
EFADN, with the exception that extension records are stored in the EFEXT4 and capability/configuration parameters are
stored in EFCCP2. The Comparison Method Pointer refers to a record number in EFCMI.
3GPP
Release 15 68 3GPP TS 31.102 V15.21.0 (2018-0610)
EFADN.

This EF contains extension data of a BDN/SSC.

Access Conditions:
READ PIN
UPDATE PIN2
DEACTIVE ADM
ACTIVATE ADM

For contents and coding see clause 4.4.2.4 EFEXT1.
4.2.46 EFCMI (Comparison Method Information)

This EF contains the list of Comparison Method Identifiers and alpha-tagging associated with BDN entries (see EF BDN).

Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to X Alpha Identifier M X bytes
X+1 Comparison Method Identifier M 1 byte
- Alpha Identifier.
Contents:
Alpha-tagging of the associated Comparison Method Identifier.
Coding:
Same as the alpha identifier in EFADN.
- Comparison Method Identifier.

Contents:
- this byte describes the comparison method which is associated with a BDN record. Its interpretation is not specified
but it shall be defined by the card issuers implementing the BDN feature on their USIMs.
Coding:
- binary; values from 0 to 255 are allowed.
The default coding 255 is reserved for empty field.
3GPP
Release 15 69 3GPP TS 31.102 V15.21.0 (2018-0610)
4.2.47 EFEST (Enabled Services Table)

If service n° 2, 6, 34 or 35 is "available" (as indicated in the USIM Service Table), this file shall be present.
This EF indicates which services are enabled. If a service is not indicated as enabled in this table, the ME shall not
select the service.

SFI: '05'
Access Conditions:
READ PIN
UPDATE PIN2
DEACTIVATE ADM
ACTIVATE ADM

etc.
-Services
Contents: Service n°1: Fixed Dialling Numbers (FDN)
Service n°2: Barred Dialling Numbers (BDN)
Service n°3: APN Control List (ACL)
The EF shall contain at least one byte. Further bytes may be included, but if the EF includes an optional byte, then the
EF shall also contain all bytes before that byte. Other services are possible in the future. The coding falls under the
responsibility of the 3GPP.
Coding:
- 1 bit is used to code each service:

- bit = 1: service activated;
- bit = 0: service deactivated.
- Unused bits shall be set to '0'.
A service which is listed in this table is enabled if it is indicated as available in the USIM Service Table (UST) and
indicated as activated in the Enabled Services Tables (EST) otherwise this service is, either not available or disabled.
First byte:
b8 b7 b6 B5 b4 b3 b2 b1
Service n°1
Service n°2
Service n°3
Service n°4
Service n°5
Service n°6
Service n°7
Service n°8
etc.
4.2.48 EFACL (Access Point Name Control List)

This EF contains the list of allowed APNs (Access Point Names) or DNNs. If this file is present in the USIM, the
Enabled Services Table (EFEST) shall also be present.
3GPP
Release 15 70 3GPP TS 31.102 V15.21.0 (2018-0610)

File size: X bytes (X>1) Update activity: low
Access Conditions:
READ PIN
UPDATE PIN2
DEACTIVATE ADM
ACTIVATE ADM

1 Number of APNs/DNNs M 1 byte
2 to X APN/DNN TLVs M X-1 byte
For contents and coding of APN/DNN-TLV values see TS 23.003 [25]. The tag value of the APN/DNN-TLV shall be
'DD'. "Network provided APN/DNN" is coded with a TLV object of length zero.
4.2.49 EFDCK (Depersonalisation Control Keys)

This EF provides storage for the de-personalization control keys associated with the OTA de-personalization cycle of
TS 22.022 [27].
Identifier: '6F2C' Structure: transparent Optional

File Size: 16 bytes Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 4 8 digits of network de-personalization control key M 4 bytes
5 to 8 8 digits of network subset de-personalization M 4 bytes
control key
9 to 12 8 digits of service provider de-personalization M 4 bytes
control key
13 to 16 8 digits of corporate de-personalization control M 4 bytes
key
Empty control key bytes shall be coded 'FFFFFFFF'.
4.2.50 EFCNL (Co-operative Network List)

This EF contains the Co-operative Network List for the multiple network personalization services defined in
TS 22.022 [27].

File size: 6n bytes, (n ≥ 1) Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to 6 Element 1 of co-operative net list M 6 bytes
: : : :
6n-5 to 6n Element n of co-operative net list O 6 bytes
3GPP
Release 15 71 3GPP TS 31.102 V15.21.0 (2018-0610)
- Co-operative Network List.
Contents:
- PLMN network subset, service provider ID and corporate ID of co-operative networks.
Coding:
- For each 6 byte list element.
Bytes 1 to 3: PLMN (MCC + MNC): according to TS 24.008 [9].
Byte 4:
b8 b7 b6 b5 b4 b3 b2 b1
LS bit of network subset digit 1

:
:
MS bit of network subset digit 1
LS bit of network subset digit 2
:
:
MS bit of network subset digit 2
Byte 5:
b8 b7 b6 b5 b4 b3 b2 b1
LS bit of service provider digit 1

:
:
MS bit of service provider digit 1
LS bit of service provider digit 2
:
:
MS bit of service provider digit 2
Byte 6:
b8 b7 b6 b5 b4 b3 b2 b1
LS bit of corporate digit 1

:
:
MS bit of corporate digit 1
LS bit of corporate digit 2
:
:
MS bit of corporate digit 2
- Empty fields shall be coded with 'FF'.
- The end of the list is delimited by the first MCC field coded 'FFF'.
3GPP
Release 15 72 3GPP TS 31.102 V15.21.0 (2018-0610)
4.2.51 EFSTART-HFN (Initialisation values for Hyperframe number)

This EF contains the values of STARTCS and STARTPS of the bearers that were protected by the keys in EFKEYS or
EFKEYSPS at release of the last CS or PS RRC connection. These values are used to control the lifetime of the keys (see
TS 33.102 [13]).
Identifier: '6F5B' Structure: transparent Mandatory

SFI: '0F'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 3 STARTCS M 3 bytes
4 to 6 STARTPS M 3 bytes
- STARTCS
Contents: Initialisation value for Hyperframe number – CS domain.
Coding: The LSB of STARTCS is stored in bit 1 of byte 3. Unused nibbles are set to 'F'.
- STARTPS
Contents: Initialisation value for Hyperframe number – PS domain.
Coding: As for STARTCS.
4.2.52 EFTHRESHOLD (Maximum value of START)

This EF contains the maximum value of STARTCS or STARTPS. This value is used to control the lifetime of the keys
(see TS 33.102 [13]).
Identifier: '6F5C' Structure: transparent Mandatory

SFI: '10'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to 3 Maximum value of STARTCS or STARTPS. M 3 bytes
- Maximum value of STARTCS or STARTPS.

Coding: As for STARTCS
4.2.53 EFOPLMNwACT (Operator controlled PLMN selector with Access

Technology)
This EF contains the coding for n PLMNs where n is determined by the operator. This information is determined by the
operator and defines the preferred PLMNs in priority order. The first record indicates the highest priority and the n th
record indicates the lowest. The EF also contains the Access Technologies for each PLMN in this list. (see
TS 23.122 [31])
3GPP
Release 15 73 3GPP TS 31.102 V15.21.0 (2018-0610)

SFI: '11'
File size: 5n bytes , (n ≥ 8) Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

: :
39 to 40 8th PLMN Access Technology Identifier M 2 bytes
44 to 45 9th PLMN Access Technology Identifier O 2 bytes
: :
(5n-4) to (5n-2) Nth PLMN (lowest priority) O 3 bytes
(5n-1) to 5n Nth PLMN Access Technology Identifier O 2 bytes
- PLMN.
Contents:
Coding:
- Access Technology Identifier:

Coding:
- See EFPLMNwACT for coding.
4.2.54 EFHPLMNwAcT (HPLMN selector with Access Technology)

The HPLMN Selector with access technology data field shall contain the HPLMN code, or codes together with the
respected access technology in priority order (see TS 23.122 [31]).
Identifier: '6F62' Structure: Transparent Optional

SFI: '13'
File size: 5n (n ≥ 1) bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

6 to 8 2nd PLMN O 3 bytes
9 to 10 2nd PLMN Access Technology Identifier O 2 bytes
: :
(5n-4) to (5n-2) nth PLMN (lowest priority) O 3 bytes
(5n-1) to 5n nth PLMN Access Technology Identifier O 2 bytes
- PLMN
Contents:
Coding:
3GPP
Release 15 74 3GPP TS 31.102 V15.21.0 (2018-0610)
- Access Technology:
Contents: The Access Technology of the HPLMN that the ME will assume when searching for the HPLMN, in priority
order. The first Access Technology in the list has the highest priority.
Coding:
- See EFPLMNwACT for coding.
4.2.55 EFARR (Access Rule Reference)

This EF contains the access rules for files located under the USIM ADF in the UICC. If the security attribute tag '8B' is
indicated in the FCP it contains a reference to a record in this file.
Structure of EFARR at ADF-level
Identifier: '6F06' Structure: Linear fixed Mandatory

SFI: '17'
Record Length: X bytes, (X > 0) Update activity: low
Access Conditions:
READ ALW
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to X Access Rule TLV data objects M X bytes
This EF contains one or more records containing access rule information according to the reference to expanded format
as defined in ISO/IEC 7816-4 [20]. Each record represents an access rule. Unused bytes in the record are set to 'FF'.
If the card cannot access EFARR , any attempt to access a file with access rules indicated in this EFARR shall not be
granted.
3GPP
Release 15 75 3GPP TS 31.102 V15.21.0 (2018-0610)
4.2.56 Void
4.2.57 EFNETPAR (Network Parameters)

This EF contains information concerning the cell frequencies
Network Parameter storage may reduce the extent of the terminal search of FDD, TDD or GSM carriers when selecting
a cell. The network parameters stored in the USIM shall be in accordance with the procedures specified in this clause.
The RF carrier frequency information is stored on 2 bytes and coded on 16 bits starting from 0,0 MHz. Each increment
of the 16 bit value is an increment of 200 kHz in frequency. This allows the exact channel frequency to be stored in this
data field making it independent of any band information. It is up to the terminal to associate the indicated frequency
with a particular band, e.g. GSM 900, GSM 1800 etc. This means that a range from 0 to 13,1 GHz can be covered, with
the resolution of 200 kHz. The frequency indicated is always the terminal receiver carrier frequency.
The EF provides a minimum storage capacity of 46 bytes in order to provide the capability of storing at least two cell
information TLV objects, e.g. GSM/FDD or FDD/TDD in its minimum configuration, i.e. the terminal can rely on the
required memory space for storing at least two cell information lists offering 8 GSM neighbour carrier frequencies and
8 Intra/Inter frequencies, respectively. In what configuration the available memory actually is being used is up to the
terminal.
A terminal shall ignore a TLV object or the value of a carrier frequency which is beyond its capabilities, i.e. an FDD
only terminal shall ignore the GSM related frequency information. When updating this file, the terminal shall update it
with the current values available in the terminal. Updating of this file shall start from the beginning of the file. The
terminal need not respect the structure of any information previously stored, i.e. an FDD only terminal may overwrite
the GSM parameters stored in this file by another terminal.
The GSM cell information constructed TLV object contains the information of the BCCH channel frequency that the
terminal is currently camped on, indicated by tag '80'. The constructed TLV object also contains an indication of up to
32 neighbour BCCH carrier frequencies indicated by tag '81'. In order to store a complete set of GSM network
parameters, a total of 72 bytes is required. The terminal shall convert the BCCH channel information, as specified in
TS 44.018 [28], received from the network into the corresponding frequency before storing it in the USIM.
The FDD cell information constructed TLV object contains the scrambling code information for the intra frequency
carrier, tag '80', and the inter frequency scrambling codes, tag '81'. The intra frequency carrier information may contain
up to 32 scrambling codes (m) while there is a limitation of the number of inter frequency scrambling codes (n1, n2,
n3). The number of inter frequencies that can be indicated is limited to three and the total amount of scrambling codes
for the inter frequencies is limited to 32 (n1+n2+n3 <= 32), i.e. if only one inter frequency carrier is indicated, it can
contain up to 32 scrambling codes. If two or more inter frequency carriers are indicated, a total of 32 scrambling codes
can be provided. How the information is split between the inter frequency carriers is determined by the terminal. In
order to store a complete set of FDD cell information a total of 146 bytes is required. The terminal shall convert the
UARFCN information, as specified in TS 25.101 [33], received from the network into the corresponding frequency
before storing it in the USIM.
The TDD cell information constructed TLV object has the same structure as the FDD cell information TLV object.
NOTE: Currently there is no inter frequency cell information required for the TDD case.
Identifier: '6FC4' Structure: transparent Mandatory

File size: X bytes, (X ≥ 46) Update activity: high
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to X TLV object(s) containing GSM/FDD/TDD cell O X
information
- EFNETPAR Cell Information tags
3GPP
Release 15 76 3GPP TS 31.102 V15.21.0 (2018-0610)
Description Value Information Element size

bytes
GSM Cell Information Tag 'A0' 1
Camping Frequency Tag '80' 1
Camping Frequency Information 2
Neighbour Frequency Tag '81' 1
Neighbour Frequency Information 2*m
(8 <= m <= 32)
FDD Cell Information Tag 'A1' 1
Intra Frequency Information Tag '80' 1
Scrambling code Information 2*m
(8 <= m <= 32)
Inter Frequency Information Tag '81' 1
Scrambling code information 2*(n1+n2+n3)
(8 <= n1+n2+n3 <= 32)
TDD Frequency information Tag 'A2' 1
Intra Frequency Information Tag '80' 1
Cell parameters ID 2*m
(8 <= m <= 32)
Inter Frequency Information Tag '81' 1
Cell parameters ID 2*(n1+n2+n3)
(8 <= n1+n2+n3 <= 32)
- GSM Cell Information, if tag 'A0' is present in this EF the content of this TLV is as follows:
Description Value M/O Length
GSM Cell Information Tag 'A0'' M 1
Length '4+ (2+2*m) M 1
(<=70) '
Current camped cell BCCH frequency '80' M 1
information tag
Length '02' M 1
Current camped BCCH frequency M 2
Neighbour Cell BCCH Frequency '81' O 1
information tag
Length 2*m (=< 32) O 1
Neighbour BCCH carrier frequencies O 2*m
(8 <= m <= 32)
- FDD Cell Information. If tag 'A1' is present in this EF the content of this TLV is as follows:

FDD Cell Information Tag 'A1' M 1
Length 4+(2*m) M 1
+(4+2*n1)+(4+2*
n2)+(4+2*n3)
(<=144)
FDD Intra Frequency information tag '80' M 1
Length 2+2*m M 1
Intra Frequency carrier frequency M 2
Intra Frequency scrambling codes M 2*m
(8 <= m <= 32)
FDD Inter Frequency information tag '81' O 1
(see NOTE 1)
Length 2+2*n (NOTE 2) O 1
Inter Frequency carrier frequencies O 2
Inter Frequency scrambling codes O 2*n (NOTE 2)
NOTE 1: This TLV object may occur up to 3 times within the constructed TLV object
depending how many inter frequencies are indicated
NOTE 2: n is in this case n1, n2 or n3, 8 <= (n1+n2+n3)<=32
3GPP
Release 15 77 3GPP TS 31.102 V15.21.0 (2018-0610)
- TDD Cell Information: If tag 'A2' is present in this EF the content of this TLV is as follows:

TDD Cell Information Tag 'A2' M 1
Length 4+(2*m) M 1
+(4+2*n1)+(4+2*
n2)+(4+2*n3)
(<=144)
TDD Intra Frequency information tag '80' M 1
Length 2+2*m M 1
Intra Frequency carrier frequency M 2
Intra Frequency scrambling codes M 2*m
(8 <= m <= 32)
TDD Inter Frequency information tag '81' O 1
(see NOTE 1)
Length 2+2*n (NOTE 2) O 1
Inter Frequency carrier frequencies O 2
Inter Frequency scrambling codes O 2*n (NOTE 2)
NOTE 1: This TLV object may occur up to 3 times within the constructed TLV object
depending how many inter frequencies are indicated
NOTE 2: n is in this case n1, n2 or n3, 8 <= (n1+n2+n3)<=32
4.2.58 EFPNN (PLMN Network Name)

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 [9].
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 [31].
If the EFOPL 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).
Identifier: '6FC5' Structure: linear fixed Optional

SFI: '19'
Record length: X bytes; X ≥ 3 Update activity: low
Access Conditions:
READ ALWAYS
UPDATE ADM
ACTIVATE ADM
DEACTIVATE ADM

1 to X Network name TLV objects M X bytes
- Network name TLV objects.

The content and coding (Full name for network and Short name for network) is defined below, where the fields
within the objects are defined in TS 24.008 [9]:
3GPP
Release 15 78 3GPP TS 31.102 V15.21.0 (2018-0610)
Coding of the Network name TLV objects
Length Description Status

1 byte Full name for network IEI: '43' M
(This shall be the same as that used in the
MM/GMM INFORMATION message).
1 byte Length of Full name for network Name contents M
Y bytes Full name for network contents (Octets 3 to n of M
network name information element)
1 byte Short name for network IEI: '45' O
(This shall be the same as that used in the
MM/GMM INFORMATION message).
1 byte Length of Short name for network C1
Z bytes Short name for network contents (Octets 3 to n C1
of network name information element)
1 byte PLMN Additional Information tag ('80') O
1 byte Length of PLMN Additional Information C2
W bytes PLMN Additional Information (coded using one C2
of the UCS2 code options as defined in
TS 31.101 [11]).
C1: this field shall be present if the short name for network IEI is present
C2: this field shall be present if the PLMN Additional Information tag is
present
Unused bytes shall be set to 'FF'.
4.2.59 EFOPL (Operator PLMN List)

This EF contains a prioritised list of Location Area Information (LAI) or Tracking Area Identity (TAI) identities that
are used to associate a specific operator name contained in EFPNN or EFPNNI with the LAI/TAI. The ME shall use this EF
in association with the EFPNN in place of any network name stored within the ME's internal list and any network name
received when registered to the PLMN, as defined by TS 24.008 [9] or TS 24.301 [51]. The PLMN Network Name may
also be provided in a graphical format in EFPNNI. The ME shall use the text format or the graphical format or both to
display the service provider name according to the rules defined in section 4.2.89.

SFI: '1A'
Record length: X bytes, (X ≥ 8) Update activity: low
Access Conditions:
READ ALWAYS
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to 7 Location Area Identity/Tracking Area Identity M 7 bytes
8 PLMN Network Name Record Identifier M 1 byte
- Location Area Identity/Tracking Area Identity
Contents:
Location Area Information, this comprises of the MCC, MNC and LAC
Tracking Area Identity, this comprises of the MCC, MNC and TAC
Coding:
PLMN : according to TS 24.008 [9]/TS 24.301 [51]
A BCD value of 'D' in any of the MCC and/or MNC digits shall be used to indicate a "wild" value for that
corresponding MCC/MNC digit
LAC/TAC : according to TS 24.008 [9]/TS 24.301 [51]
3GPP
Release 15 79 3GPP TS 31.102 V15.21.0 (2018-0610)
Two values for the LAC/TAC are stored in order to allow a range of LAC/TAC values to be specified for a
given PLMN. A value of '0000' stored in bytes 4 to 5 and a value of 'FFFE' stored in bytes 6 to 7 shall be
used to indicate the entire range of LACs/TACs for the given PLMN. In the case where only a single
LAC/TAC value is to be specified then the value stored in bytes 4 to 5 shall be identical to the value stored
in bytes 6 to 7 for the given PLMN. If a range of LAC/TAC values are to be specified, then the value stored
in bytes 4 to 5 shall be the start of the LAC/TAC range and the value stored in bytes 6 to 7 shall be the end
of the LAC/TAC range for the given PLMN.
- PLMN Network Name Record Identifier
Contents:
Identifier of operator name to be displayed
Coding:
A value of '00' indicates that the name is to be taken from other sources, see TS 22.101 [24]
A value in the range '01' to 'FE' indicates the record number in EFPNN that shall be displayed as the registered
PLMN name. It also indicates the record number in EFPNNI that may be displayed as the registered PLMN
name icon.
NOTE: The intent of this file is to provide exceptions to the other sources of a network name. Care should be
taken not to introduce too many PLMN entries. An excessive number of entries could result in a longer
initialisation period.
4.2.60 EFMBDN (Mailbox Dialling Numbers)

This EF contains dialling numbers to access mailboxes associated with Voicemail, Fax, Electronic Mail and other
messages. It may also contain associated alpha-tags for each supported mailbox. Each dialling number shall be
associated with a message waiting indication group type using EFMBI (see TS 23.038 [5] for message waiting indication
group types).

Access Conditions:
READ PIN
UPDATE PIN/ADM
DEACTIVATE ADM
ACTIVATE ADM

X+3 to X+12 Dialling Number/SSC contents M 10 bytes
X+14 Extension 6 Record Identifier M 1 byte
that extension records are stored in the EFEXT6 and with the exception that Capability/Configuration parameters are
stored in the EFCCP2.
EFADN.
3GPP
Release 15 80 3GPP TS 31.102 V15.21.0 (2018-0610)

This EF contains extension data of an MBDN (see MBDN in 4.2.60).

Access Conditions:
READ PIN
UPDATE PIN/ADM
DEACTIVATE ADM
ACTIVATE ADM

For contents and coding, see clause 4.4.2.4 (EFEXT1).
4.2.62 EFMBI (Mailbox Identifier)

This EF contains information to associate mailbox dialling numbers in EFMBDN with a message waiting indication group
type and subscriber profile (as defined in TS 23.097 [36]). A message waiting indication group type may either be
Voicemail, Fax, Electronic Mail, Other or Videomail (as defined in TS 23.040 [6]).
This EF contains as many records as there are subscriber profiles (shall be record to subscriber profile). Each record
contains references to mailbox dialling numbers in EFMBDN (one reference for each message waiting indication group
type).

Record length: X bytes, (X ≥ 4) Update activity: low
Access Conditions:
READ PIN
UPDATE PIN/ADM
DEACTIVATE ADM
ACTIVATE ADM

1 Mailbox Dialling Number Identifier – Voicemail M 1 byte
2 Mailbox Dialling Number Identifier – Fax M 1 byte
3 Mailbox Dialling Number Identifier – Electronic M 1 byte
Mail
4 Mailbox Dialling Number Identifier – Other M 1byte
5 Mailbox Dialling Number Identifier – Videomail O 1 byte
- Mailbox Dialling Number Identifier (message waiting group type = Voicemail, Fax, Electronic Mail, Other or
Videomail).
Contents:
Identifies the mailbox dialling number to be associated with message waiting type.
Coding:
'00' – no mailbox dialling number associated with message waiting indication group type.
'xx' – record number in EFMBDN associated with message waiting indication group type.
4.2.63 EFMWIS (Message Waiting Indication Status)

3GPP
Release 15 81 3GPP TS 31.102 V15.21.0 (2018-0610)
This EF contains the status of indicators that define whether or not a Voicemail, Fax, Electronic Mail, Other or
Videomail message is waiting (as defined in TS 23.040 [6]). The ME uses the status after re-activation to determine
whether or not to display the respective message-waiting indication on its display.
This EF contains as many records as there are subscriber profiles (shall be record to subscriber profile) as defined in
TS 23.097 [36] for MSP.
Identifier: '6FCA' Structure: Linear fixed Optional

Record length: X bytes, (X ≥ 5) Update activity: high
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 Message Waiting Indicator Status M 1 byte
2 Number of Voicemail Messages Waiting M 1 byte
3 Number of Fax Messages Waiting M 1 byte
4 Number of Electronic Mail Messages Waiting M 1 byte
5 Number of Other Messages Waiting M 1 byte
6 Number of Videomail Messages waiting O 1 byte
Message Waiting Indication Status

Contents:
Indicates the status of the message-waiting indication.
Coding:
The indicator status for each indicator type is 1 bit long and set as follows:
bit = 1: Set Indication Active
bit = 0: Set Indication Inactive
b8 b7 B6 b5 b4 b3 b2 b1
Message Waiting Indication Status – Voicemail

Message Waiting Indication Status – Fax
Message Waiting Indication Status – Electronic Mail
Message Waiting Indication Status – Other
Message Waiting Indication Status - Videomail
RFU
Number of Voicemail Messages Waiting

Contents:
Contains the number of voicemail messages waiting (see TS 23.040 [6]).
Coding:
Binary.
Number of Fax Messages Waiting

Contents:
Contains the number of fax messages waiting (see TS 23.040 [6]).
Coding:
Binary.
Number of Electronic Mail Messages Waiting

Contents:
Contains the number of electronic mail messages waiting (see TS 23.040 [6])
Coding:
Binary.
Number of Other Messages Waiting

Contents:
3GPP
Release 15 82 3GPP TS 31.102 V15.21.0 (2018-0610)
Contains the number of other messages waiting (see TS 23.040 [6]).
Coding:
Binary.
Number of Videomail Messages Waiting

Contents:
Contains the number of Videomail messages waiting (see TS 23.040 [6]).
Coding:
Binary.
4.2.64 EFCFIS (Call Forwarding Indication Status)

This EF contains the status of indicators that are used to record whether call forward is active. The ME uses the status
after re-activation to determine whether or not to display the respective Call Forwarding indicator on its display.
This EF contains as many records as there are subscriber profiles (shall be record to subscriber profile) as defined in
TS 23.097 [36] for MSP.
Identifier: '6FCB' Structure: Linear Fixed Optional

Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 MSP number M 1 byte
2 CFU indicator status M 1 byte
3 Length of BCD number M 1 byte
4 TON and NPI M 1 byte
5 to 14 Dialling Number M 10 bytes
15 Capability/Configuration2 Record Identifier M 1 byte
16 Extension 7 Record Identifier M 1 byte
NOTE: For contents and coding of data items not detailed below, see the respective data items of EF ADN (clause
4.4.2.3), Capability/Configuration2 Record Identifier and Extension 7 Record Identifier.
MSP number:
Contents:
The MSP number contains the Profile Identity of the subscriber profile. The Profile Identity shall be between 1and 4
as defined in TS 23.097 [36] for MSP.
Coding:
Binary.
CFU indicator status:
Contents:
Indicates the status of the call forward unconditional indicator. Service code = 21 (CFU) or 002 (for CFU part of all
CF), as defined in TS 22.030 [4]
Coding:
The indicator status for each indicator type is 1 bit long and is set as follows:
bit = 1: Set indication active
bit = 0: Set indication inactive.
3GPP
Release 15 83 3GPP TS 31.102 V15.21.0 (2018-0610)
B8 b7 b6 b5 b4 b3 b2 b1
CFU indicator status – Voice

MMI Service code = 11 (Telephony), as defined in TS
22.030 [4]).
CFU indicator status – Fax
MMI Service code = 13 (Fax), as defined in TS 22.030
[4]).
CFU indicator status – All data teleservices
MMI Service code = 12 (Data (Teleservices)), as
defined in TS 22.030 [4]).
CFU indicator status – SMS
MMI Service code = 16 (SMS), as defined in TS 22.030
[4].
CFU indicator status – All bearer services
MMI Service code = 20 (Data (Bearer Services)), as
defined in TS 22.030 [4]).
RFU (e.g. for other MMI service codes)

This EF contains extension data of a CFIS (Call Forwarding Indication Status - see 4.2.64).
Identifier: '6FCC' Structure: linear fixed Optional

Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

4.2.66 EFSPDI (Service Provider Display Information)

This EF contains information regarding the service provider display i.e. the service provider PLMN list.
Identifier: '6FCD' Structure: transparent Optional

SFI: '1B'
File size: x bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to x TLV object(s) containing Service Provider M x bytes
information
Tag Value Tag Description

'A3' Service provider display information Tag
'80' Service provider PLMN list tag
The service provider display information object is a constructed TLV coded according to ISO/IEC 8825-1 [35].
3GPP
Release 15 84 3GPP TS 31.102 V15.21.0 (2018-0610)
- Service provider PLMN list

Contents:
This TLV contains a list of n PLMNs in which the Service Provider Name shall be displayed, as defined in
clause 4.2.12 (EFSPN).
Coding:
Description M/O Length

Service provider PLMN list tag M 1 byte
Length (see note) M x bytes
1st PLMN entry M 3 bytes
2nd PLMN entry O 3 bytes
3rd PLMN entry O 3 bytes
…
nth PLMN entry O 3 bytes
Note: the length is 3*n bytes, where n denotes the number of PLMN entries. The length can
be coded on one or more bytes according to ISO/IEC 8825-1 [35].
Each PLMN is coded as follows:

Mobile Country Code (MCC) followed by the Mobile Network Code (MNC) according to TS 24.008 [9].
In case a PLMN entry is not used, it shall be set to 'FF FF FF'.
4.2.67 EFMMSN (MMS Notification)

This EF contains information in accordance with TS 23.140 [38] and X.S0016-000-A v1.0 [45] comprising MMS
notifications (and associated parameters) which have been received by the UE from the network. A 3GPP terminal
needs only to support the MMS implementation specified in TS 23.140 [38].
Identifier: ’6FCE’ Structure: Linear fixed Optional

Record length: 4+X bytes Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM
1 to 2 MMS Status M 2 bytes
3 MMS Implementation M 1 byte
4 to X+3 MMS Notification M X bytes
X+4 Extension file record number M 1 byte
- MMS Status
Content:
The status bytes contain the status information of the notification.
Coding:
b1 indicates whether there is valid data or if the location is free. B2 indicates whether the MMS notification has been read
or not. Bits b3-b4 of the first byte indicate the MM retrieval, MM rejection, or MM forwarding status, Bits b5-b8 of the
first byte and the entire second byte are reserved for future use.
First byte:
b8 b7 b6 b5 b4 b3 b2 b1
X X X 0 Free space
X X X 1 Used space
X X 0 1 Notification not read
3GPP
Release 15 85 3GPP TS 31.102 V15.21.0 (2018-0610)
X X 1 1 Notification read
0 0 X 1 MM not retrieved
0 1 X 1 MM retrieved
1 0 X 1 MM rejected
1 1 X 1 MM forwarded
Reserved for future use
Second byte:
b8 b7 b6 b5 b4 b3 b2 b1
Reserved for future use
- MMS Implementation
Contents:
The MMS Implementation indicates the used implementation type, e.g. WAP.
Coding:
Allocation of bits:
Bit number Parameter indicated
1 WAP implementation of MMS as defined in TS 23.140 [38]
2 Reserved for 3GPP2: M-IMAP implementation of MMS as defined in X.S0016-000-A v1.0 [45]
3 Reserved for 3GPP2: SIP implementation of MMS as defined in X.S0016-000-A v1.0 [45]
4-8 Reserved for future use
Bit value Meaning

0 Implementation not supported.
1 Implementation supported.
- MMS Notification
Contents:
The MMS Notification contains the MMS notification.
Coding:
The MMS Notification is coded according to the MMS Implementation as indicated in Byte 3.
Any unused byte shall be set to 'FF'.
- Extension file record number

Contents:
- extension file record number. This byte identifies the number of a record in the EFEXT8 containing extension data for the
notification information. The use of this byte is optional. If it is not used it shall be set to 'FF'.
Coding:
- binary.
3GPP
Release 15 86 3GPP TS 31.102 V15.21.0 (2018-0610)
4.2.68 EFEXT8 (Extension 8)

This EF contains extension data of a MMS Notification (Multimedia Messaging Service - see 4.2.67).
Identifier: '6FCF' Structure: linear fixed Optional

Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

2 to X+1 Extension data M X bytes
X+2 Identifier M 1 byte
The structure of this EF is identical to the structure of EFEXT1 (see clause 4.4.2.4).
- Record type.
Contents:
type of the record, see clause 4.4.2.4
Coding:
according to the "additional data" type
- Extension data.
Contents:
additional data (MMS notification extension)
Coding:
the first byte of the extension data gives the number of bytes of the remainder of the MMS notification in this record.
The following bytes contain the extension of the MMS notification.
- Identifier.
Contents:
identifier of the next extension record (in EXT8) to enable longer storage of information.
Coding:
record number of next record. 'FF' identifies the end of the chain.
4.2.69 EFMMSICP (MMS Issuer Connectivity Parameters)

This EF contains values for Multimedia Messaging Connectivity Parameters as determined by the issuer, which can be
used by the ME for MMS network connection. This file may contain one or more sets of Multimedia Messaging Issuer
Connectivity Parameters. The first set of Multimedia Messaging Issuer Connectivity Parameters is used as the default
set. Each set of Multimedia Messaging Issuer Connectivity Parameters may consist of one or more Interface to Core
Network and Bearer information TLV objects, but shall contain only one MMS implementation TLV object, one MMS
Relay/Server TLV object and one Gateway TLV object. The order of the Interface to Core Network and Bearer
information TLV objects in the MMS Connectivity TLV object defines the priority of the Interface to Core Network
and Bearer information, with the first TLV object having the highest priority.
3GPP
Release 15 87 3GPP TS 31.102 V15.21.0 (2018-0610)
Identifier: '6FD0' Structure: Transparent Optional

File Size: X1+…+ Xn bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to X1 MMS Connectivity Parameters TLV M X1 bytes
object
X1+1 to X1 + X2 MMS Connectivity Parameters TLV O X2 bytes
object
… …
X1+…+ Xn-1+1 to X1+…+ Xn MMS Connectivity Parameters TLV O Xn bytes
object
MMS Connectivity Parameters tags
Description Tag Value

MMS Connectivity Parameters Tag 'AB'
MMS Implementation Tag ‘80’
MMS Relay/Server Tag ‘81’
Interface to Core Network and Bearer Information Tag '82'
GatewayTag '83'
Reserved for 3GPP2: MMS Authentication Mechanism Tag '84'
Reserved for 3GPP2: MMS Authentication User Name Tag '85'
- MMS Connectivity Parameters contents
3GPP
Release 15 88 3GPP TS 31.102 V15.21.0 (2018-0610)
Description Value M/O Length (bytes)

MMS Connectivity Parameters Tag 'AB' M 1
Length Note 1 M Note 2
MMS Implementation Tag '80' M 1
Length 1 M 1
MMS Implementation Information -- M 1
MMS Relay/Server Tag '81' M 1
Length X1 M Note 2
MMS Relay/Server Address -- M X1
MMS Authentication Mechanism Tag '84' C1 1
Length X2 C1 Note 2
MMS Authentication Mechanism -- C1 X2
MMS Authentication User Name Tag '85' C1 1
Length X3 C1 Note 2
MMS Authentication User Name -- C1 X3
1st Interface to Core Network and '82' C2 1
Bearer Information Tag (highest priority)
Length Y1 C2 Note 2
1st Interface to Core Network and -- C2 Y1
Bearer information
2nd Interface to Core Network and '82' C2 1
Bearer Information Tag
Length Y2 C2 Note 2
2nd Interface to Core Network and -- C2 Y2
Bearer information
…
Nth Interface to Core Network and '82' C2 1
Bearer Information Tag (lowest priority)
Length Y3 C2 Note 2
Nth Interface to Core Network and -- C2 Y3
Bearer information
GatewayTag '83' O 1
Length Z O Note 2
Gateway Information -- O Z
Note 1: This is the total size of the constructed TLV object.
Note 2: The length is coded according to ISO/IEC 8825-1 [35].
C1: Reserved for 3GPP2: only present if M-IMAP or SIP indicated in tag 80.
C2: Only present if WAP is indicated in tag 80.
- MMS Implementation Tag '80'

See section 4.2.67 for contents and coding.
- MMS Relay/server Tag '81'

Contents:
The MMS relay/server contains the address of the associated MMS relay/server.
Coding:
The MMS relay/server address is coded according to the guideline provided in TS 23.140 [38].
- MMS Authentication Mechanism Tag '84'

Contents:
The MMS authentication mechanism contains the authentication mechanism used for M-IMAP and SIP.
Coding:
The MMS authentication mechanism is coded according to the guidelines provided in X.S0016-000-A v1.0 [45].
- MMS Authentication User Name Tag '85'

Contents:
The MMS Authentication User Name contains the authentication user name used for M-IMAP and SIP.
Coding:
The MMS authentication User Name is coded according to the guidelines provided in X.S0016-000-A v1.0 [45].
- Interface to Core Network and Bearer Information Tag '82'

Contents:
The Interface to Core Network and Bearer Information may contain the following information to set up the bearer:
Bearer, Address, Type of address, Speed, Call type, Authentication type, Authentication id, Authentication password.
3GPP
Release 15 89 3GPP TS 31.102 V15.21.0 (2018-0610)
Coding:
The coding is according to the guideline provided in TS 23.140 [38].
- Gateway Tag '83'

Contents:
The Gateway may contain the following information; Address, Type of address, Port, Service, Authentication type,
Authentication id and Authentication password.
Coding:
The coding is according to the guideline provided in TS 23.140 [38].
An Example for the coding of these parameters can be found in Annex J.2.
4.2.70 EFMMSUP (MMS User Preferences)

This EF contains values for Multimedia Messaging Service User Preferences, which can be used by the ME for user
assistance in preparation of mobile multimedia messages (e.g. default values for parameters that are often used).
Identifier: '6FD1' Structure: Linear Fixed Optional

Record Length: X bytes Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to X MMS User Preference TLV Objects M X bytes
MMS User Preference tags

MMS Implementation Tag '80'
MMS User preference profile name Tag '81'
MMS User Preference information Tag '82'
MMS User Preference information

MMS Implementation Tag '80' M 1
Length 1 M Note
MMS Implementation information -- M 1
MMS User preference profile name Tag '81' M 1
Length X M Note
MMS User profile name -- M X
MMS User Preference information Tag '82' M 1
Length Y M Note
MMS User Preference information -- M Y
Note: The length is coded according to ISO/IEC 8825-1 [35]
- MMS Implementation Tag '80'

For contents and coding see 4.2.67
- MMS User preference profile name Tag '81'

Contents:
Alpha tagging of the MMS user preference profile.
Coding:
this alpha-tagging shall use either:
3GPP
Release 15 90 3GPP TS 31.102 V15.21.0 (2018-0610)
- the SMS default 7-bit coded alphabet as defined in TS 23.038 [5] with bit 8 set to 0. The alpha identifier shall be left
justified.
Or:
- MMS User Preference information Tag '82'

Contents:
The following information elements may be coded; Sender Visibility, Delivery Report, Read-Reply, Priority, Time of
Expiry and Earliest Delivery Time.
Coding:
Depending upon the MMS implementation as indicated in Tag '80'.
An Example for the coding of these parameters can be found in Annex J.1.
4.2.71 EFMMSUCP (MMS User Connectivity Parameters)

If service n°52 and n°55 are "available", this file shall be present.
This EF contains values for Multimedia Messaging Connectivity Parameters as determined by the user, which can be
used by the ME for MMS network connection. This file may contain one or more sets of Multimedia Messaging User
Connectivity Parameters. Each set of Multimedia Messaging User Connectivity Parameters may consist of one or more
Interface to Core Network and Bearer information TLV objects, but shall contain only one MMS implementation TLV
object, one MMS Relay/Server TLV object and one Gateway TLV object. The order of the Interface to Core Network
and Bearer information TLV objects in the MMS Connectivity TLV object defines the priority of the Interface to Core
Network and Bearer information, with the first TLV object having the highest priority.
Identifier: '6FD2' Structure: Transparent Optional

File Size: X1+…+ Xn bytes Update activity: low
Access Conditions:
READ PIN
UPDATE PIN/PIN2
DEACTIVATE ADM
ACTIVATE ADM

1 to X1 MMS Connectivity Parameters TLV O X1 bytes
object
X1+1 to X1 + X2 MMS Connectivity Parameters TLV O X2 bytes
object
… …
X1+…+ Xn-1+1 to X1+…+ Xn MMS Connectivity Parameters TLV O Xn bytes
object
For the contents and coding see 4.2.69
4.2.72 EFNIA (Network's Indication of Alerting)

This EF contains categories and associated text related to the Network's indication of alerting in the MS service defined
in TS 22.101 [24].
3GPP
Release 15 91 3GPP TS 31.102 V15.21.0 (2018-0610)
Identifier: '6FD3' Structure: linear fixed Optional

Record length : X+1 bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 Alerting category M 1 byte
2 to X+1 Informative text M X bytes
- Alerting category
Contents:
category of alerting for terminating traffic.
Coding:
according to TS 24.008 [9]. Value 'FF' means that no information on alerting category is available.
- Informative text
Contents:
text describing the type of terminating traffic associated with the category.
Coding:
see the coding of the Alpha Identifier item of the EFADN. The maximum number of characters for this
informative text is indicated in TS 22.101 [24].
4.2.73 EFVGCS (Voice Group Call Service)

This EF contains a list of those VGCS group identifiers the user has subscribed to. The elementary file is used by the
ME for group call establishment and group call reception.

File size: 4n bytes, (1 n  50) Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to 4 Group ID 1 M 4 bytes
5 to 8 Group ID 2 O 4 bytes
: : : :
(4n-3) to 4n Group ID n O 4 bytes
- Group ID
Contents: VGCS Group ID, according to TS 23.003 [25]
Coding:
The VGCS Group ID is of a variable length with a maximum length of 8 digits. Each VGCS Group ID is
coded on four bytes, with each digit within the code being coded on four bits corresponding to BCD code.
3GPP
Release 15 92 3GPP TS 31.102 V15.21.0 (2018-0610)
If a VGCS Group ID of less than 8 digits is chosen, then the unused nibbles shall be set to 'F'. VGCS
Group ID Digit 1 is the most significant digit of the Group ID.
Byte 1:
b8 b7 b6 b5 b4 b3 b2 b1
LSB of Digit 1 of Group ID 1

:
:
MSB of Digit 1 of Group ID 1
:
:
Byte 2:
b8 b7 b6 b5 b4 b3 b2 b1

:
:
:
:
Byte 3:
b8 b7 b6 b5 b4 b3 b2 b1

:
:
:
:
Byte 4:
b8 b7 b6 b5 b4 b3 b2 b1

:
:
:
:
:
: etc........
3GPP
Release 15 93 3GPP TS 31.102 V15.21.0 (2018-0610)
Byte (4n-3) to 4n:
b8 b7 b6 b5 b4 b3 b2 b1
LSB of Digit 7 of Group ID n

:
:
MSB of Digit 7 of Group ID n
:
:
If storage for fewer than the maximum possible number n of VGCS Group Ids, is required, the excess
bytes shall be set to 'FF'.
4.2.74 EFVGCSS (Voice Group Call Service Status)

This EF contains the status of activation for the VGCS group identifiers. The elementary file is directly related to the
EFVGCS. This EF shall always be allocated if EFVGCS is allocated.

Access Conditions:
READ PIN
UPDATE PIN/ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to 7 Activation/Deactivation Flags M 7 bytes
Activation/Deactivation Flags
Contents: Activation/Deactivation Flags of the appropriate Group Ids

Coding: bit = 0 means - Group ID deactivated
bit = 1 means - Group ID activated
Byte 1:
b8 b7 b6 b5 b4 b3 b2 b1
Group ID 1
:
:
:
:
:
:
Group ID 8
etc : : : : : : : :
3GPP
Release 15 94 3GPP TS 31.102 V15.21.0 (2018-0610)
Byte 7:
b8 b7 b6 b5 b4 b3 b2 b1
Group ID 49
Group ID 50
b3=1
b4=1
b5=1
b6=1
b7=1
b8=1
4.2.75 EFVBS (Voice Broadcast Service)

This EF contains a list of those VBS group identifiers the user has subscribed to. The elementary file is used by the ME
for broadcast call establishment and broadcast call reception.

File size: 4n bytes, (1  n  50) Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to 4 Group ID 1 M 4 bytes
5 to 2 Group ID 2 O 4 bytes
: : : :
(4n-3) to 4n Group ID n O 4 bytes
Group ID
Contents: VBS Group ID, according to TS 23.003 [25]

Coding: The VBS Group ID is of a variable length with a maximum length of 8 digits. Each VBS Group
ID is coded on four bytes, with each digit within the code being coded on four bits corresponding
to BCD code. If a VBS Group ID of less than 8 digits is chosen, then the unused nibbles shall be
set to 'F'. VBS Group ID Digit 1 is the most significant digit of the Group ID.
Byte 1:
b8 b7 b6 b5 b4 b3 b2 b1

:
:
:
:
3GPP
Release 15 95 3GPP TS 31.102 V15.21.0 (2018-0610)
Byte 2:
b8 b7 b6 b5 b4 b3 b2 b1

:
:
:
:
Byte 3:
b8 b7 b6 b5 b4 b3 b2 b1

:
:
:
:
Byte 4:
b8 b7 b6 b5 b4 b3 b2 b1

:
:
:
:
:
: etc........
Byte (4n-3) to 4n:
b8 b7 b6 b5 b4 b3 b2 b1

:
:
:
:
If storage for fewer than the maximum possible number n of VBS Group Ids, is required, the excess bytes shall be set to
'FF'.
4.2.76 EFVBSS (Voice Broadcast Service Status)

3GPP
Release 15 96 3GPP TS 31.102 V15.21.0 (2018-0610)
This EF contains the status of activation for the VBS group identifiers. The elementary file is directly related to the
EFVBS. This EF shall always be allocated if EFVBS is allocated.

Access Conditions:
READ PIN
UPDATE PIN/ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to 7 Activation/Deactivation Flags M 7 bytes
Activation/Deactivation Flags
Contents: Activation/Deactivation Flags of the appropriate Group Ids

Coding: see coding of EFVGCSS
4.2.77 EFVGCSCA (Voice Group Call Service Ciphering Algorithm)

This EF contains the ciphering algorithm identifiers for each of the Master Group Key (V_Ki) of each VGCS group that
the user has subscribed to (defined in EFVGCS).
Identifier: '6FD4' Structure: transparent Optional

Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 VGCS Group ciphering algorithm identifier for M 1 byte
1st V_Ki of Group 1
2 VGCS Group ciphering algorithm identifier for M 1 byte
2nd V_Ki of Group 1
3 VGCS Group ciphering algorithm identifier for O 1 byte
1st V_Ki of Group 2
4 VGCS Group ciphering algorithm identifier for O 1 byte
2nd V_Ki of Group 2
: : : :
2n-1 VGCS Group ciphering algorithm identifier for O 1 byte
1st V_Ki of Group n
2n VGCS Group ciphering algorithm identifier for O 1 byte
2nd V_Ki of Group n
3GPP
Release 15 97 3GPP TS 31.102 V15.21.0 (2018-0610)
Ciphering Algorithm Identifier:
Contents: Ciphering Algorithm identifier for the specified Master Group Key of each Voice Call Group
Coding:
Value
‘00’ no ciphering
‘01’ ciphering with algorithm GSM A5/1
‘08’ to ‘FF’ RFU
4.2.78 EFVBSCA (Voice Broadcast Service Ciphering Algorithm)

This EF contains the ciphering algorithm identifiers for each of the Master Group Key (V_Ki) of each VBS group that
the user has subscribed to (defined in EFVBS).

Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 VBS Group ciphering algorithm identifier for 1st M 1 byte
V_Ki of Group 1
2 VBS Group ciphering algorithm identifier for 2nd M 1 byte
V_Ki of Group 1
3 VBS Group ciphering algorithm identifier for 1st O 1 byte
V_Ki of Group 2
4 VBS Group ciphering algorithm identifier for 2nd O 1 byte
V_Ki of Group 2
: : : :
2n-1 VBS Group ciphering algorithm identifier for 1st O 1 byte
V_Ki of Group n
2n VBS Group ciphering algorithm identifier for 2nd O 1 byte
V_Ki of Group n
Ciphering Algorithm Identifier:
Contents: Ciphering Algorithm identifier for the specified Master Group Key of each Voice Broadcast
Group
Coding: See coding of EFVGCSCA
4.2.79 EFGBABP (GBA Bootstrapping parameters)

This EF contains the AKA Random challenge (RAND) and Bootstrapping Transaction Identifier (B-TID) associated
with a GBA bootstrapping procedure.
3GPP
Release 15 98 3GPP TS 31.102 V15.21.0 (2018-0610)

File length: L+X+N+3 bytes Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 Length of RAND (X) M 1 byte
2 to (X +1) RAND M X bytes
X+2 Length of B-TID (L) M 1 byte
(X+3) to (X+2+L) B-TID M L bytes
X+L+3 Length of key lifetime M 1 byte
(X+L+4) to Key lifetime M N bytes
(X+L+N+3)
Length of RAND
Contents: number of bytes, not including this length byte, of RAND field
RAND
Contents: Random challenge used in the GBA_U bootstrapping procedure.

Coding: as defined in TS 33.103 [13]
Length of B-TID
Contents: number of bytes, not including this length byte, of B-TID field
B-TID
Content: Bootstrapping Transaction Identifier the GBA_U bootstrapped keys

Coding: As defined in TS 33.220 [42]
Length of key lifetime
Contents: number of bytes, not including this length byte, of key lifetime field
Key lifetime
Content: Lifetime of the GBA_U bootstrapped keys

4.2.80 EFMSK (MBMS Service Keys List)

A record of this EF contains the list of MBMS Service Keys (MSK) and associated parameters, which are related to an
MBMS Key Domain. There are up to two MSKs per Key Domain ID/Key Group ID pair, where the Key Group ID is
the Key Group part of the MSK ID as defined in TS 33.246 [43]. Two 4 byte MSK IDs stored within a record have the
same value for the 2 byte Key Group part.
3GPP
Release 15 99 3GPP TS 31.102 V15.21.0 (2018-0610)

Record length: 8n+4 bytes, (n ≥ 2) Update activity: high
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to 3 Key Domain ID M 3 bytes
4 Number of stored MSK IDs and M 1 byte
corresponding TS
5 to 8 1st MSK ID M 4 bytes
9 to 12 1st Time Stamp Counter (TS) M 4 bytes
13 to 16 2nd MSK ID M 4 bytes
17 to 20 2nd Time Stamp Counter (TS) M 4 bytes
: : : :
8(n-1)+5 to 8n nth MSK ID O 4 bytes
(See Note)
8n+1 to 8n+4 nth Time Stamp Counter (TS) C 4 bytes
(See Note)
Note: In the current version of the specification, these bytes are RFU.
Key Domain ID:
Content: Identifier of the Domain of the BM-SC providing MBMS Service.

Number of stored MSK IDs and corresponding TS:

Content: Number of stored MSK IDs and corresponding Time Stamp counter (TS) within the record, as defined in
TS 33.246 [43]. This number shall not exceed the maximum limit of MSK IDs fixed in TS 33.246 [43] (e.g if the
maximum number of MSK IDs is 2, then this byte may only take the following values: '00', '01', '02').
Coding: binary.
MSK ID:
Content: Identifier of MBMS Service Key (MSK) within a particular Key Domain.
Time Stamp Counter (TS):
Content: Counter for MIKEY replay protection in MTK delivery. Each counter is associated with a
particular MSK.
Any unused bytes shall be set to 'FF'.
4.2.81 EFMUK (MBMS User Key)

This EF contains the identifier of the MBMS User Key (MUK) that is used to protect the transfer of MBMS Service
Keys (MSK). The file also contains the Time Stamp Counter associated with the MUK, which is used for Replay
Protection in MSK transport messages. This EF shall not contain MUK IDs with the same Idi part.
3GPP
Release 15 100 3GPP TS 31.102 V15.21.0 (2018-0610)

Record length: Z bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM
Bytes Description M/O Bytes

1 to Z MBMS User Key TLV objects M 1 to Z
MBMS User Key tags

MUK ID Tag 'A0'
Time Stamp Counter Tag '81'
MBMS User Key information

MUK ID Tag 'A0' M 1
Length X M Note
MUK Idr Tag '80' M 1
Lenght A M Note
MUK Idr value -- M A
MUK Idi Tag '82' M 1
Lenght W M Note
MUK Idi Value - M W
Time Stamp Counter Tag '81' M 1
Length Y M Note
Time Stamp Counter value -- M Y
- MUK ID Tag 'A0'. This constructed data object consists of the Idr, and the Idi
- Idr Tag '80'
Content:
Idr part of MBMS User Key (MUK).
Coding:
As defined in TS 33.246 [43]
- Idi Tag '82'
Content:
Idi part of MBMS User Key (MUK).
Coding:
- Time Stamp Counter Tag '81'

Content:
Counter for MIKEY replay protection in MSK delivery. The counter is associated with the particular MUK. The
length value is defined in TS 33.246 [43].
Coding:
3GPP
Release 15 101 3GPP TS 31.102 V15.21.0 (2018-0610)
4.2.82 Void
4.2.83 EFGBANL (GBA NAF List)

This EF contains the list of NAF_ID and B-TID associated to a GBA NAF derivation procedure.
Identifier: '6FDA' Structure: Linear fixed Optional

Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to Z NAF Key Identifier TLV objects M Z bytes
NAF Key Identifier tags

NAF_ID Tag '80'
B-TID Tag '81'
NAF Key Identifier information

NAF_ID Tag '80' M 1
Length X M Note
NAF_ID value -- M X
B-TID Tag '81' M 1
Length Y M Note
B-TID value -- M Y
- NAF_ID Tag '80'

Contents:
Identifier of Network Application Function used in the GBA_U NAF Derivation procedure.
Coding:
- B-TID Tag '81'

Content:
Bootstrapping Transaction Identifier of the GBA_U bootstrapped key
Coding:
Unused bytes shall be set to 'FF'
4.2.84 EFEHPLMN (Equivalent HPLMN)

This EF contains the coding for n EHPLMNs. The usage of EHPLMN is defined in TS 23.122 [31]. This data field may
contain the HPLMN code derived from the IMSI as an EHPLMN entry.
3GPP
Release 15 102 3GPP TS 31.102 V15.21.0 (2018-0610)

SFI: '1D'
File size: 3n, (n 1) Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to 3 1st EHPLMN (highest priority) M 3 bytes
4 to 6 2nd EHPLMN O 3 bytes
: :
(3n-2) to (3n) nth EHPLMN (lowest priority) O 3 bytes
- EHPLMN
Contents:
Coding:
Unused entries shall be set to 'FF FF FF'
4.2.85 EFEHPLMNPI (Equivalent HPLMN Presentation Indication)

If service n°71 and service n°73 are "available", this file shall be present.
This EF contains an indication to the ME for the presentation of the available EHPLMN(s). The usage of the EHPLMN
presentation indication is defined in TS 23.122 [31].
Identifier: '6FDB' Structure: transparent Optional

Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 EHPLMN Presentation Indication M 1 byte
- EHPLMN Presentation Indication:

Contents:
EHPLMN display mode
Coding:
- '00' - No preference for the display mode
- '01' - Display the highest-priority available EHPLMN only
- '02' - Display all the available EHPLMNs
- All other values are RFU
4.2.86 EFLRPLMNSI (Last RPLMN Selection Indication)

This EF contains an indication to the ME for the selection of the RPLMN or the home network at switch on, or
following recovery from lack of coverage. The usage of the Last RPLMN Selection Indication is defined in
TS 23.122 [31].
3GPP
Release 15 103 3GPP TS 31.102 V15.21.0 (2018-0610)
Identifier: '6FDC' Structure: transparent Optional

Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 Last RPLMN Selection Indication M 1 byte
- Last RPLMN Selection Indication:

Contents:
Last RPLMN Selection Indication
Coding:
- '00' - The UE shall attempt registration on the last RPLMN at switch-on or recovery from out-of-coverage as
described in TS 23.122 [31]
- '01' - The UE shall attempt registration either on the HPLMN or the last RPLMN at switch-on or recovery from out-
of-coverage as described in TS 23.122 [31]
4.2.87 EFNAFKCA (NAF Key Centre Address)

This EF contains one or more NAF Key Centre 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.
Identifier: '6FDD' Structure: Linear fixed Optional

Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to Z NAF Key Centre TLV object M Z bytes
NAF Key Centre tags

NAF Key Centre address Tag '80'
NAF Key Centre information

NAF Key Centre address Tag '80' M 1
Length X M Note
NAF Key Centre address value -- M X
Note: The length is coded according to ISO/IEC 8825-1 [35].
- NAF Key Centre Address value (Tag '80')
Contents:
Fully qualified Domain Name (FQDN) of the NAF Key Centre used in the Local Key Establishment
procedures (see TS 33.110 [47]).
3GPP
Release 15 104 3GPP TS 31.102 V15.21.0 (2018-0610)
Coding:
Encoded to an octet string according to UTF-8 encoding rules as described in IETF RFC 3629 [48].
4.2.88 EFSPNI (Service Provider Name Icon)

This EF may contain one or several links to the service provider name icon. When more than one link is available, 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). The requirements for
the display by the ME are defined in section 4.2.12.
Identifier: '6FDE' Structure: transparent Optional

File Size: X bytes Update activity: low
Access Conditions:
READ ALWAYS
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to X Icon TLV object(s) M X bytes
This file may contain one or several service provider name Icon TLV object(s). The coding of the service provider
name Icon TLV objects is described hereafter:
Length Description Value Status

1 byte Icon Tag (See Note 1) -- M
1 byte Length (see Note 2) Y+1 M
1 byte Icon Qualifier -- M
Y bytes Icon Link -- M
Note 1: The tag value indicates the type and format of the Icon Link that is provided in the TLV value
field (e.g. Tag '80' indicates that the Icon link is a URI, while Tag '81' indicates that the Icon Link is the
record number of the corresponding image in EFIMG).
Note 2: coded according to ISO/IEC 8825-1 [35].
- Icon Tag
Contents: Tag value.
- When the Icon Link is an URI, the Tag value shall be set to '80'.
- When the Icon Link is a pointer to the record number of the corresponding image in EFIMG, the Tag value
shall be set to '81'.
- All other values are RFU.
Coding: binary.
- Icon Qualifier
Contents: The icon qualifier indicates to the ME how the icon shall be used.
- '01' = icon is self-explanatory, i.e. if displayed, it replaces the corresponding name in text format.
- '02' = icon is not self-explanatory, i.e. if displayed, it shall be displayed together with the corresponding
name in text format.
Coding: binary.
- Icon Link
Contents: Link to the icon. This link shall point to a UICC resource.
Coding:
3GPP
Release 15 105 3GPP TS 31.102 V15.21.0 (2018-0610)
- When the Tag value indicates an URI (i.e. Tag = '80') , the Icon Link shall be encoded to an octet string
according to UTF-8 encoding rules as described in IETF RFC 3629 [48] (e.g.
http://127.0.0.1:3516/pub/files/spng.jpg).
- When the Tag value indicates that the Icon Link contains the record number of the corresponding image in
EFIMG (i.e. Tag = '81'), the Icon Link shall be encoded in binary.
4.2.89 EFPNNI (PLMN Network Name Icon)

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).
Identifier: '6FDF' Structure: linear fixed Optional

Record length: X bytes Update activity: low
Access Conditions:
READ ALWAYS
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to X Icon TLV object(s) M X bytes
Each record may contain one or several PLMN network name Icon TLV object(s). The coding of the Icon TLV
object(s) is described in EFSPNI.
4.2.90 EFNCP-IP (Network Connectivity Parameters for USIM IP connections)

This EF contains the network activation parameters to be used by the ME for establishing a data channel (e.g. PDP
context activation) for UICC remote IP connectivity as described in ETSI TS 102 483 [50].
Each record contains a network connectivity parameters set. A network connectivity parameters set may comprise an
Access Point Name, a Login and Password of the Access Point Name, a Data Destination Address Range and the
Bearer Description. The priority order of the different Network Connectivity Parameters sets is the same as the order of
the record numbers.
Each network connectivity parameters set provides a condition and the network connectivity parameters to be used
when this condition is met:
- The network activation parameters present in a record shall be associated with this Data Destination Address
Range in the same record (i.e. if a record contains a Data Destination Address Range, all IP packets that are sent
by the UICC to any network destination address belonging to this Address Range shall transit through a network
connection established using the parameters provided in that record).
Note: A Data Destination Address Range TLV with a zero length prefix matches all addresses of the
address type.
In a record, if the Access Point Name has a value part, the associated Login and Password may be provided. If
supported by the ME, the Login and Password may be used for Access Point Name authentication. If only the Login is
present, the ME shall use its default Password configuration if any. If the Login and Password are not present, the ME
shall use its default Login/Password configuration if any. If no authentication is requested, the Login and Password
shall be ignored. The Password TLV can only be provided in a record if a Login TLV is provided in the same record.
In any record, if the Access Point Name has no value part, the ME may use its default Access Point Name or the default
subscription value together with the other network connectivity parameters of that record.
3GPP
Release 15 106 3GPP TS 31.102 V15.21.0 (2018-0610)
When present, the Bearer Description TLV provides recommended values for parameters that the ME should use to
establish the data link for UICC remote IP connections. However if the ME or network does not support these values,
the ME selects the most appropriate values.
Structure of EFNCP-IP
Identifier: '6FE2' Structure: linear fixed Optional

Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to M Data Destination Address Range TLV M M bytes
M+1 to M+N Access Point Name TLV M N bytes
M+N+1 to Login TLV C O bytes
M+N+O
M+N+O+1 to Password TLV C P bytes
M+N+O+P
M+N+O+P+1 Bearer description TLV C Q bytes
to
M+N+O+P+Q
- Data Destination Address Range TLV

Contents: the data destination address or the range of data destination addresses.
Coding: the coding of the Data Destination Address Range TLV object is described hereafter.

1 byte Data Destination Address Range Tag 83 M
1 byte Length (see note1) X M
1 byte Type of Address -- M
1 byte Prefix length (in bits) '00' to M
'20' for
IPv4
'00' to
'80' for
IPv6
0 to 16 Prefix --
bytes
- Type of Address
Contents: the type of data destination address range.
Coding:
- '21' = IPv4 address range;
- '57' = IPv6 address range;
- Other values are RFU.
- Prefix length
Contents: the number N of valid bits of the prefix of the address range. A prefix length of zero denotes
the default "all IP addresses" range.
Coding: binary
- Prefix
3GPP
Release 15 107 3GPP TS 31.102 V15.21.0 (2018-0610)
Contents: Prefix, i.e. the leftmost bits of the address range. All addresses where the leftmost N bits match
the prefix belong to the address range.
Coding:
- the leftmost N bits encode the prefix of the address range. If N is not an integer multiple of 8, the
prefix is right padded with zeroes to the next octet boundary.
- Access Point Name TLV

Contents: Access Point Name provides information to the ME necessary to identify the Gateway entity which
provides interworking with an external packet data network.
Coding: the coding of the Access Point Name TLV object is described hereafter. The Access Point Name
Value is coded as defined in TS 23.003 [25].

1 byte Access Point Name Tag 80 M
1 byte Length (see note 1) W M
W bytes Access Point Name Value -- M
- Login TLV
Contents: the login of the Access Point Name.
Coding: the coding of the Login TLV object is described hereafter. The Login Value is coded as for SMS Data
coding scheme defined in TS 23.038 [5]. Parts of the data coding scheme other than the character set
indication shall be ignored.

1 byte Login Tag 81 M
1 byte Length (see note 1) X M
X bytes Login Value -- M
- Password TLV
Contents: the password of the Access Point Name.
Coding: the coding of the Password TLV object is described hereafter. The Password Value is coded as for
SMS Data coding scheme defined in TS 23.038 [5]. Parts of the data coding scheme other than the
character set indication shall be ignored.

1 byte Password Tag 82 M
1 byte Length (see note 1) Y M
Y bytes Password Value -- M
-
- Bearer Description TLV
Contents: bearer description.
Coding: the coding of the Bearer Description TLV object is described hereafter. The Bearer Description Value
is encoded as the value part of the "Bearer description" TLV data object defined in TS 31.111 [12].

1 byte Bearer Description Tag 84 M
1 byte Length (see note 1) Z M
Z bytes Bearer Description Value -- M
Any unused bytes shall be set to 'FF'.
3GPP
Release 15 108 3GPP TS 31.102 V15.21.0 (2018-0610)
4.2.91 EFEPSLOCI (EPS location information)

This EF contains the following EPS location information:
- Globally Unique Temporary Identifier (GUTI);

- Last visited registered Tracking Area Identity (TAI);
- EPS update status.
Identifier: '6FE3' Structure: transparent Optional

SFI: '1E'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 12 GUTI M 12 bytes
13 to17 Last visited registered TAI M 5 bytes
18 EPS update status M 1 byte
- GUTI.
Contents:
Globally Unique Temporary Identifier.
Coding:
as the GUTI part of the EPS mobile identity information element defined in TS 24.301 [51]. Byte 1
corresponds to "octet 2" of an EPS mobile identity information element containing a GUTI. Byte 12
corresponds to "octet 13" of an EPS mobile identity information element information element containing
a GUTI.
Byte 1: first byte of GUTI
b8 b7 b6 b5 b4 b3 b2 b1
MSB
- Last visited registered TAI

Contents:
Last visited registered Tracking Area Identity.
Coding:
as the content of the tracking area identity information element defined in TS 24.301 [51]. Byte 13
corresponds to "octet 2" of a tracking area identity information element. Byte 17 corresponds to "octet 6"
of a tracking area identity information element.
Byte 13: first byte of last visited registered TAI
b8 b7 b6 b5 b4 b3 b2 b1
MSB
3GPP
Release 15 109 3GPP TS 31.102 V15.21.0 (2018-0610)
- EPS update status.

Contents:
status of EPS update according to TS 24.301 [51].
Coding:
byte 18:
Bits: b3 b2 b1.
0 0 0 : UPDATED.
0 0 1 : NOT UPDATED.
0 1 0 : ROAMING NOT ALLOWED.
0 1 1 : reserved.
1 0 0 : reserved.
1 0 1 : reserved.
1 1 0 : reserved.
1 1 1 : reserved.
3GPP
Release 15 110 3GPP TS 31.102 V15.21.0 (2018-0610)
4.2.92 EFEPSNSC (EPS NAS Security Context)

This EF contains the EPS NAS Security context as defined in TS 33.401 [52]. This file shall contain only one record.

SFI: '18'
Record size: X bytes (X≥54) Update activity: high
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to X EPS NAS Security Context TLV Object M X bytes
EPS NAS Security Context tags

EPS NAS Security Context Tag 'A0'
EPS NAS Security Context information

EPS NAS Security Context Tag 'A0' M 1
Length (length of all subsequent data) Y M Note 1
Key set identifier KSIASME Tag '80' M 1
Length K M Note 1
Key set identifier KSIASME -- M K
ASME key (KASME) Tag '81' M 1
Length L M Note 1
ASME key (KASME) -- M L
Uplink NAS count Tag '82' M 1
Length M M Note 1
Uplink NAS count -- M M
Downlink NAS count Tag '83' M 1
Length N M Note 1
Downlink NAS count -- M N
Identifiers of selected NAS integrity and '84' M 1
encryption algorithms Tag
Length S M Note 1
Identifiers of selected NAS integrity and -- M S
encryption algorithms
Note 1: The length is coded according to ISO/IEC 8825-1 [35]
- Key set identifier KSIASME Tag '80'
Contents:
The ASME key set identifier as defined in TS 33.401 [52]. In this release the KSIASME is coded on 1 byte.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
KSIASME
3GPP
Release 15 111 3GPP TS 31.102 V15.21.0 (2018-0610)
- ASME key (KASME) Tag '81'
Contents:
The ASME Key as defined in TS 33.401 [52]. In this release a valid ASME key is coded on 32 bytes. The
ME shall treat any ASME key values stored in this EF as invalid if the ASME key set identifier indicates
that no ASME key is available or if the length indicated in the ASME key TLV is set to '00',
Coding:
The most significant bit of KASME is the most significant bit of the 1st byte of this TLV value field. The least
significant bit of KASME is the least significant bit of the last byte of this TLV value field.
- Uplink NAS count Tag '82'
Contents:
The uplink NAS count as defined in TS 33.401 [52]. In this release the Uplink NAS count is coded on 4
bytes.
Coding:
The most significant bit of the uplink NAS count is the most significant bit of the 1st byte of this TLV value
field. The least significant bit of the uplink NAS count is the least significant bit of the last byte of this
TLV value field.
- Downlink NAS count Tag '83'
Contents:
The downlink NAS count as defined in TS 33.401 [52]. In this release the downlink NAS count is coded on 4
bytes.
Coding:
The most significant bit of the downlink NAS count is the most significant bit of the 1st byte of this TLV
value field. The least significant bit of the downlink NAS count is the least significant bit of the last byte
of this TLV value field.
- Identifiers of selected NAS integrity and encryption algorithms Tag '84'
Contents:
The identifiers of selected NAS integrity and encryption algorithms as defined in TS 33.401 [52] and TS
24.301 [51]. In this release the identifiers of selected NAS integrity and encryption algorithms are coded
on 1 byte.
Coding:
as the content of the NAS security algorithms information element defined in TS 24.301 [51].
Byte 1 of this TLV value field: first byte of the NAS security algorithms information element
b8 b7 b6 b5 b4 b3 b2 b1
MSB
In order to mark the stored EPS NAS security context as invalid:

- the record bytes shall be set to 'FF', or
- the KSIASME is set to '07', or
- the length indicated in the ASME key TLV is set to '00'.
3GPP
Release 15 112 3GPP TS 31.102 V15.21.0 (2018-0610)
4.2.93 EFUFC (USAT Facility Control)

This EF contains data for USAT Facility Control related to AT commands for USAT (see TS 31.111 [12]).

Access Conditions:
READ ALW
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to X Facility list M X bytes
The facility list has the same format as the TERMINAL PROFILE defined in TS 31.111 [12].
By setting the corresponding bits to 1, the facility list defines facilities which can only be provided by the MT and
which are not allowed to be provided by the TE.
If a TERMINAL PROFILE is longer than the facility list, for the purpose of facility control, the exceeding bytes of the
TERMINAL PROFILE shall be compared according to the generic rules found in TS 31.111 [12].
4.2.94 EFNASCONFIG (Non Access Stratum Configuration)

If service n°96 is "available", this file shall be present. This EF contains some of the NAS configuration parameters
defined in TS 24.368 [65]. For each of these NAS configuration parameters, a parameter provided in EF NASCONFIG shall
take precedence over the corresponding parameter stored in the ME's non-volatile memory.

File size: Z bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
ACTIVATE ADM
DEACTIVATE ADM

1 to Z NAS configuration parameter TLV objects M Z bytes
NAS configuration parameter information
Description Value M/O/C Length (bytes)
3GPP
Release 15 113 3GPP TS 31.102 V15.21.0 (2018-0610)
NAS signalling priority Tag '80' O 1

Length L1 C Note 1
NAS signalling priority value -- C L1
NMO I Behaviour Tag '81' O 1
Length L2 C Note 1
NMO I Behaviour value -- C L2
Attach with IMSI Tag '82' O 1
Length L3 C Note 1
Attach with IMSI value -- C L3
Minimum Periodic Search Timer Tag '83' O 1
Length L4 C Note 1
Minimum Periodic Search Timer value -- C L4
Extended access barring Tag '84' O 1
Length L5 C Note 1
Extended access barring value -- C L5
Timer T3245 Behaviour Tag '85' O 1
Length L6 C Note 1
Timer T3245 Behaviour value -- C L6
Override NAS signalling low priority Tag '86' O 1
Length L7 C Note 1
Override NAS signalling low priority -- C L7
value
Override Extended access barring Tag '87' O 1
Length L8 C Note 1
Override Extended access barring value -- C L8
Fast First Higher Priority PLMN Search '88' O 1
Tag
Length L9 C Note 1
Fast First Higher Priority PLMN value -- C L9
E-UTRA Disabling Allowed for EMM '89' O 1
cause #15 Tag
Length L10 C Note 1
E-UTRA Disabling Allowed for EMM - C L10
cause #15 Value
SM_RetryWaitTime Tag '8A' O 1
Length L11 C Note 1
SM_RetryWaitTime value -- C L11
SM_RetryAtRATChange Tag '8B' O 1
Length L12 C Note 1
SM_RetryAtRATChange value -- C L12
Default_DCN_ID Tag '8C' O 1
Length L13 C Note 1
Default_DCN_ID value -- C L13
Exception Data Reporting Allowed Tag '8D' O 1
Length L14 C Note 1
Exception Data Reporting Allowed -- C L14
value
Note 1 : The length is coded according to ISO/IEC 8825-1 [35]

Note 2: C; if the Tag is present, this is mandatory.
- NAS signalling priority

Contents:
As described in TS 24.368 [65], used to determine the NAS signalling priority included in NAS messages.
Coding:
As defined for the NAS_SignallingPriority leaf in TS 24.368 [65].
- NMO I Behaviour
3GPP
Release 15 114 3GPP TS 31.102 V15.21.0 (2018-0610)
Content:
As described in TS 24.368 [65], indicates whether the "NMO I, Network Mode of Operation I" indication is
applied by the UE.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
b1 value to be interpreted as defined for the

NMO_I_Behaviour leaf in TS 24.368 [65].
RFU (see TS 31.101 [11])
- Attach with IMSI

Content:
As described in TS 24.368 [65], indicates whether attach with IMSI is performed when moving to a non-
equivalent PLMN.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1

AttachWithIMSI leaf in TS 24.368 [65].
RFU (see TS 31.101 [11])
- Minimum Periodic Search Timer

Content:
As described in TS 24.368 [65], gives a minimum value in minutes for the timer T controlling the periodic
search for higher prioritized PLMNs. The content applies a minimum value that may override the value in file
EFHPPLMN (Higher Priority PLMN search period), as specified in TS 23.122 [31] clause 4.4.3.3.1.
Coding:
As defined for the MinimumPeriodicSearchTimer leaf in TS 24.368 [65].
- Extended access barring

Content:
As described in TS 24.368 [65], indicates whether the UE applies extended access barring.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
b1 value to be interpreted as defined for

ExtendedAccessBarring leaf in TS 24.368 [65].
RFU (see TS 31.101 [11])
- Timer T3245 Behaviour

Content:
As described in TS 24.368 [65], indicates whether the timer T3245 and the related functionality is used by the
UE.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
b1 value to be interpreted as defined for

Timer_T3245_Behaviour leaf in TS 24.368 [65].
RFU (see TS 31.101 [11])
- Override NAS signalling low priority
3GPP
Release 15 115 3GPP TS 31.102 V15.21.0 (2018-0610)
Contents:
As described in TS 24.368 [65], used to determine whether the NAS signalling priority included in NAS
messages can be overriden.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1

Override_NAS_SignallingLowPriority leaf in
TS 24.368 [65].
RFU (see TS 31.101 [11])
The Override NAS signalling low priority tag and the Override Extended access barring tag shall be set to the same
value, e.g., if the UE is configured to override the NAS signalling low access priority indicator, then it has also to be
configured to override Extended access barring (see 3GPP TS 23.401 [69] subclause 4.3.17.4).
- Override Extended access barring

Contents:
As described in TS 24.368 [65], used to determine whether the Extended access barring included in NAS
messages can be overriden.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1

Override_ ExtendedAccessBarring leaf in
TS 24.368 [65].
RFU (see TS 31.101 [11])
The Override Extended access barring tag and the Override NAS signalling low priority tag shall be set to the same
value, e.g., if the UE is configured to override Extended access barring, then it has also to be configured to override
the NAS signalling low access priority indicator (see 3GPP TS 23.401 [69] subclause 4.3.17.4).
- Fast First Higher Priority PLMN Search

Contents:
Determine whether the UE can perform Fast First Higher Priority PLMN Search upon selecting a VPLMN as
specified in 3GPP TS 23.122 [31].
Coding:
b8 b7 b6 b5 b4 b3 b2 b1

FastFirstHigherPriorityPLMNSearch leaf in
TS 24.368 [65].
RFU (see TS 31.101 [11])
- E-UTRA Disabling Allowed for EMM cause #15

Contents:
Determine whether the UE is allowed to disable the E-UTRA capability when it receives the Extended EMM IE
with value cause "E-UTRAN not allowed" as specified in 3GPP TS 24.301 [51].
Coding:
b8 b7 b6 b5 b4 b3 b2 b1

EUTRADisablingAllowedforEMMcause15 leaf in
3GPP TS 24.368 [65]
RFU (see TS 31.101 [11])
- SM_RetryWaitTime
Contents:
As described in TS 24.368 [65], provides a configured UE retry wait time value applicable when in HPLMN or
EHPLMN (see 3GPP TS 23.122 [31]) for controlling the UE session management retry behaviour when prior
session management request was rejected by the network with cause value #8, #27, #32, #33 as specified in
3GPP TS 24.008 [9] and 3GPP TS 24.301 [51].
3GPP
Release 15 116 3GPP TS 31.102 V15.21.0 (2018-0610)
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
bits b1 to b8 to be interpreted as defined for the

SM_RetryWaitTime leaf in 3GPP TS 24.368 [65]
- SM_RetryAtRATChange
Contents:
As described in TS 24.368 [65], indicates the UE's retry behaviour when in HPLMN or EHPLMN (see
3GPP TS 23.122 [31]) after inter-system change between S1 mode and A/Gb or Iu mode as specified in 3GPP
TS 24.008 [9] and 3GPP TS 24.301 [51].
Coding:
b8 b7 b6 b5 b4 b3 b2 b1

SM_RetryAtRATChange leaf in 3GPP TS 24.368 [65]
RFU (see TS 31.101 [11])
- Default_DCN_ID
Contents:
As described in 3GPP TS 24.368 [65], indicates the default DCN-ID which is provided by NAS to the lower
layers at establishment of the NAS signalling connection as specified in 3GPP TS 24.301 [51].
Coding:
As the DCN-ID value inside the DCN-ID IEI defined in TS 24.008 [9] clause 10.5.5.35.
- Exception Data Reporting Allowed
Contents:
As described in 3GPP TS 24.368 [65], for the UE in NB-S1 mode indicates whether the UE is allowed to use the
RRC establishment cause mo-ExceptionData, as specified in 3GPP TS 24.301 [51].
Coding:
b8 b7 b6 b5 b4 b3 b2 b1

ExceptionDataReportingAllowed leaf in
TS 24.368 [65].
RFU (see TS 31.101 [11])
If any of these NAS configuration parameters is neither included in EFNASCONFIG nor stored in the ME's non-volatile
memory, the default value as defined for the corresponding leaf in TS 24.368 [65] shall apply.
4.2.95 EFUICCIARI (UICC IARI)

As specified in TS 24.229 [63] a ME includes the list of IARIs for the IMS applications it intends to use when sending
an initial registration or when sending subsequent registrations to the IMS in the form of a SIP REGISTER request.
This EF contains a list of IARIs associated with active applications installed on the UICC that are included in the SIP
REGISTER request in accordance with the procedures of TS 24.229 [63].
NOTE: If this file is present in both the USIM and the ISIM, the file in the ISIM is used. It is assumed that the
presence of this file in the USIM when an ISIM is present on the UICC is an incorrect configuration of
the UICC.
3GPP
Release 15 117 3GPP TS 31.102 V15.21.0 (2018-0610)

Record length: X bytes. Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
ACTIVATE ADM
DEACTIVATE ADM

1 to X IARI TLV object M X bytes
IARI TLV object:

Contents:
- The content and coding is defined below.
Coding of the IARI TLV objects

1 byte IARI TLV TAG '80' M
1 byte Length of IARI Y M
Y bytes IARI value - M
- Coding:
IMS Application Reference Identifier: shall be coded as specified in TS 24.229 [63].
4.2.96 EFPWS (Public Warning System)

If service n°97 is "available", this file shall be present. This EF contains the configuration parameters for PWS, as
defined in TS 22.268 [68].
Identifier: '6FEC' Structure: transparent Optional

File size: 1+Z bytes Update activity: low
Access Conditions:
READ ALW
UPDATE ADM
ACTIVATE ADM
DEACTIVATE ADM

1 to Z+1 PWS configuration M 1+Z bytes
Contents:
Configuration for PWS
Coding:
First byte:
b8 b7 b6 b5 b4 b3 b2 b1
b1=0 process all PWS warning messages in HPLMN and

equivalent PLMNs
b1=1 ignore all PWS warning messages in HPLMN and
equivalent PLMNs
b2=0 process all PWS warning messages in VPLMNs
b2=1 ignore all PWS warning messages in VPLMNs
RFU (see TS 31.101 [11])
3GPP
Release 15 118 3GPP TS 31.102 V15.21.0 (2018-0610)
Successive bytes:
RFU (see TS 31.101 [11])
4.2.97 EFFDNURI (Fixed Dialling Numbers URI)

If service n° 2 and service n° 99 are "available", this file may be present.
This EF contains a list of FDN stored in URI address format. It may also contain an associated alpha-tagging.
Structure of EFFDNURI
Identifier: '6FED' Structure: linear fixed Optional
Record length: X+Y bytes Update activity: low

Access Conditions:
READ PIN
UPDATE PIN2
DEACTIVATE ADM
ACTIVATE ADM

1 to X URI Address M X bytes
X+1 to X+Y Alpha Identifier O Y bytes
- URI Address.
Content:
The URI Address associated to the referenced file Record number.
Coding:
Same as URI TLV data object in EFIMPU defined in TS 31.103 [64].
- Alpha Identifier.
Contents:
-Alpha-tagging of the associated dialling number.
Coding:
- the SMS default 7-bit coded alphabet as defined in TS 23.038 [5] with bit 8 set to 0. The alpha identifier
Or:
If FDN is enabled, the ME shall only allow outgoing calls using destination addresses which are in EF FDNURI, in addition
to the EFFDN entries, following the same principle as defined in the Fixed Number Dialling description in TS 22.101
[24] applied to URI addresses.
The EFFDNURI shall be enforced:
- If the dialling number introduced by the user is an URI
- Or if the dialling number has been stored in the UE as a URI
NOTE: The value of Y (the number of bytes in the alpha-identifier) may be different to the length denoted X in
EFFDN.
4.2.98 EFBDNURI (Barred Dialling Numbers URI)

This EF contains a list of BDN stored in URI address format. It may also contain an associated alpha-tagging.
3GPP
Release 15 119 3GPP TS 31.102 V15.21.0 (2018-0610)
Structure of EFBDNURI
Identifier: '6FEE' Structure: linear fixed Optional

Access Conditions:
READ PIN
UPDATE PIN2
DEACTIVATE ADM
ACTIVATE ADM

- URI Address.
Content:
Coding:
- Alpha Identifier.
Contents:
Alpha-tagging of the associated dialling number.
Coding:
or:
If BDN is enabled, the ME shall only allow outgoing calls using destination addresses which are neither in EF BDNURI nor
in the EFBDN entries, following the same principle as defined in the Barring of Dialled Numbers described in TS 22.101
[24] applied to URI addresses.
The EFBDNURI shall be enforced:
- If the dialling number introduced by the user is an URI
- Or if the dialling number has been stored in the UE as a URI
EFBDN.
4.2.99 EFSDNURI (Service Dialling Numbers URI)

This EF contains a list of SDN stored in URI address format. It may also contain an associated alpha-tagging. If the
service n°112 is available this file will contain the eCall test and reconfiguration URIs that are used by an UE in eCall
and normal service mode.
3GPP
Release 15 120 3GPP TS 31.102 V15.21.0 (2018-0610)
Structure of EFSDNURI
Identifier: '6FEF' Structure: linear fixed Optional

Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

- URI Address.
Content:
Coding:
- Alpha Identifier.
Contents:
Alpha-tagging of the associated dialling number.
Coding:
or:
If SDN is enabled, the ME shall perform SDN procedure using destination addresses which are in EF SDNURI or in EFSDN
entries, following the same principle as defined in the Service Dialling Numbers description in TS 22.101 [24] applied
to URI addresses.
EFSDN.
4.2.100 EFIWL (IMEI(SV) White Lists)

The file EFIWL stores ranges of values of IMEI(SV) to which the USIM is authorized to be paired as defined in this
specification.
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.
Identifier: '6FF0' Structure: linear fixed Optional

Record length: X+2 bytes (X>=16) Update activity: low
Access Conditions:
READ ADM
UPDATE ADM
ACTIVATE ADM
DEACTIVATE ADM

1 to X+2 IMEI or IMEISV range TLV object M X+2 bytes
- IMEI(SV) range of values TLV object.

The content and coding is defined below, where IMEI and IMEISV are defined in 3GPP TS 23.003[25]:
3GPP
Release 15 121 3GPP TS 31.102 V15.21.0 (2018-0610)
Coding of the IMEI Range TLV objects

1 byte Tag of Range of IMEI values: ‘80’ M
1 byte Length M
X bytes IMEI range of values that the USIM is C
authorized to be paired to (Detail 1)
Coding of the IMEISV Range TLV objects

1 byte Tag of Range of IMEISV values: ‘81’ M
1 byte Length M
X bytes IMEISV range of values that the USIM is C
authorized to be paired to (Detail 1)
Detail 1:
 Following the Length of the TLV, the range is defined as follow: [lower value][higher value].
 The authorized values of IMEI or IMEISV in an authorized range of values include the lower and higher
values of the specified range.
 To define an authorized individual IMEI or IMEISV, the lower value and the higher value of a range shall
both be equal to the value of the authorized IMEI or IMEISV.
 For an IMEI, the Check Digit is not considered in the evaluation
 For an IMEISV, the TAC|SNR part and the SVN part may be evaluated separately
Coding:
 IMEI and IMEISV coding is defined in 3GPP TS 23.003 [25] and 3GPP TS 24.008 [9]
 Unused nibble (IMEI) is set to 'F'
UICC OTA mechanism is used to update the file EF IWL stored in the USIM. This mechanism provides dynamic
management of the pairing to change the allowed combinations of USIM and MTC ME(s) by adding or removing
authorized IMEI(SV) ranges in the file EF IWL.
4.2.101 EFIPS (IMEI(SV) Pairing Status)

The EFIPS file stores the status of USAT Application Pairing checking.
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.
Structure of EFIPS
Identifier: '6FF1' Structure: Cyclic Optional

Access Conditions:
READ ALWAYS
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1-2 Status of the last pairing procedure (detail 1) O 2 bytes
3 Link to a record of EFIPD (detail 2) O 1 byte
4 Reserved for future use - 1 byte
3GPP
Release 15 122 3GPP TS 31.102 V15.21.0 (2018-0610)
Due to the frequency of the pairing procedure, it is recommended that this file contain at least 100 records.
Detail 1:
These 2 bytes contain the status of the last pairing procedure as defined below:
- If the pairing is successful then:
1. Byte 1 is the character "O"
2. Byte 2 is the character "K"
- If the pairing is not successful then:
1. Byte 1 is the character "K"
2. Byte 2 is the character "O"
- The characters are coded using the SMS default 7-bit coded alphabet as defined in TS 23.038 [5] with bit 8 set to
0.
Detail 2:
This byte contains a link to a record of EFIPD file:
- Unsigned integer coded from '01' to 'FE'
4.2.102 EFIPD (IMEI(SV) of Pairing Device)

The EFIPD contains the IMEI(SV) as defined in TS 23.003[25] that was used in the USAT Application Pairing
procedure.
Identifier: '6FF2' Structure: linear fixed Optional

Record length: X+2 bytes (X>=8) Update activity: high
Access Conditions:
READ ADM
UPDATE ADM
ACTIVATE ADM
DEACTIVATE ADM

1 to X+2 IMEI or IMEISV TLV object M X+2 bytes
- IMEI(SV) TLV object.

The content and coding is defined below, where IMEI and IMEISV are defined in 3GPP TS 23.003[25]:
Coding of the IMEI TLV object

1 byte Tag for an IMEI: '80' M
1 byte Length M
X bytes IMEI value used in the pairing procedure C
Coding of the IMEISV TLV object

1 byte Tag for an IMEISV: '81' M
1 byte Length M
X bytes IMEISV value used in the pairing procedure C
 Coding:IMEI and IMEISV coding is defined in 3GPP TS 23.003 [25] and 3GPP TS 24.008 [9]
 Unused nibble (IMEI) is set to 'F'
3GPP
Release 15 123 3GPP TS 31.102 V15.21.0 (2018-0610)
Unused bytes are set to 'FF'.
4.2.103 EFePDGId (Home ePDG Identifier)

This EF contains zero or more Home Evolved Packet Data Gateway (ePDG) Identifier data objects as defined in the
"Selection of the ePDG" UE procedure of 3GPP TS 24.302 [79].
Identifier: '6FF3' Structure: transparent Optional

File size: >X bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to X Home ePDG identifier TLV data object O X bytes
X+1 to Y Home ePDG identifier TLV data object O Y-X bytes
…
Home ePDG Identifier TLV data object
Contents:
- Address of Evolved Packet Data Gateway, in the format of a FQDN, an IPv4 address, or an IPv6 address.
Coding:
- The tag value of this Home ePDG Identifier TLV data object shall be '80'. The format of the data object is as
follows:
Field Length (bytes)

Tag 1
Length 1
Address Type 1
Home ePDG Address Address Length
Address Type: Type of the ePDG address.
- This field shall be set to the type of the ePDG address according to the following:
Value Address Type

'00' FQDN
'01' IPv4
'02' IPv6
All other values are
reserved
ePDG Address: Address of the Evolved Packet Data Gateway
Contents:
- This field shall be set to the address of the ePDG.
Coding:
- When the Address Type is set to '00', the corresponding ePDG FQDN Address shall be encoded to an octet
string according to UTF-8 encoding rules as specified in IETF RFC 3629 [48].
3GPP
Release 15 124 3GPP TS 31.102 V15.21.0 (2018-0610)
- When the Address Type is set to '01', the corresponding ePDG IPv4 Address is in octet 5 to octet 8 of the
Home ePDG Identifier TLV data object. Bit 8 of octet 5 represents the most significant bit of the IP address
and bit 1 of octet 8 the least significant bit.
- When the Address Type is set to '02', the corresponding ePDG IPv6 Address is in octet 5 to octet 20 of the
Home ePDG Identifier TLV data object. Bit 8 of octet 5 represents the most significant bit of the IP address
and bit 1 of octet 20 the least significant bit.
4.2.104 EFePDGSelection (ePDG Selection Information)

This EF contains Evolved Packet Data Gateway (ePDG) selection information for one or more PLMNs as defined in the
"Selection of the ePDG" UE procedure of 3GPP TS 24.302 [79].

Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to Z ePDG selection information TLV data object O Z bytes
The file contains one ePDG selection information TLV data object. The ePDG selection information TLV data object
contains a list of PLMNs which are preferred for ePDG selection. The list of PLMNs may include the HPLMN. For
each PLMN, it is indicated:
 the preference order (priority) given to ePDG of a PLMN and
 whether selection of an ePDG in such PLMN should be based on Tracking/Location Area Identity FQDN or on
Operator Identifier FQDN,
as specified in the "Selection of the ePDG" UE procedure of 3GPP TS 24.302 [79].
ePDG selection information TLV data object:

ePDG Selection Information Tag '80' M 1
Length 5n M Note
PLMN 1 -- C 3
ePDG Priority -- C 2
ePDG FQDN format '00' or '01' C 1
…
PLMN n -- C 3
ePDG Priority -- C 2
ePDG FQDN format indicator '00' or '01' C 1
PLMN:
Contents:
Coding:
- According to TS 24.008 [9].
3GPP
Release 15 125 3GPP TS 31.102 V15.21.0 (2018-0610)
- A BCD value of 'D' in any of the MCC and/or MNC digits shall be used to indicate a "wild" value for that
corresponding MCC/MNC digit.
- A value of 'DDDDDD' represents "any PLMN" value.
ePDG Priority:
Contents:
- The PLMN Priority represents the preference order given to ePDGs of a PLMN.
Coding:
- ePDG Priority value is coded as a 2-Byte integer.
ePDG FQDN format:
Contents:
- Indicates whether the selection of an ePDG in this PLMN should be based on Tracking/Location Area
Identity FQDN or on Operator Identifier FQDN (see 3GPP TS 24.302 [79]).
Coding:
- '00': Indicates that Operator Identifier FQDN format shall be used (see 3GPP TS 24.302 [79]).
- '01': Indicates that location based FQDN format shall be used (see 3GPP TS 24.302 [79]).
- Other values are RFU.
4.2.104a EFePDGIdEm (Emergency ePDG Identifier)

This EF contains zero or more Emergency Evolved Packet Data Gateway (ePDG) Identifier data objects.

File size: >X bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to X Emergency ePDG identifier TLV data object O X bytes
X+1 to Y Emergency ePDG identifier TLV data object O Y-X bytes
…
For coding, see EFePDGId
3GPP
Release 15 126 3GPP TS 31.102 V15.21.0 (2018-0610)
4.2.105 EFePDGSelectionEm (ePDG Selection Information for Emergency Services)

This EF contains Evolved Packet Data Gateway (ePDG) selection information for Emergency Services.

Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to Z ePDG selection information for Emergency O Z bytes
Services TLV data object
For coding, see EFePDGSelection
4.2.106 EFFromPreferred (From Preferred)

It shall be possible to define if the UE uses the From header field for the determination of the originating party identity
in the OIP service. For more detailed description see 3GPP TS 24.607 [86] subclause 4.5.2.12.
the UICC.
Identifier: '6FF7’ Structure: transparent Optional

File size: n bytes. Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
ACTIVATE ADM
DEACTIVATE ADM

1 Status M 1 bytes
- Status.
Contents:
Status byte indication if From header field is used or not.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
See 3GPP TS 24.417 [87] subclause 5.4.

RFU (see 3GPP TS 31.101 [3])
4.2.107 EFIMSConfigData (IMS Configuration Data)

This EF contains the IMS configuration data object as specified in 3GPP TS 24.167 [88].
3GPP
Release 15 127 3GPP TS 31.102 V15.21.0 (2018-0610)
For the structure, content and coding of this file, see EFIMSConfigData in 3GPP TS 31.103 [2]
4.2.108 EFTVCONFIG (TV Configuration)

This EF contains the configuration of the parameters related to TV service provided via a PLMN.
Identifier: '6FXX’ Structure: linear fixed Optional

Record size: Z bytes. Update activity: low
Access Conditions:
READ ALWAYS
UPDATE ADM
ACTIVATE ADM
DEACTIVATE ADM

1 to 3 PLMN identity M 3 bytes
54 to 4+X TMGI List TLV O X bytes
4+X+1 to EARFCN List TLV O Y bytes
4+X+1+Y
4+X+Y+2 to Z RFU C Z-X-Y-3 bytes
- PLMN
Contents:
As described in TS 24.117 [91], the identity of the PLMN for which the TV service configuration applies.
Coding:
According to TS 24.008 [9].
- TMGI List TLV

Contents:
List of TMGIs.
Coding:
TMGI List Tag 'A0' M 1
Length 9n M Note
ENTRY 1 --- C 9
ENTRY 2 --- C 9
...
ENTRY n --- C 9
NOTE: The length is coded according to ISO/IEC 8825-1 [35]
Each entry is coded:

1 to 6 TMGI M 6 bytes
7 to 8 USD File Id M 2 bytes
9 Service type M 1 byte
- TMGI
Contents:
The TMGI is defined as specified in TS 23.003 [25].

Coding:
TMGI is coded in 6 bytes:
- bytes 1 to 3: contain the MBMS Service ID, with the first digit coded in the most significant nibble of the
first byte, and the last digit coded in the least significant nibble of the third byte.
- bytes 4 to 6: contain the MCC and MNC values of the TMGI, coded as a PLMN according to 24.008 [9].
- USD File Id
3GPP
Release 15 128 3GPP TS 31.102 V15.21.0 (2018-0610)
Contents:
File identifier of the EFTVUSD inside the DFTV containing the User Service Description (USD).
Coding:
According to TS 31.101 [11]
- Service type
Contents:
Type of service for which the entry is valid.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
For Service Announcement service. This is equivalent

to an entry in the TMGIListForSA leaf in TS 24.117
[91].
For User service. This is equivalent to an entry in
the TMGIListForService leaf in TS 24.117 [91].
RFU
- EARFCN List TLV

Contents:
List of the E-UTRA ARFCN value of MBMS frequency.
Coding:
EARFCN List Tag 'A1' M 1
Length 4m M Note
EARFCN 1 --- C 4
EARFCN 2 --- C 4
...
EARFCN m --- C 4
Each EARFCN is coded in 4 bytes, as specified in 3GPP TS 36.101 [92].
4.2.109 EF3GPPPSDATAOFF (3GPP PS Data Off)

This EF contains information about which SIP and non SIP Services are 3GPP PS Data Off Exempt.

Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1-4 SIP and non-SIP Exempt Services M 4 bytes
- SIP and non-SIP Exempt Services.

Contents:
- the services that are 3GPP PS Data Off exempt as specified in 3GPP TS 22.011 [2].
Coding:
- each service that can be 3GPP PS Data Off exempt is coded on one bit.
Byte 1:
3GPP
Release 15 129 3GPP TS 31.102 V15.21.0 (2018-0610)
b8 b7 b6 b5 b4 b3 b2 b1

USSI_exempt leaf in TS 24.391 [94]
MMTEL_voice_exempt leaf in TS 24.275 [r95]
MMTEL_video_exempt leaf in TS 24.275 [r95]
SSP_XCAP_config_exempt leaf in TS 24.424 [93]
SMSoIP_exempt leaf in TS 24.167 [88]
Bearer_independent_protocol leaf of the
Exempted_service_list in TS 24.368 [96]
Device_management_over_PS leaf of the
Exempted_service_list in TS 24.368 [96]
RFU
Byte 2:
b8 b7 b6 b5 b4 b3 b2 b1

USSI_roaming_exempt leaf in TS 24.391 [94]
MMTEL_voice_roaming_exempt leaf in TS 24.275 [r95]
MMTEL_video_roaming_exempt leaf in TS 24.275 [r95]
SSP_XCAP_config_roaming_exempt leaf in
TS 24.424 [93]
SMSoIP_roaming_exempt leaf in TS 24.167 [88]
Bearer_independent_protocol leaf of the
Exempted_service_list_roaming in TS 24.368 [96]
Device_management_over_PS leaf of the
Exempted_service_list_roaming in TS 24.368 [96]
RFU
Bytes 3 to 4 are RFU.
4.2.110 EF3GPPPSDATAOFFservicelist (3GPP PS Data Off Service List)

If service n° 118 is "available", this file shall be present. This file contains a list of particular IMS services not defined
by 3GPP, where each such IMS service is identified by an IMS communication service identifier. (See
3GPP TS 22.011 [2]). The usage of this file is described in 3GPP TS 24.229 [63] subclauses 4.17 B.3.1.5 and L.3.1.5.
Identifier: '6FFA Structure: linear fixed Optional

Record length: X bytes. Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
ACTIVATE ADM
DEACTIVATE ADM

1 to X ICSI TLV object M X bytes
ICSI TLV object:

Contents:
3GPP
Release 15 130 3GPP TS 31.102 V15.21.0 (2018-0610)
- The content and coding is defined below.
Coding of the ICSI TLV objects

1 byte ICSI TLV TAG '80' M
1 byte Length of ICSI Y M
Y bytes ICSI value - M
- Coding:
IMS Communication Service Identifier: shall be coded as specified in TS 24.229 [63].
4.2.111 EFXCAPConfigData (XCAP Configuration Data)

This EF contains the XCAP configuration data object as specified in 3GPP TS 24.424 [101], OMA OMA-TS-
XDM_MO-V1_1-20080627-A [103] and OMA-DDS-DM_ConnMO-V1_0-20081107-A [100]:
For the structure, content and coding of this file, see EFXCAPConfigData in 3GPP TS 31.103 [2].
the UICC.
4.2.112 EFEARFCNList (EARFCN list for MTC/NB-IOT UEs)

If Service n°121 is "available", this file shall be present.
This EF contains NAS configuration MO having a list of EARFCNs and associated geographical area coordinates
configured in the UE for initial cell search of MTC carrier or NB-IoT carrier.
Identifier: '6FFE’'6FFD’ Structure: transparent Optional

File size: X bytes. Update activity: low
Access Conditions:
READ ALWAYS
UPDATE ADM
ACTIVATE ADM
DEACTIVATE ADM

1 to Z EARFCN List TLV data object M Z bytes
This EF contains one or more EARFCN List TLV data objects
EARFCN List information:

EARFCN List TLV 'A0' M 1
Length X M Note 1
EARFCN Tag '80' M 1
Length Note2 M 1
EARFCN value -- M Note2
Geographical Area – Polygon Tag '81' M 1
Length 6*n (n>2) M Note 1
Geographical Area – Polygon value -- M 6*n (n>2)
Note 2: EARFCN is coded in 4 bytes, as specified in 3GPP TS 36.101 [92]
Each EARFCN List TLV data object shall contain one EARFCN and one or more Geographical Area objects.
3GPP
Release 15 131 3GPP TS 31.102 V15.21.0 (2018-0610)
- Geographical Area – Polygon Tag '81'

Contents:
A geographical area defined by a polygon with 3 or more points.
Coding:
1 to 3 Latitude of point 1 M 3 bytes
4 to 6 Longitude of point 1 M 3 bytes
19 to 21 Latitude of point 4 O 3 bytes
22 to 24 Longitude of point 4 O 3 bytes
: : : :
(6n-5) to 6n-3 Latitude of point n O 3 bytes
(6n-2) to 6n Longitude of point n O 3 bytes
Latitude and longitude are coded as defined in subclause 6.1 of 3GPP TS 23.032 [75].
NOTE: The upper limit of 15 specified in 3GPP TS 23.032 [9] for the number of points in a polygon shape does
not apply to the number of coordinates in a geographical area described as a polygon here.
4.2.113 EF5GS3GPPLOCI (5GS 3GPP location information)

If Service n°122 (5GS support) is "available", this file shall be present.
This EF contains the following 5GS location information for 3GPP access:
- 5G-Globally Unique Temporary Identifier (5G-GUTI);

- Last visited registered Tracking Area Identity in 5GS (TAI);
- 5GS update status.
Identifier: '6FFF' Structure: transparent Optional

SFI: 'xx'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 12 5G-GUTI for 3GPP access M 12 bytes
13 to17 Last visited registered TAI in 5GS for 3GPP M 5 bytes
access
18 5GS update status for 3GPP access M 1 byte
- 5G-GUTI for 3GPP access.

Contents:
5G-Globally Unique Temporary Identifier for 3GPP access.
Coding:
as the 5G-GUTI part of the 5GS mobile identity information element defined in TS 24.501 [104]. Byte 1
corresponds to "octet 2" of an 5GS mobile identity information element containing a 5G-GUTI. Byte 12
corresponds to "octet 13" of an 5GS mobile identity information element information element containing a 5G-
GUTI.
Byte 1: first byte of 5G-GUTI for 3GPP access
b8 b7 b6 b5 b4 b3 b2 b1
MSB
3GPP
Release 15 132 3GPP TS 31.102 V15.21.0 (2018-0610)
- Last visited registered TAI in 5GS for 3GPP access

Contents:
Last visited registered Tracking Area Identity in 5GS for 3GPP access.
Coding:
as the content of the tracking area identity information element defined in TS 24.501 [104]. Byte 13 corresponds to
"octet 2" of a tracking area identity information element. Byte 17 corresponds to "octet 6" of a tracking area
identity information element.
Byte 13: first byte of last visited registered TAI for 3GPP access
b8 b7 b6 b5 b4 b3 b2 b1
MSB
- 5GS update status for 3GPP access.

Contents:
status of 5GS update for 3GPP access according to TS 24.501 [104].
Coding:
byte 18:
Bits: b3 b2 b1.
0 0 0 : 5U1 UPDATED.
0 0 1 : 5U2 NOT UPDATED.
0 1 0 : 5U3 ROAMING NOT ALLOWED.
0 1 1 : reserved.
1 0 0 : reserved.
1 0 1 : reserved.
1 1 0 : reserved.
1 1 1 : reserved.
4.2.114 EF5GAUTHKEYS (5G authentication keys)

This EF contains KAUSF and KSEAF that are generated on the ME using CK and IK as part of AKA procedures as
described in TS 33.501 [105].

File size: >= 36 bytes Update activity: high
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

KAUSF Tag '80' M 1
Length K (Note2) M Note1
KAUSF -- M K (Note2)
KSEAF Tag '81' M 1
Length L (Note2) M Note1
KSEAF -- M L (Note2)
Note 2: As per TS 33.501 [105], the length of keys KAUSF and KSEAF is 16 bytes each
- KAUSF Tag '80'.
3GPP
Release 15 133 3GPP TS 31.102 V15.21.0 (2018-0610)
Contents:
- KAUSF as described in TS 33.501[105]).
Coding:
- The most significant bit of KAUSF is the most significant bit of the 1st byte of this TLV value field. The least
significant bit of KAUSF is the least significant bit of the last byte of this TLV value field.
- KSEAF Tag '81'.
Contents:
- KSEAF as described in TS 33.501[105]).
Coding:
- The most significant bit of KSEAF is the most significant bit of the 1st byte of this TLV value field. The least
significant bit of KSEAF is the least significant bit of the last byte of this TLV value field.
4.2.115 EF5GS3GPPNSC (5GS 3GPP Access NAS Security Context)

This EF contains the 5GS 3GPP access NAS security context as defined in TS 24.501 [104], consisting of K AMF with the
associated key set identifier, the UE security capabilities, and the uplink and downlink NAS COUNT values. This file
shall contain one record.

Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to X 5GS NAS Security Context TLV Object M X bytes
5GS NAS Security Context tags

5GS NAS Security Context Tag 'A0'
5GS NAS Security Context information
3GPP
Release 15 134 3GPP TS 31.102 V15.21.0 (2018-0610)

5GS NAS Security Context Tag 'A0' M 1
ngKSI Tag '80' M 1
Length K M Note 1
ngKSI -- M K
KAMF Tag '81' M 1
Length L M Note 1
KAMF -- M L
Length M M Note 1
Length N M Note 1
Length S M Note 1
- ngKSI Tag '80'
Contents:
The ngKSI (Key Set Identifier in 5G) as defined in TS 33.501 [105] is coded on 1 byte.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
ngKSI
- KAMF Tag '81'
Contents:
The KAMF as defined in TS 33.501 [105] is coded on 32 bytes. The ME shall treat any KAMF values stored in this EF
as invalid if the ngKSI indicates that no KAMF is available or if the length indicated in the KAMF TLV is set to '00',
Coding:
The most significant bit of KAMF is the most significant bit of the 1st byte of this TLV value field. The least
significant bit of KAMF is the least significant bit of the last byte of this TLV value field.
Contents:
The uplink NAS count as defined in TS 33.501 [105] is coded on 4 bytes.
Coding:
The most significant bit of the uplink NAS count is the most significant bit of the 1st byte of this TLV value field.
The least significant bit of the uplink NAS count is the least significant bit of the last byte of this TLV value
field.
Contents:
The downlink NAS count as defined in TS 33.501 [105] is coded on 4 bytes.
3GPP
Release 15 135 3GPP TS 31.102 V15.21.0 (2018-0610)
Coding:
The most significant bit of the downlink NAS count is the most significant bit of the 1st byte of this TLV value field.
The least significant bit of the downlink NAS count is the least significant bit of the last byte of this TLV value
field.
Contents:
The identifiers of selected NAS integrity and encryption algorithms as defined in TS 33.501 [105] and TS 24.501
[104]. In this release the identifiers of selected NAS integrity and encryption algorithms are coded as 4-bit
identifiers.
Coding:
Least significant bit of the security algorithm identifier is the b1 of this TLV value field. Most siginificant bit of the
security algorithm identifier is b4 of this TLV value field as per the NAS security algorithms identifer element
b8 b7 b6 b5 b4 b3 b2 b1
LSB of security algorithm identifier
MSB of security algorithm identifier

RFU
RFU
RFU
RFU
In order to mark the stored 5GS NAS security context as invalid:

- the ngKSI is set to '07', or
- the length indicated in the KAMF TLV is set to '00'.
4.2.116 EF5GS3GPPNSC (5GS non-3GPP Access NAS Security Context)

This EF contains the 5GS non-3GPP access NAS security context as defined in TS 24.501 [104], consisting of K AMF
with the associated key set identifier, the UE security capabilities, and the uplink and downlink NAS COUNT values.
This file shall contain one record.
Identifier: '6F03 Structure: linear fixed Optional

Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

For content and coding see clause 4.2.116 for EF5GS3GPPNSC.
3GPP
Release 15 136 3GPP TS 31.102 V15.21.0 (2018-0610)
4.2.117 EFSUCI_Calc_Info (Subscription Concealed Identifier Calculation

Information EF)
If "SUCI calculation is to be performed by the ME" (i.e. Service n°124 is "available" and Service n°125 is not
"available"), this file shall be present.
If "SUCI calculation is to be performed by the USIM" (i.e. Service n°124 is "available" and Service n°125 is
"available"), this file shall not be available to the ME.
If Service n°124 is not "available", this file shall not be available to the ME. This EF contains at least one SUCI
calculation Information data object information needed by the ME for the support of sSubscription identifier privacy as
defined in 3GPP TS 33.501[105]. The number of SUCI calculation information data object depends on the number of
Home Network Public Keys.

File size: X bytes (X ≥ 2Z) Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to Z Protection Scheme Identifier List data M Z bytes
objectSUCI Calculation Information TLV data
object 1
Z+1 to Y+Z Home Network Public Key List data objectSUCI OC Y bytes
Calculation Information TLV data object 2
... ... ... ...
X-W+1 to X Routing Information TLV data objectSUCI OC W bytes
Calculation Information TLV data object n
Editor’s Note: The presence condition of Routing Information TLV data object is FFS.
SUCI (Subscription Concealed Identifier) Calculation Information data object:

Each SUCI Calculation Information TLV data object shall only contain one Protection Scheme Identifier List data
object and at most one Home Network Public Key data object.

SUCI Calculation Information TLV data object tag 'A0' M 1
SUCI Calculation Information TLV data object length L1 M Note 1
Protection Scheme Identifier List data object '80' M L2
Home Network Public Key data object '81' C Note 2
Note 2: See conditions in text of the data object
- Protection Scheme Identifier List data object.

Contents:
- This data object shall always be present. If Protection Scheme Identifier List data object length is not zero, this data
object contains a list of the Protection Scheme Identifiers in priority orderand the corresponding Key index. The first
Protection Scheme Identifier entry has the highest priority and the last entry has the lowest priority. The Key Index
value indicates the position of the Home Network Public Key in the Home Network Public Key List, that is applicable
to the Protection Scheme.
Coding:
3GPP
Release 15 137 3GPP TS 31.102 V15.21.0 (2018-0610)
Protection Scheme Identifier List data object tag '80''A0' M 1

Protection Scheme Identifier List data object length L1 M Note 1
Protection Scheme Identifier 1 (Highest priority) -- MO 1
Key Index 1 -- C (Note 1
2)
Protection Scheme Iidentifier 2 -- O 1
Key Index 2 -- C (Note 1
2)
… … … …
Protection Scheme Identifier N (Lowest priority) -- O 1
Key Index N -- C (Note 1
2)
Note 2: This field is present only if the corresponding Protection Scheme Identifier field is
present
The Protection Scheme Identifier represents a protection scheme as described in 3GPP TS 33.501 [105] and it is
coded in one byte as follows:
b8 b7 b6 b5 b4 b3 b2 b1
Protection Scheme identifier coded as described in

3GPP TS 33.501 [105]
RFU, bit = 0
Editor’s Note: The format may need to be updated depending on the outcome of 3GPP TS 23.003.
The Key Index is coded in one byte such that its value indicates the position of the Home Network Public Key in the
Home Network Public Key List data object, that is applicable to the Protection Scheme. A Key Index with a value
of "1" refers to the first Network Public Key entry in the Home Network Public Key List, and so on. A Key Index
with a value of "0" indicates that there is no Home Network Public Key associated with that Protection Scheme
(e.g., in the case of null-scheme).
- Home Network Public Key List data object.
Contents:
This data object contains a list of the Home Network Public Key and the corresponding Home Network Public Key
Identifier that shall be used by the ME to calculate the SUCI.
This data object may not be be present if none of the protection scheme profiles identified by the Protection Scheme
Identifiers included in the Protection Scheme Identifier List data object use the Home Network Public Key (e.g.
null-scheme). If this data object is present, it shall contain at least one Home Network Public Key and the
corresponding Home Network Public Key Identifier..
Coding:
Each Home Network Public Key data object shall only contain one Home Network Public Key Identifier and one
Home Network Public Key value.
3GPP
Release 15 138 3GPP TS 31.102 V15.21.0 (2018-0610)
Home Network Public Key List data object '81''A1' CM 1

Home Network Public Key List data object length L1 CM Note 1
Home Network Public Key 1 Identifier tag '82' CM 1
Home Network Public Key 1 Identifier length L2 CM Note 1
Home Network Public Key 1 Identifier -- CM L2
Home Network Public Key 1Value tag '83' CM 1
Home Network Public Key 1Value length L3 CM Note 1
Home Network Public Key 1Value -- CM L3
… … … …
Home Network Public Key N Identifier tag '80' O 1
Home Network Public Key N Identifier length L4 O Note 1
Home Network Public Key N Identifier -- O L4
Home Network Public Key N tag '81' O 1
Home Network Public Key N length L5 O Note 1
Home Network Public Key N -- O L5
Editor’s Note: Coding of the Home Network Public Key Identifier and Home Network Public Key are FFS.
- Routing Information TLV data object.
Contents:
This data object contains Routing Indicator that allows together with the MCC and MNC to route network signalling
with SUCI to AUSF and UDM instances capable to serve the subscriber, as specified in 3GPP TS 23.003 [25]. This
data object may not be present in the case of null-scheme. If this data object is present, it shall have a valid Routing
Indicator.
Coding:
Routing Information TLV data object tag 'A2' C 1
Routing Information TLV data object L1 C Note 1
length
Routing Information TLV data object value -- C L1
Editor’s Note: Contents and coding of the above data object TLV value is are FFS.
4.2.118 EFUAC_AIC (UAC Access Identities Configuration)
This EF contains the configuration information pertaining to access identities allocated for specific high priority
services that can be used by the subscriber. The assigned access identities are used, in combination with
an access category, to control the access attempts. For more information see TS°22.261°[106] and
TS°24.501°[104].

File size: X 4 bytes (X > 1) Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to 4X UAC access identities configuration M 4X bytes
- UAC access identities configuration

Contents:
- Configuration of certain Unified Access Control (UAC) access identities specified in configuration according
to TS°24.501°[104]°subclause°4.5.2.
Coding:
3GPP
Release 15 139 3GPP TS 31.102 V15.21.0 (2018-0610)
- Each access identity configuration is coded on one bit.
Byte 1:
b8 b7 b6 b5 b4 b3 b2 b1
b1=0: UE is not configured for Multimedia Priority

Service in the country of its HPLMN.
b1=1: UE is configured for Multimedia Priority
b2=0: UE is not configured for Mission Critical
Services in the HPLMN or EHPLMN.
b2=1: UE is configured for Mission Critical Services
in the HPLMN or EHPLMN.RFU
RFU
Byte(s) 2 to 4X:
Bits b1 to b8 are RFU.
4.2.119 EFSteering_of_UE_in_VPLMN (Steering of UE in VPLMN)

If service n 127 is "available", this file shall be present.
This file allows the HPLMN to configure the support of the USIM for Steering of UE in VPLMN. The procedure is
specified in 3GPP TS 23.122 [31]
NOTE:Access Identities 11 to 15 (as specified in TS 24.501

[104]) are configured as Access Classes 11 to 15 in
EFACC, specified in clause 4.2.15.
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1-2 Steering of UE in VPLMN Configuration M 2 bytes
- Steering of UE in VPLMN Configuration.

Contents:
- configuration parameters for steering of UE in VPLMN.
Coding:
Byte 1:
3GPP
Release 15 140 3GPP TS 31.102 V15.21.0 (2018-0610)
b8 b7 b6 b5 b4 b3 b2 b1
b1=0 steering of UE in VPLMN during registration not

supported
b1=1 steering of UE in VPLMN during registration
supported (see Note)
RFU
RFU
RFU
RFU
RFU
RFU
RFU
Byte 2 is RFU.
4.3 DFs at the USIM ADF (Application DF) Level

DFs may be present as child directories of USIM ADF. The following DFs are defined:
DFPHONEBOOK '5F3A' (see Note 2).
DFGSM-ACCESS '5F3B'.
DFMexE '5F3C'.
DFWLAN '5F40'.
DFHNB '5F50'.
DFSoLSA '5F70'.
DFBCAST '5F80' (see Note 1).
DFProSe '5F90'.
DFACDC '5FA0'
DFTV '5FB0'
DF5GS '5FC0'
Note 1: The DF identifier '5F80' is reserved for OMA BCAST Smart Card Profile [49]
Note 2: DF for application specific phonebook. This DF has the same structure as the DFPHONEBOOK under DFTELECOM.
4.4 Contents of DFs at the USIM ADF (Application DF) level

4.4.1 Contents of files at the DF SoLSA level
This only applies if the Support of Localised Service Areas is supported, as indicated by Service Number 23 in the
USIM Service Table and specified in TS 23.073 [23] .
The Efs contain information about the users subscribed local service areas.
3GPP
Release 15 141 3GPP TS 31.102 V15.21.0 (2018-0610)
4.4.1.1 EFSAI (SoLSA Access Indicator)

This EF contains the 'LSA only access indicator'. This EF shall always be allocated if DF SoLSA is present.
If the indicator is set, the network will prevent terminated and/or originated calls when the MS is camped in cells that
are not included in the list of allowed LSAs in EFSLL. Emergency calls are, however, always allowed.
The EF also contains a text string which may be displayed when the MS is out of the served area(s).

File size: X + 1 bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 LSA only access indicator M 1 byte
2 to X+1 LSA only access indication text M X bytes
- LSA only access indicator
Contents: indicates whether the MS is restricted to use LSA cells only or not.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
b1=0: LSA only access not activated

b1=1: LSA only access activated
RFU
- LSA only access indication text
Contents: text to be displayed by the ME when it's out of LSA area.
Coding: the string shall use either
shall be left justified. Unused bytes shall be set to 'FF'; or
4.4.1.2 EFSLL (SoLSA LSA List)

This EF contains information describing the LSAs that the user is subscribed to. This EF shall always be allocated if
DFSoLSA is present.
Each LSA is described by one record that is linked to a LSA Descriptor file. Each record contains information of the
PLMN, priority of the LSA, information about the subscription and may also contain a text string and/or an icon that
identifies the LSA to the user. The text string can be edited by the user.
3GPP
Release 15 142 3GPP TS 31.102 V15.21.0 (2018-0610)

Record length: X + 10 bytes Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to X LSA name O X bytes
X+1 Configuration parameters M 1 byte
X+2 RFU M 1 byte
X+3 Icon Identifier M 1 byte
X+4 Priority M 1 byte
X+5 to X+7 PLMN code M 3 bytes
X+8 to X+9 LSA Descriptor File Identifier M 2 byte
X+10 LSA Descriptor Record Identifier M 1 byte
- LSA name
Contents: LSA name string to be displayed when the ME is camped in the corresponding area, dependant on the
contents of the LSA indication for idle mode field.
Coding: the string shall use either
shall be left justified. Unused bytes shall be set to 'FF'; or
- one of theUCS2 code options defined in the annex of TS 31.101 [11].
- Configuration parameters
Contents: Icon qualifier, control of idle mode support and control of LSA indication for idle mode.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
Icon qualifier
Idle mode support
LSA indication for idle mode
RFU
Icon qualifier:
Contents: The icon qualifier indicates to the ME how the icon is to be used.
B2, b1: 00: icon is not to be used and may not be present
01: icon is self-explanatory, i.e. if displayed, it replaces the LSA name
10: icon is not self-explanatory, i.e. if displayed, it shall be displayed together with the LSA name
11: RFU
Idle mode support:
Contents: The idle mode support is used to indicate whether the ME shall favour camping on the LSA cells in
idle mode.
B3 = 0: Idle mode support disabled

b3 = 1: Idle mode support enabled
LSA indication for idle mode:
Contents: The LSA indication for idle mode is used to indicate whether or not the ME shall display the LSA
name when the ME is camped on a cell within the LSA.
3GPP
Release 15 143 3GPP TS 31.102 V15.21.0 (2018-0610)
B4 = 0: LSA indication for idle mode disabled

b4 = 1: LSA indication for idle mode enabled
Bits b5 to b8 are RFU (see subclause 9.3).
- Icon Identifier
Contents: The icon identifier addresses a record in EFIMG.
Coding: binary.
- Priority
Contents: Priority of the LSA which gives the ME the preference of this LSA relative to the other LSAs.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
Priority
RFU
'0' is lowest priority, 'F' is highest.
- PLMN code
Contents: MCC + MNC for the LSA.
Coding: according to TS 24.008 [9] and EFLOCI.
- LSA Descriptor File Identifier:
Contents: these bytes identify the EF which contains the LSA Descriptors forming the LSA.
Coding: byte X+8: high byte of the LSA Descriptor file;

byte X+9: low byte of the LSA Descriptor file.
- LSA Descriptor Record Identifier:
Contents: this byte identifies the number of the first record in the LSA Descriptor file forming the LSA.
Coding: binary.
3GPP
Release 15 144 3GPP TS 31.102 V15.21.0 (2018-0610)
4.4.1.3 LSA Descriptor files

Residing under DFSoLSA, there may be several LSA Descriptor files. These Efs contains one or more records again
containing LSA Descriptors forming the LSAs. LSAs can be described in four different ways. As a list of LSA Ids, as a
list of LAC + Cis, as a list of Cis or as a list of LACs. As the basic elements (LSA ID, LAC + CI, CI and LAC) of the
four types of lists are of different length, they can not be mixed within one record. Different records may contain
different kinds of lists within the Efs. Examples of codings of LSA Descriptor files can be found in annex F.
Identifier: '4FXX' Structure: linear fixed Optional

Record length: n*X+2 bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 LSA descriptor type and number M 1 byte
2 to X+1 1st LSA Descriptor M X bytes
X+2 to 2X+1 2nd LSA Descriptor M X bytes
: : : :
(n-1)*X+2 to nth LSA Descriptor M X bytes
n*X+1
n*X+2 Record Identifier M 1 byte
- LSA descriptor type and number:
Contents: The LSA descriptor type gives the format of the LSA descriptor and the number of valid LSA
Descriptors within the record.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
LSA descriptor type

Number of LSA Descriptors
LSA descriptor type:
Contents: Gives the format of the LSA Descriptors.
B2, b1: 00: LSA ID.

01: LAC + CI
10: CI
11: LAC
Number of LSA Descriptors:
Contents: Gives the number of valid LSA Descriptors in the record.
Coding: binary, with b8 as MSB and b3 as LSB leaving room for 64 LSA Descriptors per record.
- LSA Descriptor
Contents: Dependant of the coding indicated in the LSA descriptor type:
- in case of LSA ID the field length 'X' is 3 bytes;
- in case of LAC + CI the field length 'X' is 4 bytes;
- in case of CI the field length 'X' is 2 bytes;
- in case of LAC the field length 'X' is 2 bytes.
3GPP
Release 15 145 3GPP TS 31.102 V15.21.0 (2018-0610)
Coding: according to TS 24.008 [9].
- Record Identifier:
Contents: This byte identifies the number of the next record containing the LSA Descriptors forming the LSA.
Coding: record number of next record. 'FF' identifies the end of the chain.
This file utilises the concept of chaining as for EFEXT1.
The identifier '4FXX' shall be different from one LSA Descriptor file to the other and different from the identifiers of
EFSAI and EFSLL. For the range of 'XX', see 3GPP TS 31.101 [11].
4.4.2 Contents of files at the DF PHONEBOOK level

The Efs in the DFPHONEBOOK level contain phone book related features as required in 3GPP TS 21.111 [1].
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, when the terminal supports
application specific phonebooks, it shall be possible for the user to select which phonebook the user would like to
access.
Support of the global phonebook is mandatory, except for Terminals of type ND, NK or NS, as specified in 3GPP TS
31.111 [12] Annex P, for which support is optional. Terminals that support the global phonebook shall conditionally
support, the application specific phonebooks, also known as local phonebook. The support of local phone book is:
a) optional for terminals that support alternative phonebook applications; and
NOTE 1: Such terminals could be of type "Smartphone" as described in GSMA: "IMEI Allocation and Approval
Process" [84].
b) mandatory for terminals that do not support alternative phonebook applications.
NOTE 2: Such terminals could be of type "Feature Phone" as described in GSMA: "IMEI Allocation and Approval
Process" [84].
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 DFPHONEBOOK under DFTELECOM.. Each specific USIM application phonebook is
located in DFPHONEBOOK of its respective Application ADFUSIM. The organisation of files in DFPHONEBOOK under ADFUSIM
and under DF TELECOM follows the same rules. Yet DFPHONEBOOK under ADFUSIM may contain a different set of files than
DFPHONEBOOK under DFTELECOM. All phonebook related Efs are located under their respective DFPHONEBOOK. USIM specific
phonebooks are dedicated to application specific entries. Each application specific phonebook is protected by the
application PIN.
EFADN and EFPBR shall always be present if the DFPhonebook is present. If any phonebook file other than EFADN or EFEXT1,
is used, then EFPBC shall be present.
If a GSM application resides on the UICC, the Efs ADN and EXT1 from one DFPHONEBOOK (defined at GSM application
installation) are mapped to DFTELECOM. Their file Ids are specified in 3GPP TS 51.011 [18], i.e. EFADN = '6F3A' and
EFEXT1 = '6F4A', respectively.
If the UICC is inserted into a terminal accessing the ADN and EXT1 files under DF TELECOM; and a record in these files
has been updated, a flag in the corresponding entry control information in the EFPBC is set from 0 to 1 by the UICC. If
the UICC is later inserted into a terminal that supports the global and/or application specific phonebook, the terminal
shall check the flag in EFPBC and if this flag is set, shall update the EFCC, and then reset the flag. A flag set in EFPBC
results in a full synchronisation of the phonebook between an external entity and the UICC (if synchronisation is
requested).
The EF structure related to the public phonebook is located under DFPHONEBOOK in DFTELECOM. A USIM specific
phonebook may exist for application specific entries. The application specific phonebook is protected by the application
PIN. The organisation of files in the application specific phonebook follows the same rules as the one specified for the
3GPP
Release 15 146 3GPP TS 31.102 V15.21.0 (2018-0610)
public phone book under DFTELECOM. The application specific phonebook may contain a different set of files than the one
in the public area under DFTELECOM.
4.4.2.1 EFPBR (Phone Book Reference file)

This file describes the structure of the phonebook. All Efs representing the phonebook are specified here (with the
exception of EFPSC, EFPUID and EFCC), 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, EFADN and EFADN1. 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 EFPBR.
The SFI value assigned to an EF which is indicated in EFPBR shall correspond to the SFI indicated in the TLV object in
EFPBR.
The reference file is a file that contains information how the information in the different files is to be combined together
to form a phone book entry. The reference file contains records. Each record specifies the structure of up to 254 entries
in the phone book. Each phone book entry consists of data stored in files indicated in the reference file record. The
entry structure shall be the same over all the records in the EF PBR. If more than 254 entries are to be stored, a second
record is needed in the reference file. The structure of a phone book entry is defined by different TLV objects that are
stored in a reference file record. The reference file record structure describes the way a record in a file that is part of the
phonebook is used to create a complete entry. Three different types of file linking exist.
Type 1 files: Files that contain as many records as the reference/master file (EF ADN, EFADN1) and are linked on
record number bases (Rec1 -> Rec1). The master file record number is the reference.
Type 2 files: Files that contain less entries than the master file and are linked via pointers in the index
administration file (EFIAP).
Type 3 files: Files that are linked by a record identifier within a record.
Table 4.1: Phone Book Reference file Constructed Tags
Tag Value Constructed TAG Description

'A8' Indicating files where the amount of records equal to
master EF, type 1
'A9' Indicating files that are linked using the index
administration file, type 2. Order of pointer appearance
in index administration EF is the same as the order of
file Ids following this tag
'AA' Indicating files that are linked using a record identifier,
type 3. (The file pointed to is defined by the TLV
object.)
The first file ID in the first record of EFPBR indicated using constructed Tag 'A8' is called the master EF. Access
conditions for all other files in the Phonebook structure using Tags 'A8', 'A9' or 'AA' is set to the same as for the master
EF unless otherwise specified in the present document.
File Ids indicated using constructed Tag 'A8' is a type 1 file and contains the same number of records as the first file
that is indicated in the data part of this TLV object. All files following this Tag are mapped one to one using the record
numbers/Ids of the first file indicated in this TLV object.
File Ids indicated using constructed Tag 'A9' are mapped to the master EF (the file ID indicated as the first data object
in the TLV object using Tag 'A8') using the pointers in the index administration file. The order of the pointers in the
index administration file is the same as the order of the file Ids presented after Tag 'A9'. If this Tag is not present in the
reference file record the index administration file is not present in the structure. In case the index administration file is
not present in the structure it is not indicated in the data following tag 'A8'.
File Ids indicated using constructed Tag 'AA' indicate files that are part of the reference structure but they are addressed
using record identifiers within a record in one or more of the files that are part of the reference structure. The length of
the tag indicates whether the file to be addressed resides in the same directory or if a path to the file is provided in the
TLV object.
3GPP
Release 15 147 3GPP TS 31.102 V15.21.0 (2018-0610)
Type 2 and type 3 files contain records that may be shared between several phonebook entries (except when otherwise
indicated). The terminal shall ensure that a shared record is emptied when the last phonebook entry referencing it is
modified in such a way that it doesn't reference the record anymore.
NOTE: in the current version of the specification, only type 3 files contain records that may be shared.
Each constructed Tag contains a list of primitive Tags indicating the order and the kind of data (e.g. ADN, IAP,…) of
the reference structure.
The primitive tag identifies clearly the type of data, its value field indicates the file identifier and, if applicable, the SFI
value of the specified EF. That is, the length value of a primitive tag indicates if an SFI value is available for the EF or
not:
- Length = '02' Value: 'FID (2 bytes)'
- Length = '03' Value: 'FID (2 bytes)', 'SFI (1 byte)'
Table 4.2: Tag definitions for the phone book kind of file
Tag Value TAG Description

'C0' EFADN data object
'C1' EFIAP data object
'C2' EFEXT1 data object
'C3' EFSNE data object
'C4' EFANR data object
'C5' EFPBC data object
'C6' EFGRP data object
'C7' EFAAS data object
'C8' EFGAS data object
'C9' EFUID data object
'CA' EFEMAIL data object
'CB' EFCCP1 data object
'CC' EFPURI data object
Table 4.3 (below) lists the allowed types for each kind of file:
Table 4.3: Presence of files as type
File name Type 1 Type 2 Type 3

EFAAS X
EFADN X
EFANR X X
EFEMAIL X X
EFEXT1 X
EFGAS X
EFGRP X
EFIAP X
EFPBC X
EFSNE X X
EFUID X
EFCCP1 X
EFPURI X X
3GPP
Release 15 148 3GPP TS 31.102 V15.21.0 (2018-0610)
Phone Book Reference file EFPBR structure
Identifier: '4F30' Structure: linear fixed Conditional

(see Note)
Record Length: X bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to X TLV object(s) for indicating Efs that are part of M X bytes
the phone book structure
NOTE: This file is mandatory if and only if DFPhonebook is present.
At the end of each record, unused bytes, if any, shall be filled with 'FF'.
4.4.2.2 EFIAP (Index Administration Phone book)

This file is present if Tag 'A9' is indicated in the reference file.
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 EFADN (shall be record to record). The index
administration file contains the same amount of records as EFADN. The order of the pointers in an EFIAP 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 the EFPBR following tag 'A9'.
The value 'FF' is an invalid record number/ID and is used in any location in to indicate that no corresponding record in
the indicated file is available.
The content of EFIAP is set to 'FF' at the personalisation stage.
Index administration file EFIAP structure
Identifier: '4FXX' Structure: linear fixed Conditional

(see Note)
SFI: 'YY'
Record Length: X bytes, (X ≥ 1) Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 Record number of the first object indicated after M 1 byte
Tag 'A9'
2 Record number of the second object indicated C 1 byte
after Tag 'A9'
X Record number of the xth object indicated after C 1 byte
Tag 'A9'
NOTE 1: This file is mandatory if and only if type 2 files are present.
NOTE 2: xth-field marked with ‘C’ is mandatory if xth-object indicated following tag ‘A9’ is
present in EFPBR
4.4.2.3 EFADN (Abbreviated dialling numbers)

This EF contains Abbreviated Dialling Numbers (ADN) and/or Supplementary Service Control strings (SSC). In
addition it contains identifiers of associated network/bearer capabilities and identifiers of extension records. It may also
contain an associated alpha-tagging.
3GPP
Release 15 149 3GPP TS 31.102 V15.21.0 (2018-0610)

(see Note)
SFI: 'YY'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

NOTE: This file is mandatory if and only if DFPHONEBOOK is present.
- Alpha Identifier.
Contents:
- Alpha-tagging of the associated dialling number.
Coding:
- this alpha-tagging shall use either:
Or:
NOTE 1: The value of X may be from zero to 241. Using the command GET RESPONSE the ME can determine
the value of X.
- Length of BCD number/SSC contents.

Contents:
- this byte gives the number of bytes of the following two data items containing actual BCD number/SSC
information. This means that the maximum value is 11, even when the actual ADN/SSC information length is greater
than 11. When an ADN/SSC has extension, it is indicated by the extension1 identifier being unequal to 'FF'. The
remainder is stored in the EFEXT1 with the remaining length of the additional data being coded in the appropriate
additional record itself (see clause 4.4.2.4).
Coding:
- TON and NPI.

Contents:
- Type of number (TON) and numbering plan identification (NPI).
Coding:
- according to TS 24.008 [9]. If the Dialling Number/SSC String does not contain a dialling number, e.g. a control
string deactivating a service, the TON/NPI byte shall be set to 'FF' by the ME (see note 2).
NOTE 2: If a dialling number is absent, no TON/NPI byte is transmitted over the radio interface (see
TS 24.008 [9]). Accordingly, the ME should not interpret the value 'FF' and not send it over the radio
interface.
B8 b7 b6 b5 b4 b3 b2 b1
NPI
TON
1
3GPP
Release 15 150 3GPP TS 31.102 V15.21.0 (2018-0610)
- Dialling Number/SSC String

Contents:
- up to 20 digits of the telephone number and/or SSC information.
Coding:
- according to TS 24.008 [9], TS 22.030 [4] and the extended BCD-coding (see table 4.4). If the telephone number or
SSC is longer than 20 digits, the first 20 digits are stored in this data item and the remainder is stored in an associated
record in the EFEXT1. The record is identified by the Extension1 Record Identifier. If ADN/SSC require less than
20 digits, excess nibbles at the end of the data item shall be set to 'F'. Where individual dialled numbers, in one or more
records, of less than 20 digits share a common appended digit string the first digits are stored in this data item and the
common digits stored in an associated record in the EFEXT1. The record is identified by the Extension 1 Record
Identifier. Excess nibbles at the end of the data item shall be set to 'F'.
Byte X+3
B8 b7 B6 b5 b4 b3 b2 b1
LSB of Digit 1
:
:
MSB of Digit 1
LSB of Digit 2
:
:
MSB of Digit 2
Byte X+4:
B8 b7 B6 b5 b4 b3 b2 b1
LSB of Digit 3
:
:
MSB of Digit 3
LSB of Digit 4
:
:
MSB of Digit 4
etc.
- Capability/Configuration1 Record Identifier.

Contents:
- capability/configuration identification byte. This byte identifies the number of a record in the EF CCP1 containing
associated capability/configuration parameters required for the call. The use of this byte is optional. If it is not used it
shall be set to 'FF'.
Coding:
- binary.
- Extension1 Record Identifier.

Contents:
- extension1 record identification byte. This byte identifies the number of a record in the EF EXT1 containing an
associated called party subaddress or additional data. The use of this byte is optional. If it is not used it shall be set to
'FF'.
- if the ADN/SSC requires both additional data and called party subaddress, this byte identifies the additional record.
A chaining mechanism inside EFEXT1 identifies the record of the appropriate called party subaddress (see clause 4.4.2.4).
Coding:
- binary.
3GPP
Release 15 151 3GPP TS 31.102 V15.21.0 (2018-0610)
NOTE 3: EFADN in the public phone book under DFTELECOM may be used by USIM, GSM and also other applications
in a multi-application card. If the non-GSM application does not recognise the use of Type of Number
(TON) and Number Plan Identification (NPI), then the information relating to the national dialling plan
shall be held within the data item dialling number/SSC and the TON and NPI fields set to UNKNOWN.
This format would be acceptable for 3G operation and also for the non-GSM application where the TON
and NPI fields shall be ignored.
EXAMPLE: SIM storage of an International Number using E.164 [22] numbering plan.
TON NPI Digit field.

USIM application 001 0001 abc...
Other application compatible with 3G 000 0000 xxx...abc...
where "abc..." denotes the subscriber number digits (including its country code), and "xxx..."
denotes escape digits or a national prefix replacing TON and NPI.
NOTE 4: When the ME acts upon the EFADN with a SEARCH RECORD command in order to identify a character
string in the alpha-identifier, it is the responsibility of the ME to ensure that the number of characters
used as SEARCH RECORD parameters are less than or equal to the value of X if the MMI allows the
user to offer a greater number.
Table 4.4: Extended BCD coding
BCD Value Character/Meaning

'0' "0"
: :
'9' "9"
'A' "*"
'B' "#"
'C' DTMF Control digit separator (see TS 22.101 [24]).
'D' "Wild" value. This will cause the MMI to prompt the user for a single digit (see TS 22.101 [24]).
'E' RFU.
'F' Endmark e.g. in case of an odd number of digits.
BCD values 'C', 'D' and 'E' are never sent across the radio interface.
NOTE 5: The interpretation of values 'D', 'E' and 'F' as DTMF digits is for further study.
NOTE 6: A second or subsequent 'C' BCD value will be interpreted as a 3 second PAUSE (see TS 22.101 [24]).
4.4.2.4 EFEXT1 (Extension1)

This EF contains extension data of an ADN/SSC.
Extension data is caused by:
- an ADN/SSC which is greater than the 20 digit capacity of the ADN/SSC Elementary File or where common
digits are required to follow an ADN/SSC string of less than 20 digits. The remainder is stored in this EF as a
record, which is identified by a specified identification byte inside the ADN/SSC Elementary File. The EXT1
record in this case is specified as additional data;
- an associated called party subaddress. The EXT1 record in this case is specified as subaddress data.
3GPP
Release 15 152 3GPP TS 31.102 V15.21.0 (2018-0610)

SFI: 'YY'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

- Record type.
Contents:
- type of the record.
Coding:
B8 b7 b6 b5 b4 b3 b2 b1
Called Party Subaddress

Additional data
RFU
- b3 to b8 are reserved and set to 0;
- a bit set to 1 identifies the type of record;
- only one type can be set;
- '00' indicates the type "unknown" or "free".
The following example of coding means that the type of extension data is "additional data":
B8 b7 b6 b5 b4 b3 b2 b1
0 0 0 0 0 0 1 0
- Extension data.
Contents:
additional data or Called Party Subaddress depending on record type.
Coding:
Case 1, Extension1 record is additional data:
- The first byte of the extension data gives the number of bytes of the remainder of ADN/SSC. The coding
of remaining bytes is BCD, according to the coding of ADN/SSC. Unused nibbles at the end shall be set
to 'F'. It is possible if the number of additional digits exceeds the capacity of the additional record to chain
another record inside the EXT1 Elementary File by the identifier in byte 13. In this case byte 2 (first byte
of the extension data) of all records for additional data within the same chain indicates the number of
bytes ('01' to '0A') for ADN/SSC (respectively MSISDN, LND) within the same record unequal to 'FF'.
Case 2, Extension1 record is Called Party Subaddress:
- The subaddress data contains information as defined for this purpose in TS 24.008 [9]. All information
defined in TS 24.008, except the information element identifier, shall be stored in the USIM. The length
of this subaddress data can be up to 22 bytes. In those cases where two extension records are needed,
these records are chained by the identifier field. The extension record containing the first part of the
called party subaddress points to the record which contains the second part of the subaddress.
- Identifier.
Contents:
identifier of the next extension record to enable storage of information longer than 11 bytes.
3GPP
Release 15 153 3GPP TS 31.102 V15.21.0 (2018-0610)
Coding:
record number of next record. 'FF' identifies the end of the chain.
- Example of a chain of extension records being associated to an ADN/SSC. The extension1 record identifier
(Byte 14+X) of EFADN is set to 3.
In this example, ADN/SSC is associated to additional data (records 3 and 4) which represent the last 27 or 28 digits of
the whole ADN/SSC (the first 20 digits are stored in EFADN) and a called party subaddress whose length is more than 11
bytes (records 6 and 1).
4.4.2.5 EFPBC (Phone Book Control)

This EF contains control information related to each entry in the phone book. This EF contains as many records as the
EFADN associated with it (shall be record to record). Each record in EFPBC points to a record in its EFADN. This file
indicates the control information and the hidden information of each phone book entry.
The content of EFPBC is linked to the associated EFADN record by means of the ADN record number/ID (there is a one to
one mapping of record number/identifiers between EFPBC and EFADN).
Structure of control file EFPBC

(see Note)
SFI: 'YY'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 Entry Control Information M 1 byte
2 Hidden Information M 1 byte
NOTE: This file is mandatory if one or both of the following is true:
- hidden entries are supported
- a GSM SIM application is supported in the UICC.
- Entry Control Information.

Contents:
- provides some characteristics about the phone book entry e.g. modification by a terminal accessing the ADN and
EXT1 files under DFTELECOM (see clause 4.4.2).
Coding:
3GPP
Release 15 154 3GPP TS 31.102 V15.21.0 (2018-0610)
b8 B7 b6 B5 b4 B3 b2 B1
Modified phonebook entry '1', no change '0'

RFU (see TS 31.101)
- Hidden Information.
Contents:
indicates to which USIM application of the UICC this phone book entry belongs, so that the corresponding secret code
can be verified to display the phone book entry. If the secret code is not verified, then the phone book entry is hidden.
Coding:
'00' – the phone book entry is not hidden;
'xx' – the phone book entry is hidden. 'xx' is the record number in EFDIR of the associated USIM application.
4.4.2.6 EFGRP (Grouping file)

This EF contains the grouping information for each phone book entry. This file contains as many records as the
associated EFADN. Each record contains a list of group identifiers, where each identifier can reference a group to which
the entry belongs.
Structure of grouping file EFGRP

(see Note)
SFI: 'YY'
Record Length: X bytes (1  X 10) Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 Group Name Identifier 1 M 1 byte
2 Group Name Identifier 2 O 1 byte
X Group Name Identifier X O 1 byte
NOTE: This file is mandatory if and only if EFGAS is present.
- Group Name Identifier x.
Content:
- indicates if the associated entry is part of a group, in that case it contains the record number of the group name in
EFGAS.
- One entry can be assigned to a maximum of 10 groups.
Coding:
- '00' – no group indicated;
'XX' – record number in EFGAS containing the alpha string naming the group of which the phone book entry is a
member.
4.4.2.7 EFAAS (Additional number Alpha String)

This file contains the alpha strings that are associated with the user defined naming tags for additional numbers
referenced in EFANR.
3GPP
Release 15 155 3GPP TS 31.102 V15.21.0 (2018-0610)
Structure of EFAAS

SFI: Optional
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to X Alpha text string M X bytes
- Alpha text string.
Content:
- user defined text for additional number.
Coding:
- same as the alpha identifier in EFADN.
4.4.2.8 EFGAS (Grouping information Alpha String)

This file contains the alpha strings that are associated with the group name referenced in EF GRP.
Structure of EFGAS

(see Note)
SFI: Optional
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to X Alpha text string M X bytes
NOTE: This file is mandatory if and only if EFGRP is present.
- Alpha text string
Content:
- group names.
Coding:
- same as the alpha identifier in EFADN.
4.4.2.9 EFANR (Additional Number)

Several phone numbers and/or Supplementary Service Control strings (SSC) can be attached to one EF ADN record, using
one or several EFANR. The amount of additional number entries may be less than or equal to the amount of records in
EFADN. The EF structure is linear fixed. Each record contains an additional phone number or Supplementary Service
Control strings (SSC). This record cannot be shared between several phonebook entries. The first byte indicates
whether the record is free or the type of additional number referring to the record number in EF AAS, containing the text
to be displayed. The following part indicates the additional number and the reference to the associated record in the
EFADN file. In addition it contains identifiers of associated network/bearer capabilities and identifiers of extension
records.
3GPP
Release 15 156 3GPP TS 31.102 V15.21.0 (2018-0610)
Structure of EFANR

SFI: 'YY'
Record length: 15 or 17 bytes Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 Additional Number Record identifier M 1 byte
2 Length of BCD number/SSC contents M 1 byte
3 TON and NPI M 1 byte
4 to 13 Additional number/SSC String M 10 bytes
14 Capability/Configuration1 Record Identifier M 1 byte
15 Extension1 Record Identifier M 1 byte
16 ADN file SFI C 1 byte
17 ADN file Record Identifier C 1 byte
NOTE: The fields marked C above are mandatory if and only if the file is not type 1 (as
specified in EFPBR)
- Additional Number Record Identifier
Content:
- describes the type of the additional number defined in the file EFAAS.
Coding:
- '00' – no additional number description;
'xx' – record number in EFAAS describing the type of number (e.g. "FAX");
'FF' – free record.
- Length of BCD number/SSC contents
Contents:
- this byte gives the number of bytes of the following two data items containing actual BCD number/SSC
information. This means that the maximum value is 11, even when the actual additional number/SSC information
length is greater than 11. When the additional number/SSC has extension, it is indicated by the extension1 identifier
being unequal to 'FF'. The remainder is stored in the EFEXT1 with the remaining length of the additional data being coded
in the appropriate additional record itself (see clause 4.4.2.4).
Coding:
- same as the length of BCD number/SSC string byte in EFADN.
- TON and NPI.
Contents:
- Type of number (TON) and numbering plan identification (NPI).
Coding:
- same as the TON and NPI byte in EFADN.
- Additional number/SSC string
Content:
- up to 20 digits of the additional phone number and/or SSC information linked to the phone book entry.
Coding:
- same as the dialling number /SSC string in EFADN.
- Capability/Configuration1 Record Identifier.
3GPP
Release 15 157 3GPP TS 31.102 V15.21.0 (2018-0610)
Contents:
- This byte identifies the number of a record in the EFCCP1 containing associated capability/configuration parameters
required for the call. The use of this byte is optional. If it is not used it shall be set to 'FF'.
Coding:
- binary.
- Extension1 Record Identifier.
Contents:
- extension1 record identification byte. This byte identifies the number of a record in the EF EXT1 containing an
associated called party subaddress or additional data. The use of this byte is optional. If it is not used it shall be set to
'FF'.
if the number requires both additional data and called party subaddress, this byte identifies the additional record. A
chaining mechanism inside EFEXT1 identifies the record of the appropriate called party subaddress (see clause 4.4.2.4).
Coding:
- binary.
- ADN file SFI.
Content:
- Short File identifier of the associated EFADN file.
Coding:
- as defined in the UICC specification.
- ADN file Record Identifier
Content:
- record identifier of the associated phone book entry.
Coding:
- 'xx' – record identifier of the corresponding ADN record.
4.4.2.10 EFSNE (Second Name Entry)

The phone book also contains the option of a second name entry. The amount of second name entries may be less than
or equal to the amount of records in EFADN. Each record contains a second name entry. This record cannot be shared
between several phonebook entries.
Structure of EFSNE

SFI: 'YY'
Record length: X or X+2 bytes Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to X Alpha Identifier of Second Name M X bytes
X+1 ADN file SFI C 1 byte
X+2 ADN file Record Identifier C 1 byte
specified in EFPBR)
- Alpha Identifier of Second Name.
Content:
- string defining the second name of the phone book entry.
3GPP
Release 15 158 3GPP TS 31.102 V15.21.0 (2018-0610)
Coding:
- as the alpha identifier for EFADN.
- ADN file SFI.
Content:
Coding:
- as defined in the UICC specification.
- ADN file Record Identifier
Content:
record identifier of the associated phone book entry.
Coding:
'xx' – record identifier of the corresponding ADN record.
4.4.2.11 EFCCP1 (Capability Configuration Parameters 1)

This EF contains parameters of required network and bearer capabilities and ME configurations associated with a call
established using a phone book entry.
Structure of EFCCP1

SFI: 'YY'
Record length: X bytes, X  15 Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to X Bearer capability information element M X bytes
- Bearer capability information element.

- see TS 24.008 [9]. The Information Element Identity (IEI) shall be excluded; i.e. the first byte of the EF CCP1 record
shall be Length of the bearer capability contents.
''- unused bytes are filled with 'FF'
4.4.2.12 Phone Book Synchronisation

To support synchronisation of phone book data with other devices, the USIM may provide the following files to be used
by the synchronisation method: a phone book synchronisation counter (PSC), a unique identifier (UID) and change
counter (CC) to indicate recent changes.
If synchronisation is supported in the phonebook, then EFPSC, EFUID, EFPUID and EFCC are all mandatory.
4.4.2.12.1 EFUID (Unique Identifier)

The EFUID is used to uniquely identify a record and to be able to keep track of the entry in the phone book. The terminal
assigns the (UID) when a new entry is created. The value of the UID does not change as long as the value of the PBID
remains the same. The UID shall remain on the UICC, in EFUID, until the PBID is regenerated. This means that when a
phone book entry is deleted, the content of the linked information (e.g. ADN, E-MAIL,..) shall be set to the
personalization value 'FF…FF'. But the UID-value of the deleted record shall not be used when a new entry is added to
the phonebook until the PBID is regenerated, but it shall be set to a new value.
3GPP
Release 15 159 3GPP TS 31.102 V15.21.0 (2018-0610)
If/when the PBID is regenerated, all UIDs for the entry in the phone book shall be assigned new values starting from 1.
If more than one EFUID exists (i.e. multiple phone book file sets) then all values of UIDs used in that phone book shall
be unique over all phone book file sets within that phone book. The new value of the UID for each entry shall then be
kept until the PBID is regenerated again.
Structure of EFUID

(see Note)
SFI: 'YY'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 2 Unique Identifier (UID) of Phone Book Entry M 2 bytes
NOTE: This file is mandatory if and only if synchronisation is supported in the phonebook.
- Unique Identifier of Phone Book Entry.
Content:
- number to unambiguously identify the phone book entry for synchronisation purposes.
Coding:
- hexadecimal value. At initialisation all UIDs are personalised to ''00 00'' (i.e. empty).
4.4.2.12.2 EFPSC (Phone book Synchronisation Counter)

The phone book synchronisation counter (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.
Structure of EFPSC
Identifier: '4F22' Structure: transparent Conditional

(see Note)
SFI: 'YY'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 4 Phone book synchronisation counter (PSC) M 4 bytes
- PSC: Unique synchronisation counter of Phone Book.
3GPP
Release 15 160 3GPP TS 31.102 V15.21.0 (2018-0610)
Content:
number to unambiguously identify the status of the phone book for synchronisation purposes.
Coding:
hexadecimal value.
The phone book identifier (PBID) coding based on the EFPSC is described hereafter:
- For a phone book residing in DF-telecom:
- PBID = ICCid (10bytes) "fixed part" + 4 bytes (in EFPSC) "variable part".
- For a phone book residing in an USIM application:
- PBID = 10 last bytes of (ICCid XOR AID) "fixed part" + 4 bytes (in EFPSC) "variable part".
To be able to detect if the PSC needs to be regenerated (i.e. the variable part) the following test shall be made by
the terminal before for each update of either the CC or the assignment of a new UID:
- Each time the terminal has to increment the value of the UID the following test is needed:
- If UID = 'FF FF' then.
{Increment PSC mod 'FF FF FF FF'; all the UIDs shall be regenerated}.
- Each time the terminal has to increment the value of CC the following test is needed:
If CC = 'FF FF' then.
{Increment PSC mod 'FF FF FF FF'; CC=0001}.
NOTE: If the phonebook is deleted then the terminal will change the PSC according to:
Incrementing PSC modulus 'FFFFFFFF'.
4.4.2.12.3 EFCC (Change Counter)

The change counter (CC) shall be used to detect changes made to the phone book.
Every update/deletion of an existing phone book entry or the addition of a new phone book entry causes the terminal to
increment the EFCC. The concept of having a CC makes it possible to update the phone book in different terminals,
which still are able to detect the changes (e.g. changes between different handset and/or 2 nd and 3rd generation of
terminals).
Structure of EFCC

(see Note)
SFI: 'YY'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 2 Change Counter (CC) of Phone Book M 2 bytes
- Change Counter of Phone Book.
Content:
- indicates recent change(s) to phone book entries for synchronisation purposes.
3GPP
Release 15 161 3GPP TS 31.102 V15.21.0 (2018-0610)
Coding:
- hexadecimal value. At initialisation, CC shall be personalised to '00 00' (i.e. empty).
4.4.2.12.4 EFPUID (Previous Unique Identifier)

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 EFUID.
Structure of EFPUID

(see Note)
SFI: 'YY'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 2 Previous Unique Identifier (PUID) of Phone M 2 bytes
Book Entry
- Previous unique Identifier of Phone Book Entry.
Content:
- Previous number that was used to unambiguously identify the phone book entry for synchronisation purposes.
Coding:
- As for EFUID
4.4.2.13 EFEMAIL (e-mail address)

This EF contains the e-mail addresses that may be linked to a phone book entry. Several e-mail addresses can be
attached to one EFADN record, using one or several EFEMAIL. The number of email addresses may be equal to or less
than the amount of records in EFADN. Each record contains an e-mail address. The first part indicates the e-mail 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.
Structure of EFEMAIL

SFI: 'YY'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to X E-mail Address M X bytes
: : : :
: : : :
specified in EFPBR)
3GPP
Release 15 162 3GPP TS 31.102 V15.21.0 (2018-0610)
- E-mail Address.
Content:
- string defining the e-mail address
Coding:
- the SMS default 7-bit coded alphabet as defined in TS 23.038 [5] with bit 8 set to 0. The alpha identifier shall be left
justified. Unused bytes shall be set to 'FF'.
- ADN file SFI.
Content:
- short File identifier of the associated EFADN file.
Coding:
- ADN file Record Identifier.
Content:
Coding:
- binary.
4.4.2.14 Phonebook restrictions

This clause lists some general restrictions that apply to the phonebook:
- if an EFPBR file contains more than one record, then they shall all be formatted identically on a type-by-type
basis, e.g. if EFPBR record #1 contains one type 1 e-mail then all EFPBR records shall have one type 1 email;
- if an EFPBR record contains more than one reference to one kind of file, such as two EFEMAIL files, then they shall
all be formatted identically on a type-by-type basis, e.g. if an EFPBR record has 2 email addresses, then they shall
have the same record size and the same number of records in each EFPBR entry;
- an EFPBR record may contain TLV entries indicating that the file exist as a type 1 and 2 file, e.g. a phonebook
entry may have two emails, one with a one-to-one mapping (type 1) and one with a indirect mapping (type 2).
Regardless of the type, files in all entries shall have the same record configuration;
- an EFPBR record shall not contain more than one occurrence of a given kind of file indicated in tag 'AA' (type 3
link). For instance, an EFPBR record may only contain one reference to an EFEXT1.
4.4.2.15 EFPURI (Phonebook URIs)

This EF contains the URI address that may be linked to a phonebook entry. Several URI addresses can be attached to
one EFADN record, using one or several EFPURI. The number of URI addresses may be equal to or less than the amount of
records in EFADN. 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 EFADN file. This record cannot be shared between several
phonebook entries.
3GPP
Release 15 163 3GPP TS 31.102 V15.21.0 (2018-0610)
Structure of EFPURI

SFI: 'YY'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

specified in EFPBR)
- URI Address.
Content:
- The URI Address associated to the ADN Record.
Coding:
- Same as URI TLV data object in EFIMPU defined in TS 31.103 [64].
- ADN file SFI.
Content:
Coding:
- ADN file Record Identifier.
Content:
Coding:
- binary.
4.4.3 Contents of files at the DF GSM-ACCESS level

(Files required for GSM Access)
The Efs described in this clause are required for the USIM application to be able to access service through a GSM
network.
The presence of this DF and thus the support of a GSM access is indicated in the 'USIM Service Table' as service no.
'27' being available.
3GPP
Release 15 164 3GPP TS 31.102 V15.21.0 (2018-0610)
4.4.3.1 EFKc (GSM Ciphering key Kc)

This EF contains the ciphering key Kc and the ciphering key sequence number n for enciphering in a GSM access
network.

SFI: '01'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 8 Ciphering key Kc M 8 bytes
9 Ciphering key sequence number n M 1 byte
- Ciphering key Kc.

Coding:
- the least significant bit of Kc is the least significant bit of the eighth byte. The most significant bit of Kc is the most
significant bit of the first byte.
- Ciphering key sequence number n

Coding:
b8 b7 b6 b5 b4 b3 b2 b1
N
NOTE: TS 24.008 [9] defines the value of n=111 as "key not available". Therefore the value '07' and not 'FF'
should be present following the administrative phase.
4.4.3.2 EFKcGPRS (GPRS Ciphering key KcGPRS)

This EF contains the ciphering key KcGPRS and the ciphering key sequence number n for GPRS (see TS 23.060 [7]).

SFI: '02
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 8 Ciphering key KcGPRS M 8 bytes
9 Ciphering key sequence number n for GPRS M 1 byte
- Ciphering key KcGPRS.

Coding:
the least significant bit of KcGPRS is the least significant bit of the eighth byte. The most significant bit of KcGPRS
is the most significant bit of the first byte.
- Ciphering key sequence number n for GPRS.

Coding:
3GPP
Release 15 165 3GPP TS 31.102 V15.21.0 (2018-0610)
b8 b7 b6 b5 b4 b3 b2 b1
n
NOTE: TS 24.008 [9] defines the value of n=111 as "key not available". Therefore the value '07' and not 'FF'
should be present following the administrative phase.
4.4.3.3 Void
4.4.3.4 EFCPBCCH (CPBCCH Information)

This EF contains information concerning the CPBCCH according to TS 44.018 [28].
CPBCCH storage may reduce the extent of a Mobile Station's search of CPBCCH carriers when selecting a cell. The
CPBCCH carrier lists shall be in accordance with the procedures specified TS 23.022 [29]. The MS stores CPBCCH
information (from the System Information 19 message, Packet System Information 3, and Packet System Information 3
bis) on the USIM. The same CPBCCH carrier shall never occur twice in the list.

File size: 2n bytes Update activity: high
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 2 Element 1 of CPBCCH carrier list M 2 bytes
: : : :
2n-1 to 2n Element n of CPBCCH carrier list M 2 bytes
- Element in CPBCCH carrier list

Coding:
Byte 1: first byte of CPBCCH carrier list element
b8 b7 b6 b5 b4 b3 b2 b1
LSB of ARFCN
:
:
:
:
:
:
:
Byte 2: second byte of CPBCCH carrier list element
b8 b7 b6 b5 b4 b3 b2 b1
:
MSB of ARFCN
High/Low band indicator
bits b4 to b7 are RFU
Empty indicator
- ARFCN (10 bits) as defined in TS 45.005 [34].
- High/Low band indicator: If the ARFCN indicates possibly a channel in the DCS 1800 or a channel in the
PCS 1900 band, if the bit is set to '1' the channel is in the higher band (GSM 1900). If the bit is set to '0',
3GPP
Release 15 166 3GPP TS 31.102 V15.21.0 (2018-0610)
the lower band (GSM 1800) is indicated. If ARFCN indicates a unique channel, this indicator shall be set
to '0'.
- Empty indicator: If this bit is set to '1', no valid CPBCCH carrier is stored in this position. If the Empty
Indicator is set to '1', the content of the CPBCCH carrier field shall be ignored. The empty indicator shall
also be used, and set to '1', if storage of fewer than maximum number n, of CPBCCH carrier fields is
required.
4.4.3.5 EFInvScan (Investigation Scan)

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

Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 Investigation scan flags M 1 byte
- Investigation scan flags
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
In limited service mode

After successful PLMN selection
Bits b3 to b8 are coded RFU
A '1' in a bit position indicates that the investigation scan shall be performed for the condition
corresponding to that bit position and a '0' that it shall not be performed.
If this elementary file is not present, no investigation scan shall be performed.
4.4.4 Contents of files at the MexE level

This clause specifies the Efs in the dedicated file DFMexE. It only applies if the USIM supports MexE (see
TS 23.057 [30]).
The presence of this DF is indicated in the 'USIM Service Table' as service no. '41' being available.
The Efs in the Dedicated File DFMexE contain execution environment related information.
3GPP
Release 15 167 3GPP TS 31.102 V15.21.0 (2018-0610)
4.4.4.1 EFMexE-ST (MexE Service table)

This EF indicates which MexE services are available. If a service is not indicated as available in the USIM, the ME
shall not select this service.

File size: X bytes, X ≥ 1 Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

etc.
X Services (8X-7) to (8X) O 1 byte
-Services
Contents: Service n°1: Operator Root Public Key
Service n°2: Administrator Root Public Key
Service n°3: Third Party Root Public Key
Service n°4: RFU
Coding:
the coding rules of the USIM Service Table apply to this table.
4.4.4.2 EFORPK (Operator Root Public Key)

This EF contains the descriptor(s) of certificates containing the Operator Root Public Key. This EF shall only be
allocated if the operator wishes to verify applications and certificates in the MexE operator domain using a root public
key held in the USIM. Each record of this EF contains one certificate descriptor.
For example, an operator may provide a second key for recover disaster procedure in order to limit OTA data to load.

Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 Parameters indicator M 1 byte
2 Flags M 1 byte
3 Type of certificate M 1 byte
4 to 5 Key/certificate file identifier M 2 bytes
6 to 7 Offset into key/certificate file M 2 bytes
8 to 9 Length of key/certificate data M 2 bytes
10 Key identifier length (X) M 1 byte
11 to 10+X Key identifier M X bytes
- Parameter indicator
Contents:
The parameter indicator indicates if record is full and which optional parameters are present
3GPP
Release 15 168 3GPP TS 31.102 V15.21.0 (2018-0610)
Coding: bit string
b8 b7 b6 b5 b4 b3 b2 b1
Certificate descriptor is valid (bit1=0 key

descriptor is valid)
Reserved bit set to 1 (bitx=0 optional parameter
present)
- Flags
Contents:
The authority flag indicates whether the certificate identify an authority (i.e. CA or AA) or not.
Coding: bit string
b8 b7 b6 b5 b4 b3 b2 b1
Authority certificate (bit=1 certificate of an

authority)
RFU
RFU
- Type of certificate
Contents:
This field indicates the type of certificate containing the key.
Coding: binary:
0 : WTLS
1 : X509
2 : X9.68
Other values are reserved for further use
- Key/certificate File Identifier
Contents:
these bytes identify an EF which is the key/certificate data file (see clause 4.4.4.5), holding the actual key/certificate
data for this record.
Coding:
byte 4: high byte of Key/certificate File Identifier;
byte 5: low byte of Key/certificate File Identifier.
- Offset into Key/certificate File
Contents:
these bytes specify an offset into the transparent key/certificate data File identified in bytes 4 and 5.
Coding:
byte 6: high byte of offset into Key/certificate Data File;
byte 7: low byte of offset into Key/certificate Data File
- Length of Key/certificate Data
Contents:
these bytes yield the length of the key/certificate data, starting at the offset identified in "Offset into Key/certificate
File" field.
Coding:
byte 8: high byte of Key/certificate Data length;
byte 9: low byte of Key/certificate Data length.
- Key identifier length
3GPP
Release 15 169 3GPP TS 31.102 V15.21.0 (2018-0610)
Contents:
This field gives length of key identifier
Coding:
binary
- Key identifier
Contents:
This field provides a means of identifying certificates that contain a particular public key (chain building) and linking
the public key to its corresponding private key. For more information about value and using see TS 23.057 [30].
Coding:
octet string
NOTE: transparent key/certificate data longer than 256 bytes may be read using successive READ BINARY
commands.
4.4.4.3 EFARPK (Administrator Root Public Key)

This EF contains the descriptor(s) of certificates containing the Administrator Root Public Key. This EF shall only be
allocated if the SIM issuer wishes to control the Third Party certificates on the terminal using an Administrator root
public key held in the USIM. Each record of this EF contents one certificate descriptor.
This file shall contain only one record.

Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

2 Flags M 1 byte
For contents and coding of all data items see the respective data items of the EF ORPK (clause 4.4.4.2).
3GPP
Release 15 170 3GPP TS 31.102 V15.21.0 (2018-0610)
4.4.4.4 EFTPRPK (Third Party Root Public Key)

This EF contains descriptor(s) of certificates containing the Third Party root public key (s). This EF shall only be
allocated if the USIM issuer wishes to verify applications and certificates in the MexE Third Party domain using root
public key(s) held in the USIM. This EF can contain one or more root public keys. Each record of this EF contains one
certificate descriptor.
For example, an operator may provide several Third Party Root Public Keys.
Identifier:'4F43' Structure: linear fixed Optional

Record length: X + Y + 11 bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

2 Flags M 1 byte
11+X Certificate identifier length (Y) M 1 byte
12+X to Certificate identifier M Y bytes
11+X+Y
- Certificate identifier length

Contents:
This field gives the length of the certificate identifier
Coding:
binary
- Certificate identifier
Contents:
This field identifies the issuer and provides an easy way to find a certificate. For more information about the value and
usage see TS 23.057 [30].
Coding:
Octet string
For contents and coding of all other data items see the respective data items of the EF ORPK (clause 4.4.4.2).
4.4.4.5 EFTKCDF (Trusted Key/Certificates Data Files)

Residing under DFMexE, there may be several key/certificates data files. These Efs containing key/certificates data shall
have the following attributes:
3GPP
Release 15 171 3GPP TS 31.102 V15.21.0 (2018-0610)
Identifier: '4FXX' Structure: transparent Optional

File size: Y bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to Y Key/Certificate Data M Y bytes
Contents and coding:
Key/certificate data are accessed using the key/certificates descriptors provided by EF TPRPK (see clause 4.4.4.4).
The identifier '4FXX' shall be different from one key/certificate data file to another. For the range of 'XX', see
TS 31.101 [11]. The length Y may be different from one key/certificate data file to another.
4.4.5 Contents of files at the DF WLAN level

This clause describes the additional files that are used for WLAN purposes.
DFWLAN shall be present at the ADFUSIM level if either of the services nº59, nº60, nº61, nº62, nº63, nº66, n°81, n°82,
n°83, n°84 or n°88 are "available" in the corresponding EFUST (USIM Service Table).
4.4.5.1 EFPseudo (Pseudonym)

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

SFI : '01'
File size: Y bytes (Yn+2) Update activity: high
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 2 Pseudonym Length M 2 bytes
3 to n+2 Pseudonym M n bytes
-Pseudonym Length
Contents:
- these bytes give the number of bytes of the following data item containing the Pseudonym value.
Coding:
- unsigned length coded on 2 bytes
- Pseudonym.
Contents:
-Pseudonym to be used as the username part of the NAI
Coding:
- As described for the user portion of the NAI in TS 33.234 [41]. Unused bytes shall be set to 'FF' and shall
not be considered as a part of the value.
3GPP
Release 15 172 3GPP TS 31.102 V15.21.0 (2018-0610)
4.4.5.2 EFUPLMNWLAN (User controlled PLMN selector for I-WLAN Access)

This EF contains the coding for preferred PLMNs to be used for WLAN PLMN Selection. This information is
determined by the user and defines the preferred PLMNs of the user in priority order. The first PLMN entry indicates
the highest priority and the nth PLMN entry indicates the lowest. It shall be possible to store at least the number of
PLMNs specified in TS 24.234 [40].

SFI: '02'
File size: 3n (where n 10) Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

: :
: :
(3n-2) to 3n Nth PLMN (lowest priority) O 3 bytes
- PLMN
Contents:
Coding:
4.4.5.3 EFOPLMNWLAN (Operator controlled PLMN selector for I-WLAN Access)

This EF contains the coding for operator preferred PLMNs to be used for WLAN PLMN Selection. This information is
determined by the operator and defines the operator preferred PLMNs in priority order. The first PLMN entry indicates
the highest priority and the nth PLMN entry indicates the lowest. It shall be possible to store at least the number of
PLMNs specified in TS 24.234 [40].

SFI: '03'
File size: 3n (where n 10) Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

: :
: :
(3n-2) to 3n Nth PLMN (lowest priority) O 3 bytes
3GPP
Release 15 173 3GPP TS 31.102 V15.21.0 (2018-0610)
- PLMN
Contents:
Coding:
4.4.5.4 EFUWSIDL (User controlled WLAN Specific Identifier List)

This file contains the user preferred list of WLAN specific identifier (WSID) for WLAN selection in priority order. The
first record indicates the highest priority and the nth record indicates the lowest. This file is used for WLAN selection
and shall store a list of at least the number of WSIDs specified in TS 24.234 [40].

SFI: '04'
Record size: X+1 bytes Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 Length of WSID M 1 bytes
2 to X + 1 WSID M X bytes
-Length of WSID
Contents:
- this byte gives the number of bytes of the following data item containing the WSID.
Coding:
- unsigned length coded on one byte
-WSID
Contents:
- WLAN specific identifier (WSID) as defined in TS 24.234 [40].
Coding:
- binary. Unused bytes shall be set to 'FF' and not used either as a part of the value or for length calculation.
4.4.5.5 EFOWSIDL (Operator controlled WLAN Specific IdentifierList)

This file contains the operator preferred list of WLAN specific identifier (WSID) for WLAN selection in priority order.
The first record indicates the highest priority and the nth record indicates the lowest. This file is used for WLAN
selection It shall be possible to store at least the number of PLMNs specified in TS 24.234 [40].

SFI: '05'
Record size: X + 1 bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

3GPP
Release 15 174 3GPP TS 31.102 V15.21.0 (2018-0610)
-Length of WSID
Contents:
- this byte gives the number of bytes of the following data item containing the WSID.
Coding:
- unsigned length coded on one byte
-WSID
Contents:
- WLAN specific identifier (WSID) as defined in TS 24.234 [40].
Coding:
- binary. Unused bytes shall be set to 'FF' and not used either as a part of the value or for length calculation.
4.4.5.6 EFWRI (WLAN Reauthentication Identity)

This EF contains a list of parameters linked to a re-authentication identity to be used in fast re-authentication. Re-
authentication identities and related parameters (Master Key and Counter Value) are provided as part of a previous
authentication sequence.

SFI: '06'
File size: n bytes, (n  J+K+L+6) Update activity: high
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 Reauthentication Identity Tag '80' M 1 byte
2 Re-authentication Identity Length M 1 byte
3 to J+2 Re-authentication Identity Value M J bytes
J+3 Master Key Tag '81' M 1 byte
J+4 Master Key Length M 1 byte
J+5 to J+K+4 Master Key Value M K bytes
J+K+5 Counter Tag '82' M 1 byte
J+K+6 Counter Length M 1 byte
J+K+7 to Counter Value M L bytes
J+K+L+6
- Reauthentication Identity
Contents:
- Re-authentication identity TLV to be used as the username part of the NAI.
Coding:
Tag '80'
Unsigned length on 1 byte
Value: As described for the user portion of the NAI in TS 33.234 [41]. Unused bytes shall be set to 'FF' and shall not be
considered as a part of the value.
- Master Key
Contents:
- Master Key TLV.
Coding:
Tag '81'
Value: As described in TS 33.234 [41].
3GPP
Release 15 175 3GPP TS 31.102 V15.21.0 (2018-0610)
- Counter
Contents:
- Counter TLV
Coding:
Tag '82'
Value: As described in TS 33.234 [41].
4.4.5.7 EFHWSIDL (Home I-WLAN Specific Identifier List)

This file contains the Home I-WLAN specific identifier list (WSID list) for I-WLAN selection in priority order. The
WSIDs in this list are known to connect to the HPLMN. The first record indicates the highest priority and the n th record
indicates the lowest. This file is used for I-WLAN selection. It shall be possible to store at least the number of WSIDs
specified in TS 24.234 [40].

SFI: '07'
Record size: X + 1 bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

For contents and coding see EFOWSIDL.
4.4.5.8 EFWEHPLMNPI (I-WLAN Equivalent HPLMN Presentation Indication)

This EF contains an indication to the ME for the presentation of the available EHPLMN(s) during I-WLAN selection
procedures. The usage of the I-WLAN EHPLMN presentation indication is defined in TS 24.234 [40].

SFI: '08'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 I-WLAN EHPLMN Presentation Indication M 1 byte
- I-WLAN EHPLMN Presentation Indication:

Contents:
I-WLAN EHPLMN display mode
Coding:
- '00' - No preference for the display mode
- '01' - Display the highest-priority available EHPLMN only
3GPP
Release 15 176 3GPP TS 31.102 V15.21.0 (2018-0610)
- '02' - Display all the available EHPLMNs
4.4.5.9 EFWHPI (I-WLAN HPLMN Priority Indication)

This EF contains an indication to the ME for the selection of the I-WLAN EHPLMN or the I-WLAN last Registered
PLMN. The usage of the I-WLAN HPLMN Priority Indication file is defined in TS 24.234 [40].

SFI: '09'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 I-WLAN Last RPLMN Selection Indication M 1 byte
- I-WLAN Last RPLMN Selection Indication:

Contents:
I-WLAN Last RPLMN Selection Indication
Coding:
- '00' - The UE shall attempt registration on the last I-WLAN RPLMN as described in TS 24.234 [40]
- '01' - The UE shall attempt registration on the I-WLAN home network as described in TS 24.234 [40]
4.4.5.10 EFWLRPLMN (I-WLAN Last Registered PLMN)

This EF contains I-WLAN Last Registered PLMN Selection. The usage of the I-WLAN Last Registered PLMN is
Identifier: '4F4A' Structure: transparent Optional

SFI: '0A'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 3 I-WLAN Last Registered PLMN M 3 bytes
- I-WLAN Last Registered PLMN

Contents:
Coding:
3GPP
Release 15 177 3GPP TS 31.102 V15.21.0 (2018-0610)
4.4.5.11 EFHPLMNDAI (HPLMN Direct Access Indicator)

This EF contains HPLMN Direct Access related informations. The usage of the HPLMN Direct Access Indicator file is
Identifier: '4F4B' Structure: transparent Optional

SFI: '0B'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 HPLMN Direct Access Indication M 1byte
- HPLMN Direct Access Indication:

Contents:
HPLMN Direct Access Indication
Coding:
- '00' – HPLMN Direct Access Indicator is disabled
- '01' – HPLMN Direct Access Indicator is enabled
4.4.6 Contents of files at the DF HNB level
4.4.6.1 Introduction
This clause describes the additional files that are used for Home (e)NodeB purposes.
DFHNB shall be present at the ADFUSIM level if service nº86 and/or service nº90 isare "available" in EFUST .
4.4.6.2 EFACSGL (Allowed CSG Lists)

This EF contains the coding for CSG ID belonging to the Allowed CSG lists. Furthermore, for each CSG ID in the list,
a link to the corresponding HNB name and CSG Type may be provided.

SFI: '01'
Record length: X Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to X CSG Lists TLV object M X bytes
Note: The CSG List in different records may contain the same PLMN
The CSG List TLV object shall contain only one PLMN TLV object, Tag '80', and at least one CSG information TLV,
Tag '81'. A record may contain one or more CSG List TLV objects. This means that all CSG Ids in one CSG List TLV
object belong to the same PLMN.
3GPP
Release 15 178 3GPP TS 31.102 V15.21.0 (2018-0610)
CSG List Tags

CSG List TLV object Tag 'A0'
CSG List information

CSG List Tag 'A0' M 1
Length Y M Note
PLMN Tag '80' M 1
Length A M Note
PLMN -- M A
CSG Information Tag '81' M 1
Length W M Note
CSG Information - M W
- PLMN Tag '80'
Contents:
Coding:
CSG Information Tag '81'
Tag '81' Coding:
1 CSG Type indication M 1 byte

2 HNB Name indication M 1 byte
3 to W CSG ID M W-2 bytes
Note: The length of the CSG ID is calculated from the TLV object length
- CSG Type indication
Contents:
the CSG Type for the subsequent CSG ID.
Coding:
a value of '00' indicates that the CSG Type is to be taken from other sources (e.g. stored in the non-
volatile memory of the ME). A value in the range '01' to 'FE' indicates the record number in EF CSGT
that shall be displayed as the CSG Type.
- HNB Name indication
Contents:
the HNB name for the subsequent CSG ID.
Coding:
3GPP
Release 15 179 3GPP TS 31.102 V15.21.0 (2018-0610)
a value of '00' indicates that the HNB name is to be taken from other sources (e.g. broadcasted by the
Home Node B or stored in the non-volatile memory of the ME). A value in the range '01' to 'FE'
indicates the record number in EFHNBN that shall be displayed as the HNB name.
- CSG ID
Contents:
CSG ID which is part of the allowed CSG list.
Coding:
the CSG ID shall be encoded as defined in TS 23.003 [25]. The CSG ID is coded left justified, i.e. the
most significant bit of the CSG ID is coded on bit 8 of byte 3, over the number of bits as specified in
TS 23.003 [25] using bytes 3 to W . The unused rightmost bits of byte W shall be set 1.
3GPP
Release 15 180 3GPP TS 31.102 V15.21.0 (2018-0610)
4.4.6.3 EFCSGT (CSG Type)

This EF contains the CSG Type. The CSG Type is defined in TS 22.220 [54]. The association between a CSG ID and
the corresponding CSG Type is provided in EFACSGL. The CSG Type may be provided in text or in graphic format.

SFI: '02'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to X CSG Type TLV objects M X bytes
CSG Type tags

Text CSG Type Tag '89'
Graphics CSG Type Tag '80' or '81'
CSG Type information
Contents:
CSG Type contains either Text CSG Type or Graphic CSG Type or both the Graphic and Text CSG Types
Coding:
Text CSG Type:

Text CSG Type Tag '89' M 1
Length K M Note
Text CSG Type -- M K
Note: The length is coded according to ISO/IEC 8825-1 [35].
Graphic CSG Type:

Graphic CSG Type Tag '80' or '81' M 1
Length K+1 M Note 1
Graphic CSG Type Icon Qualifier -- M 1
Graphic CSG Type Icon Link -- M K (Note 2)
Note 2: The tag value indicates the type and format of the Icon Link that is provided in the
TLV value field (e.g. Tag '80' indicates that the Icon link is a URI, while Tag '81'
indicates that the Icon Link is the record number of the corresponding image in
EFIMG).
- Text CSG Type Tag '89'
Contents:
Tag value for the CSG Type in text format.
3GPP
Release 15 181 3GPP TS 31.102 V15.21.0 (2018-0610)
Coding:
- '89' = the Text CSG Type is coded using one of the UCS2 code options as defined in TS 31.101 [11].
- Graphic CSG Type Tag
Contents:
Tag value for the CSG Type in graphic format with the Icon Qualifier or an Icon Link
Coding:
- '80' = the Graphic CSG Type Icon Link is an URI
- '81' = the Graphic CSG Type Icon Link is a pointer to the record number of the corresponding image in
EFIMG,
- Graphic CSG Type Icon Qualifier

Contents:
The icon qualifier indicates to the ME how the icon shall be used.
Coding:
- '01' = icon is self-explanatory, i.e. if displayed, it replaces the corresponding name in text format.
- '02' = icon is not self-explanatory, i.e. if displayed, it shall be displayed together with the corresponding
name in text format.
- Graphic CSG Type Icon Link

Contents:
Link to the icon. This link shall point to a UICC resource.
Coding:
- When the Tag value indicates an URI (i.e. Tag = '80') , the Icon Link shall be encoded to an octet string
according to UTF-8 encoding rules as described in IETF RFC 3629 [48] (e.g.
http://127.0.0.1:3516/pub/files/csgtype.jpg).
- When the Tag value indicates that the Icon Link contains the record number of the corresponding image in
EFIMG (i.e. Tag = '81'), the Icon Link shall be encoded in binary.
3GPP
Release 15 182 3GPP TS 31.102 V15.21.0 (2018-0610)
4.4.6.4 EFHNBN (Home NodeB Name)

This EF contains the HNB name. The HNB name is defined in TS 22.220 [54]. HNB name is a common name referring
to HNB/HeNB. The association between a CSG ID and the corresponding HNB name is provided in EF ACSGL.

SFI: '03'
Access Conditions:
READ PIN
UPDATE PIN
ACTIVATE ADM
DEACTIVATE ADM

1 to X HNB Name TLV object M X bytes
HNB Name tags

HNB Name Tag '80'
HNB Name information

HNB Name Tag '80' M 1
Length K M Note
HNB Name -- M K
- HNB Name Tag '80'
Contents:
name of the HNB or HeNB.
Coding:
coded using one of the UCS2 code options as defined in TS 31.101 [11].
4.4.6.5 EFOCSGL (Operator CSG Lists)

This EF contains the coding for CSG Ids belonging to the Operator CSG lists. Furthermore, for each CSG ID in the list,
a link to the corresponding HNB name and CSG type may be provided. Within one PLMN the first occurrence of CSG
ID indicates the highest priority CSG ID and the last occurrence indicates the lowest.
NOTE 1: There is no requirement for the ME to take the priority into account.
Additionally, if service n°92 is "available", this EF allows the HPLMN to control, on a per PLMN basis, which
available CSGs are displayed by the ME during a manual CSG selection. If there is no CSG display indicator for a
PLMN, the ME shall display the available CSGs according to the value in EFAD byte 3 bit 2.
NOTE 2: Operators should ensure that all CSG display indicators have the same value if the same PLMN is used in
multiple CSG List TLV objects.
3GPP
Release 15 183 3GPP TS 31.102 V15.21.0 (2018-0610)

SFI: '04'
Record length: Y bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to X Operator CSG List TLV objects M X bytes
Note: The CSG List in different records may contain the same PLMN
The Operator CSG List TLV object shall contain only one PLMN TLV object, Tag '80', and at least one Operator CSG
information TLV, Tag '81'. A record may contain one or more Operator CSG List TLV objects. This means that all
CSG Ids in one Operator CSG List TLV object belong to the same PLMN.
Additionally, the Operator CSG List TLV object may contain one CSG Display Indicator TLV object, if service n°92 is
available.
CSG List Tags

Operator CSG List TLV object Tag 'A0'
CSG List information

CSG List Tag 'A0' M 1
Length Y M Note
PLMN Tag '80' M 1
Length A M Note
PLMN -- M A
CSG Information Tag '81' M 1
Length W M Note
CSG Information - M W
CSG Display indicator tag '82' O 1
Length Z O Note
CSG Display indicator - O Z
- PLMN Tag '80'
Contents:
Coding:
- CSG Information Tag '81'
Tag '81' Coding:
1 CSG Type indication M 1 byte

2 HNB Name indication M 1 byte
3 to W CSG ID M W-2 bytes
Note: The length of the CSG ID is calculated from the TLV object length
- CSG Type indication
3GPP
Release 15 184 3GPP TS 31.102 V15.21.0 (2018-0610)
Contents:
the CSG Type for the subsequent CSG ID.
Coding:
a value of '00' indicates that the CSG Type is to be taken from other sources (e.g. stored in the
non-volatile memory of the ME). A value in the range '01' to 'FE' indicates the record number in
EFCSGT that shall be displayed as the CSG Type.
- HNB Name indication
Contents:
the HNB name for the subsequent CSG ID.
Coding:
a value of '00' indicates that the HNB name is to be taken from other sources (e.g. broadcasted by
the Home Node B or stored in the non-volatile memory of the ME). A value in the range '01' to
'FE' indicates the record number in EFHNBN that shall be displayed as the HNB name.
- CSG ID
Contents:
CSG ID which is part of the allowed CSG list.
Coding:
the CSG ID shall be encoded as defined in TS 23.003 [25]. The CSG ID is coded left justified, i.e.
the most significant bit of the CSG ID is coded on bit 8 of byte 3, over the number of bits as
specified in TS 23.003 [25] using bytes 3 to W. The unused rightmost bits of byte W shall be set 1.
- CSG display indicator Tag '82':
Coding:
- '00' All available CSG Ids can be displayed during a manual CSG selection
- '01' Only CSG Ids contained in Operator CSG lists shall be displayed during a manual CSG
selection
Unused bytes shall be set to 'FF'
4.4.6.6 EFOCSGT (Operator CSG Type)

This EF contains the Operator CSG Types. The CSG Type is defined in TS 22.220 [54]. The association between an
Operator CSG ID and the corresponding Operator CSG Type is provided in EFOCSGL. The Operator CSG Type may be
provided in text or in graphic format.

SFI: '05'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to X CSG Type TLV objects M X bytes
3GPP
Release 15 185 3GPP TS 31.102 V15.21.0 (2018-0610)
For coding see EFCSGT
4.4.6.7 EFOHNBN (Operator Home NodeB Name)

This EF contains the Operator HNB names. The HNB name is defined in TS 22.220 [54]. HNB Name is a common
name referring to HNB/HeNB. The association between an Operator CSG ID and the corresponding Operator HNB
name is provided in EFOCSGL.

SFI: '06'
Access Conditions:
READ PIN
UPDATE ADM
ACTIVATE ADM
DEACTIVATE ADM

1 to X HNB Name TLV object M X bytes
For coding see EFHNBN
4.4.7 Void
4.4.8 Contents of files at the DF ProSe level
This clause describes the additional files that are used for ProSe purposes.
DFProSe shall be present at the ADFUSIM level if service nº101 is "available" in EFUST .
4.4.8.2 EFPROSE_MON (ProSe Monitoring Parameters)

If service n°1 is "available" in the ProSe Service Table, this file shall be present.
This EF contains the authorized PLMNs for restricted ProSe direct discovery for public safety as described in TS
24.334 [70]. This file shall be used only if the ME is authorized as per content of EFAD or received service authorization
from the ProSe Function.
Each record shall be associated with a different PLMN.

SFI: '01'
Record size: Z bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to Z ProSe Discovery monitoring parameters TLV O Z bytes
data object
ProSe Discovery monitoring parameters information
3GPP
Release 15 186 3GPP TS 31.102 V15.21.0 (2018-0610)
ProSe Discovery monitoring parameters 'A0' M 1

TLV
Length X M Note
PLMN Tag '80' M 1
Length L1 M Note
PLMN value -- M L1
Model Tag '82' O 1
Length 1 C 1
Model value -- C 1
- PLMN
Contents:
As described in TS 24.333 [71], the PLMN code of the operator in which the UE is authorised to use ProSe
direct discovery monitoring.
Coding:
As defined for the <X>/MonitoringPolicy/<X>/PLMN leaf in TS 24.333 [71].
- Model
Contents:
Model used for the ProSe direct discovery, as described in TS 24.334 [70].
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
b1 indicates if the UE is authorised for Restricted

Model A monitoring policy
Model B discoveree policy.
RFU (see TS 31.101 [11])
If the data object is missing, the UE shall behave as if only Restricted Model A monitoring policy is allowed. All
other values are reserved.
4.4.8.3 EFPROSE_ANN (ProSe Announcing Parameters)

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

SFI: '02'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to Z ProSe Discovery announcing parameters TLV O Z bytes
data object
ProSe Discovery announcing parameters information
3GPP
Release 15 187 3GPP TS 31.102 V15.21.0 (2018-0610)
ProSe Discovery announcing 'A0' M 1

parameters TLV
Length X M Note 1
PLMN Tag '80' M 1
Length L1 M Note 1
PLMN value -- M L1
Range Tag (Note 3) '81' O 1
Length L2 C Note 1
Range value -- C L2
Model Tag '82' O 1
Length 1 C 1
Model value -- C 1
Note 3: The Range data object is obsolete from Rel-13 onwards and shall be ignored if
present.
- PLMN
Contents:
As described in TS 24.333 [71], the PLMN code of the operator in which the UE is authorised to use ProSe
direct discovery announcing.
Coding:
As defined for the <X>/AnnouncingPolicy/<X>/PLMN leaf in TS 24.333 [71].
- Model
Contents:
Model used for the ProSe direct discovery, as described in TS 24.334 [70].
Coding:
b8 b7 b6 b5 b4 b3 b2 b1

Model A announcing policy
Model B discoverer policy.
RFU (see TS 31.101 [11])
If the data object is missing, the UE shall behave as if only Restricted Model A announcing policy is allowed.
All other values are reserved.
4.4.8.4 EFPROSEFUNC (HPLMN ProSe Function)

This EF contains the IP address of the HPLMN ProSe Function.
NOTE: only usage of the first record is supported in the current release of the specification.

SFI: '03'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to Z HPLMN ProSe Function Address TLV data M Z bytes
object
HPLMN ProSe Function information
3GPP
Release 15 188 3GPP TS 31.102 V15.21.0 (2018-0610)

HPLMN ProSe Function Tag '80' M 1
Length A+1 M 1
Address type -- M 1
HPLMN ProSe Function Address -- M A
- Address type
Contents:
Type of the HPLMN ProSe Function address.
Coding:
A value of '00' indicates FQDN, a value of '01' indicates IPv4, a value of '02' indicates IPv6. All other
values are reserved.
- HPLMN ProSe Function Address
Contents:
Address of the HPLMN ProSe function.
Coding:
Depending on the Address type. When the HPLMN ProSe Function type is set to '00', the
corresponding HPLMN ProSe Function Address shall be encoded to an octet string according to UTF-
8 encoding rules as specified in IETF RFC 3629 [48].
4.4.8.5 EFPROSE_RADIO_COM (ProSe Direct Communication Radio Parameters)

This EF contains the radio paramenters 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 [70]. This file shall be used only if the ME is authorized as per content
of EFAD or received service authorization from the ProSe Function.

SFI: '04'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 ProSe Direct Communication not served by E- M 1 byte
UTRAN
2 to Z + 1 ProSe Radio parameters TLV data object M Z bytes
The file may contain one or more ProSe Radio parameters TLV data objects.
ProSe Direct Communication not served by E-UTRAN:
3GPP
Release 15 189 3GPP TS 31.102 V15.21.0 (2018-0610)
Contents:
Indicates if the ME is authorized to perform ProSe Direct Communication and/or one-to-one ProSe direct
communication when not served by E-UTRAN.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
b1=0 indicates that the UE is not authorised to

perform one-to-many ProSe direct communication when
not served by E-UTRAN
b1=1 indicates that UE is authorised to perform one-
to-many ProSe direct communication when not served
by E-UTRAN
perform one-to-one ProSe direct communication when
not served by E-UTRAN
b2=1 indicates that the UE is authorised to perform
one-to-one ProSe direct communication when not
served by E-UTRAN.
RFU (see TS 31.101 [11])
ProSe Radio parameters information:

ProSe Direct Communication 'A0' M 1
parameters TLV
Length X M Note 1
Length L1 M Note 1
Geographical Area – Polygon value -- M L1
Radio parameters Tag '81' M 1
Length L2 M Note 1
Radio parameters value -- M L2
Each ProSe Radio parameters TLV data object shall contain one or more Geographical Area objects and one Radio
parameters object.

Contents:
Coding:
: : : :
(6n-5) to 6n-3 Latitude of point n M 3 bytes
(6n-2) to 6n Longitude of point n M 3 bytes
not apply to the number of coordinates in a geographical area described as a polygon for ProSe
communications.
- Radio parameters Tag '81'

Contents:
The radio parameters used for ProSe Direct Communication
Coding:
Coded as SL-Preconfiguration in 3GPP TS 36.331 [74].
3GPP
Release 15 190 3GPP TS 31.102 V15.21.0 (2018-0610)
4.4.8.6 EFPROSE_RADIO_MON (ProSe Direct Discovery Monitoring Radio Parameters)


SFI: '05'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 ProSe Direct Discovery Monitoring not served M 1 byte
by E-UTRAN
ProSe Direct Discovery monitoring not served by E-UTRAN:
Contents:
Indicates if the ME is authorized to perform restricted ProSe Direct Discovery monitoring when not served by
E-UTRAN.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1

perform ProSe direct discovery model A monitoring
when not served by E-UTRAN
ProSe direct discovery model A monitoring when not
served by E-UTRAN
perform ProSe direct discovery model B discoveree
operation when not served by E-UTRAN
ProSe direct discovery model B discoveree operation
when not served by E-UTRAN.
RFU (see TS 31.101 [11])
ProSe Radio parameters information

ProSe Radio parameters TLV 'A0' M 1
Length X M Note 1
Length L1 M Note 1
Length L2 M Note 1
parameters object.
3GPP
Release 15 191 3GPP TS 31.102 V15.21.0 (2018-0610)
Contents:
Coding:
: : : :
communications.

Contents:
Coding:
4.4.8.7 EFPROSE_RADIO_ANN (ProSe Direct Discovery Announcing Radio Parameters)


SFI: '06'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 ProSe Direct Discovery Announcing not M 1 byte
served by E-UTRAN
ProSe Direct Discovery announcing not served by E-UTRAN:
Contents:
Indicates if the ME is authorized to perform restricted ProSe Direct Discovery announcing when not served by
E-UTRAN.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1

perform ProSe direct discovery model A announcing
when not served by E-UTRAN
ProSe direct discovery model A announcing when not
served by E-UTRAN
perform ProSe direct discovery model B discoverer
operation when not served by E-UTRAN
3GPP
Release 15 192 3GPP TS 31.102 V15.21.0 (2018-0610)

ProSe direct discovery model B discoverer operation
when not served by E-UTRAN.
RFU (see TS 31.101 [11])
ProSe Radio parameters information

ProSe Radio parameters TLV 'A0' M 1
Length X M Note 1
Length L1 M Note 1
Length L2 M Note 1
parameters object.

Contents:
Coding:
: : : :
communications.

Contents:
Coding:
4.4.8.8 EFPROSE_POLICY (ProSe Policy Parameters)

This EF contains the policy paramenters to be used for ProSe direct communication for public safety, as described in
TS 24.334 [70]. This file shall be used only if the ME is authorized as per content of EFAD or received service
authorization from the ProSe Function.
Each record shall be associated with a different ProSe group.
3GPP
Release 15 193 3GPP TS 31.102 V15.21.0 (2018-0610)

SFI: '07'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to Z ProSe Policy parameters TLV data object M Z bytes
ProSe Policy parameters information:

ProSe Policy parameters Tag 'A0' M 1
Length X M Note
ProSe Layer-2 Group ID tag '80' M 1
Length 3 M 1
ProSe Layer-2 Group ID -- M 3
ProSe UE ID tag '81' M 1
Length 3 M 1
ProSe UE ID -- M 3
ProSe Group IP multicast address tag '82' M 1
Length A M 1
ProSe Group IP multicast address -- M A
Address type tag '83' M 1
Length 1 M 1
Address type -- M 1
IPv4 address as source tag '84' O 1
Length 4 C 1
IPv4 address as source -- C 4
Group related security tag '85' M 1
Length B M Note
Group related security contents -- M B
Application Layer Group ID tag '86' O 1
Length C C Note
Application Layer Group ID -- C C
- ProSe Layer-2 Group ID tag '80'
Contents:
Contains the ProSe Layer-2 Group ID, as defined in TS 23.303 [73]
Coding:
As per TS 33.303 [72]
- ProSe UE ID tag '81'
Contents:
Contains the ProSe UE ID, equivalent to the layer-2 source address of the sending UE, as defined in
TS 23.303 [73]
Coding:
As per TS 33.303 [72]
- ProSe Group IP multicast address tag '82'
Contents:
3GPP
Release 15 194 3GPP TS 31.102 V15.21.0 (2018-0610)
IPv4 or IPv6 group IP multicast addressed to be used for ProSe direct communication associated with
the corresponding layer-2 group ID.
Coding:
Depending on the Address type
- Address type tag '83'
Contents:
Type of IP address.
Coding:
A value of '01' indicates IPv4, a value of '02' indicates IPv6. All other values are reserved.
- IPv4 address as source tag '84'
Contents:
IPv4 addressed to be used as source, in case of IPv4 address. This TLV shall be ignored if address
type is different from IPv4.
Coding:
IPv4 address
- Group related security tag '85'
Contents:
Parameters related to the group security.
Coding:
1 to 32 PGK as defined in TS 33.303 [72] M 32 bytes

33 PGK Id as defined in TS 33.303 [72]. M 1 byte
34 Algorithm Info as defined in TS 33.303 [72] M 1 byte
35 to B RFU O (B-34) bytes
- Application Layer Group ID '86'
Contents:
Application layer group that the UE belongs to.
Coding:
As per TS 23.303 [73]
4.4.8.9 EFPROSE_PLMN (ProSe PLMN Parameters)

This EF contains the authorized PLMNs for ProSe direct communication for public safety, as described in TS 24.334
[70]. This file shall be used only if the ME is authorized as per content of EFAD or received service authorization from
the ProSe Function.
3GPP
Release 15 195 3GPP TS 31.102 V15.21.0 (2018-0610)

SFI: '08'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to Z ProSe PLMN parameters TLV data object O Z bytes
ProSe Policy parameters information:

ProSe PLMN parameters Tag 'A0' M 1
Length X M Note
PLMN tag '80' M 1
Length 3 M 1
PLMN -- M 3
Direct communication authorisation tag '81' O 1
Length 1 C 1
Direct communication authorisation -- C 1
- PLMN tag '80'
Contents:
Contains the PLMNs in which the UE is authorised to perform ProSe direct communication when
served by E-UTRAN
Coding:
- Direct communication authorisation tag '81'
Contents:
Indicates if the UE is authorised to use one-to-one and/or one-to-many ProSe direct communication.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
b1 indicates if the UE is authorised for one-to-many

ProSe direct communication
b2 indicates if the UE is authorised for one-to-one
ProSe direct communication.
RFU (see TS 31.101 [11])
If the data object is missing, the UE shall behave as if only one-to-many ProSe direct communication
is authorized in the PLMN. All other values are reserved.
4.4.8.10 EFPROSE_GC (ProSe Group Counter)

This EF contains the PTK ID and Counter associated with the PGK currently in use for a ProSe Group.
3GPP
Release 15 196 3GPP TS 31.102 V15.21.0 (2018-0610)

SFI: '09'
File size: X >= 9 bytes Update activity: high
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to L ProSe Group Counter data object O L bytes
L+1 to 2xL ProSe Group Counter data object O L bytes
: : : :
ProSe Group Counter:

ProSe Group Counter Tag '80' M 1
Length X >= 7 M Note
ProSe Layer-2 Group ID -- M 3
PTK ID -- M 2
Counter -- M 2
RFU -- O X
- ProSe Layer-2 Group ID

Contents:
Contains the ProSe Layer-2 Group ID, as defined in TS 23.303 [73]
Coding:
As per TS 33.303 [72]
- PTK ID
Contents:
Contains the PTK value, as defined in TS 33.303 [72]
Coding:
As per TS 33.303 [72]
- Counter
Contents:
Contains the Counter for the PGK used in the group, as defined in TS 33.303 [72]
Coding:
As per TS 33.303 [72]
3GPP
Release 15 197 3GPP TS 31.102 V15.21.0 (2018-0610)
4.4.8.11 EFPST (ProSe Service Table)

If service n°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.

SFI: '10'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

etc.
-Services
Contents: Service n°1: ProSe direct discovery parameters
Service n°2: HPLMN ProSe Function
Service n°3: ProSe Direct Communication radio parameters
Service n°4: ProSe Direct Discovery monitoring radio parameters
Service n°5: ProSe Direct Discovery announcing radio parameters
Service n°6: ProSe policy parameters
Service n°7: ProSe group counter
Service n°8: ProSe Usage Information Reporting configuration
Service n°9: UICC ProSe Direct Communication usage information reporting
Service n°10 ProSe Group Member Discovery parameters
Service n°11 ProSe Relay parameters
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.
If service n°9 is "available", then service n°8 shall also be "available".
If service n°10 is "available", then service n°1 shall also be "available".
Coding:
Same as coding of USIM Service Table
4.4.8.12 EFPROSE_UIRC (ProSe UsageInformationReportingConfiguration)

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 [70] and TS 32.277 [77]. 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.
3GPP
Release 15 198 3GPP TS 31.102 V15.21.0 (2018-0610)

SFI: '11'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to Z ProSe M Z bytes
UsageInformationReportingConfiguration TLV
data objects
3GPP
Release 15 199 3GPP TS 31.102 V15.21.0 (2018-0610)
ProSe UsageInformationReportingConfiguration parameters information:

ProSe ServerAddress tag '80' C 1
Length A C Note
ProSe ServerAddress -- C A
ProSe CollectionPeriod tag '81' M 1
Length 3 M 1
ProSe CollectionPeriod -- M 3
ProSe ReportingWindow tag '82' M 1
Length 3 M 1
ProSe ReportingWindow -- M 3
ProSe ReportGroupParameters tag '83' O 1
Length 1 O 1
ProSe ReportGroupParameters -- O 1
ProSe '84' O 1
ReportTimeStampsFirstTransmissionAn
dReception tag
Length 1 O 1
ProSe -- O 1
ReportTimeStampsFirstTransmissionAn
dReception
ProSe ReportDataTransmitted tag '85' O 1
Length 1 O 1
ProSe ReportDataTransmitted -- O 1
ProSe ReportDataReceived tag '86' O 1
Length 1 O 1
ProSe ReportDataReceived -- O 1
ProSe '87' O 1
ReportTimeStampsOutOfCoverage tag
Length 1 O 1
ProSe -- O 1
ReportTimeStampsOutOfCoverage
ProSe ReportLocationInCoverage tag '88' O 1
Length 1 O 1
ProSe ReportLocationInCoverage -- O 1
ProSe ReportRadioParameters tag '89' O 1
Length 1 O 1
ProSe ReportRadioParameters -- O 1
- ProSe ServerAddress
Contents:
As described in TS 24.333 [71], used to determine the IPv4 or IPv6 address the UE or the USIM shall use to
send the usage report to. If no server address is provided, the UE shall upload the usage information reports to
the IP address of the HPLMN ProSe Function. If the USIM supports storage of the usage information, the server
address is mandatory.
Coding:
As defined for the ProSe ServerAddress leaf in TS 24.333 [71].
- ProSe CollectionPeriod
Contents:
As described in TS 24.333 [71], contains the time interval, in unit of minutes, at which the UE shall generate the
usage information reports. Setting the CollectionPeriod to a value of 0 disables generation of usage information
reports at the UE.
Coding:
As defined for the ProSe CollectionPeriod leaf in TS 24.333 [71].
- ProSe ReportingWindow
3GPP
Release 15 200 3GPP TS 31.102 V15.21.0 (2018-0610)
Contents:
As described in TS 24.333 [71], contains the time window, in units of minutes, during which the UE shall upload
the usage information report to the server. Setting the ReportingWindow to a value of 0 disables upload of the
usage information reports by the UE.
Coding:
As defined for the ProSe ReportingWindow leaf in TS 24.333 [71].
- ProSe ReportGroupParameters
Contents:
As described in TS 24.333 [71], indicates whether or not the UE shall report the group parameters for one-to-
many ProSe direct communication in the usage information. The default value 0 applies if this TLV is not
provisioned.
Coding:
As defined for the ProSe ReportGroupParameters leaf in TS 24.333 [71].
- ProSe ReportTimeStampsFirstTransmissionAndReception
Contents:
As described in TS 24.333 [71], indicates whether or not the UE shall report the time stamps of the first
transmission/reception during the collection period in the usage information. The default value 0 applies if this
TLV is not provisioned
Coding:
As defined for the ProSe ReportTimeStampsFirstTransmissionAndReception leaf in TS 24.333 [71].
- ProSe ReportDataTransmitted
Contents:
As described in TS 24.333 [71], indicates whether or not the UE shall report the amount of data transmitted
during the collection period in the usage information, and whether with location information. The default value 1
applies if this TLV is not provisioned
Coding:
As defined for the ProSe ReportDataTransmitted leaf in TS 24.333 [71].
- ProSe ReportDataReceived
Contents:
As described in TS 24.333 [71], indicates whether or not the UE shall report the amount of data received during
the collection period in the usage information, and whether with location information. The default value 1
applies if this TLV is not provisioned
Coding:
As defined for the ProSe ReportDataReceived leaf in TS 24.333 [71].
- ProSe ReportTimeStampsOutOfCoverage
Contents:
As described in TS 24.333 [71], indicates whether or not the UE shall report the time stamps when it went in and
out of E-UTRAN coverage during the collection period in the usage information. The default value 0 applies if
this TLV is not provisioned
Coding:
As defined for the ProSe ReportTimeStampsOutOfCoverage leaf in TS 24.333 [71].
- ProSe ReportLocationInCoverage
Contents:
As described in TS 24.333 [71], indicates whether or not the UE shall report the list of locations of the UE when
in E-UTRAN coverage during the collection period in the usage information.
Coding:
As defined for the ProSe ReportLocationInCoverage leaf in TS 24.333 [71].
- ProSe ReportRadioParameters
3GPP
Release 15 201 3GPP TS 31.102 V15.21.0 (2018-0610)
Contents:
As described in TS 24.333 [71], indicates whether or not the UE shall report the radio parameters used for ProSe
direct communication (i.e. indicator of which radio resources used and radio frequency used) during the
reporting period in the usage information.
Coding:
As defined for the ProSe ReportRadioParameters leaf in TS 24.333 [71].
4.4.8.12 EFPROSE_GM_DISCOVERY (ProSe Group Member Discovery Parameters)
This EF contains the ProSe discovery parameters for public safety, as described in TS 24.334 [70]. This file shall be
used only if the ME is authorized as per content of EFAD or received service authorization from the ProSe Function.

SFI: '12'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to Y Group member discovery parameters TLV O Y bytes
data object
Group member discovery parameters information:

Group member discovery parameters 'A0' M 1
Tag
Length X M Note
User Info ID tag '80' M 1
Length 6 M 1
User Info ID -- M 6
Discovery Group ID tag '81' M 1
Length 3 M 1
Discovery Group ID -- M 3
Application Layer Group ID tag '82' M 1
Length Y M Note
Application Layer Group ID -- M Y
Each record shall contain at most one Group member discovery parameters information.
- User Info ID tag '80'
Contents:
Indicates the user information which is sent by the announcing or discoverer or discoveree UE over
the air during Group Member Discovery procedures.
Coding:
As defined in TS 24.334 [70].
- Discovery Group ID tag '81'
Contents:
Indicates the group ID of the discovery group that the UE belongs to when group member discovery
is performed.
Coding:
3GPP
Release 15 202 3GPP TS 31.102 V15.21.0 (2018-0610)
- Application Layer Group ID tag '82'
Contents:
Indicates the Application Layer Group ID identifying an application layer group that the UE belongs
to.
Coding:
As per TS 23.303 [73]
4.4.8.13 EFPROSE_RELAY (ProSe Relay Parameters)

This EF contains the authorized PLMNs for ProSe UE-to-network relay for public safety, as described in TS 24.334
[70]. This file shall be used only if the ME is authorized as per content of EFAD or received service authorization from
the ProSe Function.

SFI: '13'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to Z ProSe Relay parameters TLV data object O Z bytes
ProSe Relay parameters information:

ProSe Relay parameters Tag 'A0' M 1
Length X M Note
PLMN tag '80' M 1
Length 3 M 1
PLMN -- M 3
Relay type tag '81' M 1
Length 1 M 1
Relay type -- M 1
- PLMN tag '80'
Contents:
Contains the PLMNs in which the UE is authorised to act as a ProSe UE-to-network relay and/or use
a ProSe UE-to-network relay.
Coding:
- Relay type tag '81'
Contents:
3GPP
Release 15 203 3GPP TS 31.102 V15.21.0 (2018-0610)
Indicates if the UE is authorized to act as a ProSe UE-to-network relay and/or use a ProSe UE-to-
network relay.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
b1=0 indicates that the UE is not authorised to act

as a ProSe UE-to-network relay.
b1=1 indicates that the UE is authorised to act as a
ProSe UE-to-network relay.
b2=0 indicates that the UE is not authorised to use
a ProSe UE-to-network relay.
b2=1 indicates that the UE is authorised to use a
ProSe UE-to-network relay.
RFU (see TS 31.101 [11])
4.4.8.14 EFPROSE_RELAY_DISCOVERY (ProSe Relay Discovery Parameters)

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

SFI: '14'
File size: Z bytes (Z > 5 bytes) Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to 6 User Info ID M 6 bytes
-- Remote UE parameters TLV data object O X bytes
-- Relay parameters TLV data object O Y bytes
User Info ID
Contents:
Indicates the user information which is sent by the announcing or discoverer or discoveree UE over the air during
Group Member Discovery procedures.
Coding:
Remote UE parameters information:
The EF can contain multiple Remote UE parameters data objects.
3GPP
Release 15 204 3GPP TS 31.102 V15.21.0 (2018-0610)
Remote UE parameters Tag 'A0' M 1

Length X M Note
Relay Service Code tag '80' M 1
Length 3 M 1
Relay Service Code -- M 3
User Info ID of Relay tag '81' O 1
Length 6 C 1
User Info ID of Relay -- C 6
IP Versions tag '82' M 1
Length 1 M 1
IP Versions -- M 1
Security content tag '83' M 1
Length Y M Note
Security content -- M Y
- Relay Service Code tag '80'
Contents:
Indicates the connectivity service that the ProSe UE-to-network relay provides to public safety
applications.
Coding:
- User Info ID of Relay tag '81'
Contents:
Indicates the user information of the ProSe UE-to-network relay that the remote UE seeks to discover
during ProSe UE-to-network relay discovery procedures.
Coding:
- IP Versions tag '82'
Contents:
Indicates the IP version(s) that the remote UE can use for the relay traffic associated with the Relay
Service Code.
Coding:
A value of '01' indicates IPv4, a value of '02' indicates IPv6, a value of '03' indicates IPv4v6. All other
values are reserved.
- Security Content tag '83'
Contents:
Parameters related to the relay discovery.
Coding:
3GPP
Release 15 205 3GPP TS 31.102 V15.21.0 (2018-0610)
Byte(s) Description M/O Length

1 to 32 PSDK as defined in TS 33.303 [72] M 32 bytes
33 PSDK Id as defined in TS 33.303 [72]. M 1 byte
34 Bitmask of keys: M 1 byte
- b1=1 indicates that DUSK is to be used
- b2=1 indicates that DUCK is to be used
- b3=1 indicates that DUIK is to be used
- all other bits are RFU
35 to 57 DUCK encryption bitmask, as defined in TS M 23 bytes
24.334 [70] (applicable when DUCK is used)
58 to Y RFU O (Y-57) bytes
Relay parameters information:
The EF can contain multiple Relay parameters data objects.

Relay parameters Tag 'A1' M 1
Length X M Note
Relay Service Code tag '80' M 1
Length 3 M 1
Relay Service Code -- M 3
PDN type tag '81' O 1
Length 1 C 1
PDN type -- C 1
APN tag '82' O 1
Length 3 C 1
APN -- C 3
ProSe Relay UE ID tag '83' M 1
Length 3 M 1
ProSe Relay UE ID -- M 3
Security content tag '84' M 1
Length Y M Note
Security content -- M Y
- Relay Service Code tag '80'
Contents:
Indicates the connectivity service that the ProSe UE-to-network relay provides to public safety
applications.
Coding:
- PDN type tag '81'
Contents:
Indicates the IP version of the PDN connection to be used for the relayed traffic associated with a
Relay Service Code.
Coding:
A value of '01' indicates IPv4, a value of '02' indicates IPv6. All other values are reserved.
- APN tag '82'
Contents:
Indicates the PDN connection that the ProSe UE-to-network relay uses for the relayed traffic
associated with a Relay Service Code. If this TLV is missing, then the default APN is used for the
PDN connectivity.
3GPP
Release 15 206 3GPP TS 31.102 V15.21.0 (2018-0610)
Coding:
A network access point name
- ProSe Relay UE ID tag '83'
Contents:
Indicates the link layer identifier used for direct communication associated with a Relay Service
Code.
Coding:
- Security Content tag '84'
Contents:
Parameters related to the relay discovery.
Coding:
Byte(s) Description M/O Length

1 to 32 PSDK as defined in TS 33.303 [72] M 32 bytes
33 PSDK Id as defined in TS 33.303 [72]. M 1 byte
34 Bitmask of keys: M 1 byte
- b1=1 indicates that DUSK is to be used
- b2=1 indicates that DUCK is to be used
- b3=1 indicates that DUIK is to be used
- all other bits are RFU
35 to 57 DUCK encryption bitmask, as defined in TS M 23 bytes
24.334 [70] (applicable when DUCK is used)
58 to Y RFU O (Y-57) bytes
4.4.9 Contents of files at the DF ACDC level
This clause describes the additional files that are used for ACDC configuration.
DFACDC shall be present at the ADFUSIM level if service nº108 is "available" in EFUST (USIM Service Table).
4.4.9.2 EFACDC_LIST (ACDC List)

This EF contains the link to EFs containing the ACDC for each operating system identifier. The ME parses the content
of the EFACDC_LIST and retrieves the file id and optionally the SFI to further access the relevant ACDC configuration.
3GPP
Release 15 207 3GPP TS 31.102 V15.21.0 (2018-0610)

SFI: '01'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to L1 ACDC OS TLV data object 1 M L1 bytes
L1+1 to L1+L2 ACDC OS TLV data object 2 O L2 bytes
: : : :
L1+L2+...+L(n- ACDC OS TLV data object n O Ln bytes
1)+1 to L1+L2+...
+Ln
ACDC OS TLV data object

ACDC OS tag 'A0' M 1
Length X+19 M Note
OS Id -- M 16
File Id -- M 2
SFI -- M 1
RFU -- O X
- OS Id
Contents:
The Operating System identifier
Coding:
A Universally Unique IDentifier (UUID) as specified in IETF RFC 4122 [80].
- File Id
Contents:
File Id of the EF containing the ACDC configuration for the Operating System
Coding:
According to TS 31.101 [11]
- SFI
Contents:
Short File Identifier of the EF containing configuration for the Operating System
Coding:
According to TS 31.101 [11]. The value '0' indicates that SFI is not allocated for the file.
4.4.9.3 EFACDC_OS_CONFIG (ACDC OS configuration)

This EF contains the ACDC configuration for a specific Operating System. The ME retrieves ths file id or the SFI of
the file from the EFACDC_LIST.
3GPP
Release 15 208 3GPP TS 31.102 V15.21.0 (2018-0610)

SFI: 'XX' (optional)
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to L1 ACDC App Id 1 M L1 bytes
L1+1 to L1+L2 ACDC App Id 2 O L2 bytes
: : :
L1+L2+...+L(n- ACDC App Id n O Ln bytes
1)+1 to L1+L2+...
+Ln
ACDC App Id

ACDC App Id tag 'A0' M 1
Length X M Note
ACDC category tag '80' M 1
Length 1 M 1
ACDC category -- M 1
OS App Id tag '81' M 1
Length L M Note
OS App Id -- M L
- ACDC category
Contents:
The ACDC category indicates the category to which the identified application belongs.
Coding:
As the ACDCCategory leaf in 24.105 [81]
- OS App Id
Contents:
indicates an OS specific application identifier
Coding:
As the OSAppId leaf in 24.105 [81]
4.4.10 Contents of files at the DF TV level
This clause describes the additional files that are used for TV service configuration.
DFTV shall be present at the ADFUSIM level if service nº116 is "available" in EFUST (USIM Service Table).
4.4.10.2 EFTVUSD (TV User Service Description)

This file contains the User Service Description (USD) associated with one or more entries in the EF TVCONFIG. The ME
retrieves this file identifier from the EFTVCONFIG.
Multiple EFTVUSD files may exist in the DF, each one associated with a different entry in EF TVCONFIG.
3GPP
Release 15 209 3GPP TS 31.102 V15.21.0 (2018-0610)

Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to L USD TLV data object M L bytes
L+1 to Z RFU O Z-L bytes
USD TLV data object:

USD Tag 'A0' M 1
Length X M Note
USD -- C X
USD:
Contents:
- User Service Description (USD).
Coding:
- According to TS 26.346 [99] clause J.1.
4.4.11 Contents of files at the DF5GS level
This clause describes the files that are specific for 5GS.
DF5GS shall be present at the ADFUSIM level if any of the following services are "available" in EFUST (USIM Service
Table):
Service n°122 5GS Mobility Management Information
Service n°123 5G Security Parameters
Service n°124 Subscription identifier privacy support
Service n°125 SUCI calculation by the USIM
Service n°126 UAC Access Identities support
Service n°127 Steering of UE in VPLMN
4.4.11.2 EF5GS3GPPLOCI (5GS 3GPP location information)

If service n°122 is "available" in EFUST, this file shall be present.
This EF contains the following 5GS location information for 3GPP access:

3GPP
Release 15 210 3GPP TS 31.102 V15.21.0 (2018-0610)

SFI: '01'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 12 5G-GUTI for 3GPP access M 12 bytes
13 to18 Last visited registered TAI in 5GS for 3GPP M 6 bytes
access
19 5GS update status for 3GPP access M 1 byte
- 5G-GUTI for 3GPP access.

Contents:
5G-Globally Unique Temporary Identifier for 3GPP access.
Coding:
as the 5G-GUTI part of the 5GS mobile identity information element defined in TS 24.501 [104]. Byte 1
corresponds to "octet 2" of an 5GS mobile identity information element containing a 5G-GUTI. Byte 12
corresponds to "octet 13" of an 5GS mobile identity information element information element containing
a 5G-GUTI.
Byte 1: first byte of 5G-GUTI for 3GPP access
b8 b7 b6 b5 b4 b3 b2 b1
MSB
- Last visited registered TAI in 5GS for 3GPP access

Contents:
Last visited registered Tracking Area Identity in 5GS for 3GPP access.
Coding:
as the content of the tracking area identity information element defined in TS 24.501 [104]. Byte 13
corresponds to "octet 2" of a tracking area identity information element. Byte 18 corresponds to "octet 7"
of a tracking area identity information element.
Byte 13: first byte of last visited registered TAI for 3GPP access
b8 b7 b6 b5 b4 b3 b2 b1
MSB
- 5GS update status for 3GPP access.

Contents:
status of 5GS update for 3GPP access according to TS 24.501 [104].
Coding:
byte 19:
3GPP
Release 15 211 3GPP TS 31.102 V15.21.0 (2018-0610)
Bits: b3 b2 b1.
0 0 0 : 5U1 UPDATED.
0 0 1 : 5U2 NOT UPDATED.
0 1 0 : 5U3 ROAMING NOT ALLOWED.
0 1 1 : reserved.
1 0 0 : reserved.
1 0 1 : reserved.
1 1 0 : reserved.
1 1 1 : reserved.
***** Next change *****
4.4.11.3 EF5GSN3GPPLOCI (5GS non-3GPP location information)

This EF contains the following 5GS location information for non-3GPP access:


SFI: '02'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to 12 5G-GUTI for non-3GPP access M 12 bytes
13 to18 Last visited registered TAI in 5GS for non-3GPP M 6 bytes
access
19 5GS update status for non-3GPP access M 1 byte
For content and coding see clause 4.4.11.2 for EF5GS3GPPLOCI.
4.4.11.4 EF5GS3GPPNSC (5GS 3GPP Access NAS Security Context)

This EF contains the 5GS 3GPP access NAS security context as defined in TS 24.501 [104], consisting of K AMF with the
associated key set identifier, the UE security capabilities, and the uplink and downlink NAS COUNT values. This file
shall contain one record.

SFI: '03'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

3GPP
Release 15 212 3GPP TS 31.102 V15.21.0 (2018-0610)
5GS NAS Security Context tags

5GS NAS Security Context Tag 'A0'
5GS NAS Security Context information

5GS NAS Security Context Tag 'A0' M 1
ngKSI Tag '80' M 1
Length K M Note 1
ngKSI -- M K
KAMF Tag '81' M 1
Length L M Note 1
KAMF -- M L
Length M M Note 1
Length N M Note 1
Length S M Note 1
- ngKSI Tag '80'
Contents:
The ngKSI (Key Set Identifier in 5G) as defined in TS 33.501 [105] is coded on 1 byte.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
ngKSI
- KAMF Tag '81'
Contents:
The KAMF as defined in TS 33.501 [105] is coded on 32 bytes. The ME shall treat any KAMF values stored in
this EF as invalid if the ngKSI indicates that no KAMF is available or if the length indicated in the KAMF
TLV is set to '00',
Coding:
The most significant bit of KAMF is the most significant bit of the 1st byte of this TLV value field. The least
significant bit of KAMF is the least significant bit of the last byte of this TLV value field.
Contents:
The uplink NAS count as defined in TS 33.501 [105] is coded on 4 bytes.
Coding:
3GPP
Release 15 213 3GPP TS 31.102 V15.21.0 (2018-0610)
The most significant bit of the uplink NAS count is the most significant bit of the 1st byte of this TLV value
field. The least significant bit of the uplink NAS count is the least significant bit of the last byte of this
TLV value field.
Contents:
The downlink NAS count as defined in TS 33.501 [105] is coded on 4 bytes.
Coding:
The most significant bit of the downlink NAS count is the most significant bit of the 1st byte of this TLV
value field. The least significant bit of the downlink NAS count is the least significant bit of the last byte
of this TLV value field.
Contents:
The identifiers of selected NAS integrity and encryption algorithms as defined in TS 33.501 [105] and TS
24.501 [104]. In this release the identifiers of selected NAS integrity and encryption algorithms are coded
as 4-bit identifiers.
Coding:
Coding is same as the content of the NAS security algorithms information element defined in
TS 24.501 [104].
Byte 1 of this TLV value field: first byte of the value part of the NAS security algorithms information
element
b8 b7 b6 b5 b4 b3 b2 b1
MSB
Least significant bit of the security algorithm identifier is the b1 of this TLV value field. Most siginificant bit
of the security algorithm identifier is b4 of this TLV value field as per the NAS security algorithms
identifer element defined in TS 33.501 [105].
b8 b7 b6 b5 b4 b3 b2 b1
LSB of security algorithm identifier
MSB of security algorithm identifier

RFU
RFU
RFU
RFU
In order to mark the stored 5GS NAS security context as invalid:

- the ngKSI is set to '07', or
- the length indicated in the KAMF TLV is set to '00'.
4.4.11.5 EF5GSN3GPPNSC (5GS non-3GPP Access NAS Security Context)

If Service n°122 is "available" in EFUST, this file shall be present.
3GPP
Release 15 214 3GPP TS 31.102 V15.21.0 (2018-0610)
This EF contains the 5GS non-3GPP access NAS security context as defined in TS 24.501 [104], consisting of K AMF
with the associated key set identifier, the UE security capabilities, and the uplink and downlink NAS COUNT values.
This file shall contain one record.

SFI: '04'
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

For content and coding see clause 4.4.11.4 for EF5GS3GPPNSC.
4.4.11.6 EF5GAUTHKEYS (5G authentication keys)

If Service n°123 is "available" in EFUST, this file shall be present.
This EF contains KAUSF and KSEAF that are generated on the ME using CK and IK as part of AKA procedures as
described in TS 33.501 [105].

SFI: '05'
File size: >= 68 bytes Update activity: high
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

KAUSF Tag '80' M 1
Length K (Note2) M Note1
KAUSF -- M K (Note2)
KSEAF Tag '81' M 1
Length L (Note2) M Note1
KSEAF -- M L (Note2)
Note 2: As per TS 33.501 [105], the length of keys KAUSF and KSEAF is 32 bytes each
- KAUSF Tag '80'.
Contents:
- KAUSF as described in TS 33.501[105]).
Coding:
- The most significant bit of KAUSF is the most significant bit of the 1st byte of this TLV value field. The least
significant bit of KAUSF is the least significant bit of the last byte of this TLV value field.
- KSEAF Tag '81'.
Contents:
- KSEAF as described in TS 33.501[105]).
Coding:
3GPP
Release 15 215 3GPP TS 31.102 V15.21.0 (2018-0610)
- The most significant bit of KSEAF is the most significant bit of the 1st byte of this TLV value field. The least
significant bit of KSEAF is the least significant bit of the last byte of this TLV value field.
4.4.11.7 EFUAC_AIC (UAC Access Identities Configuration)

This EF contains the configuration information pertaining to access identities allocated for specific high priority
services that can be used by the subscriber. The assigned access identities are used, in combination with an access
category, to control the access attempts. For more information see TS 22.261 [106] and TS 24.501 [104].

SFI: '06'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to 4 UAC access identities configuration M 4 bytes
- UAC access identities configuration

Contents:
- Configuration of certain Unified Access Control (UAC) access identities specified in TS 24.501 [104]
subclause 4.5.2.
Coding:
- Each access identity configuration is coded on one bit.
Byte 1:
b8 b7 b6 b5 b4 b3 b2 b1
b1=0: UE is not configured for Multimedia Priority

b1=1: UE is configured for Multimedia Priority
b2=0: UE is not configured for Mission Critical
Services in the HPLMN or EHPLMN.
b2=1: UE is configured for Mission Critical Services
in the HPLMN or EHPLMN.
RFU
Bytes 2 to 4:
Bits b1 to b8 are RFU.
NOTE: Access Identities 11 to 15 (as specified in TS 24.501 [104]) are configured as Access Classes 11 to 15 in
EFACC, specified in clause 4.2.15.
4.4.11.8 EFSUCI_Calc_Info (Subscription Concealed Identifier Calculation

Information EF)
If "SUCI calculation is to be performed by the ME" (i.e. service n°124 is "available" in EF UST and service n°125 is not
"available" in EFUST), this file shall be present.
3GPP
Release 15 216 3GPP TS 31.102 V15.21.0 (2018-0610)
If "SUCI calculation is to be performed by the USIM" (i.e. service n°124 is "available" in EF UST and service n°125 is
"available" in EFUST), this file shall not be available to the ME.
If service n°124 is not "available" in EFUST, this file shall not be available to the ME. This EF contains information
needed by the ME for the support of subscription identifier privacy as defined in 3GPP TS 33.501[105].

SFI: '07'
File size: X bytes (X ≥ 2) Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to Z Protection Scheme Identifier List data object M Z bytes
Z+1 to Y+Z Home Network Public Key List data object C Y bytes
X-W+1 to X Routing Information TLV data object C W bytes
Editor’s Note: The presence condition of Routing Information TLV data object is FFS.
- Protection Scheme Identifier List data object.

Contents:
This data object shall always be present. If Protection Scheme Identifier List data object length is not zero, this data
object contains a list of the Protection Scheme Identifier and the corresponding Key Index. The first Protection
Scheme Identifier entry has the highest priority and the last Protection Scheme Identifier entry has the lowest
priority. The Key Index value indicates the position of the Home Network Public Key in the Home Network Public
Key List, that is applicable to the Protection Scheme.
Coding:
Description Value M/O/C Length

(bytes)
Protection Scheme Identifier List data object tag 'A0' M 1
Protection Scheme Identifier List data object length L1 M Note 1
Protection Scheme Identifier 1 (Highest priority) -- O 1
Key Index 1 -- C (Note 2) 1
Protection Scheme Identifier 2 -- O 1
Key Index 2 -- C (Note 2) 1
… … … …
Protection Scheme Identifier N (Lowest priority) -- O 1
Key Index N -- C (Note 2) 1
Note 2: This field is present only if the corresponding Protection Scheme Identifier field is
present
The Protection Scheme Identifier represents a protection scheme as described in 3GPP TS 33.501 [105] and it is
coded in one byte as follows:
b8 b7 b6 b5 b4 b3 b2 b1
Protection Scheme identifier coded as described in

3GPP TS 33.501 [105]
RFU, bit = 0
Editor’s Note: The format may need to be updated depending on the outcome of 3GPP TS 23.003.
The Key Index is coded in one byte such that its value indicates the position of the Home Network Public Key in the
Home Network Public Key List data object, that is applicable to the Protection Scheme. A Key Index with a value
of "1" refers to the first Network Public Key entry in the Home Network Public Key List, and so on. A Key Index
with a value of "0" indicates that there is no Home Network Public Key associated with that Protection Scheme
(e.g., in the case of null-scheme).
3GPP
Release 15 217 3GPP TS 31.102 V15.21.0 (2018-0610)
- Home Network Public Key List data object.

Contents:
This data object contains a list of the Home Network Public Key and the corresponding Home Network Public Key
Identifier that shall be used by the ME to calculate the SUCI.
This data object may not be present if none of the protection scheme profiles identified by the Protection Scheme
Identifiers included in the Protection Scheme Identifier List data object use the Home Network Public Key (e.g.
null-scheme). If this data object is present, it shall contain at least one Home Network Public Key and the
corresponding Home Network Public Key Identifier.
Coding:
Description Value M/O/C Length

(bytes)
Home Network Public Key List data object 'A1' C 1
Home Network Public Key List data object length L1 C Note 1
Home Network Public Key 1 Identifier tag '80' C 1
Home Network Public Key 1 Identifier length L2 C Note 1
Home Network Public Key 1 Identifier -- C L2
Home Network Public Key 1 tag '81' C 1
Home Network Public Key 1 length L3 C Note 1
Home Network Public Key 1 -- C L3
… … … …
Home Network Public Key N Identifier tag '80' O 1
Home Network Public Key N Identifier length L4 O Note 1
Home Network Public Key N Identifier -- O L4
Home Network Public Key N tag '81' O 1
Home Network Public Key N length L5 O Note 1
Home Network Public Key N -- O L5
Editor’s Note: Coding of the Home Network Public Key Identifier and Home Network Public Key are FFS.
- Routing Information TLV data object.

Contents:
his data object contains Routing Indicator that allows together with the MCC and MNC to route network signalling
with SUCI to AUSF and UDM instances capable to serve the subscriber, as specified in 3GPP TS 23.003 [25]. This
data object may not be present in the case of null-scheme. If this data object is present, it shall have a valid Routing
Indicator.
Coding:
Routing Information TLV data object tag 'A2' C 1
Routing Information TLV data object length L1 C Note 1
Routing Information TLV data object value -- C L1
Editor’s Note: Coding of the above data object TLV value is FFS.
4.4.11.9 EFSteering_of_UE_in_VPLMN (Steering of UE in VPLMN)

If service n 127 is "available" in EFUST, this file shall be present.
This file allows the HPLMN to indicate that the UE is to receive control plane based Steering of Roaming information
in a Registration Accept message during initial registration in a VPLMN. The control plane based Steering of Roaming
procedure is specified in 3GPP TS 23.122 [31]
3GPP
Release 15 218 3GPP TS 31.102 V15.21.0 (2018-0610)

SFI: '08'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1-2 Steering of UE in VPLMN Configuration M 2 bytes
- Steering of UE in VPLMN Configuration.

Contents:
- configuration parameters for steering of UE in VPLMN.
Coding:
Byte 1:
b8 b7 b6 b5 b4 b3 b2 b1
b1=0 Registration Accept may contain control plane

based Steering of Roaming information during initial
registration in a VPLMN
b1=1 Registration Accept shall contain control plane
based Steering of Roaming information during initial
registration in a VPLMN
RFU
RFU
RFU
RFU
RFU
RFU
RFU
Byte 2 is RFU.
4.5 Contents of Efs at the TELECOM level

The Efs in the Dedicated File DFTELECOM contain service related information.
4.5.1 EFADN (Abbreviated dialling numbers)

In case of a present GSM application on the UICC the first EFADN (i.e. reflected by the first record in EFPBR) of the
DFPHONEBOOK is mapped (with an identifier equal to '6F3A') to DFTELECOM to ensure backwards compatibility.
A 3G ME shall not access this file. The information is accessible for a 3G ME in EFADN under DFPHONEBOOK.

In case of a present GSM application on the UICC the first EFEXT1 (i.e. reflected by the first record in EFPBR) of the
DFPHONEBOOK is mapped (with an identifier equal to '6F4A') to DFTELECOM to ensure backwards compatibility.
A 3G ME shall not access this file. The information is accessible for a 3G ME in EFEXT1 under DFPHONEBOOK.
4.5.3 EFECCP (Extended Capability Configuration Parameter)

In case of a present GSM application on the UICC the first EFCCP1 (i.e. reflected by the first record in EFPBR) of the
DFPHONEBOOK is mapped (with an identifier equal to '6F4F') to DFTELECOM to ensure backwards compatibility. There shall
3GPP
Release 15 219 3GPP TS 31.102 V15.21.0 (2018-0610)
not be any EFCCP (with a file-id of '6F3D') under DFTELECOM because otherwise a GSM terminal could create
inconsistencies within the phonebook.
A 3G ME shall not access this file. The information is accessible for a 3G ME in EFCCP1 under DFPHONEBOOK.
4.5.4 EFSUME (SetUpMenu Elements)

This File is defined in ETSI TS 102 222 [39], and has the file identifier '6F54'.
4.5.5 EFARR (Access Rule Reference)

This EF contains the access rules for files located under the DFTELECOM in the UICC. If the security attribute tag '8B' is
indicated in the FCP it contains a reference to a record in this file.
Structure of EFARR at DFTelecom-level
Identifier: '6F06' Structure: Linear fixed Mandatory

Access Conditions:
READ ALW
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to X Access Rule TLV data objects M X bytes
This EF contains one or more records containing access rule information according to the reference to expanded format
as defined in ISO/IEC 7816-4 [20]. Each record represents an access rule. Unused bytes in the record are set to 'FF'.
If the card cannot access EFARR, any attempt to access a file with access rules indicated in this EFARR shall not be
granted.
4.5.6 EFICE_DN (In Case of Emergency – Dialling Number)

This EF contains one or more records containing number formatted ICE information, according to TS 22.101 [24].
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.
Structure of EFICE_DN at DFTelecom-level
Identifier: '6FE0' Structure: Linear fixed Optional

SFI: Optional
Access Conditions:
READ ALWAYS
UPDATE PIN
DEACTIVATE PIN or Issuer Specified PIN (see Note)
ACTIVATE PIN or Issuer Specified PIN (see Note)
Note: The Issuer Specified PIN is a PIN with a global key reference (see TS 31.101 [11])
specified by the card Issuer.
Coding:
3GPP
Release 15 220 3GPP TS 31.102 V15.21.0 (2018-0610)
As for EFADN
4.5.7 EFICE_FF (In Case of Emergency – Free Format)

This EF contains one or more records containing free formatted ICE information, according to TS 22.101 [24].
Structure of EFICE_FF at DFTelecom-level
Identifier: '6FE1' Structure: Linear fixed Optional

SFI: Optional
Record length: >=X+Y bytes Update activity: low
Access Conditions:
READ ALWAYS
UPDATE PIN
1 to X ICE Free Format Label TLV M X bytes
X+1 to X+Y ICE Free Format Content TLV M Y bytes
- ICE Free Format Label TLV
Contents:
This TLV contains a label that summarises the type of content that is contained in the associated ICE Free
Format Content TLV (e.g. "medical alert information").
Coding:
ICE Free Format Label TLV is coded as follows:
Tag value is '80'
Length is coded according to ISO/IEC 8825-1 [35].
Value is as for value part of the text string TLV in 3GPP TS 31.111 [12]. If the length is 0 and there is no
value part then the terminal shall interpret this as no label is used.
- ICE Free Format Content TLV
Contents:
This TLV contains a ICE Free Format Content (e.g. "Allergy to work").
Coding:
ICE Free Format Content TLV is coded as follows:
Tag value is '81'
Length is coded according to ISO/IEC 8825-1 [35].
Value is as for value part of the text string TLV in 3GPP TS 31.111 [12]. If the length is 0 and there is no
value part then the terminal shall interpret this as no label is used.
Padding: unused bytes in each record shall be set to 'FF'.
4.5.8 EFRMA (Remote Management Actions)

This File is defined in ETSI TS 102 222 [39], and has the file identifier '6F53'.
3GPP
Release 15 221 3GPP TS 31.102 V15.21.0 (2018-0610)
4.5.9 EFPSISMSC (Public Service Identity of the SM-SC)

This file shall be present if and only if service n°12 and n°91 are "available".
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 24.341 [55].

File size: X bytes Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to X URI TLV data object M X bytes
- URI
Contents:
- SIP URI or tel URI of the Public Service Identity of the SM-SC.
Coding:
- For contents and syntax of URI TLV data object values see IETF RFC 3261 [56]. The URI shall be encoded
to an octet string according to UTF-8 encoding rules as specified in IETF RFC 3629 [57]. The tag value of
the URI TLV data object shall be '80'.
4.6 Contents of DFs at the TELECOM level

4.6.0 List of DFs at the TELECOM level
DFs may be present as child directories of DFTELECOM. The following DFs have been defined:
- DFGRAPHICS '5F50'.
- DFPHONEBOOK '5F3A'.
(DF for public phone book. This DF has the same structure as DFPHONEBOOK under ADF USIM).
- DFMULTIMEDIA '5F3B'.
- DFMMSS '5F3C'
(The contents of DF for MMSS are defined in C.S0074-A [53]. This DF for MMSS is not applicable to 3GPP only
terminals).
- DFMCSDFMCPTT '5F3D'.
- DFV2X '5F3E'.
4.6.1 Contents of files at the DFGRAPHICS level

The Efs in the Dedicated File DFGRAPHICS contain graphical information.
4.6.1.1 EFIMG (Image)

Each record of this EF identifies instances of one particular graphical image, which graphical image is identified by this
EF's record number.
3GPP
Release 15 222 3GPP TS 31.102 V15.21.0 (2018-0610)
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.

Record length: 9n+1 or 9n+2 bytes, (n ≥ 1) Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 Number of Actual Image Instances M 1 byte
2 to 10 Descriptor of Image Instance 1 M 9 bytes
11 to 19 Descriptor of Image Instance 2 O 9 bytes
: : : :
9(n-1)+2 to 9n+1 Descriptor of Image Instance n O 9 bytes
9n + 2 RFU (see TS 31.101 [11]) O 1 byte
- Number of Actual Image Instances.
Contents:
- this byte gives the number of actual image instances described in the following data items (i.e. unused descriptors
are not counted).
Coding:
- binary.
- Image Instance Descriptor
Contents:
- a description of an image instance.
Coding:
- Byte 1: Image Instance Width
Contents:
- this byte specifies the image instance width, expressed in raster image points.
Coding:
- binary.
Byte 2: Image Instance Height.
Contents:
- this byte specifies the image instance height, expressed in raster image points.
Coding:
- binary.
Byte 3: Image Coding Scheme.
Contents:
- this byte identifies the image coding scheme that has been used in encoding the image instance.
Coding:
- '11' - basic image coding scheme as defined in annex B;
- '21' - colour image coding scheme as defined in annex B;
- '22' - colour image coding scheme with transparency as defined in annex B;
other values are reserved for future use.
3GPP
Release 15 223 3GPP TS 31.102 V15.21.0 (2018-0610)
Bytes 4 and 5: Image Instance Data File Identifier.
Contents:
- these bytes identify an EF which is the image instance data file (see clause 4.6.1.2), holding the actual image data
for this particular instance.
Coding:
- byte 4: high byte of Image Instance Data File Identifier;
- byte 5: low byte of Image Instance Data File Identifier.
Bytes 6 and 7: Offset into Image Instance Data File.
Contents:
- these bytes specify an offset into the transparent Image Instance Data File identified in bytes 4 and 5. The data for
this image instance is found starting at this offset in the Image Instance Data File.
Coding:
- byte 6: high byte of offset into Image Instance Data File;
byte 7: low byte of offset into Image Instance Data File.
Bytes 8 and 9: Length of Image Instance Data.
Contents:
- these bytes yield the length of the image instance data, starting at the offset identified in bytes 6 and 7. For the
colour image coding scheme, as defined in annex B, the length of image instance data excludes the CLUT.
Coding:
- byte 8: high byte of Image Instance Data length;
- byte 9: low byte of Image Instance Data length.
NOTE: Transparent image instance data longer than 256 bytes may be read using successive READ BINARY
commands.
4.6.1.2 EFIIDF (Image Instance Data Files)

Residing under DFGRAPHICS, there may be several image instance data files. Each Image Instance Data File contains data
for one or more image instances. These Efs containing image instance data shall have the following attributes:

File size: Y bytes Update activity: low
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to Y Image Instance Data M Y bytes
Contents and coding:

- Image instance data are accessed using the image instance descriptors provided by EF IMG (see clause 4.6.1.1).
The identifier '4FXX' shall be different from one image instance data file to the other. For the range of 'XX',
TS 31.101 [11]. The length Y may be different from one image instance data file to the other.
4.6.1.3 EFICE_graphics (In Case of Emergency – Graphics)

This EF contains ICE graphical information, according to TS 22.101 [24].
3GPP
Release 15 224 3GPP TS 31.102 V15.21.0 (2018-0610)
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.
Structure of EFICE_graphics at DFgraphics-level
Identifier: '4F21' Structure: BER-TLV Optional

SFI: Optional
Record length: X Update activity: low
Access Conditions:
READ ALWAYS
UPDATE PIN
1 to X ICE graphics Data object M X bytes
- ICE graphics Data Object
Coding of the ICE graphics Data Objects
Length Description Coding Status

1 to T bytes (T ≤ 3) ICE graphics Data Object tag As defined in TS 31.101 [11] M
for BER-TLV structured files
1 to L (L ≤ 4) ICE graphics Data Object As defined in TS 31.101 [11] M
length for BER-TLV structured files
X-L-T bytes ICE graphics Content JPEG format M
4.6.1.4 Void
4.6.1.5 Void
4.6.2 Contents of files at the DFPHONEBOOK under the DFTELECOM

This DF has the same structure as DFPHONEBOOK under the ADFUSIM.
4.6.3 Contents of files at the DFMULTIMEDIA level

The Efs in the Dedicated File DFMULTIMEDIA contain multimedia information. This DF shall be present if service n°67 is
available, i.e. if the card supports MMS storage.
4.6.3.1 EFMML (Multimedia Messages List)

This file contains information about the MM data stored in EFMMDF. MM information are encapsulated in a BER-TLV
data object. Each data object in EFMML points to a corresponding MM in EFMMDF.
3GPP
Release 15 225 3GPP TS 31.102 V15.21.0 (2018-0610)

Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to X MM Descriptor Data Object(s) M X bytes
- MM Descriptor Data Object

The content and coding are defined below:
Coding of the MM Descriptor Data Objects

1 to A bytes (A ≤ 3) MM Descriptor Data Object tag As defined in TS 31.101 [11] M
1 to B bytes (B ≤ 4) MM Descriptor Data Object length As defined in TS 31.101 [11] M
1 byte MMS Implementation tag '80' M
1 byte MMS Implementation length M
1 byte MMS Implementation See below M
1 byte MM File Identifier / SFI tag '81' M
1 byte MM File Identifier / SFI length M
1 or 2 bytes MM File Identifier / SFI See below M
1 byte MM Content Data Object Tag tag '82' M
1 byte MM Content Data Object Tag length M
1 to C bytes (C ≤ 3) MM Content Data Object Tag See below M
1 byte MM Size tag '83' M
1 byte MM Size length M
1 to D bytes (D ≤ 4) MM Size in bytes See below M
1 byte MM Status tag '84' M
1 byte MM Status length M
2 bytes MM Status See below M
1 byte MM Alpha Identifier tag '85' M
1 byte MM Alpha Identifier length M
1 to E bytes MM Alpha Identifier See below M
- MMS Implementation
Contents:
The MMS Implementation indicates the used implementation type, e.g. WAP.
Coding:
Allocation of bits:
Bit number Parameter indicated
1 WAP implementation of MMS
2 to 8 Reserved for future use
Bit value Meaning

0 Implementation not supported.
1 Implementation supported.
- MM File Identifier / SFI

Contents:
file identifier or SFI of EFMMDF which contains the actual MM message. If the length of this TLV object is
equal to 1 then the content indicates the SFI of the EFMMDF, the SFI is coded on b1 to b5. Otherwise the TLV
contains the file identifier.
Coding:
- MM Content Data Object Tag
3GPP
Release 15 226 3GPP TS 31.102 V15.21.0 (2018-0610)
Contents:
tag indentifying a MM (i.e. identifying a data object) within EFMMDF.
Coding:
- MM Size
Contents:
size of the corresponding MM stored in EFMMDF.
Coding:
- MM Status
Contents:
The status bytes contain the status information of the stored Multimedia Message.
Coding:
First byte:
bit b1 indicates whether the MM has been read or not. Bit b2 indicates the MM forwarding status. Bit b3 indicates
whether it is a received MM or an originated MM. Bits b4 to b8 are reserved for future use.
Second byte:
Coding of the second byte depends on whether the MM has been identified as a received MM or originated MM in the
first byte:
- Received MM coding:
bits b1 and b2 are used to provide information on Read-reply reports. Bits b3 to b8 are reserved for
future use.
- Originated MM coding:
bit b1 is used to provide information on Delivery-report. Bits b2 to b8 are reserved for future use.
First byte:
b8 b7 b6 b5 b4 b3 b2 b1
MM read, bit = 1 / MM not read, bit = 0
MM forwarded, bit = 1
Received MM, bit = 1 / Originated MM, bit = 0
RFU, bit = 0
Second byte coding for Received MM:
b8 b7 b6 b5 b4 b3 b2 b1
Read-reply report requested, bit = 1
Read-reply report sent, bit = 1
Read-reply report created, bit = 1
Delivery report requested, bit = 1
Delivery report creation allowed, bit = 1
RFU, bit = 0
Second byte coding for Originated MM:
b8 b7 b6 b5 b4 b3 b2 b1
Delivery report received, bit = 1
3GPP
Release 15 227 3GPP TS 31.102 V15.21.0 (2018-0610)
Delivery report requested, bit = 1
Read-Reply report requested, bit = 1
Read-Reply report received, bit = 1
MM sent, bit = 1
RFU, bit = 0
- MM Alpha Identifier
Contents:
information about the MM to be displayed to the user (e.g. sender, subject, date etc).
Coding:
this alpha identifier shall use either:
- the SMS default 7-bit coded alphabet as defined in TS 23.038 [5] with bit 8 set to 0. The alpha
identifier shall be left justified. Unused bytes shall be set to 'FF';
- or one of the UCS2 coded options as defined in the annex of TS 31.101 [11].
4.6.3.2 EFMMDF (Multimedia Messages Data File)

Residing under DFMULTIMEDIA, this EF contains Multimedia Messages data. The structure of this EF is BER-TLV (see
TS 31.101 [11]). Each MM in this file is identified by a tag. The tag value for a particular MM in this file is stored in
EFMML.

Update activity: low
Access Conditions:
READ PIN
UPDATE PIN
DEACTIVATE ADM
ACTIVATE ADM

1 to X MM Content Data Object(s) M X bytes
- MM Content Data Object

The content and coding are defined below:
Coding of the MM Content Data Objects

1 to T bytes (T ≤ 3) MM Content Data Object tag As defined in TS 31.101 [11] M
1 to L (L ≤ 4) MM Content Data Object length As defined in TS 31.101 [11] M
X-L-T bytes MM Content According to MMS M
Implementation
Contents:
The Multimedia Message content consists of MM headers and a message body. The content of the Multimedia Message
data depends on whether the MM has been identified as a received MM or an originated MM:
- For a received message, the stored Multimedia Message data consists of the information elements (i.e.
relevant MM control information and MM content) of the MM1_retrieve.RES (see TS 23.140 [38]).
- For an originated message, the stored Multimedia Message data consists of the information elements (i.e.
relevant MM control information and MM content) of the MM1_submit.REQ (see TS 23.140 [38]).
Coding:
The MM data encapsulation scheme and encoding rules are defined by the MMS Implementation.
3GPP
Release 15 228 3GPP TS 31.102 V15.21.0 (2018-0610)
4.6.4 Contents of files at the DFMCSDFMCPTT level

The EFs in the Dedicated File DFMCSDFMCPTT contain management objects related to Mission Critical Services
(including MCPTT, MCS, MCData, MCVideo), as specified in 3GPP TS 24.48323.379 [890].
4.6.4.1 EFMST (MCSMCPTT Service Table)

If service n°109 is "available" in the USIM Service Table or service n°15 is "available" in the ISIM Service Table, this
file shall be present. This EF indicates the coding of the MCSMCPTT management objects and which MCPTT, MCS,
MCData or MCVideo services are available. If a service is not indicated as available in the MCSMCPTT Service
Table, the ME shall not select this service.

SFI: '01'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 Coding of the MCS MCPTT management objects M 1 byte
etc.
Coding of the MCSMCPTT management objects
Contents:
Indicates the coding used for all the MCSMCPTT management objects stored in the DFMCSDFMCPTT.
Coding:
A value of '00' indicates the XML format described in TS 24.483 [89]. All other values are reserved.
Editor’s Note: the definition of other encoding formats is for future study.
The EF shall contain at least one byte for services. 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.
-Services
Contents: Service n°1: MCPTT UE configuration data
Service n°2: MCPTT User profile dataUser configuration data
Service n°3: MCS Group configuration data
Service n°4: MCPTT Service configuration data
Service n°5: MCS UE initial configuration data
Service n°6: MCData UE configuration data
Service n°7: MCData user profile data
Service n°8: MCData service configuration data
Service n°9: MCVideo UE configuration data
Service n°10: MCVideo user profile data
Service n°11: MCVideo service configuration data
Coding:
Same as coding of USIM Service Table.
4.6.4.2 EFMCPTTEFMCS_ CONFIG (MCPTT MCS configuration data)

If at least one of the services n°1, 2, 3 or 4 is "available" in the MCPTT MCS Service Table, this file shall be present.
3GPP
Release 15 229 3GPP TS 31.102 V15.21.0 (2018-0610)
This EF contains zero, one or more MCPTT configuration data objects, as specified in 3GPP TS 24.483 [89] Annex
B.2, Annex B3, Annex B.4 and Annex B.5.

SFI: '02'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to Y Mission Critical ServicesMCPTT O Y bytes
configuration data object
The MCSPTT configuration data is encoded as specified in the MCSPTT Service Table.
Mission Critical ServicesCPTT configuration data object tag:
MCPTT configuration data objects Tag Values Condition

MCPTT UE configuration data '80' Shall be present if service n°1 is
"available" in the MCSPTT service table
MCPTT uUser configurationprofile '81' Shall be present if service n°2 is
data "available" in the MCSPTT service table
MCSPTT Group configuration data '82' Shall be present if service n°3 is
MCPTT Service configuration data '83' Shall be present if service n°4 is
MCS UE initial configuration data '84' Shall be present if service n°5 is
"available" in the MCS service table
MCData UE configuration data '85' Shall be present if service n°6 is
MCData user profile data '86' Shall be present if service n°7 is
MCData service configuration data '87' Shall be present if service n°8 is
MCVideo UE configuration data '88' Shall be present if service n°9 is
MCVideo user profile data '89' Shall be present if service n°10 is
MCVideo service configuration data '8A' Shall be present if service n°11 is
4.6.4.3 Void
4.6.4.4 Void
3GPP
Release 15 230 3GPP TS 31.102 V15.21.0 (2018-0610)
4.6.4.5 Void
4.6.5 Contents of files at the DFV2X level
4.6.5.1 V2X configuration data related files

The EFs in the Dedicated File DFV2X contain management objects related to V2X, as specified in 3GPP TS 24.386 [98].
4.6.5.2 EFVST (V2X Service Table)

If service n°119 is "available" in the USIM Service Table, this file shall be present. This EF indicates the coding of the
V2X management objects and which V2X services are available. If a service is not indicated as available in the V2X
Service Table, the ME shall not select this service.

SFI: '01'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 Coding of the V2X management objects M 1 byte
etc.
Coding of the V2X management objects
Contents:
Indicates the coding used for all the V2X management objects.stored in the DF V2X.
Coding:
A value of '00' indicates the XML format described in TS 24.385 [97]. All other values are reserved.
Editor’s Note: the definition of other encoding formats is for future study.
The EF shall contain at least one byte for services. 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.
Services
Contents: Service n°1: V2X configuration data
Coding:
Same as coding of USIM Service Table.
4.6.5.3 EFV2X_CONFIG (V2X configuration data)

This EF contains zero, one or more V2X configuration data objects, as specified in TS 24.385 [97].
3GPP
Release 15 231 3GPP TS 31.102 V15.21.0 (2018-0610)

SFI: '02'
Access Conditions:
READ PIN
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

1 to X V2X configuration data O X bytes
The V2X configuration data is encoded as specified in the V2X Service Table.
V2X configuration data object tag:
V2X configuration data objects Tag Values Condition

V2X configuration data '80' Shall be present if service n°1 is
"available" in the V2X service table
3GPP
Release 15 232 3GPP TS 31.102 V15.21.0 (2018-0610)
4.7 Files of USIM

This clause contains two figures depicting the file structure of the UICC and the ADFUSIM. ADFUSIM shall be selected
using the AID and information in EFDIR.
3GPP
Release 15 233 3GPP TS 31.102 V15.21.0 (2018-0610)
MF
'3F00'
EFDIR EFPL EFARR EFICCID EFUMPC

'2F00' '2F05' '2F06' '2FE2' '2F08'
DFGSM see TS
'7F20' 51.011 [18]
DFCD see TS
'7F11' 31.101 [11]
DFTELECOM
'7F10'
EFARR EFADN EFFDN EFSMS EFMSISDN

'6F06' '6F3A' '6F3B' '6F3C' '6F40'
EFSMSP EFSMSS EFLND EFSMSR EFSDN

'6F42' '6F43' '6F44' '6F47' '6F49'
EFEXT1 EFEXT2 EFEXT3 EFBDN EFEXT4

'6F4A' '6F4B' '6F4C' '6F4D' '6F4E'
EFECCP EFRMA EFSUME EFICE_DN EFICE_FF

'6F4F' '6F53' '6F54' '6FE0' '6FE1'
EFPSISMSC
'6FE5'
DFGRAPHICS
'5F50'
EFIMG EFIIDFn EFICE_graphics

'4F20' '4FXX' '4F21'
DFPHONEBOOK
'5F3A'
EFPSC EFCC EFPUID EFPBR EFUID

'4F22' '4F23' '4F24' '4F30' '4FXX'
EFCCP1 EFIAP EFADN EFEXT1 EFPBC

'4FXX' '4FXX' '4FXX' '4FXX' '4FXX'
EFGRP EFAAS EFGAS EFANR EFSNE

EFEMAIL EFPURI
'4FXX' '4FXX'
DFMULTIMEDIA
'5F3B'
EFMML EFMMDF
'4F47' '4F48'
DFMMSS See
'5F3C' C.S0074-
A[53]
3GPP
Release 15 234 3GPP TS 31.102 V15.21.0 (2018-0610)
DFMCSPTT
'5F3D'
EFMST EFMCSPTT
_CONFIG
'4F01' '4F02'
DFV2X
'5F3E'
EFVST EFV2X_CONFIG
'4F01' '4F02'
NOTE 1: Files under DFTELECOM with shaded background are defined in 3GPP TS 51.011 [18].
NOTE 2: Void.
NOTE 3: Files under DFMMSS are defined in C.S0074-A [53].
NOTE 4: The values '4F03', '4F04' and '4F05' under DFMCSPTT were used in earlier versions of this specification, and
should not be re-assigned in future versions.
Figure 4.1: File identifiers and directory structures of UICC
3GPP
Release 15 235 3GPP TS 31.102 V15.21.0 (2018-0610)
3GPP
Release 15 236 3GPP TS 31.102 V15.21.0 (2018-0610)
ADFUSIM
EFLI EFARR EFIMSI EFKeys EFKeysPS

'6F05' '6F06' '6F07' '6F08' '6F09'
EFDCK EFHPPLMN EFCNL EFACMmax EFUST

'6F2C' '6F31' '6F32' '6F37' '6F38'
EFACM EFFDN EFSMS EFGID1 EFGID2

'6F39' '6F3B' '6F3C' '6F3E' '6F3F'
EFMSISDN EFPUCT EFSMSP EFSMSS EFCBMI

'6F40' '6F41' '6F42' '6F43' '6F45'
EFSPN EFSMSR EFCBMID EFSDN EFEXT2

'6F46' '6F47' '6F48' '6F49' '6F4B'
EFEXT3 EFBDN EFEXT5 EFCCP2 EFCBMIR

'6F4C' '6F4D' '6F4E' '6F4F' '6F50'
EFEXT4 EFEST EFACL EFCMI EFSTART-HFN

'6F55' '6F56' '6F57' '6F58' '6F5B'
EFTHRESHOLD EFPLMNwAcT EFOPLMNwAcT EFHPLMNwAcT EFPSLOCI

'6F5C' '6F60' '6F61' '6F62' '6F73'
EFACC EFFPLMN EFLOCI EFICI EFOCI

'6F78' '6F7B' '6F7E' '6F80' '6F81'
EFICT EFOCT EFAD EFVGCS EFVGCSS

'6F82' '6F83' '6FAD' '6FB1' '6FB2'
EFVBS EFVBSS EFeMLPP EFAaeM EFECC

'6FB3' '6FB4' '6FB5' '6FB6' '6FB7'
EFHiddenkey EFNETPAR EFPNN EFOPL EFMBDN

'6FC3' '6FC4' '6FC5' '6FC6' '6FC7'
EFEXT6 EFMBI EFMWIS EFCFIS EFEXT7

'6FC8' '6FC9' '6FCA' '6FCB' '6FCC'
EFSPDI EFMMSN EFEXT8 EFMMSICP EFMMSUP

'6FCD' '6FCE' '6FCF' '6FD0' '6FD1'
EFMMSUCP EFNIA EFVGCSCA EFVBSCA EFGBAP

'6FD2' '6FD3' '6FD4' '6FD5' '6FD6'
EFMSK EFMUK EFEHPLMN EFGBANL EFEHPLMNPI

'6FD7' '6FD8' '6FD9' '6FDA' '6FDB'
EFLRPLMNSI EFNAFKCA EFSPNI EFPNNI EFNCP-IP

'6FDC' '6FDD' '6FDE' '6FDF' '6FE2'
EFEPSLOCI EFEPSNSC EFUFC EFUICCIARI EFNASCONFIG

'6FE3' '6FE4' '6FE6' '6FE7' '6FE8'
3GPP
Release 15 237 3GPP TS 31.102 V15.21.0 (2018-0610)
EFPWS EFFDNURI EFBDNURI EFSDNURI EFIWL

'6FEC' '6FED' '6FEE' '6FEF' '6FF0'
EFIPS EFIPD EFePDGId EFePDGSelection EFePDGIdEm

'6FF1' '6FF2' '6FF3' '6FF4' '6FF5'
EFePDGSelectionE EFFromPreferred EFIMSConfigData EF3GPPPSDATAOF EF3GPPPSDATAOF

m F Fservicelist
'6FF6' '6FF7' '6FF8' '6FF9' '6FFA'
EFTVCONFIG EFXCAPConfigData EFEARFCNList EF5GSLOCI EF5GS3GPPNSC

'6FFB' '6FFC' '6FFE '6FFF' '6F00'
EF5GSN3GPPNSC EFSteering_of_UE_i
n_VPLMN
'6F01 '6F05'
DFPHONEBOOK
'5F3A'
EFPSC EFCC EFPUID EFPBR EFUID

'4F22' '4F23' '4F24' '4F30' '4FXX'
EFCCP1 EFIAP EFADN EFEXT1 EFPBC

EFGRP EFAAS EFGAS EFANR EFSNE

EFEMAIL EFPURI
'4FXX' '4FXX'
DFGSM-ACCESS
'5F3B'
EFKc EFKcGPRS EFCPBCCH EFinvSCAN

'4F20' '4F52' '4F63' '4F64'
DFMexE
'5F3C'
EFMexE-ST EFORPK EFARPK EFTPRK EFTKCDF

'4F40' '4F41' '4F42' '4F43' '4FXX'
DFSoLSA
'5F70'
EFSAI EFSLL
'4F30' '4F31'
DFWLAN
'5F40'
EFPseudo EFUPLMNWLAN EF0PLMNWLAN EFUWSIDL EFOWSIDL

'4F41' '4F42' '4F43' '4F44' '4F45'
EFWRI EFHWSIDL EFWEHPLMNPI EFWHPI EFWLRPLMN

'4F46' '4F47' '4F48' '4F49' '4F4A'
3GPP
Release 15 238 3GPP TS 31.102 V15.21.0 (2018-0610)
EFHPLMNDAI
'4F4B'
DFHNB
'5F50'
EFACSGL EFCSGT EFHNBN EFOCSGL EFOCSGT

'4F81' '4F82' '4F83' '4F84' '4F85'
EFOHNBN
'4F86'
DFProSe
'5F90'
EFPROSE_MON EFPROSE_ANN EFPROSEFUNC EFPROSE_RADIO_ EFPROSE_RADIO_

COM MON
'4F01' '4F02' '4F03' '4F04' '4F05'
EFPROSE_RADIO_ EFPROSE_POLICY EFPROSE_PLMN EFPROSE_GC EFPST

ANN
'4F06' '4F07' '4F08' '4F09' '4F10'
EFPROSE_UIRC EFPROSE_GM_DI EFPROSE_RELAY EFPROSE_RELAY_

SCOVERY DISCOVERY
'4F11' '4F12' '4F13' '4F14'
DFACDC
'5FA0'
EFACDC_LIST EFACDC_OS_CON
FIG
'4F01' '4FXX'
DFTV
'5FB0'
EFTVUSD
'4FXX'
DF5GS
'5FC0'
EF5GS3GPPLOCI EF5GSN3GPPLOCI EF5GS3GPPNSC EF5GSN3GPPNSC EF5GAUTHKEYS

'4F01' '4F02' '4F03' '4F04' '4F05'
EFUAC_AIC EFSUCI_Calc_Info EFSteering_of_UE_i

n_VPLMN
'4F06' '4F07' '4F08'
Figure 4.2: File identifiers and directory structures of USIM
3GPP
Release 15 239 3GPP TS 31.102 V15.21.0 (2018-0610)
NOTE 5: The value '6F65' under ADFUSIM was used in earlier versions of this specification, and should not be re-
assigned in future versions.
5 Application protocol
The requirements stated in the corresponding section 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 "EFUST"). 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 EFDIR file is found or no USIM
applications are listed in the EFDIR file, the ME may then try to select the GSM application as specified in
TS 51.011 [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 EFPL at the MF unless any of the following conditions applies:
- if the EFLI has the value 'FFFF' in its highest priority position, then the preferred language selection shall be the
language preference in the EFPL at the MF level according the procedure defined in TS 31.101 [11];
- if the ME does not support any of the language codes indicated in EFLI , or if EFLI is not present, then the
language selection shall be as defined in EFPL at the MF level according the procedure defined in
TS 31.101 [11];
- if neither the languages of EFLI nor EFPL are supported by the terminal, then the terminal shall use its own
internal default selection.
3GPP
Release 15 240 3GPP TS 31.102 V15.21.0 (2018-0610)
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;
- Access control information request;
- 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;
3GPP
Release 15 241 3GPP TS 31.102 V15.21.0 (2018-0610)
- 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 EFECC. If EFECC does not contain any valid number,
the ME shall use the emergency numbers it stores for use in setting up an emergency call without a
USIM.
Update: The ME performs the updating procedure with EFECC.
NOTE: The update procedure is only applicable when access conditions of ADM for update is set to ALW, PIN
or PIN2.
3GPP
Release 15 242 3GPP TS 31.102 V15.21.0 (2018-0610)
5.1.5 Language indication

Request: The ME performs the reading procedure with EFLI.
Update: The ME performs the updating procedure with EFLI.
5.1.6 Administrative information request

The ME performs the reading procedure with EFAD.
5.1.7 USIM service table request

The ME performs the reading procedure with EFUST.
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,
or 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, EFIMSI, EFLOCI, EFPSLOCI and
EFEPSLOCI.
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
3GPP
Release 15 243 3GPP TS 31.102 V15.21.0 (2018-0610)
ME may suspend the UICC during the extended idle mode DRX cycle. In this case, the ME shall resume the UICC
successfully before the end of the extended idle mode DRX cycle or before any other transmission to the network.
In case the UICC does not support the UICC suspension mechanism, the PIN of the USIM is disabled and deactivation
of UICC is authorized in EFAD, the UE may optionally deactivate the UICC (as specified in clause 6A.1 of
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, EFIMSI, EFLOCI, EFPSLOCI and
EFEPSLOCI.
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.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

The ME performs the reading procedure with EFIMSI.
5.2.3 Access control information request

The ME performs the reading procedure with EFACC.
5.2.4 Higher Priority PLMN search period request

The ME performs the reading procedure with EFHPPLMN.
5.2.5 Location information

Request: The ME performs the reading procedure with EFLOCI.
Update: The ME performs the updating procedure with EFLOCI.
In the case when updating EFLOCI with data containing the TMSI value and the card reports the error '6581' (Memory
Problem), the ME shall terminate 3G operation.
5.2.6 Cipher and Integrity key

Request: The ME performs the reading procedure with EFKeys.
Update: The ME performs the updating procedure with EFKeys.
5.2.7 Forbidden PLMN

Request: The ME performs the reading procedure with EFFPLMN.
Update: The ME performs the updating procedure with EFFPLMN.
3GPP
Release 15 244 3GPP TS 31.102 V15.21.0 (2018-0610)
5.2.8 Void
5.2.9 User Identity Request

The ME selects a USIM and performs the reading procedure with EFIMSI.
5.2.10 GSM Cipher key

Requirement: Service n°27 "available".
Request: The ME performs the reading procedure with EFKc.
Update: The ME performs the updating procedure with EFKc.
5.2.11 GPRS Cipher key

Request: The ME performs the reading procedure with EFKcGPRS.
Update: The ME performs the updating procedure with EFKcGPRS.
5.2.12 Initialisation value for Hyperframe number

Request: The ME performs the reading procedure with EFSTART-HFN.
Update: The ME performs the updating procedure with EFSTART-HFN.
5.2.13 Maximum value of START

Request: The ME performs the reading procedure with EFTHRESHOLD.
5.2.14 HPLMN selector with Access Technology request

Request: The ME performs the reading procedure with EFHPLMNwAcT.
5.2.15 Packet Switched Location information

Request: The ME performs the reading procedure with EFPSLOCI.
Update: The ME performs the updating procedure with EFPSLOCI.
5.2.16 Cipher and Integrity key for Packet Switched domain

Request: The ME performs the reading procedure with EFKeysPS.
Update: The ME performs the updating procedure with EFKeysPS.
5.2.17 LSA information

Request: The ME performs the reading procedure with EFSAI, EFSLL and its associated LSA Descriptor files.
Update: The ME performs the updating procedure with EFSLL.
3GPP
Release 15 245 3GPP TS 31.102 V15.21.0 (2018-0610)
5.2.18 Voice Group Call Services

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

Voice Broadcast Service
Request: The ME performs the reading procedure with EFVBS.
Voice Broadcast Service Status
Request: The ME performs the reading procedure with EFVBSS.
Update: The ME performs the updating procedure with EFVBSS.
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 EFGBABP. 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 EFMUK 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 EFMSK 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

Request: The ME performs the reading procedure with EFEHPLMN.
3GPP
Release 15 246 3GPP TS 31.102 V15.21.0 (2018-0610)
5.2.26 Last RPLMN Selection Indication request

Request: The ME performs the reading procedure with EFLRPLMNSI.
5.2.27 EPS Location Information

Request: The ME performs the reading procedure with EFEPSLOCI.
Update: The ME performs the updating procedure with EFEPSLOCI.
5.2.28 EPS NAS Security Context

Request: The ME performs the reading procedure with EFEPSNSC.
Update: The ME performs the updating procedure with EFEPSNSC.
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

Request: The ME performs the reading procedure with EFNASCONFIG.
For each NAS configuration parameter, a parameter provided in EFNASCONFIG shall take precedence over the
corresponding parameter stored in the ME's non-volatile memory.
5.2.30 PWS Configuration

Request: The ME performs the reading procedure with EFPWS.
5.2.31 EPS 5GS Location Information

Request: The ME performs the reading procedure with EF5GS3GPPLOCI or with EF5GSN3GPPLOCI.
Update: The ME performs the updating procedure with EF5GS3GPPLOCI or with EF5GSN3GPPLOCI.
5.2.32 5GS NAS Security Context

Request: The ME performs the reading procedure with EF5GS3GPPNSC and EF5GSN3GPPNSC.
Update: The ME performs the updating procedure with EF5GS3GPPNSC and EF5GSN3GPPNSC.
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].
3GPP
Release 15 247 3GPP TS 31.102 V15.21.0 (2018-0610)
5.3 Subscription related procedures

5.3.1 Phone book procedures
5.3.1.1 Initialisation
The ME first reads the content of EFPBR to determine the configuration phonebook. If the EFIAP file is indicated in EFPBR
following tag 'A8' the ME reads the content of EFIAP 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 EFPBC the 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 EFHiddenkey.
Update: The ME performs the updating procedure with EFHiddenkey.
5.3.2 Dialling numbers

Requirements:
- Service n°1 "available" for ADN located under the local phonebook;
- Presence of EFADN in EFPBR for ADN located under the global phonebook;
- Presence of EFANR in EFPBR 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 EFADN and its associated extension files EFCCP1 and EFEXT1 as
described in the procedures below, but also to EFANR, EFFDN, EFMSISDN, EFBDN, EFSDN, EFOCI, EFICI, and EFMBDN and 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.
3GPP
Release 15 248 3GPP TS 31.102 V15.21.0 (2018-0610)
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 EFEXT1. 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 EFEXT1. 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 EFADN 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 seeks for a free record in EFEXT1. 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 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 EFEXT1. 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 EFEXT1. 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 EFADN is marked as "free".
Request: The ME sends the identification of the information to be read. The ME shall analyse the data of
EFADN to ascertain, whether additional data is associated in EFEXT1 or EFCCP1. If necessary, then the
ME performs the reading procedure on these Efs to assemble the complete ADN/SSC.
3GPP
Release 15 249 3GPP TS 31.102 V15.21.0 (2018-0610)
Purge: The ME shall access each EF which references EFEXT1 (EFEXT2, EFEXT6) 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

Request: The USIM seeks for the identified short message. If this message is found, the ME performs the
reading procedure with EFSMS.
If service n°10 is "available" and the status of the SMS is '1D' (status report requested, received
and stored in EFSMSR), the ME performs the reading procedure with the corresponding record in
EFSMSR. If the ME does not find a corresponding record in EFSMSR, then the ME shall update the
status of the SMS with '15' (status report requested, received but not stored in EFSMSR).
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 EFSMS.
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 EFSMS, 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 EFSMSR), the ME performs the erasure procedure for EFSMSR with the corresponding
record in EFSMSR.
5.3.4 Advice of charge

Accumulated Call Meter.
3GPP
Release 15 250 3GPP TS 31.102 V15.21.0 (2018-0610)
Request: The ME performs the reading procedure with EFACM. The USIM returns the last updated value of
the ACM.
Initialisation: The ME performs the updating procedure with EFACM using the new initial value.
Increasing: The ME performs the increasing procedure with EFACM sending the value which has to be added.
Accumulated Call Meter Maximum Value.
Request: The ME performs the reading procedure with EFACMmax.
Initialisation: The ME performs the updating procedure with EFACMmax using the new initial maximum value.
Price per Unit and Currency Table (PUCT).
Request: The ME performs the reading procedure with EFPUCT.
Update: The ME performs the updating procedure with EFPUCT.
5.3.5 Capability configuration parameters

Request: The ME performs the reading procedure with EFCCP2.
Update: The ME performs the updating procedure with EFCCP2.
Erasure: The ME sends the identification of the requested information to be erased. The content of the
identified record in EFCCP2 is marked as "free".
5.3.6 User controlled PLMN selector with Access Technology

Request: The ME performs the reading procedure with EFPLMNwACT.
Update: The ME performs the updating procedure with EFPLMNwACT.
5.3.7 Cell broadcast message identifier

Request: The ME performs the reading procedure with EFCBMI.
Update: The ME performs the updating procedure with EFCBMI.
5.3.8 Group identifier level 1

Request: The ME performs the reading procedure with EFGID1.
5.3.9 Group identifier level 2

Request: The ME performs the reading procedure with EFGID2.
5.3.10 Service provider name

Request: The ME performs the reading procedure with EFSPN.
3GPP
Release 15 251 3GPP TS 31.102 V15.21.0 (2018-0610)
5.3.11 Enhanced multi level precedence and pre-emption service

Request: The ME performs the reading procedure with EFeMLPP.
5.3.12 Cell broadcast message identifier ranges

Request: The ME performs the reading procedure with EFCBMIR.
Update: The ME performs the updating procedure with EFCBMIR.
5.3.13 Short message status report

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 EFSMSR 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 EFSMS. If such a record identifier is found in
EFSMSR, it is used for storage. If such a record identifier is not found, then the ME seeks for a free
entry in EFSMSR for storage. If no free entry is found the ME runs the Purge procedure with EFSMSR.
If there is still no free entry, the status report is not stored.
If the ME found an appropriate record in EFSMSR for storage, it updates the record with the status
report setting the record identifier in EFSMSR to the appropriate record number of the short message
in EFSMS.
The status in EFSMS is updated accordingly by performing the update procedure with EFSMS.
Erasure: The ME runs the update procedure with EFSMSR 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 EFSMSR. With each record
the ME checks the corresponding short messages in EFSMS. If the status (byte 1) of the
corresponding SMS is not equal '1D' (status report requested, received and stored in EFSMSR), the
ME shall perform the erasure procedure with the appropriate record in EFSMSR.
5.3.14 APN Control List

Request: The ME performs the reading procedure with EFACL.
Update: The ME performs the updating procedure with EFACL.
Enabling: The ME activates service n°3 in EFEST (bit n°3 set to "1").
Disabling: The ME deactivates service n°3 in EFEST (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
EFACL 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 EFACL.
3GPP
Release 15 252 3GPP TS 31.102 V15.21.0 (2018-0610)
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 EFACL 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 EFACL.
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 EFACL 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 EFACL.
5.3.15 Depersonalisation Control Keys

Request: The ME performs the reading procedure with EFDCK.
5.3.16 Co-operative Network List

Request: The ME performs the reading procedure with EFCNL.
5.3.17 CPBCCH information

Request: The ME performs the reading procedure with EFCPBCCH.
Update: The ME performs the updating procedure with EFCPBCCH.
5.3.18 Investigation Scan

Request: The ME performs the reading procedure with EFInvScan.
5.3.19 Enabled Services Table Request

Requirement: Service n°2, 6, 34 or 35 "available".
Request: The ME performs the reading procedure with EFEST.
Update: The ME performs the updating procedure with EFEST.
5.3.20 Operator controlled PLMN selector with Access Technology

Request: The ME performs the reading procedure with EFOPLMNwACT
5.3.21 HPLMN selector with Access Technology

Request: The ME performs the reading procedure with EFHPLMNwACT
3GPP
Release 15 253 3GPP TS 31.102 V15.21.0 (2018-0610)
5.3.22 Automatic Answer on eMLPP service

Requirement: Service n°25 "available"
Request: The ME performs the reading procedure with EFAaeM.
Update: The ME performs the updating procedure with EFAaeM.
5.3.23 Network Parameter information

Request: The ME performs the reading procedure with EFNETPAR.
Update: The ME performs the updating procedure with EFNETPAR.
5.3.24 PLMN network name

Request: The ME performs the reading procedure with EFPNN.
5.3.25 Operator PLMN List

Request: The ME performs the reading procedure with EFOPL
5.3.26 Message Waiting Indication

Request: The ME performs the reading procedure with EFMWIS.
Update: The ME performs the updating procedure with EFMWIS.
5.3.27 Call Forwarding Indication Status

Request: The ME performs the reading procedure with EFCFIS.
Update: The ME performs the updating procedure with EFCFIS.
5.3.28 Service Provider Display Information

Requirement: Service n°19 and 51 are "available".
Request: The ME performs the reading procedure with EFSPDI.
Update: The ME performs the updating procedure with EFSPDI.
5.3.29 MMS Notifications

Request: The ME sends the identification of the information to be read, then the ME performs the reading
procedure with EFMMSN. If Service n°53 is available the ME shall analyse the data of EFMMSN to
ascertain, whether additional data is associated in EFEXT8. If necessary, then the ME performs the
reading procedure on EFEXT8 to assemble the complete MMS notification.
Update: The ME analyses and assembles the MMS notification to be stored as follows:
3GPP
Release 15 254 3GPP TS 31.102 V15.21.0 (2018-0610)
- if the MMS notification contains not more bytes than the maximum possible number for EFMMSN 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 EFMMSN.
- if the MMS notification contains more bytes than the maximum possible number for EFMMSN then the ME seeks for
a sufficient number of free records in EFEXT8 to store the complete MMS notification.
- If there is not a sufficient number of EFEXT8 records 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 EFMMSN is coded with the associated record number in the EFEXT8. The
remaining bytes are stored in the selected EFEXT8 record where the type of the record is then set to
"additional data". The second byte of the EFEXT8 record 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 EFEXT8 by 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 EFEXT8
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 EFEXT8 are then marked by the ME as "free" by setting them to 'FF'.
5.3.30 MMS Issuer Connectivity Parameters

Request: the ME performs the reading procedure with EFMMSICP.
Update: The ME performs the updating procedure with EFMMSICP.
5.3.31 MMS User Preferences

Request: the ME performs the reading procedure with EFMMSUP.
Update: The ME performs the updating procedure with EFMMSUP.
5.3.32 MMS User Connectivity Parameters

Requirement: Service n°52 and n°55 "available".
Request: the ME performs the reading procedure with EFMMSUCP.
Update: The ME performs the updating procedure with EFMMSUCP.
5.3.33 Network's indication of alerting

Request: The ME performs the reading procedure with EFNIA.
5.3.34 Multimedia Messages Storage

If the terminal supports Multimedia Message Storage on the USIM, then the following procedures apply.
3GPP
Release 15 255 3GPP TS 31.102 V15.21.0 (2018-0610)
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 EFMMDF, a BER-TLV structured file.
A list of multimedia messages is stored in the BER-TLV file EFMMLwhere each data object identifies one Multimedia
Message stored in EFMMDF.
Prerequisite: Service n°67 "available".
Request: The ME performs the reading procedures on EFMML 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 EFMML) for the multimedia message and check for
available space in the EFMMDF 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 DFMULTIMEDIA files. Then
the ME performs the following procedures:
If there is no available empty space in the EFMMDF file to store the MM, the procedure is aborted
and the user is notified.
Else, the ME stores the MM in EFMMDF, then updates the information in EFMML accordingly.
Erasure: After a successful deletion of an MM in EFMMDF the terminal updates the information in EFMML
accordingly.
5.3.35 Equivalent HPLMN Presentation Indication request

Request: The ME performs the reading procedure with EFEHPLMNPI.
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 EFNAFKCA.
5.3.37 Service provider name Icon

Request: The ME performs the reading procedure with EFSPN and EFSPNI.
5.3.38 PLMN network name Icon

Request: The ME performs the reading procedure with EFPNN and EFPNNI.
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. EFICE_DN, EFICE_FF or EFICE_graphics.
Request: The terminal performs the read procedure with EFICE_DN and/or EFICE_FF and/or EFICE_graphics.
Update: The terminal performs the update procedure with EFICE_DN and/or EFICE_FF and/or
EFICE_graphics.
Disable ICE display: The terminal performs the deactivate procedure consecutively on all the supported files
(EFICE_DN, EFICE_FF and EFICE_graphics).
3GPP
Release 15 256 3GPP TS 31.102 V15.21.0 (2018-0610)
Enable ICE display: The terminal performs the activate procedure consecutively on all the supported files (EF ICE_DN,
EFICE_FF and EFICE_graphics ).
The content of the EFICE_DN, EFICE_FF and EFICE_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, EFFDN or EFSDN or EFFDNURI or EFSDNURI 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 EFEST).
Request: The ME performs the reading procedure with EFFDN.
If eCall only calls are supported, then EFFDN 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, 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 EFEST).
Request: The ME performs the reading procedure with EFFDNURI.
If eCall only calls are supported, then EFFDNURI 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. 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 EFEST).
Request: The ME performs the reading procedure with EFSDN.
If eCall and normal calls are supported, then the last two entries of EFSDN 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, 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 EFEST).
Request: The ME performs the reading procedure with EFSDNURI.
If eCall and normal calls are supported, then the last two entries of EFSDNURI 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. A terminal in eCall and normal mode performs the SDN related procedures.
NOTE: These URIs can contain MSISDNs encoded as tel URIs.
3GPP
Release 15 257 3GPP TS 31.102 V15.21.0 (2018-0610)
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 EFPSISMSC.
Update: The ME performs the updating procedure with EFPSISMSC.
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 EFUICCIARI.
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 EFUICCIARI prior to sending a registration to the IMS.
5.3.43 TV Configuration
Request: The ME performs the reading procedure with EFTVCONFIG.
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
EF3GPPPSDataOff.
5.3.45 3GPP PS Data Off service list related procedures

Request: If the ME supports 3GPP PS Data Off the ME shall perform the reading procedure with
EF3GPPPSDATAOFFservicelist. If the ME performs the reading procedure with EF3GPPPSDATAOFFservicelist, the UE
shall use the 3GPP PS Data Off Service list in the EF3GPPPSDATAOFFservicelist as described in
TS 24.229 [63] subclauses 4.17, B.3.1.5 and L.3.1.5.
3GPP
Release 15 258 3GPP TS 31.102 V15.21.0 (2018-0610)
5.3.46 EARFCN list for MTC/NB-IOT UEs

Request: The ME performs the reading procedure with EFEARFCNList.
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 EFSUCI_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.
5.3.49 Control plane-based Steering of RoamingUE in VPLMN related

procedures
Request: The ME performs the reading procedure with EFSteering_of_UE_in_VPLMN
Editor's Note: The procedure may need to be updated depending on the decision (in 3GPP TS 24.501 and/or
3GPP TS 33.501) whether the security terminates in the ME or the USIM.
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 in a VPLMN.
If service n°127 is not "available" in the USIM Service Table, the Registration Accept may contain control plane based
Steering of Roaming information during the initial registration 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.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.
3GPP
Release 15 259 3GPP TS 31.102 V15.21.0 (2018-0610)
5.4.3 Data Download via SMS-CB

The ME shall perform the reading procedure with EFCBMID, 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

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

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

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

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

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

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.
3GPP
Release 15 260 3GPP TS 31.102 V15.21.0 (2018-0610)
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 EFUFC.
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 EFIWL.
EFIWL, EFIPS, EFIPD 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 white list configured in the USIM (EFIWL)
- 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

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 EFMexE-ST
3GPP
Release 15 261 3GPP TS 31.102 V15.21.0 (2018-0610)
5.5.2 Operator root public key

Requirement: Service n°41 (MexE) "available" and MexE ST service n°1 (EFORPK) "available".
Request: The ME performs the reading procedure with EFORPK. The ME shall analyse the data of EFORPK
(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 (EFARPK) "available".
Request: The ME performs the reading procedure with EFARPK. The ME shall analyse the data of EFARPK
(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 (EFTPRPK) "available".
Request: The ME performs the reading procedure with EFTPRPK. The ME shall analyse the data of EFTPRPK
(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 EFTKCDF. The ME shall analyse the data of EFTKCDF
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. EFUWSIDL, EFHWSIDL, EFOWSIDL, EFWEHPLMNPI , EFWLRPLMN, EFWHPI and
EFHPLMDAI)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
EFOPLMNWLAN respectively 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"
3GPP
Release 15 262 3GPP TS 31.102 V15.21.0 (2018-0610)
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 EFNCP-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 EFNCP-IP before 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 EFNCP-IP.
5.8 H(e)NB related procedures

5.8.1 CSG Access Control procedures
Request: The terminal performs the read procedure with EFACSGL.
Update: The terminal performs the updating procedure with EFACSGL
The ME shall read the allowed CSG Ids from EFACSGL in order to perform H(e)NB selection procedures. The lists in
EFACSGL shall take precedence over the list stored in the ME non-volatile memory.
Request: The terminal performs the read procedure with with EFOCSGL.
The ME shall read the Operator CSG Ids from EFOCSGL in order to perform H(e)NB selection procedures. The list in
EFOCSGL shall take precedence over the list stored in the ME non-volatile memory.
In case of a manual CSG cell selection, the ME shall read EFAD and CSG Lists Display Indicators from EFOCSGL and
display CSG Ids accordingly. The configuration in EFOCSGL shall 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

Request: The terminal performs the read procedure with EFACSGL and EFCSGT.
3GPP
Release 15 263 3GPP TS 31.102 V15.21.0 (2018-0610)
Update: The terminal performs the updating procedure with EFACSGL
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.
Request: The terminal performs the read procedure with EFOCSGL and EFOCSGT.
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 EFOCSGL. The Operator CSG Type has precedence.
5.8.3 HNB name display related procedures

Request: The terminal performs the read procedure with EFACSGL and EFHNBN.
Update: The terminal performs the updating procedure with EFACSGL and EFHNBN.
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.
Request: The terminal performs the read procedure with EFOCSGL and EFOHNBN.
The ME shall discover the association between the selected CSG ID and either a HNB Name from EF ACSGL or an
Operator HNB from EFOCSGL. The Operator HNB Name has precedence. If this association exists, the HNB Name shall
be displayed.
In case of a manual CSG cell selection, the ME shall read EFAD and the CSG Lists Display Indicators from EFOCSGL and
display HNB Name accordingly. The configuration in EFOCSGL shall 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 EFPROSE_MON. and EFPROSE_ANN.
5.9.2 HPLMN ProSe Function address

Request: The ME performs the reading procedure with EFPROSEFUNC.
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 EFAD or the ME received service authorization from the ProSe Function.
Request: The ME performs the reading procedure with EFPROSE_RADIO_COM.
3GPP
Release 15 264 3GPP TS 31.102 V15.21.0 (2018-0610)
5.9.4 ProSe direct discovery related Procedures

Request: The ME performs the reading procedure with EFPROSE_RADIO_MON.
Request: The ME performs the reading procedure with EFPROSE_RADIO_ANN.

Request: The ME performs the reading procedure with EFPROSE_POLICY.

enabled in EFAD or the ME received service authorization from the ProSe Function
Request: The ME performs the reading procedure with EFPROSE_PLMN.
5.9.7 ProSe Group Counter related Procedures

Request: The ME performs the reading procedure with EFPROSE_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 EFPROSE_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 EFPROSE_GC in order to guarantee
that EF is not filled with unnecessary entries.
5.9.8 ProSe Usage Information Reporting Configuration related

Procedures
Request: The ME performs the reading procedure with EFPROSE_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

Request: The ME performs the reading procedure with EFPROSE_GM_DISCOVERY.
3GPP
Release 15 265 3GPP TS 31.102 V15.21.0 (2018-0610)
5.9.10 ProSe Relay related Procedures

Request: The ME performs the reading procedure with EFPROSE_RELAY and EFPROSE_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 EFePDGId. The UE then shall use the Home ePDG
identifier(s) present in the EFePDGId to perform the ePDG selection procedure as defined in
3GPP TS 24.302 [79].
If EFePDGId and EFePDGSelection 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

Request: The ME performs the reading procedure with EFePDGSelection. The UE then shall use the ePDG
selection information present in the EFePDGSelection to perform the ePDG selection procedure as
defined in 3GPP TS 24.302 [79].
If EFePDGId and EFePDGSelection 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.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 EFACDC.
5.12 MCPTT MCS related procedures

5.12.1 MCPTT MCS configuration
Requirement: At least one of the services is "available" in the MCS Service Tableservice n°1, 2, 3 or 4 is
"available" in the MCPTT Service Table.
Request: The ME performs the reading procedure with EFMCSPTT _CONFIG.
3GPP
Release 15 266 3GPP TS 31.102 V15.21.0 (2018-0610)
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
Request: The ME performs the reading procedure with EFePDGIdEm. The UE then shall use the Emergency
ePDG identifier(s) present in the EFePDGIdEm to perform the ePDG selection procedure.
If EFePDGIdEm and EFePDGSelectionEm 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

Request: The ME performs the reading procedure with EFePDGSelectionEm. The UE then shall use the ePDG
selection information for Emergency Services present in the EFePDGSelectionEm to perform the ePDG
selection procedure.
If EFePDGIdEm and EFePDGSelectionEm 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

Request: The ME performs the reading procedure with EFFromPreferred. The UE then shall use the From
Preferred value in the EFFromPreferred as described in 3GPP TS 24.607 [86] subclause 4.5.2.12.
5.13.5 IMS Configuration Data related procedures

3GPP
Release 15 267 3GPP TS 31.102 V15.21.0 (2018-0610)
Request: The ME may perform the reading procedure with EFIMSConfigData. If the ME performs the reading
procedure with EFIMSConfigData, the UE shall use the IMS Configuration Data in the EFIMSConfigData as
described in 3GPP TS 24.229 [32] subclause L.2.2.5.1D and
3GPP TS 24.229 [32] subclause 6.1.1.
5.13.6 XCAP Configuration Data related procedures

Request: The ME may perform the reading procedure with EFXCAPConfigData . If the ME performs the reading
procedure with EFXCAPConfigData , the UE shall use the EFXCAPConfigData as described in TS 24.623
[102] subclause 5.2.1.3 and TS 24.623 [102] subclause B.2
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 EFV2X_CONFIG.
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 EFUAC_AIC.
6 Security features
The security aspects of 3G are specified in TS 33.102 [13] and TS 33.103 [14]. This clause gives information related to
security features supported by the USIM to enable the following:
- authentication of the USIM to the network;
- authentication of the network to the USIM;
- authentication of the user to the USIM;
- data confidentiality over the radio interface;
- file access conditions;
- conversion functions to derive GSM parameters.
6.1 Authentication and key agreement procedure

This clause gives an overview of the authentication mechanism and cipher and integrity key generation which are
invoked by the network. For the specification of the corresponding procedures across the USIM/ME interface see
clause 5.
The mechanism achieves mutual authentication by the user and the network showing knowledge of a secret key K
which is shared between and available only to the USIM and the AuC in the user's HE. In addition, the USIM and the
3GPP
Release 15 268 3GPP TS 31.102 V15.21.0 (2018-0610)
HE keep track of counters SQNMS and SQNHE respectively to support network authentication. SQNHE is a counter in the
HLR/AuC, individual for each user and SQNMS denotes the highest sequence number the USIM has ever accepted.
When the SN/VLR initiates an authentication and key agreement, it selects the next authentication vector and sends the
parameters RAND and AUTN (authentication token) to the user. Each authentication token consists of the following
components: a sequence number SQN, an Authentication Management Field (AMF) and a message authentication code
MAC over the RAND, SQN and AMF.
The USIM checks whether AUTN can be accepted and, if so, produces a response RES which is sent back to the
SN/VLR. The SN/VLR compares the received RES with XRES. If they match the SN/VLR considers the authentication
and key agreement exchange to be successfully completed. The USIM also computes CK and IK. The established keys
CK and IK will be used by the ME to perform ciphering and integrity functions.
A permanent secret key K is used in this procedure. This key K has a length of 128 bits or 256 bits and is stored within
the USIM for use in the algorithms described below. Also more than one secret key K can be stored in the USIM. The
active key to be used by the algorithms is signalled within the AMF field in the AUTN.
6.2 Cryptographic Functions

The names and parameters of the cryptographic functions supported by the USIM are defined in TS 33.102 [13]. These
are:
f1: a message authentication function for network authentication used to compute XMAC;
f1*: a message authentication function for support to re-synchronisation with the property that no
valuable information can be inferred from the function values of f1* about those of f1, ..., f5, f5*
and vice versa;
f2: a message authentication function for user authentication used to compute SRES;
f3: a key generating function to compute the cipher key CK;
f4: a key generating function to compute the integrity key IK;
f5: a key generating function to compute the anonymity key AK (optional);
f5*: a key generating function to compute AK in re-synchronisation procedures with the property that
no valuable information can be inferred from the function values of f5* about those of f1, f1*,
f2, ..., f5 and vice versa.
These cryptographic functions may exist either discretely or combined within the USIM.
6.3 GSM Conversion Functions

To gain GSM access, the USIM provides the conversion functions c2 and c3. These functions derive the required GSM
parameters (SRES, cipher key Kc) from available 3G parameters.
6.4 User verification and file access conditions

The security architecture as defined in TS 31.101 [11] applies to the USIM application with the following definitions
and additions.
- The USIM application shall use a global key reference as PIN and local key reference as PIN2. For access to
DFTELECOM the PIN shall be verified. Access with PIN2 is limited to the ADF(USIM).
- The only valid values for the usage qualifier are '00' (verification requirement is not used) and '08' (user
authentication knowledge based (PIN)) as defined in ISO/IEC 7816-4 [20].
Disabling of PIN2 is allowed. This is, however, not the case if PIN2 is mapped to the CHV2 of a GSM application.
3GPP
Release 15 269 3GPP TS 31.102 V15.21.0 (2018-0610)
7 USIM Commands
7.1 AUTHENTICATE
7.1.1 Command description
The function can be used in several different contexts:
- a 3G security context, when 3G authentication vectors (RAND, XRES, CK, IK, AUTN) are available (i.e. the
UE is located in the UTRAN, or in a GSM radio access network which is connected to a 3G or 3G capable
VLR/SGSN), or
- a GSM security context, when GSM authentication data are available only (i.e. the UE is located in the GSM
radio access network which is connected to a non-3G capable VLR/SGSN)
- a VGCS/VBS security context, when VGCS/VBS authentication data is available
- a GBA_U security context, when a GBA bootstrapping procedure is requested
- a MBMS security context, when a MBMS security procedure is requested
- a Local Key Establishment security context, when a Local Key Establishment procedure is requested.
The function is used in GSM or 3G security context during the procedure for authenticating the USIM to its HE and
vice versa. In addition, a cipher key and an integrity key are calculated. For the execution of the command the USIM
uses the subscriber authentication key K, which is stored in the USIM.
The function is used in VGCS/VBS security context during the procedure for retrieving the VGCS/VBS Short Term
Key (VSTK) used by the terminal in establishing VGCS/VBS calls.
The function is used in GBA security context in two different modes:
a) Bootstrapping Mode: during the procedure for mutual authenticating of the USIM and the Bootstrapping Server
Function (BSF) and for deriving bootstrapped key material from the AKA run.
b) NAF Derivation Mode: during the procedure for deriving Network Application Function (NAF) specific keys
from previous bootstrapped key material.
The function is used in MBMS security context in two different modes:
a) MSK Update Mode: during the procedure for updating an MBMS Service Key (MSK).
b) MTK Generation Mode: during the procedure for retrieving the MBMS Traffic Key (MTK) used by the terminal
to decrypt MBMS data.
The function is related to a particular USIM and shall not be executable unless the USIM application has been selected
and activated, and the current directory is the USIM ADF or any subdirectory under this ADF and a successful PIN
verification procedure has been performed (see clause 5).
7.1.1.1 3G security context

The USIM first computes the anonymity key AK = f5K (RAND) and retrieves the sequence number SQN = (SQN Å
AK) Å AK.
Then the USIM computes XMAC = f1K (SQN || RAND || AMF) and compares this with the MAC which is included in
AUTN. If they are different, the USIM abandons the function.
Next the USIM verifies that the received sequence number SQN is previously unused. If it is unused and its value is
lower than SQNMS, it shall still be accepted if it is among the last 32 sequence numbers generated. A possible
verification method is described in TS 33.102 [13].
3GPP
Release 15 270 3GPP TS 31.102 V15.21.0 (2018-0610)
NOTE: This implies that the USIM has to keep a list of the last used sequence numbers and the length of the list
is at least 32 entries.
If the USIM detects the sequence numbers to be invalid, this is considered as a synchronisation failure and the USIM
abandons the function. In this case the command response is AUTS, where:
AUTS = Conc(SQNMS) || MACS;
Conc(SQNMS) = SQNMS  f5*K(RAND) is the concealed value of the counter SQNMS in the USIM; and.
MACS = f1*K(SQNMS || RAND || AMF) where:
RAND is the random value received in the current user authentication request;
the AMF assumes a dummy value of all zeroes so that it does not need to be transmitted in clear in the
resynchronisation message.
If the sequence number is considered in the correct range, the USIM computes RES = f2 K (RAND), the cipher key
CK = f3K (RAND) and the integrity key IK = f4K (RAND) and includes these in the command response. Note that if this
is more efficient, RES, CK and IK could also be computed earlier at any time after receiving RAND.
The use of AMF is HE specific and while processing the command, the content of the AMF has to be interpreted in the
appropriate manner. The AMF may e.g. be used for support of multiple algorithms or keys or for changing the size of
lists, see TS 33.102 [13].
If Service n°27 is "available", the USIM calculates the GSM response parameter K C, using the conversion function
Input:
- RAND, AUTN (AUTN:= SQN Å AK || AMF || MAC).
Output:
- RES, CK, IK if Service n°27 is "not available".
Or
- RES, CK, IK, KC if Service n°27 is "available".
Or
- AUTS.
7.1.1.2 GSM security context

USIM operation in an GSM security context is supported if Service n°38 is "available".
The USIM computes RES = f2K (RAND), the cipher key CK = f3K (RAND) and the integrity key IK = f4K (RAND).
Next the USIM calculates the GSM response parameters SRES and KC, using the conversion functions defined in
TS 33.102 [13].
Input:
- RAND.
Output:
- SRES; KC.
7.1.1.3 VGCS/VBS security context

USIM operation in a VGCS/VBS security context is supported if both Service n°57 and Service n°64 are “available”
(VGCS security context) or if both Service n°58 and Service n°65 are "available" (VBS security context).
The USIM computes the Short Term Key (VSTK) associated with a particular VGCS/VBS Group Identifier
(Group_Id). For this computation, the USIM uses the Voice Group (for VGCS) or Broadcast Group (for VBS) Key
(V_Ki) identified by their respective Group_Id and Master Group Key Identifier (VK_Id). The USIM retrieves the
Group_Id and the service flag (VGCS or VBS) from the received Voice Service Identifier (Vservice_Id).
3GPP
Release 15 271 3GPP TS 31.102 V15.21.0 (2018-0610)
NOTE: The Group_Id has a variable length according to TS 43.068 [46].
The USIM shall first search if the Group_Id corresponds to a stored VGCS Group Identifier in EFVGCS or a stored VBS
Group Identifier in EFVBS.
Then, the USIM shall retrieve the V_Ki corresponding to the given Group_Id and VK_Id.
Then the USIM uses V_Ki and VSTK_RAND as input parameters for the A8_V key derivation function (as defined in
TS 43.020 [44]) in order to compute and returns VSTK.
Input:
- Vservice_Id, VK_Id, VSTK_RAND
Output:
- VSTK.
7.1.1.4 GBA security context (Bootstrapping Mode)

USIM operations in GBA security context are supported if service n°68 is "available".
The USIM receives the RAND and AUTN*. The USIM first computes the anonymity key AK = f5K (RAND) and
retrieves the sequence number SQN = (SQN Å AK) Å AK.
The USIM calculates IK = f4K (RAND) and MAC (by performing the MAC modification function described in
TS 33.220 [42]). Then the USIM computes XMAC = f1K (SQN || RAND || AMF) and compares this with the MAC
previously produced. If they are different, the USIM abandons the function.
Then the USIM performs the checking of AUTN* as in UMTS security context. If the USIM detects the sequence
numbers to be invalid, this is considered as a synchronisation failure and the USIM abandons the function. In this case
the command response is AUTS, which is computed as in UMTS security context.
If the sequence number is considered in the correct range, the USIM computes RES = f2 K (RAND) and the cipher key
CK = f3K (RAND).
The USIM then derives and stores GBA_U bootstrapped key material from CK, IK values. The USIM shall also stores
RAND in the RAND field of EFGBABP
The USIM stores GBA_U bootstrapped key material from only one bootstrapping procedure. The previous
bootstrapped key material, if present, shall be replaced by the new one. This key material is linked with the data
contained in EFGBABP : RAND, which is updated by the USIM and B-TID, which shall be further updated by the ME.
NOTE: According to TS 33.220 [42], NAF-specific keys that may be stored on the USIM are not affected by this
bootstrapping operation.
RES is included in the command response after flipping the least significant bit.
Input:
- RAND, AUTN*
Output:
- RES
or
- AUTS
7.1.1.5 GBA security context (NAF Derivation Mode)

USIM operations in GBA security context are supported if service n°68 is "available".
3GPP
Release 15 272 3GPP TS 31.102 V15.21.0 (2018-0610)
The USIM receives the NAF_ID and IMPI.
The USIM performs Ks_ext_NAF and Ks_int_NAF derivation as defined in TS 33.220 [42] using the key material
from the previous GBA_U bootstrapping procedure.
If no key material is available this is considered as a GBA Bootstrapping failure and the USIM abandons the function.
The status word ‘6985’ (Conditions of use not satisfied) is returned.
Otherwise, the USIM stores Ks_int_NAF and associated B-TID together with NAF_ID. The Ks_int_NAF keys related
to other NAF_Ids, which are already stored in the USIM, shall not be affected. The USIM updates EFGBANL as follows:
- If a record with the given NAF_ID already exists, the USIM updates the B-TID field of this record with the B-
TID value associated to the GBA_U bootstrapped key involved in this GBA_U NAF derivation procedure.
- If a record with the given NAF_ID does not exist, the USIM uses an empty record to store the NAF_ID and the
B-TID value associated to the GBA_U bootstrapped key involved in this GBA_U NAF Derivation procedure.
NOTE: According to TS 33.220 [42], the USIM can contain several Ks_int_NAF together with the associated B-
TID and NAF_ID, but there is at most one pair of Ks_int_NAF and associated B-TID stored per
NAF_ID.
- In case no empty record is available the USIM shall overwrite an existing record to store the NAF_ID and the B-
TID value associated to the GBA_U bootstrapped key involved in this GBA_U NAF Derivation procedure. To
determine the record to overwrite, the USIM shall construct a list of record numbers by storing in the list first
position the record number of the last used (i.e. involved in an Authentication command) or derived
Ks_int_NAF and by shifting down the remaining list elements. The last record number in this list corresponds to
the record to overwrite when the USIM runs out of free records. If an existing record corresponding to a
Ks_int_NAF key in use is overwritten, the application Ks_int_NAF shall not be affected (e.g. in case a
Ks_int_NAF was put into use as an MBMS MUK key, the MUK key shall continue to be available for the
MBMS application).
Then, the USIM returns Ks_ext_NAF.
Input:
- NAF_ID, IMPI
Output:
- Ks_ext_NAF
7.1.1.6 MBMS security context (MSK Update Mode)

USIM operations in MBMS security context are supported if service n°69 is "available".
The USIM receives the MIKEY packet containing an MSK update message. First, the USIM uses the MUK ID to
identify the Ks_int_NAF corresponding with a previous bootstrapping procedure.
The USIM shall check if a new NAF derivation procedure involving the received Idi in the MIKEY message has been
performed or if it is the first time that this Idi is used. If this check cannot be performed because the corresponding
Ks_int_NAF key was overwritten, the USIM abandons the function and returns the status word '6985' (Conditions of
use not satisfied). In case of a new NAF derivation procedure or a new Idi, the USIM shall store the last bootstrapped
Ks_int_NAF as the last generated MUK and update EFMUK as follows:
- If a record with the received Idi (included in the MUK ID: see TS 33.246 [43]) value is already present, then the
MUK ID is stored in the corresponding field of this record, and the associated Time Stamp Counter (TS) field is
reset. Additionally, the USIM internally stores the last successfully used MUK (i.e. MUK that was used during
the last successful MSK update procedure), along with its MUK ID for further use (e.g. to detect Key freshness
failure).
- If a record with the received Idi does not exist, the USIM uses an empty record to include the MUK ID, and reset
the associated TS field.
- In case there is no empty record available in EFMUK the USIM abandons the function and the status word '9867'
(Authentication error, no available memory space in EFMUK) is returned.
3GPP
Release 15 273 3GPP TS 31.102 V15.21.0 (2018-0610)
NOTE: In case no empty record in EFMUK is available the ME should run a MUK Deletion Mode procedure to
free entries in EFMUK before running an MSK Update Mode procedure that involves a new MUK key.
NOTE: In case the ME receives the status word '6985', the ME should derive the required Ks_int_NAF key. In
case the corresponding bootstrapping key Ks is still available, the ME should invoke the Authenticate
command in "GBA - NAF derivation Mode" before invoking again the AUTHENTICATE command in
"MBMS - MSK Update Mode". In case the corresponding bootstrapping key has been updated, the ME
should put the new B-TID into use.
If the received MUK ID does not correspond to the last generated MUK (i.e. last bootstrapped MUK) then the USIM
proceeds as follows:
- If the received MUK ID corresponds to the last successfully used MUK then the USIM uses this MUK to verify
the integrity of the message. If the verification is unsuccessful, the USIM abandons the function and returns the
status word '9862' (Authentication error, incorrect MAC). If the verification is successful, the USIM abandons
the function and returns the status word '9865' (Key Freshness Failure), indicating to the ME that the received
MIKEY message is protected using the last successfully used MUK that does not correspond to the last
generated MUK (the new B-TID shall be put into use: see TS 33.246 [43]). In this case, the USIM shall not
return a MIKEY verification message.
- Otherwise, this is considered as a bootstrapping failure (incorrect MUK) and the USIM abandons the function.
The status word ‘6A88’ (Referenced data not found) is returned.
Otherwise, if the received MUK ID corresponds to the last generated MUK, the USIM uses the MUK value for MSK
validation and derivation functions as described in TS 33.246 [43]. If the validation is unsuccessful, the status word
'9862' (Authentication error, incorrect MAC) is returned and the USIM abandons the function.
After a successful MSK Update procedure the USIM stores the received credentials (e.g. MSK and/or Key Validity
data) and updates EFMSK as follows:
- If a record with the received Key Domain ID and Key Group part (i.e. Key Group part of the MSK ID) already
exists, USIM stores the older MSK ID (if any) and its associated TS as the 2nd MSK ID and TS. The newer MSK
ID is stored as the 1st MSK ID. In case the received MSK message has the same MSK ID as a stored MSK, the
TS associated to this stored MSK is stored as the 1st TS. Otherwise, the 1st TS value is reset. The number of
stored MSK IDs and corresponding TS shall be set to '02' if the USIM stores two different MSK IDs. The USIM
shall not store two MSK IDs with the same Key Number part in the same record.
- If a record with the received Key Domain ID and Key Group part does not exist, the USIM uses an empty record
to include those values. The received MSK ID is stored as the 1st MSK ID and the associated TS is reset. The 2nd
MSK ID and the associated TS are set to 'FF FF'. The number of stored MSK IDs and corresponding TS shall be
set to '01'. In case there is no empty record available in EFMSK the USIM abandons the function and the status
word '9866' (Authentication error, no available memory space) is returned.
- In the case of a BM-SC solicited pull procedure (i.e. when the Key Number part of the MSK ID is set to 0x0),
EFMSK is not updated.
NOTE: In case no empty record is available the ME should run an MSK Deletion Mode procedure to free entries
in EFMSK before running an MSK Update Mode procedure that contains a new MSK key.
Then, the USIM stores the Time Stamp field (retrieved from the MIKEY message) in its corresponding field under
EFMUK.
The USIM stores internally the last successfully used MUK along with its MUK ID for further use. This MUK may be
used beyond its GBA validity (i.e. after the derivation of a new Ks_int_NAF resulting from a new bootstrap procedure)
to verify the integrity of a MIKEY message in order to detect a synchronization failure. This may occur if the last
derived Ks_int_NAF did not reach the BM-SC.
The MSK is not necessarily updated in the MIKEY message, since a MSK transport message can be sent e.g. to update
the Key Validity data or as part of a BM-SC solicited pull procedure. In such a case the USIM shall use the status word
'9000' to inform the ME that the MIKEY message validation using the last generated MUK has succeeded.
Finally, if the V-bit in the HDR field of the received MIKEY message is set then the USIM shall produce a MSK
Verification Message as described in TS 33.246 [43]. In this case the command response is the MIKEY verification
message.
3GPP
Release 15 274 3GPP TS 31.102 V15.21.0 (2018-0610)
Input:
- MIKEY message
Output:
- MIKEY message
or
- None
7.1.1.7 Void
7.1.1.8 MBMS security context (MTK Generation Mode)

The USIM receives the MIKEY message containing an MBMS MTK and a Salt key (if Salt key is available). First, the
USIM retrieves the MSK with the Key Domain ID and the MSK ID given by the Extension payload of the MIKEY
message (as described in TS 33.246 [43]).
If the needed MSK does not exist, this is considered as a MSK failure and the USIM abandons the function. The status
word '6A88' (Referenced data not found) is returned.
If the key validity data of the MSK indicates an invalidated MSK (i.e. SEQl is greater than SEQu) then the USIM
returns the status word '6985' (Conditions of use not satisfied) and abandons the function. SEQl and SEQu are defined
in TS 33.246 [43].
Otherwise, the USIM performs the MBMS Generation and Validation Function (MGV-F) as described in
TS 33.246 [43] using MSK.
If the USIM detects that the given MTK ID is invalid, this is considered as a SEQp freshness failure and the USIM
abandons the function. The status word '9865' (Key freshness failure) is returned.
If the integrity validation of the MIKEY message is unsuccessful, the USIM abandons the function and returns the
status word '9862' (Authentication error, incorrect MAC).
After successful MGV_F procedure the USIM stores the Time Stamp field (retrieved from the MIKEY message) as the
Time Stamp Counter (TS) associated with the involved MSK under EFMSK
The USIM also stores MTK ID (retrieved from the MIKEY message) as the SEQl associated with MSK.
Then, the USIM returns MTK and Salt key (if Salt key is available).
Input:
- MIKEY message
Output:
- MTK and Salt (if available).
7.1.1.9 MBMS security context (MSK Deletion Mode)

The USIM receives the Key Domain ID and the Key Group part of the MSK ID. The USIM shall identify in the EFMSK
the record containing MSK IDs having this Key Domain ID and Key Group part.
If no record is identified, the USIM abandons the function and returns the status word '6A88' (Referenced data not
found).
If a record is found, the USIM shall delete all corresponding MSKs and set to 'FF' the bytes of this record.
3GPP
Release 15 275 3GPP TS 31.102 V15.21.0 (2018-0610)
Input:
- Key Domain ID, MSK ID Key Group part
Output:
- None.
7.1.1.10 MBMS security context (MUK Deletion Mode)

The USIM shall identify in EFMUK the record containing the received MUK ID.
If no record is identified, the USIM abandons the function and returns the status word '6A88' (Referenced data not
found).
If a record is found, the USIM shall delete the corresponding MUK and set to 'FF' the bytes of this record. If a
corresponding Ks_int_NAF key is present (i.e. with the same NAF_ID), it shall be deleted and its corresponding record
in EFGBANL shall be set to 'FF'. In case the corresponding Ks key is present (i.e. with the same B-TID), it shall be deleted
and the content of EFGBABP shall be set to 'FF'.
Input:
MUK ID TLV
Output:
- None
7.1.1.11 Local Key Establishment security context (Key Derivation mode)

USIM operations in this security context are supported if service n°68 and service n°76 are "available".
The USIM receives the NAF_ID corresponding to the NAF Key Centre, the Terminal_ID, the Terminal_appli_ID, the
UICC_appli_ID, RANDx, the Counter Limit value and the MAC as described in TS 33.110 [47].
The USIM uses the NAF_ID to identify the Ks_int_NAF associated to the NAF Key Centre. If no valid Ks_int_NAF is
available, this is considered as a Key Establishment failure and the USIM abandons the function. The status word
'6A88' (Referenced data not found) is returned.
If the Ks_local key derivation is not authorized by the local UICC policy (e.g. Terminal_appli_ID/UICC_appli_ID
association not authorized or Terminal_ID value not authorized), the USIM abandons the function. The status word
'6985' (Conditions of use not satisfied) is returned.
Otherwise, the USIM retrieves the appropriate Ks_int_NAF, derives Ks_local as described in TS 33.110 [47]. The
USIM verifies the MAC value received from the Terminal as described in TS 33.110 [47]:
- If the verification is unsuccessful, the USIM abandons the function and returns the status word '9862'
(Authentication error, incorrect MAC).
- If the verification is successful, the USIM stores Ks_local and associated parameters Terminal_ID,
Terminal_appli_ID, UICC_appli_ID, RANDx and the Ks_local Counter Limit. The USIM returns the Local Key
Establishment Operation Response TLV (indicating a successful Key Derivation operation) and a response
MAC, which is derived as described in TS 33.110 [47].
The minimum number of Local keys that can be stored by the USIM shall be defined by the service provider at the pre-
issuance of the card.
In case the maximum number of Local Key was already reached or there is not enough available memory in the USIM,
the USIM shall overwrite a Local Key and its associated data in order to store the new one. To determine the Ks_local
to overwrite, the USIM shall construct a list of Ks_local identifiers by storing in the list first position the Ks_local
identifier of the last used or derived Ks_local and by shifting down the remaining list elements. The last Ks_local
identifier in this list corresponds to the Ks_local to overwrite when the USIM runs out of free memory or when the
3GPP
Release 15 276 3GPP TS 31.102 V15.21.0 (2018-0610)
maximum number of Ks_local keys is reached. If an existing Ks_local in use is overwritten, the application using
Ks_local shall not be affected.
Input:
- Local Key Establishment Mode (Key Derivation mode), Counter Limit, request MAC, Key Identifier (i.e.
NAF_ID, Terminal_ID, Terminal_appli_ID, UICC_appli_ID, RANDx)
Output:
- Key Derivation operation status, response MAC.
7.1.1.12 Local Key Establishment security context (Key Availability Check mode)
USIM operations in this security context are supported if service n°68 and service n°76 are "available".
The USIM receives a Ks_local identifier. The USIM checks if a corresponding valid Ks_local is available. If a valid
Ks_local key is available the Local Key Establishment Operation Response TLV (indicating a successful Key
Availability Check operation) is returned. In case no valid Ks_local key is available the command fails and the status
word '6A88' (Referenced data not found) is returned.
Input:
Local Key Establishment Mode (Key Availability Check mode), Key identifier (i.e. NAF_ID, Terminal_ID,
Terminal_appli_ID, UICC_appli_ID, RANDx).
Output:
- Key Availability Check Operation Status.
7.1.2 Command parameters and data

This command can be used with an EVEN or an ODD instruction (INS) code. The EVEN instruction code can be used
when the challenge data provided by the terminal is not TLV encapsulated data and the length of the challenge data
provided by the terminal is less than 256 bytes.
The ODD instruction code shall be used with the security context specified in table 2, when challenge and response data
is TLV encapsulated regardless of their length. Terminals and UICCs that do not support security context requiring
TLV format (e.g. MBMS), do not have to support AUTHENTICATE command with ODD instruction code.
EVEN INS code
Code Value
CLA As specified in TS 31.101 [11]
INS '88'
P1 '00'
P2 See table 1 below
Lc See below
Data See below
Le '00', or maximum length of data expected in
response
Parameter P2 specifies the authentication context as follows:
3GPP
Release 15 277 3GPP TS 31.102 V15.21.0 (2018-0610)
Table 1: Coding of the reference control P2
Coding Meaning
b8-b1
'1-------' Specific reference data (e.g. DF
specific/application dependant key)
'----- XXX' Authentication context:
000 GSM context
001 3G context
010 VGCS/VBS context
100 GBA context
All other codings are RFU.
ODD INS code
The authentication data and the authentication response data are encapsulated in BER-TLV objects structured using tag
'73' for BER-TLV structured data and tag '53' otherwise.
How this command can chain successive blocks of authentication data, or authentication
response data is described in TS 31 101 [11].
If P1 indicates "First block of authentication data" or "Next block of authentication data":
Input:
- Authentication data encapsulated in a BER-TLV data object.
Output:
- None.
Code Value
INS '89'
P1 As specified in TS 31.101 [11]
Lc Length of the subsequent data field
Data Authentication related data
Le Not present
If P1 indicates "First block of authentication response data" or "Next block of authentication response data":
Input:
- None.
Output:
- Authentication response data encapsulated in a BER-TLV data object.
Code Value
INS '89'
P1 As specified in TS 31.101 [11]
Lc Not present
Data Not present
Le Length of the response data
Parameter P1 is used to control the data exchange between the terminal and the UICC as defined in TS 31.101 [11].
Parameter P2 specifies the authentication context as follows:
3GPP
Release 15 278 3GPP TS 31.102 V15.21.0 (2018-0610)
Coding Meaning
b8-b1
'1-------' Specific reference data (e.g. DF specific/application dependant key)
'----- XXX' Authentication context:
101 MBMS context
110 Local Key Establishment mode
Command parameters/data:
7.1.2.1 GSM/3G security context
Byte(s) Description Length

1 Length of RAND (L1) 1
2 to (L1+1) RAND L1
(L1+2) Length of AUTN (L2) (see note) 1
(L1+3) to AUTN (see note) L2
(L1+L2+2)
Note: Parameter present if and only if in 3G security context.
The coding of AUTN is described in TS 33.102 [13]. The most significant bit of RAND is coded on bit 8 of byte 2. The
most significant bit of AUTN is coded on bit 8 of byte (L1+3).
Response parameters/data, case 1, 3G security context, command successful:

1 "Successful 3G authentication" tag = 'DB' 1
2 Length of RES (L3) 1
3 to (L3+2) RES L3
(L3+3) Length of CK (L4) 1
(L3+4) to CK L4
(L3+L4+3)
(L3+L4+4) Length of IK (L5) 1
(L3+L4+5) to IK L5
(L3+L4+L5+4)
(L3+L4+L5+5) Length of KC (= 8) (see note) 1
(L3+L4+L5+6 KC (see note) 8
to
(L3+L4+L5+13)
Note: Parameter present if and only if Service n°27 is "available".
The most significant bit of RES is coded on bit 8 of byte 3. The most significant bit of CK is coded on bit 8 of byte
(L3+4). The most significant bit of IK is coded on bit 8 of byte (L3+L4+5).
Response parameters/data, case 2, 3G security context, synchronisation failure:

1 "Synchronisation failure" tag = 'DC' 1
2 Length of AUTS (L1) 1
3 to (L1+2) AUTS L1
The coding of AUTS is described in TS 33.102 [13]. The most significant bit of AUTS is coded on bit 8 of byte 3.
Response parameters/data, case 3, GSM security context, command successful:
3GPP
Release 15 279 3GPP TS 31.102 V15.21.0 (2018-0610)

1 Length of SRES (= 4) 1
2 to 5 SRES 4
6 Length of KC (= 8) 1
7 to 14 KC 8
The most significant bit of SRES is coded on bit 8 of byte 2. The most significant bit of Kc is coded on bit 8 of byte 7.
7.1.2.2 VGCS/VBS security context

1 Length of Vservice_Id 1
2 to 5 Vservice_Id 4
6 Length of VK_Id 1
7 VK_Id 1
8 Length of VSTK_RAND (L1) 1
9 to L1+8 VSTK_RAND L1
Vservice_Id is coded in the same way as the octets 2-5 in the Descriptive group or broadcast call reference information
element as defined in TS 24.008 [9].
An Example for the coding of Vservice_Id can be found in Annex K.
The coding of VK_Id is as follows:
Coding of VK_Id
Coding Meaning
b8-b1
'00000001' Corresponds to the 1st group key
'00000010' Corresponds to the 2nd group key
The coding of VSTK_RAND is described in TS 43.020 [44]. The VSTK_RAND shall be inserted left-aligned into the
L1 bytes, with unused bits to the right set to zero.
Response parameters/data, VGCS/VBS security context, command successful:

1 "Successful VGCS/VBS operation" tag = 'DB' 1
2 Length of VSTK (16) 1
3 to 18 VSTK 16
7.1.2.3 GBA security context (Bootstrapping Mode)

1 “GBA Security Context Bootstrapping Mode” tag = ‘DD’ 1
2 Length of RAND (L1) 1
3 to (L1+2) RAND L1
(L1+3) Length of AUTN (L2) 1
(L1+4) to AUTN L2
(L1+L2+3)
Response parameters/data, GBA security context (Bootstrapping Mode), synchronisation failure:

1 "Synchronisation failure" tag = 'DC' 1
2 Length of AUTS (L1) 1
3 to (L1+2) AUTS L1
AUTS coded as for UMTS Security context.
3GPP
Release 15 280 3GPP TS 31.102 V15.21.0 (2018-0610)
Response parameters/data, GBA security context (Bootstrapping Mode), command successful:

1 "Successful GBA operation" tag = 'DB' 1
2 Length of RES (L) 1
3 to (L+2) RES L
RES coded as for UMTS Security context.
7.1.2.4 GBA security context (NAF Derivation Mode)

1 “GBA Security Context NAF Derivation Mode” tag = ‘DE’ 1
2 Length of NAF_ID (L1) 1
3 to (L1+2) NAF_ID L1
(L1+3) Length of IMPI (L2) 1
(L1+4) to IMPI L2
(L1+L2+3)
Response parameters/data, GBA security context (NAF Derivation Mode), command successful:

1 "Successful GBA operation" tag = 'DB' 1
2 Length of Ks_ext_NAF (L) 1
3 to (L+2) Ks_ext_NAF L
Coding of Ks_ext_NAF as described in TS 33.220 [42].
7.1.2.5 MBMS security context (All Modes)
Byte(s) Description Coding Length

1 MBMS Data Object tag (‘53’) As defined in TS 31.101 [11] for 1
BER-TLV data object
2 to 1+A bytes (A ≤ 4) MBMS Data Object length (L1) As defined in TS 31.101 [11] for A
BER-TLV data object
A+2 MBMS Security Context Mode See below 1
A+3 to (A+L1+1) MIKEY message or Key Domain ID || L1-1
MSK ID Key Group part or MUK ID TLV
Only the MIKEY message shall be transmitted in the MBMS security context mode '01' or '02'.
Only the Key Domain ID (coded on 3 bytes as described in TS 33.246 [43]) concatenated with the Key Group part of
the MSK ID (coded on two bytes as described in TS 33.246 [43] where the last transmitted byte represents the least
significant byte of the Key Group part) shall be transmitted in the MBMS security context mode '03'.
Only the MUK ID TLV shall be transmitted in the MBMS security context mode '04'. The MUK ID TLV, containing
the MUK Idr and MUK Idi only, shall be encoded as described in clause 4.2.81.
Parameter MBMS Security Context Mode specifies the MBMS mode in which MBMS security procedure is performed
as follows:
Coding of MBMS Security Context Mode
Coding Meaning
'01' MSK Update Mode
‘02' MTK Generation Mode
'03' MSK Deletion Mode
'04' MUK Deletion Mode
Response parameters/data, MBMS security context (MSK Update Mode), command successful:
3GPP
Release 15 281 3GPP TS 31.102 V15.21.0 (2018-0610)

1 MBMS operation response Data Object tag As defined in TS 31.101 [11] for 1
(‘53’) BER-TLV data object
2 to 1+A bytes (A ≤ 4) MBMS operation response Data Object length As defined in TS 31.101 [11] for A
(L) BER-TLV data object
A+2 "Successful MBMS operation" tag = 'DB' (see 1
note 1)
A+3 to (A+L+1) MIKEY message (see note 1) L-1
NOTE 1: Parameter present if a MIKEY verification message is returned. Otherwise, the USIM returns "53 01 DB"
Response parameters/data, MBMS security context (MTK Generation Mode), command successful:

2 to 1+A bytes (A ≤ 4) MBMS operation response Data Object length As defined in TS 31.101 [11] for A
(L) BER-TLV data object
A+2 "Successful MBMS operation" tag = 'DB' 1
A+3 to (A+L+1) MTK || Salt (if Salt key is available) L-1
Response parameters/data, MBMS security context (MSK and MUK Deletion Mode), command successful:

2 MBMS operation response Data Object length As defined in TS 31.101 [11] for 1
BER-TLV data object
3 "Successful MBMS operation" tag = 'DB' 1
The coding of parameters is described in TS 33.246 [43].
Note: The constructed TLV tag value 'AE' is used by OMA BCAST Smart Card Profile [49] for the encapsulation
of command and response parameters/data.
7.1.2.6 Local Key Establishment security context (All Modes)

The Local Key Establishment Control TLV is included in the command data to indicate the security context mode. The
Local Key Establishment Control TLV is also included in the response data to indicate the operation status.
Table 3: Coding of the Local Key Establishment Control TLV
Tag Value Length Value / Meaning

'80' Coded according to Local Key Establishment context:
ISO/IEC 8825-1 [35] '01': Key Derivation mode
'02': Key Availability Check mode
Operation Status:
'DB': Successful Operation
7.1.2.6.1 Local Key Establishment security context (Key Derivation mode)


1 Key Derivation Data Object tag (‘73’) As defined in TS 31.101 [11] for 1
BER-TLV data object
2 to A+1 bytes (A ≤ 4) Key Derivation Data Object length (L) As defined in TS 31.101 [11] for A
BER-TLV data object
A+2 to (A+L+1) Key Derivation Data Object L
3GPP
Release 15 282 3GPP TS 31.102 V15.21.0 (2018-0610)
- Key Derivation Data Object content: The TLVs defined in table 4 are included in the Key Derivation Data
Object.
Table 4: Coding of the Key Derivation Data Object

Local Key Establishment Control Coded as defined in M B
TLV section 7.1.2.6. The
value field shall be set
to '01'
Counter Limit tag '81' M 1
Length C M Note 1
Counter Limit Coded as defined in M C
TS 33.110 [47]
Request MAC tag '82' M 1
Length D M Note 1
Request MAC Coded as defined in M D (see Note 3)
TS 33.110 [47]
Key Identifier tag 'A0' M 1
Length E (see Note 2) M Note 1
NAF_ID tag '83' M 1
Length F M Note 1
NAF_ID Coded as defined in M F
TS 33.220 [42]
Terminal_ID tag '84' M 1
Length G M Note 1
Terminal_ID Coded as defined in M G
TS 33.110 [47]
Terminal_appli_ID tag '85' M 1
Length H M Note 1
Terminal_appli_ID Coded as defined in M H
TS 33.110 [47]
UICC_appli_ID tag '86' M 1
Length I M Note 1
UICC_appli_ID Coded as defined in M I
TS 33.110 [47]
RANDx tag '87' M 1
Length J M Note 1
RANDx Coded as defined in M J (see Note 4)
TS 33.110 [47]
Note 2: The Key Identifier TLV is a constructed TLV containing the following primitive
TLVs: NAF_ID, Terminal_ID, Terminal_appli_ID, UICC_appli_ID and RANDx. E
is the length of the constructed Key Identifier value.
Note 3: The most significant bit of the request MAC is coded on bit 8 of the first byte
following the MAC Length.
Note 4: The most significant bit of the RANDx is coded on bit 8 of the first byte following
the RANDx Length.
Response parameters/data, Local Key Establishment security context (Key Derivation mode), command successful:

1 Key Derivation Operation Response Data As defined in TS 31.101 [11] for 1
Object tag (‘73’) BER-TLV data object
2 to A1+1 bytes (A1 ≤ 4) Key Derivation Operation Response Data As defined in TS 31.101 [11] for A1
Object length (L1) BER-TLV data object
A1+2 to (A1+L1+1) Key Derivation Operation Response Data L1
Object
Key Derivation Operation Response Data Object content: The TLVs defined in table 5 are included in the Key
Derivation Operation Response Data Object.
3GPP
Release 15 283 3GPP TS 31.102 V15.21.0 (2018-0610)
Table 5: Coding of the Key Derivation Operation Response Data Object

Local Key Establishment Control Coded as defined in M B
TLV section 7.1.2.6. The
value field shall be
set to 'DB'
Response MAC tag '82' M 1
Length C M Note 1
Response MAC Coded as defined in M C (see Note 2)
TS 33.110 [47]
Note 2: The most significant bit of the response MAC is coded on bit 8 of the first byte
following the MAC length.
7.1.2.6.2 Local Key Establishment security context (Key Availability Check mode)

1 Key Availability Check Data Object tag As defined in TS 31.101 [11] for 1
2 to 1+A bytes (A ≤ 4) Key Availability Check Data Object As defined in TS 31.101 [11] for A
length (L) BER-TLV data object
A+2 to (A+L+1) Key Availability Check Data Object L
- Key Availability Check Data Object content: The TLVs defined in table 6 are included in the Key Availability
Check Data Object.
Table 6: Coding of the Key Availability Check Data Object

Local Key Establishment Coded as defined in M B
Control TLV section 7.1.2.6. The value
field shall be set to '02'
Key Identifier TLV Coded as defined in M C
section 7.1.2.6.1
Response parameters/data, Local Key Establishment security context (Key Availability Check mode), command
successful:

1 Key Availability Check Operation Response As defined in TS 31.101 [11] for 1
Data Object tag ('73') BER-TLV data object
2 to 1+A1 bytes (A1 ≤ 4) Key Availability Check Operation Response As defined in TS 31.101 [11] for A1
Data Object length (L1) BER-TLV data object
A1+2 to (A1+L1+1) Key Availability Check Operation Response L1
Data Object
- Key Availability Check Operation Response Data Object content: The TLV defined in table 7 is included in the
Key Availability Check Operation Response Data Object.
Table 7: Coding of the Key Availability Check Operation Response Data Object

Local Key Establishment Control TLV Coded as defined in M B
section 7.1.2.6. The
value field shall be
set to 'DB'
3GPP
Release 15 284 3GPP TS 31.102 V15.21.0 (2018-0610)
7.2 Void
7.3 Status Conditions Returned by the USIM

Status of the card after processing of the command is coded in the status bytes SW1 and SW2. This clause specifies the
coding of the status bytes in the following tables, in addition to the ones defined in TS 31.101 [11].
7.3.1 Security management

SW1 SW2 Error description
'98' '62' - Authentication error, incorrect MAC
'98' '64' - Authentication error, security context not supported
'98' '65' - Key freshness failure
'98' '66' - Authentication error, no memory space available
'98' '67' - Authentication error, no memory space available in EFMUK
3GPP
Release 15 285 3GPP TS 31.102 V15.21.0 (2018-0610)
7.3.2 Status Words of the Commands

The following table shows for each command the possible status conditions returned (marked by an asterisk *).
Commands and status words
Status Words
AUTHENTICATE
GET IDENTIYY
90 00 * *
91 XX * *
93 00
98 50
98 62 *
98 64 *
98 65 *
98 66 *
98 67 *
62 00 * *
62 81
62 82
62 83
62 F1 *
62 F3 *
63 CX
63 F1 *
64 00 * *
65 00 * *
65 81 * *
67 00 * *
67 XX – (see note) * *
68 00 * *
68 81 * *
68 82 * *
69 81
69 82 * *
69 83
69 84 *
69 85 * *
69 86
6A 80
6A 81 * *
6A 82
6A 83
6A 86 * *
6A 87
6A 88 * *
6B 00 * *
6E 00 * *
6F 00 * *
6F XX – (see note) * *
NOTE:Except SW2 = '00'.
3GPP
Release 15 286 3GPP TS 31.102 V15.21.0 (2018-0610)
7.4 Optional commands

The following command is optional for the USIM application:
- GET CHALLENGE command as defined in TS 31.101 [11].
- GET IDENTITY command as defined in clause 7.5
Note: OMA BCAST Smart Card Profile [49] defines a command using instruction code INS '1B'
7.5 GET IDENTITY

7.5.1 Command description
The function can be used in the following contexts:
- a SUCI context, to retrieve the SUCI when "SUCI calculation is to be performed by the USIM".
The function is related to a particular USIM and shall not be executable unless the USIM application has been selected
and activated, and the current directory is the USIM ADF or any subdirectory under this ADF and a successful PIN
verification procedure has been performed (see clause 5).
If GET IDENTITY command is not supported by the UICC, then the status word '6D00' (Instruction code not supported
or invalid) shall be returned.
7.5.1.1 SUCI context

SUCI context shall be supported if "SUCI calculation is to be performed by the USIM" (i.e. Service n°124 and Service
n°125 are "available").
The command returns the SUCI which is a privacy preserving identifier containing the concealed SUPI. The function is
used in 5GS in the specific cases described in 3GPP TS 33.501 [105] prior to mutual authentication between the UE and
the SN.
The SUCI returned is calculated as described in 3GPP TS 33.501 [105].
For the execution of the command, the following information shall be available in the USIM:
- Home network identifier (i.e. MCC and MNC) (see Note).
- Routing indicator (see Note).
- Home network public key (see Note).
- Home network public key identifier (see Note).
- Protection scheme identifier (see Note).
- SUPI.
NOTE: Provision and storage of the information in the USIM when "SUCI calculation is to be performed by the
USIM" (i.e. Service n°124 and Service n°125 are "available") is out of the scope of the specification.
The SUCI is designed for one-time use, however, the freshness and randomness of SUCI returned upon each call of the
command depends on the protection scheme configured. There is the special case where the protection scheme used is
null-scheme, in such case SUCI contains the non concealed SUPI.
If the home network public key is not provisioned in the USIM, the SUCI shall be calculated using the null-scheme
irrespective of the protection scheme stored in the USIM.
3GPP
Release 15 287 3GPP TS 31.102 V15.21.0 (2018-0610)
The returned SUCI consists of the concatenation of the following information as described in 3GPP TS 23.003
[25]33.501 [105]:
Editor’s Note: Coding of the following information in SUCI is not yet defined in 3GPP TS 24.501 [104]
Editor’s Note: Format is not defined yet in 3GPP TS 33.501.
- SUPI Type
- Home network identifier (i.e. MCC and MNC).
- Routing indicator.
- Protection scheme identifier.
- Home network public key identifier.
- Home network identifier.
Editor’s Note: 3GPP TS 33.501 does not specify which information is contained in Home Network identifier. Only
examples are provided in Section 6.12.
- Scheme output, resulting from the protection scheme profile, identified by the protection scheme identifier. The
protection scheme profile shall be one of those defined in Annex C of 3GPP TS 33.501 [105] or one of those
specified by the Home network.
If SUCI context command is supported and:
- Service n°124 is not "available" or:
- "SUCI calculation is to be performed by the ME” (i.e. Service n°124 is "available", and Service n°125 is not
"available")
the status word '6985' (Conditions of use not satisfied) shall be returned
Editor’s Note: It is FFS to specify the behavior in case other parameters (e.g. Home network public key identifier,
some necessary data is not provisioned) are not correctly configured
7.a5.2 Command parameters and data
Code Value
INS '78'
P1 '00'
P2 Identity context, see Table X below'
Lc Length of the subsequent data field or not present,
see below
Data See below
Le '00', or maximum length of data expected in
response
3GPP
Release 15 288 3GPP TS 31.102 V15.21.0 (2018-0610)
Parameter P2 specifies the identity context as follows:
b8 b7 b6 b5 b4 b3 b2 b1 Meaning
0 - - - - - - - Global reference data
1 - - - - - - - Special reference data
- X X X X X X X Identity Context (See below)
- 0 0 0 0 0 0 1 SUCI
7.5.2.1 SUCI context

Command parameters/data: None
Response parameters/data:

1 to Le SUCI TLV data object Le
Subscription Concealed Identifier TLV data object:

SUCI TLV data object tag 'A1' M 1
Length X M Note
SUCI value -- M X
- SUCI
For contents and coding of the SUCI data object TLV value see 3GPP TS 23.003 [25] and
3GPP TS 24.501 [104]TS 33.501 [105]. The most significant bit of SUCI is the most significant bit of the 1st
byte of this TLV value field. The least significant bit of SUCI is the least significant bit of the last byte of this
TLV value field.
Editor’s Note: Format of SUCI value is still to be completed in 3GPP TS 24.501 [104].not defined yet in 3GPP TS
33.501.
8 Void
3GPP
Release 15 289 3GPP TS 31.102 V15.21.0 (2018-0610)
Annex A (informative):
EF changes via Data Download or USAT applications
This annex defines if changing the content of an EF by the network (e.g. by sending an SMS), or by a USAT
Application, is advisable. Updating of certain EFs "over the air" such as EFACC could result in unpredictable behaviour
of the UE; these are marked "Caution" in the table below. Certain EFs are marked "No"; under no circumstances should
"over the air" changes of these EFs be considered.
3GPP
Release 15 290 3GPP TS 31.102 V15.21.0 (2018-0610)
File identification Description Change advised

'2F00' Application directory Caution
'2F05' Preferred languages Yes
'2F06' Access rule reference Caution
'2F08' UICC Maximum Power Consumption No
'2FE2' ICC identification No
'4F01' ProSe Monitoring Parameters Yes
'4F01' ACDC List Yes
'4F01' MCPTT MCS Service Table Yes
'4F01' V2X Service Table Yes
‘4F01’ 5GS 3GPP location information Caution (Note 1)
'4F02' V2X configuration data Yes
'4F02' ProSe Announcing Parameters Yes
'4F02' MCPTT MCS configuration data Yes
‘4F02’ 5GS non-3GPP location information Caution (Note 1)
'4F03' HPLMN ProSe Function Yes
‘4F03’ 5GS 3GPP Access NAS Security Context Caution
'4F04' ProSe Direct Communication Radio Parameters Yes
‘4F04’ 5GS non-3GPP Access NAS Security Context Caution
'4F05' ProSe Direct Discovery Monitoring Radio Parameters Yes
‘4F05’ 5G authentication keys No
'4F06' ProSe Direct Discovery Announcing Radio Parameters Yes
'4F06' UAC Access Identities Configuration Caution
'4F07' ProSe Policy Parameters Yes
'4F07' Subscriber Concealed Identifier Calculation Information Yes
'4F08' ProSe PLMN Parameters Yes
'4F08' Steering of UE in VPLMN Yes
'4F09' ProSe Group Counter No
'4F10' ProSe Service Table Caution
'4F11' ProSe UsageInformationReportingConfiguration Caution (Note 4)
'4F12' ProSe Group Member Discovery Parameters Yes
'4F13' ProSe Relay Parameters Yes
'4F14' ProSe Relay Discovery Parameters Yes
'4F20' Image data Yes
‘4F20’ GSM Ciphering key Kc No
'4FXX' Image Instance data Files Yes
'4FXX' ACDC OS Configuration Yes
'4F21' ICE graphics Yes
'4FXX' Unique identifier Yes
'4F22' Phone book synchronisation counter Yes
'4F23' Change counter Yes
'4F24' Previous unique identifier Yes
'4F30' Phone book reference file Yes
'4FXX' Capability configuration parameters 1 Yes
'4F30' SoLSA Access Indicator Caution
'4F31' SoLSA LSA List Caution
'4FXX' LSA Descriptor files Caution
‘4F52’ GPRS Ciphring key KcGPRS No
'4F63' CPBCCH Information No
'4F64’ Investigation Scan Caution
'4FXX' Additional number alpha string Yes
'4FXX' Additional number Yes
'4FXX' Second name entry Yes
'4FXX' Grouping information alpha string Yes
'4FXX' Phone book control Yes
'4FXX' E-mail addresses Yes
'4FXX' Index administration phone book Yes
'4FXX' Extension 1 Yes
'4FXX' Abbreviated dialling numbers Yes
'4FXX' Grouping file Yes
'4FXX' TV User Service Description Yes
'4F41' Pseudonym Caution
'4F42' User controlled PLMN selector for I-WLAN No
'4F43' Operator controlled PLMN selector for I-WLAN Caution
3GPP
Release 15 291 3GPP TS 31.102 V15.21.0 (2018-0610)

'4F44' User controlled WSID List No
'4F45' Operator controlled WSID List Caution
'4F46' WLAN Reauthentication Identity No
4F47' Home I-WLAN Specific Identifier List Yes
'4F47' Multimedia Messages List Yes
'4F48' I-WLAN Equivalent HPLMN Presentation Indication Yes
'4F48' Multimedia Messages Data File Yes
'4F49' I-WLAN HPLMN Priority Indication Yes
'4F4A' I-WLAN Last Registered PLMN Caution
'4F4B' HPLMN Direct Access Indicator Yes
'4F81' Allowed CSG lists Yes
'4F82' CSG Type Yes
'4F83' HNB name Yes
'4F84' Operator CSG lists Yes
'4F85' Operator CSG Type Yes
'4F86' Operator HNB name Yes
'6F05' Language indication Yes
‘6F06’ Access rule reference (under ADFUSIM and DFTELECOM) Caution
'6F07' IMSI Caution (Note 1)
'6F08' Ciphering and integrity keys No
'6F09' Ciphering and integrity keys for packet switched No
domain
'6F2C' De-personalization Control Keys Caution
'6F31' Higher Priority PLMN search period Caution
'6F32' Co-operative network list Caution
'6F37' ACM maximum value Yes
'6F38' USIM service table Caution
'6F39' Accumulated call meter Yes
'6F3B' Fixed dialling numbers Yes (Note 2)
'6F3C' Short messages Yes
'6F3E' Group identifier level 1 Yes
'6F3F' Group identifier level 2 Yes
'6F40' MSISDN storage Yes
'6F41' PUCT Yes
'6F42' SMS parameters Yes
'6F43' SMS status Yes
'6F45' CBMI Caution
'6F46' Service provider name Yes
'6F47' Short message status reports Yes
'6F48' CBMID Yes
'6F49' Service Dialling Numbers Yes (Note 2)
'6F4B' Extension 2 Yes
'6F4C' Extension 3 Yes
'6F4D' Barred dialling numbers Yes
'6F4E' Extension 5 Yes
'6F4F' Capability configuration parameters 2 Yes
'6F50' CBMIR Yes
'6F54' SetUp Menu Elements Yes
‘6F55’ Extension 4 Yes
'6F56' Enabled services table Caution
'6F57' Access point name control list Yes
'6F58' Comparison method information Yes
'6F5B' Initialisation value for Hyperframe number Caution
'6F5C' Maximum value of START Yes
'6F60' User controlled PLMN selector with Access Technology No
'6F61' Operator controlled PLMN selector with Access Caution
Technology
'6F62' HPLMN selector with Access Technology Caution
'6F73' Packet switched location information Caution (Note 1)
'6F78' Access control class Caution
'6F7B' Forbidden PLMNs Caution
'6F7E' Location information No (Note 1)
'6F80' Incoming call information Yes
3GPP
Release 15 292 3GPP TS 31.102 V15.21.0 (2018-0610)

'6F81' Outgoing call information Yes
'6F82' Incoming call timer Yes
'6F83' Outgoing call timer Yes
'6FAD' Administrative data Caution
'6FB1' Voice Group Call Service Yes
'6FB2' Voice Group Call Service Status Yes
'6FB3' Voice Broadcast Service Yes
'6FB4' Voice Broadcast Service Status Yes
'6FB5' Enhanced Multi Level Pre-emption and Priority Yes
'6FB6' Automatic Answer for eMLPP Service Yes
'6FB7' Emergency Call Codes Caution
'6FC3' Key for hidden phone book entries No
'6FC4' Network Parameters No
'6FC5' PLMN Network Name Yes
'6FC6' Operator Network List Yes
'6FC7' Mailbox Dialling Numbers Yes
'6FC8' Extension 6 Yes
'6FC9' Mailbox Identifier Caution
'6FCA' Message Waiting Indication Status Caution
'6FCB' Call Forwarding Indication Status Caution
'6FCC' Extension 7 Yes
'6FCD' Service Provider Display Information Yes
'6FCE' MMS Notification Yes
'6FCF' Extension 8 Yes
'6FD0' MMS Issuer Connectivity Parameters Yes
'6FD1' MMS User Preferences Yes
'6FD2' MMS User Connectivity Parameters Yes
'6FD3' Network's indication of alerting (NIA) Caution
'6FD4' Voice Group Call Service Ciphering Algorithm Yes
'6FD5' Voice Broadcast Service Ciphering Algorithm Yes
'6FD6' GBA Bootstrapping parameters Caution
'6FD7' MBMS Service Keys List Caution
'6FD8' MBMS User Key Caution
'6FD9' EHPLMN Caution
'6FDA' GBA NAF List Caution
'6FDB' EHPLMN Presentation Indication Caution
'6FDC' Last RPLMN Selection Indication Caution
'6FDD' NAF Key Centre Address Caution
'6FDE' Service Provider Name Icon Yes
'6FDF' PLMN Network Name Icon Yes
'6FE0' In Case of Emergency – Dialling Number Yes
'6FE1' In Case of Emergency – Free Format Yes
'6FE2' Network Connectivity Parameters for UICC IP Yes
connections
'6FE3' EPS location information Caution (Note 1)
'6FE4' EPS NAS Security Context Caution
'6FE5' Public Service Identity of the SM-SC Yes
'6FE6' USAT Facility Control Caution
'6FE7' UICC IARI Caution (Note 3)
'6FE8' Non Access Stratum Configuration Yes
'6FE9' UICC certificate Yes
'6FEA' Relay Node ID Yes
'6FEB' Max value of Secure Channel counter Caution
'6FEC' Public Warning System Yes
'6FED' FDN URI Yes (Note 2)
'6FEE' BDN URI Yes
'6FEF' SDN URI Yes (Note 2)
'6FF0' IMEI(SV) White List Yes
'6FF1' IMEI(SV) Pairing Status Caution
'6FF2' IMEI(SV) Pairing Devices Caution
'6FF3' Home ePDG Identifier Yes
'6FF4' ePDG Selection Information Yes
'6FF5' Emergency ePDG Identifier Yes
3GPP
Release 15 293 3GPP TS 31.102 V15.21.0 (2018-0610)

'6FF6' ePDG Selection Information for Emergency Services Yes
'6FF7' From Preferred Yes
'6FF8' IMSConfigData Caution (Note 5)
'6FF9' 3GPPPSDATAOFF Caution (Note 5)
'6FFA' 3GPPPSDATAOFFservicelist Caution (Note 5)
'6FFB' TV Configuration Yes
'6FFC' XCAP Configuration Data Yes
'6FFD' EARFCN List for MTC/NB-IOT UEs Yes

'6FFE' 5GS 3GPP location information Caution (Note 1)
'6FFF' 5GS non-3GPP location information Caution (Note 1)
'6F00' 5G authentication keys No
'6F01' 5GS 3GPP Access NAS Security Context Caution
'6F02' 5GS non-3GPP Access NAS Security Context Caution
'6F03' Subscriber Cconcealed Iidentifier Ccalculation Yes
Iinformation
'6F04' UAC Access Identities Configuration Caution
'6FFE' Steering of UE in VPLMN Yes
NOTE1: If EFIMSI is changed, the UICC should issue REFRESH as defined in 3GPP TS 31.111 [12] and
update EFLOCI, EFPSLOCI, EFEPSLOCI and EF5GSLOCI accordingly.
NOTE2: This file may contain eCALL related test and reconfiguration numbers or URIs.
NOTE3: If EFUICCIARI is changed, the UICC shall issue a REFRESH command as defined in TS 31.111.
The ME shall read the updated list of IARIs associated with active applications installed on the
UICC.
NOTE4: Updating EFProSe_UIRC Over-The-Air, especially adding more parameters to the report, may
cause a reduction of number of reports to be able to be stored in the UE.
3GPP
Release 15 294 3GPP TS 31.102 V15.21.0 (2018-0610)
Annex B (normative):
Image Coding Schemes
The following image coding schemes are applicable to rectangular raster images. Raster image points are assumed to be
of square shape. They are numbered sequentially from 1 onwards, starting at the upper left corner, proceeding line by
line downwards, each line in turn proceeding from left to right, and ending at the image's lower right corner.
The following example illustrates the numbering scheme for raster image points by showing how the corner points are
numbered, assuming an image length of x points and an image height of y points.
1 x
(x * (y-1) + 1) (x * y)
B.1 Basic Image Coding Scheme

This coding scheme applies to rectangular raster images made up of raster points that are either set or not set. This
coding scheme does not support any notion of colour. Image data are coded as follows:

1 image width = X 1
2 image height = Y 1
3 to K+2 image body K
Coding of image body:
- The status of each raster image point is coded in one bit, to indicate whether the point is set (status = 1) or not set
(status = 0).
Byte 1:
B8 b7 b6 b5 b4 b3 b2 b1
status of raster point 8

Byte 2:
B8 b7 b6 b5 b4 b3 b2 b1

etc.
Unused bits shall be set to 1.
3GPP
Release 15 295 3GPP TS 31.102 V15.21.0 (2018-0610)
B.2 Colour Image Coding Scheme

This coding scheme applies to coloured rectangular raster images. Raster image point colours are defined as references
into a colour look-up table (CLUT), which contains a subset of the red-green-blue colour space. The CLUT in turn is
located in the same transparent file as the image instance data themselves, at an offset defined within the image instance
data.
Image data are coded as follows:

1 Image width = X 1
2 Image height = Y 1
3 Bits per raster image point = B 1
4 Number of CLUT entries = C 1
5 to 6 Location of CLUT (Colour Look-up Table) 2
7 to K+6 Image body K
Bits per raster image point:
Contents:
- the number B of bits used to encode references into the CLUT, thus defining a raster image point's colour. B
shall have a value between 1 and 8.
Coding:
- binary.
Number of entries in CLUT:

Contents:
- the number C of entries in the CLUT which may be referenced from inside the image body. CLUT entries are
numbered from 0 to C-1. C shall have a value between 1 and 2**B.
Coding:
- binary. The value 0 shall be interpreted as 256.
Location of CLUT:
Contents:
- this item specifies where the CLUT for this image instance may be found. The CLUT is always located in the same
transparent file as the image instance data themselves, at an offset determined by these two bytes.
Coding:
- Byte 1: high byte of offset into Image Instance File.
- Byte 2: low byte of offset into Image Instance File.
Image body:
Coding:
- each raster image point uses B bits to reference one of the C CLUT entries for this image instance. The CLUT entry
being thus referenced yields the raster image point's colour. The image body is arrayed as for the Basic Colour Image
Coding Scheme, that is, starting with the highest bit of the first raster image point's colour information.
Byte 1:
B8 b7 b6 b5 b4 b3 b2 b1
... etc
... etc
... etc
... etc
... etc
Bit B-2 of raster point 1 CLUT reference
Bit B-1 of raster point 1 CLUT reference
Bit B (MSB) of raster point 1 CLUT reference
3GPP
Release 15 296 3GPP TS 31.102 V15.21.0 (2018-0610)
etc.
Unused bits shall be set to 1.
The CLUT (Colour Look-up Table) for an image instance with C colours is defined as follows:
Contents:
- C CLUT entries defining one colour each.
Coding:
- the C CLUT entries are arranged sequentially:
Byte(s) of CLUT CLUT Entry

1-3 entry 0
... ...
3*(C-1) +1 to 3*C Entry C-1
Each CLUT entry in turn comprises 3 bytes defining one colour in the red-green-blue colour space:
Byte(s) of CLUT entry Intensity of Colour

1 Red
2 Green
3 Blue
A value of 'FF' means maximum intensity, so the definition 'FF' '00' 00' stands for fully saturated red.
NOTE 1: Two or more image instances located in the same file can share a single CLUT.
NOTE 2: Most MEs capable of displaying colour images are likely to support at least a basic palette of red, green,
blue and white.
B.3 Colour Image Coding Scheme with Transparency

This coding scheme is identical to the Colour Image Coding Scheme as defined in appendix B.2, with the following
exception:
- Entry number C-1in the colour look-up table (CLUT), where C is the number of entries in the CLUT,
defines transparency. Raster image points which point to this entry are transparent, so that the underlying
colour in the display is shown.
The three colour-coding bytes of entry number C-1 in the CLUT are of no importance when referenced from images
using the '22' coding scheme.
NOTE: Two different descriptors in the EFIMG file with Image Coding Scheme '21' and '22' may point to the same
actual image instance. In that case, the descriptor with Image Coding Scheme '21' would describe an
image where a raster image point pointing to entry number C-1 in the CLUT would have the colour
described in that CLUT entry, while the descriptor with Image Coding Scheme '22' would describe an
image where a raster image point pointing to entry number C-1 in the CLUT is transparent.
3GPP
Release 15 297 3GPP TS 31.102 V15.21.0 (2018-0610)
Annex C (informative):
Structure of the Network parameters TLV objects
Structure of the GSM network parameter TLV object, 0<= m <=32
Tag Length Tag Length BCCH Tag Length BCCH BCCH BCCH
Currently Frequenc Neighbour Neighbour Neighbour ………… Neighbour
Camped y BCCH Frequency Frequency Frequency
Frequenc downlink Frequency 1 2 m
y
'A0' '80' '02' '81'
Structure of the FDD network parameter TLV object, 0 <= m <= 32
Tag Length Tag Length Intra Primary Primary Tag Lengt Inter Primary
Intra Frequency Scrambling Scrambling Inter h Frequency Scrambling
frequency downlink code 1 code m frequency downlink code n1
carrier carrier carrier carrier
'A1' '80' '81'
Structure of the TDD network parameter TLV object, 0 <= m <= 32
Tag Length Tag Length Intra Primary Primary Tag Lengt Inter Primary
Intra Frequency Scrambling Scrambling Inter h Frequency Scrambling
frequency downlink code 1 code m frequency downlink code n1
carrier carrier carrier carrier
'A2' '80' '81'
3GPP
Release 15 298 3GPP TS 31.102 V15.21.0 (2018-0610)
Annex D (informative):
Tags defined in 31.102
3GPP
Release 15 299 3GPP TS 31.102 V15.21.0 (2018-0610)
Tag Name of Data Element Usage

'43' Full name for network IEI PLMN Network Name (EFPNN)
'45' Short name for network IEI PLMN Network Name (EFPNN)
'53' MBMS Data Object AUTHENTICATE command parameter,
in MBMS security context
'53' MBMS operation response Data Object Response to AUTHENTICATE
The following tags are encapsulated within '53' command, in MBMS security context
'DB' successful MBMS operation tag
'73' Key Derivation Data Object AUTHENTICATE command parameter,
The following tags are encapsulated within '73' in Local Key Establishment security
'80' Local Key Establishment Control tag context
'81' Counter limit tag
'82' Request MAC tag
'83' NAF_ID tag
'84' Terminal_ID tag
'85' Terminal_appli_ID_tag
'86' UICC_appli_ID tag
'87' RANDx tag
'A0' Key Identifier tag
'73' Key Derivation Operation Response Object Response to AUTHENTICATE
The following tags are encapsulated within '73' command, in Local Key Establishment
'80' Local Key Establishment Control tag security context
'82' Request MAC tag
'73' Key Availability Check Data Object AUTHENTICATE command parameter

The following tags are encapsulated within '73' in Local Key Establishment security
'80' Local Key Establishment Control tag context
'A0' Key Identifier tag
'80' NAF_ID tag GBA NAF List (EFGBANL)
'80' NAF Key Centre address tag NAF Key Centre Address (EFNAFKCA)
'80' Icon Tag (Icon link is URI) Service Provider Name Icon (EFSPNI)
'80' Reauthentication Identity tag WLAN Reauthentication Identity (EFWRI)
'80' NAS signalling priority Tag Non Access Stratum Configuration
(EFNASCONFIG)
'80' MMS Implementation tag MMS User Preference (EFMMSUP)
Multimedia Messages List (EFMML)
'80' IARI TLV TAG UICC IARI (EFUICCIARI)
'80' Graphics CSG Type tag (Icon link is URI) CSG Type (EFCSGT)
'80' HNB Name tag Home NodeB Name (EFHNBN)
'80' PLMN Additional information tag PLMN Network Name (EFPNN)
'80' ICE Free Format Label tag In Case of Emergency – Free Format
(EFICE-FF)
'80' HPLMN ProSe Function tag Address of the HPLMN ProSe Function
(EFPROSEFUNC)
'80' ProSe Group Counter Counter for ProSe group (EFPROSE_GC)
'80' ProSe ServerAddress tag Server address for usage information
reports (EFPROSE_UIRC)
'80' Home ePDG Identifier TLV Home ePDG Identifier (EFePDGId)
'80' ePDG Selection Information TLV ePDG Selection Information
(EFePDGSelection)
'80' Emergency ePDG Identifier TLV Emergency ePDG Identifier (EFePDGIdEm)
'80' ePDG Selection Information for Emergency Services TLV ePDG Selection Information for
Emergency Services (EFePDGSelectionEm)
'80' XCAP_conn_params_policy TLV TAG EFXCAPConfigData
'80' IMS configuration data encoding EFIMSConfigData
'81' IMS configuration data EFIMSConfigData
'80' KAUSF tag EF5GAUTHKEYS
'80' Protection Scheme Identifier List data object tag Protection Scheme Identifier List
(EFSUCI_Calc_Info)
'81' B-TID tag GBA NAF List (EFGBANL)
'81' Icon Tag (Icon link is record number) Service Provider Name Icon (EFSPNI)
'81' Master key tag WLAN Reauthentication Identity (EFWRI)
'81' Time Stamp counter tag MBMS User Key (EFMUK)
'81' MMS User preference profile name tag MMS User Preference (EFMMSUP)
'81' Login Tag Network Connectivity Parameters for
USIM IP connections (EFNCP-IP)
'81' NMO I Behaviour Tag Non Access Stratum Configuration
3GPP
Release 15 300 3GPP TS 31.102 V15.21.0 (2018-0610)
(EFNASCONFIG)
3GPP
Release 15 301 3GPP TS 31.102 V15.21.0 (2018-0610)
'81' Graphics CSG Type tag (Icon link is record number) CSG Type (EFCSGT)
'81' ICE Free Format Content tag In Case of Emergency – Free Format
(EFICE-FF)
'81' MM File Identifier / SFI tag Multimedia Messages List (EFMML)
'81' ProSe CollectionPeriod tag Collection Period Parameter
(EFPROSE_UIRC)
'82' Counter tag WLAN Reauthentication Identity (EFWRI)
'82' MMS User Preference information tag MMS User Preference (EFMMSUP)
'82' Password Tag Network Connectivity Parameters for
'82' Attach with IMSI Tag Non Access Stratum Configuration
(EFNASCONFIG)
'82' MM Content Data Object Tag Multimedia Messages List (EFMML)
'82' ProSe ReportingWindow tag Reporting Window Parameter
(EFPROSE_UIRC)
'802' Home Network Public Key Identifier tag Home Network Public Key Identifier
(EFSUCI_Calc_Info)
'81' KSEAF tag EF5GAUTHKEYS
'83' Data Destination Address Range Tag Network Connectivity Parameters for
'83' Minimum Periodic Search Timer Tag Non Access Stratum Configuration
(EFNASCONFIG)
'83' MM Size tag Multimedia Messages List (EFMML)
'83' ProSe ReportGroupParameters tag Reporting Parameter for Goups
(EFPROSE_UIRC)
'813' Home Network Public Key Value tag Home Network Public Key Value
(EFSUCI_Calc_Info)
'84' Bearer Description Tag Network Connectivity Parameters for
'84' Extended access barring Tag Non Access Stratum Configuration
(EFNASCONFIG)
'84' MM Status tag Multimedia Messages List (EFMML)
'84' ProSe ReportTimeStampsFirstTransmissionAndReception tag Reporting Parameter (EFPROSE_UIRC)
'85' Timer T3245 Behaviour Tag Non Access Stratum Configuration
(EFNASCONFIG)
'85' MM Alpha Identifier tag Multimedia Messages List (EFMML)
'85' ProSe ReportDataTransmitted tag Reporting Parameter for transmitted
Data (EFPROSE_UIRC)
'86' Override NAS signalling low priority Tag Non Access Stratum Configuration
(EFNASCONFIG)
'86' ProSe ReportDataReceived tag Reporting Parameter for received Data
(EFPROSE_UIRC)
'87' Override Extended access barring Tag Non Access Stratum Configuration
(EFNASCONFIG)
'87' ProSe ReportTimeStampsOutOfCoverage tag Reporting Parameter (EFPROSE_UIRC)
'88' Fast First Higher Priority PLMN Search Tag Non Access Stratum Configuration
(EFNASCONFIG)
'88' ProSe ReportLocationInCoverage tag Reporting Parameter (EFPROSE_UIRC)
'89' Text CSG Type tag CSG Type (EFCSGT)
'89' E-UTRA Disabling Allowed for EMM cause #15 Tag Non Access Stratum Configuration
(EFNASCONFIG)
'89' ProSe ReportRadioParameters tag Reporting Parameter for Radio
Parameters (EFPROSE_UIRC)
'8A' SM RetryWaitTime Tag Non Access Stratum Configuration
(EFNASCONFIG)
'8B' SM RetryAtRATChange Tag Non Access Stratum Configuration
(EFNASCONFIG)
'8C' Default_DCN_ID Tag Non Access Stratum Configuration
(EFNASCONFIG)
'8D' Exception Data Reporting Allowed Tag Non Access Stratum Configuration
(EFNASCONFIG)
'A0' MUK ID tag MBMS User Key (EFMUK)
The following tags are encapsulated within 'A0'
'80' MUk IDr tag
'82' MUk IDi tag
'A0' EPS NAS security Context tag EPS NAS Security Context (EFEPSPSC)
3GPP
Release 15 302 3GPP TS 31.102 V15.21.0 (2018-0610)
'80' Key set identifier KSIASME Tag

'81' ASME key (KASME) Tag
'82' Uplink NAS count Tag
'83' Downlink NAS count Tag
'84' Identifiers of selected NAS integrity and encryption algorithms
Tag
3GPP
Release 15 303 3GPP TS 31.102 V15.21.0 (2018-0610)
'A0' CSG List TLV object tag Allowed CSG List (EFACSGL)
'80' PLMN tag
'81' CSG Information tag
'A0' GSM cell information Network Parameters (EFNETPAR)
The following tags are encapsulated within 'A0':
'80' GSM Camping Frequency Information data object
'81' GSM Neighbour Frequency Information data object
'A0' Operator CSG List TLV object Tag Operator CSG Lists (EFOCSGL)
'80' PLMN Tag
'81' CSG Information Tag
'82' CSG Display indicator tag
'A0' ProSe Discovery monitoring parameters ProSe Monitoring Parameters
The following tags are encapsulated within 'A0': (EFPROSE_MON)
'80' PLMN tag
'81' RFU
'82' Model tag
'A0' ProSe Discovery announcing parameters ProSe Announcing Parameters
The following tags are encapsulated within 'A0': (EFPROSE_ANN)
'80' PLMN tag
'81' Range tag
'82' Model tag
'A0' ProSe Policy parameters ProSe Policy Parameters
The following tags are encapsulated within 'A0': (EFPROSE_POLICY)
'80' ProSe Layer-2 Group ID tag
'81' ProSe UE ID tag
'82' ProSe Group IP multicast address tag
'83' Address type tag
'84' Ipv4 address as source tag
'85' Group related security tag
'86' Application Layer Group ID tag
'A0' ProSe PLMN Parameters tag ProSe PLMN Parameters (EFPROSE_PRMN)
'80'PLMN tag
'81' Direct communication authorisation tag
'A0' ProSe Direct Communication parameters tag ProSe Direct Communication Radio
The following tags are encapsulated within 'A0' Parameters (EF PROSE_RADIO_COM)
'80' Geographical Area – Polygon tag
'81' Radio parameters tag
'A0' ProSe Radio parameters tag ProSe Direct Discovery Monitoring
The following tags are encapsulated within 'A0' Radio Parameters (EFPROSE_RADIO_MON)
'A0' ProSe Radio parameters tag ProSe Direct Discovery Announcing
The following tags are encapsulated within 'A0' Radio Parameters (EFPROSE_RADIO_ANN)
'A0' ACDC OS tag ACDC List (EFACDC_LIST)
'A0' ACDC App Id tag ACDC OS Configuration
The following tags are encapsulated within 'A0' (EFACDC_OS_CONFIG)
'80' ACDC category tag
'81' OS App Id tag
'A0' Group member discovery parameters tag ProSe Group Member Discovery
The following tags are encapsulated within 'A0' Parameters (EFPROSE_GM_DISCOVERY)
'80' User Info ID tag
'81' Discovery Group ID tag
'82' Application Layer Group ID tag
'A0' ProSe Relay Parameters tag ProSe Relay Parameters (EFPROSE_RELAY)
'80' PLMN tag
'81' Relay type tag
'A0' Remote UE parameters tag ProSe Relay Discovery Parameters
The following tags are encapsulated within 'A0' (EFPROSE_RELAY_DISCOVERY)
'80' Relay Service Code tag
'81' User Info ID of Relay tag
'82' IP Versions tag
'83' Security content tag
3GPP
Release 15 304 3GPP TS 31.102 V15.21.0 (2018-0610)
'A0' TMGI List Tag TV Configuration (EFTVCONFIG)

'A0' USD Tag TV User Service Description (EFTVUSD)
'A0' XCAP_conn_params_policy part tag EFXCAPConfigData
'81' AccessForXCAP Tag
'82' Number of XCAP connection parameters policy part TLV’s Tag
'A1' XCAP connection parameters policy part tag
'A0' EARFCN List tag EARFCN list for MTC/NB-IOT UEs

The following tags are encapsulated within 'A0' (EFEARFCNList)
'80' EARFCN tag
'A0' 5GS 3GPP access NAS security Context tag or 5GS non-3GPP 5GS 3GPP Access NAS Security
access NAS security Context tag Context (EF5GS3GPPSNSC) or
The following tags are encapsulated within 'A0' 5GS non-3GPP Access NAS Security
'80' ngKSI Tag Context (EF5GSN3GPPSNSC)
'81' KAMF Tag
'82' Uplink NAS count Tag
'83' Downlink NAS count Tag
'84' Identifiers of selected NAS integrity and encryption algorithms
Tag
'A0' Protection Scheme Identifier List data object tagSUCI Calculation Protection Scheme Identifier List
Information TLV data object tag (EFSUCI_Calc_Info)SUCI Calculation
The following tags are encapsulated under 'A0': Information TLV data object
'80' Protection Scheme Identifier List data object tag (EFSUCI_Calc_Info)
'81' Home Network Public Key data object tag
'A1' XCAP connection parameters policy part tag EFXCAPConfigData
'81' Access Tag
'82' Application name Tag
'83' Provider ID Tag
'84' URI Tag
'85' XCAP Aithentication User Name Tag
'86' XCAP Authentication password Tag
'87'…XCAP Authentication type Tag
'88'…Address type Tag
'89'…Address Tag
'8A'…PDP Authentication type Tag
'8B'…PDP Authentication Name Tag
'8C'…PDP Authentication Secret Tag
'A1' FDD cell information Network Parameters (EFNETPAR)
'80' FDD Intra Frequency Information data object
'81' FDD Inter Frequency Information data object
'A1' Relay parameters tag ProSe Relay Discovery Parameters
The following tags are encapsulated within 'A0' (EFPROSE_RELAY_DISCOVERY)
'80' Relay Service Code tag
'81' PDN type tag
'82' APN tag
'83' ProSe Relay UE ID tag
'84' Security content tag
'A1' EARFCN List Tag TV Configuration (EFTVCONFIG)
'A1' SUCI TLV data object tag Response to GET IDENTITY
'A1' Home Network Public Key List data object Home Network Public Key List
The following tags are encapsulated under 'A1' (EFSUCI_Calc_Info)
'80' Home Network Public Key Identifier tag
'81' Home Network Public Key tag
'A2' TDD frequency information Network Parameters (EFNETPAR)
'80' TDD Intra Frequency Information data object
'81' TDD Inter Frequency Information data object
'A2' Routing Information TLV data object tag Routing Information
(EFSUCI_Calc_Info)
'A3' Service provider display information Service Provider Display Information
The following tags are encapsulated within 'A3': (EFSPDI)
'80' Service provider PLMN list
'A8' Indicator for type 1 EFs (amount of records equal to master EF) Phone Book Reference File (EFPBR)
3GPP
Release 15 305 3GPP TS 31.102 V15.21.0 (2018-0610)
'C0' EFADN data object

'C1' EFIAP data object
'C5' EFPBC data object
'C6' EFGRP data object
'C9' EFUID data object
'A9' Indicator for type 2 EFs (EFs linked via the index administration file) Phone Book Reference File (EFPBR)
'AA' Indicator for type 3 EFs (EFs addressed inside an object using a Phone Book Reference File (EFPBR)
record identifier as a pointer)
The following tags are encapsulated within 'AA':
'C2' EFEXT1 data object
'C7' EFAAS data object
'C8' EFGAS data object
'CB' EFCCP1 data object
'AB' MMS Connectivity Parameters: MMS Connectivity Parameters
The following are encapsulated under ‘AB’: (EFMMSICP / EFMMSUCP)
'80' MMS Implementation Tag
'81' MMS Relay/Server Tag
'82' Interface to core network and bearer Tag
'83' Gateway Tag
'84' Reserved for 3GPP2: MMS Authentication Mechanism Tag
'85' Reserved for 3GPP2: MMS Authentication User Name Tag
'DB' Successful 3G authentication Response to AUTHENTICATE
'DB' Successful VGCS/VBS operation authentication tag Response to AUTHENTICATE
'DB' Successful GBA operation tag Response to AUTHENTICATE
'DC' Synchronisation failure Response to AUTHENTICATE
'DD' Access Point Name APN Control List (EFACL)
'DD' GBA Security Context Bootstrapping Mode tag AUTHENTICATE command parameter,
in GBA security context
'DE' GBA Security Context NAF Derivation Mode tag Response to AUTHENTICATE
NOTE: the value 'FF' is an invalid tag value. For ASN.1 tag assignment rules see ISO/IEC 8825-1 [35]
3GPP
Release 15 306 3GPP TS 31.102 V15.21.0 (2018-0610)
Annex E (informative):
Suggested contents of the EFs at pre-personalization
If EFs have an unassigned value, it may not be clear from the main text what this value should be. This annex suggests
values in these cases.
3GPP
Release 15 307 3GPP TS 31.102 V15.21.0 (2018-0610)
File Identification Description Value
'2F00' Application directory Card issuer/operator dependent
'2F05' Preferred languages 'FF…FF'
'2F06' Access rule reference Card issuer/operator dependent
'2F08' UICC Maximum Power Consumption Card issuer/operator dependent
'2FE2' ICC identification operator dependent
'4F01' ProSe Monitoring Parameters Operator dependent
'4F01' ACDC List Operator dependent
'4F01' MCPTT MCS Service Table '0000'
'4F01' V2X Service Table Operator dependent
'4F01' 5GS 3GPP location information 'FF…FF'
'4F02' V2X configuration data Operator dependent
'4F02' ProSe Announcing Parameters Operator dependent
'4F02' MCPTT MCS configuration data Operator dependent
'4F02' 5GS non-3GPP location information 'FF…FF'
'4F03' HPLMN ProSe Function Operator dependent
'4F03' 5GS 3GPP Access NAS Security Context 'FF…FF'
'4F04' ProSe Direct Communication Radio Operator dependent

Parameters
'4F04' 5GS non-3GPP Access NAS Security Context 'FF…FF'
'4F05' ProSe Direct Discovery Monitoring Radio Operator dependent

Parameters
'4F05' 5G authentication keys Operator dependent
'4F06' ProSe Direct Discovery Announcing Radio Operator dependent

Parameters
'4F06' UAC Access Identities Configuration Operator dependent
'4F07' ProSe Policy Parameters Operator dependent
'4F07' Subscriber Concealed Identifier Calculation Operator dependent

Information
'4F08' Steering of UE in VPLMN Operator dependent
'4F08' ProSe PLMN Parameters Operator dependent
'4F09' ProSe Group Counter 'FF…FF'
'4F10' ProSe Service Table Operator dependent
'4F11' ProSe Operator dependent

UsageInformationReportingConfiguration
'4F12' ProSe Group Member Discovery Parameters Operator dependent
'4F13' ProSe Relay Parameters Operator dependent
'4F14' ProSe Relay Discovery Parameters Operator dependent
3GPP
Release 15 308 3GPP TS 31.102 V15.21.0 (2018-0610)
'4F20' Image data '00FF...FF'
‘4F20’ GSM Ciphering key Kc 'FF...FF07'
'4FXX' Image instance data files 'FF…FF'
'4FXX' ACDC OS Configuration Operator dependent
'4FXX' TV User Service Description Operator dependent
'4F21' ICE graphics 'FF…FF'
'4FXX' Unique identifier '0000'
'4F22' Phone book synchronisation counter '00000000'
'4F23' Change counter '0000'
'4F24' Previous unique identifier '0000'
'4F30' Phone book reference file Operator dependent
'4F30' SoLSA Access Indicator '00FF...FF'
'4F31' SoLSA LSA List 'FF...FF'
'4FXX' LSA Descriptor files 'FF…FF'
'4FXX' Capability configuration parameters 1 'FF…FF'
‘4F52’ GPRS Ciphring key KcGPRS 'FF...FF07'
'4F63' CPBCCH Information 'FF..FF'
'4F64' Investigation PLMN scan '00'
'4FXX' E-mail addresses 'FF…FF'
'4FXX' Additional number alpha string 'FF…FF'
'4FXX' Second name entry 'FF…FF'
'4FXX' Abbreviated dialling numbers 'FF...FF'
'4FXX' Grouping file '00…00'
'4FXX' Grouping information alpha string 'FF…FF'
'4FXX' Phone book control '0000'
'4FXX' Index administration phone book 'FF…FF'
'4FXX' Additional number 'FF…FF'
'4FXX' Extension 1 '00FF...FF'
'4F41' Pseudonym '0000FF…FF'
'4F42' User Controlled PLMN selector for I-WLAN 'FF…FF'
'4F43' Operator Controlled PLMN selector for I- Operator dependent

WLAN
'4F44' User Controlled WSID list '00FF…FF'
'4F45' Operator controlled WSID list Operator dependent
3GPP
Release 15 309 3GPP TS 31.102 V15.21.0 (2018-0610)
'4F46' WLAN Reauthentication Identity 'FF…FF'
'4F47' Home I-WLAN Specific Identifier List Operator dependent
'4F47' Multimedia Messages List 'FF…FF'
'4F48' I-WLAN Equivalent HPLMN Presentation Operator dependent

Indication
'4F48' Multimedia Messages Data File 'FF…FF'
'4F49' I-WLAN HPLMN Indication Operator dependent
'4F4A' I-WLAN Last Registered PLMN 'FFFFFF'
'4F4B' HPLMN Direct Access Indicator Operator dependent
'4F81' Allowed CSG lists Operator dependent
'4F82' CSG Type Operator dependent
'4F83' HNB name Operator dependent
'4F84' Operator CSG lists Operator dependent
'4F85' Operator CSG Type Operator dependent
'4F86' Operator HNB name Operator dependent
'6F05' Language indication 'FF…FF'
'6F06' Access rule reference (under ADFUSIM and Card issuer/operator dependent
DFTELECOM)
'6F07' IMSI Operator dependent
'6F08' Ciphering and integrity keys '07FF…FF'
'6F09' Ciphering and integrity keys for packet '07FF…FF'

switched domain
'6F2C' De-personalization control keys 'FF…FF'
'6F31' Higher Priority PLMN search period 'FF'
'6F32' Co-operative network list 'FF…FF'
'6F37' ACM maximum value '000000' (see note 1)
'6F38' USIM service table Operator dependent
'6F39' Accumulated call meter '000000'
'6F3B' Fixed dialling numbers 'FF...FF'
'6F3C' Short messages '00FF...FF'
'6F3E' Group identifier level 1 Operator dependent
'6F3F' Group identifier level 2 Operator dependent
'6F40' MSISDN storage 'FF...FF'
'6F41' PUCT 'FFFFFF0000'
'6F42' SMS parameters 'FF...FF'
'6F43' SMS status 'FF...FF'
3GPP
Release 15 310 3GPP TS 31.102 V15.21.0 (2018-0610)
'6F45' CBMI 'FF...FF'
'6F46' Service provider name Operator dependent
'6F47' Short message status reports '00FF…FF'
'6F48' CBMID 'FF...FF'
'6F49' Service Dialling Numbers 'FF...FF'
'6F4B' Extension 2 '00FF...FF'
'6F4C' Extension 3 '00FF...FF'
'6F4D' Barred Dialling Numbers 'FF...FF'
'6F4E' Extension 5 '00FF...FF'
'6F4F' Capability configuration parameters 2 'FF...FF'
'6F50' CBMIR 'FF...FF'
'6F54' SetUp Menu Elements Operator dependent
'6F55' Extension 4 '00FF...FF'
'6F56' Enabled services table Operator dependent
'6F57' Access point name control list '00FF…FF'
'6F58' Comparison method information 'FF…FF'
'6F5B' Initialisation value for Hyperframe number 'F0 00 00 F0 00 00'
'6F5C' Maximum value of START Operator dependent
'6F60' User controlled PLMN selector with Access 'FFFFFF0000..FFFFFF0000'

Technology
'6F61' Operator controlled PLMN selector with 'FFFFFF0000..FFFFFF0000'
Access Technology
'6F62' HPLMN selector with Access Technology 'FFFFFF0000..FFFFFF0000'
'6F73' Packet switched location information 'FFFFFFFF FFFFFF xxxxxx 0000 FF 01' (see
note 2)
'6F78' Access control class Operator dependent
'6F7B' Forbidden PLMNs 'FF...FF'
'6F7E Location information 'FFFFFFFF xxxxxx 0000 FF 01' (see note 2)
'6F80' Incoming call information 'FF…FF 000000 00 01FFFF'
'6F81' Outgoing call information 'FF…FF 000000 01FFFF'
'6F82' Incoming call timer '000000'
'6F83' Outgoing call timer '000000'
'6FAD' Administrative data Operator dependent
'6FB1' Voice Group Call Service Operator dependent
'6FB2' Voice Group Call Service Status Operator dependent
'6FB3' Voice Broadcast Service Operator dependent
3GPP
Release 15 311 3GPP TS 31.102 V15.21.0 (2018-0610)
'6FB4' Voice Broadcast Service Status Operator dependent
'6FB5' EMLPP Operator dependent
'6FB6' AaeM '00'
'6FB7' Emergency call codes Operator dependent
'6FC3' Key for hidden phone book entries 'FF…FF'
'6FC4' Network Parameters 'FF…FF'
'6FC5' PLMN Network Name Operator dependent
'6FC6' Operator Network List Operator dependent
'6FC7' Mailbox Dialling Numbers Operator dependent
'6FC8' Extension 6 '00 FF...FF'
'6FC9' Mailbox Identifier Operator dependent
'6FCA' Message Waiting Indication Status '00 00 00 00 00'
'6FCB' Call Forwarding Indication Status 'xx 00 FF...FF'
'6FCC' Extension 7 '00 FF...FF'
'6FCD' Service Provider Display Information
'6FCE' MMS Notification '00 00 00 FF…FF'
'6FCF' Extension 8 '00FF...FF'
'6FD0' MMS Issuer Connectivity Parameters 'FF…FF'
'6FD1' MMS User Preferences 'FF…FF'
'6FD2' MMS User Connectivity Parameters 'FF…FF'
'6FD3' Network's Indication of Alerting (NIA) 'FF...FF'

'6FD4' Voice Group Call Service Ciphering Algorithm '00…00'
'6FD5' Voice Broadcast Service Ciphering Algorithm '00…00'
'6FD6' GBA Bootstrapping parameters 'FF…FF'
'6FD7' MBMS Service Keys List 'FF…FF'
'6FD8' MBMS User Key 'FF…FF'
'6FD9' EHPLMN 'FF…FF' or xxxxxx (see Note 2)
'6FDA' GBA NAF List 'FF…FF'
'6FDB' EHPLMN Presentation Indication '00'
'6FDC' Last RPLMN Selection Indication '00'
'6FDD' NAF Key Centre Address 'FF…FF'
'6FDE' Service Provider Name Icon '00 FF…FF'
'6FDF' PLMN Network Name Icon '00 FF…FF'
'6FE0' In Case of Emergency – Dialling Number Operator dependent
'6FE1' In Case of Emergency – Free Format Operator dependent
'6FE2' Network Connectivity Parameters for UICC IP Operator dependent
connections
'6FE3' EPS location information 'FFFFFFFFFFFFFFFFFFFFFFFF xxxxxx0000
01' (see note 2)
'6FE4' EPS NAS Security Context 'FF…FF'
'6FE5' Public Service Identity of the SM-SC Operator dependent
'6FE6' USAT Facility Control '80 1E 60 C0 1E 90 00 80 04 00 00 00
00 00 00 00 00 F0 00 00 00 00 40 00
00 00 00 00 00 80'
'6FE7' UICC IARI Operator dependent
'6FE8' Non Access Stratum Configuration Operator dependent
3GPP
Release 15 312 3GPP TS 31.102 V15.21.0 (2018-0610)
'6FE9' UICC certificate Card Issuer / Operator dependent

'6FEA' Relay Node ID Operator dependent
'6FEB' Max value of Secure Channel counter FF..FF
'6FEC' Public Warning System Operator dependent
'6FED' FDN URI 'FF…FF'
'6FEE' BDN URI 'FF…FF'
'6FEF' SDN URI 'FF…FF'
‘6FF0’ IMEI(SV) White List Operator dependent (at least 1 range of
IMEI(SV) values)
‘6FF1’ IMEI(SV) Pairing Status 'FF…FF'
‘6FF2’ IMEI(SV) Pairing Devices 'FF…FF'
'6FF3' Home ePDG Identifier 'FF…FF'
'6FF4' ePDG Selection Information 'FF…FF'
'6FF5' Emergency ePDG Identifier 'FF…FF'
'6FF6' ePDG Selection Information for Emergency 'FF…FF'
Services
'6FF7' From Preferred '00'
'6FF8’ IMSConfigData Operator dependent
'6FF9' 3GPPPSDATAOFF Operator dependent
'6FFA' 3GPPPSDATAOFFservicelist Operator dependent
'6FFB' TV Configuration Operator dependent
'6FFC’ XCAP Configuration Data Operator dependent
'6FFDE' EARFCN list for MTC/NB-IOT UEs Operator dependent
'6F01' 5G authentication keys 'FF…FF'
'6F02' 5GS 3GPP Access NAS Security Context 'FF…FF'
'6F03' 5GS non-3GPP Access NAS Security Context 'FF…FF'
'6F04’ Subscriber Concealed Identifier Calculation Operator dependent
InformationSUCI Calculation Information
'6F04' UAC Access Identities Configuration Operator dependent
'6F05' Steering of UE in VPLMN Yes
NOTE 1: The value '000000' means that ACMmax is not valid, i.e. there is no restriction on the ACM. When
assigning a value to ACMmax, care should be taken not to use values too close to the maximum possible
value 'FFFFFF', because the INCREASE command does not update EFACM if the units to be added would
exceed 'FFFFFF'. This could affect the call termination procedure of the Advice of Charge function.
NOTE 2: xxxxxx stands for any valid MCC and MNC, coded according to TS 24.008 [9].
3GPP
Release 15 313 3GPP TS 31.102 V15.21.0 (2018-0610)
Annex F (informative):
Examples of coding of LSA Descriptor files for SoLSA
The length of all the records is determined by the LSA descriptor containing the largest number of bytes. Combinations
containing different numbers of LSa IDs, LAC+ CI and CI or LAC can therefore be done. Various examples are show.
Due to the OTA management of the records it is recommended that the record length is maximum 100 bytes in order to
leave room for command descriptor and signature information in the SMS.
This first example contains two LSAs, one described by two LSa IDs and another described by three Cell IDs, giving a
record length of 8 bytes.
1st record: LSA descriptor LSA ID (3 bytes) LSA ID (3 bytes) Identifier (1 byte)
type = LSA ID
and number = 2
(1 byte)
2nd record: LSA descriptor CI (2 bytes) CI (2 bytes) CI (2 bytes) Identifier (1 byte)

type = CI and
number = 3
(1 byte)
The second example contains two LSAs, one described by one LSA ID and one described by two Cell Ids, giving a
record length of 6 bytes.
1st record: LSA descriptor LSA ID (3 bytes) 'FF' Identifier (1 byte)

type = LSA ID
and number = 1
(1 byte)
2nd record: LSA descriptor CI (2 bytes) CI (2 bytes) Identifier (1 byte)

type = CI and
number = 2
(1 byte)
3GPP
Release 15 314 3GPP TS 31.102 V15.21.0 (2018-0610)
Annex G (informative):
Phonebook Example
This example phonebook has more than 254 entries. Additional number (3 additional numbers) information, second
name and e-mail information can be added to each ADN entry. In addition each entry has a 2 byte Unique ID (UID)
attached to it. The phonebook also contains three files that are shared EFEXT1, EFAAS and EFGAS. These files are addressed
from inside a file. EFEXT1 is addressed via EFADN, EFADN1, EFAAS is addressed via EFANRA, EFANRA1, EFANRB, EFANRB1,
EFANRC, EFANRC1 and EFGAS is addressed via EFGRP, EFGRP1. The phonebook supports two levels of grouping and hidden
entries in EFPBC.
Two records are needed in the phonebook reference file PBR '4F30' for supporting more than 254 entries. The content
of the phonebook reference file PBR '4F30' records is as shown in table G.2. The structure of the DF PHONEBOOK is shown
in table G.1.
The content of phonebook entries in the range from 1-508 is described in the tables G.3 and G.4.
Table G.1: Structure of EFs inside DFPHONEBOOK
DFPHONEBOOK
'5F3A'
Common Files
EFPBR EFEXT1 EFAAS EFGAS

'4F30' '4F4A' '4F4B' '4F4C'
EFPSC EFCC EFPUID

'4F22' '4F23' '4F24'
PhoneBook Set1
EFADN EFPBC EFANRA EFANRB

'4F3A' '4F09' '4F11' '4F13'
EFPURI EFEMAIL EFSNE EFUID EFGRP EFANRC

'4F54' '4F50' '4F19' '4F21' '4F26' '4F15'
PhoneBook Set2
EFADN1 EFPBC1 EFANRA1 EFANRB1

'4F3B' '4F0A' '4F12' '4F14'
EFPURI1 EFEMAIL1 EFSNE1 EFUID1 EFGRP1 EFANRC1

'4F55' '4F51' '4F1A' '4F20' '4F25' '4F16'
3GPP
Release 15 315 3GPP TS 31.102 V15.21.0 (2018-0610)
Table G.2: Contents of EF PBR
Rec 1 Tag'A8' L='2D' (for Phonebook Set1)
Tag'C0' L='03' '4F3A' '01' Tag'C5' L='03' '4F09' '02' Tag'C6' L='03' '4F26' '03'
Tag'C4' L='03' '4F11' '04' Tag'C4' L='03' '4F13' '05' Tag'C4' L='03' '4F15' '06'
Tag'C3' L='03' '4F19' '07' Tag'C9' L='03' '4F21' '12' Tag'CA' L='03' '4F50' '09'
Tag'CC' L='03' '4F54' '16'
Tag'AA' L='0F'
Tag'C2' L='03' '4F4A' '08' Tag'C7' L='03' '4F4B' '14' Tag'C8' L='03' '4F4C' '15'
Rec 2 Tag'A8' L='2D' (for Phonebook Set 2)
Tag'C0' L='03' '4F3B' '0A' Tag'C5' L='03' '4F0A' '0B' Tag'C6' L='03' '4F25' '0C'
Tag'C4' L='03' '4F12' '0D Tag'C4' L='03' '4F14' '0E' Tag'C4' L='03' '4F16' '0F'
Tag'C3' L='03' '4F1A' '10' Tag'C9' L='03' '4F20' '13' Tag'CA' L='03' '4F51' '11'
Tag'CC' L='03' '4F55' '17'
Tag'AA' L='0F'
Tag'C2' L='03' '4F4A' '08' Tag'C7' L='03' '4F4B' '14' Tag'C8' L='03' ‘4F4C '15'
Table G.3: Structure of the 254 first entries in the phonebook

Phone ADN PBC GRP ANRA ANRB ANRC SNE UID EXT1 AAS GAS EMAIL PURI
book '4F3A' '4F09' '4F26' '4F11' '4F13' '4F15' '4F19' '4F21' '4F4A' '4F4B' '4F4C' '4F50' '4F54'
entry SFI '01' SFI '02' SFI '03' SFI '04' SFI '05' SFI '06' SFI '07' SFI '12' SFI '08' SFI '14' SFI '15' SFI '09' SFI '16'
#1 ADN EXT1 Hidden Rec n°1 ANRA ANRB ANRC Second UID Rec '02' Record Record email SIP
Content Ident. (AID rec Rec n°3 Rec n°1 Rec n°1 Rec n°1 Name numbers no.'s as address URI/TE
Bytes (Byte N° 3) '00' Alpha as defined L URI
(1- X+14): String defined in in GRP
(X+13)) Rec '02' the ANRs
#2 ADN EXT1 Not Rec n°2 ANRA ANRB ANRC Second UID Rec '2A' Record Record email SIP
Content Ident. Hidden Rec n°1 Rec n°2 Rec n°2 Rec n°2 Name numbers no.'s as address URI/TE
Bytes (Byte Rec n°3 Alpha as defined L URI
(1- X+14): String defined in in GRP
(X+13)) Rec '2A' the
ANRs
#3
:
:
:
# 254
3GPP
Release 15 316 3GPP TS 31.102 V15.21.0 (2018-0610)
Table G.4: Structure of phone book entries 255 to 508 (Rec 1-254)
Phone ADN1 PBC1 GRP1 ANRA1 ANRB1 ANRC1 SNE1 UID1 EXT1 AAS GAS EMAIL1 PURI1
book '4F3B' '4F0A' '4F25' '4F12' '4F14' '4F16' '4F1A' '4F20' '4F4A' '4F4B' '4F4C' '4F51' '4F55'
entry SFI '0A' SFI '0B' SFI '0C' SFI '0D' SFI '0E' SFI '0F' SFI '10' SFI '13' SFI '08' SFI '14' SFI '15' SFI '11' SFI '17'
#255 ADN EXT1 Hidden Rec n°1 ANRA1 ANRB1 ANRC1 Second UID Rec '03' Record Record email SIP
Content Ident. (AID Rec n°3 Rec n°1 Rec n°1 Rec n°1 Name numbers no.'s as address URI/TE
Bytes (Byte Rec n° '00' Alpha as defined L URI
(1- X+14): 3) String defined in in
(X+13)) Rec '03' the ANRs GRP1
#256 ADN EXT1 Not Rec n°2 ANRA1 ANRB1 ANRC1 Second UID Rec '2B' Record Record email SIP
Content Ident. Hidden Rec n°1 Rec n°2 Rec n°2 Rec n°2 Name numbers no.'s as address URI/TE
Bytes (Byte Rec n°3 Alpha as defined L URI
(1- X+14): String defined in in
(X+13)) Rec '2B' the ANRs GRP1
#257
:
:
:
#508
3GPP
Release 15 317 3GPP TS 31.102 V15.21.0 (2018-0610)
Figure G.1: Structure and Relations of the Example Phone Book
3GPP
Release 15 318 3GPP TS 31.102 V15.21.0 (2018-0610)
Annex H (normative):
List of SFI Values
This annex lists SFI values assigned in the present document.
H.1 List of SFI Values at the USIM ADF Level

File Identification SFI Description
'6FB7' '01' Emergency call codes
'6F05' '02' Language indication
'6FAD' '03' Administrative data
'6F38' '04' USIM service table
'6F56' '05' Enabled services table
'6F78' '06' Access control class
'6F07' '07' IMSI
'6F08' '08' Ciphering and integrity keys
'6F09' '09' Ciphering and integrity keys for packet switched domain
'6F60' '0A' User PLMN selector
'6F7E '0B' Location information
'6F73' '0C' Packet switched location information
'6F7B' '0D' Forbidden PLMNs
'6F48' '0E' CBMID
'6F5B' '0F' Hyperframe number
'6F5C' '10' Maximum value of hyperframe number
'6F61' '11' Operator PLMN selector
'6F31' '12' Higher Priority PLMN search period
'6F62' '13' Preferred HPLMN access technology
'6F80' '14' Incoming call information
'6F81' '15' Outgoing call information
'6F4F' '16' Capability configuration parameters 2
'6F06' '17' Access Rule Reference
'6FC5' '19' PLMN Network Name
'6FC6' '1A' Operator Network List
'6FCD' '1B' Service Provider Display Information
‘6F39’ ‘1C’ Accumulated Call Meter (see note)
'6FD9' '1D' Equivalent HPLMN
'6FE3' '1E' EPS location information
'6FE4' '18' EPS NAS Security Context
NOTE: When used the value ‘1C’ shall be used as SFI for EFACM, for compatibility reasons the terminal shall accept
other values.
H.2 List of SFI Values at the DF GSM-ACCESS Level

'4F20' '01' GSM Ciphering Key Kc
'4F52' '02' GPRS Ciphering Key KcGPRS
All other SFI values are reserved for future use.
3GPP
Release 15 319 3GPP TS 31.102 V15.21.0 (2018-0610)
H.3 List of SFI Values at the DF WLAN Level

'4F41' '01' Pseudonym
'4F42' '02' User controlled PLMN for WLAN
'4F43' '03' Operator controlled PLMN for WLAN
'4F44' '04' User controlled WSID list
'4F45' '05' Operator controlled WSID list
'4F46' '06' WLAN Reauthentication Identity
'4F47' '07' Home I-WLAN Specific Identifier List
'4F48' '08' I-WLAN Equivalent HPLMN Presentation Indication
'4F49' '09' I-WLAN HPLMN Priority Indication
'4F4A' '0A' I-WLAN Last Registered PLMN
'4F4B' '0B' HPLMN Direct Access Indicator
H.4 List of SFI Values at the DF HNB Level

'4F81' '01' Allowed CSG lists
'4F82' '02' CSG Type
'4F83' '03' HNB name
'4F84' '04' Operator CSG lists
'4F85' '05' Operator CSG Type
'4F86' '06' Operator HNB name
H.5 List of SFI Values at the DF ProSe Level

'4F01' '01' ProSe Monitoring Parameters
'4F02' '02' ProSe Announcing Parameters
'4F03' '03' HPLMN ProSe Function
'4F04' '04' ProSe Direct Communication Radio Parameters
'4F05' '05' ProSe Direct Discovery Monitoring Radio Parameters
'4F06' '06' ProSe Direct Discovery Announcing Radio Parameters
'4F07' '07' ProSe Policy Parameters
'4F08' '08' ProSe PLMN Parameters
'4F09' '09' ProSe Group Counter
'4F10' '10' ProSe Service Table
'4F11' '11' ProSe UsageInformationReportingConfiguration
'4F12' '12' ProSe Group Member Discovery Parameters
'4F13' '13' ProSe Relay Parameters
'4F14' '14' ProSe Relay Discovery Parameters
H.6 List of SFI Values at the DF ACDC Level

'4F01' '01' ACDC List
Other SFI values can be allocated to various EFACDC_OS_CONFIG: these are listed inside EFACDC_LIST.
3GPP
Release 15 320 3GPP TS 31.102 V15.21.0 (2018-0610)
H.7 List of SFI Values at the DF MCPTT MCS Level

'4F01' '01' MCPTT MCS Service Table
'4F02' '02' MCPTT MCS configuration data
NOTE: The values '03', '04' and '05' were used in earlier versions of the specification and should not be
reallocated.
H.8 List of SFI Values at the DF V2X Level

'4F01' '01' V2X Service Table
'4F02' '02' V2X configuration data
NOTE: The values '03', '04' and '05' were used in earlier versions of the specification and should not be
reallocated.
H.9 List of SFI Values at the DF 5GS Level

'4F01' '01' 5GS 3GPP location information (Note)
'4F02' '02' 5GS non-3GPP location information (Note)
'4F03' '03' 5GS 3GPP Access NAS Security Context
'4F04' '04' 5GS non-3GPP Access NAS Security Context
'4F05' '05' 5G authentication keys
'4F06' '06' UAC Access Identities Configuration
'4F07' '07' Subscriber Concealed Identifier Calculation Information
'4F08' '08' Steering of UE in VPLMN
NOTE: If EFIMSI is changed, the UICC should issue REFRESH as defined in 3GPP TS 31.111 [12]
and update EF5GS3GPPLOCI and EF5GSN3GPPLOCI accordingly.
H.10 List of SFI Values at the DF 5GS Level

'4F01' '01' 5GS 3GPP location information (Note)
'4F02' '02' 5GS non-3GPP location information (Note)
'4F03' '03' 5GS 3GPP Access NAS Security Context
'4F04' '04' 5GS non-3GPP Access NAS Security Context
'4F05' '05' 5G authentication keys
'4F06' '06' UAC Access Identities Configuration
'4F07' '07' Subscriber Concealed Identifier Calculation Information
'4F08' '08' Steering of UE in VPLMN
NOTE: If EFIMSI is changed, the UICC should issue REFRESH as defined in 3GPP TS 31.111 [12]
and update EF5GS3GPPLOCI and EF5GSN3GPPLOCI accordingly.
3GPP
Release 15 321 3GPP TS 31.102 V15.21.0 (2018-0610)
Annex I (informative):
USIM Application Session Activation/Termination
The purpose of this annex is to illustrate the different Application Session procedures.
Figure I.1 USIM Application Session Activation procedure
Figure I.2 USIM Application Session Termination procedure
3GPP
Release 15 322 3GPP TS 31.102 V15.21.0 (2018-0610)
Annex J (informative):
Example of MMS coding
This annex gives an example for the coding of MMS User Preferences, while the MMS User Information Preference
parameters are coded according to the WAP implementation of MMS.
J.1 Coding example for MMS User Preferences

0x80 MMS Implementation Tag
0x01 (Length = "1")
0x01 (MMS implementation information = "(WAP")
0x81 MMS User Preference Profile Name Tag
0x0E (Length = "14")
43 68 72 69 73 74 6D 61 73 20 43 61 72 64
(profile name = "Christmas Card"; 14 characters, 14 Bytes)
0x82 MMS User Information Preference Information Tag
0x19 (Length = "25")
0x14 0x80 (visibility: = "hide"; 2 Bytes)
0x06 0x80 (delivery report: = "yes"; 2 Bytes)
0x10 0x80 (read-reply: = "yes"; 2 Bytes)
0x0F 0x81 (priority: = "normal"; 2 Bytes)
0x07 0x07 0x80 0x05 0x11 0x22 0x33 0x44 0x55

(Delivery-Time-Tag, Value-Length, Absolute-Token-Tag, Date-Value-Length, Date-Value; 9 Bytes)
0x08 0x06 0x81 0x04 0x55 0x22 0x33 0x44

(Expiry Tag, Value-Length, Relative-Token-Tag, Delta-Second-Value-Length, Delta-Second-Value; 8
Bytes)
J.2 Coding Example for MMS Issuer/User Connectivity

Parameters
0xAB MMS Connectivity Parameters Tag
0x81 0x88 (Length = "136") (Length bytes greater than 127 are coded onto 2 bytes according to ISO/IEC 8825-1 [35])
0x80 MMS Implementation Tag
0x01 (Length = "1")
0x01 (MMS implementation information = "WAP"; 1 Byte)
0x81 MMS Relay/Server Tag
0x17 (Length = "23")
3GPP
Release 15 323 3GPP TS 31.102 V15.21.0 (2018-0610)
0x68 0x74 0x74 0x70 0x3A 0x2F 0x2F 0x6D 0x6D 0x73 0x2D 0x6F 0x70 0x65 0x72 0x61 0x74
0x6F 0x72 0x2E 0x63 0x6F 0x6D
(MMS Relay/Server information = "http://mms-operator.com"; 23 characters; 23 Bytes)
0x82 Interface to Core Network and Bearer Tag
0x32 (Length = "50")
0x10 0xAA (bearer = "GSM-CSD"; 2 Bytes)
0x08 0x2B 0x34 0x39 0x35 0x33 0x34 0x31 0x39 0x30 0x36 0x00
(address = "+495341906", 12 Bytes)
0x09 0x87 (type of address = "E164"; 2 Bytes)
0x25 0xC5 (speed = "autobauding"; 2 Bytes)
0x0A 0x90 (call type = "ANALOG_MODEM"; 2 Bytes)
0x0C 0x9A (authentication type = "PAP"; 2 Bytes)
0x0D 0x64 0x75 0x6D 0x6D 0x79 0x11 0x6E 0x61 0x6D 0x65 0x00
(authentication id = "dummy_name"; 12 Bytes)
0x0E 0x64 0x75 0x6D 0x6D 0x79 0x11 0x70 0x61 0x73 0x73 0x77 0x6F 0x72 0x64 0x00
(authentication pw = "dummy_password"; 16 Bytes)
0x83 Gateway Tag
0x36 (Length = "54")
0x20 0x31 0x37 0x30 0x2E 0x31 0x38 0x37 0x2E 0x35 0x31 0x2E 0x33 0x00
(address = "170.187.51.3"; 14 Bytes)
0x21 0x85 (type of address = "IPv4"; 2 Bytes)
0x23 0x39 0x32 0x30 0x33 0x00 (port = "9203"; 6 Bytes)
0x24 0xCB (service = "CO-WSP"; 2 Bytes)
0x19 0x9C (authentication type = "HTTP BASIC"; 2 Bytes)
0x1A 0x64 0x75 0x6D 0x6D 0x79 0x11 0x6E 0x61 0x6D 0x65 0x00
(authentication id = "dummy_name"; 12 Bytes)
0x1B 0x64 0x75 0x6D 0x6D 0x79 0x11 0x70 0x61 0x73 0x73 0x77 0x6F 0x72 0x64 0x00
(authentication pw = "dummy_password"; 16 Bytes)
3GPP
Release 15 324 3GPP TS 31.102 V15.21.0 (2018-0610)
Annex K (informative):
Examples of VService_Id coding
This annex gives examples for the coding of VService_Id,
It is assumed that:
- acknowledgement flag bit is set to 0;
- the call priority bits are set to 0.
GroupId Content of EFVBS or EFVGCs VService_Id(vbs) VService_Id(vgcs)

00000000 F0FFFFFF 00000000 00000010
00000001 F1FFFFFF 00000020 00000030
00000012 21FFFFFF 00000180 00000190
00000123 21F3FFFF 00000F60 00000F70
00001234 2143FFFF 00009A40 00009A50
00012345 2143F5FF 00060720 00060730
00123456 214365FF 003C4800 003C4810
01234567 214365F7 025AD0E0 025AD0F0
12345678 21436587 178C29C0 178C29D0
99999999 99999999 BEBC1FE0 BEBC1FF0
13452670 31546207 19A8AFC0 19A8AFD0
3GPP
Release 15 325 3GPP TS 31.102 V15.21.0 (2018-0610)
Annex L (normative):
USIM-INI and USIM-RN for Relay Nodes
L.1 Introduction
USIM-RN and USIM-INI are used for Relay Node network connections establishment.
USIM-INI, if present on the UICC, and USIM-RN include at least all mandatory files defined for a USIM in the present
document, with the exception of files related to emergency calls.
Editor’s note: It is FFS whether the list of files mandatory to support can be reduced further.
USIM-INI is only required in case of a certificate based solution as described in TS 33.401 [52].
For the certificate-based solution, the UICC shall support BIP-UICC server mode (see TS 31.111 [12]) and may support
the Inter-Chip USB UICC/terminal interface (see TS 31.101 [11]) to perform the TLS handshake.
The USIM-RN is used to ensure a one to one binding with the Relay Node. The security architecture for Relay Nodes is
L.2 Application selection procedure

Application selection is performed according to the procedures defined in clause 5.1.1.1. The following provisions
apply:
When using pre-shared keys, only a USIM-RN is required, and the Relay Node will establish directly a secure channel
with USIM-RN. It is assumed that the Relay Node knows the "3G application code" within the PIX value reserved for
3GPP USIM-RN.
When using certificate based procedure, the UICC inserted in the Relay Node shall contains two USIMs, the USIM-RN
and USIM-INI. In case initial provisioning is required, the Relay Node will first select USIM-INI, either by direct
application selection or by use of the EF_DIR file.
1. Direct application selection: with full or with partial AID. It is assumed that the Relay Node knows the "3G
application code" within the PIX value reserved for 3GPP USIM-INI.
2. By use of the EF_DIR file: The Relay Node identifies the USIM-INI, which is characterised by an AID with a
"3G application code" within the PIX value reserved for 3GPP USIM-INI, see TS 31.101 [11], and selects the
USIM-INI by AID. The AID of the USIM-RN is characterised by an AID with a "3G application code" within
the PIX value reserved for 3GPP USIM-RN, see TS 31.101 [11]. If the only applications present in EF_DIR are
a USIM-RN and a USIM-INI, the terminal omits user presentation and proceeds to application selection.
The USIM applications USIM-INI and USIM-RN are not simultaneously active. USIM-INI is used to establish an
initial network connection and USIM-INI is deactivated once the network related operations are finished. USIM-INI is
deactivated prior to activating USIM-RN.
USIM-INI may be selected on any logical channel, see TS 31.101 [11]. Prior to selecting USIM-RN a new logical
channel shall be opened using the MANAGE CHANNEL command as specified in TS 31.101 [11], an application to
application secure channel can only be established on a logical channel different from channel 0. USIM-RN is then
selected on the new logical channel.
3GPP
Release 15 326 3GPP TS 31.102 V15.21.0 (2018-0610)
USIM-RN shall be configured to support implicit and explicit application selection. The Relay Node will first select
USIM-INI, according to the application selection mechanisms specified in TS 31.101 [11]. When the USIM-RN is
selected explicitly, the Relay Node shall send a SELECT by AID APDU command in clear text prior to secure channel
establishment. The implicit selection mechanism is performed by specifying USIM-RN AID in the MANAGE
SECURE CHANNEL – Establish Master SA command.
L.3 Secure channel operation

The USIM-RN shall allow communication only via "Secured APDU" secure channel as defined in ETSI TS 102 484
[66].
NOTE: The above implies in particular that the AUTHENTICATE command to the USIM-RN is not executed
outside the secure channel.In case the pre-shared key solution is used to establish the secure channel only the USIM-RN
is required for establishing the connection, and the Relay Node will establish directly a secure channel with the USIM-
RN before attaching to the network. The initial network connection using USIM-INI is not required in this case, and
hence USIM-INI is not required.
In case the certificate based solution is used, the UICC inserted in the Relay Node shall contain two USIMs, USIM-RN
and USIM-INI. A TLS handshake shall be used to provide key material for the Master SA for the secured APDU
protocol, according to ETSI TS 102 484 [66].
L.4 Support of commands

The Relay Node may limit the set of APDU commands encapsulated in TRANSACT DATA command to the strict
minimum (READ BINARY, READ RECORD, SELECT, STATUS, UPDATE BINARY, UPDATE RECORD,
AUTHENTICATE).
The Relay Node and the UICC shall support letter class 'e' toolkit commands for BIP, see TS 31.111 [12]. In order to
support toolkit the TERMINAL PROFILE, TERMINAL RESPONSE, ENVELOPE and FETCH commands need to be
supported. These commands are not issued on the secure channel. According to TS 31.111 [12], USAT commands shall
be sent on logical channel 0.
L.5 Storage of certificates

If the UICC supports the certificate based procedure, the UICC shall be provisioned with the UICC certificate and the
root certificate. The UICC certificate, which is used as a server certificate in the TLS handshake, is stored in EF CERT in
USIM-INI as it needs to be accessed by the RN for reading the CRL distribution point before establishing the secure
channel, for details cf. TS 33.401 [52]. The root certificate, which is used to verify the RN certificate in the TLS
handshake, is only needed for UICC-internal purposes and need not be stored in an EF.
L.6 Relay Node files support

L.6.1 USIM-INI Files
L.6.1.1 EFCERT (UICC Certificate)

This file contains the UICC Certificate.
3GPP
Release 15 327 3GPP TS 31.102 V15.21.0 (2018-0610)
File size: N bytes Update activity: low

Access Conditions:
READ ALW
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

X UICC Certificate M X
The format is as specified in TS 33.401 [52].
L.6.2 USIM-RN Files
L.6.2.1 eFRNid (Relay Node identifier)

This EF contains the Relay Node identifier the USIM-RN is bound to, see TS 33.401 [52].
An USIM-RN shall contain this file. The content of this file is not intended to be read on UICC-RN interface. It serves
as a storage location for the Relay Node identifier to which the UICC is bound. The file content is described for the
purpose of Over-The-Air update.
Identifier: '6FEA' Structure: transparent Optional
File size: N bytes Update activity: low

Access Conditions:
READ ADM
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

Country Tag '80' O 1 byte
Country Length = 2 C 1 byte
Country code (ASCII characters) C 2 bytes
Organization Tag '81' M 1 byte
Organization Length M 1 byte
Organization name (characters coded in UTF8) M K bytes
Common Name Tag '82' M 1 byte
Common Name Length M 1 byte
Common Name (characters coded in UTF8) M L bytes
Serial Number Tag '82' O 1 byte
Serial Number Length C 1 byte
Serial Number (characters coded in ASCII) C M bytes
NOTE: C: if the Tag is present, this is mandatory
3GPP
Release 15 328 3GPP TS 31.102 V15.21.0 (2018-0610)
L.6.2.2 EFSCCmax (maximum value of Secure Channel Counter)

This EF contains the maximum number of transaction allowed with the same Connection SA, when a secure channel is
established. When the counter value in TRANSACT DATA command reaches the maximum value, the terminal shall
derive new key material using Manage Secure Channel APDU – establish SA – Connection SA, see ETSI TS 102.484
[66].
An USIM with an Application ID in the USIM-RN range shall contain this file.
Identifier: '6FEB' Structure: transparent Optional

Access Conditions:
READ ALW
UPDATE ADM
DEACTIVATE ADM
ACTIVATE ADM

8 Secure Channel counter M 8 byte
NOTE: The value of the Secure channel counter is set at personalisation. It is not intended to be updated or modified
as a result of establishing a new Connection SA.
3GPP
Release 15 329 3GPP TS 31.102 V15.21.0 (2018-0610)
Annex M (normative):
USIM application dedicated for IOPS
M.1 Introduction
IOPS allows to provide network service to Public Safety users even in the case the network has no or only limited
backhaul connectivity. One of the main issues in such cases is the missing backhaul to perform authentication. A
solution has been defined by using local HSSs which take over the responsibility for authentication in IOPS mode.
A problem identified for IOPS security when making use of local HSS is the higher probability of a compromise of a
local HSS. Therefore the security solution described in TS 33.401 uses a local HSS with different authentication
credentials than the standard HSS in normal operation. Additionally there might be several local HSSs and to further
reduce the impact of possible compromised local HSSs, each local HSS should use different authentication credentials.
The security solution described in 3GPP TS 33.401 [52] is based on a USIM application dedicated for IOPS and using
derived individual keys per local HSS.
3GPP TS 23.401 [69] Annex K specifies a PLMN identity dedicated for IOPS mode of operation. Additionally a USIM
dedicated for IOPS uses an Access Control Class of '11' or '15'.
M.2 Features of the USIM dedicated for IOPS

The USIM dedicated for IOPS may be implemented as a single USIM on a UICC or as a secondary USIM application
together with a normal USIM on one UICC. The USIM for IOPS is a regular USIM application and contains all
mandatory EFs for a USIM and may also include any of the optional EFs defined for a USIM.
The USIM dedicated for IOPS nevertheless has some specifics:
- As specified in 3GPP TS 23.401 [69] Annex K, the Access Control Class in EFACC is set to either '11' or '15'. The
specific values for the Access Control Class prevent UEs with different Access Control Classes from trying to
attach to the IOPS network.
- The entry for the USIM dedicated for IOPS in EFDIR has a label starting with 'USIM-IOPS'.
In case multiple local HSSs are to be supported, The USIM should also support:
- The AMF (Authentication Management Field) mechanism as described in 3GPP TS 33.401 [52] Annex F.4.1 is
supported.
- An Operator specific mechanism to derive local HSS individual keys is supported (see 3GPP TS 33.401 [52]
Annex F.4).
NOTE: The mechanism to derive local HSS specific keys in the USIM dedicated for IOPS is specific to an
Operator and needs to be agreed for the local HSS and the USIM. One example mechanism is described
in 3GPP TS 33.401 [52] Annex F.4.2.
M.3 Selection mechanisms

The method for selecting a USIM dedicated for IOPS is left to ME implementation.
3GPP
Release 15 330 3GPP TS 31.102 V15.21.0 (2018-0610)
Annex N (informative):
Change history
The table below indicates all CRs that have been incorporated into the present document since it was initially approved.
3GPP
Release 15 331 3GPP TS 31.102 V15.21.0 (2018-0610)
TSG # / TSG Doc. WG doc CR Rev Cat Subject/Comment New

Date
TP-27 Creation of Rel-7 version based on v6.9.0 7.0.0
TP-27 TP-050018 T3-050189 0264 1 F Correction to overcome IMSI number space limitation – inclusion 7.0.0
of EHPLMN
CT-28 CP-050136 C6-050402 0277 A ISO/IEC 7816-series revision 7.1.0
CT-28 CP-050139 C6-050370 0272 Essential correction of the phonebook (access to mapped filed & 7.1.0
"hidden key" coding)
CT-28 CP-050139 C6-050372 0285 A Added EF_ARR under DF_TELECOM 7.1.0
CT-28 CP-050139 C6-050374 0280 A Modifications regarding WLAN 7.1.0
CT-28 CP-050139 C6-050376 0282 A Alignment of MBMS procedures with TS 33.246 7.1.0
CT-28 CP-050139 C6-050404 0287 A Number of stored MSKs 7.1.0
CT-28 CP-050139 C6-050478 0289 A Essential correction of phonebook support 7.1.0
CT-28 CP-050139 C6-050483 0291 A Corrections to eMLPP and AAeM 7.1.0
CT-28 CP-050139 C6-050406 0278 F Correction to EF-HPLMN 7.1.0
CT-29 CP-050460 C6-050689 0294 2 F Clarification on ADM access condition 7.2.0
CT-29 CP-050460 C6-050729 0295 2 F Editorial corrections 7.2.0
CT-30 CP-050499 C6-050876 0298 F Clarifications in DF_PHONEBOOK level 7.3.0
CT-30 CP-050499 C6-050898 0297 A NAF Id alignment with TS 33.246 7.3.0
CT-31 CP-060018 C6-060158 0304 1 A Addition of mandatory UST services id references for 7.4.0
VGCS/VBS security context definition
CT-31 CP-060023 C6-060119 0299 C Change to allow PNN segmentation of the HPLMN and 7.4.0
EHPLMN support
CT-31 CP-060023 C6-060122 0302 F Indication of services in the USIM 7.4.0
CT-31 CP-060023 C6-060184 0305 C Correction of service numbers associated to the UST 7.4.0
CT-31 CP-060156 C6-060121 0301 1 A Padding of VSTK_RAND 7.4.0
- - - - - - MCC Completion of implementation of C6-060184 7.4.1
CT-32 CP-060239 C6-060277 0308 A USAT related procedures - Additional Terminal Profile 7.5.0
CT-32 CP-060239 C6-060279 0310 a VService_Id coding examples 7.5.0
CT-33 CP-060385 C6-060601 0318 1 F Essential correction of the authenticate command in order to 7.6.0
process message longer than 255 bytes
CT-34 CP-060541 C6-060781 0320 1 A Correction of the MSK Update procedures 7.7.0
CT-34 CP-060541 C6-060808 0322 2 A Clarification of the USIM behavior when MSK key is not updated 7.7.0
CT-34 CP-060541 C6-060785 0324 1 A Correction of MBMS Security Context description 7.7.0
CT-34 CP-060541 C6-060764 0327 - A Correction of the references to a non-exisiting table in 7.7.0
Authenticate command description
CT-34 CP-060541 C6-060817 0332 - A Correction of the MUK Update procedures 7.7.0
CT-34 CP-060547 C6-060788 0331 - F Correction of the Tables in section 7.1.2.5 7.7.0
CT-35 CP-070072 C6-070059 0340 - F Correction of the EHPLMN SFI 7.8.0
CT-35 CP-070067 C6-070120 0334 2 B Presentation of EHPLMN 7.8.0
CT-35 CP-070067 C6-070133 0336 2 B Last RPLMN Selection Indication 7.8.0
CT-35 CP-070071 C6-070123 0339 1 A MSK management procedures 7.8.0
CT-36 CP-070305 C6-070311 0341 1 B Presentation of additional information in manual selection mode 7.9.0
CT-36 CP-070299 C6-070310 0349 1 F Correction of EF-IMG and EF-IIDF 7.9.0
CT-36 CP-070464 - 0350 1 A GBA NAF Keys and MUKs storage policy 7.9.0
2007-06 - - - - - Correction to implementation of '0x' as '04' in 7.1.2.5 (MCC) 7.9.1
CT-37 CP-070620 C6-070417 0347 3 B Key Establishment mechanism: alignment with TS 33.110 7.10.0
CT-37 CP-070611 C6-070434 0352 - A Inconsistency in the MSK update procedures 7.10.0
CT-38 CP-070840 C6-070523 0355 - F Correction of reference to 3GPP TS 23.140 7.11.0
CT-38 CP-070840 C6-070586 0354 - F Completion of missing "Terminal Applications" entry in the UST 7.11.0
CT-38 CP-070841 C6-070884 0343 5 B Reservation of parameters for OMA BCAST Smart Card Profile 8.0.0
CT-39 CP-080166 C6-080063 0365 1 A MBMS security – Authentication error 9866 8.1.0
CT-39 CP-080167 C6-080059 0362 1 A Add the support of EHPLMN in the automatic network selection 8.1.0
CT-39 CP-080168 C6-080014 0360 - F Correction of UST due to error in CR implementation 8.1.0
CT-39 CP-080168 C6-080064 0366 1 B Correction of typo in the description of one of the fields of 8.1.0
EFMBI.
CT-39 CP-080168 C6-080070 0357 3 B Storage of SPN and PNN in graphic format 8.1.0
Note: changes to clauses 5.3.10 and 5.3.24 have been moved to
new sections with appropriate names.
CT-40 CP-080385 C6-080147 0368 1 F Clarification of content of EFUID 8.2.0
CT-41 CP-080582 C6-080273 0372 - A Authentication of GBA 8.3.0
CT-41 CP-080642 C6-080266 0373 2 B Introduction of ICE information in the UICC 8.3.0
CT-41 CP-080642 C6-080289 0375 2 B Configuration of Network Connectivity parameters for UICC 8.3.0
remote IP connections
CT-41 CP-080642 C6-080245 0376 - B Introduction of new access technologies for LTE 8.3.0
CT-42 CP-080904 C6-080469 0374 5 B Storage of EPS Mobility Management parameters 8.4.0
CT-42 CP-080904 C6-080468 0380 4 B USIM provisioning for home (e)NodeB 8.4.0
CT-42 CP-080904 C6-080444 0382 1 B Support for LTE in the EF-Operator PLMN 8.4.0
CT-42 CP-080909 C6-080409 0383 - F Correction to Example for MMS Issuer/User Connectivity 8.4.0
Parameters
CT-42 CP-080961 -------------- 0385 2 B Addition of I-WLAN related files and procedures 8.4.0
CT-43 CP-090188 C6-090007 0386 - F Removal of KNASint and KNASenc in EFEPSNSC 8.5.0
3GPP
Release 15 332 3GPP TS 31.102 V15.21.0 (2018-0610)
CT-43 CP-090188 C6-090056 0387 1 F Correction of EF EPSNSC 8.5.0

CT-43 CP-090188 C6-090077 0390 - B Support of EPS in USAT: extension of Call control 8.5.0
CT-43 CP-090192 C6-090074 0388 1 B HPLMN Direct Access Indicator for I-WLAN 8.5.0
CT-43 CP-090198 C6-090080 0384 5 F Correction of Network Connectivity parameters for UICC remote 8.5.0
IP connections (Email approval)
CT-44 CP-090451 C6-090110 0391 - F correction of coding of suggested contents of the EF_EPSLOCI 8.6.0
at pre-personalization
CT-44 CP-090451 C6-090188 0392 2 F correction of update status via Data Download or USAT 8.6.0
Application for EF_EPSLOCI and EF_EPSNSC
CT-44 CP-090479 --------------- 0396 2 D Editorial modifications of File structure overview 8.6.0
CT-44 CP-090479 --------------- 0398 2 A Correction of wrong file names 8.6.0
CT-44 CP-090451 C6-090112 0399 - F Removal of NH and NCC parameters from EFEPSNSC 8.6.0
CT-44 CP-090451 C6-090116 0400 - F Correction for EPS in USIM security related procedures 8.6.0
CT-44 CP-090451 C6-090160 0405 - C Allowed CSG List updateable by ME 8.6.0
CT-45 CP-090712 C6-090305 0402 1 F eCALL related enhancements 8.7.0
CT-45 CP-090712 C6-090301 0406 1 F Correction of coding of CSG ID 8.7.0
CT-45 CP-090713 C6-090309 0409 2 F Essential correction of EFSPDI encoding 8.7.0
CT-45 CP-090714 C6-090304 0412 3 F Align files at Telecom level according to TS 102 222 9.0.0
CT-45 CP-090714 C6-090307 0416 2 B Support For Multimode System Selection Storage 9.0.0
CT-46 CP-090991 C6-090415 0423 - F Correction to application session termination 9.1.0
CT-46 CP-090991 C6-090423 0428 - D Editorial correction on tables in NAF Key Centre tag and NAF 9.1.0
Key Centre information
CT-46 CP-090992 C6-090440 0425 - A Correction of incorrect tag value 9.1.0
CT-46 CP-090990 C6-090460 0410 3 B Introduction of operator controlled CSG list for H(e)NB 9.1.0
CT-46 CP-090990 C6-090500 0427 1 A Correction of Allowed CSG list 9.1.0
CT-47 CP-100187 C6-100031 0429 - F Correction to EF_ACSGL access condition 9.2.0
CT-47 CP-100187 C6-100055 0431 - F Correction to informative Annex D 9.2.0
CT-47 CP-100188 C6-100111 0432 - B Introduction of Indicator for Inhibition of Allowed CSG List 9.2.0
CT-47 CP-100189 C6-100115 0433 - B Introduction of ICE (In Case of Emergency) graphics files 9.2.0
CT-48 CP-100391 C6-100260 0434 1 F ICE graphics related procedure 9.3.0
CT-49 CP-100585 C6-100403 0446 A Introduction of an ISIM EF to support Public Service Identity for 9.4.0
SMS over IP
CT-49 CP-100586 C6-100358 0443 A Update of reference to ETSI TS 102 483 9.4.0
CT-49 CP-100587 C6-100328 0438 F Alignment of HNB and HeNB to the service requirements 9.4.0
CT-49 CP-100587 C6-100387 0439 1 F Update reference to 3GPP2 specifications 9.4.0
CT-50 CP-100826 C6-100596 0450 1 F Correction to Issuer specified PIN for ICE files 9.5.0
CT-50 CP-100827 C6-100617 0448 1 F Allocation of File ID for EF_ICE-graphics 9.5.0
CT-50 CP-100827 C6-100618 0451 1 F ETSI SCP specification reference update 9.5.0
CT-50 CP-100826 C6-100643 0466 A Correction of EF_EPSNSC content description 9.5.0
CT-50 CP-100823 C6-1006428 0462 1 B Communication control for IMS procedures in USIM 10.0.0
CT-51 CP-110236 C6-110191 0464 5 B Introduction of Smart Card Web Server launch functionality 10.1.0
CT-51 CP-110239 C6-110062 0467 1 B Addition of an EF for USAT facility control 10.1.0
CT-51 CP-110244 C6-110089 0469 1 B Addition of 'Extended Terminal Application' support in EF_UST 10.1.0
CT-51 CP-110244 C6-110064 0470 1 D Correction to coding of EF_MMSICP 10.1.0
CT-51 CP-110242 C6-110092 0471 F CSG lists display Control 10.1.0
CT-51 CP-110297 0472 3 B Introduction of the IARI list in the USIM 10.1.0
CT-51 CP-110302 0473 7 B Non-Access Stratum (NAS) configuration parameters 10.1.0
CT-51 CP-110235 C6-110160 0475 1 B Procedures for Relay Node USIM 10.1.0
CT-52 CP-110516 --------------- 0482 2 A Essential correction to EPS NAS security context update 10.2.0
CT-52 CP-110527 --------------- 0479 3 C Priority for NAS configuration parameters 10.2.0
CT-53 CP-110593 C6-110414 0483 2 A Clarification of ACL in EPS Network 10.3.0
CT-53 CP-110703 0485 2 F Correction to NAS configuration parameters coding 10.3.0
CT-53 CP-110595 C6-110411 0484 1 F Correction of service required for EF-EST to be present 11.0.0
CT-55 CP-120173 0503 1 A Correction of EF_ICON references in EF_LAUNCH_SCWS 11.1.0
CT-55 CP-120143 C6-120074 0504 1 D Corrections in the section DFs at the USIM ADF level 11.1.0
CT-55 CP-120181 0510 A Correction to Allowed CSG list and Operator CSG list coding 11.1.0
CT-55 CP-120145 C6-120091 0509 A Update of reference to ETSI TS 102 484 11.1.0
CT-55 CP-120145 C6-120096 0511 A Correction to EF_UICCIARI section number 11.1.0
CT-55 CP-120145 C6-120100 0512 A FID allocation and other corrections to USIM for Relay Nodes 11.1.0
CT-56 CP-120385 C6-120221 0516 A Correction to reference for CSG Type in EFCSGT 11.2.0
CT-56 CP-120386 C6-120277 0519 1 B Adding new NAS configuration parameter for SIMTC 11.2.0
CT-57 CP-120620 C6-120440 0535 1 A Update of reference to ASN.1 coding specification 11.3.0
CT-58 CP-120866 C6-120565 0546 A Correction of update activity for EF_MSK 11.4.0
CT-58 CP-120867 C6-120610 0536 2 A HPLMN or RPLMN selection clarification 11.4.0
CT-58 CP-120867 C6-120574 0539 1 A Clarification for CSG Display Control during manual selection 11.4.0
CT-58 CP-120867 C6-120604 0517 2 B Addition of EF with PWS configuration 11.4.0
CT-60 CP-130361 C6-130196 0558 1 A Essential correction of CSG Type coding description 11.5.0
CT-60 CP-130362 C6-130170 0552 1 D Correction of file name for User controlled PLMN selector for 12.0.0
WLAN in the WLAN related procedure
CT-61 CP-130530 C6-130379 0562 2 A Handling of Multiple CSG ID display indicators for same PLMN id 12.1.0
CT-61 CP-130531 C6-130384 0565 2 F Usage of SMS record identifier of EFSMSR as pattern for 12.1.0
SEARCH RECORD
3GPP
Release 15 333 3GPP TS 31.102 V15.21.0 (2018-0610)
CT-62 CP-130794 C6-130537 0567 B Fast higher priority PLMN search upon entering VPLMN 12.2.0
CT-63 CP-140161 C6-140077 0572 1 B Addition of POLL INTERVAL ENVELOPE command 12.3.0
CT-63 CP-140161 C6-140109 0571 4 B Presence detection due to active PDP context 12.3.0
CT-63 CP-140162 C6-140080 0569 1 B URI support for USIM Phonebook 12.3.0
CT-64 CP-140423 C6-140278 0568 3 B New UICC service in UST for URI support 12.4.0
CT-64 CP-140431 C6-140231 0581 F New UICC service in UST for URI support 12.4.0
CT-64 CP-140432 C6-140271 0573 1 F Addition of configuration parameter for EMM cause #15 12.4.0
extension
CT-64 CP-140441 C6-140280 0580 1 F Correction of length coding for EFPSEUDO 12.4.0
CT-65 CP-140699 C6-140472 0588 1 B Addition of DF for ProSe configuration 12.5.0
CT-65 CP-140699 C6-140477 0587 1 B Enablement of ProSe functionality for Public Safety 12.5.0
CT-65 CP-140699 C6-140482 0593 1 B Addition of EFs with monitoring and announcing information for 12.5.0
ProSe Direct Discovery
CT-65 CP-140699 C6-140491 0589 2 B Addition of a EF with IP address of the ProSe Function 12.5.0
CT-65 CP-140699 C6-140492 0590 2 B Addition of EF with radio parameters for public safety ProSe 12.5.0
direct communication in out of coverage scenario
CT-65 CP-140699 C6-140493 0591 2 B Addition of EF with policy parameters for public safety ProSe 12.5.0
direct services in out of coverage scenario
CT-65 CP-140699 C6-140494 0592 2 B Addition of EF with parameters for public safety ProSe direct 12.5.0
communication for PLMNs different from HPLMN
CT-65 CP-140700 C6-140495 0600 1 C Removal of USIM Service Table Service for Poll Interval 12.5.0
Negotiation
CT-65 CP-140701 C6-140504 0595 2 A 'Override NAS signalling low priority' and 'Override Extended 12.5.0
access barring' linkage
CT-65 CP-140703 C6-140505 0586 3 B Extension of URI support by USIM services 12.5.0
CT-65 CP-140708 C6-140502 0601 F Correction of change request implementation errors 12.5.0
CT-66 CP-140955 C6-140624 0602 D Removal of editor's notes for ProSe files 12.6.0
CT-66 CP-140955 C6-140710 0604 2 F Changes to ProSe Radio Parameters for Direct Communication 12.6.0
CT-66 CP-140955 C6-140711 0605 1 F Changes for ProSe Policy Parameters 12.6.0
CT-66 CP-140955 C6-140724 0603 2 F Removal of unnecessary items in ProSe parameters 12.6.0
CT-66 CP-140955 C6-140726 0611 3 B Addition of EF to store PTK ID and counter for ProSe direct 12.6.0
communication
CT-66 CP-140956 C6-140722 0609 1 C Extension of URI support by USIM BDN service 12.6.0
CT-66 CP-140956 C6-140723 0610 1 C Extension of URI support by USIM SDN service 12.6.0
CT-66 CP-140957 C6-140727 0597 6 B USAT Pairing whitelist file 12.6.0
CT-66 CP-140957 C6-140728 0598 6 B USAT Application Pairing: Pairing Status and IMEISV Files 12.6.0
CT-66 CP-140957 C6-140729 0596 3 B USAT Application Pairing for MTC device reference and 12.6.0
procedure
CT-67 CP-150154 C6-150077 0613 1 F Removal of circles geographical areas 12.7.0
CT-67 CP-150154 C6-150078 0614 1 C ProSe Service Table 12.7.0
CT-67 CP-150154 C6-150081 0616 1 B ProSe Direct Communication usage monitoring 12.7.0
CT-67 CP-150154 C6-150082 0615 1 B Addition of services for ProSe Direct Communication usage 12.7.0
information storage and reporting
CT-67 CP-150155 C6-150096 0617 3 B Addition of UE configuration parameters for SM Retry restriction 12.7.0
CT-67 CP-150156 C6-150100 0622 3 F Correction of Annex D list of tags 12.7.0
CT-67 CP-150180 0612 2 F Clarification of Direct Communication Radio Parameters 12.7.0
CT-68 CP-150382 C6-150203 0626 F Geographical Area in Direct Communication Radio Parameters 12.8.0
CT-68 CP-150383 C6-150205 0627 F Clarification of text for UE configuration parameters for SM Retry 12.8.0
restriction
CT-68 CP-150379 C6-150267 0635 1 A Correct file access conditions to activate/deactivate 12.8.0
CT-68 CP-150384 C6-150274 0625 1 F Correction for FDN and BDN usage in case of IMS 12.8.1
CT-68 CP-150381 C6-150290 0628 1 B URI support for SMS indicator in UST 13.0.0
CT-68 CP-150394 C6-150311 0629 2 B Support of Enhanced IMS Call Control by USIM 13.0.0
CT-69 CP-150563 C6-150423 0638 F Clarification to the applicability of the UE retry wait time value or 13.1.0
behaviour
CT-69 CP-150563 C6-150468 0639 1 C Replacement of EF LAUNCH SCWS with EF LAUNCH PAD 13.1.0
CT-69 CP-150563 C6-150464 0641 1 B UICC interface in Power Saving Mode (PSM) 13.1.0
CT-69 CP-150561 C6-150478 0648 A Alignment of EFs at the MF level with TS 31.101 13.1.0
CT-70 CP-150830 C6-150608 0659 A Alignment of the EFIPS record length 13.2.0
CT-70 CP-150829 C6-150618 0645 2 F Correction of EF NASconfig 13.2.0
CT-70 CP-150832 C6-150635 0637 4 B ePDG Configuration Information 13.2.0
CT-70 CP-150833 C6-150637 0651 1 B UICC interface during eDRX 13.2.0
CT-71 CP-160149 C6-160105 0688 1 B Addition of ACDC configuration parameters 13.3.0
CT-71 CP-160148 C6-160028 0666 F Update of ProSe ReportGroupParameters in EF-PROSE_UIRC 13.3.0
CT-71 CP-160148 C6-160029 0667 B Authorization for one-to-one direct communcation when not 13.3.0
served by E-UTRAN
CT-71 CP-160148 C6-160066 0664 1 B Addition of model for direct discovery for public safety. 13.3.0
CT-71 CP-160148 C6-160067 0665 1 B Addition of radio parameters for ProSe Direct Discovery 13.3.0
CT-71 CP-160148 C6-160068 0668 1 B Authorization for one-to-one direct communication 13.3.0
CT-71 CP-160148 C6-160069 0669 1 B Addition of Application Layer Group ID 13.3.0
CT-71 CP-160148 C6-160070 0675 1 B Addition of ProSe discovery parameters 13.3.0
CT-71 CP-160148 C6-160071 0676 1 B Addition of ProSe relay configuration 13.3.0
CT-71 CP-160147 C6-160103 0680 3 B USIM application dedicated for IOPS 13.3.0
3GPP
Release 15 334 3GPP TS 31.102 V15.21.0 (2018-0610)
CT-71 CP-160146 C6-160091 0679 1 B Addition of MCPTT related parameters 13.3.0

CT-71 CP-160143 C6-160042 0674 D Editorial modification of EF-PROSE_GC 13.3.0
CT-71 CP-160145 C6-160052 0670 1 C Making Local Phone Book Optional 13.3.0
CT-71 CP-160150 C6-160058 0672 1 B ePDG Configuration Information for Emergency Services over 13.3.0
WLAN
CT-71 CP-160141 C6-160094 0682 1 A Essential correction of EF-EPSNSC for invalid stored EPS NAS 13.3.0
security context
CT-71 CP-160144 C6-160041 0673 D Editorial correction to EF-NASCONFIG 13.3.0
CT-71 CP-160144 C6-160056 0677 1 F ePDG Configuration Information alignment with SA2 agreement 13.3.0
CT-71 CP-160144 C6-160077 0663 2 F Correction of presence condition of EFPNN and EFOPL 13.3.0
CT-71 CP-160144 C6-160107 0671 2 F Correction to UICC interface in PSM 13.3.0
CT-72 CP-160347 C6-160225 0691 F Allocation of SFI values for USIM ADF 13.4.0
CT-72 CP-160349 C6-160270 0690 1 C Making phonebook support optional for MEs with reduced 13.4.0
feature capabilities
CT-72 CP-160350 C6-160277 0695 1 F Unique MCPTT configuration data file 13.4.0
CT-72 CP-160351 C6-160276 0697 1 F Security content in ProSe Relay Discovery Parameters 13.4.0
CT-72 CP-160352 C6-160281 0698 C Enhancement to EF HPPLMN for higher priority PLMN search 13.4.0
for IoT devices
CT-73 CP-160546 C6-160410 0703 1 F Correction of I-WLAN specification references 13.5.0
CT-73 CP-160549 C6-160359 0700 B Test and reconfiguration URIs for eCall over IMS Emergency 14.0.0
Services using the PS domain in E-UTRAN
CT-74 CP-160788 C6-160631 0705 2 A Essential correction to UICC interface in PSM mode 14.1.0
CT-74 CP-160789 C6-160624 0702 3 B URI support for SMS-PP DOWNLOAD indicator in UST 14.1.0
CT-74 CP-160794 C6-160539 0707 B Addition of Default DCN-ID parameter in EFnasconfig 14.1.0
CT-74 CP-160795 C6-160619 0710 1 B Support of OIP OIR Policy 14.1.0
CT-74 CP-160818 0708 4 B Default EPS bearer context usage restriction policy configuration 14.1.0
CT-75 C6-170106 C6-170107 0716 3 B Added new EF with TV configuration 14.2.0
CT-75 CP-170231 C6-170091 0714 - B UE configuration for exceptional data reporting 14.2.0
CT-75 CP-170174 C6-170111 0720 1 B Addition of configuration parameter for Light Connection for 14.2.0
Roaming UEs
CT-75 CP-170172 C6-170130 0729 3 F Correct references for release 14 14.2.0
CT-75 CP-170212 C6-170086 0713 1 F Clarification on the parameters in the EF-NASCONFIG 14.2.0
CT-75 CP-170212 C6-170128 0717 2 B 3GPP PS Data Off 14.2.0
CT-75 CP-170213 C6-170127 0718 1 B Introduction of SUSPEND UICC command 14.2.0
CT-75 CP-170213 C6-170056 0719 - B AKA with 256-bit input key K 14.2.0
CT-75 CP-170164 C6-170105 0728 1 A Correction of coding for EFNCP-IP (Network Connectivity 14.2.0
Parameters for USIM IP connections)
CT-75 CP-170171 C6-170135 0721 3 B BER-TLV EF for V2X configuration data file 14.2.0
CT-76 CP-171163 C6-170222 0734 - F Various corrections for the PS Data Off configuration 14.3.0
CT-76 CP-171160 C6-170261 0737 1 B Introduction of E-UTRAN in NB-S1 mode in EFs encoded 14.3.0
as EFPLMNwAct
CT6 CP-171159 C6-170277 0733 1 F Alignment of TV configuration in the USIM with TS 14.3.0
24.117
CT6 CP-171161 C6-170274 0731 1 F Removal of Editor’s Note on DCN-ID length for eDecor 14.3.0
CT6 CP-171162 C6-170296 0715 5 B XCAP configuration parameters 14.3.0
CT6 CP-173151 C6-170734 0742 2 A Correction of requirements for eCall modes 14.4.0
CT6 CP-173133 C6-170622 0743 - F Correction of DFV2X 14.4.0
CT6 CP-173150 C6-170628 0744 - F Wrong implementation of CR for XCAP Configuration 14.4.0
Data
CT6 CP-173150 C6-170706 0746 1 F Clarification on the number of coordinates in a 14.4.0
geographical area
CT6 CP-173150 C6-170701 0747 1 F Correction for emergency call handling in case of UICC 14.4.0
presence detection fails
CT6 CP-180134 C6-180059 0767 1 B Enhance coding of Access Technology in EFPLMNwAcT 15.0.0
to accommodate 5GS
CT6 CP-180131 C6-180072 0768 1 B Configuration parameter for handover between WLAN 15.0.0
and EPS
CT6 CP-181158 C6-180256 0771 3 B Introduce an EF that contains list of EARFCNs and the 15.1.0
geographical areas associated with the EARFCNs for
enabling cell search of MTC carrier or NB-IOT carrier.
CT6 CP-181155 C6-180159 0772 1 B LOCI file for 5GS 15.1.0
CT6 CP-181158 C6-180162 0773 1 F Clarification on interactions between PSM and on-going 15.1.0
BIP sessions
CT6 CP-181155 C6-180172 0774 2 B Introduce an EF that contains keys generated by ME 15.1.0
from CK and IK.
CT6 CP-181155 C6-180187 0776 4 B Introduce EFs that contain NAS full native security 15.1.0
context from 5G Mobility Management Information.
CT6 CP-181155 C6-180293 0778 7 B Subscription identifier privacy suppport 15.1.0
CT6 CP-181155 C6-180167 0779 - F Corrections related to V2X 15.1.0
3GPP
Release 15 335 3GPP TS 31.102 V15.21.0 (2018-0610)
CT6 CP-181155 C6-180275 0780 2 B Introduce an EF that contains 5G UAC Access Identity 15.1.0
Information
CT6 CP-181155 C6-180185 0781 - B Removing implementation of CR0768 15.1.0
CT6 CP-181155 C6-180285 0784 2 B 3GPP PS Data Off - update to services for roaming 15.1.0
CT6 CP-181155 C6-180291 0785 1 B Support of 5GS new steering of roaming procedures 15.1.0
CT6 CP-181155 C6-180261 0786 1 B USIM Service Table update for PDU session call control 15.1.0
support
CT6 CP-181158 C6-180237 0787 - F Clarification on interactions between eDRX cycle and on- 15.1.0
going BIP sessions
CT6 CP-181155 C6-180276 0788 - F Correction after implementation of a non accepted CR 15.1.0
after CT#75 plenary
CT6 CP-182185 C6-180371 0794 1 B Allow configuration of MCS (Access Identity 2) via USIM. 15.2.0
CT6 CP-182189 C6-180315 0795 - C Update EFHPPLMN description to clarify timer T 15.2.0
interpretation based on the RAT in use.
CT6 CP-182185 C6-180404 0797 3 B Modify structure of SUCI Calc EF and introduce Routing 15.2.0
Indicator
CT6 CP-182194 C6-180535 0798 3 C Remove the control plane based SoR related EF and use 15.2.0
only the EF-UST.
CT6 CP-182185 C6-180418 0799 1 C Corrections to the control plane based SoR related EF 15.2.0
CT6 CP-182185 C6-180419 0803 4 C Introduction of DF-5GS 15.2.0
CT6 CP-182185 C6-180393 0806 3 F Updates to USIM management procedures for 5GS 15.2.0
CT6 CP-182185 C6-180567 0809 2 F Clarification of GET IDENTITY 15.2.0
CT6 CP-182185 C6-180408 0810 1 F Correct Kseaf and Kausf length in EF5GAUTHKEYS to 15.2.0
align with SA3 specification
CT6 CP-182185 C6-180564 0814 2 F Correction of 5GS 3GPP Access NAS Security Context 15.2.0
CT6 CP-182185 C6-180553 0816 2 B Extend text in EF ACL clause to also include DNN 15.2.0
CT6 CP-182187 C6-180538 0808 2 B Mission Critical Services configuration data update to 15.2.0
USIM
3GPP

3GPP TS 31.102

Uploaded by

Copyright:

Available Formats

3GPP TS 31.102

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3GPP TS 31.102

Uploaded by

Copyright:

Available Formats

3rd Generation Partnership Project;

3GPP support office address

No part may be reproduced except as authorized by written permission.

4.2.104 EFePDGSelection (ePDG Selection Information).......................................................................................114

4.6.3.1 EFMML (Multimedia Messages List).............................................................................................206

5.3 Subscription related procedures..............................................................................................................227

5.4.5 MO-SMS control by USIM...............................................................................................................239

6.2 Cryptographic Functions.........................................................................................................................248

H.2 List of SFI Values at the DF GSM-ACCESS Level.....................................................................291

Annex K (informative): Examples of VService_Id coding................................................................297

Annex M (normative): USIM application dedicated for IOPS.........................................................302

Annex N (informative): Change history..............................................................................................303

4.2.5 EFPLMNwAcT (User controlled PLMN selector with Access Technology).............................................24

4.2.66 EFSPDI (Service Provider Display Information)...................................................................................74

4.4.2 Contents of files at the DF PHONEBOOK level..............................................................................134

4.4.8.8 EFPROSE_POLICY (ProSe Policy Parameters).....................................................................................182

5.1.5 Language indication..........................................................................................................................220

5.3.22 Automatic Answer on eMLPP service..............................................................................................231

5.8.3 HNB name display related procedures..............................................................................................241

7.1.2.6 Local Key Establishment security context (All Modes)..............................................................259

Annex K (informative): Examples of VService_Id coding................................................................295

L.5 Storage of certificates.............................................................................................................................297

Annex M (normative): USIM application dedicated for IOPS.........................................................300

Annex N (informative): Change history..................................................................................................301

x the first digit:

1 presented to TSG for information;

2 presented to TSG for approval;

3 or greater indicates TSG approved document under change control.

The present document specifies:

- specific command parameters;

- contents of Efs (Elementary Files);

 For a specific reference, subsequent revisions do not apply.

[1] 3GPP TS 21.111: "USIM and IC Card Requirements".

[2] 3GPP TS 22.011: "Service accessibility".

[3] 3GPP TS 22.024: "Description of Charge Advice Information (CAI)".

[5] 3GPP TS 23.038: "Alphabets and language".

[11] 3GPP TS 31.101: "UICC-Terminal Interface, Physical and Logical Characteristics".

[12] 3GPP TS 31.111: "USIM Application Toolkit (USAT)".

[13] 3GPP TS 33.102: "3GPP Security; Security Architecture".

[14] 3GPP TS 33.103: "3GPP Security; Integration Guidelines".

[16] 3GPP TS 23.041: "Technical realization of Cell Broadcast (CB)".

[17] 3GPP TS 02.07: "Mobile Stations (MS) features".

[24] 3GPP TS 22.101: "Service aspects; service principles".

[25] 3GPP TS 23.003: "Numbering, Addressing and Identification".

[27] 3GPP TS 22.022: "Personalisation of Mobile Equipment (ME); Mobile functionality

[33] 3GPP TS 25.101: "UE Radio Transmission and Reception (FDD)".

[34] 3GPP TS 45.005: "Radio Transmission and Reception".

[36] 3GPP TS 23.097: "Multiple Subscriber Profile (MSP)".

[42] 3GPP TS 33.220: "Generic Authentication Architecture (GAA); Generic bootstrapping

[43] 3GPP TS 33.246: "Security of Multimedia Broadcast/Multicast Service".

[49] Open Mobile Alliance; OMA-TS-BCAST_SvcCntProtection

[55] 3GPP TS 24.341: "Support of SMS over IP networks; Stage 3"

[56] IETF RFC 3261: "SIP: Session Initiation Protocol".

[59] OMA Smartcard-Web-Server Approved Version 1.1 - 12 May 2009

NOTE: Available from http://www.ietf.org/rfc/rfc2046.txt.

[68] 3GPP TS 22.268: "Public Warning System (PWS) Requirements".

[70] 3GPP TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to Proximity-services

[71] 3GPP TS 24.333: "Proximity-services (ProSe) Management Objects (MO)"

[72] 3GPP TS 33.303: "Proximity-based Services (ProSe); Security aspects"