8e0
8e0
8e0
0 (2012-01)
Technical Specification
3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Characteristics of the Universal Subscriber Identity Module (USIM) application (Release 8)
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 8
Keywords
UMTS, SIM, card, LTE
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.
2012, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, 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 currently being 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 8
Contents
Contents....................................................................................................................................................3 Foreword.................................................................................................................................................10 Introduction.............................................................................................................................................10 1 Scope...................................................................................................................................................11 2 References............................................................................................................................................11 3 Definitions, symbols, abbreviations and coding conventions...............................................................13
3.1 Definitions............................................................................................................................................................13 3.2 Symbols................................................................................................................................................................13 3.3 Abbreviations.......................................................................................................................................................14 3.4 Coding Conventions.............................................................................................................................................15
3GPP
Release 8
4.2.41 Void 55 4.2.42 EFHiddenkey (Key for hidden phone book entries).......................................................................................55 4.2.43 Void 55 4.2.44 EFBDN (Barred Dialling Numbers)...............................................................................................................55 4.2.45 EFEXT4 (Extension4)....................................................................................................................................56 4.2.46 EFCMI (Comparison Method Information)....................................................................................................56 4.2.47 EFEST (Enabled Services Table)...................................................................................................................57 4.2.48 EFACL (Access Point Name Control List).....................................................................................................57 4.2.49 EFDCK (Depersonalisation Control Keys)....................................................................................................58 4.2.50 EFCNL (Co-operative Network List).............................................................................................................58 4.2.51 EFSTART-HFN (Initialisation values for Hyperframe number)....................................................................60 4.2.52 EFTHRESHOLD (Maximum value of START)............................................................................................60 4.2.53 EFOPLMNwACT (Operator controlled PLMN selector with Access Technology)......................................60 4.2.54 EFHPLMNwAcT (HPLMN selector with Access Technology)....................................................................61 4.2.55 EFARR (Access Rule Reference)...................................................................................................................62 4.2.56 Void 63 4.2.57 EFNETPAR (Network Parameters)................................................................................................................63 4.2.58 EFPNN (PLMN Network Name)....................................................................................................................65 4.2.59 EFOPL (Operator PLMN List).......................................................................................................................66 4.2.60 EFMBDN (Mailbox Dialling Numbers).........................................................................................................67 4.2.61 EFEXT6 (Extension6)....................................................................................................................................68 4.2.62 EFMBI (Mailbox Identifier)...........................................................................................................................68 4.2.63 EFMWIS (Message Waiting Indication Status)..............................................................................................68 4.2.64 EFCFIS (Call Forwarding Indication Status)..................................................................................................70 4.2.65 EFEXT7 (Extension7)....................................................................................................................................71 4.2.66 EFSPDI (Service Provider Display Information)...........................................................................................71 4.2.67 EFMMSN (MMS Notification)......................................................................................................................72 4.2.68 EFEXT8 (Extension 8)...................................................................................................................................74 4.2.69 EFMMSICP (MMS Issuer Connectivity Parameters) ...................................................................................74 4.2.70 EFMMSUP (MMS User Preferences) ...........................................................................................................77 4.2.71 EFMMSUCP (MMS User Connectivity Parameters) ....................................................................................78 4.2.72 EFNIA (Network's Indication of Alerting).....................................................................................................78 4.2.73 EFVGCS (Voice Group Call Service)............................................................................................................79 4.2.74 EFVGCSS (Voice Group Call Service Status)...............................................................................................81 4.2.75 EFVBS (Voice Broadcast Service).................................................................................................................82 4.2.76 EFVBSS (Voice Broadcast Service Status)....................................................................................................83 4.2.77 EFVGCSCA (Voice Group Call Service Ciphering Algorithm)....................................................................84 4.2.78 EFVBSCA (Voice Broadcast Service Ciphering Algorithm).........................................................................85 4.2.79 EFGBABP (GBA Bootstrapping parameters)................................................................................................85 4.2.80 EFMSK (MBMS Service Keys List)..............................................................................................................86 4.2.81 EFMUK (MBMS User Key)...........................................................................................................................87 4.2.82 Void 88 4.2.83 EFGBANL (GBA NAF List)..........................................................................................................................88 4.2.84 EFEHPLMN (Equivalent HPLMN)...............................................................................................................89 4.2.85 EFEHPLMNPI (Equivalent HPLMN Presentation Indication)......................................................................90 4.2.86 EFLRPLMNSI (Last RPLMN Selection Indication)......................................................................................90 4.2.87 EFNAFKCA (NAF Key Centre Address)......................................................................................................91 4.2.88 EFSPNI (Service Provider Name Icon)..........................................................................................................92 4.2.89 EFPNNI (PLMN Network Name Icon)..........................................................................................................93 4.2.90 EFNCP-IP (Network Connectivity Parameters for USIM IP connections)....................................................93 4.2.91 EFEPSLOCI (EPS location information).......................................................................................................96 4.2.92 EFEPSNSC (EPS NAS Security Context)......................................................................................................98 4.3 DFs at the USIM ADF (Application DF) Level................................................................................................100 4.4 Contents of DFs at the USIM ADF (Application DF) level..............................................................................100 4.4.1 Contents of files at the DF SoLSA level.........................................................................................................100 4.4.1.1 EFSAI (SoLSA Access Indicator)...............................................................................................................100 4.4.1.2 EFSLL (SoLSA LSA List)...........................................................................................................................101 4.4.1.3 LSA Descriptor files....................................................................................................................................103 4.4.2 Contents of files at the DF PHONEBOOK level............................................................................................104 4.4.2.1 EFPBR (Phone Book Reference file)..........................................................................................................104 4.4.2.2 EFIAP (Index Administration Phone book).................................................................................................106
3GPP
Release 8
4.4.2.3 EFADN (Abbreviated dialling numbers).....................................................................................................107 4.4.2.4 EFEXT1 (Extension1).................................................................................................................................110 4.4.2.5 EFPBC (Phone Book Control).....................................................................................................................112 4.4.2.6 EFGRP (Grouping file)................................................................................................................................112 4.4.2.7 EFAAS (Additional number Alpha String).................................................................................................113 4.4.2.8 EFGAS (Grouping information Alpha String).............................................................................................114 4.4.2.9 EFANR (Additional Number)......................................................................................................................114 4.4.2.10 EFSNE (Second Name Entry)...................................................................................................................116 4.4.2.11 EFCCP1 (Capability Configuration Parameters 1)....................................................................................116 4.4.2.12 Phone Book Synchronisation.....................................................................................................................117 4.4.2.12.1 EFUID (Unique Identifier)......................................................................................................................117 4.4.2.12.2 EFPSC (Phone book Synchronisation Counter).....................................................................................118 4.4.2.12.3 EFCC (Change Counter).........................................................................................................................119 4.4.2.12.4 EFPUID (Previous Unique Identifier)....................................................................................................119 4.4.2.13 EFEMAIL (e-mail address).......................................................................................................................120 4.4.2.14 Phonebook restrictions...............................................................................................................................121 4.4.3 Contents of files at the DF GSM-ACCESS level (Files required for GSM Access).......................................................................................................121 4.4.3.1 EFKc (GSM Ciphering key Kc)..................................................................................................................122 4.4.3.2 EFKcGPRS (GPRS Ciphering key KcGPRS).............................................................................................122 4.4.3.3 Void 123 4.4.3.4 EFCPBCCH (CPBCCH Information)..........................................................................................................123 4.4.3.5 EFInvScan (Investigation Scan)...................................................................................................................124 4.4.4 Contents of files at the MExE level................................................................................................................124 4.4.4.1 EFMExE-ST (MExE Service table).............................................................................................................125 4.4.4.2 EFORPK (Operator Root Public Key).........................................................................................................125 4.4.4.3 EFARPK (Administrator Root Public Key)................................................................................................127 4.4.4.4 EFTPRPK (Third Party Root Public Key)...................................................................................................128 4.4.4.5 EFTKCDF (Trusted Key/Certificates Data Files).......................................................................................128 4.4.5 Contents of files at the DF WLAN level .......................................................................................................129 4.4.5.1 EFPseudo (Pseudonym)...............................................................................................................................129 4.4.5.2 EFUPLMNWLAN (User controlled PLMN selector for I-WLAN Access)...............................................130 4.4.5.3 EFOPLMNWLAN (Operator controlled PLMN selector for I-WLAN Access).........................................130 4.4.5.4 EFUWSIDL (User controlled WLAN Specific IDentifier List)..................................................................131 4.4.5.5 EFOWSIDL (Operator controlled WLAN Specific IDentifierList)............................................................131 4.4.5.6 EFWRI (WLAN Reauthentication Identity)................................................................................................132 4.4.5.7 EFHWSIDL (Home I-WLAN Specific Identifier List)...............................................................................133 4.4.5.8 EFWEHPLMNPI (I-WLAN Equivalent HPLMN Presentation Indication)................................................133 4.4.5.9 EFWHPI (I-WLAN HPLMN Priority Indication).......................................................................................134 4.4.5.10 EFWLRPLMN (I-WLAN Last Registered PLMN)...................................................................................134 4.4.5.11 EFHPLMNDAI (HPLMN Direct Access Indicator).................................................................................134 4.4.6 Contents of files at the DF HNB level ...........................................................................................................135 4.4.6.1 Introduction..................................................................................................................................................135 4.4.6.2 EFACSGL (Allowed CSG Lists).................................................................................................................135 4.4.6.3 EFCSGT (CSG Type)..................................................................................................................................138 4.4.6.4 EFHNBN (Home NodeB Name).................................................................................................................140 4.5 Contents of EFs at the TELECOM level...........................................................................................................140 4.5.1 EFADN (Abbreviated dialling numbers)........................................................................................................140 4.5.2 EFEXT1 (Extension1)....................................................................................................................................140 4.5.3 EFECCP (Extended Capability Configuration Parameter).............................................................................141 4.5.4 EFSUME (SetUpMenu Elements)..................................................................................................................141 4.5.5 EFARR (Access Rule Reference)...................................................................................................................141 4.5.6 EFICE_DN (In Case of Emergency Dialling Number)...............................................................................141 4.5.7 EFICE_FF (In Case of Emergency Free Format)........................................................................................142 4.5.8 EFPSISMSC (Public Service Identity of the SM-SC)....................................................................................143 4.6 Contents of DFs at the TELECOM level...........................................................................................................143 4.6.1 Contents of files at the DFGRAPHICS level..................................................................................................143 4.6.1.1 EFIMG (Image)............................................................................................................................................143 4.6.1.2 EFIIDF (Image Instance Data Files)............................................................................................................145 4.6.2 Contents of files at the DFPHONEBOOK under the DFTELECOM.............................................................145 4.6.3 Contents of files at the DFMULTIMEDIA level............................................................................................146
3GPP
Release 8
4.6.3.1 EFMML (Multimedia Messages List).........................................................................................................146 4.6.3.2 EFMMDF (Multimedia Messages Data File)..............................................................................................148 4.7 Files of USIM....................................................................................................................................................150
5 Application protocol..........................................................................................................................154
5.1 USIM management procedures..........................................................................................................................154 5.1.1 Initialisation....................................................................................................................................................154 5.1.1.1 USIM application selection..........................................................................................................................154 5.1.1.2 USIM initialisation.......................................................................................................................................154 5.1.1.3 GSM related initialisation procedures..........................................................................................................155 5.1.2 Session termination.........................................................................................................................................156 5.1.2.1 3G session termination.................................................................................................................................156 5.1.2.1.1 GSM termination procedures....................................................................................................................156 5.1.2.2 3G session reset............................................................................................................................................156 5.1.3 USIM application closure...............................................................................................................................156 5.1.4 Emergency call codes......................................................................................................................................156 5.1.5 Language indication........................................................................................................................................157 5.1.6 Administrative information request................................................................................................................157 5.1.7 USIM service table request.............................................................................................................................157 5.1.8 Void 157 5.1.9 UICC presence detection................................................................................................................................157 5.2 USIM security related procedures......................................................................................................................157 5.2.1 Authentication algorithms computation..........................................................................................................157 5.2.2 IMSI request....................................................................................................................................................157 5.2.3 Access control information request.................................................................................................................157 5.2.4 Higher Priority PLMN search period request.................................................................................................157 5.2.5 Location information.......................................................................................................................................157 5.2.6 Cipher and Integrity key.................................................................................................................................157 5.2.7 Forbidden PLMN............................................................................................................................................158 5.2.8 Void 158 5.2.9 User Identity Request......................................................................................................................................158 5.2.10 GSM Cipher key...........................................................................................................................................158 5.2.11 GPRS Cipher key..........................................................................................................................................158 5.2.12 Initialisation value for Hyperframe number..................................................................................................158 5.2.13 Maximum value of START..........................................................................................................................158 5.2.14 HPLMN selector with Access Technology request .....................................................................................158 5.2.15 Packet Switched Location information.........................................................................................................158 5.2.16 Cipher and Integrity key for Packet Switched domain.................................................................................158 5.2.17 LSA information...........................................................................................................................................159 5.2.18 Voice Group Call Services............................................................................................................................159 5.2.19 Voice Broadcast Services..............................................................................................................................159 5.2.20 Generic Bootstrapping architecture (Bootstrap)...........................................................................................159 5.2.21 Generic Bootstrapping architecture (NAF Derivation).................................................................................159 5.2.22 MSK MIKEY Message Reception................................................................................................................159 5.2.23 MTK MIKEY Message Reception...............................................................................................................159 5.2.24 Void 160 5.2.25 EHPLMN request..........................................................................................................................................160 5.2.26 Last RPLMN Selection Indication request...................................................................................................160 5.3 Subscription related procedures.........................................................................................................................160 5.3.1 Phone book procedures...................................................................................................................................160 5.3.1.1 Initialisation.................................................................................................................................................160 5.3.1.2 Creation/Deletion of information.................................................................................................................160 5.3.1.3 Hidden phone book entries .........................................................................................................................161 5.3.2 Dialling numbers.............................................................................................................................................161 5.3.3 Short messages................................................................................................................................................163 5.3.4 Advice of charge.............................................................................................................................................163 5.3.5 Capability configuration parameters...............................................................................................................163 5.3.6 User controlled PLMN selector with Access Technology..............................................................................164 5.3.7 Cell broadcast message identifier...................................................................................................................164 5.3.8 Group identifier level 1...................................................................................................................................164 5.3.9 Group identifier level 2...................................................................................................................................164 5.3.10 Service provider name..................................................................................................................................164
3GPP
Release 8
5.3.11 Enhanced multi level precedence and pre-emption service..........................................................................164 5.3.12 Cell broadcast message identifier ranges......................................................................................................164 5.3.13 Short message status report...........................................................................................................................164 5.3.14 APN Control List..........................................................................................................................................165 5.3.15 Depersonalisation Control Keys...................................................................................................................165 5.3.16 Co-operative Network List............................................................................................................................165 5.3.17 CPBCCH information...................................................................................................................................165 5.3.18 Investigation Scan.........................................................................................................................................166 5.3.19 Enabled Services Table Request...................................................................................................................166 5.3.20 Operator controlled PLMN selector with Access Technology.....................................................................166 5.3.21 HPLMN selector with Access Technology...................................................................................................166 5.3.22 Automatic Answer on eMLPP service..........................................................................................................166 5.3.23 Network Parameter information....................................................................................................................166 5.3.24 PLMN network name....................................................................................................................................166 5.3.25 Operator PLMN List.....................................................................................................................................166 5.3.26 Message Waiting Indication..........................................................................................................................166 5.3.27 Call Forwarding Indication Status................................................................................................................167 5.3.28 Service Provider Display Information..........................................................................................................167 5.3.29 MMS Notifications.......................................................................................................................................167 5.3.30 MMS Issuer Connectivity Parameters..........................................................................................................167 5.3.31 MMS User Preferences.................................................................................................................................168 5.3.32 MMS User Connectivity Parameters............................................................................................................168 5.3.33 Network's indication of alerting....................................................................................................................168 5.3.34 Multimedia Messages Storage......................................................................................................................168 5.3.35 Equivalent HPLMN Presentation Indication request....................................................................................168 5.3.36 NAF Key Centre Address request.................................................................................................................168 5.3.37 Service provider name Icon..........................................................................................................................169 5.3.38 PLMN network name Icon............................................................................................................................169 5.3.39 ICE Information request................................................................................................................................169 5.3.40 eCall Related Procedures..............................................................................................................................169 5.3.40.1 eCall Only support.....................................................................................................................................169 5.3.40.2 eCall and Normal call support ..................................................................................................................169 5.3.41 SM-over-IP...................................................................................................................................................169 5.4 USAT related procedures...................................................................................................................................170 5.4.1 Data Download via SMS-PP...........................................................................................................................170 5.4.2 Image Request.................................................................................................................................................170 5.4.3 Data Download via SMS-CB..........................................................................................................................170 5.4.4 Call Control by USIM.....................................................................................................................................170 5.4.5 MO-SMS control by USIM.............................................................................................................................170 5.4.6 Data Download via USSD and USSD application mode................................................................................170 5.4.7 Additional TERMINAL PROFILE after UICC activation ............................................................................170 5.4.8 Terminal Applications.....................................................................................................................................170 5.4.9 Call control on EPS PDN connection by USIM.............................................................................................171 5.5 MExE related procedures...................................................................................................................................171 5.5.1 MExE ST........................................................................................................................................................171 5.5.2 Operator root public key.................................................................................................................................171 5.5.3 Administrator root public key.........................................................................................................................171 5.5.4 Third Party root public key(s).........................................................................................................................171 5.5.5 Trusted Key/Certificates Data Files................................................................................................................171 5.6 WLAN related procedures................................................................................................................................171 5.6.1 WLAN Selection related Procedures .............................................................................................................171 5.6.2 WLAN PLMN Selection related procedures..................................................................................................172 5.6.3 WLAN access authentication related procedures..........................................................................................172 5.6.4 WLAN access re-authentication related procedures......................................................................................172 5.7 Network Connectivity Parameters for UICC IP connections related procedures.............................................172 5.8 HNB related procedures....................................................................................................................................172 5.8.1 CSG Access Control procedures ....................................................................................................................172 5.8.2 CSG Type related procedures.........................................................................................................................173 5.8.3 HNB name display related procedures...........................................................................................................173
6 Security features.................................................................................................................................173
6.1 Authentication and key agreement procedure....................................................................................................173
3GPP
Release 8
6.2 Cryptographic Functions....................................................................................................................................174 6.3 GSM Conversion Functions...............................................................................................................................174 6.4 User verification and file access conditions.......................................................................................................174
7 USIM Commands..............................................................................................................................174
7.1 AUTHENTICATE.............................................................................................................................................174 7.1.1 Command description.....................................................................................................................................174 7.1.1.1 3G security context......................................................................................................................................175 7.1.1.2 GSM security context..................................................................................................................................176 7.1.1.3 VGCS/VBS security context........................................................................................................................176 7.1.1.4 GBA security context (Bootstrapping Mode)..............................................................................................177 7.1.1.5 GBA security context (NAF Derivation Mode)...........................................................................................177 7.1.1.6 MBMS security context (MSK Update Mode)............................................................................................178 7.1.1.7 Void 180 7.1.1.8 MBMS security context (MTK Generation Mode)......................................................................................180 7.1.1.9 MBMS security context (MSK Deletion Mode)..........................................................................................180 7.1.1.10 MBMS security context (MUK Deletion Mode).......................................................................................180 7.1.1.11 Local Key Establishment security context (Key Derivation mode)..........................................................181 7.1.1.12 Local Key Establishment security context (Key Availability Check mode).............................................182 7.1.2 Command parameters and data.......................................................................................................................182 7.1.2.1 GSM/3G security context............................................................................................................................184 7.1.2.2 VGCS/VBS security context........................................................................................................................184 7.1.2.3 GBA security context (Bootstrapping Mode)..............................................................................................185 7.1.2.4 GBA security context (NAF Derivation Mode)...........................................................................................186 7.1.2.5 MBMS security context (All Modes)..........................................................................................................186 7.1.2.6 Local Key Establishment security context (All Modes)..............................................................................187 7.1.2.6.1 Local Key Establishment security context (Key Derivation mode).........................................................187 7.1.2.6.2 Local Key Establishment security context (Key Availability Check mode)............................................189 7.2 Void 190 7.3 Status Conditions Returned by the USIM..........................................................................................................190 7.3.1 Security management......................................................................................................................................190 7.3.2 Status Words of the Commands......................................................................................................................191 7.4 Optional commands...........................................................................................................................................192
8 Void...................................................................................................................................................192 Annex A (informative): EF changes via Data Download or USAT applications....................193 Annex B (normative): Image Coding Schemes.......................................................................197 B.1 Basic Image Coding Scheme..........................................................................................................197 B.2 Colour Image Coding Scheme........................................................................................................198 B.3 Colour Image Coding Scheme with Transparency.........................................................................199 Annex C (informative): Structure of the Network parameters TLV objects..........................200 Annex D (informative): Tags defined in 31.102........................................................................201 Annex E (informative): Suggested contents of the EFs at pre-personalization......................202 Annex F (informative): Examples of coding of LSA Descriptor files for SoLSA...................206 Annex G (informative): Phonebook Example...........................................................................207
3GPP
Release 8
Annex H (normative): List of SFI Values................................................................................210 H.1 List of SFI Values at the USIM ADF Level...................................................................................210 H.2 List of SFI Values at the DF GSM-ACCESS Level.......................................................................210 H.3 List of SFI Values at the DF WLAN Level....................................................................................211 H.4 List of SFI Values at the DF HNB Level........................................................................................211 Annex I (informative): USIM Application Session Activation/Termination.........................212 Annex J (informative): Example of MMS coding ...................................................................213
J.1 Coding example for MMS User Preferences .....................................................................................................213 J.2 Coding Example for MMS Issuer/User Connectivity Parameters ....................................................................213
3GPP
Release 8
10
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 8
11
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.
References
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] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] 3GPP TS 21.111: "USIM and IC Card Requirements". 3GPP TS 22.011: "Service accessibility". 3GPP TS 22.024: "Description of Charge Advice Information (CAI)". 3GPP TS 22.030: "Man-Machine Interface (MMI) of the User Equipment (UE)". 3GPP TS 23.038: "Alphabets and language". 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)". 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". 3GPP TS 22.067: "enhanced Multi Level Precedence and Pre-emption service (eMLPP) Stage 1". 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage 3". 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface". 3GPP TS 31.101: "UICC-Terminal Interface, Physical and Logical Characteristics". 3GPP TS 31.111: "USIM Application Toolkit (USAT)".
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
3GPP
Release 8
12
[13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26] [27] [28] [29] [30] [31] [32] [33] [34] [35] [36] [37] [38] [39] [40] [41] [42] [43]
3GPP TS 33.102: "3GPP Security; Security Architecture". 3GPP TS 33.103: "3GPP Security; Integration Guidelines". 3GPP TS 22.086: "Advice of charge (AoC) Supplementary Services - Stage 1". 3GPP TS 23.041: "Technical realization of Cell Broadcast (CB)". 3GPP TS 02.07: "Mobile Stations (MS) features". 3GPP TS 51.011 Release 4: "Specification of the Subscriber Identity Module Mobile Equipment (SIM ME) interface". ISO 639 (1988): "Code for the representation of names of languages". ISO/IEC 7816-4: "Integrated circuit cards, Part 4: Organization, security and commands for interchange". Void. ITU-T Recommendation E.164: "The international public telecommunication numbering plan". 3GPP TS 23.073: "Support of Localised Service Area (SoLSA); Stage 2". 3GPP TS 22.101: "Service aspects; service principles". 3GPP TS 23.003: "Numbering, Addressing and Identification". Void. 3GPP TS 22.022: "Personalisation of Mobile Equipment (ME); Mobile functionality specification". 3GPP TS 44.018 "Mobile Interface Layer3 Specification, Radio Resource control protocol". 3GPP TS 23.022: "Functions related to Mobile Station (MS) in idle mode and group receive mode". 3GPP TS 23.057: "Mobile Execution Environment (MExE);Functional description; Stage 2". 3GPP TS 23.122: "NAS Functions related to Mobile Station (MS) in idle mode". Void. 3GPP TS 25.101: "UE Radio Transmission and Reception (FDD)". 3GPP TS 45.005: "Radio Transmission and Reception". ISO/IEC 8825 (1990): "Information technology; Open Systems Interconnection; Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1)". 3GPP TS 23.097: "Multiple Subscriber Profile (MSP)". Void. 3GPP TS 23.140 Release 6: "Multimedia Messaging Service (MMS); Functional description; stage 2". ETSI TS 102 222 V7.1.0: "Administrative commands for telecommunications applications". 3GPP TS 24.234: "3GPP System to WLAN Interworking; UE to Network protocols;Stage 3". 3GPP TS 33.234: "3G Security; Wireless Local Area Network (WLAN) interworking security". 3GPP TS 33.220: "Generic Authentication Architecture (GAA); Generic bootstrapping architecture". 3GPP TS 33.246: "Security of Multimedia Broadcast/Multicast Service".
3GPP
Release 8
13
[44] [45] [46] [47] [48] [49] [50] [51] [52] [53] [54] [55]
3GPP TS 43.020: "Technical Specification Group Services and system Aspects; Security related network functions" X.S0016-000-A v1.0: "3GPP2 Multimedia Messaging System MMS Specification Overview, Revision A" 3GPP TS 43.068: "Technical Specification Group Core Network; Voice Group Call Service (VGCS); Stage 2". 3GPP TS 33.110: "Key establishment between a Universal Integrated Circuit Card (UICC) and a terminal". IETF RFC 3629 (2003): "UTF-8, a transformation format of ISO 10646". Open Mobile Alliance; OMA-TS-BCAST_SvcCntProtection URL: http://www.openmobilealliance.org/ ETSI TS TS 102 483 V8.1.0: "UICC-Terminal interface; Internet Protocol connectivity between UICC and Terminal". 3GPP TS 24.301: "Technical Specification Group Core Network and Terminals; Non-AccessStratum (NAS) protocol for Evolved Packet Systems (EPS): Stage 3". 3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture". 3GPP TS 24.341: "Support of SMS over IP networks; Stage 3" IETF RFC 3261: "SIP: Session Initiation Protocol". IETF RFC 3629 (2003): "UTF-8, a transformation format of ISO 10646".
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. 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
3GPP
Release 8
14
f1 f1* f2 f3 f4 f5
Exclusive OR Message authentication function used to compute MAC 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 Message authentication function used to compute RES and XRES Key generating function used to compute CK Key generating function used to compute IK Key generating function used to compute AK
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply: 3GPP AC ACL ADF AID AK ALW AMF AoC APN ASME ASN.1 AuC AUTN BDN BER-TLV B-TID CCP CK CLI CNL CPBCCH CS DCK DF DO EF EPS FCP FFS GSM HE HNB ICC ICE ICI ICT ID IDi IDr IEI IK IMSI K KC KSI LI LSB 3rd Generation Partnership Project Access Condition APN Control List Application Dedicated File Application IDentifier Anonymity key ALWays Authentication Management Field Advice of Charge Access Point Name Access Security Management Entity Abstract Syntax Notation One Authentication Centre Authentication token Barred Dialling Number Basic Encoding Rule - TLV Bootstrapping Transaction IDentifier Capability Configuration Parameter Cipher key Calling Line Identifier Co-operative Network List COMPACT Packet BCCH Circuit switched Depersonalisation Control Keys Dedicated File Data Object Elementary File Evolved Packet System File Control Parameters For Further Study Global System for Mobile communications Home Environment Home NodeB Integrated Circuit Card In Case of Emergency Incoming Call Information Incoming Call Timer IDentifier Identity of the initiator Identity of the responder Information Element Identifier Integrity key International Mobile Subscriber Identity USIM Individual key Cryptographic key used by the cipher A5 Key Set Identifier Language Indication Least Significant Bit
3GPP
Release 8
15
MAC MAC-A MAC-I MBMS MCC MExE MF MGV-F MIKEY MM MMI MMS MNC MODE MSB MSK MTK MUK NEV NPI OCI OCT PBID PIN PL PS PS_DO RAND RANDMS RES RFU RST SDN SE SEQp SFI SGSN SN SQN SRES SW TLV USAT USIM VLR WLAN WSID XRES
Message authentication code MAC used for authentication and key agreement MAC used for data integrity of signalling messages Multimedia Broadcast/Multicast Service Mobile Country Code Mobile Execution Environment Master File MTK Generation and Validation Function Multimedia Internet KEYing Multimedia Message Man Machine Interface Multimedia Messaging Service Mobile Network Code Indication packet switched/circuit switched mode Most Significant Bit MBMS Service Key MBMS Traffic Key MBMS User Key NEVer Numbering Plan Identifier Outgoing Call Information Outgoing Call Timer Phonebook Identifier Personal Identification Number Preferred Languages Packet switched PIN Status Data Object Random challenge Random challenge stored in the USIM User response Reserved for Future Use Reset Service dialling number Security Environment Sequence number for MGV-F stored in the USIM Short EF Identifier Serving GPRS Support Node Serving Network Sequence number Signed RESponse calculated by a USIM Status Word Tag Length Value USIM Application Toolkit Universal Subscriber Identity Module Visitor Location Register Wireless Local Area Network WLAN Specific Identifier Expected user RESponse
3GPP
Release 8
16
This clause specifies the EFs for the 3GPP session defining access conditions, data items and coding. A data item is a part of an EF which represents a complete logical entity, e.g. the alpha tag in an EFADN record. A file is associated with attributes that depending of the file type indicates how data is to be accessed e.g. file size, record length etc. Although in the present document some files and data items stored in a file are indicated as having a fixed length; when reading such structures the terminal shall derive the length of the data item from the attributes provided in the file information i.e. not use the fixed value specified for the file in the present document. Although the terminal is able to read the entire structure it should only use those elements in the data item which is recognised by the terminal. For any EF, when the SFI is not indicated in the description of the file it is not allowed to assign an SFI. If in the description of the file an SFI value is indicated the file shall support SFI. The SFI value shall be assigned by the card issuer. It is mandatory for EFs stating an SFI value ('YY') in the description of their structure to provide an SFI. For files where in the file description the SFI is indicated as 'Optional' the file may support an SFI. For an overview containing all files see figures 4.1 and 4.2.
3GPP
Release 8
17
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' SFI: '02' File size: 2n bytes, (n 1) Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to 2 3 to 4 2n-1 to 2n Structure: transparent Update activity: low ALW PIN ADM ADM M/O M O O Length 2 bytes 2 bytes 2 bytes Optional
Description 1st language code (highest priority). 2nd language code Nth language code (lowest priority).
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'.
Update activity: low PIN ADM ADM ADM Description M/O M M Length 1 byte 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:
3GPP
Release 8
18
b8
B7
b6
B5
b4
b3
b2
b8
b7
b6
B5
b4 b3
b2
etc.
Update activity: high PIN PIN ADM ADM M/O M M M Length 1 byte 16 bytes 16 bytes
- 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.
3GPP
Release 8
19
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.
Identifier: '6F09' SFI: '09' File size: 33 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 2 to 17 18 to 33 Structure: transparent Mandatory
Update activity: high PIN PIN ADM ADM M/O M M M Length 1 byte 16 bytes 16 bytes
Description Key set identifier KSIPS Ciphering key CKPS Integrity key IKPS
- 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.
3GPP
Release 8
20
Identifier: '6F60' SFI: '0A' File size: 5n (where n 8 bytes) Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to 3 4 to 5 6 to 8 9 to 10 : 36 to 38 39 to 40 41 to 43 44 to 45 : (5n-4) to (5n-2) (5n-1) to 5n
Structure: transparent Update activity: low PIN PIN ADM ADM M/O M M M M M M O O O O
Optional
Description 1st PLMN (highest priority) 1st PLMN Access Technology Identifier 2nd PLMN 2nd PLMN Access Technology Identifier : 8th PLMN 8th PLMN Access Technology Identifier 9th PLMN 9th PLMN Access Technology Identifier : Nth PLMN (lowest priority) Nth PLMN Access Technology Identifier
Length 3 bytes 2 bytes 3 bytes 2 bytes 3 bytes 2 bytes 3 bytes 2 bytes 3 bytes 2 bytes
- PLMN Contents: - Mobile Country Code (MCC) followed by the Mobile Network Code (MNC). Coding: - according to TS 24.008 [9]. - 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. Byte5n-1:
b8 b7 b6 b5 b4 b3 b2 b1 RFU RFU RFU RFU RFU RFU E-UTRAN UTRAN
Byte 5n:
b8 b7 b6 b5 b4 b3 b2 b1 RFU RFU RFU RFU cdma2000 1xRTT cdma2000 HRPD GSM COMPACT GSM
3GPP
Release 8
21
Identifier: '6F31' SFI: '12' File size: 1 byte Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 Time interval
Structure: transparent
Mandatory
Update activity: low PIN ADM ADM ADM Description M/O M Length 1 byte
- Time interval. Contents: the time interval between two searches. Coding: the time interval is coded in integer multiples of n minutes. The range is from n minutes to a maximum value. The value '00' indicates that no attempts shall be made to search for any higher priority PLMN. The encoding is: '00': '01': '02': : : 'YZ': No higher priority PLMN search attempts; n minutes; 2n minutes; (16Y+Z)n minutes (maximum value).
For specification of the integer timer interval n, the maximum value and the default period refer to TS 22.011 [2].
- 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 8
22
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.
3GPP
Release 8
23
3GPP
Release 8 Identifier: '6F38' SFI: '04' File size: X bytes, (X 1) Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 2 3 4 etc.
24 Structure: transparent
Update activity: low PIN ADM ADM ADM M/O M O O O Length 1 byte 1 byte 1 byte 1 byte
Description Services n1 to n8 Services n9 to n16 Services n17 to n24 Services n25 to n32
3GPP
25
3GPP
Release 8
26
3GPP
27
Service n1: Service n2: Service n3: Service n4: Service n5: Service n6: Service n7: Service n8: Service n9: Service n10: Service n11: Service n12: Service n13: Service n14: Service n15: Service n16: Service n17: Service n18: Service n19: Service n20: Service n21: Service n22: Service n23: Service n24: Service n25: Service n26: Service n27: Service n28: Service n29: Service n30: Service n31: Service n32: Service n33: Service n34: Service n35: Service n36: Service n37: Service n38: Service n39: Service n40: Service n41: Service n42: Service n43: Service n44: Service n45: Service n46: Service n47: Service n48: Service n49: Service n50: Service n51: Service n52 Service n53 Service n54 Service n55 Service n56 Service n57 Service n58 Service n59 Service n60 Service n61 Service n62 Service n63 Service n64 Service n65 Service n66 Service n67 Service n68
Local Phone Book Fixed Dialling Numbers (FDN) Extension 2 Service Dialling Numbers (SDN) Extension3 Barred Dialling Numbers (BDN) Extension4 Outgoing Call Information (OCI and OCT) Incoming Call Information (ICI and ICT) Short Message Storage (SMS) Short Message Status Reports (SMSR) Short Message Service Parameters (SMSP) Advice of Charge (AoC) Capability Configuration Parameters 2 (CCP2) Cell Broadcast Message Identifier Cell Broadcast Message Identifier Ranges Group Identifier Level 1 Group Identifier Level 2 Service Provider Name User controlled PLMN selector with Access Technology MSISDN Image (IMG) Support of Localised Service Areas (SoLSA) Enhanced Multi-Level Precedence and Pre-emption Service Automatic Answer for eMLPP RFU GSM Access Data download via SMS-PP Data download via SMS-CB Call Control by USIM MO-SMS Control by USIM RUN AT COMMAND command shall be set to '1' Enabled Services Table APN Control List (ACL) Depersonalisation Control Keys Co-operative Network List GSM security context CPBCCH Information Investigation Scan MExE Operator controlled PLMN selector with Access Technology HPLMN selector with Access Technology Extension 5 PLMN Network Name Operator PLMN List Mailbox Dialling Numbers Message Waiting Indication Status Call Forwarding Indication Status Reserved and shall be ignored Service Provider Display Information Multimedia Messaging Service (MMS) Extension 8 Call control on GPRS by USIM MMS User Connectivity Parameters Network's indication of alerting in the MS (NIA) VGCS Group Identifier List (EFVGCS and EFVGCSS) VBS Group Identifier List (EFVBS and EFVBSS) Pseudonym User Controlled PLMN selector for I-WLAN access Operator Controlled PLMN selector for I-WLAN access User controlled WSID list Operator controlled WSID list VGCS security VBS security WLAN Reauthentication Identity Multimedia Messages Storage Generic Bootstrapping Architecture (GBA)
3GPP
Release 8 Service n69 Service n70 Service n71 Service n72 Service n73 Service n74 Service n75 Service n76 Service n77 Service n78 Service n79 Service n80 Service n81 Service n82 Service n83 Service n84 Service n85 Service n86 Service n87 Service n88 Service n89 Service n90 Service n91
28
MBMS security Data download via USSD and USSD application mode Equivalent HPLMN Additional TERMINAL PROFILE after UICC activation Equivalent HPLMN Presentation Indication Last RPLMN Selection Indication OMA BCAST Smart Card Profile GBA-based Local Key Establishment Mechanism Terminal Applications Service Provider Name Icon PLMN Network Name Icon Connectivity Parameters for USIM IP connections Home I-WLAN Specific Identifier List I-WLAN Equivalent HPLMN Presentation Indication I-WLAN HPLMN Priority Indication I-WLAN Last Registered PLMN EPS Mobility Management Information Allowed CSG Lists and corresponding indications Call control on EPS PDN connection by USIM HPLMN Direct Access eCall Data Not applicable (used in later release) Support for SM-over-IP
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. 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 Service Service Service Service Service Service Service n1 n2 n3 n4 n5 n6 n7 n8
Second byte:
b8 b7 b6 B5 B4 b3 b2 b1 Service Service Service Service Service Service Service Service n9 n10 n11 n12 n13 n14 n15 n16
etc.
3GPP
Release 8
29
Update activity: high PIN PIN/PIN2 (fixed during administrative management) PIN ADM ADM
Bytes Description M/O Length 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.
3GPP
Release 8
30
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' File size: n bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to n Structure: transparent Optional Update activity: low PIN ADM ADM ADM M/O O Length n bytes
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.
- 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:
3GPP
Release 8
31
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].
- 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 23 b3 22 b2 21 b1 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:
3GPP
Release 8
32
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.
1 to 2
3 to 4 : 2n-1 to 2n
- 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'.
Update activity: low PIN ADM ADM ADM M/O M Length 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.
3GPP
Release 8
33
Byte 1:
b8 15 b7 14 b6 13 b5 12 b4 11 b3 10 b2 09 b1 08 Number of the ACC (except for bit b3)
Byte 2:
b8 07 b7 06 b6 05 b5 04 b4 03 b3 02 b2 01 b1 00 Number of the ACC
Update activity: low PIN PIN ADM ADM Description M/O M M M M : O Length 3 bytes 3 bytes 3 bytes 3 bytes : 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'.
3GPP
Release 8
34
Temporary Mobile Subscriber Identity (TMSI); Location Area Information (LAI); Location update status.
Update activity: high PIN PIN ADM ADM M/O M M M M Length 4 bytes 5 bytes 1 byte 1 byte
- TMSI Contents: Temporary Mobile Subscriber Identity. Coding: according to TS 24.008 [9].
B8 MSB b7 b6 b5 b4 B3 b2 b1
- LAI Contents: Location Area Information. Coding: according to TS 24.008 [9]. Byte 5: first byte of LAI
b8 MSB b7 b6 b5 b4 b3 b2 b1
- 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]).
3GPP
Release 8
35
Update activity: low ALW ADM ADM ADM M/O M M M O Length 1 byte 2 bytes 1 byte X bytes
Description UE operation mode Additional information length of MNC in the IMSI RFU
- 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)
b1 is used to control the ciphering indicator feature as specified in TS 22.101 [24]. - ME manufacturer specific information (if b2=1 in byte 1):
3GPP
Release 8
36
- 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)
If service n 29 is "available", this file shall be present. 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.
Identifier: '6F48' SFI: '0E' File size: 2n bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to 2 3 to 4 : 2n-1 to 2n Structure: transparent Update activity: low PIN ADM ADM ADM M/O O O : O Length 2 bytes 2 bytes : 2 bytes Optional
- 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'.
3GPP
Release 8
37
Update activity: low ALW ADM ADM ADM M/O M O M Length 3 bytes X bytes 1 byte
Description Emergency Call Code Emergency Call Code Alpha Identifier Emergency Service Category
- 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 :: :: MSB LSB : : MSB of Digit 1 of Digit 1 of Digit 2 of Digit 2
Byte 2:
b8 b7 b6 b5 b4 b3 b2 b1 LSB : : MSB LSB : : MSB of Digit 3 of Digit 3 of Digit 4 of Digit 4
Byte 3:
b8 b7 b6 b5 b4 b3 b2 b1 LSB : : MSB LSB : : MSB of Digit 5 of Digit 5 of Digit 6 of Digit 6
3GPP
Release 8
38
- 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].
Description CB Message Identifier Range 1 CB Message Identifier Range 2 : CB Message Identifier Range n
- 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'.
3GPP
Release 8
39
Identifier: '6F73' SFI: '0C' File size: 14 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to 4 5 to 7 8 to13 14
Structure: transparent
Mandatory
Update activity: high PIN PIN ADM ADM M/O M M M M Length 4 bytes 3 bytes 6 bytes 1 byte
Description P-TMSI P-TMSI signature value RAI Routing Area update status
- P-TMSI. Contents: Packet Temporary Mobile Subscriber Identity. Coding: according to TS 24.008 [9]. Byte 1: first byte of P-TMSI
b8 MSB b7 B6 B5 B4 B3 b2 b1
- P-TMSI signature value. Contents: Packet Temporary Mobile Subscriber Identity signature value. Coding: according to TS 24.008 [9]. Byte 5: first byte of P-TMSI signature value.
b8 MSB b7 B6 B5 B4 B3 b2 b1
- RAI Contents: Routing Area Information. Coding: according to TS 24.008 [9]. Byte 8: first byte of RAI
b8 MSB b7 b6 b5 b4 b3 b2 b1
- Routing Area update status. Contents: status of routing area update according to TS 24.008 [9].
3GPP
Release 8
40
Coding: byte 14: b3 b2 b1. 0 0 0 : 0 0 1 : 0 1 0 : 0 1 1 : 1 1 1 : Bits b4 to b8 are RFU (see TS 31.101 [11]). Bits: updated. not updated. PLMN not allowed. Routing Area not allowed. reserved.
Description Alpha Identifier Length of BCD number/SSC contents TON and NPI Dialling Number/SSC String Capability/Configuration2 Record Identifier Extension2 Record Identifier
For contents and coding of all data items see the respective data items of the EFADN (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 SMS when FDN is enabled. For the FDN procedures related to SMS see TS 22.101 [24] and TS 31.111 [12]. NOTE: The value of X (the number of bytes in the alpha-identifier) may be different to the length denoted X in EFADN.
3GPP
Release 8
41
Identifier: '6F3C' Record length: 176 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 2 to 176 Status Remainder
Structure: linear fixed Optional Update activity: low PIN PIN ADM ADM Description M/O M M Length 1 byte 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 X X 0 0 1 b2 X X 0 1 1 b1 0 1 1 1 1 free space used space message received by UE from network; message read message received by UE from network; message to be read UE originating message; message to be sent
b8
b7
b6
b5 X 0 0 1 1
b4 X 0 1 0 1
b3 1 1 1 1 1
b2 0 0 0 0 0
b1 1 1 1 1 1 UE originating message; message sent to Status report not requested Status report requested but not (yet) Status report requested, received but in EF-SMSR; Status report requested, received and in EF-SMSR; RFU (see TS 31.101 [11]) the network: received; not stored stored
- 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. 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: message to be sent: message sent to the network: Value of the TP-message-reference: 'FF'. 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'.
3GPP
Release 8
42
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.
Description Alpha Identifier Length of BCD number/SSC contents TON and NPI Dialling Number/SSC String Capability/Configuration2 Record Identifier Extension5 Record Identifier
For contents and coding of all data items see the respective data items of EFADN. 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. NOTE: The value of X (the number of bytes in the alpha-identifier) may be different to the length denoted X in EFADN.
3GPP
Release 8
43
Identifier: '6F42' Record length: 28+Y bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to Y Y+1 Y+2 to Y+13 Y+14 to Y+25 Y+26 Y+27 Y+28
Structure: linear fixed Optional Update activity: low PIN PIN ADM ADM M/O O M M M M M M Length Y bytes 1 byte 12 bytes 12 bytes 1 byte 1 byte 1 byte
Description Alpha-Identifier Parameter Indicators TP-Destination Address TS-Service Centre Address TP-Protocol Identifier TP-Data Coding Scheme TP-Validity Period
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. 7 reserved, set to 1. 8 reserved, set to 1. Bit value 0 1 Meaning. Parameter present. Parameter absent.
- TP-Destination Address. Contents and Coding: as defined for SM-TL address fields in TS 23.040 [6]. - TP-Service Centre Address. Contents and Coding: as defined for RP-Destination address Centre Address in TS 24.011 [10]. - TP-Protocol Identifier. Contents and Coding: as defined in TS 23.040 [6]. TP-Data Coding Scheme.
3GPP
Release 8
44
Contents and Coding: as defined in TS 23.038 [5]. - TP-Validity Period. Contents and Coding: as defined in TS 23.040 [6] for the relative time format.
Description Last Used TP-MR SMS "Memory Cap. Exceeded" Not. Flag RFU
- 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.
3GPP
Release 8
45
Identifier: '6F49' Record length: X+14 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1-X X+1 X+2 X+3 to X+12 X+13 X+14
Structure: linear fixed Optional Update activity: low PIN ADM ADM ADM M/O O M M M M M Length X bytes 1 bytes 1 byte 10 bytes 1 byte 1 byte
Description Alpha identifier Length of BCD number/SSC contents TON and NPI Dialling Number/SSC String Capability/Configuration2 Record Identifier Extension3 Record Identifier
For contents and coding of all data items see the respective data items of the EFADN (clause 4.4.2.3), with the exception that extension records are stored in the EFEXT3 and capability/configuration parameters are stored in EFCCP2. NOTE: The value of X (the number of bytes in the alpha-identifier) may be different to the length denoted X in EFADN.
3GPP
Release 8
46
- 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'.
3GPP
Release 8
47
The first byte of this link is used to identify clearly the phone book location either global (i.e. under DFTELECOM) 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' SFI: '14' Record length: X+28 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to X X+1 X+2 X+3 to X+12 X+13 X+14 X+15 to X+21 X+22 to X+24 X+25 X+26 to X+28 PIN PIN ADM ADM M/O O M M M M M M M M M Length X bytes 1 byte 1 byte 10 bytes 1 byte 1 byte 7 bytes 3 bytes 1 byte 3 bytes Structure: Cyclic Optional
Description Alpha Identifier Length of BCD number contents TON and NPI Incoming Call Number Capability/Configuration2 Record Identifier Extension5 Record Identifier Incoming call date and time (see detail 1) Incoming call duration (see detail 2) Incoming call status (see detail 3) Link to phone book entry (see detail 4)
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
3GPP
Release 8
48
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
3GPP
Release 8
49
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:
b8 b7 b6 b5 b4 b3 b2 b1 0 Global Phone Book (DFTELECOM) 1 Local Phone Book (USIM Specific) RFU
3GPP
Release 8
50
Description Alpha Identifier Length of BCD number/SSC contents TON and NPI Outgoing Call Number/SSC String Capability/Configuration2 Record Identifier Extension5 Record Identifier Outgoing call date and time Outgoing call duration Link to Phone Book Entry
NOTE:
When the contents are invalid, they are filled with 'FF'.
3GPP
Release 8
51
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
3GPP
Release 8
52
Structure of EFOCT
Identifier: '6F83' Record length: 3 bytes Access Conditions: READ UPDATE INCREASE DEACTIVATE ACTIVATE Bytes 1 to 3 Structure: cyclic Optional Update activity: high PIN PIN/PIN2 (fixed during administrative management) PIN ADM ADM M/O M Length 3 bytes
Contents and Coding: see TS 24.008 [9]. The Information Element Identity (IEI) shall be excluded, i.e. the first byte of the EFCCP2 record
3GPP
Release 8
53
shall be Length of the bearer capability contents. - unused bytes are filled with 'FF'.
- 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 priority priority priority priority priority priority 0 level level level level level level level A B 0 1 2 3 4
NOTE:
Priority levels A and B can not be subscribed to (see TS 22.067 [5] for details). If priority levels 0, 1 and 2 are subscribed to, EFeMLPP shall be coded '1C'.
EXAMPLE 1:
- 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 8
54
b8
b7
b6
b5
b4
b3
b2
b1 fast fast fast fast fast fast fast 0 call call call call call call call set-up set-up set-up set-up set-up set-up set-up condition condition condition condition condition condition condition for for for for for for for priority priority priority priority priority priority priority level level level level level level level A B 0 1 2 3 4
EXAMPLE 2:
If fast call set-up is allowed for priority levels 0, and 1, then byte 2 of EFeMLPP is coded '0C'.
- 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 Automatic Automatic Automatic Automatic Automatic Automatic 0 answer answer answer answer answer answer answer priority priority priority priority priority priority priority for for for for for for for priority priority priority priority priority priority priority level level level level level level level A B 0 1 2 3 4
EXAMPLE:
If automatic answer is allowed for incoming calls with priority levels A, 0 and 1, then EFAAeM is coded '0D'.
3GPP
Release 8
55
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' File size: 4 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to 4 Hidden Key Structure: transparent Optional Update activity: low PIN PIN ADM ADM Description M/O M Length 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.
Description Alpha Identifier Length of BCD number/SSC contents TON and NPI Dialling Number/SSC String Capability/Configuration2 Record Identifier Extension4 Record Identifier Comparison Method Pointer
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 8
56
NOTE:
The value of X (the number of bytes in the alpha-identifier) may be different to the length denoted X in EFADN.
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 8
57
-Services Contents:
Fixed Dialling Numbers (FDN) Barred Dialling Numbers (BDN) 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 Service Service Service Service Service Service Service n1 n2 n3 n4 n5 n6 n7 n8
etc.
3GPP
Release 8
58
Identifier: '6F57' File size: X bytes (X>1) Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 2 to X Number of APNs APN TLVs
Structure: transparent Optional Update activity: low PIN PIN2 ADM ADM Description M/O M M Length 1 byte X-1 byte
For contents and coding of APN-TLV values see TS 23.003 [25]. The tag value of the APN-TLV shall be 'DD'. "Network provided APN" is coded with a TLV object of length zero.
Description 8 digits of network de-personalization control key 8 digits of network subset de-personalization control key 8 digits of service provider de-personalization control key 8 digits of corporate de-personalization control key
3GPP
Release 8
59
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 : : MS LS : : MS bit of network subset digit 1 bit of network subset digit 1 bit of network subset digit 2 bit of network subset digit 2
Byte 5:
b8 b7 b6 b5 b4 b3 b2 b1 LS : : MS LS : : MS bit of service provider digit 1 bit of service provider digit 1 bit of service provider digit 2 bit of service provider digit 2
Byte 6:
b8 b7 b6 b5 b4 b3 b2 b1 LS : : MS LS : : MS bit of corporate digit 1 bit of corporate digit 1 bit of corporate digit 2 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 8
60
Update activity: high PIN PIN ADM ADM Description M/O M M Length 3 bytes 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. -
Update activity: low PIN ADM ADM ADM M/O M Length 3 bytes
3GPP
Release 8
61
Identifier: '6F61' SFI: '11' File size: 5n bytes , (n 8) Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to 3 4 to 5 : 36 to 38 39 to 40 41 to 43 44 to 45 : (5n-4) to (5n-2) (5n-1) to 5n
Structure: transparent Update activity: low PIN ADM ADM ADM M/O M M M M O O O O
Optional
Description 1st PLMN (highest priority) 1st PLMN Access Technology Identifier : 8th PLMN 8th PLMN Access Technology Identifier 9th PLMN 9th PLMN Access Technology Identifier : Nth PLMN (lowest priority) Nth PLMN Access Technology Identifier
- PLMN. Contents: - Mobile Country Code (MCC) followed by the Mobile Network Code (MNC). Coding: - according to TS 24.008 [9]. - Access Technology Identifier: Coding: - See EFPLMNwACT for coding.
Description 1st PLMN (highest priority) 1st PLMN Access Technology Identifier 2nd PLMN 2nd PLMN Access Technology Identifier : nth PLMN (lowest priority) nth PLMN Access Technology Identifier
- PLMN Contents: Mobile Country Code (MCC) followed by the Mobile Network Code (MNC). Coding: according to TS 24.008 [47].
3GPP
Release 8
62
- 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.
Update activity: low ALW ADM ADM ADM M/O M Length 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 8
63
3GPP
Release 8
64
Description GSM Cell Information Tag Camping Frequency Tag Camping Frequency Information Neighbour Frequency Tag Neighbour Frequency Information FDD Cell Information Tag Intra Frequency Information Tag Scrambling code Information Inter Frequency Information Tag Scrambling code information TDD Frequency information Tag Intra Frequency Information Tag Cell parameters ID Inter Frequency Information Tag Cell parameters ID
Value 'A0' '80' '81' 'A1' '80' '81' 'A2' '80' '81'
Information Element size bytes 1 1 2 1 2*m (8 <= m <= 32) 1 1 2*m (8 <= m <= 32) 1 2*(n1+n2+n3) (8 <= n1+n2+n3 <= 32) 1 1 2*m (8 <= m <= 32) 1 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 GSM Cell Information Tag Length Current camped cell BCCH frequency information tag Length Current camped BCCH frequency Neighbour Cell BCCH Frequency information tag Length Neighbour BCCH carrier frequencies Value 'A0'' '4+ (2+2*m) (<=70) ' '80' '02' '81' 2*m (=< 32) M/O M M M M M O O O Length 1 1 1 1 2 1 1 2*m (8 <= m <= 32)
FDD Cell Information. If tag 'A1' is present in this EF the content of this TLV is as follows:
Description FDD Cell Information Tag Length Value 'A1' 4+(2*m) +(4+2*n1)+(4+2* n2)+(4+2*n3) (<=144) '80' 2+2*m M/O M M Length 1 1
FDD Intra Frequency information tag Length Intra Frequency carrier frequency Intra Frequency scrambling codes
M M M M
FDD Inter Frequency information tag '81' O (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 8
65
TDD Cell Information: If tag 'A2' is present in this EF the content of this TLV is as follows:
Description TDD Cell Information Tag Length Value 'A2' 4+(2*m) +(4+2*n1)+(4+2* n2)+(4+2*n3) (<=144) '80' 2+2*m M/O M M Length 1 1
TDD Intra Frequency information tag Length Intra Frequency carrier frequency Intra Frequency scrambling codes
M M M M
TDD Inter Frequency information tag '81' O (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
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 8
66
Identifier: '6FC6' SFI: '1A' Record length: X bytes, (X 8) Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to 7 8
Update activity: low ALWAYS ADM ADM ADM M/O M M Length 7 bytes 1 byte
Description Location Area Identity/Tracking Area Identity PLMN Network Name Record Identifier
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
3GPP
Release 8
67
LAC/TAC : according to TS 24.008 [9]/TS 24.301 [51] 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.
Description Alpha Identifier Length of BCD number/SSC contents TON and NPI Dialling Number/SSC contents Capability/Configuration2 Record Identifier Extension 6 Record Identifier
For contents and coding of all data items see the respective data items of the EFADN (clause 4.4.2.3), with the exception that extension records are stored in the EFEXT6 and with the exception that Capability/Configuration parameters are stored in the EFCCP2. NOTE: The value of X (the number of bytes in the alpha-identifier) may be different to the length denoted X in EFADN.
3GPP
Release 8
68
Description Mailbox Dialling Number Identifier Voicemail Mailbox Dialling Number Identifier Fax Mailbox Dialling Number Identifier Electronic Mail Mailbox Dialling Number Identifier Other Mailbox Dialling Number Identifier Videomail
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.
3GPP
Release 8
69
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' Record length: X bytes, (X 5) Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 2 3 4 5 6 Structure: Linear fixed Optional Update activity: high PIN PIN ADM ADM M/O M M M M M O Length 1 byte 1 byte 1 byte 1 byte 1 byte 1 byte
Description Message Waiting Indicator Status Number of Voicemail Messages Waiting Number of Fax Messages Waiting Number of Electronic Mail Messages Waiting Number of Other Messages Waiting Number of Videomail Messages waiting
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 Message Message Message Message RFU Waiting Waiting Waiting Waiting Waiting Indication Indication Indication Indication Indication Status Status Status Status Status Voicemail Fax Electronic Mail Other Videomail
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 8
70
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
If service n49 is "available", this file shall be present. 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' Record length: 16 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 2 3 4 5 to 14 15 16 Structure: Linear Fixed Optional Update activity: low PIN PIN ADM ADM M/O M M M M M M M Length 1 byte 1 byte 1 byte 1 byte 10 bytes 1 byte 1 byte
Description MSP number CFU indicator status Length of BCD number TON and NPI Dialling Number Capability/Configuration2 Record Identifier Extension 7 Record Identifier
NOTE:
For contents and coding of data items not detailed below, see the respective data items of EFADN (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 8
71
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)
Tag Description Service provider display information Tag Service provider PLMN list tag
The service provider display information object is a constructed TLV coded according to ISO/IEC 8825 [35].
3GPP
Release 8
72
- 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 [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'.
M/O M M M M
- 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
X X X
X X 0
0 1 1
3GPP
Release 8
X 0 0 1 1 X 0 1 0 1 1 X X X X 1 1 1 1 1
73
Notification read MM not retrieved MM retrieved MM rejected 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 8
74
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.
3GPP
Release 8
75
Identifier: '6FD0' File Size: X1++ Xn bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to X1 X1+1 to X1 + X2 X1++ Xn-1+1 to X1++ Xn PIN ADM ADM ADM
Description MMS Connectivity Parameters TLV object MMS Connectivity Parameters TLV object MMS Connectivity Parameters TLV object
M/O M O
Xn bytes
3GPP
Release 8
76
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 [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 8
77
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]. Unused bytes shall be set to 'FF'. An Example for the coding of these parameters can be found in Annex J.2.
- 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 8
78
- 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: - one of the UCS2 coded options as defined in the annex of TS 31.101 [11]. - 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.
PIN PIN/PIN2 (fixed during administrative management) ADM ADM Description MMS Connectivity Parameters TLV object MMS Connectivity Parameters TLV object MMS Connectivity Parameters TLV object M/O O O Length X1 bytes X2 bytes
Xn bytes
3GPP
Release 8
79
Identifier: '6FD3' Record length : X+1 bytes Access Conditions: READ UPDATE INVALIDATE REHABILITATE Bytes 1 2 to X+1
Structure: linear fixed Optional Update activity: low PIN ADM ADM ADM M/O M M Length 1 byte 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].
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 8
80
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 : : MSB LSB : : MSB of Digit 1 of Group ID 1 of Digit 1 of Group ID 1 of Digit 2 of Group ID 1 of Digit 2 of Group ID 1
Byte 2:
b8 b7 b6 b5 b4 b3 b2 b1 LSB : : MSB LSB : : MSB of Digit 3 of Group ID 1 of Digit 3 of Group ID 1 of Digit 4 of Group ID 1 of Digit 4 of Group ID 1
Byte 3:
b8 b7 b6 b5 b4 b3 b2 b1 LSB : : MSB LSB : : MSB of Digit 5 of Group ID 1 of Digit 5 of Group ID 1 of Digit 6 of Group ID 1 of Digit 6 of Group ID 1
Byte 4:
b8 b7 b6 b5 b4 b3 b2 b1 LSB : : MSB LSB : : MSB of Digit 7 of Group ID 1 of Digit 7 of Group ID 1 of Digit 8 of Group ID 1 of Digit 8 of Group ID 1
: : etc........
3GPP
Release 8
81
If storage for fewer than the maximum possible number n of VGCS Group IDs, is required, the excess bytes shall be set to 'FF'.
Activation/Deactivation Flags of the appropriate Group IDs bit = 0 means - Group ID deactivated bit = 1 means - Group ID activated
etc
: :
3GPP
Release 8
82
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
Group ID Contents: Coding: VBS Group ID, according to TS 23.003 [25] 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 LSB : : MSB LSB : : MSB of Digit 1 of Group ID 1 of Digit 1 of Group ID 1 of Digit 2 of Group ID 1 of Digit 2 of Group ID 1
3GPP
Release 8
83
Byte 2:
b8 b7 b6 b5 b4 b3 b2 b1 LSB : : MSB LSB : : MSB of Digit 3 of Group ID 1 of Digit 3 of Group ID 1 of Digit 4 of Group ID 1 of Digit 4 of Group ID 1
Byte 3:
b8 b7 b6 b5 b4 b3 b2 b1 LSB : : MSB LSB : : MSB of Digit 5 of Group ID 1 of Digit 5 of Group ID 1 of Digit 6 of Group ID 1 of Digit 6 of Group ID 1
Byte 4:
b8 b7 b6 b5 b4 b3 b2 b1 LSB : : MSB LSB : : MSB of Digit 7 of Group ID 1 of Digit 7 of Group ID 1 of Digit 8 of Group ID 1 of Digit 8 of Group ID 1
If storage for fewer than the maximum possible number n of VBS Group IDs, is required, the excess bytes shall be set to 'FF'.
3GPP
Release 8
84
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.
Identifier: '6FB4' File size: 7 bytes Access Conditions: READ UPDATE INVALIDATE REHABILITATE Bytes 1 to 7 Structure: transparent Optional Update activity: low PIN PIN/ADM (fixed during administrative management) ADM ADM M/O M Length 7 bytes
Activation/Deactivation Flags Contents: Coding: Activation/Deactivation Flags of the appropriate Group IDs see coding of EFVGCSS
Description VGCS Group ciphering algorithm identifier for 1st V_Ki of Group 1 VGCS Group ciphering algorithm identifier for 2nd V_Ki of Group 1 VGCS Group ciphering algorithm identifier for 1st V_Ki of Group 2 VGCS Group ciphering algorithm identifier for 2nd V_Ki of Group 2 : VGCS Group ciphering algorithm identifier for 1st V_Ki of Group n VGCS Group ciphering algorithm identifier for 2nd V_Ki of Group n
3GPP
Release 8
85
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 02 ciphering with algorithm GSM A5/2 03 ciphering with algorithm GSM A5/3 04 ciphering with algorithm GSM A5/4 05 ciphering with algorithm GSM A5/5 06 ciphering with algorithm GSM A5/6 07 ciphering with algorithm GSM A5/7 08 to FF RFU
Description VBS Group ciphering algorithm identifier for 1st V_Ki of Group 1 VBS Group ciphering algorithm identifier for 2nd V_Ki of Group 1 VBS Group ciphering algorithm identifier for 1st V_Ki of Group 2 VBS Group ciphering algorithm identifier for 2nd V_Ki of Group 2 : VBS Group ciphering algorithm identifier for 1st V_Ki of Group n VBS Group ciphering algorithm identifier for 2nd V_Ki of Group n
Ciphering Algorithm Identifier: Contents: Coding: Ciphering Algorithm identifier for the specified Master Group Key of each Voice Broadcast Group See coding of EFVGCSCA
3GPP
Release 8
86
Identifier: '6FD6' File length: L+X+N+3 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 2 to (X +1) X+2 (X+3) to (X+2+L) X+L+3 (X+L+4) to (X+L+N+3)
Structure: transparent Optional Update activity: low PIN PIN ADM ADM M/O M M M M M M Length 1 byte X bytes 1 byte L bytes 1 byte N bytes
Description Length of RAND (X) RAND Length of B-TID (L) B-TID Length of key lifetime Key lifetime
Length of RAND Contents: RAND Contents: Coding: Length of B-TID Contents: B-TID Content: Coding: Bootstrapping Transaction Identifier the GBA_U bootstrapped keys As defined in TS 33.220 [42] number of bytes, not including this length byte, of B-TID field Random challenge used in the GBA_U bootstrapping procedure. as defined in TS 33.103 [13] number of bytes, not including this length byte, of RAND field
Length of key lifetime Contents: Key lifetime Content: Coding: Lifetime of the GBA_U bootstrapped keys As defined in TS 33.220 [42] number of bytes, not including this length byte, of key lifetime field
3GPP
Release 8
87
Identifier: '6FD7' Structure: linear fixed Optional Record length: 8n+4 bytes, (n 2) Update activity: low Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to 3 4 5 to 8 9 to 12 13 to 16 17 to 20 : 8(n-1)+5 to 8n 8n+1 to 8n+4 PIN ADM ADM ADM M/O M M M M M M : O (See Note) C (See Note) Length 3 bytes 1 byte 4 bytes 4 bytes 4 bytes 4 bytes : 4 bytes 4 bytes
Description Key Domain ID Number of stored MSK IDs and corresponding TS 1st MSK ID 1st Time Stamp Counter (TS) 2nd MSK ID 2nd Time Stamp Counter (TS) : nth MSK ID nth Time Stamp Counter (TS)
Note: In the current version of the specification, these bytes are RFU. Key Domain ID: Content: Coding: Identifier of the Domain of the BM-SC providing MBMS Service. As defined in TS 33.246 [43]
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: Coding: Identifier of MBMS Service Key (MSK) within a particular Key Domain. As defined in TS 33.246 [43]
Time Stamp Counter (TS): Content: Coding: Counter for MIKEY replay protection in MTK delivery. Each counter is associated with a particular MSK. As defined in TS 33.246 [43]
3GPP
Release 8
88
Identifier: '6FD8' Record length: Z bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to Z
Structure: linear fixed Optional Update activity: low PIN ADM ADM ADM M/O M Bytes 1 to Z
MBMS User Key tags Description MUK ID Tag Time Stamp Counter Tag MBMS User Key information Description Value M/O
M M M M M M M M M M M
Tag Value
'A0' '81'
Length (bytes)
1 Note 1 Note A 1 Note W 1 Note Y
MUK ID Tag 'A0' Length X MUK IDr Tag '80' Lenght A MUK IDr value -MUK IDi Tag '82' Lenght W MUK IDi Value Time Stamp Counter Tag '81' Length Y Time Stamp Counter value -Note: The length is coded according to ISO/IEC 8825 [35]
- 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: As defined in TS 33.246 [43] - 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: As defined in TS 33.246 [43] Unused bytes shall be set to 'FF'.
3GPP
Release 8
89
This EF contains the list of NAF_ID and B-TID associated to a GBA NAF derivation procedure.
Identifier: '6FDA' Record length: Z bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to Z Structure: Linear fixed Optional Update activity: low PIN ADM ADM ADM M/O M Length Z bytes
NAF Key Identifier tags Description NAF_ID Tag B-TID Tag NAF Key Identifier information Description Value M/O
M M M M M M
Tag Value
'80' '81'
Length (bytes)
1 Note X 1 Note Y
NAF_ID Tag '80' Length X NAF_ID value -B-TID Tag '81' Length Y B-TID value -Note: The length is coded according to ISO/IEC 8825 [35]
- NAF_ID Tag '80' Contents: Identifier of Network Application Function used in the GBA_U NAF Derivation procedure. Coding: As defined in TS 33.220 [42] - B-TID Tag '81' Content: Bootstrapping Transaction Identifier of the GBA_U bootstrapped key Coding: As defined in TS 33.220 [42] Unused bytes shall be set to 'FF'
3GPP
Release 8
90
Identifier: '6FD9' SFI: '1D' File size: 3n, (n 1) Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to 3 4 to 6 : (3n-2) to (3n)
Structure: transparent Update activity: low PIN ADM ADM ADM M/O M O O
Optional
Description 1st EHPLMN (highest priority) 2nd EHPLMN : nth EHPLMN (lowest priority)
- EHPLMN Contents: - Mobile Country Code (MCC) followed by the Mobile Network Code (MNC). Coding: - according to TS 24.008 [9]. Unused entries shall be set to 'FF FF FF'
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
3GPP
Release 8
91
Identifier: '6FDC' File size: 1 byte Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1
Structure: transparent Optional Update activity: low PIN ADM ADM ADM M/O M Length 1 byte
Last RPLMN Selection Indication: Contents: Last RPLMN Selection Indication Coding: - '00' - The UE shall attempt registration on the last RPLMN as described in TS 23.122 [31] - '01' - The UE shall attempt registration on the home network as described in TS 23.122 [31] - All other values are RFU
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]). Coding: Encoded to an octet string according to UTF-8 encoding rules as described in IETF RFC 3629 [48].
3GPP
Release 8
92
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 [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. - All other values are RFU. Coding: binary. Icon Link Contents: Link to the icon. This link shall point to a UICC resource. Coding:
3GPP
Release 8
93
- 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.
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.
3GPP
Release 8
94
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' Record length: Z bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to M M+1 to M+N M+N+1 to M+N+O M+N+O+1 to M+N+O+P M+N+O+P+1 to M+N+O+P+Q Structure: linear fixed Optional Update activity: low PIN ADM ADM ADM M/O M M C C C Length M bytes N bytes O bytes P bytes Q bytes
Description Data Destination Address Range TLV Access Point Name TLV Login TLV Password TLV Bearer description TLV
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].
Length Description 1 byte Access Point Name Tag 1 byte Length (see note 1) 1 byte Access Point Name Value Note 1: coded according to ISO/IEC 8825 [35]. Value 80 X -Status M M 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.
Length Description 1 byte Login Tag 1 byte Length (see note 1) 1 byte Login Value Note 1: coded according to ISO/IEC 8825 [35]. Value 81 X -Status M M 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.
3GPP
Release 8
95 Length Description 1 byte Password Tag 1 byte Length (see note 1) 1 byte Password Value Note 1: coded according to ISO/IEC 8825 [35].
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.
Length 1 byte 1 byte 1 byte 1 byte Description Data Destination Address Range Tag Length (see note1) Type of Address Prefix length (in bits) Value 83 X -'00' to '20' for IPv4 '00' to '80' for IPv6 -Status M M M M
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 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.
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].
3GPP
Release 8
96 Length Description 1 byte Bearer Description Tag 1 byte Length (see note 1) 1 byte Bearer Description Value Note 1: coded according to ISO/IEC 8825 [35].
Update activity: high PIN PIN ADM ADM M/O M M M Length 12 bytes 5 bytes 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 MSB b7 b6 b5 b4 b3 b2 b1
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.
3GPP
Release 8
97
EPS update status. Contents: status of EPS update according to TS 24.301 [51]. Coding: byte 18: b3 b2 b1. 0 0 0 : 0 0 1 : 0 1 0 : 0 1 1 : 1 0 0 : 1 0 1 : 1 1 0 : 1 1 1 : Bits b4 to b8 are RFU (see TS 31.101 [11]). Bits: UPDATED. NOT UPDATED. ROAMING NOT ALLOWED. reserved. reserved. reserved. reserved. reserved.
3GPP
Release 8
98
Update activity: high PIN PIN ADM ADM M/O M Length X bytes
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 bits b4 to b8 are coded 0
3GPP
Release 8
99
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 MSB b7 b6 b5 b4 b3 b2 b1
Unused bytes shall be set to 'FF'. In order to mark the stored EPS NAS security context as invalid, the record bytes shall be set to 'FF'.
3GPP
Release 8
100
Note 1: The DF identifier '5F80' is reserved for OMA BCAST Smart Card Card profile [49] Note 2: DF for application specific phonebook. This DF has the same structure as the DFPHONEBOOK under DFTELECOM.
4.4.1.1
This EF contains the 'LSA only access indicator'. This EF shall always be allocated if DFSoLSA 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).
Identifier: '4F30' File size: X + 1 bytes Access Conditions: READ UPDATE INVALIDATE REHABILITATE Bytes 1 2 to X+1 Structure: transparent Optional Update activity: low PIN ADM ADM ADM M/O M M Length 1 byte X bytes
Description LSA only access indicator LSA only access indication text
Contents: indicates whether the MS is restricted to use LSA cells only or not.
3GPP
Release 8
101
Coding:
b8 b7 b6 b5 b4 b3 b2 b1 b1=0: LSA only access not activated b1=1: LSA only access activated RFU
Contents: text to be displayed by the ME when it's out of LSA area. 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 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.4.1.2
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.
Identifier: '4F31' Record length: X + 10 bytes Access Conditions: READ UPDATE INVALIDATE REHABILITATE Bytes 1 to X X+1 X+2 X+3 X+4 X+5 to X+7 X+8 to X+9 X+10 Structure: linear fixed Optional Update activity: low PIN PIN ADM ADM M/O O M M M M M M M Length X bytes 1 byte 1 byte 1 byte 1 byte 3 bytes 2 byte 1 byte
Description LSA name Configuration parameters RFU Icon Identifier Priority PLMN code LSA Descriptor File Identifier LSA Descriptor Record Identifier
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 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 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:
3GPP
Release 8
102
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: b3 = 1: Idle mode support disabled 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. b4 = 0: b4 = 1: LSA indication for idle mode disabled LSA indication for idle mode enabled
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
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:
3GPP
Release 8
103
Contents: this byte identifies the number of the first record in the LSA Descriptor file forming the LSA. Coding: binary.
4.4.1.3
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' Record length: n*X+2 bytes Access Conditions: READ UPDATE INVALIDATE REHABILITATE Bytes 1 2 to X+1 X+2 to 2X+1 : (n-1)*X+2 to n*X+1 n*X+2 Structure: linear fixed Optional Update activity: low PIN ADM ADM ADM M/O M M M : M M Length 1 byte X bytes X bytes : X bytes 1 byte
Description LSA descriptor type and number 1st LSA Descriptor 2nd LSA Descriptor : nth LSA Descriptor Record Identifier
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;
3GPP
Release 8
104
in case of CI the field length 'X' is 2 bytes; in case of LAC the field length 'X' is 2 bytes.
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 TS 31.101 [11].
4.4.2.1
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'
3GPP
Release 8
105
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: Type 2 files: Type 3 files: Files that contain as many records as the reference/master file (EFADN, EFADN1) and are linked on record number bases (Rec1 -> Rec1). The master file record number is the reference. Files that contain less entries than the master file and are linked via pointers in the index administration file (EFIAP). Files that are linked by a record identifier within a record. Table 4.1: Phone Book Reference file Constructed Tags
Tag Value 'A8' 'A9' Constructed TAG Description Indicating files where the amount of records equal to master EF, type 1 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 Indicating files that are linked using a record identifier, type 3. (The file pointed to is defined by the TLV object.)
'AA'
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. 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.
3GPP
Release 8
106
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 'C0' 'C1' 'C2' 'C3' 'C4' 'C5' 'C6' 'C7' 'C8' 'C9' 'CA' 'CB' TAG Description EFADN data object EFIAP data object EFEXT1 data object EFSNE data object EFANR data object EFPBC data object EFGRP data object EFAAS data object EFGAS data object EFUID data object EFEMAIL data object EFCCP1 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 EFAAS EFADN EFANR EFEMAIL EFEXT1 EFGAS EFGRP EFIAP EFPBC EFSNE EFUID EFCCP1 Type 1 X X X Type 2 Type 3 X
X X X X
X X X X X
X X
Description TLV object(s) for indicating EFs that are part of the phone book structure 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
3GPP
Release 8
107
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' SFI: 'YY' Record Length: X bytes, (X 1) Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 PIN PIN ADM ADM Structure: linear fixed Conditional (see Note)
Description M/O Length 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
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.
Identifier: '4FXX' SFI: 'YY' Record length: X+14 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE PIN PIN ADM ADM Length X bytes 1 byte 1 byte 10 bytes 1 byte 1 byte Structure: linear fixed Conditional (see Note)
Bytes Description M/O 1 to X Alpha Identifier O X+1 Length of BCD number/SSC contents M X+2 TON and NPI M X+3 to X+12 Dialling Number/SSC String M X+13 Capability/Configuration1 Record Identifier M X+14 Extension1 Record Identifier M NOTE: This file is mandatory if and only if DFPHONEBOOK is present.
3GPP
Release 8
108
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]. 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: - according to TS 24.008 [9]. - 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
- 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 : : MSB LSB : : MSB of Digit 1 of Digit 1 of Digit 2 of Digit 2
3GPP
Release 8
109
Byte X+4:
B8 b7 B6 b5 b4 b3 b2 b1 LSB : : MSB LSB : : MSB of Digit 3 of Digit 3 of Digit 4 of Digit 4
etc. - Capability/Configuration1 Record Identifier. Contents: - capability/configuration identification byte. 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 EFEXT1 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. 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.
3GPP
Release 8
110
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.
Identifier: '4FXX' SFI: 'YY' Record length: 13 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 2 to 12 13 Record type Extension data Identifier Structure: linear fixed Update activity: low PIN PIN ADM ADM Description M/O M M M Length 1 byte 11 bytes 1 byte Optional
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".
3GPP
Release 8
111
The following example of coding means that the type of extension data is "additional data":
B8 0 b7 0 b6 0 b5 0 b4 0 b3 0 b2 1 b1 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. 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. EF EXT1
Byte: 1 Record Type 2 3 4 5 6 7 8 9 10 11 12 13 Identifier Extension data
01 xx 02 02 xx 01
xx xx 0A 04 xx xx
xx xx xx xx xx xx
xx xx xx xx xx xx
xx xx xx xx xx xx
xx xx xx xx xx xx
xx xx xx FF xx xx
xx xx xx FF xx xx
xx xx xx FF xx xx
xx xx xx FF xx xx
xx xx xx FF xx xx
xx xx xx FF xx xx
FF xx 04 06 xx 01
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).
3GPP
Release 8
112
4.4.2.5
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
Identifier: '4FXX' SFI: 'YY' Record length: 2 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE PIN PIN ADM ADM Length 1 byte 1 byte Structure: linear fixed Conditional (see Note)
Bytes Description M/O 1 Entry Control Information M 2 Hidden Information M 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:
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
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.
3GPP
Release 8
113
SFI: 'YY' Record Length: X bytes (1 X 10) Access Conditions: READ PIN UPDATE PIN DEACTIVATE ADM ACTIVATE ADM Bytes 1 2 X NOTE: Description Group Name Identifier 1 Group Name Identifier 2 Group Name Identifier X
M/O M O O
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
This file contains the alpha strings that are associated with the user defined naming tags for additional numbers referenced in EFANR. Structure of EFAAS
Identifier: '4FXX' SFI: Optional Record length: X bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to X Alpha text string Structure: linear fixed Update activity: low PIN PIN ADM ADM Description M/O M Length X bytes Optional
Content: - user defined text for additional number. Coding: - same as the alpha identifier in EFADN.
3GPP
Release 8
114
4.4.2.8
This file contains the alpha strings that are associated with the group name referenced in EFGRP. Structure of EFGAS
Identifier: '4FXX' SFI: Optional Record length: X bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to X NOTE: Alpha text string PIN PIN ADM ADM Description M/O M Length X bytes Structure: linear fixed Conditional (see Note)
4.4.2.9
Several phone numbers and/or Supplementary Service Control strings (SSC) can be attached to one EFADN 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 EFAAS, 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. Structure of EFANR
Identifier: '4FXX' SFI: 'YY' Record length: 15 or 17 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Structure: linear fixed Update activity: low PIN PIN ADM ADM Optional
Bytes Description M/O Length 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)
3GPP
Release 8
115
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.
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 EFEXT1 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.
3GPP
Release 8
116
Content: - record identifier of the associated phone book entry. Coding: - 'xx' record identifier of the corresponding ADN record.
4.4.2.10
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
Identifier: '4FXX' SFI: 'YY' Record length: X or X+2 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Structure: linear fixed Update activity: low PIN PIN ADM ADM Optional
Bytes Description M/O Length 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 NOTE: The fields marked C above are mandatory if and only if the file is not type 1 (as specified in EFPBR)
Content: - string defining the second name of the phone book entry. Coding: - as the alpha identifier for EFADN. 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.11
This EF contains parameters of required network and bearer capabilities and ME configurations associated with a call established using a phone book entry.
3GPP
Release 8
117
Structure of EFCCP1
Identifier: '4FXX' SFI: 'YY' Record length: X bytes, X 15 Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to X Structure: linear fixed Update activity: low PIN PIN ADM ADM M/O M Length X bytes Optional
Contents and Coding: - see TS 24.008 [9]. The Information Element Identity (IEI) shall be excluded; i.e. the first byte of the EFCCP1 record shall be Length of the bearer capability contents. ''- unused bytes are filled with 'FF'
4.4.2.12
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.
Bytes Description M/O Length 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.
3GPP
Release 8
118
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).
Bytes Description M/O Length 1 to 4 Phone book synchronisation counter (PSC) M 4 bytes NOTE: This file is mandatory if and only if synchronisation is supported in the phonebook.
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}.
3GPP
Release 8
119
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'.
Bytes Description M/O Length 1 to 2 Change Counter (CC) of Phone Book M 2 bytes NOTE: This file is mandatory if and only if synchronisation is supported in the phonebook.
Content: - indicates recent change(s) to phone book entries for synchronisation purposes. Coding: - hexadecimal value. At initialisation, CC shall be personalised to '00 00' (i.e. empty).
3GPP
Release 8
120
Structure of EFPUID
Identifier: '4F24' SFI: 'YY' File size: 2 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to 2 NOTE: PIN PIN ADM ADM Structure: transparent Conditional (see Note)
Description M/O Length Previous Unique Identifier (PUID) of Phone M 2 bytes Book Entry This file is mandatory if and only if synchronisation is supported in the phonebook.
Content: - Previous number that was used to unambiguously identify the phone book entry for synchronisation purposes. Coding: As for EFUID
4.4.2.13
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 EFADN file. This record cannot be shared between several phonebook entries. Structure of EFEMAIL
Identifier: '4FXX' SFI: 'YY' Record length: X or X+2 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Structure: linear fixed Update activity: low PIN PIN ADM ADM Optional
Bytes Description M/O Length 1 to X E-mail Address M X bytes : : : : : : : : X+1 ADN file SFI C 1 byte X+2 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)
- 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'.
3GPP
Release 8
121
Content: - short File identifier of the associated EFADN file. Coding: - as defined in TS 31.101. ADN file Record Identifier.
Content: - record identifier of the associated phone book entry. 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.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 8
122
4.4.3.1
If service n27 is "available", this file shall be present. This EF contains the ciphering key Kc and the ciphering key sequence number n for enciphering in a GSM access network.
Identifier: '4F20' SFI: '01' File size: 9 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to 8 9 Structure: transparent Optional
Update activity: high PIN PIN ADM ADM M/O M M Length 8 bytes 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 bits b4 to b8 are coded 0
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
If service n27 is "available", this file shall be present. This EF contains the ciphering key KcGPRS and the ciphering key sequence number n for GPRS (see TS 23.060 [7]).
Identifier: '4F52' SFI: '02 File size: 9 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to 8 9 Structure: transparent Optional
Update activity: high PIN PIN ADM ADM M/O M M Length 8 bytes 1 byte
Description Ciphering key KcGPRS Ciphering key sequence number n for GPRS
- 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 8
123
b8
b7
b6
b5
b4
b3
b2
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 4.4.3.4
If service n39 is "available", this file shall be present. 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.
Identifier: '4F63' File size: 2n bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to 2 : 2n-1 to 2n Structure: transparent Optional Update activity: high PIN PIN ADM ADM M/O M : M Length 2 bytes : 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 : : : : : : :
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 8
124
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
If service n40 is "available", this file shall be present. This EF contains two flags used to control the investigation scan for higher prioritized PLMNs not offering voice services.
Identifier: '4F64' File size: 1 byte Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 Structure: transparent Optional Update activity: low PIN ADM ADM ADM M/O M Length 1 byte
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
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 8
125
4.4.4.1
If service n41 is "available", this file shall be present. 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.
Identifier: '4F40' File size: X bytes, X 1 Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 2 etc. X Structure: transparent Optional Update activity: low PIN ADM ADM ADM M/O M O O Length 1 byte 1 byte 1 byte
-Services Contents:
Operator Root Public Key Administrator Root Public Key Third Party Root Public Key RFU
Coding: the coding rules of the USIM Service Table apply to this table.
4.4.4.2
If service n41 is "available", this file shall be present. 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.
Identifier: '4F41' Record length: X + 10 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 2 3 4 to 5 6 to 7 8 to 9 10 11 to 10+X Structure: linear fixed Optional Update activity: low PIN ADM ADM ADM M/O M M M M M M M M Length 1 byte 1 byte 1 byte 2 bytes 2 bytes 2 bytes 1 byte X bytes
Description Parameters indicator Flags Type of certificate Key/certificate file identifier Offset into key/certificate file Length of key/certificate data Key identifier length (X) Key identifier
- Parameter indicator Contents: The parameter indicator indicates if record is full and which optional parameters are present
3GPP
Release 8
126
- 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 8
127
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
If service n41 is "available", this file shall be present. 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.
Identifier: '4F42' Record length: X + 10 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 2 3 4 to 5 6 to 7 8 to 9 10 11 to 10+X Structure: linear fixed Optional Update activity: low PIN ADM ADM ADM M/O M M M M M M M M Length 1 byte 1 byte 1 byte 2 bytes 2 bytes 2 bytes 1 byte X bytes
Description Parameters indicator Flags Type of certificate Key/certificate file identifier Offset into key/certificate file Length of key/certificate data Key identifier length (X) Key identifier
For contents and coding of all data items see the respective data items of the EFORPK (clause 4.4.4.2).
3GPP
Release 8
128
4.4.4.4
If service n41 is "available", this file shall be present. 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' Record length: X + Y + 11 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 2 3 4 to 5 6 to 7 8 to 9 10 11 to 10+X 11+X 12+X to 11+X+Y Structure: linear fixed Optional Update activity: low PIN ADM ADM ADM M/O M M M M M M M M M M Length 1 byte 1 byte 1 byte 2 bytes 2 bytes 2 bytes 1 byte X bytes 1 byte Y bytes
Description Parameters indicator Flags Type of certificate Key/certificate file identifier Offset into key/certificate file Length of key/certificate data Key identifier length (X) Key identifier Certificate identifier length (Y) Certificate identifier
- 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 EFORPK (clause 4.4.4.2).
4.4.4.5
Residing under DFMExE, there may be several key/certificates data files. These EFs containing key/certificates data shall have the following attributes:
3GPP
Release 8
129
Identifier: '4FXX' File size: Y bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to Y
Structure: transparent Optional Update activity: low PIN ADM ADM ADM M/O M Length Y bytes
Contents and coding: Key/certificate data are accessed using the key/certificates descriptors provided by EFTPRPK (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.1
EFPseudo (Pseudonym)
If service n59 is "available", this file shall be present. 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].
Identifier: '4F41' SFI : '01' File size: Y bytes (Y n+2) Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to 2 3 to n+2 Structure: Transparent Optional
Update activity: high PIN PIN ADM ADM M/O M M Length 2 bytes n bytes
-Pseudonym Length Contents: - this byte gives 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 8
130
4.4.5.2
If service n60 is "available", this file shall be present. 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].
Identifier: '4F42' SFI: '02' File size: 3n (where n 10) Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to 3 4 to 6 : 28 to 30 31 to 33 : (3n-2) to 3n Structure: transparent Optional
Update activity: low PIN PIN ADM ADM M/O M M M O O Length 3 bytes 3 bytes 3 bytes 3 bytes 3 bytes
Description 1st PLMN (highest priority) 2nd PLMN : 10th PLMN 11th PLMN : Nth PLMN (lowest priority)
- PLMN Contents: - Mobile Country Code (MCC) followed by the Mobile Network Code (MNC). Coding: - according to TS 24.008 [9].
Update activity: low PIN ADM ADM ADM M/O M M M O O Length 3 bytes 3 bytes 3 bytes 3 bytes 3 bytes
Description 1st PLMN (highest priority) 2nd PLMN : 10th PLMN 11th PLMN : Nth PLMN (lowest priority)
3GPP
Release 8
131
- PLMN Contents: - Mobile Country Code (MCC) followed by the Mobile Network Code (MNC). Coding: - according to TS 24.008 [9].
4.4.5.4
If service n62 is "available", this file shall be present. 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].
Identifier: '4F44' SFI: '04' Record size: X+1 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 2 to X + 1 Length of WSID WSID Structure: linear fixed Optional
Update activity: low PIN PIN ADM ADM Description M/O M M Length 1 bytes 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
If service n63 is "available", this file shall be present. 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].
Identifier: '4F45' SFI: '05' Record size: X + 1 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 2 to X + 1 Length of WSID WSID Structure: linear fixed Optional
Update activity: low PIN ADM ADM ADM Description M/O M M Length 1 bytes X bytes
3GPP
Release 8
132
-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
If service n66 is "available", this file shall be present. This EF contains a list of parameters linked to a re-authentication identity to be used in fast re-authentication. Reauthentication identities and related parameters (Master Key and Counter Value) are provided as part of a previous authentication sequence.
Identifier: '4F46' SFI: '06' File size: n bytes, (n J+K+L+6) Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 2 3 to J+2 J+3 J+4 J+5 to J+K+4 J+K+5 J+K+6 J+K+7 to J+K+L+6 Structure: Transparent Optional
Update activity: high PIN PIN ADM ADM M/O M M M M M M M M M Length 1 byte 1 byte J bytes 1 byte 1 byte K bytes 1 byte 1 byte L bytes
Description Reauthentication Identity Tag '80' Re-authentication Identity Length Re-authentication Identity Value Master Key Tag '81' Master Key Length Master Key Value Counter Tag '82' Counter Length Counter Value
- 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' Unsigned length on 1 byte Value: As described in TS 33.234 [41].
3GPP
Release 8
133
- Counter Contents: - Counter TLV Coding: Tag '82' Unsigned length on 1 byte Value: As described in TS 33.234 [41].
4.4.5.7
If service n81 is "available", this file shall be present. 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 nth 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].
Identifier: '4F47' SFI: '07' Record size: X + 1 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 2 to X + 1 Length of WSID WSID Structure: linear fixed Optional
Update activity: low PIN ADM ADM ADM Description M/O M M Length 1 bytes X bytes
4.4.5.8
If service n82 is "available", this file shall be present. 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].
Identifier: '4F48' SFI: '08' File size: 1 byte Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 Structure: transparent Update activity: low PIN ADM ADM ADM M/O M Length 1 byte Optional
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 '02' - Display all the available EHPLMNs
3GPP
Release 8
134
4.4.5.9
If service n83 is "available", this file shall be present. 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].
Identifier: '4F49' SFI: '09' File size: 1 byte Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 Structure: transparent Update activity: low PIN ADM ADM ADM M/O M Length 1 byte Optional
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] All other values are RFU
4.4.5.10
If service n84 is "available", this file shall be present. This EF contains I-WLAN Last Registered PLMN Selection. The usage of the I-WLAN Last Registered PLMN is defined in TS 24.234 [40].
Identifier: '4F4A' SFI: '0A' File size: 3 bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to 3 Structure: transparent Update activity: low PIN PIN ADM ADM M/O M Length 3 bytes Optional
I-WLAN Last Registered PLMN Contents: - Mobile Country Code (MCC) followed by the Mobile Network Code (MNC).
4.4.5.11
3GPP
Release 8
135
This EF contains HPLMN Direct Access related informations. The usage of the HPLMN Direct Access Indicator file is defined in TS 23.234 [40].
Identifier: '4F4B' SFI: '0B' File size: 1 byte Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 Structure: transparent Update activity: low PIN ADM ADM ADM M/O M Length 1byte Optional
HPLMN Direct Access Indication: Contents: HPLMN Direct Access Indication Coding: - '00' HPLMN Direct Access Indicator is disabled '01' HPLMN Direct Access Indicator is enabled
This clause describes the additional files that are used for Home (e)NodeB purposes. DFHNB shall be present at the ADFUSIM level if service n86 is "available" in EFUST .
4.4.6.2
If service n86 is "available", this file shall be present. This EF contains the coding for CSG IDs 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.
Identifier: '4F81' SFI: '01' Record length: X Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Structure: linear fixed Update activity: low PIN PIN ADM ADM Length X bytes Optional
Bytes Description M/O 1 to X Allowed CSG Lists TLV object M 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. CSG List Tags
3GPP
Release 8
136
Description CSG List TLV object Tag CSG List information Description Value M/O
M M M M M M M M
Tag Value
'A0'
Length (bytes)
1 Note 1 Note A 1 Note W
CSG List Tag 'A0' Length Y PLMN Tag '80' Length A PLMN -CSG Information Tag '81' Length W CSG Information Note: The length is coded according to ISO/IEC 8825 [35]
PLMN Tag '80' Contents: Mobile Country Code (MCC) followed by the Mobile Network Code (MNC). Coding: according to TS 24.008 [47].
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. 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 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:
3GPP
Release 8
137
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. Unused bytes shall be set to 'FF'.
3GPP
Release 8
138
4.4.6.3
If service n86 is "available", this file shall be present. This EF contains the CSG Type. The CSG Type is defined in TS 22.011 [2]. 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.
Identifier: '4F82' SFI: '02' Record length: X bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to X Structure: linear fixed Update activity: low PIN PIN ADM ADM M/O M Length X bytes Optional
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:
Description Value Text CSG Type Tag '89' Length K Text CSG Type -Note: The length is coded according to ISO/IEC 8825 [35]. M/O M M M Length (bytes) 1 Note K
Text CSG Type Tag Contents: Tag value for the CSG Type in text format.
3GPP
Release 8
139
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, - All other values are RFU. 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. - All other values are RFU. 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 8
140
4.4.6.4
If service n86 is "available", this file shall be present. This EF contains the HNB name. The HNB name is defined in TS 22.011 [2]. The association between a CSG ID and the corresponding HNB name is provided in EFACSGL.
Identifier: '4F83' SFI: '03' Record length: X bytes; X 3 Access Conditions: READ UPDATE ACTIVATE DEACTIVATE Bytes 1 to X Structure: linear fixed Update activity: low PIN PIN ADM ADM M/O M Length X bytes Optional
HNB Name Tag '80' Contents: name of the HNB.. Coding: coded using one of the UCS2 code options as defined in TS 31.101 [11].
3GPP
Release 8
141
A 3G ME shall not access this file. The information is accessible for a 3G ME in EFEXT1 under DFPHONEBOOK.
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 8
142
- 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 [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:
3GPP
Release 8
143
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 [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'.
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 [54]. The URI shall be encoded to an octet string according to UTF-8 encoding rules as specified in IETF RFC 3629 [55]. The tag value of the URI TLV data object shall be '80'.
(DF for public phone book. This DF has the same structure as DFPHONEBOOK under ADF USIM). DFMULTIMEDIA '5F3B'.
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 8
144
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.
Identifier: '4F20' Structure: linear fixed Optional Record length: 9n+1 or 9n+2 bytes, (n 1) Update activity: low Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 2 to 10 11 to 19 : 9(n-1)+2 to 9n+1 9n + 2 PIN ADM ADM ADM M/O M M O : O O Length 1 byte 9 bytes 9 bytes : 9 bytes 1 byte
Description Number of Actual Image Instances Descriptor of Image Instance 1 Descriptor of Image Instance 2 : Descriptor of Image Instance n RFU (see TS 31.101 [11])
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 8
145
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
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:
Identifier: '4FXX' File size: Y bytes Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to Y Structure: transparent Optional Update activity: low PIN ADM ADM ADM M/O M Length Y bytes
Contents and coding: - Image instance data are accessed using the image instance descriptors provided by EFIMG (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.
3GPP
Release 8
146
4.6.3.1
If service n67 is "available", this file shall be present. 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.
Identifier: '4F47' Access Conditions: READ UPDATE INVALIDATE REHABILITATE Bytes 1 to X Structure: BER-TLV Update activity: low PIN PIN ADM ADM M/O M Length X bytes Optional
- MM Descriptor Data Object The content and coding are defined below: Coding of the MM Descriptor Data Objects
Length 1 to A bytes (A 3) 1 to B bytes (B 4) 1 byte 1 byte 1 byte 1 byte 1 byte 1 or 2 bytes 1 byte 1 byte 1 to C bytes (C 3) 1 byte 1 byte 1 to D bytes (D 4) 1 byte 1 byte 2 bytes 1 byte 1 byte 1 to E bytes Description MM Descriptor Data Object tag MM Descriptor Data Object length MMS Implementation tag '80' MMS Implementation length MMS Implementation MM File Identifier / SFI tag '81' MM File Identifier / SFI length MM File Identifier / SFI MM Content Data Object Tag tag '82' MM Content Data Object Tag length MM Content Data Object Tag MM Size tag '83' MM Size length MM Size in bytes MM Status tag '84' MM Status length MM Status MM Alpha Identifier tag '85' MM Alpha Identifier length MM Alpha Identifier Coding Status As defined in TS 31.101 [11] M for BER-TLV structured files As defined in TS 31.101 [11] M for BER-TLV structured files M M See below M M M See below M M M See below M M M See below M M M See below M M M 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 0 Meaning Implementation not supported.
3GPP
Release 8
147
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: according to TS 31.101 [11]. - MM Content Data Object Tag Contents: tag indentifying a MM (i.e. identifying a data object) within EFMMDF. Coding: according to TS 31.101 [11]. - MM Size Contents: size of the corresponding MM stored in EFMMDF. Coding: according to TS 31.101 [11]. - 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. 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
Originated MM coding: bit b1 is used to provide information on Delivery-report. Bits b2 to b8 are reserved for future use.
3GPP
Release 8
148
Delivery report requested, bit = 1 Delivery report creation allowed, 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
If service n67 is "available", this file shall be present. 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.
Identifier: '4F48' Access Conditions: READ UPDATE DEACTIVATE ACTIVATE Bytes 1 to X Structure: BER-TLV Optional Update activity: low PIN PIN ADM ADM M/O M Length X bytes
- MM Content Data Object The content and coding are defined below: Coding of the MM Content Data Objects
Length Description 1 to T bytes (T 3) MM Content Data Object tag 1 to L (L 4) X-L-T bytes MM Content Data Object length MM Content Coding As defined in TS 31.101 [11] for BER-TLV structured files As defined in TS 31.101 [11] for BER-TLV structured files According to MMS Implementation Status M M M
Contents:
3GPP
Release 8
149
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 8
150
3GPP
Release 8
EFICCID '2FE2'
EFARR '6F06' EFSMSP '6F42' EFEXT1 '6F4A' EFECCP '6F4F' DFGRAPHICS '5F50' EFIMG '4F20' DFPHONEBOOK '5F3A' EFPSC '4F22' EFCCP1 '4FXX' EFGRP '4FXX' EFEMAIL '4FXX' DFMULTIMEDIA '5F3B' EFMML '4F47'
EFIIDFn '4FXX'
EFMMDF '4F48'
NOTE 1: Files under DFTELECOM with shaded background are defined in TS 51.011 [18]. NOTE 2: The value '6F65' under ADFUSIM was used in earlier versions of this specification, and should not be reassigned in future versions.
3GPP
Release 8
152
ADFUSIM EFLI '6F05' EFDCK '6F2C' EFACM '6F39' EFMSISDN '6F40' EFSPN '6F46' EFEXT3 '6F4C' EFEXT4 '6F55' EFTHRESHOLD '6F5C' EFACC '6F78' EFICT '6F82' EFVBS '6FB3' EFHiddenkey '6FC3' EFEXT6 '6FC8' EFSPDI '6FCD' EFMMSUCP '6FD2' EFMSK '6FD7' EFARR '6F06' EFHPPLMN '6F31' EFFDN '6F3B' EFPUCT '6F41' EFSMSR '6F47' EFBDN '6F4D' EFEST '6F56' EFPLMNwAcT '6F60' EFFPLMN '6F7B' EFOCT '6F83' EFVBSS '6FB4' EFNETPAR '6FC4' EFMBI '6FC9' EFMMSN '6FCE' EFNIA '6FD3' EFMUK '6FD8' EFIMSI '6F07' EFCNL '6F32' EFSMS '6F3C' EFSMSP '6F42' EFCBMID '6F48' EFEXT5 '6F4E' EFACL '6F57' EFOPLMNwAcT '6F61' EFLOCI '6F7E' EFAD '6FAD' EFeMLPP '6FB5' EFPNN '6FC5' EFMWIS '6FCA' EFEXT8 '6FCF' EFVGCSCA '6FD4' EFEHPLMN '6FD9' EFKeys '6F08' EFACMmax '6F37' EFGID1 '6F3E' EFSMSS '6F43' EFSDN '6F49' EFCCP2 '6F4F' EFCMI '6F58' EFHPLMNwAcT '6F62' EFICI '6F80' EFVGCS '6FB1' EFAAeM '6FB6' EFOPL '6FC6' EFCFIS '6FCB' EFMMSICP '6FD0' EFVBSCA '6FD5' EFGBANL '6FDA' EFKeysPS '6F09' EFUST '6F38' EFGID2 '6F3F' EFCBMI '6F45' EFEXT2 '6F4B' EFCBMIR '6F50' EFSTART-HFN '6F5B' EFPSLOCI '6F73' EFOCI '6F81' EFVGCSS '6FB2' EFECC '6FB7' EFMBDN '6FC7' EFEXT7 '6FCC' EFMMSUP '6FD1' EFGBAP '6FD6' EFEHPLMNPI '6FDB'
3GPP
Release 8
153
EFLRPLMNSI '6FDC' EFEPSLOCI '6FE3' DFPHONEBOOK '5F3A' EFPSC '4F22' EFCCP1 '4FXX' EFGRP '4FXX' EFEMAIL '4FXX' DFGSM-ACCESS '5F3B' EFKc '4F20' DFMExE '5F3C' EFMExE-ST '4F40' DFSoLSA '5F70' EFSAI '4F30' DFWLAN '5F40' EFPseudo '4F41' 1) 1) 2) 2) 3) 3) 4) 4) 1) 2) 3) 4) 1) 2) 3) 4) 1) 2) 3) 4) EFWRI '4F46' EFHPLMNDAI '4F4B'
EFSPNI '6FDE'
EFPNNI '6FDF'
EFNCP-IP '6FE2'
EFKcGPRS '4F52'
EFCPBCCH '4F63'
EFinvSCAN '4F64'
EFORPK '4F41'
EFARPK '4F42'
EFTPRK '4F43'
EFTKCDF '4FXX'
EFSLL '4F31'
3GPP
Release 8
154
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.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 EFLI 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.
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.
3GPP
Release 8
155
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-CS 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-CS 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; Cipher key and integrity key request for CS- and/or PS-mode; EPS NAS Security Context request for EPS; 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
If GSM access is enabled the following procedures shall be performed if the applicable service is enabled and if the ME supports the GSM compact access technology. Investigation Scan request; CPBCCH information request.
3GPP
Release 8
156
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. Cipher Key and Integrity Key update for CS-and/or PS-domain. EPS NAS Security Context update for EPS 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
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.
Update: NOTE:
3GPP
Release 8
157
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.
3GPP
Release 8
158
Update:
3GPP
Release 8
159
Voice Group Call Service Status Request: Update: The ME performs the reading procedure with EFVGCSS. The ME performs the updating procedure with EFVGCSS.
Voice Broadcast Service Status Request: Update: The ME performs the reading procedure with EFVBSS. The ME performs the updating procedure with EFVBSS.
3GPP
Release 8
160
5.2.27
Request: Update:
Requirement:
5.2.28
Request: Update:
Requirement:
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].
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 EFADN 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 EFADN is the last to be deleted.
3GPP
Release 8
161
5.3.1.3
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 EFHiddenkey. 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: Update: The ME performs the reading procedure with EFHiddenkey. The ME performs the updating procedure with EFHiddenkey.
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. 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.
3GPP
Release 8
162
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 EFEXT1 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 EFADN. 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: Request: The ME sends the identification of the information to be erased. The content of the identified record in EFADN is marked as "free". 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. 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'.
Purge:
The following three procedures are only applicable to service n2 (FDN). FDN capability request. The ME shall check the state of service n2, 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 n2 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 n6 (BDN). BDN capability request. The ME shall check the state of service n6, 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.
3GPP
Release 8
163
Accumulated Call Meter Maximum Value. Request: Initialisation: The ME performs the reading procedure with EFACMmax. The ME performs the updating procedure with EFACMmax using the new initial maximum value.
Price per Unit and Currency Table (PUCT). Request: Update: The ME performs the reading procedure with EFPUCT. The ME performs the updating procedure with EFPUCT.
3GPP
Release 8
164
Update:
3GPP
Release 8
165
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: Purge: 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'. 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.
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 EFACL, 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. 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.
3GPP
Release 8
166
3GPP
Release 8
167
Update:
- 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 EFMMSN. 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 n53 is available all associated records in EFEXT8 are then marked by the ME as "free" by setting them to 'FF'.
3GPP
Release 8
168
Update:
3GPP
Release 8
169
Disable ICE display: The terminal performs the deactivate procedure consecutively on all the supported files (EFICE_DN and EFICE_FF). Enable ICE display: The terminal performs the activate procedure consecutively on all the supported files (EFICE_DN and EFICE_FF). The content of the EFICE_DN and EFICE_FF shall be preserved when enabling and disabling the ICE display.
5.3.40.1
Request:
Requirement:
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. A terminal in eCall only mode performss the FDN related procedures.
5.3.40.2
Requirement: Request:
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. A terminal in eCall and normal mode performs the SDN related procedures.
5.3.41 SM-over-IP
Requirement: Request: Service n12 and n91 "available". the ME performs the reading procedure with EFPSISMSC.
3GPP
Release 8
170
Update:
3GPP
Release 8
171
5.5.1 MExE ST
Requirement: Request: Service n41 (MExE) "available". The ME performs the reading procedure with EFMExE-ST
Requirement:
3GPP
Release 8
172
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.7
The EFNCP-IP access procedures are described in ETSI TS 102 483 [50]. Request:
Requirement:
The ME shall read the allowed CSG IDs from EFACSGL in order to perform HNB selection procedures. The lists in EFACSGL shall take precedence over the list stored in the ME non-volatile memory.
3GPP
Release 8
173
The ME shall discover the association between the selected CSG ID and a CSG Type from EFACSGL. If this association exists, the provided CSG Type shall be displayed.
The ME shall discover the association between the selected CSG ID and a HNB name from EFACSGL. If this association exists, the provided HNB name shall be displayed.
6
-
Security features
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.
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:
3GPP
Release 8
174
A permanent secret key K is used in this procedure. This key K has a length of 128 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.
These cryptographic functions may exist either discretely or combined within the USIM.
Disabling of PIN2 is allowed. This is, however, not the case if PIN2 is mapped to the CHV2 of a GSM application.
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
3GPP
Release 8
175
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]. 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 = f2K (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].
3GPP
Release 8
176
If Service n27 is "available", the USIM calculates the GSM response parameter KC, using the conversion function defined in TS 33.102 [13]. Input: RAND, AUTN (AUTN:= SQN AK || AMF || MAC).
Output: or or AUTS. RES, CK, IK, KC if Service n27 is "available". RES, CK, IK if Service n27 is "not available".
7.1.1.2
USIM operation in an GSM security context is supported if Service n38 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.
7.1.1.3
USIM operation in a VGCS/VBS security context is supported if both Service n57 and Service n64 are available (VGCS security context) or if both Service n58 and Service n65 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). 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
3GPP
Release 8
177
Output: VSTK.
7.1.1.4
USIM operations in GBA security context are supported if service n68 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 = f2K (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
USIM operations in GBA security context are supported if service n68 is "available". 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 BTID value associated to the GBA_U bootstrapped key involved in this GBA_U NAF derivation procedure.
3GPP
Release 8
178
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. According to TS 33.220 [42], the USIM can contain several Ks_int_NAF together with the associated BTID and NAF_ID, but there is at most one pair of Ks_int_NAF and associated B-TID stored per NAF_ID.
NOTE:
In case no empty record is available the USIM shall overwrite an existing record to store the NAF_ID and the BTID 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
USIM operations in MBMS security context are supported if service n69 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. 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. 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.
NOTE: NOTE:
If the received MUK ID does not correspond to the last generated MUK (i.e. last bootstrapped MUK) then the USIM proceeds as follows:
3GPP
Release 8
179
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. 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.
NOTE:
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. Input: MIKEY message Output: or None MIKEY message
3GPP
Release 8
180
7.1.1.7 7.1.1.8
USIM operations in MBMS security context are supported if service n69 is "available". 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
USIM operations in MBMS security context are supported if service n69 is "available". 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. Input: Key Domain ID, MSK ID Key Group part Output: None.
7.1.1.10
USIM operations in MBMS security context are supported if service n69 is "available".
3GPP
Release 8
181
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
USIM operations in this security context are supported if service n68 and service n76 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 preissuance 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 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)
3GPP
Release 8
182
7.1.1.12
USIM operations in this security context are supported if service n68 and service n76 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.
Parameter P2 specifies the authentication context as follows: Table 1: Coding of the reference control P2
Coding b8-b1 '1-------' '----- XXX' Meaning Specific reference data (e.g. DF specific/application dependant key) 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":
3GPP
Release 8
183
Output: None.
Code CLA INS P1 P2 Lc Data Le Value As specified in TS 31.101 [11] '89' As specified in TS 31.101 [11] See table 2 below Length of the subsequent data field Authentication related data Not present
If P1 indicates "First block of authentication response data" or "Next block of authentication response data": Input: None.
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: Table 2: Coding of the reference control P2
Coding b8-b1 '1-------' '----- XXX' Meaning Specific reference data (e.g. DF specific/application dependant key) Authentication context: 101 MBMS context 110 Local Key Establishment mode
3GPP
Release 8
184
Command parameters/data:
7.1.2.1
Length 1 L1 1 L2
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:
Byte(s) Description 1 "Successful 3G authentication" tag = 'DB' 2 Length of RES (L3) 3 to (L3+2) RES (L3+3) Length of CK (L4) (L3+4) to CK (L3+L4+3) (L3+L4+4) Length of IK (L5) (L3+L4+5) to IK (L3+L4+L5+4) (L3+L4+L5+5) Length of KC (= 8) (see note) (L3+L4+L5+6 KC (see note) to (L3+L4+L5+13) Note: Parameter present if and only if Service n27 is "available". Length 1 1 L3 1 L4 1 L5 1 8
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:
Byte(s) 1 2 3 to (L1+2) Description "Synchronisation failure" tag = 'DC' Length of AUTS (L1) AUTS Length 1 1 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:
Byte(s) 1 2 to 5 6 7 to 14 Description Length of SRES (= 4) SRES Length of KC (= 8) KC Length 1 4 1 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
3GPP
Release 8
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 b8-b1 '00000001' '00000010' Meaning Corresponds to the 1st group key 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:
Byte(s) 1 2 3 to 18 Description "Successful VGCS/VBS operation" tag = 'DB' Length of VSTK (16) VSTK Length 1 1 16
7.1.2.3
AUTS coded as for UMTS Security context. Response parameters/data, GBA security context (Bootstrapping Mode), command successful:
Byte(s) 1 2 3 to (L+2) Description "Successful GBA operation" tag = 'DB' Length of RES (L) RES Length 1 1 L
3GPP
Release 8
186
7.1.2.4
Response parameters/data, GBA security context (NAF Derivation Mode), command successful:
Byte(s) 1 2 3 to (L+2) Description "Successful GBA operation" tag = 'DB' Length of Ks_ext_NAF (L) Ks_ext_NAF Length 1 1 L
7.1.2.5
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 '01' 02' '03' '04' Meaning MSK Update Mode MTK Generation Mode MSK Deletion Mode MUK Deletion Mode
Response parameters/data, MBMS security context (MSK Update Mode), command successful:
Description Coding Length 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" Byte(s) 1
Response parameters/data, MBMS security context (MTK Generation Mode), command successful:
3GPP
Release 8
187
Description MBMS operation response Data Object tag (53) MBMS operation response Data Object length (L) "Successful MBMS operation" tag = 'DB' MTK || Salt (if Salt key is available)
Coding Length As defined in TS 31.101 [11] for 1 BER-TLV data object As defined in TS 31.101 [11] for A BER-TLV data object 1 L-1
Response parameters/data, MBMS security context (MSK and MUK Deletion Mode), command successful:
Byte(s) 1 2 3 Description Coding Length MBMS operation response Data Object tag As defined in TS 31.101 [11] for 1 (53) BER-TLV data object MBMS operation response Data Object length As defined in TS 31.101 [11] for 1 BER-TLV data object "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
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 '80' Coded according to ISO/IEC 8825 [35] Value / Meaning Local Key Establishment context: '01': Key Derivation mode '02': Key Availability Check mode Operation Status: 'DB': Successful Operation
7.1.2.6.1
Command parameters/data:
Byte(s) 1 2 to A+1 bytes (A 4) A+2 to (A+L+1) Description Key Derivation Data Object tag (73) Key Derivation Data Object length (L) Key Derivation Data Object Coding As defined in TS 31.101 [11] for BER-TLV data object As defined in TS 31.101 [11] for BER-TLV data object Length 1 A L
Key Derivation Data Object content: The TLVs defined in table 4 are included in the Key Derivation Data Object.
3GPP
Release 8
188
Response parameters/data, Local Key Establishment security context (Key Derivation mode), command successful:
Description Key Derivation Operation Response Data Object tag (73) 2 to A1+1 bytes (A1 4) Key Derivation Operation Response Data Object length (L1) A1+2 to (A1+L1+1) Key Derivation Operation Response Data Object Byte(s) 1 Coding Length As defined in TS 31.101 [11] for 1 BER-TLV data object As defined in TS 31.101 [11] for A1 BER-TLV data object L1
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 8
189
7.1.2.6.2
Command parameters/data:
Byte(s) 1 2 to 1+A bytes (A 4) A+2 to (A+L+1) Description Key Availability Check Data Object tag (73) Key Availability Check Data Object length (L) Key Availability Check Data Object Coding As defined in TS 31.101 [11] for BER-TLV data object As defined in TS 31.101 [11] for BER-TLV data object Length 1 A 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
Description Local Key Establishment Control TLV Key Identifier TLV Value Coded as defined in section 7.1.2.6. The value field shall be set to '02' Coded as defined in section 7.1.2.6.1 M/O M M Length (bytes) B C
Response parameters/data, Local Key Establishment security context (Key Availability Check mode), command successful:
Description Key Availability Check Operation Response Data Object tag ('73') 2 to 1+A1 bytes (A1 4) Key Availability Check Operation Response Data Object length (L1) A1+2 to (A1+L1+1) Key Availability Check Operation Response Data Object Byte(s) 1 Coding Length As defined in TS 31.101 [11] for 1 BER-TLV data object As defined in TS 31.101 [11] for A1 BER-TLV data object L1
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
Description Local Key Establishment Control TLV Value Coded as defined in section 7.1.2.6. The value field shall be set to 'DB' M/O M Length (bytes) B
3GPP
Release 8
190
3GPP
Release 8
191
3GPP
Release 8
192
Note: OMA BCAST Smart Card Profile [49] defines a command using instruction code INS '1B'
Void
3GPP
Release 8
193
3GPP
Release 8 File identification '2F00' '2F05' '2F06' '2FE2' '4F20' 4F20 '4FXX' '4FXX' '4F22' '4F23' '4F24' '4F30' '4FXX' '4F30' '4F31' '4FXX' 4F52 '4F63' '4F64 '4FXX' '4FXX' '4FXX' '4FXX' '4FXX' '4FXX' '4FXX' '4FXX' '4FXX' '4FXX' '4F41' '4F42' '4F43' '4F44' '4F45' '4F46' 4F47' '4F47' '4F48' '4F48' '4F49' '4F4A' '4F4B' '4F81' '4F82' '4F83' '6F05' 6F06 '6F07' '6F08' '6F09' '6F2C' '6F31' '6F32' '6F37' '6F38' '6F39' '6F3B' '6F3C' '6F3E' '6F3F' '6F40' '6F41' '6F42'
194
3GPP TS 31.102 V8.14.0 (2012-01) Change advised Caution Yes Caution No Yes No Yes Yes Yes Yes Yes Yes Yes Caution Caution Caution No No Caution Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Caution No Caution No Caution No Yes Yes Yes Yes Yes Caution Yes Yes Yes Yes Yes Caution Caution (Note 1) No No Caution Caution Caution Yes Caution Yes Yes (Note 2) Yes Yes Yes Yes Yes Yes
Description Application directory Preferred languages Access rule reference ICC identification Image data GSM Ciphering key Kc Image Instance data Files Unique identifier Phone book synchronisation counter Change counter Previous unique identifier Phone book reference file Capability configuration parameters 1 SoLSA Access Indicator SoLSA LSA List LSA Descriptor files GPRS Ciphring key KcGPRS CPBCCH Information Investigation Scan Additional number alpha string Additional number Second name entry Grouping information alpha string Phone book control E-mail addresses Index administration phone book Extension 1 Abbreviated dialling numbers Grouping file Pseudonym User controlled PLMN selector for I-WLAN Operator controlled PLMN selector for I-WLAN User controlled WSID List Operator controlled WSID List WLAN Reauthentication Identity Home I-WLAN Specific Identifier List Multimedia Messages List I-WLAN Equivalent HPLMN Presentation Indication Multimedia Messages Data File I-WLAN HPLMN Priority Indication I-WLAN Last Registered PLMN HPLMN Direct Access Indicator Allowed CSG lists CSG Type HNB name Language indication Access rule reference (under ADFUSIM and DFTELECOM) IMSI Ciphering and integrity keys Ciphering and integrity keys for packet switched domain De-personalization Control Keys Higher Priority PLMN search period Co-operative network list ACM maximum value USIM service table Accumulated call meter Fixed dialling numbers Short messages Group identifier level 1 Group identifier level 2 MSISDN storage PUCT SMS parameters
3GPP
Release 8 File identification '6F43' '6F45' '6F46' '6F47' '6F48' '6F49' '6F4B' '6F4C' '6F4D' '6F4E' '6F4F' '6F50' '6F54' 6F55 '6F56' '6F57' '6F58' '6F5B' '6F5C' '6F60' '6F61' '6F62' '6F73' '6F78' '6F7B' '6F7E' '6F80' '6F81' '6F82' '6F83' '6FAD' '6FB1' '6FB2' '6FB3' '6FB4' '6FB5' '6FB6' '6FB7' '6FC3' '6FC4' '6FC5' '6FC6' '6FC7' '6FC8' '6FC9' '6FCA' '6FCB' '6FCC' '6FCD' '6FCE' '6FCF' '6FD0' '6FD1' '6FD2' '6FD3' '6FD4' '6FD5' '6FD6' '6FD7' '6FD8' '6FD9' '6FDA' '6FDB'
195
Description Change advised SMS status Yes CBMI Caution Service provider name Yes Short message status reports Yes CBMID Yes Service Dialling Numbers Yes (Note 2) Extension 2 Yes Extension 3 Yes Barred dialling numbers Yes Extension 5 Yes Capability configuration parameters 2 Yes CBMIR Yes SetUp Menu Elements Yes Extension 4 Yes Enabled services table Caution Access point name control list Yes Comparison method information Yes Initialisation value for Hyperframe number Caution Maximum value of START Yes User controlled PLMN selector with Access Technology No Operator controlled PLMN selector with Access Caution Technology HPLMN selector with Access Technology Caution Packet switched location information Caution (Note 1) Access control class Caution Forbidden PLMNs Caution Location information No (Note 1) Incoming call information Yes Outgoing call information Yes Incoming call timer Yes Outgoing call timer Yes Administrative data Caution Voice Group Call Service Yes Voice Group Call Service Status Yes Voice Broadcast Service Yes Voice Broadcast Service Status Yes Enhanced Multi Level Pre-emption and Priority Yes Automatic Answer for eMLPP Service Yes Emergency Call Codes Caution Key for hidden phone book entries No Network Parameters No PLMN Network Name Yes Operator Network List Yes Mailbox Dialling Numbers Yes Extension 6 Yes Mailbox Identifier Caution Message Waiting Indication Status Caution Call Forwarding Indication Status Caution Extension 7 Yes Service Provider Display Information Yes MMS Notification Yes Extension 8 Yes MMS Issuer Connectivity Parameters Yes MMS User Preferences Yes MMS User Connectivity Parameters Yes Network's indication of alerting (NIA) Caution Voice Group Call Service Ciphering Algorithm Yes Voice Broadcast Service Ciphering Algorithm Yes GBA Bootstrapping parameters Caution MBMS Service Keys List Caution MBMS User Key Caution EHPLMN Caution GBA NAF List Caution EHPLMN Presentation Indication Caution
3GPP
Release 8 File identification '6FDC' '6FDD' '6FDE' '6FDF' '6FE0' '6FE1' '6FE2' '6FE3' '6FE4' '6FE5'
NOTE1: NOTE2:
196 Description Last RPLMN Selection Indication NAF Key Centre Address Service Provider Name Icon PLMN Network Name Icon In Case of Emergency Dialling Number In Case of Emergency Free Format Network Connectivity Parameters for UICC IP connections EPS location information EPS NAS Security Context Public Service Identity of the SM-SC
3GPP TS 31.102 V8.14.0 (2012-01) Change advised Caution Caution Yes Yes Yes Yes Yes Caution (Note 1) Caution Yes
If EFIMSI is changed, the UICC should issue REFRESH as defined in TS 31.111 and update EFLOCI, EFPSLOCI and EFEPSLOCI accordingly. This file may contain eCALL related test and reconfiguration numbers.
3GPP
Release 8
197
B.1
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:
Byte(s) 1 2 3 to K+2 Description image width = X image height = Y image body Length 1 1 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 status status status status status status status of of of of of of of of raster raster raster raster raster raster raster raster point point point point point point point point 8 7 6 5 4 3 2 1
Byte 2:
B8 b7 b6 b5 b4 b3 b2 b1 status status status status status status status status of of of of of of of of raster raster raster raster raster raster raster raster point point point point point point point point 16 15 14 13 12 11 10 9
3GPP
Release 8
198
B.2
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:
Byte(s) 1 2 3 4 5 to 6 7 to K+6 Description Image width = X Image height = Y Bits per raster image point = B Number of CLUT entries = C Location of CLUT (Colour Look-up Table) Image body Length 1 1 1 1 2 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 8
199
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 1-3 ... 3*(C-1) +1 to 3*C CLUT Entry entry 0 ... 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 1 2 3 Intensity of Colour Red Green 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
-
This coding scheme is identical to the Colour Image Coding Scheme as defined in appendix B.2, with the following exception:
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 8
200
'A0'
'02'
'A1'
'A2'
3GPP
Release 8
201
'A1'
'A2'
'A3' 'A8'
Service Provider Display Information (EFSPDI) Phone Book Reference File (EFPBR)
'A9'
'AA'
'AB'
NOTE:
the value 'FF' is an invalid tag value. For ASN.1 tag assignment rules see ISO/IEC 8825 [35]
3GPP
Release 8
202
3GPP
Release 8 File Identification '2F00' '2F05' '2F06' '2FE2' '4F20' 4F20 '4FXX' '4FXX' '4F22' '4F23' '4F24' '4F30' '4F30' '4F31' '4FXX' '4FXX' 4F52 '4F63' '4F64' '4FXX' '4FXX' '4FXX' '4FXX' '4FXX' '4FXX' '4FXX' '4FXX' '4FXX' '4FXX' '4F41' '4F42' '4F43' '4F44' '4F45' '4F46' '4F47' '4F47' '4F48' '4F48' '4F49' '4F4A' '4F4B' '4F81' '4F82' '4F83' '6F05' '6F06' '6F07' '6F08' '6F09' '6F2C' '6F31' '6F32' '6F37' '6F38' '6F39' '6F3B' '6F3C' '6F3E' '6F3F'
203 Description Application directory Preferred languages Access rule reference ICC identification Image data GSM Ciphering key Kc Image instance data files Unique identifier Phone book synchronisation counter Change counter Previous unique identifier Phone book reference file SoLSA Access Indicator SoLSA LSA List LSA Descriptor files Capability configuration parameters 1 GPRS Ciphring key KcGPRS CPBCCH Information Investigation PLMN scan E-mail addresses Additional number alpha string Second name entry Abbreviated dialling numbers Grouping file Grouping information alpha string Phone book control Index administration phone book Additional number Extension 1 Pseudonym User Controlled PLMN selector for I-WLAN Operator Controlled PLMN selector for IWLAN User Controlled WSID list Operator controlled WSID list WLAN Reauthentication Identity Home I-WLAN Specific Identifier List Multimedia Messages List I-WLAN Equivalent HPLMN Presentation Indication Multimedia Messages Data File I-WLAN HPLMN Indication I-WLAN Last Registered PLMN HPLMN Direct Access Indicator Allowed CSG lists CSG Type HNB name Language indication Access rule reference (under ADFUSIM and DFTELECOM) IMSI Ciphering and integrity keys Ciphering and integrity keys for packet switched domain De-personalization control keys Higher Priority PLMN search period Co-operative network list ACM maximum value USIM service table Accumulated call meter Fixed dialling numbers Short messages Group identifier level 1 Group identifier level 2
3GPP TS 31.102 V8.14.0 (2012-01) Value Card issuer/operator dependant 'FFFF' Card issuer/operator dependant operator dependant '00FF...FF' 'FF...FF07' 'FFFF' '0000' '00000000' '0000' '0000' Operator dependant '00FF...FF' 'FF...FF' 'FFFF' 'FFFF' 'FF...FF07' 'FF..FF' '00' 'FFFF' 'FFFF' 'FFFF' 'FF...FF' '0000' 'FFFF' '0000' 'FFFF' 'FFFF' '00FF...FF' '00FFFF' 'FFFF' Operator dependant '00FFFF' Operator dependant 'FFFF' Operator dependent 'FFFF' Operator dependent 'FFFF' Operator dependent 'FFFFFF' Operator dependent Operator dependent Operator dependent Operator dependent 'FFFF' Card issuer/operator dependant Operator dependant '07FFFF' '07FFFF' 'FFFF' 'FF' 'FFFF' '000000' (see note 1) Operator dependant '000000' 'FF...FF' '00FF...FF' Operator dependant Operator dependant
3GPP
Release 8 '6F40' '6F41' '6F42' '6F43' '6F45' '6F46' '6F47' '6F48' '6F49' '6F4B' '6F4C' '6F4D' '6F4E' '6F4F' '6F50' '6F54' '6F55' '6F56' '6F57' '6F58' '6F5B' '6F5C' '6F60' '6F61' '6F62' '6F73' '6F78' '6F7B' '6F7E '6F80' '6F81' '6F82' '6F83' '6FAD' '6FB1' '6FB2' '6FB3' '6FB4' '6FB5' '6FB6' '6FB7' '6FC3' '6FC4' '6FC5' '6FC6' '6FC7' '6FC8' '6FC9' '6FCA' '6FCB' '6FCC' '6FCD' '6FCE' '6FCF' '6FD0' '6FD1' '6FD2' '6FD3' '6FD4' '6FD5' '6FD6' '6FD7'
204 MSISDN storage PUCT SMS parameters SMS status CBMI Service provider name Short message status reports CBMID Service Dialling Numbers Extension 2 Extension 3 Barred Dialling Numbers Extension 5 Capability configuration parameters 2 CBMIR SetUp Menu Elements Extension 4 Enabled services table Access point name control list Comparison method information Initialisation value for Hyperframe number Maximum value of START User controlled PLMN selector with Access Technology Operator controlled PLMN selector with Access Technology HPLMN selector with Access Technology Packet switched location information Access control class Forbidden PLMNs Location information Incoming call information Outgoing call information Incoming call timer Outgoing call timer Administrative data Voice Group Call Service Voice Group Call Service Status Voice Broadcast Service Voice Broadcast Service Status EMLPP AaeM Emergency call codes Key for hidden phone book entries Network Parameters PLMN Network Name Operator Network List Mailbox Dialling Numbers Extension 6 Mailbox Identifier Message Waiting Indication Status Call Forwarding Indication Status Extension 7 Service Provider Display Information MMS Notification Extension 8 MMS Issuer Connectivity Parameters MMS User Preferences MMS User Connectivity Parameters Network's Indication of Alerting (NIA) Voice Group Call Service Ciphering Algorithm Voice Broadcast Service Ciphering Algorithm GBA Bootstrapping parameters MBMS Service Keys List
3GPP TS 31.102 V8.14.0 (2012-01) 'FF...FF' 'FFFFFF0000' 'FF...FF' 'FF...FF' 'FF...FF' Operator dependant '00FFFF' 'FF...FF' 'FF...FF' '00FF...FF' '00FF...FF' 'FF...FF' '00FF...FF' 'FF...FF' 'FF...FF' Operator dependant '00FF...FF' Operator dependant '00FFFF' 'FFFF' 'F0 00 00 F0 00 00' Operator dependant 'FFFFFF0000..FFFFFF0000' 'FFFFFF0000..FFFFFF0000' 'FFFFFF0000..FFFFFF0000' 'FFFFFFFF FFFFFF xxxxxx 0000 FF 01' (see note 2) Operator dependant 'FF...FF' 'FFFFFFFF xxxxxx 0000 FF 01' (see note 2) 'FFFF 000000 00 01FFFF' 'FFFF 000000 01FFFF' '000000' '000000' Operator dependant Operator dependant Operator dependant Operator dependant Operator dependant Operator dependant '00' Operator dependant 'FFFF' 'FFFF' Operator dependant Operator dependant Operator dependant '00 FF...FF' Operator dependant '00 00 00 00 00' 'xx 00 FF...FF' '00 FF...FF' '00 00 00 FFFF' '00FF...FF' 'FFFF' 'FFFF' 'FFFF' 'FF...FF' '0000' '0000' 'FFFF' 'FFFF'
3GPP
Release 8 '6FD8' '6FD9' '6FDA' '6FDB' '6FDC' '6FDD' '6FDE' '6FDF' '6FE0' '6FE1' '6FE2' '6FE3' '6FE4' '6FE5'
205 MBMS User Key EHPLMN GBA NAF List EHPLMN Presentation Indication Last RPLMN Selection Indication NAF Key Centre Address Service Provider Name Icon PLMN Network Name Icon In Case of Emergency Dialling Number In Case of Emergency Free Format Network Connectivity Parameters for UICC IP connections EPS location information EPS NAS Security Context Public Service Identity of the SM-SC
3GPP TS 31.102 V8.14.0 (2012-01) 'FFFF' 'FFFF' or xxxxxx (see Note 2) 'FFFF' '00' '00' 'FFFF' '00 FFFF' '00 FFFF' Operator dependant Operator dependant Operator dependant 'FFFFFFFFFFFFFFFFFFFFFFFF xxxxxx0000 01' (see note 2) 'FFFF' Operator dependant
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 8
206
2nd record:
CI (2 bytes)
CI (2 bytes)
CI (2 bytes)
Identifier (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 type = LSA ID and number = 1 (1 byte) LSA ID (3 bytes) 'FF' Identifier (1 byte)
2nd record:
CI (2 bytes)
CI (2 bytes)
Identifier (1 byte)
3GPP
Release 8
207
3GPP
Release 8
208
Rec 2 Tag'A8' L='2D' Tag'C0' L='03' '4F3B' Tag'C4' L='03' '4F12' Tag'C3' L='03' '4F1A' Tag'AA' L='0F' Tag'C2' L='03' '4F4A'
(for Phonebook Set 2) '0A' '0D '10' Tag'C5' L='03' '4F0A' Tag'C4' L='03' '4F14' Tag'C9' L='03' '4F20' '0B' '0E' '13' Tag'C6' L='03' '4F25' Tag'C4' L='03' '4F16' Tag'CA' L='03' '4F51' '0C' '0F' '11'
'08'
'14'
'15'
#1
#2
UID
email address
#3 : : : # 254
Table G.4: Structure of phone book entries 255 to 508 (Rec 1-254)
Phone book entry ADN1 PBC1 '4F3B' '4F0A' SFI '0A' SFI '0B' ADN EXT1 Hidden Content Ident. (AID Bytes (Byte Rec n (1X+14): 3) (X+13)) Rec '03' ADN EXT1 Not Content Ident. Hidden Bytes (Byte (1X+14): (X+13)) Rec '2B' GRP1 ANRA1 ANRB1 '4F25' '4F12' '4F14' SFI '0C' SFI '0D' SFI '0E' Rec n1 ANRA1 ANRB1 Rec n3 Rec n1 Rec n1 '00' ANRC1 '4F16' SFI '0F' ANRC1 Rec n1 SNE1 '4F1A' SFI '10' Second Name Alpha String Second Name Alpha String UID1 '4F20' SFI '13' UID AAS '4F4B' SFI '14' Record numbers as defined in the ANRs Rec '2B' Record numbers as defined in the ANRs EXT1 '4F4A' SFI '08' Rec '03' GAS EMAIL1 '4F4C' '4F51' SFI '15' SFI '11' Record email no.'s as address defined in GRP1 Record email no.'s as address defined in GRP1
#255
#256
UID
#257 : : : #508
3GPP
Release 8
209
1 :1
ADN 1 ...
1 :1
PBC 1 ...
1 :1
E M A IL 1 ...
SNE 1 ...
254
1 :1
254
254
254
254
254 G RP 1
254
EXT1 1 ...
G AS 1 ...
G R P1 1
1 :1
254 PBC1 1 ... E M A IL 1 1 1 ... 254 ... ANRC1 1 ... SNE1 1 ... 254
ADN1 1 ...
1 :1
254
254
254
254
254
1 :1
3GPP
Release 8
210
H.1
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
3GPP
Release 8
211
H.3
File Identification '4F41' '4F42' '4F43' '4F44' '4F45' '4F46' '4F47' '4F48' '4F49' '4F4A' '4F4B'
H.4
3GPP
Release 8
212
Terminal Application selection Select AID=USIM (P2='00') Select File Id Application initialisation procedure is terminated Status (P1='01')
UICC
Read Binary
Terminal Application termination procedure is started Status (P1='02') Select File Id Select AID=USIM (P2='40')
UICC
Update Binary
Application closure
3GPP
Release 8
213
3GPP
Release 8
214
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 0x5F 0x6E 0x61 0x6D 0x65 0x00 (authentication id = "dummy_name"; 12 Bytes) 0x0E 0x64 0x75 0x6D 0x6D 0x79 0x5F 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 0x5F 0x6E 0x61 0x6D 0x65 0x00 (authentication id = "dummy_name"; 12 Bytes) 0x1B 0x64 0x75 0x6D 0x6D 0x79 0x5F 0x70 0x61 0x73 0x73 0x77 0x6F 0x72 0x64 0x00 (authentication pw = "dummy_password"; 16 Bytes)
3GPP
Release 8
215
GroupId 00000000 00000001 00000012 00000123 00001234 00012345 00123456 01234567 12345678 99999999 13452670
3GPP
Release 8
216
3GPP
Release 8
TSG # / Date TP-27 TP-27 CT-28 CT-28 CT-28 CT-28 CT-28 CT-28 CT-28 CT-28 CT-28 CT-29 CT-29 CT-30 CT-30 CT-31 CT-31 CT-31 CT-31 CT-31 CT-32 CT-32 CT-33 CT-34 CT-34 CT-34 CT-34 CT-34 CT-34 CT-35 CT-35 CT-35 CT-35 CT-36 CT-36 CT-36 2007-06 CT-37 CT-37 CT-38 CT-38 CT-38 CT-39 CT-39 CT-39 CT-39 CT-39 CT-40 CT-41 CT-41 CT-41 CT-41 CT-42 CT-42 CT-42 CT-42 CT-42 CT-43 CT-43 CT-43 TSG Doc. TP-050018 CP-050136 CP-050139 CP-050139 CP-050139 CP-050139 CP-050139 CP-050139 CP-050139 CP-050139 CP-050460 CP-050460 CP-050499 CP-050499 CP-060018 CP-060023 CP-060023 CP-060023 CP-060156 CP-060239 CP-060239 CP-060385 CP-060541 CP-060541 CP-060541 CP-060541 CP-060541 CP-060547 CP-070072 CP-070067 CP-070067 CP-070071 CP-070305 CP-070299 CP-070464 CP-070620 CP-070611 CP-070840 CP-070840 CP-070841 CP-080166 CP-080167 CP-080168 CP-080168 CP-080168 CP-080385 CP-080582 CP-080642 CP-080642 CP-080642 CP-080904 CP-080904 CP-080904 CP-080909 CP-080961 CP-090188 CP-090188 CP-090188 WG doc T3-050189 C6-050402 C6-050370 C6-050372 C6-050374 C6-050376 C6-050404 C6-050478 C6-050483 C6-050406 C6-050689 C6-050729 C6-050876 C6-050898 C6-060158 C6-060119 C6-060122 C6-060184 C6-060121 C6-060277 C6-060279 C6-060601 C6-060781 C6-060808 C6-060785 C6-060764 C6-060817 C6-060788 C6-070059 C6-070120 C6-070133 C6-070123 C6-070311 C6-070310 C6-070417 C6-070434 C6-070523 C6-070586 C6-070884 C6-080063 C6-080059 C6-080014 C6-080064 C6-080070 C6-080147 C6-080273 C6-080266 C6-080289 C6-080245 C6-080469 C6-080468 C6-080444 C6-080409 -------------C6-090007 C6-090056 C6-090077 CR 0264 0277 0272 0285 0280 0282 0287 0289 0291 0278 0294 0295 0298 0297 0304 0299 0302 0305 0301 0308 0310 0318 0320 0322 0324 0327 0332 0331 0340 0334 0336 0339 0341 0349 0350 0347 0352 0355 0354 0343 0365 0362 0360 0366 0357 0368 0372 0373 0375 0376 0374 0380 0382 0383 0385 0386 0387 0390 Rev 1 Cat F A A A A A A A F F F F A A C F C A A A F A A A A A F F B B A B F A B A F F B A A F B B F A B B B B B B F B F F B
217
Subject/Comment
2 2
1 -
1 1 2 1 2 2 1 1 1 1 3 5 1 1 1 3 1 2 2 5 4 1 2 1 -
Creation of Rel-7 version based on v6.9.0 Correction to overcome IMSI number space limitation inclusion of EHPLMN ISO/IEC 7816-series revision Essential correction of the phonebook (access to mapped filed & "hidden key" coding) Added EF_ARR under DF_TELECOM Modifications regarding WLAN Alignment of MBMS procedures with TS 33.246 Number of stored MSKs Essential correction of phonebook support Corrections to eMLPP and AAeM Correction to EF-HPLMN Clarification on ADM access condition Editorial corrections Clarifications in DF_PHONEBOOK level NAF Id alignment with TS 33.246 Addition of mandatory UST services id references for VGCS/VBS security context definition Change to allow PNN segmentation of the HPLMN and EHPLMN support Indication of services in the USIM Correction of service numbers associated to the UST Padding of VSTK_RAND MCC Completion of implementation of C6-060184 USAT related procedures - Additional Terminal Profile VService_Id coding examples Essential correction of the authenticate command in order to process message longer than 255 bytes Correction of the MSK Update procedures Clarification of the USIM behavior when MSK key is not updated Correction of MBMS Security Context description Correction of the references to a non-exisiting table in Authenticate command description Correction of the MUK Update procedures Correction of the Tables in section 7.1.2.5 Correction of the EHPLMN SFI Presentation of EHPLMN Last RPLMN Selection Indication MSK management procedures Presentation of additional information in manual selection mode Correction of EF-IMG and EF-IIDF GBA NAF Keys and MUKs storage policy Correction to implementation of '0x' as '04' in 7.1.2.5 (MCC) Key Establishment mechanism: alignment with TS 33.110 Inconsistency in the MSK update procedures Correction of reference to 3GPP TS 23.140 Completion of missing "Terminal Applications" entry in the UST Reservation of parameters for OMA BCAST Smart Card Profile MBMS security Authentication error 9866 Add the support of EHPLMN in the automatic network selection Correction of UST due to error in CR implementation Correction of typo in the description of one of the fields of EFMBI. Storage of SPN and PNN in graphic format Note: changes to clauses 5.3.10 and 5.3.24 have been moved to new sections with appropriate names. Clarification of content of EFUID Authentication of GBA Introduction of ICE information in the UICC Configuration of Network Connectivity parameters for UICC remote IP connections Introduction of new access technologies for LTE Storage of EPS Mobility Management parameters USIM provisioning for home (e)NodeB Support for LTE in the EF-Operator PLMN Correction to Example for MMS Issuer/User Connectivity Parameters Addition of I-WLAN related files and procedures Removal of KNASint and KNASenc in EFEPSNSC Correction of EF EPSNSC Support of EPS in USAT: extension of Call control
3GPP
Release 8
CT-43 CT-43 CT-44 CT-44 CT-44 CT-44 CT-44 CT-44 CT-44 CT-45 CT-45 CT-45 CT-46 CT-46 CT-46 CT-48 CT-49 CT-49 CT-49 CT-50 CT-50 CT-52 CT-53 CT-54 CP-090192 CP-090198 CP-090451 CP-090451 CP-090479 CP-090479 CP-090451 CP-090451 CP-090451 CP-090712 CP-090712 CP-090713 CP-091011 CP-090992 CP-090990 CP-100391 CP-100585 CP-100586 CP-100586 CP-100826 CP-100826 CP-110516 CP-110593 CP-110898 C6-090074 C6-090080 C6-090110 C6-090188 ----------------------------C6-090112 C6-090116 C6-090160 C6-090305 C6-090301 C6-090309 C6-090436 C6-090439 C6-090459 C6-100281 C6-100400 C6-100357 C6-100384 C6-100595 C6-100636 --------------C6-110412 C6-110571 0388 0384 0391 0392 0396 0398 0399 0400 0405 0402 0406 0409 0394 0424 0426 0437 0444 0442 0445 0449 0465 0478 0486 0488 1 5 2 2 2 1 1 2 1 1 1 1 B F F F D A F F C F F F F F F F F F F F F F F F
218
1 3 1 2
HPLMN Direct Access Indicator for I-WLAN Correction of Network Connectivity parameters for UICC remote IP connections (Email approval) correction of coding of sugested contents of the EF_EPSLOCI at pre-personalization correction of update status via Data Download or USAT Application for EF_EPSLOCI and EF_EPSNSC Editorial modifications of File structure overview Correction of wrong file names Removal of NH and NCC parameters from EFEPSNSC Correction for EPS in USIM security related procedures Allowed CSG List updateable by ME eCALL related enhancements Correction of coding of CSG ID Essential correction of EFSPDI encoding Reference update Correction of incorrect tag value Correction of Allowed CSG list (Combination of C6-090413 and C6-090419) ICE related procedure Introduction of an ISIM EF to support Public Service Identity for SMS over IP Update of reference to ETSI TS 102 483 Alignment of HNB and HeNB to the service requirements Correction to Issuer specified PIN for ICE files Correction of EF_EPSNSC content description Essential correction to EPS NAS security context update Clarification of ACL in EPS Network Correction to Allowed CSG List coding
3GPP