8 Test USIM Parameters
34.1083GPPCommon test environments for User Equipment (UE)Conformance testingRelease 15TS
8.1 Introduction
This clause defines default parameters for programming the elementary files of the test USIM. The requirements of this clause do not apply to the USIM/ME tests of 3GPP TS 31.120 [39] and 3GPP TS 31.121 [40].
8.1.1 Definitions
"Test USIM card":
A USIM card supporting the test algorithm for authentication, programmed with the parameters defined in this clause. The electrical, mechanical and environmental requirements of the test USIM card are specified in 3GPP TS 31.101 [22] and 3GPP TS 31.102 [23].
"Test USIM":
Either a test USIM card or the USIM simulator programmed with the parameters defined in this clause.
8.1.2 Definition of the test algorithm for authentication
In order to be able to easily test the UMTS authentication and key agreement procedure as specified in 3GPP TS 33.102 [24] and 3GPP TS 33.105 [26] along the whole system, the availability of a test algorithm for generation of authentication vector based on quintets is needed (in GSM triplets was used). Additionally, calculation of the parameters for re-synchronization requests is needed. The definition of the test algorithm are the functions f1, f2, f3, f4, f5 and the corresponding functions for re-synchronization are f1* and f5*.
For test USIM intended to be used for inter-RAT or GERAN-only test cases then the test USIM shall support the conversion functions c2 and c3 according to 3GPP TS 33.102 [24], clause 6.8.1.2 to derive the GSM SRES and ciphering key Kc from the UMTS XRES and cipher/integrity keys CK and IK.
The test algorithm defined in the present clause shall be implemented in test USIM cards as well in test USIM simulators and SS. The test algorithm may also, for test purposes, be implemented in AUC.
The following procedure employs bit wise modulo 2 addition ("XOR").
The following convention applies:
All data variables in the specification of this test algorithm are presented with the most significant substring on the left hand side and the least significant substring on the right hand side. A substring may be a bit, byte or other arbitrary length bitstring. Where a variable is broken down into a number of substrings, the leftmost (most significant) substring is numbered 0, the next most significant is numbered 1, and so on through to the least significant.
8.1.2.1 Authentication and key derivation in the test USIM and SS
The following steps describe sequence of operations for the functions f1, f2, f3, f4 and f5 to perform in the test USIM and SS, in order to obtain the XMAC/MAC, RES/XRES, CK, IK, Kc and AK respectively, to be used in the authentication and key agreement procedure.
Step 1:
XOR to the challenge RAND, a predefined number K (in which at least one bit is not zero, see clause 8.2), having the same bit length (128 bits) as RAND.
The result XDOUT of this is:
XDOUT[bits 0,1, . . .126,127] = K [bits 0,1, . . .126,127] XOR RAND[bits 0,1, . . .126,127]
Step 2:
RES (test USIM), XRES (SS), CK, IK and AK are extracted from XDOUT this way:
RES[bits 0,1, . . .n-1,n] = f2(XDOUT,n) = XDOUT[bits 0,1, . . .n-1,n] (with 30 < n < 128)
NOTE: Suggested length for RES is 128 bits (i.e. n = 127).
In SS and AUC, the XRES calculation is identical to RES.
CK[bits 0,1, . . .126,127] = f3(XDOUT) = XDOUT[bits 8,9, . . .126,127,0,1, . . .6,7]
IK[bits 0,1, . . . 126,127] = f4(XDOUT) = XDOUT[bits 16,17, . . .126,127,0,1, . . .14,15]
AK[bits 0,1, . . . 46,47] = f5(XDOUT) = XDOUT[bits 24,25, . . .70,71]
For test USIM intended for inter-RAT testing the GSM ciphering key Kc shall be derived from the UMTS cipher/integrity keys:
Kc[bits 0,1, . . . 62,63] = c3(CK,IK), see 3GPP TS 33.102 [24], clause 6.8.1.2.
Step 3:
Concatenate SQN with AMF to obtain CDOUT like this:
CDOUT[bits 0,1,. . .62,63] = SQN[bits 0,1,. . .46,47] || AMF[bits 0,1,. . .14,15]
NOTE: For test USIM the SQN = SQNMS = SQNSS[bits 0,1,. . .46,47] = AUTN[bits 0,1,. . .46,47] XOR AK[bits 0,1, . . . 46,47] where AUTN is the received authentication token.
Step 4:
XMAC (test USIM) and MAC (SS) are calculated from XDOUT and CDOUT this way:
XMAC[bits 0,1, . . .62, 63] = f1(XDOUT, CDOUT) = XDOUT[bits 0,1. . .62,63] XOR CDOUT[bits 0,1,. . .62,63]
NOTE: In SS and AUC, the MAC calculation is identical to XMAC.
Step 5:
The SS calculates the authentication token AUTN:
AUTN[bits 0,1,..126,127] = SQN AK[bits 0,1,. . .46,47] || AMF[bits 0,1,. . .14,15] || MAC[bits 0,1, . . .62, 63]
Where SQN AK[bits 0,1,. . .46,47] = SQN[bits 0,1,. . .46,47] XOR AK[bits 0,1, . . . 46,47]
8.1.2.2 Generation of re-synchronization parameters in the USIM
For SS to be able to initiate an authentication re-synchronization procedure a specific AMF value has been defined.
AMFRESYNCH = AMF[bits 0,1,..14,15] = "1111 1111 1111 1111"
When the test USIM receives an authentication token (AUTN) having the value of AMF field equal to the AMFRESYNCH value then the test USIM shall initiate the re-synchronization procedure.
When the test USIM starts the re-synchronization procedure, the MAC-S and AK have to be calculated using the functions f1* and f5*, which in the test algorithm are identical to f1 and f5, respectively.
Step 1:
XOR to the challenge RAND, a predefined number K (in which at least one bit is not zero, see 8.2), having the same bit length (128 bits) as RAND.
The result XDOUT of this is:
XDOUT[bits 0,1, . . .126,127] = K[bits 0,1, . . .126,127] XOR RAND[bits 0,1, . . .126,127]
Step 2:
AK is extracted from XDOUT this way:
AK[bits 0,1, . . . 46,47] = f5*(XDOUT) = XDOUT[bits 24,25, . . .70,71]
Step 3:
Concatenate SQNMS with AMF* to obtain CDOUT like this:
CDOUT[bits 0,1,. . .62,63] = SQNMS[bits 0,1,. . .46,47] || AMF*[bits 0,1,. . .14,15]
Where AMF* assumes a dummy value of all zeros.
NOTE 1: For test USIM the SQNMS = SQNSS[bits 0,1,. . .46,47] = AUTN[bits 0,1,. . .46,47] XOR AK[bits 0,1, . . . 46,47] where AUTN is the received authentication token.
NOTE 2: For SS and AUC the SQNMS = AUTS[bits 0,1,. . .46,47] XOR AK[bits 0,1, . . . 46,47] where AUTS is the received re-synchronization parameter.
Step 4:
MAC-S is calculated from XDOUT and CDOUT this way:
MAC-S[bits 0,1, . . .62, 63] = f1*(XDOUT, CDOUT) = XDOUT[bits 0,1. . .62,63] XOR CDOUT[bits 0,1,. . .62,63]
NOTE: In SS and AUC, the XMAC-S calculation is identical to MAC-S.
Step 5:
The test USIM calculates the re-synchronization parameter AUTS:
AUTS[bits 0,1,..110,111] = SQNMS AK[bits 0,1,. . .46,47] || MAC-S[bits 0,1, . . .62, 63]
Where SQNMS AK[bits 0,1,. . .46,47] = SQNMS [bits 0,1,. . .46,47] XOR AK[bits 0,1, . . . 46,47]
8.1.2.3 Using the authentication test algorithm for UE conformance testing
8.1.2.3.1 Authentication accept case
The authentication accept case is illustrated in figures 8.1.2.3.1 and 8.1.2.3.2.
The SS calculates the authentication token AUTN according to the test algorithm as specified in clause 8.1.2.1 (step 1 to step 5) using an AMF value different from the AMFRESYNCH value.
The SS sends an authentication request, including RAND and AUTN parameters, to the ME/USIM.
Based on the received RAND parameter the test USIM calculates the RES, CK, IK, Kc and XMAC parameters according to clause 8.1.2.1 (step 1 to step 4). The test USIM extracts the SQNMS = SQNSS, AMF and MAC parameters from the received authentication token AUTN.
The test USIM checks that XMAC = MAC and then return the RES, CK and IK parameters to the ME.
Figure 8.1.2.3.1: Network accepted by UE (USIM not supporting derivation of GSM cipher key Kc)
Figure 8.1.2.3.2: Network accepted by UE (USIM supporting derivation of GSM cipher key Kc)
8.1.2.3.2 MAC failure case
The MAC failure case is illustrated in figure 8.1.2.3.2.
The SS calculates the authentication token AUTN according to the test algorithm as specified in clause 8.1.2.1 (step 1 to step 5) using an AMF value different from the AMFRESYNCH value and a MAC value different from what is calculated in clause 8.1.2.1 step 4.
The SS sends an authentication request, including RAND and AUTN parameters, to the ME/USIM.
Based on the received RAND parameter The test USIM calculates the RES, CK, IK, Kc and XMAC parameters according to clause 8.1.2.1 (step 1 to step 4).
The test USIM extracts the SQNMS = SQNSS, AMF and MAC parameters from the received authentication token AUTN.
When the test USIM identifies that the calculated XMAC value is different from the MAC value received in AUTN then the USIM notifies the ME of the MAC failure and the ME sends an AUTENTICATION FAILURE message to the SS (cause "MAC failure").
Figure 8.1.2.3.2: MAC failure cases
8.1.2.3.3 SQN failure case
The SQN failure case is illustrated in figure 8.1.2.3.3.
The SS calculates the authentication token AUTN according to the test algorithm as specified in clause 8.1.2.1 (step 1 to step 5) using an AMF value equal to AMFRESYNCH.
The SS sends an authentication request, including RAND and AUTN parameters, to the UE/USIM.
The test USIM extracts the SQNMS = SQNSS, AMF and MAC parameters from the received authentication token AUTN.
When the test USIM identifies that the AMF field is equal to the AMFRESYNCH value it calculates the re-synchronization parameter AUTS as specified in clause 8.1.2.2 (step 1 to step 5) and forward it to the ME.
The ME sends an AUTHENTICATION FAILURE message to the SS including the AUTS parameter.
Figure 8.1.2.3.3: SQN failure case
8.1.3 Definition of the test algorithm for VGCS/VBS VSTK generation
In order to be able to easily test the VGCS/VBS key generation and encryption as specified in TS 43.020 [44] and TS 31.102 [23] along the whole system, the availability of a test algorithm for generation of the VSTK-key is needed.
The test algorithm defined in the present clause shall be implemented in test USIM cards as well in test USIM simulators and SS.
The following procedure employs bit wise modulo 2 addition ("XOR").
The following convention applies:
All data variables in the specification of this test algorithm are presented with the most significant substring on the left hand side and the least significant substring on the right hand side. A substring may be a bit, byte or other arbitrary length bitstring. Where a variable is broken down into a number of substrings, the leftmost (most significant) substring is numbered 0, the next most significant is numbered 1, and so on through to the least significant.
8.1.3.1 VSTK generation in the test USIM and SS
The following steps describe the sequence of operations for the function A8_V (TS 43.020 [44]) to be performed in the test USIM and SS, in order to obtain the VSTK, to be used in the subsequent ME/BSS key derivation steps for VGCS/VBS ciphering.
Step 1:
Expand the 36-bit value VSTK_RAND to an intermediate 40-bit value EXPAND:
FILLER[bits 0,..7] = “11111111”
EXPAND [bits 0,1, . . .39] = FILLER[bits 0,..3] || VSTK_RAND[bits 0,1, . . .35]
Expand the 40-bit value EXPAND to a 128-bit value EXP_RAND:
EXP_RAND[bits 0,1, . . .126,127] = EXPAND[bits 0,1, . . .39] || EXPAND[bits 0,1, . . .39] || EXPAND[bits 0,1, . . .39] || FILLER[bits 0,..7]
Step 2:
XOR the expanded 128 bit EXP_RAND with a stored V_Ki i.e. a 128 bit Voice Group or Broadcast Group Key (128 bit) number taken by the USIM from an internal table indexed by VK_Id and Group_Id
The result VSTK of this is:
VSTK[bits 0,1, . . .126,127] = V_Ki [bits 0,1, . . .126,127] XOR EXP_RAND[bits 0,1, . . .126,127]
8.2 Default Parameters for the test USIM
K:
Size: 16 Bytes
Default values: Bytes 1 (HEX): 00
Bytes 2 (HEX): 01
Bytes 3 (HEX): 02
Bytes 4 (HEX): 03
Bytes 5 (HEX): 04
Bytes 6 (HEX): 05
Bytes 7 (HEX): 06
Bytes 8 (HEX): 07
Bytes 9 (HEX): 08
Bytes 10 (HEX): 09
Bytes 11 (HEX): 0A
Bytes 12 (HEX): 0B
Bytes 13 (HEX): 0C
Bytes 14 (HEX): 0D
Bytes 15 (HEX): 0E
Bytes 16 (HEX): 0F
PIN Disabling:
The PIN enabled / disabled flag will be set to "PIN Disabled". This ensures that when the Test USIM is inserted into a UE the user will not be prompted for PIN entry.
8.3 Default settings for the Elementary Files (EFs)
The format and coding of elementary files of the USIM are defined in 3GPP TS 31.101 [22] and 3GPP TS 31.102 [23]. The following clauses define the default parameters to be programmed into each elementary file. Some files may be updated by the UE based on information received from the SS. These are identified in the following clauses.
If EFs have an unassigned value, it may not be clear from the main text what this value should be. This clause suggests values in these cases.
8.3.1 Contents of the EFs at the MF level
8.3.1.1 EFDIR
8.3.1.2 EFICCID (ICC Identity)
The programming of this EF is a test house option.
8.3.1.3 EFPL (Preferred Languages)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.1.4 EFARR (Access rule reference)
The programming of this EF is a test house option.
8.3.2 Contents of files at the USIM ADF (Application DF) level
8.3.2.1 EFLI (Language Indication)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.2 EFIMSI (IMSI)
The IMSI value will be chosen by the test house. The IMSI used by the SS will align this value.
File size: 9 bytes
Default values: Byte 1 (DEC): 8
Bytes 2 to 9 (HEX): 09 10 10 ** ** ** ** **
49 24 10 ** ** ** ** ** (for Band VI and Band IX)
"*" indicates any number between 0 and 9 subject to the restriction that IMSI mod 1000 (i.e. bytes 7, 8 and 9) lies in one of the following ranges:
– 063 to 125, 189 to 251, 315 to 377, 441 to 503, 567 to 629, 693 to 755, 819 to 881 or 945 to 999.
NOTE: This ensures that the UE can listen to the second CCCH when more than one basic physical channel is configured for the CCCH. This is necessary for the test of "paging re-organization".
8.3.2.3 EFKeys (Ciphering and Integrity Keys)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.4 EFKeysPS (Ciphering and Integrity Keys for Packet Switched domain)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.5 EFPLMNwAcT (User controlled PLMN selector with Access Technology)
File size: 5n bytes
Default values (HEX): Bytes 1 to 3: 32 F4 10 (MCC, MNC) – Translates to 234, 01
Bytes 4 to 5: C8 B0 (Access Technology) – Translates to UTRAN,
E-UTRAN, NG-RAN, GSM, cdma2000 HRPD,
cdma2000 1xRTT
Bytes 6 to 8: 32 F4 20 (MCC, MNC)
Bytes 9 to 10: C8 B0 (Access Technology)
Bytes 11 to 13: 32 F4 30 (MCC, MNC)
….
….
….
Bytes(5n-4) to (5n-2): 32 F4 43 (MCC, MNC)
Bytes (5n-1) to 5n: C8 B0 (Access Technology)
PLMNs are shown coded above since this is the largest number required for a test. It is necessary to take this into account since the USIM cards must be dimensioned to cope with this number of records.
8.3.2.6 EFHPPLMN (Higher Priority PLMN search period)
File size: 1 byte
Default value (HEX): 00 (No higher priority PLMN search attempts)
8.3.2.7 EFACMmax (ACM maximum value)
File size: 3 bytes
Default: Byte 1: 00
Byte 2: 00
Byte 3: 00
The above translates to: "Not valid".
8.3.2.8 EFUST (USIM Service Table)
Services will be allocated and activated as follows.
|
Services |
Activated |
Version |
|
|---|---|---|---|
|
Service n°1 : |
Local Phone Book |
Option |
|
|
Service n°2 : |
Fixed Dialling Numbers (FDN) |
Option |
|
|
Service n°3 : |
Extension 2 |
Option |
|
|
Service n°4 : |
Service Dialling Numbers (SDN) |
Option |
|
|
Service n°5 : |
Extension3 |
Option |
|
|
Service n°6 : |
Barred Dialling Numbers (BDN) |
Option |
|
|
Service n°7 : |
Extension4 |
Option |
|
|
Service n°8 : |
Outgoing Call Information (OCI and OCT) |
Option |
|
|
Service n°9 : |
Incoming Call Information (ICI and ICT) |
Option |
|
|
Service n°10: |
Short Message Storage (SMS) |
Yes |
|
|
Service n°11: |
Short Message Status Reports (SMSR) |
Option |
|
|
Service n°12: |
Short Message Service Parameters (SMSP) |
Yes |
|
|
Service n°13: |
Advice of Charge (AoC) |
Yes |
|
|
Service n°14: |
Capability Configuration Parameters (CCP) |
Yes |
|
|
Service n°15: |
Cell Broadcast Message Identifier |
Yes |
|
|
Service n°16: |
Cell Broadcast Message Identifier Ranges |
Yes |
|
|
Service n°17: |
Group Identifier Level 1 |
Option |
|
|
Service n°18: |
Group Identifier Level 2 |
Option |
|
|
Service n°19: |
Service Provider Name |
Option |
|
|
Service n°20: |
User controlled PLMN selector with Access Technology |
Yes |
|
|
Service n°21: |
MSISDN |
Option |
|
|
Service n°22: |
Image (IMG) |
Option |
|
|
Service n°23: |
Not used (reserved for SoLSA) |
No |
|
|
Service n°24: |
Enhanced Multi‑Level Precedence and Pre‑emption Service |
Option |
|
|
Service n°25: |
Automatic Answer for eLMPP |
Option |
|
|
Service n°26: |
RFU |
No |
|
|
Service n°27: |
GSM Access |
Yes |
|
|
Service n°28: |
Data download via SMS-PP |
Option |
|
|
Service n°29: |
Data download via SMS‑CB |
Option |
|
|
Service n°30: |
Call Control by USIM |
Option |
|
|
Service n°31: |
MO-SMS Control by USIM |
Option |
|
|
Service n°32: |
RUN AT COMMAND command |
Option |
|
|
Service n°33: |
Packet Switched Domain |
Yes |
|
|
Service n°34: |
Enabled Services Table |
Yes |
|
|
Service n°35: |
APN Control List (ACL) |
Option |
|
|
Service n°36: |
Depersonalization Control Keys |
Option |
|
|
Service n°37: |
Co-operative Network List |
Option |
|
|
Service n°38: |
GSM security context |
Yes |
|
|
Service n°39: |
CPBCCH Information |
Yes |
|
|
Service n°40: |
Investigation Scan |
Yes |
|
|
Service n°41: |
MExE |
Option |
|
|
Service n°42 |
Operator controlled PLMN selector with Access Technology |
Yes |
|
|
Service n°43 |
HPLMN selector with Access Technology |
Yes |
|
|
Service n°44 |
Extension 5 |
Option |
|
|
Service n°45 |
PLMN Network Name |
Option |
|
|
Service n°46 |
Operator PLMN List |
Option |
|
|
Service n°47 |
Mailbox Dialling Numbers |
Option |
|
|
Service n°48 |
Message Waiting Indication Status |
Option |
|
|
Service n°49 |
Call Forwarding Indication Status |
Option |
|
|
Service n°50 |
Reserved and shall be ignored |
Option |
|
|
Service n°51 |
Service Provider Display Information |
Option |
|
|
Service n°52 |
Multimedia Messaging Service (MMS) |
Option |
|
|
Service n°53 |
Extension 8 |
Option |
|
|
Service n°54 |
Call control on GPRS by USIM |
Option |
|
|
Service n°55 |
MMS User Connectivity Parameters |
Option |
|
|
Service n°56 |
Network’s indication of alerting in the MS (NIA) |
Option |
|
|
Service n°57 |
VGCS Group Identifier List (EFVGCS and EFVGCSS) |
YES |
|
|
Service n°58 |
VBS Group Identifier List (EFVBS and EFVBSS) |
YES |
|
|
Service n°59 |
Pseudonym |
Option |
REL-6 and later |
|
Service n°60 |
User Controlled PLMN selector for WLAN access |
Option |
REL-6 and later |
|
Service n°61 |
Operator Controlled PLMN selector for WLAN access |
Option |
REL-6 and later |
|
Service n°62 |
User controlled WSID list |
Option |
REL-6 and later |
|
Service n°63 |
Operator controlled WSID list |
Option |
REL-6 and later |
|
Service n°64 |
VGCS security |
YES |
REL-6 and later |
|
Service n°65 |
VBS security |
YES |
REL-6 and later |
|
Service n°66 |
WLAN Reauthentication Identity |
Option |
REL-6 and later |
|
Service n°67 |
Multimedia Messages Storage |
Option |
REL-6 and later |
|
Service n°68 |
Generic Bootstrapping Architecture (GBA) |
Option |
REL-6 and later |
|
Service n°69 |
MBMS security |
Option |
REL-6 and later |
|
Service n°70 |
Data download via USSD and USSD application mode |
Option |
REL-6 and later |
|
Service n°71 |
Equivalent HPLMN |
Option |
REL-6 and later |
|
Service n°72 |
Additional TERMINAL PROFILE after UICC activation |
Option |
REL-6 and later |
|
Service n°73 |
Equivalent HPLMN Presentation Indication |
Option |
REL-6 and later |
|
Service n°74 |
Last RPLMN Selection Indication |
Yes |
REL-7 and later |
|
Service n°75 |
OMA BCAST Smart Card Profile |
No |
REL-7 and later |
|
Service n°76 |
GBA-based Local Key Establishment Mechanism |
Option |
REL-7 and later |
|
Service n°77 |
Terminal Applications |
No |
REL-7 and later |
|
Service n°78 |
Service Provider Name Icon |
Option |
REL-8 and later |
|
Service n°79 |
PLMN Network Name Icon |
Option |
REL-8 and later |
|
Service n°80 |
Connectivity Parameters for USIM IP connections |
Option |
REL-8 and later |
|
Service n°81 |
Home I-WLAN Specific Identifier List |
No |
REL-8 and later |
|
Service n°82 |
I-WLAN Equivalent HPLMN Presentation Indication |
No |
REL-8 and later |
|
Service n°83 |
I-WLAN HPLMN Priority Indication |
No |
REL-8 and later |
|
Service n°84 |
I-WLAN Last Registered PLMN |
No |
REL-8 and later |
|
Service n°85 |
EPS Mobility Management Information |
Option |
REL-8 and later |
|
Service n°86 |
Allowed CSG Lists and corresponding indications |
Option |
REL-8 and later |
|
Service n°87 |
Call control on EPS PDN connection by USIM |
No |
REL-8 and later |
|
Service n°88 |
HPLMN Direct Access |
Option |
REL-8 and later |
|
Service n°89 |
eCall Data |
Option |
REL-8 and later |
|
Service nº90 |
Operator CSG Lists and corresponding indications |
Option |
REL-9 and later |
|
Service nº92 |
Support of CSG Display Control |
Option |
REL-9 and later |
8.3.2.9 EFACM (Accumulated Call Meter)
File size: 3 bytes
Default: Byte 1: 00
Byte 2: 00
Byte 3: 00
The above translates to: "Not yet implemented".
8.3.2.10 EFGID1 (Group Identifier Level 1)
The programming of this EF is a test house option.
8.3.2.11 EFGID2 (Group Identifier Level 2)
The programming of this EF is a test house option.
8.3.2.12 EFSPN (Service Provider Name)
The programming of this EF is a test house option.
8.3.2.13 EFPUCT (Price per Unit and Currency Table)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.14 EFCBMI (Cell Broadcast Message identifier selection)
The programming of this EF is a test house option.
The file size is 2n bytes, where n is the number of Cell broadcast message identifier records – each record defining a type of Cell Broadcast message which may be accessed by the UE. Care should be taken when dimensioning the USIM to take into account the number of Cell Broadcast message identifier records required.
8.3.2.15 EFACC (Access Control Class)
The EFACC type A is the default type.
Type A;
File size: 2 Bytes
Default values (BIN): Byte 1: 000000**
Byte 2: ********
The test house may set any single bit shown by "*" to "1". All remaining bits of byte 2 will be set to "0". This determines the access control class of the USIM.
Type B;
Default values (BIN): Byte 1: 111110**
Byte 2: ********
The test house may set any single bit shown by "*" to "1". All remaining bits of byte 2 will be set to "0". This determines the access control class of the USIM.
Type C;
File size: 2 Bytes
Default values (BIN): Byte 1: 100010**
Byte 2: ********
The test house may set any single bit shown by "*" to "1". This determines the access control class of the USIM.
Type D;
Default values (BIN): Byte 1: 011100**
Byte 2: ********
The test house may set any single bit shown by "*" to "1". This determines the access control class of the USIM.
8.3.2.16 EFFPLMN (Forbidden PLMNs)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.17 EFLOCI (Location Information)
File size: 11 Bytes
Default values: Bytes 1 to 4 (HEX): FF FF FF FF (TMSI)
Bytes 5 to 9 (HEX): 42 F6 18 FF FE (LAI)
Byte 10 (HEX): FF (RFU)
Byte 11 (BIN): 00000001 (Location Update Status = "not updated")
Bytes 5 to 9: LAI-MCC = 246 (bytes 5 to 6) and LAI-MNC = 81 (byte 7) are frequently used. The LAC (bytes 8 to 9) is set to "FF FE" since this, in conjunction with byte 11 setting of "01", is used to ensure that the UE performs a location update at the beginning of a test.
Bytes in this file (e.g. TMSI in bytes 1 to 4) may be updated as a result of a location update attempt by the UE.
8.3.2.18 EFAD (Administrative Data)
File size: 4 bytes
Default values Byte 1: 10000000 – (type approval operations)
Byte 2: 00000000
Byte 3: 00000000
Byte 4: 00000010
8.3.2.19 Void
8.3.2.20 EFCBMID (Cell Broadcast Message Identifier for Data Download)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.21 EFECC (Emergency Call Codes)
The programming of this EF is a test house option.
8.3.2.22 EFCBMIR (Cell Broadcast Message Identifier Range selection)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.23 EFPSLOCI (Packet Switched location information)
File size: 14 Bytes
Default values: Bytes 1 to 4 (HEX): FF FF FF FF (P-TMSI)
Bytes 5 to 7 (HEX): FF FF FF (P-TMSI signature value)
Bytes 8 to 13 (HEX): 42 F6 18 FF FE FF (RAI)
Byte 14 (BIN): 00000001 (Routing Area update status = "not updated")
Bytes 8 to 13: RAI-MCC = 246 (bytes 8 to 9) and RAI-MNC = 81 (byte 10) are frequently used. The LAC (bytes 11 to 12) is set to "FF FE" since this, in conjunction with byte 14 setting of "01", is used to ensure that the UE performs a location update at the beginning of a test.
Bytes in this file (e.g. P-TMSI in bytes 1 to 4) may be updated as a result of a location update attempt by the UE.
8.3.2.24 EFFDN (Fixed Dialling Numbers)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.25 EFSMS (Short messages)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.26 EFMSISDN (MSISDN)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.27 EFSMSP (Short message service parameters)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.28 EFSMSS (SMS status)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.29 EFSDN (Service Dialling Numbers)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.30 EFEXT2 (Extension2)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.31 EFEXT3 (Extension3)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.32 EFSMSR (Short message status reports)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.33 EFICI (Incoming Call Information)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.34 EFOCI (Outgoing Call Information)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.35 EFICT (Incoming Call Timer)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.36 EFOCT (Outgoing Call Timer)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.37 EFEXT5 (Extension5)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.38 EFCCP2 (Capability Configuration Parameters 2)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.39 EFeMLPP (enhanced Multi Level Precedence and Pre-emption)
The programming of this EF is a test house option.
8.3.2.40 EFAAeM (Automatic Answer for eMLPP Service)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.41 Void
8.3.2.42 EFHiddenkey (Key for hidden phone book entries)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.43 Void
8.3.2.44 EFBDN (Barred dialling numbers)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.45 EFEXT4 (Extension 4)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.46 EFCMI (Comparison method information)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.47 EFEST (Enabled service table)
The programming of this EF is a test house option.
8.3.2.48 EFACL (Access point name control list)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.49 EFDCK (Depersonalization control keys)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.50 EFCNL (Co-operative network list)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.51 EFSTART-HFN (Initialisation values for Hyperframe number)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.52 EFTHRESHOLD (Maximum value of START)
The programming of this EF is a test house option.
8.3.2.53 EFOPLMNwACT (Operator controlled PLMN selector with Access Technology)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.54 EFHPLMNwAcT (HPLMN selector with Access Technology)
File size: 5n (n ≥ 1) Bytes
Default values: Bytes 1 to 3 (HEX): 00 F1 10 (MCC/MNC of Test UICC’s Home PLMN)
44 F2 10 (MCC/MNC of Band VI and Band IX Test UICC’s Home PLMN
Bytes 4 to 5 (HEX): C8 B0 (all Access Technologies)
Bytes 6 to 5n (HEX): FF FF FF 00 00
FF FF FF 00 00
…
FF FF FF 00 00
Bytes 1 to 3: 1st HPLMN entry with HPLMN-MCC = 001 (442 for Band VI and Band IX) (bytes 1 to 2) and HPLMN-MNC = 01 (byte 3) which are frequently used in multimode and equal the EF IMSI’s default MCC/MNC information.
Bytes 4 to 5: All Access Technologiesy selected for 1st HPLMN entry.
Bytes 6 to 5n: 2nd and more HPLMN entries are empty as per default EF parameters given in 3GPP TS 31.102 [23], annex E.
8.3.2.55 EFARR (Access rule reference)
The programming of this EF is a test house option.
8.3.2.56 Void
8.3.2.57 EFNETPAR (Network Parameters)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.58 EFPNN (PLMN Network Name)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.59 EFOPL (Operator PLMN List)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.60 EFMBDN (Mailbox Dialling Numbers)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.61 EFEXT6 (Extension6)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.62 EFMBI (Mailbox Identifier)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.63 EFMWIS (Message Waiting Indication Status)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.64 EFCFIS (Call Forwarding Indication Status)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.65 EFEXT7 (Extension7)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.66 EFSPDI (Service Provider Display Information)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.67 EFMMSN (MMS Notification)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.68 EFEXT8 (Extension 8)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.69 EFMMSICP (MMS Issuer Connectivity Parameters)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.70 EFMMSUP (MMS User Preferences)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.71 EFMMSUCP (MMS User Connectivity Parameters)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.72 EFNIA (Network’s Indication of Alerting)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
If service n°57 is "available", this file shall be present.
This EF contains a list of those VGCS group identifiers the user has subscribed to. The elementary file is used by the ME for group call establishment and group call reception.
File size: Bytes 200
Default values:
|
Bytes |
Group ID |
Value |
BCD encoding in the USIM |
|---|---|---|---|
|
1-4 |
1 |
12 |
21 FF FF FF |
|
5-8 |
2 |
123 |
21 F3 FF FF |
|
9-12 |
3 |
1234 |
21 43 FF FF |
|
13-16 |
4 |
12348 |
21 43 F8 FF |
|
17-20 |
5 |
123491 |
21 43 19 FF |
|
21-24 |
6 |
1235029 |
21 53 20 F9 |
|
25-28 |
7 |
12351 |
21 53 F1 FF |
|
29-32 |
8 |
12352 |
21 53 F2 FF |
|
33-36 |
9 |
12353 |
21 53 F3 FF |
|
37-40 |
10 |
12354 |
21 53 F4 FF |
|
41-44 |
11 |
12355 |
21 53 F5 FF |
|
45-48 |
12 |
12356 |
21 53 F6 FF |
|
49-52 |
13 |
12357 |
21 53 F7 FF |
|
53-56 |
14 |
12358 |
21 53 F8 FF |
|
57-60 |
15 |
12359 |
21 53 F9 FF |
|
61-64 |
16 |
20000 |
02 00 F0 FF |
|
65-68 |
17 |
20001 |
02 00 F1 FF |
|
69-72 |
18 |
20002 |
02 00 F2 FF |
|
73-76 |
19 |
20003 |
02 00 F3 FF |
|
77-80 |
20 |
20004 |
02 00 F4 FF |
|
81-84 |
21 |
20005 |
02 00 F5 FF |
|
85-88 |
22 |
20006 |
02 00 F6 FF |
|
89-92 |
23 |
20007 |
02 00 F7 FF |
|
93-96 |
24 |
20008 |
02 00 F8 FF |
|
97-100 |
25 |
20009 |
02 00 F9 FF |
|
101-104 |
26 |
20010 |
02 10 F0 FF |
|
105-108 |
27 |
66660 |
66 66 F0 FF |
|
109-112 |
28 |
66661 |
66 66 F1 FF |
|
113-116 |
29 |
66662 |
66 66 F2 FF |
|
117-120 |
30 |
666638 |
66 66 83 FF |
|
121-124 |
31 |
66664 |
66 66 F4 FF |
|
125-128 |
32 |
66665 |
66 66 F5 FF |
|
129-132 |
33 |
66666 |
66 66 F6 FF |
|
133-136 |
34 |
66667 |
66 66 F7 FF |
|
137-140 |
35 |
66668 |
66 66 F8 FF |
|
141-144 |
36 |
66669 |
66 66 F9 FF |
|
145-148 |
37 |
66670 |
66 76 F0 FF |
|
149-152 |
38 |
80120 |
08 21 F0 FF |
|
153-156 |
39 |
80121 |
08 21 F1 FF |
|
157-160 |
40 |
80122 |
08 21 F2 FF |
|
161-164 |
41 |
80123 |
08 21 F3 FF |
|
165-168 |
42 |
80124 |
08 21 F4 FF |
|
169-172 |
43 |
80125 |
08 21 F5 FF |
|
173-176 |
44 |
80126 |
08 21 F6 FF |
|
177-180 |
45 |
80127 |
08 21 F7 FF |
|
181-184 |
46 |
80128 |
08 21 F8 FF |
|
185-188 |
47 |
80129 |
08 21 F9 FF |
|
189-192 |
48 |
80130 |
08 31 F0 FF |
|
193-196 |
49 |
99999 |
99 99 F9 FF |
|
197-200 |
50 |
1111119 |
11 11 11 F9 |
For Group Id = 1 V_Ki with VK_Id = 0:
Size: 16 Bytes
Default values: Bytes 1 (HEX): 00
Bytes 2 (HEX): 01
Bytes 3 (HEX): 02
Bytes 4 (HEX): 03
Bytes 5 (HEX): 04
Bytes 6 (HEX): 05
Bytes 7 (HEX): 06
Bytes 8 (HEX): 07
Bytes 9 (HEX): 08
Bytes 10 (HEX): 09
Bytes 11 (HEX): 0A
Bytes 12 (HEX): 0B
Bytes 13 (HEX): 0C
Bytes 14 (HEX): 0D
Bytes 15 (HEX): 0E
Bytes 16 (HEX): 0F
Group Id= 1: V_Ki with VK_Id = 1:
Size: 16 Bytes
Default values: Bytes 1 (HEX): 01
Bytes 2 (HEX): 02
Bytes 3 (HEX): 03
Bytes 4 (HEX): 04
Bytes 5 (HEX): 05
Bytes 6 (HEX): 06
Bytes 7 (HEX): 07
Bytes 8 (HEX): 08
Bytes 9 (HEX): 09
Bytes 10 (HEX): 0A
Bytes 11 (HEX): 0B
Bytes 12 (HEX): 0C
Bytes 13 (HEX): 0D
Bytes 14 (HEX): 0E
Bytes 15 (HEX): 0F
Bytes 16 (HEX): 00
8.3.2.74 EFVGCSS (Voice Group Call Service Status)
.If service n°57 is "available", this file shall be present.
This EF contains the status of activation for the VGCS group identifiers. The elementary file is directly related to the EFVGCS. This EF shall always be allocated if EFVGCS is allocated. The following list of group ID are activated: 1, 4, 20, 30, 50.
File size: 7 Bytes
Default value(HEX) : Bytes 1-7: ’09 00 08 20 00 00 FE’
8.3.2.75 EFVBS (Voice Broadcast Service)
If service n°58 is "available", this file shall be present.
This EF contains a list of those VBS group identifiers the user has subscribed to. The elementary file is used by the ME for broadcast call establishment and broadcast call reception.
File size: Bytes 200
Default values:
|
Bytes |
Group ID |
Value |
BCD encoding in the USIM |
|---|---|---|---|
|
1-4 |
1 |
12 |
21 FF FF FF |
|
5-8 |
2 |
123 |
21 F3 FF FF |
|
9-12 |
3 |
1234 |
21 43 FF FF |
|
13-16 |
4 |
12348 |
21 43 F8 FF |
|
17-20 |
5 |
123491 |
21 43 19 FF |
|
21-24 |
6 |
1235029 |
21 53 20 F9 |
|
25-28 |
7 |
12351 |
21 53 F1 FF |
|
29-32 |
8 |
12352 |
21 53 F2 FF |
|
33-36 |
9 |
12353 |
21 53 F3 FF |
|
37-40 |
10 |
12354 |
21 53 F4 FF |
|
41-44 |
11 |
12355 |
21 53 F5 FF |
|
45-48 |
12 |
12356 |
21 53 F6 FF |
|
49-52 |
13 |
12357 |
21 53 F7 FF |
|
53-56 |
14 |
12358 |
21 53 F8 FF |
|
57-60 |
15 |
12359 |
21 53 F9 FF |
|
61-64 |
16 |
20000 |
02 00 F0 FF |
|
65-68 |
17 |
20001 |
02 00 F1 FF |
|
69-72 |
18 |
20002 |
02 00 F2 FF |
|
73-76 |
19 |
20003 |
02 00 F3 FF |
|
77-80 |
20 |
20004 |
02 00 F4 FF |
|
81-84 |
21 |
20005 |
02 00 F5 FF |
|
85-88 |
22 |
20006 |
02 00 F6 FF |
|
89-92 |
23 |
20007 |
02 00 F7 FF |
|
93-96 |
24 |
20008 |
02 00 F8 FF |
|
97-100 |
25 |
20009 |
02 00 F9 FF |
|
101-104 |
26 |
20010 |
02 10 F0 FF |
|
105-108 |
27 |
66660 |
66 66 F0 FF |
|
109-112 |
28 |
66661 |
66 66 F1 FF |
|
113-116 |
29 |
66662 |
66 66 F2 FF |
|
117-120 |
30 |
666638 |
66 66 83 FF |
|
121-124 |
31 |
66664 |
66 66 F4 FF |
|
125-128 |
32 |
66665 |
66 66 F5 FF |
|
129-132 |
33 |
66666 |
66 66 F6 FF |
|
133-136 |
34 |
66667 |
66 66 F7 FF |
|
137-140 |
35 |
66668 |
66 66 F8 FF |
|
141-144 |
36 |
66669 |
66 66 F9 FF |
|
145-148 |
37 |
66670 |
66 76 F0 FF |
|
149-152 |
38 |
80120 |
08 21 F0 FF |
|
153-156 |
39 |
80121 |
08 21 F1 FF |
|
157-160 |
40 |
80122 |
08 21 F2 FF |
|
161-164 |
41 |
80123 |
08 21 F3 FF |
|
165-168 |
42 |
80124 |
08 21 F4 FF |
|
169-172 |
43 |
80125 |
08 21 F5 FF |
|
173-176 |
44 |
80126 |
08 21 F6 FF |
|
177-180 |
45 |
80127 |
08 21 F7 FF |
|
181-184 |
46 |
80128 |
08 21 F8 FF |
|
185-188 |
47 |
80129 |
08 21 F9 FF |
|
189-192 |
48 |
80130 |
08 31 F0 FF |
|
193-196 |
49 |
99999 |
99 99 F9 FF |
|
197-200 |
50 |
1111119 |
11 11 11 F9 |
8.3.2.76 EFVBSS (Voice Broadcast Service Status)
If service n°58 is "available", this file shall be present.
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.
The following list of group ID are activated: 1, 4, 20, 30, 50.
File size: 7 Bytes
Default values (HEX): Bytes 1-7: ’09 00 08 20 00 00 FE’
For Group ID= 1 V_Ki with VK_Id = 0:
Size: 16 Bytes
Default values: Bytes 1 (HEX): 0F
Bytes 2 (HEX): 0E
Bytes 3 (HEX): 0D
Bytes 4 (HEX): 0C
Bytes 5 (HEX): 0B
Bytes 6 (HEX): 0A
Bytes 7 (HEX): 09
Bytes 8 (HEX): 08
Bytes 9 (HEX): 07
Bytes 10 (HEX): 06
Bytes 11 (HEX): 05
Bytes 12 (HEX): 04
Bytes 13 (HEX): 03
Bytes 14 (HEX): 02
Bytes 15 (HEX): 01
Bytes 16 (HEX): 00
For Group Id=1 V_Ki with VK_Id = 1:
Size: 16 Bytes
Default values: Bytes 1 (HEX): 00
Bytes 2 (HEX): 0F
Bytes 3 (HEX): 0E
Bytes 4 (HEX): 0D
Bytes 5 (HEX): 0C
Bytes 6 (HEX): 0B
Bytes 7 (HEX): 0A
Bytes 8 (HEX): 09
Bytes 9 (HEX): 08
Bytes 10 (HEX): 07
Bytes 11 (HEX): 06
Bytes 12 (HEX): 05
Bytes 13 (HEX): 04
Bytes 14 (HEX): 03
Bytes 15 (HEX): 02
Bytes 16 (HEX): 01
8.3.2.77 EFVGCSCA (Voice Group Call Service Ciphering Algorithm)
If service n°64 is "available", this file shall be present.
This EF contains the ciphering algorithm identifiers for each of the Master Group Key (V_Ki) of each VGCS group that the user has subscribed to (defined in EFVGCS).
File size: 2 Bytes
Default value: Byte 1 = ‘01’ (i.e. A5/1) and Byte 2 = ‘03’ (i.e. A5/3)
8.3.2.78 EFVBSCA (Voice Broadcast Service Ciphering Algorithm)
If service n°65 is "available", this file shall be present.
This EF contains the ciphering algorithm identifiers for each of the Master Group Key (V_Ki) of each VBS group that the user has subscribed to (defined in EFVBS).
File size: 2 Bytes
Default value: Byte 1 = ‘01’ (i.e. A5/1) and Byte 2 = ‘03’ (i.e. A5/3)
8.3.2.79 EFGBABP (GBA Bootstrapping parameters)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.80 EFMSK (MBMS Service Keys List)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.81 EFMUK (MBMS User Key)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.82 Void
8.3.2.83 EFGBANL (GBA NAF List)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.84 EFEHPLMN (Equivalent HPLMN)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.85 EFEHPLMNPI (Equivalent HPLMN Presentation Indication)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.86 EFLRPLMNSI (Last RPLMN Selection Indication)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.87 EFNAFKCA (NAF Key Centre Address)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.88 EFSPNI (Service Provider Name Icon)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.89 EFPNNI (PLMN Network Name Icon)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.90 EFNCP-IP (Network Connectivity Parameters for USIM IP connections)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.2.91 EFEPSLOCI (EPS location information)
The programming of this EF is a test house option.
8.3.2.92 EFEPSNSC (EPS NAS Security Context)
The programming of this EF is a test house option.
8.3.3 Contents of DFs at the USIM ADF (Application DF) level
8.3.3.1 Contents of files at the USIM SoLSA level
8.3.3.1.1 EFSAI (SoLSA Access Indicator)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.1.2 EFSLL (SoLSA LSA List)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.1.3 LSA Descriptor files
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.1.4 Contents of files at the MExE level
8.3.3.1.4.1 EFMExE-ST (MExE Service table)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.1.4.2 EFORPK (Operator Root Public Key)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.1.4.3 EFARPK (Administrator Root Public Key)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.1.4.4 EFTPRPK (Third Party Root Public Key)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.1.4.5 EFTKCDF (Trusted Key/Certificates Data Files)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.2 Contents of files at the DF PHONEBOOK level
8.3.3.2.1 EFPBR (Phone Book Reference file)
The programming of this EF is a test house option.
8.3.3.2.2 EFIAP (Index Administration Phone book)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.2.3 EFADN (Abbreviated dialling numbers)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.2.4 EFEXT1 (Extension1)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.2.5 EFPBC (Phone Book Control)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.2.6 EFGRP (Grouping file)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.2.7 EFAAS (Additional number Alpha String)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.2.8 EFGAS (Grouping information Alpha String)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.2.9 EFANR (Additional Number)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.2.10 EFSNE (Second Name Entry)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.2.11 EFCCP1 (Capability Configuration Parameters 1)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.2.12 Phone Book Synchronization
8.3.3.2.12.1 EFUID (Unique Identifier)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.2.12.2 EFPSC (Phone book Synchronization Counter)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.2.12.3 EFCC (Change Counter)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.2.12.4 EFPUID (Previous Unique Identifier)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.2.13 EFEMAIL (e-mail address)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.3 Contents of files at the DF GSM-ACCESS level (Files required for GSM Access)
8.3.3.3.1 EFKc (GSM Ciphering key Kc)
File size: 9 Bytes
Default values (HEX): Bytes 1 to 8: Align with Kc used by SS
Byte 9: 07
Byte 9 is set to 07 to indicate that there is no key available at the start of a test.
The bytes within this elementary file may be updated by the UE as a result of a successful authentication attempt.
8.3.3.3.2 EFKcGPRS (GPRS Ciphering key KcGPRS)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.3.3 Void
8.3.3.3.4 EFCPBCCH (CPBCCH Information)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.3.3.5 EFInvScan (Investigation Scan)
The programming of this EF follows default parameter.
8.3.3.4 Contents of files at the DF HNB level
8.3.3.4.1 EFACSGL (Allowed CSG Lists)
The programming of this EF is a test house option.
8.3.3.4.2 EFCSGT (CSG Type)
The programming of this EF is a test house option.
8.3.3.4.3 EFHNBN (Home NodeB Name)
The programming of this EF is a test house option.
8.3.3.4.4 EFOCSGL (Operator CSG Lists)
The programming of this EF is a test house option.
8.3.3.4.5 EFOCSGT (Operator CSG Type)
The programming of this EF is a test house option.
8.3.3.4.6 EFOHNBN (Operator Home NodeB Name)
The programming of this EF is a test house option.
8.3.4 Contents of EFs at the TELECOM level
8.3.4.1 EFADN (Abbreviated dialling numbers)
The programming of this EF is a test house option. It should be noted that sufficient space should be provided on the USIM card for 101 records.
8.3.4.2 EFEXT1 (Extension1)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.4.3 EFECCP (Extended Capability Configuration Parameter)
The programming of this EF is a test house option.
8.3.4.4 EFSUME (SetUpMenu Elements)
The programming of this EF is a test house option.
8.3.4.5 EFARR (Access rule reference)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.5 Contents of DFs at the TELECOM level
8.3.5.1 Contents of files at the DFGRAPHICS level
8.3.5.1.1 EFIMG (Image)
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.5.1.2 Image Instance Data Files
The programming of this EF follows default parameter written in 3GPP TS 31.102 [23], annex E.
8.3.5.2 Contents of files at the DFPHONEBOOK under the DFTELECOM
The programming of this EF is a test house option.